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

Curtis Villamizar <curtis@ans.net> Wed, 25 October 1995 22:32 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20791; 25 Oct 95 18:32 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa20787; 25 Oct 95 18:32 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id RAA19503; Wed, 25 Oct 1995 17:58:22 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id SAA00988 for rolc-out; Wed, 25 Oct 1995 18:09:11 -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 SAA00979 for <rolc@nexen.com>; Wed, 25 Oct 1995 18:09:09 -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 RAA19499 for <rolc@nexen.com>; Wed, 25 Oct 1995 17:57:50 -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 SAA18653; Wed, 25 Oct 1995 18:08:24 -0400
Message-Id: <199510252208.SAA18653@brookfield.ans.net>
To: Yakov Rekhter <yakov@cisco.com>
cc: curtis@ans.net, rolc@nexen.com
Reply-To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Wed, 25 Oct 1995 10:55:48 PDT." <199510251755.KAA19690@hubbub.cisco.com>
Date: Wed, 25 Oct 1995 18:08:24 -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/

In message <199510251755.KAA19690@hubbub.cisco.com>om>, Yakov Rekhter writes:
> Curtis,
> 
> > I also don't see that we need a new term for describe a prefix which
> > covers a subset of the NBMA or covers the NBMA completely.  (Or
> > whatever APR was supposed to mean).
> 
> As you may remember, this document used the term LIS. However, at the
> IP-ATM WG meeting, when I presented this document it was quite clear
> consensus that a new term is needed, as the semantics (and constraints)
> of APR are different from an IP subnet (or LIS).
> 
> Yakov.


Yakov,

I remeber the following points made during that discussion:

  subnet - a small atomic unit that generally has a single prefix

    note: all hosts within a subnet prefix are considered directly
    reachable on the subnet.  There may be more than one prefix on a
    subnet, but a subnet prefix always exactly overlaps the subnet.
    (ignoring ugly proxy arp based hacks).

  network - one or more subnets connected by routing

    note:  network number is obsoleted by CIDR.  may have multiple
    prefixes as in the valid usage <org name's> network.

  internetwork - more than one network connected by routing

    generally assumed to have multiple prefixes

RFC1577 uses LIS rather than subnet so as not to confuse the OSI guys.

Currently network implies subnets connected by routing *only*.  The
notion of cut-through allows direct connections across subnets without
IP forwarding.

In an NBMA subnet (subnet often implied as in "for an NBMA OSPF
does..."), there is no broadcast, and all hosts are interconnected.
In a large NBMA network, there may be multiple NBMA subnets and from a
layer 2 standpoint all hosts are interconnected.

We need a term which defines the region for which cut-through or
direct connection is possible.  The term NBMA network fits well but
the term is defined as something that doesn't support broadcast so a
another term is wanted (maybe not needed, but wanted).

This is different from the set of prefixes covered by the NBMA.  I
don't remember a call for a new term to describe a prefix that falls
within an NBMA network.

Curtis