This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
The naming of this article is a bit odd.
I think it should be named "6rd" (most commonly used) or possibly "IPv6 Rapid Deployment on IPv4 Infrastructures" --22.214.171.124 (talk) 13:11, 30 January 2010 (UTC)
The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
The result of the move request was: no move. DrKiernan (talk) 17:37, 24 February 2010 (UTC)
The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
This draft proposal only has 4 citations , so it's doubtful it needs a Wikipedia page at all. The book I found above indicated it's just a minor modification of 6to4, so a smerge/redirect may be more appropriate anyway. Pcapping 15:50, 23 February 2010 (UTC)
I imagine the it has not been cited much in academia as it has only been an informational RFC for a month, and the IETF standards process has not finished. But I do not see how this would not be notable, and I think the sources show that. If you just want to merge it with 6to4, please add a Merge template instead. --126.96.36.199 (talk) 22:56, 23 February 2010 (UTC)
Technically 6in4, 6to4 and 6rd all use the same packet format. The difference comes in how they are administered and addressed. I think each scheme is different enough to deserve it's own article but I could see it being argued either way. Plugwash (talk) 00:51, 18 January 2013 (UTC)
"Although these 64-bit prefixes are sufficient for sites that have only one LAN, as typical for residential and SoHo sites, it is not enough for large enterprise sites". WHAT? IPv4^2 is not enough? are you crazy? —Preceding unsigned comment added by 188.8.131.52 (talk) 20:06, 10 July 2010 (UTC)
No enterprise could work on a single flat LAN, no matter of how many computers could be numbered in that LAN. Actually I don't think you will ever see more than several hundreds hosts in a single LAN in practice, so much for your 64 bits :) Mro (talk) 09:07, 11 July 2010 (UTC)
Yes, but what prevents the owner of the xxxx:xxxx:xxxx prefix from subnetting? —Preceding unsigned comment added by 184.108.40.206 (talk) 05:21, 29 October 2010 (UTC)
Ipv6 stateless autoconfiguration requires a /64 allocated to each subnet and is the only IPv6 autoconfiguration system supported by windows XP. So if you have XP boxes on your network and don't want to have to configure them manually from the command line you need a /64 for every subnet. Plugwash (talk) 12:21, 2 November 2011 (UTC)