--- 1/draft-ietf-ccamp-rfc4327bis-00.txt 2006-02-22 20:12:19.000000000 +0100 +++ 2/draft-ietf-ccamp-rfc4327bis-01.txt 2006-02-22 20:12:20.000000000 +0100 @@ -1,25 +1,25 @@ Network Working Group M. Dubuc Internet Draft T. Nadeau -Replaces RFC 4327 Cisco Systems +Obsoletes RFC 4327 Cisco Systems Category: Standard Track J. Lang Sonos, Inc. E. McGinnis Hammerhead Systems A. Farrel Old Dog Consulting - January 2006 + February 2006 Link Management Protocol (LMP) Management Information Base (MIB) - draft-ietf-ccamp-rfc4327bis-00.txt + draft-ietf-ccamp-rfc4327bis-01.txt Status of This Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -36,21 +36,21 @@ The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2006). Abstract - This document provides minor corrections to RFC 4327. + This document provides minor corrections to and obsoletes RFC 4327. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling the Link Management Protocol (LMP). Table of Contents 1. The Internet-Standard Management Framework ......................3 2. Introduction ....................................................3 @@ -69,43 +69,25 @@ 7. Example of LMP Control Channel Setup ............................6 8. Application of the Interfaces Group to LMP ......................9 8.1. Support of the LMP Layer by ifTable .......................10 9. LMP MIB Module Definitions .....................................12 10. Security Considerations .......................................76 11. Contributors ..................................................77 12. Acknowledgements ..............................................77 13. IANA Considerations ...........................................77 13.1. IANA Considerations for lmp ifType .......................77 13.2. IANA Considerations for LMP-MIB ..........................77 - 14. References ....................................................77 - 14.1. Normative References .....................................77 - 14.2. Informative References ...................................78 - 15. Authors' Addresses ............................................79 - - - -Changes from RFC 4327 - -a. Show that this document replaces RFC 4327. -b. Indicate in Abstract that this document provides minor corrections to - RFC 4327. -c. Correct use of TruthValue settings such that True is always 1, and - False is always 2. -d. Update to acknowledgements section. -e. Note in IANA section to show no further action required. -f. Remove identification of RFC 4327 and request RFC Editor to insert - new RFC number. -g. Update timestamps. -h. Update author information. -i. Added punctuation to REFERENCE clauses. - - + 14. Changes from RFC 4327 to RFC XXXX .............................78 + 15. References ....................................................78 + 15.1. Normative References .....................................78 + 15.2. Informative References ...................................79 + 16. Authors' Addresses ............................................79 1. 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]. 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). @@ -536,21 +518,21 @@ InterfaceIndexOrZero, ifIndex FROM IF-MIB -- RFC 2863 InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC 4001 teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType FROM TE-LINK-STD-MIB; -- RFC 4220 lmpMIB MODULE-IDENTITY - LAST-UPDATED "200601170000Z" -- 17 January 2006 + LAST-UPDATED "200602190000Z" -- 19 February 2006 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) Working Group" CONTACT-INFO " Martin Dubuc Email: dubuc.consulting@sympatico.ca Thomas D. Nadeau Email: tnadeau@cisco.com Jonathan P. Lang @@ -558,34 +540,43 @@ Evan McGinnis Email: emcginnis@hammerheadsystems.com Adrian Farrel Email: adrian@olddog.co.uk" DESCRIPTION "Copyright (C) 2006 The Internet Society. This version of the MIB module is part of RFC XXXX; see the RFC itself for full legal notices. --- RFC Editor. Please replace XXXX with new RFC number and remove this --- note. +-- RFC Editor. Please replace XXXX with new RFC number and remove +-- this note. This MIB module contains managed object definitions for the Link Management Protocol (LMP) as defined in 'Link Management Protocol'." -- Revision history. REVISION - "200601170000Z" -- 17 January 2006 + "200602190000Z" -- 19 February 2006 DESCRIPTION - "Initial version published as RFC XXXX" --- RFC Editor. Please replace XXXX with new RFC number and remove this --- note. + "Revised version to: + - fix textual descriptions of TruthValue settings such that True + is always 1, and False is always 2. + - add punctuation to REFERENCE clauses. + + This revision published as RFC XXXX" +-- RFC Editor. Please replace XXXX with new RFC number and remove +-- this note. + REVISION + "200601110000Z" -- 11 January 2006 + DESCRIPTION + "Initial version published as RFC 4327" ::= { transmission 227 } -- Textual Conventions LmpInterval ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The interval delay in milliseconds." SYNTAX Unsigned32 (1..65535) @@ -3734,42 +3725,66 @@ EMail: sudheer@ieee.org 12. Acknowledgements The general structure of this document has been modeled around the MPLS Label Switching Router (LSR) MIB [RFC3813]. The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and George Wang. - Thanks to Tom Petch for spotting inconsistencies in RFC 4327. + Thanks to Tom Petch for spotting inconsistencies in RFC 4327 and to + Bert Wijnen for document review. 13. IANA Considerations No new IANA actions are requested in this document. All IANA actions from RFC 4327 still hold and are reproduced here for information. Note that new assignments can only be made via a Standards Action as specified in [RFC2434]. 13.1. IANA Considerations for lmp ifType The IANA has assigned 227 ifType for LMP interfaces. 13.2. IANA Considerations for LMP-MIB The IANA has assigned { transmission 227 } to the LMP-MIB module specified in this document. -14. References +14. Changes from RFC 4327 to RFC XXXX +-- RFC Editor: Please replace XXXX with the assigned RFC number and +-- remove this note. -14.1. Normative References + The following changes have been made relative to RFC 4327. + + a. Show that this document obsoletes RFC 4327. + b. Indicate in Abstract that this document provides minor corrections + to RFC 4327. + c. Correct use of TruthValue settings such that True is always 1, and + False is always 2. + d. Update to acknowledgements section. + e. Note in IANA section to show no further action required. + f. Remove identification of RFC 4327 and request RFC Editor to insert + new RFC number. + g. Update timestamps. + h. Update author information. + i. Added punctuation to REFERENCE clauses. + j. Update Revision History clause. + k. Add this section. + l. Remove square braces from references to external documents from + within the MIB module itself. + +15. References + +15.1. Normative References [RFC2119] 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., and J. Schoenwaelder, "Structure of Management Information Version 2 @@ -3807,38 +3822,37 @@ [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems", RFC 4209, October 2005. [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering Link Management Information Base", RFC 4220, November 2005. -14.2. Informative References +15.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. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004. -15. Authors' Addresses +16. Authors' Addresses Martin Dubuc EMail: dubuc.consulting@sympatico.ca - Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719 EMail: tnadeau@cisco.com Jonathan P. Lang Sonos, Inc. 223 E. De La Guerra St.