4 ms·
"IPv6 uses NPT, where you can transform one prefix into another prefix." What? No, NPT is a nonstandard experimental hack that's in no way part of IPv6 or supp
by fulafel 6y ago
"IPv6 uses NPT, where you can transform one prefix into another prefix."
What? No, NPT is a nonstandard experimental hack that's in no way part of IPv6 or supported by any standards track IETF protocols.
"IPv6 was a draft in 1997(!), and became a real Internet Standard in 2017"
The draft part of the claim is false, the basic IPv6 RFCs came out of draft and were published as standards track RFCs in 1995 eg https://tools.ietf.org/html/rfc1883 https://tools.ietf.org/html/rfc1883 / https://tools.ietf.org/html/rfc1884 https://tools.ietf.org/html/rfc1884 and then subsequent revisions in 1998 and 2017.
- djhaskin987 6y agoRFC = "Request For Comment", not actual standard. It's just when RFCs are published, generally people start immediately implementing them as if they were.
- fulafel 6y agoThe RFC publication series is where all kinds of IETF documents are published, standards or not. Having a RFC number doesn't mean that a document is or isn't standards track. IOW all IETF standards are RFCs, but not all RFCs are standards or proposed standards. The "request for comments" title of the series does remind us of the collegial and unbureucratic roots of the IETF, vowing to reject kings, presidents and voting & believing in rough consensus plus running code etc :) however in the standards track case there is no rfc number assigned to the doc in the draft phase, it's instead published in the separate internet-drafts directory by the working group and goes through all kinds of process and iteration before getting published as a proposed standard RFC. See eg https://en.wikipedia.org/wiki/Internet_Standard https://en.wikipedia.org/wiki/Internet_Standard