Cameron, > > > Is it the case that MAP deployments require DHCPv6 and therefore for > > > mobile the solution is scoped only for 3GPP release 10 and beyond > > > networks? > > > > MAP could be provisioned with whatever protocol you like. DHCPv6 is kind of > > the obvious one and the one IETF controls. > > which one would fit best in a 3GPP environment? GTP (or DNS)? > > > > None come to mind. > > GTP with PCO might work, but I think it would end up being a lot of sdo heavy > lifting to make that work and the timeline would be long. > > I am still unclear on how MAP works. Is it a /128 that the CE must use so > that magic happens ? If so, I am not even sure that is scoped currently in > 3gpp since the use case is pd with dhcpv6
do you know how 6to4 or ISATAP works? it works pretty much just like that, but with the forwarding mapping being from IPv4 address to IPv6 address instead of from an IPv6 address to an IPv4 tunnel end point address. > For someone who wants MAP to work in 3gpp, the best path may be to hold out > for dhcpv6 and make specific requirements on how the ue must source traffic > from an address acquired from dhcpv6 when MAP is the transition solution. there isn't any specific requirements as such. for MAP-E all traffic is terminated at a single address that the CE has to 'configure' for itself based on the delegated prefix / assigned address. > But, it may end up looking like a square peg pounded into a round hole. But, > such is life in transition indeed. of course in 3GPP where you already have a tunnel, one would think you could take advantage of that. cheers, Ole _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
