Re: Network Edge definition (Re: An alternative to TCP (part 1))
"Michael W. Condry" <condry@intel.com> Wed, 28 February 2001 17:40 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15551 for ietf-outbound.10@ietf.org; Wed, 28 Feb 2001 12:40:04 -0500 (EST)
Received: from ganymede.or.intel.com (jffdns01.or.intel.com [134.134.248.3]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA15252 for <ietf@ietf.org>; Wed, 28 Feb 2001 12:31:47 -0500 (EST)
Received: from condryvaio-desk.intel.com (condryvaio-desk.jf.intel.com [134.134.159.80]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.35 2001/02/12 09:03:45 smothers Exp $) with ESMTP id RAA27051; Wed, 28 Feb 2001 17:30:57 GMT
Message-Id: <5.0.2.1.2.20010228092714.01ef9bf0@FMSMSX63.fm.intel.com>
X-Sender: mwcondry@FMSMSX63.fm.intel.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 28 Feb 2001 09:29:00 -0800
To: Harald Alvestrand <Harald@Alvestrand.no>, joaquin.riverarodriguez@telefonica-data.com, jag@kw.com.cn
From: "Michael W. Condry" <condry@intel.com>
Subject: Re: Network Edge definition (Re: An alternative to TCP (part 1))
Cc: ietf@ietf.org
In-Reply-To: <4.3.2.7.2.20010208120715.0588ecb0@127.0.0.1>
References: <C12569ED.002D1528.00@notes06.telefonica-data.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Loop: ietf@ietf.org
When we consider applications services there are many logical points to call the network edge, for just one example see draft-erickson-opes-taxonomy-00.txt At 12:10 PM 2/8/2001 +0100, Harald Alvestrand wrote: >At 09:17 08/02/2001 +0100, joaquin.riverarodriguez@telefonica-data.com wrote: >>Anyway, I agree with Mr Gao that it will be usefull to have a distinguishing >>name for the last network element, something like ONE "outest network >>element" >>or END "edge netework device" or any other that may be chosen. > >I think the (layer 3) network edge is inside my computer, where the TCP >stacks interfaces to the applications. The layer 7 network edge is even >further in. > >A much mmore interesting edge is the edge of a control area (where the >corporate edge meets the ISP edge, or where the corporate network meets my >in-house network, for instance). > >Very few things change where my drop-cable plugs into my hub. > >-- >Harald Tveit Alvestrand, alvestrand@cisco.com >+47 41 44 29 94 >Personal email: Harald@Alvestrand.no Michael W. Condry Director, Network Edge Technology
- RE: An alternative to TCP (part 1) aaron
- An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Valdis.Kletnieks
- Re: An alternative to TCP (part 1) John Stracke
- Re: An alternative to TCP (part 1) stanislav shalunov
- RE: An alternative to TCP (part 1) Christian Huitema
- RE: An alternative to TCP (part 1) Larry Foore
- RE: An alternative to TCP (part 1) Tony Hain
- Re: An alternative to TCP (part 1) stanislav shalunov
- RE: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Larry Foore
- Re: An alternative to TCP (part 1) Keith Moore
- Re: An alternative to TCP (part 1) Colin Perkins
- Re: An alternative to TCP (part 1) Rahmat M. Samik-Ibrahim
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jon Crowcroft
- Re: An alternative to TCP (part 1) Richard Carlson
- Re: An alternative to TCP (part 1) John Stracke
- Re: An alternative to TCP (part 1) Harald Alvestrand
- Re: An alternative to TCP (part 1) Bob Braden
- Re: An alternative to TCP (part 1) Keith Moore
- Re: An alternative to TCP (part 1) Mark Allman
- Re: An alternative to TCP (part 1) Kevin Farley
- Re: An alternative to TCP (part 1) Mahadevan Iyer
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Larry Foore
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) joaquin.riverarodriguez
- Re: An alternative to TCP (part 1) Jun'an Gao
- Network Edge definition (Re: An alternative to TC… Harald Alvestrand
- Re: An alternative to TCP (part 1) John Stracke
- RE: An alternative to TCP (part 1) Iliff, Tina
- Re: Network Edge definition (Re: An alternative t… Joe Touch
- Re: An alternative to TCP (part 1) Randall R. Stewart
- RE: An alternative to TCP (part 1) Bernard Aboba
- Re: An alternative to TCP (part 1) tytso
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Bernard Aboba
- Re: Network Edge definition (Re: An alternative t… Marvin Sanchez Garache
- Re: An alternative to TCP (part 1) Randall R. Stewart
- Re: An alternative to TCP (part 1) Randall R. Stewart
- Re: Network Edge definition (Re: An alternative t… Lloyd Wood
- RE: Network Edge definition (Re: An alternative t… Bojan Lekovic
- Not developing protocols (was: Re: An alternative… John Stracke
- Re: An alternative to TCP (part 1) Richard Carlson
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: Not developing protocols Ofer Inbar
- Re: An alternative to TCP (part 1) Mark Allman
- Re: An alternative to TCP (part 1) Fred Baker
- Re: An alternative to TCP (part 1) James P. Salsman
- Re: Network Edge definition (Re: An alternative t… Michael W. Condry