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

Yakov Rekhter <yakov@cisco.com> Wed, 25 October 1995 00:04 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24137; 24 Oct 95 20:04 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24133; 24 Oct 95 20:04 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id TAA11590; Tue, 24 Oct 1995 19:31:24 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id TAA17855 for rolc-out; Tue, 24 Oct 1995 19:41:43 -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 TAA17846 for <rolc@nexen.com>; Tue, 24 Oct 1995 19:41:40 -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 TAA11583 for <rolc@nexen.com>; Tue, 24 Oct 1995 19:30:32 -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 QAA25871; Tue, 24 Oct 1995 16:37:25 -0700
Message-Id: <199510242337.QAA25871@hubbub.cisco.com>
To: curtis@ans.net
cc: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Tue, 24 Oct 95 11:50:28 EDT." <199510241550.LAA12436@brookfield.ans.net>
Date: Tue, 24 Oct 95 16:37:25 PDT
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/

Curtis,

> > I have no problems of describing the decoupling the "local/remote"
> > outcome from the addressing information as "an extension" (or probably
> > "evolution").
> 
> IMO Declaring a "new IP architecture" is generally a bad thing to do
> unless that is closer to what you are doing.  This is a minor
> extension.

Ok. I'll change the text to describe the change as "a minor extension".

> Another key point (from the off list exchange):
> 
> A new term was needed for "a specific subset of the internetwork
> topology in which the underlying network does not prevent all hosts or
> routers from being directly reachable without IP forwarding to an
> intermediate party".  This has nothing to do with addressing and any
> overlap with an address prefix, whether intentional or coincidental,
> does not define the region.  The term "address prefix region" is
> absolutely the wrong term.  The old terms commonly used were "NBMA
> network" or "subnet in the OSI sense".  You need to pick a term that
> clearly reflects what you are describing.
> 
> You are proposing to decouple addressing and then defining a term that
> couples "aka NBMA network" with an address prefix.  Fix the ommision
> of hop-by-hop QoS and one hop off the NBMA procedures and get rid of
> the coupling with address prefix entirely and I'll wholeheartedly
> support the draft.

I'll certainly include the reference to the hop-by-hop QoS. Likewise, I'll
add "one hop off the NBMA procedures".  However, the address prefix has to
be retained, as it provides coupling between hosts and routers on the NBMA
network (a router on the NBMA network may act as a last hop for only a subset 
of all the hosts connected to the NBMA network). 

Yakov.