IETF Logo Mail Archive

Re: [EME] EME charter

Joe Touch <touch@ISI.EDU> Mon, 13 November 2006 16:26 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjedj-000371-19; Mon, 13 Nov 2006 11:26:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjedh-00036l-Ro for eme@irtf.org; Mon, 13 Nov 2006 11:26:29 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gjedf-0001XK-Gj for eme@irtf.org; Mon, 13 Nov 2006 11:26:29 -0500
Received: from [127.0.0.1] (pool-71-106-94-15.lsanca.dsl-w.verizon.net [71.106.94.15]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id kADGMaPH020957; Mon, 13 Nov 2006 08:22:36 -0800 (PST)
Message-ID: <45589BCA.5090902@isi.edu>
Date: Mon, 13 Nov 2006 08:22:34 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
Subject: Re: [EME] EME charter
References: <C17E007E.17EC9%mshore@cisco.com>
In-Reply-To: <C17E007E.17EC9%mshore@cisco.com>
X-Enigmail-Version: 0.94.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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="===============0247895582=="
Errors-To: eme-bounces@irtf.org


Melinda Shore wrote:
> On 11/13/06 1:10 AM, "Fergie" <fergdawg@netzero.net> wrote:
>> Having said that, I would tend to think that endpoints can defined
>> as the source (originator) & destination addresses in any IP
>> packet.
> 
> One layer's endpoint is another layer's middlebox.  For example,
> relays are, unfortunately, increasingly common in VoIP networks
> and while they're effectively transparent to the application
> peers they are being addressed directly.

Agreed. I've had a definition for a while derived from the well-known:

 	hardware: that which can be kicked

	software: everything else

------

My definition of "endpoint":

	endpoint: that which *I* can kick

	middle: everything else

Joe


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

v2.23.0 | Report a Bug | By Email