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

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15120; 23 Oct 95 12:56 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15116; 23 Oct 95 12:55 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA29870; Mon, 23 Oct 1995 12:27:51 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id MAA27990 for rolc-out; Mon, 23 Oct 1995 12:37:07 -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 MAA27981 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:37:04 -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 MAA29797 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:26:10 -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 JAA06681; Mon, 23 Oct 1995 09:33:08 -0700
Message-Id: <199510231633.JAA06681@hubbub.cisco.com>
To: Andrew Smith <asmith@baynetworks.com>
cc: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt (1)
In-reply-to: Your message of "Fri, 20 Oct 95 13:29:59 PDT." <9510202029.AA19258@milliways-le0.engwest>
Date: Mon, 23 Oct 1995 09:33:08 -0700
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,

> Editorial stuff:
> 
> 1. There's a typo on p3: grep for RFC1597.

Ok. I'll fix it.

> 
> 2. How should we reference the NHRP work here? Not allowed to reference
> internet-drafts.

We could either (a) remove  NHRP from the Reference section, or (b) refer
to NHRP as "work in progress". I'd like to get Joel's opinion on this
(as he is the Routing AD and should tell us what is more appropriate).

> 
> 3. Are RFCs allowed to reference ATM Forum documents? Should probably
> reference LANE (ftp://atmforum.com/pub/LANE/af-lane-0021.000)
> since it is mentioned in the text.

I can certainly stick reference to LANE. Where in the text would you
suggest to put it.


> 
> 4. Maybe mention MPOA somehow?

Again, please suggest where to put it and I'll stick it in.

Yakov.