idnits 2.17.1 draft-ietf-ips-ifcp-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 21 longer pages, the longest (page 3) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2002) is 7857 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC1213' is mentioned on line 189, but not defined == Unused Reference: 'IFCP001' is defined on line 1067, but no explicit reference was found in the text == Unused Reference: 'ISNS001' is defined on line 1072, but no explicit reference was found in the text == Unused Reference: 'RFC2737' is defined on line 1085, but no explicit reference was found in the text == Unused Reference: 'RFC2851' is defined on line 1088, but no explicit reference was found in the text == Unused Reference: 'T11FCGS3' is defined on line 1159, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IFCP001' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISNS001' -- Possible downref: Non-RFC (?) normative reference: ref. 'FCMGT01' ** Obsolete normative reference: RFC 2737 (Obsoleted by RFC 4133) ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 16 errors (**), 0 flaws (~~), 10 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Kevin Gibbons 3 Internet Draft Charles Monia 4 Josh Tseng 5 Expires: April 2003 Nishan Systems 7 Franco Travostino 8 Nortel 10 October 2002 12 Definitions of Managed Objects 13 For iFCP 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance 18 with all provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as "work 29 in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright Notice 39 Copyright (C) The Internet Society (2002). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base 44 (MIB) for use with network management protocols in the Internet 45 community. In particular, it defines a basic set of managed 46 objects for SNMP-based monitoring and management of the Internet 47 Fibre Channel Protocol (iFCP). 49 This memo specifies a MIB module in a manner that is compliant to 50 the SMIv2. The set of objects is consistent with the SNMP 51 framework and existing SNMP standards. 53 This memo is a product of the IP Storage (IPS) working group 55 Gibbons Expires April 2003 1 56 within the Internet Engineering Task Force. Comments are 57 solicited and should be addressed to the working group's mailing 58 list at ips@ece.cmu.edu and/or the authors. 60 Table of Contents 62 Status of this Memo...............................................1 63 Copyright Notice..................................................1 64 Abstract..........................................................1 65 Table of Contents.................................................2 66 1. Introduction..................................................3 67 2. The SNMP Management Framework.................................3 68 3. Overview......................................................4 69 4. Technical Description.........................................4 70 5. MIB Definition................................................5 71 6. Security Considerations......................................20 72 7. Normative References.........................................20 73 8. Non-Normative References.....................................22 74 9. Authors� Addresses...........................................22 75 10. Full Copyright Statement.....................................22 77 Gibbons Expires April 2003 2 78 1. Introduction 80 The iFCP protocol provides Fibre Channel fabric functionality on an 81 IP network in which TCP/IP switching and routing elements replace 82 Fibre Channel components. This draft provides a mechanism to 83 monitor and control iFCP Gateway instances, and their associated 84 sessions, using SNMP. 86 2. The SNMP Management Framework 88 The SNMP Management Framework presently consists of five major 89 components: 91 o An overall architecture, described in RFC 2571 [RFC2571]. 93 o Mechanisms for describing and naming objects and events for 94 the purpose of management. The first version of this 95 Structure of Management Information (SMI) is called SMIv1 96 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 97 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 98 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 99 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 101 o Message protocols for transferring management information. 102 The first version of the SNMP message protocol is called 103 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 104 second version of the SNMP message protocol, which is not an 105 Internet standards track protocol, is called SNMPv2c and 106 described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The 107 third version of the message protocol is called SNMPv3 and 108 described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 109 2574 [RFC2574]. 111 o Protocol operations for accessing management information. 112 The first set of protocol operations and associated PDU 113 formats is described in STD 15, RFC 1157 [RFC1157]. A 114 second set of protocol operations and associated PDU formats 115 is described in RFC 1905 [RFC1905]. 117 o A set of fundamental applications described in RFC 2573 118 [RFC2573] and the view-based access control mechanism 119 described in RFC 2575 [RFC2575]. 121 A more detailed introduction to the current SNMP Management 122 Framework can be found in RFC 2570 [RFC2570]. 124 Managed objects are accessed via a virtual information store, 125 termed the Management Information Base or MIB. Objects in the 126 MIB are defined using the mechanisms defined in the SMI. 128 This memo specifies a MIB module that is compliant to the SMIv2. 129 A MIB conforming to the SMIv1 can be produced through the 130 appropriate translations. The resulting translated MIB must be 132 Gibbons Expires April 2003 3 133 semantically equivalent, except where objects or events are 134 omitted because no translation is possible (use of Counter64). 135 Some machine readable information in SMIv2 will be converted into 136 textual descriptions in SMIv1 during the translation process. 137 However, this loss of machine readable information is not 138 considered to change the semantics of the MIB. 140 3. Overview 142 The iFCP protocol can be used by FC to IP based storage gateways 143 for FCP storage interconnects. Figure 1 provides an example 144 interconnect between iFCP gateways. 146 Gateway Region Gateway Region 147 +--------+ +--------+ +--------+ +--------+ 148 | FC | | FC | | FC | | FC | 149 | Device | | Device | | Device | | Device | Fibre 150 |........| |........| FC |........| |........| Channel 151 | N_PORT | | N_PORT |<.........>| N_PORT | | N_PORT | Device 152 +---+----+ +---+----+ Traffic +----+---+ +----+---+ Domain 153 | | | | ^ 154 +---+----+ +---+----+ +----+---+ +----+---+ | 155 | F_PORT | | F_PORT | | F_PORT | | F_PORT | | 156 =+========+==+========+===========+========+==+========+========== 157 | iFCP Layer |<--------->| iFCP Layer | | 158 |....................| ^ |....................| | 159 | iFCP Portal | | | iFCP Portal | v 160 +--------+-----------+ | +----------+---------+ IP 161 iFCP|Gateway Control iFCP|Gateway Network 162 | Data | 163 | | 164 | | 165 |<------Encapsulated Frames------->| 166 | +------------------+ | 167 | | | | 168 +------+ IP Network +--------+ 169 | | 170 +------------------+ 172 The iFCP MIB is designed to allow SNMP to be used to monitor and 173 manage local iFCP gateway instances, including the configuration of 174 iFCP sessions between gateways. 176 4. Technical Description 178 The MIB is divided into sections for iFCP local gateway instance 179 management, iFCP session management, and iFCP session statistics. 181 The section for iFCP gateway management provides default settings 182 and information about each local instance. A single management 183 entity can monitor multiple local gateway instances. Each local 184 gateway is conceptually an independent gateway that has both Fibre 185 Channel and IP interfaces. Other standard MIBs, such as the Fibre 186 Management MIB [FCMGT01], the Interfaces Group MIB [RFC2863] and 188 Gibbons Expires April 2003 4 189 MIB II [RFC1213] can be used to manage non-iFCP specific gateway 190 parameters. The local gateway instance section provides iFCP 191 specific information as well as optional links to other standard 192 management MIBs. 194 The iFCP session management section provides information on iFCP 195 sessions that are using one of the local iFCP gateway instances. 196 This section allows the management of specific iFCP parameters. 198 The iFCP session statistics section provides statistical 199 information on the iFCP sessions that are using one of the local 200 iFCP gateways. These tables augment the session management table. 201 Additional statistical information for an iFCP gateway or session, 202 that is not iFCP specific, can be obtained using other standard 203 MIBs. The iFCP statistics are provided in both standard and low- 204 capacity (counter32) methods. 206 5. MIB Definition 208 IFCP-MGMT-MIB DEFINITIONS ::= BEGIN 209 -- 210 -- IETF iFCP Management Information Base (MIB) 211 -- 212 IMPORTS 213 MODULE-IDENTITY, 214 OBJECT-TYPE, 215 Counter32, 216 Counter64, 217 Integer32, 218 Unsigned32, 219 experimental 220 FROM SNMPv2-SMI 222 OBJECT-GROUP, 223 MODULE-COMPLIANCE 224 FROM SNMPv2-CONF 226 TEXTUAL-CONVENTION, 227 TruthValue 228 FROM SNMPv2-TC 230 -- From RFC 2571 231 SnmpAdminString 232 FROM SNMP-FRAMEWORK-MIB 234 -- From RFC 2851 235 InetAddressType, 236 InetAddress 237 FROM INET-ADDRESS-MIB 239 -- From IETF Fibre Channel Management MIB, RFC TBD 240 FcNameIdOrZero, 241 FcAddressId 242 FROM FC-MGMT-MIB 244 Gibbons Expires April 2003 5 245 ; 247 ifcpMgmtMIB MODULE-IDENTITY 248 LAST-UPDATED "0210080000Z" 249 ORGANIZATION "IETF IPS Working Group" 250 CONTACT-INFO " 251 Attn: Kevin Gibbons 252 Nishan Systems 253 3850 North First Street 254 San Jose, CA 95134 255 USA 256 Tel : +1 408 519-3700 257 email : kgibbons@nishansystems.com 259 Charles Monia 260 Nishan Systems 261 3850 North First Street 262 San Jose, CA 95134 263 USA 264 Tel : +1 408 519-3700 265 email : cmonia@nishansystems.com 267 Josh Tseng 268 Nishan Systems 269 3850 North First Street 270 San Jose, CA 95134 271 USA 272 Tel : +1 408 519-3700 273 email : jtseng@nishansystems.com 275 Franco Travostino 276 Nortel Networks 277 3 Federal Street 278 Billerica, MA 01821 279 USA 280 Tel : +1 978 288-7708 281 email : travos@nortelnetworks.com 282 " 284 DESCRIPTION "The MIB for internet Fibre Channel Protocol 285 (iFCP) management." 287 -- an IETF number has not yet been assigned 288 ::= {experimental 4371} 290 IfIndexType ::= TEXTUAL-CONVENTION 291 STATUS current 292 DESCRIPTION "Represents possible interface indexes that 293 can be used on the iFCP gateway. This can 294 be used as an index for the IF-MIB ifTable, 295 if supported by the system, or other 296 interface table, to obtain additional 297 information about the interface." 298 REFERENCE "RFC 2863, The Interfaces Group MIB (IF-MIB)" 300 Gibbons Expires April 2003 6 301 SYNTAX Integer32 (1..2147483647) 303 IfcpVersionType ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION "Represents the iFCP version supported." 306 SYNTAX INTEGER (0..255) 308 PortType ::= TEXTUAL-CONVENTION 309 STATUS current 310 DESCRIPTION "The value for a TCP Port being used for 311 an iFCP session. The canonical port for 312 iFCP is 3420." 313 REFERENCE "draft-ietf-ips-ifcp-13.txt" 314 SYNTAX INTEGER (0..65535) 316 IpTOVor0Type ::= TEXTUAL-CONVENTION 317 STATUS current 318 DESCRIPTION "The maximum propagation delay, in seconds, 319 for an encapsulated FC frame to traverse the 320 IP network. A value of 0 implies fibre 321 channel frame lifetime limits will not be 322 enforced." 323 REFERENCE "draft-ietf-ips-ifcp-13.txt" 324 SYNTAX INTEGER (0..3600) 326 LTIor0Type ::= TEXTUAL-CONVENTION 327 STATUS current 328 DESCRIPTION "The value for the Liveness Test Interval 329 (LTI) being used in an iFCP connection, in 330 seconds. A value of 0 implies no Liveness 331 Test Interval will be used." 332 REFERENCE "draft-ietf-ips-ifcp-13.txt" 333 SYNTAX INTEGER (0..65535) 335 IfcpSessionStateType ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION "The value for an iFCP session state." 338 SYNTAX INTEGER {down(0), openPending(1), open(2)} 340 IfcpAddressModeType ::= TEXTUAL-CONVENTION 341 STATUS current 342 DESCRIPTION "The values for iFCP Address Translation 343 Mode." 344 REFERENCE "draft-ietf-ips-ifcp-13.txt" 345 SYNTAX INTEGER {addressTransparent(0), 346 addressTranslation(1)} 348 -- 349 -- Internet Fibre Channel Protocol (iFCP) 350 -- 352 ifcpGatewayObj OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1} 353 ifcpGatewayConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2} 355 Gibbons Expires April 2003 7 356 -- 357 -- Local iFCP Gateway Instance Information ================== 358 -- 360 ifcpLclGatewayObjInfo OBJECT IDENTIFIER ::= {ifcpGatewayObj 1} 362 ifcpLclGtwyInstTable OBJECT-TYPE 363 SYNTAX SEQUENCE OF IfcpLclGtwyInstEntry 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "Information about all local iFCP Gateway instances that can be 368 monitored and controled. This table contains an entry for each 369 local iFCP Gateway instance that is being managed." 370 ::= {ifcpLclGatewayObjInfo 1} 372 ifcpLclGtwyInstEntry OBJECT-TYPE 373 SYNTAX IfcpLclGtwyInstEntry 374 MAX-ACCESS not-accessible 375 STATUS current 376 DESCRIPTION 377 "An entry in the local iFCP Gateway Instance table. 378 Parameters and settings for the gateway are found here." 379 INDEX { ifcpLclGtwyInstIndex } 380 ::= {ifcpLclGtwyInstTable 1} 382 IfcpLclGtwyInstEntry ::= SEQUENCE { 383 ifcpLclGtwyInstIndex Unsigned32, 384 ifcpLclGtwyInstPhyIndex Unsigned32, 385 ifcpLclGtwyInstVersionMin IfcpVersionType, 386 ifcpLclGtwyInstVersionMax IfcpVersionType, 387 ifcpLclGtwyInstAddrTransMode IfcpAddressModeType, 388 ifcpLclGtwyInstFcBrdcstSupport TruthValue, 389 ifcpLclGtwyInstDefaultIpTOV IpTOVor0Type, 390 ifcpLclGtwyInstDefaultLTInterval LTIor0Type, 391 ifcpLclGtwyInstDescr SnmpAdminString, 392 ifcpLclGtwyInstNumActiveSessions Unsigned32 393 } 395 ifcpLclGtwyInstIndex OBJECT-TYPE 396 SYNTAX Unsigned32 (1..2147483647) 397 MAX-ACCESS not-accessible 398 STATUS current 399 DESCRIPTION 400 "An arbitrary integer value to uniquely identify this iFCP 401 Gateway from other local Gateway instances." 402 ::= {ifcpLclGtwyInstEntry 1} 404 ifcpLclGtwyInstPhyIndex OBJECT-TYPE 405 SYNTAX Unsigned32 (0..2147483647) 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "An index indicating the location of this local gateway within 411 Gibbons Expires April 2003 8 412 a larger entity, if one exists. If supported, this is the 413 entPhysicalIndex from the Entity MIB (Version 2), for this iFCP 414 Gateway. If not supported it is either an index into a chassis 415 MIB, as supported by the system, or 0." 416 REFERENCE "RFC 2737, Entity MIB (Version 2)" 417 ::= {ifcpLclGtwyInstEntry 2} 419 ifcpLclGtwyInstVersionMin OBJECT-TYPE 420 SYNTAX IfcpVersionType 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The minimum iFCP protocol version supported by the local iFCP 425 gateway instance." 426 REFERENCE "draft-ietf-ips-ifcp-13.txt" 427 ::= {ifcpLclGtwyInstEntry 3} 429 ifcpLclGtwyInstVersionMax OBJECT-TYPE 430 SYNTAX IfcpVersionType 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The maximum iFCP protocol version supported by the local iFCP 435 gateway instance." 436 REFERENCE "draft-ietf-ips-ifcp-13.txt" 437 ::= {ifcpLclGtwyInstEntry 4} 439 ifcpLclGtwyInstAddrTransMode OBJECT-TYPE 440 SYNTAX IfcpAddressModeType 441 MAX-ACCESS read-write 442 STATUS current 443 DESCRIPTION 444 "The local iFCP gateway operating mode. Changing this value may 445 cause existing sessions to be disrupted." 446 DEFVAL { addressTranslation } 447 ::= {ifcpLclGtwyInstEntry 5} 449 ifcpLclGtwyInstFcBrdcstSupport OBJECT-TYPE 450 SYNTAX TruthValue 451 MAX-ACCESS read-write 452 STATUS current 453 DESCRIPTION 454 "Whether the local iFCP gateway supports FC Broadcast. Changing 455 this value may cause existing sessions to be disrupted." 456 DEFVAL { false } 457 ::= {ifcpLclGtwyInstEntry 6} 459 ifcpLclGtwyInstDefaultIpTOV OBJECT-TYPE 460 SYNTAX IpTOVor0Type 461 MAX-ACCESS read-write 462 STATUS current 463 DESCRIPTION 464 "The default IP_TOV used for iFCP sessions at this gateway. 465 This is the default maximum propagation delay that will be 467 Gibbons Expires April 2003 9 468 used for an iFCP session. The value can be changed on a 469 per-session basis. The valid range is 0 - 3600 seconds. 470 A value of 0 implies that fibre channel frame lifetime limits 471 will not be enforced." 472 DEFVAL { 6 } 473 ::= {ifcpLclGtwyInstEntry 7} 475 ifcpLclGtwyInstDefaultLTInterval OBJECT-TYPE 476 SYNTAX LTIor0Type 477 MAX-ACCESS read-write 478 STATUS current 479 DESCRIPTION 480 "The default Liveness Test Interval (LTI), in seconds, used 481 for iFCP sessions at this gateway. This is the default 482 value for an iFCP session and can be changed on a 483 per-session basis. The valid range is 0 - 65535 seconds. 484 A value of 0 implies no Liveness Test Interval will be 485 performed on a session." 486 DEFVAL { 10 } 487 ::= {ifcpLclGtwyInstEntry 8} 489 ifcpLclGtwyInstDescr OBJECT-TYPE 490 SYNTAX SnmpAdminString (SIZE (0..64)) 491 MAX-ACCESS read-write 492 STATUS current 493 DESCRIPTION 494 "A user entered description for this iFCP Gateway." 495 DEFVAL { "" } 496 ::= {ifcpLclGtwyInstEntry 9} 498 ifcpLclGtwyInstNumActiveSessions OBJECT-TYPE 499 SYNTAX Unsigned32 (0..4294967295) 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The current total number of iFCP sessions in the open or 504 open-pending state." 505 ::= {ifcpLclGtwyInstEntry 10} 507 -- 508 -- iFCP N Port Session Information ============================ 509 -- 511 ifcpNportSessionInfo OBJECT IDENTIFIER ::= {ifcpGatewayObj 2} 513 ifcpSessionAttributesTable OBJECT-TYPE 514 SYNTAX SEQUENCE OF 515 IfcpSessionAttributesEntry 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "An iFCP session consists of the pair of N_PORTs comprising 520 the session endpoints joined by a single TCP/IP connection. 521 This table provides information on each iFCP session currently 523 Gibbons Expires April 2003 10 524 using a local iFCP Gateway instance. iFCP sessions are created 525 and removed by the iFCP Gateway instances, which are reflected 526 in this table." 527 ::= {ifcpNportSessionInfo 1} 529 ifcpSessionAttributesEntry OBJECT-TYPE 530 SYNTAX IfcpSessionAttributesEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "An entry in the session table." 535 INDEX { ifcpLclGtwyInstIndex, ifcpSessionIndex } 536 ::= {ifcpSessionAttributesTable 1} 538 IfcpSessionAttributesEntry ::= SEQUENCE { 539 ifcpSessionIndex Integer32, 540 ifcpSessionLclPrtlIfIndex IfIndexType, 541 ifcpSessionLclPrtlAddrType InetAddressType, 542 ifcpSessionLclPrtlAddr InetAddress, 543 ifcpSessionLclPrtlTcpPort PortType, 544 ifcpSessionLclNpWwun FcNameIdOrZero, 545 ifcpSessionLclNpFcid FcAddressId, 546 ifcpSessionRmtNpWwun FcNameIdOrZero, 547 ifcpSessionRmtPrtlIfAddrType InetAddressType, 548 ifcpSessionRmtPrtlIfAddr InetAddress, 549 ifcpSessionRmtPrtlTcpPort PortType, 550 ifcpSessionRmtNpFcid FcAddressId, 551 ifcpSessionRmtNpFcidAlias FcAddressId, 552 ifcpSessionIpTOV IpTOVor0Type, 553 ifcpSessionLclLTIntvl LTIor0Type, 554 ifcpSessionRmtLTIntvl LTIor0Type, 555 ifcpSessionBound TruthValue 556 } 558 ifcpSessionIndex OBJECT-TYPE 559 SYNTAX Integer32 (1..2147483647) 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "The iFCP session index is a unique value used as an index 564 to the table, along with a specific local iFCP Gateway 565 instance. This index is used because the local N Port and 566 remote N Port information would create an complex index that 567 would be difficult to implement." 568 ::= {ifcpSessionAttributesEntry 1} 570 ifcpSessionLclPrtlIfIndex OBJECT-TYPE 571 SYNTAX IfIndexType 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "This is the local interface in the ifTable being used as the 576 local portal in this session, as described in the IF-MIB. 577 This can be used as an index for the ifTable to obtain 579 Gibbons Expires April 2003 11 580 additional information about the interface." 581 REFERENCE "RFC 2863, The Interfaces Group MIB (IF-MIB)" 582 ::= {ifcpSessionAttributesEntry 2} 584 ifcpSessionLclPrtlAddrType OBJECT-TYPE 585 SYNTAX InetAddressType 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The type of address in ifcpSessionLclIfAddr." 590 ::= {ifcpSessionAttributesEntry 3} 592 ifcpSessionLclPrtlAddr OBJECT-TYPE 593 SYNTAX InetAddress 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "This is the external IP address of the interface being used 598 for the iFCP local portal in this session." 599 ::= {ifcpSessionAttributesEntry 4} 601 ifcpSessionLclPrtlTcpPort OBJECT-TYPE 602 SYNTAX PortType 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "This is the TCP port number that is being used for the iFCP 607 local portal in this session. This is normally an ephemeral 608 port number selected by the gateway." 609 ::= {ifcpSessionAttributesEntry 5} 611 ifcpSessionLclNpWwun OBJECT-TYPE 612 SYNTAX FcNameIdOrZero 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "World Wide Unique Name of the local N Port. For an unbound 617 session this variable will be empty." 618 DEFVAL { "" } 619 ::= {ifcpSessionAttributesEntry 6} 621 ifcpSessionLclNpFcid OBJECT-TYPE 622 SYNTAX FcAddressId 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "Fibre Channel Identifier of the local N Port. For an unbound 627 session this variable will be empty" 628 ::= {ifcpSessionAttributesEntry 7} 630 ifcpSessionRmtNpWwun OBJECT-TYPE 631 SYNTAX FcNameIdOrZero 632 MAX-ACCESS read-only 633 STATUS current 635 Gibbons Expires April 2003 12 636 DESCRIPTION 637 "World Wide Unique Name of the remote N Port. For an unbound 638 session this variable will be empty." 639 DEFVAL { "" } 640 ::= {ifcpSessionAttributesEntry 8} 642 ifcpSessionRmtPrtlIfAddrType OBJECT-TYPE 643 SYNTAX InetAddressType 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "The type of address in ifcpSessionRmtPrtlIfAddr." 648 ::= {ifcpSessionAttributesEntry 9} 650 ifcpSessionRmtPrtlIfAddr OBJECT-TYPE 651 SYNTAX InetAddress 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "This is the remote gateway IP address being used for the 656 portal on the remote iFCP gateway." 657 ::= {ifcpSessionAttributesEntry 10} 659 ifcpSessionRmtPrtlTcpPort OBJECT-TYPE 660 SYNTAX PortType 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "This is the TCP port number being used for the portal on the 665 remote iFCP gateway. Generally, this will be the iFCP 666 canonical port." 667 DEFVAL { 3420 } 668 ::= {ifcpSessionAttributesEntry 11} 670 ifcpSessionRmtNpFcid OBJECT-TYPE 671 SYNTAX FcAddressId 672 MAX-ACCESS read-only 673 STATUS current 674 DESCRIPTION 675 "Fibre Channel Identifier of the remote N Port. For an unbound 676 session this variable will be empty." 677 ::= {ifcpSessionAttributesEntry 12} 679 ifcpSessionRmtNpFcidAlias OBJECT-TYPE 680 SYNTAX FcAddressId 681 MAX-ACCESS read-only 682 STATUS current 683 DESCRIPTION 684 "Fibre Channel Identifier Alias assigned by the local gateway 685 for the remote N Port. For an unbound session this variable 686 will be empty." 687 ::= {ifcpSessionAttributesEntry 13} 689 ifcpSessionIpTOV OBJECT-TYPE 691 Gibbons Expires April 2003 13 692 SYNTAX IpTOVor0Type 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 "The IP_TOV being used for this iFCP session. This is the 697 maximum propagation delay that will be used for the iFCP 698 session. The value can be changed on a per-session basis 699 and initially defaults to ifcpLclGtwyInstDefaultIpTOV for 700 the local gateway instance. The valid range is 0 - 3600 701 seconds. A value of 0 implies fibre channel frame lifetime 702 limits will not be enforced." 703 ::= {ifcpSessionAttributesEntry 14} 705 ifcpSessionLclLTIntvl OBJECT-TYPE 706 SYNTAX LTIor0Type 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The Liveness Test Interval (LTI) used for this iFCP session. 711 The value can be changed on a per-session basis and initially 712 defaults to ifcpLclGtwyInstDefaultLTInterval for the local 713 gateway instance. The valid range is 0 - 65535 seconds. 714 A value of 0 implies that the gateway will not originate 715 Liveness Test messages for the session." 716 ::= {ifcpSessionAttributesEntry 15} 718 ifcpSessionRmtLTIntvl OBJECT-TYPE 719 SYNTAX LTIor0Type 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The Liveness Test Interval (LTI) as requested by the remote 724 gateway instance to use for this iFCP session. This value may 725 change over the life of the session. The valid range is 0 - 726 65535 seconds. A value of 0 implies that the remote gateway 727 has not been requested to originate Liveness Test messages for 728 the session." 729 ::= {ifcpSessionAttributesEntry 16} 731 ifcpSessionBound OBJECT-TYPE 732 SYNTAX TruthValue 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "This value indicates whether this session is bound to a 737 specific local and remote N Port. Sessions by default are 738 unbound and ready for future assignment to a local and remote 739 N Port." 740 ::= {ifcpSessionAttributesEntry 17} 742 -- 743 -- Local iFCP Gateway Instance Session Statistics ============= 744 -- 746 Gibbons Expires April 2003 14 747 ifcpSessionStatsTable OBJECT-TYPE 748 SYNTAX SEQUENCE OF 749 IfcpSessionStatsEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "This table provides statistics on an iFCP session." 754 ::= {ifcpNportSessionInfo 2} 756 ifcpSessionStatsEntry OBJECT-TYPE 757 SYNTAX IfcpSessionStatsEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "iFCP specific statistics per session." 762 AUGMENTS {ifcpSessionAttributesEntry} 763 ::= {ifcpSessionStatsTable 1} 765 IfcpSessionStatsEntry ::= SEQUENCE { 766 ifcpSessionState IfcpSessionStateType, 767 ifcpSessionDuration Unsigned32, 768 ifcpSessionTxFrames Counter64, 769 ifcpSessionRxFrames Counter64, 770 ifcpSessionStaleFrames Counter64, 771 ifcpSessionHeaderCRCErrors Counter64, 772 ifcpSessionFcPayloadCRCErrors Counter64, 773 ifcpSessionOtherErrors Counter64 774 } 776 ifcpSessionState OBJECT-TYPE 777 SYNTAX IfcpSessionStateType 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The current session operating state." 782 ::= {ifcpSessionStatsEntry 1} 784 ifcpSessionDuration OBJECT-TYPE 785 SYNTAX Unsigned32 (0..4294967295) 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "This indicates, in seconds, how long the iFCP session has 790 been in an open or open-pending state. When a session is 791 down the value is reset to 0." 792 ::= {ifcpSessionStatsEntry 2} 794 ifcpSessionTxFrames OBJECT-TYPE 795 SYNTAX Counter64 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The total number of iFCP frames transmitted since the 800 connection was first established." 802 Gibbons Expires April 2003 15 803 ::= {ifcpSessionStatsEntry 3} 805 ifcpSessionRxFrames OBJECT-TYPE 806 SYNTAX Counter64 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The total number of iFCP frames received since the 811 connection was first established." 812 ::= {ifcpSessionStatsEntry 4} 814 ifcpSessionStaleFrames OBJECT-TYPE 815 SYNTAX Counter64 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "The total number of received iFCP frames that were stale and 820 discarded since the connection was first established." 821 ::= {ifcpSessionStatsEntry 5} 823 ifcpSessionHeaderCRCErrors OBJECT-TYPE 824 SYNTAX Counter64 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The total number of CRC errors that occurred in the frame 829 header, detected since the connection was first established. 830 Usually, a single Header CRC error is sufficient to 831 terminate an iFCP session." 832 ::= {ifcpSessionStatsEntry 6} 834 ifcpSessionFcPayloadCRCErrors OBJECT-TYPE 835 SYNTAX Counter64 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The total number of CRC errors that occurred in the Fibre 840 Channel frame payload detected since the connection was first 841 established." 842 ::= {ifcpSessionStatsEntry 7} 844 ifcpSessionOtherErrors OBJECT-TYPE 845 SYNTAX Counter64 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "The total number of errors, other then errors explicitly 850 measured, detected since the connection was first established." 851 ::= {ifcpSessionStatsEntry 8} 853 -- 854 -- Low Capacity Statistics 855 -- 857 Gibbons Expires April 2003 16 858 ifcpSessionLcStatsTable OBJECT-TYPE 859 SYNTAX SEQUENCE OF 860 IfcpSessionLcStatsEntry 861 MAX-ACCESS not-accessible 862 STATUS current 863 DESCRIPTION 864 "This table provides low capacity statistics on an iFCP session. 865 This is provided for backward compatibility with systems that 866 do not support Counter64." 867 ::= {ifcpNportSessionInfo 3} 869 ifcpSessionLcStatsEntry OBJECT-TYPE 870 SYNTAX IfcpSessionLcStatsEntry 871 MAX-ACCESS not-accessible 872 STATUS current 873 DESCRIPTION 874 "iFCP specific statistics per session." 875 AUGMENTS {ifcpSessionAttributesEntry} 876 ::= {ifcpSessionLcStatsTable 1} 878 IfcpSessionLcStatsEntry ::= SEQUENCE { 879 ifcpSessionLcTxFrames Counter32, 880 ifcpSessionLcRxFrames Counter32, 881 ifcpSessionLcStaleFrames Counter32, 882 ifcpSessionLcHeaderCRCErrors Counter32, 883 ifcpSessionLcFcPayloadCRCErrors Counter32, 884 ifcpSessionLcOtherErrors Counter32 885 } 887 ifcpSessionLcTxFrames OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "The total number of iFCP frames transmitted since the 893 connection was first established." 894 ::= {ifcpSessionLcStatsEntry 1} 896 ifcpSessionLcRxFrames OBJECT-TYPE 897 SYNTAX Counter32 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "The total number of iFCP frames received since the 902 connection was first established." 903 ::= {ifcpSessionLcStatsEntry 2} 905 ifcpSessionLcStaleFrames OBJECT-TYPE 906 SYNTAX Counter32 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "The total number of received iFCP frames that were stale and 911 discarded since the connection was first established." 913 Gibbons Expires April 2003 17 914 ::= {ifcpSessionLcStatsEntry 3} 916 ifcpSessionLcHeaderCRCErrors OBJECT-TYPE 917 SYNTAX Counter32 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The total number of CRC errors that occurred in the frame 922 header, detected since the connection was first established. 923 Usually, a single Header CRC error is sufficient to 924 terminate an iFCP session." 925 ::= {ifcpSessionLcStatsEntry 4} 927 ifcpSessionLcFcPayloadCRCErrors OBJECT-TYPE 928 SYNTAX Counter32 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The total number of CRC errors that occurred in the Fibre 933 Channel frame payload detected since the connection was first 934 established." 935 ::= {ifcpSessionLcStatsEntry 5} 937 ifcpSessionLcOtherErrors OBJECT-TYPE 938 SYNTAX Counter32 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The total number of errors, other then errors explicitly 943 measured, detected since the connection was first established." 944 ::= {ifcpSessionLcStatsEntry 6} 946 --========================================================== 948 ifcpGroups OBJECT IDENTIFIER ::= {ifcpGatewayConformance 1} 950 ifcpLclGatewayGroup OBJECT-GROUP 951 OBJECTS { 952 ifcpLclGtwyInstPhyIndex, 953 ifcpLclGtwyInstVersionMin, 954 ifcpLclGtwyInstVersionMax, 955 ifcpLclGtwyInstAddrTransMode, 956 ifcpLclGtwyInstFcBrdcstSupport, 957 ifcpLclGtwyInstDefaultIpTOV, 958 ifcpLclGtwyInstDefaultLTInterval, 959 ifcpLclGtwyInstDescr, 960 ifcpLclGtwyInstNumActiveSessions 961 } 962 STATUS current 963 DESCRIPTION 964 "iFCP local device info group" 965 ::= {ifcpGroups 1} 967 ifcpLclGatewaySessionGroup OBJECT-GROUP 969 Gibbons Expires April 2003 18 970 OBJECTS { 971 ifcpSessionLclPrtlIfIndex, 972 ifcpSessionLclPrtlAddrType, 973 ifcpSessionLclPrtlAddr, 974 ifcpSessionLclPrtlTcpPort, 975 ifcpSessionLclNpWwun, 976 ifcpSessionLclNpFcid, 977 ifcpSessionRmtNpWwun, 978 ifcpSessionRmtPrtlIfAddrType, 979 ifcpSessionRmtPrtlIfAddr, 980 ifcpSessionRmtPrtlTcpPort, 981 ifcpSessionRmtNpFcid, 982 ifcpSessionRmtNpFcidAlias, 983 ifcpSessionIpTOV, 984 ifcpSessionLclLTIntvl, 985 ifcpSessionRmtLTIntvl, 986 ifcpSessionBound 987 } 988 STATUS current 989 DESCRIPTION 990 "iFCP Session group" 991 ::= {ifcpGroups 4} 993 ifcpLclGatewaySessionStatsGroup OBJECT-GROUP 994 OBJECTS { 995 ifcpSessionState, 996 ifcpSessionDuration, 997 ifcpSessionTxFrames, 998 ifcpSessionRxFrames, 999 ifcpSessionStaleFrames, 1000 ifcpSessionHeaderCRCErrors, 1001 ifcpSessionFcPayloadCRCErrors, 1002 ifcpSessionOtherErrors 1003 } 1004 STATUS current 1005 DESCRIPTION 1006 "iFCP Session Statistics group" 1007 ::= {ifcpGroups 5} 1009 ifcpLclGatewaySessionLcStatsGroup OBJECT-GROUP 1010 OBJECTS { 1011 ifcpSessionLcTxFrames, 1012 ifcpSessionLcRxFrames, 1013 ifcpSessionLcStaleFrames, 1014 ifcpSessionLcHeaderCRCErrors, 1015 ifcpSessionLcFcPayloadCRCErrors, 1016 ifcpSessionLcOtherErrors 1017 } 1018 STATUS current 1019 DESCRIPTION 1020 "iFCP Session Low Capacity Statistics group" 1021 ::= {ifcpGroups 6} 1023 ifcpCompliances OBJECT IDENTIFIER ::= {ifcpGatewayConformance 2} 1025 Gibbons Expires April 2003 19 1026 ifcpGatewayComplianceV1 MODULE-COMPLIANCE 1027 STATUS current 1028 DESCRIPTION 1029 "Minimum implementation for iFCP MIB compliance." 1030 MODULE -- this module 1031 MANDATORY-GROUPS { 1032 ifcpLclGatewayGroup 1033 } 1034 ::= {ifcpCompliances 1} 1036 END 1038 6. Security Considerations 1040 There are a number of management objects defined in this MIB that 1041 have a MAX-ACCESS clause of read-write and/or read-create. Such 1042 objects may be considered sensitive or vulnerable in some network 1043 environments. The support for SET operations in a non-secure 1044 environment without proper protection can have a negative effect 1045 on network operations. 1047 SNMPv1 by itself is not a secure environment. Even if the 1048 network itself is secure (for example by using IPSec), even then, 1049 there is no control as to who on the secure network is allowed to 1050 access and GET/SET (read/change/create/delete) the objects in 1051 this MIB. 1053 It is recommended that the implementers consider the security 1054 features as provided by the SNMPv3 framework. Specifically, the 1055 use of the User-based Security Model RFC 2574 [RFC2574] and the 1056 View-based Access Control Model RFC 2575 [RFC2575] is 1057 recommended. 1059 It is then a customer/user responsibility to ensure that the SNMP 1060 entity giving access to an instance of this MIB, is properly 1061 configured to give access to the objects only to those principals 1062 (users) that have legitimate rights to indeed GET or SET 1063 (change/create/delete) them. 1065 7. Normative References 1067 [IFCP001] Charles Monia, Rod Mullendore, Franco Travostino, 1068 Wayland Jeong, Mark Edwards, "iFCP - A Protocol for 1069 Internet Fibre Channel Storage Networking", , Expires February 2003 1072 [ISNS001] Josh Tseng, Kevin Gibbons, Franco Travostino, Curt Du 1073 Laney, Joe Souza "iSNS Internet Storage Name Service", 1074 , Expires March 2003 1076 [FCMGT01] Keith McCloghrie, "Fibre Channel Management MIB", 1077 , Expires December 1078 2002 1080 Gibbons Expires April 2003 20 1082 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group 1083 MIB (IF-MIB)", RFC 2863, June 2000. 1085 [RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)", 1086 RFC 2737, December 1999. 1088 [RFC2851] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder 1089 "Textual Conventions for Internet Network Addresses", 1090 RFC 2851, June 2000. 1092 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1093 Architecture for Describing SNMP Management Frameworks", 1094 RFC 2571, April 1999. 1096 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1097 Identification of Management Information for TCP/IP- 1098 based Internets", STD 16, RFC 1155, May 1990. 1100 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1101 STD 16, RFC 1212, March 1991. 1103 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 1104 the SNMP", RFC 1215, March 1991. 1106 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1107 J., Rose, M., and S. Waldbusser, "Structure of 1108 Management Information Version 2 (SMIv2)", STD 58, RFC 1109 2578, April 1999. 1111 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1112 J., Rose, M., and S. Waldbusser, "Textual Conventions 1113 for SMIv2", STD 58, RFC 2579, April 1999. 1115 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1116 J., Rose, M., and S. Waldbusser, "Conformance Statements 1117 for SMIv2", STD 58, RFC 2580, April 1999. 1119 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1120 "Simple Network Management Protocol", STD 15, RFC 1157, 1121 May 1990. 1123 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1124 "Introduction to Community-based SNMPv2", RFC 1901, 1125 January 1996. 1127 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1128 "Transport Mappings for Version 2 of the Simple Network 1129 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1131 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1132 "Message Processing and Dispatching for the Simple 1133 Network Management Protocol (SNMP)", RFC 2572, April 1134 1999. 1136 Gibbons Expires April 2003 21 1138 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 1139 Model (USM) for version 3 of the Simple Network 1140 Management Protocol (SNMPv3)", RFC 2574, April 1999. 1142 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1143 "Protocol Operations for Version 2 of the Simple Network 1144 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1146 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1147 Applications", RFC 2573, April 1999. 1149 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1150 Access Control Model (VACM) for the Simple Network 1151 Management Protocol (SNMP)", RFC 2575, April 1999. 1153 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1154 "Introduction to Version 3 of the Internet-standard 1155 Network Management Framework", RFC 2570, April 1999. 1157 8. Non-Normative References 1159 [T11FCGS3] Fibre Channel - Generic Services 3, NCITS 348-2000. 1161 9. Authors� Addresses 1163 Kevin Gibbons 1164 E-mail: kgibbons@NishanSystems.com, 1165 Charles Monia 1166 E-mail: cmonia@NishanSystems.com, 1167 Josh Tseng 1168 E-mail: jtseng@NishanSystems.com, 1169 Postal: Nishan Systems 1170 3850 North First Street 1171 San Jose, CA 95134-1702 1172 USA 1174 Tel: (408) 519-3700 1175 Fax: (408) 519-3705 1177 Franco Travostino 1178 Nortel Networks 1179 3 Federal Street 1180 Billerica, MA 01821 1181 USA 1183 Tel: (978) 288-7708 1185 E-mail: travos@nortelnetworks.com 1187 10. Full Copyright Statement 1189 "Copyright (C) The Internet Society 2002. All Rights Reserved. 1191 Gibbons Expires April 2003 22 1192 This document and translations of it may be copied and furnished 1193 to others, and derivative works that comment on or otherwise 1194 explain it or assist in its implementation may be prepared, 1195 copied, published and distributed, in whole or in part, without 1196 restriction of any kind, provided that the above copyright notice 1197 and this paragraph are included on all such copies and derivative 1198 works. However, this document itself may not be modified in any 1199 way, such as by removing the copyright notice or references to 1200 the Internet Society or other Internet organizations, except as 1201 needed for the purpose of developing Internet standards in which 1202 case the procedures for copyrights defined in the Internet 1203 Standards process must be followed, or as required to translate 1204 it into languages other than English. 1206 The limited permissions granted above are perpetual and will not 1207 be revoked by the Internet Society or its successors or assigns. 1209 This document and the information contained herein is provided on 1210 An "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1211 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1212 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1213 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1214 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1215 PURPOSE." 1217 Gibbons Expires April 2003 23