Deprecating Infrastructure "int" Domains
draft-davies-int-historic-05

[Ballot comment]
Both subsections of Section 3 use the clause "no longer functions as described in the document".  Do those things still function some other way, or not at all?  The clause could be interpreted either way; if we mean the former, we should include a reference to the current description, if one exists.  Otherwise, I suggest something more definitive like "is no longer operational".

[Ballot comment]
# GEN AD review of draft-davies-int-historic-05

CC @larseggert

Thanks to Vijay Gurbani for the General Area Review Team (Gen-ART) review
(https://mailarchive.ietf.org/arch/msg/gen-art/Y9z9nvAs8du0ftVhmIVS5namsm4).

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Grammar/style

#### Section 3.1, paragraph 1
```
ANA shall coordinate the removal of any of the historical "int" domains disc
                                ^^^^^^^^^
```
Consider simply using "of" instead.

#### Section 5, paragraph 1
```
ation This document is the result of an comprehensive inventory conducted by
                                    ^^
```
Use "a" instead of "an" if the following word doesn't start with a vowel sound,
e.g. "a sentence", "a university".

#### Section 6, paragraph 1
```
ins are highly likely to be obsolete and this document is intended to formal
                                    ^^^^
```
Use a comma before "and" if it connects two independent clauses (unless they
are closely connected and short).

#### Section 6, paragraph 1
```
e that assessment. There are a small number of existing "int" domains nomina
                            ^^^^^^^^^^^^^^^^^
```
Specify a number, remove phrase, use "a few", or use "some".

#### Section 6, paragraph 1
```
se. While they would not qualify for a "int" domain under current criteria,
                                    ^
```
Use "an" instead of "a" if the following word starts with a vowel sound, e.g.
"an article", "an hour".

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool

[Ballot comment]
This document performs useful housekeeping work; no good deed goes unpunished, and so thanks to IANA (Kim Davis and Amanda Baber) for writing it and dealing with all of the process, etc.

Reminder to self: The related status change document (status-change-int-tlds-to-historic) was approved on  2022-12-15, and should be released at the same time as this document.

Note changed to '[ This IESG note to be removed before publication: The Status Change document (https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/) was approved, but the responsible AD (Warren Kumari) is holding it until *this* document is approved. This note is a (probably futile) attempt to remind him to release the status change when draft-davies-int-historic is approved. ]'

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-davies-int-historic-04. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

Upon approval of this document, IANA shall coordinate the removal of any of the historical "int" domains listed below which are still delegated in the "int" zone:

atma.int
ip4.int
ip6.int
nsap.int
rdi.int
reg.int
tpc.int

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

David Dong
IANA Services Specialist

The following Last Call announcement was sent out (ends 2022-11-23):

From: The IESG
To: IETF-Announce
CC: draft-davies-int-historic@ietf.org, tjw.ietf@gmail.com, warren@kumari.net
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Deprecating infrastructure "int" domains) to Informational RFC


The IESG has received a request from an individual submitter to consider the
following document: - 'Deprecating infrastructure "int" domains'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-11-23. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-davies-int-historic/

Please also see: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ (the associated "status change" document)

No IPR declarations have been submitted directly on this I-D.

Note changed to '[ This IESG note to be removed before publication: Please also see the Status Change document: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ - "Moving TCP.INT and NSAP.INT infrastructure domains to historic" ]'

Note changed to '[ This IESG note to be removed before publication: Please see the Status Change document: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ - "Moving TCP.INT and NSAP.INT infrastructure domains to historic" ]'

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-davies-int-historic-03. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

IANA will coordinate the removal of any of the historical "int" domains discussed in the approved document that are still delegated in the "int" zone.

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Michelle Thangtamsatid
IANA Services Specialist

The following Last Call announcement was sent out (ends 2022-04-26):

From: The IESG
To: IETF-Announce
CC: draft-davies-int-historic@ietf.org, tjw.ietf@gmail.com, warren@kumari.net
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Deprecating infrastructure "int" domains) to Informational RFC


The IESG has received a request from an individual submitter to consider the
following document: - 'Deprecating infrastructure "int" domains'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-04-26. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-davies-int-historic/



No IPR declarations have been submitted directly on this I-D.

Note changed to '[ This IESG note to be removed before publication - it is placed here to draw attention / link to the status-change doc. ]
Please see the Status Change document: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ - "Moving TCP.INT and NSAP.INT infrastructure domains to historic"'

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

Note changed to 'Please see the Status Change document: https://datatracker.ietf.org/doc/status-change-int-tlds-to-historic/ - "Moving TCP.INT and NSAP.INT infrastructure domains to historic"

[ This IESG note to be removed before publication - it is placed here to draw attention / link to the status-change doc. ]'