From: Bob Harold [mailto:[email protected]] Sent: Thursday, August 18, 2016 6:56 PM To: Tirumaleswar Reddy (tireddy) <[email protected]> Cc: Warren Kumari <[email protected]>; [email protected]; [email protected]; [email protected] Subject: Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dnsodtls.
On Thu, Aug 18, 2016 at 1:14 AM, Tirumaleswar Reddy (tireddy) <[email protected]<mailto:[email protected]>> wrote: From: Bob Harold [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, August 17, 2016 9:13 PM To: Warren Kumari <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dnsodtls. On Tue, Aug 16, 2016 at 1:05 PM, Warren Kumari <[email protected]<mailto:[email protected]>> wrote: Dear DPRIVE WG, The authors of draft-ietf-dprive-dnsodtls have indicated that they believe that the document is ready, and have asked for Working Group Last Call. The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsodtls/ Please review this draft to see if you think it is ready for publication and send comments to the list, clearly stating your view. This WGLC ends Tue 30-Aug-2016. In addition, to satisfy RFC 6702 ("Promoting Compliance with Intellectual Property Rights (IPR)"): Are you personally aware of any IPR that applies to draft-ietf-dprive-dnsodtls? If so, has this IPR been disclosed in compliance with IETF IPR rules? (See RFCs 3979, 4879, 3669, and 5378 for more details.) Thanks, Warren Kumari Looks good to me. A couple grammatical concerns: Section "3.1. Session Initiation" The last sentance might sound better by adding "therefore" in the middle: "There are significant security issues in mixing protected and unprotected data, therefore UDP connections on a port designated by a given server for DNS-over- DTLS are reserved purely for encrypted communications." [TR] Updated in my local copy. Section "4. Performance Considerations" This sentence does not read well to me: "TLS False Start] which reduces round-trips by allowing the TLS second flight of messages (ChangeCipherSpec) to also contain the (encrypted) DNS query. " [TR] How about the following line ? TLS False Start [I-D.ietf-tls-falsestart] can reduce the round-trips in certain situations. [BH] That would work.. I was think just change "which reduces" to "can reduce": "TLS False Start] can reduce round-trips by allowing the TLS second flight of messages (ChangeCipherSpec) to also contain the (encrypted) DNS query. " [TR] Thanks, updated. -Tiru -Tiru -- Bob Harold
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
