From imss-bounces@ietf.org Thu Dec 01 09:59:42 2005 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 1EhpuQ-0001Ys-9S; Thu, 01 Dec 2005 09:59:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhpuK-0001SZ-Ju; Thu, 01 Dec 2005 09:59:36 -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 JAA00575; Thu, 1 Dec 2005 09:58:49 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhqEq-0000HA-1L; Thu, 01 Dec 2005 10:20:48 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EhpuJ-0002IR-Pv; Thu, 01 Dec 2005 09:59:35 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 01 Dec 2005 09:59:35 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: imss@ietf.org Subject: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-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 ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-12-15. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-04.txt _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Dec 01 16:09:47 2005 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 1EhvgZ-0000lq-Pt; Thu, 01 Dec 2005 16:09:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhvgY-0000kq-8S for imss@megatron.ietf.org; Thu, 01 Dec 2005 16:09:46 -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 QAA02982 for ; Thu, 1 Dec 2005 16:08:57 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ehw13-0001we-7v for imss@ietf.org; Thu, 01 Dec 2005 16:30:59 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jB1L9VRY003972 for ; Thu, 1 Dec 2005 15:09:31 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Thu, 1 Dec 2005 22:09:05 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508C0A395@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Imss (E-mail)" Date: Thu, 1 Dec 2005 22:09:18 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [imss] IESG approved: draft-ietf-imss-ip-over-fibre-channel-03.txt X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org Fomral announcement will be posted in a few days by the IESG secretraiat. Thanks to the authors and the WG. The IESG has agreed to request expedited processing by the RFC-Editor to try and get an RFC number by Jan 20th. Bert _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Dec 05 16:39:12 2005 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 1EjO3E-00022v-Kf; Mon, 05 Dec 2005 16:39:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjO3A-00021m-Ca; Mon, 05 Dec 2005 16:39:08 -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 QAA14401; Mon, 5 Dec 2005 16:38:18 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjOOX-00024K-79; Mon, 05 Dec 2005 17:01:13 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EjO39-0007qy-C0; Mon, 05 Dec 2005 16:39:07 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 05 Dec 2005 16:39:07 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel' to Proposed Standard X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org The IESG has approved the following document: - 'Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel ' as a Proposed Standard This document obsoletes RFC2625 and RFC3831. This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Bert Wijnen and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-ip-over-fibre-channel-03.txt Technical Summary This document specifies the encapsulation of IPv6, IPv4 and ARP packets over Fibre Channel. This document also specifies the methods for forming IPv6 link-local addresses and statelessly autoconfigured IPv6 addresses on Fibre Channel networks, and a mechanism to perform IPv4 address resolution over Fibre Channel networks. This document (when published as RFC) obsoletes RFC2625 and RFC3831. Working Group Summary This document has been reviewed by Fibre Channel experts in Technical Committee T11 (Fibre Channel standards organization) in addition to members of the IMSS WG. There is solid support for this document both in the WG and from T11. Protocol Quality This document replaces and consolidates two separate RFCs on IPv4 over Fibre Channel (RFC 2625) and IPv6 over Fibre Channel (RFC 3831). Most of its technical content is unchanged from those RFCs. The technical changes that have been made are primarily based on implementation experience. The protocol has been reviewed for the IESG by David L. Black (WG chair). Also Bert Wijnen has reviewed this document for the IESG. In addition, Brian Haberman has done a review for the INT Area as requested by WG-chair (David Black) via Margaret Wasserman. Note to RFC Editor - Make sure the abstract lists the RFCs that will be obsoleted: OLD: Abstract This document specifies the way of encapsulating IPv6, IPv4 and ARP packets over Fibre Channel. This document specifies also the method of forming IPv6 link-local addresses and statelessly autoconfigured IPv6 addresses on Fibre Channel networks, and a mechanism to perform IPv4 address resolution over Fibre Channel networks. NEW: Abstract This document specifies the way of encapsulating IPv6, IPv4 and ARP packets over Fibre Channel. This document specifies also the method of forming IPv6 link-local addresses and statelessly autoconfigured IPv6 addresses on Fibre Channel networks, and a mechanism to perform IPv4 address resolution over Fibre Channel networks. This document obsoletes RFC2625 and RFC3831. - In the acknowledgement section pls add a few more acknowledgements: OLD: The authors would like to acknowledge the ANSI INCITS T11.3 Task Group members who reviewed this document as well as the authors of [RFC-2625] and [RFC-3831]. NEW: The authors would like to acknowledge the ANSI INCITS T11.3 Task Group members who reviewed this document as well as the authors of [RFC-2625] and [RFC-3831]. The authors also thank the IMSS WG and Brian Haberman for their review and comments. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Dec 12 17:09:07 2005 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 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 (PST) 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 List-Unsubscribe: , List-Post: List-Help: List-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 ' > 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 From imss-bounces@ietf.org Fri Dec 16 09:09:09 2005 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 1EnGGj-0001Jp-4I; Fri, 16 Dec 2005 09:09:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EnGGd-0001Gl-5W; Fri, 16 Dec 2005 09:09:07 -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 JAA22727; Fri, 16 Dec 2005 09:08:02 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EnGID-0008Vg-2M; Fri, 16 Dec 2005 09:10:43 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 16 Dec 2005 06:08:50 -0800 X-IronPort-AV: i="3.99,261,1131350400"; d="scan'208"; a="379574060:sNHT35013186" Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jBGE8lQK027890; Fri, 16 Dec 2005 06:08:47 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id GAA04358; Fri, 16 Dec 2005 06:08:44 -0800 (PST) From: Keith McCloghrie Message-Id: <200512161408.GAA04358@cisco.com> Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed To: brc@zurich.ibm.com (Brian E Carpenter) Date: Fri, 16 Dec 2005 06:08:44 -0800 (PST) In-Reply-To: from "Brian E Carpenter" at Dec 16, 2005 08:56:15 AM 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: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Content-Transfer-Encoding: 7bit Cc: iesg@ietf.org, Orly_n@rad.co.il, imss@ietf.org, bwijnen@lucent.com, roger_cummings@symantec.com, black_david@emc.com, Keith McCloghrie X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org Hi Brian, Your words are fine. I didn't mean to imply that either party is required to agree with the other, but past experience showed that neither party had the full range of technical knowledge needed to produce the desired result without help from the other. Thanks, Keith. > Keith, > > No technical comment from me, but I was tickled by two of your > phrases. > > > ...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. > ... > > ...Thus, to comply with the decision of T11.5, > > I trust that what you really mean is > > ...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 > considered for the IETF standards track. > > and > > ...Thus, to be consistent with the decision of T11.5 > > since the IETF is autonomous in its decisions. > > Regards > Brian > > Keith McCloghrie wrote: > >>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 ' > >> 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 From imss-bounces@ietf.org Tue Dec 20 09:32:29 2005 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 1EoiXV-0004Uf-Kd; Tue, 20 Dec 2005 09:32:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EoiXT-0004UQ-TG for imss@megatron.ietf.org; Tue, 20 Dec 2005 09:32:27 -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 JAA04294 for ; Tue, 20 Dec 2005 09:31:23 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoiZt-00060M-6Q for imss@ietf.org; Tue, 20 Dec 2005 09:34:58 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBKEWJpH028258; Tue, 20 Dec 2005 08:32:19 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Tue, 20 Dec 2005 15:32:18 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508E66CA1@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "David Black (E-mail)" Date: Tue, 20 Dec 2005 14:26:10 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: "Imss \(E-mail\)" Subject: [imss] FW: Last Call Expired: X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org I have not seen any IETF Last Call comments, so, unless I hear objections today, this doc goes on Jan 5 agenda for IESG. Bert -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of DraftTracker Mail System Sent: Tuesday, December 13, 2005 05:30 To: iesg@ietf.org Cc: iesg-secretary@ietf.org Subject: Last Call Expired: Please DO NOT reply on this email. ID: draft-ietf-imss-fc-fam-mib IETF Last Call has ended, and the state has been changed to Waiting for Writeup https://datatracker.ietf.org/cgi-bin/idtracker.cgi?command=view_id&dTag=12530&rfc_flag=0&ballot_id=1833 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Dec 20 09:32:32 2005 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 1EoiXY-0004VW-Pk; Tue, 20 Dec 2005 09:32:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EoiXT-0004UM-RY; Tue, 20 Dec 2005 09:32:32 -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 JAA04297; Tue, 20 Dec 2005 09:31:23 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoiZt-00060P-6X; Tue, 20 Dec 2005 09:34:58 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBKEWJJt028262; Tue, 20 Dec 2005 08:32:19 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Tue, 20 Dec 2005 15:32:18 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508E66CA0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Keith McCloghrie , iesg@ietf.org Subject: RE: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard Date: Tue, 20 Dec 2005 14:26:09 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: imss@ietf.org, Orly_n@rad.co.il X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org So Keith and co-authors/editors, I am going to assume a new revision to address these IETF Last Call comments, right? Any idea when I can expect that? Today maybe ? If so, I can probably get the doc on Jan 5 IESG agenda. AS far as I know, the below were the only IETF Last Call Comments. Bert > -----Original Message----- > From: Keith McCloghrie [mailto:kzm@cisco.com] > Sent: Monday, December 12, 2005 23:09 > To: iesg@ietf.org > Cc: imss@ietf.org; black_david@emc.com; roger_cummings@symantec.com; > bwijnen@lucent.com; Orly_n@rad.co.il > Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to > Proposed Standard > > > > 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 ' > > 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 From imss-bounces@ietf.org Tue Dec 20 09:37:02 2005 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 1Eoibu-0005yL-Bz; Tue, 20 Dec 2005 09:37:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eoibs-0005xS-Ok; Tue, 20 Dec 2005 09:37:01 -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 JAA05248; Tue, 20 Dec 2005 09:35:56 -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 1EoieH-0006Ew-5O; Tue, 20 Dec 2005 09:39:31 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 20 Dec 2005 06:36:49 -0800 X-IronPort-AV: i="3.99,273,1131350400"; d="scan'208"; a="686551982:sNHT33589012" 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 jBKEamQg000888; Tue, 20 Dec 2005 06:36:48 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id GAA21311; Tue, 20 Dec 2005 06:36:47 -0800 (PST) From: Keith McCloghrie Message-Id: <200512201436.GAA21311@cisco.com> Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed To: bwijnen@lucent.com ("Wijnen, Bert (Bert)") Date: Tue, 20 Dec 2005 06:36:47 -0800 (PST) In-Reply-To: from "Wijnen, Bert (Bert)" at Dec 20, 2005 02:26:09 PM 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: 6640e3bbe8a4d70c4469bcdcbbf0921d Content-Transfer-Encoding: 7bit Cc: imss@ietf.org, Keith McCloghrie , Orly_n@rad.co.il, iesg@ietf.org X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org Yes, I should be able to produce a new version today, and make the submission to internet-drafts@ietf.org today. Keith. > So Keith and co-authors/editors, I am going to assume a new revision > to address these IETF Last Call comments, right? > Any idea when I can expect that? Today maybe ? > If so, I can probably get the doc on Jan 5 IESG agenda. > > AS far as I know, the below were the only IETF Last Call Comments. > > Bert > > -----Original Message----- > > From: Keith McCloghrie [mailto:kzm@cisco.com] > > Sent: Monday, December 12, 2005 23:09 > > To: iesg@ietf.org > > Cc: imss@ietf.org; black_david@emc.com; roger_cummings@symantec.com; > > bwijnen@lucent.com; Orly_n@rad.co.il > > Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to > > Proposed Standard > > > > > > > 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 ' > > > 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 From imss-bounces@ietf.org Tue Dec 20 15:52:10 2005 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 1EooSw-0007mC-GA; Tue, 20 Dec 2005 15:52:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EooQz-0006uS-VC; Tue, 20 Dec 2005 15:50:10 -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 PAA04372; Tue, 20 Dec 2005 15:49:05 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EooTN-0005YT-Q1; Tue, 20 Dec 2005 15:52:39 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EooQs-0008Tw-H5; Tue, 20 Dec 2005 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 20 Dec 2005 15:50:02 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-nsm-mib-05.txt X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre-Channel Name Server MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-nsm-mib-05.txt Pages : 38 Date : 2005-12-20 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to the Name Server function of a Fibre Channel network. The Fibre Channel Name Server provides a means for Fibre Channel ports to register and discover Fibre Channel names and attributes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-imss-fc-nsm-mib-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-12-20143448.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-nsm-mib-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-12-20143448.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart-- From imss-bounces@ietf.org Fri Dec 23 09:07:12 2005 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 1EpnZg-0000xs-4w; Fri, 23 Dec 2005 09:07:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EnASC-0004Q1-P3; Fri, 16 Dec 2005 02:56:38 -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 CAA15480; Fri, 16 Dec 2005 02:55:34 -0500 (EST) Received: from mtagate3.de.ibm.com ([195.212.29.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EnATi-0003RZ-Bh; Fri, 16 Dec 2005 02:58:12 -0500 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate3.de.ibm.com (8.12.10/8.12.10) with ESMTP id jBG7uN5C089204; Fri, 16 Dec 2005 07:56:23 GMT Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jBG7uMgi229502; Fri, 16 Dec 2005 08:56:22 +0100 Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av03.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id jBG7uM6g019850; Fri, 16 Dec 2005 08:56:22 +0100 Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id jBG7uL7d019838; Fri, 16 Dec 2005 08:56:21 +0100 Received: from zurich.ibm.com (sig-9-145-129-125.de.ibm.com [9.145.129.125]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id IAA64368; Fri, 16 Dec 2005 08:56:20 +0100 Message-ID: <43A2731F.8050701@zurich.ibm.com> Date: Fri, 16 Dec 2005 08:56:15 +0100 From: Brian E Carpenter Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: Keith McCloghrie Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard References: <200512122208.OAA23070@cisco.com> In-Reply-To: <200512122208.OAA23070@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 93e7fb8fef2e780414389440f367c879 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 23 Dec 2005 09:07:10 -0500 Cc: roger_cummings@symantec.com, Orly_n@rad.co.il, imss@ietf.org, bwijnen@lucent.com, black_david@emc.com, iesg@ietf.org X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org Keith, No technical comment from me, but I was tickled by two of your phrases. > ...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. ... > ...Thus, to comply with the decision of T11.5, I trust that what you really mean is ...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 considered for the IETF standards track. and ...Thus, to be consistent with the decision of T11.5 since the IETF is autonomous in its decisions. Regards Brian Keith McCloghrie wrote: >>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 ' >> 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 From imss-bounces@ietf.org Fri Dec 23 21:33:37 2005 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 1EpzE0-0003MJ-VS; Fri, 23 Dec 2005 21:33:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EpzDu-0003Ka-Nn for imss@megatron.ietf.org; Fri, 23 Dec 2005 21:33:35 -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 VAA15345 for ; Fri, 23 Dec 2005 21:32:23 -0500 (EST) From: Black_David@emc.com Received: from mexforward.lss.emc.com ([168.159.213.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpzH3-0004Gc-I2 for imss@ietf.org; Fri, 23 Dec 2005 21:36:45 -0500 Received: from mailhub.lss.emc.com (nirah.lss.emc.com [10.254.144.13]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jBO2XHTp027316; Fri, 23 Dec 2005 21:33:17 -0500 (EST) Received: from MAHO3MSX2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32]) by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id jBO2XEDl002126; Fri, 23 Dec 2005 21:33:14 -0500 (EST) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 23 Dec 2005 21:33:14 -0500 Message-ID: To: brc@zurich.ibm.com Subject: RE: [imss] Last Call: 'Fibre-Channel Name Server MIB' to Proposed Standard Date: Fri, 23 Dec 2005 21:33:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.1.0.0, Antispam-Data: 2005.12.23.35 X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ -3, HASHBUSTER_BLOCK_V2 3.4, NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HASHBUSTER_BLOCK_V2_1 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.3 (/) X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7 Cc: imss@ietf.org, Black_David@emc.com X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org Sorry for the delayed appearance of this message to the list - it was caught in the IETF spam-trap, which I only just got a "round tuit" for emptying ... Thanks, --David ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ---------------------------------------------------- > -----Original Message----- > From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org] On > Behalf Of Brian E Carpenter > Sent: Friday, December 16, 2005 2:56 AM > To: Keith McCloghrie > Cc: roger_cummings@symantec.com; Orly_n@rad.co.il; > imss@ietf.org; bwijnen@lucent.com; Black, David; iesg@ietf.org > Subject: Re: [imss] Last Call: 'Fibre-Channel Name Server > MIB' to Proposed Standard > > Keith, > > No technical comment from me, but I was tickled by two of your > phrases. > > > ...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. > ... > > ...Thus, to comply with the decision of T11.5, > > I trust that what you really mean is > > ...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 > considered for the IETF standards track. > > and > > ...Thus, to be consistent with the decision of T11.5 > > since the IETF is autonomous in its decisions. > > Regards > Brian > > Keith McCloghrie wrote: > >>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 ' > >> 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 mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Dec 27 14:30:40 2005 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 1ErKWu-0002h8-P6; Tue, 27 Dec 2005 14:30:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ErKWt-0002gw-I7 for imss@megatron.ietf.org; Tue, 27 Dec 2005 14:30:39 -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 OAA03784 for ; Tue, 27 Dec 2005 14:29:30 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com ([168.159.213.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ErKal-0000U3-Dc for imss@ietf.org; Tue, 27 Dec 2005 14:34:41 -0500 Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9]) by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id jBRJUMRM014037 for ; Tue, 27 Dec 2005 14:30:24 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Tue, 27 Dec 2005 14:30:22 -0500 Message-ID: To: imss@ietf.org Date: Tue, 27 Dec 2005 14:30:20 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.1.0.0, Antispam-Data: 2005.12.27.20 X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ -3, NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.3 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: Black_David@emc.com Subject: [imss] IMSS WG MIB status X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org The FAM and NSM MIBs are through IETF Last Call and under consideration by the IESG for approval for publication as RFCs. The NSM MIB has been revised based on the last call comment about reject reason codes (see Keith's email of December 12th for a description of the revisions), and it is the revised version of the MIB that is being considered by the IESG - we've taken the absence of response to Keith's email to signify approval of the changes, but if anyone has an issue, please speak up *quickly*. The WG Last Call on the Routing Information, FSPF and Virtual Fabric MIBs has completed without comments, and the reject reason code issue found in the NSM MIB does not apply to these three MIBs. Therefore WG Last Call on the Routing Information, FSPF and Virtual Fabric MIBs has completed successfully, and I will be submitting them to the ADs/IESG with a request for publication as RFCs by the first week of January. Thanks, --David ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ---------------------------------------------------- _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss