Internet Draft Thomas D. Nadeau Expires: December 2004 Cisco Systems, Inc. Dave Danenberg David Zelig Corrigent Systems Andrew G. Malis Tellabs, Inc. June 2004 Definitions for Textual Conventions and OBJECT-IDENTITIES for Pseudo-Wires Management draft-ietf-pwe3-pw-tc-mib-05.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright (C) The Internet Society (2001). All rights reserved. 1 Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes the textual conventions to be used in the various Pseudo Wire (PW) MIB modules. Nadeau et al. Expires December 2004 [page 1] PWE3 TC MIB June 2004 Table of Contents 1 Abstract.......................................................1 2 Introduction...................................................2 3 Terminology....................................................2 4 The Internet-Standard Management Framework.....................2 5 Object Definition..............................................3 6 Security Considerations........................................9 7 IANA considerations............................................9 8 References....................................................10 8.1 Normative References........................................10 8.2 Informative references......................................11 9 Author's Addresses............................................11 10 Full Copyright Statement....................................11 11 Intellectual Property Notice................................12 2 Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines Textual Conventions used in IETF PW and PW-related MIBs. Comments should be made directly to the MPLS mailing list at pwe3@ietf.org. For an introduction to the concepts of Pseudo-Wires, see [PWREQ] and [PWARCH]. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [BCP14]. 3 Terminology This document uses terminology from the document describing the PW architecture [PWARCH]. 4 The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Nadeau et al Expires December 2004 [page 2] PWE3 TC MIB June 2004 Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 5 Object Definition PW-TC-DRAFT05-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Unsigned32, Integer32, transmission FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC; pwTCMIB MODULE-IDENTITY LAST-UPDATED "200406141200Z" -- 14 June 2004 12:00:00 GMT ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working Group" CONTACT-INFO " Thomas D. Nadeau Postal: Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-497-3051 Email: tnadeau@cisco.com Dave Danenberg Email: dave_danenberg@yahoo.com David Zelig Postal: Corrigent Systems. 126, Yigal Alon St. Tel Aviv, ISRAEL Phone: +972-3-6945273 E-mail: davidz@corrigent.com Andrew G. Malis Postal: Tellabs, Inc. 2730 Orchard Parkway San Jose, CA 95134 Email: Andy.Malis@tellabs.com The PWE3 Working Group (email distribution pwe3@ietf.org, http://www.ietf.org/html.charters/pwe3-charter.html) " Nadeau et al Expires December 2004 [page 3] PWE3 TC MIB June 2004 DESCRIPTION "This MIB Module provides Textual Conventions and OBJECT-IDENTITY Objects to be used in networks implementing PW services. Copyright (C) The Internet Society (date). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices. -- RFC Ed.: replace yyyy with actual RFC number & remove this note " -- Revision history. REVISION "200406141200Z" -- 14 June 2004 12:00:00 GMT DESCRIPTION " Changes from previous drafts: - Update PW types based on new IANA draft -04. - FCS Retention status has been updated to include FCS size mismatch. " REVISION "200402031200Z" -- 3 February 2004 12:00:00 GMT DESCRIPTION " Changes from previous drafts: - Change IANA request text. - Change PwVcRemoteCwStatus to PwVcCwStatus and add two enum so the textual convention will indicate the full status of the CW negotiation including the final result. " REVISION "200311301200Z" -- 30 November 2003 12:00:00 GMT DESCRIPTION " Changes from previous drafts: - Removing non-necessary textual convention. - Adapt description of main clause based on MIB boilerplate. " REVISION "200307281200Z" -- 28 July 2003 12:00:00 GMT DESCRIPTION "Adding objects to cover new control draft. Adapt VC types for current values in WG documents." REVISION "200305011200Z" -- 1 May 2003 12:00:00 GMT DESCRIPTION "Adding PwVcAttachmentIdentifierType, Adapt VC types for current values in WG documents." REVISION "200205281200Z" -- 28 May 2002 12:00:00 GMT DESCRIPTION "Adding PwVcType, and enhance some descriptions." REVISION "200201301200Z" -- 30 January 2002 12:00:00 GMT DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and PwOperStatus." REVISION "200112201200Z" -- 20 Dec 2001 12:00:00 GMT DESCRIPTION "Remove PwVcInstance" Nadeau et al Expires December 2004 [page 4] PWE3 TC MIB June 2004 REVISION "200107121200Z" -- 12 July 2001 12:00:00 GMT DESCRIPTION "Initial version." -- Please see the IANA Considerations Section. -- The requested pwStdMIB subId is 1, e.g. -- ::= { pwStdMIB 1 } ::= { pwStdMIB x } pwStdMIB OBJECT IDENTIFIER -- This object identifier needs to be assigned by IANA. ::= { transmission xxx } PwGroupID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An administrative identification mechanism for grouping a set of service-specific pseudo-wire services. May only have local significance." SYNTAX Unsigned32 PwVcIDType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Pseudo-Wire Identifier. Used to identify the PW (together with some other fields) in the signaling session. Zero if the PW is set-up manually." SYNTAX Unsigned32 PwVcIndexType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Pseudo Wire Index. Locally unique index for indexing several MIB tables associated with a particular PW." SYNTAX Unsigned32 PwVcVlanCfg ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "VLAN configuration for Ethernet PW. Values between 0 to 4095 indicate the actual VLAN field value. A value of 4096 indicates that the object refer to untagged frames, i.e. frames without 802.1Q field. A value of 4097 indicates that the object is not relevant." SYNTAX Integer32 (0..4097) Nadeau et al Expires December 2004 [page 5] PWE3 TC MIB June 2004 PwOperStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the operational status of the PW. - up(1): Ready to pass packets. - down(2): If PW signaling has not yet finished, or indications available at the service level indicate that the VC is not passing packets. - testing(3): If AdminStatus at the PW level is set to test. - dormant(4): The PW is not available because of the required resources are occupied PW with higher priority PWs . - notPresent(5): Some component is missing to accomplish the set up of the PW. - lowerLayerDown(6):The underlying PSN or outer tunnel is not in OperStatus 'up' state. " SYNTAX INTEGER { up(1), down(2), testing(3), unknown(4), dormant(5), notPresent(6), lowerLayerDown(7) } PwVcType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the PW type (i.e. the carried service). " SYNTAX INTEGER { other(0), frameRelayDlci(1), atmAal5SduVcc(2), atmTransparent(3), ethernetTagged(4), ethernet(5), hdlc(6), ppp(7), cem(8), -- old format atmCellNto1Vcc(9), atmCellNto1Vpc(10), ipLayer2Transport(11), atmCell1to1Vcc(12), atmCell1to1Vpc(13), atmAal5PduVcc(14), Nadeau et al Expires December 2004 [page 6] PWE3 TC MIB June 2004 frameRelayPortMode(15), cep(16), e1Satop(17), t1Satop(18), e3Satop(19), t3Satop(20), basicCesPsn(21), basicTdmIp(22), tdmCasCesPsn(23), tdmCasTdmIp(24) } PwVcAttachmentIdentifierType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An octet string used in the generalized FEC element for identifying attachment forwarder and groups. The NULL identifier is of zero length. " SYNTAX OCTET STRING (SIZE (0..255)) PwVcCwStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the status of the control word negotiation based on the local configuration and the indications received from the peer node. waitingForNextMsg(1) indicates that the node is waiting for another label mapping from the remote. sentWrongBitErrorCode(2) indicates that the local node has notified the peer about mismatch in the C bit. rxWithdrawWithWrongBitErrorCode(3) indicates that a withdraw message has been received with the wrong C-bit error code. illegalReceivedBit(4) indicates a C bit configuration with the remote which is not compatible with the PW type. cwPresent(5) indicates that the CW is present for this PW: if signaling is used - C bit is set and agreed between the peers, and for manual configured PW the local configuration require the use of the CW. cwNotPresent(6) indicates that the CW is not present for this PW: if signaling is used - C bit is reset and agreed between the peers, and for manual configured PW the local configuration requires that CW would not be used. Nadeau et al Expires December 2004 [page 7] PWE3 TC MIB June 2004 notYetKnown(7) indicate that a label mapping has not yet received from the peer. " SYNTAX INTEGER { waitingForNextMsg (1), sentWrongBitErrorCode (2), rxWithdrawWithWrongBitErrorCode (3), illegalReceivedBit (4), cwPresent (5), cwNotPresent (6), notYetKnown(7) } PwVcCapabilities ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the optional capabilities of the control protocol. A value of zero indicates the basic LDP PW signaling. Values may be added in the future based on new capabilities introduced in IETF documents. " SYNTAX BITS { pwStatusIndication (0) } PwVcStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The status of the PW and the interfaces affecting this PW. If none of the bits are set, it indicate no faults are reported. " SYNTAX BITS { pwNotForwarding (0), customerFacingPwRxFault (1), customerFacingPwTxFault (2), psnFacingPwRxFault (3), psnFacingPwTxFault (4) } PwVcFragSize ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "If set to value other than zero, it indicates desired fragmentation to the value set. If set to zero, fragmentation is not desired for PSN bound packets. " SYNTAX Unsigned32 PwVcFragStatus ::= TEXTUAL-CONVENTION Nadeau et al Expires December 2004 [page 8] PWE3 TC MIB June 2004 STATUS current DESCRIPTION "The status of the fragmentation process based on local configuration and the remote capability. noFrag(0) bit indicates that local configuration is for no fragmentation. cfgFragGreaterThanPsnMtu(1) bit indicates the local desire to fragment, but the fragmentation size desired is greater than the MTU available at the PSN between peers. Fragmentation is not done in this case. cfgFragButRemoteIncapable(2) bit indicates that the local configuration indicates the desire for fragmentation but the remote is not capable of fragmentation. cfgFragFcsLengthMismatch(3) bit indicates that there is a mismatch between the FCS size between the local configuration and the remote configuration. fragEnabled(4) bit indicates that both the local was configured for fragmentation and the remote has the cabability to accept fragmented packets, and the FCS size is equal in both peers. " SYNTAX BITS { noFrag (0), cfgFragGreaterThanPsnMtu (1), cfgFragButRemoteIncapable (2), remoteFragCapable (3), fragEnabled (4) } END 6 Security Considerations This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MPLS MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. Therefore, this document has no impact on the security of the Internet. 7 IANA considerations IANA is requested to make a MIB OID assignment under the transmission branch, that is, assign the pwStdMIB under Nadeau et al Expires December 2004 [page 9] PWE3 TC MIB June 2004 { transmission TBD }. In the future, PWE3 related standards track PW modules should be rooted under the pwStdMIB subtree. The IANA is requested to manage that namespace. New assignments can only be made via a Standards Action as specified in [RFC2434]. This document also requests IANA to assign { pwStdMIB 1 } to the PW MIB specified in this document. 8 References 8.1 Normative References [PWREQ] Xio, X., et al, "Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)", work-in-progress. [PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in- progress. [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1700, October 1994. See also: http://www.isi.edu/in- notes/iana/assignments/smi-numbers [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS,(http://www.isi.edu/in- notes/iana/assignements/address-family-numbers), for MIB see: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib [PWE3IANA] Martini, L., et al., ôIANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)ö, work-in-progress. [BCP14] Bradner, S., "Key words for use in RFCs to Indicate requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP: 26, RFC 2434, October 1998. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. Nadeau et al Expires December 2004 [page 10] PWE3 TC MIB June 2004 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. 8.2 Informative references [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. 9 Author's Addresses Thomas D. Nadeau Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Email: tnadeau@cisco.com Dave Danenberg Email: dave_danenberg@yahoo.com David Zelig Corrigent Systems 126, Yigal Alon st. Tel Aviv, ISRAEL Phone: +972-3-6945273 Email: davidz@corrigent.com Andrew G. Malis Tellabs, Inc. 2730 Orchard Parkway San Jose, CA 95134 Email: Andy.Malis@tellabs.com 10 Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process Nadeau et al Expires December 2004 [page 11] PWE3 TC MIB June 2004 must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 11 Intellectual Property Notice The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11 [RFC2028]. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Nadeau et al Expires December 2004 [page 12]