Yes, as a subset of shim6. Ie, using an 8+8 static mapping for the local ULID(s), and using whatever shim6 control messages are needed to map the remote ULID to the correct remote locator(s). It would be assumed that the ULIDs are composed of a prefix and a host ID, obviously. The mapping would only change the prefix.
I think it would be very useful to allow such a mapping, and hence allow split/proxy shim6.
i agree it would be useful but i still not sure how do you deal with security stuff in this case...
There are no security implications to static mapping. It never changes.
regards, marcelo
No more than there are security implications to a non-shim6 host forwarding packets according to a static routing table of destination->nexthop.
regards, -- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.