draft-ietf-hubmib-ether-chipsets-01.txt   rfc2666.txt 
Hub MIB Working Group J. Flick Network Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company Request for Comments: 2666 Hewlett-Packard Company
March 1999 Category: Informational August 1999
Definitions of Object Identifiers for Definitions of Object Identifiers for
Identifying Ethernet Chip Sets Identifying Ethernet Chip Sets
<draft-ietf-hubmib-ether-chipsets-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This memo provides information for the Internet community. It does
all provisions of Section 10 of RFC2026. Internet-Drafts are working not specify an Internet standard of any kind. Distribution of this
documents of the Internet Engineering Task Force (IETF), its areas, memo is unlimited.
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines OBJECT IDENTIFIER values for use with network This memo defines OBJECT IDENTIFIER values for use with network
management protocols in the Internet community. In particular, it management protocols in the Internet community. In particular, it
contains registered OID values for use with the dot3StatsEtherChipSet contains registered OID values for use with the dot3StatsEtherChipSet
object in the EtherLike-MIB [16]. These registrations have been object in the EtherLike-MIB [16]. These registrations have been
split from [16] into a separate document for maintenance purposes. split from [16] into a separate document for maintenance purposes.
Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com.
Table of Contents Table of Contents
1. Introduction ............................................... 2 1. Introduction ............................................... 2
2. The SNMP Management Framework .............................. 2 2. The SNMP Management Framework .............................. 2
3. Definitions ................................................ 3 3. Definitions ................................................ 3
4. Intellectual Property ...................................... 14 4. Intellectual Property ...................................... 14
5. Acknowledgements ........................................... 15 5. Acknowledgements ........................................... 15
6. References ................................................. 15 6. References ................................................. 15
7. Security Considerations .................................... 17 7. Security Considerations .................................... 16
8. Author's Address ........................................... 17 8. Author's Address ........................................... 17
9. Full Copyright Statement ................................... 17 9. Full Copyright Statement ................................... 18
1. Introduction 1. Introduction
This memo defines OBJECT IDENTIFIER values for use with network This memo defines OBJECT IDENTIFIER values for use with network
management protocols in the Internet community. In particular, it management protocols in the Internet community. In particular, it
contains registered OID values for use with the dot3StatsEtherChipSet contains registered OID values for use with the dot3StatsEtherChipSet
object in the EtherLike-MIB [16]. These registrations have been object in the EtherLike-MIB [16]. These registrations have been
split from [16] into a separate document for maintenance purposes. split from [16] into a separate document for maintenance purposes.
The dot3StatsEtherChipSet object has recently been deprecated. The The dot3StatsEtherChipSet object has recently been deprecated. The
skipping to change at page 2, line 34 skipping to change at page 2, line 29
For those chipsets not represented in this document, implementors For those chipsets not represented in this document, implementors
should assign OBJECT IDENTIFIER values within that part of the should assign OBJECT IDENTIFIER values within that part of the
registration tree delegated to individual enterprises. registration tree delegated to individual enterprises.
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in STD
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC second version, called SMIv2, is described in STD 58, RFC 2578
1904 [7]. [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
The third version of the message protocol is called SNMPv3 and 1906 [10]. The third version of the message protocol is called
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [8]. A second set of protocol
and associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2275 the view-based access control mechanism described in RFC 2575
[15]. [15].
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. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
skipping to change at page 3, line 39 skipping to change at page 3, line 34
ETHER-CHIPSET-MIB DEFINITIONS ::= BEGIN ETHER-CHIPSET-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
dot3 dot3
FROM EtherLike-MIB; FROM EtherLike-MIB;
etherChipsetMIB MODULE-IDENTITY etherChipsetMIB MODULE-IDENTITY
LAST-UPDATED "9901280202Z" -- January 28, 1999 LAST-UPDATED "9908240400Z" -- August 24, 199
ORGANIZATION "IETF 802.3 Hub MIB Working Group" ORGANIZATION "IETF 802.3 Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
To subscribe: hubmib-request@hprnd.rose.hp.com To subscribe: hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Lucent Technologies Postal: Lucent Technologies
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
skipping to change at page 4, line 35 skipping to change at page 4, line 30
EtherLike-MIB. Implementations which support EtherLike-MIB. Implementations which support
the dot3StatsEtherChipSet object for backwards the dot3StatsEtherChipSet object for backwards
compatability may continue to use these values. compatability may continue to use these values.
For those chipsets not represented in this For those chipsets not represented in this
module, registration is required in other module, registration is required in other
documentation, e.g., assignment within that documentation, e.g., assignment within that
part of the registration tree delegated to part of the registration tree delegated to
individual enterprises (see RFC 1155 and RFC individual enterprises (see RFC 1155 and RFC
1902)." 1902)."
REVISION "9901280031Z" -- January 28, 1999 REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "Initial version of this module created by DESCRIPTION "Initial version of this module created by
splitting the chipset registration information splitting the chipset registration information
out from the EtherLike-MIB." out from the EtherLike-MIB.
::= { mib-2 XX } Version published as RFC 2666."
-- NOTE TO RFC EDITOR: When this document is published as ::= { mib-2 70 }
-- an RFC, change XX to next available mib-2 branch,
-- assigned by IANA, and delete this comment.
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-IDENTITY dot3ChipSetAMD7990 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Advanced DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am7990 Local Area Network Micro Devices Am7990 Local Area Network
Controller for Ethernet (LANCE)." Controller for Ethernet (LANCE)."
skipping to change at page 13, line 4 skipping to change at page 12, line 42
Controller." Controller."
::= { dot3ChipSetToshiba 1 } ::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 } dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Lucent DESCRIPTION "The authoritative identifier for the Lucent
Technologies ATT1MX10 (Spinnaker) Quad MAC and Technologies ATT1MX10 (Spinnaker) Quad MAC and
Tranceiver for Ethernet Frame Switching." Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Lucent DESCRIPTION "The authoritative identifier for the Lucent
Technologies LUC3M08 Eight Ethernet MACs for Technologies LUC3M08 Eight Ethernet MACs for
10/100 Mbits/s Frame Switching." 10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 } ::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 } dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileoGT48001 OBJECT-IDENTITY dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Galileo DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48001A Switched Ethernet Technology GT-48001A Switched Ethernet
Controller." Controller."
::= { dot3ChipSetGalileo 1 } ::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-IDENTITY dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Galileo DESCRIPTION "The authoritative identifier for the Galileo
skipping to change at page 15, line 18 skipping to change at page 15, line 12
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
5. Acknowledgements 5. Acknowledgements
This document was produced by the Ethernet Interfaces and Hub MIB This document was produced by the Ethernet Interfaces and Hub MIB
Working Group. Working Group.
6. References 6. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2571, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, Management Information for TCP/IP-based Internets", STD 16, RFC
RFC 1155, Performance Systems International, Hughes LAN Systems, 1155, May 1990.
May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, Performance Systems International, Hughes LAN Systems, RFC 1212, March 1991.
March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the [4] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, March 1991
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Structure of Management Information for Version 2 of the Simple M. and S Waldbusser, "Structure of Management Information
Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Conventions for Version 2 of the Simple Network Management M. and S Waldbusser, "Textual Conventions for SMIv2", STD 58,
Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco RFC 2579, April 1999.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Conformance Statements for Version 2 of the Simple Network M. and S Waldbusser, "Conformance Statements for SMIv2", STD 58,
Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., RFC 2580, STD 58, April 1999.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, SNMP Research, Network Management Protocol", STD 15, RFC 1157, May 1990.
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP "Introduction to Community-based SNMPv2", RFC 1901, January
Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1996.
Inc., International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
"Transport Mappings for Version 2 of the Simple Network Mappings for Version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., (SNMPv2)", RFC 1906, January 1996.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Protocol (SNMP)", RFC 2572, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. (SNMPv3)", RFC 2574, May 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Protocol (SNMPv2)", RFC 1905, January 1996.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, May 1999.
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, (SNMP)", RFC 2575, May 1999.
Inc., Cisco Systems, Inc., January 1998
[16] Flick, J., and J. Johnson, "Definitions of Managed Objects for [16] Flick, J. and J. Johnson, "Definitions of Managed Objects for
the Ethernet-like Interface Types", work in progress, the Ethernet-like Interface Types", RFC 2665, August 1999.
draft-ietf-hubmib-etherif-mib-v2-02.txt, Hewlett-Packard
Company, RedBack Networks, January, 1999.
7. Security Considerations 7. Security Considerations
There are no management objects actually defined in this MIB module. There are no management objects actually defined in this MIB module.
It merely contains a list of OBJECT IDENTIFIER values for use in It merely contains a list of OBJECT IDENTIFIER values for use in
other MIB modules. As such, it does not, by itself, have any effect other MIB modules. As such, it does not, by itself, have any effect
on the security of the Internet. on the security of the Internet.
The values in this module are expected to be used only for backwards The values in this module are expected to be used only for backwards
compatability with the deprecated dot3StatsEtherChipSet object in the compatability with the deprecated dot3StatsEtherChipSet object in the
skipping to change at page 17, line 32 skipping to change at page 16, line 50
network via SNMP. Not all versions of SNMP provide features for such network via SNMP. Not all versions of SNMP provide features for such
a secure environment. a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. access and GET (read) the objects in this MIB.
It is recommended that the implementors consider the security It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to a managed object whose values are defined in entity giving access to a managed object whose values are defined in
this MIB, is properly configured to give access to those objects only this MIB, is properly configured to give access to those objects only
to those principals (users) that have legitimate rights to access to those principals (users) that have legitimate rights to access
them. them.
8. Author's Address 8. Author's Address
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Email: johnf@rose.hp.com EMail: johnf@rose.hp.com
9. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
skipping to change at line 834 skipping to change at page 18, line 32
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 40 change blocks. 
117 lines changed or deleted 80 lines changed or added

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