From imss-bounces@ietf.org Fri Nov 10 15:50:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GidKn-0004nf-7G; Fri, 10 Nov 2006 15:50:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GidKb-0004ih-AU; Fri, 10 Nov 2006 15:50:33 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GidKb-0004zU-8H; Fri, 10 Nov 2006 15:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GidKa-0007dw-U8; Fri, 10 Nov 2006 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 7BCF1175BD;
	Fri, 10 Nov 2006 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GidK6-0006ac-09; Fri, 10 Nov 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GidK6-0006ac-09@stiedprstage1.ietf.org>
Date: Fri, 10 Nov 2006 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-rscn-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>
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 Registered State Change Notification (RSCN) MIB
	Author(s)	: C. DeSanti, et al.
	Filename	: draft-ietf-imss-fc-rscn-mib-02.txt
	Pages		: 32
	Date		: 2006-11-10
	
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 management of Fibre Channel's Registered State Change
   Notifications (RSCNs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-rscn-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-rscn-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-rscn-mib-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

Content-Type: text/plain
Content-ID: <2006-11-10142423.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-11-10142423.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From imss-bounces@ietf.org Mon Nov 27 13:59:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GolhU-0000JP-3c; Mon, 27 Nov 2006 13:59:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GolhT-0000Iv-56
	for imss@ietf.org; Mon, 27 Nov 2006 13:59:31 -0500
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GolhR-0002L3-QL
	for imss@ietf.org; Mon, 27 Nov 2006 13:59:31 -0500
Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12])
	by mexforward.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	kARIxT2S023872
	for <imss@ietf.org>; Mon, 27 Nov 2006 13:59:29 -0500 (EST)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	kARIwr00020624
	for <imss@ietf.org>; Mon, 27 Nov 2006 13:59:26 -0500 (EST)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.11]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Nov 2006 13:59:17 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Nov 2006 13:59:16 -0500
Message-ID: <F222151D3323874393F83102D614E055068B88EF@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: APB - G D Ramkumar 
Thread-Index: AccSViMtwVS+iXWdRnCfbYFA1AZu6Q==
X-Priority: 1
Priority: Urgent
Importance: high
To: <imss@ietf.org>
X-OriginalArrivalTime: 27 Nov 2006 18:59:17.0376 (UTC)
	FILETIME=[23669000:01C71256]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.11.27.103433
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2,
	PRIORITY_NO_NAME 0.716, NO_REAL_NAME 0, __C230066_P5 0, __CT 0,
	__CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0,
	__HAS_MSGID 0, __HAS_X_PRIORITY 0, __IMS_MSGID 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Black_David@emc.com
Subject: [imss] APB - G D Ramkumar 
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>
Errors-To: imss-bounces@ietf.org

The imss Virtual Fabrics MIB is stuck in Authors 48
Hours state and has not been published as an RFC because
G D Ramkumar has not been heard from.  All authors are
required to review the final draft of an RFC before it
can be published.

If anyone knows where G D Ramkumar is, please tell him
to contact me (imss WG chair) ASAP.  If I do not hear
from him *this week*, he is at risk of being removed
as an author of the resulting RFC - such a removal is
a permanent action that cannot be changed after the
RFC is published.

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

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



From imss-bounces@ietf.org Tue Nov 28 18:01:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpBwj-00087o-Tr; Tue, 28 Nov 2006 18:01:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpBwg-0007pt-3q; Tue, 28 Nov 2006 18:00:58 -0500
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GpBwd-0001U4-Nm; Tue, 28 Nov 2006 18:00:58 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kASN0tBf006952; 
	Tue, 28 Nov 2006 15:00:55 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kASN0tMm006951;
	Tue, 28 Nov 2006 15:00:55 -0800
Date: Tue, 28 Nov 2006 15:00:55 -0800
Message-Id: <200611282300.kASN0tMm006951@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4747 on The Virtual Fabrics 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>
Errors-To: imss-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4747

        Title:      The Virtual Fabrics MIB 
        Author:     S. Kipp, G. Ramkumar,
                    K. McCloghrie
        Status:     Standards Track
        Date:       November 2006
        Mailbox:    scott.kipp@mcdata.com, 
                    gramkumar@stanfordalumni.org, 
                    kzm@cisco.com
        Pages:      20
        Characters: 39034
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-vf-mib-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4747.txt

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.  [STANDARDS TRACK]

This document is a product of the Internet and Management Support for 
Storage Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



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



