Re: Last Call for draft-ietf-rolc-apr-00.txt (1)
Andrew Smith <asmith@baynetworks.com> Mon, 23 October 1995 22:40 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22036;
23 Oct 95 18:40 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa22023;
23 Oct 95 18:40 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com
(8.6.12/8.6.12) with ESMTP id SAA02914; Mon, 23 Oct 1995 18:16:48 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
SAA03722 for rolc-out; Mon, 23 Oct 1995 18:24:57 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id SAA03713 for
<rolc@nexen.com>; Mon, 23 Oct 1995 18:24:55 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com
[134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id SAA04683 for
<rolc@nexen.com>; Mon, 23 Oct 1995 18:23:57 -0400
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com
(4.1/SMI-4.1) id AA02567; Mon, 23 Oct 95 15:21:34 PDT
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by
pobox.synoptics.com (4.1/SMI-4.1)
id AA02650; Mon, 23 Oct 95 15:22:56 PDT
Received: by milliways-le0.engwest (4.1/SMI-4.1)
id AA20672; Mon, 23 Oct 95 15:22:55 PDT
Date: Mon, 23 Oct 95 15:22:55 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9510232222.AA20672@milliways-le0.engwest>
To: yakov@cisco.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt (1)
Cc: rolc@nexen.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/
> From yakov@cisco.com Mon Oct 23 09:23:33 1995 > To: asmith@BayNetworks.COM (Andrew Smith) > Cc: rolc@nexen.com > Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt (1) > Date: Mon, 23 Oct 95 09:20:26 PDT > From: Yakov Rekhter <yakov@cisco.com> Yakov, > > 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 ? In the references section 9. You already mention LANE in the text in section 6, page 8. BTW, since section 6 is supposed to be just conclusions, maybe it would be more appropriate to bring in the mentions of LANE and MPOA as other examples of ATM technologies earlier on e.g. in the "background" section 1 . > > > > 4. Maybe mention MPOA somehow? > > > Again, we could probably do this... Where would you like to stick such reference ? See above. Difficult to find a concrete document to cite as a reference right now :-) I do, however, think it worthwhile in an information RFC to point readers at where the standards-track work *is* going on. > Yakov. > Andrew ******************************************************************************** Andrew Smith TEL: +1 408 764 1574 Technology Synergy Unit FAX: +1 408 988 5525 Bay Networks, Inc. E-m: asmith@baynetworks.com Santa Clara, CA ********************************************************************************
- Re: Last Call for draft-ietf-rolc-apr-00.txt (1) Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt (1) Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt (1) Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt (1) Andrew Smith