On Jun 9, 2011, at 11:24 AM, Keith Moore wrote: > > [...] But when the support people for a fairly well-established telco haven't even heard of IPv6, it's hard to believe that it's going to be available anytime soon. I have another anecdote to relate. When I contacted the support staff at the moderately sized regional ISP I use at home, to ask about whether they might move to providing native IPv6 service instead of their subscribers-only IPv6-in-IPv4 tunnel service, the support person was knowledgeable about IPv6, but unhelpful. I explained who I am, and what I do at Apple, and tried very hard without disclosing Apple Confidential information to explain that it's not just a hobby for me... I need *native* IPv6 into my home in San Francisco for my day job, and that I want to stay with my current provider rather than move to one of its competitors, which I named, and which I know to be rolling out native IPv6 service in my area in the immediate future. I hoped that might jog something loose. I'm quite willing and able to help them conduct a native IPv6 trial. The support person said, "Let me pass along your information to our chief of network operations." A couple days later, I heard back from the support person. "We have no plans to offer native IPv6." Meanwhile, 6to4 works fine on their network so long as remote IPv6 destinations have a working return path route to 2002::/16, i.e. they are complying with I-D.ietf-v6ops-6to4-advisory now. -- james woodyatt <jhw@xxxxxxxxx> member of technical staff, core os networking _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf