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]/
[bcop] A question about RIPE-690
- Previous message (by thread): [bcop] A question about RIPE-690
- Next message (by thread): [bcop] A question about RIPE-690
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Thu Jun 23 13:13:31 CEST 2022
Hi Xuo, One /64 prefix per subscriber. Personally, I prefer (and did that way in many customers) option 4.1.4 (/64 prefix out of the IPv6 prefix assigned to the end-user), as per RFC6603. Regards, Jordi @jordipalet El 23/6/22, 13:09, "BCOP en nombre de Xuo Guoto" <bcop-bounces at ripe.net en nombre de xuoguoto at protonmail.com> escribió: Hello all, I have a question about RIPE-690. In section 4.1.1 it says: <quote> Using a /64 prefix from a dedicated pool of IPv6 prefixes is the most common scenario and currently the best practice. A separate block of IPv6 space is allocated for the WAN links to the end customer CPEs, so that when CPE connects to the network and performs router discovery, a /64 prefix is used to number both ends of the connection. </quote> My question is that: Is the /64 prefix common for all WAN links or a separate /64 prefix is to be allotted for each WAN link? It may be obvious, but from reading the docs its not clear for me. I understand that for PD it has to be a separate prefix for each customer CPE. Apologies if this is not the right forum for asking this question. X. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/bcop/attachments/20220623/20dca108/attachment.html>
- Previous message (by thread): [bcop] A question about RIPE-690
- Next message (by thread): [bcop] A question about RIPE-690
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]