Re: [EME] EME charter

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjd6B-0002Sc-Li; Mon, 13 Nov 2006 09:47:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjd6A-0002SW-DK for eme@irtf.org; Mon, 13 Nov 2006 09:47:46 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gjd69-0005DD-1V for eme@irtf.org; Mon, 13 Nov 2006 09:47:46 -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 kADEkaUF029150; Mon, 13 Nov 2006 06:46:37 -0800 (PST)
Message-ID: <4558854A.4040707@isi.edu>
Date: Mon, 13 Nov 2006 06:46:34 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Yangwoo Ko <newcat@icu.ac.kr>
Subject: Re: [EME] EME charter
References: <4557D5ED.9030807@ecs.umass.edu> <4558080D.60303@isi.edu> <45580A8A.3040707@icu.ac.kr>
In-Reply-To: <45580A8A.3040707@icu.ac.kr>
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: 41c17b4b16d1eedaa8395c26e9a251c4
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="===============0464343902=="
Errors-To: eme-bounces@irtf.org


Yangwoo Ko wrote:
> 
> Joe Touch wrote:
>>
>> Tilman Wolf wrote:
>> ...
>>> The EME charter can be found at
>>> http://irtf.org/charter?gtype=rg&group=eme . The goal of our research
>>> group is to explore issues related to "middleboxes," i.e., devices that
>>> are placed inside the network along the end-to-end communication path.
>>> Our next immediate milestones are to develop an applicability statement
>>> followed by a design choices document.
>>
>> Some feedback on the charter. It talks about middleboxes that endpoints
>> don't know about, as if the endpoint is the problem.
>>
>> Problem-causing middleboxes don't *want* to be found; they want to be
>> "transparent".
>>
>> Resolving - or prohibiting - that transparency should be included and
>> addressed.
>>
>> Joe
> 
> I agree with the argument that "transparency" is problematic.
> By the way, if they are not transparent, why should we call
> them as "middleboxes" ? Aren't they just end-points? 

I was hoping someone would get to that point ;-)

> It seems
> to be necessary to differentiate middleboxes that are well
> identified and explicitly exploited by end-points and that
> are trying to be transparent.

If the former are endpoints (E2E RG focus), and the latter are
impossible to 'please', what's left for EME?

Joe

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