draft-ietf-pim-bsr-mib-04.txt   draft-ietf-pim-bsr-mib-05.txt 
PIM WG B. Joshi PIM WG B. Joshi
Internet-Draft Infosys Technologies Ltd. Internet-Draft Infosys Technologies Ltd.
Expires: April 27, 2008 R. Bijlani Expires: November 1, 2008 R. Bijlani
Cisco Systems April 30, 2008
October 25, 2007
PIM Bootstrap Router MIB PIM Bootstrap Router MIB
draft-ietf-pim-bsr-mib-04.txt draft-ietf-pim-bsr-mib-05.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.
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
skipping to change at page 1, line 35 skipping to change at page 1, line 34
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 April 27, 2008. This Internet-Draft will expire on November 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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 (Protocol
Independent Multicast).
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 . . . . . . . . . . . . . . . . . . . 19 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 9.1. Normative References . . . . . . . . . . . . . . . . . . . 21
9.2. Informative References . . . . . . . . . . . . . . . . . . 22 9.2. Informative References . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . . . 24
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], [RFC5059].
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
tables from one of the earlier version of PIM MIB draft [I-D.ietf- tables from one of the earlier version of PIM MIB [RFC5060].
pim-mib-v2].
2. The Internet-Standard Management Framework 2. 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 43 skipping to change at page 3, line 41
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
This MIB module contains four tables. The tables are: This MIB module contains four tables. The tables are:
1. The Candidate-RP Table, which contains one row for each multicast 1. The Candidate-RP Table, which contains one row for each multicast
group address prefix for which the local router is to advertise group address prefix for which the local router is configured to
itself as a Candidate-RP. This table exists on routers that are advertise itself as a Candidate-RP. This table exists on routers
configured as Candidate-RP. that are configured as Candidate-RP.
2. The Elected BSR RP-Set Table, which contains one row for each 2. The 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.
This table exists on a router that is an elected BSR. This table exists on a router that is an elected BSR.
3. The Candidate-BSR Table, which contains one row for each 3. The Candidate-BSR Table, which contains one row for each
Candidate-BSR configuration for the local router. This table Candidate-BSR configuration for the local router. This table
exists on routers that are configured as Candidate-BSR. exists on routers that are configured as Candidate-BSR.
4. The Elected BSR Table, which contains one row for each elected 4. The Elected BSR Table, which contains one row for each elected
skipping to change at page 4, line 33 skipping to change at page 4, line 33
RowStatus, TruthValue, RowStatus, TruthValue,
StorageType FROM SNMPv2-TC 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 "200710250000Z" -- 25 October 2007
ORGANIZATION ORGANIZATION
"IETF Protocol Independent Multicast (PIM) Working Group" "IETF Protocol Independent Multicast (PIM) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pim@ietf.org "Email: pim@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/pim-charter.html" 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 IETF Trust (2007). This version Copyright (C) The IETF Trust (2008). 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 "200710250000Z" -- 25 October 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 7, line 46 skipping to change at page 7, line 46
this zone." this zone."
::= { pimBsrCandidateRPEntry 6 } ::= { pimBsrCandidateRPEntry 6 }
pimBsrCandidateRPPriority OBJECT-TYPE pimBsrCandidateRPPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority for this Candidate RP advertised in "The priority for this Candidate RP advertised in
Candidate-RP-Advertisements." Candidate-RP-Advertisements."
REFERENCE "I-D.ietf-pim-sm-bsr section 3.2" REFERENCE "RFC5059 section 3.2"
DEFVAL { 192 } DEFVAL { 192 }
::= { pimBsrCandidateRPEntry 7 } ::= { pimBsrCandidateRPEntry 7 }
pimBsrCandidateRPAdvInterval OBJECT-TYPE pimBsrCandidateRPAdvInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..26214) SYNTAX Unsigned32 (1..26214)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Candidate RP generates Candidate-RP-Advertisements "A Candidate RP generates Candidate-RP-Advertisements
periodically. This object represents the time interval periodically. This object represents the time interval
in seconds between two consecutive advertisements." in seconds between two consecutive advertisements."
REFERENCE "I-D.ietf-pim-sm-bsr section 3.2 and section 5" REFERENCE "RFC5059 section 3.2 and section 5"
DEFVAL { 60 } DEFVAL { 60 }
::= { pimBsrCandidateRPEntry 8 } ::= { pimBsrCandidateRPEntry 8 }
pimBsrCandidateRPHoldtime OBJECT-TYPE pimBsrCandidateRPHoldtime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Holdtime for this Candidate RP. The amount of time (in "Holdtime for this Candidate RP. The amount of time (in
seconds) this Candidate-RP entry is valid. seconds) this Candidate-RP entry is valid.
This object's value can be zero only when this C-RP is This object's value can be zero only when this C-RP is
shutting down" shutting down"
REFERENCE "I-D.ietf-pim-sm-bsr section 4.2" REFERENCE "RFC5059 section 4.2"
DEFVAL { 150 } DEFVAL { 150 }
::= { pimBsrCandidateRPEntry 9 } ::= { pimBsrCandidateRPEntry 9 }
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
skipping to change at page 11, line 22 skipping to change at page 11, line 22
::= { pimBsrElectedBSRRPSetEntry 5 } ::= { pimBsrElectedBSRRPSetEntry 5 }
pimBsrElectedBSRRPSetPriority OBJECT-TYPE pimBsrElectedBSRRPSetPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority for RP. Numerically higher values for "The priority for RP. Numerically higher values for
this object indicate lower priorities, with the value this object indicate lower priorities, with the value
zero denoting the highest priority." zero denoting the highest priority."
REFERENCE "I-D.ietf-pim-sm-bsr section 4.1" REFERENCE "RFC5059 section 4.1"
::= { pimBsrElectedBSRRPSetEntry 6 } ::= { pimBsrElectedBSRRPSetEntry 6 }
pimBsrElectedBSRRPSetHoldtime OBJECT-TYPE pimBsrElectedBSRRPSetHoldtime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The holdtime for RP" "The holdtime for RP"
REFERENCE "I-D.ietf-pim-sm-bsr section 4.1" REFERENCE "RFC5059 section 4.1"
::= { pimBsrElectedBSRRPSetEntry 7 } ::= { pimBsrElectedBSRRPSetEntry 7 }
pimBsrElectedBSRRPSetExpiryTime OBJECT-TYPE pimBsrElectedBSRRPSetExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum time remaining before this entry will be "The minimum time remaining before this entry will be
aged out. The value zero indicates that this entry will aged out. The value zero indicates that this entry will
never be aged out." never be aged out."
skipping to change at page 13, line 5 skipping to change at page 13, line 5
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 a "The zone index uniquely identifies the zone on a
device to which this Candidate BSR is attached. There is device to which this Candidate BSR is attached. There is
one entry for each zone in ipMcastZoneTable. Scope-level one entry for each zone in ipMcastZoneTable. Scope-level
information for this zone can be extracted from information for this zone can be extracted from
ipMcastZoneTable in IP Multicast MIB. ipMcastZoneTable in IP Multicast MIB [RFC5132]."
[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 17, line 15 skipping to change at page 17, line 12
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pimBsrElectedBSRLostElection notification should be "A pimBsrElectedBSRLostElection notification should be
generated when current E-BSR lost election to a new generated when current E-BSR lost election to a new
Candidate BSR. Only an E-BSR should generate this Candidate BSR. Only an E-BSR should generate this
notification. notification.
This notification is generated when This notification is generated when
pimBsrCandidateBSRElectedBSR becomes FALSE." pimBsrCandidateBSRElectedBSR becomes FALSE."
REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" REFERENCE "RFC5059 section 3.1"
::= { pimBsrNotifications 1 } ::= { pimBsrNotifications 1 }
pimBsrCandidateBSRWinElection NOTIFICATION-TYPE pimBsrCandidateBSRWinElection NOTIFICATION-TYPE
OBJECTS { pimBsrCandidateBSRElectedBSR } OBJECTS { pimBsrCandidateBSRElectedBSR }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pimBsrCandidateBSRWinElection notification should be "A pimBsrCandidateBSRWinElection notification should be
generated when a C-BSR wins BSR Election. Only an generated when a C-BSR wins BSR Election. Only an
E-BSR should generate this notification. E-BSR should generate this notification.
This notification is generated when This notification is generated when
pimBsrCandidateBSRElectedBSR becomes TRUE." pimBsrCandidateBSRElectedBSR becomes TRUE."
REFERENCE "I-D.ietf-pim-sm-bsr section 3.1" REFERENCE "RFC5059 section 3.1"
::= { pimBsrNotifications 2 } ::= { pimBsrNotifications 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
pimBsrCompliance MODULE-COMPLIANCE pimBsrCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for PIM routers that implement "The compliance statement for PIM routers that implement
skipping to change at page 21, line 4 skipping to change at page 20, line 38
rights to access (read/change/create/delete) them. rights to access (read/change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
pimBsrMIB { mib-2 XXX } pimBsrMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is 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 requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" 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 (here and in the MIB module) with the assigned value and to remove
this note. 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 [RFC5060] by R.
[I-D.ietf-pim-mib-v2] by R. Sivaramu, J. Lingard and B. Joshi. Sivaramu, J. Lingard and B. Joshi.
Many thanks to Bill Fenner, Stig Venaas, Nidhi Bhaskar, David Many thanks to Bill Fenner, Stig Venaas, Nidhi Bhaskar, David
Mcwalter, David Harrington and J. W. Atwood for their feedback on Mcwalter, David Harrington and J. W. Atwood for their feedback on
this MIB module. 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
skipping to change at page 22, line 5 skipping to change at page 21, line 39
April 1999. April 1999.
[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.
[I-D.ietf-pim-mib-v2] [RFC5060] Sivaramu, R., Lingard, J., McWalter, D., Joshi, B., and A.
Lingard, J., "Protocol Independent Multicast MIB", Kessler, "Protocol Independent Multicast MIB", RFC 5060,
draft-ietf-pim-mib-v2-10 (work in progress), March 2007. January 2008.
[I-D.ietf-pim-sm-bsr] [RFC5059] Bhaskar, N., Gall, A., Lingard, J., and S. Venaas,
Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", "Bootstrap Router (BSR) Mechanism for Protocol Independent
draft-ietf-pim-sm-bsr-10 (work in progress), Multicast (PIM)", RFC 5059, January 2008.
February 2007.
[I-D.ietf-mboned-ip-mcast-mib] [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
McWalter, D., "IP Multicast MIB", MIB", RFC 5132, December 2007.
draft-ietf-mboned-ip-mcast-mib-05 (work in progress),
March 2007.
9.2. Informative References 9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Authors' Addresses Authors' Addresses
Bharat Joshi Bharat Joshi
Infosys Technologies Ltd. Infosys Technologies Ltd.
44 Electronics City, Hosur Road 44 Electronics City, Hosur Road
Bangalore 560 100 Bangalore 560 100
India India
Email: bharat_joshi@infosys.com Email: bharat_joshi@infosys.com
URI: http://www.infosys.com/ URI: http://www.infosys.com/
Raina Bijlani Raina Bijlani
Cisco Systems
170 W.Tasman Drive
San Jose CA 95134
USA
Email: rainab@cisco.com Email: rainab@gmail.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 24, line 41 skipping to change at page 24, line 41
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, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE 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 IETF Trust (2007). This document is subject to the Copyright (C) The IETF Trust (2008). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as rights, licenses and restrictions contained in BCP 78, and 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. 29 change blocks. 
47 lines changed or deleted 36 lines changed or added

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