Re: [rrg] RRG to hibernation

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 12 November 2012 02:48 UTC

Return-Path: <jmh@joelhalpern.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 A267B21F841E for <rrg@ietfa.amsl.com>; Sun, 11 Nov 2012 18:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level:
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 O9ElGYZxU1aY for <rrg@ietfa.amsl.com>; Sun, 11 Nov 2012 18:48:34 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3978C21F8425 for <rrg@irtf.org>; Sun, 11 Nov 2012 18:48:34 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 981C1A68FB for <rrg@irtf.org>; Sun, 11 Nov 2012 18:48:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 501A61C02F3B; Sun, 11 Nov 2012 18:48:30 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-52-236.clppva.btas.verizon.net [71.161.52.236]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id B60331C02F3A; Sun, 11 Nov 2012 18:48:29 -0800 (PST)
Message-ID: <50A06376.5040002@joelhalpern.com>
Date: Sun, 11 Nov 2012 21:48:22 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Christian Huitema <huitema@huitema.net>
References: <20121112015552.DC3BA18C0C7@mercury.lcs.mit.edu> <08d501cdc07b$582cbdd0$08863970$@huitema.net>
In-Reply-To: <08d501cdc07b$582cbdd0$08863970$@huitema.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rrg@irtf.org
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 02:48:35 -0000

I can well believe we can, for a reasonable value of all, update all 
host TCP and UDP engines with a small, migratable, change.
We can't change all host applications.
And we can not make a change that does not interoperate with existing hosts.

Yours,
Joel

On 11/11/2012 9:13 PM, Christian Huitema wrote:
>>      > 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
>