Re: [rrg] RRG to hibernation

heinerhummel@aol.com Mon, 12 November 2012 09:23 UTC

Return-Path: <heinerhummel@aol.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B90D821F84BB for <rrg@ietfa.amsl.com>; Mon, 12 Nov 2012 01:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[AWL=1.200, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WaiahjmqZ+SI for <rrg@ietfa.amsl.com>; Mon, 12 Nov 2012 01:23:47 -0800 (PST)
Received: from imr-ma01.mx.aol.com (imr-ma01.mx.aol.com [64.12.206.39]) by ietfa.amsl.com (Postfix) with ESMTP id BD33721F8487 for <rrg@irtf.org>; Mon, 12 Nov 2012 01:23:47 -0800 (PST)
Received: from mtaomg-mb06.r1000.mx.aol.com (mtaomg-mb06.r1000.mx.aol.com [172.29.41.77]) by imr-ma01.mx.aol.com (Outbound Mail Relay) with ESMTP id 1E4073800036B; Mon, 12 Nov 2012 04:23:47 -0500 (EST)
Received: from core-dqa002b.r1000.mail.aol.com (core-dqa002.r1000.mail.aol.com [172.29.211.197]) by mtaomg-mb06.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id D0645E000081; Mon, 12 Nov 2012 04:23:46 -0500 (EST)
References: <20121112015552.DC3BA18C0C7@mercury.lcs.mit.edu> <08d501cdc07b$582cbdd0$08863970$@huitema.net>
To: huitema@huitema.net, rrg@irtf.org
In-Reply-To: <08d501cdc07b$582cbdd0$08863970$@huitema.net>
X-MB-Message-Source: WebUI
MIME-Version: 1.0
From: heinerhummel@aol.com
X-MB-Message-Type: User
Content-Type: multipart/alternative; boundary="--------MB_8CF8ECE8D24E7CF_C04_DB62A_webmail-m173.sysops.aol.com"
X-Mailer: Webmail 37130-STANDARD
Received: from 178.27.21.1 by webmail-m173.sysops.aol.com (64.12.78.179) with HTTP (WebMailUI); Mon, 12 Nov 2012 04:23:46 -0500
Message-Id: <8CF8ECE8D1B624F-C04-3AD82@webmail-m173.sysops.aol.com>
X-Originating-IP: [178.27.21.1]
Date: Mon, 12 Nov 2012 04:23:46 -0500
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1352712227; bh=EOP9t5RIKmhMy0jfDJrdlNpJ90tlFEs4hr+F3yCTP74=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=ocxrwZQEhJRqQ/S0rCZp8AwwAbtT5ESn1nzLQ6K/Qwo/oopQIRquddvqmEekDaMjF c4UoW61nwTvY6bHd+7O5DFi35Dr+IxB26ETex1OqdJOW9zgdUD1Zxl5duczqgquXi4 qkgsu3cbklhalZiM8IxK6/gIaIsvafYHRXSop0Lg=
X-AOL-SCOLL-SCORE: 0:2:358541984:93952408
X-AOL-SCOLL-URL_COUNT: 0
x-aol-sid: 3039ac1d294d50a0c022034a
Subject: Re: [rrg] RRG to hibernation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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: Mon, 12 Nov 2012 09:23:49 -0000

Christian,
you are absolutely right. However,  avoiding any impact on the users has been the number ONE objective of LISP.
And now, by moving even to LISP-DDT,i.e. dumping allegeable worse variants, the consequences will be disasterous.
Heiner



-----Ursprüngliche Mitteilung----- 
Von: Christian Huitema <huitema@huitema.net>
An: 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>; rrg <rrg@irtf.org>
Verschickt: Mo, 12 Nov 2012 3:13 am
Betreff: Re: [rrg] RRG to hibernation


>     > It does require a new suite of transport protocols
>     > ...
>     > the odds of ever reaching deployment on an approach which requires
us
>     > to abandon TCP and UDP are not good?
> 
> That's infeasible; you can't require changing all hosts. You need to see
if you can
> come up with some approach that avoids that.
> 
> (E.g. if we have location-identity separatation deployed, you could hide
the new
> locators from the hosts.)

I think that we are giving up too early on the feasibility of updating all
hosts. Indeed, any substantial change in routing and addressing would most
probably end up changing all hosts, or at least most of them. I also think
that a research group should not necessarily shy away from investigations
that affect all hosts. If research comes out with a brilliant shiny star on
the horizon, then engineering might follow. If the best we can do is hack on
the edges of current solutions, then engineering groups can definitely do
that, no need for a research group.

-- Christian Huitema




_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg