| Do they also plan $5 per ip as well Do they also plan $5 per ip as well?
If the tv side can make a lot by renting hardware whats stopping the internet side doing the same with outlet type fees. just replace outlet with a ip. |
|
Reviews:
 ·Comcast
| said by Joe12345678:Do they also plan $5 per ip as well? If the tv side can make a lot by renting hardware whats stopping the internet side doing the same with outlet type fees. just replace outlet with a ip. No.
What will likely happen is that the router will use a form of NAT (such as the RADVD daemon already used in third-party router firmware today) to partition addresses out of a customer-specific /64 (which is exactly how tunnelbrokers, such as Hurricane Electric and SixxS, operate today). It's not rocket science; nor does it require reinventing the wheel.
Here are the three pieces required to deploy IPv6 on any sort of ISP-wide scale:
1. Support at the client. (For PCs/Macs, this is pretty much a non-issue; Windows XP and newer, OS X from 10.4 up, and any recent distribution of Linux, Solaris/OpenSolaris, or a BSD, supports IPv6 today. The problem is non-computer MIDs and game consoles, which will require firmware updates or upgrades; the older hardware may need to be replaced.)
2. Support in the ISP's hardware. (This is where the rubber meets the road for any ISP, let alone one the size of Comcast. For IPv6 to be useful, every device that requires an IP address *must* support IPv6, or gracefully degrade to IPv4 in a transparent manner. The issue for Comcast is the older hardware that doesn't gracefully degrade; that hardware will have to go.)
3. Support in the middleware. Most of that glue framework already supports IPv6 (the IP-address problem is an old one for Comcast; it didn't sneak up on them). IPv6 can actually solve several rather thorny issues that Comcast faces from an equipment and system-management POV. Further, IPv6 neatly sidesteps the issue of network neutrality (the protocol itself includes QoS functionality; further, DNS is extremely decentralized, which makes programs like Sandvine utterly useless). |
|
Reviews:
 ·VOIPo
 ·Windstream
·BroadVoice
| said by PGHammer:2. Support in the ISP's hardware. (This is where the rubber meets the road for any ISP, let alone one the size of Comcast. For IPv6 to be useful, every device that requires an IP address *must* support IPv6, or gracefully degrade to IPv4 in a transparent manner. The issue for Comcast is the older hardware that doesn't gracefully degrade; that hardware will have to go.) What are you talking about with "gracefully degrade to IPv4"?
Hardware either supports IPv6 or it doesn't, or doesn't need to (switches, layer 2 bridges and such)
Any hardware routing layer 3 traffic will need to be IPv6 aware
Any Hardware only routing layer2 traffic will not care about IPv6
said by PGHammer:3. Support in the middleware. Most of that glue framework already supports IPv6 (the IP-address problem is an old one for Comcast; it didn't sneak up on them). IPv6 can actually solve several rather thorny issues that Comcast faces from an equipment and system-management POV. Further, IPv6 neatly sidesteps the issue of network neutrality (the protocol itself includes QoS functionality; further, DNS is extremely decentralized, which makes programs like Sandvine utterly useless). IPv6 doesn't sidestep Net neutrality, it can still be slowed down/sped up with the same type of hardware used before just it will now be ipv6 aware.
Although the RST Packet isuess may (not really looked in to this) be negated due to ipsec being included in IPv6 (again i said may).
--
ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k |
|
AVonGaussPremium
join:2007-11-01
Boynton Beach, FL | reply to PGHammer
said by PGHammer:What will likely happen is that the router will use a form of NAT (such as the RADVD daemon already used in third-party router firmware today) to partition addresses out of a customer-specific /64 (which is exactly how tunnelbrokers, such as Hurricane Electric and SixxS, operate today). It's not rocket science; nor does it require reinventing the wheel. RADVD is an advertising daemon, it is not nor related to any form of NAT. While a few IPv6 NAT concepts have been created, I have not heard of anyone seriously discussing bringing NAT to the world of IPv6. There really is no good reason to do so. |
|
Reviews:
·Comcast
| reply to Napsterbater
I was referring specifically to layer-3 devices (such as STBs, CMTS equipment, etc.)
RADVD (in routers supporting IPv6 tunnel endpoints) allows a router to distribute IPv6 addresses from an assigned /48. The number of possible IPv6 addresses supported by a single /48, however, FAR exceeds the physical capacity of any router (home or commercial) shipping today; therefore, traditional NAT is un-needed with IPv6. (The reason why I called RA a type of network-address translation is due to the IP-assignment parameters it uses, especially how, with the modern version of RA in router firmware, it automatically assigns an IPv6 address to the router itself, and without user intervention.) |
|
|
|
AVonGaussPremium
join:2007-11-01
Boynton Beach, FL | RADVD does not distribute or assign IPv6 address, it is merely an announcement daemon and is not tied to a /48 prefix - most commonly used prefix would probably be a /64.
»en.wikipedia.org/wiki/Radvd |
|
| reply to PGHammer
But you have to tell it what subnet is in use, it cant be auto assinged.
Again you will ethier have a static subnet or no router on your end and just be using a switch.
Unless they come up with something new. |
|
Reviews:
·Comcast
| It's not auto-assigned because tunnels don't use DHCPv6 (if DHCPv6 were used, you wouldn't need RADVD, as you don't need RADVD with DHCPv4 today). RADVD and subnetting is used as an alternative to DHCPv6 for tunnels because IPv4 (not IPv6) is still the default for most of the Internet. |
|
