Re: rfc4941bis: Change to Valid Lifetime of temporary addresses

Fernando Gont <fgont@si6networks.com> Thu, 20 February 2020 18:30 UTC

Return-Path: <fgont@si6networks.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 84D2A12004F for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 10:30:33 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 VEFNUNrL8fvu for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 10:30:32 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE71512004E for <6man@ietf.org>; Thu, 20 Feb 2020 10:30:31 -0800 (PST)
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 5618A86BAB; Thu, 20 Feb 2020 19:30:29 +0100 (CET)
Subject: Re: rfc4941bis: Change to Valid Lifetime of temporary addresses
From: Fernando Gont <fgont@si6networks.com>
To: "6man@ietf.org" <6man@ietf.org>
References: <9cb65947-f634-e250-bfdc-134cfa2c91e9@si6networks.com>
Message-ID: <928b03dd-31f0-a2b2-218f-6494fad9f0cf@si6networks.com>
Date: Thu, 20 Feb 2020 15:27:31 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <9cb65947-f634-e250-bfdc-134cfa2c91e9@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nC5nliI0d0u_bvPh2orPMo7fXpg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Feb 2020 18:30:33 -0000

Folks,

As discussed before, and also based on recent feedback, I'll be applying 
the following change to the next rev of the document.

This change changes the Preferred Lifetime and Valid Lifetime of 
temporary addresses to 1 day and two days, respectively, thus reducing 
the number of concurrent addresses.

If you have any objections, please speak up.

Thanks!

Cheers,
Fernando




On 30/1/20 19:27, Fernando Gont wrote:
> Folks,
> 
> It has been suggested by Lorenzo Colitti, David Farmer, and others, to 
> change the default Valid Lifetime of temporary addresses.
> 
> Namely, to change it from the current (RFC4941) "one week", to "two 
> days". This indirectly limits the maximum number of temporary addresses 
> employed by hosts. (2, compared to the current 11 (as per RFC4941)).
> 
> This requires these changes:
> 
> * Section 3.5:
> 
> OLD:
>     Because the precise frequency at which it is appropriate to generate
>     new addresses varies from one environment to another, implementations
>     SHOULD provide end users with the ability to change the frequency at
>     which addresses are regenerated.  The default value is given in
>     TEMP_PREFERRED_LIFETIME and is one day.  In addition, the exact time
>     at which to invalidate a temporary address depends on how
>     applications are used by end users.  Thus, the suggested default
>     value of one week (TEMP_VALID_LIFETIME) may not be appropriate in all
>     environments.  Implementations SHOULD provide end users with the
>     ability to override both of these default values.
> 
> NEW:
>     Because the precise frequency at which it is appropriate to generate
>     new addresses varies from one environment to another, implementations
>     SHOULD provide end users with the ability to change the frequency at
>     which addresses are regenerated.  The default value is given in
>     TEMP_PREFERRED_LIFETIME and is one day.  In addition, the exact time
>     at which to invalidate a temporary address depends on how
>     applications are used by end users.  Thus, the suggested default
>     value of two days (TEMP_VALID_LIFETIME) may not be appropriate in all
>     environments.  Implementations SHOULD provide end users with the
>     ability to override both of these default values.
> 
> 
> * Section 5:
> 
> OLD:
>     TEMP_VALID_LIFETIME -- Default value: 1 week.  Users should be able
>     to override the default value.
> 
> NEW:
>     TEMP_VALID_LIFETIME -- Default value: two days.  Users should be able
>     to override the default value.
> 
> 
> Comments? Objections?
> 
> Thanks!
> 
> Cheers,


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492