From imss-bounces@ietf.org Fri Apr 13 12:25:49 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 1HcOXG-0008Ge-62; Fri, 13 Apr 2007 12:22:06 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1HcOXE-0008ER-AZ
	for imss-confirm+ok@megatron.ietf.org; Fri, 13 Apr 2007 12:22:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcOXD-00087n-AV
	for imss@ietf.org; Fri, 13 Apr 2007 12:22:03 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcOTu-0006KJ-4y
	for imss@ietf.org; Fri, 13 Apr 2007 12:18:39 -0400
Received: from mailhub.lss.emc.com (nirah.lss.emc.com [10.254.144.13])
	by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l3DGIbKN029796
	for <imss@ietf.org>; Fri, 13 Apr 2007 12:18:37 -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
	l3DGIYmt014881
	for <imss@ietf.org>; Fri, 13 Apr 2007 12:18:37 -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); 
	Fri, 13 Apr 2007 12:18:30 -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: Fri, 13 Apr 2007 12:18:30 -0400
Message-ID: <F222151D3323874393F83102D614E055068B9271@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: TMDA deployment for IETF mailing lists
Thread-Index: Acd951/KCMNyFcnXQuaal0QlRiMQuA==
To: <imss@ietf.org>
X-OriginalArrivalTime: 13 Apr 2007 16:18:30.0597 (UTC)
	FILETIME=[6010A750:01C77DE7]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604,
	Antispam-Data: 2007.4.13.85034
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3,
	NO_REAL_NAME 0, __C230066_P5 0, __CP_URI_IN_BODY 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: 0.2 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Black_David@emc.com
Subject: [imss] TMDA deployment for IETF mailing lists
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

Folks,

Tagged Message Delivery Agent (TMDA - http://tmda.net/)
software has been deployed for the imss WG mailing list.
If you are subscribed to this list, or to any IETF mailing
list hosted at ietf.org, you will not be affected, as all
such addresses are on TMDA's whitelist.

The only effect should be that if you post to the imss
list from an email address that is not subscribed to
any IETF mailing list hosted at ietf.org, you will need
to respond to a TMDA email challenge before you get
the email notice that your post has been held for
administrator approval.

The reason for deployment is that I currently have to
wade through a dozen or more attempts to send spam to
the imss list every day, just in case one of them is
an actual message (I can't remember the last time an
actual message showed up in that fashion) - TMDA will
automatically reject most of the spams, reducing the
burden on me.

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


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



From imss-bounces@ietf.org Tue Apr 24 15:50:49 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 1HgR2H-0000GK-3i; Tue, 24 Apr 2007 15:50:49 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1HgR23-0008AZ-84
	for imss-confirm+ok@megatron.ietf.org; Tue, 24 Apr 2007 15:50:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgR22-00089N-DA; Tue, 24 Apr 2007 15:50:34 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HgR20-0003eR-UX; Tue, 24 Apr 2007 15:50:34 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id C0215175EC;
	Tue, 24 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HgR1W-00017u-GO; Tue, 24 Apr 2007 15:50:02 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1HgR1W-00017u-GO@stiedprstage1.ietf.org>
Date: Tue, 24 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: imss@ietf.org, David Black <black_david@emc.com>
Subject: [imss] WG Action: RECHARTER: Internet and Management Support for 
 Storage (imss) 
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 charter of the Internet and Management Support for Storage (imss)
working group in the Operations and Management Area of the IETF has been
updated. For additional information, please contact the Area Directors
or the working group Chairs.

+++

Internet and Management Support for Storage (imss)
--------------------------------------------------

Current Status: Active Working Group 

Additional information is available at tools.ietf.org/wg/imss 

Chair(s):
David Black <black_david@emc.com> 

Operations and Management Area Director(s):
Dan Romascanu <dromasca@avaya.com> 
Ronald Bonica <rbonica@juniper.net> 

Operations and Management Area Advisor:
Dan Romascanu <dromasca@avaya.com> 

Technical Advisor(s):
Keith McCloghrie <kzm@cisco.com> 
Margaret Wasserman <margaret@thingmagic.com> 

Mailing Lists:
General Discussion: imss@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/imss
Archive: http://www.ietf.org/mail-archive/web/imss/index.html

Description of Working Group:
Fibre Channel is a high speed network technology primarily used for
storage networking (i.e., Storage Area Networks [SANs]). Two important
aspects of Fibre Channel interact with the Internet:
- Fibre Channel can encapsulate and carry IP protocol traffic
- Fibre Channel devices can be managed via SNMP

The Internet and Management Support for Storage WG (imss) is chartered
to address two areas, specifically:
- IPv4 over Fibre Channel has been specified in RFC 2625. A
corresponding specification for IPv6 is needed.
- An initial Fibre Channel Management MIB has been developed by
the IP Storage (ips) WG; extensions are needed to encompass
management of additional aspects of Fibre Channel, such
as zoning.

In the future, other storage related MIBs for other storage transports
such as INCITS T10 Serial Attached SCSI (SAS) or SCSI command specific
MIBs may be proposed. This group would work with the appropriate
technical committee(s) in a manner similar to that described for INCITS
T11 below.

As Fibre Channel standardization is handled by the INCITS T11 Technical
Committee (http://www.t11.org), a close working relationship with T11 is
essential to the WG's success. In particular:
- The IPv6 over Fibre Channel specification will be based on
draft-desanti-ipv6-over-fibre-channel-02.txt. This draft
was originally developed within a T11 study group and T11
has officially recommended this draft to the IETF.
- The WG will not standardize management of Fibre Channel 
features ahead of their incorporation into appropriate T11 
Fibre Channel standards.
- The WG will work closely with T11, specifically Task Group 
T11.5, on the functionality and structure of the MIBs it 
develops for management of Fibre Channel.

In addition to working closely with the INCITS T11 Technical Committee,
this Working Group will work closely with IETF IPv6 Working Group as
appropriate. In particular, the IPv6 Working Group will be kept informed
on the progress and status of the IPv6 over Fibre Channel specification.
The IMSS Working Group Last Call announcement will be cross-posted to
the IPv6 WG mailing list.

Goals and Milestones:
Done Submit IPv6 over Fibre Channel draft to IESG for consideration
as Proposed Standard 
Done Submit Fibre Channel Fabric Address Manager MIB to IESG for
consideration as Proposed Standard 
Done Submit Fibre Channel Name Server MIB to IESG for consideration
as Proposed Standard 
Done Work with T11.5 to determine what additional MIB modules are
needed 
Done Submit Routing Information, FSPF and Virtual Fabrics MIBs to
IESG for consideration as Proposed Standard 
Done Submit Fibre Channel Zone Server, RSCN, and Fabric Configuration
Server MIBs to IESG for consideration as Proposed Standard 
Done Review working group charter and determine what additional work,
if any, should be undertaken by working group 
December 2007 Submit Fibre Channel Security MIB modules to IESG for
consideration as proposed standard


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



From imss-bounces@ietf.org Wed Apr 25 11:44:47 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 1Hgjfj-0006WT-80; Wed, 25 Apr 2007 11:44:47 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43)
	id 1Hgjfh-0006WL-Vk
	for imss-confirm+ok@megatron.ietf.org; Wed, 25 Apr 2007 11:44:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgjfh-0006WC-M8
	for imss@ietf.org; Wed, 25 Apr 2007 11:44:45 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgjfg-0000Nz-8T
	for imss@ietf.org; Wed, 25 Apr 2007 11:44:45 -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
	l3PFih0I012976
	for <imss@ietf.org>; Wed, 25 Apr 2007 11:44:43 -0400 (EDT)
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com
	[10.254.64.54])
	by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id
	l3PFiIrS006578
	for <imss@ietf.org>; Wed, 25 Apr 2007 11:44:42 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.12]) by
	corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Apr 2007 11:44:32 -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: Wed, 25 Apr 2007 11:44:31 -0400
Message-ID: <F222151D3323874393F83102D614E055068B930D@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Action: RECHARTER: Internet and Management Support for
	Storage (imss) 
Thread-Index: AceGqcYXS+lvb5TNRR+Me6AkyeRcFwApoeXg
To: <imss@ietf.org>
X-OriginalArrivalTime: 25 Apr 2007 15:44:32.0563 (UTC)
	FILETIME=[9E425830:01C78750]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604,
	Antispam-Data: 2007.4.25.82235
X-PerlMx-Spam: Gauge=, SPAM=1%, Reason='EMC_FROM_0+ -3, NO_REAL_NAME 0,
	__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0,
	__HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __PHISH_PHRASE1_F 0, __SANE_MSGID 0'
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Subject: [imss] FW: WG Action: RECHARTER: Internet and Management Support
	for Storage (imss) 
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

FYI - this charter update is to add the work item for the FC
Security MIB modules.  The body of the charter is unchanged.

Many thanks to Dan Romascanu (our AD) for making this happen.

Thanks,
--David=20

-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org]=20
Sent: Tuesday, April 24, 2007 3:50 PM
To: ietf-announce@ietf.org
Cc: Black, David; imss@ietf.org
Subject: WG Action: RECHARTER: Internet and Management Support for
Storage (imss)=20

The charter of the Internet and Management Support for Storage (imss)
working group in the Operations and Management Area of the IETF has been
updated. For additional information, please contact the Area Directors
or the working group Chairs.

+++

Internet and Management Support for Storage (imss)
--------------------------------------------------

Current Status: Active Working Group=20

Additional information is available at tools.ietf.org/wg/imss=20

Chair(s):
David Black <black_david@emc.com>=20

Operations and Management Area Director(s):
Dan Romascanu <dromasca@avaya.com>=20
Ronald Bonica <rbonica@juniper.net>=20

Operations and Management Area Advisor:
Dan Romascanu <dromasca@avaya.com>=20

Technical Advisor(s):
Keith McCloghrie <kzm@cisco.com>=20
Margaret Wasserman <margaret@thingmagic.com>=20

Mailing Lists:
General Discussion: imss@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/imss
Archive: http://www.ietf.org/mail-archive/web/imss/index.html

Description of Working Group:
Fibre Channel is a high speed network technology primarily used for
storage networking (i.e., Storage Area Networks [SANs]). Two important
aspects of Fibre Channel interact with the Internet:
- Fibre Channel can encapsulate and carry IP protocol traffic
- Fibre Channel devices can be managed via SNMP

The Internet and Management Support for Storage WG (imss) is chartered
to address two areas, specifically:
- IPv4 over Fibre Channel has been specified in RFC 2625. A
corresponding specification for IPv6 is needed.
- An initial Fibre Channel Management MIB has been developed by
the IP Storage (ips) WG; extensions are needed to encompass
management of additional aspects of Fibre Channel, such
as zoning.

In the future, other storage related MIBs for other storage transports
such as INCITS T10 Serial Attached SCSI (SAS) or SCSI command specific
MIBs may be proposed. This group would work with the appropriate
technical committee(s) in a manner similar to that described for INCITS
T11 below.

As Fibre Channel standardization is handled by the INCITS T11 Technical
Committee (http://www.t11.org), a close working relationship with T11 is
essential to the WG's success. In particular:
- The IPv6 over Fibre Channel specification will be based on
draft-desanti-ipv6-over-fibre-channel-02.txt. This draft
was originally developed within a T11 study group and T11
has officially recommended this draft to the IETF.
- The WG will not standardize management of Fibre Channel=20
features ahead of their incorporation into appropriate T11=20
Fibre Channel standards.
- The WG will work closely with T11, specifically Task Group=20
T11.5, on the functionality and structure of the MIBs it=20
develops for management of Fibre Channel.

In addition to working closely with the INCITS T11 Technical Committee,
this Working Group will work closely with IETF IPv6 Working Group as
appropriate. In particular, the IPv6 Working Group will be kept informed
on the progress and status of the IPv6 over Fibre Channel specification.
The IMSS Working Group Last Call announcement will be cross-posted to
the IPv6 WG mailing list.

Goals and Milestones:
Done Submit IPv6 over Fibre Channel draft to IESG for consideration
as Proposed Standard=20
Done Submit Fibre Channel Fabric Address Manager MIB to IESG for
consideration as Proposed Standard=20
Done Submit Fibre Channel Name Server MIB to IESG for consideration
as Proposed Standard=20
Done Work with T11.5 to determine what additional MIB modules are
needed=20
Done Submit Routing Information, FSPF and Virtual Fabrics MIBs to
IESG for consideration as Proposed Standard=20
Done Submit Fibre Channel Zone Server, RSCN, and Fabric Configuration
Server MIBs to IESG for consideration as Proposed Standard=20
Done Review working group charter and determine what additional work,
if any, should be undertaken by working group=20
December 2007 Submit Fibre Channel Security MIB modules to IESG for
consideration as proposed standard



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



