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]/
[address-policy-wg] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo.vegoda at icann.org
Wed Jun 13 16:57:25 CEST 2007
On 13 Jun 2007, at 3:09pm, Sascha Lenz wrote: [...] >> If the fees aren't a problem then the easiest way to get the >> address space might be to sign up as an LIR, get the minimum >> allocation and break it up. It's not the most elegant solution but >> it should work. > > *purr* That's quite a customer-friendly rule-bending in my eyes - > it doesn't solve the general "how to justify the size of an > assignment needed for routing" issue. > > They only "half-way right" solution to this in my head sounds like > becoming LIR and dedicating a sub-allocation of the PA space you > get for Anycast announcement. This way you can seperately announce > the Sub-Allocation, and have no problems justifying a routable > *assignment* > The actual assignment within the sub-allocation can be a /29 then > or whatever you really need for the Anycast setup. > ...doesn't really sound appealing for me though. Yes, routes could be shorter prefixes than assignments. It's certainly not ideal and it probably means the LIR would never qualify for an additional allocation but it would fix a short term problem while there is no policy meeting this need. Regards, -- Leo Vegoda IANA Numbers Liaison
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]