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

Re: [address-policy-wg] Status of 2011-02 Policy Proposal Removal of multihomed requirement for IPv6)?
by Albert Siersema 09 Nov '11

09 Nov '11

Geza, > I do see it differently. PI address space is easy to use, however, this > allocation mechanism does not scale. Therefore was invented CIDR and PA > allocation, if you do remember... Could you eleborate on "does not scale" ? When deploying IPv6 one should set aside an IPv4 mindset. The same goes for the whole rehashing of the "does not scale" issue. You can't expect early 90's routing hardware to do the job of current BGP Internet routing. And when everyone will be running IPv6 (not tomorrow), the current limits for hardware won't apply. Let's not go into a discussion on asics / 64-core cpu's, but I'm pretty certain that hardware including tcams etc will keep up if the market demands it. Maybe you're referring to something altogether different, that's why I ask. I fully concur with Thomas on this point: for all the IPv4 PI allocations out there it should be possible to get an IPv6 allocation as well. Indeed nothing has changed with regard to the reasons for applying and being granted PI space. The current policy kind of suggests that everyone with IPv4 PI space should just quit their business and hand it over to the LIR as they are the only ones getting PI space for customer traffic. Regards, Albert > Turchanyi Geza schrieb am 07.11.2011 10:02: > nothing stops th IPv4 PI owners to use IPv6 PA.... > > > Nothing stops anybody of using PA, neither in IPv4 nor in v6. That's not > the question. > > But any reasons, why somebody wants/needs IPv4 PI space will usually fully > apply to IPv6 also. It would seem stupid to me, to have IPv4 ("the past") > as PI but IPv6 ("the future") as PA. That won't make sense. What changed > between my v4 PI application and my v6 PI application? If I won't need PI > on v6 any more, I probably won't need it on v4 any longer. > > Siple question: do I need my machines to have provider independend IP > addresses or not? If yes, then I need *ANY* address (IPv4, IPv6, > IPvSomething) to be PI and not PA. > > So, if somebody already has IPv4 PI space, he/she should more or less > automatically receive v6 PI under the same conditions as for v4. He/she > just has to reason, why some default /48 won't be enough. Thats my opinion. > > regards, > Thomas

7 8

Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by Anfinsen, Ragnar 09 Nov '11

09 Nov '11

Late, but anyway. We support this proposal. MVH/Regards Ragnar > -----Opprinnelig melding----- > Fra: address-policy-wg-bounces(a)ripe.net [mailto:address-policy-wg- > bounces(a)ripe.net] På vegne av Emilio Madaio > Sendt: 21. oktober 2011 12:45 > Til: policy-announce(a)ripe.net > Kopi: address-policy-wg(a)ripe.net > Emne: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the > Minimum Size for IPv6 Initial Allocation) > > > 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 >

4 4

6rd as technology that might have an impact to HD ratio
by Jan Zorz ＠ go6.si 05 Nov '11

05 Nov '11

Hi, During last week the question was risen "what do we do, if we get /29, assign /30 for 6rd, use /30 for native part of deployment, then we fill it up and need additional allocation? Is 6RD /30 assignment valid as a whole in HD ratio game?" Well, my thoughts on this are: 1. If you filled up the whole /30, then you should probably not be running 6RD anymore, get rid of it and use that space for native 2. If you filled up /30 and can't get rid of 6RD, evaluate again you addressing plan sanity :) 3. If nothing of the above does apply, you are probably so big you should get more than /29 as initial allocation anyway 4. What else can possibly go wrong? So, 6RD should not be treated as anything special, as it is not a part of modified text in the policy, therefore if you are running 6RD, you still need to show the number of sites that you are covering with IPv6 PD and this has really nothing to do with 2011-04 proposal (but I can see new HD ratio discussion in the horizon :) ) I was specifically asked to put this question forward on this mailinglist in order to provide some further guidance for IPRAs, if 2011-04 reaches consensus (hope so :) ) Cheers, Jan

2 1

Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by boggits 05 Nov '11

05 Nov '11

On 21 October 2011 11:44, Emilio Madaio <emadaio(a)ripe.net> wrote: > www.ripe.net/ripe/policies/proposals/2011-04 Okay, I can see the logic, but please can we not do this :) I'm all for allowing a policy that says LIR can request a /29 rather than a /32 and that deploying 6rd is a valid reason for allocating a /29 as an initial block but can we do this by having the LIR send the documentation in and having it reviewed for logic. J -- James Blessing 07989 039 476

15 41

Re: [address-policy-wg] 2011-04 New Policy Proposal (Extension of the Minimum Size for IPv6 Initial Allocation)
by Daniel Holme 02 Nov '11

02 Nov '11

On 21 October 2011 12:44, Emilio Madaio <emadaio(a)ripe.net> wrote: > 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. Hi On the premises that there are no protocol specific comments in the policy then I support this proposal too. This should be a matter of address assignment policy only. Based on a mixture of /56 and /48 assignments to users it's easily possible for a medium to large ISP to need more than a /32. Also, increasing allocation sizes can only do good things for the IPv6 DFZ. -- Daniel Holme

1 0

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Sascha Luck 02 Nov '11

02 Nov '11

On Tue, Oct 25, 2011 at 11:51:26AM +0200, Emilio Madaio wrote: > > http://www.ripe.net/ripe/policies/proposals/2011-05 > I, too, support this proposal (Disclosure: We operate an IXP) Kind Regards, Sascha Luck

1 0

2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Kjetil Otter Olsen 02 Nov '11

02 Nov '11

We (Norwegian Internet eXchange) support this proposal. Best regards, Kjetil Otter Olsen, NIX.no

1 0

concept document: IPv6 PA/PI unification
by Gert Doering 01 Nov '11

01 Nov '11

Hi AP WG, next week at the RIPE meeting (and by remote participation, of course) I want to continue discussing an idea that came up before, and that I brought up at RIPE 62 already - doing away with the distinction between IPv6 PA and IPv6 PI space, going for a "unified number distribution policy" (to give credits, it's not exactly my original idea, but has been brought up a couple of times by members of the community in the last years). Feedback from RIPE 62 was mostly positive, with "we need to think about many details", so Sander and I sat down and tried to write a concept document that has some answers about the details - which needs to be discussed, refined, and eventually formed into a full-featured policy proposal to go through the PDP. So far, this is to start the thought process, and to get your ideas about it - especially ideas of the sort "this is not going to work *because* <detail we've overlooked>". But I'm taking "we want to keep the difference between PA and PI!" as well - but if you say so, please explain where you see the benefit of "more complicated rules". The discussion will take place on Thursday morning, in the 09:00-10:30 time slot. thanks for helping shape policy, Gert Doering -- APWG chair --------------------------------------------------------------- Motivation: why? ---------------- - PA and PI are just different labels for "IPv6 addresses" ... but with different strings attached: - PI must not be used for 3rd party assignments (problem for hosting providers) - only single PA allocation for LIRs possible, even if multiple independent networks exist - network structure and operation is very different these days than at the time where the PA/PI distinction was made. The boundaries between networks, different operators and different services are not as clear as they used to be... - the classic distinction "PA is for ISPs and their access customers" "PI is for enterprises that do not do ISP-like business" has been overcome by reality, and there are no longer clear borders between "ISP", "enterprise" and "end-customer" networks - Network addresses are for *numbering network devices*. Limiting what someone is allowed to do with certain addresses creates confusion. Constantly having to tweak policy to work around this is the wrong solution. Goals and Caveats ----------------- - encourage IPv6 deployment - be flexible enough to accommodate both typical and non-typical network- and business models - do not encourage assignment of /64 or single addresses to end users - do not encourage excessive routing table growth - encourage proper documentation and discourage lying to the RIPE NCC to wiggle around policy restrictions The Proposal ------------ - abandon distinction between PA (allocation) and PI (assignment) - everything is just "numbers" - RIPE NCC hands out "block(s) of numbers" to "users of numbers" - see below for answers on the fine print... Who get's address space? ------------------------ - existing model is kept: LIRs as distribution point for address space - either to "the LIR organization" - classic model: "LIR is part of the Internet Provider business" - or via the LIR to "the entity that wants to use the space and take responsibility for it" (sponsoring LIR), keeping the contractual requirements of 2007-01 - "Direct Assignment Users" members could still be possible, but "every NCC member is an LIR" would simplify things further (see "Costs" section) Amount of space per "block of numbers"? --------------------------------------- - /48 (or larger with justification) by default - /32.../29 (or larger with justification) allowed when planning to assign to 3rd parties - multiple "blocks of numbers" to or via a single LIR allowed and expected to be a frequently seen usage case Allocation from well-known ranges for anything that people might want to treat specially in their routing policy (former "special case" and PI policies): - IXP - Root DNS - Anycast DNS - /33.../48 blocks Cost? ----- - determined by AGM, but we can discuss models here and provide recommendations to AGM and NCC board, e.g.: * base cost per year per LIR * yearly recurring cost "per block of numbers", independent of size(!), reflecting the cost of handling the address space request, documentation, RIPE database, etc., which increase if you need "many blocks" Multiple blocks per LIR? ------------------------ - since there would no longer be any difference between PA and PI, "more than one block going to a single LIR" would be a typical case - so it needs to be permitted - "get any number of blocks that people are asking for" is not likely to get consensus due to pressure on the routing system - proposal for compromise: ``one "block of numbers" per "network"'' - needs workable definition for "network": - interconnected network - operated by the same entity - operated as a layer 3 network - be flexible in allowing multiple blocks, but don't *require* anyone to actually ask for multiple number blocks if they are happy with using the same address block for multiple networks/sites/... - problem cases to keep in mind, leading to this definition - ISPs providing L3 services on top of other ISPs' Layer 2 infrastructure - single LIRs providing addresses to two independent Layer 3 networks that are not directly connected - e.g. due to political (commercial/NREN), legal or geographical reasons - "classical PI" type connections - end users with independent numbers - Multiple L3 providers providing address space to a single user must be allowed (multi-homing, special-purpose networks, etc.) -- 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

4 7

Re: [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Daniel Holme 01 Nov '11

01 Nov '11

On 25 October 2011 11:51, Emilio Madaio <emadaio(a)ripe.net> 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. > http://www.ripe.net/ripe/policies/proposals/2011-05 Hi I support this proposal. -- Daniel Holme Kcom

1 0

2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
by Rolf Schärer 01 Nov '11

01 Nov '11

+1 I support the proposal Cheers, Rolf ------------------------------------------------------------------------------- netspring gmbh rolf schärer, ccie #17218 alte gasse 4 rolf.schaerer(a)netspring.ch 8610 uster, switzerland Tel: +41 44 500 79 70

1 0