Internet Draft C. DeSanti S. Kode K. McCloghrie S. Gai Cisco Systems 10 January 2005 Fibre-Channel Routing Information MIB 05-011v0 and draft-kzm-fc-rtm-mib-00.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html" Copyright Notice Copyright (C) The Internet Society (2005). All Rights Reserved. Abstract This memo 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 information related to routing within a Fibre Channel fabric which is independent of the usage of a particular routing protocol. At present, this memo is in development as part of the SM-RTM project of T11.5 (http://www.t11.org). The plan is that it will later become a work item of IETF's IMSS working group. Expires July 2005 [Page 1] Internet Draft FC Routing Information MIB January 2005 Table of Contents 1 Introduction ................................................. 3 1.1 Change Log ................................................. 3 2 The Internet-Standard Management Framework ................... 3 3 Short Overview of Fibre Channel .............................. 4 4 Relationship to Other MIBs ................................... 5 5 MIB Overview ................................................. 5 5.1 Fibre Channel management instance .......................... 5 5.2 Switch Index ............................................... 6 5.3 Fabric Index ............................................... 6 5.4 The t11FcRouteGroup Group .................................. 6 6 The T11-FC-ROUTE-MIB Module .................................. 7 7 Intellectual Property ........................................ 14 8 Acknowledgements ............................................. 15 9 Normative References ......................................... 15 10 Informative References ...................................... 16 11 IANA Considerations ......................................... 16 12 Security Considerations ..................................... 16 13 Authors' Addresses .......................................... 18 Expires July 2005 [Page 2] Internet Draft FC Routing Information MIB January 2005 1. Introduction This memo 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 information related to the Fibre Channel network's Routing Table for routing within a Fabric. Managed objects specific to particular routing protocols, such as FSPF, are not specified in this MIB module. 1.1. Change Log This section to be deleted when the document becomes approved. 1.1.1. Initial version: Initial version was submitted to T11.5 as 04-747v0 on 13 November 2004. 1.1.2. Changes made in 10 January version The following changes were made for the version was submitted to T11.5 as: 05-011v0 on 10 January 2005, and to the IETF as: draft-kzm-imss-fc-rtm-mib-00.txt. - created the t11FcRouteFabricTable to hold t11FcRouteFabricLastChange (was previously a scalar). - added t11FcRouteStorageType (see requirement for a StorageType object on page 22 of draft-ietf-ops-mib-review-guidelines-03.txt). 2. 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 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]. Expires July 2005 [Page 3] Internet Draft FC Routing Information MIB January 2005 3. Short Overview of Fibre Channel The Fibre Channel (FC) is logically a bidirectional point-to-point serial data channel, structured for high performance. Fibre Channel provides a general transport vehicle for higher level protocols such as Small Computer System Interface (SCSI) command sets, the High- Performance Parallel Interface (HIPPI) data framing, IP (Internet Protocol), IEEE 802.2, and others. Physically, Fibre Channel is an interconnection of multiple communication points, called N_Ports, interconnected either by a switching network, called a Fabric, or by a point-to-point link. A Fibre Channel "node" consists of one or more N_Ports. A Fabric may consist of multiple Interconnect Elements, some of which are switches. An N_Port connects to the Fabric via a port on a switch called an F_Port. When multiple FC nodes are connected to a single port on a switch via an "Arbitrated Loop" topology, the switch port is called an FL_Port, and the nodes' ports are called NL_Ports. The term Nx_Port is used to refer to either an N_Port or an NL_Port. The term Fx_Port is used to refer to either an F_Port or an FL_Port. A switch port, which is interconnected to another switch port via an Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a bridge device with an E_Port on a switch; a B_Port provides a subset of E_Port functionality. Many Fibre Channel components, including the fabric, each node, and most ports, have globally-unique names. These globally-unique names are typically formatted as World Wide Names (WWNs). More information on WWNs can be found in [FC-FS]. WWNs are expected to be persistent across agent and unit resets. Fibre Channel frames contain 24-bit address identifiers which identify the frame's source and destination ports. Each FC port has both an address identifier and a WWN. When a fabric is in use, the FC address identifiers are dynamic and are assigned by a switch. Each octet of a 24-bit address represents a level in an address hierarchy, with a Domain_ID being the highest level of the hierarchy. The routing of frames within the Fabric is normally based on the standard routing protocol, called the Fabric Shortest Path First (FSPF) protocol. The operation of FSPF (or any other routing protocol) allows a switch to generate and maintain its own routing table of how to forward frames it receives, i.e., a table in which to lookup the destination address of a received frame in order to determine the best link by which to forward that frame towards its Expires July 2005 [Page 4] Internet Draft FC Routing Information MIB January 2005 destination. 4. Relationship to Other MIBs The first standardized MIB for Fibre Channel [RFC2837] was focussed on Fibre Channel switches. It is being replaced by the more generic Fibre Channel Management MIB [FC-MGMT] which defines basic information for Fibre Channel hosts and switches, including extensions to the standard IF-MIB for Fibre Channel interfaces. This MIB extends beyond [FC-MGMT] to cover the routing of traffic within a Fabric of a Fibre Channel network. The standard routing protocol for Fibre Channel is FSPF [FC-SW-4]. Another MIB [FC-FSM- MIB] specifies management information specific to FSPF. This MIB contains routing information which is independent of FSPF (i.e., it would still apply even if a routing protocol other than FSPF were in use in the network). This MIB imports some common Textual Conventions from T11-TC-MIB, defined in [FC-FAM-MIB]. 5. MIB Overview This MIB module provides the means for monitoring the operation of, and configuring some parameters of, one or more instances of the FSPF protocol. (Note that there are no definitions in this MIB module of "managed actions" which can be invoked via SNMP.) 5.1. Fibre Channel management instance A Fibre Channel management instance is defined in [FC-MGMT] as a separable managed instance of Fibre Channel functionality. Fibre Channel functionality may be grouped into Fibre Channel management instances in whatever way is most convenient for the implementation(s). For example, one such grouping accommodates a single SNMP agent having multiple AgentX [RFC2741] sub-agents, with each sub-agent implementing a different Fibre Channel management instance. The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB [FC-MGMT] as the index value to uniquely identify each Fibre Channel management instance within the same SNMP context ([RFC3411] section 3.3.1). Expires July 2005 [Page 5] Internet Draft FC Routing Information MIB January 2005 5.2. Switch Index The FC-MGMT-MIB [FC-MGMT] defines the fcmSwitchTable as a table of information about Fibre Channel switches which are managed by Fibre Channel management instances. Each Fibre Channel management instance can manage one or more Fibre Channel switches. The Switch Index, fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value to uniquely identify a Fibre Channel switch amongst those (one or more) managed by the same Fibre Channel management instance. 5.3. Fabric Index The latest standard for an interconnecting Fabric containing multiple Fabric Switch elements is [FC-SW-4]. [FC-SW-4] specifies the operation of both a single Fabric in a physical infrastructure, as well as the support of multiple Virtual Fabrics operating within one (or more) physical infrastructures. Whether operating on a physical Fabric (i.e., without Virtual Fabrics) or within a Virtual Fabric, the operation of FSPF within a Fabric is identical. Therefore, this MIB defines all Fabric-related information in tables which are INDEX- ed by an arbitrary integer, named a "Fabric Index", the syntax of which is IMPORTed from the T11-TC-MIB. In a physical Fabric (i.e., without Virtual Fabrics), the value of this Fabric Index will always be 1. In an environment of multiple Virtual Fabrics, this index serves to distinguish one Virtual Fabric from another. It is quite possible, and may even be likely, that (a port of) a Fibre Channel switch will be connected to multiple such Fabrics. Thus, in order to simplify a management protocol query concerning all the Fabrics to which a single switch is connected, fcmSwitchIndex will be listed before t11FamFabricIndex when they both appear in the same INDEX clause. 5.4. The t11FcRouteGroup Group This MIB contains one object group, the t11FcRouteGroup. This group contains objects to allow the displaying and the configuring of routes in the Fibre Channel Routing tables for the locally-managed switches. Expires July 2005 [Page 6] Internet Draft FC Routing Information MIB January 2005 6. The T11-FC-ROUTE-MIB Module T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] RowStatus, TruthValue, TimeStamp, StorageType FROM SNMPv2-TC -- [RFC2579] InterfaceIndex FROM IF-MIB -- [RFC2863] fcmInstanceIndex, fcmSwitchIndex, FcAddressIdOrZero, FcDomainIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT] T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] t11FcRouteMIB MODULE-IDENTITY LAST-UPDATED "200501040000Z" ORGANIZATION "T11" CONTACT-INFO " Claudio DeSanti Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA EMail: cds@cisco.com Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Email: kzm@cisco.com" DESCRIPTION "The MIB module for configuring and displaying Fibre Channel Route Information." REVISION "200501040000Z" DESCRIPTION "Initial version of this MIB module." ::= { mib-2 nnn } -- to be determined later t11FcRouteNotifications OBJECT IDENTIFIER ::= { t11FcRouteMIB 0 } t11FcRouteObjects OBJECT IDENTIFIER ::= { t11FcRouteMIB 1 } t11FcRouteConformance OBJECT IDENTIFIER ::= { t11FcRouteMIB 2 } Expires July 2005 [Page 7] Internet Draft FC Routing Information MIB January 2005 -- -- Per-Fabric routing information -- t11FcRouteFabricTable OBJECT-TYPE SYNTAX SEQUENCE OF T11FcRouteFabricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table containing Fibre Channel Routing information which is specific to a Fabric." ::= { t11FcRouteObjects 1 } t11FcRouteFabricEntry OBJECT-TYPE SYNTAX T11FcRouteFabricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains routing information specific to a particular Fabric on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex)." INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FcRouteFabricIndex } ::= { t11FcRouteFabricTable 1 } T11FcRouteFabricEntry ::= SEQUENCE { t11FcRouteFabricIndex T11FabricIndex, t11FcRouteFabricLastChange TimeStamp } t11FcRouteFabricIndex OBJECT-TYPE SYNTAX T11FabricIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index value which uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-3, only a single Fabric can operate within a physical infrastructure, and thus, the value of this Fabric Index will always be 1. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures. In such a case, index value is used to uniquely identify a Expires July 2005 [Page 8] Internet Draft FC Routing Information MIB January 2005 particular Fabric within a physical infrastructure." ::= { t11FcRouteFabricEntry 1 } t11FcRouteFabricLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the most recent time when any corresponding row in the t11FcRouteTable, was created, modified, or deleted. A corresponding row in the t11FcRouteTable is for the same management instance, the same switch and same Fabric as the row in this table. If no change has occurred since the last restart of the management system, then the value of this object is 0." ::= { t11FcRouteFabricEntry 2 } -- -- Fibre Channel Routing table -- t11FcRouteTable OBJECT-TYPE SYNTAX SEQUENCE OF T11FcRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Fibre Channel Routing tables for the locally-managed switches. This table lists all the routes that are configured in and/or calculated by any local switch for any Fabric. For entries configured by a user, t11FcRouteProto has the value 'netmgmt'; only entries of this type can be deleted by the user." ::= { t11FcRouteObjects 2 } t11FcRouteEntry OBJECT-TYPE SYNTAX T11FcRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains a route to a particular destination on a particular Fabric via a particular output interface, and learned in a particular manner." INDEX { fcmInstanceIndex, fcmSwitchIndex, Expires July 2005 [Page 9] Internet Draft FC Routing Information MIB January 2005 t11FcRouteFabricIndex, t11FcRouteDestAddrId, t11FcRouteDestMask, t11FcRouteProto, t11FcRouteInterface } ::= { t11FcRouteTable 1 } T11FcRouteEntry ::= SEQUENCE { t11FcRouteDestAddrId FcAddressIdOrZero, t11FcRouteDestMask FcAddressIdOrZero, t11FcRouteProto INTEGER, t11FcRouteInterface InterfaceIndex, t11FcRouteDomainId FcDomainIdOrZero, t11FcRouteMetric Unsigned32, t11FcRouteType INTEGER, t11FcRoutePermanent TruthValue, t11FcRouteStorageType StorageType, t11FcRouteRowStatus RowStatus } t11FcRouteDestAddrId OBJECT-TYPE SYNTAX FcAddressIdOrZero MAX-ACCESS not-accessible STATUS current DESCRIPTION "The destination FC_ID of this route." ::= { t11FcRouteEntry 1 } t11FcRouteDestMask OBJECT-TYPE SYNTAX FcAddressIdOrZero MAX-ACCESS not-accessible STATUS current DESCRIPTION "The mask to be logical-ANDed with the destination address Id before being compared to the value in the t11FcRouteDestAddrId field. This can only be 255.255.255 or 255.255.0 or 255.0.0." ::= { t11FcRouteEntry 2 } t11FcRouteProto OBJECT-TYPE SYNTAX INTEGER { other(1), local(2), netmgmt(3), fspf(4) } Expires July 2005 [Page 10] Internet Draft FC Routing Information MIB January 2005 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The mechanism via which this route was learned: other(1) - not specified local(2) - local interface netmgmt(3)- static route fspf(4) - Fibre Shortest Path First. " ::= { t11FcRouteEntry 3 } t11FcRouteInterface OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ifIndex value, which identifies the local Fibre Channel interface through which the next hop of this route is to be reached." ::= { t11FcRouteEntry 4 } t11FcRouteDomainId OBJECT-TYPE SYNTAX FcDomainIdOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "The domain ID of next hop switch. This object can have a value of zero if the value of t11FcRouteProto is 'local'." ::= { t11FcRouteEntry 5 } t11FcRouteMetric OBJECT-TYPE SYNTAX Unsigned32 (0..65536) MAX-ACCESS read-create STATUS current DESCRIPTION "The routing metric for this route. The use of this object is dependent on t11FcRouteProto." ::= { t11FcRouteEntry 6 } t11FcRouteType OBJECT-TYPE SYNTAX INTEGER { Expires July 2005 [Page 11] Internet Draft FC Routing Information MIB January 2005 local(1), remote(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of route. local(1): refers to a route for which the next hop is the final destination; remote(2): refers to a route for which the next hop is not the final destination." DEFVAL {local} ::= { t11FcRouteEntry 7 } t11FcRoutePermanent OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object indicates what happens to this route when the output interface (given by the corresponding value of t11FcRouteInterface) is operationally 'down'. If this object's value is 'true', the route is to be retained in this table. If this object's value is 'false', the route is to be removed from this table." DEFVAL {true} ::= { t11FcRouteEntry 8 } t11FcRouteStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row." DEFVAL { nonVolatile } ::= { t11FcRouteEntry 9 } t11FcRouteRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION Expires July 2005 [Page 12] Internet Draft FC Routing Information MIB January 2005 "The status of this conceptual row." ::= { t11FcRouteEntry 10 } -- -- Conformance -- t11FcRouteCompliances OBJECT IDENTIFIER ::= { t11FcRouteConformance 1 } t11FcRouteGroups OBJECT IDENTIFIER ::= { t11FcRouteConformance 2 } t11FcRouteCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities which implement the T11-FC-ROUTE-MIB." MODULE -- this module MANDATORY-GROUPS { t11FcRouteGroup } OBJECT t11FcRoutePermanent MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT t11FcRouteDomainId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT t11FcRouteMetric MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT t11FcRouteType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT t11FcRouteStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required." Expires July 2005 [Page 13] Internet Draft FC Routing Information MIB January 2005 OBJECT t11FcRouteRowStatus SYNTAX INTEGER { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { t11FcRouteCompliances 1 } t11FcRouteGroup OBJECT-GROUP OBJECTS { t11FcRouteFabricLastChange, t11FcRouteDomainId, t11FcRouteMetric, t11FcRouteType, t11FcRoutePermanent, t11FcRouteStorageType, t11FcRouteRowStatus } STATUS current DESCRIPTION "A collection of objects for displaying and configuring routes." ::= { t11FcRouteGroups 1 } END 7. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies 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 obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice Expires July 2005 [Page 14] Internet Draft FC Routing Information MIB January 2005 this standard. Please address the information to the IETF Executive Director. 8. Acknowledgements This document is currently a work item of the INCITS Task Group T11.5. 9. 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. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 58, RFC 3411, December 2002. [FC-SW-4] "Fibre Channel - Switch Fabric - 3 (FC-SW-4)", ANSI NCITS xxx-xxxx, T11/Project 1674-D/Rev 7.1, October 2004. [FC-MGMT] K. McCloghrie, "Fibre Channel Management MIB", Internet-Draft (draft-ietf-ips-fcmgmt-mib-nn.txt), work-in-progress. [FC-FAM-MIB] DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf- imss-fc-fam-mib-nn.txt), work-in-progress. [FC-FSM-MIB] DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "MIB for Expires July 2005 [Page 15] Internet Draft FC Routing Information MIB January 2005 Fibre-Channel's Fabric Shortest Path First Protocol", Internet- Draft (draft-kzm-imss-fc-fspf-mib-nn.txt), work-in-progress. 10. Informative References [RFC2837] Teow, K., "Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard", RFC 2837, May 2000. [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. 11. IANA Considerations None. 12. Security Considerations There are several management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These objects and their sensitivity/vulnerability are: t11FcRouteDomainId, t11FcRouteMetric, t11FcRouteType, t11FcRoutePermanent, t11FcRouteRowStatus -- configure new routes and/or modify existing routes. Such objects may be considered sensitive or vulnerable in some network environments. For example, the ability to change network topology or network speed may afford an attacker the ability to obtain better performance at the expense of other network users. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly Expires July 2005 [Page 16] Internet Draft FC Routing Information MIB January 2005 to even encrypt the values of these objects when sending them over the network via SNMP. The objects and their sensitivity/vulnerability are: the write-able objects listed above plus one other: t11FcRouteLastChangeTime -- the time of the last routing table change. 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 this MIB module. It is RECOMMENDED that implementors consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), 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. Expires July 2005 [Page 17] Internet Draft FC Routing Information MIB January 2005 13. Authors' Addresses Claudio DeSanti Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Phone: +1 408 853-9172 EMail: cds@cisco.com Srini Kode Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Phone: +1 408 853-9164 EMail: skode@cisco.com Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Phone: +1 408-526-5260 Email: kzm@cisco.com Silvano Gai Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Phone: +1 408-526-7269 Email: sgai@cisco.com 14. 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." Expires July 2005 [Page 18] Internet Draft FC Routing Information MIB January 2005 15. Disclaimer of validity 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. Copies of IPR disclosures made to the IETF Secretariat and any 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 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Expires July 2005 [Page 19]