Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard
Keith McCloghrie <kzm@cisco.com> Mon, 12 December 2005 22:09 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elvr1-00058i-LY; Mon, 12 Dec 2005 17:09:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elvqn-00057i-Ja; Mon, 12 Dec 2005 17:09:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04756; Mon, 12 Dec 2005 17:07:48 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElvrW-0000Nf-T5; Mon, 12 Dec 2005 17:09:40 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 12 Dec 2005 14:08:35 -0800
X-IronPort-AV: i="3.99,244,1131350400"; d="scan'208"; a="683815321:sNHT187870790"
Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jBCM8WBH018519; Mon, 12 Dec 2005 14:08:32 -0800 (PST)
Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA23070; Mon, 12 Dec 2005 14:08:31 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200512122208.OAA23070@cisco.com>
Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard
To: iesg@ietf.org
Date: Mon, 12 Dec 2005 14:08:31 -0800
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.2 (++)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit
Cc: imss@ietf.org, Orly_n@rad.co.il, black_david@emc.com, bwijnen@lucent.com, roger_cummings@symantec.com
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org
> The IESG has received a request from the Internet and Management Support > for Storage WG to consider the following document: > > - 'Fibre-Channel Name Server MIB ' > <draft-ietf-imss-fc-nsm-mib-04.txt> as a Proposed Standard draft-ietf-imss-fc-nsm-mib-04.txt is the second in a series of Fibre Channel MIBs which are being defined in the T11.5 working-group of INCITS, and then passed onto the IETF's IMSS Working Group to be approved as Internet Standards. T11.5 is presently working on the content of last few MIBs in the series. In the T11.5 meeting last week, the review of Letter Ballot comments for the Fibre Channel Zone Server MIB prompted a discussion about having consistency in the MIB representation of error codes across all types of Rejects (SW_RJT's, CT_IU Rejects, LS_RJT's). The outcome of the discussion was this: since Fibre Channel defines error codes in a consistent manner for all "Generic Services" (defined in the FC-GS-5 specification), so too should each of the MIBs define objects in a consistent manner to represent those error codes. Specifically, since FC-GS-5 defines error codes as consisting of three separate values: Reason-Code, Reason-Code-Explanation, and Reason-Vendor-Specific-Code each of the relevant MIBs should define three separate objects, one for each of these three values. One such relevant MIB is the Fibre-Channel Name Server MIB in draft-ietf-imss-fc-nsm-mib-04.txt, presently in IETF Last Call, which defines a notification to be generated when a request is rejected. Two of the objects that it requires to be included in that notification are: t11NsRejectReasonCode, t11NsRejReasonCodeExp, representing the Reason-Code and Reason-Code-Explanation, but it does not specify an object representing the Reason-Vendor-Specific-Code. Thus, to comply with the decision of T11.5, the MIB contained in draft-ietf-imss-fc-nsm-mib-04.txt should be updated to contain an object for the Reason-Vendor-Specific-Code. The specific edits which would be required for this change are listed below. Keith. --------------------- The edits to draft-ietf-imss-fc-nsm-mib-04.txt are to insert lines (those marked with an asterisk in the margin) as follows: 1. The addition of one additional OBJECT-TYPE in the t11NsRejectTable: T11NsRejectEntry ::= SEQUENCE { t11NsRejectCtCommandString OCTET STRING, t11NsRejectReasonCode T11NsGs4RejectReasonCode, t11NsRejReasonCodeExp T11NsRejReasonCodeExpl, * t11NsRejReasonVendorCode OCTET STRING } 2. The definition of the additional object: * t11NsRejReasonVendorCode OBJECT-TYPE * SYNTAX OCTET STRING (SIZE(1)) * MAX-ACCESS read-only * STATUS current * DESCRIPTION * "A registration reject vendor-specific code. This * object contains the vendor-specific code of the most * recent Name Server Registration request failure for the * particular port on the particular fabric." * ::= { t11NsRejectEntry 4 } 3. The insertion of t11NsRejectReasonVendorCode as an additional object in the t11NsRejectRegNotify notification: t11NsRejectRegNotify NOTIFICATION-TYPE OBJECTS { t11FamLocalSwitchWwn, t11NsRegPortName, t11NsRejectCtCommandString, t11NsRejectReasonCode, t11NsRejReasonCodeExp, * t11NsRejReasonVendorCode } STATUS current DESCRIPTION "This notification is generated ... The value of t11NsRejectCtCommandString indicates the rejected request, and the values of t11NsRejectReasonCode, t11NsRejReasonCodeExp and * t11NsRejReasonVendorCode indicate the reason for the rejection. ... 4. The inclusion of the new object in the relevant object group: t11NsNotifyControlGroup OBJECT-GROUP OBJECTS { t11NsRejectCtCommandString, t11NsRejectReasonCode, t11NsRejReasonCodeExp, * t11NsRejReasonVendorCode, t11NsInfoSubsetRejReqNotfyEnable } STATUS current DESCRIPTION "A collection ... 5. Update of the example in section 5.5 which mentions "each pair of t11NsRejectReasonCode and t11NsRejReasonCodeExp objects" so that it refers to "each set of t11NsRejectReasonCode, t11NsRejReasonCodeExp and t11NsRejectReasonVendorCode objects". _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss
- [imss] Last Call: 'Fibre-Channel Name Server MIB'… The IESG
- Re: [imss] Last Call: 'Fibre-Channel Name Server … Keith McCloghrie
- RE: [imss] Last Call: 'Fibre-Channel Name Server … Wijnen, Bert (Bert)
- Re: [imss] Last Call: 'Fibre-Channel Name Server … Brian E Carpenter
- RE: [imss] Last Call: 'Fibre-Channel Name Server … Black_David