From imss-bounces@ietf.org Sat Sep 03 08:32:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBXCY-0002OY-QE; Sat, 03 Sep 2005 08:32:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EBXCX-0002OQ-Tk
	for imss@megatron.ietf.org; Sat, 03 Sep 2005 08:32:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02870
	for <imss@ietf.org>; Sat, 3 Sep 2005 08:32:52 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EBXEu-0007Jo-86
	for imss@ietf.org; Sat, 03 Sep 2005 08:35:20 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-4.cisco.com with ESMTP; 03 Sep 2005 05:32:45 -0700
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j83CWg0J015431
	for <imss@ietf.org>; Sat, 3 Sep 2005 05:32:43 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id FAA06606
	for imss@ietf.org; Sat, 3 Sep 2005 05:32:42 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200509031232.FAA06606@cisco.com>
To: imss@ietf.org
Date: Sat, 3 Sep 2005 05:32:42 -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: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [imss] I-D ACTION:draft-kzm-imss-fc-zs-mib-00.txt (fwd)
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

FYI.  This is one of the MIBs listed in the Paris minutes under
the heading: "(Near) Future".  At present, it is being proposed
to T11.5 for their SM-ZSM project.   The plan is that when T11.5
approve it, it will become a work item of this working group.

Keith.
-------------
Forwarded message:
> From: Internet-Drafts@ietf.org
> To: i-d-announce@ietf.org
> Message-Id: <E1EBKMD-0001Zv-CB@newodin.ietf.org>
> Date: Fri, 02 Sep 2005 18:50:01 -0400
> Subject: I-D ACTION:draft-kzm-imss-fc-zs-mib-00.txt 
> 
> --NextPart
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title		: Fibre-Channel Zone Server MIB
> 	Author(s)	: K. McCloghrie, et al.
> 	Filename	: draft-kzm-imss-fc-zs-mib-00.txt
> 	Pages		: 71
> 	Date		: 2005-9-2
> 	
>    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 Zone Server.  At present, this memo is being
>    proposed to 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-kzm-imss-fc-zs-mib-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-kzm-imss-fc-zs-mib-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-kzm-imss-fc-zs-mib-00.txt".
> 	

_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss



From imss-bounces@ietf.org Tue Sep 13 15:50:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFGnC-0000eg-JR; Tue, 13 Sep 2005 15:50:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFGn5-0000am-5t; Tue, 13 Sep 2005 15:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10455;
	Tue, 13 Sep 2005 15:50:00 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFGrX-00036U-5H; Tue, 13 Sep 2005 15:54:39 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EFGn3-00008k-SB; Tue, 13 Sep 2005 15: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: <E1EFGn3-00008k-SB@newodin.ietf.org>
Date: Tue, 13 Sep 2005 15:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fspf-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
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=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		: MIB for Fibre-Channel's Fabric Shortest Path First Protocol
	Author(s)	: C. DeSanti, et al.
	Filename	: draft-ietf-imss-fc-fspf-mib-00.txt
	Pages		: 39
	Date		: 2005-9-13
	
   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.  This memo was originally developed as the SM-FSM
   project of T11.5 (http://www.t11.org).  With the approval of SM-FSM,
   the memo was forwarded to, and has 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-fspf-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-fspf-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-fspf-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-9-13152920.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imss-fc-fspf-mib-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-imss-fc-fspf-mib-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-13152920.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 Sep 13 15:50:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFGnJ-0000kC-HA; Tue, 13 Sep 2005 15:50:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFGn5-0000bN-Ni; Tue, 13 Sep 2005 15:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10464;
	Tue, 13 Sep 2005 15:50:00 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFGrX-00036S-3g; Tue, 13 Sep 2005 15:54:39 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EFGn3-00008f-RH; Tue, 13 Sep 2005 15: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: <E1EFGn3-00008f-RH@newodin.ietf.org>
Date: Tue, 13 Sep 2005 15:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-rtm-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
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=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-00.txt
	Pages		: 21
	Date		: 2005-9-13
	
   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.  This memo was originally
   developed as the SM-RTM project of T11.5 (http://www.t11.org).  With
   the approval of SM-RTM, the memo was forwarded to, and has 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-rtm-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-rtm-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-rtm-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-9-13152718.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imss-fc-rtm-mib-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-imss-fc-rtm-mib-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-13152718.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 Wed Sep 21 20:30:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIEyY-0002iX-2G; Wed, 21 Sep 2005 20:30:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIEyV-0002iR-AB
	for imss@megatron.ietf.org; Wed, 21 Sep 2005 20:30:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12191
	for <imss@ietf.org>; Wed, 21 Sep 2005 20:30:06 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com ([168.159.2.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIF4d-0007Yh-G3
	for imss@ietf.org; Wed, 21 Sep 2005 20:36:27 -0400
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9])
	by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j8M0U1cB002640
	for <imss@ietf.org>; Wed, 21 Sep 2005 20:30:02 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <RT50S36P>; Wed, 21 Sep 2005 20:28:48 -0400
Message-ID: <F222151D3323874393F83102D614E0557A6E57@CORPUSMX20A.corp.emc.com>
To: imss@ietf.org
Date: Wed, 21 Sep 2005 20:28:42 -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.1.0.0,
	Antispam-Data: 2005.9.21.32
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ 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: b132cb3ed2d4be2017585bf6859e1ede
Cc: Black_David@emc.com
Subject: [imss] Publication Requested: IP over FC
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

Publication has just been requested on the IP over FC draft.  The
PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used.  Here is the PROTO writeup:

	Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel
	         draft-ietf-imss-ip-over-fibre-channel-01.txt

David L. Black (acting 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.

        Do you have any concerns about the
        depth or breadth of the reviews that have been performed?

No, but see next question.

   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.)?

Expert review by an Internet Area expert would be a good idea.  I don't
expect problems, as most of the IP aspects of this draft are based on
consolidation of two existing RFCs.

   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 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).

Boilerplate text is out of date, but it was ok when the draft was
submitted.  RFC Editor will correct this if a new version of the draft
is not required in the interim.

Henrik's (really useful) checker says everything else is ok.

   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.

   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 document specifies the encapsulation of IPv6, IPv4 and ARP 
   packets over Fibre Channel.  This document also specifies the methods
   for 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.

--  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

   This document replaces and consolidates two separate RFCs on IPv4 over
   Fibre Channel (RFC 2625) and IPv6 over Fibre Channel (RFC 3831).  Most
   of its technical content is unchanged from those RFCs.  The technical
   changes that have been made are primarily based on implementation
   experience.

   The protocol has been reviewed for the IESG by David L. Black.


Thanks,
--David (acting IMSS WG chair)
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------


_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss



From imss-bounces@ietf.org Wed Sep 21 20:30:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIEz2-0002xV-LQ; Wed, 21 Sep 2005 20:30:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIEyz-0002xE-EK
	for imss@megatron.ietf.org; Wed, 21 Sep 2005 20:30:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12213
	for <imss@ietf.org>; Wed, 21 Sep 2005 20:30:36 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com ([168.159.2.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIF57-0007ZQ-JX
	for imss@ietf.org; Wed, 21 Sep 2005 20:36:57 -0400
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9])
	by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j8M0U5qP023689
	for <imss@ietf.org>; Wed, 21 Sep 2005 20:30:34 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <RT50S372>; Wed, 21 Sep 2005 20:30:02 -0400
Message-ID: <F222151D3323874393F83102D614E0557A6E58@CORPUSMX20A.corp.emc.com>
To: imss@ietf.org
Date: Wed, 21 Sep 2005 20:29:37 -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.1.0.0,
	Antispam-Data: 2005.9.21.31
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ 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: 2857c5c041d6c02d7181d602c22822c8
Cc: Black_David@emc.com
Subject: [imss] Publication Requested: FAM MIB
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

Publication has just been requested on the FAM MIB draft.  The
PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used.  Here is the PROTO writeup:

                Fibre Channel Fabric Address Manager MIB
                   draft-ietf-imss-fc-fam-mib-01.txt

David L. Black (acting 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 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).

Boilerplate text is out of date, but it was ok when the draft was
submitted.  RFC Editor will correct this if a new version of the draft
is not required in the interim.

Henrik's (really useful) checker says everything else is ok.

   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 only normative reference to an ID is to
draft-ietf-ips-fcmgmt-mib-nn.txt which is now RFC 4044.

   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 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 IESG by Keith McCloghrie.

Thanks,
--David (acting 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 Fri Sep 23 15:50:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EItYt-0004CS-Ri; Fri, 23 Sep 2005 15:50:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EItYa-00045P-9K; Fri, 23 Sep 2005 15:50:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03425;
	Fri, 23 Sep 2005 15:50:01 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EItf3-000784-L3; Fri, 23 Sep 2005 15:56:46 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EItYX-0002hw-RH; Fri, 23 Sep 2005 15: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: <E1EItYX-0002hw-RH@newodin.ietf.org>
Date: Fri, 23 Sep 2005 15:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-nsm-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
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF.

	Title		: Fibre-Channel Name Server MIB
	Author(s)	: C. DeSanti, et al.
	Filename	: draft-ietf-imss-fc-nsm-mib-02.txt
	Pages		: 38
	Date		: 2005-9-23
	
This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for information related
   to the Name Server function of a Fibre Channel network.  The Fibre
   Channel Name Server provides a means for Fibre Channel ports to
   register and discover Fibre Channel names and attributes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-nsm-mib-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-nsm-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-nsm-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: <2005-9-23120837.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imss-fc-nsm-mib-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-imss-fc-nsm-mib-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-23120837.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 Sep 23 18:44:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIwH6-0007P7-I7; Fri, 23 Sep 2005 18:44:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIwH5-0007N9-A8
	for imss@megatron.ietf.org; Fri, 23 Sep 2005 18:44:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20181
	for <imss@ietf.org>; Fri, 23 Sep 2005 18:44:08 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com ([168.159.2.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIwNb-0005Yd-HH
	for imss@ietf.org; Fri, 23 Sep 2005 18:50:56 -0400
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9])
	by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j8NMi67G008383
	for <imss@ietf.org>; Fri, 23 Sep 2005 18:44:07 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <RT50XXFQ>; Fri, 23 Sep 2005 18:44:06 -0400
Message-ID: <F222151D3323874393F83102D614E0557A6E8C@CORPUSMX20A.corp.emc.com>
To: imss@ietf.org
Date: Fri, 23 Sep 2005 18:44:00 -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.1.0.0,
	Antispam-Data: 2005.9.23.28
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ 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: 2857c5c041d6c02d7181d602c22822c8
Subject: [imss] Publication Requested: NSM MIB
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

Publication has just been requested on the NSM MIB draft.  The
PROTO process (cf. draft-ietf-proto-wgchair-doc-shepherding-05.txt)
is being used.  Here is the PROTO writeup:

                     Fibre-Channel Name Server MIB
                    draft-ietf-imss-fc-nsm-mib-02.txt

Requested Publication Status: Proposed Standard RFC
PROTO shepherd: David L. Black (acting 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).

Henrik's (really useful) checker says everything is ok.

   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 only normative reference to an ID is to 
draft-ietf-imss-fc-fam-mib-nn.txt for which Proposed Standard RFC
publication has already been requested.

   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 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.
   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 Tue Sep 27 15:50:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKLTQ-0005Nt-62; Tue, 27 Sep 2005 15:50:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKLSo-00059J-UO; Tue, 27 Sep 2005 15:50:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05172;
	Tue, 27 Sep 2005 15:50:05 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EKLa4-0007dQ-RB; Tue, 27 Sep 2005 15:57:38 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EKLSk-0004TB-Fu; Tue, 27 Sep 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EKLSk-0004TB-Fu@newodin.ietf.org>
Date: Tue, 27 Sep 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-virtual-fabrics-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
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=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-virtual-fabrics-mib-00.txt
	Pages		: 20
	Date		: 2005-9-27
	
   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-virtual-fabrics-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-virtual-fabrics-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-virtual-fabrics-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-9-27120416.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-imss-fc-virtual-fabrics-mib-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-imss-fc-virtual-fabrics-mib-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-9-27120416.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 Sep 30 20:20:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELV7I-0003cs-Sx; Fri, 30 Sep 2005 20:20:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELV7C-0003Kh-Ug
	for imss@megatron.ietf.org; Fri, 30 Sep 2005 20:20:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00531
	for <imss@ietf.org>; Fri, 30 Sep 2005 20:20:33 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com ([168.159.2.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELVFA-0003pR-PE
	for imss@ietf.org; Fri, 30 Sep 2005 20:28:49 -0400
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9])
	by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j910KWUP029698
	for <imss@ietf.org>; Fri, 30 Sep 2005 20:20:32 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <RT6AHGVX>; Fri, 30 Sep 2005 20:20:31 -0400
Message-ID: <F222151D3323874393F83102D614E0557A6F24@CORPUSMX20A.corp.emc.com>
To: imss@ietf.org
Date: Fri, 30 Sep 2005 20:20:28 -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.1.0.0,
	Antispam-Data: 2005.9.30.32
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ 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: de4f315c9369b71d7dd5909b42224370
Subject: [imss] Meeting in Vancouver
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group
	<imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>,
	<mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

The IMSS WG will meet in Vancouver (Nov. 6-11); I've
just requested a 1 hour slot.

The official imss WG drafts will be on the agenda for the
imss meeting, along with a T11.5 status report.  If
anyone wants meeting time for any other purpose, please
send me a note indicating the amount of time needed,
the purpose, and the associated Internet-Draft.

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



