The Routing Over Large Clouds Mailing List Archive by date

[Andrew Smith <asmith@baynetworks.com>]

> From atmpost@matmos.hpl.hp.com Tue May  9 12:59:35 1995
> To: yakov@watson.ibm.com
> Cc: ip-atm@matmos.hpl.hp.com, rolc@maelstrom.acton.timeplex.com,
>         gja@thumper.bellcore.com
> Subject: Re: draft-rekhter-ip-atm-architecture-00.txt 
> In-Reply-To: Your message of Tue, 09 May 1995 15:12:20 -0400.
>              <199505091913.AA256446802@matmos.hpl.hp.com> 
> Date: Tue, 09 May 1995 15:38:46 -0400
> From: Grenville Armitage <gja@thumper.bellcore.com>
 
> >>So, let's propose to use the term "ASP" -- Application Specific
> >>Partition.
> 
> 'Partition' sounds so much like open-plan offices, but I suppose
> I can see why Application Specific Scope would have problems :)

At the ATM Forum acronym brainstorming session today we came up with
many different aspects of the "subnet" word (all applicable to IP)
including some or all of the following: 

- Unit of address summarisation in routing protocols
- Set of stations with direct layer 2 connectivity
- Scope of internetwork-layer broadcasts.
- Set of addresses a host should directly "ARP" for.
- Set of stations one hop apart (TTL=0 on the wire)
- Layer 2 broadcast scope

I think that the chances of finding a single definition/acronym for
use in draft-rekhter-ip-atm-architecture-00.txt is quite small but
maybe only a few of these are relevant from the point of view of 
this draft.

> gja
> 

Andrew


P.S. I'm not at liberty to disclose the official acronyms for all of these
terms as they might change tomorrow :-)



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