Re: Are IPv6 auto-configured addresses transient?

Christopher Morrow <christopher.morrow@gmail.com> Sun, 18 October 2009 21:01 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E07BA3A687E for <ipv6@core3.amsl.com>; Sun, 18 Oct 2009 14:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ITqjp+NqlMrn for <ipv6@core3.amsl.com>; Sun, 18 Oct 2009 14:01:23 -0700 (PDT)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id EC0633A67C0 for <ipv6@ietf.org>; Sun, 18 Oct 2009 14:01:22 -0700 (PDT)
Received: by iwn16 with SMTP id 16so2060755iwn.29 for <ipv6@ietf.org>; Sun, 18 Oct 2009 14:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Z/Y6ZsgfvUVTsS/pjSAkmswjBg/0lTKPCpjOoXd+dkI=; b=WzYjfErae02nDbe1OMHFT3rfHB1vx+eT0PAmwHvM7cYXqJiTZdsu2zxj3CSEysDoI1 vflyl+I6ANjovyT+Qjje9sN2ARXefQOaFJSF73GWMk+RiF8+o7saR41tYN18LrYS0grv 3lOXrrgUnrFW4WDeyZK90jr43RLMxMcraH6sc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tw9raiR5/Nh+yo3H/H68zfsljkltgWsbNHbvEUe0C63Nq1KjZ4VTN8hP7PVWB0ZCmK wdEYmLNEItWyDj89KoWZ9zgy0wj691wYXCUb8hNZeZaiakjouLX0YutSVzXg8aPdVLNM lfbL0ynVBWIANa7e1LlOJHj/iJ4aB+Bj3t+6c=
MIME-Version: 1.0
Received: by 10.231.125.28 with SMTP id w28mr1439382ibr.50.1255899684082; Sun, 18 Oct 2009 14:01:24 -0700 (PDT)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D084DF2A3@xmb-rtp-20e.amer.cisco.com>
References: <5988ed3c0910070925iaa3b136jd500d30037946a3a@mail.gmail.com> <1C461E2E-C218-42EF-BC23-D8B1B4389C40@sandstorm.net> <4AD8AEDC.2000800@innovationslab.net> <B00EDD615E3C5344B0FFCBA910CF7E1D084DF2A3@xmb-rtp-20e.amer.cisco.com>
Date: Sun, 18 Oct 2009 17:01:24 -0400
Message-ID: <75cb24520910181401i7f34c1a3y9f49ee472be231d1@mail.gmail.com>
Subject: Re: Are IPv6 auto-configured addresses transient?
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org, Margaret Wasserman <mrw@sandstorm.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2009 21:01:24 -0000

On Sun, Oct 18, 2009 at 9:28 AM, Hemant Singh (shemant)
<shemant@cisco.com> wrote:
>>-----Original Message-----
>>From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian Haberman
>>Sent: Friday, October 16, 2009 1:35 PM
>>To: Margaret Wasserman
>>Cc: ipv6@ietf.org
>>Subject: Re: Are IPv6 auto-configured addresses transient?
>
>
>>I *think* that Vijay is asking a more general question about
>>applications rather than how to get IPv6 addresses (or service).  If I
>>interpreted his earlier comments correctly, he is asking what does an
>>application know about an address that it is using.  For example, if
>>Vijay's application is long-lived would it be affected by an address
>>becoming deprecated and no longer reachable.  In this case, the address
>
>>stays reachable for some period of time until the deprecated prefix is
>>removed from the routing system.
>
> I don't see any problem here.  Till a specific long-lived application
> screw case is described, I am not convinced the app needs to know

I have a long lived ssh session between two devices, both of which use
enhanced privacy addresses that rotate hourly.

(example provided)

Note that in most cases the ip address stays live on the device as
long as there's something actively using it... so its not really a
problem, unless the entire subnet changes (upstream provider change
for instance).

> anything related to lifetimes of addresses.  On an IPv6 node, if
> anything related to the addresses on a network interface changes, the
> changes will affect the network interfaces the app is using.  Even in
> IPv4, if an app is using an IP address of a network interface on the
> node, the app tracks changes of the IP address on the network interface

The app MAY track this info, it MAY also not :( sadly some people
hardcode the ip address into the application, of course you can't fix
that case.

-chris