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] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Previous message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Scholten
mark at streamservice.nl
Wed May 5 00:39:02 CEST 2010
> -----Original Message----- > From: address-policy-wg-admin at ripe.net [mailto:address-policy-wg- > admin at ripe.net] On Behalf Of Gert Doering > Sent: Tuesday, May 04, 2010 9:50 PM > To: Mark Scholten > Cc: 'Gert Doering'; 'Richard Hartmann'; 'Carsten Schiefner'; address- > policy-wg at ripe.net > Subject: Re: [address-policy-wg] Discrepancy Between RIPE Policies on > IPv4 and IPv6 Provider Independent (PI) Address Space > > Hi, > > On Tue, May 04, 2010 at 06:52:41PM +0200, Mark Scholten wrote: > > The current options we have to implement IPv6 prevent us from > > implementing it. There are multiple problems we see currently: > > - We probably won't get PI IPv6 space > > Where do you see the hurdle? See my point below (co location for customers). > > > - With IPv6 we would like to offer a client (collocation) at least a > > /112 (with PI this isn't allowed if I'm correctly informed) > > This is the "datacenter" / "hosting shop" case I mentioned, and this > definitely needs clarification what the community views as useful here. > > (Note that you can't do this with IPv4 PI either, giving customers in > your colocation space a, say, /29 from your IPv4 PI range) With IPv4 customers "accept"/"understand" that IP space is limited and giving 1 IP/server is accepted by the customers we have, with IPv6 a few of our clients won't accept it. They will probably at least require/use 20 IP addresses (so they don't need to run services on "strange" ports). > > > - PA IPv6 address space is currently not available for us (this also > > prevents us to implement IPv6) > > You *could* become a LIR... which would make IPv6 PA space available > very easily. Becoming a LIR would also mean doing the paperwork that comes with it and we now have another organization doing that for us (and we don't really have the time for it to do it). > > > We also know some networks (with AS number) that currently use IPv4 > PI > > and don't are a LIR (and don't use IPv4 PA). They also need a > solution > > for the mentioned problems before they could implement IPv6. > > I'm not sure I understand why they wouldn't be able to use IPv6 PI...? Some of them have also co location clients that now have 1 IP (acceptable under current IPv4 PI rules) that will require multiple IPv6 addresses. Regards, Mark > > Gert Doering > -- APWG chair > -- > Total number of prefixes smaller than registry allocations: 150584 > > 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] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]