Re: [v6ops] [E] New Version Notification for draft-mishra-v6ops-variable-slaac-problem-stmt-01.txt

[Bob Hinden <[e-mail]>]

Alexandre,

> On Nov 3, 2020, at 11:56 AM, Alexandre Petrescu <[e-mail]> wrote:
>>> 
>>> What Lorenzo said.
>>> 
>>> Further, I did quick read and see some immediate issues.
>>> 
>>> First off SLACC works just fine with any size prefix/interface ID.    The protocol supports different sized prefixes/IIDs.   The purported issue relates to interface ID sizes.   These drafts appear to be confused about that.
>>> 
>>>    Gyan> Understood that SLAAC in itself does not create the restriction as the 64 bit boundary restriction is due to 64 bit IID fixed length when A flag is set.
>> Good, then I suggest you stop calling it a SLAAC problem.*
> 
> We struggled during internal discussions about what to call it so that it gets better through.
> 
> Indeed, the SLAAC spec is independent of the prefix length.

Correct.

> 
> However, SLAAC spec needs IP-over-foo specs to give an IID.  And these latter are all 64bit len.  Indirectly, this makes that SLAAC forms GUAs with only a 64bit plen.
> 
> Maybe one would be ok to call it and _indirect_ SLAAC-GUA problem?

Again, ND and SLAAC works fine with any combination of prefix and IID length (as long as they add up to 128 bits, and the IID isn’t too small to avoid collisions on the link).

It’s not a SLAAC-GUA problem.  RFC4291 defines how long IIDs are:

   For all unicast addresses, except those that start with the binary
   value 000, Interface IDs are required to be 64 bits long...

Bob



> 
> (I formulated yesterday a longer email explaining this in more detail butd I hold it in my Drafts folder, and I restrain)
> 
> Alex
> 
>>>    The 6man draft below identifies the solution and references the last time this topic came up about a year or so ago with this draft "https://tools.ietf.org/html/draft-bourbaki-6man-classless-ipv6-05"
>>>    This draft submitted on 6man discusses the history behind the slaac 64 bit fixed iid and refrences the v6ops draft problem statement and defines the RA flag solution for slaac to support vlsm & eliminating the IID fixed 64 bit boundary.
>> I, and I suspect most of the working group, are very aware of the history and background on this topic.
>> Bob
>> _______________________________________________
>> v6ops mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops