This mailing list interface will be retired once we upgrade our mailing list system. Click here to use the new RIPE NCC Forum.
Best Current Operational Practices (BCOP) Task Force
Threaded
Collapse
[bcop] A question about RIPE-690
Hello all, I have a question about RIPE-690. In section 4.1.1 it says: 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. 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.
Hi. A separate one for each customer. Allocate the /64 and use whatever you’d like (/64, /126, /127, etc.) Luis On Thu, 23 Jun 2022 at 08:08 Xuo Guoto <xuoguoto _at_ protonmail _dot_ com> wrote: > Hello all, > > I have a question about RIPE-690. In section 4.1.1 it says: > > > 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. > > > 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://lists.ripe.net/mailman/listinfo/bcop >
Thanks Jordi and Luis for the clarification. X. Sent with Proton Mail secure email. ------- Original Message ------- On Thursday, June 23rd, 2022 at 7:44 PM, Luis Balbinot <luis _at_ luisbalbinot _dot_ com> wrote: > Hi. > > A separate one for each customer. Allocate the /64 and use whatever you’d like (/64, /126, /127, etc.) > > Luis > > On Thu, 23 Jun 2022 at 08:08 Xuo Guoto <xuoguoto _at_ protonmail _dot_ com> wrote: > > > Hello all, > > > > I have a question about RIPE-690. In section 4.1.1 it says: > > > > > > 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. > > > > > > 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://lists.ripe.net/mailman/listinfo/bcop