MPLS is well-spread all over (most) ISPs and is well-confined to ISP networks, i.e. it is not an end-user topic at all. In support of IPv4-forever a new brand of MPLS may accomplish packet forwarding down to the destination geo-patch (square degree) or even closer. The ingress router adds the new MPLS-label which indexes the destination geo-patch and which is never SWITCHED (replaced) down the road. A second "MPLS-label" may even convey the destination square minute... Do not assume that hereby only a single path is enabled. No: multiple ones. And by means of further conveyed data some differentiated sub-sets thereof might be selected.
I will not continue explaining TARA once more (how to get this information and how to map it to the next hop), but make some general syntax considerations triggered by the current discussion about "IPv4 or only IPv6". Ipv4 as well as IPv6 will be serviced simultaneously. There won't be any MTU-size problems. The end-user is out of the game. There is no major problem during the introduction phase. Map-encap, map-translate, Flow-label, optional parameter: why not a new brand of L2-label ?!!! Heiner
