draft-ietf-storm-ifcpmib-05.txt   draft-ietf-storm-ifcpmib-06.txt 
INTERNET-DRAFT Prakash Venkatesen, Editor INTERNET-DRAFT Prakash Venkatesen, Editor
STORM Working Group HCL Technologies STORM Working Group HCL Technologies
Intended status: Proposed Standard September 27, 2010 Intended status: Proposed Standard October 25, 2010
Expires: March 2011 Expires: April 2011
Obsoletes: 4369 Obsoletes: 4369
Definitions of Managed Objects for Internet Fibre Channel Protocol Definitions of Managed Objects for Internet Fibre Channel Protocol
(iFCP) (iFCP)
draft-ietf-storm-ifcpmib-05.txt draft-ietf-storm-ifcpmib-06.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on March 27, 2011. This Internet-Draft will expire on April 25, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 36 skipping to change at page 2, line 36
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......................................5
5. MIB Definition.................................................5 5. MIB Definition.................................................5
6. Security Considerations.......................................27 6. Security Considerations.......................................27
7. IANA Considerations...........................................28 7. IANA Considerations...........................................28
8. References....................................................28 8. References....................................................29
8.1. Normative References.....................................28 8.1. Normative References.....................................29
8.2. Informative References...................................29 8.2. Informative References...................................30
9. Acknowledgments...............................................30 9. Acknowledgments...............................................30
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
skipping to change at page 5, line 9 skipping to change at page 5, line 9
The following MIB module imports from SNMPv2-SMI [RFC2578], SNMPv2- The following MIB module imports from SNMPv2-SMI [RFC2578], SNMPv2-
TC [RFC2579], SNMPv2-CONF [RFC2580], HCNUM-TC [RFC2856], IF-MIB TC [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 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 updates the iFCP MIB module [RFC4369] for deprecated. This document obsoletes the iFCP MIB module [RFC4369]
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,
skipping to change at page 6, line 22 skipping to change at page 6, line 22
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 "201009200000Z" LAST-UPDATED "201010250000Z"
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) The IETF Trust (2010). This
version of this MIB module is part of RFC xxxx; version of this MIB module is part of RFC xxxx;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Editor: replace xxxx with actual RFC number & remove this note.
REVISION "201009200000Z" REVISION "201010250000Z"
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 xxxx."
-- RFC Editor: replace xxxx with actual RFC number & remove this note.
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
-- --
skipping to change at page 7, line 38 skipping to change at page 7, line 38
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
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. The value addressTranslation(2) is Mode."
deprecated."
REFERENCE "RFC yyyy, Updates to the iFCP Protocol and REFERENCE "RFC yyyy, Updates to the iFCP Protocol and
Internet Protocol Number 133 " Internet Protocol Number 133 "
-- RFC Editor: replace yyyy with the RFC number assigned to
-- draft-ietf-storm-ifcp-ipn133-updates & remove this note.
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 ==================
skipping to change at page 9, line 46 skipping to change at page 9, line 45
gateway instance." gateway instance."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
::= {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. This should always may cause existing sessions to be disrupted."
have the value addressTransparent(1) because address REFERENCE "RFC 4172, iFCP Protocol Specification;
translation mode is deprecated. " RFC yyyy, Updates to the iFCP Protocol and
REFERENCE "RFC yyyy, Updates to the iFCP Protocol and
Internet Protocol Number 133 " Internet Protocol Number 133 "
-- RFC Editor: replace yyyy with the RFC number assigned to
-- draft-ietf-storm-ifcp-ipn133-updates & remove this note.
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. "Whether the local iFCP gateway supports FC Broadcast.
Changing this value may cause existing sessions to be Changing this value may cause existing sessions to be
disrupted." 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"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The default IP_TOV used for iFCP sessions at this gateway. "The default IP_TOV used for iFCP sessions at this gateway.
This is the default maximum propagation delay that will be This is the default maximum propagation delay that will be
used for an iFCP session. The value can be changed on a used for an iFCP session. The value can be changed on a
per-session basis. The valid range is 0 - 3600 seconds. per-session basis. The valid range is 0 - 3600 seconds.
A value of 0 implies that fibre channel frame lifetime limits A value of 0 implies that fibre channel frame lifetime limits
will not be enforced." will not be enforced."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
DEFVAL { 6 } DEFVAL { 6 }
::= {ifcpLclGtwyInstEntry 7} ::= {ifcpLclGtwyInstEntry 7}
ifcpLclGtwyInstDefaultLTInterval OBJECT-TYPE ifcpLclGtwyInstDefaultLTInterval OBJECT-TYPE
SYNTAX IfcpLTIorZero SYNTAX IfcpLTIorZero
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The default Liveness Test Interval (LTI), in seconds, used "The default Liveness Test Interval (LTI), in seconds, used
for iFCP sessions at this gateway. This is the default for iFCP sessions at this gateway. This is the default
value for an iFCP session and can be changed on a value for an iFCP session and can be changed on a
per-session basis. The valid range is 0 - 65535 seconds. per-session basis. The valid range is 0 - 65535 seconds.
A value of 0 implies no Liveness Test Interval will be A value of 0 implies no Liveness Test Interval will be
performed on a session." performed on a session."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
skipping to change at page 16, line 5 skipping to change at page 16, line 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Fibre Channel Identifier of the remote N Port. For an "Fibre Channel Identifier of the remote N Port. For an
unbound session, this variable will be a zero-length string." unbound session, this variable will be a zero-length string."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
::= {ifcpSessionAttributesEntry 12} ::= {ifcpSessionAttributesEntry 12}
ifcpSessionRmtNpFcidAlias OBJECT-TYPE ifcpSessionRmtNpFcidAlias OBJECT-TYPE
SYNTAX FcAddressIdOrZero SYNTAX FcAddressIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS current
DESCRIPTION DESCRIPTION
"Fibre Channel Identifier Alias assigned by the local gateway "Fibre Channel Identifier Alias assigned by the local gateway
for the remote N Port. For an unbound session, this variable for the remote N Port. For an unbound session, this variable
will be a zero-length string. This object is deprecated because will be a zero-length string."
the address translation mode is deprecated." REFERENCE "RFC 4172, iFCP Protocol Specification"
REFERENCE "RFC yyyy, Updates to the iFCP Protocol and
Internet Protocol Number 133 "
::= {ifcpSessionAttributesEntry 13} ::= {ifcpSessionAttributesEntry 13}
ifcpSessionIpTOV OBJECT-TYPE ifcpSessionIpTOV OBJECT-TYPE
SYNTAX IfcpIpTOVorZero SYNTAX IfcpIpTOVorZero
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP_TOV being used for this iFCP session. This is the "The IP_TOV being used for this iFCP session. This is the
maximum propagation delay that will be used for the iFCP maximum propagation delay that will be used for the iFCP
session. The value can be changed on a per-session basis session. The value can be changed on a per-session basis
and initially defaults to ifcpLclGtwyInstDefaultIpTOV for and initially defaults to ifcpLclGtwyInstDefaultIpTOV for
the local gateway instance. The valid range is 0 - 3600 the local gateway instance. The valid range is 0 - 3600
seconds. A value of 0 implies fibre channel frame lifetime seconds. A value of 0 implies fibre channel frame lifetime
limits will not be enforced." limits will not be enforced."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
::= {ifcpSessionAttributesEntry 14} ::= {ifcpSessionAttributesEntry 14}
ifcpSessionLclLTIntvl OBJECT-TYPE ifcpSessionLclLTIntvl OBJECT-TYPE
SYNTAX IfcpLTIorZero SYNTAX IfcpLTIorZero
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Liveness Test Interval (LTI) used for this iFCP session. "The Liveness Test Interval (LTI) used for this iFCP session.
The value can be changed on a per-session basis and initially The value can be changed on a per-session basis and initially
defaults to ifcpLclGtwyInstDefaultLTInterval for the local defaults to ifcpLclGtwyInstDefaultLTInterval for the local
gateway instance. The valid range is 0 - 65535 seconds. gateway instance. The valid range is 0 - 65535 seconds.
A value of 0 implies that the gateway will not originate A value of 0 implies that the gateway will not originate
Liveness Test messages for the session." Liveness Test messages for the session."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
::= {ifcpSessionAttributesEntry 15} ::= {ifcpSessionAttributesEntry 15}
ifcpSessionRmtLTIntvl OBJECT-TYPE ifcpSessionRmtLTIntvl OBJECT-TYPE
SYNTAX IfcpLTIorZero SYNTAX IfcpLTIorZero
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Liveness Test Interval (LTI) as requested by the remote "The Liveness Test Interval (LTI) as requested by the remote
gateway instance to use for this iFCP session. This value may gateway instance to use for this iFCP session. This value may
change over the life of the session. The valid range is 0 - change over the life of the session. The valid range is 0 -
65535 seconds. A value of 0 implies that the remote gateway 65535 seconds. A value of 0 implies that the remote gateway
has not been requested to originate Liveness Test messages for has not been requested to originate Liveness Test messages for
the session." the session."
REFERENCE "RFC 4172, iFCP Protocol Specification" REFERENCE "RFC 4172, iFCP Protocol Specification"
skipping to change at page 24, line 8 skipping to change at page 24, line 9
DESCRIPTION DESCRIPTION
"Support is only required for global IPv4 "Support is only required for global IPv4
and IPv6 address types." and IPv6 address types."
OBJECT ifcpSessionRmtPrtlIfAddrType OBJECT ifcpSessionRmtPrtlIfAddrType
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Support is only required for global IPv4 "Support is only required for global IPv4
and IPv6 address types." and IPv6 address types."
OBJECT ifcpLclGtwyInstAddrTransMode
SYNTAX IfcpAddressMode {addressTransparent(1),
addressTranslation(2)}
DESCRIPTION
"This object must support addressTransparent(1) and
addressTranslation(2)."
::= {ifcpCompliances 1} ::= {ifcpCompliances 1}
ifcpGatewayComplianceNoTrans 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 is deprecated." Address translation mode has been deprecated in the iFCP standard."
REFERENCE "RFC 4172, iFCP Protocol Specification;
RFC yyyy, Updates to the iFCP Protocol and
Internet Protocol Number 133 "
-- RFC Editor: replace yyyy with the RFC number assigned to
-- draft-ietf-storm-ifcp-ipn133-updates & remove this note.
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifcpLclGatewayGroup, ifcpLclGatewayGroup,
ifcpLclGatewaySessionGroupNoTrans, ifcpLclGatewaySessionGroupNoTranslation,
ifcpLclGatewaySessionStatsGroup, ifcpLclGatewaySessionStatsGroup,
ifcpLclGatewaySessionLcStatsGroup ifcpLclGatewaySessionLcStatsGroup
} }
OBJECT ifcpSessionLclPrtlAddrType OBJECT ifcpSessionLclPrtlAddrType
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Support is only required for global IPv4 "Support is only required for global IPv4
and IPv6 address types." and IPv6 address types."
OBJECT ifcpSessionRmtPrtlIfAddrType OBJECT ifcpSessionRmtPrtlIfAddrType
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Support is only required for global IPv4 "Support is only required for global IPv4
and IPv6 address types." and IPv6 address types."
OBJECT ifcpLclGtwyInstAddrTransMode OBJECT ifcpLclGtwyInstAddrTransMode
SYNTAX IfcpAddressMode { addressTransparent(1) } SYNTAX IfcpAddressMode {addressTransparent(1)}
DESCRIPTION DESCRIPTION
"Support is only required for address "Support is only required for addressTransparent(1)."
Transparent mode."
::= {ifcpCompliances 2} ::= {ifcpCompliances 2}
ifcpGroups OBJECT IDENTIFIER ::= {ifcpGatewayConformance 2} ifcpGroups OBJECT IDENTIFIER ::= {ifcpGatewayConformance 2}
ifcpLclGatewayGroup OBJECT-GROUP ifcpLclGatewayGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ifcpLclGtwyInstPhyIndex, ifcpLclGtwyInstPhyIndex,
ifcpLclGtwyInstVersionMin, ifcpLclGtwyInstVersionMin,
ifcpLclGtwyInstVersionMax, ifcpLclGtwyInstVersionMax,
skipping to change at page 26, line 37 skipping to change at page 27, line 5
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}
ifcpLclGatewaySessionGroupNoTrans OBJECT-GROUP ifcpLclGatewaySessionGroupNoTranslation OBJECT-GROUP
OBJECTS { OBJECTS {
ifcpSessionLclPrtlIfIndex, ifcpSessionLclPrtlIfIndex,
ifcpSessionLclPrtlAddrType, ifcpSessionLclPrtlAddrType,
ifcpSessionLclPrtlAddr, ifcpSessionLclPrtlAddr,
ifcpSessionLclPrtlTcpPort, ifcpSessionLclPrtlTcpPort,
ifcpSessionLclNpWwun, ifcpSessionLclNpWwun,
ifcpSessionLclNpFcid, ifcpSessionLclNpFcid,
ifcpSessionRmtNpWwun, ifcpSessionRmtNpWwun,
ifcpSessionRmtPrtlIfAddrType, ifcpSessionRmtPrtlIfAddrType,
ifcpSessionRmtPrtlIfAddr, ifcpSessionRmtPrtlIfAddr,
skipping to change at page 29, line 41 skipping to change at page 30, line 10
[RFC4369] Gibbons, K., Monia, C., Tseng, J. and Travostino, F, [RFC4369] Gibbons, K., Monia, C., Tseng, J. and Travostino, F,
"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 [RFCyyyy] Black, D. and D. Peterson, "Updates to the iFCP Protocol
and Internet Protocol Number 133", RFC yyyy, mmyy and Internet Protocol Number 133", RFC yyyy, mmyy
(Note to the RFC Editor: please replace yyyy with the RFC number
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 with the first Credit goes to the authors of [RFC4369] for preparing the first version
version of the iFCP MIB module. I wish to thank David Black, Tom Talpey of the iFCP MIB module. I wish to thank David Black, Tom Talpey and
and David Harrington for their significant inputs on this update. David Harrington for their significant inputs on this update.
Authors' Address Authors' Address
Prakash Venkatesen Prakash Venkatesen
HCL Technologies Ltd. HCL Technologies Ltd.
50-53, Greams Road, 50-53, Greams Road,
Chennai - 600006 Chennai - 600006
India India
EMail: prakashvn@hcl.com EMail: prakashvn@hcl.com
Authors of RFC 4369: Authors of RFC 4369:
Kevin Gibbons Kevin Gibbons
2Wire Corporation 2Wire Corporation
1704 Automation Parkway 1704 Automation Parkway
San Jose, CA 95131 USA San Jose, CA 95131 USA
Phone: (408)895-1387 Phone: (408)895-1387
EMail: kgibbons@2wire.com EMail: kgibbons@yahoo.com
Charles Monia Charles Monia
Consultant Consultant
7553 Morevern Circle 7553 Morevern Circle
San Jose, CA 95135 USA San Jose, CA 95135 USA
EMail: charles_monia@yahoo.com EMail: charles_monia@yahoo.com
Josh Tseng Josh Tseng
Riverbed Technology Riverbed Technology
501 2nd Street, Suite 410 501 2nd Street, Suite 410
 End of changes. 31 change blocks. 
33 lines changed or deleted 59 lines changed or added

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