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]/
[address-policy-wg] Re: Re: 200 customer requirements for IPv6
- Previous message (by thread): [address-policy-wg] Re: Re: Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Oppermann
oppermann at pipeline.ch
Fri Nov 18 18:37:25 CET 2005
Randy Bush wrote: > > >>> Who are you to decide who is too small to be allowed independence? > >> someone with routers which have to carry all those prefixes > > You mean the very small tier 1 club? All others can default and don't > > _have_ to carry all those prefixes. > > no, that's not what i mean and you know it. the number of t1s is > a very tiny percentage of those carrying full routing. you may > wish it otherwise. i may wish it otherwise. but until there is > solid technology to support better routing, that's life. get used > to it. > > > What's _your_ solution to this problem _now_ in IPv6? > > stop deployment, which is negligible anyway, and fix the technology. > and fixing is not applying endless half-assed hacks that don't > actually do the job. > > we're gonna live with this stuff for a very long time. it should > be very far more solid design than it is. if we're patching now, > what will be the kludge level 20 years from now? Here comes Andre's guide to fix IPv6(tm): 1. Make /32 the only routable entity so we can use perfect match in the DFZ instead of longest-prefix match. Perfect match scales better and is way more economically to implement in hard- and soft- ware. (MPLS is perfect match too.) Beyond /32 use longest-prefix up to /64. 32 bit in the DFZ give us 4 billion routable entities. See "Scalability issues in the Internet routing system" thread on NANOG, starting 18. October 2005. 2. Drop the Flow Label and Next Header fields from the IPv6 header. They are architectually broken and do not belong to this layer. Just encapsulate the packet in another layer like MPLS. Next Header is broken because it's just source routing again. Dead for a long time. Nobody in their right mind will allow header popping through their firewall/network. 3. Reinsert packet fragmentation into the IPv6 header. Path MTU discovery just ain't cutting it. 4. Drop 64 bits from the IPv6 address. The lower 64 bit are just pointless as host indentifier. Very poor overhead ratio. 6. Do away with those stupid ':' separators in IPv6 addresses. No, I'm not joking. It ain't to late yet to fix it. Details and variations can be discussed. ;-) -- Andre Oppermann oppermann at networx.ch - AS8271 andre at freebsd.org - TPC/IP Kernel Developer
- Previous message (by thread): [address-policy-wg] Re: Re: Re: 200 customer requirements for IPv6
- Next message (by thread): [address-policy-wg] 200 customer requirements for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]