- address-policy-wg - mailman.ripe.net

2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Steven Bakker 28 Oct '11

28 Oct '11

Just piping in to say I support this proposal. -- Steven

1 0

2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Michiel Appelman 28 Oct '11

28 Oct '11

I fully support the new policy proposal. -- Michiel Appelman AMS-IX

1 0

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Nigel Titley 27 Oct '11

27 Oct '11

On 25/10/2011 10:51, Emilio Madaio wrote: > Dear Colleagues, > > A proposed change to RIPE Document ripe-530, "IPv4 Address Allocation > and Assignment Policies for the RIPE NCC Service Region", is now > available for discussion. > I hate to be a killjoy here, but doesn't the average IXP use less than a /22? Part of the rational says: "Much of the work that goes into creating Internet Exchange Points today is done in regions of the world where there is no Internet Exchange Point yet. Opening an IXP helps to develop the Internet and Internet community in that region, so the work really is 'good of the Internet'. Starving these regions of an opportunity to build a simple open Internet Exchange Point would be severely damaging to Internet users in regions under-served by IXPs." But a brand new IXP will be able to get a /22 under the existing rules. Surely that's enough? I have a general dislike of "special cases" especially where they don't seem to be necessary. And this seems to be unnecessary. Nigel

3 7

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Barry O'Donovan 27 Oct '11

27 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/10/11 10:51, Emilio Madaio wrote: > A proposed change to RIPE Document ripe-530, "IPv4 Address > Allocation and Assignment Policies for the RIPE NCC Service > Region", is now available for discussion. We support this policy. - Barry - -- Kind regards, Barry O'Donovan http://www.opensolutions.ie/ Open Source Solutions Ltd Lynx House, Old Church Road, Lower Kilmacud Road, Stillorgan, Co. Dublin. Open Source Solutions Limited is a company registered in the Republic of Ireland (#438231). Open Source Solutions Limited trades as Open Solutions (registered business name #329120). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6ppK0ACgkQ9qwC7To4L8xItACdEfwnvF3KijY7um0Pba0/VfsQ ly0An1TO9dfQfDjKm9TCDt4kexwS589H =uiRD -----END PGP SIGNATURE-----

1 0

2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Vincent PAGES 27 Oct '11

27 Oct '11

HI, I'm the technical manager of LyonIX (Lyon Internet Exchange http://www.lyonix.net) We support the proposal. Regards, -- Vincent PAGES - Responsable Technique Rezopole - Lyonix Rezopole inaugure SaintetIX le 17 Novembre 2011 Mail: vpages(a)rezopole.net Standard: +33 4 27 46 00 50 Fax: +33 4 27 46 00 51 PGP: 7E06128C Skype: vincent.rezopole REZOPOLE (LYONIX Le GIX NAP de Lyon / Rhone-Alpes) 5 passage de l'avenir 69200 Vénissieux France - Email : info(a)lyonix.net - Web : www.lyonix.net

1 0

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Tom Hodgson 27 Oct '11

27 Oct '11

On Tue, 25 Oct 2011, Emilio Madaio wrote: > > A proposed change to RIPE Document ripe-530, "IPv4 Address Allocation > and Assignment Policies for the RIPE NCC Service Region", is now > available for discussion. > I do wonder how many special cases we will see crop up before we've let v4 exit stage left, however the benefits brought by the reservation of a /16 for increased network interconnection I think justify the addition to the policy. There is a question of whether the IXP should just become an LIR to receive an allocation that way, however I neither believe that an IXP should be forced into becoming an LIR or that all IXPs necessarily have an appropriate entity with which to do so, especially when they are in the startup phase. Therefore I support this policy. -- Tom Hodgson tom(a)someaddress.net

4 3

Proposal 2011-02 moving to Last Call
by Sander Steffann 26 Oct '11

26 Oct '11

Hello working group, After a extensive analysis of the discussions on the mailing list about proposal 2011-02 we have come to the conclusion that we have rough consensus on this policy proposal, and we have decided to move this policy proposal to Last Call. We have seen much support for this proposal on the mailing list. On the other hand we have seen concern about accelerated growth of the routing table caused by implementing this policy. Data from other RIRs that have a more liberal IPv6 PI policy have not shown evidence for excessive growth in IPv6 PI assignments. As of today, Sep 23, there are 2420 /48 routes in the global BGP table, compared to 3600 /32 routes and ~1100 routes of other prefix lengths. Based on this data we consider the arguments agains this proposal based on possible routing table growth as addressed. We will ask the RIPE NCC to ask for extensive documentation in the IPv6 PI request form about why IPv6 PI space is requested instead of PA space. The intention of this is to be able to analyze the reasons for organizations to request PI space and to make requesters think twice when requesting PI space. If this policy proposal has consensus at the end of Last Call we will also ask the RIPE NCC to monitor and regularly report on IPv6 PI assignment statistics so we can see if the number of PI requests runs out of bounds. On behalf of the Address Policy WG chairs, Sander Steffann

7 10

AP WG Agenda for RIPE63
by Gert Doering 26 Oct '11

26 Oct '11

Hi APWG folks, RIPE meeting orga, below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Amsterdam in the following three time slots: Wednesday, Nov 02, 09:00 - 10:30 Wednesday, Nov 02, 11:00 - 12:30 Thursday, Nov 03, 09:00 - 11:30 The exact time lines depend a bit on how much discussion is going on, so we might move items one time slot "up" or "down". If you have anything else you want to see on the agenda, or of we need to change anything, please let us know. regards, Gert Doering, APWG chair ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters (welcome, thanking the scribe, approving the minutes, etc.) B. Current Policy Topics - Emilio Madaio - global policy overview "what's going on?" - common policy topics in all regions (end of IPv4, transfers, ...) - overview over concluded proposals in the RIPE region since RIPE61 [list of things that the WG chairs collective agrees on] - brief overview over new proposals (2011-04, 2011-05) C. Policy Development Office Activities - Emilio Madaio D. Feedback From NCC Registration Service - Alex le Heux (Emilio and Alex will give the WG some insights on policy development topics from the NCC side) E Discussion of open policy proposals, part I 2011-02 IPv6 PI assignment policy / removal of multihoming req. (current status, by the AP WG chairs) 2011-04 initial IPv6 allocation size / 6rd (Jan Zorz) ---------------------------------------------------------------------- Wednesday, 11:00-12:30 ---------------------------------------------------------------------- J. Welcome back K. Discussion of open policy proposals, part II 2011-05 IPv4 Assignments to IXPs from the Last /8 (Andy Davidson, representing the EIX WG) L. on (Inter-RIR) transfers - Dave Wilson (tbc) M. IPv4 maintenance policy - Rob Blokzijl Introduction to a Work-in-Progress document about governance of IPv4 resources in the RIPE region after run-out + Q&A. N. On Renumbering IPv6 networks - N.N. [ report from the discussion in the IPv6 WG on Tuesday ] O. On Certificates - from the APWG chair [ what happened, and what next ] ---------------------------------------------------------------------- Thursday, 09:00-10:30 ---------------------------------------------------------------------- R. On IPv6 PI/PA Unification Discussion how the IPv6 PA/PI policies can be reworked in a fundamental way to better fit the needs of all IPv6 Users. Discussion led by working group chairs. S. Rough Edges of the current policies "if things show up" T. Discussion of open policy proposals "if we need more time" Y. Open Policy Hour "The Open Policy Hour (OPH) is a showcase for your policy ideas. If you have a policy proposal you'd like to debut, prior to formally submitting it, here is your opportunity." (Idea from ARIN policy meeting) Z. AOB -- 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

1 1

Policy Proposal: 2006-05 "PI Assignment Size" implemented
by Matt Parker 26 Oct '11

26 Oct '11

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that the policy described in proposal 2006-05, "PI Assignment Size", has been implemented. Requests for IPv4 Provider Independent (PI) address space received on or after Wednesday, 27 October 2011, will be evaluated by the RIPE NCC Registration Services Department under the new policy. The RIPE policy proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-05 The following RIPE Documents have been updated to reflect this policy implementation: http://www.ripe.net/ripe/docs/ipv4-policies http://www.ripe.net/ripe/docs/pi-requestsupport Regards, Matt Parker RIPE NCC Registration Services

1 0

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Remco Van Mook 26 Oct '11

26 Oct '11

Hi all, As I already indicated when this was last presented at the RIPE meeting, I strongly support a proposal to this end. The one thing I'm missing is the criteria for the size of the assignment - when does an IXP get a /24, /23 or a /22? With 'run out fairly' as accepted policy I don't think the timeframes set there are in any way realistic for Internet exchanges. So, clean as the current proposal is, I'd suggest making it a bit messier and adding very explicit criteria. 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 (Yes, this means renumbering every single time. Yes, it's a pain. Yes, if you run out of a /22 for your peering LAN you're fresh out of luck.) And while we're at it, I would suggest to add to 5.6.4: c. Any address space that is returned by an IXP will be added to the reserve as outlined in 5.6.2. Sorry :) Best, Remco van Mook Director of Interconnection, Europe remco.vanmook(a)eu.equinix.com +31 61 135 6365 MOB EQUINIX 51-53 Great Marlborough Street London, W1F 7JT, United Kingdom On 25-10-11 11:51, "Emilio Madaio" <emadaio(a)ripe.net> wrote: > > >Dear Colleagues, > >A proposed change to RIPE Document ripe-530, "IPv4 Address Allocation >and Assignment Policies for the RIPE NCC Service Region", is now >available for discussion. > > > >You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2011-05 > >We encourage you to review this proposal and send your comments to ><address-policy-wg(a)ripe.net> before 22 November 2011. > >Regards > >Emilio Madaio >Policy Development Officer >RIPE NCC > > This email is from Equinix Europe Limited or one of its associated/subsidiary companies. This email, and any files transmitted with it, contains information which is confidential, may be legally privileged and is solely for the use of the intended recipient. If you have received this email in error, please notify the sender and delete this email immediately. Equinix Europe Limited. Registered Office: Quadrant House, 4 Thomas More Square, London E1W 1YW. Registered in England and Wales, No. 6293383.

3 3