draft-ietf-adslmib-vdsl-ext-mcm-05.txt   draft-ietf-adslmib-vdsl-ext-mcm-06.txt 
Network Working Group M. Dodge Network Working Group M. Dodge
Category: Internet Draft ECI Telecom Category: Internet Draft ECI Telecom
B. Ray B. Ray
PESA Switching Systems PESA Switching Systems
December 2004 January 2005
Definitions of Managed Object Extensions Definitions of Managed Object Extensions
for Very High Speed Digital Subscriber Lines (VDSL) Using for Very High Speed Digital Subscriber Lines (VDSL) Using
Multiple Carrier Modulation (MCM) Line Coding Multiple Carrier Modulation (MCM) Line Coding
draft-ietf-adslmib-vdsl-ext-mcm-05.txt draft-ietf-adslmib-vdsl-ext-mcm-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in accordance with which he or she becomes aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 41 skipping to change at page 1, line 40
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
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.
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 document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) module for use with network management protocols in the (MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for Internet community. In particular, it describes objects used for
managing the Line Code Specific parameters of Very High Speed managing the Line Code Specific parameters of Very High Speed
Digital Subscriber Line (VDSL) interfaces using Multiple Carrier Digital Subscriber Line (VDSL) interfaces using Multiple Carrier
Modulation (MCM) Line Coding. It is an optional extension to the Modulation (MCM) Line Coding. It is an optional extension to the
VDSL-LINE-MIB, RFC 3728, which handles line code independent VDSL-LINE-MIB, RFC 3728, which handles line code independent
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework .................... 2
2. Overview ...................................................... 2 2. Overview ...................................................... 2
2.1 Relationship of this MIB Module to other MIB Modules .......... 3 2.1 Relationship of this MIB Module to other MIB Modules .......... 3
2.2 Conventions used in the MIB Module ............................ 3 2.2 Conventions used in the MIB Module ............................ 3
2.3 Structure ..................................................... 3 2.3 Structure ..................................................... 3
2.4 Persistence ................................................... 4 2.4 Persistence ................................................... 4
3. Conformance and Compliance .................................... 4 3. Conformance and Compliance .................................... 4
4. Definitions ................................................... 5 4. Definitions ................................................... 5
5. Acknowledgements .............................................. 18 5. Acknowledgements .............................................. 18
6. Security Considerations ....................................... 18 6. Security Considerations ....................................... 18
7. IANA Considerations ............................................ 19 7. IANA Considerations ............................................ 20
8. References ..................................................... 19 8. References ..................................................... 20
8.1 Normative References ........................................... 19 8.1 Normative References ........................................... 20
8.2 Informative References ......................................... 21 8.2 Informative References ......................................... 21
Authors' Addresses ............................................. 21 Authors' Addresses ............................................. 21
Full Copyright Statement ....................................... 21 Full Copyright Statement ....................................... 22
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 5, line 21 skipping to change at page 5, line 21
OBJECT-TYPE, OBJECT-TYPE,
transmission, transmission,
Unsigned32 FROM SNMPv2-SMI -- [RFC2578] Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
RowStatus FROM SNMPv2-TC -- [RFC2579] RowStatus FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
ifIndex FROM IF-MIB -- [RFC2863] ifIndex FROM IF-MIB -- [RFC2863]
vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728] vdslLineConfProfileName FROM VDSL-LINE-MIB; -- [RFC3728]
vdslExtMCMMIB MODULE-IDENTITY vdslExtMCMMIB MODULE-IDENTITY
LAST-UPDATED "200412160000Z" -- December 16, 2004 LAST-UPDATED "200501160000Z" -- January 16, 2005
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 6, line 29 skipping to change at page 6, line 29
Vtuc -- (VTUC) transceiver at near (Central) end of line Vtuc -- (VTUC) transceiver at near (Central) end of line
Vtur -- (VTUR) transceiver at Remote end of line Vtur -- (VTUR) transceiver at Remote end of line
Vtu -- One of either Vtuc or Vtur Vtu -- One of either Vtuc or Vtur
Curr -- Current Curr -- Current
LCS -- Line Code Specific LCS -- Line Code Specific
Max -- Maximum Max -- Maximum
PSD -- Power Spectral Density PSD -- Power Spectral Density
Rx -- Receive Rx -- Receive
Tx -- Transmit Tx -- Transmit
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2005). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC XXXX: see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200412160000Z" -- December 16, 2004 REVISION "200501160000Z" -- January 16, 2005
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XX with assigned number & remove this note -- RFC Ed.: replace XX with assigned number & remove this note
::= { transmission XX } -- To be assigned by IANA ::= { transmission XX } -- To be assigned by IANA
-- RFC Ed.: we suggest to put it under { transmission 228 } because -- RFC Ed.: we suggest to put it under { transmission 228 } because
-- this is the next available number, transmission 227 -- this is the next available number, transmission 227
-- would be used for the SCM MIB. -- would be used for the SCM MIB.
vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 } vdslLineExtMCMMib OBJECT IDENTIFIER ::= { vdslExtMCMMIB 1 }
vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1} vdslLineExtMCMMibObjects OBJECT IDENTIFIER ::= {vdslLineExtMCMMib 1}
skipping to change at page 7, line 10 skipping to change at page 7, line 10
DESCRIPTION DESCRIPTION
"This table contains additional information on multiple "This table contains additional information on multiple
carrier VDSL lines. One entry in this table reflects a carrier VDSL lines. One entry in this table reflects a
profile defined by a manager which can be used to profile defined by a manager which can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 1 } ::= { vdslLineExtMCMMibObjects 1 }
vdslLineMCMConfProfileEntry OBJECT-TYPE vdslLineMCMConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileEntry SYNTAX VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
skipping to change at page 8, line 30 skipping to change at page 8, line 30
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 2 } ::= { vdslLineExtMCMMibObjects 2 }
vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxBandEntry SYNTAX VdslLineMCMConfProfileTxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index." is defined by a start and a stop tone index."
skipping to change at page 10, line 16 skipping to change at page 10, line 16
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 3 } ::= { vdslLineExtMCMMibObjects 3 }
vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileRxBandEntry SYNTAX VdslLineMCMConfProfileRxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index." is defined by a start and a stop tone index."
skipping to change at page 12, line 9 skipping to change at page 12, line 9
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL line. These a multiple carrier modulation (MCM) VDSL line. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 4 } ::= { vdslLineExtMCMMibObjects 4 }
vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxPSDEntry SYNTAX VdslLineMCMConfProfileTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a tone." which defines the power spectral density (PSD) for a tone."
skipping to change at page 13, line 45 skipping to change at page 13, line 45
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 5 } ::= { vdslLineExtMCMMibObjects 5 }
vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the maximum power spectral density (PSD) which defines the maximum power spectral density (PSD)
skipping to change at page 15, line 36 skipping to change at page 15, line 36
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
If an entry in this table is referenced by a line which If an entry in this table is referenced by a line which
does not use MCM, it has no effect on the operation of that does not use MCM, it has no effect on the operation of that
line. line.
All read-create objects defined in this MIB module SHOULD be All read-create-objects defined in this table SHOULD be
stored persistently." stored persistently."
::= { vdslLineExtMCMMibObjects 6 } ::= { vdslLineExtMCMMibObjects 6 }
vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a which defines the power spectral density (PSD) for a
skipping to change at page 17, line 29 skipping to change at page 17, line 29
{ vdslLineExtMCMConformance 1 } { vdslLineExtMCMConformance 1 }
vdslLineExtMCMCompliances OBJECT IDENTIFIER ::= vdslLineExtMCMCompliances OBJECT IDENTIFIER ::=
{ vdslLineExtMCMConformance 2 } { vdslLineExtMCMConformance 2 }
vdslLineExtMCMMibCompliance MODULE-COMPLIANCE vdslLineExtMCMMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which "The compliance statement for SNMP entities which
manage VDSL interfaces." manage VDSL interfaces."
MODULE -- this module MODULE -- this module
GROUP vdslLineExtMCMGroup MANDATORY-GROUPS
DESCRIPTION {
"This group is an optional extension for VDSL lines which vdslLineExtMCMGroup
utilize Multiple Carrier Modulation (MCM)." }
::= { vdslLineExtMCMCompliances 1 } ::= { vdslLineExtMCMCompliances 1 }
-- units of conformance -- units of conformance
vdslLineExtMCMGroup OBJECT-GROUP vdslLineExtMCMGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
vdslLineMCMConfProfileTxWindowLength, vdslLineMCMConfProfileTxWindowLength,
vdslLineMCMConfProfileRowStatus, vdslLineMCMConfProfileRowStatus,
vdslLineMCMConfProfileTxBandStart, vdslLineMCMConfProfileTxBandStart,
skipping to change at page 19, line 4 skipping to change at page 19, line 4
vdslLineMCMConfProfileTxPSDPSD, vdslLineMCMConfProfileTxPSDPSD,
vdslLineMCMConfProfileTxPSDRowStatus, vdslLineMCMConfProfileTxPSDRowStatus,
vdslLineMCMConfProfileMaxTxPSDTable vdslLineMCMConfProfileMaxTxPSDTable
vdslLineMCMConfProfileMaxTxPSDTone, vdslLineMCMConfProfileMaxTxPSDTone,
vdslLineMCMConfProfileMaxTxPSDPSD, vdslLineMCMConfProfileMaxTxPSDPSD,
vdslLineMCMConfProfileMaxTxPSDRowStatus, vdslLineMCMConfProfileMaxTxPSDRowStatus,
vdslLineMCMConfProfileMaxRxPSDTable vdslLineMCMConfProfileMaxRxPSDTable
vdslLineMCMConfProfileMaxRxPSDTone, vdslLineMCMConfProfileMaxRxPSDTone,
vdslLineMCMConfProfileMaxRxPSDPSD, vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus vdslLineMCMConfProfileMaxRxPSDRowStatus
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
vulnerable in some network environments.
VDSL layer connectivity from the Vtur will permit the subscriber to VDSL layer connectivity from the Vtur will permit the subscriber to
manipulate both the VDSL link directly and the VDSL embedded manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager. management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other an end-user to increase their service levels or affect other
end-users in either a positive or negative manner. For this reason, end-users in either a positive or negative manner. For this reason,
the tables and objects listed above should be considered to contain the tables and objects listed above should be considered to contain
sensitive information. sensitive information.
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
vdslLineMCMConfProfileTable,
vdslLineMCMConfProfileTxWindowLength,
vdslLineMCMConfProfileRowStatus,
vdslLineMCMConfProfileTxBandTable,
vdslLineMCMConfProfileTxBandStart,
vdslLineMCMConfProfileTxBandStop,
vdslLineMCMConfProfileTxBandRowStatus,
vdslLineMCMConfProfileRxBandTable,
vdslLineMCMConfProfileRxBandStart,
vdslLineMCMConfProfileRxBandStop,
vdslLineMCMConfProfileRxBandRowStatus,
vdslLineMCMConfProfileTxPSDTable,
vdslLineMCMConfProfileTxPSDTone,
vdslLineMCMConfProfileTxPSDPSD,
vdslLineMCMConfProfileTxPSDRowStatus,
vdslLineMCMConfProfileMaxTxPSDTable
vdslLineMCMConfProfileMaxTxPSDTone,
vdslLineMCMConfProfileMaxTxPSDPSD,
vdslLineMCMConfProfileMaxTxPSDRowStatus,
vdslLineMCMConfProfileMaxRxPSDTable
vdslLineMCMConfProfileMaxRxPSDTone,
vdslLineMCMConfProfileMaxRxPSDPSD,
vdslLineMCMConfProfileMaxRxPSDRowStatus
Read access of the physical band parameters may provide knowledge
to an end-user that would allow malicious behavior, for example
the application of an intentional interference on one or all of
the physical bands in use.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
skipping to change at page 21, line 40 skipping to change at page 22, line 21
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
EMail: rray@pesa.com EMail: rray@pesa.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and to the rights, licenses and restrictions contained in BCP 78 and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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