--- 1/draft-ietf-bfd-mib-02.txt 2006-10-23 01:12:08.000000000 +0200 +++ 2/draft-ietf-bfd-mib-03.txt 2006-10-23 01:12:08.000000000 +0200 @@ -1,16 +1,18 @@ BFD Working Group Thomas D. Nadeau Standard Track Zafar Ali Cisco Systems, Inc. + Expires: April 2007 October 2006 + Bidirectional Forwarding Detection Management Information Base - draft-ietf-bfd-mib-02.txt + draft-ietf-bfd-mib-03.txt Status of this Memo By submitting this Internet-Draft, each 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 becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other @@ -29,39 +31,41 @@ Abstract This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol [BFD]. Contents - 1. Introduction...................................................2 - 2. Terminology....................................................3 - 3. The Internet-Standard Management Framework.....................3 - 3. Brief Description of MIB Objects...............................3 - 3.1 General Variables..........................................3 - 3.2 Session Table (bfdSessionTable)............................3 - 3.3 Session Performance Table (bfdSessionPerfTable)............3 - 3.4 Session Mapping Table (bfdSessMapTable)....................3 - 4. BFD MIB Module Definitions.....................................4 - 5. Security Considerations.......................................21 - 6. Acknowledgements..............................................22 - 7. References....................................................23 - 7.1 Normative References.........................................23 - 7.2 Informative References.......................................23 - 8. Author's Addresses............................................23 - 9. Full Copyright Statement......................................24 - 10. IANA Considerations.........................................41 - 10.1. IANA Considerations for BFD-STD-MIB.......................41 - 11. Intellectual Property Statement.............................41 + 1. Introduction..................................................2 + 2. Terminology...................................................3 + 3. The Internet-Standard Management Framework....................3 + 3. Brief Description of MIB Objects..............................3 + 3.1 General Variables.............................................3 + 3.2 Session Table (bfdSessionTable)...............................3 + 3.3 Session Performance Table (bfdSessionPerfTable)...............3 + 3.4 Session Mapping Table (bfdSessMapTable).......................3 + BFD MIB October 20, 2006 + + 5. BFD MIB Module Definitions....................................4 + 6. Security Considerations......................................21 + 7. IANA Considerations..........................................41 + 7.1 IANA Considerations for BFD-STD-MIB..........................41 + 8. References...................................................23 + 8.1 Normative References.........................................23 + 8.2 Informative References.......................................23 + 9. Acknowledgements.............................................22 + 10. Authors' Addresses...........................................23 + 11. Intellectual Property Statement..............................41 + 12. Full Copyright Statement.....................................24 1. Introduction This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor Bi-Directional Forwarding Detection on devices supporting this feature. This document adopts the definitions, acronyms and mechanisms @@ -85,20 +89,22 @@ here. 3. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally + BFD MIB October 20, 2006 + accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 4. Brief Description of MIB Objects This section describes objects pertaining to BFD. The MIB objects @@ -120,35 +126,40 @@ performance counts on a per session basis. This table is an AUGMENT to the bfdSessionTable. 3.4 Session Mapping Table (bfdSessMapTable) The BFD Session Mapping Table maps the complex indexing of the BFD sessions to the flat BFDIndex used in the BfdSessionTable. 5. BFD MIB Module Definitions + This MIB module makes references to the following documents. + [RFC2578], [RFC2579], [RFC2580], [RFC3291], and [RFC3413]. + BFD-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Counter64, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI -- [RFC2578] - MODULE-COMPLIANCE, OBJECT-GROUP, - NOTIFICATION-GROUP - FROM SNMPv2-CONF -- [RFC2580] - TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TimeStamp + BFD MIB October 20, 2006 + FROM SNMPv2-TC -- [RFC2579] + MODULE-COMPLIANCE, OBJECT-GROUP, + NOTIFICATION-GROUP + FROM SNMPv2-CONF -- [RFC2580] + InetAddress, InetAddressType, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC3291] ; bfdMIB MODULE-IDENTITY LAST-UPDATED "200507221200Z" -- 04 July 2005 12:00:00 EST ORGANIZATION "IETF" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. @@ -176,24 +187,27 @@ bfdObjects OBJECT IDENTIFIER ::= { bfdMIB 1 } bfdConformance OBJECT IDENTIFIER ::= { bfdMIB 3 } bfdScalarObjects OBJECT IDENTIFIER ::= { bfdObjects 1 } -- Textual Conventions BfdSessIndexTC ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" + BFD MIB October 20, 2006 + STATUS current DESCRIPTION "An index used to uniquely identify BFD sessions." SYNTAX Unsigned32 (1..4294967295) + BfdInterval ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The BFD interval delay in microseconds." SYNTAX Unsigned32 (1..4294967295) BfdDiag ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A common BFD diagnostic code." @@ -223,20 +237,22 @@ The value 'enabled' denotes that the BFD Process is active on at least one interface; 'disabled' disables it on all interfaces." DEFVAL { enabled } ::= { bfdScalarObjects 1 } bfdVersionNumber OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current + BFD MIB October 20, 2006 + DESCRIPTION "The current version number of the BFD protocol." REFERENCE " BFD Version 0 (draft-katz-ward-bfd-02.txt)" DEFVAL { 0 } ::= { bfdScalarObjects 3 } -- BFD Session Table -- The BFD Session Table specifies BFD session specific -- information. @@ -269,22 +285,24 @@ bfdSessState INTEGER, bfdSessRemoteHeardFlag TruthValue, bfdSessDiag Unsigned32, bfdSessOperMode INTEGER, bfdSessDemandModeDesiredFlag TruthValue, bfdSessEchoFuncModeDesiredFlag TruthValue, bfdSessControlPlanIndepFlag TruthValue, bfdSessAddrType InetAddressType, bfdSessAddr InetAddress, bfdSessDesiredMinTxInterval BfdInterval, - bfdSessDesiredMinRxInterval BfdInterval, - bfdSessDesiredMinEchoRxInterval BfdInterval, + bfdSessReqMinRxInterval BfdInterval, + BFD MIB October 20, 2006 + + bfdSessReqMinEchoRxInterval BfdInterval, bfdSessDetectMult Unsigned32, bfdSessStorType StorageType, bfdSessRowStatus RowStatus, bfdSessAuthPresFlag TruthValue, bfdSessAuthenticationType INTEGER } bfdSessIndex OBJECT-TYPE SYNTAX BfdSessIndexTC MAX-ACCESS not-accessible @@ -318,20 +336,21 @@ ::= { bfdSessEntry 3 } bfdSessRemoteDiscr OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the session discriminator chosen by the remote system for this BFD session." ::= { bfdSessEntry 4 } + BFD MIB October 20, 2006 bfdSessUdpPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The UDP Port for BFD. The default value is the well-known value for this port." REFERENCE "draft-katz-ward-bfd-02.txt and @@ -366,22 +385,25 @@ the BFD session." ::= { bfdSessEntry 7 } bfdSessDiag OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "A diagnostic code specifying the local system's reason for the last transition of the session from up(1) + BFD MIB October 20, 2006 + to some other state." ::= { bfdSessEntry 8 } + bfdSessOperMode OBJECT-TYPE SYNTAX INTEGER { asyncModeWEchoFun(1), asynchModeWOEchoFun(2), demandModeWEchoFunction(3), demandModeWOEchoFunction(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies current operating mode that BFD @@ -413,20 +435,22 @@ DESCRIPTION "This object indicates that the local system's desire to use Echo mode. Specifically, it is set to true(1) if the local system wishes to use Echo mode or false(0) if not" DEFVAL { false } ::= { bfdSessEntry 11 } bfdSessControlPlanIndepFlag OBJECT-TYPE SYNTAX TruthValue + BFD MIB October 20, 2006 + MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates that the local system's ability to continue to function through a disruption of the control plane. Specifically, it is set to true(1) if the local system BFD implementation is independent of the control plane. Otherwise, the value is set to false(0)" DEFVAL { false } @@ -461,39 +485,41 @@ DESCRIPTION "This object specifies IP address of the interface associated with this BFD session. It can also be used to enabled BFD on a specific interface. The value is set to zero when BFD session is not associated with a specific interface. " ::= { bfdSessEntry 14 } bfdSessDesiredMinTxInterval OBJECT-TYPE SYNTAX BfdInterval + BFD MIB October 20, 2006 + MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the minimum interval, in microseconds, that the local system would like to use when transmitting BFD Control packets." ::= { bfdSessEntry 15 } - bfdSessDesiredMinRxInterval OBJECT-TYPE + bfdSessReqMinRxInterval OBJECT-TYPE SYNTAX BfdInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the minimum interval, in microseconds, between received BFD Control packets the local system is capable of supporting." ::= { bfdSessEntry 16 } - bfdSessDesiredMinEchoRxInterval OBJECT-TYPE + bfdSessReqMinEchoRxInterval OBJECT-TYPE SYNTAX BfdInterval MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the minimum interval, in microseconds, between received BFD Echo packets that this system is capable of supporting." ::= { bfdSessEntry 17 } bfdSessDetectMult OBJECT-TYPE @@ -509,20 +535,22 @@ MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row." ::= { bfdSessEntry 19 } bfdSessRowStatus OBJECT-TYPE + BFD MIB October 20, 2006 + SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the bfdSessRowStatus and bfdSessStorageType." ::= { bfdSessEntry 20 } @@ -557,20 +585,22 @@ bfdSessPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF BfdSessPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies BFD Session performance counters." ::= { bfdObjects 3 } bfdSessPerfEntry OBJECT-TYPE + BFD MIB October 20, 2006 + SYNTAX BfdSessPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by a BFD-enabled node for every BFD Session. bfdCounterDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table." AUGMENTS { bfdSessEntry } ::= { bfdSessPerfTable 1 } @@ -605,20 +635,22 @@ MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of BFD messages sent for this BFD session." ::= { bfdSessPerfEntry 2 } bfdSessUpTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current + BFD MIB October 20, 2006 + DESCRIPTION "The value of sysUpTime on the most recent occasion at which the session came up. If no such up event exists this object contains a zero value." ::= { bfdSessPerfEntry 3 } bfdSessPerfLastSessDownTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current @@ -653,22 +685,25 @@ STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which any one or more of the session counters suffered a discontinuity. The relevant counters are the specific instances associated with this BFD session of any Counter32 object contained in the BfdSessPerfTable. If no such discontinuities have occurred since the last re-initialization of the local management + BFD MIB October 20, 2006 + subsystem, then this object contains a zero value." ::= { bfdSessPerfEntry 7 } + bfdSessPerfPktInHC OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This value represents the total number of BFD messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfPktIn if bfdSessPerfPktInHC is supported according to the rules spelled out in RFC2863." @@ -698,23 +733,26 @@ indexing of the BFD sessions to the flat BFDIndex used in the BfdSessionTable. Implementors need to be aware that if the value of the bfdSessAddr (an OID) has more that 111 sub-identifiers, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. " + BFD MIB October 20, 2006 + REFERENCE "BFD Version 0 (draft-katz-ward-bfd-02.txt)" ::= { bfdObjects 4 } + bfdSessMapEntry OBJECT-TYPE SYNTAX BfdSessMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The BFD Session Entry describes BFD session that is mapped to this index. Implementors need to be aware that if the value of the mplsInSegmentMapLabelPtrIndex (an OID) has more @@ -745,20 +783,22 @@ -- Notification Configuration bfdSessNotificationsEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is set to true(1), then it enables the emission of bfdSessUp and bfdSessDown + BFD MIB October 20, 2006 + notifications; otherwise these notifications are not emitted." REFERENCE "See also RFC3413 for explanation that notifications are under the ultimate control of the MIB modules in this document." DEFVAL { false } ::= { bfdScalarObjects 4 } bfdSessUp NOTIFICATION-TYPE @@ -793,20 +833,22 @@ bfdSessDiag -- high range value } STATUS current DESCRIPTION "This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the down(4) or adminDown(5) states from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e: down(4) or adminDown(5)). The two instances + BFD MIB October 20, 2006 + of bfdSessDiag in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of sessions have transitioned into the down(4) or adminDown(5) states at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be @@ -841,20 +883,22 @@ MODULE -- This module. MANDATORY-GROUPS { bfdSessionGroup, bfdSessionPerfGroup, bfdSessionPerfHCGroup, bfdNotificationGroup } GROUP bfdSessionPerfHCGroup DESCRIPTION "This group is mandatory for those bfdPerfTable + BFD MIB October 20, 2006 + entries for which any of the objects bfdSessPerfPktInHC or bfdSessPerfPktOutHC wraps around too quickly based on the criteria specified in RFC 2863 for high-capacity counters." GROUP bfdNotificationGroup DESCRIPTION "This group is only mandatory for those implementations which can efficiently implement the notifications contained in this group." @@ -887,22 +931,24 @@ bfdSessRemoteDiscr, bfdSessUdpPort, bfdSessState, bfdSessRemoteHeardFlag, bfdSessDiag, bfdSessOperMode, bfdSessDemandModeDesiredFlag, bfdSessEchoFuncModeDesiredFlag, bfdSessControlPlanIndepFlag, bfdSessDesiredMinTxInterval, - bfdSessDesiredMinRxInterval, - bfdSessDesiredMinEchoRxInterval, + bfdSessReqMinRxInterval, + BFD MIB October 20, 2006 + + bfdSessReqMinEchoRxInterval, bfdSessDetectMult, bfdSessStorType, bfdSessRowStatus, bfdSessMapBfdIndex, bfdSessAuthPresFlag, bfdSessAuthenticationType } STATUS current DESCRIPTION "Collection of objects needed for BFD sessions." @@ -935,20 +981,22 @@ performance of BFD sessions for which the values of bfdSessPerfPktIn, bfdSessPerfPktOut wrap around too quickly." ::= { bfdGroups 3 } bfdNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { bfdSessUp, bfdSessDown } + BFD MIB October 20, 2006 + STATUS current DESCRIPTION "Set of notifications implemented in this module." ::= { bfdGroups 4 } END 6. Security Considerations @@ -982,125 +1030,117 @@ table sensative. SNMP versions prior to SNMPv3 did not include adequate security. 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 allowed to access and GET/SET "read/change/create/delete" the objects in these MIB modules. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework "see [RFC3410], section 8", + BFD MIB October 20, 2006 + including full support for the SNMPv3 cryptographic mechanisms "for authentication and privacy". Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module, is properly configured to give access to the objects only to those principals "users" that have legitimate rights to indeed GET or SET "change/create/delete" them. -7. Acknowledgements - - We would like to thank David Ward for his comments and suggestions. +7. IANA Considerations -8. References + There is one MIB module contained in this document. The following + "IANA Considerations" subsection requests IANA for a new + assignment under the mib-2 subtree. New assignments can only + be made via a Standards Action as specified in [RFC2434]. -8.1 Normative References +7.1. IANA Considerations for BFD-STD-MIB - [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding - Detection", draft-ietf-bfd-base-02.txt. + The IANA is requested to assign { mib-2 XXX } to the + MPLS-L3VPN-STD-MIB module specified in this document. - [BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths", - draft-ietf-bfd-multihop-03.txt. +8. References - [BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow - BFD For MPLS LSPs, draft-ietf-bfd-mpls-02.txt. +8.1 Normative References [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 3291, May 2002. + [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding + Detection", draft-ietf-bfd-base-05.txt. + + BFD MIB October 20, 2006 + + [BFD-MH] Katz, D., and Ward, D., "BFD for Multihop Paths", + draft-ietf-bfd-multihop-04.txt. + + [BFD-LSP] Aggarwal, R., Kompella, K., T. D. Nadeau, and G. Swallow + BFD For MPLS LSPs, draft-ietf-bfd-mpls-03.txt. + 8.2 Informative References [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate - Requirement Levels", RFC 2119, BCP 14, March 1997. + Requirement Levels", RFC 2119, BCP 14, April 1997. [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP Applications", RFC 3413, December 2002. [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. -9. Authors' Addresses +9. Acknowledgements + + We would like to thank David Ward for his comments and suggestions. + +10. Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. 300 Beaver Brook Road Boxboro, MA 01719 - Phone: +1-978-936-1470 + Phone: 978-936-1470 Email: tnadeau@cisco.com Zafar Ali Cisco Systems Inc. 100 South Main St. #200 Ann Arbor, MI 48104, USA. - Phone: +1-734-276-2459 + Phone: 734-276-2459 Email: zali@cisco.com -10. Full Copyright Statement - - Copyright (C) The Internet Society (2005). This document is subject - to the rights, licenses and restrictions contained in BCP 78, and - except as set forth therein, the authors retain all their rights. - - This document and the information contained herein are provided on an - "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS - OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET - ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, - INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE - INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED - WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - -11. IANA Considerations - - There is one MIB module contained in this document. The following - "IANA Considerations" subsection requests IANA for a new - assignment under the mib-2 subtree. New assignments can only - be made via a Standards Action as specified in [RFC2434]. - -11.1. IANA Considerations for BFD-STD-MIB - The IANA is requested to assign { mib-2 XXX } to the - MPLS-L3VPN-STD-MIB module specified in this document. - -12. Intellectual Property Statement +11. Intellectual Property Statement + BFD MIB October 20, 2006 The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. @@ -1109,10 +1149,29 @@ attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. + +12. Full Copyright Statement + + Copyright (C) The Internet Society (2006). This document is subject + to the rights, licenses and restrictions contained in BCP 78, and + except as set forth therein, the authors retain all their rights. + + This document and the information contained herein are provided on an + "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS + OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET + ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, + INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE + INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED + WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. + +Acknowledgement + + Funding for the RFC Editor function is provided by the IETF + Administrative Support Activity (IASA).