/128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

Brian, (changed topic to be more descriptive) >> Consider cellular host case: >> - host implements e.g. ND proxy and DHCPv6 PD for WAN connection >> sharing >> - host attaches to a network where only DHCPv6 happens to be used >> - host gets single /128 IPv6 address from DHCPv6 >> - host tries

What is the IETF consensus on the" Brokenness of specs w.r.t. client behavior with M&O bits"

Hello, all. I would like to see what is the IETF consensus on this topic. Currently we have no further conclusion on this topic than the point that it is very difficult to choose the silver bullet among several options listed by Thomas and Ralph. However, I also believe that we need to encourag

Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

Hello, Teemu. Thank you for your clarification. > Consider cellular host case: > - host implements e.g. ND proxy and DHCPv6 PD for WAN connection sharing > - host attaches to a network where only DHCPv6 happens to be used > - host gets single /128 IPv6 address from DHCPv6 > - host tries to get som