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] IPv6 questions regarding ripe and address ranges
- Previous message (by thread): [ipv6-wg] IPv6 questions regarding ripe and address ranges
- Next message (by thread): [ipv6-wg] IPv6 questions regarding ripe and address ranges
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peeters, Ralph
ralph.peeters at oce.com
Tue Mar 17 11:37:03 CET 2009
>Yes, you are stuck in IPv4 ways. If you have an independent network with a unique routing policy >and you allocate IPv6 addresses to the customers who connect to your network, then you are clearly an ISP and should get a /32. >If you have some network infrastructure in another continent that does not randomly route traffic across the ocean and back, >then it has a unique routing policy, etc. The main change from our ipv4 to a ipv6 network will seem more in the range of: we currently use a private class a range with local internet connectivity by nat, which in ipv6 we want to get rid of. That's why I'm looking into multiple address blocks because of multihoming and local POP. >Why? A three /48 blocks take up just as much routing table space as three /32 blocks. >More importantly, if you the ISP only have a /48 then you cannot assign /48 blocks to customers which is bad, bad, bad. Well we are not a ISP. But as long as I can request a good address range per location by becoming a member I don't mind too much on the size of the block because (in all fairness) i don't think we will ever need more then a /48. But I'll leave those ipv4 ways behind me from now on and go with the flow. >The most important concept in IPv6 addressing that is different from >IPv4 addressing, is that the IPv6 address space is very, .... very, very, very, big. Point taken :) >The second most important concept is that the subnetting architecture is designed to waste large amounts of address space. >This "wasted" address space buys certain advantages. First, it means that most subnets can grow for a long time without running out of addresses. >Also, there is no global policy that requires a network operator to get all of their global addresses from a single RIR, >and there is also no global policy that requires them to get their addresses from each RIR in which they have network infrastructure. >Just do whatever works best for your network. That is what other network operators have done in the past. So to conclude: Ripe membership will (basically) give me a /32 per location no matter the number of users or location? Thanks, Ralph Peeters This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
- Previous message (by thread): [ipv6-wg] IPv6 questions regarding ripe and address ranges
- Next message (by thread): [ipv6-wg] IPv6 questions regarding ripe and address ranges
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]