> I'd politely suggest that this is an area that the RIPE NCC should not
> get involved in, especially from the point of view of implicitly issuing
> recommended practice by implying that there is a problem with doing
> this.  The IXP associations are better placed to gather consensus for
> creating best practices, and there is no general consensus in the IXP
> community on this issue.

Full agreement with Nick, the (controlled) announcement or otherwise
of an IXP prefix is not a registry policy issue.

Cheers,
Rob

Reply via email to