Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE

tianxiang li <peter416733@gmail.com> Mon, 12 September 2016 03:02 UTC

Return-Path: <peter416733@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA81612B0E5 for <dhcwg@ietfa.amsl.com>; Sun, 11 Sep 2016 20:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kvh7FB5EpT34 for <dhcwg@ietfa.amsl.com>; Sun, 11 Sep 2016 20:02:38 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86F4C12B044 for <dhcwg@ietf.org>; Sun, 11 Sep 2016 20:02:38 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id d191so67296669oih.2 for <dhcwg@ietf.org>; Sun, 11 Sep 2016 20:02:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NJYg4GFd3KDb71lZ1F0SiOn0gEfYpy6lt02s0XzvgaI=; b=yDZTSjNrTAECljV6DIPUS2TccwY2uDgzMbP3Wa9m1Ee65vEn8DUb6eOu8gH2Ehz6gu 0wTTjm6fOtkx5RY+ziDoSC2tCkuFKu4U0SZy7ifLZ4mL784hLOhdGljz1G1DQFFgM9t9 jxlftyUEdvIb/d2SlRA1JC75JFDHAI5Ui3Z8/aaBj8nkWk1HK0CF9XR3laNZD9yPUvVW 2vv+lPP2GOoy0J5bIByCdxjtguTyJHnjL+4Y8aqmpWiRo5o8pJt3aastsD3U1LWxG50F Ht0pW6LvqzGEzkiea0sUiDTS/LBNsa4M921cR5UHcKV285gXaVrxEGdNdUYVIjCowLX+ iKrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NJYg4GFd3KDb71lZ1F0SiOn0gEfYpy6lt02s0XzvgaI=; b=eymzEPqhVoR28XaQrtBZcBcDRUm4P4pQsrXs/d2MG+dthxchI/koxD8Oc11cVUClAr Y1IO5VK47LhDLuVmbKkkW72Y6p9uDsCuG83XNGAFw9fRMdqR1JvnB+6eZhcS+pGNx9cE /2NleUa1NnUqu8xbV1IQe5XrHAwoMwSdIleX9E8HsDEPbjUhpoSvInwQRH4zvRmiaAFs RVGxxTH0cTszbvreU6iiXVkHJG0sorYY+DNhaQLbQvlA/zMcLxQV8mbZYAmimI7EuS7X DftwLAGMehdWnuhYxyaq3pjD1gik300Ft6OU0Kkh5xFUGQ2QYLiqIKT7V+LPBv4ncqf6 OdxQ==
X-Gm-Message-State: AE9vXwNHnbnKAC3A4oVYkcJUVkmhhkZLwgZJ+FmGe44facf51AnHgVtXfomUSFwfiVxsPXbDRC0r13DBoCVjkg==
X-Received: by 10.157.22.166 with SMTP id c35mr19296178ote.172.1473649357987; Sun, 11 Sep 2016 20:02:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.54.215 with HTTP; Sun, 11 Sep 2016 20:01:57 -0700 (PDT)
In-Reply-To: <313807947.869636.1473340159086.JavaMail.zimbra@network1.net>
References: <58B66897-2F0D-4916-AF5A-42D5DC172DE5@cisco.com> <CAFx+hEPS+c1-d9TyOccLdhjDtBUots4LuXdDi6iV6ECaReb9eQ@mail.gmail.com> <313807947.869636.1473340159086.JavaMail.zimbra@network1.net>
From: tianxiang li <peter416733@gmail.com>
Date: Mon, 12 Sep 2016 11:01:57 +0800
Message-ID: <CAFx+hENvg_CeBh0Sxn+-ynTY0oT-wJ3pD9X_CoW2VYpBwQa_LA@mail.gmail.com>
To: perl-list <perl-list@network1.net>
Content-Type: multipart/alternative; boundary="001a1141f05e81ab4d053c46bab6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/oRRCyzwXa2XBIRq9tyK8PWR3DIs>
Cc: dhcwg <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Sep 2016 03:02:40 -0000

Thank you for explaining this point. It does seem like the desirable
method, and a /64 is sufficient enough for address allocation, so  I
guess there's no need to address rebalancing.

Thanks,
Tianxiang

2016-09-08 21:09 GMT+08:00 perl-list <perl-list@network1.net>:

>
>
> ------------------------------
>
> *From: *"tianxiang li" <peter416733@gmail.com>
> *To: *"Kim Kinnear" <kkinnear@cisco.com>
> *Cc: *"dhcwg" <dhcwg@ietf.org>
> *Sent: *Wednesday, September 7, 2016 10:37:06 PM
> *Subject: *Re: [dhcwg] DHCPv6 Failover -- LAST CHANCE
>
> 4.2.1 Independent allocation
>
>
>
> “In this allocation scheme, used for allocating individual IPv6 addresses,
> available IPv6 addresses are permanently (until server configuration
> changes) split between servers…”
>
>
>
> If active-passive mode is used, it would mean that the addresses in the
> secondary server would not be used unless the primary server fails. In that
> case, wouldn’t permanently splitting the addresses between the primary and
> secondary server a waste of addresses?
>
>
>
> If the address pool in the primary server becomes scarce, wouldn’t a
> rebalancing mechanism be useful?
>
>
> I read this section as just a codifying of what we do now without
> failover.  We put half the /64 on the "primary" and half on the
> "secondary".  It provides for some enhanced behavior where clients won't
> need to get a new address in the case of server failure as the remaining
> server can renew addresses.  Also, you wouldn't need to do any math as the
> server would arithmetically split in half for you any subnets that are
> marked for this behavior.  If offered a choice in the future, I would
> probably choose this method as it is the simplest.
>
> Also, this bit here: "It also assumes that the pool assigned to each
> server will never deplete." negates your comment about addresses becoming
> scarce.  It is highly recommended (by all articles and documentation that
> I've seen) that all end networks be configured as /64 subnets.  There are
> quite a lot of addresses in a /64.  More than are in the entire IPv4
> address space, is my understanding.  It is unlikely that a /64 will
> experience IP address scarcity.
>