AW: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Richard,
A /64 in IPv6 is what a single address is for IPv4.
I don't agree on this when talking about connecting servers. Place a server in a segment and assign it's interface an IPv4 address 192.168.0.1/24 and an IPv6 address FC00::1/64. Will you (be able to) address another server in the same segment using addresses within those prefixes? Can you get that server connected in IPv4 deploying 192.168.0.0/32 onto its interface? The relevant part here what I meant by 'single address' is the number of addresses configured onto those customers server. Indepent of doing v4 oder v6 you'll configured 'a single address' at the server to get it connected. I agree with you when talking i.e. about DSL lines. Instead of the typical /32 assigned for IPv4 you'll put a /64 on the line. But that's another topic talking about lines instead of servers. As said this were quickly noted items that came to my mind. For the last case of a /64 segment dedicated to one customer I'm not sure but might agree with you that as this would be the equivalent to the DSL line's example. As long as you don't route another /64 (or whatever size) onto customer equipment addressed in this segment. But it's definitely hard to tell where to draw the line. regards, Marcus ----------------------------------------------------------------------------------------- Engineering IP Services Versatel West GmbH Unterste-Wilms-Strasse 29 D-44143 Dortmund Fon: +49-(0)231-399-4486 | Fax: +49-(0)231-399-4491 marcus.gerdon@versatel.de | www.versatel.de Sitz der Gesellschaft: Dortmund | Registergericht: Dortmund HRB 21738 Geschäftsführer: Dr. Hai Cheng, Joachim Bellinghoven ----------------------------------------------------------------------------------------- AS8881 / AS8638 / AS13270 / AS29610 | MG3031-RIPE -----------------------------------------------------------------------------------------
-----Ursprüngliche Nachricht----- Von: Richard Hartmann [mailto:richih.mailinglist@gmail.com] Gesendet: Donnerstag, 6. Mai 2010 10:50 An: Marcus.Gerdon Cc: address-policy-wg@ripe.net Betreff: Re: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
On Thu, May 6, 2010 at 08:42, Marcus.Gerdon <Marcus.Gerdon@versatel.de> wrote:
- single address for connecting a customers server => PI - contained /64 (!) segment (i.e. dedicated vlan for a customers rack) => I think somewhat of a border case, but tend to *no* PI
A /64 in IPv6 is what a single address is for IPv4. This is obviously a _very_ reduced view for the sake of my argument, but I think doing this is valid, in this case.
Richard
On Thu, May 6, 2010 at 11:51, Marcus.Gerdon <Marcus.Gerdon@versatel.de> wrote:
I don't agree on this when talking about connecting servers.
As I said, I reduced the example extremely for the sake of argument. While there are many valid reasons why a single machine could have more than one IP (virtualization, SSL, etc) with both IPv4 and IPv6, IPv6 certainly makes using up IPs easier as there are so many. The be explicit: A customer with a single server who is assigned a /32 with IPv4 would and should still receive a full /64 with IPv6. Even when he really only needs one address, now or ever. This would not be allowed with PI space with the scheme you propose. I am not sure if it _should_ be allowed with PI space in the first place, but if it is, a full /64, not a /128, should be assigned. Richard
* Marcus Gerdon:
Richard,
A /64 in IPv6 is what a single address is for IPv4.
I don't agree on this when talking about connecting servers.
But it's arguably true if you want to separate those servers at the IP layer. Then you have to use separate subnets, and the IETF says that subnets have to be /64s (or larger). Some implementations even enforce that.
A /64 in IPv6 is what a single address is for IPv4.
I don't agree on this when talking about connecting servers.
What is a server? It is not unusual to see a 1U rackmount device called a "server" in hosting data centres. These server things have 4 CPU chips each with 4 cores, and 64G of RAM. Each of the 16 cores can run at least 3 average virtual machines giving you 48 vms in the device, and it is common enough to see people running as many as 7 or 8 VMs per core so you could easily have 112 VMs. In addition to the 112 virtual servers, each needing a /128 for every one of their virtual network interfaces, it is common to find people implementing virtual networks with virtual routers and switches, including a virtual DMZ/firewall setup. Clearly it is not unusual to find a so-called server device that actually does require more than a /64 allocation in order to remain aligned with IPv6 architecture and not start subnetting /64 blocks. --Michael Dillon
participants (4)
-
Florian Weimer
-
Marcus.Gerdon
-
michael.dillon@bt.com
-
Richard Hartmann