Re: Generic anycast addresses...

[George Michaelson <[e-mail]>]

Scope beyond your own administrative boundary is ill-defined. in
Routing constraints, NOEXPORT and NOPEER are not well deployed always.
path length limits are also not in your own control: you are trying to
seed behaviour into the routing framework which demands others accede
to your requests, but thats all they are: requests.

TTL in actual packets in flight is a different matter. But the hop is
not respecting of the boundaries here its about the elements the
actual IP packet takes, not the AS adjacencies along the path. It
doesn't relate sensibly to anything beyond the immediate link.

So.. I think this stuff is heading to a place where the "scope" is
well understood, albiet not exactly wired down, between local and the
edge of the AS containing the (mixture of) local links, but beyond
that, is ill-defined or un-defined.

Is that ok? Is that what you want?

-G