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

Andrew Smith <asmith@baynetworks.com> Tue, 24 October 1995 21:17 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22138; 24 Oct 95 17:17 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa22134; 24 Oct 95 17:17 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA10371; Tue, 24 Oct 1995 16:49:33 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id RAA16354 for rolc-out; Tue, 24 Oct 1995 17:00:17 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id RAA16345 for <rolc@nexen.com>; Tue, 24 Oct 1995 17:00:14 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id QAA25567 for <rolc@nexen.com>; Tue, 24 Oct 1995 16:59:15 -0400
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA21172; Tue, 24 Oct 95 13:56:49 PDT
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA24588; Tue, 24 Oct 95 13:58:11 PDT
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA21893; Tue, 24 Oct 95 13:58:10 PDT
Date: Tue, 24 Oct 95 13:58:10 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9510242058.AA21893@milliways-le0.engwest>
To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
Cc: rolc@nexen.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,

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

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

> 
> Curtis
> 


Andrew


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy     				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************