Re: [EME] EME charter

Yangwoo Ko <newcat@icu.ac.kr> Mon, 13 November 2006 06:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjUuR-0007a6-Ro; Mon, 13 Nov 2006 01:03:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjUuQ-0007WS-MD for eme@irtf.org; Mon, 13 Nov 2006 01:03:06 -0500
Received: from sniper.icu.ac.kr ([210.107.128.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GjUuO-0002p7-SX for eme@irtf.org; Mon, 13 Nov 2006 01:03:06 -0500
Received: (snipe 2156 invoked by uid 0); 13 Nov 2006 15:04:22 +0900
Received: from newcat@icu.ac.kr with Spamsniper 2.96.00 (Processed in 0.059018 secs);
Received: from unknown (HELO ?192.168.10.206?) (ZDI?own@210.107.250.150) by unknown with SMTP; 13 Nov 2006 15:04:22 +0900
X-RCPTTO: touch@ISI.EDU, wolf@ecs.umass.edu, eme@irtf.org
Message-ID: <45580A8A.3040707@icu.ac.kr>
Date: Mon, 13 Nov 2006 15:02:50 +0900
From: Yangwoo Ko <newcat@icu.ac.kr>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [EME] EME charter
References: <4557D5ED.9030807@ecs.umass.edu> <4558080D.60303@isi.edu>
In-Reply-To: <4558080D.60303@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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>
Errors-To: eme-bounces@irtf.org

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? 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.

Regards

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