draft-ietf-ccamp-rfc4327bis-00.txt   draft-ietf-ccamp-rfc4327bis-01.txt 
Network Working Group M. Dubuc Network Working Group M. Dubuc
Internet Draft T. Nadeau Internet Draft T. Nadeau
Replaces RFC 4327 Cisco Systems Obsoletes RFC 4327 Cisco Systems
Category: Standard Track J. Lang Category: Standard Track J. Lang
Sonos, Inc. Sonos, Inc.
E. McGinnis E. McGinnis
Hammerhead Systems Hammerhead Systems
A. Farrel A. Farrel
Old Dog Consulting Old Dog Consulting
January 2006 February 2006
Link Management Protocol (LMP) Management Information Base (MIB) Link Management Protocol (LMP) Management Information Base (MIB)
draft-ietf-ccamp-rfc4327bis-00.txt draft-ietf-ccamp-rfc4327bis-01.txt
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 47 skipping to change at page 1, line 47
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract 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) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Link In particular, it describes managed objects for modeling the Link
Management Protocol (LMP). Management Protocol (LMP).
Table of Contents Table of Contents
1. The Internet-Standard Management Framework ......................3 1. The Internet-Standard Management Framework ......................3
2. Introduction ....................................................3 2. Introduction ....................................................3
skipping to change at page 2, line 31 skipping to change at page 2, line 31
7. Example of LMP Control Channel Setup ............................6 7. Example of LMP Control Channel Setup ............................6
8. Application of the Interfaces Group to LMP ......................9 8. Application of the Interfaces Group to LMP ......................9
8.1. Support of the LMP Layer by ifTable .......................10 8.1. Support of the LMP Layer by ifTable .......................10
9. LMP MIB Module Definitions .....................................12 9. LMP MIB Module Definitions .....................................12
10. Security Considerations .......................................76 10. Security Considerations .......................................76
11. Contributors ..................................................77 11. Contributors ..................................................77
12. Acknowledgements ..............................................77 12. Acknowledgements ..............................................77
13. IANA Considerations ...........................................77 13. IANA Considerations ...........................................77
13.1. IANA Considerations for lmp ifType .......................77 13.1. IANA Considerations for lmp ifType .......................77
13.2. IANA Considerations for LMP-MIB ..........................77 13.2. IANA Considerations for LMP-MIB ..........................77
14. References ....................................................77 14. Changes from RFC 4327 to RFC XXXX .............................78
14.1. Normative References .....................................77 15. References ....................................................78
14.2. Informative References ...................................78 15.1. Normative References .....................................78
15. Authors' Addresses ............................................79 15.2. Informative References ...................................79
16. Authors' Addresses ............................................79
<Note to be removed before submission for publication as an RFC>
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.
</End of note to be removed before submission for publication as an RFC>
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 12, line 35 skipping to change at page 12, line 35
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; -- RFC 4220 FROM TE-LINK-STD-MIB; -- RFC 4220
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200601170000Z" -- 17 January 2006 LAST-UPDATED "200602190000Z" -- 19 February 2006
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@sympatico.ca Email: dubuc.consulting@sympatico.ca
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
skipping to change at page 13, line 8 skipping to change at page 13, line 8
Evan McGinnis Evan McGinnis
Email: emcginnis@hammerheadsystems.com Email: emcginnis@hammerheadsystems.com
Adrian Farrel Adrian Farrel
Email: adrian@olddog.co.uk" Email: adrian@olddog.co.uk"
DESCRIPTION DESCRIPTION
"Copyright (C) 2006 The Internet Society. This version of "Copyright (C) 2006 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC XXXX; see the RFC itself
for full legal notices. for full legal notices.
-- RFC Editor. Please replace XXXX with new RFC number and remove
-- this note.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200601170000Z" -- 17 January 2006 "200602190000Z" -- 19 February 2006
DESCRIPTION DESCRIPTION
"Initial version published as RFC XXXX" "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 } ::= { transmission 227 }
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 77, line 26 skipping to change at page 77, line 26
EMail: sudheer@ieee.org EMail: sudheer@ieee.org
12. Acknowledgements 12. Acknowledgements
The general structure of this document has been modeled around the The general structure of this document has been modeled around the
MPLS Label Switching Router (LSR) MIB [RFC3813]. MPLS Label Switching Router (LSR) MIB [RFC3813].
The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and
George Wang. 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 13. IANA Considerations
No new IANA actions are requested in this document. All IANA actions No new IANA actions are requested in this document. All IANA actions
from RFC 4327 still hold and are reproduced here for information. from RFC 4327 still hold and are reproduced here for information.
Note that new assignments can only be made via a Standards Action as Note that new assignments can only be made via a Standards Action as
specified in [RFC2434]. specified in [RFC2434].
13.1. IANA Considerations for lmp ifType 13.1. IANA Considerations for lmp ifType
The IANA has assigned 227 ifType for LMP interfaces. The IANA has assigned 227 ifType for LMP interfaces.
13.2. IANA Considerations for LMP-MIB 13.2. IANA Considerations for LMP-MIB
The IANA has assigned { transmission 227 } to the LMP-MIB module The IANA has assigned { transmission 227 } to the LMP-MIB module
specified in this document. 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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC an IANA Considerations Section in RFCs", BCP 26, RFC
2434, October 1998. 2434, October 1998.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 "Structure of Management Information Version 2
skipping to change at page 78, line 48 skipping to change at page 79, line 33
[RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management
Protocol (LMP) for Dense Wavelength Division Protocol (LMP) for Dense Wavelength Division
Multiplexing (DWDM) Optical Line Systems", RFC 4209, Multiplexing (DWDM) Optical Line Systems", RFC 4209,
October 2005. October 2005.
[RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic
Engineering Link Management Information Base", RFC Engineering Link Management Information Base", RFC
4220, November 2005. 4220, November 2005.
14.2. Informative References 15.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)", Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004. RFC 3812, June 2004.
15. Authors' Addresses 16. Authors' Addresses
Martin Dubuc Martin Dubuc
EMail: dubuc.consulting@sympatico.ca EMail: dubuc.consulting@sympatico.ca
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
EMail: tnadeau@cisco.com EMail: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Sonos, Inc. Sonos, Inc.
223 E. De La Guerra St. 223 E. De La Guerra St.
 End of changes. 15 change blocks. 
36 lines changed or deleted 54 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/