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/address-policy-wg@ripe.net/
[address-policy-wg] Any-cast or uni-cast solutions
- Previous message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
- Next message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Thu May 24 08:34:51 CEST 2012
Randy, On Thursday, 2012-05-24 07:32:02 +0900, Randy Bush <randy at psg.com> wrote: > > The need and the route origination must be in the RIPE NCC service > > region. > > ahem! the ncc has repeatedly said over many years that it has nothing > to do with routing. I don't think this is true. For example, I remember the requirements for IPv4 PI space have included peering. I think a more accurate claim is that the RIPE NCC has always said that they don't guarantee that any resource you are issued can be routed. This makes sense, because that is between you and your peers (and the rest of the Internet). So, you may need to meet certain routing requirements to qualify for resources. But once you get them it's up to you to make them work. Cheers, -- Shane
- Previous message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
- Next message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]