Re: [rrg] Terminology

jnc@mercury.lcs.mit.edu (Noel Chiappa) Wed, 03 February 2010 23:49 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20AA628B23E for <rrg@core3.amsl.com>; Wed, 3 Feb 2010 15:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.403
X-Spam-Level:
X-Spam-Status: No, score=-6.403 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBX3J336GYq3 for <rrg@core3.amsl.com>; Wed, 3 Feb 2010 15:49:26 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 65E6F3A6811 for <rrg@irtf.org>; Wed, 3 Feb 2010 15:49:26 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2DC456BE5DF; Wed, 3 Feb 2010 18:50:09 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20100203235009.2DC456BE5DF@mercury.lcs.mit.edu>
Date: Wed, 03 Feb 2010 18:50:09 -0500
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Terminology
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 23:49:27 -0000

    > From: RJ Atkinson <rja.lists@gmail.com>

    > I don't find the "CES" or "CEE" terms to be very meaningful, in that
    > they don't really inform one about the important properties of any
    > proposal.

{Visualize Noel falling off chair...}

Say what?

In deployment terms (which also has a big effect on the economics), it's very
important, because it tells you whether one needs to modify hosts or not. You
may not think that's a significant barrier, but I (and probably others) don't
agree.

Even in architectural terms, it's important: whether some function is
implemented in 'the network' or 'the edge' is a fairly significant decision in
architectural terms - and it is just that choice that the CES/CEE choice
highlights.

Yes, CES/CEE is not the only, or most, significant architectural axis, but
it's surely not one I would characterize as 'not really ... important'.

	Noel