Re: Are IPv6 auto-configured addresses transient?
Margaret Wasserman <mrw@sandstorm.net> Fri, 16 October 2009 01:42 UTC
Return-Path: <mrw@sandstorm.net>
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 ABF5028C188 for <ipv6@core3.amsl.com>; Thu, 15 Oct 2009 18:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Level:
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=0.734, 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 s+4vVAsfBXAW for <ipv6@core3.amsl.com>; Thu, 15 Oct 2009 18:42:07 -0700 (PDT)
Received: from QMTA15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by core3.amsl.com (Postfix) with ESMTP id 8DED928C158 for <ipv6@ietf.org>; Thu, 15 Oct 2009 18:42:06 -0700 (PDT)
Received: from OMTA20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by QMTA15.emeryville.ca.mail.comcast.net with comcast id tCEm1c0091smiN4AFDiB0g; Fri, 16 Oct 2009 01:42:11 +0000
Received: from [10.36.0.42] ([173.48.144.147]) by OMTA20.emeryville.ca.mail.comcast.net with comcast id tDhy1c00T3B1aZH8gDi2ZM; Fri, 16 Oct 2009 01:42:09 +0000
Message-Id: <1C461E2E-C218-42EF-BC23-D8B1B4389C40@sandstorm.net>
From: Margaret Wasserman <mrw@sandstorm.net>
To: Vijayrajan ranganathan <vijayrn@gmail.com>
In-Reply-To: <5988ed3c0910070925iaa3b136jd500d30037946a3a@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Are IPv6 auto-configured addresses transient?
Date: Thu, 15 Oct 2009 21:41:56 -0400
References: <5988ed3c0910070925iaa3b136jd500d30037946a3a@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
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: Fri, 16 Oct 2009 01:42:08 -0000
Hi Vijayrajan, On Oct 7, 2009, at 12:25 PM, 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? Auto-configured global IPv6 addresses are "leased" to an interface for a specified "lifetime". They expire at the end of that lifetime if the lifetime is not renewed. > 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? Typically, IPv6 router advertisements will advertise fairly long (at least several hour) lifetimes for their prefixes, and those lifetimes are renewed each time a hosts receives another router advertisement, which should happen quite often. Also, when the address lifetime expires, the addresses do not go away, they are merely deprecated. They will continue to be used for ongoing communication, and may be used for new communication if no other addresses are available. So, prefix lifetimes offer a way to replace an existing address with a new address when the network configuration changes, but they do not prevent continued local communication if the only router (or every router) goes down for an extended period, for example. > 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? Most global prefixes in IPv6 are provider-assigned, so they would change if you change ISPs, or perhaps if your ISP changes their network configuration. Some registries do seem to over provider- independent IPv6 addresses, but I don't know all of the details about how you would get one of those and/or how you would get an ISP to route it. You'd need to contact a registry and your ISP to work that out. Margaret
- Are IPv6 auto-configured addresses transient? Vijayrajan ranganathan
- Re: Are IPv6 auto-configured addresses transient? Antonio Querubin
- Re: Are IPv6 auto-configured addresses transient? Brian E Carpenter
- Re: Are IPv6 auto-configured addresses transient? Fred Baker
- Re: Are IPv6 auto-configured addresses transient? Seiichi Kawamura
- Re: Are IPv6 auto-configured addresses transient? Margaret Wasserman
- Re: Are IPv6 auto-configured addresses transient? Brian Haberman
- RE: Are IPv6 auto-configured addresses transient? Hemant Singh (shemant)
- Re: Are IPv6 auto-configured addresses transient? Christopher Morrow
- RE: Are IPv6 auto-configured addresses transient? Hemant Singh (shemant)
- Re: Are IPv6 auto-configured addresses transient? Mark Andrews
- Re: Are IPv6 auto-configured addresses transient? Brian E Carpenter
- RE: Are IPv6 auto-configured addresses transient? Hemant Singh (shemant)