Re: Last Call for draft-ietf-rolc-apr-00.txt (2)

Andrew Smith <asmith@baynetworks.com> Fri, 20 October 1995 21:00 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19588; 20 Oct 95 17:00 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa19573; 20 Oct 95 17:00 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA24156; Fri, 20 Oct 1995 16:33:15 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id QAA10908 for rolc-out; Fri, 20 Oct 1995 16:41:47 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id QAA10899 for <rolc@nexen.com>; Fri, 20 Oct 1995 16:41:44 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id QAA24137 for <rolc@nexen.com>; Fri, 20 Oct 1995 16:31:22 -0400
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA02159; Fri, 20 Oct 95 13:36:38 PDT
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA24818; Fri, 20 Oct 95 13:37:59 PDT
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA19263; Fri, 20 Oct 95 13:37:55 PDT
Date: Fri, 20 Oct 95 13:37:55 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9510202037.AA19263@milliways-le0.engwest>
To: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt (2)
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

Why is this a ROLC i-d/RFC? 

This is just as much an ip-atm issue? I don't see any large-cloud-specific 
stuff in this draft, although I agree it is not atm-specific. 
The draft does, however, address many of the points raised by papers like 
the Framework document in ip-atm. Maybe it should be just an "IETF" or "IAB" 
draft? But in that case, you should probably give it wider circulation than 
just the ROLC list before RFCing it - I know many people who did not know of 
the existence of this draft because they are not interested in large clouds
and don't follow ROLC.

Also, might it not be a good idea to try to get some of these ideas on the
standards track, rather than letting them languish as "informational"?
Just a thought.

Andrew


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy 				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************