Re: Are IPv6 auto-configured addresses transient?

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 07 October 2009 22:00 UTC

Return-Path: <brian.e.carpenter@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 76AC428C0CF for <ipv6@core3.amsl.com>; Wed, 7 Oct 2009 15:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level:
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167, 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 g0hry+1hfYOr for <ipv6@core3.amsl.com>; Wed, 7 Oct 2009 15:00:39 -0700 (PDT)
Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.216.176]) by core3.amsl.com (Postfix) with ESMTP id 84AB13A6914 for <ipv6@ietf.org>; Wed, 7 Oct 2009 15:00:39 -0700 (PDT)
Received: by pxi6 with SMTP id 6so6081704pxi.32 for <ipv6@ietf.org>; Wed, 07 Oct 2009 15:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=oI/xPdKSA4C6zs+dVJVr7oGS6kkoi6d0A7xqMjh4/AM=; b=bHRrlChzgB/O4yCw5Mpr0E5lcwlF6AUabla8wVPrxLyD9pia1Ys0dRAiSvxUnGlDWo 6JUjc082a8ifxfhxXz+htaPTt44jvLUpWCV3DIs+3BanZaFHyKFxqVKbAPFBMF0Ae9jX 2cHNGBljLSAF3Vc+1NyPJJl1RxqrdBbrs+/Rk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=CHkDINtW0sp85urRnuHosE5ei0ODWQ+AZ8qd8/O8hBroiFnDQmOV7yB5H1eMIBVF0Y PMAVW6MfbUX0dvS6asDPPn4bADGkYyTbJ553oB/tanXHMQGukczkIswRqJxOPNFzgdwr JYLudnWmdk3m2I5RrkOeAV8QaHHvGG881Vvwg=
Received: by 10.115.66.10 with SMTP id t10mr776181wak.20.1254952937511; Wed, 07 Oct 2009 15:02:17 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 22sm486529pzk.6.2009.10.07.15.02.16 (version=SSLv3 cipher=RC4-MD5); Wed, 07 Oct 2009 15:02:17 -0700 (PDT)
Message-ID: <4ACD0FE6.9020508@gmail.com>
Date: Thu, 08 Oct 2009 11:02:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Vijayrajan ranganathan <vijayrn@gmail.com>
Subject: Re: Are IPv6 auto-configured addresses transient?
References: <5988ed3c0910070925iaa3b136jd500d30037946a3a@mail.gmail.com>
In-Reply-To: <5988ed3c0910070925iaa3b136jd500d30037946a3a@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
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: Wed, 07 Oct 2009 22:00:40 -0000

Vijay,

I think it's been safe to say for many years that *all*
IP addresses, of either family, are transient, with limited
exceptions (i.e. stable servers). I don't see that IPv6
autoconf addresses are qualitatively different in that respect.

It is a deep design bug that when applications obtain an address
from lower layers, it doesn't come with a lifetime attached.
Addresses derived from A or AAAA records, DHCP or DHCPv6, etc.,
all have finite lifetimes, and it's very sad that applications
don't know it.

Actually let me plug the GROBJ BOF in Hiroshima, and the associated
draft-carpenter-behave-referral-object (version 01 coming soon).
Address lifetime becomes an especially serious problem when
referring addresses from one host to another.

   Brian

On 2009-10-08 05:25, Vijayrajan ranganathan wrote:
> Hi Everyone,
> Is there a notion that auto-configured IPv6 addresses based on
> globally unique prefixes are transient compared to manually configured
> ones?
> I know that we could configure them to have infinite lifetimes & such,
> but I am thinking of a large IPv6 deployment where these addresses are
> expected to be up 24/7. I mean, just the fact that lifetimes could be
> modified on the router, the advertising router could become
> unreachable etc.
> 
> As an IPv6 application developer, would I have to factor in this
> "transiency" of autoconf addresses in my design all the time? How safe
> & normal
> is it to replace all manual IPv6 address configuration with
> auto-configuration in a large IPv6 deployment esp in an environment
> that is very sensitive
> to non-availability of addresses?
> 
> Another related question, is it common for a site's global prefix(es)
> to change? In this regard, are they any different from an IANA
> assigned IPv4
> network-id for example?
> 
> Thanks & Regards
> Vijay
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>