Re: draft-rekhter-ip-atm-architecture-00.txt
Andrew Smith <asmith@baynetworks.com> Wed, 10 May 1995 01:00 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13507;
9 May 95 21:00 EDT
Received: from maelstrom.acton.timeplex.com by IETF.CNRI.Reston.VA.US
id aa13503; 9 May 95 21:00 EDT
Received: (from root@localhost) by maelstrom.acton.timeplex.com
(8.6.9/ACTON-MAIN-1.2) id UAA05788 for rolc-out;
Tue, 9 May 1995 20:53:34 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com
[134.177.3.18]) by maelstrom.acton.timeplex.com (8.6.9/ACTON-MAIN-1.2) with
SMTP id UAA05783 for <rolc@maelstrom.acton.timeplex.com>;
Tue, 9 May 1995 20:53:28 -0400
Received: from BayNetworks.COM ([134.177.1.95]) by lightning.synoptics.com
(4.1/SMI-4.1) id AA16383; Tue, 9 May 95 17:50:14 PDT
Received: from milliways (milliways-sbf0.synoptics.com) by BayNetworks.COM
(4.1/SMI-4.1) id AA16743; Tue, 9 May 95 17:51:16 PDT
Received: by milliways (4.1/2.0N)
id AA07518; Tue, 9 May 95 17:54:24 PDT
Message-Id: <9505100054.AA07518@milliways>
Date: Tue, 9 May 95 17:54:24 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
To: ip-atm@matmos.hpl.hp.com, rolc@maelstrom.acton.timeplex.com
Subject: Re: draft-rekhter-ip-atm-architecture-00.txt
Cc: gja@thumper.bellcore.com
X-Orig-Sender: owner-rolc@maelstrom.timeplex.com
Precedence: bulk
X-Info: Submissions to rolc@maelstrom.timeplex.com
X-Info: [Un]Subscribe requests to rolc-request@maelstrom.timeplex.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
> 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 ********************************************************************************
- Re: draft-rekhter-ip-atm-architecture-00.txt Grenville Armitage
- draft-rekhter-ip-atm-architecture-00.txt yakov
- draft-rekhter-ip-atm-architecture-00.txt yakov
- Re: draft-rekhter-ip-atm-architecture-00.txt Andrew Smith
- draft-rekhter-ip-atm-architecture-00.txt yakov
- draft-rekhter-ip-atm-architecture-00.txt yakov
- Re: draft-rekhter-ip-atm-architecture-00.txt Curtis Villamizar
- draft-rekhter-ip-atm-architecture-00.txt yakov
- draft-rekhter-ip-atm-architecture-00.txt yakov
- Re: draft-rekhter-ip-atm-architecture-00.txt Jeffrey A. Buffum - Bay Networks