Re: draft-bourbaki-6man-classless-ipv6-00

Le 15/06/2017 à 03:00, Lorenzo Colitti a écrit :
> On Thu, Jun 15, 2017 at 2:36 AM, Manfredi, Albert E 
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>>
> wrote:
> 
> -----Original Message----- From: ipv6 [mailto:ipv6-bounces@ietf.org 
> <mailto:ipv6-bounces@ietf.org>] On Behalf Of otroan@employees.org 
> <mailto:otroan@employees.org>
> 
>> What _problem_ does changing the 64 bit boundary solve for _you_?
> 
> A category of problems, such as creating hotspots with smartphones 
> that have been allocated a single /64.
> 
> 
> That works today on all major smartphone OSes.

If this refers to '64share' - that's an INFORMATIONAL way of of working. 
  It has drawbacks.

If OS means OS distribution - that's that particular distribution's 
advantage, or inconvenient.

An OS like linux can be distributed as Android (run the non-scalable 
64share, avoid DHCP-PD) or can be distributed as Legato (dont run 
64share and run the scalable DHCP-PD).

Please be precise with respect to 'OS'.

> And the situation is actually the opposite: the only reason it works
> today is that phones *already had* a /64 instead of a /128.

They may have it, in a way.

So, if that category of problems is not sufficient, a similar  category 
of problems is other major IoT or M2M devices that run other major OS 
distribution than smartphones.

In the automotive market these small routers are called for example 
on-board routers and road-side units.

Similar small routers are in the smart building and smart city markets.

These need to connect to cellular networks and offer connectivity to 
more other devices than a smartphone does.

Alex

> If part of what makes IPv6 wonderful is SLAAC, then I don't think 
> it's wise to cripple non-/64 solutions by artificially mandating that
> SLAAC be only possible with /64s. The smartphone hotspot example is
> one in which a non-/64 SLAAC would work great. And there's simply no
> reason to state that SLAAC can only work with /64s. It's not true!
> 
> 
> SLAAC doesn't work unless the network provides enough address space
> to make collisions vanishingly unlikely.
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 