Re: Errata for RFC4862

神明達哉 <jinmei@wide.ad.jp> Tue, 10 January 2017 19:31 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B7C12984A for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 11:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 lkOFggAkmTZ5 for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 11:31:46 -0800 (PST)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 A7C821297D0 for <ipv6@ietf.org>; Tue, 10 Jan 2017 11:31:46 -0800 (PST)
Received: by mail-qk0-x234.google.com with SMTP id u25so569606965qki.2 for <ipv6@ietf.org>; Tue, 10 Jan 2017 11:31:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=xxRnMUEiKL7SJo9q4NShaXusHT/+tohqoqYPFn0JY/A=; b=Jx3l+U1piMNObD9FiI8dq2DfkkxlPgjclh9uzSxov2LYSEY6MK9KkSNR1CU5WJPtaF hCl62SqHHXnOUCPp2koCp/DiAff/UiUo+w9Ee6fXQQ0WtAgADMBP7McoPEgWLKXYKRJc wmiJlJkGinhSR3LW8YxGclNjMwOsZv3JEUyJ0N20IHk5iUsXA+EOZC8ZtV0+uR1LunsI HAYpbT/a5z7VYxwunKKe99LFGmyXfiGcWeRymAn3ZuI+WWHTzXBGbMus6ihs3xPgiL43 xJwThtiq1/Mcmytn355HVM+lJ1Ti+jSMvNbQgtDURIMZi/7zPq+MnUCbDZoqySoj00Q/ kDLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=xxRnMUEiKL7SJo9q4NShaXusHT/+tohqoqYPFn0JY/A=; b=B/wrkSiJSDXfBtV75PCWHn2lX2h0h+mCDhDnQlcLAif0tfljjCF3yotQrSPN0D+RY4 LOrEiWp2oHhG62s6J3/U9q0u51sDQ42Cci/46S08kNzF+nADM+fEqRj0K06p6cFtXkRT gIR+mk3zDOmEVs29shfr0DvnE195KiauJx2C7FurM9dQIDkAUm2UJqaWSc03NxzzdSDS VdgXun1/H6rDNulu/Ib4JAkErtSgcGArWgU4Lz8B+9EmiCOXCCikqUeIpob7LJIF4N84 XW32GKBtbUeNGIqkRopvpbvBfxqnF6/qTRPiwweXgMzOhSWJKChTwwiHQ9C3lCDFIn0y Sa2A==
X-Gm-Message-State: AIkVDXJOGJ3/YP/xXfPsvDREP61M3zQZFexBfDPAXGCCg5qR7FqUjiPlnGi4ZkWHu5pxIoO48RG9iI66nMB75w==
X-Received: by 10.55.161.11 with SMTP id k11mr4507545qke.149.1484076705727; Tue, 10 Jan 2017 11:31:45 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.29 with HTTP; Tue, 10 Jan 2017 11:31:45 -0800 (PST)
In-Reply-To: <4921ADB7-42A6-443E-B639-A3F6F300B13C@jisc.ac.uk>
References: <CAO42Z2xH9wqXKFjtAbv6isQ3cG1=FNUmkNFq2DGJdqj9BFDVaQ@mail.gmail.com> <E459F5B0-D088-4D74-B92A-9A8671249716@employees.org> <4921ADB7-42A6-443E-B639-A3F6F300B13C@jisc.ac.uk>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Tue, 10 Jan 2017 11:31:45 -0800
X-Google-Sender-Auth: UZ_FKO1L-HgGQ8Mc0cIePpxxHu8
Message-ID: <CAJE_bqesE0Y+0mpmkWHji+JGhPAtmWJx4LjA4Kz+8ij+Li0E4g@mail.gmail.com>
Subject: Re: Errata for RFC4862
To: Tim Chown <Tim.Chown@jisc.ac.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rJp-KmiUZYPKn12qQANfCgNgkXA>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 10 Jan 2017 19:31:48 -0000

At Tue, 10 Jan 2017 12:45:27 +0000,
Tim Chown <Tim.Chown@jisc.ac.uk> wrote:

> My recollection of running renumbering experiments is that it’s the
> Preferred Lifetime that matters, i.e. when that is set to zero for a
> prefix, the prefix is marked as deprecated.  So when renumbering,
> you run with two prefixes advertised, old and new, setting the
> Preferred Lifetime to 0 on the old prefix (even though the Valid
> Lifetime is set to 2+ hours), so that the address with the new
> prefix is used for newly initiated communications (as per RFC 6724,
> Rule 3).

Yes, but I guess what Ole tried to point out (which I agree with) is
that the valid lifetime will also have to decrease to 0 eventually,
and this original text of RFC4862 allows such decrease operation
without requiring explicit authentication if done by gradually:

> >>     1.  If the received Valid Lifetime is greater than 2 hours or
> >>         greater than RemainingLifetime, set the valid lifetime of the
> >>         corresponding address to the advertised Valid Lifetime.

--
JINMEI, Tatuya