From imss-bounces@ietf.org Mon Jan 02 14:21:08 2006 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 1EtVEy-0001JJ-FZ; Mon, 02 Jan 2006 14:21:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtVEw-0001HY-So for imss@megatron.ietf.org; Mon, 02 Jan 2006 14:21: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 OAA04371 for ; Mon, 2 Jan 2006 14:19:54 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtVK4-000288-0y for imss@ietf.org; Mon, 02 Jan 2006 14:26:25 -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 k02JKuVO008337 for ; Mon, 2 Jan 2006 13:20:57 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Mon, 2 Jan 2006 20:20:56 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508F18048@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Imss (E-mail)" Date: Mon, 2 Jan 2006 20:20: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: cab78e1e39c4b328567edb48482b6a69 Subject: [imss] FW: COMMENT: 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 -----Original Message----- From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com] Sent: Monday, January 02, 2006 19:15 To: imss@ietf.org Cc: Wijnen, Bert (Bert); Russ Housley (E-mail) Subject: FW: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Redirecting to the correct WG. -- Rich -----Original Message----- From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf Of Wijnen, Bert (Bert) Sent: Monday, January 02, 2006 7:48 AM To: Russ Housley (E-mail) Cc: Ipcdn (E-mail) Subject: [ipcdn] FW: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Sharp eyes Russ! I have "fixed" it with a note to RFC-Editor. Bert -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of Russ Housley Sent: Monday, January 02, 2006 00:00 To: iesg@ietf.org Subject: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Fibre Channel Fabric Address Manager MIB (Proposed Standard) COMMENT Section 12: s/t11FamRcFabricNotifyEnabl/t11FamRcFabricNotifyEnable/ _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Jan 03 10:07:10 2006 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 1Etnkk-00035O-8b; Tue, 03 Jan 2006 10:07:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtUDF-0003na-4A for imss@megatron.ietf.org; Mon, 02 Jan 2006 13:15:17 -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 NAA28490 for ; Mon, 2 Jan 2006 13:14:02 -0500 (EST) Received: from paoakoavas09.cable.comcast.com ([208.17.35.58] helo=cable.comcast.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtUIL-0000Sa-Uw for imss@ietf.org; Mon, 02 Jan 2006 13:20:35 -0500 Received: from ([10.20.62.12]) by paoakoavas09.cable.comcast.com with ESMTP id KP-TDCH7.15990784; Mon, 02 Jan 2006 13:14:41 -0500 Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by PACDCEXCRLY02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 2 Jan 2006 13:14:40 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 2 Jan 2006 13:14:40 -0500 Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CF4AA@PACDCEXCMB01.cable.comcast.com> Thread-Topic: FW: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Thread-Index: AcYPm2WvuMOh4PgoTJe5vigbsP+ENQAKye1A From: "Woundy, Richard" To: X-OriginalArrivalTime: 02 Jan 2006 18:14:40.0939 (UTC) FILETIME=[6636EFB0:01C60FC8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 03 Jan 2006 10:07:08 -0500 Cc: "Wijnen, Bert \(Bert\)" , "Russ Housley \(E-mail\)" Subject: [imss] FW: COMMENT: 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 Redirecting to the correct WG. -- Rich -----Original Message----- From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf Of Wijnen, Bert (Bert) Sent: Monday, January 02, 2006 7:48 AM To: Russ Housley (E-mail) Cc: Ipcdn (E-mail) Subject: [ipcdn] FW: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Sharp eyes Russ! I have "fixed" it with a note to RFC-Editor. Bert -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of Russ Housley Sent: Monday, January 02, 2006 00:00 To: iesg@ietf.org Subject: COMMENT: draft-ietf-imss-fc-fam-mib-03.txt Fibre Channel Fabric Address Manager MIB (Proposed Standard) COMMENT Section 12: s/t11FamRcFabricNotifyEnabl/t11FamRcFabricNotifyEnable/ _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Jan 05 11:13:43 2006 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 1EuXkF-0008MH-OY; Thu, 05 Jan 2006 11:13:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuXkE-0008MC-3e for imss@megatron.ietf.org; Thu, 05 Jan 2006 11:13:42 -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 LAA03117 for ; Thu, 5 Jan 2006 11:12:27 -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 1EuXpt-0008AJ-In for imss@ietf.org; Thu, 05 Jan 2006 11:19:36 -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 k05GDR3f008016 for ; Thu, 5 Jan 2006 11:13:27 -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 k05GDNTW012465 for ; Thu, 5 Jan 2006 11:13:25 -0500 (EST) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 5 Jan 2006 11:13:22 -0500 Message-ID: To: imss@ietf.org Date: Thu, 5 Jan 2006 11:13: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: 2006.1.5.14 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: 7d33c50f3756db14428398e2bdedd581 Subject: [imss] New versions of Routing Info, Virtual Fabrics MIBs coming 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 After conclusion of WG Last Call, some problems have been found with references in these two MIBs (missing references and/or bad citations in the MIB). New versions of these two MIBs are coming to correct these and a few typos - there is no change to actual MIB content. I will be submitting the publication requests (sending the MIBs to the ADs/IESG for further review) shortly after they appear. The FSPF MIB publication request will be submitted shortly. Copies of all requests will appear on the mailing list. 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 Thu Jan 05 11:28:02 2006 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 1EuXy6-0004Hi-4q; Thu, 05 Jan 2006 11:28:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuXy4-0004H1-Ci; Thu, 05 Jan 2006 11:28: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 LAA04979; Thu, 5 Jan 2006 11:26:45 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuY3l-0000Gu-Tg; Thu, 05 Jan 2006 11:33:55 -0500 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 05 Jan 2006 08:27:50 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k05GRnc1009582; Thu, 5 Jan 2006 08:27:49 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA22957; Thu, 5 Jan 2006 08:27:49 -0800 (PST) From: Keith McCloghrie Message-Id: <200601051627.IAA22957@cisco.com> To: internet-drafts@ietf.org (Internet Drafts Submissions) Date: Thu, 5 Jan 2006 08:27:49 -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: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 7bit Cc: imss@ietf.org Subject: [imss] submission of draft-ietf-imss-fc-rtm-mib-02.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 Please accept this submission of an updated I-D. You can find the text at: ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-rtm-mib-02.txt Thanks, Keith. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Jan 05 16:25:27 2006 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 1Eucbv-0005aa-Fm; Thu, 05 Jan 2006 16:25:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eucbu-0005aU-DV for imss@megatron.ietf.org; Thu, 05 Jan 2006 16:25: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 QAA22309 for ; Thu, 5 Jan 2006 16:24:09 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Euche-0006Me-Dy for imss@ietf.org; Thu, 05 Jan 2006 16:31:23 -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 k05LPJMC014179; Thu, 5 Jan 2006 15:25:19 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Thu, 5 Jan 2006 22:25:17 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508FC8C12@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Keith McCloghrie (E-mail)" Date: Thu, 5 Jan 2006 17:58:52 +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: 2.9 (++) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: "Margaret Wasserman \(E-mail\)" , "Imss \(E-mail\)" Subject: [imss] DISCUSS on 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 and WG, Margaret Wasserman: Discuss: [2006-01-05] Is there a reason why this MIB includes IP addresses stored as 16-byte octet strings, rather than as InetAddress objects? (e.g. t11NsRegNodeIpAddress) I guess the answer is in REFERENCE "ANSI INCITS 387-2004, Fibre Channel - Generic Services-4 (FC-GS-4)" Or you may have answered it in an earlier email. But I am in the middle of the IESG conf call now, so won't get to go check it untill later. Maybe you have the answer ready right from the top of your head. Bert _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Jan 05 17:55:47 2006 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 1Eue1L-0000zp-HD; Thu, 05 Jan 2006 17:55:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eue1K-0000zG-2p for imss@megatron.ietf.org; Thu, 05 Jan 2006 17:55: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 RAA05539 for ; Thu, 5 Jan 2006 17:54:30 -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 1Eue74-00026F-Ry for imss@ietf.org; Thu, 05 Jan 2006 18:01:44 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 05 Jan 2006 14:55:35 -0800 X-IronPort-AV: i="3.99,335,1131350400"; d="scan'208"; a="387893686:sNHT30429800" 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 k05MtYjt014092; Thu, 5 Jan 2006 14:55:35 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA08343; Thu, 5 Jan 2006 14:50:50 -0800 (PST) From: Keith McCloghrie Message-Id: <200601052250.OAA08343@cisco.com> To: bwijnen@lucent.com Date: Thu, 5 Jan 2006 14:50:50 -0800 (PST) In-Reply-To: from "Wijnen, Bert (Bert)" at Jan 05, 2006 05:58:52 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: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Cc: margaret@thingmagic.com, imss@ietf.org, Keith McCloghrie Subject: [imss] Re: DISCUSS on 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 Bert/Margaret, Tha answer is documented in section 5.5 of draft-ietf-imss-fc-nsm-mib-05.txt which says: The objects defined in the t11NsRegTable represent the values registered with the Name Server. The SNMP agent MUST report the actual values, even if they are incorrectly formatted. This is the reason why, for example, the two objects which represent IP- addresses, t11NsNodeIpAddress and t11NsPortIpAddress, have the SYNTAX of OCTET STRING, so that they are able to represent invalid values (which could not be represented using InetAddressType and InetAddress). Keith. > Keith and WG, > > Margaret Wasserman: > Discuss: > [2006-01-05] Is there a reason why this MIB includes IP > addresses stored as 16-byte octet strings, rather than > as InetAddress objects? (e.g. t11NsRegNodeIpAddress) > > I guess the answer is in > REFERENCE > "ANSI INCITS 387-2004, Fibre Channel - Generic > Services-4 (FC-GS-4)" > > Or you may have answered it in an earlier email. > > But I am in the middle of the IESG conf call now, so won't get to > go check it untill later. Maybe you have the answer ready > right from the top of your head. > > Bert > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Jan 05 18:50:16 2006 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 1Eues4-0006ka-IU; Thu, 05 Jan 2006 18:50:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Euerq-0006ga-QU; Thu, 05 Jan 2006 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 SAA12783; Thu, 5 Jan 2006 18:48:46 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Euexc-0004CQ-TU; Thu, 05 Jan 2006 18:56:01 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Euerp-0003zV-KA; Thu, 05 Jan 2006 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: Thu, 05 Jan 2006 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-fc-rtm-mib-02.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 Routing Information MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-rtm-mib-02.txt Pages : 22 Date : 2006-1-5 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 routing within a Fibre Channel fabric which is independent of the usage of a particular routing protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-rtm-mib-02.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-rtm-mib-02.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-rtm-mib-02.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: <2006-1-5154446.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-rtm-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-rtm-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-1-5154446.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 Jan 06 12:30:30 2006 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 1EuvQ6-0006da-MB; Fri, 06 Jan 2006 12:30:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuvQ5-0006dI-St for imss@megatron.ietf.org; Fri, 06 Jan 2006 12:30:29 -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 MAA16669 for ; Fri, 6 Jan 2006 12:29:13 -0500 (EST) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuvW0-0000Sc-Es for imss@ietf.org; Fri, 06 Jan 2006 12:36:37 -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 k06HULcW022161 for ; Fri, 6 Jan 2006 11:30:22 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Fri, 6 Jan 2006 18:30:19 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508FC8D22@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Imss (E-mail)" Date: Fri, 6 Jan 2006 12:49:56 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.7 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Subject: [imss] FW: DISCUSS on 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 WG, the DISCUSS has been cleared, and so the doc is approved by IESG. Formal announcement will follow in the next few days by IESG secretaray. And the FAM MIB oducmnet was also approved yesterday. Congrats, and thanks to the authors/editors. Bert -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of Margaret Wasserman Sent: Friday, January 06, 2006 02:05 To: 'Wijnen, Bert (Bert)'; 'Keith McCloghrie (E-mail)' Cc: 'Iesg (E-mail)' Subject: RE: DISCUSS on Yes. I'm sorry that I didn't find that in my review. I have removed my discuss. Margaret > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On > Behalf Of Wijnen, Bert (Bert) > Sent: Thursday, January 05, 2006 6:39 PM > To: Margaret Wasserman (E-mail); Keith McCloghrie (E-mail) > Cc: Iesg (E-mail) > Subject: FW: DISCUSS on > > Thanks Keith. > > Margareth, I think this allows you to clear your DISCUSS, right? > > Bert > > -----Original Message----- > From: Keith McCloghrie [mailto:kzm@cisco.com] > Sent: Thursday, January 05, 2006 23:51 > To: bwijnen@lucent.com > Cc: imss@ietf.org; margaret@thingmagic.com; kzm@cisco.com > Subject: Re: DISCUSS on > > > Bert/Margaret, > > Tha answer is documented in section 5.5 of > draft-ietf-imss-fc-nsm-mib-05.txt which says: > > The objects defined in the t11NsRegTable represent the values > registered with the Name Server. The SNMP agent MUST report the > actual values, even if they are incorrectly formatted. This is the > reason why, for example, the two objects which represent IP- > addresses, t11NsNodeIpAddress and t11NsPortIpAddress, have > the SYNTAX > of OCTET STRING, so that they are able to represent invalid values > (which could not be represented using InetAddressType and > InetAddress). > > Keith. > > > > Keith and WG, > > > > Margaret Wasserman: > > Discuss: > > [2006-01-05] Is there a reason why this MIB includes IP > > addresses stored as 16-byte octet strings, rather than > > as InetAddress objects? (e.g. t11NsRegNodeIpAddress) > > > > I guess the answer is in > > REFERENCE > > "ANSI INCITS 387-2004, Fibre Channel - Generic > > Services-4 (FC-GS-4)" > > > > Or you may have answered it in an earlier email. > > > > But I am in the middle of the IESG conf call now, so won't > get to go > > check it untill later. Maybe you have the answer ready > right from the > > top of your head. > > > > Bert > > > > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Fri Jan 06 19:37:28 2006 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 1Ev25I-0001c8-B8; Fri, 06 Jan 2006 19:37:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ev25H-0001c3-Hn for imss@megatron.ietf.org; Fri, 06 Jan 2006 19:37: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 TAA28749 for ; Fri, 6 Jan 2006 19:36:11 -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 1Ev2BH-0000Nt-4V for imss@ietf.org; Fri, 06 Jan 2006 19:43:39 -0500 Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.1.0/Switch-3.1.7) with ESMTP id k070bID4017753 for ; Fri, 6 Jan 2006 19:37:18 -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 k070bFAe004721 for ; Fri, 6 Jan 2006 19:37:16 -0500 (EST) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 6 Jan 2006 19:37:15 -0500 Message-ID: To: imss@ietf.org Date: Fri, 6 Jan 2006 19:37:10 -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: 2006.1.6.31 X-PerlMx-Spam: Gauge=, SPAM=1%, Reasons='EMC_FROM_00+ -3, EMC_BODY_1+ -1, 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: 825e642946eda55cd9bc654a36dab8c2 Cc: Black_David@emc.com Subject: [imss] Publication Requested: FSPF MIB 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 RFC publication has just been requested for the FSPF MIB draft. The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt) is being used. Here is the PROTO writeup: MIB for Fibre-Channel's Fabric Shortest Path First Protocol draft-ietf-imss-fc-fspf-mib-01.txt Requested Publication Status: Proposed Standard PROTO shepherd: David L. Black (IMSS WG Chair) ------------------------------------------------------------------------ 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Yes. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Yes. 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, and the IMSS WG's MIB expert. Do you have any concerns about the depth or breadth of the reviews that have been performed? No. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, etc.)? Needs the usual IETF OPS Area MIB Doctor review. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? It's hard to distinguish the two cases due to somewhat thin WG membership. There is solid support for this document both in the WG and from T11. 1.f) [... not distributed to the WG ...] 1.g) Have the chairs verified that the document adheres to all of the ID nits? (see http://www.ietf.org/ID-Checklist.html). The online checker thinks some of the pages are 1 line too long - not worth revising the draft to address. The required copyright statement is present, although enough whitespace has been removed to fool the online checker. 1.h) Is the document split into normative and informative references? Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? (note here that the RFC editor will not publish an RFC with normative references to IDs, it will delay publication until all such IDs are also ready for publication as RFCs.) Yes. The normative references to Internet Drafts are: o draft-ietf-imss-fc-fam-mib-nn.txt - In RFC Editor's Queue o draft-ietf-imss-fc-rtm-mib-nn.txt - Publication is being requested at the same time as this MIB. 1.i) For Standards Track and BCP documents, the IESG approval announcement includes a write-up section with the following sections: * Technical Summary * Working Group Summary * Protocol Quality 1.j) Please provide such a write-up. Recent examples can be found in the "protocol action" announcements for approved documents. -- Technical Summary 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 Fabric Shortest Path First (FSPF) routing protocol. -- Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. -- Protocol Quality The protocol has been reviewed for the imss WG by Keith McCloghrie. An approval announcement will need to credit a MIB Doctor as having reviewed this for the IESG as Keith is both an author of this draft and the imss WG's MIB expert. ---------------------------------------------------- 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 Fri Jan 06 19:37:34 2006 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 1Ev25O-0001cb-F1; Fri, 06 Jan 2006 19:37:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ev25N-0001cW-Cb for imss@megatron.ietf.org; Fri, 06 Jan 2006 19:37: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 TAA28752 for ; Fri, 6 Jan 2006 19:36: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 1Ev2BN-0000Ny-0M for imss@ietf.org; Fri, 06 Jan 2006 19:43:45 -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.7) with ESMTP id k070bOnk018125 for ; Fri, 6 Jan 2006 19:37:24 -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 k070bLqF014282 for ; Fri, 6 Jan 2006 19:37:22 -0500 (EST) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 6 Jan 2006 19:37:21 -0500 Message-ID: To: imss@ietf.org Date: Fri, 6 Jan 2006 19:37:17 -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: 2006.1.6.31 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: 2857c5c041d6c02d7181d602c22822c8 Cc: Black_David@emc.com Subject: [imss] Publication Requested: RTM MIB 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 RFC publication has just been requested for the RTM MIB draft. The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt) is being used. Here is the PROTO writeup: Fibre-Channel Routing Information MIB draft-ietf-imss-fc-rtm-mib-02.txt Requested Publication Status: Proposed Standard PROTO shepherd: David L. Black (IMSS WG Chair) ------------------------------------------------------------------------ 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Yes. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Yes. 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, and the IMSS WG's MIB expert. Do you have any concerns about the depth or breadth of the reviews that have been performed? No. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, etc.)? Needs the usual IETF OPS Area MIB Doctor review. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? It's hard to distinguish the two cases due to somewhat thin WG membership. There is solid support for this document both in the WG and from T11. 1.f) [... not distributed to the WG ...] 1.g) Have the chairs verified that the document adheres to all of the ID nits? (see http://www.ietf.org/ID-Checklist.html). The online checker thinks some of the pages are 1 line too long - not worth revising the draft to address. 1.h) Is the document split into normative and informative references? Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? (note here that the RFC editor will not publish an RFC with normative references to IDs, it will delay publication until all such IDs are also ready for publication as RFCs.) Yes. The normative references to Internet Drafts are: o draft-ietf-imss-fc-fam-mib-nn.txt - In RFC Editor's Queue o draft-ietf-imss-fc-fspf-mib-nn.txt - Publication is being requested at the same time as this MIB. 1.i) For Standards Track and BCP documents, the IESG approval announcement includes a write-up section with the following sections: * Technical Summary * Working Group Summary * Protocol Quality 1.j) Please provide such a write-up. Recent examples can be found in the "protocol action" announcements for approved documents. -- Technical Summary 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 routing within a Fibre Channel fabric which is independent of the usage of a particular routing protocol. -- Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. -- Protocol Quality The protocol has been reviewed for the imss WG by Keith McCloghrie. An approval announcement will need to credit a MIB Doctor as having reviewed this for the IESG as Keith is both an author of this draft and the imss WG's MIB expert. ---------------------------------------------------- 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 Jan 09 12:52:49 2006 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 1Ew1CL-0001mg-0Z; Mon, 09 Jan 2006 12:52:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ew1CE-0001k1-OO; Mon, 09 Jan 2006 12:52:42 -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 MAA06779; Mon, 9 Jan 2006 12:51:22 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ew1Il-0005nU-QN; Mon, 09 Jan 2006 12:59:27 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ew1CD-0000oc-5x; Mon, 09 Jan 2006 12:52:41 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 09 Jan 2006 12:52:41 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'Fibre-Channel Name Server MIB' 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: - 'Fibre-Channel Name Server MIB ' as a Proposed Standard 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-fc-nsm-mib-05.txt Technical Summary 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. Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Protocol Quality The protocol has been reviewed by Keith McCloghrie for the imss WG. Keith is one in the group of authors. Orly Nicklass did independent MIB Doctor review and Bert Wijnen reviewed this document for the IESG. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Mon Jan 09 16:02:44 2006 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 1Ew4A8-0005qm-Ti; Mon, 09 Jan 2006 16:02:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ew4A3-0005pR-AJ; Mon, 09 Jan 2006 16:02:40 -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 QAA22759; Mon, 9 Jan 2006 16:01:20 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ew4Gc-0003oL-9Q; Mon, 09 Jan 2006 16:09:26 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ew49w-0006O9-4s; Mon, 09 Jan 2006 16:02:32 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 09 Jan 2006 16:02:32 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'Fibre Channel Fabric Address Manager MIB' 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: - 'Fibre Channel Fabric Address Manager MIB ' as a Proposed Standard 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-fc-fam-mib-03.txt Technical Summary 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. Fabric Address Manager refers to the functionality of acquiring DomainID(s) as specified in [FC-SW-3], and managing Fibre Channel Identifiers as specified in [FC-FS]. Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Protocol Quality The protocol has been reviewed for the imss WG by Keith McCloghrie (who is one in the group of authors). Orly Nicklass did independent MIB doctor review and Bert Wijnen reviewed the document for the IESG. Note to RFC Editor - Section 7 is redundant with the back matter. So it is best deleted. - Fix typo (missing "e"), sect 12 page 40 OLD: t11FamRcFabricNotifyEnabl -- ability to enable/disable a notification. NEW: t11FamRcFabricNotifyEnable -- ability to enable/disable a notification. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Jan 25 20:48:27 2006 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 1F1wFP-0002Z6-Gc; Wed, 25 Jan 2006 20:48:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1wFN-0002X4-Nk; Wed, 25 Jan 2006 20:48:25 -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 UAA21960; Wed, 25 Jan 2006 20:46:54 -0500 (EST) Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1wPF-0005KN-3f; Wed, 25 Jan 2006 20:58:37 -0500 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k0Q1lT623197; Wed, 25 Jan 2006 17:47:29 -0800 (PST) Message-Id: <200601260147.k0Q1lT623197@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 25 Jan 2006 17:47:29 -0800 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Score: -14.6 (--------------) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: imss@ietf.org, rfc-editor@rfc-editor.org Subject: [imss] RFC 4338 on Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel 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 Request for Comments is now available in online RFC libraries. RFC 4338 Title: Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel Author(s): C. DeSanti, C. Carlson, R. Nixon Status: Standards Track Date: January 2006 Mailbox: cds@cisco.com, craig.carlson@qlogic.com, bob.nixon@emulex.com Pages: 33 Characters: 75541 Obsoletes: 3831, 2625 I-D Tag: draft-ietf-imss-ip-over-fibre-channel-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4338.txt This document specifies the way of encapsulating IPv6, IPv4, and Address Resolution Protocol (ARP) packets over Fibre Channel. This document also specifies 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 RFC 2625 and RFC 3831. This document is a product of the Internet and Management Support for Storage Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <060125174437.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc4338 --OtherAccess Content-Type: Message/External-body; name="rfc4338.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <060125174437.RFC@RFC-EDITOR.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 Jan 26 05:34:58 2006 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 1F24Sw-0007IF-Jm; Thu, 26 Jan 2006 05:34:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F24Sv-0007Hp-BN for imss@megatron.ietf.org; Thu, 26 Jan 2006 05:34:57 -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 FAA01658 for ; Thu, 26 Jan 2006 05:33:24 -0500 (EST) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F24cr-0006WP-Ax for imss@ietf.org; Thu, 26 Jan 2006 05:45:13 -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 k0QAYpXp002145 for ; Thu, 26 Jan 2006 04:34:52 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Thu, 26 Jan 2006 11:34:50 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550922CD4C@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Imss (E-mail)" Subject: FW: [imss] RFC 4338 on Transmission of IPv6, IPv4, and Address Re solution Protocol (ARP) Packets over Fibre Channel Date: Thu, 26 Jan 2006 11:34:47 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C62264.2108FC0E" X-Spam-Score: 0.0 (/) X-Scan-Signature: 0770535483960d190d4a0d020e7060bd 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 message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C62264.2108FC0E Content-Type: text/plain; charset="iso-8859-1" Congrats to the WG and authors/editors. Keep going! Bert -----Original Message----- From: imss-bounces@ietf.org [mailto:imss-bounces@ietf.org]On Behalf Of rfc-editor@rfc-editor.org Sent: Thursday, January 26, 2006 02:47 To: ietf-announce@ietf.org Cc: imss@ietf.org; rfc-editor@rfc-editor.org Subject: [imss] RFC 4338 on Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel A new Request for Comments is now available in online RFC libraries. RFC 4338 Title: Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel Author(s): C. DeSanti, C. Carlson, R. Nixon Status: Standards Track Date: January 2006 Mailbox: cds@cisco.com, craig.carlson@qlogic.com, bob.nixon@emulex.com Pages: 33 Characters: 75541 Obsoletes: 3831, 2625 I-D Tag: draft-ietf-imss-ip-over-fibre-channel-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4338.txt This document specifies the way of encapsulating IPv6, IPv4, and Address Resolution Protocol (ARP) packets over Fibre Channel. This document also specifies 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 RFC 2625 and RFC 3831. This document is a product of the Internet and Management Support for Storage Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ------_=_NextPart_000_01C62264.2108FC0E Content-Type: message/rfc822 To: Subject: Date: Thu, 26 Jan 2006 10:43:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C62264.2108FC0E" ------_=_NextPart_002_01C62264.2108FC0E Content-Type: text/plain ------_=_NextPart_002_01C62264.2108FC0E Content-Type: application/octet-stream; name="ATT03994.txt" Content-Disposition: attachment; filename="ATT03994.txt" Content-type: message/external-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <060125174437.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc4338 ------_=_NextPart_002_01C62264.2108FC0E Content-Type: message/external-body; site="in-notes"; dir="rfc4338.txt"; mode="ftp.isi.edu"; access-type="anon-ftp" ------_=_NextPart_002_01C62264.2108FC0E-- ------_=_NextPart_000_01C62264.2108FC0E Content-Type: text/plain; name="ATT03995.txt" Content-Disposition: attachment; filename="ATT03995.txt" _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss ------_=_NextPart_000_01C62264.2108FC0E 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_000_01C62264.2108FC0E-- From imss-bounces@ietf.org Thu Jan 26 15:51:05 2006 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 1F2E5B-0004Wp-H8; Thu, 26 Jan 2006 15:51:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2E4H-0004Ky-UO; Thu, 26 Jan 2006 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 PAA24047; Thu, 26 Jan 2006 15:48:37 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2EEF-0005WE-1x; Thu, 26 Jan 2006 16:00:28 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1F2E4A-0008OV-Ek; Thu, 26 Jan 2006 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: Thu, 26 Jan 2006 15:50:02 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-vf-mib-01.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-01.txt Pages : 21 Date : 2006-1-26 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-01.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-01.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-01.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: <2006-1-26151052.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-vf-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-vf-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-1-26151052.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 Jan 30 12:32:08 2006 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 1F3csq-0004qD-5g; Mon, 30 Jan 2006 12:32:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3cso-0004n8-Jj for imss@megatron.ietf.org; Mon, 30 Jan 2006 12:32: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 MAA11231 for ; Mon, 30 Jan 2006 12:30: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 1F3d3T-0003RK-L1 for imss@ietf.org; Mon, 30 Jan 2006 12:43:08 -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.7) with ESMTP id k0UHVmSe010650 for ; Mon, 30 Jan 2006 12:31:48 -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 k0UHUluT015167 for ; Mon, 30 Jan 2006 12:31:44 -0500 (EST) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jan 2006 12:30:43 -0500 Message-ID: To: imss@ietf.org Date: Mon, 30 Jan 2006 12:30:38 -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: 2006.01.30.084605 X-PerlMx-Spam: Gauge=, SPAM=1%, Reasons='EMC_FROM_00+ -3, EMC_BODY_1+ -1, EMC_FROM_0+ -0, 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: 093efd19b5f651b2707595638f6c4003 Cc: Black_David@emc.com Subject: [imss] Publication Requested: VF MIB 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 RFC publication has just been requested for the VF MIB draft. The PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt) is being used. Here is the PROTO writeup: PROTO writeup: The Virtual Fabrics MIB draft-ietf-imss-fc-vf-mib-01.txt Requested Publication Status: Proposed Standard PROTO shepherd: David L. Black (IMSS WG Chair) ------------------------------------------------------------------------ 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Yes. There are (at least) a couple of minor editing problems that can be addressed during MIB Doctor Review or after IETF Last Call: - A character has been dropped from the title of Section 7 - the title should be: The T11-FC-VIRTUAL-FABRIC-MIB Module (not -IRTUAL-) - The [FC-FAM-MIB] reference is out of date. The current version of that draft is draft-ietf-imss-fc-fam-mib-03.txt . 1.b) Has the document had adequate review from both key WG members and key non-WG members? Yes. 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, and the IMSS WG's MIB expert. Do you have any concerns about the depth or breadth of the reviews that have been performed? No. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, etc.)? Needs the usual IETF OPS Area MIB Doctor review. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? It's hard to distinguish the two cases due to somewhat thin WG membership. There is solid support for this document both in the WG and from T11. 1.f) [... not distributed to the WG ...] 1.g) Have the chairs verified that the document adheres to all of the ID nits? (see http://www.ietf.org/ID-Checklist.html). The online nits checker complains about a boilerplate paragraph being split across pages, which is not an actual problem. Everything else is fine. 1.h) Is the document split into normative and informative references? Yes. Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? (note here that the RFC editor will not publish an RFC with normative references to IDs, it will delay publication until all such IDs are also ready for publication as RFCs.) There is one normative reference to an Internet-Draft: draft-desanti-fc-fabric-addr-mgr-mib-0x.txt - As noted above, this draft has been replaced, and hence this reference should be to draft-ietf-imss-fc-fam-mib-03.txt, which is already in the RFC Editor's Queue. 1.i) For Standards Track and BCP documents, the IESG approval announcement includes a write-up section with the following sections: * Technical Summary * Working Group Summary * Protocol Quality 1.j) Please provide such a write-up. Recent examples can be found in the "protocol action" announcements for approved documents. -- Technical Summary 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 Fabric function. -- Working Group Summary This document was reviewed in the IMSS WG and in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. -- Protocol Quality The protocol has been reviewed for the IMSS WG by Keith McCloghrie. An approval announcement will need to credit a MIB Doctor as having reviewed this for the IESG as Keith is both an author of this draft and the IMSS WG's MIB expert. ---------------------------------------------------- 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