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

Curtis Villamizar <curtis@ans.net> Tue, 24 October 1995 19:34 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19450; 24 Oct 95 15:34 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa19446; 24 Oct 95 15:34 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id PAA09370; Tue, 24 Oct 1995 15:06:18 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id PAA14892 for rolc-out; Tue, 24 Oct 1995 15:15:33 -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 PAA14883 for <rolc@nexen.com>; Tue, 24 Oct 1995 15:15:30 -0400
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 PAA09354 for <rolc@nexen.com>; Tue, 24 Oct 1995 15:04:15 -0400
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 PAA13393 for <rolc@nexen.com>; Tue, 24 Oct 1995 15:14:09 -0400
Message-Id: <199510241914.PAA13393@brookfield.ans.net>
To: rolc@nexen.com
Reply-To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
Date: Tue, 24 Oct 1995 15:14:08 -0400
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/

Just following instructions.  (almost) I removed one of my comments.
Joel fired off I think 3 separate notes.  I think he just meant this
one.

------- Forwarded Message

Received: from interlock.ans.net (interlock.ans.net [147.225.5.2]) by brookfield.ans.net (8.6.12/8.6.12) with SMTP id OAA13101 for <curtis@brookfield.ans.net>et>; Tue, 24 Oct 1995 14:11:42 -0400
Received: from ns.Newbridge.Com by interlock.ans.net with SMTP id AA15763
  (InterLock SMTP Gateway 3.0 for <curtis@ans.net>)t>);
  Tue, 24 Oct 1995 14:08:57 -0400
Received: (from adm@localhost) by ns.newbridge.com (8.6.12/8.6.12) id NAA22976 for <curtis@ans.net>et>; Tue, 24 Oct 1995 13:39:48 -0400
Received: from portero(192.75.23.66) by ns via smap (V1.3)
	id sma022965; Tue Oct 24 13:39:24 1995
Received: from mako.us.Newbridge.com (mako.us.newbridge.com [138.120.85.99]) by kanmaster.ca.newbridge.com (8.6.12/8.6.12) with SMTP id NAA13879 for <curtis@ans.net>et>; Tue, 24 Oct 1995 13:39:20 -0400
Received: from lobster.Newbridge.COM by mako.us.Newbridge.com (4.1/SMI-4.0)
	id AA09197; Tue, 24 Oct 95 13:34:32 EDT
Received: by lobster.Newbridge.COM (5.0/SMI-SVR4)
	id AA12328; Tue, 24 Oct 1995 13:38:25 +0500
Date: Tue, 24 Oct 1995 13:38:25 +0500
From: jhalpern@Newbridge.COM (Joel Halpern)
Message-Id: <9510241738.AA12328@lobster.Newbridge.COM>
To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
X-Sun-Charset: US-ASCII
Content-Length: 1512

Would you please send your note (with my comments) to the list.
I think the discussion will help others.  (I meant to send it to the
list myself, but sent it too soon.)

Thanks,
Joel


- ----- Begin Included Message -----

>From curtis@brookfield.ans.net Tue Oct 24 13:32:02 1995
To: jhalpern@ca.newbridge.com (Joel Halpern)
Cc: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt 
Date: Tue, 24 Oct 1995 13:39:00 -0400
From: Curtis Villamizar <curtis@ans.net>


In message <9510241631.AA12285@lobster.Newbridge.COM>OM>, Joel Halpern writes:
> If Yakov's document said that APR=whole NBMA network, then I missed it.
> I certainly would not agree with that.  I am pretty sure that it was not
> his intent.  If you can find where it said that, I would like to fix it.

It sounds like you interpretation of an APR is a prefix that falls
entirely within an NBMA.

> The problem here may be related to that fact that the primary applicability
> of an APR is for operation over an NBMA network.  Some of the descriptive
> text may need repair to avoid implying the wrong meaning.

Yes.  We need to be clear as to whether this is a subset or an exact
match for an NBMA.

> Yours,
> Joel M. Halpern				jhalpern@newbridge.com
> Newbridge Networks Inc. 

Regards,

Curtis


- ----- End Included Message -----



------- End of Forwarded Message