Re: [EME] EME charter

Melinda Shore <mshore@cisco.com> Mon, 13 November 2006 18:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjgrn-00062W-B4; Mon, 13 Nov 2006 13:49:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjgrl-00061i-Vi for eme@irtf.org; Mon, 13 Nov 2006 13:49:09 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GjgjT-0003EU-Ho for eme@irtf.org; Mon, 13 Nov 2006 13:40:38 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-5.cisco.com with ESMTP; 13 Nov 2006 10:40:34 -0800
X-IronPort-AV: i="4.09,418,1157353200"; d="scan'208"; a="344349026:sNHT1264768756"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kADIeXeI002088; Mon, 13 Nov 2006 13:40:33 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kADIeXYJ023973; Mon, 13 Nov 2006 13:40:33 -0500 (EST)
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Nov 2006 13:40:33 -0500
Received: from 128.107.177.244 ([128.107.177.244]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([171.70.151.187]) with Microsoft Exchange Server HTTP-DAV ; Mon, 13 Nov 2006 18:40:33 +0000
User-Agent: Microsoft-Entourage/11.2.3.060209
Date: Mon, 13 Nov 2006 13:40:31 -0500
Subject: Re: [EME] EME charter
From: Melinda Shore <mshore@cisco.com>
To: Joe Touch <touch@ISI.EDU>, Saikat Guha <saikat@cs.cornell.edu>
Message-ID: <C17E264F.17FBC%mshore@cisco.com>
Thread-Topic: [EME] EME charter
Thread-Index: AccHUzI+cQUsEXNGEduQBwAKleNSdA==
In-Reply-To: <4558B979.8040300@isi.edu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 13 Nov 2006 18:40:33.0517 (UTC) FILETIME=[33BEC9D0:01C70753]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1118; t=1163443233; x=1164307233; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20<mshore@cisco.com> |Subject:=20Re=3A=20[EME]=20EME=20charter |Sender:=20 |To:=20Joe=20Touch=20<touch@ISI.EDU>, =20Saikat=20Guha=20<saikat@cs.cornel l.edu>; bh=H78Gl2bokRkCr6Sp6fmyN0FkuN2QlrRMQfVJ75sIFIk=; b=XV0kPnONfZjrGDgr2BII+Gsogl2tx1CzbhJ3B2PHgN3NSWnRSiWpZehDrlw8x1EO/0Z0HXyJ 06wWtyUHH9C5l7Z6J1S4mBz1phy680cTMUKaZ0X4pcI/n9Y4qLaOouS7;
Authentication-Results: rtp-dkim-2; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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

On 11/13/06 1:29 PM, "Joe Touch" <touch@ISI.EDU> wrote:
> The real reason is that some middlebox designer somewhere thought they
> knew better than the person at the endpoint about what an E2E
> communication was supposed to do.

I think a lot of what's driving this has more to do with 1) maladapted
business models, and 2) perceptions around security, actually.  This is
particularly true around voice where on the one hand there's a higher
level of comfort with control plane/data plane separation and on the
other a tendency to solve problems that crop up by dropping more stuff
into the network (and granted, it's a lot easier to add new things than
it is to remove or change existing ones).  The enterprise case is somewhat
more complicated since there's a different relationship with users (they
aren't customers in the traditional sense) and there's a different
relationship to the network's assets.  I think that a lot of what's going
wrong on networks today, at least around middleboxes, has economic
roots rather than technical ones.  I don't have a clue what to do about
that.

Melinda

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