Re: [EME] EME charter

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjUl1-0002Ei-2w; Mon, 13 Nov 2006 00:53:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjUkz-0002EW-Ns for eme@irtf.org; Mon, 13 Nov 2006 00:53:21 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GjUky-0001mi-D0 for eme@irtf.org; Mon, 13 Nov 2006 00:53:21 -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 kAD5qG53029661; Sun, 12 Nov 2006 21:52:16 -0800 (PST)
Message-ID: <4558080D.60303@isi.edu>
Date: Sun, 12 Nov 2006 21:52:13 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Tilman Wolf <wolf@ecs.umass.edu>
Subject: Re: [EME] EME charter
References: <4557D5ED.9030807@ecs.umass.edu>
In-Reply-To: <4557D5ED.9030807@ecs.umass.edu>
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: 769a46790fb42fbb0b0cc700c82f7081
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="===============1015992335=="
Errors-To: eme-bounces@irtf.org


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


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