On Sat, Jul 2, 2011 at 8:10 PM, Keith Moore <moore@xxxxxxxxxxxxxxxxxxxx> wrote: > On Jul 2, 2011, at 3:21 PM, Cameron Byrne wrote: > > I saw the same thing. It is a shame that work that directly removes barriers > to REAL ipv6 deployment gets shouted down by a few people not involved in > REAL ipv6 deployment > > I find myself wondering what you mean by REAL IPv6. For me, REAL IPv6 is > code that uses the IPv6 programming model, 128 bit addresses, end-to-end > transparency, no NATs. 6to4 certainly qualifies. That's not what it means to me. REAL IPv6 is a replacement for IPv4 and can address greater than 100s of billions of endpoint and is suitable for very large traffic loads. As an access network provider, i need content on native IPv6. It does not make sense to anyone in my organization or industry to deploy IPv6 unilaterally. There is no benefit in this approach vs just doing NAT444. If there is IPv6 content on a meaningful scale ( by the numbers that means for "my network": Google, Facebook, Yahoo and their CDNs ...), then i have a solid business case for IPv6 access networks. Full Stop. If the content guys say 6to4 is a pain, and they do, then i need to help them find a way to solve that pain. I operate in an address exhausted world, so NAT44 is my only IPv4 tool for growth. In the meantime, i null route the 6to4 anycast address because it creates half open state in my CGN. Been doing that for at least 5 years. My next step is filtering AAAA over IPv4 access because 6to4 client brokeness won't die on its own, that will be rolled out in a few months. Operating a network means making the tweeks that keep the wheels rolling, and we don't find many technology purist in my line of work. Other access providers like 6to4 so much that they want to NAT it. This is the reason why historic is the proper term. http://tools.ietf.org/html/draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-02 I look forward to that discussion on ietf@ Cameron > Keith > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf