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

Curtis Villamizar <curtis@ans.net> Wed, 01 November 1995 15:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13212; 1 Nov 95 10:50 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa13208; 1 Nov 95 10:50 EST
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id KAA24683; Wed, 1 Nov 1995 10:23:54 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id KAA17485 for rolc-out; Wed, 1 Nov 1995 10:35:24 -0500
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 KAA17476; Wed, 1 Nov 1995 10:35:21 -0500
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id KAA24671; Wed, 1 Nov 1995 10:22:42 -0500
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1]) by brookfield.ans.net (8.6.12/8.6.12) with ESMTP id KAA04864; Wed, 1 Nov 1995 10:32:27 -0500
Message-Id: <199511011532.KAA04864@brookfield.ans.net>
To: "Andrew G. Malis" <malis@nexen.com>
cc: Andrew Smith <asmith@baynetworks.com>, rolc@nexen.com
Reply-To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Wed, 01 Nov 1995 09:55:08 EST." <199511011455.JAA07327@phish.nexen.com>
Date: Wed, 01 Nov 1995 10:32:27 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Curtis Villamizar <curtis@ans.net>
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/

In message <199511011455.JAA07327@phish.nexen.com>, "Andrew G. Malis" writes:
> 
> > I think that it would also be productive to have a discussion on this 
> > draft at the IETF meeting before forwarding to the AD. The ROLC session
> > does not overlap with int-serv, ip-atm or rsvp so we should be
> > able to get the relevant contributors from those groups together.
> 
> I would like to ask the WG's consensus on this.  We currently have one
> session scheduled.  If we expect a lot of discussion at the IETF on
> the draft, we may want to schedule a second session just for that
> purpose.  Comments?

If this draft was sent to int-serv or rsvp in the first place you
would have recieved a lot of comments from people on those lists that
don't lurk on the rolc list.

You might want to have some discussion at Dallas and forward a note
about this draft to int-serv and rolc prior to the meeting to get
comments.  This will avoid sending a draft with insufficient review to
the AD and getting a barrage of comments when the draft hits
ietf-announce (clearly less desirable).

Curtis