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 ]
Gert Doering
gert at space.net
Tue Oct 25 21:03:11 CEST 2011
Hi,
On Tue, Oct 25, 2011 at 07:06:05PM +0100, Remco Van Mook wrote:
> With some first hand experience in setting up Exchanges, I would suggest
> the following:
>
> - a new IXP gets a /24
> - an existing IXP that runs out of its /24 (whether from this /16 or
> another range) gets a /23 and has to return the old /24
> - an existing IXP that runs out of its /23 (whether from this /16 or
> another range) gets a /22 and has to return the old /23
I think this is all logical to people setting up exchanges - but indeed,
it might be useful to make this clear to people evaluating such a request,
quite likely having never worked at an IXP yet...
Andy, you're taking notes? :-)
Gert Doering
-- APWG chair
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- 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 ]