From owner-ipfc@standards.gadzoox.com  Tue Feb  1 15:27:49 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 PAA01770
	for <ipfc-archive@odin.ietf.org>; Tue, 1 Feb 2000 15:27:47 -0500 (EST)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id MAA16875
	for ipfc-list; Tue, 1 Feb 2000 12:12:09 -0800
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 MAA16872
	for <ipfc@standards.gadzoox.com>; Tue, 1 Feb 2000 12:12:06 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01407;
	Tue, 1 Feb 2000 15:19:58 -0500 (EST)
Message-Id: <200002012019.PAA01407@ietf.org>
To: IETF-Announce: ;
Cc: ipfc@standards.gadzoox.com
From: The IESG <iesg-secretary@ietf.org>
SUBJECT: Last Call: Definitions of Managed Objects for the Fabric
	 Element in Fibre Channel Standard to Proposed Standard
Reply-to: iesg@ietf.org
Date: Tue, 01 Feb 2000 15:19:58 -0500
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk


The IESG has received a request from the IP Over Fibre Channel Working
Group to consider Definitions of Managed Objects for the Fabric Element
in Fibre Channel Standard <draft-ietf-ipfc-fabric-element-mib-07.txt>
as a Proposed Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by February 15, 2000.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipfc-fabric-element-mib-07.txt





From owner-ipfc@standards.gadzoox.com  Thu Feb  3 17:08: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 RAA00906
	for <ipfc-archive@odin.ietf.org>; Thu, 3 Feb 2000 17:08:45 -0500 (EST)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id NAA17942
	for ipfc-list; Thu, 3 Feb 2000 13:54:06 -0800
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from gordan.pl.gadzoox.com (gordan.pl.gadzoox.com [209.95.220.16])
	by standards.gadzoox.com (8.8.7/8.8.7) with ESMTP id NAA17939
	for <ipfc@standards.gadzoox.com>; Thu, 3 Feb 2000 13:54:05 -0800
Received: by gordan.pl.gadzoox.com with Internet Mail Service (5.5.2650.21)
	id <1B6P4D7L>; Thu, 3 Feb 2000 14:02:17 -0800
Message-ID: <312419998E3CD211A52900A0C991A47A2254AB@gordan.pl.gadzoox.com>
From: Murali Rajagopal <murali@gadzoox.com>
To: "'ipfc@standards.gadzoox.com'" <ipfc@standards.gadzoox.com>
Subject: FW: 47th IETF: SCHEDULING REQUESTS
Date: Thu, 3 Feb 2000 14:02:15 -0800 
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

IPFC WG meets March 29, Wednesday 1 -3 PM.

Agenda:

1. Discuss RFC 2625 Interoperability Test Suites
   A Test Suite in the form an Internet-Draft will be published prior to the
meeting.
   The Test Suite is now slated for a July date due to schedule conflicts
with some key participants.
   So far I have received favorable responses to participate from 7 vendors.

2. Internet-Drafts Status:
        Definitions of Managed Objects for the Fabric Element in Fibre
Channel Standard - Brocade 
        Fibre Channel Management Framework Integration MIB - EMC
        A Framework for Fibre Channel MIBs - Sun and Gadzoox

3. New Business 
        Proposal for a Storage Library MIB - Andrea Westerinen SNIA
        Other (details to be announced later)



-----Original Message-----
From: agenda@ietf.org [mailto:agenda@ietf.org] 
Sent: Thursday, February 03, 2000 1:24 PM
To: wgchairs@ietf.org; bofchairs@ietf.org
Subject: 47th IETF: SCHEDULING REQUESTS


Meeting Dates: March 26-31, 2000
Location: Adelaide, Australia

We are currently taking scheduling requests for ALL Working Groups 
and BOFs. The cut-off for requesting a slot is Friday, March 3 at 
1700 ET. The agenda for the working group is due by Thursday, 
March 17 at 1200 PM, please submit the agenda to: 
    agenda@ietf.org 
BOF agendas are due at the time the request is made.

If you cancel a scheduled working group session, please send a 
message to agenda@ietf.org as soon as possible. If you cancel a 
session once on site at the meeting, please inform someone at 
the IETF Registration Desk.

With respect to working group and BOF requests, please note the 
following:

1. All scheduling requests must be sent to the appropriate Area 
   Director(s) with a copy to: agenda@ietf.org 

   Applications: Patrik Faltstrom <paf@swip.net>
                 Keith Moore <moore@cs.utk.edu> 
   Internet: Thomas Narten <narten@raleigh.ibm.com> 
             Eric Nordmark <nordmark@eng.sun.com>
   Operations: Randy Bush <randy@psg.com>
               Bert Wijnen <wijnen@vnet.ibm.com>
   Routing: Rob Coltun <rcoltun@siara.com>
            Dave Oran <oran@cisco.com>
   Security: Marcus Leech <mleech@nortelnetworks.com>
             Jeff Schiller <jis@mit.edu>
   Transport: Scott Bradner <sob@harvard.edu> 
              Vern Paxson <vern@aciri.org>
   User Services: April Marine <april.marine@nominum.com>

   All requests are subject to AD approval. You MUST provide the 
   following information before the group will be scheduled:

a. Working Group or BOF name. (Please read the BOF Procedure at
   ftp://ftp.ietf.org/ietf/1bof-procedures.txt 
   before requesting a slot for a BOF.)

b. Area under which Working Group (or BOF) appears;

c. Conflicts you wish to avoid, please be as specific as possible. 

d. Expected Attendance:

e. Special requests. i.e., multicast (data projectors will be available
   in all meeting rooms) 

2. All groups will be scheduled in a regular two hour session unless
   you specifically request a one hour session.  If you request a
   one hour session, the working group will be scheduled on Tuesday.

3. Working groups will be allowed a maximum of two slots. If your 
   working group will need more, please let me know. Additional slots 
   will be available after agenda scheduling has closed (currently 
   March 3) and with approval from the AD.

4. BOF's will not be scheduled unless the AD approved request is 
   accompanied by a full description, BOF name and acronym,
   chairs name and an agenda. 


