RFC 4159

Deprecation of "ip6.int"

📅 published August 2005, from ietf

RFC 4159: Deprecation of "ip6.int" 💖

Okay bestie, here's the tea. 🫖✨ This RFC is a Best Current Practice (that's BCP 109), written by G. Huston from APNIC, and it dropped in August 2005. 🎀 The title block doesn't list anything it obsoletes or updates. 💅

Status of This Memo 🦋

This document is a BCP for the Internet Community, and it's asking for discussion and suggestions for improvements. Distribution is unlimited, so share it with everyone. 🌸

Copyright (C) The Internet Society (2005). 🌈

Abstract ✨

So the main idea is that using ip6.int for Standards Conformant IPv6 implementations is being deprecated. 🙈

1. IPv6 Standards Action 👑

Okay, so back in August 2001 the IETF put out [RFC3152], and it said that ip6.int as the domain for reverse-mapping IPv6 addresses to DNS names was deprecated. 🕰️ It also said ip6.int would be phased out in an orderly fashion, which is very much a "we see you coming" moment. 💅

Now, as of 1 September 2005, the IETF is telling the community that the DNS domain ip6.int should no longer be used to do reverse mapping of IPv6 addresses to domain names. Instead, ip6.arpa should be used from here on out, following the IANA Considerations in [RFC3596]. 🧚 So ip6.int is deprecated, and it's discontinued in IPv6 implementations that conform to the IPv6 Internet Standards. Bye bye! 👋💜

The Regional Internet Registries (RIRs) are also being told that keeping up the delegation of entries in ip6.int is no longer required as part of infrastructure services that support Standards Conformant IPv6 implementations, starting 1 September 2005. 🫶 The RIRs are asked to work with their communities to agree on a schedule for ending registration services for the ip6.int domain. Teamwork makes the dream work! 🔥

2. IANA Considerations 🌷

IANA is told that the ip6.int domain for reverse mapping of IPv6 addresses to domain names is no longer part of Standards Conformant support of IPv6, as of 1 September 2005. 📋

3. Security Considerations 🔐

Okay, this part is serious, so listen up 🚨 While DNS spoofing of address-to-name mapping has been exploited in IPv4, removing the ip6.int zone from the standard IPv6 specification creates no new threats to the security of the internet. 🛡️ Phew, no new risk, iykyk. 😭

4. Acknowledgements 🫶

This document was put together with help from Kurt Lindqvist, Thomas Narten, Paul Wilson, David Kessens, Bob Hinden, Brian Haberman, and Bill Manning. 🎀 Shoutout to the whole squad! 💖

5. Normative References 📚

[RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152,
          August 2001.

[RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, "DNS
          Extensions to Support IP Version 6", RFC 3596, October
          2003.

Author's Address 🖊️

Geoff Huston
APNIC

EMail: gih@apnic.net

Copyright (C) The Internet Society (2005).

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 💀

Intellectual Property 🧠

The IETF takes no position on the validity or scope of any Intellectual Property Rights or other rights that might be claimed to apply to the implementation or use of the technology described in this document, or on whether any license under such rights might or might not be available. It also doesn't say it has made any independent effort to identify any such rights. 🤷‍♀️ Info on how rights work for RFC documents is in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat, and any assurances of licenses to be made available, or the result of an attempt to get a general license or permission for implementers or users of this specification, can be found in the IETF online IPR repository at http://www.ietf.org/ipr. 📂

The IETF invites any interested party to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that may cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org. 📬

Acknowledgement 💜

Funding for the RFC Editor function is currently provided by the Internet Society. 🌸✨

📦 where this page comes from