From imss-bounces@ietf.org Thu Aug 02 21:57:26 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGmPt-0006z0-QT; Thu, 02 Aug 2007 21:57:25 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IGmPt-0006xU-2Z
	for imss-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 21:57:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGmPs-0006xK-O6
	for imss@ietf.org; Thu, 02 Aug 2007 21:57:24 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGmPs-0000nf-7k
	for imss@ietf.org; Thu, 02 Aug 2007 21:57:24 -0400
Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12])
	by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l731vL0p003833; Thu, 2 Aug 2007 21:57:21 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l731v4XH005998; Thu, 2 Aug 2007 21:57:19 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.12]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Aug 2007 21:57:16 -0400
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: Thu, 2 Aug 2007 21:57:11 -0400
Message-ID: <F222151D3323874393F83102D614E0550A4D245E@CORPUSMX20A.corp.emc.com>
In-Reply-To: <F222151D3323874393F83102D614E0550A4D2273@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Acceptance of draft-kzm-imss-fc-fcsp-mib-00.txt as an imss WG
	draft
Thread-Index: Ace/ZBPzGhtl515DQp2PIl21TnEhnwWDS3ow
References: <F222151D3323874393F83102D614E0550A4D2273@CORPUSMX20A.corp.emc.com>
To: <imss@ietf.org>
X-OriginalArrivalTime: 03 Aug 2007 01:57:16.0257 (UTC)
	FILETIME=[9E061D10:01C7D571]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604,
	Antispam-Data: 2007.7.6.21134
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3,
	NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: -3.7 (---)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: dromasca@avaya.com
Subject: [imss] RE: Acceptance of draft-kzm-imss-fc-fcsp-mib-00.txt as an
	imss WG draft
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

Having seen no further comment beyond Dan's, the FCSP MIB
is now an official imss WG draft.

Keith - please submit this as a draft-ietf-imss WG draft
when you can.

Thanks,
--David (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
----------------------------------------------------

> -----Original Message-----
> From: Black, David=20
> Sent: Thursday, July 05, 2007 8:25 PM
> To: imss@ietf.org
> Cc: Black, David; 'Romascanu, Dan (Dan)'
> Subject: Acceptance of draft-kzm-imss-fc-fcsp-mib-00.txt as=20
> an imss WG draft
>=20
> As Keith noted to the list last month, the draft
> draft-kzm-imss-fc-fcsp-mib-00.txt has been posted to
> the Internet-Draft servers.  This contains security
> management MIB modules that have been worked on in T11,
> and is intended as the starting point for the final
> work item on the imss WG's charter:
>=20
> Dec 2007	Submit Fibre Channel Security MIB modules
> 		to IESG for consideration as proposed standard
>=20
> In the absence of objection, this draft will be accepted
> as an official imss WG draft during the IETF meeting
> week in Chicago, July 22-27.  Note: the imss WG is not
> meeting in Chicago as my intent is to handle work on
> this draft almost entirely on the mailing list.  There
> will be a meeting in Vancouver if there are technical
> issues to discuss.
>=20
> I would like to see comments on acceptance of this draft,
> and particularly on its size.  The draft is nearly
> 250 pages - security is not easy to manage ;-).  It
> contains 6 MIB modules, and so I'm interested in hearing
> whether the draft ought to be split into multiple smaller
> drafts that may be easier to handle.
>=20
> Thanks,
> --David (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
> ----------------------------------------------------
>=20
>=20


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



From imss-bounces@ietf.org Fri Aug 03 22:59:58 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9rv-00014T-34; Fri, 03 Aug 2007 22:59:55 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IH9rt-00014E-5B
	for imss-confirm+ok@megatron.ietf.org; Fri, 03 Aug 2007 22:59:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9rs-000132-Pm; Fri, 03 Aug 2007 22:59:52 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IH9rs-0007wG-BX; Fri, 03 Aug 2007 22:59:52 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id C75BEDF03B; Fri,  3 Aug 2007 19:59:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070804025945.C75BEDF03B@bosco.isi.edu>
Date: Fri,  3 Aug 2007 19:59:45 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4935 on Fibre Channel Fabric Configuration Server 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 4935

        Title:      Fibre Channel Fabric Configuration Server 
                    MIB 
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    cds@cisco.com, 
                    hvivek@cisco.com, 
                    kzm@cisco.com,  sgai@nuovasystems.com
        Pages:      50
        Characters: 97345
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc4935.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 Fabric Configuration Server function of a Fibre Channel network.  [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



From imss-bounces@ietf.org Fri Aug 03 23:00:03 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9s3-0001Am-Sk; Fri, 03 Aug 2007 23:00:03 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IH9s3-00018x-6H
	for imss-confirm+ok@megatron.ietf.org; Fri, 03 Aug 2007 23:00:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9s2-00018p-Sd; Fri, 03 Aug 2007 23:00:02 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IH9s1-0007wU-M8; Fri, 03 Aug 2007 23:00:02 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 06C15DF03D; Fri,  3 Aug 2007 19:59:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070804025956.06C15DF03D@bosco.isi.edu>
Date: Fri,  3 Aug 2007 19:59:56 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4936 on Fibre Channel Zone Server 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 4936

        Title:      Fibre Channel Zone Server MIB 
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    cds@cisco.com, 
                    hvivek@cisco.com, 
                    kzm@cisco.com,  sgai@nuovasystems.com
        Pages:      84
        Characters: 170801
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-zs-mib-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4936.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 a Fibre Channel Zone Server.  [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



From imss-bounces@ietf.org Sun Aug 05 05:35:02 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHcVq-0007ys-0z; Sun, 05 Aug 2007 05:35:02 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IHcVo-0007yl-TI
	for imss-confirm+ok@megatron.ietf.org; Sun, 05 Aug 2007 05:35:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHcVk-0007vA-VK
	for imss@ietf.org; Sun, 05 Aug 2007 05:34:57 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IHcVk-00058O-H4
	for imss@ietf.org; Sun, 05 Aug 2007 05:34:56 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 05 Aug 2007 05:34:55 -0400
X-IronPort-AV: i="4.19,221,1183348800"; 
	d="scan'208"; a="50207527:sNHT13365816"
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: Sun, 5 Aug 2007 11:34:14 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A042C825E@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 4936 on Fibre Channel Zone Server MIB
Thread-Index: AcfWQ+lx2LfEtsFdQ+quWz/j3opaHwA/6xmQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <imss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Subject: [imss] FW: RFC 4936 on Fibre Channel Zone Server 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

=20
Congratulations and thanks to the editors and the whole Working Group
for the publication of RFC 4935 and RFC 4936.=20

Dan


=20

-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]=20
Sent: Saturday, August 04, 2007 6:00 AM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: imss@ietf.org; rfc-editor@rfc-editor.org
Subject: RFC 4936 on Fibre Channel Zone Server MIB


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

       =20
        RFC 4936

        Title:      Fibre Channel Zone Server MIB=20
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    cds@cisco.com,=20
                    hvivek@cisco.com,=20
                    kzm@cisco.com,  sgai@nuovasystems.com
        Pages:      84
        Characters: 170801
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-zs-mib-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4936.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 a
Fibre Channel Zone Server.  [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=20

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

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


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



From imss-bounces@ietf.org Tue Aug 07 17:39:38 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIWm8-0003So-1s; Tue, 07 Aug 2007 17:39:36 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IIWm7-0003Sf-Af
	for imss-confirm+ok@megatron.ietf.org; Tue, 07 Aug 2007 17:39:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIWm5-0003SX-MZ; Tue, 07 Aug 2007 17:39:35 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IIWm4-0001Fh-LD; Tue, 07 Aug 2007 17:39:33 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm2e46b933ed; Wed, 08 Aug 2007 05:51:27 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm3e46b42917; Sat, 04 Aug 2007 11:50:24 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Sat, 04 Aug 2007 11:50:24 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9rw-00017f-Qz; Fri, 03 Aug 2007 22:59:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IH9rs-000132-Pm; Fri, 03 Aug 2007 22:59:52 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IH9rs-0007wG-BX; Fri, 03 Aug 2007 22:59:52 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id C75BEDF03B; Fri,  3 Aug 2007 19:59:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070804025945.C75BEDF03B@bosco.isi.edu>
Date: Fri,  3 Aug 2007 19:59:45 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: rfc-editor@rfc-editor.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4935 on Fibre Channel Fabric Configuration Server MIB
X-BeenThere: imss@ietf.org
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 4935

        Title:      Fibre Channel Fabric Configuration Server 
                    MIB 
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    cds@cisco.com, 
                    hvivek@cisco.com, 
                    kzm@cisco.com,  sgai@nuovasystems.com
        Pages:      50
        Characters: 97345
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc4935.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 Fabric Configuration Server function of a Fibre Channel network.  [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

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


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



From imss-bounces@ietf.org Tue Aug 14 15:16:58 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL1rD-0004SJ-TT; Tue, 14 Aug 2007 15:15:11 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IL1r5-0004Kk-6L
	for imss-confirm+ok@megatron.ietf.org; Tue, 14 Aug 2007 15:15:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL1r4-0004KR-6V; Tue, 14 Aug 2007 15:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL1r3-0003KE-QR; Tue, 14 Aug 2007 15:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id B13B026E5C;
	Tue, 14 Aug 2007 19:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IL1r3-0000PD-K9; Tue, 14 Aug 2007 15:15: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: <E1IL1r3-0000PD-K9@stiedprstage1.ietf.org>
Date: Tue, 14 Aug 2007 15:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: imss@ietf.org
Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fcsp-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>
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 Security Protocols (FC-SP)
	Author(s)	: C. DeSanti, et al.
	Filename	: draft-ietf-imss-fc-fcsp-mib-00.txt
	Pages		: 249
	Date		: 2007-8-14
	

   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 FC-SP, the Security Protocols defined for Fibre Channel.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fcsp-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-fcsp-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-fcsp-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: <2007-8-14145824.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-8-14145824.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 Aug 24 18:58:40 2007
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOi5G-0005bD-Nv; Fri, 24 Aug 2007 18:56:54 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1IOi5F-0005b0-EM
	for imss-confirm+ok@megatron.ietf.org; Fri, 24 Aug 2007 18:56:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOi5F-0005as-4r; Fri, 24 Aug 2007 18:56:53 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IOi5D-00029x-Tt; Fri, 24 Aug 2007 18:56:53 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id A17F3E0085; Fri, 24 Aug 2007 15:55:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070824225520.A17F3E0085@bosco.isi.edu>
Date: Fri, 24 Aug 2007 15:55:20 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4983 on Fibre Channel Registered State Change
	Notification (RSCN) 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 4983

        Title:      Fibre Channel Registered State Change 
                    Notification (RSCN) MIB 
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    cds@cisco.com, 
                    hvivek@cisco.com, 
                    kzm@cisco.com,  sgai@nuovasystems.com
        Pages:      28
        Characters: 56049
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc4983.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 management of Fibre Channel's Registered State
Change Notifications (RSCNs).  [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



