draft-ietf-pim-bsr-mib-01.txt   draft-ietf-pim-bsr-mib-02.txt 
PIM WG B. Joshi PIM WG B. Joshi
Internet-Draft Infosys Technologies Ltd. Internet-Draft Infosys Technologies Ltd.
Expires: May 2, 2007 R. Bijlani Expires: August 13, 2007 R. Bijlani
Cisco Systems Cisco Systems
October 29, 2006 February 9, 2007
PIM Bootstrap Router MIB PIM Bootstrap Router MIB
draft-ietf-pim-bsr-mib-01.txt draft-ietf-pim-bsr-mib-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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."
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 May 2, 2007. This Internet-Draft will expire on August 13, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing the Bootstrap Router (BSR) mechanism for PIM. managing the Bootstrap Router (BSR) mechanism for PIM.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 20 9.2. Informative References . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . . . . . 22 Intellectual Property and Copyright Statements . . . . . . . . . . 23
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Bootstrap Router (BSR) mechanism for PIM. [RFC4601], [I-D.ietf-pim- Bootstrap Router (BSR) mechanism for PIM. [RFC4601], [I-D.ietf-pim-
sm-bsr]. sm-bsr].
This document was created by moving some of the PIM BSR specific MIB This document was created by moving some of the PIM BSR specific MIB
skipping to change at page 4, line 12 skipping to change at page 4, line 12
2. The BSR Elected BSR RP-Set Table, which contains one row for each 2. The BSR Elected BSR RP-Set Table, which contains one row for each
Group-to-RP mapping that was received in C-RP advertisements. Group-to-RP mapping that was received in C-RP advertisements.
3. The BSR Candidate-BSR Table, which contains one row for each 3. The BSR Candidate-BSR Table, which contains one row for each
Candidate-BSR configuration for the local router. Candidate-BSR configuration for the local router.
4. The BSR Elected BSR Table, which contains one row for each 4. The BSR Elected BSR Table, which contains one row for each
elected BSR. elected BSR.
This MIB module uses textual conventions defined in the IF-MIB This MIB module uses textual conventions defined in the IF-MIB
[RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-
MIB[RTPROTO].
5. Definitions 5. Definitions
PIM-BSR-MIB DEFINITIONS ::= BEGIN PIM-BSR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
mib-2, Unsigned32, TimeTicks FROM SNMPv2-SMI mib-2, Unsigned32, TimeTicks FROM SNMPv2-SMI
RowStatus, TruthValue FROM SNMPv2-TC RowStatus, TruthValue,
StorageType FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
InetAddressType, InetAddressType,
InetAddressPrefixLength, InetAddressPrefixLength,
InetAddress, InetAddress,
InetZoneIndex FROM INET-ADDRESS-MIB; InetZoneIndex FROM INET-ADDRESS-MIB;
pimBsrMIB MODULE-IDENTITY pimBsrMIB MODULE-IDENTITY
LAST-UPDATED "200610230000Z" -- 23 October 2006 LAST-UPDATED "200702040000Z" -- 4 February 2007
ORGANIZATION "IETF PIM Working Group" ORGANIZATION
"IETF Protocol Independent Multicast (PIM) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pim@ietf.org" "Email: pim@ietf.org
WG charter:
http://www.ietf.org/html.charters/pim-charter.html"
DESCRIPTION DESCRIPTION
"The MIB module for management of the Bootstrap Router "The MIB module for management of the Bootstrap Router
(BSR) mechanism for PIM routers. (BSR) mechanism for PIM routers.
Copyright (C) The Internet Society (2006). This version Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200610230000Z" -- 23 October 2006 REVISION "200702040000Z" -- 4 February 2007
DESCRIPTION "Initial version, published as RFC yyyy." DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
-- --
-- Top-level structure -- Top-level structure
-- --
pimBsrNotifications OBJECT IDENTIFIER ::= { pimBsrMIB 0 } pimBsrNotifications OBJECT IDENTIFIER ::= { pimBsrMIB 0 }
skipping to change at page 6, line 6 skipping to change at page 6, line 11
PimBsrCandidateRPEntry ::= SEQUENCE { PimBsrCandidateRPEntry ::= SEQUENCE {
pimBsrCandidateRPAddressType InetAddressType, pimBsrCandidateRPAddressType InetAddressType,
pimBsrCandidateRPAddress InetAddress, pimBsrCandidateRPAddress InetAddress,
pimBsrCandidateRPGroupAddress InetAddress, pimBsrCandidateRPGroupAddress InetAddress,
pimBsrCandidateRPGroupPrefixLength InetAddressPrefixLength, pimBsrCandidateRPGroupPrefixLength InetAddressPrefixLength,
pimBsrCandidateRPBidir TruthValue, pimBsrCandidateRPBidir TruthValue,
pimBsrCandidateRPAdvTimer TimeTicks, pimBsrCandidateRPAdvTimer TimeTicks,
pimBsrCandidateRPPriority Unsigned32, pimBsrCandidateRPPriority Unsigned32,
pimBsrCandidateRPAdvInterval Unsigned32, pimBsrCandidateRPAdvInterval Unsigned32,
pimBsrCandidateRPHoldtime Unsigned32, pimBsrCandidateRPHoldtime Unsigned32,
pimBsrCandidateRPStatus RowStatus pimBsrCandidateRPStatus RowStatus,
pimBsrCandidateRPStorageType StorageType
} }
pimBsrCandidateRPAddressType OBJECT-TYPE pimBsrCandidateRPAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Inet address type of the Candidate-RP." "The Inet address type of the Candidate-RP."
::= { pimBsrCandidateRPEntry 1 } ::= { pimBsrCandidateRPEntry 1 }
skipping to change at page 8, line 26 skipping to change at page 8, line 32
pimBsrCandidateRPStatus OBJECT-TYPE pimBsrCandidateRPStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table." created, or old entries deleted from this table."
::= { pimBsrCandidateRPEntry 10 } ::= { pimBsrCandidateRPEntry 10 }
pimBsrCandidateRPStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows having the value
'permanent' need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { pimBsrCandidateRPEntry 11 }
-- --
-- The BSR Elected BSR RP-Set Table -- The BSR Elected BSR RP-Set Table
-- --
pimBsrElectedBSRRPSetTable OBJECT-TYPE pimBsrElectedBSRRPSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF PimBsrElectedBSRRPSetEntry SYNTAX SEQUENCE OF PimBsrElectedBSRRPSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing BSR-specific information "The (conceptual) table listing BSR-specific information
skipping to change at page 12, line 4 skipping to change at page 12, line 22
::= { pimBsrCandidateBSRTable 1 } ::= { pimBsrCandidateBSRTable 1 }
PimBsrCandidateBSREntry ::= SEQUENCE { PimBsrCandidateBSREntry ::= SEQUENCE {
pimBsrCandidateBSRZoneIndex InetZoneIndex, pimBsrCandidateBSRZoneIndex InetZoneIndex,
pimBsrCandidateBSRAddressType InetAddressType, pimBsrCandidateBSRAddressType InetAddressType,
pimBsrCandidateBSRAddress InetAddress, pimBsrCandidateBSRAddress InetAddress,
pimBsrCandidateBSRPriority Unsigned32, pimBsrCandidateBSRPriority Unsigned32,
pimBsrCandidateBSRHashMaskLength Unsigned32, pimBsrCandidateBSRHashMaskLength Unsigned32,
pimBsrCandidateBSRElectedBSR TruthValue, pimBsrCandidateBSRElectedBSR TruthValue,
pimBsrCandidateBSRBootstrapTimer TimeTicks, pimBsrCandidateBSRBootstrapTimer TimeTicks,
pimBsrCandidateBSRStatus RowStatus pimBsrCandidateBSRStatus RowStatus,
pimBsrCandidateBSRStorageType StorageType
} }
pimBsrCandidateBSRZoneIndex OBJECT-TYPE pimBsrCandidateBSRZoneIndex OBJECT-TYPE
SYNTAX InetZoneIndex SYNTAX InetZoneIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The zone index uniquely identifies the zone on "The zone index uniquely identifies the zone on a"
a device to which this Candidate BSR is attached. device to which this Candidate BSR is attached. There is
There is one entry for each zone in ipMcastZoneTable. one entry for each zone in ipMcastZoneTable. Scope-level
Scope-level information for this zone can be extracted information for this zone can be extracted from
from ipMcastZoneTable in IP MCAST MIB" ipMcastZoneTable in IP Multicast MIB.
[I-D.ietf-mboned-ip-mcast-mib]."
::= { pimBsrCandidateBSREntry 1 } ::= { pimBsrCandidateBSREntry 1 }
pimBsrCandidateBSRAddressType OBJECT-TYPE pimBsrCandidateBSRAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of the Candidate-BSR." "The address type of the Candidate-BSR."
::= { pimBsrCandidateBSREntry 2 } ::= { pimBsrCandidateBSREntry 2 }
skipping to change at page 13, line 43 skipping to change at page 14, line 15
pimBsrCandidateBSRStatus OBJECT-TYPE pimBsrCandidateBSRStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may "The status of this row, by which new entries may
be created, or old entries deleted from this table." be created, or old entries deleted from this table."
::= { pimBsrCandidateBSREntry 8 } ::= { pimBsrCandidateBSREntry 8 }
pimBsrCandidateBSRStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this row. Rows having the value
'permanent' need not allow write-access to any columnar
objects in the row."
DEFVAL { nonVolatile }
::= { pimBsrCandidateBSREntry 9 }
-- --
-- The BSR Elected-BSR Table -- The BSR Elected-BSR Table
-- --
pimBsrElectedBSRTable OBJECT-TYPE pimBsrElectedBSRTable OBJECT-TYPE
SYNTAX SEQUENCE OF PimBsrElectedBSREntry SYNTAX SEQUENCE OF PimBsrElectedBSREntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table containing information about "The (conceptual) table containing information about
skipping to change at page 19, line 10 skipping to change at page 19, line 41
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 to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to access (read/change/create/delete) them. rights to access (read/change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
PIM-BSR-MIB should be rooted under the mib-2 subtree. IANA is The MIB module in this document uses the following IANA-assigned
requested to assign { mib-2 XXX } to the PIM-BSR-MIB module specified OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
in this document.
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pimBsrMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
8. Acknowledgments 8. Acknowledgments
This MIB module is based on the original work in This MIB module is based on the original work in
[I-D.ietf-pim-mib-v2] by R. Sivaramu, J. Lingard and B. Joshi. [I-D.ietf-pim-mib-v2] by R. Sivaramu, J. Lingard and B. Joshi.
Many thanks to Stig Venaas, Nidhi Bhaskar, David Mcwalter, David Many thanks to Stig Venaas, Nidhi Bhaskar, David Mcwalter, David
Harrington and J. W. Atwood for their feedback on this MIB module. Harrington and J. W. Atwood for their feedback on this MIB module.
Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have
been used for comparison while editing this MIB module. been used for comparison while editing this MIB module.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23,
RFC 2365, July 1998.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
skipping to change at page 20, line 17 skipping to change at page 20, line 49
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[RTPROTO] IANA, "IP Route Protocol MIB",
http://www.iana.org/assignments/ianaiprouteprotocol-mib,
September 2000.
[I-D.ietf-pim-mib-v2] [I-D.ietf-pim-mib-v2]
Lingard, J., "Protocol Independent Multicast MIB", Lingard, J., "Protocol Independent Multicast MIB",
draft-ietf-pim-mib-v2-06 (work in progress), April 2006. draft-ietf-pim-mib-v2-06 (work in progress), April 2006.
[I-D.ietf-pim-sm-bsr] [I-D.ietf-pim-sm-bsr]
Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM",
draft-ietf-pim-sm-bsr-08 (work in progress), May 2006. draft-ietf-pim-sm-bsr-08 (work in progress), May 2006.
[I-D.ietf-mboned-ip-mcast-mib] [I-D.ietf-mboned-ip-mcast-mib]
McWalter, D., "IP Multicast MIB", McWalter, D., "IP Multicast MIB",
skipping to change at page 22, line 33 skipping to change at page 23, line 33
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 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, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE 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.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2007). This document is subject to the
to the rights, licenses and restrictions contained in BCP 78, and rights, licenses and restrictions contained in BCP 78, and except as
except as set forth therein, the authors retain all their rights. set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 22 change blocks. 
42 lines changed or deleted 79 lines changed or added

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