Auto-configuring IPv6 transition mechanisms on customer devices

[swmike at swm.pp.se (Mikael Abrahamsson)]

On Fri, 14 Dec 2018, Brandon Martin wrote:

> Are there any (draft, standard, or otherwise) defined mechanisms for 
> indicating to customer-provided devices that they should configure IPv6 to 
> IPv4 transition mechanisms such as MAP, 4rd, 464XLAT, etc. and providing the 
> configuration details thereof?
>
> I'm not aware of any.  It seems like this is something that, if defined, 
> would make deployment of such mechanisms a lot easier even if SPs provide the 
> customer edge router that implements said mechanisms.  I guess they'd 
> probably be implemented as extensions to DHCPv6 or similar or embedded in RAs 
> (the latter seems ugly).

We use this to configure LW4o6 tunnels using DHCPv6. This is already 
present in OpenWrt via the MAP package. It supports both MAP-E and LW4o6.

https://tools.ietf.org/html/rfc7598

DHCPv6 Options for Configuration of Softwire Address and Port-Mapped 
Clients

    This document specifies DHCPv6 options, termed Softwire46 options,
    for the provisioning of Softwire46 Customer Edge (CE) devices.
    Softwire46 is a collective term used to refer to architectures based
    on the notion of IPv4 Address plus Port (A+P) for providing IPv4
    connectivity across an IPv6 network.

-- 
Mikael Abrahamsson    email: swmike at swm.pp.se