draft-ietf-imss-fc-rtm-mib-00.txt   draft-ietf-imss-fc-rtm-mib-01.txt 
Internet Draft C. DeSanti Internet Draft C. DeSanti
S. Kode S. Kode
K. McCloghrie K. McCloghrie
S. Gai S. Gai
Cisco Systems Cisco Systems
22 August 2005 20 October 2005
Fibre-Channel Routing Information MIB Fibre-Channel Routing Information MIB
draft-ietf-imss-fc-rtm-mib-00.txt draft-ietf-imss-fc-rtm-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.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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/1id-abstracts.txt. http://www.ietf.org/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
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 for information related In particular, it describes managed objects for information related
to routing within a Fibre Channel fabric which is independent of the to routing within a Fibre Channel fabric which is independent of the
usage of a particular routing protocol. This memo was originally usage of a particular routing protocol.
developed as the SM-RTM project of T11.5 (http://www.t11.org). With
the approval of SM-RTM, the memo was forwarded to, and has become a
work item of, IETF's IMSS working group.
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 Short Overview of Fibre Channel .............................. 3 3 Short Overview of Fibre Channel .............................. 3
4 Relationship to Other MIBs ................................... 4 4 Relationship to Other MIBs ................................... 4
5 MIB Overview ................................................. 5 5 MIB Overview ................................................. 5
5.1 Fibre Channel management instance .......................... 5 5.1 Fibre Channel management instance .......................... 5
5.2 Switch Index ............................................... 5 5.2 Switch Index ............................................... 5
5.3 Fabric Index ............................................... 5 5.3 Fabric Index ............................................... 5
5.4 The t11FcRouteGroup Group .................................. 6 5.4 The t11FcRouteGroup Group .................................. 6
5.5 The t11FcRouteTable's INDEX ................................ 6
6 The T11-FC-ROUTE-MIB Module .................................. 7 6 The T11-FC-ROUTE-MIB Module .................................. 7
7 Intellectual Property ........................................ 17 7 Intellectual Property ........................................ 17
8 Acknowledgements ............................................. 17 8 Acknowledgements ............................................. 17
9 Normative References ......................................... 17 9 Normative References ......................................... 18
10 Informative References ...................................... 18 10 Informative References ...................................... 19
11 IANA Considerations ......................................... 18 11 IANA Considerations ......................................... 19
12 Security Considerations ..................................... 19 12 Security Considerations ..................................... 19
13 Authors' Addresses .......................................... 20 13 Authors' Addresses .......................................... 21
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 for information related In particular, it describes managed objects for information related
to the Fibre Channel network's Routing Table for routing within a to the Fibre Channel network's Routing Table for routing within a
Fabric. Managed objects specific to particular routing protocols, Fabric. Managed objects specific to particular routing protocols,
such as FSPF, are not specified in this MIB module. such as FSPF, are not specified in this MIB module.
skipping to change at page 4, line 37 skipping to change at page 4, line 37
lookup the destination address of a received frame in order to lookup the destination address of a received frame in order to
determine the best link by which to forward that frame towards its determine the best link by which to forward that frame towards its
destination. destination.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
The first standardized MIB for Fibre Channel [RFC2837] was focussed The first standardized MIB for Fibre Channel [RFC2837] was focussed
on Fibre Channel switches. It is being replaced by the more generic on Fibre Channel switches. It is being replaced by the more generic
Fibre Channel Management MIB [FC-MGMT] which defines basic Fibre Channel Management MIB [FC-MGMT] which defines basic
information for Fibre Channel hosts and switches, including information for Fibre Channel hosts and switches, including
extensions to the standard IF-MIB for Fibre Channel interfaces. extensions to the standard IF-MIB [RFC2863] for Fibre Channel
interfaces.
This MIB extends beyond [FC-MGMT] to cover the routing of traffic This MIB extends beyond [FC-MGMT] to cover the routing of traffic
within a Fabric of a Fibre Channel network. The standard routing within a Fabric of a Fibre Channel network. The standard routing
protocol for Fibre Channel is FSPF [FC-SW-4]. Another MIB [FC-FSM- protocol for Fibre Channel is FSPF [FC-SW-4]. Another MIB [FC-FSM-
MIB] specifies management information specific to FSPF. This MIB MIB] specifies management information specific to FSPF. This MIB
contains routing information which is independent of FSPF (i.e., it contains routing information which is independent of FSPF (i.e., it
would still apply even if a routing protocol other than FSPF were in would still apply even if a routing protocol other than FSPF were in
use in the network). use in the network).
This MIB imports some common Textual Conventions from T11-TC-MIB, This MIB imports some common Textual Conventions from T11-TC-MIB,
skipping to change at page 6, line 22 skipping to change at page 6, line 23
It is quite possible, and may even be likely, that a Fibre Channel It is quite possible, and may even be likely, that a Fibre Channel
switch will have ports connected to multiple virtual and/or physical switch will have ports connected to multiple virtual and/or physical
Fabrics. Thus, in order to simplify a management protocol query Fabrics. Thus, in order to simplify a management protocol query
concerning all the Fabrics to which a single switch is connected, concerning all the Fabrics to which a single switch is connected,
fcmSwitchIndex will be listed before t11FcRouteFabricIndex when they fcmSwitchIndex will be listed before t11FcRouteFabricIndex when they
both appear in the same INDEX clause. both appear in the same INDEX clause.
5.4. The t11FcRouteGroup Group 5.4. The t11FcRouteGroup Group
This MIB contains one object group, the t11FcRouteGroup. This group This MIB contains one object group, the t11FcRouteGroup, which
contains objects to allow the displaying and the configuring of contains objects to allow the displaying and the configuring of
routes in the Fibre Channel Routing tables for the locally-managed routes in the Fibre Channel Routing tables for the locally-managed
switches. switches.
5.5. The t11FcRouteTable's INDEX
It is normally valuable for a MIB table which contains routes to be
ordered such that a management application is able to query the table
based on some attribute, without having to read every row in the MIB
table. This requires the rows in the table be ordered according to
such attributes, and thus, that those attributes be represented by
objects included in the table's INDEX clause. Examples of this can
be seen in the ipCidrRouteTable [RFC2096], and more recently, the
inetCidrRouteTable in [RFC2096bis].
Providing the same useful feature in the MIB in this document,
results in having an unusually large number (ten) of objects in the
t11FcRouteTable's INDEX clause. However, all ten are either integers
or strings of length 0 or 3 octets. Thus, the aggregate number of
sub-identifiers to be appended to an OBJECT-TYPE's OID when naming an
instance of an object in this table, is at most 22 sub-identifiers,
i.e., less than the *minimum* number to be appended for the
inetCidrRouteTable table. In other words, while ten is an unusually
large number of objects in an INDEX clause, the resultant OIDs are
not unusually large.
6. The T11-FC-ROUTE-MIB Module 6. The T11-FC-ROUTE-MIB Module
T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578] Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
RowStatus, TimeStamp, RowStatus, TimeStamp,
StorageType FROM SNMPv2-TC -- [RFC2579] StorageType FROM SNMPv2-TC -- [RFC2579]
InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB -- [RFC2863] InterfaceIndex, InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
fcmInstanceIndex, fcmSwitchIndex, fcmInstanceIndex, fcmSwitchIndex,
FcAddressIdOrZero, FcDomainIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT] FcAddressIdOrZero, FcDomainIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT]
T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB]
t11FcRouteMIB MODULE-IDENTITY t11FcRouteMIB MODULE-IDENTITY
LAST-UPDATED "200504140000Z" LAST-UPDATED "200510120000Z"
ORGANIZATION "T11" ORGANIZATION "T11"
CONTACT-INFO CONTACT-INFO
" Claudio DeSanti " Claudio DeSanti
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 USA San Jose, CA 95134 USA
EMail: cds@cisco.com EMail: cds@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA USA 95134 San Jose, CA USA 95134
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for configuring and displaying Fibre "The MIB module for configuring and displaying Fibre
Channel Route Information." Channel Route Information.
REVISION "200504140000Z" Copyright (C) The Internet Society (2005). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Editor: replace yyyy with actual RFC number & remove this note
REVISION "200510120000Z"
DESCRIPTION DESCRIPTION
"Initial version of this MIB module." "Initial version of this MIB module, published as RFCyyyy."
::= { mib-2 nnn } -- to be determined later -- RFC-Editor, replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } -- to be assigned by IANA
-- RFC Editor: replace XXX with IANA-assigned number & remove this note
t11FcRouteNotifications OBJECT IDENTIFIER ::= { t11FcRouteMIB 0 } t11FcRouteNotifications OBJECT IDENTIFIER ::= { t11FcRouteMIB 0 }
t11FcRouteObjects OBJECT IDENTIFIER ::= { t11FcRouteMIB 1 } t11FcRouteObjects OBJECT IDENTIFIER ::= { t11FcRouteMIB 1 }
t11FcRouteConformance OBJECT IDENTIFIER ::= { t11FcRouteMIB 2 } t11FcRouteConformance OBJECT IDENTIFIER ::= { t11FcRouteMIB 2 }
-- --
-- Per-Fabric routing information -- Per-Fabric routing information
-- --
t11FcRouteFabricTable OBJECT-TYPE t11FcRouteFabricTable OBJECT-TYPE
SYNTAX SEQUENCE OF T11FcRouteFabricEntry SYNTAX SEQUENCE OF T11FcRouteFabricEntry
skipping to change at page 9, line 37 skipping to change at page 9, line 41
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Fibre Channel Routing tables for the "The Fibre Channel Routing tables for the
locally-managed switches. This table lists all the locally-managed switches. This table lists all the
routes that are configured in and/or computed by any routes that are configured in and/or computed by any
local switch for any Fabric. local switch for any Fabric.
Such routes are used by a switch to forward frames (of user Such routes are used by a switch to forward frames (of user
data) on a Fabric. The conceptual process is based on data) on a Fabric. The conceptual process is based on
extracting the Destination Fibre Channel Addresss Identifier extracting the Destination Fibre Channel Address Identifier
(D_ID) out of a received frame (of user data), and comparing (D_ID) out of a received frame (of user data), and comparing
it to each entry of this table which is applicable to the it to each entry of this table which is applicable to the
given switch and Fabric. Such comparison consists of first given switch and Fabric. Such comparison consists of first
performing a logical-AND of the extracted D_ID with a mask performing a logical-AND of the extracted D_ID with a mask
(the value of t11FcRouteDestMask), and second comparing the (the value of t11FcRouteDestMask), and second comparing the
result of that 'AND' operation to the value of result of that 'AND' operation to the value of
t11FcRouteDestAddrId. A similar comparison is made of the t11FcRouteDestAddrId. A similar comparison is made of the
Source Fibre Channel Addresss Identifier (D_ID) of a frame Source Fibre Channel Addresss Identifier (D_ID) of a frame
against the t11FcRouteSrcAddrId and t11FcRouteSrcMask values against the t11FcRouteSrcAddrId and t11FcRouteSrcMask values
of an entry. If an entry's value of t11FcRouteInInterface of an entry. If an entry's value of t11FcRouteInInterface
skipping to change at page 13, line 22 skipping to change at page 13, line 24
This object can have a value of zero if the value This object can have a value of zero if the value
of t11FcRouteProto is 'local'." of t11FcRouteProto is 'local'."
::= { t11FcRouteEntry 8 } ::= { t11FcRouteEntry 8 }
t11FcRouteMetric OBJECT-TYPE t11FcRouteMetric OBJECT-TYPE
SYNTAX Unsigned32 (0..65536) SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing metric for this route. "The routing metric for this route.
The use of this object is dependent on
t11FcRouteProto." The use of this object is dependent on t11FcRouteProto."
::= { t11FcRouteEntry 9 } ::= { t11FcRouteEntry 9 }
t11FcRouteType OBJECT-TYPE t11FcRouteType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
local(1), local(1),
remote(2) remote(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of route. "The type of route.
local(1): refers to a route for which the next Fibre
Channel port is the final destination; local(1) - a route for which the next Fibre Channel
remote(2): refers to a route for which the next Fibre port is the final destination;
Channel port is not the final destination." remote(2) - a route for which the next Fibre Channel
port is not the final destination."
DEFVAL {local} DEFVAL {local}
::= { t11FcRouteEntry 10 } ::= { t11FcRouteEntry 10 }
t11FcRouteIfDown OBJECT-TYPE t11FcRouteIfDown OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
remove(1), remove(1),
retain(2) retain(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 17, line 7 skipping to change at page 17, line 7
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for displaying and configuring "A collection of objects for displaying and configuring
routes." routes."
::= { t11FcRouteGroups 1 } ::= { t11FcRouteGroups 1 }
END END
7. Intellectual Property 7. Intellectual Property
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 or other rights that might be claimed to intellectual property 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; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat."
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 which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director."
8. Acknowledgements 8. Acknowledgements
This document was originally developed and approved by the INCITS This document was originally developed and approved by the INCITS
Task Group T11.5. Task Group T11.5 (http://www.t11.org) as the SM-RTM project. We wish
to acknowledge the contributions and comments from the INCITS
Technical Committee T11, including the following:
T11 Chair: Robert Snively, Brocade
T11 Vice Chair: Claudio DeSanti, Cisco Systems
T11.5 Chair: Roger Cummings, Symantec
T11.5 members, especially:
Ken Hirata, Emulex
Scott Kipp, McData
Elizabeth G. Rodriguez, Dot Hill
9. Normative References 9. Normative References
[RFC2578] [RFC2578]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Structure of Management Information Version 2 and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] [RFC2579]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999. 2579, April 1999.
[RFC2580] [RFC2580]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC
2580, April 1999. 2580, April 1999.
[RFC2863]
McCloghrie, K., and F. Kastenholz, "The Interface$ Group MIB", RFC
2863, June 2000.
[RFC3411] [RFC3411]
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing Simple Network Management Protocol (SNMP) Management Describing Simple Network Management Protocol (SNMP) Management
Frameworks", STD 58, RFC 3411, December 2002. Frameworks", STD 58, RFC 3411, December 2002.
[FC-SW-3] [FC-SW-3]
"Fibre Channel - Switch Fabric - 3 (FC-SW-3)", INCITS 384-2004, "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", INCITS 384-2004,
2004. 2004.
[FC-SW-4] [FC-SW-4]
skipping to change at page 18, line 33 skipping to change at page 19, line 8
Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf- Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf-
imss-fc-fam-mib-nn.txt), work-in-progress. imss-fc-fam-mib-nn.txt), work-in-progress.
[FC-FSM-MIB] [FC-FSM-MIB]
DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "MIB for DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "MIB for
Fibre-Channel's Fabric Shortest Path First Protocol", Internet- Fibre-Channel's Fabric Shortest Path First Protocol", Internet-
Draft (draft-ietf-imss-fc-fspf-mib-nn.txt), work-in-progress. Draft (draft-ietf-imss-fc-fspf-mib-nn.txt), work-in-progress.
10. Informative References 10. Informative References
[RFC2741]
Daniele, M., Wijnen, B., Ellison, M., and D. Francisco, "Agent
Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000.
[RFC2837] [RFC2837]
Teow, K., "Definitions of Managed Objects for the Fabric Element in Teow, K., "Definitions of Managed Objects for the Fabric Element in
Fibre Channel Standard", RFC 2837, May 2000. Fibre Channel Standard", RFC 2837, May 2000.
[RFC3410] [RFC3410]
Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and
Applicability Statements for Internet- Standard Management Applicability Statements for Internet- Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
[RFC2096]
Baker, F., "IP Forwarding Table MIB", RFC 2096, January 1997.
[RFC2096bis]
Haberman, B., "IP Forwarding Table MIB", Internet-Draft (draft-
ietf-ipv6-rfc2096-update-07.txt), work-in-progress.
11. IANA Considerations 11. IANA Considerations
IANA is requested to make the OID assignment for the MIB module under IANA is requested to make an MIB OID assignment for the T11-FC-ROUTE-
the appropriate subtree. MIB module under the appropriate subtree.
12. Security Considerations 12. Security Considerations
There are several management objects defined in this MIB module with There are several management objects defined in this MIB module with
a MAX-ACCESS clause of read-write and/or read-create. Such objects a MAX-ACCESS clause of read-write and/or read-create. Such objects
may be considered sensitive or vulnerable in some network may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These objects and their network operations. These objects and their
sensitivity/vulnerability are: sensitivity/vulnerability are:
skipping to change at page 21, line 5 skipping to change at page 21, line 35
Phone: +1 408-526-5260 Phone: +1 408-526-5260
Email: kzm@cisco.com Email: kzm@cisco.com
Silvano Gai Silvano Gai
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA USA 95134 San Jose, CA USA 95134
Phone: +1 408-526-7269 Phone: +1 408-526-7269
Email: sgai@cisco.com Email: sgai@cisco.com
14. Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
"This document and the information contained herein are provided on This document and the information contained herein are provided on an
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
15. Disclaimer of validity Disclaimer of validity
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
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
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.
Acknowledgment Acknowledgment
 End of changes. 32 change blocks. 
47 lines changed or deleted 96 lines changed or added

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