Domain Name System Media Types
RFC 4027
Yes
(Ted Hardie)
No Objection
(Alex Zinin)
(Allison Mankin)
(Bill Fenner)
(Margaret Cullen)
(Russ Housley)
(Scott Hollenbeck)
(Steven Bellovin)
Note: This ballot was opened for revision 02 and is now closed.
Ted Hardie Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Allison Mankin Former IESG member
No Objection
No Objection
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
(2004-10-13)
Unknown
Comments from the OPS directorate by Rob Austein: summary: seems harmless relies on (and makes normative reference to) experimental rfc 2540, which specifies two date formats and manages to hnork both of them in trivial ways. the binary date format skips lightly over clock wrap, which, admittedly, won't happen until 2106, but rfc 2540 claims to be about archival formats. the text date format is obviously intended to interpreted in utc, that's never quite stated except via a cross reference to the binary format, which, strictly speaking, does not nail down whether the text format is utc or not. none of this is simon's fault, just a weakness of the rfc to which he's referring.
Harald Alvestrand Former IESG member
No Objection
No Objection
(2004-10-14)
Unknown
Reviewed by Mary Barnes, Gen-ART Her review: Draft is ready to publish as Informational with the correction of the following editorial nits. Nits: ----- - Needs updating to new template reflecting RFC 3668/3667. - Abstract: 1st sentence: "This document register..." should read "This document registers..." - Introduction: Last paragraph, same comment as abstract. - Section 2, security considerations: "This media type identify..." should read "This media type identifies..." - Section 2, security considerations, second sentence: "This data may be security relevant according to..." should likely read something like "This data may be secured according to ...." - Section 3, Encoding considerations: "Binary transports is..." should read "Binary transport is..." - Section 3, Security considerations: Same 2 comments as for Section 2 above.
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Steven Bellovin Former IESG member
No Objection
No Objection
()
Unknown
Thomas Narten Former IESG member
No Objection
No Objection
(2004-10-14)
Unknown
> This document register the media types application/dns and text/dns, s/register/registers/ > Applications which use this media type: DNS related software, > including software storing and using certificates stored in DNS. Not sure this is right. The certificate using software is presumably using DNS protocols, not extracting data out of zone file formats. > transfered in a line oriented mode. Text literals may contain CRLF s/line oriented/line-oriented/ > within the text. Binary transports is possible between systems that s/transports/transport/