Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02

We have been using DHCPv6 PD client for a long time and have released a proof of
concept implementation:

http://linkupnetworks.org/aero/aero-3.0.2.tgz

We also have an internal-only implementation that runs on Android. We have been
using it for over a year to work with enterprise mobile devices. This not is not a sales
pitch for our code, but rather a proof that the DHCPv6 PD client function is very
lightweight and easy to implement. I will make a plug for KEA, however - it is a
great DHCPv6 server system, open source and standards-compliant:

http://kea.isc.org/wiki

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Tuesday, March 21, 2017 2:53 AM
> To: Ross Chandler <ross@eircom.net>
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02 - multiple prefixes per device
> 
> Le 20/03/2017 à 19:26, Ross Chandler a écrit :
> >
> >> On 20 Mar 2017, at 13:01, Alexandre Petrescu
> >> <alexandre.petrescu@gmail.com> wrote:
> >>
> >>> "Optionally a single network prefix shorter than the default /64
> >>>  prefix may be assigned to a PDN connection. In this case, the
> >>> /64 default prefix used for IPv6 stateless autoconfiguration
> >>> will be allocated from this network prefix; the remaining
> >>> address space from the network prefix can be delegated to the
> >>> PDN connection using prefix delegation after the default bearer
> >>> establishment and IPv6 prefix allocation via IPv6 stateless
> >>> address autoconfiguration as defined in clause 5.3.1.2.2.”
> >>>
> >>> “The UE uses DHCPv6 to request additional IPv6 prefixes (i.e.
> >>> prefixes in addition to the default prefix) from the PDN GW after
> >>> completing stateless IPv6 address autoconfiguration procedures.”
> >>
> >> This seems to indicate that the PDN GW plays both a role of
> >> DHCPv6-PD Requesting Router aka DHCPv6 Client (when it gets
> >> "assigned" a shorter-than-64 prefix) _and_ the role of DHCPv6-PD
> >> Delegating Router aka DHCPv6 Server (when it delegates additional
> >> IPv6 prefixes to the UE).
> >>
> >> This is a little bit awkward for setting up routing.
> >>
> >> It would be simpler if the PDN GW were a DHCPv6 Relay.
> >>
> >> Has it been considered to make the PDN GW a DHCPv6 Relay?
> >
> >
> > In the case of /64 per host, the implementation I’ve seen supplies
> > the prefix needed by SLAAC by having the GW address assignment
> > function generate a DHCPv6 PD request which the GW relays either to
> > an internal DHCPv6 server  or to a central server. That is in a TWAG
> > supplied by one of the draft’s authors. It seems to be done in a way
> > ripe for extension to support UE DHCPv6-PD requests after the
> > initial SLAAC /64 is assigned.
> 
> Sounds promising.
> 
> We wrote a python DHCPv6 client called "PD tester" that issues DHCPv6 PD
> requests to cellular networks.  We tested it on a one cellular network
> and no answer until now.
> 
> We would like to test it on other cellular networks.
> 
> Is the TWAG applied in some cellular network?
> 
> Alex
> 
> >
> > Ross
> >
> >
> >
> >
> >
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops