| from label switching, so what I'm suggesting is that we take the bull by
| the horns once and for all and run MPLS over IP instead of under it...
an mplsd-like tag fits neatly in the first half of an ipvsux destination
address, although there are other places in the vsux header you can put
tag bits if you're inclined to do so for stacking reasons or whatnot.
one nicety of stuffing the tag into the vsux header (or even *below*
the vsux header, as payload) is that you can forward through v6 networks
such as they exist, without them also simultaneously having to be MPLSd.
that is, you abstract a collection of vsux-but-not-mplsd routers
into a connection between two lsrs (with likely hit to reservation based
control plane).
in other words, a particularly useful mplsd label is one that causes the
next-hop lsr to generate a packet that is relevant within a non-mplsd
network with its own topological namespace. that is, generate an IPvsux
or ordinary IP packet out an interface such that things on the other
side of the interface can route back to it. that is, tag "xyzi" means
be a NAT and send packet out IP/IPvsux interface "i".
this has all the same problems of NAT where there is no end-to-end
namespace that is not TOPOLOGICAL in nature separate from but convertible
between a namespace populated with globally unique IDENTITY names.
(where that namespace can mean single hosts or service locations or whatever,
but not two or more of these things simultaneously! overloading bad.)
Sean.