From owner-ipfc@standards.gadzoox.com  Mon Oct  2 06:07:14 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04366
	for <ipfc-archive@odin.ietf.org>; Mon, 2 Oct 2000 06:07:13 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id BAA09983
	for ipfc-list; Mon, 2 Oct 2000 01:50:39 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id BAA09980
	for <ipfc@standards.gadzoox.com>; Mon, 2 Oct 2000 01:50:33 -0700
Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA11088
	for <ipfc@standards.gadzoox.com>; Mon, 2 Oct 2000 06:00:39 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id GAA11084
	for <ipfc@standards.gadzoox.com>; Mon, 2 Oct 2000 06:00:39 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <TGFQT0VF>; Mon, 2 Oct 2000 12:00:33 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB09661207@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: ipfc@standards.gadzoox.com, Murali Rajagopal <muralir@lightsand.com>
Subject: RE: ips Administrative Matters and framework document
Date: Mon, 2 Oct 2000 12:00:22 +0200 
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

Comments inline

> ----------
> From: 	Murali Rajagopal[SMTP:muralir@lightsand.com]
> Sent: 	Saturday, September 30, 2000 11:09 PM
> To: 	ipfc@standards.gadzoox.com
> Subject: 	Fw: ips Administrative Matters and framework document
> 
> Dear IPFC WG Members:
> 
> The FC-IP standardization work is now officially under the charter of the
> IPS WG.
> 
> The IPFC WG will continue to operate until its chartered work is complete.
> We have two drafts - one framework and the other a Management MIB in the
> process of completion within the IPFC WG.
> 
> The frame work doc. is now sent out for a Last Call comments. It is
> expected
> that the Management MIB will be completed by the San Diego Meeting.
> 
Well, if I remember well (but I would have to dig into my email archives,
and
some of them I no longer have access to since I switched employers), then
I have send serious comments about this MIB to the author.

For one thing, the MIB is still (rev 4 of the doc) in SMIv1 format, and IETF
stds track MIBs have to be in SMIv2 format for MANY years already.

You are also using DisplayString (we have switched to UTF8 based strings
like SnmpAdminString), you are using IpAddress (which is IPv4 specific and
we want support for IPv6 these days) etc etc etc.

A few good places to look at and check:
    http://www.ietf.org/ID-nits.html
    http://www.ops.ietf.org/

If I get a positive email that when I dig up my earlier comments, that
the author/editor will study it and act on it, then I will try to find it.

Bert
> Regards,
> 
> Murali Rajagopal
> 
> IPFC WG Chair
> 
> LightSand Communications
> muralir@lightsand.com
> 
> ----- Original Message -----
> From: <Black_David@emc.com>
> To: <ips@ece.cmu.edu>
> Sent: Friday, September 29, 2000 3:58 PM
> Subject: ips Administrative Matters and framework document
> 
> 
> > The ips WG charter is now posted on the IETF web site at:
> >
> > http://www.ietf.org/html.charters/ips-charter.html
> >
> > Everyone should read it, as it contains a number of
> > important statements of goals, requirements, and restrictions,
> > in addition to a current set of expected milestones.
> >
> > There are no drafts currently linked to the charter.  The
> > current plan is to have new versions of the iSCSI and FC over
> > IP drafts submitted as WG documents (draft-ietf-ips-...) and
> > link them at that point.  Things have changed sufficiently
> > since the last versions, that linking them to the web
> > copy of the charter could seriously mislead people who
> > aren't following the mailing list.  This should happen
> > by the end of October, and hopefully a lot earlier (yes,
> > this is a public hint to the document authors :-) ).
> >
> > That takes care of the first milestone on the charter.
> > The second milestone is to get an initial version of
> > the framework document submitted as an Internet-Draft.
> > The charter says:
> >
> >   "The WG will produce a framework document that provides
> >    an overview of the environments in which its encapsulated
> >    protocols and related protocols are expected to operate."
> >
> > The framework document is the place for discussions of how, why
> > and where iSCSI and FC-over-IP might be used and what the various
> > other components are that have to be present to make them usable
> > aside from implementations of these protocols.  This also includes
> > complementarity of these protocols and discussion of overlap/
> > situations in which both might be applicable.
> >
> > The initial version of the framework document will be produced
> > by an off-line author team for review and comment by the WG.
> > I'm looking for a few good authors for the document - expertise
> > on networking, SCSI and Fibre Channel will be needed in the
> > author team.  Volunteers should have the time available to produce
> > significant text in the next couple of months, and there's
> > a need for one person to put in the time to coordinate this
> > effort and assemble the text as document editor.  The rewards
> > are fleeting fame as a co-author of the document; I would
> > guess that it'll go through several serious revisions over the
> > next 6 months or so before it can be submitted for publication
> > as an informational RFC.  If you're interested (and I hope
> > a number of folks out there are), please send me email directly.
> >
> > Thanks,
> > --David
> >
> > ---------------------------------------------------
> > David L. Black, Senior Technologist
> > EMC Corporation, 42 South St., Hopkinton, MA  01748
> > +1 (508) 435-1000 x75140     FAX: +1 (508) 497-8500
> > black_david@emc.com       Mobile: +1 (978) 394-7754
> > ---------------------------------------------------
> >
> >
> 


From owner-ipfc@standards.gadzoox.com  Mon Oct  2 12:10:03 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10248
	for <ipfc-archive@odin.ietf.org>; Mon, 2 Oct 2000 12:10:02 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id HAA10147
	for ipfc-list; Mon, 2 Oct 2000 07:54:27 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from mumm.ibr.cs.tu-bs.de (root@mumm.ibr.cs.tu-bs.de [134.169.34.190])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id HAA10144
	for <ipfc@standards.gadzoox.com>; Mon, 2 Oct 2000 07:54:23 -0700
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191])
	by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id SAA06164;
	Mon, 2 Oct 2000 18:04:29 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id SAA07023; Mon, 2 Oct 2000 18:04:29 +0200
Date: Mon, 2 Oct 2000 18:04:29 +0200
Message-Id: <200010021604.SAA07023@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: bwijnen@lucent.com
CC: ipfc@standards.gadzoox.com, muralir@lightsand.com
In-reply-to: 
	<2413FED0DFE6D111B3F90008C7FA61FB09661207@nl0006exch002u.nl.lucent.com>
	(bwijnen@lucent.com)
Subject: Re: ips Administrative Matters and framework document
References:  <2413FED0DFE6D111B3F90008C7FA61FB09661207@nl0006exch002u.nl.lucent.com>
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk


>>>>> Wijnen, Bert (Bert) writes:

Bert> Well, if I remember well (but I would have to dig into my email
Bert> archives, and some of them I no longer have access to since I
Bert> switched employers), then I have send serious comments about
Bert> this MIB to the author.

Bert, you asked me a while ago to assist the IPFC folks to make their
MIBs "IETF compliant". I actually offered help to fix this one at the
46th IETF meeting in Washington DC. I was later told that they lack a
person who is able to make the SMIv1->SMIv2 conversion. So I decided
to help them and I did the conversion myself.

So I created an SMIv2 version of the MIB with lots of technical
questions inside which I mailed to S. Blumenau on April 12, 2000 and
two days later to the working group mailing list. On June 1st,
S. Blumenau submitted <draft-ietf-ipfc-fcmgmt-int-mib-04.txt> which
does not include any of the SMIv2 changes I made. In fact, I have
never heard anything on the SMIv2 version since I submitted it.

Looking back, I must tell you that I feel like having wasted my time
to help the IPFC folks to complete their work. Perhaps there is not
enough interest to get this MIB on the IETF standards track...

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>




From owner-ipfc@standards.gadzoox.com  Wed Oct 11 20:18:16 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24753
	for <ipfc-archive@odin.ietf.org>; Wed, 11 Oct 2000 20:18:15 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id QAA15137
	for ipfc-list; Wed, 11 Oct 2000 16:02:39 -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 QAA15134
	for <ipfc@standards.gadzoox.com>; Wed, 11 Oct 2000 16:02:35 -0700
Received: from cx418298b (cx418298-b.orng1.occa.home.com [24.1.179.117])
	by lightsand.com (8.9.3+Sun/8.9.1) with SMTP id RAA29740;
	Wed, 11 Oct 2000 17:11:18 -0700 (PDT)
Message-ID: <00ff01c033e2$10ebfae0$75b30118@orng1.occa.home.com>
From: "Murali Rajagopal" <muralir@lightsand.com>
To: "Juergen Schoenwaelder" <schoenw@ibr.cs.tu-bs.de>, <bwijnen@lucent.com>
Cc: <ipfc@standards.gadzoox.com>
References:  <2413FED0DFE6D111B3F90008C7FA61FB09661207@nl0006exch002u.nl.lucent.com> <200010021604.SAA07023@henkell.ibr.cs.tu-bs.de>
Subject: Re: ips Administrative Matters and framework document
Date: Wed, 11 Oct 2000 17:19:18 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Juergen:

Your work for the MIB is not wasted. The MIB work is unfortunately moving
very slowly.
EMC has stated that they would finish the work by Dec. meeting.

We all from the IPFC WG are very thankful for your efforts.

Regards,

Murali Rajagopal
IPFC WG Chair

----- Original Message -----
From: "Juergen Schoenwaelder" <schoenw@ibr.cs.tu-bs.de>
To: <bwijnen@lucent.com>
Cc: <ipfc@standards.gadzoox.com>; <muralir@lightsand.com>
Sent: Monday, October 02, 2000 9:04 AM
Subject: Re: ips Administrative Matters and framework document


>
> >>>>> Wijnen, Bert (Bert) writes:
>
> Bert> Well, if I remember well (but I would have to dig into my email
> Bert> archives, and some of them I no longer have access to since I
> Bert> switched employers), then I have send serious comments about
> Bert> this MIB to the author.
>
> Bert, you asked me a while ago to assist the IPFC folks to make their
> MIBs "IETF compliant". I actually offered help to fix this one at the
> 46th IETF meeting in Washington DC. I was later told that they lack a
> person who is able to make the SMIv1->SMIv2 conversion. So I decided
> to help them and I did the conversion myself.
>
> So I created an SMIv2 version of the MIB with lots of technical
> questions inside which I mailed to S. Blumenau on April 12, 2000 and
> two days later to the working group mailing list. On June 1st,
> S. Blumenau submitted <draft-ietf-ipfc-fcmgmt-int-mib-04.txt> which
> does not include any of the SMIv2 changes I made. In fact, I have
> never heard anything on the SMIv2 version since I submitted it.
>
> Looking back, I must tell you that I feel like having wasted my time
> to help the IPFC folks to complete their work. Perhaps there is not
> enough interest to get this MIB on the IETF standards track...
>
> /js
>
> --
> Juergen Schoenwaelder      Technical University Braunschweig
> <schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
> Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
> Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
>
>
>



From owner-ipfc@standards.gadzoox.com  Tue Oct 17 14:00:02 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18182
	for <ipfc-archive@odin.ietf.org>; Tue, 17 Oct 2000 14:00:01 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id JAA18351
	for ipfc-list; Tue, 17 Oct 2000 09:43:20 -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 JAA18348
	for <ipfc@standards.gadzoox.com>; Tue, 17 Oct 2000 09:43:17 -0700
Received: from lightsand (dhcp074.lightsand.com [192.168.1.74])
	by lightsand.com (8.9.3+Sun/8.9.1) with SMTP id KAA00142
	for <ipfc@standards.gadzoox.com>; Tue, 17 Oct 2000 10:52:52 -0700 (PDT)
From: "Murali Rajagopal" <muralir@lightsand.com>
To: "IPFC" <ipfc@standards.gadzoox.com>
Subject: FW: Internet-Draft Cut-off Dates for San Diego IETF
Date: Tue, 17 Oct 2000 10:53:26 -0700
Message-ID: <NEBBJIDLAMKEBGHHCBJPMEPMCAAA.muralir@lightsand.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



----- Original Message ----- 
From: "Internet-Drafts Administrator" <internet-drafts@ietf.org>
To: <IETF-Announce:>
Sent: Monday, October 16, 2000 8:42 AM
Subject: Internet-Draft Cut-off Dates for San Diego IETF


> 
> NOTE: There are TWO (2) Internet-Draft Cut-off dates
> 
> The IESG has authorized an experiment for the upcoming IETF meeting.
> There will be two Internet-Draft cut-off dates:
> 
> November 17: Cut-off for Initial Submissions (new documents)
> 
> All initial submissions (-00) must be submitted by Friday, November 17,
> 1730 US-EST.  Initial submissions received after this time will not be
> announced nor made available in the internet-drafts directory,  and
> will have to be resubmitted.
> 
> As before, all initial submissions (-00.txt) with a filename beginning
> with a draft-ietf MUST be approved by the appropriate WG Chair prior to
> processing and announcing. WG Chair approval must be received by
> Monday, November 20.
> 
> Do NOT wait until the last minute to submit.
> 
> Be advised: NO placeholders. Updates to initial submissions received
>             the week of November 17 will NOT be accepted.
> 
> 
> November 24: FINAL Internet-Draft Cut-off
> 
> All revised Internet-Draft submissions must be submitted by Friday,
> November 24 2000 at 1700 US-EST. Internet-Drafts received after this
> time will NOT be announced nor made available in the Internet-Drafts
> Directories.
> 
> We will begin accepting Internet-Draft submissions the week of the
> meeting, though announcements will NOT be sent until the IETF meeting
> is over.
> 
> Thank you for your understanding and cooperation. Please do not
> hesitate to contact us if you have any questions or concerns.
> 
> 
> 
> FYI:  These and other significant date can be found at 
>       http://www.ietf.org/meetings/cutoff_dates_49.html
> 
> 




From owner-ipfc@standards.gadzoox.com  Tue Oct 17 16:49:17 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20904
	for <ipfc-archive@odin.ietf.org>; Tue, 17 Oct 2000 16:49:16 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id MAA18485
	for ipfc-list; Tue, 17 Oct 2000 12:31:46 -0700
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from min.ecn.purdue.edu (khandkar@min.ecn.purdue.edu [128.46.200.41])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id MAA18482
	for <ipfc@standards.gadzoox.com>; Tue, 17 Oct 2000 12:31:41 -0700
Received: from localhost (khandkar@localhost)
	by min.ecn.purdue.edu (8.9.3/8.9.3moyman) with ESMTP id PAA02784
	for <ipfc@standards.gadzoox.com>; Tue, 17 Oct 2000 15:41:41 -0500 (EST)
Date: Tue, 17 Oct 2000 15:41:40 -0500 (EST)
From: Snehal Khandkar <khandkar@ecn.purdue.edu>
To: IPFC <ipfc@standards.gadzoox.com>
Subject: Help: To Unsubscribe from list.
In-Reply-To: <NEBBJIDLAMKEBGHHCBJPMEPMCAAA.muralir@lightsand.com>
Message-ID: <Pine.GSO.4.21.0010171535440.29934-100000@min.ecn.purdue.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk


I cannot unsubscribe from the list. I have mailed 
majordomo@standards.gadzoox.com : automatic 
owner-ipfc@standards.gadzoox.com: operator managed

But without any response. Please let me know about the procedures.

Sorry for posting this message to the general list.

Thank you,
Snehal



From owner-ipfc@standards.gadzoox.com  Mon Oct 23 23:06:09 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13932
	for <ipfc-archive@odin.ietf.org>; Mon, 23 Oct 2000 23:06:08 -0400 (EDT)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id SAA21901
	for ipfc-list; Mon, 23 Oct 2000 18:49:36 -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 SAA21898
	for <ipfc@standards.gadzoox.com>; Mon, 23 Oct 2000 18:49:31 -0700
Received: from cx418298b (cx418298-b.orng1.occa.home.com [24.1.179.117])
	by lightsand.com (8.9.3+Sun/8.9.1) with SMTP id TAA28739
	for <ipfc@standards.gadzoox.com>; Mon, 23 Oct 2000 19:59:04 -0700 (PDT)
Message-ID: <004b01c03d67$83eac1a0$75b30118@orng1.occa.home.com>
From: "Murali Rajagopal" <muralir@lightsand.com>
To: <ipfc@standards.gadzoox.com>
Subject: Fw: 48th IETF Proceedings
Date: Mon, 23 Oct 2000 20:07:16 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Proceedings Editor" <proceedings@ietf.org>
To: <IETF-Announce:>
Sent: Monday, October 23, 2000 10:13 AM
Subject: 48th IETF Proceedings


> 
> 
> The proceedings of the 48th IETF Meeting, held in Pittsburgh, PA are now
> available at:
> 
> http://www.ietf.org/proceedings/00jul/index.html
> 
> 
> 
> 
> 



From owner-ipfc@standards.gadzoox.com  Tue Oct 31 14:18:22 2000
Received: from standards.gadzoox.com (standards.gadzoox.com [216.52.31.24])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10925
	for <ipfc-archive@odin.ietf.org>; Tue, 31 Oct 2000 14:18:20 -0500 (EST)
Received: (from majordom@localhost)
	by standards.gadzoox.com (8.8.7/8.8.7) id JAA26293
	for ipfc-list; Tue, 31 Oct 2000 09:58:21 -0800
X-Authentication-Warning: standards.gadzoox.com: majordom set sender to owner-ipfc@standards.gadzoox.com using -f
Received: from smtp4.cluster.oleane.net (smtp4.cluster.oleane.net [195.25.12.62])
	by standards.gadzoox.com (8.8.7/8.8.7) with SMTP id JAA26290
	for <ipfc@standards.gadzoox.com>; Tue, 31 Oct 2000 09:58:15 -0800
Received: from oleane  (dyn-1-1-210.Vin.dialup.oleane.fr [195.25.4.210])  by smtp4.cluster.oleane.net  with SMTP id UAA65457 for <ipfc@standards.gadzoox.com>; Tue, 31 Oct 2000 20:08:14 +0100 (CET)
Message-ID: <011c01c0436e$5be260c0$8001a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <ipfc@standards.gadzoox.com>
Subject: Beyond SDH
Date: Tue, 31 Oct 2000 20:11:19 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0119_01C04376.BBA79D60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-ipfc@standards.gadzoox.com
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0119_01C04376.BBA79D60
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

To what extent is the Sonet/SDH layer used?
What is the impact of the exponential development of IP networks on the
future of Sonet/SDH?
What role can Gigabit Ethernet play when applied to the WAN? Will the
future 10 Gigabit Ethernet standard replace SDH/Sonet? Is the Digital =
Wrapper the solution?



"Beyond Sonet/SDH" conference, Paris, 10-13 April 2001.
A call for paper is online at:=20
http://www.upperside.fr/babeyondsdh.htm

------=_NextPart_000_0119_01C04376.BBA79D60
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV>
<DIV>
<P><FONT face=3DArial size=3D2>To what extent is the <STRONG>Sonet/SDH=20
</STRONG>layer used?<BR>What is the impact of the exponential =
development of=20
<B>IP networks</B> on the<BR>future of Sonet/SDH?<BR>What role can =
Gigabit=20
Ethernet play when applied to the WAN? Will the<BR>future <B>10 Gigabit=20
Ethernet</B> standard replace SDH/Sonet? Is the <B>Digital Wrapper</B> =
the=20
solution?<BR><BR></FONT></P><FONT face=3DArial><FONT =
size=3D2><STRONG>"Beyond=20
Sonet/SDH" </STRONG>conference, Paris, 10-13 April =
2001.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>A call for paper is online at: =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.upperside.fr/babeyondsdh.htm">http://www.upperside.fr/=
babeyondsdh.htm</A></FONT></DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0119_01C04376.BBA79D60--