From imss-bounces@ietf.org Tue Nov 08 20:51:08 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 1EZf7E-0000FB-Fr; Tue, 08 Nov 2005 20:51:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZf7D-0000Ex-KT; Tue, 08 Nov 2005 20:51: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 UAA02547; Tue, 8 Nov 2005 20:50:40 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZfN8-0003ZB-Rv; Tue, 08 Nov 2005 21:07:35 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 08 Nov 2005 17:50:58 -0800 Received: from [10.21.122.196] (sjc-vpn6-708.cisco.com [10.21.122.196]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jA91ouZC029586; Tue, 8 Nov 2005 17:50:56 -0800 (PST) Message-ID: <437155FD.1050208@cisco.com> Date: Tue, 08 Nov 2005 17:50:53 -0800 From: Claudio DeSanti User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: iesg@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: imss@ietf.org Subject: [imss] Re: Last Call: '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 During the resolution of a comment from the Internet Area review we added the following sentence to section 5.1: The U/L bit has no function in Fibre Channel (because an N_Port_Name is used only as an identifier, not as an address to which frames are forwarded), however it has to be properly handled when a Name_Identifier is converted to an EUI-64 address. Although the parenthetical sentence is true, it is not really the reason why the U/L bit has no function in Fibre Channel, because the uniqueness scope of a Fibre Channel Name_Identifier is due to its NAA rather than to the fact that it is not used in forwarding. To avoid confusion, I propose to just remove the parenthetical sentence, resulting in the following sentence: The U/L bit has no function in Fibre Channel, however it has to be properly handled when a Name_Identifier is converted to an EUI-64 address. Thanks, Claudio. The IESG wrote: > The IESG has received a request from the Internet and Management Support for > Storage WG to consider the following document: > > - 'Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel ' > as a Proposed Standard > > This document (once approved) will obsolete RFC2625 and RFC3831. > > 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-11-13. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-imss-ip-over-fibre-channel-02.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Nov 09 13:28:25 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 1EZugL-0007J1-1s; Wed, 09 Nov 2005 13:28:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZugJ-0007Il-G1 for imss@megatron.ietf.org; Wed, 09 Nov 2005 13:28:23 -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 NAA28058 for ; Wed, 9 Nov 2005 13:27:56 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com ([168.159.2.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZuwN-0004wi-D9 for imss@ietf.org; Wed, 09 Nov 2005 13:44:59 -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.6) with ESMTP id jA9ISGwE008784 for ; Wed, 9 Nov 2005 13:28:19 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Nov 2005 13:27:51 -0500 Message-ID: To: imss@ietf.org Date: Wed, 9 Nov 2005 13:27:37 -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.11.9.18 X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ -3, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __KNOWN_SPAMMER_ADDRESS_5 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.3 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Subject: [imss] Vancouver Minutes (DRAFT) 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 Please send any corrections, etc. to the list. Thanks, --David Internet and Management Support for Storage (imss) WG Meeting - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840 Minutes - DRAFT ------------------------------------------------------ Administrivia, agenda bashing, draft status review, etc.: 15 min David L. Black, EMC (new imss WG chair) Blue sheets Note Well Milestones (see WG charter page on IETF web site) WG Draft status - IP over FC draft is in IETF Last Call - FAM and NSM MIBs should go to IETF Last Call by the end of next week (Keith McCloghrie and Bert Wijnen will coordinate to make this happen). - Remaining 3 WG MIBs will go to WG Last Call by end of November. --> Record status T11.5 Status, Fibre Channel MIBs under development: 20 min Roger Cummings (Symantec, T11.5 chair) See slides. T11.5 has 3 more MIBs that will be sent to the imss WG - Zone Server MIB, Registered State Change Notification MIB, and Fabric Configuration Server MIB. The imss WG's current Apr 06 milestone to determine what to do next will be replaced by a milestone (later in 2006) to work on these 3 MIBs. These 3 MIBs may not be ready for handoff to imss prior to the next IETF meeting, but the mechanism used in Paris for the VF MIB can be reused - the imss WG can decide to accept the drafts as official WG drafts subject to a pending T11 formal votes to pass change control to the IETF. T11.5 is considering assigning MIB development responsibility to protocol development work groups instead of the current approach of having a separate group that works on MIBs. This will be discussed at the T11 meetings in early December. FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min Roger Cummings (Symantec, T11.5 chair) draft-cummings-imss-flip-00.txt See presentation. Netconf appears promising for the configuration aspects of FLIP, but currently contains no support for events or notifications from the configured device. Use of netconf would result in functionality at the level of the configuration model instead of a 1-1 match between FAIS API calls and RPCs. The required event/notification mechanism needs to be capable of carrying a fair amount of structured information - it is somewhat analogous to the use of COPS to ask a policy decision point "I just received this RSVP reservation request, what should I do about it?". There are also concerns about effective transmission of bulk binary data (encoding in XML is unworkable, but encapsulation or wrapping in XML is probably ok). The netconf group is not currently standardizing schemas, but will want/need to, so this could be a timely interaction between imss and netconf. The FLIP concept and suggested use of netconf will be discussed further in the early December T11 meetings. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Nov 09 17:08:34 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 1EZy7O-0001KY-Ti; Wed, 09 Nov 2005 17:08:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZy7N-0001I0-GL for imss@megatron.ietf.org; Wed, 09 Nov 2005 17:08:33 -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 RAA13741 for ; Wed, 9 Nov 2005 17:08:05 -0500 (EST) From: Black_David@emc.com Received: from mailhub.lss.emc.com ([168.159.2.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZyNT-0003tx-C8 for imss@ietf.org; Wed, 09 Nov 2005 17:25:11 -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.6) with ESMTP id jA9M8S2l013094; Wed, 9 Nov 2005 17:08:29 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Nov 2005 17:08:28 -0500 Message-ID: To: roger_cummings@symantec.com, imss@ietf.org Subject: RE: [imss] Vancouver Minutes (DRAFT) Date: Wed, 9 Nov 2005 17:08:19 -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.11.9.25 X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_BODY_PROD_1+ -5, EMC_FROM_00+ -3, NO_REAL_NAME 0, __C230066_P5 0, __CHILD_PORN_NOT_1 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __KNOWN_SPAMMER_ADDRESS_5 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.3 (/) X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243 Cc: 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 Roger, 1) is an AI to you (Roger). Please cc: me so that I can track the results. 2) will be corrected in the final minutes. I will also remove your T11.5 chair affiliation from the FLIP agenda item in the minutes to match the bashed agenda. Thanks, --David p.s. How come none of the Symantec pens here at IETF work? I'm sitting in front of a pile of them. I know ... they're not Veritas pens ;-). ---------------------------------------------------- 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 ---------------------------------------------------- > David, > > Thanks for posting the minutes so promptly. > > Two minor points: > > 1) Bert made a suggestion that a message is sent to the Netconf mailing > list soliciting interest in helping with the schema definition. Is that > an AI to you or I? > > 2) I'd like to modify the last sentence to read " The FLIP concept and > suggested use of netconf will be discussed further at T11 before the > next imss meeting." The focus for December has to be resolving FAIS > Letter Ballot comments, and if that means that the FLIP discussion > doesn't get done until later, that's the way it should be. > > Regards, > > > > > Roger > > > -----Original Message----- > > From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org] On > > Behalf Of Black_David@emc.com > > Sent: Wednesday, November 09, 2005 1:28 PM > > To: imss@ietf.org > > Subject: [imss] Vancouver Minutes (DRAFT) > > > > Please send any corrections, etc. to the list. > > > > Thanks, > > --David > > > > Internet and Management Support for Storage (imss) WG Meeting > > - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840 > > Minutes - DRAFT > > ------------------------------------------------------ > > > > Administrivia, agenda bashing, draft status review, etc.: 15 min > > David L. Black, EMC (new imss WG chair) > > Blue sheets > > Note Well > > Milestones (see WG charter page on IETF web site) > > WG Draft status > > - IP over FC draft is in IETF Last Call > > - FAM and NSM MIBs should go to IETF Last Call by the > > end of next week (Keith McCloghrie and > > Bert Wijnen > > will coordinate to make this happen). > > - Remaining 3 WG MIBs will go to WG Last Call by end > > of November. > > > > --> Record status > > > > T11.5 Status, Fibre Channel MIBs under development: 20 min > > Roger Cummings (Symantec, T11.5 chair) > > > > See slides. > > > > T11.5 has 3 more MIBs that will be sent to the imss WG - Zone > > Server MIB, Registered State Change Notification MIB, and > > Fabric Configuration Server MIB. The imss WG's current Apr > > 06 milestone to determine what to do next will be replaced by > > a milestone (later in 2006) to work on these 3 MIBs. These 3 > > MIBs may not be ready for handoff to imss prior to the next > > IETF meeting, but the mechanism used in Paris for the VF MIB > > can be reused - the imss WG can decide to accept the drafts > > as official WG drafts subject to a pending T11 formal votes > > to pass change control to the IETF. > > > > T11.5 is considering assigning MIB development responsibility > > to protocol development work groups instead of the current > > approach of having a separate group that works on MIBs. This > > will be discussed at the T11 meetings in early December. > > > > FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min > > Roger Cummings (Symantec, T11.5 chair) > > draft-cummings-imss-flip-00.txt > > > > See presentation. Netconf appears promising for the > > configuration aspects of FLIP, but currently contains no > > support for events or notifications from the configured > > device. Use of netconf would result in functionality at the > > level of the configuration model instead of a 1-1 match > > between FAIS API calls and RPCs. The required > > event/notification mechanism needs to be capable of carrying > > a fair amount of structured information - it is somewhat > > analogous to the use of COPS to ask a policy decision point > > "I just received this RSVP reservation request, what should I > > do about it?". There are also concerns about effective > > transmission of bulk binary data (encoding in XML is > > unworkable, but encapsulation or wrapping in XML is probably > > ok). The netconf group is not currently standardizing > > schemas, but will want/need to, so this could be a timely > > interaction between imss and netconf. > > > > The FLIP concept and suggested use of netconf will be > > discussed further in the early December T11 meetings. > > > > _______________________________________________ > > 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 Thu Nov 10 18:18:19 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 1EaLgR-0002WR-Pf; Thu, 10 Nov 2005 18:18:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZvUQ-0004KD-4i for imss@megatron.ietf.org; Wed, 09 Nov 2005 14:20: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 OAA01956 for ; Wed, 9 Nov 2005 14:19:42 -0500 (EST) Received: from silver.veritas.com ([143.127.12.111]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZvkT-0006g0-UE for imss@ietf.org; Wed, 09 Nov 2005 14:36:46 -0500 Received: from sxchcon1-int.veritas.com (HELO SVLXCHCON1.enterprise.veritas.com) (10.137.18.171) by silver.veritas.com with ESMTP; 09 Nov 2005 11:19:50 -0800 Received: from hroxchcon1.enterprise.veritas.com ([10.67.33.17]) by SVLXCHCON1.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 11:19:49 -0800 Received: from hroxchcln1.enterprise.veritas.com ([10.67.33.21]) by hroxchcon1.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 14:19:48 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [imss] Vancouver Minutes (DRAFT) Date: Wed, 9 Nov 2005 14:19:47 -0500 Message-ID: Thread-Topic: [imss] Vancouver Minutes (DRAFT) Thread-Index: AcXlW8yjUvH4+6YVSfuimls3OhbsNAAAz7eA From: "Roger Cummings" To: , X-OriginalArrivalTime: 09 Nov 2005 19:19:48.0030 (UTC) FILETIME=[8CB735E0:01C5E562] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 10 Nov 2005 18:18:18 -0500 Cc: 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 David, Thanks for posting the minutes so promptly. Two minor points: 1) Bert made a suggestion that a message is sent to the Netconf mailing list soliciting interest in helping with the schema definition. Is that an AI to you or I? 2) I'd like to modify the last sentence to read " The FLIP concept and suggested use of netconf will be discussed further at T11 before the next imss meeting." The focus for December has to be resolving FAIS Letter Ballot comments, and if that means that the FLIP discussion doesn't get done until later, that's the way it should be. Regards, Roger > -----Original Message----- > From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org] On=20 > Behalf Of Black_David@emc.com > Sent: Wednesday, November 09, 2005 1:28 PM > To: imss@ietf.org > Subject: [imss] Vancouver Minutes (DRAFT) >=20 > Please send any corrections, etc. to the list. >=20 > Thanks, > --David >=20 > Internet and Management Support for Storage (imss) WG Meeting=20 > - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840=20 > Minutes - DRAFT > ------------------------------------------------------ >=20 > Administrivia, agenda bashing, draft status review, etc.: 15 min > David L. Black, EMC (new imss WG chair) > Blue sheets > Note Well > Milestones (see WG charter page on IETF web site) > WG Draft status > - IP over FC draft is in IETF Last Call > - FAM and NSM MIBs should go to IETF Last Call by the > end of next week (Keith McCloghrie and=20 > Bert Wijnen > will coordinate to make this happen). > - Remaining 3 WG MIBs will go to WG Last Call by end > of November. >=20 > --> Record status >=20 > T11.5 Status, Fibre Channel MIBs under development: 20 min > Roger Cummings (Symantec, T11.5 chair) >=20 > See slides. >=20 > T11.5 has 3 more MIBs that will be sent to the imss WG - Zone=20 > Server MIB, Registered State Change Notification MIB, and=20 > Fabric Configuration Server MIB. The imss WG's current Apr=20 > 06 milestone to determine what to do next will be replaced by=20 > a milestone (later in 2006) to work on these 3 MIBs. These 3=20 > MIBs may not be ready for handoff to imss prior to the next=20 > IETF meeting, but the mechanism used in Paris for the VF MIB=20 > can be reused - the imss WG can decide to accept the drafts=20 > as official WG drafts subject to a pending T11 formal votes=20 > to pass change control to the IETF. >=20 > T11.5 is considering assigning MIB development responsibility=20 > to protocol development work groups instead of the current=20 > approach of having a separate group that works on MIBs. This=20 > will be discussed at the T11 meetings in early December. >=20 > FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min > Roger Cummings (Symantec, T11.5 chair) > draft-cummings-imss-flip-00.txt >=20 > See presentation. Netconf appears promising for the=20 > configuration aspects of FLIP, but currently contains no=20 > support for events or notifications from the configured=20 > device. Use of netconf would result in functionality at the=20 > level of the configuration model instead of a 1-1 match=20 > between FAIS API calls and RPCs. The required=20 > event/notification mechanism needs to be capable of carrying=20 > a fair amount of structured information - it is somewhat=20 > analogous to the use of COPS to ask a policy decision point=20 > "I just received this RSVP reservation request, what should I=20 > do about it?". There are also concerns about effective=20 > transmission of bulk binary data (encoding in XML is=20 > unworkable, but encapsulation or wrapping in XML is probably=20 > ok). The netconf group is not currently standardizing=20 > schemas, but will want/need to, so this could be a timely=20 > interaction between imss and netconf. >=20 > The FLIP concept and suggested use of netconf will be=20 > discussed further in the early December T11 meetings. >=20 > _______________________________________________ > imss mailing list > imss@ietf.org > https://www1.ietf.org/mailman/listinfo/imss >=20 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Fri Nov 11 10:52:15 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 1EabCJ-0005Ga-66; Fri, 11 Nov 2005 10:52:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EabCH-0005GE-2X for imss@megatron.ietf.org; Fri, 11 Nov 2005 10:52:13 -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 KAA14594 for ; Fri, 11 Nov 2005 10:51:43 -0500 (EST) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EabSi-00014N-Gu for imss@ietf.org; Fri, 11 Nov 2005 11:09:12 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id jABFpuPJ012793; Fri, 11 Nov 2005 09:51:57 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Fri, 11 Nov 2005 16:51:55 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155088C7BA4@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Roger Cummings , Black_David@emc.com, imss@ietf.org Subject: RE: [imss] Vancouver Minutes (DRAFT) Date: Fri, 11 Nov 2005 16:51:53 +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: 36b1f8810cb91289d885dc8ab4fc8172 Cc: 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 Inline > -----Original Message----- > From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org]On Behalf Of > Roger Cummings > Sent: Wednesday, November 09, 2005 20:20 > To: Black_David@emc.com; imss@ietf.org > Subject: RE: [imss] Vancouver Minutes (DRAFT) > > > David, > > Thanks for posting the minutes so promptly. > > Two minor points: > > 1) Bert made a suggestion that a message is sent to the > Netconf mailing list soliciting interest in helping with the schema > definition. Is that an AI to you or I? > We can go back to listen to the audio if we want to, but I think I mentioned that I suggested to send a msg to netconf list to inform them about your FLIP draft and sollicit partcipation/help. I think I also mentioned that doing a XML schema might be an option, but if that should be standardized right away is to be determined. NetConf sofar has not gotten approval from the ADs to do any standardization work foe XML Schemas. Once we have a schema definition and once we see people implement/play with it/use it, then we can discuss if we can or should standardize. They also are discussing events. And since you seem to have a requirement, it would be good to clearly specify them and see how well they match with requirements that others claim in this space. Bert > 2) I'd like to modify the last sentence to read " The FLIP concept and > suggested use of netconf will be discussed further at T11 before the > next imss meeting." The focus for December has to be resolving FAIS > Letter Ballot comments, and if that means that the FLIP discussion > doesn't get done until later, that's the way it should be. > > Regards, > > > > > Roger > > > -----Original Message----- > > From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org] On > > Behalf Of Black_David@emc.com > > Sent: Wednesday, November 09, 2005 1:28 PM > > To: imss@ietf.org > > Subject: [imss] Vancouver Minutes (DRAFT) > > > > Please send any corrections, etc. to the list. > > > > Thanks, > > --David > > > > Internet and Management Support for Storage (imss) WG Meeting > > - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840 > > Minutes - DRAFT > > ------------------------------------------------------ > > > > Administrivia, agenda bashing, draft status review, etc.: 15 min > > David L. Black, EMC (new imss WG chair) > > Blue sheets > > Note Well > > Milestones (see WG charter page on IETF web site) > > WG Draft status > > - IP over FC draft is in IETF Last Call > > - FAM and NSM MIBs should go to IETF Last Call by the > > end of next week (Keith McCloghrie and > > Bert Wijnen > > will coordinate to make this happen). > > - Remaining 3 WG MIBs will go to WG Last Call by end > > of November. > > > > --> Record status > > > > T11.5 Status, Fibre Channel MIBs under development: 20 min > > Roger Cummings (Symantec, T11.5 chair) > > > > See slides. > > > > T11.5 has 3 more MIBs that will be sent to the imss WG - Zone > > Server MIB, Registered State Change Notification MIB, and > > Fabric Configuration Server MIB. The imss WG's current Apr > > 06 milestone to determine what to do next will be replaced by > > a milestone (later in 2006) to work on these 3 MIBs. These 3 > > MIBs may not be ready for handoff to imss prior to the next > > IETF meeting, but the mechanism used in Paris for the VF MIB > > can be reused - the imss WG can decide to accept the drafts > > as official WG drafts subject to a pending T11 formal votes > > to pass change control to the IETF. > > > > T11.5 is considering assigning MIB development responsibility > > to protocol development work groups instead of the current > > approach of having a separate group that works on MIBs. This > > will be discussed at the T11 meetings in early December. > > > > FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min > > Roger Cummings (Symantec, T11.5 chair) > > draft-cummings-imss-flip-00.txt > > > > See presentation. Netconf appears promising for the > > configuration aspects of FLIP, but currently contains no > > support for events or notifications from the configured > > device. Use of netconf would result in functionality at the > > level of the configuration model instead of a 1-1 match > > between FAIS API calls and RPCs. The required > > event/notification mechanism needs to be capable of carrying > > a fair amount of structured information - it is somewhat > > analogous to the use of COPS to ask a policy decision point > > "I just received this RSVP reservation request, what should I > > do about it?". There are also concerns about effective > > transmission of bulk binary data (encoding in XML is > > unworkable, but encapsulation or wrapping in XML is probably > > ok). The netconf group is not currently standardizing > > schemas, but will want/need to, so this could be a timely > > interaction between imss and netconf. > > > > The FLIP concept and suggested use of netconf will be > > discussed further in the early December T11 meetings. > > > > _______________________________________________ > > 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 > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Nov 15 10:43:04 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 1Ec2xc-0002fk-57; Tue, 15 Nov 2005 10:43:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ec2xZ-0002fA-8T for imss@megatron.ietf.org; Tue, 15 Nov 2005 10:43:02 -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 KAA01272 for ; Tue, 15 Nov 2005 10:42:28 -0500 (EST) Received: from silver.veritas.com ([143.127.12.111]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ec3El-0008Eh-Dd for imss@ietf.org; Tue, 15 Nov 2005 11:00:51 -0500 Received: from sxchcon1-int.veritas.com (HELO SVLXCHCON1.enterprise.veritas.com) (10.137.18.171) by silver.veritas.com with ESMTP; 15 Nov 2005 07:42:36 -0800 Received: from hroxchcon2.enterprise.veritas.com ([10.67.33.18]) by SVLXCHCON1.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Nov 2005 07:42:35 -0800 Received: from hroxchcln1.enterprise.veritas.com ([10.67.33.21]) by hroxchcon2.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Nov 2005 10:42:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [imss] Vancouver Minutes (DRAFT) Date: Tue, 15 Nov 2005 10:42:32 -0500 Message-ID: Thread-Topic: [imss] Vancouver Minutes (DRAFT) Thread-Index: AcXm1+XzQMAWpsExRySwsUjZqZjDQgCiuxxQ From: "Roger Cummings" To: "Wijnen, Bert \(Bert\)" , , X-OriginalArrivalTime: 15 Nov 2005 15:42:32.0405 (UTC) FILETIME=[315B3050:01C5E9FB] X-Spam-Score: 0.0 (/) X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f Content-Transfer-Encoding: quoted-printable Cc: 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 Thanks for the clarification, Bert. I'll get a message out to the netconf list this week once I've posted a new version of the I-D with a section about requirements for events. I'll also see if I can put in a summary of the types of function calls in the current API to serve as a basis for a discussion on the types of operation that will be required. Regards, Roger Cummings Symantec roger_cummings@symantec.com > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20 > Sent: Friday, November 11, 2005 10:52 AM > To: Roger Cummings; Black_David@emc.com; imss@ietf.org > Subject: RE: [imss] Vancouver Minutes (DRAFT) >=20 > Inline >=20 > > -----Original Message----- > > From: imss-bounces@ietf.org=20 > [mailto:imss-bounces@ietf.org]On Behalf Of=20 > > Roger Cummings > > Sent: Wednesday, November 09, 2005 20:20 > > To: Black_David@emc.com; imss@ietf.org > > Subject: RE: [imss] Vancouver Minutes (DRAFT) > >=20 > >=20 > > David, > >=20 > > Thanks for posting the minutes so promptly. > >=20 > > Two minor points: > >=20 > > 1) Bert made a suggestion that a message is sent to the Netconf=20 > > mailing list soliciting interest in helping with the schema=20 > > definition. Is that an AI to you or I? > >=20 >=20 > We can go back to listen to the audio if we want to, but I=20 > think I mentioned that I suggested to send a msg to netconf=20 > list to inform them about your FLIP draft and sollicit=20 > partcipation/help. >=20 > I think I also mentioned that doing a XML schema might be an=20 > option, but if that should be standardized right away is to=20 > be determined. > NetConf sofar has not gotten approval from the ADs to do any=20 > standardization work foe XML Schemas. Once we have a schema=20 > definition and once we see people implement/play with it/use=20 > it, then we can discuss if we can or should standardize. >=20 > They also are discussing events. And since you seem to have a=20 > requirement, it would be good to clearly specify them and see=20 > how well they match with requirements that others claim in this space. >=20 > Bert > > 2) I'd like to modify the last sentence to read " The FLIP=20 > concept and=20 > > suggested use of netconf will be discussed further at T11=20 > before the=20 > > next imss meeting." The focus for December has to be resolving FAIS=20 > > Letter Ballot comments, and if that means that the FLIP discussion=20 > > doesn't get done until later, that's the way it should be. > >=20 > > Regards, > >=20 > >=20 > >=20 > >=20 > > Roger > >=20 > > > -----Original Message----- > > > From: imss-bounces@ietf.org=20 > [mailto:imss-bounces@ietf.org] On Behalf=20 > > > Of Black_David@emc.com > > > Sent: Wednesday, November 09, 2005 1:28 PM > > > To: imss@ietf.org > > > Subject: [imss] Vancouver Minutes (DRAFT) > > >=20 > > > Please send any corrections, etc. to the list. > > >=20 > > > Thanks, > > > --David > > >=20 > > > Internet and Management Support for Storage (imss) WG Meeting > > > - Vancouver, Canada Tuesday, November 8, 2005: 1740-1840=20 > Minutes -=20 > > > DRAFT > > > ------------------------------------------------------ > > >=20 > > > Administrivia, agenda bashing, draft status review, etc.: 15 min > > > David L. Black, EMC (new imss WG chair) > > > Blue sheets > > > Note Well > > > Milestones (see WG charter page on IETF web site) > > > WG Draft status > > > - IP over FC draft is in IETF Last Call > > > - FAM and NSM MIBs should go to IETF Last Call by the > > > end of next week (Keith McCloghrie and=20 > Bert Wijnen > > > will coordinate to make this happen). > > > - Remaining 3 WG MIBs will go to WG Last Call by end > > > of November. > > >=20 > > > --> Record status > > >=20 > > > T11.5 Status, Fibre Channel MIBs under development: 20 min > > > Roger Cummings (Symantec, T11.5 chair) > > >=20 > > > See slides. > > >=20 > > > T11.5 has 3 more MIBs that will be sent to the imss WG -=20 > Zone Server=20 > > > MIB, Registered State Change Notification MIB, and Fabric=20 > > > Configuration Server MIB. The imss WG's current Apr > > > 06 milestone to determine what to do next will be replaced by a=20 > > > milestone (later in 2006) to work on these 3 MIBs. These=20 > 3 MIBs may=20 > > > not be ready for handoff to imss prior to the next IETF=20 > meeting, but=20 > > > the mechanism used in Paris for the VF MIB can be reused=20 > - the imss=20 > > > WG can decide to accept the drafts as official WG drafts=20 > subject to=20 > > > a pending T11 formal votes to pass change control to the IETF. > > >=20 > > > T11.5 is considering assigning MIB development responsibility to=20 > > > protocol development work groups instead of the current=20 > approach of=20 > > > having a separate group that works on MIBs. This will be=20 > discussed=20 > > > at the T11 meetings in early December. > > >=20 > > > FLIP (FAIS Line Interface Protocol) Conceptual Discussion: 25 min > > > Roger Cummings (Symantec, T11.5 chair) > > > draft-cummings-imss-flip-00.txt > > >=20 > > > See presentation. Netconf appears promising for the=20 > configuration=20 > > > aspects of FLIP, but currently contains no support for events or=20 > > > notifications from the configured device. Use of netconf would=20 > > > result in functionality at the level of the configuration model=20 > > > instead of a 1-1 match between FAIS API calls and RPCs. The=20 > > > required event/notification mechanism needs to be capable of=20 > > > carrying a fair amount of structured information - it is somewhat=20 > > > analogous to the use of COPS to ask a policy decision=20 > point "I just=20 > > > received this RSVP reservation request, what should I do=20 > about it?". =20 > > > There are also concerns about effective transmission of=20 > bulk binary=20 > > > data (encoding in XML is unworkable, but encapsulation or=20 > wrapping=20 > > > in XML is probably ok). The netconf group is not currently=20 > > > standardizing schemas, but will want/need to, so this could be a=20 > > > timely interaction between imss and netconf. > > >=20 > > > The FLIP concept and suggested use of netconf will be discussed=20 > > > further in the early December T11 meetings. > > >=20 > > > _______________________________________________ > > > imss mailing list > > > imss@ietf.org > > > https://www1.ietf.org/mailman/listinfo/imss > > >=20 > >=20 > > _______________________________________________ > > imss mailing list > > imss@ietf.org > > https://www1.ietf.org/mailman/listinfo/imss > >=20 >=20 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Nov 15 18:50:08 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 1EcAYy-0004Lr-JF; Tue, 15 Nov 2005 18:50:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcAYs-0004Je-II; Tue, 15 Nov 2005 18:50:02 -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 SAA07534; Tue, 15 Nov 2005 18:49:28 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EcAqC-0000OK-LQ; Tue, 15 Nov 2005 19:07:56 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EcAYr-0001hC-Gz; Tue, 15 Nov 2005 18:50:01 -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, 15 Nov 2005 18:50:01 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: imss@ietf.org Subject: [imss] I-D ACTION: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 --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 : Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-ip-over-fibre-channel-03.txt Pages : 32 Date : 2005-11-15 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-ip-over-fibre-channel-03.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-ip-over-fibre-channel-03.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-ip-over-fibre-channel-03.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-11-15170105.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-ip-over-fibre-channel-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-ip-over-fibre-channel-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-11-15170105.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 Thu Nov 17 13:07: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 1EcoAW-0000z4-DM; Thu, 17 Nov 2005 13:07:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcoAU-0000xt-Mz for imss@megatron.ietf.org; Thu, 17 Nov 2005 13:07:30 -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 NAA10850 for ; Thu, 17 Nov 2005 13:06:56 -0500 (EST) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EcoSA-0003En-96 for imss@ietf.org; Thu, 17 Nov 2005 13:25:47 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id jAHI7EVn007728 for ; Thu, 17 Nov 2005 12:07:14 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Thu, 17 Nov 2005 19:07:13 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550897EFE3@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: imss@ietf.org Date: Thu, 17 Nov 2005 19:07: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: b5d20af10c334b36874c0264b10f59f1 Subject: [imss] FW: New Version Notification - draft-ietf-imss-fc-nsm-mib-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 IMSS WG members, FYI, MIB DOctor review. It seems as if it was not yet posted to the WG list. Thanks to Orly for the review. Bert -----Original Message----- From: Orly Nicklass [mailto:orly_n@rad.com] Sent: Monday, October 31, 2005 10:19 To: Keith McCloghrie (E-mail) Cc: vgaonkar@cisco.com; hvivek@cisco.com; sgai@cisco.com; Wijnen, Bert (Bert); David Black (E-mail); cds@cisco.com Subject: RE: New Version Notification - draft-ietf-imss-fc-nsm-mib-03.txt Hi, While reviewing the ID I have not found any critical issue and in general it is well written. However, I like to point to some possible clarifications that can be added for non-initiated: 1-The term RSCN is used in few places, I think it will be a good idea to fully state it in first appearance as Registered State Change Notification. 2-sections 5.4.3 and 5.4.4. descriptions are a bit confusing, I had to read it few times to get it clear. Can it be improved somehow? Other small editorial/administrative suggestions: 1-References Section has [FC-SW-3] "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", ANSI NCITS xxx-xxxx, T11/Project 1508-D/Rev 6.6, December 2003. I am not sure what the xxx-xxxx should be, In fam-mib I saw [FC-SW-3] "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", ANSI INCITS 384-2004, June 2004. December 2003. Having two dates is not ok either, so I suppose both places better be fixed during final publication 2-[FC-FAM-MIB] DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf- imss-fc-fam-mib-nn.txt), work-in-progress. According to the memo 3rd paragraph it is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." so it has to be changed to -[FC-FAM-MIB] DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- Channel Fabric Address Manager MIB", work-in-progress. 3-in the reference clause of some MIB objects, it is common today to state the item within [] and not within (). Example page 11.(very small issue) 4-section 4 Relationship to Other MIBs, has the word focussed in the first line, (typo err) should be changed to focused 5-at the very end of the MIB typo err: t11NsNotifyGroup NOTIFICATION-GROUP NOTIFICATIONS {t11NsRejectRegNotify } STATUS current DESCRIPTION "A collection of notifications for monitoring rejections of Name Server regsitrations." ^ registrations Compilation tools and nits were fine. Orly -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] Sent: Sunday, October 16, 2005 17:54 To: David Black (E-mail); cds@cisco.com; Keith McCloghrie (E-mail) Cc: vgaonkar@cisco.com; hvivek@cisco.com; sgai@cisco.com; Orly Nicklass Subject: FW: New Version Notification - draft-ietf-imss-fc-nsm-mib-03.txt Orly has agreed/volunteered to review this MIB document with a target completion date of end of october. Thanks Orly! Bert _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Sat Nov 19 00:52:15 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 1EdLe3-0004uc-1S; Sat, 19 Nov 2005 00:52:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdLe1-0004uX-U9 for imss@megatron.ietf.org; Sat, 19 Nov 2005 00:52:13 -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 AAA08068 for ; Sat, 19 Nov 2005 00:51:38 -0500 (EST) From: Black_David@emc.com Received: from hop-nat-131.emc.com ([168.159.213.131] helo=mexforward.lss.emc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EdLvz-0000FG-6k for imss@ietf.org; Sat, 19 Nov 2005 01:10:49 -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.6) with ESMTP id jAJ5q2rW020414 for ; Sat, 19 Nov 2005 00:52:02 -0500 (EST) 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.6) with ESMTP id jAJ5q0jk012532 for ; Sat, 19 Nov 2005 00:52:01 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Sat, 19 Nov 2005 00:52:00 -0500 Message-ID: To: imss@ietf.org Date: Sat, 19 Nov 2005 00:51:55 -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.11.18.42 X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ -3, NO_REAL_NAME 0, __C230066_P5 0, __CHILD_PORN_NOT_1 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: 7655788c23eb79e336f5f8ba8bce7906 Subject: [imss] Changes in 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 According to the draft editor, the following minor changes were made from the -02 to the -03 version of the IP over FC draft in response to IETF Last Call comments: - In the front page, changed the word "replaces" to "obsoletes"; - In section 1, changed 2 times the word "replaces" to "obsoletes"; - In section 5.1, removed the sentence "(because an N_Port_Name is used only as an identifier, not as an address to which frames are forwarded)"; - In section 16, added the sentence "as well as the authors of [RFC-2625] and [RFC-3831]". The draft tracker shows the draft as now being in IESG Evaluation for final approval as an RFC. 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 From imss-bounces@ietf.org Mon Nov 21 12:55: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 1EeFt6-0007eW-Ba; Mon, 21 Nov 2005 12:55:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeFt0-0007eO-8q for imss@megatron.ietf.org; Mon, 21 Nov 2005 12:55:26 -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 MAA18770 for ; Mon, 21 Nov 2005 12:54:48 -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 1EeGBR-0002OS-2z for imss@ietf.org; Mon, 21 Nov 2005 13:14:30 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 21 Nov 2005 09:55:10 -0800 X-IronPort-AV: i="3.97,357,1125903600"; d="scan'208"; a="368239957:sNHT29123252" Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jALHt9CJ018064 for ; Mon, 21 Nov 2005 09:55:09 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id JAA17111 for imss@ietf.org; Mon, 21 Nov 2005 09:55:09 -0800 (PST) From: Keith McCloghrie Message-Id: <200511211755.JAA17111@cisco.com> To: imss@ietf.org Date: Mon, 21 Nov 2005 09:55:09 -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: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: 7bit Subject: [imss] Re: Submitting updated I-D's - draft-ietf-imss-fc-nsm-mib-04.txt (fwd) 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, The review of the FC Name Server MIB by a MIB Doctor (Orly Nicklass) and our Area Director (Bert Wijnen) raised a number of minor issues. The most significant was this clarification: > > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-nsm-mib-04.txt > > > > - smicng says: > > E: f(fcnsm.mi2), (693,13) Index item "t11NsRegFc4TypeValue" > > must be defined with syntax that includes a range > > > > So are all possible values of an Unsigned32 valid? Even then > > it is easy to include a range. I think I understand why zero > > is a valid (index) value. You may add a few words about that too. > > I had to do some research to check the answer to this, and I've > included the results of my research in the updated definition: > > t11NsRegFc4TypeValue OBJECT-TYPE > SYNTAX Unsigned32 (0..255) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "An integer value which identifies an FC-4 TYPE value > (representing a particular protocol type, as specified > in FC-FS) for which an FC-4 Descriptor has been > registered. > > An instance of this object contains a 'Type value' > which corresponds to a '1' bit in the value of the > t11NsRegFc4Type registered for the same port; > this correspondence is as specified in FC-GS-4." > REFERENCE > "ANSI INCITS 387-2004, Fibre Channel - Generic > Services-4 (FC-GS-4), section 5.2.3.8, and > ANSI INCITS 373-2003, Fibre Channel - Framing and > Signaling (FC-FS), section 9.6, Table 29." > ::= { t11NsRegFc4DescriptorEntry 1 } The updated document is at ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-nsm-mib-04.txt I plan to submit as an updated I-D in a few days. Thanks to Orly and Bert for their reviews, Keith. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Nov 22 18:50:23 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 1Eehu3-00021u-3f; Tue, 22 Nov 2005 18:50:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eehtj-0001ly-8v; Tue, 22 Nov 2005 18:50:03 -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 SAA29812; Tue, 22 Nov 2005 18:49:24 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EeiCT-0004yw-5Q; Tue, 22 Nov 2005 19:09:25 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Eehth-0005aS-QH; Tue, 22 Nov 2005 18:50:01 -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, 22 Nov 2005 18:50:01 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fam-mib-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 --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 Fabric Address Manager MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-fam-mib-03.txt Pages : 43 Date : 2005-11-22 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 a Fibre Channel network's Fabric Address Manager. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-03.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-fam-mib-03.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-fam-mib-03.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-11-22172908.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-fam-mib-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-fam-mib-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-11-22172908.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 Mon Nov 28 12:57:51 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 1EgnGB-0003lQ-Jj; Mon, 28 Nov 2005 12:57:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EgnG7-0003kK-AG; Mon, 28 Nov 2005 12:57:47 -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 MAA09175; Mon, 28 Nov 2005 12:57:03 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Egna2-0007Ff-Db; Mon, 28 Nov 2005 13:18:22 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EgnG6-0007y6-Ko; Mon, 28 Nov 2005 12:57:46 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 28 Nov 2005 12:57:46 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: imss@ietf.org Subject: [imss] Last Call: 'Fibre Channel Fabric Address Manager 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 Fabric Address Manager 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-12. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-03.txt _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Nov 28 15:50:23 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 1Egpx9-0008FZ-PK; Mon, 28 Nov 2005 15:50:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Egpwq-00081K-TD; Mon, 28 Nov 2005 15:50:04 -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 PAA03620; Mon, 28 Nov 2005 15:49:19 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EgqGm-0006T1-4D; Mon, 28 Nov 2005 16:10:40 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Egpwo-0007p3-Im; Mon, 28 Nov 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: Mon, 28 Nov 2005 15:50:02 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-vf-mib-00.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 : The Virtual Fabrics MIB Author(s) : S. Kipp, et al. Filename : draft-ietf-imss-fc-vf-mib-00.txt Pages : 22 Date : 2005-11-28 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 Fibre Channel network's Virtual Fabrics function. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-vf-mib-00.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-vf-mib-00.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-vf-mib-00.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-11-28142952.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-vf-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-vf-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-11-28142952.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 Mon Nov 28 16:42:44 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 1Egqlo-0001b5-4v; Mon, 28 Nov 2005 16:42:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Egqln-0001b0-45 for imss@megatron.ietf.org; Mon, 28 Nov 2005 16:42:43 -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 QAA24714 for ; Mon, 28 Nov 2005 16:41:58 -0500 (EST) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Egr5j-0005DJ-3z for imss@ietf.org; Mon, 28 Nov 2005 17:03:20 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 28 Nov 2005 13:42:33 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jASLgWCJ004643 for ; Mon, 28 Nov 2005 13:42:32 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id NAA12199 for imss@ietf.org; Mon, 28 Nov 2005 13:42:32 -0800 (PST) From: Keith McCloghrie Message-Id: <200511282142.NAA12199@cisco.com> To: imss@ietf.org Date: Mon, 28 Nov 2005 13:42:32 -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: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Content-Transfer-Encoding: 7bit Subject: [imss] I-D ACTION:draft-kzm-imss-fc-fcs-mib-00.txt (fwd) 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 FYI. Keith. --------------- Forwarded message: > From: Internet-Drafts@ietf.org > To: i-d-announce@ietf.org > Message-Id: > Date: Mon, 28 Nov 2005 15:50:02 -0500 > Subject: I-D ACTION:draft-kzm-imss-fc-fcs-mib-00.txt > > --NextPart > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Fibre-Channel Fabric Configuration Server MIB > Author(s) : C. DeSanti, et al. > Filename : draft-kzm-imss-fc-fcs-mib-00.txt > Pages : 50 > Date : 2005-11-28 > > 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 Fabric Configuration Server function of a Fibre Channel > network. At present, this memo is a work item of T11.5 > (http://www.t11.org). The plan is that it will later be a work item > of the IETF's IMSS working group. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-kzm-imss-fc-fcs-mib-00.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-kzm-imss-fc-fcs-mib-00.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-kzm-imss-fc-fcs-mib-00.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. > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Nov 28 16:43:46 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 1Egqmo-000221-G2; Mon, 28 Nov 2005 16:43:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Egqmn-000217-Kq for imss@megatron.ietf.org; Mon, 28 Nov 2005 16:43:45 -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 QAA24906 for ; Mon, 28 Nov 2005 16:43:00 -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 1Egr6i-0005Gj-8v for imss@ietf.org; Mon, 28 Nov 2005 17:04:21 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 28 Nov 2005 13:43:33 -0800 X-IronPort-AV: i="3.97,385,1125903600"; d="scan'208"; a="371149054:sNHT25017256" 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 jASLhWeS008358 for ; Mon, 28 Nov 2005 13:43:32 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id NAA12391 for imss@ietf.org; Mon, 28 Nov 2005 13:43:32 -0800 (PST) From: Keith McCloghrie Message-Id: <200511282143.NAA12391@cisco.com> To: imss@ietf.org Date: Mon, 28 Nov 2005 13:43:32 -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: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Subject: [imss] I-D ACTION:draft-kzm-imss-fc-rscn-mib-00.txt (fwd) 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 FYI. Keith. --------------- Forwarded message: > From: Internet-Drafts@ietf.org > To: i-d-announce@ietf.org > Message-Id: > Date: Mon, 28 Nov 2005 15:50:02 -0500 > Subject: I-D ACTION:draft-kzm-imss-fc-rscn-mib-00.txt > > --NextPart > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Fibre Channel Registered State Change Notification (RSCN) MIB > Author(s) : C. DeSanti, et al. > Filename : draft-kzm-imss-fc-rscn-mib-00.txt > Pages : 23 > Date : 2005-11-28 > > 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 management of Fibre Channel's Registered State Change > Notifications (RSCNs). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-kzm-imss-fc-rscn-mib-00.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-kzm-imss-fc-rscn-mib-00.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-kzm-imss-fc-rscn-mib-00.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. > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Nov 28 19:03: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 1EgsxZ-00032S-W0; Mon, 28 Nov 2005 19:03:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EgsxY-00032K-P0 for imss@megatron.ietf.org; Mon, 28 Nov 2005 19:03:00 -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 TAA12307 for ; Mon, 28 Nov 2005 19:02:17 -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 1EgtHW-0002Yu-2r for imss@ietf.org; Mon, 28 Nov 2005 19:23:39 -0500 Received: from mailhub.lss.emc.com (uraeus.lss.emc.com [10.254.144.14]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.6) with ESMTP id jAT02m8R023443; Mon, 28 Nov 2005 19:02:48 -0500 (EST) 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.6) with ESMTP id jAT02k75010445; Mon, 28 Nov 2005 19:02:46 -0500 (EST) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Mon, 28 Nov 2005 19:02:46 -0500 Message-ID: To: imss@ietf.org Date: Mon, 28 Nov 2005 19:02:44 -0500 Importance: high X-Priority: 1 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.11.28.29 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, __HAS_X_PRIORITY 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.8 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: bwijnen@lucent.com, Black_David@emc.com Subject: [imss] imss WG Last Call: Routing Information, FSPF and Virtual Fabric M IBs 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 This is to announce an imss WG Last Call on the following three MIB drafts: Fibre-Channel Routing Information MIB draft-ietf-imss-fc-rtm-mib-01.txt MIB for Fibre-Channel's Fabric Shortest Path First Protocol draft-ietf-imss-fc-fspf-mib-01.txt The Virtual Fabrics MIB draft-ietf-imss-fc-vf-mib-00.txt Note that the Virtual Fabrics MIB is not the initial imss WG draft of this MIB despite its -00 version number. Due to some confusion, it was necessary to change the name of the draft for this MIB from its previous name, which was also an imss WG draft. That name change is recorded in the IETF draft tracker: https://datatracker.ietf.org/public/pidtracker.cgi This WG Last Call will run through 12 midnight Eastern Time on Sunday, December 18, 2005 (your WG chair hopes to deal with Last Call results on Monday, December 19th or shortly thereafter). Technical comments *must* be sent to the imss mailing list. Editorial comments may be sent directly to the draft editors (but please cc: me): Routing Information and FSPF MIBs: Keith McCloghrie [kzm@cisco.com] Virtual Fabrics MIB: Scott Kipp [scott.kipp@mcdata.com] Thanks, --David (imss WG chair) ---------------------------------------------------- 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 From imss-bounces@ietf.org Wed Nov 30 15:51:22 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 1EhYvC-0001v2-KF; Wed, 30 Nov 2005 15:51:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhYu0-0001Ct-8a; Wed, 30 Nov 2005 15:50: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 PAA11419; Wed, 30 Nov 2005 15:49:22 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhZEJ-0002fe-OO; Wed, 30 Nov 2005 16:11:07 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EhYtu-0006sg-8Y; Wed, 30 Nov 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: Wed, 30 Nov 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-04.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-04.txt Pages : 38 Date : 2005-11-30 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-04.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-04.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-04.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-11-30114713.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-nsm-mib-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-11-30114713.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--