Re: [EME] EME charter

Saikat Guha <saikat@cs.cornell.edu> Mon, 13 November 2006 18:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjgWX-0006vv-UR; Mon, 13 Nov 2006 13:27:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjgWW-0006vq-TD for eme@irtf.org; Mon, 13 Nov 2006 13:27:12 -0500
Received: from exchfenlb-2.cs.cornell.edu ([128.84.97.34] helo=exchfe2.cs.cornell.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GjgWV-0001Vv-Ma for eme@irtf.org; Mon, 13 Nov 2006 13:27:12 -0500
Received: from exchfe2.cs.cornell.edu ([128.84.97.28]) by exchfe2.cs.cornell.edu with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Nov 2006 13:27:11 -0500
Received: from [172.23.16.54] ([172.23.16.54]) by exchfe2.cs.cornell.edu over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Nov 2006 13:27:10 -0500
Subject: Re: [EME] EME charter
From: Saikat Guha <saikat@cs.cornell.edu>
To: Fergie <fergdawg@netzero.net>
In-Reply-To: <20061112.221056.5535.1439635@webmail13.lax.untd.com>
References: <20061112.221056.5535.1439635@webmail13.lax.untd.com>
Organization: Cornell University
Date: Mon, 13 Nov 2006 13:27:53 -0500
Message-Id: <1163442473.4894.54.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5)
X-OriginalArrivalTime: 13 Nov 2006 18:27:10.0273 (UTC) FILETIME=[54F97B10:01C70751]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: eme@irtf.org
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0464714437=="
Errors-To: eme-bounces@irtf.org

On Mon, 2006-11-13 at 06:10 +0000, Fergie wrote:
> Having said that, I would tend to think that endpoints can defined
> as the source (originator) & destination addresses in any IP
> packet.

What about IP source route where the destination keeps changing :-p

From the perspective of the IP, it makes sense to define the IP endpoint
as the source or destination of a datagram. This definition on its own
causes problems in the presence of mobility and multi-homing.

From a broader perspective, one potential definition 
may be: 
      the application instances that are trying to 
      communicate over the Internet. 

For example, a web browser and a web server are application instances
trying to communicate -- HTTP endpoints. The Internet enables these
endpoints to communicate by, under the hood, managing multiple IP
addresses, picking TCP or SCTP or other appropriate transports,
discovering and invoking in-network middlebox functionality such as NAT
and firewalls as directed by local network administrators, etc.

-- 
Saikat
_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme