[v6ops] cpe-slaac-renum: Proposed text for prefix lifetimes
Fernando Gont <fgont@si6networks.com> Wed, 08 April 2020 11:59 UTC
Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC7E3A0795 for <v6ops@ietfa.amsl.com>; Wed, 8 Apr 2020 04:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 4aqwp4FMANao for <v6ops@ietfa.amsl.com>; Wed, 8 Apr 2020 04:59:48 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD863A0788 for <v6ops@ietf.org>; Wed, 8 Apr 2020 04:59:48 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 3E0F18092F; Wed, 8 Apr 2020 13:59:45 +0200 (CEST)
To: IPv6 Operations <v6ops@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <77a84b82-716d-e754-9317-8876af5e49db@si6networks.com>
Date: Wed, 08 Apr 2020 08:59:33 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9rfCV1IXotSW7Fb5PMifkMz1kAk>
Subject: [v6ops] cpe-slaac-renum: Proposed text for prefix lifetimes
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2020 11:59:51 -0000
Folks, In this recent thread on cpe-slaac-renum, there was a proposal to add text to the draft, and I promised I would start a new thread just in case somebody missed the chance to review in the rather long thread. This text is meant to reflect the comments from Philip, Lorenzo, and others (please do let me know if I misunderstood what you mean). The text is: ---- cut here ---- The Valid Lifetime and Preferred Lifetime of PIOs have direct impact on two different aspects: * The amount of time hosts may end up employing stale network configuration information (see [draft-ietf-v6ops-slaac-renum]). * The amount of time Customer Edge routers would need to persist trying to deprecate stale network configuration information (to handle cases where nodes miss Router Advertisements and thus still consider the stale information as valid). As a result, CPE Routers SHOULD override the default "Preferred Lifetime" and "Valid Lifetime" values from [RFC4861], and employ shorter values to mitigate the aforementioned effect, while complying with the requirement from Section 2.1 of this document, and the recommendations in RFC7772. This document RECOMMENDS that Customer Edge Router set the Router Lifetime and PIO Preferred Lifetime to 2700 seconds (45 minutes) and the PIO Valid Lifetime to 86400 seconds (1 day). We note that a CPE Router need not employ the (possibly long) DHCPv6-PD lease times in the Valid Lifetime and Preferred Lifetime of PIOs sent in Router Advertisements messages to advertise sub-prefixes of the leased prefix. Instead, CPE Routers SHOULD use shorter values for the Valid Lifetime and Preferred Lifetime of PIOs, since subsequent Router Advertisement messages will nevertheless refresh the associated lifetimes, leading to the same effective lifetimes as specified by the DHCPv6-lease time. --- cut here ---- The above change tackles to different issues: * Saner lifetimes that at least allow for proper garbage collection in a timelier manner. * In the typical scenario (but depending on DHCPv6 server parameters), the DHCPv6-PD leased will be longer than the PIO lifetimes advertised by the CE Router, and the CE Router will renew the prefix lease well before the PIO lifetimes need to be adjusted/reduced (to avoid having PIO lifetimes that span past the dhcpv6-pd lease). The result is that, in practice, the CE Routers would send RAs that always contain the same lifetime values, thus avoiding the battery consumption problem mentioned by Lorenzo. Thoughts? Thanks! Cheers, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- [v6ops] cpe-slaac-renum: Proposed text for prefix… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Bernie Volz (volz)
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Bernie Volz (volz)
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Bernie Volz (volz)
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Niall O'Reilly
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Bernie Volz (volz)
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… otroan
- [v6ops] slaac-renum: Protocol-based improvements … Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Owen DeLong
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Owen DeLong
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Bernie Volz (volz)
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Owen DeLong
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Ted Lemon
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Erik Kline
- Re: [v6ops] cpe-slaac-renum: Proposed text for pr… Fernando Gont