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/ipv6-wg@ripe.net/
[ipv6-wg] RIPE Policy vs IETF RFC
- Previous message (by thread): [ipv6-wg] RIPE Policy vs IETF RFC
- Next message (by thread): [ipv6-wg] RIPE Policy vs IETF RFC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Ponzone
david.ponzone at ipeva.fr
Mon Jun 13 12:11:20 CEST 2016
> Le 13 juin 2016 à 11:58, Roger Jørgensen <rogerj at gmail.com> a écrit : > > I would say, please don't mix implementation with actual usage. I can > run 100 000 x /128 internal while only have 2 x /48 external. > +1 Even if I don’t see a reason at the moment to assign a /128 to a customer, there could be one in the future, so I don’t think RIPE should try to enforce any policy as it doesn’t have any negative impact on the Internet. This is valid as long as the IPv6 address space stays aggregated, and that the maximum prefix length allowed in the global routing table is /48 (or else, as it seems there is no unanimity on this). Perhaps there should be a formal recommendation/policy about the maximum prefix length any AS should accept. David Ponzone Direction Technique email: david.ponzone at ipeva.fr <mailto:david.ponzone at ipeva.fr> tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr <blocked::http://www.ipeva.fr/> - www.ipeva-studio.com <blocked::http://www.ipeva-studio.com/> Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20160613/377dbd3b/attachment.html>
- Previous message (by thread): [ipv6-wg] RIPE Policy vs IETF RFC
- Next message (by thread): [ipv6-wg] RIPE Policy vs IETF RFC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]