From mailman-bounces@ietf.org Fri Oct 1 09:56:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00606 for ; Fri, 1 Oct 2004 09:56:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDO1o-0007nn-8L for imss-web-archive@ietf.org; Fri, 01 Oct 2004 10:04:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDKAD-0005hS-RZ for imss-web-archive@ietf.org; Fri, 01 Oct 2004 05:57:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: imss-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Oct 2004 05:22:04 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for imss-web-archive@ietf.org: List Password // URL ---- -------- imss@ietf.org otpees https://www1.ietf.org/mailman/options/imss/imss-web-archive%40ietf.org From imss-bounces@ietf.org Mon Oct 4 04:57:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14060 for ; Mon, 4 Oct 2004 04:57:32 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEOo4-0003lq-5m for imss-web-archive@ietf.org; Mon, 04 Oct 2004 05:06:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEOd7-0004fg-U0; Mon, 04 Oct 2004 04:55:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEOZ4-0003xg-E7 for imss@megatron.ietf.org; Mon, 04 Oct 2004 04:51:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13501 for ; Mon, 4 Oct 2004 04:51:23 -0400 (EDT) Received: from [203.199.83.27] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEOi6-0002je-CX for imss@ietf.org; Mon, 04 Oct 2004 05:00:47 -0400 Received: (qmail 16315 invoked by uid 510); 4 Oct 2004 08:51:07 -0000 Date: 4 Oct 2004 08:51:07 -0000 Message-ID: <20041004085107.16314.qmail@webmail17.rediffmail.com> Received: from unknown (61.95.158.130) by rediffmail.com via HTTP; 04 oct 2004 08:51:06 -0000 MIME-Version: 1.0 From: "Uma Chandrasekaran" To: imss@ietf.org Content-type: multipart/mixed; boundary="Next_1096879866---0-203.199.83.27-16129" X-Spam-Score: 0.8 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Subject: [imss] Information needed regarding SAN Management via SNMP X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Uma Chandrasekaran 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 X-Spam-Score: 0.8 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 This is a multipart mime message --Next_1096879866---0-203.199.83.27-16129 Content-type: multipart/alternative; boundary="Next_1096879866---1-203.199.83.27-16129" This is a multipart mime message --Next_1096879866---1-203.199.83.27-16129 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0AHi
=0A
=0AI am newbie to SAN.
=0A
=0AI would like to kno= w how many Fibre Channel Devices can be managed via SNMP without Performanc= e degrade. I understand this is a very subjective question. I feel that whe= n we increase the devices (20 switches + 1000 storage devices), SAN Discove= ry using SNMP degrades. Discovery is still degrades under load. In real tim= e, how many switches + storage devices can be discovered using SAN Manageme= nt using SNMP.
=0A
=0AIs there any draft or link which provides the = performance/scalability parameters or deployment of a generic SAN Managemen= t.
=0A
=0AYour response on this would be highly appreciated.
=0A<= BR>=0AThanks in Advance.
=0A
=0ARegards
=0AUma Chandrasekaran. =0A
=0A
=0A
=0A=0A

=0A

=0A To: imss-request@ietf.org Subject: Information needed regarding SAN Management via SNMP Content-type: multipart/alternative; boundary="Next_1096875751---0-203.199.83.38-28497" This is a multipart mime message --Next_1096875751---0-203.199.83.38-28497 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0AHi
=0A
=0AI am newbie to SAN. I would like to know how many Fib= re Channel Devices can be managed via SNMP without Performance degrade. =0A
=0AIs there any draft or link which provides the performance/scalab= ility parameters of a generic SAN Management.
=0A
=0AYour response o= n this would be highly appreciated.
=0A
=0AThanks in Advance.
=0A<= BR>=0ARegards
=0AUma Chandrasekaran.=0A

=0A

=0A=0A --Next_1096875751---0-203.199.83.38-28497 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi=0A=0AI am newbie to SAN. I would like to know how many Fibre Channel Dev= ices can be managed via SNMP without Performance degrade. =0A=0AIs there an= y draft or link which provides the performance/scalability parameters of a = generic SAN Management. =0A=0AYour response on this would be highly appreci= ated.=0A=0AThanks in Advance.=0A=0ARegards=0AUma Chandrasekaran. --Next_1096875751---0-203.199.83.38-28497-- --Next_1096879866---0-203.199.83.27-16129 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --Next_1096879866---0-203.199.83.27-16129-- From imss-bounces@ietf.org Thu Oct 21 19:12:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24833 for ; Thu, 21 Oct 2004 19:12:17 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKmJE-0000NS-HB for imss-web-archive@ietf.org; Thu, 21 Oct 2004 19:25:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKl5J-0004Zn-06; Thu, 21 Oct 2004 18:07:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKj0T-0006bT-OG; Thu, 21 Oct 2004 15:53:53 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13498; Thu, 21 Oct 2004 15:53:51 -0400 (EDT) Message-Id: <200410211953.PAA13498@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 21 Oct 2004 15:53:51 -0400 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fam-mib-00.txt X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre Channel Fabric Address Manager MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-fam-mib-00.txt Pages : 38 Date : 2004-10-21 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. At present, this memo is a work item of T11.5 (http://www.t11.org). The plan is that it will later be a work item of the IETF's IMSS working group. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-imss-fc-fam-mib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-imss-fc-fam-mib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154546.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-fam-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-fam-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154546.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart-- From imss-bounces@ietf.org Thu Oct 21 19:16:01 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25857 for ; Thu, 21 Oct 2004 19:16:01 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKmMr-0000i7-1y for imss-web-archive@ietf.org; Thu, 21 Oct 2004 19:29:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKl5N-0004bQ-Lk; Thu, 21 Oct 2004 18:07:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKj0q-0006kI-Nl; Thu, 21 Oct 2004 15:54:16 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13524; Thu, 21 Oct 2004 15:54:14 -0400 (EDT) Message-Id: <200410211954.PAA13524@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 21 Oct 2004 15:54:14 -0400 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-nsm-mib-00.txt X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre Channel Name Server MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-nsm-mib-00.txt Pages : 36 Date : 2004-10-21 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 Name Server function. At present, this memo is a work item of T11.5 (http://www.t11.org). The plan is that it will later become a work item of IETF's IMSS working group. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-imss-fc-nsm-mib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154551.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-nsm-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154551.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart-- From imss-bounces@ietf.org Wed Oct 27 14:37:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00333 for ; Wed, 27 Oct 2004 14:37:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMstN-0003qK-9D for imss-web-archive@ietf.org; Wed, 27 Oct 2004 14:51:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMsdn-0004g2-5w; Wed, 27 Oct 2004 14:35:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMsbq-0004MW-Fi for imss@megatron.ietf.org; Wed, 27 Oct 2004 14:33:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29969 for ; Wed, 27 Oct 2004 14:33:20 -0400 (EDT) From: elizabeth.rodriguez@dothill.com Received: from artecon.dothill.com ([155.254.128.254] helo=dothill.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMsph-0003kV-Ew for imss@ietf.org; Wed, 27 Oct 2004 14:47:45 -0400 Received: from exchange.artecon.com (exchange [206.6.182.75]) by dothill.com (8.12.9+Sun/8.12.5) with ESMTP id i9RIRFLl005286; Wed, 27 Oct 2004 11:27:15 -0700 (PDT) Received: by EXCHANGE with Internet Mail Service (5.5.2653.19) id <4M1402ST>; Wed, 27 Oct 2004 11:31:33 -0700 Message-ID: To: imss@ietf.org Date: Wed, 27 Oct 2004 11:36:19 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: margaret@thingmagic.com, bwijnen@lucent.com Subject: [imss] Call for Agenda Items for IMSS WG agenda, IETF 61 in Washington D .C. 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 X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b All, I have requested a 1 hour meeting time in Washington D.C. for the IMSS Working group. If anyone would like to request agenda time please do so by Sunday, October 31. The agenda items I have so far include: New working group drafts: Two new working group drafts are available. These drafts address two working group charter items: Fibre Channel Name Server MIB: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-00.txt Fibre Channel Fabric Address Manager MIB: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-00.txt (formerly Domain Mgr MIB) One proposed work item: Fibre Channel over IPv4: http://www.ietf.org/internet-drafts/draft-desanti-imss-ipv4-over-fibre-chann el-00.txt This draft is a proposed draft that the authors believe should either update or replace RFC 2625. It includes details of differences between RFC 2625 and the ID. Time permitting, INCITS T11.5 would also like to propose new work for the IMSS working group to consider. There are currently no drafts for these proposals, but would cover FSPF (Fibre Shortest Path First) MIB and a routing protocol independent Routing Information MIB. Thanks, Elizabeth _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Oct 27 16:49:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12661 for ; Wed, 27 Oct 2004 16:49:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMuxo-00074g-Tk for imss-web-archive@ietf.org; Wed, 27 Oct 2004 17:04:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMuaQ-0005uP-Q2; Wed, 27 Oct 2004 16:40:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMuR2-0002ZS-1s for imss@megatron.ietf.org; Wed, 27 Oct 2004 16:30:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10619 for ; Wed, 27 Oct 2004 16:30:17 -0400 (EDT) Received: from skyway-bridge.veritas.com ([143.127.131.4] helo=ROSMIME02.enterprise.veritas.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMueu-0006S4-I1 for imss@ietf.org; Wed, 27 Oct 2004 16:44:44 -0400 Received: from lmoxch01.enterprise.veritas.com (unverified) by ROSMIME02.enterprise.veritas.com (Content Technologies SMTPRS 4.3.12) with ESMTP id ; Wed, 27 Oct 2004 15:29:34 -0500 Received: by lmoxch01.enterprise.veritas.com with Internet Mail Service (5.5.2656.59) id <40TNQJD8>; Wed, 27 Oct 2004 16:29:34 -0400 Message-ID: From: Roger Cummings To: "'elizabeth.rodriguez@dothill.com'" , imss@ietf.org Subject: RE: [imss] Call for Agenda Items for IMSS WG agenda, IETF 61 in W ashington D .C. Date: Wed, 27 Oct 2004 16:29:27 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Cc: margaret@thingmagic.com, bwijnen@lucent.com X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: imss-bounces@ietf.org Errors-To: imss-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Elizabeth, I'll present a Liaison Report from T11.5 as per usual. Should we also be talking about the recent IANA registry activities? Regards, Roger Cummings > -----Original Message----- > From: elizabeth.rodriguez@dothill.com > [mailto:elizabeth.rodriguez@dothill.com] > Sent: Wednesday, October 27, 2004 2:36 PM > To: imss@ietf.org > Cc: margaret@thingmagic.com; bwijnen@lucent.com > Subject: [imss] Call for Agenda Items for IMSS WG agenda, IETF 61 in > Washington D .C. > > > All, > > I have requested a 1 hour meeting time in Washington D.C. for the IMSS > Working group. > If anyone would like to request agenda time please do so by > Sunday, October > 31. > > The agenda items I have so far include: > > New working group drafts: > Two new working group drafts are available. > These drafts address two working group charter items: > Fibre Channel Name Server MIB: > http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-00.txt > Fibre Channel Fabric Address Manager MIB: > http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fam-mib-00.txt > (formerly Domain Mgr MIB) > > One proposed work item: > Fibre Channel over IPv4: > http://www.ietf.org/internet-drafts/draft-desanti-imss-ipv4-ov er-fibre-chann el-00.txt This draft is a proposed draft that the authors believe should either update or replace RFC 2625. It includes details of differences between RFC 2625 and the ID. Time permitting, INCITS T11.5 would also like to propose new work for the IMSS working group to consider. There are currently no drafts for these proposals, but would cover FSPF (Fibre Shortest Path First) MIB and a routing protocol independent Routing Information MIB. Thanks, Elizabeth _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss