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

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14513; 25 Oct 95 13:53 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa14509; 25 Oct 95 13:53 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id NAA16105; Wed, 25 Oct 1995 13:15:27 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id NAA26219 for rolc-out; Wed, 25 Oct 1995 13:14:35 -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 NAA26210 for <rolc@nexen.com>; Wed, 25 Oct 1995 13:14: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 NAA15979 for <rolc@nexen.com>; Wed, 25 Oct 1995 13:03:11 -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 NAA17532; Wed, 25 Oct 1995 13:13:51 -0400
Message-Id: <199510251713.NAA17532@brookfield.ans.net>
To: Andrew Smith <asmith@baynetworks.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 "Tue, 24 Oct 1995 13:58:10 PDT." <9510242058.AA21893@milliways-le0.engwest>
Date: Wed, 25 Oct 1995 13:13:46 -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 <9510242058.AA21893@milliways-le0.engwest>st>, Andrew Smith writes:
> 
> Curtis,
> 
> > IMO Internetwork Address Sub-Group is about as obscure as you can get.
> 
> Yes - deliberately so. In MPOA we needed a term that carried absolutely
> no connotations of connectivity or the lack of it. This was purely a
> term for describing address summarisation. I think that is also the
> term that you are looking for. I, too, think that APR is the
> wrong term for what Yakov is describing - his term carries some connectivity
> implications with it, at least as currently defined in draft-ietf-rolc-apr-00
> .
> 
> > ....
> 
> We still need your NBMA definition.

Are you suggesting that we adapt IASG and give it no meaning at all so
that when we figure out what it is for the choice of term won't
conflict with the eventual usage?  Or are you being sarcastic?

Sounds like you wan a new term for NBMA.  I'll agree one is needed.

> > 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, 
> 
> Agreed - for this special case it is not worth inventing a new TLA or FLA.

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).

> Andrew

Curtis