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] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Previous message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Next message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Thu Oct 27 17:42:45 CEST 2011
On 27/10/2011 15:56, Andy Davidson wrote: > Thanks for the emails. > > Almost no IXPs have PA, and most community based ones don't have budget for their own LIR. This policy allows successful IXPs to be born in 2012 as they have been between 1994 and 2011. i.e. the equivalent of PI. It will provide policy parity with IPv6 too, where IXP specific policy exists in order to sidestep restrictions designed for other networks. Hmm, yes, I see what you mean. I think what might have confused me is the 5.6 section heading "Use of last /8 for PA allocations". The IXP allocation section (not being PA, as you've pointed out) doesn't really belong here. And yes, I agree this is nit-picking, before anyone says it for me. And following the clarification I'm happy with the intent of the proposal (whilst still being unhappy with special cases in general). Nigel
- Previous message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Next message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]