 jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | [IPv6] Deployment of IPv6 Begins I am happy to announce that we’ve achieved another critical milestone in our transition to IPv6 – we’ve started the pilot market deployment of IPv6 to customers in selected markets! The first area is Pleasanton, CA. We will soon cover all of our earlier IPv6 trial areas as well.
This first phase will support certain types of directly connected CPE, where a single computer is connected directly to a cable modem. This will depend upon the cable modem (a subset of DOCSIS 3.0 cable modems, which will expand over time) and will also depend upon the operating system (only Windows 7, Windows Vista, Mac OS X 10.7 / Lion), which must support stateful DHCPv6.
While this may seem like a small step, our approach is to progressively widen our deployment over time. Later phases will support home gateway devices (Apple, D-Link, Netgear, etc.). For directly connected CPE, we will allocate an individual IPv6 address (/128), since we know that only a single device is connecting, with no additional need to subnet.
The cable devices that will initially support IPv6 are listed at »mydeviceinfo.comcast.net/?s=i&so···sc=84and are shown with a checkmark in the IPv6 column (click the top of the column to sort by that variable). This list will expand in the coming weeks and months as we complete testing of other devices.
It is also important to note that we are deploying native dual stack, which means a customer gets both IPv6 and IPv4 addresses. That means we are not using tunneling technology or large scale Network Address Translation (NAT). In contrast to tunneling and large scale NAT, native dual stack avoids breaking or slowing applications and maintains a better and faster broadband Internet experience.
For more information, check out these two blog posts at »blog.comcast.com/2011/11/ipv6-de···ent.html and »blog.comcast.com/2011/11/ipv6-de···ogy.html, and keep an eye on our IPv6 Information Center at »www.comcast6.net.
--
JL
Comcast |
|
 somms
join:2003-07-28
Salt Lake City, UT | According to the official supported deveice link, I would have to now downgrade my Motorola SB6121 to the older/obsolete SB6120 in order to participate! |
|
jus10
join:2009-08-04
Sterling, VA Reviews:
 ·Comcast
| reply to jlivingood
Is there anyway to get a list of "earlier IPv6" trial areas?
I take it there is also a difference between "will support" and "works". While the DS3 modem would seem to be needed (have that), there are plenty of things which support DHCPv6 which aren't on that list. My DHCPv6-foo is rather weak. I would assume it still gives out a /64 which in turn could be advertised via ravd to the rest of my lan (thus they all get v6 address)? Or does DHCPv6 authoritatively control everything in the /64 and thus I'd only have 1 ipv6 address? That would be a regression over what I presently have where all of my lan is on ipv6. However I don't think I'm in a trial area so I guess I have some time. |
|
jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | reply to somms
said by somms:According to the official supported deveice link, I would have to now downgrade my Motorola SB6121 to the older/obsolete SB6120 in order to participate!
As I noted above, "This list will expand in the coming weeks and months as we complete testing of other devices."
So no need to downgrade.  We'll add more devices soon.
--
JL
Comcast |
|
jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | reply to jus10
said by jus10:Is there anyway to get a list of "earlier IPv6" trial areas? Yes, you can browse through older posts @ »www.comcast6.net. We have mentioned previously San Francisco, CA, Philadelphia, PA, Miramar, FL, Chicago, IL, and Denver, CO. We are, however, admittedly vague on where in each of those areas, for operational reasons.
That being said - it never hurts to contact your local market to tell them you really want IPv6. 
said by jus10:I take it there is also a difference between "will support" and "works". While the DS3 modem would seem to be needed (have that), there are plenty of things which support DHCPv6 which aren't on that list. Yes, there sure is. First, we have found that many devices that say they support IPv6 don't work the way they should. So we do a bunch of testing to ensure everything works as expected before we enable a device. As you might imagine, we have quite a queue of devices to test. Our next phase is home gateway devices.
--
JL
Comcast |
|
somms
join:2003-07-28
Salt Lake City, UT | reply to jlivingood
said by jlivingood:said by somms:According to the official supported deveice link, I would have to now downgrade my Motorola SB6121 to the older/obsolete SB6120 in order to participate!
As I noted above, "This list will expand in the coming weeks and months as we complete testing of other devices." So no need to downgrade. We'll add more devices soon. Thanks for confirming SB6121 IPv6 support will be included eventually...already have a E4200 IPv6 ready wireless router parked behind my SB6121 whenever Comcast decides to throw the switch! |
|
jus10
join:2009-08-04
Sterling, VA Reviews:
·Comcast
| reply to jlivingood
Understandable. I don't think my Airport Extreme is listed as supporting DHCPv6 at all so I won't be a guinea pig this time around.
I'll see if I can pester my local market into rolling out ipv6. I'm in the greater DC area but I'm not sure if I'm really in that "market". If DC were Philly, I live in the equivalent of Berks County.
Progress is exciting! |
|
|
|
jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | said by jus10:Understandable. I don't think my Airport Extreme is listed as supporting DHCPv6 at all so I won't be a guinea pig this time around. The Apple Airport Extreme is actually pretty good - we have used it in our IPv6 trials. It can receive IPv6 on the WAN interface, like a /64, which is what you will want. (As noted - a subsequent phase later this year.)
said by jus10:I'll see if I can pester my local market into rolling out ipv6. I'm in the greater DC area but I'm not sure if I'm really in that "market". If DC were Philly, I live in the equivalent of Berks County. Hey now - careful! I'm from Berks County originally. But, yeah, I know what you mean.
--
JL
Comcast |
|
 ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to jlivingood
Since the thread from Steve got whacked, I will post my comment from there, here:
Still no love for business customers and the SMC's and not on the IPv6 list. |
|
jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | said by ropeguru:Still no love for business customers and the SMC's and not on the IPv6 list. One surefire way to express your desire for IPv6 on Business Class is to contact their sales team and express your interest...
JL
--
JL
Comcast |
|
WB3FFV
join:2001-12-11
Abingdon, MD | Well be it good, or bad, I have many times mentioned to the Business side, that I wanted IPv6, and I can't speak for the rest of the country, but at least here in the Baltimore, MD area, they are clooless, and don't even know what I am talking about.
I guess on the bright side, I am running native dual stack in a datacenter, so just made my own tunnel, so I now have dual-stack running here at home over my Comcast service. Still it would be far nicer if I didn't have to loop through my datacenter to have it.. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to jlivingood
said by jlivingood:said by ropeguru:Still no love for business customers and the SMC's and not on the IPv6 list. One surefire way to express your desire for IPv6 on Business Class is to contact their sales team and express your interest... JL Good thought. If my rep is not as clueless as others have posted about theirs, I will use this as a little leverage. My 2 year contract is up next month and I need to decide what I am going to do. |
|
csnyder
join:2007-09-10
Grand Rapids, MI | reply to jlivingood
Jason,
Thanks for all of your work on this effort, especially for your efforts to be so accessible to the community; my two-years-ago-self would be astonished to hear me say this, but I'm happy to be a Comcast customer (at least for Internet service - no comment on TV or phone).
I'm hoping that you'll switch on IPv6 in my market (Grand Rapids, MI) soon. We just got D3 recently, so I'm not sure how that factors in to our timetable. In the meantime, I'll replace my five-year-old modem at home and start pestering the workplace CS reps about upgrading my office to a D3 gateway. |
|
 DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | reply to jus10
said by jus10:Understandable. I don't think my Airport Extreme is listed as supporting DHCPv6 at all so I won't be a guinea pig this time around.
Progress is exciting!
Why would you want to USE DHCP with IPv6?
use a proper /64 on all network segments |
|
 whfsdudePremium
join:2003-04-05
Washington, DC
 ·T-Mobile US
| said by DarkLogix 
Why would you want to USE DHCP with IPv6?
use a proper /64 on all network segments
2. Push prefix information to the client if there is a routed assignment.
3. IPAM management. SLAAC is great for small networks but you might want to integrate your addressing management into whatever software you are using for IPv4. Think of issues such as support where a support agent can retrieve both IPv4 and IPv6 addresses or routed addresses for a client. |
|
 jjmb
join:2009-12-01
USA | reply to DarkLogix
We mentioned the use of the dual band Airport Extremes as part of our trials some time ago. It works quite well! It supports stateful DHCPv6 on the WAN interface and SLAAC only the LAN side, which is perfectly acceptable. Of course this assumes no shorter than a /64 IPv6 prefix length on the LAN side of the router.
FWIW - DHCPv6 does have it usefulness and value.
John |
|
| reply to jlivingood
ok so what about the areas who have yet to see the trials? Are those areas just going to switch completely over overnight or is it too going to be a long transitional period? Also nice to see you again J. |
|
jus10
join:2009-08-04
Sterling, VA Reviews:
·Comcast
| reply to jjmb
Ah cool. So as I understand it, whenever Comcast moves to the next phase and starts rolling out /64s, I can set the AEBS to state-fully request the /64 and then it can statelessly give out addresses on the LAN. That's actually about perfect .
I have no problems with DHCPv6. I think there was some confusion on my earlier posts. As I understand it, you guys are using DHCPv6 so it doesn't matter if I do or not. The part I was confused on was whether DHCPv6 was state-full the whole way down (that is it issues v6 to hosts inside of my lan; behind the router) or if the router acted as a middle-man and just SLAAC'ed out the /64. I'm guessing from how you described the AEBS it works like the latter. |
|
Reviews:
·Comcast
2 edits | reply to somms
said by somms:According to the official supported deveice link, I would have to now downgrade my Motorola SB6121 to the older/obsolete SB6120 in order to participate!
I got one of each and they really use the same firmware so I think the lack of a checkmark is a simple formality and nothing to worry about. Plus I got the same E4200 router, Just be sure to update the firmware to 1.0.03 since it includes native IPv6 support |
|
Reviews:
·Comcast
1 edit | reply to jlivingood
said by jlivingood:That being said - it never hurts to contact your local market to tell them you really want IPv6. Explain to me how we "contact our local market" since there is no phone number we can call to our service centers, the call centers don't know jack squat (and frankly don't care) about IPv6 or how to get in touch with the engineers to give the message, and calling corporate doesn't really get anyone anywhere unless your dealing with ComcastSteve. Aren't you the one who's in charge of all of this and makes the decisions as to wherer to go next? |
|
