Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

There are many solutions for that, and in fact, some of them, not "in RFCs" are being used.

For example, you can use by default the first /64 for the WAN link, then 2nd one for the smartphone itself, then the rest don't need to be standardized. In fact, which one uses the smartphone itself is not needed.

See RFC3633, and also https://tools.ietf.org/html/draft-palet-v6ops-p2p-links-04.

In fact, I recall having seen some slides or document indicating that each /64 allocated to a smartphone is actually a /60 and part of it is the p2p link, but I'm not sure if that was before the actual standards, just an idea, or actual standards. I need to find that document to make sure ....

... Just found it! https://www.rmv6tf.org/wp-content/uploads/2012/11/Cisco_Suthar_Designing-LTE-with-IPv6_26-April-20111.pdf

Regards,
Jordi
@jordipalet

El 9/11/20 10:35, "ipv6 en nombre de Alexandre Petrescu" <ipv6-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:

    Le 09/11/2020 à 02:25, Brian E Carpenter a écrit :
    > On 09-Nov-20 13:00, Ca By wrote:
    >> 
    >> 
    >> On Fri, Nov 6, 2020 at 1:05 AM <otroan@employees.org 
    >> <mailto:otroan@employees.org>> wrote:
    [...]
    > Just handing out a /56 to each PDP context would be so much better.

    Sounds reasonable because a /56 is so much space, and can make several /64s.

    But still, it would not be enough.  How would the smartphone form an
    IPv6 address when receiving a /56 in the RA?  There is no spec that
    tells it how to, because the IID must be 64bit and the smartphone would
    not know how to pad the remaining 8 bits.

    At that point the operator might want to put a /64 in an RA and also
    respond to DHCPv6-PD with a /56 inside.  It would be a double address
    architecture effort.

    This is why I am wondering how would one think the smartphone would be
    happy enough when receiving a /56 in a DHCPv6 advertisement.

    Alex

    > 
    > Brian
    > 
    >> 
    >> None of that exists today in mobile. I feel the effort and scale 
    >> are daunting, so i am not going to do it.
    >> 
    >> But, getting a knob in the gateway to set the RA to be 60 (or 
    >> other) instead of 64 would be easy. And, that knob could be 
    >> constrained to only compatible device type (chef’s kisses!)... it 
    >> can be done
    >> 
    >> 
    >> 
    >> Best regards, Ole
    >> 
    >> 
    >> --------------------------------------------------------------------
    >>
    >>
    >>
    >> 
    IETF IPv6 working group mailing list
    >> ipv6@ietf.org Administrative Requests: 
    >> https://www.ietf.org/mailman/listinfo/ipv6 
    >> --------------------------------------------------------------------
    >>
    >

    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.