[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 ]
David Conrad
drc at virtualized.org
Thu May 24 18:12:38 CEST 2012
Shane, On May 23, 2012, at 11:34 PM, Shane Kerr wrote: > 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. Actually, all the RIRs have said this. > 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. All the RIRs have also said this. > So, you may need to meet certain routing requirements to qualify for > resources. Historically, this was _not_ the case. Long, long ago, there was a bit of a dust up between the IAB and (at least some) RIR folks that resulted in RFC 1814. However, that was long ago and policies might have changed. Regards, -drc
- 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 ]