| reply to brad
Re: IPv6 beta I think there was some suggestion in one of the RFCs that residential customers should get a /56 and commercial accounts should get a /48. Or some sort of industry defacto type standard. Anyway, that seems to be how it's shaking out.
Technically, you don't need a /64 on the WAN side, either. I've brought up my TekSavvy link using the /64 for my LAN, and using the link-local addresses for the WAN gateway. Works fine. Just means that if you want to remotely log into your router, you're technically going through the WAN to the LAN to log in. I think the /64 on the WAN side is really just an artifact of IPv4 thinking. But they're cheap, and if it makes people feel more comfortable about the deployment, then it's worthwhile. |
|
Reviews:
 ·linode
1 edit | said by Mersault:I think there was some suggestion in one of the RFCs that residential customers should get a /56 and commercial accounts should get a /48. Or some sort of industry defacto type standard. Anyway, that seems to be how it's shaking out.
That's RFC6177. It clearly states something that simultaneously proves and disproves my point:
This document moves away from the previous recommendation that a single default assignment size (e.g., a /48) makes sense for all end sites in the general case. End sites come in different shapes and sizes, and a one-size-fits-all approach is not necessary or appropriate. The rest of the RFC seems to suggest that, although it's not one-size-fits-all, it should be between (& not including) /64 and /48. So there's nothing wrong here, I guess. Personally, I don't see the need for anything as big as a /56, but I guess some people will have a use for it.
I guess what I'm still wondering is why there are two separate subnets, and why there can't just be one /56 or one /64 (or one /whatever) (things my CCNA didn't teach me). |
|
| said by squircle:I guess what I'm still wondering is why there are two separate subnets, and why there can't just be one /56 or one /64 (or one /whatever) (things my CCNA didn't teach me).
I think it probably just has to do with the way the PPPoE service works with TekSavvy. I recall configuring a PPPoE daemon, and basically you assign an address to an endpoint (in the IPv6 world, this is a /64), and then you would separately assign any routes that you wanted to route in addition. Hence in the IPv4 world you get a static IP, and then a completely different /29, if you order them from TekSavvy. Same general deal with IPv6 (this is conjecture, but it's what I suspect). |
|
|
|
| reply to squircle
Also, check out this news from Google. |
|
brad
join:2007-09-06
Etobicoke, ON | »www.worldipv6launch.org/
Google properties, Facebook, the remaining Microsoft properties, Yahoo, Cisco to name a few. Akamai, Limelight and a few other CDNs going full v6 production was/is a blocker for thousands of other sites going v6. This will help to push IPv6 much further along having so many large sites with AAAA records and no whitelisting games or special URLs.
IMO this should be a challenge for TSI to be much further along by June 6th. Have full production v6 for both ON/QC and AB/BC DSL customers by then. There is no shortage of CPE gear from D-Link/Netgear/Linksys and some other vendors as well as third-party firmware options to allow for v6 over DSL. |
|
brad
join:2007-09-06
Etobicoke, ON | reply to squircle
said by squircle:Personally, I don't see the need for anything as big as a /56, but I guess some people will have a use for it.
A /60 for consumer connections which allows for up to 16 /64's would be a good default, maybe allow for an opt-in for a /56. Business connections are good with a /56 by default and opt-in for a /48. |
|
