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

Re: [address-policy-wg] 2011-04 New Policy Proposal
by Ahmed Abu-Abed 25 Oct '11

25 Oct '11

Interesting to see a v6-in-v4 access protocol triggering a significant change in allocation policy. As 6rd gobbles up 32 bits for the v4 address at the consumers v6 assignment, there is an alternative in RFC 5572 (TSP) that presents v6-in-v4 access on CPEs without such a need. And TSP can be implemented as a software client so LIRs do not need to change the CPEs to roll out IPv6 to end users. -Ahmed ------------------------------ Message: 8 Date: Mon, 24 Oct 2011 21:28:47 +0200 From: "Jan Zorz @ go6.si" <jan(a)go6.si> Subject: Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation) To: address-policy-wg(a)ripe.net Message-ID: <4EA5BC6F.90005(a)go6.si> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 10/24/11 7:29 PM, Randy Bush wrote: > why are we screwing around? let's go straight to a /16 or at least a > /20. it would not be fair to legacy v6 allocations :) can only expand to /29 without renumbering :S cheers, Jan

2 1

Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by Remco Van Mook 24 Oct '11

24 Oct '11

All, I support the thought that LIRs should be able to get up to a /29 as an initial allocation with no documentation required. However, that doesn't mean I support the policy proposal in its current form. Here's why. In the current policy text, it's very clear cut that unless you provide documentation (which means you've thought about how to deploy), you get a /32. I would not want a situation where people get a /29 without thinking, making a mess of it and then come back. So you could get a /29 if you asked for it specifically, otherwise you get a /32. So I would propose the following: Organisations that meet the initial allocation criteria are eligible to receive an initial allocation of /32. For initial allocations up to /29 no additional documentation is necessary. Organisations may qualify for an initial allocation greater than /29 by submitting documentation that reasonably justifies the request. If so, the allocation size will be based on the number of existing users and the extent of the organisation's infrastructure. --snip-- And, of course, using up your /29 in one go means no additional adjacent reserved address space on the RIPE NCC books, but that's an implementation issue :) 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 21-10-11 12:44, "Emilio Madaio" <emadaio(a)ripe.net> wrote: > >Dear Colleagues, > >A new RIPE Policy Proposal has been made and is now available for >discussion. > >You can find the full proposal at: > > www.ripe.net/ripe/policies/proposals/2011-04 > >We encourage you to review this proposal and send your comments to ><address-policy-wg(a)ripe.net> before 18 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 2

Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by Sascha Lenz 24 Oct '11

24 Oct '11

Hi, > Dear Colleagues, > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > You can find the full proposal at: > > www.ripe.net/ripe/policies/proposals/2011-04 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 18 November 2011. Short: I support it. Long: well, i'm one of those guys who prefer to implement native IPv6 from scratch and skip all those crappy transition methods completely. It actually works im my world. ...but unfortunately(?) my world is huge corporate networks and rather small scale ISPs, haven't worked for a big ISPs for a decade now, so i guess there could be a case for 6rd somewhere else. It's a little awkward that the proposal mentions "small ISPs", because with small ISPs there shouldn't be a problem to implement native IPv6... Anyways, the reason why i do support the proposal is just getting the additional bits for proper subnetting, that actually is a little PITA if you're a "not-big-yet-but-not-so-little-anymore"-type ISP. Doing network design meant to last more than some years the right way is a little hard there with a /32 sometimes. So i would welcome /29s instead of /32s. I cannot always justify more than an initial /32 at the moment. If that also helps with 6RD deployments, and it certainly does, sure, good thing. I don't see any downside of that since even for the earlier Allocations this was reserved already. But we should be clear here: /29 should be the end of the road for "no documentation needed". -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect

1 0

2011-03 Proposal Accepted (Post-depletion IPv4 address recycling)
by Emilio Madaio 21 Oct '11

21 Oct '11

Dear Colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-528, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-03 The updated RIPE policy document is ripe-530 and is available at: http://www.ripe.net/ripe/docs/ripe-530 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by Emilio Madaio 21 Oct '11

21 Oct '11

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

1 0

2011-01 Proposal Accepted (Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA)
by Emilio Madaio 20 Oct '11

20 Oct '11

Dear Colleagues, Consensus has been reached, and the proposal described in 2011-01, "Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-01 The new RIPE document is ripe-529 and is available at: http://www.ripe.net/ripe/docs/ripe-529 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

2006-05 Proposal Accepted (PI Assignment Size)
by Emilio Madaio 20 Oct '11

20 Oct '11

Dear Colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-527, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-05 The updated RIPE document is ripe-528 and is available at: http://www.ripe.net/ripe/docs/ripe-528 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Items for the AP WG meeting agenda?
by Gert Doering 11 Oct '11

11 Oct '11

Hi APWG folks, RIPE 63 is nearing, and Sander and I are working on the agenda for the meeting. We have three time slots: Wednesday, 09:00-12:30, and Thursday, 09:00-10:30, so we have plenty of time to discuss things that *you* want to see discussed... So far the agenda has all the usual stuff (reporting on the PDP, discussion of open policy proposals), which will be published in the next days - we're still working on details, and waiting for some confirmations. If there is anything non-standard that you want to see, please let me or Sander know. 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

1 0

2008-08 Policy Proposal Withdrawn (Initial Certification Policy in the RIPE NCC Service Region)
by Emilio Madaio 03 Oct '11

03 Oct '11

Dear Colleagues, The proposal 2008-08, "Initial Certification Policy in the RIPE NCC Service Region", has been withdrawn. It is now archived and can be found at: http://www.ripe.net/ripe/policies/archived-policy-proposals Reason for withdrawal: after carefully following the discussion in the Concluding Phase of the Policy Development Process, the proposer is of the opinion that consensus on this proposal is not possible within the RIPE community. As a consequence, the proposer has decided to withdraw the proposal. Regards Emilio Madaio Policy Development Officer RIPE NCC

14 27

(Draft) minutes from APWG Meeting at RIPE 62
by Gert Doering 28 Sep '11

28 Sep '11

Hello Working Group, the draft minutes from the APWG sessions at the last RIPE meeting have now been published: http://www.ripe.net/ripe/groups/wg/ap/minutes/minutes-from-ripe-62 please let us know if there is anything that needs to be corrected or amended. Thanks to the RIPE NCC for their work on this, and apologies to the WG for the delay in publishing - that was all my doing, dragging my feet with the initial review. 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

1 0