draft-ietf-storm-ifcpmib-07.txt   rfc6173.txt 
INTERNET-DRAFT Prakash Venkatesen, Editor
STORM Working Group HCL Technologies
Intended status: Proposed Standard November 17, 2010
Expires: May 2011
Obsoletes: 4369
Definitions of Managed Objects for Internet Fibre Channel Protocol Internet Engineering Task Force (IETF) P. Venkatesen, Ed.
(iFCP) Request for Comments: 6173 HCL Technologies
draft-ietf-storm-ifcpmib-07.txt Obsoletes: 4369 March 2011
Category: Standards Track
ISSN: 2070-1721
Status of this Memo Definitions of Managed Objects
for the Internet Fibre Channel Protocol (iFCP)
This Internet-Draft is submitted to IETF in full conformance with the Abstract
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document defines Management Information Base (MIB) objects to
Task Force (IETF), its areas, and its working groups. Note that monitor and control the Internet Fibre Channel Protocol (iFCP)
other groups may also distribute working documents as Internet- gateway instances and their associated sessions, for use with network
Drafts. management protocols.
Internet-Drafts are draft documents valid for a maximum of six months This document obsoletes RFC 4369.
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 Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 17, 2011. This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6173.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Abstract
This document defines Management Information Base (MIB) objects to
monitor and control iFCP Gateway instances and their associated
sessions, for use with network management protocols.
This document obsoletes RFC4369.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework.....................2 1. The Internet-Standard Management Framework.....................2
2. Introduction...................................................3 2. Introduction...................................................3
3. Technical Description..........................................4 3. Technical Description..........................................4
4. Differences from RFC 4369......................................5 4. Differences from RFC 4369......................................4
5. MIB Definition.................................................5 5. MIB Definition.................................................5
6. Security Considerations.......................................27 6. Security Considerations.......................................28
7. IANA Considerations...........................................28 7. IANA Considerations...........................................29
8. References....................................................29 8. References....................................................29
8.1. Normative References.....................................29 8.1. Normative References.....................................29
8.2. Informative References...................................30 8.2. Informative References...................................30
9. Acknowledgments...............................................30 9. Acknowledgments...............................................31
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 3, line 15 skipping to change at page 3, line 5
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
The iFCP protocol (RFC 4172 [RFC4172]) provides Fibre Channel fabric iFCP (RFC 4172 [RFC4172]) provides Fibre Channel fabric functionality
functionality on an IP network in which TCP/IP switching and routing on an IP network in which TCP/IP switching and routing elements
elements replace Fibre Channel components. The iFCP protocol is used replace Fibre Channel components. iFCP is used between iFCP
between iFCP Gateways. This protocol can be used by FC-to-IP-based gateways. This protocol can be used by FC-to-IP-based storage
storage gateways for Fibre Channel Protocol (FCP) storage gateways for Fibre Channel Protocol (FCP) storage interconnects.
interconnects.
Figure 1 provides an example of an interconnect between iFCP Figure 1 provides an example of an interconnect between iFCP
gateways. gateways.
Gateway Region Gateway Region Gateway Region Gateway Region
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+ +--------+
| FC | | FC | | FC | | FC | | FC | | FC | | FC | | FC |
| Device | | Device | | Device | | Device | Fibre | Device | | Device | | Device | | Device | Fibre
|........| |........| FC |........| |........| Channel |........| |........| FC |........| |........| Channel
| N_PORT | | N_PORT |<.........>| N_PORT | | N_PORT | Device | N_PORT | | N_PORT |<.........>| N_PORT | | N_PORT | Device
skipping to change at page 3, line 52 skipping to change at page 3, line 41
iFCP|Gateway Control iFCP|Gateway Network iFCP|Gateway Control iFCP|Gateway Network
| Data | | Data |
| | | |
| | | |
|<------Encapsulated Frames------->| |<------Encapsulated Frames------->|
| +------------------+ | | +------------------+ |
| | | | | | | |
+------+ IP Network +--------+ +------+ IP Network +--------+
| | | |
+------------------+ +------------------+
Figure 1: Interconnect between iFCP Gateways Figure 1: Interconnect between iFCP Gateways
The iFCP MIB Module is designed to allow a network management The iFCP MIB module is designed to allow a network management
protocol such as SNMP to be used to monitor and manage local iFCP protocol such as SNMP to be used to monitor and manage local iFCP
gateway instances, including the configuration of iFCP sessions gateway instances, including the configuration of iFCP sessions
between gateways. between gateways.
3. Technical Description 3. Technical Description
The iFCP MIB Module is divided into sections for iFCP local gateway The iFCP MIB module is divided into sections for iFCP local gateway
instance management, iFCP session management, and iFCP session instance management, iFCP session management, and iFCP session
statistics. statistics.
The section for iFCP gateway management provides default settings and The section for iFCP gateway management provides default settings and
information about each local instance. A single management entity information about each local instance. A single management entity
can monitor multiple local gateway instances. Each local gateway is can monitor multiple local gateway instances. Each local gateway is
conceptually an independent gateway that has both Fibre Channel and conceptually an independent gateway that has both Fibre Channel and
IP interfaces. The default IP Time Out Value (IP_TOV) is IP interfaces. The default IP Time Out Value (IP_TOV) is
configurable for each gateway. Other standard MIBs, such as the configurable for each gateway. Other standard MIBs, such as the
Fibre Management MIB [RFC4044] or Interfaces Group MIB [RFC2863], can Fibre Management MIB [RFC4044] or Interfaces Group MIB [RFC2863], can
skipping to change at page 4, line 35 skipping to change at page 4, line 30
as optional links to other standard management MIBs. as optional links to other standard management MIBs.
The iFCP session management section provides information on iFCP The iFCP session management section provides information on iFCP
sessions that use one of the local iFCP gateway instances. This sessions that use one of the local iFCP gateway instances. This
section allows the management of specific iFCP parameters, including section allows the management of specific iFCP parameters, including
changing the IP_TOV from the default setting of the gateway. changing the IP_TOV from the default setting of the gateway.
The iFCP session statistics section provides statistical information The iFCP session statistics section provides statistical information
on the iFCP sessions that use one of the local iFCP gateways. These on the iFCP sessions that use one of the local iFCP gateways. These
tables augment the session management table. Additional statistical tables augment the session management table. Additional statistical
information for an iFCP gateway or session, that is not information for an iFCP gateway or session, that is not iFCP-
iFCP-specific, can be obtained using other standard MIBs. The iFCP specific, can be obtained using other standard MIBs. The iFCP
statistics are provided in both high-capacity (Counter64) and low- statistics are provided in both high-capacity (Counter64) and low-
capacity (Counter32) methods. capacity (Counter32) methods.
The following MIB module imports from SNMPv2-SMI [RFC2578], SNMPv2- The following MIB module imports from SNMPv2-SMI [RFC2578], SNMPv2-TC
TC [RFC2579], SNMPv2-CONF [RFC2580], HCNUM-TC [RFC2856], IF-MIB [RFC2579], SNMPv2-CONF [RFC2580], HCNUM-TC [RFC2856], IF-MIB
[RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001], [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001],
FC-MGMT-MIB [RFC4044], ENTITY-MIB (v3)[RFC4133] and RMON2-MIB FC-MGMT-MIB [RFC4044], ENTITY-MIB (v3) [RFC4133], and RMON2-MIB
[RFC4502]. [RFC4502].
4. Differences from RFC 4369 4. Differences from RFC 4369
As explained in [RFCyyyy], the iFCP address translation mode is
(Note to the RFC Editor: replace yyyy with the RFC number assigned to
draft-ietf-storm-ifcp-ipn133-updates & remove this note.)
deprecated. This document obsoletes the iFCP MIB module [RFC4369] As explained in [RFC6172], the iFCP address translation mode is
deprecated. This document obsoletes the iFCP MIB module [RFC4369]
for this change. for this change.
5. MIB Definition 5. MIB Definition
IFCP-MGMT-MIB DEFINITIONS ::= BEGIN IFCP-MGMT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Gauge32, Gauge32,
Integer32, Integer32,
Unsigned32, Unsigned32,
transmission transmission
skipping to change at page 6, line 22 skipping to change at page 6, line 16
FcNameIdOrZero, FcNameIdOrZero,
FcAddressIdOrZero FcAddressIdOrZero
FROM FC-MGMT-MIB FROM FC-MGMT-MIB
-- From RFC 4133 -- From RFC 4133
PhysicalIndexOrZero PhysicalIndexOrZero
FROM ENTITY-MIB FROM ENTITY-MIB
; ;
ifcpMgmtMIB MODULE-IDENTITY ifcpMgmtMIB MODULE-IDENTITY
LAST-UPDATED "201010250000Z" LAST-UPDATED "201103090000Z"
ORGANIZATION "IETF STORage Maintenance (STORM) Working Group" ORGANIZATION "IETF STORage Maintenance (STORM) Working Group"
CONTACT-INFO " CONTACT-INFO "
Working Group Email : storm@ietf.org Working Group Email : storm@ietf.org
Attn: Prakash Venkatesen Attn: Prakash Venkatesen
HCL Technologies HCL Technologies
Email: prakashvn@hcl.com" Email: prakashvn@hcl.com"
DESCRIPTION DESCRIPTION
"This module defines management information specific "This module defines management information specific
to internet Fibre Channel Protocol (iFCP) gateway to Internet Fibre Channel Protocol (iFCP) gateway
management. management.
Copyright (C) The IETF Trust (2010). This Copyright (c) 2011 IETF Trust and the persons
version of this MIB module is part of RFC xxxx; identified as authors of the code. All rights
see the RFC itself for full legal notices." reserved.
REVISION "201010250000Z" Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant
to, and subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info)."
REVISION "201103090000Z"
DESCRIPTION DESCRIPTION
"Second version of iFCP Management Module. The iFCP "Second version of iFCP Management Module. The iFCP
address translation mode is deprecated. address translation mode is deprecated.
This MIB module published as RFC xxxx." This MIB module published as RFC 6173."
REVISION "200601170000Z" REVISION "200601170000Z"
DESCRIPTION DESCRIPTION
"Initial version of iFCP Management Module. "Initial version of iFCP Management Module.
This MIB module published as RFC 4369." This MIB module published as RFC 4369."
::= { transmission 230 } ::= { transmission 230 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
IfcpIpTOVorZero ::= TEXTUAL-CONVENTION IfcpIpTOVorZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION "The maximum propagation delay, in seconds, DESCRIPTION "The maximum propagation delay, in seconds,
for an encapsulated FC frame to traverse the for an encapsulated FC frame to traverse the
IP network. A value of 0 implies fibre IP network. A value of 0 implies fibre
channel frame lifetime limits will not be channel frame lifetime limits will not be
enforced." enforced."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
SYNTAX Unsigned32 (0..3600) SYNTAX Unsigned32 (0..3600)
skipping to change at page 7, line 39 skipping to change at page 7, line 34
IfcpSessionStates ::= TEXTUAL-CONVENTION IfcpSessionStates ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The value for an iFCP session state." DESCRIPTION "The value for an iFCP session state."
SYNTAX INTEGER {down(1), openPending(2), open(3)} SYNTAX INTEGER {down(1), openPending(2), open(3)}
IfcpAddressMode ::= TEXTUAL-CONVENTION IfcpAddressMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The values for iFCP Address Translation DESCRIPTION "The values for iFCP Address Translation
Mode." Mode."
REFERENCE "RFC yyyy, Updates to the iFCP Protocol and REFERENCE "RFC 6172, Deprecation of iFCP Address
Internet Protocol Number 133 " Translation Mode"
SYNTAX INTEGER {addressTransparent(1), SYNTAX INTEGER {addressTransparent(1),
addressTranslation(2)} addressTranslation(2)}
-- --
-- Internet Fibre Channel Protocol (iFCP) -- Internet Fibre Channel Protocol (iFCP)
-- --
ifcpGatewayObjects OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1} ifcpGatewayObjects OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1}
ifcpGatewayConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2} ifcpGatewayConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2}
-- --
-- Local iFCP Gateway Instance Information ================== -- Local iFCP Gateway Instance Information ==================
-- --
ifcpLclGatewayInfo OBJECT IDENTIFIER ::= {ifcpGatewayObjects 1} ifcpLclGatewayInfo OBJECT IDENTIFIER ::= {ifcpGatewayObjects 1}
ifcpLclGtwyInstTable OBJECT-TYPE ifcpLclGtwyInstTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfcpLclGtwyInstEntry SYNTAX SEQUENCE OF IfcpLclGtwyInstEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about all local iFCP Gateway instances that can "Information about all local iFCP gateway instances that can
be monitored and controlled. This table contains an entry be monitored and controlled. This table contains an entry
for each local iFCP Gateway instance that is being managed." for each local iFCP gateway instance that is being managed."
::= {ifcpLclGatewayInfo 1} ::= {ifcpLclGatewayInfo 1}
ifcpLclGtwyInstEntry OBJECT-TYPE ifcpLclGtwyInstEntry OBJECT-TYPE
SYNTAX IfcpLclGtwyInstEntry SYNTAX IfcpLclGtwyInstEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the local iFCP Gateway Instance table. "An entry in the local iFCP gateway instance table.
Parameters and settings for the gateway are found here." Parameters and settings for the gateway are found here."
INDEX { ifcpLclGtwyInstIndex } INDEX { ifcpLclGtwyInstIndex }
::= {ifcpLclGtwyInstTable 1} ::= {ifcpLclGtwyInstTable 1}
IfcpLclGtwyInstEntry ::= SEQUENCE { IfcpLclGtwyInstEntry ::= SEQUENCE {
ifcpLclGtwyInstIndex Unsigned32, ifcpLclGtwyInstIndex Unsigned32,
ifcpLclGtwyInstPhyIndex PhysicalIndexOrZero, ifcpLclGtwyInstPhyIndex PhysicalIndexOrZero,
ifcpLclGtwyInstVersionMin Unsigned32, ifcpLclGtwyInstVersionMin Unsigned32,
ifcpLclGtwyInstVersionMax Unsigned32, ifcpLclGtwyInstVersionMax Unsigned32,
ifcpLclGtwyInstAddrTransMode IfcpAddressMode, ifcpLclGtwyInstAddrTransMode IfcpAddressMode,
skipping to change at page 8, line 52 skipping to change at page 8, line 46
ifcpLclGtwyInstNumActiveSessions Gauge32, ifcpLclGtwyInstNumActiveSessions Gauge32,
ifcpLclGtwyInstStorageType StorageType ifcpLclGtwyInstStorageType StorageType
} }
ifcpLclGtwyInstIndex OBJECT-TYPE ifcpLclGtwyInstIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer value to uniquely identify this iFCP "An arbitrary integer value to uniquely identify this iFCP
Gateway from other local Gateway instances." gateway from other local gateway instances."
::= {ifcpLclGtwyInstEntry 1} ::= {ifcpLclGtwyInstEntry 1}
ifcpLclGtwyInstPhyIndex OBJECT-TYPE ifcpLclGtwyInstPhyIndex OBJECT-TYPE
SYNTAX PhysicalIndexOrZero SYNTAX PhysicalIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index indicating the location of this local gateway within "An index indicating the location of this local gateway within
a larger entity, if one exists. If supported, this is the a larger entity, if one exists. If supported, this is the
entPhysicalIndex from the Entity MIB (Version 3), for this entPhysicalIndex from the Entity MIB (Version 3), for this
iFCP Gateway. If not supported, or if not related to a iFCP gateway. If not supported, or if not related to a
physical entity, then the value of this object is 0." physical entity, then the value of this object is 0."
REFERENCE "Entity MIB (Version 3)" REFERENCE "Entity MIB (Version 3)"
::= {ifcpLclGtwyInstEntry 2} ::= {ifcpLclGtwyInstEntry 2}
ifcpLclGtwyInstVersionMin OBJECT-TYPE ifcpLclGtwyInstVersionMin OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum iFCP protocol version supported by the local iFCP "The minimum iFCP protocol version supported by the local iFCP
skipping to change at page 9, line 47 skipping to change at page 9, line 46
::= {ifcpLclGtwyInstEntry 4} ::= {ifcpLclGtwyInstEntry 4}
ifcpLclGtwyInstAddrTransMode OBJECT-TYPE ifcpLclGtwyInstAddrTransMode OBJECT-TYPE
SYNTAX IfcpAddressMode SYNTAX IfcpAddressMode
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local iFCP gateway operating mode. Changing this value "The local iFCP gateway operating mode. Changing this value
may cause existing sessions to be disrupted." may cause existing sessions to be disrupted."
REFERENCE "RFC 4172, iFCP Protocol Specification; REFERENCE "RFC 4172, iFCP Protocol Specification;
RFC yyyy, Updates to the iFCP Protocol and RFC 6172, Deprecation of iFCP Address
Internet Protocol Number 133 " Translation Mode"
DEFVAL { addressTransparent } DEFVAL { addressTransparent }
::= {ifcpLclGtwyInstEntry 5} ::= {ifcpLclGtwyInstEntry 5}
ifcpLclGtwyInstFcBrdcstSupport OBJECT-TYPE ifcpLclGtwyInstFcBrdcstSupport OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether the local iFCP gateway supports FC Broadcast. "This value indicates whether the local iFCP gateway supports
Changing this value may cause existing sessions to be FC Broadcast. Changing this value may cause existing sessions
disrupted." to be disrupted."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
DEFVAL { false } DEFVAL { false }
::= {ifcpLclGtwyInstEntry 6} ::= {ifcpLclGtwyInstEntry 6}
ifcpLclGtwyInstDefaultIpTOV OBJECT-TYPE ifcpLclGtwyInstDefaultIpTOV OBJECT-TYPE
SYNTAX IfcpIpTOVorZero SYNTAX IfcpIpTOVorZero
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 11, line 7 skipping to change at page 11, line 10
performed on a session." performed on a session."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
DEFVAL { 10 } DEFVAL { 10 }
::= {ifcpLclGtwyInstEntry 8} ::= {ifcpLclGtwyInstEntry 8}
ifcpLclGtwyInstDescr OBJECT-TYPE ifcpLclGtwyInstDescr OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64)) SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A user-entered description for this iFCP Gateway." "A user-entered description for this iFCP gateway."
DEFVAL { "" } DEFVAL { "" }
::= {ifcpLclGtwyInstEntry 9} ::= {ifcpLclGtwyInstEntry 9}
ifcpLclGtwyInstNumActiveSessions OBJECT-TYPE ifcpLclGtwyInstNumActiveSessions OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current total number of iFCP sessions in the open or "The current total number of iFCP sessions in the open or
open-pending state." open-pending state."
skipping to change at page 11, line 50 skipping to change at page 12, line 4
ifcpSessionAttributesTable OBJECT-TYPE ifcpSessionAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SYNTAX SEQUENCE OF
IfcpSessionAttributesEntry IfcpSessionAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An iFCP session consists of the pair of N_PORTs comprising "An iFCP session consists of the pair of N_PORTs comprising
the session endpoints joined by a single TCP/IP connection. the session endpoints joined by a single TCP/IP connection.
This table provides information on each iFCP session This table provides information on each iFCP session
currently using a local iFCP Gateway instance. iFCP sessions currently using a local iFCP gateway instance. iFCP sessions
are created and removed by the iFCP Gateway instances, which are created and removed by the iFCP gateway instances, which
are reflected in this table." are reflected in this table."
::= {ifcpNportSessionInfo 1} ::= {ifcpNportSessionInfo 1}
ifcpSessionAttributesEntry OBJECT-TYPE ifcpSessionAttributesEntry OBJECT-TYPE
SYNTAX IfcpSessionAttributesEntry SYNTAX IfcpSessionAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry contains information about one iFCP session consisting "Each entry contains information about one iFCP session consisting
of a pair of N_PORTs joined by a single TCP/IP connection. This of a pair of N_PORTs joined by a single TCP/IP connection. This
table's INDEX includes ifcpLclGtwyInstIndex, which identifies the table's INDEX includes ifcpLclGtwyInstIndex, which identifies the
local iFCP Gateway instance that created the session for the local iFCP gateway instance that created the session for the
entry. entry.
Soon after an entry is created in this table for an iFCP session, it Soon after an entry is created in this table for an iFCP session, it
will correspond to an entry in the tcpConnectionTable of the TCP-MIB will correspond to an entry in the tcpConnectionTable of the TCP-MIB
(RFC 4022). The corresponding entry might represent a preexisting (RFC 4022). The corresponding entry might represent a preexisting
TCP connection, or it might be a newly-created entry. (Note that if TCP connection, or it might be a newly created entry. (Note that if
IPv4 is being used, an entry in RFC 2012's tcpConnTable may also IPv4 is being used, an entry in RFC 2012's tcpConnTable may also
correspond.) The values of ifcpSessionLclPrtlAddrType and correspond.) The values of ifcpSessionLclPrtlAddrType and
ifcpSessionRmtPrtlIfAddrType in this table and the values of ifcpSessionRmtPrtlIfAddrType in this table and the values of
tcpConnectionLocalAddressType and tcpConnectionRemAddressType used tcpConnectionLocalAddressType and tcpConnectionRemAddressType used
as INDEX values for the corresponding entry in the as INDEX values for the corresponding entry in the
tcpConnectionTable should be the same; this makes it simpler to tcpConnectionTable should be the same; this makes it simpler to
locate a session's TCP connection in the TCP-MIB. (Of course, all locate a session's TCP connection in the TCP-MIB. (Of course, all
four values need to be 'ipv4' if there's a corresponding entry in four values need to be 'ipv4' if there's a corresponding entry in
the tcpConnTable.) the tcpConnTable.)
skipping to change at page 13, line 23 skipping to change at page 13, line 27
ifcpSessionBound TruthValue, ifcpSessionBound TruthValue,
ifcpSessionStorageType StorageType ifcpSessionStorageType StorageType
} }
ifcpSessionIndex OBJECT-TYPE ifcpSessionIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The iFCP session index is a unique value used as an index "The iFCP session index is a unique value used as an index
to the table, along with a specific local iFCP Gateway to the table, along with a specific local iFCP gateway
instance. This index is used because the local N Port and instance. This index is used because the local N Port and
remote N Port information would create an complex index that remote N Port information would create a complex index that
would be difficult to implement." would be difficult to implement."
::= {ifcpSessionAttributesEntry 1} ::= {ifcpSessionAttributesEntry 1}
ifcpSessionLclPrtlIfIndex OBJECT-TYPE ifcpSessionLclPrtlIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the interface index in the IF-MIB ifTable being used "This is the interface index in the IF-MIB ifTable being used
as the local portal in this session, as described in the as the local portal in this session, as described in the
skipping to change at page 20, line 7 skipping to change at page 20, line 23
in the value of this counter can occur at reinitialization in the value of this counter can occur at reinitialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of ifcpSessionDiscontinuityTime." the value of ifcpSessionDiscontinuityTime."
::= {ifcpSessionStatsEntry 7} ::= {ifcpSessionStatsEntry 7}
ifcpSessionHeaderCRCErrors OBJECT-TYPE ifcpSessionHeaderCRCErrors OBJECT-TYPE
SYNTAX ZeroBasedCounter64 SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of CRC errors that occurred in the frame "The total number of Cyclic Redundancy Check (CRC) errors that
header, detected by the gateway for this session. Usually, occurred in the frame header, detected by the gateway for this
a single Header CRC error is sufficient to terminate an session. Usually, a single Header CRC error is sufficient to
iFCP session. Discontinuities in the value of this terminate an iFCP session. Discontinuities in the value of this
counter can occur at reinitialization of the management counter can occur at reinitialization of the management system,
system, and at other times as indicated by the value of and at other times as indicated by the value of
ifcpSessionDiscontinuityTime." ifcpSessionDiscontinuityTime."
::= {ifcpSessionStatsEntry 8} ::= {ifcpSessionStatsEntry 8}
ifcpSessionFcPayloadCRCErrors OBJECT-TYPE ifcpSessionFcPayloadCRCErrors OBJECT-TYPE
SYNTAX ZeroBasedCounter64 SYNTAX ZeroBasedCounter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of CRC errors that occurred in the Fibre "The total number of CRC errors that occurred in the Fibre
Channel frame payload, detected by the gateway for this Channel frame payload, detected by the gateway for this
skipping to change at page 21, line 12 skipping to change at page 21, line 30
ifcpSessionStatsTable: ifcpSessionTxOctets, ifcpSessionStatsTable: ifcpSessionTxOctets,
ifcpSessionRxOctets, ifcpSessionTxFrames, ifcpSessionRxOctets, ifcpSessionTxFrames,
ifcpSessionRxFrames, ifcpSessionStaleFrames, ifcpSessionRxFrames, ifcpSessionStaleFrames,
ifcpSessionHeaderCRCErrors, ifcpSessionFcPayloadCRCErrors, ifcpSessionHeaderCRCErrors, ifcpSessionFcPayloadCRCErrors,
and ifcpSessionOtherErrors. If no such discontinuities have and ifcpSessionOtherErrors. If no such discontinuities have
occurred since the last reinitialization of the local occurred since the last reinitialization of the local
management subsystem, then this object contains a zero value." management subsystem, then this object contains a zero value."
::= {ifcpSessionStatsEntry 11} ::= {ifcpSessionStatsEntry 11}
-- --
-- Low Capacity Statistics -- Low-Capacity Statistics
-- --
ifcpSessionLcStatsTable OBJECT-TYPE ifcpSessionLcStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SYNTAX SEQUENCE OF
IfcpSessionLcStatsEntry IfcpSessionLcStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides low capacity statistics for an iFCP "This table provides low-capacity statistics for an iFCP
session. These are provided for backward compatibility with session. These are provided for backward compatibility with
systems that do not support Counter64-based objects. At systems that do not support Counter64-based objects. At
1-Gbps rates, a Counter32-based object can wrap as often as 1-Gbps rates, a Counter32-based object can wrap as often as
every 34 seconds. Counter32-based objects can be sufficient every 34 seconds. Counter32-based objects can be sufficient
for many situations. However, when possible, it is for many situations. However, when possible, it is
recommended to use the high capacity statistics in recommended to use the high-capacity statistics in
ifcpSessionStatsTable based on Counter64 objects." ifcpSessionStatsTable based on Counter64 objects."
::= {ifcpNportSessionInfo 3} ::= {ifcpNportSessionInfo 3}
ifcpSessionLcStatsEntry OBJECT-TYPE ifcpSessionLcStatsEntry OBJECT-TYPE
SYNTAX IfcpSessionLcStatsEntry SYNTAX IfcpSessionLcStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Provides iFCP-specific statistics per session." "Provides iFCP-specific statistics per session."
AUGMENTS {ifcpSessionAttributesEntry} AUGMENTS {ifcpSessionAttributesEntry}
skipping to change at page 23, line 28 skipping to change at page 24, line 4
ifcpSessionLcOtherErrors OBJECT-TYPE ifcpSessionLcOtherErrors OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of errors, other than errors explicitly "The total number of errors, other than errors explicitly
measured, detected by the gateway for this session." measured, detected by the gateway for this session."
::= {ifcpSessionLcStatsEntry 8} ::= {ifcpSessionLcStatsEntry 8}
--========================================================== --==========================================================
ifcpCompliances ifcpCompliances
OBJECT IDENTIFIER ::= {ifcpGatewayConformance 1} OBJECT IDENTIFIER ::= {ifcpGatewayConformance 1}
ifcpGatewayCompliance MODULE-COMPLIANCE ifcpGatewayCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This MODULE-COMPLIANCE has been deprecated because address "This MODULE-COMPLIANCE has been deprecated because address
translation mode has been deprecated in the iFCP standard. It has translation mode has been deprecated in the iFCP standard. It has
the implementation requirements for iFCP MIB module compliance." the implementation requirements for iFCP MIB module compliance."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifcpLclGatewayGroup, ifcpLclGatewayGroup,
ifcpLclGatewaySessionGroup, ifcpLclGatewaySessionGroup,
ifcpLclGatewaySessionStatsGroup, ifcpLclGatewaySessionStatsGroup,
ifcpLclGatewaySessionLcStatsGroup ifcpLclGatewaySessionLcStatsGroup
} }
OBJECT ifcpSessionLclPrtlAddrType OBJECT ifcpSessionLclPrtlAddrType
skipping to change at page 24, line 26 skipping to change at page 24, line 47
addressTranslation(2)." addressTranslation(2)."
::= {ifcpCompliances 1} ::= {ifcpCompliances 1}
ifcpGatewayComplianceNoTranslation MODULE-COMPLIANCE ifcpGatewayComplianceNoTranslation MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Implementation requirements for iFCP MIB module compliance. "Implementation requirements for iFCP MIB module compliance.
Address translation mode has been deprecated in the iFCP standard." Address translation mode has been deprecated in the iFCP standard."
REFERENCE "RFC 4172, iFCP Protocol Specification; REFERENCE "RFC 4172, iFCP Protocol Specification;
RFC yyyy, Updates to the iFCP Protocol and RFC 6172, Deprecation of iFCP Address
Internet Protocol Number 133 " Translation Mode"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifcpLclGatewayGroup, ifcpLclGatewayGroup,
ifcpLclGatewaySessionGroupNoTranslation, ifcpLclGatewaySessionGroupNoTranslation,
ifcpLclGatewaySessionStatsGroup, ifcpLclGatewaySessionStatsGroup,
ifcpLclGatewaySessionLcStatsGroup ifcpLclGatewaySessionLcStatsGroup
} }
OBJECT ifcpSessionLclPrtlAddrType OBJECT ifcpSessionLclPrtlAddrType
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
skipping to change at page 26, line 49 skipping to change at page 27, line 25
ifcpSessionLcRxOctets, ifcpSessionLcRxOctets,
ifcpSessionLcTxFrames, ifcpSessionLcTxFrames,
ifcpSessionLcRxFrames, ifcpSessionLcRxFrames,
ifcpSessionLcStaleFrames, ifcpSessionLcStaleFrames,
ifcpSessionLcHeaderCRCErrors, ifcpSessionLcHeaderCRCErrors,
ifcpSessionLcFcPayloadCRCErrors, ifcpSessionLcFcPayloadCRCErrors,
ifcpSessionLcOtherErrors ifcpSessionLcOtherErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"iFCP Session Low Capacity Statistics group. This group "iFCP Session Low-Capacity Statistics group. This group
provides statistics with low-capacity 32-bit counters provides statistics with low-capacity 32-bit counters
for each iFCP session currently active between iFCP for each iFCP session currently active between iFCP
gateways. This group is only required for agents that gateways. This group is only required for agents that
do not support Counter64-based data types, or that need do not support Counter64-based data types, or that need
to support SNMPv1 applications." to support SNMPv1 applications."
::= {ifcpGroups 6} ::= {ifcpGroups 6}
ifcpLclGatewaySessionGroupNoTranslation OBJECT-GROUP ifcpLclGatewaySessionGroupNoTranslation OBJECT-GROUP
OBJECTS { OBJECTS {
ifcpSessionLclPrtlIfIndex, ifcpSessionLclPrtlIfIndex,
skipping to change at page 27, line 28 skipping to change at page 28, line 4
ifcpSessionRmtPrtlIfAddrType, ifcpSessionRmtPrtlIfAddrType,
ifcpSessionRmtPrtlIfAddr, ifcpSessionRmtPrtlIfAddr,
ifcpSessionRmtPrtlTcpPort, ifcpSessionRmtPrtlTcpPort,
ifcpSessionRmtNpFcid, ifcpSessionRmtNpFcid,
ifcpSessionIpTOV, ifcpSessionIpTOV,
ifcpSessionLclLTIntvl, ifcpSessionLclLTIntvl,
ifcpSessionRmtLTIntvl, ifcpSessionRmtLTIntvl,
ifcpSessionBound, ifcpSessionBound,
ifcpSessionStorageType ifcpSessionStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"iFCP Session group. This group provides information "iFCP Session group. This group provides information
about each iFCP session currently active between iFCP about each iFCP session currently active between iFCP
gateways." gateways."
::= {ifcpGroups 7} ::= {ifcpGroups 7}
END END
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects 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. network operations.
Changing the following object values, with a MAX-ACCESS of read- Changing the following object values, with a MAX-ACCESS of read-
write, may cause disruption in storage traffic: write, may cause disruption in storage traffic:
skipping to change at page 28, line 26 skipping to change at page 29, line 6
the network via SNMP. the network via SNMP.
The following object tables provide information about storage traffic The following object tables provide information about storage traffic
sessions, and can indicate to a user who is communicating and sessions, and can indicate to a user who is communicating and
exchanging storage data: exchanging storage data:
ifcpLclGtwyInstTable ifcpLclGtwyInstTable
ifcpSessionAttributesTable ifcpSessionAttributesTable
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
ifcpMgmtMIB { transmission 230 } ifcpMgmtMIB { transmission 230 }
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April "Textual Conventions for SMIv2", STD 58, RFC 2579, April
skipping to change at page 30, line 5 skipping to change at page 30, line 31
[RFC4044] McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, [RFC4044] McCloghrie, K., "Fibre Channel Management MIB", RFC 4044,
May 2005. May 2005.
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)",
RFC 4133, August 2005. RFC 4133, August 2005.
[RFC4172] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and [RFC4172] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and
M. Edwards, "iFCP - A Protocol for Internet Fibre Channel M. Edwards, "iFCP - A Protocol for Internet Fibre Channel
Storage Networking", RFC 4172, September 2005. Storage Networking", RFC 4172, September 2005.
[RFC4369] Gibbons, K., Monia, C., Tseng, J. and Travostino, F, [RFC4369] Gibbons, K., Monia, C., Tseng, J., and F. Travostino,
"Definitions of Managed Objects for Internet Fibre Channel "Definitions of Managed Objects for Internet Fibre Channel
Protocol (iFCP)", RFC 4369, January 2006. Protocol (iFCP)", RFC 4369, January 2006.
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management [RFC4502] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2", RFC 4502, May 2006. Information Base Version 2", RFC 4502, May 2006.
[RFCyyyy] Black, D. and D. Peterson, "Updates to the iFCP Protocol [RFC6172] Black, D. and D. Peterson, "Deprecation of the Internet
and Internet Protocol Number 133", RFC yyyy, mmyy Fibre Channel Protocol (iFCP) Address Translation Mode",
(Note to the RFC Editor: please replace yyyy with the RFC number RFC 6172, March 2011.
assigned to draft-ietf-storm-ifcp-ipn133-updates, replace mmyy
with the RFC month and year assigned to
draft-ietf-storm-ifcp-ipn133-updates & remove this note.)
8.2. Informative References 8.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
9. Acknowledgments 9. Acknowledgments
Credit goes to the authors of [RFC4369] for preparing the first version Credit goes to the authors of [RFC4369] (listed below) for preparing
of the iFCP MIB module. I wish to thank David Black, Tom Talpey and the first version of the iFCP MIB module. I wish to thank David
David Harrington for their significant inputs on this update. Black, Tom Talpey, and David Harrington for their significant inputs
on this update.
Authors' Address Authors of RFC 4369:
Prakash Venkatesen Kevin Gibbons
HCL Technologies Ltd. 2Wire Corporation
50-53, Greams Road, 1704 Automation Parkway
Chennai - 600006 San Jose, CA 95131 USA
India Phone: (408)895-1387
EMail: prakashvn@hcl.com EMail: kgibbons@yahoo.com
Authors of RFC 4369: Charles Monia
Consultant
7553 Morevern Circle
San Jose, CA 95135 USA
EMail: charles_monia@yahoo.com
Kevin Gibbons Josh Tseng
2Wire Corporation Riverbed Technology
1704 Automation Parkway 501 2nd Street, Suite 410
San Jose, CA 95131 USA San Francisco, CA 94107 USA
Phone: (408)895-1387 Phone: (650)274-2109
EMail: kgibbons@yahoo.com EMail: joshtseng@yahoo.com
Charles Monia
Consultant
7553 Morevern Circle
San Jose, CA 95135 USA
EMail: charles_monia@yahoo.com
Josh Tseng Franco Travostino
Riverbed Technology eBay Inc.
501 2nd Street, Suite 410 2145 Hamilton Avenue
San Francisco, CA 94107 USA San Jose, CA 95125
Phone: (650)274-2109 EMail: travos@ieee.org
EMail: joshtseng@yahoo.com
Franco Travostino Author's Address
eBay Inc.
2145 Hamilton Avenue Prakash Venkatesen (editor)
San Jose, CA 95125 HCL Technologies Ltd.
EMail: travos@ieee.org 50-53, Greams Road,
Chennai - 600006
India
EMail: prakashvn@hcl.com
 End of changes. 82 change blocks. 
157 lines changed or deleted 144 lines changed or added

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