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]/
[ipv6-wg] Clear Guidance for Enterprises
- Previous message (by thread): [ipv6-wg] Clear Guidance for Enterprises
- Next message (by thread): [ipv6-wg] Clear Guidance for Enterprises
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Richardson
mcr+ietf at sandelman.ca
Sun Jul 30 21:08:32 CEST 2023
Xuo Guoto via ipv6-wg <ipv6-wg at ripe.net> wrote: > 1. How will we assign address to routers? Like will we should be > assigning 2001:db8:2000::1/35 or 2001:db8:2000::1/64 for router No. Each router needs a /128 as a loopback address to use. I assign them all from a single /64 for that purpose. The /128s go into the your IGP. Many of your p2p ethernet links between sites/routers might not need prefixes at all. > interface? 2. How will we be assigning static address to (DNS?) > servers? I don't understand the question. > 2.1 One IP from /35? 2.2 An IP from the /64 assigned to No. Why would you be throwing /35s around? If your DNS servers participate in IGP, then a /128 on a loopback interface, assuming they have multiple interfaces works. Otherwise a static allocation from the /64 that the routers provide. > We have three interfaces in the router with one facing upstream and is > using a /127 assigned by the up stream provider, of the other two one > iface is for servers and another for BNGs. How are ipv6 address > allocated in these interfaces. Statically? -- Michael Richardson <mcr+IETF at sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 658 bytes Desc: not available URL: </ripe/mail/archives/ipv6-wg/attachments/20230730/8ae5dcac/attachment.sig>
- Previous message (by thread): [ipv6-wg] Clear Guidance for Enterprises
- Next message (by thread): [ipv6-wg] Clear Guidance for Enterprises
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]