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] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Previous message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu Oct 20 22:10:43 CEST 2016
Hello Sergey, > If I am not wrong, the main idea of the NCC is to switch to IPv6 > networks. But it strongly tries to stretch this process. You seem to misunderstand how this works. It is the community that sets these policies, not the NCC. The RIPE NCC implements what the internet community (us) wants it to do. The NCC definitely isn't stretching the process of getting IPv6 deployed, quite the opposite. > So I opposite this proposal. Noted. Cheers, Sander -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: </ripe/mail/archives/address-policy-wg/attachments/20161020/32bdcc09/attachment.sig>
- Previous message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
- Next message (by thread): [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]