On 5 Oct 2015, at 9:32, Jakob Schlyter wrote:

The document goes well beyond describing the files, and this is where it fails. Further, the files are not the only way that the trust anchor is published, so the document is fairly incomplete.

Trust anchors may be published in other ways, but IMHO that is out of scope for this document.

But that is the scope given in both the title and the abstract of the document.

If it is not up for discussion, then the document should not be progressed in the IETF at all. Instead, the description of the ICANN's publication methodology should be published by ICANN.

The file formats are not up for discussion, as existing implementations depend on them. The description on how to interpret the contents are of course up for discussion. I'm just saying we need to be careful what we change, if we choose to change things that's been in production for over 5 years.

Fully agree. That is why this should not be an IETF document, and instead it should be written and published by the organization that is responsible for the formats and publication methods.

--Paul Hoffman

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to