Re: rfc4941bis: Change to Valid Lifetime of temporary addresses

+1  In agreement with the change.

Gyan

On Thu, Feb 20, 2020 at 1:30 PM Fernando Gont <fgont@si6networks.com> wrote:

> 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
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
-- 

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com