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

Yakov Rekhter <yakov@cisco.com> Mon, 23 October 1995 16:54 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15096; 23 Oct 95 12:54 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15092; 23 Oct 95 12:54 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA29783; Mon, 23 Oct 1995 12:25:42 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id MAA27912 for rolc-out; Mon, 23 Oct 1995 12:33:29 -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 MAA27903 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:33:27 -0400
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA29754 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:22:34 -0400
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by hubbub.cisco.com (8.6.12/CISCO.GATE.1.1) with SMTP id JAA06338; Mon, 23 Oct 1995 09:29:32 -0700
Message-Id: <199510231629.JAA06338@hubbub.cisco.com>
To: Andrew Smith <asmith@baynetworks.com>
cc: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt (2)
In-reply-to: Your message of "Fri, 20 Oct 95 13:37:55 PDT." <9510202037.AA19263@milliways-le0.engwest>
Date: Mon, 23 Oct 95 09:29:32 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.com>
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/

Andrew,

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

These are mostly procedural questions, and I hope that either Joel (as the Routing AD)
or Andy (as the ROLC WG chair) would be in a better position to answer them.

Yakov.