Re: [ipv6-wg] Clear Guidance for Enterprises
Thanks every one for suggestions. I found one more resource which is more in tune with what I was looking for: https://blog.apnic.net/2023/04/04/ipv6-architecture-and-subnetting-guide-for-network-engineers-and-operators/ X. Sent with [Proton Mail](https://proton.me/) secure email. --- Original Message --- On Monday, July 31st, 2023 at 9:31 PM, Fearghas Mckay wrote: > On 31 Jul 2023 at 11:19:29, Sander Steffann wrote: > >> See if you can find a friendly local person in your local Network Operators >> Group (NOG) to help you a bit. NOGs are a great place for those looking to >> learn. And otherwise feel free to contact me off-list. I’ll happily get you >> started. > > UKNOF and NetLDN would be good places to start. > > https://uknof.uk/ > > https://netldn.uk/ > > f-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
Re: [ipv6-wg] Clear Guidance for Enterprises
Thanks for your input Michael. The vagueness of the problem description reflects my own confusion. We are not using IGP as of now, its a small NOC with a couple of devices. --- Original Message --- On Monday, July 31st, 2023 at 12:38 AM, Michael Richardson wrote: > Each router needs a /128 as a loopback address to use. > I assign them all from a single /64 for that purpose. Ok. > Many of your p2p ethernet links between sites/routers might not > need prefixes at all. This is not clear. > > 2. How will we be assigning static address to (DNS?) > > servers? > > > I don't understand the question. My question was that I have a /35 (say 2001:db8:2000::/35), and a router with three interfaces, one a p2p link with upstream, rest two interfaces are connected to two different segments as shown below: │ ┌─┴───┐ │ │ │ Router│ │ │ └┬───┬┘ A│ │ B ┌─┘ └───┐ │ │ ┌─┴───┐ ┌───┴──┐ │ CD │ E │ F│ ┌───┴┐ ┌──┴──┐ ┌──┴─┐ ┌──┴─┐ │ dns1 │ │ mail1 │ │ S1│ │S2 │ └┘ └─┘ └┘ └┘ In the diagram above what will be the ip address at points A to F? C-F are servers and need static ip address. > Otherwise a static allocation > from the /64 that the routers provide. Can you please elaborate this? Thanks for your patience and time. I hope the questions I am having will be shared by many and will be addressed in the guidelines when published! X. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
Re: [ipv6-wg] Clear Guidance for Enterprises
Hello all, Resurrecting an old thread to share some experience when trying to start deploying ipv6 on a small London based ISP. As a start we are deploying in a test location which is setup as a "site". We have a /29 allocated and that's been divided into /32 for each site. Which is again divided into /35 for various functions in the NOC including for servers (DNS, Speed Test etc), subscriber allocation (/64 and a /56 per subscriber), loopback address etc. There is sufficient guidelines and documentation to reach till this point. But from here on, it's pretty dark. Some of the question for which we have no clear guidelines are: 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 interface? 2. How will we be assigning static address to (DNS?) servers? 2.1 One IP from /35? 2.2 An IP from the /64 assigned to router interface? 2.3 An IP from a different /64 but from same /35? In the case of 2.3 will the routing work? 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. There are not much (atleast not to my google fu) resources addressing these nuts and bolts configuration information. I am writing this to share a from the trenches perspective to this discussion Thanks X. --- Original Message --- On Wednesday, June 14th, 2023 at 9:38 PM, Paolo Volpato via ipv6-wg wrote: > Hi Wilhelm, All, > > I have noticed that some people would be happy to cooperate to your idea of a > paper for IPv6 in enterprises (me included :-) > Wonder if you have thought of any rough plan to start and organize the work. > > Many thanks > Paolo -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
[ipv6-wg] SLAAC and Broadcast RA
Dear WG, Apologies if this mail is off topic here. I have a question about BCOP-690 wrt SLAAC BCOP-690 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 understanding of this recommendation is that in an ISP scenario, each RG will be assigned a seperate /64 prefix for CPE WAN. The ISP BRAS or BNG is also expected to send periodic multicast RA. My question is how a multicast RA can be sent to a VLAN, in which each RG is expected to have a different /64 prefix? R-43 of TR-177 says: The BNG MUST be configurable to send multicast RA messages that do not contain a Prefix Information Option (PIO), in order to advertise the default router address. R-44 says: The BNG SHOULD support sending periodic and solicited multicast RA messages having the unicast MAC address of the RG or of the hosts behind a bridged RG (see RFC 6085 [26]). Reading these two together, is it correct to say that BNG should be sending out periodic multicast RA without PIO, but RA with PIO should be sent only as a reply to an RS message from RG, with multicast IPv6 destination address but with unicast link-layer address of RG. Thanks and Regards, X.-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
