draft-ietf-bfd-tc-mib-01.txt   draft-ietf-bfd-tc-mib-02.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: December 14, 2012 N. Akiya Expires: December 20, 2013 N. Akiya
Cisco Systems Cisco Systems
June 14, 2012 June 18, 2013
Definitions of Textual Conventions (TCs) for Definitions of Textual Conventions (TCs) for
Bidirectional Forwarding Detection (BFD) Management Bidirectional Forwarding Detection (BFD) Management
draft-ietf-bfd-tc-mib-01 draft-ietf-bfd-tc-mib-02
Abstract Abstract
This draft defines a Management Information Base (MIB) module which This draft defines a Management Information Base (MIB) module which
contains Textual Conventions to represent commonly used Bidirectional contains Textual Conventions to represent commonly used Bidirectional
Forwarding Detection (BFD) management information. The intent is Forwarding Detection (BFD) management information. The intent is
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD
related MIB modules that would otherwise define their own related MIB modules that would otherwise define their own
representations. representations.
Status of this Memo Requirements Language
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 BCP 14, RFC 2119
[RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 4, 2012. This Internet-Draft will expire on December 20, 2013.
BFD-TC-STD-MIB June 14, 2012
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Requirements Language
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 [RFC2119].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3 3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8 6.1. Normative References . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 8 6.2. Informative References . . . . . . . . . . . . . . . . . 9
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
8 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
This document defines a MIB module which contains Textual Conventions
for Bidirectional Forwarding Detection (BFD) protocols. These
Textual Conventions should be imported by MIB modules which manage
BFD protocols.
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 [RFC2119].
BFD-TC-STD-MIB June 14, 2012
For an introduction to the concepts of BFD, see [BFD], [BFD-1HOP] and
[BFD-MH].
2. The Internet-Standard Management Framework
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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Introduction
This document defines a MIB module which contains Textual Conventions
for Bidirectional Forwarding Detection (BFD) protocols. These
Textual Conventions should be imported by MIB modules which manage
BFD protocols.
For an introduction to the concepts of BFD, see [RFC5880], [RFC5881]
and [RFC5883].
3. BFD Textual Conventions MIB Definitions 3. BFD Textual Conventions MIB Definitions
BFD-TC-STD-MIB DEFINITIONS ::= BEGIN BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32 MODULE-IDENTITY, mib-2, Unsigned32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
bfdTCStdMib MODULE-IDENTITY bfdTCStdMib MODULE-IDENTITY
LAST-UPDATED "201206141200Z" -- 14 June 2012 12:00:00 EST LAST-UPDATED "201306191200Z" -- 19 June 2013 12:00:00 EST
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
Juniper Networks Juniper Networks
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems, G.K. Cisco Systems, Inc.
BFD-TC-STD-MIB June 14, 2012
Email: nobo@cisco.com" Email: nobo@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB module defines TEXTUAL-CONVENTIONs for concepts "This MIB module defines TEXTUAL-CONVENTIONs for concepts
used in Bidirectional Forwarding Detection (BFD) used in Bidirectional Forwarding Detection (BFD)
protocols." protocols."
REVISION "201206141200Z" -- 14 June 2012 12:00:00 EST REVISION "201306191200Z" -- 19 June 2013 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 5 for details -- RFC Ed.: assigned by IANA, see section 5 for details
BfdSessIndexTC ::= TEXTUAL-CONVENTION BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index used to uniquely identify BFD sessions." "An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
BfdIntervalTC ::= TEXTUAL-CONVENTION BfdIntervalTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD interval in microseconds." "The BFD interval in microseconds."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
BfdMultiplierTC ::= TEXTUAL-CONVENTION BfdMultiplierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
skipping to change at page 5, line 4 skipping to change at page 4, line 33
noDiagnostic(0), noDiagnostic(0),
controlDetectionTimeExpired(1), controlDetectionTimeExpired(1),
echoFunctionFailed(2), echoFunctionFailed(2),
neighborSignaledSessionDown(3), neighborSignaledSessionDown(3),
forwardingPlaneReset(4), forwardingPlaneReset(4),
pathDown(5), pathDown(5),
concatenatedPathDown(6), concatenatedPathDown(6),
administrativelyDown(7), administrativelyDown(7),
reverseConcatenatedPathDown(8) reverseConcatenatedPathDown(8)
} }
BFD-TC-STD-MIB June 14, 2012
BfdSessTypeTC ::= TEXTUAL-CONVENTION BfdSessTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session type" "BFD session type"
REFERENCE REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010. Detection (BFD), RFC 5880, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding Katz, D. and D. Ward, Bidirectional Forwarding
skipping to change at page 6, line 4 skipping to change at page 5, line 33
BfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION BfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"UDP destination port number of BFD control packets. "UDP destination port number of BFD control packets.
3784 represents single hop BFD session. 3784 represents single hop BFD session.
4784 represents multi hop BFD session. 4784 represents multi hop BFD session.
However, syntax is left open to wider range of values However, syntax is left open to wider range of values
purposely for two reasons: purposely for two reasons:
BFD-TC-STD-MIB June 14, 2012
1. implementation uses non-compliant port number for 1. implementation uses non-compliant port number for
valid proprietary reason. valid proprietary reason.
2. potential future extension drafts." 2. potential future extension drafts."
REFERENCE REFERENCE
"Use of port 3784 from Katz, D. and D. Ward, "Use of port 3784 from Katz, D. and D. Ward,
Bidirectional Forwarding Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop)", Detection (BFD) for IPv4 and IPv6 (Single Hop)",
RFC 5881, June 2010. RFC 5881, June 2010.
Use of port 4784 from Katz, D. and D. Ward, Bidirectional Use of port 4784 from Katz, D. and D. Ward, Bidirectional
skipping to change at page 7, line 4 skipping to change at page 6, line 34
down(2), down(2),
init(3), init(3),
up(4), up(4),
failing(5) failing(5)
} }
BfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION BfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD authentication type" "BFD authentication type"
BFD-TC-STD-MIB June 14, 2012
REFERENCE REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward, "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), Bidirectional Forwarding Detection (BFD),
RFC 5880, June 2010." RFC 5880, June 2010."
SYNTAX INTEGER { SYNTAX INTEGER {
noAuthentication(-1), noAuthentication(-1),
reserved(0), reserved(0),
simplePassword(1), simplePassword(1),
keyedMD5(2), keyedMD5(2),
meticulousKeyedMD5(3), meticulousKeyedMD5(3),
skipping to change at page 7, line 29 skipping to change at page 7, line 8
BfdSessionAuthenticationKeyTC ::= TEXTUAL-CONVENTION BfdSessionAuthenticationKeyTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x " DISPLAY-HINT "1x "
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD authentication key type. "BFD authentication key type.
A BfdSessionAuthenticationKeyTC is always interpreted within A BfdSessionAuthenticationKeyTC is always interpreted within
the context of an BfdSessAuthenticationTypeTC value. Every the context of an BfdSessAuthenticationTypeTC value. Every
usage of the BfdSessionAuthenticationTypeTC textual usage of the BfdSessionAuthenticationTypeTC textual
convention is required to specify the the convention is required to specify the
BfdSessionAuthenticationKeyTC object that provides the BfdSessionAuthenticationKeyTC object that provides the
context. It is suggested that the context. It is suggested that the
BfdSessionAuthentcationTypeTC object be logically registered BfdSessionAuthentcationTypeTC object be logically registered
before the object(s) that use the before the object(s) that use the
BfdSessionAuthenticationKeyTC textual convention, if they BfdSessionAuthenticationKeyTC textual convention, if they
appear in the same logical row. appear in the same logical row.
The value of a BfdSessionAuthenticationKeyTC must always be The value of a BfdSessionAuthenticationKeyTC must always be
consistent with the value of the associated consistent with the value of the associated
BfdSessionAuthencationTypeTC object. Attempts to set a BfdSessionAuthencationTypeTC object. Attempts to set a
skipping to change at page 8, line 4 skipping to change at page 7, line 33
The following size constraints for a The following size constraints for a
BfdSessionAuthenticationKeyTC object are defined for the BfdSessionAuthenticationKeyTC object are defined for the
associated BfdSessionAuthenticationTypeTC values show below: associated BfdSessionAuthenticationTypeTC values show below:
noAuthentication(-1): SIZE(0) noAuthentication(-1): SIZE(0)
reserved(0): SIZE(0) reserved(0): SIZE(0)
simplePassword(1): SIZE(1..16) simplePassword(1): SIZE(1..16)
keyedMD5(2): SIZE(16) keyedMD5(2): SIZE(16)
meticulousKeyedMD5(3): SIZE(16) meticulousKeyedMD5(3): SIZE(16)
keyedSHA1(4): SIZE(20) keyedSHA1(4): SIZE(20)
BFD-TC-STD-MIB June 14, 2012
meticulousKeyedSHA1(5): SIZE(20) meticulousKeyedSHA1(5): SIZE(20)
When this textual convention is used as the syntax of an When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128 index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, STD 58. In this case, sub-identifiers specified in SMIv2, STD 58. In this case,
the object definition MUST include a 'SIZE' clause to limit the object definition MUST include a 'SIZE' clause to limit
the number of potential instance sub-identifiers; otherwise the number of potential instance sub-identifiers; otherwise
the applicable constraints MUST be stated in the appropriate the applicable constraints MUST be stated in the appropriate
conceptual row DESCRIPTION clauses, or in the surrounding conceptual row DESCRIPTION clauses, or in the surrounding
documentation if there is no single DESCRIPTION clause that documentation if there is no single DESCRIPTION clause that
skipping to change at page 8, line 35 skipping to change at page 8, line 14
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other BFD defines a set of textual conventions which may be used by other BFD
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has modules that define management objects. Therefore, this document has
no impact on the security of the Internet. no impact on the security of the Internet.
5. IANA Considerations 5. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
bfdTCStdMib { mib-2 XXX } bfdTCStdMib { mib-2 XXX }
[RFC Editor Note (to be removed prior to publication): the IANA is [Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note.] this note.]
6. References 6. References
BFD-TC-STD-MIB June 14, 2012
6.1. Normative References 6.1. Normative References
[BFD] Katz, D. and D. Ward, "Bidirectional Forwarding [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Detection (BFD)", RFC 5880, June 2010. Requirement Levels", BCP 14, RFC 2119, March 1997.
[BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop)",
RFC 5881, June 2010.
[BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD) for Multihop Paths", RFC 5883,
June 2010.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
STD 58, RFC 2579, April 1999. 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", RFC 2580, STD 58, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
6.2. Informative References [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
Requirement Levels", BCP 14, RFC 2119, March 1997. (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
2010.
[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for Multihop Paths", RFC 5883, June 2010.
6.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 Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, RFC
3413, December 2002.
Appendix A. Acknowledgments Appendix A. Acknowledgments
We would like to thank David Ward and Jeffrey Haas for their comments Authors would like to thank David Ward and Jeffrey Haas for their
and suggestions. comments and suggestions.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
Email: tnadeau@lucidvision.com
BFD-TC-STD-MIB June 14, 2012 EMail: tnadeau@juniper.net
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems
2000 Innovation Drive
Kanata, Ontario K2K 3E8
Canada
Email: zali@cisco.com EMail: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems G.K. Cisco Systems
Shinjuku Mitsui Building
2-1-1 Nishi-Shinjuku, Shinjuku-Ku
Tokyo 163-0409
Japan
Email: nobo@cisco.com EMail: nobo@cisco.com
 End of changes. 40 change blocks. 
101 lines changed or deleted 80 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/