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

AP meeting at RIPE 62 - Agenda draft
by Gert Doering 15 Apr '11

15 Apr '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: Thursday, May 05, 09:00 - 10:30 Thursday, May 05, 11:00 - 12:30 Friday, May 06, 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 ---------------------------------------------------------------------- Thursday, 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 2010-05 Global Policy for IPv4 ... post exhaustion - withdrawn 2010-06 Registration Requirements for IPv6 ... Assignments - accepted 2010-07 Ambiguity cleanup on IPv6 Addr. ... Policy for IXP - withdrawn 2010-02 Allocations from the last /8 - accepted 2008-07 Effcient Use of Historical IPv4 Resources - withdrawn 2010-01 Temporary Internet Number Assignment Polices - Last Call - brief overview over new proposals (2011-01, 2011-02) C. Document Cosmetic Surgeries Project - Emilio Madaio - update on current status - how to go forward? D. On IPv6 Documentation Requirements - Marco Hogewoning Short presentation explaining how the policy change 2010-06 and AGGREGATED-BY-LIR affects day-to-day business for LIRs assigning IPv6 blocks to end users. E. Rough Edges of the current policies Report from the RIPE NCC Registration Services department on issues and unintended side-effects showing up in the daily implementation of the RIPE policies. o policy for upgrade of "initial /32 allocation" assigned to large carriers to "something large enough for their needs" (Explanation how these cases are currently handled, Alex Le Heux) o IPv6 PI discussions between RIPE members and the NCC RS (Explanation to the audience where the "sore spots" are, Alex L.H.) ---------------------------------------------------------------------- Thursday, 11:00-12:30 ---------------------------------------------------------------------- L. On IPv6 PI Policy 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. M. Discussion of open policy proposals - IPv6 related 2011-02 (IPv6 PI multihoming) N. On Transfer Guidelines - David Wilson bringing non-obvious problems with transfers into the open goal: write a RIPE BCP document ---------------------------------------------------------------------- Friday, 09:00-10:30 ---------------------------------------------------------------------- S. More Rough Edges of the current policies "if more things show up" T. Discussion of open policy proposals 2006-05 IPv4 PI Assignment Size [ONGOING] 2008-08 Initial Certification Policy for (...) Address Space Holders [ONGOING] 2010-01 Temporary Internet Number Assignment Policies [ONGOING] 2011-01 Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA [NEW policy proposal] 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 -- did you enable 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 0

APNIC activated to 'Final /8' policy
by Sander Steffann 14 Apr '11

14 Apr '11

Hi WG, The IPv4 pool of APNIC has just gone below 1 /8. Therefore APNIC is the first RIR who has activated their 'Final /8' policy: http://www.apnic.net/services/apply-for-resources Sander Steffann APWG co-chair

1 0

2010-01 Last Call for Comments (Temporary Internet Number Assignment Policies)
by Emilio Madaio 13 Apr '11

13 Apr '11

Dear Colleagues, The proposal described in 2010-01 is now at its Concluding Phase. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2010-01 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 11 May 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

AW: [address-policy-wg] 2008-08 New Draft Document Published (Initial Certification Policy in the RIPE NCC Service Region)
by Klaus.Kinder＠telekom.de 12 Apr '11

12 Apr '11

Gesendet von meinem Windows® Phone. ----- Ursprüngliche Nachricht ----- Von: Emilio Madaio <emadaio(a)ripe.net> Gesendet: Dienstag, 12. April 2011 17:16 An: policy-announce(a)ripe.net <policy-announce(a)ripe.net> Cc: address-policy-wg(a)ripe.net <address-policy-wg(a)ripe.net> Betreff: [address-policy-wg] 2008-08 New Draft Document Published (Initial Certification Policy in the RIPE NCC Service Region) Dear Colleagues, Following the feedback received, the draft document for the proposal described in 2008-08 was edited and published. The new impact analysis that was conducted for this proposal has also been published. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-08 and the draft document at: http://www.ripe.net/ripe/policies/proposals/2008-08/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 26 April 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

AW: [address-policy-wg] 2008-08 New Draft Document Published (Initial Certification Policy in the RIPE NCC Service Region)
by Klaus.Kinder＠telekom.de 12 Apr '11

12 Apr '11

Gesendet von meinem Windows® Phone. ----- Ursprüngliche Nachricht ----- Von: Emilio Madaio <emadaio(a)ripe.net> Gesendet: Dienstag, 12. April 2011 17:16 An: policy-announce(a)ripe.net <policy-announce(a)ripe.net> Cc: address-policy-wg(a)ripe.net <address-policy-wg(a)ripe.net> Betreff: [address-policy-wg] 2008-08 New Draft Document Published (Initial Certification Policy in the RIPE NCC Service Region) Dear Colleagues, Following the feedback received, the draft document for the proposal described in 2008-08 was edited and published. The new impact analysis that was conducted for this proposal has also been published. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-08 and the draft document at: http://www.ripe.net/ripe/policies/proposals/2008-08/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 26 April 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Status of 2010-01 (Temporary Internet Number Assignment Policies)
by Gert Doering 12 Apr '11

12 Apr '11

Dear AP Working Group, RIPE Policy Proposal 2010-01 (Temporary Internet Number Assignment Policies) concluded its Last Call phase on 28 December 2011. After consultation between the Working Group Chairs, however, it has been decided that reporting of the process in this case was insufficient, that is, the working group has not been properly informed why the WG chairs have decided to go to Last Call. It has therefore been decided that the Last Call phase for this proposal should be repeated. Emilio will announce a new Last Call phase today or tomorrow. The reason why we decided to go for Last Call in the first place, and are now doing it again: - Feedback to the mailing list regarding the proposal itself has been mostly positive. - A few people voiced concerns in the mailing list discussion, and at the RIPE 61 meeting, but when specifically asked at the RIPE 61 meeting whether they wanted to see changes now or go ahead with the proposal, those raising the concerns agreed to move forward with the Policy Development Process and look at changes in future revisions. - It was agreed that it's important to have a reservation for temporary IPv4 assignments in place while there still *is* something to reserve - and that the specific details of the implementation can always be changed later on. You can read the full text of the proposal at: http://ripe.net/ripe/policies/proposals/2010-01.html The (draft) meetings from the RIPE 61 APWG meeting can be found here: http://www.ripe.net/ripe/groups/wg/ap/minutes/minutes-from-ripe-61 (just search for 2010-01) Gert Doering -- APWG Chair -- did you enable 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

RIPE IPv4 Pool Graph
by Ahmed Abu-Abed 06 Apr '11

06 Apr '11

Greetings, RIPE NCC is now publishing an IPv4 pool graph with weekly updates, and the latest data show five /8 blocks are remaining. More at http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-po… Regards, -Ahmed

1 0

IPv6 PI request is turned down for my multihomed hosting facility - Why?
by Jan Tuomi 01 Apr '11

01 Apr '11

Hi, A have made a request for a IPv6 PI / 48 allocation for my hosting facility. I am mostly hosting shared services, but I also have a lot of Co-located services for my customers. I am already multihomed to have redundancy from two ISPs for IPv4 and I am going to setup the IPv6 Network the same way. My ASN is 196704, and I am multihoming trough IP-Only (AS12552) and Telenor (AS8434). My sponsoring LIR says that I can get an assignment from their PA-space right away, BUT then I would not be multi-homed, so that is NOT an option. The answer I get from you (RIPE) is: You mentioned that several of the subnets will be used to provide services to your customers (LEON Hosting, Co-location/Dedicated servers). Unfortunately current IPv6 address assignment and allocation policy does not permit the use of IPv6 PI address space for these services. At this time IPv6 PI address space cannot be used for any service where a customer would receive a subnet of IP space (including a single IP). Therefore it cannot be used for colocation services, dedicated servers, SSL certificates etc. There is currently a discussion on exactly this subject within the RIPE community. Ventiro AB are welcome to sign up for the mailing list and join the discussion. You can find the mailing list here: http://www.ripe.net/ripe/mail/ripe-lists/address-policy-wg I need to be multihomed because i feel its safer to have redandancy from separate upstreams with separate infrastructure than buying the redundancy from one provider. My business is to keep servers running in my hosting facility, part of them owned by me, part of them owned by the customers. Some servers are shared among several customers, some are dedicated to one customer only. With todays technology as far as I know I must have separate IPs for SSL-enabled services. Is it RIPEs hidden agenda to put small hosting facilitys out of business with IPv6 and force all customers to use the bigger ISPs? When I requested my IPv4 PI allocation, I was already planning to also run with IPv6 to be prepared for the future and somehow try to help with the transition to IPv6, so people dont have the arguments that we dont use IPv6 because there is no services, its now so much services from a global point of view, but it wouldnt be IPv4 only.... So what should I do? What are my options? // Janne _______________________ V E N T I R O ______ Janne Tuomi, tuomi(a)ventiro.se Tel: +46-11-36 52 00 GSM: +46-70-224 6000 Fax: +46-11-36 52 05

14 31

2011-01 New Policy Proposal (Global Policy for post exhaustion IPv4 mechanisms by the IANA)
by Emilio Madaio 22 Mar '11

22 Mar '11

Dear Colleagues, A new Global Policy Proposal has been made and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-01/ We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 18 April 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

6 7

RE: [address-policy-wg] IPv6 allocations for 6RD
by Kurt Smolderen 21 Mar '11

21 Mar '11

I strongly support the idea of assigning a smaller prefix to ISPs which are in a state of deploying IPv6 but need to use transitional mechanism for (some of) their customers. Mark has described one of the problems very clear in his email: if an ISP has only a /32 prefix and needs to use all 32 IPv4 bits in the 6rd configuration, only a /64 can be delivered to the home instead of the desired /56 or /48. Needing all 32 bits is for instance the case when an ISP offers internet connectivity to some of its customers via a partnership with another ISP. However, I want to point to an additional problem which appears when an ISP wants to deploy native IPv6 but needs to roll out 6rd (or any other transitional technique) as well. For native IPv6, the ISP will create an IPv6 addressing plan. This will normally include separate prefixes for the ISP's own servers, the ISP's backbone, the ISP's customers etc. For the 6rd domain, the full /32 range is however needed. So at this stage, the ISP has two options: 1) Implement 6rd only 2) Implement native IPv6 only and exclude some customers from being able to use IPv6 (those which would normally be connected through 6rd) I strongly believe we all agree 6rd is only a temporary solution. So I can't imagine we would prefer skipping native IPv6 deployments in favor of IPv6 transitional mechanisms. I also believe we all agree we should enable IPv6 for as much customers as we can, which makes me conclude the second 'option' is not really an option at all... My primary concern is that any ISP - regardless of how small or big it is - can independently of other organizations/ ISPs move forward with IPv6 deployment. RIPE can support this by adapting a policy which - albeit for a limited time span - allows the assignment of a contiguous IPv6 prefix which size does not only depend on the amount of customers the ISP has, but also incorporates the needed technologies to 'IPv6-enable' as much customers as possible. Regards, -Kurt

7 17