On 30/07/2020 15:46, Joe Abley wrote:
On 30 Jul 2020, at 16:36, Paul Wouters <[email protected]> wrote:

Seems like .org needs to update an 18+ year old operation policy, and
just to clarify that has nothing to do with this draft as .org already
has this problem.

Again, I'm not a lawyer, but I think what we are doing is a consequence of the 
contract we have to operate the ORG registry. If that's right you are of course 
entirely at liberty to engage through the ICANN bottom-up policy-development 
process to advocate for individual contract changes for the 1,500 or so TLDs 
that are operated under essentially the same contract.

ICANN procedures and hence application process for new gTLDs have specific text/question to address the handling of "orphaned glue records" in the registry zonefile, in the sense that the operator needs to document what it does, which probably hints at the fact that there is no one size fits all solution here.

Question 28 of https://newgtlds.icann.org/en/applicants/agb/evaluation-questions-criteria-04jun12-en.pdf
is:

Abuse Prevention and Mitigation: Applicants should describe the proposed policies and procedures to minimize abusive registrations and other activities that have a negative impact on Internet users. A complete answer should include, but is not limited to:

[..]

Proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6);

</quote>


There is even a SSAC comment on this too.
[SAC048]: SSAC Comment on the Orphan Glue Records in the Draft Applicant Guidebook (12 May 2011)


https://www.icann.org/en/system/files/files/sac-048-en.pdf

Note specifically this part:

Orphaned glue can be used for abusive purposes; however, the dominant use of orphaned glue supports the correct and ordinary operation of the DNS. Thus it is inappropriate to include the management of orphaned glue under the rubric of "abuse prevention and mitigation" and we suggest that it be removed


--
Patrick Mevzek

_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to