nanog mailing list archives
Re: IPv6 Confusion
From: Randy Bush <randy () psg com>
Date: Fri, 20 Feb 2009 14:49:50 +0900
Do you really want to keep state for hundreds of end user devices in your equipment? In my mind, IPv6 more than ever requires the customer to have their own L3 device (which you delegate a /56 to with DHCPv6-PD). Imagine the size of your TCAM needed with antispoofing ACLs and adjacancies when the customer has 100 active IPv6 addresses (remember that IPv6 enabled devices often have multiple IPv6 addresses, my windows machine regularily grabs 3 for instance).
we do not have to imagine. c & j have both demonstrated the nat scaling problem when protyping for comcast. that is why the idea of a 'carrier grade' nat in the core has become man near-edge nats and ds-lite. it is sorely broken architecture. randy
Current thread:
- RE: IPv6 Confusion, (continued)
- RE: IPv6 Confusion Tony Hain (Feb 17)
- Re: IPv6 Confusion Randy Bush (Feb 17)
- RE: IPv6 Confusion Steven Lisson (Feb 17)
- Re: IPv6 Confusion Randy Bush (Feb 17)
- Re: IPv6 Confusion Brandon Galbraith (Feb 17)
- Re: IPv6 Confusion Randy Bush (Feb 17)
- RE: IPv6 Confusion Frank Bulk (Feb 19)
- Re: IPv6 Confusion Jack Bates (Feb 19)
- RE: IPv6 Confusion Frank Bulk (Feb 19)
- RE: IPv6 Confusion Mikael Abrahamsson (Feb 19)
- Re: IPv6 Confusion Randy Bush (Feb 19)
- Re: IPv6 Confusion Bob Snyder (Feb 19)
- Re: IPv6 Confusion Adrian Chadd (Feb 20)
- Re: IPv6 Confusion Nathan Ward (Feb 17)
- Re: IPv6 Confusion Brandon Galbraith (Feb 17)
- RE: IPv6 Confusion Steven Lisson (Feb 17)
- RE: IPv6 Confusion Skywing (Feb 17)
- Re: IPv6 Confusion Nathan Ward (Feb 17)
- RE: IPv6 Confusion TJ (Feb 18)
- Re: IPv6 Confusion Jack Bates (Feb 18)
- Re: IPv6 Confusion Nathan Ward (Feb 17)