Re: OPENPGPKEY RRTYPE review - [IANA #773394]

Jay Daley <[email protected]> Tue, 12 Aug 2014 08:20:34 +1200
Newsgroups gmane.ietf.dnsext
Message-ID <[email protected]>
On 12/08/2014, at 3:01 am, Paul Wouters <[email protected]> wrote:

> 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.

I do.  Some good reasons were presented on the list and having those in the document provides a significantly better reference than list archives.  Currently there is no explanation at all given of the prefix.

> - 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.

That would be useful too.

> - 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.

I don't buy the "none of this is important enough to hold up the process" argument - I see no explanation of an urgent need that overrides doing a quality job.

Jay

> 
> 
> Did I miss anything in particular that you thought needed to be added?
> 
> Paul
> 


-- 
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley

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