From owner-ipfc@standards.gadzoox.com  Mon Jul  3 15:29:24 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06618
	for <ipfc-archive@odin.ietf.org>; Mon, 3 Jul 2000 15:29:23 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id MAA24165
	for ipfc-list; Mon, 3 Jul 2000 12:14:41 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id MAA24162
	for <ipfc@standards.gadzoox.com>; Mon, 3 Jul 2000 12:14:37 -0700
Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA27930
	for <ipfc@standards.gadzoox.com>; Mon, 3 Jul 2000 15:23:10 -0400 (EDT)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id PAA27910
	for <ipfc@standards.gadzoox.com>; Mon, 3 Jul 2000 15:23:10 -0400 (EDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2650.21)
	id <N9NPZVHF>; Mon, 3 Jul 2000 14:05:23 -0500
Message-ID: <80B684C5E29FD211AA8000A0C9CDD91904D096F5@IL0015EXCH005U>
From: "Rodriguez, Elizabeth G (Elizabeth)" <egrodriguez@lucent.com>
To: "'ipfc@standards.gadzoox.com'" <ipfc@standards.gadzoox.com>
Subject: FW: 47th IETF Proceedings
Date: Mon, 3 Jul 2000 14:05:13 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk



-----Original Message-----
From: Proceedings@ietf.org [mailto:Proceedings@ietf.org]
Sent: Monday, June 26, 2000 1:53 PM
Cc: etang@ietf.org
Subject: 47th IETF Proceedings



The proceedings of the 47th IETF Meeting, held in Adelaide, Austraiia, is
now available at:

http://www.ietf.org/proceedings/00mar/index.html


From owner-ipfc@standards.gadzoox.com  Tue Jul 18 06:39:27 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15492
	for <ipfc-archive@odin.ietf.org>; Tue, 18 Jul 2000 06:39:26 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id DAA31955
	for ipfc-list; Tue, 18 Jul 2000 03:24:16 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id DAA31952
	for <ipfc@standards.gadzoox.com>; Tue, 18 Jul 2000 03:24:13 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12259;
	Tue, 18 Jul 2000 06:32:43 -0400 (EDT)
Message-Id: <200007181032.GAA12259@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ipfc@standards.gadzoox.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ipfc-mib-framework-03.txt
Date: Tue, 18 Jul 2000 06:32:42 -0400
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Over Fibre Channel Working Group of the IETF.

	Title		: A Framework for Fibre Channel MIBs
	Author(s)	: M. Carlson, G. Bowlby, L. Hu
	Filename	: draft-ietf-ipfc-mib-framework-03.txt
	Pages		: 
	Date		: 17-Jul-00
	
This document discusses technical issues and requirements for the
management information base (MIB) for Fibre Channel and storage
network applications.  This document is likely to be expanded to
include management of specific Fibre Channel device types in the
future. The purpose is to have an overall structure and view of
Fibre Channel MIBs for consistency and interoperability. This
document does not try to cover the details of each individual MIB.
This is an initial draft document, which will evolve and expand
over time. It is the intent of this document to produce a coherent
description of a framework for various MIB development which was
and is being considered by the working group.  Selection of
specific approaches, making choices regarding engineering tradeoffs,
and detailed protocol specification, are outside of the scope of
this framework document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfc-mib-framework-03.txt

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-ipfc-mib-framework-03.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-ipfc-mib-framework-03.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:	<20000717145351.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfc-mib-framework-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ipfc-mib-framework-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-ipfc@standards.gadzoox.com  Thu Jul 20 07:24:46 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03006
	for <ipfc-archive@odin.ietf.org>; Thu, 20 Jul 2000 07:24:44 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id EAA00448
	for ipfc-list; Thu, 20 Jul 2000 04:09:45 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id EAA00445
	for <ipfc@standards.gadzoox.com>; Thu, 20 Jul 2000 04:09:41 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10139;
	Thu, 20 Jul 2000 06:43:37 -0400 (EDT)
Message-Id: <200007201043.GAA10139@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ipfc@standards.gadzoox.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ipfc-fcoverip-02.txt
Date: Thu, 20 Jul 2000 06:43:37 -0400
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over Fibre Channel Working Group of the IETF.

	Title		: Fibre Channel Over IP (FCIP)
	Author(s)	: M. Rajagopal, W. Rickard, E. Rodriguez,
                          R. Bhagwat, M. Krueger
	Filename	: draft-ietf-ipfc-fcoverip-02.txt
	Pages		: 19
	Date		: 19-Jul-00
	
Fibre Channel(FC) is a dominant technology used in Storage Area
Networks(SAN).  The purpose of this draft is to specify a standard
way of encapsulating FC frames over IP and to describe mechanisms
that allow islands of FC SANs to be interconnected over IP-based
networks running over very reliable data links. FC over IP relies on
IP-based network services to provide the connectivity between the SAN
islands over LANs, MANs, or WANs.  While the FC over IP specification
is independent of the link level transport protocol, it assumes a
high bandwidth, high reliability, low loss link level transport such
as Gigabit Ethernet, SONET, ATM, or DWDM. This specification treats
all classes of FC frames the same -- as  datagrams.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfc-fcoverip-02.txt

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-ipfc-fcoverip-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-ipfc-fcoverip-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:	<20000719140942.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfc-fcoverip-02.txt

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

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

--OtherAccess--

--NextPart--




From owner-ipfc@standards.gadzoox.com  Fri Jul 21 10:26:50 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15191
	for <ipfc-archive@odin.ietf.org>; Fri, 21 Jul 2000 10:26:50 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id HAA01115
	for ipfc-list; Fri, 21 Jul 2000 07:12:10 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from alemail1.firewall.lucent.com (alemail1.lucent.com [192.11.221.161])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id HAA01112
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 07:12:06 -0700
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA09296
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 10:20:35 -0400 (EDT)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA09289
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 10:20:35 -0400 (EDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2650.21)
	id <3ZJ5DZ93>; Fri, 21 Jul 2000 09:20:35 -0500
Message-ID: <80B684C5E29FD211AA8000A0C9CDD91904D09798@IL0015EXCH005U>
From: "Rodriguez, Elizabeth G (Elizabeth)" <egrodriguez@lucent.com>
To: "'ipfc@standards.gadzoox.com'" <ipfc@standards.gadzoox.com>
Subject: FW: I-D ACTION:draft-ietf-ipfc-fcoverip-02.txt
Date: Fri, 21 Jul 2000 09:20:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFF31E.D54A7BA0"
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BFF31E.D54A7BA0
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Thursday, July 20, 2000 5:44 AM
Cc: ipfc@standards.gadzoox.com
Subject: I-D ACTION:draft-ietf-ipfc-fcoverip-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IP over Fibre Channel Working Group of the
IETF.

	Title		: Fibre Channel Over IP (FCIP)
	Author(s)	: M. Rajagopal, W. Rickard, E. Rodriguez,
                          R. Bhagwat, M. Krueger
	Filename	: draft-ietf-ipfc-fcoverip-02.txt
	Pages		: 19
	Date		: 19-Jul-00
	
Fibre Channel(FC) is a dominant technology used in Storage Area
Networks(SAN).  The purpose of this draft is to specify a standard
way of encapsulating FC frames over IP and to describe mechanisms
that allow islands of FC SANs to be interconnected over IP-based
networks running over very reliable data links. FC over IP relies on
IP-based network services to provide the connectivity between the SAN
islands over LANs, MANs, or WANs.  While the FC over IP specification
is independent of the link level transport protocol, it assumes a
high bandwidth, high reliability, low loss link level transport such
as Gigabit Ethernet, SONET, ATM, or DWDM. This specification treats
all classes of FC frames the same -- as  datagrams.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfc-fcoverip-02.txt

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-ipfc-fcoverip-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-ipfc-fcoverip-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_000_01BFF31E.D54A7BA0
Content-Type: message/rfc822

To: 
Subject: 
Date: Thu, 20 Jul 2000 15:06:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01BFF31E.D54A7BA0"


------_=_NextPart_002_01BFF31E.D54A7BA0
Content-Type: text/plain



------_=_NextPart_002_01BFF31E.D54A7BA0
Content-Type: application/octet-stream;
	name="ATT98662"
Content-Disposition: attachment;
	filename="ATT98662"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfc-fcoverip-02.txt

------_=_NextPart_002_01BFF31E.D54A7BA0
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-ietf-ipfc-fcoverip-02.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01BFF31E.D54A7BA0--

------_=_NextPart_000_01BFF31E.D54A7BA0--


From owner-ipfc@standards.gadzoox.com  Fri Jul 21 10:27:07 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15220
	for <ipfc-archive@odin.ietf.org>; Fri, 21 Jul 2000 10:27:05 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id HAA01120
	for ipfc-list; Fri, 21 Jul 2000 07:12:34 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id HAA01117
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 07:12:31 -0700
Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA06217
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 10:21:00 -0400 (EDT)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA06207
	for <ipfc@standards.gadzoox.com>; Fri, 21 Jul 2000 10:21:00 -0400 (EDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2650.21)
	id <3ZJ5DZ0R>; Fri, 21 Jul 2000 09:21:00 -0500
Message-ID: <80B684C5E29FD211AA8000A0C9CDD91904D09799@IL0015EXCH005U>
From: "Rodriguez, Elizabeth G (Elizabeth)" <egrodriguez@lucent.com>
To: "'ipfc@standards.gadzoox.com'" <ipfc@standards.gadzoox.com>
Subject: FW: I-D ACTION:draft-ietf-ipfc-mib-framework-03.txt
Date: Fri, 21 Jul 2000 09:20:58 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFF31E.E3B08C70"
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BFF31E.E3B08C70
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Tuesday, July 18, 2000 5:33 AM
Cc: ipfc@standards.gadzoox.com
Subject: I-D ACTION:draft-ietf-ipfc-mib-framework-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IP Over Fibre Channel Working Group of the
IETF.

	Title		: A Framework for Fibre Channel MIBs
	Author(s)	: M. Carlson, G. Bowlby, L. Hu
	Filename	: draft-ietf-ipfc-mib-framework-03.txt
	Pages		: 
	Date		: 17-Jul-00
	
This document discusses technical issues and requirements for the
management information base (MIB) for Fibre Channel and storage
network applications.  This document is likely to be expanded to
include management of specific Fibre Channel device types in the
future. The purpose is to have an overall structure and view of
Fibre Channel MIBs for consistency and interoperability. This
document does not try to cover the details of each individual MIB.
This is an initial draft document, which will evolve and expand
over time. It is the intent of this document to produce a coherent
description of a framework for various MIB development which was
and is being considered by the working group.  Selection of
specific approaches, making choices regarding engineering tradeoffs,
and detailed protocol specification, are outside of the scope of
this framework document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfc-mib-framework-03.txt

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-ipfc-mib-framework-03.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-ipfc-mib-framework-03.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_000_01BFF31E.E3B08C70
Content-Type: message/rfc822

To: 
Subject: 
Date: Tue, 18 Jul 2000 09:04:06 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01BFF31E.E3B08C70"


------_=_NextPart_002_01BFF31E.E3B08C70
Content-Type: text/plain



------_=_NextPart_002_01BFF31E.E3B08C70
Content-Type: application/octet-stream;
	name="ATT81910"
Content-Disposition: attachment;
	filename="ATT81910"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfc-mib-framework-03.txt

------_=_NextPart_002_01BFF31E.E3B08C70
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-ietf-ipfc-mib-framework-03.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01BFF31E.E3B08C70--

------_=_NextPart_000_01BFF31E.E3B08C70--


From owner-ipfc@standards.gadzoox.com  Mon Jul 24 13:29:24 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03240
	for <ipfc-archive@odin.ietf.org>; Mon, 24 Jul 2000 13:29:23 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id JAA01934
	for ipfc-list; Mon, 24 Jul 2000 09:12:51 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from lightsand.com ([208.50.99.84])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id JAA01931
	for <ipfc@standards.gadzoox.com>; Mon, 24 Jul 2000 09:12:47 -0700
Received: from cx926635a (cx926635-a.msnv1.occa.home.com [24.10.148.23])
	by lightsand.com (8.9.3+Sun/8.9.1) with ESMTP id KAA16088;
	Mon, 24 Jul 2000 10:20:06 -0700 (PDT)
Message-ID: <004f01bff594$2592b600$17940a18@msnv1.occa.home.com>
Reply-To: "Raj Bhagwat" <rajb@lightsand.com>
From: "Raj Bhagwat" <rajb@lightsand.com>
To: <agenda@ietf.org>
Cc: <smb@research.att.com>, <Black_David@emc.com>, <mankin@isi.edu>,
        <sob@harvard.edu>, "Wayne Rickard" <wayne@gadzoox.com>,
        "Marjorie Krueger (E-mail)" <mkrueger@vixel.com>,
        "'Rodriguez, Elizabeth G (Elizabeth)'" <egrodriguez@lucent.com>,
        <Erik.Nordmark@eng.sun.com>, "Thomas Narten" <narten@raleigh.ibm.com>,
        <ipfc@standards.gadzoox.com>
Subject: Final agenda for the IPFC WG meeting
Date: Mon, 24 Jul 2000 10:25:19 -0700
Organization: LightSand Communications
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004C_01BFF559.774D1CA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_004C_01BFF559.774D1CA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

IP Over Fibre Channel WG (ipfc)=20

Thursday, August 3 at 1530-1730

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D

CHAIR: Murali Rajagopal

Agenda posted by - Raj Bhagwat (rajb@lightsand.com)

AGENDA:

1. Review of agenda (5 mins)

2. IP over Fibre Channel - present UNH interoperability test report,=20

     discuss next step (30 mins)

3. Status and update on MIBs (30 mins)

   - Fibre Channel Management MIB

   - FC Fabric Element MIB

   - Fibre Channel MIB Frame Work

NOTE:

Immediately following the above IPFC work items, there will be an =
informal discussion on FC over IP (draft-ietf-ipfc-fcoverip-02.txt) in =
the same room. We expect this discussion to start around 4.30pm or so. =
As of now, 'FC over IP' is not an approved work item under the IPFC =
charter.




------=_NextPart_000_004C_01BFF559.774D1CA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT size=3D2>
<P><FONT face=3D"Courier New">IP Over Fibre Channel WG (ipfc) =
</FONT></P>
<P><FONT face=3D"Courier New">Thursday, August 3 at 1530-1730</FONT></P>
<P><FONT face=3D"Courier =
New">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D</FONT></P>
<P><FONT face=3D"Courier New">CHAIR: Murali Rajagopal</FONT></P>
<P><FONT face=3D"Courier New">Agenda posted by - Raj Bhagwat (<A=20
href=3D"mailto:rajb@lightsand.com">rajb@lightsand.com</A>)</FONT></P>
<P><FONT face=3D"Courier New">AGENDA:</FONT></P></FONT><FONT size=3D2>
<P><FONT face=3D"Courier New">1. Review of agenda (5 mins)</FONT></P>
<P><FONT face=3D"Courier New">2. IP over Fibre Channel &#8211; present =
UNH=20
interoperability test report, </FONT></P>
<P><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; discuss next step =
(30=20
mins)</FONT></P>
<P><FONT face=3D"Courier New">3. Status and update on MIBs (30 =
mins)</FONT></P>
<P><FONT face=3D"Courier New">&nbsp;&nbsp; - Fibre Channel Management=20
MIB</FONT></P>
<P><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp;- FC Fabric Element =
MIB</FONT></P>
<P><FONT face=3D"Courier New">&nbsp;&nbsp; - </FONT><FONT =
face=3D"Courier New">Fibre=20
Channel MIB Frame Work</FONT></P>
<P>NOTE:</P>
<P><FONT face=3D"Courier New">Immediately following the&nbsp;above IPFC =
work=20
items, there will be an informal discussion on FC over=20
IP&nbsp;(draft-ietf-ipfc-fcoverip-02.txt) in the same room. We expect =
this=20
discussion to start around 4.30pm or so. As of now, 'FC over IP' is not =
an=20
approved work item under the IPFC charter.</FONT></P>
<P>&nbsp;</P></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_004C_01BFF559.774D1CA0--



From owner-ipfc@standards.gadzoox.com  Mon Jul 24 13:43:19 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07549
	for <ipfc-archive@odin.ietf.org>; Mon, 24 Jul 2000 13:43:18 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id JAA01942
	for ipfc-list; Mon, 24 Jul 2000 09:26:55 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from lightsand.com ([208.50.99.84])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id JAA01939
	for <ipfc@standards.gadzoox.com>; Mon, 24 Jul 2000 09:26:52 -0700
Received: from cx926635a (cx926635-a.msnv1.occa.home.com [24.10.148.23])
	by lightsand.com (8.9.3+Sun/8.9.1) with ESMTP id KAA16218
	for <ipfc@standards.gadzoox.com>; Mon, 24 Jul 2000 10:36:46 -0700 (PDT)
Message-ID: <008301bff596$78969fe0$17940a18@msnv1.occa.home.com>
Reply-To: "Raj Bhagwat" <rajb@lightsand.com>
From: "Raj Bhagwat" <rajb@lightsand.com>
To: <ipfc@standards.gadzoox.com>
Subject: Fabric Element MIB moved to Proposed Std (RFC 2837)
Date: Mon, 24 Jul 2000 10:41:58 -0700
Organization: LightSand Communications
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0080_01BFF55B.CB12CFE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0080_01BFF55B.CB12CFE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi,

For the benefit of those who have not seen the IETF announcement, the =
Fabric Element MIB authored by Kha Sin of Brocade has been moved to =
Proposed Standard. I just went through IPFC archive and realized that =
this announcement somehow did not get forwarded to the IPFC list.

Regards,

Raj Bhagwat
LightSand Communications
rajb@lightsand.com

-------------------------------------------------------------------------=
-----------------------

     To: IETF-Announce: ;=20
     Subject: RFC 2837 on FC Fabric Element MIB=20
     From: RFC Editor <rfc-ed@ISI.EDU>=20
     Date: Thu, 01 Jun 2000 15:00:56 -0700=20
     Cc: rfc-ed@ISI.EDU, ipfc@standards.gadzoox.com=20

=20


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


        RFC 2837

        Title:      Definitions of Managed Objects for the Fabric
                    Element in Fibre Channel Standard=20
        Author(s):  K. Teow
        Status:     Standards Track
        Date:       May 2000
        Mailbox:    khasin@Brocade.COM
        Pages:      48
        Characters: 87860
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ipfc-fabric-element-mib-07.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2837.txt


This memo defines an extension to the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets.  In particular, it defines the objects for managing the
operations of the Fabric Element portion of the Fibre Channel
Standards.

This document is a product of the IP Over Fibre Channel Working Group
of the IETF.

This is now a Proposed Standard Protocol.

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.echo=20
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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader=20
implementation to automatically retrieve the ASCII version
of the RFCs.

------=_NextPart_000_0080_01BFF55B.CB12CFE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>For the benefit of those who have not =
seen the IETF=20
announcement, the Fabric Element MIB authored by Kha Sin of =
Brocade&nbsp;has=20
been moved to Proposed Standard. I just went through IPFC archive and =
realized=20
that this announcement somehow did not get forwarded to the IPFC=20
list.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Raj Bhagwat</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>LightSand Communications</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:rajb@lightsand.com">rajb@lightsand.com</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
--------------------------------</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; To: =
IETF-Announce: ;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp; Subject: RFC 2837 on FC Fabric Element MIB=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp; From: RFC Editor &lt;<A=20
href=3D"mailto:rfc-ed@ISI.EDU">rfc-ed@ISI.EDU</A>&gt; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
Date: Thu, 01 Jun 2000 15:00:56 -0700 <BR>&nbsp;&nbsp;&nbsp;&nbsp; Cc: =
<A=20
href=3D"mailto:rfc-ed@ISI.EDU">rfc-ed@ISI.EDU</A>, <A=20
href=3D"mailto:ipfc@standards.gadzoox.com">ipfc@standards.gadzoox.com</A>=
=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>A new Request for Comments is now =
available in=20
online RFC libraries.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RFC=20
2837</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Definitions of Managed Objects for =
the=20
Fabric<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Element in Fibre Channel Standard =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Author(s):&nbsp; K. Teow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Status:&nbsp;&nbsp;&nbsp;&nbsp; Standards=20
Track<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May=20
2000<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Mailbox:&nbsp;&nbsp;&nbsp; <A=20
href=3D"mailto:khasin@Brocade.COM">khasin@Brocade.COM</A><BR>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Pages:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
48<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Characters:=20
87860<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Updates/Obsoletes/SeeAlso:&nbsp; None</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I-D=20
Tag:&nbsp;&nbsp;&nbsp; =
draft-ietf-ipfc-fabric-element-mib-07.txt</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"ftp://ftp.isi.edu/in-notes/rfc2837.txt">ftp://ftp.isi.edu/in-note=
s/rfc2837.txt</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>This memo defines an extension to =
the=20
Management Information Base<BR>(MIB) for use with network management =
protocols=20
in TCP/IP-based<BR>internets.&nbsp; In particular, it defines the =
objects for=20
managing the<BR>operations of the Fabric Element portion of the Fibre=20
Channel<BR>Standards.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This document is a product of the IP =
Over Fibre=20
Channel Working Group<BR>of the IETF.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This is now a Proposed Standard=20
Protocol.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This document specifies an Internet =
standards track=20
protocol for<BR>the Internet community, and requests discussion and=20
suggestions<BR>for improvements.&nbsp; Please refer to the current =
edition of=20
the<BR>"Internet Official Protocol Standards" (STD 1) for =
the<BR>standardization=20
state and status of this protocol.&nbsp; Distribution<BR>of this memo is =

unlimited.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This announcement is sent to the IETF =
list and the=20
RFC-DIST list.<BR>Requests to be added to or deleted from the IETF =
distribution=20
list<BR>should be sent to <A=20
href=3D"mailto:IETF-REQUEST@IETF.ORG">IETF-REQUEST@IETF.ORG</A>.&nbsp; =
Requests to=20
be<BR>added to or deleted from the RFC-DIST distribution list =
should<BR>be sent=20
to <A=20
href=3D"mailto:RFC-DIST-REQUEST@RFC-EDITOR.ORG">RFC-DIST-REQUEST@RFC-EDIT=
OR.ORG</A>.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Details on obtaining RFCs via FTP or =
EMAIL may be=20
obtained by sending<BR>an EMAIL message to <A=20
href=3D"mailto:rfc-info@RFC-EDITOR.ORG">rfc-info@RFC-EDITOR.ORG</A> with =
the=20
message body <BR>help: ways_to_get_rfcs.&nbsp; For example:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: <A=20
href=3D"mailto:rfc-info@RFC-EDITOR.ORG">rfc-info@RFC-EDITOR.ORG</A><BR>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Subject: getting rfcs</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; help:=20
ways_to_get_rfcs</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Requests for special distribution =
should be=20
addressed to either the<BR>author of the RFC in question, or to <A=20
href=3D"mailto:RFC-Manager@RFC-EDITOR.ORG">RFC-Manager@RFC-EDITOR.ORG</A>=
.&nbsp;=20
Unless<BR>specifically noted otherwise on the RFC itself, all RFCs are=20
for<BR>unlimited distribution.echo <BR>Submissions for Requests for =
Comments=20
should be sent to<BR><A=20
href=3D"mailto:RFC-EDITOR@RFC-EDITOR.ORG">RFC-EDITOR@RFC-EDITOR.ORG</A>.&=
nbsp;=20
Please consult RFC 2223, Instructions to RFC<BR>Authors, for further=20
information.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>Joyce K. Reynolds and Sandy=20
Ginoza<BR>USC/Information Sciences Institute</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>...</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Below is the data which will enable a =
MIME=20
compliant Mail Reader <BR>implementation to automatically retrieve the =
ASCII=20
version<BR>of the RFCs.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0080_01BFF55B.CB12CFE0--