Re: [rrg] RRG to hibernation

Dae Young KIM <dykim@cnu.kr> Tue, 13 November 2012 08:53 UTC

Return-Path: <dykim6@gmail.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 1A3C021F860D for <rrg@ietfa.amsl.com>; Tue, 13 Nov 2012 00:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 S41J9q8Zepzj for <rrg@ietfa.amsl.com>; Tue, 13 Nov 2012 00:53:15 -0800 (PST)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by ietfa.amsl.com (Postfix) with ESMTP id 170C621F85EB for <rrg@irtf.org>; Tue, 13 Nov 2012 00:53:13 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id g24so565418qab.13 for <rrg@irtf.org>; Tue, 13 Nov 2012 00:53:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=hII88pP9Nwhr/VCpoz55/rytdGwUvl115eoy92U4uKA=; b=h8SMHdCaTz259+uJ2y84wK6qWiBnlVQrLR+pV3Wu6qu6lbhNMcSI5BYfSvFpguqy5Y GZG+48/d0Fy6Y4FGJP8mXiepgx5jDsCO3iOOJkyGOqLs0/4a5nEjUQTa/ybOmQ43t8rd oFrLtW+zr+3tktkMXfrgy/pYH6AssQPWu7se8FmwJUT5GxBzOJleioeqwwU7HybaeKOb 8SA171JG2IaBdIno9mUkhzbSCt2qu02KEHRqymb8yfIMVdqeO1DTkR9tAI6lnIR4UbRq yAXY95sfM+GgKxqnv01RSLq5g6v40AzG37FrQ+OhJdx9hnatbnZYCePb4ask2rzfwYbK Y2tg==
Received: by 10.229.198.217 with SMTP id ep25mr3258861qcb.59.1352796792127; Tue, 13 Nov 2012 00:53:12 -0800 (PST)
MIME-Version: 1.0
Sender: dykim6@gmail.com
Received: by 10.49.12.9 with HTTP; Tue, 13 Nov 2012 00:52:51 -0800 (PST)
In-Reply-To: <CAFgODJeae5EwSr8aC4b3tGBMxKPZRcfKarUuuwmA1LZKjge6ng@mail.gmail.com>
References: <20121112234012.05F8E18C0CA@mercury.lcs.mit.edu> <CAFgODJcP1zvwRJukJdnqjSR-78XAMB1nSxL32gjUQB+NqpgESg@mail.gmail.com> <50A18F75.8060001@joelhalpern.com> <CAFgODJcDAzaYPrWFEJhgeCjnN_M9tdd+pdHTiccd=Dz=1mYrLg@mail.gmail.com> <EC8FD781-E416-4AE6-BA99-F74FE2DDA14D@tony.li> <CAFgODJfMBJBxNJ_M1_L=K0f2DpbZvzOBUgLZ6sT+-y+JevGeSg@mail.gmail.com> <27E72BC2-C84D-469F-9667-7A749567B477@tony.li> <CAFgODJfBX0R90oiYnxWrgC1oyr5ZPTZJA23WWu=Dbqu=xmyYTQ@mail.gmail.com> <EA48576E-4953-4408-982F-9D48497F8975@tony.li> <CAFgODJeae5EwSr8aC4b3tGBMxKPZRcfKarUuuwmA1LZKjge6ng@mail.gmail.com>
From: Dae Young KIM <dykim@cnu.kr>
Date: Tue, 13 Nov 2012 17:52:51 +0900
X-Google-Sender-Auth: r0Bk3GqMb9kHtOUnlsIcyXktyJ8
Message-ID: <CAFgODJfTfbqcV7OFeLnFqsVDcCjqe47TSBz73NJOHGu9DM8kRg@mail.gmail.com>
To: Tony Li <tony.li@tony.li>
Content-Type: multipart/alternative; boundary=005045015bad3f7ff204ce5c8cc2
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: Tue, 13 Nov 2012 08:53:16 -0000

On Tue, Nov 13, 2012 at 5:45 PM, Dae Young KIM <dykim@cnu.kr> wrote:

>
> > On the other, the same connection resilience could be achieved with some
>> sort of session management function on top of TCP, without resorting to LIS.
>>
>>
>> Absolutely true.  But then it might require application changes, which
>> we'd like to avoid.
>>
>
> And no application change with ILNP? I thought there'd be application
> changes with ILNP, although none with the routers. Apps should take only
> the half of the IPv6 address as host ID, not the whole.
>

I'm mistaken. Perhaps, no change with ILNP; rather TCP has to be changed.

The pain would be the same if a shim session layer would be inserted on top
of TCP with having the socket interface look the same to APPs...?

-- 
DY