Re: [sig-policy] New version of prop-110: Designate 1.2.3.0/24 as Anycas
> ---------------------------
>
> This proposal recommends that the APNIC community agree to assign
> 1.2.3.0/24 to the APNIC Secretariat for use in the context of locally
> scoped infrastructure support for DNS resolvers.
>
> At some future point there is nothing restricting an RFC being
> written to include this prefix into the special-purpose IPv4
> registry. However, at this time it is considered sufficient for the
> APNIC community to designate this prefix to be managed as a common
> anycast address for locally scoped infrastructure support for DNS
> resolvers.
In an off-list discussion, a question was raised as to what the intended definition of “locally scoped” is. My interpretation is that advertising 1.2.3.0/24 across an AS boundary would not be a wise thing to do, but I appreciate that authors may have a different view.
One specific example of this related to what behaviour one might expect from an IXP’s route servers. Obviously operational decisions are up to each network, but are we expecting that 1.2.3.0/24 might be exchanged between ASes, or that it would become another martian prefix?
Cheers