Intended status of the Variable SLAAC solution draft-mishra-6man-variable-slaac

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 14 December 2020 10:39 UTC

To: IPv6 <ipv6@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Intended status of the Variable SLAAC solution draft-mishra-6man-variable-slaac
Message-ID: <bd494fee-2f49-8478-81d0-bbd75201063c@gmail.com>
Date: Mon, 14 Dec 2020 11:39:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1V3ZtPzPtUeGQUTomRDNA8zQ02E>
Precedence: list

Hi, 6MANers,

I would like to suggest to consider the Intended Status of the Variable 
SLAAC draft-mishra-6man-variable-slaac to be EXPERIMENTAL, rather than 
the current value Standards Track.

What do you think?

To explain:

During the last IETF meeting we discussed extensively the concept of a 
Variable SLAAC.  In this concept the IID length would be of any length, 
rather than fixed at 64.

There was pushback as well as support to that VSLAAC concept.

As an alternative, there was a suggestion by a few participants to 
consider a 'lightweight ND-based prefix delegation mechanism.'  This 
mechanism would be developped with the blessing of a cellular operator.

But until that is done, we suggest an EXPERIMENTAL status for the 
Variable SLAAC solution draft.

What do you think?

Alex

PS: this EXPERIMENTAL I-D intended status would be accompanied by an 
implementation in the linux kernel that is conditioned by a sysctl knob. 
  This knob is initialized to zero by default.

net.ipv6.conf.enp0s3.variable_slaac=0 by default

If necessary, it would also be accompanied by an EXPERIMENTAL status for 
a 'VSLAAC' option in the kernel configuration (make menuconfig), also 
reset by default.

Intended status of the Variable SLAAC solution dr… Alexandre Petrescu