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

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24173; 24 Oct 95 20:08 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24169; 24 Oct 95 20:08 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id TAA11677; Tue, 24 Oct 1995 19:40:05 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id TAA17936 for rolc-out; Tue, 24 Oct 1995 19:51:00 -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 TAA17927 for <rolc@nexen.com>; Tue, 24 Oct 1995 19:50:57 -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 TAA11673 for <rolc@nexen.com>; Tue, 24 Oct 1995 19:39:49 -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 QAA26631; Tue, 24 Oct 1995 16:46:56 -0700
Message-Id: <199510242346.QAA26631@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 13:06:52 EDT." <199510241706.NAA12757@brookfield.ans.net>
Date: Tue, 24 Oct 95 16:46:55 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,

> It seems you want a term that covers the case where there is an
> address prefix that covers the NBMA network exactly.  I'll argue that
> this is a special case of an NBMA, so if anything, a separate term is
> needed so we can still talk about NBMA in which the is no address
> prefix that overlaps the NBMA exactly.  If you define the first term,
> the second is just "an address prefix that overlaps an NBMA exactly"
> (replacing NBMA for the term chosen).

I need a term that would cover a group of hosts on an NBMA network
with a router on the NBMA network that would act as the last hop router
for these hosts. The group of hosts may form a subset of all the 
hosts connected to the NBMA network. So, an NBMA network may have
more than one APR (more than one address prefix), but each APR
would have exactly one address prefix.

Yakov.