This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ppml] [address-policy-wg] Re: Just say *NO* to PI space -- or how to make it less destructive
- Previous message (by thread): [ppml] [address-policy-wg] Re: Just say *NO* to PI space -- or how to make it less destructive
- Next message (by thread): [ppml] [address-policy-wg] Re: Just say *NO* to PI space -- or how to make it less destructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Fri Apr 21 22:13:17 CEST 2006
> On the other hand, it make perfect sense for anyone who wants their > PI space advertised to pay their upstreams for the privilege, since > there is a real cost in doing so. Mmmm, and how is this going to guarantee that the PI space is accepted by third party networks? I'm aware that the two things are separate, paying to have your prefixes accepted by an upstream, and expecting them to be globally routable. But how is the average Joe Schmoe customer going to feel if they pay a premium to have their PI prefixes "accepted" by their ISP's upstreams, when they're not accepted by anyone else? Not convinced, Nick
- Previous message (by thread): [ppml] [address-policy-wg] Re: Just say *NO* to PI space -- or how to make it less destructive
- Next message (by thread): [ppml] [address-policy-wg] Re: Just say *NO* to PI space -- or how to make it less destructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]