Re: [EME] EME charter

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjgCG-0000dl-8s; Mon, 13 Nov 2006 13:06:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjgCF-0000dK-H9 for eme@irtf.org; Mon, 13 Nov 2006 13:06:15 -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 1GjgCE-0006oy-9O for eme@irtf.org; Mon, 13 Nov 2006 13:06:15 -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:06:13 -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:06:12 -0500
Subject: Re: [EME] EME charter
From: Saikat Guha <saikat@cs.cornell.edu>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <4558080D.60303@isi.edu>
References: <4557D5ED.9030807@ecs.umass.edu> <4558080D.60303@isi.edu>
Organization: Cornell University
Date: Mon, 13 Nov 2006 13:06:52 -0500
Message-Id: <1163441212.4894.34.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:06:12.0311 (UTC) FILETIME=[672BB670:01C7074E]
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="===============1351466804=="
Errors-To: eme-bounces@irtf.org

On Sun, 2006-11-12 at 21:52 -0800, Joe Touch wrote:
> Problem-causing middleboxes don't *want* to be found; they want to be
> "transparent".
> 
> Resolving - or prohibiting - that transparency should be included and
> addressed.

Middleboxes that are _truly transparent_ are not problematic (by
definition almost). Translucent middleboxes, on the other hand, should
indeed be addressed.

One reason such translucent middleboxes exist is that there is no way
for the middle to inform the end of policy much less require the end to
enforce it (the corporate firewall case). Another reason is that the end
cannot effectively direct the middle (the NAT case); perhaps NATs would
have been less problematic if source route was a first class citizen in
the Internet or DNS names carried end-to-end in packets. 

To the extent that the lack of middle-to-end and end-to-middle
communication prevents middleboxes from being truly transparent (to the
app layer) or fully visible (to the network layer), EME resolves to
address the problem IMHO.

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