[dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the DNS PRIVate Exchange of the IETF. Title : Specification for DNS over TLS Authors : Zi Hu Liang Zhu

[dns-privacy] Last Call: (Specification for DNS over TLS) to Proposed Standard

The IESG has received a request from the DNS PRIVate Exchange WG (dprive) to consider the following document: - 'Specification for DNS over TLS' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive

Re: [dns-privacy] Spencer Dawkins' Yes on draft-ietf-dprive-edns0-padding-02: (with COMMENT)

Thanks for the quick and clear responses! So, and I emphasize "not a blocking comment", it sounds like this isn't an RFC 2119 requirement for interoperability, but just good advice? If so, this is more like "There is no specific requirement for the value of PADDING bytes, and receivers MUST

Re: [dns-privacy] Spencer Dawkins' Yes on draft-ietf-dprive-edns0-padding-02: (with COMMENT)

Shane's explanation on padding is a great summary of the mailing list discussion during the document review. tim (as DocumentShepherd) On 3/1/16 5:39 AM, Shane Kerr wrote: Spencer, At 2016-02-29 20:38:34 -0800 "Spencer Dawkins" wrote: Thanks for producing

Re: [dns-privacy] Spencer Dawkins' Yes on draft-ietf-dprive-edns0-padding-02: (with COMMENT)

Spencer, At 2016-02-29 20:38:34 -0800 "Spencer Dawkins" wrote: > Thanks for producing this draft. I do have one question about this text: > >The PADDING octets SHOULD be set to 0x00. Other values MAY be used; >for example, in cases where there is a

[dns-privacy] Benoit Claise's No Objection on draft-ietf-dprive-edns0-padding-02: (with COMMENT)

Benoit Claise has entered the following ballot position for draft-ietf-dprive-edns0-padding-02: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please