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 ]
niels=apwg at bakker.net
niels=apwg at bakker.net
Mon Oct 31 16:34:27 CET 2011
* fweimer at bfk.de (Florian Weimer) [Wed 26 Oct 2011, 15:43 CEST]: >* Emilio Madaio: > >> http://www.ripe.net/ripe/policies/proposals/2011-05 > >I oppose this policy. IXPs shouldn't be special-cased. The >assumption of a single peering LAN per organization does not seem to >match the requirements of the industry. It is odd that preexisting >PI space must be returned, but not existing PA space. I assume PA space will just remain allocated but not assigned, i.e. falls under the LIR's assignment window requirements again. -- Niels.
- 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 ]