draft-ietf-mpls-lc-if-mib-06.txt   draft-ietf-mpls-lc-if-mib-07.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: October 2005 Cisco Systems, Inc. Expires: April 2006 Cisco Systems, Inc.
April 2005 October 2005
Multiprotocol Label Switching (MPLS) Label-Controlled ATM Multiprotocol Label Switching (MPLS) Label-Controlled ATM
and Frame-Relay Management Interface Definition and Frame-Relay Management Interface Definition
draft-ietf-mpls-lc-if-mib-06.txt draft-ietf-mpls-lc-if-mib-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is 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 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 becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Definitions that describe how label switching controlled Definitions that describe how label switching controlled
Frame-Relay and ATM interfaces can be managed given the Frame-Relay and ATM interfaces can be managed given the
interface stacking as defined in the MPLS-LSR-STD-MIB and interface stacking as defined in the MPLS-LSR-STD-MIB and
MPLS-TE-STD-MIB. MPLS-TE-STD-MIB.
Table of Contents Table of Contents
1. Introduction .............................................. 3 1. Introduction .............................................. 3
2. Terminology ............................................... 3 2. Terminology ............................................... 3
3. The SNMP Management Framework ............................. 3 3. The SNMP Management Framework ............................. 3
4. Interface Stacking of LC-ATM and LC-FR .................... 5 4. Interface Stacking of LC-ATM and LC-FR .................... 5
5. MPLS Label Controlled ATM MIB Definitions ................. 13 5. Structure of the MPLS-LC-ATM-STD-MIB module ............... 14
6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13 6. Structure of the MPLS-LC-FR-STD-MIB module ................ 14
7. Authors' Addresses ........................................ 54 draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
8. Full Copyright Statement................................... 55
9 Acknowledgments............................................ 52 7. MPLS Label Controlled ATM MIB Definitions ................. 13
10 Security Considerations ................................... 51 8. MPLS Label Controlled Frame Relay MIB Definitions ......... 15
11 IANA Considerations........................................ 55 9. Authors' Addresses ........................................ 54
12 References ................................................ 52 10. Full Copyright Statement................................... 55
13 Intellectual Property...................................... 55 11. Acknowledgments............................................ 52
12. Security Considerations ................................... 51
13. IANA Considerations........................................ 55
14. References ................................................ 52
14.1 Normative References ..................................... 52
14.2 Informative References ................................... 53
15. Intellectual Property...................................... 55
1. Introduction 1. Introduction
This memo defines how label switching controlled Frame-Relay This memo defines how label switching controlled Frame-Relay
[RFC3034] and ATM [RFC3035] interfaces can be realized given [RFC3034] and ATM [RFC3035] interfaces can be realized given
the interface stacking as defined in the MPLS-LSR-STD [RFC3813] the interface stacking as defined in the MPLS-LSR-STD [RFC3813]
and MPLS-TE-STD [RFC3812] MIBs. This document also contains a and MPLS-TE-STD [RFC3812] MIBs. This document also contains a
MIB module that sparsely augments the MPLS-LSR-STD MIB's MIB module that sparsely extends the MPLS-LSR-STD MIB's
mplsInterfaceConfTable in such a way as to identify which mplsInterfaceConfTable in such a way as to identify which
MPLS-type interfaces have LC-ATM or LC-FR capabilities. MPLS-type interfaces have LC-ATM or LC-FR capabilities.
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@uu.net. mpls@uu.net.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
RFC 2119, reference [RFC2119]. RFC 2119, reference [RFC2119].
skipping to change at page 2, line 43 skipping to change at page 3, line 4
LC-FR RFC3034 defines a label switching controlled Frame Relay LC-FR RFC3034 defines a label switching controlled Frame Relay
(LC-FR) interface a Frame-Relay interface controlled by the (LC-FR) interface a Frame-Relay interface controlled by the
label switching control component. Packets traversing label switching control component. Packets traversing
such an interface carry labels in the DLCI field such an interface carry labels in the DLCI field
LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM) LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM)
interface as an ATM interface controlled by the label interface as an ATM interface controlled by the label
switching control component. When a packet traversing such switching control component. When a packet traversing such
an interface is received, it is treated as a labeled packet. an interface is received, it is treated as a labeled packet.
The packet's top label is inferred either from the contents The packet's top label is inferred either from the contents
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
of the VCI field or the combined contents of the VPI and VCI of the VCI field or the combined contents of the VPI and VCI
fields. Any two LDP peers which are connected via an LC-ATM fields. Any two LDP peers which are connected via an LC-ATM
interface will use LDP negotiations to determine which of interface will use LDP negotiations to determine which of
these cases is applicable to that interface. these cases is applicable to that interface.
Static configuration of labels is also possible. Static configuration of labels is also possible.
When LDP is used to distribute labels for use on label-controlled When LDP is used to distribute labels for use on label-controlled
interfaces, label configuration information may be available in the interfaces, label configuration information may be available in the
MPLS-LDP-ATM-STD-MIB [RFC3815] when LC-ATM interfaces are used, or MPLS-LDP-ATM-STD-MIB [RFC3815] when LC-ATM interfaces are used, or
the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces
skipping to change at page 3, line 32 skipping to change at page 3, line 42
4. Interface Stacking of LC-ATM 4. Interface Stacking of LC-ATM
Since LC-ATM interfaces [RFC2863] can carry labeled MPLS Since LC-ATM interfaces [RFC2863] can carry labeled MPLS
traffic, they too are considered MPLS subinterfaces with traffic, they too are considered MPLS subinterfaces with
ifType = mpls(166). They differ slightly in their capability ifType = mpls(166). They differ slightly in their capability
from a packet-oriented MPLS interface in that they may from a packet-oriented MPLS interface in that they may
carry ATM or Frame-Relay encapsulated traffic. It is carry ATM or Frame-Relay encapsulated traffic. It is
thus beneficial to identify them as such. To identify thus beneficial to identify them as such. To identify
them as such, two tables are defined which extend the them as such, two tables are defined which extend the
MPLS-LSR-STD MIB's mplsInterfaceTable (see section 6 for MPLS-LSR-STD MIB's mplsInterfaceTable (see section 5 for
LC-ATM or 7 for LC-FR). LC-ATM or 6 for LC-FR).
5. MPLS Label Controlled ATM MIB Definitions 5. Structure of the MPLS-LC-ATM-STD-MIB module
The MPLS-LC-ATM-STD-MIB module is structured simply
as a table of entries which sparesely extend those
found in the interfaces table. In particular, the
entries in the mplsLcAtmStdInterfaceConfTable
extend those interfaces capable of supporting
MPLS, as is defined in [RFC3813] to include those
entries which also support LC-ATM (and their unique
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
attributes). Therefore, the module can be
visualized as follows. Note that the ifTable
comes from [RFC2863], mplsInterfaceTable from
[RFC3813] and mplsLcAtmStdInterfaceConfTable from
the MPLS-LC-ATM-STD-MIB module described below.
ifTable mplsInterfaceTable mplsLcAtmStdInterfaceConfTable
.1
.2 .2
.3
.4 .4 .4
.5
In the example shown above, five interfaces exist on the
device in question. Of those interfaces, those with
ifIndex = .2 and .4 are of ifType = mpls(166) indicating
that they are capable of MPLS. Of those two, the entry
with index .4 is capable of MPLS LC-ATM operations.
6. Structure of the MPLS-LC-FR-STD-MIB module
The MPLS-LC-FR-STD-MIB module is structured simply
as a table of entries which sparesely extend those
found in the interfaces table. In particular, the
entries in the mplsLcFrStdInterfaceConfTable
extend those interfaces capable of supporting
MPLS, as is defined in [RFC3813] to include those
entries which also support LC-Frame Relay (and their
unique attributes). Therefore, the module can be
visualized as follows. Note that the ifTable
comes from [RFC2863], mplsInterfaceTable from
[RFC3813] and mplsLcAtmStdInterfaceConfTable from
the MPLS-LC-FR-STD-MIB module described below.
ifTable mplsInterfaceTable mplsLcFrStdInterfaceConfTable
.1
.2 .2
.3
.4 .4 .4
.5
In the example shown above, five interfaces exist on the
device in question. Of those interfaces, those with
ifIndex = .2 and .4 are of ifType = mpls(166) indicating
that they are capable of MPLS. Of those two, the entry
with index .4 is capable of MPLS LC-Frame Relay operations.
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
7. MPLS Label Controlled ATM MIB Definitions
The following MIB module imports from [RFC2514], The following MIB module imports from [RFC2514],
[RFC3811], [RFC3813]. [RFC3811], [RFC3813].
MPLS-LC-ATM-STD-MIB DEFINITIONS ::= BEGIN MPLS-LC-ATM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
skipping to change at page 4, line 33 skipping to change at page 6, line 4
" "
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
MPLS Label Controlled ATM interfaces as defined in MPLS Label Controlled ATM interfaces as defined in
[RFC3035]. [RFC3035].
Copyright (C) The Internet Society (2005). This Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
-- Revision history. -- Revision history.
REVISION REVISION
"200506171200Z" -- 17 June 2005 12:00:00 GMT "200506171200Z" -- 17 June 2005 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module. -- Top level components of this MIB module.
skipping to change at page 5, line 9 skipping to change at page 6, line 31
mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 } mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 }
-- MPLS LC-ATM Interface Configuration Table. -- MPLS LC-ATM Interface Configuration Table.
mplsLcAtmStdInterfaceConfTable OBJECT-TYPE mplsLcAtmStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface MPLS LC-ATM "This table specifies per-interface MPLS LC-ATM
capability and associated information. In particular, capability and associated information. In particular,
this table sparsely augments the MPLS-LSR-STD-MIB's this table sparsely extends the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcAtmStdObjects 1 } ::= { mplsLcAtmStdObjects 1 }
mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcAtmStdInterfaceConfEntry SYNTAX MplsLcAtmStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR for "An entry in this table is created by an LSR for
every interface capable of supporting MPLS LC-ATM. every interface capable of supporting MPLS LC-ATM.
skipping to change at page 5, line 31 skipping to change at page 7, line 4
corresponding entry in ifTable and mplsInterfaceConfTable corresponding entry in ifTable and mplsInterfaceConfTable
exist. If the associated entries in ifTable and exist. If the associated entries in ifTable and
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcAtmStdInterfaceConfTable 1 } ::= { mplsLcAtmStdInterfaceConfTable 1 }
MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE {
mplsLcAtmStdCtrlVpi AtmVpIdentifier, mplsLcAtmStdCtrlVpi AtmVpIdentifier,
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, mplsLcAtmStdCtrlVci MplsAtmVcIdentifier,
mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier,
mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier,
mplsLcAtmStdVcMerge TruthValue, mplsLcAtmStdVcMerge TruthValue,
mplsLcAtmVcDirectlyConnected TruthValue, mplsLcAtmVcDirectlyConnected TruthValue,
mplsLcAtmLcAtmVPI AtmVpIdentifier, mplsLcAtmLcAtmVPI AtmVpIdentifier,
mplsLcAtmStdIfConfRowStatus RowStatus, mplsLcAtmStdIfConfRowStatus RowStatus,
mplsLcAtmStdIfConfStorageType StorageType mplsLcAtmStdIfConfStorageType StorageType
} }
skipping to change at page 6, line 29 skipping to change at page 8, line 4
::= { mplsLcAtmStdInterfaceConfEntry 3 } ::= { mplsLcAtmStdInterfaceConfEntry 3 }
mplsLcAtmStdUnlabTrafVci OBJECT-TYPE mplsLcAtmStdUnlabTrafVci OBJECT-TYPE
SYNTAX MplsAtmVcIdentifier SYNTAX MplsAtmVcIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VCI value over which this "This is the VCI value over which this
LSR is willing to accept unlabled traffic LSR is willing to accept unlabled traffic
on this interface." on this interface."
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
::= { mplsLcAtmStdInterfaceConfEntry 4 } ::= { mplsLcAtmStdInterfaceConfEntry 4 }
mplsLcAtmStdVcMerge OBJECT-TYPE mplsLcAtmStdVcMerge OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true(1), indicates that this interface "If set to true(1), indicates that this interface
is capabile of ATM VC merge, otherwise it MUST is capabile of ATM VC merge, otherwise it MUST
be set to false(2)." be set to false(2)."
skipping to change at page 6, line 51 skipping to change at page 8, line 28
mplsLcAtmVcDirectlyConnected OBJECT-TYPE mplsLcAtmVcDirectlyConnected OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether an LC-ATM is directly "This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to or indirectly (by means of a VP) connected. If set to
true(1), indicates that this interface is directly true(1), indicates that this interface is directly
connected LC-ATM, otherwise it MUST be set to connected LC-ATM, otherwise it MUST be set to
false(2)." false(2). It should be noted that although
it can be intimated from RFC 3057 that multiple
VPs maybe used, that in practice only a single
one is used, and therefore the authors of
this MIB module have chosen to model it as such."
DEFVAL { true } DEFVAL { true }
::= { mplsLcAtmStdInterfaceConfEntry 6 } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
mplsLcAtmLcAtmVPI OBJECT-TYPE mplsLcAtmLcAtmVPI OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VPI value used for indirectly "This is the VPI value used for indirectly
connected LC-ATM interfaces. For these connected LC-ATM interfaces. For these
skipping to change at page 7, line 23 skipping to change at page 9, line 4
available to MPLS, and the label MUST be available to MPLS, and the label MUST be
encoded entirely within the VCI field. encoded entirely within the VCI field.
(see [RFC3035]). If the interface is directly (see [RFC3035]). If the interface is directly
connected, this value MUST be set to zero." connected, this value MUST be set to zero."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLcAtmStdInterfaceConfEntry 7 } ::= { mplsLcAtmStdInterfaceConfEntry 7 }
mplsLcAtmStdIfConfRowStatus OBJECT-TYPE mplsLcAtmStdIfConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This is object is used to create and
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding entries in this table, the corresponding
ifEntry and mplsInterfaceConfEntry ifEntry and mplsInterfaceConfEntry
MUST exist before hand. If an entry is attempted MUST exist before hand. If an entry is attempted
to be created by a manager for a corresponding to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-ATM, mplsInterfaceConfEntry that does not support LC-ATM,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
skipping to change at page 8, line 22 skipping to change at page 10, line 4
mplsLcAtmStdGroups mplsLcAtmStdGroups
OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 } OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 }
-- Compliance requirement for full compliance -- Compliance requirement for full compliance
mplsLcAtmStdModuleFullCompliance MODULE-COMPLIANCE mplsLcAtmStdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide "Compliance statement for agents that provide
full support for MPLS-LC-ATM-STD-MIB. Such full support for MPLS-LC-ATM-STD-MIB. Such
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
devices can be monitored and also be configured devices can be monitored and also be configured
using this MIB module." using this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcAtmStdIfGroup mplsLcAtmStdIfGroup
} }
OBJECT mplsLcAtmStdIfConfRowStatus OBJECT mplsLcAtmStdIfConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
skipping to change at page 9, line 19 skipping to change at page 11, line 4
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdCtrlVci OBJECT mplsLcAtmStdCtrlVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdUnlabTrafVpi OBJECT mplsLcAtmStdUnlabTrafVpi
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdUnlabTrafVci OBJECT mplsLcAtmStdUnlabTrafVci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdVcMerge OBJECT mplsLcAtmStdVcMerge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 10, line 17 skipping to change at page 12, line 4
mplsLcAtmStdCtrlVpi, mplsLcAtmStdCtrlVpi,
mplsLcAtmStdCtrlVci, mplsLcAtmStdCtrlVci,
mplsLcAtmStdUnlabTrafVpi, mplsLcAtmStdUnlabTrafVpi,
mplsLcAtmStdUnlabTrafVci, mplsLcAtmStdUnlabTrafVci,
mplsLcAtmStdVcMerge, mplsLcAtmStdVcMerge,
mplsLcAtmVcDirectlyConnected, mplsLcAtmVcDirectlyConnected,
mplsLcAtmLcAtmVPI, mplsLcAtmLcAtmVPI,
mplsLcAtmStdIfConfRowStatus, mplsLcAtmStdIfConfRowStatus,
mplsLcAtmStdIfConfStorageType mplsLcAtmStdIfConfStorageType
} }
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-ATM "Collection of objects needed for MPLS LC-ATM
interface configuration." interface configuration."
::= { mplsLcAtmStdGroups 1 } ::= { mplsLcAtmStdGroups 1 }
END END
6. MPLS Label Controlled Frame Relay MIB Definitions 8. MPLS Label Controlled Frame Relay MIB Definitions
The following MIB module imports from [RFC2115], The following MIB module imports from [RFC2115],
[RFC3811], [RFC3813]. [RFC3811], [RFC3813].
MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
skipping to change at page 11, line 14 skipping to change at page 13, line 4
General comments should be sent to mpls@uu.net General comments should be sent to mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
MPLS Label Controlled Frame-Relay interfaces as defined MPLS Label Controlled Frame-Relay interfaces as defined
in (RFC3034). in (RFC3034).
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200506171200Z" -- 17 June 2005 12:00:00 GMT "200506171200Z" -- 17 June 2005 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial draft revision." "Initial draft revision."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module. -- Top level components of this MIB module.
skipping to change at page 11, line 38 skipping to change at page 13, line 30
mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 } mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 }
-- MPLS LC-FR Interface Configuration Table. -- MPLS LC-FR Interface Configuration Table.
mplsLcFrStdInterfaceConfTable OBJECT-TYPE mplsLcFrStdInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLcFrStdInterfaceConfEntry SYNTAX SEQUENCE OF MplsLcFrStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface MPLS LC-FR "This table specifies per-interface MPLS LC-FR
capability and associated information. In particular, capability and associated information. In particular,
this table sparsely augments the MPLS-LSR-STD-MIB's this table sparsely extends the MPLS-LSR-STD-MIB's
mplsInterfaceConfTable." mplsInterfaceConfTable."
::= { mplsLcFrStdObjects 1 } ::= { mplsLcFrStdObjects 1 }
mplsLcFrStdInterfaceConfEntry OBJECT-TYPE mplsLcFrStdInterfaceConfEntry OBJECT-TYPE
SYNTAX MplsLcFrStdInterfaceConfEntry SYNTAX MplsLcFrStdInterfaceConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR for "An entry in this table is created by an LSR for
every interface capable of supporting MPLS LC-FR. every interface capable of supporting MPLS LC-FR.
skipping to change at page 12, line 12 skipping to change at page 14, line 4
mplsInterfaceConfTable are deleted, the corresponding mplsInterfaceConfTable are deleted, the corresponding
entry in this table must also be deleted shortly entry in this table must also be deleted shortly
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcFrStdInterfaceConfTable 1 } ::= { mplsLcFrStdInterfaceConfTable 1 }
MplsLcFrStdInterfaceConfEntry ::= SEQUENCE { MplsLcFrStdInterfaceConfEntry ::= SEQUENCE {
mplsLcFrStdTrafficMinDlci DLCI, mplsLcFrStdTrafficMinDlci DLCI,
mplsLcFrStdTrafficMaxDlci DLCI, mplsLcFrStdTrafficMaxDlci DLCI,
mplsLcFrStdCtrlMinDlci DLCI, mplsLcFrStdCtrlMinDlci DLCI,
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
mplsLcFrStdCtrlMaxDlci DLCI, mplsLcFrStdCtrlMaxDlci DLCI,
mplsLcFrStdInterfaceConfRowStatus RowStatus, mplsLcFrStdInterfaceConfRowStatus RowStatus,
mplsLcFrStdInterfaceConfStorageType StorageType mplsLcFrStdInterfaceConfStorageType StorageType
} }
mplsLcFrStdTrafficMinDlci OBJECT-TYPE mplsLcFrStdTrafficMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 13, line 10 skipping to change at page 15, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the max DLCI value over which this "This is the max DLCI value over which this
LSR is willing to accept control traffic LSR is willing to accept control traffic
on this interface." on this interface."
::= { mplsLcFrStdInterfaceConfEntry 4 } ::= { mplsLcFrStdInterfaceConfEntry 4 }
mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This is object is used to create and
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding ifEntry and entries in this table, the corresponding ifEntry and
mplsInterfaceConfEntry MUST exist before hand. If an entry mplsInterfaceConfEntry MUST exist before hand. If an entry
is attempted to be created by a manager for a corresponding is attempted to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-FR, mplsInterfaceConfEntry that does not support LC-FR,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
skipping to change at page 14, line 8 skipping to change at page 16, line 4
mplsLcFrStdGroups mplsLcFrStdGroups
OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 2 } OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 2 }
-- Compliance requirement for full compliance -- Compliance requirement for full compliance
mplsLcFrStdModuleFullCompliance MODULE-COMPLIANCE mplsLcFrStdModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide "Compliance statement for agents that provide
full support for MPLS-LC-FR-STD-MIB. Such full support for MPLS-LC-FR-STD-MIB. Such
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
devices can be monitored and also be configured devices can be monitored and also be configured
using this MIB module." using this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsLcFrStdIfGroup mplsLcFrStdIfGroup
} }
OBJECT mplsLcFrStdInterfaceConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
skipping to change at page 15, line 6 skipping to change at page 17, line 4
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdTrafficMaxDlci OBJECT mplsLcFrStdTrafficMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdCtrlMinDlci OBJECT mplsLcFrStdCtrlMinDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdCtrlMaxDlci OBJECT mplsLcFrStdCtrlMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdInterfaceConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 15, line 43 skipping to change at page 17, line 43
mplsLcFrStdInterfaceConfStorageType mplsLcFrStdInterfaceConfStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-FR "Collection of objects needed for MPLS LC-FR
interface configuration." interface configuration."
::= { mplsLcFrStdGroups 1 } ::= { mplsLcFrStdGroups 1 }
END END
7. Authors' Addresses 9. Authors' Addresses
Thomas D. Nadeau Subrahmanya Hegde Thomas D. Nadeau Subrahmanya Hegde
Cisco Systems, Inc. Cisco Systems, Inc. Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 225 East Tazman Drive 300 Beaver Brook Road 225 East Tazman Drive
Boxboro, MA 01719 San Jose, CA Boxboro, MA 01719 San Jose, CA
Phone: +1-978-936-1470 Phone: +1-408-525-6562 Phone: +1-978-936-1470 Phone: +1-408-525-6562
Email: tnadeau@cisco.com Email: subrah@cisco.com Email: tnadeau@cisco.com Email: subrah@cisco.com
8. Full Copyright Statement 10. Full Copyright Statement
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
Copyright (C) The Internet Society (2005). This document is Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their 78, and except as set forth therein, the authors retain all their
rights. rights.
This document and the information contained herein are provided This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. PARTICULAR PURPOSE.
9. Acknowledgments 11. Acknowledgments
We wish to thank Joan Cucchiara and Carlos Pignataro for We wish to thank Joan Cucchiara and Carlos Pignataro for
their comments on this document. their comments on this document.
10. Security Considerations 12. Security Considerations
It is clear that these MIB modules are potentially useful for It is clear that these MIB modules are potentially useful for
monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These
MIB can also be used for configuration of certain objects, and MIB can also be used for configuration of certain objects, and
anything that can be configured can be incorrectly configured, anything that can be configured can be incorrectly configured,
with potentially disastrous results. with potentially disastrous results.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
skipping to change at page 17, line 5 skipping to change at page 19, line 5
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if traffic has been network. This is especially true if traffic has been
established over these interfaces. The use of stronger established over these interfaces. The use of stronger
mechanisms such as SNMPv3 security should be considered mechanisms such as SNMPv3 security should be considered
where possible. Specifically,SNMPv3 VACM and USM MUST be where possible. Specifically,SNMPv3 VACM and USM MUST be
used with any v3 agent which implements this MIB module. used with any v3 agent which implements this MIB module.
Administrators should consider whether read access to Administrators should consider whether read access to
these objects should be allowed, since read access may be these objects should be allowed, since read access may be
undesirable under certain circumstances. undesirable under certain circumstances.
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively mplsLcFrStdInterfaceConfTable collectively
skipping to change at page 17, line 41 skipping to change at page 19, line 43
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access instance of this MIB module, is properly configured to give access
to the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 13. IANA Considerations
As described in and as requested in the MPLS-TC-STD-MIB As described in and as requested in the MPLS-TC-STD-MIB
[RFC3811], MPLS related standards track MIB modules should be [RFC3811], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
11.1. IANA Considerations for MPLS-LC-ATM-STD-MIB draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
13.1. IANA Considerations for MPLS-LC-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 9 } to the The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-STD-MIB module specified in this document. MPLS-LC-ATM-STD-MIB module specified in this document.
11.2. IANA Considerations for MPLS-LC-FR-STD-MIB 13.2. IANA Considerations for MPLS-LC-FR-STD-MIB
The IANA is requested to assign { mplsStdMIB 10 } to the The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-STD-MIB module specified in this document. MPLS-LC-FR-STD-MIB module specified in this document.
12. References 14. References
12.1 Normative References 14.1 Normative References
[RFC3034] Conta, A., Doolan, P., Malis, A., "Use [RFC3034] Conta, A., Doolan, P., Malis, A., "Use
of Label Switching on Frame Relay Networks of Label Switching on Frame Relay Networks
Specification", Rfc3034, JANUARY 2001. Specification", Rfc3034, JANUARY 2001.
[RFC3035] Davie, B., mcCloghhrie, K., Rosen., E., Swallow, G., [RFC3035] Davie, B., mcCloghhrie, K., Rosen., E., Swallow, G.,
Rekhter, Y., Doolan, P., "MPLS using LDP and ATM VC Rekhter, Y., Doolan, P., "MPLS using LDP and ATM VC
Switching", RFC3035, January 2001. Switching", RFC3035, January 2001.
[RFC2115] Brown, C., Baker, F., "Management Information Base [RFC2115] Brown, C., Baker, F., "Management Information Base
skipping to change at page 18, line 48 skipping to change at page 21, line 4
[RFC3811] Nadeau, T., Cucchiara, J., Editors, [RFC3811] Nadeau, T., Cucchiara, J., Editors,
"Definition of Textual Conventions and OBJECT- "Definition of Textual Conventions and OBJECT-
IDENTITIES for Multi-Protocol Label Switching (MPLS) IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", RFC3811, June 2004. Management", RFC3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [RFC3812] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS
Traffic Engineering Management Information Base ", Traffic Engineering Management Information Base ",
RFC3812, June 2004. RFC3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A. and T. [RFC3813] Srinivasan, C., Viswanathan, A. and T.
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
Nadeau, "MPLS Multiprotocol Label Switching Nadeau, "MPLS Multiprotocol Label Switching
(MPLS) Label Switch Router Management (MPLS) Label Switch Router Management
Information Base ", RFC3813, June 2004. Information Base ", RFC3813, June 2004.
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
12.2 Informative References 14.2 Informative References
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[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.
[RFC3815] J. Cucchiara, et al., "Definitions of [RFC3815] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol Switching, Label Distribution Protocol
(LDP)", RFC3815, June 2004. (LDP)", RFC3815, June 2004.
13. Intellectual Property 15. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
draft-ietf-mpls-lc-if-mib-07.txt October 12, 2005
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
 End of changes. 38 change blocks. 
31 lines changed or deleted 137 lines changed or added

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