draft-ietf-bridge-rstpmib-06.txt   draft-ietf-bridge-rstpmib-07.txt 
Internet Draft V. Ngai Internet Draft V. Ngai
Expires October 2005 Enterasys Networks Expires December 2005 Enterasys Networks
draft-ietf-bridge-rstpmib-06.txt E. Bell draft-ietf-bridge-rstpmib-07.txt E. Bell
3Com Corp. 3Com Corp.
April 2005 June 2005
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
with Rapid Spanning Tree Protocol with Rapid Spanning Tree Protocol
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
or will be disclosed, and any of which I become aware will be have been or will be disclosed, and any of which he or she becomes
disclosed, in accordance with RFC 3668. 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
skipping to change at page 1, line 39 skipping to change at page 1, line 39
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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.
This Internet-Draft will expire on January 21, 2005. This Internet-Draft will expire on January 21, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This memo defines an SMIv2 MIB module for managing the Rapid Spanning This memo defines an SMIv2 MIB module for managing the Rapid Spanning
Tree capability defined by the IEEE P802.1t and P802.1w amendments to Tree capability defined by the IEEE P802.1t and P802.1w amendments to
IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
segments. The objects in this MIB are defined to apply both to segments. The objects in this MIB are defined to apply both to
transparent bridging and to bridges connected by subnetworks other transparent bridging and to bridges connected by subnetworks other
than LAN segments. than LAN segments.
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ................... 3 1 The Internet-Standard Management Framework ................... 4
2 Overview ..................................................... 3 2 Overview ..................................................... 4
3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3 3 Relationship to IEEE 802.1t and 802.1w amendments ............ 4
4 Relation to the BRIDGE-MIB ................................... 4 4 Relation to the BRIDGE-MIB ................................... 5
5 Definitions for RSTP-MIB ..................................... 5 5 Definitions for RSTP-MIB ..................................... 6
6 Acknowledgments .............................................. 11 6 Acknowledgments .............................................. 13
7 IANA Considerations .......................................... 11 7 IANA Considerations .......................................... 13
8 Security Considerations ...................................... 11 8 Security Considerations ...................................... 13
9 Normative References ......................................... 13 9 Normative References ......................................... 15
10 Informative References ...................................... 14 10 Informative References ...................................... 16
11 Authors' Addresses .......................................... 15 11 Authors' Addresses .......................................... 17
Intellectual Property Statement ............................... 16 Intellectual Property Statement ............................... 18
Disclaimer of Validity ........................................ 16 Disclaimer of Validity ........................................ 18
Copyright Statement ........................................... 16 Copyright Statement ........................................... 18
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 3, line 48 skipping to change at page 4, line 48
dot1dStpVersion (w) 17.16.1 ForceVersion dot1dStpVersion (w) 17.16.1 ForceVersion
dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration (w) 17.18.10 mcheck dot1dStpPortProtocolMigration (w) 17.18.10 mcheck
dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort
dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort
dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC
dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC
dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost
Following are the references for the above objects in 802.1D-2004. Following are the references for the above objects in 802.1D-2004
[802.1D-2004].
RSTP-MIB Name IEEE 802.1D-2004 Reference RSTP-MIB Name IEEE 802.1D-2004 Reference
dot1dStp dot1dStp
dot1dStpVersion 17.13.4 ForceVersion dot1dStpVersion 17.13.4 ForceVersion
dot1dStpTxHoldCount 17.13.12 TxHoldCount dot1dStpTxHoldCount 17.13.12 TxHoldCount
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration 17.19.13 mcheck dot1dStpPortProtocolMigration 17.19.13 mcheck
dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort
dot1dStpPortOperEdgePort 17.19.17 operEdgePort dot1dStpPortOperEdgePort 17.19.17 operEdgePort
skipping to change at page 5, line 14 skipping to change at page 6, line 14
5. Definitions for RSTP-MIB 5. Definitions for RSTP-MIB
RSTP-MIB DEFINITIONS ::= BEGIN RSTP-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32 MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dStp, dot1dStpPortEntry dot1dStp, dot1dStpPortEntry
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200503190000Z" LAST-UPDATED "200503190000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that support the Rapid Spanning Tree Protocol defined that support the Rapid Spanning Tree Protocol defined
by IEEE 802.1w." by IEEE 802.1w."
REVISION "200503190000Z" REVISION "200503190000Z"
-- RFC Ed.: replace XXXX with RFC number and remove this note -- RFC Ed.: replace XXXX with RFC number and remove this note
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX" "Copyright (C) The Internet Society (2005). The initial
version of this MIB module was published in RFC XXXX; for full
legal notices see the RFC itself. Supplementary information
may be available at:
http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace xxxx with IANA-assigned number and -- RFC Ed.: replace xxxx with IANA-assigned number and
-- remove this note -- remove this note
::= { mib-2 xxxx } ::= { mib-2 xxxx }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- subtrees in the RSTP-MIB -- subtrees in the RSTP-MIB
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 } rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 }
rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 } rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 }
skipping to change at page 6, line 18 skipping to change at page 7, line 22
rstp(2) rstp(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version of Spanning Tree Protocol the bridge is "The version of Spanning Tree Protocol the bridge is
currently running. The value 'stpCompatible(0)' currently running. The value 'stpCompatible(0)'
indicates the Spanning Tree Protocol specified in indicates the Spanning Tree Protocol specified in
IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid
Spanning Tree Protocol specified in IEEE 802.1w and Spanning Tree Protocol specified in IEEE 802.1w and
clause 17 of 802.1D-2004. New values may be defined clause 17 of 802.1D-2004. The values are directly from
as future versions of the protocol become available." the IEEE standard. New values may be defined as future
versions of the protocol become available."
REFERENCE REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp } DEFVAL { rstp }
::= { dot1dStp 16 } ::= { dot1dStp 16 }
dot1dStpTxHoldCount OBJECT-TYPE dot1dStpTxHoldCount OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 7, line 36 skipping to change at page 8, line 41
TruthValue, TruthValue,
dot1dStpPortAdminPathCost dot1dStpPortAdminPathCost
Integer32 Integer32
} }
dot1dStpPortProtocolMigration OBJECT-TYPE dot1dStpPortProtocolMigration OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When operating in RSTP (version 2) mode, writing TRUE(1) "When operating in RSTP (version 2) mode, writing true(1)
to this object forces this port to transmit RSTP BPDUs. to this object forces this port to transmit RSTP BPDUs.
Any other operation on this object has no effect and Any other operation on this object has no effect and
it always returns FALSE(2) when read." it always returns false(2) when read."
REFERENCE REFERENCE
"IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
::= { dot1dStpExtPortEntry 1 } ::= { dot1dStpExtPortEntry 1 }
dot1dStpPortAdminEdgePort OBJECT-TYPE dot1dStpPortAdminEdgePort OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative value of the Edge Port parameter. A "The administrative value of the Edge Port parameter. A
value of TRUE(1) indicates that this port should be value of true(1) indicates that this port should be
assumed as an edge-port and a value of FALSE(2) indicates assumed as an edge-port and a value of false(2) indicates
that this port should be assumed as a non-edge-port. that this port should be assumed as a non-edge-port.
Setting this object will also cause the corresponding Setting this object will also cause the corresponding
instance of dot1dStpPortOperEdgePort to change to the instance of dot1dStpPortOperEdgePort to change to the
same value. Note that even when this object's value same value. Note that even when this object's value
is true, the value of the corresponding instance of is true, the value of the corresponding instance of
dot1dStpPortOperEdgePort can be false if a BPDU has dot1dStpPortOperEdgePort can be false if a BPDU has
been received." been received."
REFERENCE REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.3" "IEEE 802.1t clause 14.8.2, 18.3.3"
::= { dot1dStpExtPortEntry 2 } ::= { dot1dStpExtPortEntry 2 }
skipping to change at page 8, line 26 skipping to change at page 9, line 32
dot1dStpPortOperEdgePort OBJECT-TYPE dot1dStpPortOperEdgePort OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational value of the Edge Port parameter. The "The operational value of the Edge Port parameter. The
object is initialized to the value of the corresponding object is initialized to the value of the corresponding
instance of dot1dStpPortAdminEdgePort. When the instance of dot1dStpPortAdminEdgePort. When the
corresponding instance of dot1dStpPortAdminEdgePort is corresponding instance of dot1dStpPortAdminEdgePort is
set, this object will be changed as well. This object set, this object will be changed as well. This object
will also be changed to FALSE on reception of a BPDU." will also be changed to false on reception of a BPDU."
REFERENCE REFERENCE
"IEEE 802.1t clause 14.8.2, 18.3.4" "IEEE 802.1t clause 14.8.2, 18.3.4"
::= { dot1dStpExtPortEntry 3 } ::= { dot1dStpExtPortEntry 3 }
dot1dStpPortAdminPointToPoint OBJECT-TYPE dot1dStpPortAdminPointToPoint OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
forceTrue(0), forceTrue(0),
forceFalse(1), forceFalse(1),
auto(2) auto(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative point-to-point status of the LAN segment "The administrative point-to-point status of the LAN segment
attached to this port. A value of forceTrue(0) indicates that attached to this port, using the enumeration values of the
this port should always be treated as if it is connected to IEEE 802.1w clause. A value of forceTrue(0) indicates
a point-to-point link. A value of forceFalse(1) indicates that this port should always be treated as if it is connected
to a point-to-point link. A value of forceFalse(1) indicates
that this port should be treated as having a shared media that this port should be treated as having a shared media
connection. A value of auto(2) indicates that this port is connection. A value of auto(2) indicates that this port is
considered to have a point-to-point link if it is an Aggregator considered to have a point-to-point link if it is an Aggregator
and all of its members are aggregatable, or if the MAC entity and all of its members are aggregatable, or if the MAC entity
is configured for full duplex operation, either through is configured for full duplex operation, either through
auto-negotiation or by management means." auto-negotiation or by management means. Manipulating this
object changes the underlying adminPortToPortMAC. "
REFERENCE REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 4 } ::= { dot1dStpExtPortEntry 4 }
dot1dStpPortOperPointToPoint OBJECT-TYPE dot1dStpPortOperPointToPoint OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational point-to-point status of the LAN segment "The operational point-to-point status of the LAN segment
attached to this port. It indicates whether a port is attached to this port. It indicates whether a port is
considered to have a point-to-point connection or not. considered to have a point-to-point connection or not.
The value is determined by management or by auto-detection, If adminPointToPointMAC is set to auto(2), then the value
as described in the dot1dStpPortAdminPointToPoint object." of operPointToPointMAC is determined in accordance with the
specific procedures defined for the MAC entity concerned,
as defined in IEEE 802.1w clause 6.5. The value is
determined dynamically; i.e., it is re-evaluated whenever
the value of adminPointToPointMAC changes, and whenever
the specific procedures defined for the MAC entity evaluate
a change in its point-to-point status."
REFERENCE REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 5 } ::= { dot1dStpExtPortEntry 5 }
dot1dStpPortAdminPathCost OBJECT-TYPE dot1dStpPortAdminPathCost OBJECT-TYPE
SYNTAX Integer32 (0..200000000) SYNTAX Integer32 (0..200000000)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administratively assigned value for the contribution "The administratively assigned value for the contribution
skipping to change at page 11, line 37 skipping to change at page 13, line 37
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
Writable objects that could be misused to cause network delays and Writable objects that could be misused to cause network delays and
spanning tree instabilities include dot1dStpVersion, spanning tree instabilities include dot1dStpVersion,
dot1dStpTxHoldCount, dot1dStpPortProtocolMigration, dot1dStpTxHoldCount, dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost. dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.
The object dot1dStpVersion could be read by an attacker to identify dot1dStpVersion could be read by an attacker to identify environments
environments containing applications or protocols which are containing applications or protocols which are potentially sensitive
potentially sensitive to RSTP mode. to RSTP mode.
The object dot1dStpPortAdminPointToPoint could be used to mislead an dot1dStpPortAdminPointToPoint could be used to mislead an access
access control protocol, such as 802.1x, to believe that only one control protocol, such as 802.1x, to believe that only one other
other system is attached to a LAN segment and to enable network system is attached to a LAN segment and to enable network access
access based on that assumption. This situation could permit based on that assumption. This situation could permit potential man-
potential man-in-the-middle attacks. in-the-middle attacks.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework. Specifically, the use provided by the SNMPv3 framework (see [RFC3410], section 8),
of the User-based Security Model [USM] and the View-based Access including full support for the SNMPv3 cryptographic mechanisms (for
Control Model [VACM] is recommended. authentication and privacy), and user-based access control.
9. Normative References 9. Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
McCloghrie, "Definitions of Managed Objects for Bridges
with Traffic Classes, Multicast Filtering and Virtual LAN
Extensions", RFC 2674, August 1999.
[802.1D-1998] "Information technology - Telecommunications and [802.1D-1998] "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Revision. This is 3: Media Access Control (MAC) Bridges: Revision. This is
a revision of ISO/IEC 10038: 1993, 802.1j-1992 and a revision of ISO/IEC 10038: 1993, 802.1j-1992 and
802.6k-1992. It incorporates P802.11c, P802.1p and 802.6k-1992. It incorporates P802.11c, P802.1p and
P802.12e." ISO/IEC 15802-3: 1998. P802.12e." ISO/IEC 15802-3: 1998.
[802.1D-2004] IEEE Project 802 Local and Metropolitan Area [802.1D-2004] IEEE Project 802 Local and Metropolitan Area
Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004. Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004.
skipping to change at page 16, line 31 skipping to change at page 18, line 31
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
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on an This document and the information contained herein are provided
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
 End of changes. 

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