Re: [rrg] RRG to hibernation

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 13 November 2012 00:08 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 8D36921F87A6 for <rrg@ietfa.amsl.com>; Mon, 12 Nov 2012 16:08:31 -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=[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 s5ZzdND5Qpcd for <rrg@ietfa.amsl.com>; Mon, 12 Nov 2012 16:08:31 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id F08E121F8775 for <rrg@irtf.org>; Mon, 12 Nov 2012 16:08:30 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 40FB0558C57 for <rrg@irtf.org>; Mon, 12 Nov 2012 16:08:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A02EC1C08E0; Mon, 12 Nov 2012 16:08:23 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.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 mailb2.tigertech.net (Postfix) with ESMTPSA id 082211C08F0; Mon, 12 Nov 2012 16:08:22 -0800 (PST)
Message-ID: <50A18F75.8060001@joelhalpern.com>
Date: Mon, 12 Nov 2012 19:08:21 -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: Dae Young KIM <dykim@cnu.kr>
References: <20121112234012.05F8E18C0CA@mercury.lcs.mit.edu> <CAFgODJcP1zvwRJukJdnqjSR-78XAMB1nSxL32gjUQB+NqpgESg@mail.gmail.com>
In-Reply-To: <CAFgODJcP1zvwRJukJdnqjSR-78XAMB1nSxL32gjUQB+NqpgESg@mail.gmail.com>
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: Tue, 13 Nov 2012 00:08:31 -0000

I do not see the difficulty.  We already have the IPv6 mechanisms to 
advertise the prefixes.  And we have the IPv6 mechanisms for hosts to 
combne the prefixes with teir IDs.
We also have the dynamic DNS mechanisms (with security) needed to 
advertise the results.

With ILP, these combinations can be changed during sessions, and traffic 
can change paths during sessions without impact.
With the current architecture, sessions can not change paths, and 
changes to the connectivity are hard to discover or utilize.

Thee are other multi-homing problems that are not solved.  Working out 
how to manage prefix assignments in an enterprise when external 
assignments change is one example of such issues (LISP takes a different 
tack, and thus the costs and benefits are different.)

Yours,
Joel

On 11/12/2012 6:59 PM, Dae Young KIM wrote:
> On Tue, Nov 13, 2012 at 8:40 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu
> <mailto:jnc@mercury.lcs.mit.edu>> wrote:
>
>          > From: Dae Young KIM <dykim@cnu.kr <mailto:dykim@cnu.kr>>
>
>          > This multiplicity of the locators, although the ID is single
>     ... also
>          > affects DNS entries.
>
>     Not necessarily. If the DNS only contains IDs (which is the way some
>     designs
>     work), then there no DNS/locator issues.
>
>
> The description on servers in Sec. 4.1 of ILNP, p. 20, implies that.
>
> The DNS concern is, however, a secondary thing. That a host has to be
> associated with multiple PA locators inserted by multiple ISPs at ILNP
> multi-homing is the real problem I'm pointing to. This is exactly the
> same situation you might require with the current IP.
>
> Where's the improvement on multi-homing? If there's no such improvement,
> have we solve the table explosion problem?
>
> --
> DY
>
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>