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]/
AW: [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 ]
Marcus.Gerdon
Marcus.Gerdon at versatel.de
Thu May 6 11:51:13 CEST 2010
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 at 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 at gmail.com] > Gesendet: Donnerstag, 6. Mai 2010 10:50 > An: Marcus.Gerdon > Cc: address-policy-wg at 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 at 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 >
- 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 ]