Technical Summary
The document marks as historic any "int" domain names that were
designated for infrastructure purposes, and identifies them for
removal from the "int" top-level domain. Any implementation that
involves these domains should be considered deprecated. This
document also marks RFC 1528 and RFC 1706 as historic, and updates
RFC 1591 by removing the documented use of "int" for international
databases.
Working Group Summary
This is an AD sponsored document; there is no WG.
However, the document is related to work in DNSOP, and the DNSOP WG was
notified / consulted:
https://mailarchive.ietf.org/arch/msg/dnsop/gL05qGuarfIEXHPIgp5VdmXA4AE/
The DNS-OARC (dns-operations) list was also informed / consulted:
https://lists.dns-oarc.net/pipermail/dns-operations/2021-October/021418.html
This document is a "cleanup" document documenting the current state of domains,
formerly used for infrastructure purposes, under the "int" TLD.
Document Quality
This document is a "cleanup" document documenting the current state of
domains, formerly used for infrastructure purposes, under the "int" TLD. It
is clear and understandable.
Personnel
Who is the Document Shepherd for this document?
- Tim Wicinski is the document shepherd
Responsible Area Director?
- Warren Kumari is RAD!!!!
(3) The Document Shepherd did a detailed review of the document
for content as well as simple editorial checks (spelling/grammar).
The shepherd feels the document is ready for publication.
(4) The Document Shepherd has no concerns on the depth or breadth
of the reviews.
(5) There is no need for broader review.
(6) There are no concerns from the document shepherd.
(7) No IPR disclosures
(8) There is no IPR
(9) While this is not a WG Document, it was brought up in DNSOP, and
the working group was in strong consensus supporting this document.
(10) There has been no appeals.
(11) All nits found have been addressed by the authors.
(12) No formal review needed
(13) All references have been identified as normative or informative.
(14) All normative references are in a clear state.
(15) There are no downward normative references
(16) This document will change existing RFCS:
Marking 1528 and 1706 as Historic
Updates 1591
Documents are listed in the Abstract and in the Introduction.
(17) The IANA considerations section is consistent with the document,
and it only describes moving removing .int domains.
(18) No new IANA registries
(19) N/A
(20) No Yang