From owner-ipfc@standards.gadzoox.com Wed Jul 7 11:59:21 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11898 for ; Wed, 7 Jul 1999 11:59:20 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id IAA12453 for ipfc-list; Wed, 7 Jul 1999 08:53:55 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from gordan.pl.gadzoox.com (gordan.pl.gadzoox.com [209.95.220.16]) by standards.gadzoox.com (8.8.7/8.8.7) with ESMTP id IAA12450 for ; Wed, 7 Jul 1999 08:53:54 -0700 Received: by gordan.pl.gadzoox.com with Internet Mail Service (5.5.2448.0) id ; Wed, 7 Jul 1999 08:54:56 -0700 Message-ID: <312419998E3CD211A52900A0C991A47A117074@gordan.pl.gadzoox.com> From: Murali Rajagopal To: "'ipfc@standards.gadzoox.com'" Subject: RFC 2625 on IP and ARP over Fibre Channel Date: Wed, 7 Jul 1999 08:54:54 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BEC891.0E6EC58A" Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk 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_01BEC891.0E6EC58A Content-Type: text/plain; charset="iso-8859-1" Folks: We finally have an official RFC number. We have achieved the initial goal set for this WG. Thanks to all who have contributed to this effort. We still have other things in the pipe (MIBs, DRAFT STD for IPv4 over FC, IPv6 ?). We'll revisit the schedule for some of these items in Norway. Regards, Murali <> A new Request for Comments is now available in online RFC libraries. RFC 2625 Title: IP and ARP over Fibre Channel Author(s): M. Rajagopal, R. Bhagwat, W. Rickard Status: Proposed Standard Date: June 1999 Mailbox: murali@gadzoox.com , raj@gadzoox.com , wayne@gadzoox.com Pages: 63 Characters: 137741 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-ipfc-fibre-channel-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2625.txt The purpose of this document is to specify a way of encapsulating IP and Address Resolution Protocol(ARP) over Fibre Channel and also to describe a mechanism(s) for IP address resolution. This document is a product of the IP Over Fibre Channel 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.echo 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 Alegre Ramos 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_01BEC891.0E6EC58A Content-Type: message/rfc822 Content-Description: Untitled Attachment To: Subject: Date: Wed, 7 Jul 1999 08:54:56 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01BEC891.0E6EC58A" ------_=_NextPart_002_01BEC891.0E6EC58A Content-Type: text/plain ------_=_NextPart_002_01BEC891.0E6EC58A Content-Type: application/octet-stream; name="ATT02655.txt" Content-Disposition: attachment; filename="ATT02655.txt" Content-type: message/external-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <990706145733.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2625 ------_=_NextPart_002_01BEC891.0E6EC58A Content-Type: message/external-body; site="in-notes"; dir="rfc2625.txt"; mode="ftp.isi.edu"; access-type="anon-ftp" ------_=_NextPart_002_01BEC891.0E6EC58A-- ------_=_NextPart_000_01BEC891.0E6EC58A-- From owner-ipfc@standards.gadzoox.com Mon Jul 12 18:24:33 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20877 for ; Mon, 12 Jul 1999 18:24:30 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id PAA14900 for ipfc-list; Mon, 12 Jul 1999 15:19:28 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from nsg0.network.com (nsg0.network.com [129.191.1.2]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id PAA14897 for ; Mon, 12 Jul 1999 15:17:35 -0700 Received: from network.com (ulysses.network.com) by nsg0.network.com (4.1/1.34) id AA08013; Mon, 12 Jul 99 17:20:50 CDT Message-Id: <378A68CC.381C03E0@network.com> Date: Mon, 12 Jul 1999 17:14:36 -0500 From: Jeremy Swift Organization: StorageTek: StorageNet Business Group X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.10 i686) X-Accept-Language: en Mime-Version: 1.0 To: ipfc@standards.gadzoox.com, jeremy_swift@storagetek.com Subject: SNIA recommendations for changes to the FC Mgmt MIB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk Content-Transfer-Encoding: 7bit I would like to make the following recommendation for changes to the Fibre Channel Management MIB: Add the following enumeration: connUnitType storage-access-device (14) -- Jeremy Swift http://www.storagetek.com Software Development Phone: (612) 391-1241 StorageTek: SNBG (800) 328-9108 ext. 1241 jeremy_swift@storagetek.com Fax: (612) 391-1095 From owner-ipfc@standards.gadzoox.com Mon Jul 12 19:03:15 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21936 for ; Mon, 12 Jul 1999 19:03:14 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id PAA14913 for ipfc-list; Mon, 12 Jul 1999 15:58:39 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from gordan.pl.gadzoox.com (gordan.pl.gadzoox.com [209.95.220.16]) by standards.gadzoox.com (8.8.7/8.8.7) with ESMTP id PAA14910 for ; Mon, 12 Jul 1999 15:58:38 -0700 Received: by gordan.pl.gadzoox.com with Internet Mail Service (5.5.2448.0) id <3V5GQWG0>; Mon, 12 Jul 1999 15:59:38 -0700 Message-ID: <312419998E3CD211A52900A0C991A47A1C19A7@gordan.pl.gadzoox.com> From: Gavin Bowlby To: ipfc@standards.gadzoox.com, jeremy_swift@storagetek.com Subject: RE: SNIA recommendations for changes to the FC Mgmt MIB Date: Mon, 12 Jul 1999 15:59:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk Jeremy: What do you see as the differences between: connUnitType = storage-device(9), -- disk,cd,tape,etc connUnitType = storage-subsystem(11), -- raid, library, etc and your proposed value: connUnitType = storage-access-device (14) ? thanks, Gavin Bowlby Gadzoox Networks -----Original Message----- From: Jeremy Swift [mailto:jeremy.swift@nsg0.network.com] Sent: Monday, July 12, 1999 3:15 PM To: ipfc@standards.gadzoox.com; jeremy_swift@storagetek.com Subject: SNIA recommendations for changes to the FC Mgmt MIB I would like to make the following recommendation for changes to the Fibre Channel Management MIB: Add the following enumeration: connUnitType storage-access-device (14) -- Jeremy Swift http://www.storagetek.com Software Development Phone: (612) 391-1241 StorageTek: SNBG (800) 328-9108 ext. 1241 jeremy_swift@storagetek.com Fax: (612) 391-1095 From owner-ipfc@standards.gadzoox.com Mon Jul 12 22:27:58 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25770 for ; Mon, 12 Jul 1999 22:27:57 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id TAA14978 for ipfc-list; Mon, 12 Jul 1999 19:23:35 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from emcmail.lss.emc.com (emcmail.lss.emc.com [168.159.48.78]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id TAA14975; Mon, 12 Jul 1999 19:23:33 -0700 Received: from fishbowl02.emc.com (fishbowl02 [168.159.48.62]) by emcmail.lss.emc.com (8.9.3/8.9.3) with SMTP id WAA23847; Mon, 12 Jul 1999 22:26:15 -0400 (EDT) Received: by fishbowl02.emc.com with VINES-ISMTP; Mon, 12 Jul 1999 22:26:18 -0400 Date: Mon, 12 Jul 1999 22:26:18 -0400 Message-ID: X-Priority: 3 (Normal) To: , , From: "steven blumenau" Reply-To: Subject: Re: RE: SNIA recommendations for changes to the FC Mgmt MIB X-Incognito-SN: 1467 X-Incognito-Version: 5.0.1.89 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk Jeremy, I had the same question as Gavin. Also, the subject of the email was "SNIA recommendations...". Is this all the feedback from the SNIA on the newest rev ? thanks Steve - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - From: "Gavin Bowlby" Subject: RE: SNIA recommendations for changes to the FC Mgmt MIB Date: 07/12/99 19:56 Jeremy: What do you see as the differences between: connUnitType = storage-device(9), -- disk,cd,tape,etc connUnitType = storage-subsystem(11), -- raid, library, etc and your proposed value: connUnitType = storage-access-device (14) ? thanks, Gavin Bowlby Gadzoox Networks -----Original Message----- From: Jeremy Swift [mailto:jeremy.swift@nsg0.network.com] Sent: Monday, July 12, 1999 3:15 PM To: ipfc@standards.gadzoox.com; jeremy_swift@storagetek.com Subject: SNIA recommendations for changes to the FC Mgmt MIB I would like to make the following recommendation for changes to the Fibre Channel Management MIB: Add the following enumeration: connUnitType storage-access-device (14) -- Jeremy Swift http://www.storagetek.com Software Development Phone: (612) 391-1241 StorageTek: SNBG (800) 328-9108 ext. 1241 jeremy_swift@storagetek.com Fax: (612) 391-1095 From owner-ipfc@standards.gadzoox.com Tue Jul 13 10:49:01 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12707 for ; Tue, 13 Jul 1999 10:49:00 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id HAA15362 for ipfc-list; Tue, 13 Jul 1999 07:42:00 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from nsg0.network.com (nsg0.network.com [129.191.1.2]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id HAA15359; Tue, 13 Jul 1999 07:37:13 -0700 Received: from network.com (ulysses.network.com) by nsg0.network.com (4.1/1.34) id AA17146; Tue, 13 Jul 99 09:33:53 CDT Message-Id: <378B4CD6.B9C45CBE@network.com> Date: Tue, 13 Jul 1999 09:27:34 -0500 From: Jeremy Swift Organization: StorageTek: StorageNet Business Group X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.10 i686) X-Accept-Language: en Mime-Version: 1.0 To: sblumenau@fishbowl02.lss.emc.com Cc: owner-ipfc@standards.gadzoox.com, ipfc@standards.gadzoox.com, jeremy_swift@storagetek.com, gavin@gadzoox.com Subject: Re: SNIA recommendations for changes to the FC Mgmt MIB References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk Content-Transfer-Encoding: 7bit No... this is just my recommendation to add to the next list of recommendations from SNIA. Sorry about that. Due to NDA, I cannot fully explain my reasons behind wanting this enumeration. I can say that the product does not fit either a "storage-device" or a "storage-subsystem," but it is a device that does exactly what the enumeration label says. Also, I don't think that this is the only product that will fall under this enumeration. I am sure that other upcoming products (not from StorageTek) will fit as well... -Jeremy steven blumenau wrote: > Jeremy, > I had the same question as Gavin. Also, the subject of the email was > "SNIA recommendations...". Is this all the feedback from the SNIA on the > newest rev ? > thanks > Steve > - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - > From: "Gavin Bowlby" > Subject: RE: SNIA recommendations for changes to the FC Mgmt MIB > Date: 07/12/99 19:56 > > Jeremy: > > What do you see as the differences between: > > connUnitType = storage-device(9), -- disk,cd,tape,etc > > connUnitType = storage-subsystem(11), -- raid, library, etc > > and your proposed value: > > connUnitType = storage-access-device (14) > > ? > > thanks, > Gavin Bowlby > Gadzoox Networks > > -----Original Message----- > From: Jeremy Swift [mailto:jeremy.swift@nsg0.network.com] > Sent: Monday, July 12, 1999 3:15 PM > To: ipfc@standards.gadzoox.com; jeremy_swift@storagetek.com > Subject: SNIA recommendations for changes to the FC Mgmt MIB > > I would like to make the following recommendation for changes to the > Fibre Channel Management MIB: > > Add the following enumeration: > > connUnitType > storage-access-device (14) > > -- > Jeremy Swift http://www.storagetek.com > Software Development Phone: (612) 391-1241 > StorageTek: SNBG (800) 328-9108 ext. 1241 > jeremy_swift@storagetek.com Fax: (612) 391-1095 -- Jeremy Swift http://www.storagetek.com Software Development Phone: (612) 391-1241 StorageTek: SNBG (800) 328-9108 ext. 1241 jeremy_swift@storagetek.com Fax: (612) 391-1095 From owner-ipfc@standards.gadzoox.com Tue Jul 13 12:52:43 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14066 for ; Tue, 13 Jul 1999 12:52:42 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id JAA15410 for ipfc-list; Tue, 13 Jul 1999 09:46:46 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from gw.vixel.com (gw.vixel.com [207.115.190.195]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id JAA15407 for ; Tue, 13 Jul 1999 09:46:36 -0700 Message-ID: <378B6E43.46FD35C@vixel.com> Date: Tue, 13 Jul 1999 09:50:11 -0700 From: "Marjorie Krueger" Organization: Vixel X-Mailer: 11911 NorthCreek Parkway South - Bothell - WA - 98011 X-Accept-Language: en MIME-Version: 1.0 To: Jeremy Swift CC: sblumenau@fishbowl02.lss.emc.com, ipfc@standards.gadzoox.com Subject: Re: SNIA recommendations for changes to the FC Mgmt MIB References: <378B4CD6.B9C45CBE@network.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk Content-Transfer-Encoding: 7bit Without violating NDA, could you describe some general things about the device? Just to make sure it doesn't fit any of the other enumerations already defined? Thanks, Marjorie Krueger Vixel Corporation Jeremy Swift wrote: > > No... this is just my recommendation to add to the next list of > recommendations from SNIA. Sorry about that. > > Due to NDA, I cannot fully explain my reasons behind wanting this > enumeration. I can say that the product does not fit either a > "storage-device" or a "storage-subsystem," but it is a device that does > exactly what the enumeration label says. > > Also, I don't think that this is the only product that will fall under this > enumeration. I am sure that other upcoming products (not from StorageTek) > will fit as well... > > -Jeremy > > steven blumenau wrote: > > > Jeremy, > > I had the same question as Gavin. Also, the subject of the email was > > "SNIA recommendations...". Is this all the feedback from the SNIA on the > > newest rev ? > > thanks > > Steve > > - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - > > From: "Gavin Bowlby" > > Subject: RE: SNIA recommendations for changes to the FC Mgmt MIB > > Date: 07/12/99 19:56 > > > > Jeremy: > > > > What do you see as the differences between: > > > > connUnitType = storage-device(9), -- disk,cd,tape,etc > > > > connUnitType = storage-subsystem(11), -- raid, library, etc > > > > and your proposed value: > > > > connUnitType = storage-access-device (14) > > > > ? > > > > thanks, > > Gavin Bowlby > > Gadzoox Networks > > > > -----Original Message----- > > From: Jeremy Swift [mailto:jeremy.swift@nsg0.network.com] > > Sent: Monday, July 12, 1999 3:15 PM > > To: ipfc@standards.gadzoox.com; jeremy_swift@storagetek.com > > Subject: SNIA recommendations for changes to the FC Mgmt MIB > > > > I would like to make the following recommendation for changes to the > > Fibre Channel Management MIB: > > > > Add the following enumeration: > > > > connUnitType > > storage-access-device (14) > > > > -- > > Jeremy Swift http://www.storagetek.com > > Software Development Phone: (612) 391-1241 > > StorageTek: SNBG (800) 328-9108 ext. 1241 > > jeremy_swift@storagetek.com Fax: (612) 391-1095 > > -- > Jeremy Swift http://www.storagetek.com > Software Development Phone: (612) 391-1241 > StorageTek: SNBG (800) 328-9108 ext. 1241 > jeremy_swift@storagetek.com Fax: (612) 391-1095 From owner-ipfc@standards.gadzoox.com Fri Jul 16 23:13:01 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12995 for ; Fri, 16 Jul 1999 23:13:00 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id UAA16895 for ipfc-list; Fri, 16 Jul 1999 20:07:37 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from emcmail.lss.emc.com (emcmail.lss.emc.com [168.159.48.78]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id UAA16892 for ; Fri, 16 Jul 1999 20:07:34 -0700 Received: from fishbowl02.emc.com (fishbowl02 [168.159.48.62]) by emcmail.lss.emc.com (8.9.3/8.9.3) with SMTP id XAA23739 for ; Fri, 16 Jul 1999 23:09:50 -0400 (EDT) Received: by fishbowl02.emc.com with VINES-ISMTP; Fri, 16 Jul 1999 23:09:51 -0400 Date: Fri, 16 Jul 1999 23:09:50 -0400 Message-ID: X-Priority: 3 (Normal) To: From: "steven blumenau" Reply-To: Subject: request for additional connUnitType for FC mgmt MIB X-Incognito-SN: 1467 X-Incognito-Version: 5.0.1.89 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk A request was put on the reflector to add a new type to the connUnitType definition. There has not been much traffic to disagree with this. If anyone has comments, please post them. Otherwise, we should just add it into the draft. Steve From owner-ipfc@standards.gadzoox.com Mon Jul 19 07:16:14 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13637 for ; Mon, 19 Jul 1999 07:16:13 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id EAA18142 for ipfc-list; Mon, 19 Jul 1999 04:09:36 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from ietf.org (odin.ietf.org [132.151.1.176]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id EAA18139 for ; Mon, 19 Jul 1999 04:09:33 -0700 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13534; Mon, 19 Jul 1999 07:12:08 -0400 (EDT) Message-Id: <199907191112.HAA13534@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipfc@standards.gadzoox.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ipfc-mib-framework-00.txt Date: Mon, 19 Jul 1999 07:12:03 -0400 Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Over Fibre Channel Working Group of the IETF. Title : A Framework for Fibre Channel MIBs Author(s) : L. Hu, G. Bowlby, M. Carlson Filename : draft-ietf-ipfc-mib-framework-00.txt Pages : Date : 07-Jul-99 This document discusses technical issues and requirements for the management information base (MIB) for Fibre Channel and storage network applications. This document is likely to be expanded to include management of specific Fibre Channel device types in the future. The purpose is to have an overall structure and view of Fibre Channel MIBs for consistency and interoperability. This document does not try to cover the details of each individual MIB. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfc-mib-framework-00.txt 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-ipfc-mib-framework-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipfc-mib-framework-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19990707100414.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipfc-mib-framework-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipfc-mib-framework-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19990707100414.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ipfc@standards.gadzoox.com Fri Jul 23 18:36:55 1999 Received: from standards.gadzoox.com (standards.gadzoox.com [208.244.121.24]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12952 for ; Fri, 23 Jul 1999 18:36:55 -0400 (EDT) Received: (from majordom@localhost) by standards.gadzoox.com (8.8.7/8.8.7) id PAA19949 for ipfc-list; Fri, 23 Jul 1999 15:31:41 -0700 X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f Received: from emcmail.lss.emc.com (emcmail.lss.emc.com [168.159.48.78]) by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id PAA19946 for ; Fri, 23 Jul 1999 15:31:37 -0700 Received: from maho3msx2.isus.emc.com (maho3msx2.isus.emc.com [168.159.208.81]) by emcmail.lss.emc.com (8.9.3/8.9.3) with ESMTP id SAA04668 for ; Fri, 23 Jul 1999 18:33:50 -0400 (EDT) Received: by maho3msx2.isus.emc.com with Internet Mail Service (5.5.2448.0) id ; Fri, 23 Jul 1999 18:34:11 -0400 Message-ID: <729D927EF825D311961000E029101CCC258B8F@mxclsa> From: Black_David@emc.com To: ipfc@standards.gadzoox.com Subject: MIB framework comments Date: Fri, 23 Jul 1999 18:35:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-ipfc@standards.gadzoox.com Precedence: bulk As noted, this is a very preliminary document, so here are some equally preliminary comments ... Section 4.2 of this draft is unfortunately confused: 4.2 SNMP Version Compatibility Fibre Channel MIBs defined in the IP over FC working group should be written in the SNMPv1 syntax. As SNMPv3 becomes available, MIBs may be written in the SNMPv3 syntax also. However, the baseline version of all FC MIBs should remain SNMPv1. Every attempt should be made to keep the SNMPv1 and SNMPv3 versions of the MIBs as close as possible. First off, the syntaxes are called SMIv1 and SMIv2; used with care (i.e., don't use counter64 in SMIv2), both are compatible with all versions of SNMP. Second, the word from those in charge (IETF Operations and Management Area Directors) is that SMIv2 is REQUIRED for all new MIBs -- an attempt to submit an SMIv1 MIB to the IESG will result in very quick rejection. Conversion tools exist to mechanically obtain an SMIv1 MIB from an SMIv2 MIB as long as counter64 was not used; this takes care of the last sentence above. There are also conversion tools that assist with the mapping in the reverse direction (only has to be done once, but and is not completely mechanical because SMIv2 is more expressive and specific in some areas than SMIv1). Much of the Security section (4.1) looks like it's actually a discussion of conformance statements. The discussion of write access looks like it can be summarized as: Conformance must not require implementation of write access, for objects that are only writeable, conformance must not require implementation of the object. Section 5.3 ought not to discuss management of the MIB tree. In particular, all the standardized MIBs will eventually wind up in the non-experimental space. --David --------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 42 South St., Hopkinton, MA 01748 +1 (508) 435-1000 x75140, FAX: +1 (508) 497-6909 black_david@emc.com ---------------------------------------------------