Re: OPENPGPKEY RRTYPE review - [IANA #773394]
Paul Wouters <[email protected]> Mon, 11 Aug 2014 11:01:34 -0400
| Newsgroups | gmane.ietf.dnsext |
|---|---|
| Message-ID | <[email protected]> |
On 08/10/2014 04:41 AM, Jay Daley wrote: > It would be helpful if the draft was updated to reflect the discussion on the list. I am unsure which discussion items you think should be added to the draft? - Comments about revoked keys? The draft does not specify anything but the openpgpk key format. Possibly this item could go into the openpgpkey-usage document, but would have no effect to the OPENPGPKEY record format. - combining _openpgpkey and _smimecert ? I do not think there is anything gained my merging the namespaces. It would just hinder opengpgp and smime clients/plug-ins in discarding irrelevant data. - comments about not using the APEX or justifying the _openpgpkey prefix? I don't think that belongs in the final document. - referencing 1035's "weak encoding of email address" and explaining why it is unusable. Can be added, although I think the draft already explains the problem when it states why it is using a sha2-224 hash. - small textual improvements suggested by Joe Abbley - Can be added to the next draft, but should that hold up this RRTYPE review? I don't think so. Did I miss anything in particular that you thought needed to be added? Paul _______________________________________________ dnsext mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsext