HTTP/2 302 date: Mon, 14 Jul 2025 18:17:44 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-rfc3041.txt cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT vary: Accept-Encoding server: cloudflare cf-ray: 95f304c35e04dfa6-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 18:17:45 GMT content-type: text/plain etag: W/"aa0f81989e1a4fd9a1e9dca9de79d204" vary: Accept-Encoding server: cloudflare cf-ray: 95f304c38ba1cf00-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 Implementation Report for RFC 3041 (IPv6 Privacy Addresses) ------------------------------------------------------------------------ 1. Implementation Name: Windows OS 2. Submitter Name: Dave Thaler 3. Submitter E-mail: dthaler@microsoft.com 4. Code Origin: Microsoft 5. Features Implemented: Section 3.2: the method described in 3.2.2 is implemented (there is no stable storage of a history value). Section 3.3: implemented as described. In addition the maximum number of DAD attempts is configurable, defaulting to 5 as required by the RFC. A new randomized interface identifier is generated for each prefix. (The same identifier is not used for multiple addresses.) Section 3.4: implemented as described, including REGEN_ADVANCE. The optional optimization of early removal of unused deprecated addresses is not implemented. Section 3.5: implemented as described, with all values configurable, with defaults as specified in Section 5. Section 4: Use of RFC 3041 is enabled by default on clients (Windows XP), and disabled by default on servers (Windows Server 2003), but configurable on both. No DNS records are registered for temporary addresses. Section 5: implemented as described. 6. Tested Interoperability by Feature: A. Lifetime Management (Section 3.4): Peers cannot detect any differences in messaging/processing from non-RFC 3041 addresses. B. DAD Operation (Section 3.3): The node using RFC 3041 addresses performs DAD for those addresses normally, and peers cannot detect any differences in messaging/processing Implementation Report for RFC 3041 (IPv6 Privacy Addresses) ------------------------------------------------------------------------ 1. Implementation Name: FreeBSD 2. Submitter Name: JINMEI, Tatuya 3. Submitter E-mail: core@kame.net 4. Code Origin: by ourselves from the scratch 5. Features Implemented: A. Lifetime Management (Section 3.4) B. DAD Operation (Section 3.3) 6. Tested Interoperability by Feature: A. Lifetime Management (Section 3.4) Verified proper Lifetime Management behavior with Router Advertisements generated by Cisco and Juniper IPv6 routers. B. DAD Operation (Section 3.3) Verified the creation of a temporary address (which is to be unique on the link) and the performance of DAD on that address without disrupting other implementations. This was tested with various implementations from different origins including Linux and Solaris 10.