From imss-bounces@ietf.org Mon May 01 18:50:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FahDR-0005ua-WE; Mon, 01 May 2006 18:50:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FahDO-0005tp-35; Mon, 01 May 2006 18:50:02 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FahDN-0001Mb-Ov; Mon, 01 May 2006 18:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k41Mo1vP018031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 22:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FahDN-0002Gd-C5; Mon, 01 May 2006 18:50:01 -0400 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, 01 May 2006 18:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fspf-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: , 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 : MIB for Fibre-Channel's Fabric Shortest Path First Protocol Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-fspf-mib-03.txt Pages : 39 Date : 2006-5-1 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fspf-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-fspf-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-fspf-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: <2006-5-1153808.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-fspf-mib-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-fspf-mib-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-1153808.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 Tue May 02 09:29:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FauwC-0000ip-GX; Tue, 02 May 2006 09:29:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FauwA-0000cg-Ui for imss@ietf.org; Tue, 02 May 2006 09:29:10 -0400 Received: from test-iport-3.cisco.com ([171.71.176.78]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fauw9-0003lI-LB for imss@ietf.org; Tue, 02 May 2006 09:29:10 -0400 Received: from sj-core-2.cisco.com ([171.71.177.254]) by test-iport-3.cisco.com with ESMTP; 02 May 2006 06:29:09 -0700 Received: from cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k42DT9h0018140 for ; Tue, 2 May 2006 06:29:09 -0700 (PDT) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id GAA21154 for imss@ietf.org; Tue, 2 May 2006 06:28:49 -0700 (PDT) From: Keith McCloghrie Message-Id: <200605021328.GAA21154@cisco.com> Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fspf-mib-03.txt (fwd) To: imss@ietf.org Date: Tue, 2 May 2006 06:28:49 -0700 (PDT) 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: b19722fc8d3865b147c75ae2495625f2 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: , Errors-To: imss-bounces@ietf.org FYI. Some of the comments we received in the recent GenART review of draft-ietf-imss-fc-rtm-mib-03.txt also applied to draft-ietf-imss-fc-fspf-mib-02.txt. The below updated submission makes the consequent editorial changes. Keith. ------------- Forwarded message: > From: Internet-Drafts@ietf.org > To: i-d-announce@ietf.org > Date: Mon, 01 May 2006 18:50:01 -0400 > Cc: imss@ietf.org > Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fspf-mib-03.txt > > 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 : MIB for Fibre-Channel's Fabric Shortest Path First Protocol > Author(s) : C. DeSanti, et al. > Filename : draft-ietf-imss-fc-fspf-mib-03.txt > Pages : 39 > Date : 2006-5-1 > > 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fspf-mib-03.txt > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue May 02 12:27:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Faxix-00051P-KI; Tue, 02 May 2006 12:27:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Faxiw-00051H-Eo; Tue, 02 May 2006 12:27:42 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faxiw-0002eU-79; Tue, 02 May 2006 12:27:42 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k42GRfvP002899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 May 2006 16:27:42 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Faxiv-0005Hh-Rl; Tue, 02 May 2006 12:27:41 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Tue, 02 May 2006 12:27:41 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: imss@ietf.org Subject: [imss] Last Call: 'The Virtual Fabrics MIB' to Proposed Standard (draft-ietf-imss-fc-vf-mib) 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: , 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: - 'The Virtual Fabrics 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 2006-05-16. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-vf-mib-02.txt _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue May 16 09:57:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg02m-0004Pf-KR; Tue, 16 May 2006 09:57:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg02l-0004Pa-KQ for imss@ietf.org; Tue, 16 May 2006 09:56:59 -0400 Received: from mexforward.lss.emc.com ([168.159.213.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg02k-0007fH-E0 for imss@ietf.org; Tue, 16 May 2006 09:56:59 -0400 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 k4GDutFL003824 for ; Tue, 16 May 2006 09:56:56 -0400 (EDT) Received: from MAHO3MSX2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4GDuiTb021226 for ; Tue, 16 May 2006 09:56:55 -0400 (EDT) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Tue, 16 May 2006 09:56:43 -0400 Message-ID: From: Black_David@emc.com To: imss@ietf.org Date: Tue, 16 May 2006 09:56:08 -0400 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.3.0.1, Antispam-Data: 2006.5.16.63110 X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, 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.2 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [imss] FSPF and RTM MIBs approved 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: , Errors-To: imss-bounces@ietf.org The IESG approved the FSPF and RTM MIB drafts for publication as Proposed Standard RFCs last week. Formal announcements should be appearing shortly. Many thanks and congratulations to the authors. 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 Tue May 16 11:37:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg1c5-0007Y0-L6; Tue, 16 May 2006 11:37:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg1c4-0007Xp-Pc; Tue, 16 May 2006 11:37:32 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg1c4-0005jC-I2; Tue, 16 May 2006 11:37:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k4GFbT1I014530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 May 2006 15:37:29 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fg1c1-0000v5-10; Tue, 16 May 2006 11:37:29 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 16 May 2006 11:37:29 -0400 X-Spam-Score: 0.1 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'MIB for Fibre-Channel's Fabric Shortest Path First Protocol' 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: , Errors-To: imss-bounces@ietf.org The IESG has approved the following document: - 'MIB for Fibre-Channel's Fabric Shortest Path First Protocol ' as a Proposed Standard This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fspf-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 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 and for the Operations and Management Area by Bert Wijnen. Note to RFC Editor The following modificatione need to be introduced by the RFC Editor: 1) [FC-FAM-MIB] became [RFC4439] 2) [FC-RTM-MIB] included in the list of Normative References is not referenced in the text. Please take it out 3) Section 3, create sub-section 3.1 Replace OLD: 3. Short Overview of Fibre Channel With NEW: 3. Short Overview of Fibre Channel 3.1 Introduction 4) Section 3, create sub-section 3.2 Replace OLD: FSPF has four major components: a) A Hello protocol, used to establish connectivity with a ... With NEW: 3.2 FSPF Protocol FSPF has four major components: a) A Hello protocol, used to establish connectivity with a ... 5) Section 3, create sub-section 3.3 Replace OLD: The latest standard for an interconnecting Fabric containing multiple Fabric Switch elements is [FC-SW-4] (which replaces the previous ... With NEW: 3.3 Virtual Fabrics The latest standard for an interconnecting Fabric containing multiple Fabric Switch elements is [FC-SW-4] (which replaces the previous ... 6) Append to Section 1 the following paragraph: NEW: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 7) Add to Normative References the Following [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. IANA Note IANA is requested to make a MIB OID assignment for the T11-FC-FSPF- MIB module under the appropriate subtree. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue May 16 12:29:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg2QS-0006fk-Lr; Tue, 16 May 2006 12:29:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg2QR-0006fW-NX; Tue, 16 May 2006 12:29:35 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg2QR-0008So-Ec; Tue, 16 May 2006 12:29:35 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k4GGT7XO028859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 May 2006 16:29:08 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fg2Pz-0007HY-Qy; Tue, 16 May 2006 12:29:07 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 16 May 2006 12:29:07 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'Fibre-Channel Routing Information 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: , Errors-To: imss-bounces@ietf.org The IESG has approved the following document: - 'Fibre-Channel Routing Information 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 Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-rtm-mib-04.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 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 and for the Operations and Management Area by Bert Wijnen. Note to RFC Editor Please make the following changes: 1) Append to Section 1 the following paragraph: NEW: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 2) Add to Normative References the Following [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 3) In Section 12: OLD: It is recommended that implementors consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT recommended. Instead, it is recommended to deploy SNMPv3 and to enable cryptographic security. NEW: It is RECOMMENDED that implementors consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. 4) Section 3, create sub-section 3.1 Replace OLD: 3. Short Overview of Fibre Channel With NEW: 3. Short Overview of Fibre Channel 3.1 Introduction 5) Section 3, create sub-section 3.2 Replace OLD: The routing of frames within the Fabric is normally based on the standard routing protocol, called the Fabric Shortest Path First ... With NEW: 3.2 Routing Protocols The routing of frames within the Fabric is normally based on the standard routing protocol, called the Fabric Shortest Path First ... 6) Section 3, create sub-section 3.3 Replace OLD: The latest standard for an interconnecting Fabric containing multiple Fabric Switch elements is [FC-SW-4] (which replaces the previous ... With NEW: 3.3 Virtual Fabrics The latest standard for an interconnecting Fabric containing multiple Fabric Switch elements is [FC-SW-4] (which replaces the previous ... IANA Note IANA is requested to make an MIB OID assignment for the T11-FC-ROUTE- MIB module under mib-2 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue May 16 13:35:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3SX-00017z-7X; Tue, 16 May 2006 13:35:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3SW-00017u-3w for imss@ietf.org; Tue, 16 May 2006 13:35:48 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg3ST-0003A3-Na for imss@ietf.org; Tue, 16 May 2006 13:35:48 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4GHYbWR027443 for ; Tue, 16 May 2006 13:34:37 -0400 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 Date: Tue, 16 May 2006 20:35:43 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Protocol Action: 'Fibre-Channel Routing Information MIB' to Proposed Standard Thread-Index: AcZ5Be6cPIMY0vFgTH2e+UR/OsL+NQACRPxA From: "Romascanu, Dan \(Dan\)" To: "imss mailing list" X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Subject: [imss] RE: Protocol Action: 'Fibre-Channel Routing Information 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: , Errors-To: imss-bounces@ietf.org Thanks and congratulations to the editor and to the Working Group for completing this work.=20 Dan =20 =20 > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org]=20 > Sent: Tuesday, May 16, 2006 7:29 PM > To: IETF-Announce > Cc: imss mailing list; Internet Architecture Board; imss=20 > chair; RFC Editor > Subject: Protocol Action: 'Fibre-Channel Routing Information=20 > MIB' to Proposed Standard=20 >=20 > The IESG has approved the following document: >=20 > - 'Fibre-Channel Routing Information MIB ' > as a Proposed Standard >=20 > This document is the product of the Internet and Management=20 > Support for Storage > =20 > Working Group.=20 >=20 > The IESG contact persons are Dan Romascanu and David Kessens. >=20 > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-rtm-mib-04.txt >=20 > Technical Summary > =20 > This memo defines a portion of the Management Information=20 > Base (MIB) > for use with network management protocols in the Internet=20 > community. > In particular, it describes managed objects for information related > to routing within a Fibre Channel fabric which is=20 > independent of the > usage of a particular routing protocol. >=20 > Working Group Summary > =20 > This document was reviewed in the IMSS WG and in Technical=20 > Committee > T11 (the official Fibre Channel standards body). T11 voted to > recommend a prior version of this document to the IETF.=20 >=20 > Protocol Quality > =20 > The protocol has been reviewed for the imss WG by Keith=20 > McCloghrie and > for the Operations and Management Area by Bert Wijnen. >=20 > Note to RFC Editor >=20 > Please make the following changes: > =20 > 1) Append to Section 1 the following paragraph: >=20 > NEW: >=20 > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",=20 > "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and=20 > "OPTIONAL" in this > document are to be interpreted as described in RFC 2119. >=20 > 2) Add to Normative References the Following >=20 > [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate > Requirement Levels", BCP 14, RFC 2119, March 1997. >=20 > 3) In Section 12: >=20 > OLD: >=20 > It is recommended that implementors consider the security=20 > features as > provided by the SNMPv3 framework (see [RFC3410], section 8), > including full support for the SNMPv3 cryptographic mechanisms (for > authentication and privacy). >=20 > Further, deployment of SNMP versions prior to SNMPv3 is NOT > recommended. Instead, it is recommended to deploy SNMPv3 and to > enable cryptographic security. >=20 > NEW:=20 >=20 > It is RECOMMENDED that implementors consider the security=20 > features as > provided by the SNMPv3 framework (see [RFC3410], section 8), > including full support for the SNMPv3 cryptographic mechanisms (for > authentication and privacy). >=20 > Further, deployment of SNMP versions prior to SNMPv3 is NOT > RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to > enable cryptographic security. >=20 > 4) Section 3, create sub-section 3.1 >=20 > Replace OLD:=20 >=20 > 3. Short Overview of Fibre Channel >=20 > With NEW: >=20 > 3. Short Overview of Fibre Channel >=20 > 3.1 Introduction >=20 > 5) Section 3, create sub-section 3.2 >=20 > Replace OLD:=20 >=20 > The routing of frames within the Fabric is normally based on the > standard routing protocol, called the Fabric Shortest Path First > ... >=20 > With NEW: >=20 > 3.2 Routing Protocols >=20 > The routing of frames within the Fabric is normally based on the > standard routing protocol, called the Fabric Shortest Path First > ... >=20 > 6) Section 3, create sub-section 3.3 >=20 > Replace OLD:=20 >=20 > The latest standard for an interconnecting Fabric=20 > containing multiple > Fabric Switch elements is [FC-SW-4] (which replaces the previous > ... >=20 > With NEW: >=20 > 3.3 Virtual Fabrics >=20 > The latest standard for an interconnecting Fabric=20 > containing multiple > Fabric Switch elements is [FC-SW-4] (which replaces the previous > ... >=20 > IANA Note >=20 > IANA is requested to make an MIB OID assignment for the=20 > T11-FC-ROUTE- MIB module under mib-2 >=20 >=20 >=20 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue May 16 13:39:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3Vb-0002ML-00; Tue, 16 May 2006 13:38:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3VZ-0002MG-Mo for imss@ietf.org; Tue, 16 May 2006 13:38:57 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg3VZ-0003JA-Bl for imss@ietf.org; Tue, 16 May 2006 13:38:57 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4GHbmPW031969 for ; Tue, 16 May 2006 13:37:49 -0400 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 Date: Tue, 16 May 2006 20:38:53 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Protocol Action: 'MIB for Fibre-Channel's Fabric Shortest Path First Protocol' to Proposed Standard Thread-Index: AcZ4/q5/+ZJYhG7cTMaxIKCLdaVymAAEMBGg From: "Romascanu, Dan \(Dan\)" To: "imss mailing list" X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Subject: [imss] RE: Protocol Action: 'MIB for Fibre-Channel's Fabric Shortest Path First Protocol' 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: , Errors-To: imss-bounces@ietf.org Thanks and congratulations to the editors and to the WGs for the completion of this work. Dan =20 =20 > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org]=20 > Sent: Tuesday, May 16, 2006 6:37 PM > To: IETF-Announce > Cc: imss mailing list; Internet Architecture Board; imss=20 > chair; RFC Editor > Subject: Protocol Action: 'MIB for Fibre-Channel's Fabric=20 > Shortest Path First Protocol' to Proposed Standard=20 >=20 > The IESG has approved the following document: >=20 > - 'MIB for Fibre-Channel's Fabric Shortest Path First Protocol ' > as a Proposed Standard >=20 > This document is the product of the Internet and Management=20 > Support for Storage > =20 > Working Group.=20 >=20 > The IESG contact persons are Dan Romascanu and David Kessens. >=20 > A URL of this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fspf-mib-03.txt >=20 > Technical Summary > =20 > This memo defines a portion of the Management Information=20 > Base (MIB) > for use with network management protocols in the Internet=20 > community. > In particular, it describes managed objects for information related > to the Fibre Channel network's Fabric Shortest Path First (FSPF) > routing protocol. > =20 > Working Group Summary > =20 > This document was reviewed in the IMSS WG and in Technical=20 > Committee > T11 (the official Fibre Channel standards body). T11 voted to > recommend a prior version of this document to the IETF. >=20 > Protocol Quality > =20 > The protocol has been reviewed for the imss WG by Keith=20 > McCloghrie and=20 > for the Operations and Management Area by Bert Wijnen. >=20 > Note to RFC Editor > =20 > The following modificatione need to be introduced by the RFC Editor: >=20 > 1) [FC-FAM-MIB] became [RFC4439] >=20 > 2) [FC-RTM-MIB] included in the list of Normative References=20 > is not referenced in the text. Please take it out =20 >=20 > 3) Section 3, create sub-section 3.1 >=20 > Replace OLD:=20 >=20 > 3. Short Overview of Fibre Channel >=20 > With NEW: >=20 > 3. Short Overview of Fibre Channel >=20 > 3.1 Introduction >=20 > 4) Section 3, create sub-section 3.2 >=20 > Replace OLD:=20 >=20 > FSPF has four major components: >=20 > a) A Hello protocol, used to establish connectivity with a > ... >=20 > With NEW: >=20 > 3.2 FSPF Protocol >=20 > FSPF has four major components: >=20 > a) A Hello protocol, used to establish connectivity with a > ... >=20 > 5) Section 3, create sub-section 3.3 >=20 > Replace OLD:=20 >=20 > The latest standard for an interconnecting Fabric=20 > containing multiple > Fabric Switch elements is [FC-SW-4] (which replaces the previous > ... >=20 > With NEW: >=20 > 3.3 Virtual Fabrics >=20 > The latest standard for an interconnecting Fabric=20 > containing multiple > Fabric Switch elements is [FC-SW-4] (which replaces the previous > ... >=20 > 6) Append to Section 1 the following paragraph: >=20 > NEW: >=20 > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",=20 > "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and=20 > "OPTIONAL" in this > document are to be interpreted as described in RFC 2119. >=20 > 7) Add to Normative References the Following >=20 > [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate > Requirement Levels", BCP 14, RFC 2119, March 1997. >=20 > IANA Note >=20 > IANA is requested to make a MIB OID assignment for the T11-FC-FSPF- > MIB module under the appropriate subtree. >=20 >=20 >=20 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss