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/[email protected]/
[address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Previous message (by thread): AW: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): AW: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Thu May 6 13:54:53 CEST 2010
On Thu, May 6, 2010 at 11:51, Marcus.Gerdon <Marcus.Gerdon at 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
- Previous message (by thread): AW: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): AW: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]