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

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15057; 23 Oct 95 12:53 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa15053; 23 Oct 95 12:53 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA29785; Mon, 23 Oct 1995 12:25:44 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id MAA27767 for rolc-out; Mon, 23 Oct 1995 12:24:26 -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 MAA27758 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:24:23 -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 MAA29670 for <rolc@nexen.com>; Mon, 23 Oct 1995 12:13:29 -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 JAA05587; Mon, 23 Oct 1995 09:20:27 -0700
Message-Id: <199510231620.JAA05587@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:20:26 -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,

> 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 can either take it out of the Reference section, or keep in the
Reference section and label it "work in progress". I hope that either Andy
or Joel would suggest how to deal with this.

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

We can certainly mention ATM Forum documents (although the document is not limited to 
ATM (and LANE)). Where in the text would you suggest to stick this reference ?

> 
> 4. Maybe mention MPOA somehow?
> 
Again, we could probably do this... Where would you like to stick such reference ?

Yakov.