On Wed, Feb 25, 2015 at 12:15 PM, Rose, Scott W. <[email protected]> wrote:
>
> On Feb 23, 2015, at 12:31 PM, Warren Kumari <[email protected]> wrote:
>
>> [ Meta top post ]
>>
>> I'd like to also draw attention to the "companion" document
>> draft-ietf-dane-openpgpkey-usage (
>> http://datatracker.ietf.org/doc/draft-ietf-dane-openpgpkey-usage/ ),
>> which describes usage of openpgpkey records, and following CNAMES.
>>
>
> Is this also in WGLC?  Either way, some comments:

It is NOT currently in WGLC -- but the comments are appreciated.

Would the WG like to WGLC this at the same time? Olafur and I has a
discussion about this - he figured it should be included, I thought
better to hold off - I'm happy to start a WGLC if folk want that.

W

>
> - In section 1 (Intro), there is an incorrect XML tag (xref)
>
> - In Section 3.3 Final paragraph about wildcards:  ...at other locations 
> (e.g. hugh@*.com) or regular expressions in keu uids are not allowed, adn any 
> OPENPGPKEY RR containing these should be ignored."
>
> Should that be a SHOULD above?  It discusses implementation behavior in 
> addition to what is already described in Sections 4.3 & 4.4.
>
> - In Section 3.4 spelling s/Resoruce/Resource and s/accomodate/accommodate
>
> - In Section 4. s/twart/thwart
>
> At least I assume that last one - my spell checker gets confused about UK vs. 
> US english.
>
> Scott
>
> ===================================
> Scott Rose
> NIST
> [email protected]
> +1 301-975-8439
> Google Voice: +1 571-249-3671
> http://www.dnsops.gov/
> https://www.had-pilot.com/
> ===================================
>
> _______________________________________________
> dane mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dane



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf

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

Reply via email to