
From nobody Sun Jan  3 06:25:23 2016
Return-Path: <warren@kumari.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947551ACD42 for <dns-privacy@ietfa.amsl.com>; Sun,  3 Jan 2016 06:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CID0-JaandE2 for <dns-privacy@ietfa.amsl.com>; Sun,  3 Jan 2016 06:25:20 -0800 (PST)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17D0B1ACD39 for <dns-privacy@ietf.org>; Sun,  3 Jan 2016 06:25:20 -0800 (PST)
Received: by mail-yk0-x22b.google.com with SMTP id k129so204443525yke.0 for <dns-privacy@ietf.org>; Sun, 03 Jan 2016 06:25:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=UkguHQWc3E4Q5M/heN2kOA1J7Vgcor2mD5pHvTKjHSY=; b=g+Lo79QOzBcywAf5DGB08FgCEH5NfjMNLAVg6dhqO6n5JWGZlVRbkEYqUq4e2qU7I5 9v25WL7YdSEmrItg0FPnb6Oc5BzJ8IgVpGVb01E4iktbDFSXF7FP3tFstIDcHLaxPkly GemhT6+e4Pi/5Yw9VCVj5uNXTCPSnKN/0cfnK1qbFGeyxMp/i4ztLxMMKMSIr9WWd3ri TAROwfh4RL05GCP93LqRoEE4EnDkDR1MZ56wiQD8SWcIXOgaBuF9Q9sTCRfSLlUbd2d3 rBfDIaUnAl5dQ3jEY4efy/4wdWNf9fSuRSDVFad8wfQz9KVQNuRtuOzUY+tF+jfQlBWb BhqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=UkguHQWc3E4Q5M/heN2kOA1J7Vgcor2mD5pHvTKjHSY=; b=c4jx21Zn4biQAgVf6shpE6Ed+26SVpSmydlxCiVget5K3me80TPvzcvqX4kJYHtknn WetcKnl5Gr7NVoU+gp2rPivrRk7KHa68Y9EEJC95YWhV0xb5Gue20RdDyw8G2X1fqG4f gbb7MFXaeD45DACiZXnT7LrCEbodXjBElOBRm4MQLxIQ4M5L6rUUnRiAEK1qU2JbgsoU +vRh1FmJJhki1pX0FaeVBuCA0ihkwQlLRqgRSIhwfJxHWFi0r22/bIePb29UFpKe9dUc 9zPy4pb1tBRQsKXS6Abs7mXvyawhMesYoOHZDtZixJIjwEHOW575qn5P7KCuwSeMePOQ eL0g==
X-Gm-Message-State: ALoCoQm0KotO4ZWDgqVh7M6t3YtJ3MSeO908ID+NC8IgECPvvmu74EfbKAk2VQRsZeuzSTjITEVS3tCZE8sjCdSwTBoSw9DPFETPv90gDqwnEMr1qIN/mmE=
X-Received: by 10.129.70.8 with SMTP id t8mr17043494ywa.105.1451831119360; Sun, 03 Jan 2016 06:25:19 -0800 (PST)
MIME-Version: 1.0
References: <CAHw9_iK1d15Fyj02cwezcW4v-PU4993k2UpmH0bVVxwTf+13Tg@mail.gmail.com>
In-Reply-To: <CAHw9_iK1d15Fyj02cwezcW4v-PU4993k2UpmH0bVVxwTf+13Tg@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Sun, 03 Jan 2016 14:25:09 +0000
Message-ID: <CAHw9_i+DRZ2yNdCVMJ1z38w+j+W1QzUVQRSHFgrYax4umzzWxA@mail.gmail.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Type: multipart/alternative; boundary=001a114d71a824e9fd05286ec63a
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/QiCoD55CoUy1gyohaf0WNIjTXwo>
Subject: Re: [dns-privacy] 2nd WGLC for draft-ietf-dprive-dns-over-tls-02.
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2016 14:25:21 -0000

--001a114d71a824e9fd05286ec63a
Content-Type: text/plain; charset=UTF-8

Hi all,

The WGLC for this concluded a while back, and Tim and I had a chance to
chat about it, and discuss with the authors.

We believe that there is consensus for publication - the authors will be
posting a new version with some (modified) text from Christian, and then we
can ship this.

I hope that everyone had a good vacation / new years break[0] and will have
soon have time to review and discuss
draft-dgr-dprive-dtls-and-tls-profiles-00.

W
[0]: Even if you don't celebrate anything around this time, the decrease in
IETF related mail from those that do makes a nice surprise...


On Wed, Dec 9, 2015 at 4:16 PM Warren Kumari <warren@kumari.net> wrote:

> Dear DPRIVE WG,
>
> Pippin: But what about WGLC?
> Aragorn: You've already had it.
> Pippin: We've had one, yes. But what about second WGLC?
>           (with apologies to JRR Tolkien / Peter Jackson)
>
>
> This is a compressed WGLC for draft-ietf-dprive-dns-over-tls.
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/
>
> The authors have addressed some changes requested during the first WGLC
> (please see Allison's mail here for details:
> https://mailarchive.ietf.org/arch/msg/dns-privacy/orjGksDRsCXV5m8vvfj0Tmdn1uM )
> and the changes are large enough that we feel a second WLGC is in order.
>
> We will primarily be looking at the changes, diff available here:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dns-over-tls-02
>
> This WGLC ends Monday 21-Dec-2015.
>
>
> Thanks,
> Warren Kumari
> (as DPRIVE WG co-chair)
>

--001a114d71a824e9fd05286ec63a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>The WGLC for this concluded a w=
hile back, and Tim and I had a chance to chat about it, and discuss with th=
e authors.=C2=A0</div><div><br></div><div>We believe that there is consensu=
s for publication - the authors will be posting a new version with some (mo=
dified) text from Christian, and then we can ship this.</div><div><br></div=
><div>I hope that everyone had a good vacation / new years break[0] and wil=
l have soon have time to review and discuss draft-dgr-dprive-dtls-and-tls-p=
rofiles-00.</div><div><br></div><div>W</div><div>[0]: Even if you don&#39;t=
 celebrate anything around this time, the decrease in IETF related mail fro=
m those that do makes a nice surprise...</div><div>=C2=A0<br></div><div><br=
></div><div>On Wed, Dec 9, 2015 at 4:16 PM Warren Kumari &lt;<a href=3D"mai=
lto:warren@kumari.net">warren@kumari.net</a>&gt; wrote:<br></div><div><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>=
Dear DPRIVE WG,<br></div><div><br></div><div><div>Pippin: But what about WG=
LC?</div><div>Aragorn: You&#39;ve already had it.</div><div>Pippin: We&#39;=
ve had one, yes. But what about second WGLC?</div></div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 (with apologies to JRR Tolkien / Peter Jackson)</div><=
div><br></div><div><br></div><div>This is a compressed WGLC for draft-ietf-=
dprive-dns-over-tls.</div><div>The draft is available here: <a href=3D"http=
s://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/" target=3D"_bl=
ank">https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/</a></=
div><div><br></div><div>The authors have addressed some changes requested d=
uring the first WGLC (please see Allison&#39;s mail here for details:=C2=A0=
<a href=3D"https://mailarchive.ietf.org/arch/msg/dns-privacy/orjGksDRsCXV5m=
8vvfj0Tmdn1uM" target=3D"_blank">https://mailarchive.ietf.org/arch/msg/dns-=
privacy/orjGksDRsCXV5m8vvfj0Tmdn1uM</a>=C2=A0) and the changes are large en=
ough that we feel a second WLGC is in order.</div><div><br></div><div>We wi=
ll primarily be looking at the changes, diff available here:=C2=A0<a href=
=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dprive-dns-over-tls-02" =
target=3D"_blank">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dprive-dns=
-over-tls-02</a></div><div><br></div><div>This WGLC ends Monday 21-Dec-2015=
.</div><div><br></div><div><br></div><div>Thanks,</div><div>Warren Kumari</=
div><div>(as DPRIVE WG co-chair)</div></div></blockquote></div></div></div>

--001a114d71a824e9fd05286ec63a--


From nobody Mon Jan  4 01:34:17 2016
Return-Path: <sara@sinodun.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB1D1A702A for <dns-privacy@ietfa.amsl.com>; Mon,  4 Jan 2016 01:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M0EG02rTWXZQ for <dns-privacy@ietfa.amsl.com>; Mon,  4 Jan 2016 01:34:14 -0800 (PST)
Received: from shcp01.hosting.zen.net.uk (shcp01.hosting.zen.net.uk [88.98.24.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05DB1A702B for <dns-privacy@ietf.org>; Mon,  4 Jan 2016 01:34:13 -0800 (PST)
Received: from [62.232.251.194] (port=19607 helo=[10.0.0.242]) by shcp01.hosting.zen.net.uk with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from <sara@sinodun.com>) id 1aG1Wg-0002ul-Uv for dns-privacy@ietf.org; Mon, 04 Jan 2016 09:34:09 +0000
From: sara <sara@sinodun.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_85978973-1CEA-402F-9372-635E35A853B3"
Date: Mon, 4 Jan 2016 09:34:08 +0000
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com>
To: dns-privacy@ietf.org
Message-Id: <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - shcp01.hosting.zen.net.uk
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sinodun.com
X-Get-Message-Sender-Via: shcp01.hosting.zen.net.uk: authenticated_id: sara+sinodun.com/only user confirmed/virtual account not confirmed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/xLw8M5-aofoxJrXRuwYLyVa9vlQ>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2016 09:34:16 -0000

--Apple-Mail=_85978973-1CEA-402F-9372-635E35A853B3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi All,=20

As discussed by the working group (in Yokohama and on the list) a new =
draft has been produced

https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00 =
<https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00>=20=


that describes usage profiles, authentication mechanisms and a (D)TLS =
profile that can be used for both DNS-over-TLS and DNS-over-DTLS:

- It discusses in detail the use of Strict and Opportunistic usage =
profiles for DNS-over-(D)TLS.

- It describes domain name based authentication mechanisms using both =
X.509 certificates and DANE as ways that a DNS server can prove its =
identity for authentication purposes.=20

- It presents a (D)TLS profile which defines the configuration options =
and protocol extensions required to optimise connection establishment =
and session resumption.

- It additionally has guidance on counter measures to DNS traffic =
analysis and server capability probing by clients.=20

We request review of this document and consideration for adoption by the =
working group.

Regards

Sara.

>> On 23 Dec 2015, at 16:12, internet-drafts@ietf.org wrote:
>>=20
>>=20
>> A new version of I-D, draft-dgr-dprive-dtls-and-tls-profiles-00.txt
>> has been successfully submitted by Sara Dickinson and posted to the
>> IETF repository.
>>=20
>> Name:		draft-dgr-dprive-dtls-and-tls-profiles
>> Revision:	00
>> Title:		Authentication and (D)TLS Profile for =
DNS-over-TLS and DNS-over-DTLS
>> Document date:	2015-12-23
>> Group:		Individual Submission
>> Pages:		17
>> URL:            =
https://www.ietf.org/internet-drafts/draft-dgr-dprive-dtls-and-tls-profile=
s-00.txt
>> Status:         =
https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>> Htmlized:       =
https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00
>>=20
>>=20
>> Abstract:
>>   This document describes how a DNS client can use a domain name to
>>   authenticate a DNS server that uses Transport Layer Security (TLS)
>>   and Datagram TLS (DTLS).  Additionally, it defines (D)TLS profiles
>>   for DNS clients and servers implementing DNS-over-TLS and DNS-over-
>>   DTLS.


--Apple-Mail=_85978973-1CEA-402F-9372-635E35A853B3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi All,&nbsp;<br class=3D""><br class=3D"">As discussed by =
the working group (in Yokohama and on the list) a new draft has been =
produced<div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles=
-00" =
class=3D"">https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profi=
les-00</a>&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">that describes usage profiles, authentication mechanisms and =
a (D)TLS profile that can be used for both DNS-over-TLS and =
DNS-over-DTLS:<br class=3D""><br class=3D"">- It discusses in detail the =
use of Strict and Opportunistic usage profiles for DNS-over-(D)TLS.<br =
class=3D""><br class=3D"">- It describes domain name based =
authentication mechanisms using both X.509 certificates and DANE as ways =
that a DNS server can prove its identity for authentication =
purposes.&nbsp;<br class=3D""><br class=3D"">- It presents a (D)TLS =
profile which defines the configuration options and protocol extensions =
required to optimise connection establishment and session resumption.<br =
class=3D""><br class=3D"">- It additionally has guidance on counter =
measures to DNS traffic analysis and server capability probing by =
clients.&nbsp;<div class=3D""><br class=3D""></div><div class=3D"">We =
request review of this document and consideration for adoption by the =
working group.<br class=3D""><div class=3D""><br class=3D"">Regards<br =
class=3D""><br class=3D"">Sara.</div></div><div><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><div dir=3D"auto" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div =
style=3D"direction: ltr;" class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 23 Dec 2015, at 16:12, <a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><br =
class=3D"">A new version of I-D, =
draft-dgr-dprive-dtls-and-tls-profiles-00.txt<br class=3D"">has been =
successfully submitted by Sara Dickinson and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-dgr-dprive-dtls-and-tls-profiles<br class=3D"">Revision:<span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>00<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Authentication and (D)TLS Profile for DNS-over-TLS and =
DNS-over-DTLS<br class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2015-12-23<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Individual Submission<br class=3D"">Pages:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>17<br =
class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-dgr-dprive-dtls-and-tls=
-profiles-00.txt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-dgr-dprive-dtls-and-=
tls-profiles-00.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-pro=
files/" =
class=3D"">https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-=
profiles/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles=
-00" =
class=3D"">https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profi=
les-00</a><br class=3D""><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how a DNS client can use =
a domain name to<br class=3D""> &nbsp;&nbsp;authenticate a DNS server =
that uses Transport Layer Security (TLS)<br class=3D""> &nbsp;&nbsp;and =
Datagram TLS (DTLS). &nbsp;Additionally, it defines (D)TLS profiles<br =
class=3D""> &nbsp;&nbsp;for DNS clients and servers implementing =
DNS-over-TLS and DNS-over-<br class=3D""> &nbsp;&nbsp;DTLS.<br =
class=3D""></div></div></blockquote></div></div></div></blockquote></div><=
br class=3D""></div></body></html>=

--Apple-Mail=_85978973-1CEA-402F-9372-635E35A853B3--


From nobody Mon Jan  4 16:11:21 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D71F1ACD86; Mon,  4 Jan 2016 16:11:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160105001118.22772.38119.idtracker@ietfa.amsl.com>
Date: Mon, 04 Jan 2016 16:11:18 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/6JO9nVF2VEyFszG_w-cZvxYf0Jw>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-03.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 00:11:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : DNS over TLS: Initiation and Performance Considerations
        Authors         : Zi Hu
                          Liang Zhu
                          John Heidemann
                          Allison Mankin
                          Duane Wessels
                          Paul Hoffman
	Filename        : draft-ietf-dprive-dns-over-tls-03.txt
	Pages           : 19
	Date            : 2016-01-04

Abstract:
   This document describes the use of TLS to provide privacy for DNS.
   Encryption provided by TLS eliminates opportunities for eavesdropping
   and on-path tampering with DNS queries in the network, such as
   discussed in RFC 7258.  In addition, this document specifies two
   usage profiles for DNS-over-TLS and provides advice on performance
   considerations to minimize overhead from using TCP and TLS with DNS.

   Note: this document was formerly named
   draft-ietf-dprive-start-tls-for-dns.  Its name has been changed to
   better describe the mechanism now used.  Please refer to working
   group archives under the former name for history and previous
   discussion.  [RFC Editor: please remove this paragraph prior to
   publication]


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dns-over-tls-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Jan  5 07:54:23 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 746311A8823 for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 07:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.339
X-Spam-Level: 
X-Spam-Status: No, score=0.339 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYhH7Z_AfeSh for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 07:54:19 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B6BD1A8822 for <dns-privacy@ietf.org>; Tue,  5 Jan 2016 07:54:19 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id AC52B2801C0; Tue,  5 Jan 2016 16:54:17 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id A73222801B7; Tue,  5 Jan 2016 16:54:17 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay1.nic.fr (Postfix) with ESMTP id A4EB74C0006; Tue,  5 Jan 2016 16:53:47 +0100 (CET)
Date: Tue, 5 Jan 2016 16:53:47 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: sara <sara@sinodun.com>
Message-ID: <20160105155347.GA30825@nic.fr>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.2.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/TaIKIlpjI_J6JzvaqY5W0nkRj_o>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 15:54:21 -0000

On Mon, Jan 04, 2016 at 09:34:08AM +0000,
 sara <sara@sinodun.com> wrote 
 a message of 172 lines which said:

> As discussed by the working group (in Yokohama and on the list) a new draft has been produced
> 
> https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00 <https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00> 

I'm confused by section 8.2. It lacks details on how name resolution
is done. I guess the workflow is the following:

* DNS _service_ resolver name is fetched from the configuration

* DNS lookup is done against the default DNS resolver (probably
acquired from DHCP or RA), with no privacy, to find the DNS _host_
resolver name and then its IP address

* Private DNS resolution can now be done against the configured
privacy-aware resolver.

Am I correct? If so, the claim of the draft that you can have "a
DNSSEC validating DNS client configured in this way to do strict DNS
privacy" is doubtful: it is not strict because of the second step,
which has no privacy. May be not a big problem in practice but still
sufficient to avoid labelling it "strict". (Same thing for 9.2, DANE.)

It seems to me that the only way to have really Strict privacy is 8.1.

Also, Table 1 is a bit optimistic: against a passive attacker,
opportunistic privacy provides protection only if the server supports
TLS. Otherwise, unlike Strict, Opportunistic will fall back. (The text
in 4.2 is correct, when it speaks of "undetermined privacy guarantee",
it's just the table which exaggerates.)

Editorial : in section 4.2, there is a reference to "section Section
5".



From nobody Tue Jan  5 11:30:32 2016
Return-Path: <rharolde@umich.edu>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D961B2C36 for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 11:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szXgW3JMhNNb for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 11:30:28 -0800 (PST)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57DE81B2C35 for <dns-privacy@ietf.org>; Tue,  5 Jan 2016 11:30:27 -0800 (PST)
Received: by mail-yk0-x22d.google.com with SMTP id v14so199231558ykd.3 for <dns-privacy@ietf.org>; Tue, 05 Jan 2016 11:30:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3G15UPLN5OoaOJ63gloTW53HsZuDoJJ+BjumagzQ/68=; b=YU3uUfCM6K3i6M9hR07iRTCbR5dsbP5HaDSq/UNcIVtRtWt1eOo8nG2Z9p7y8Zxora qNnnts5ZbjyobM3f9fCfeH2CoJy0oCx/gK4+EpRUJoz94/ZRMpkAXIBaZWJX3Dr/EQxc n0B+w66fThbc4ER3UpJ9o1YpFZZPCg/T8Xz4VAQhu16dyGcx02L1qtim+VdqvRWnTvU6 lZwkOY2vO7IeD8xhQds/GcIeKT0AEQHMk9+kDFrNr68tvr7PqQsSS/to7Zj/zNjqyXaE GfMcRnT63UtJyH35Biz+aJihpa9bR1dkpIwu772AVh3FBOAMFnaIeePyxPKrEPia1way 7Lhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3G15UPLN5OoaOJ63gloTW53HsZuDoJJ+BjumagzQ/68=; b=R6S61EkW00aG0ItzYhSaehl3VzNDFzxFK4ig/vF9x/8gwQrt9L7L5ELc8XeiNx+UjY iu7vmaHxdkQlNV849O96TZI0t+rtak3C3+HId87yQ748JLkzRwHWz88pBcwOey4VVvf4 jYryXUoAmrXY8FRO/ED00uKb3MVFxukhVO9QM3H/ObVmkXAGK57vAfY7LREXPULSWtS3 QKC2KUnOZiglu2EO//yEFP9R4jFpZxmVocA5eSplxK6yhKc7TPczngVzwutT/UYe14ks ez6uK2N/zuxMCIUJBawjQV1x2jCoUyjD9RA4SuKUOLiVEXrCqYSORvDa4zy2MLeiW4HG 1/EA==
X-Gm-Message-State: ALoCoQmP8hcMiyszPgPtRYR/YonUIv5L97bdmVSwxN8dgKcXkPqw0dtq4iMMIsUnL/DGP39jCQC9WXDFHx1vu2P8kzbprGif1ch4gLwx7SYuylowvEsh8QE=
MIME-Version: 1.0
X-Received: by 10.129.56.196 with SMTP id f187mr29235252ywa.111.1452022227148;  Tue, 05 Jan 2016 11:30:27 -0800 (PST)
Received: by 10.129.91.212 with HTTP; Tue, 5 Jan 2016 11:30:27 -0800 (PST)
In-Reply-To: <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com>
Date: Tue, 5 Jan 2016 14:30:27 -0500
Message-ID: <CA+nkc8BCQGPZftbaw7FomhYNVEtzygojrPhZ1KrTt2qYZnFVmA@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
To: sara <sara@sinodun.com>
Content-Type: multipart/alternative; boundary=001a114c88860e4fe305289b45bd
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/6y1q2GsDt8NvCt07T-ti5G0HiLA>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 19:30:30 -0000

--001a114c88860e4fe305289b45bd
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 4, 2016 at 4:34 AM, sara <sara@sinodun.com> wrote:

> Hi All,
>
> As discussed by the working group (in Yokohama and on the list) a new
> draft has been produced
>
> https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00
>
> that describes usage profiles, authentication mechanisms and a (D)TLS
> profile that can be used for both DNS-over-TLS and DNS-over-DTLS:
>
> - It discusses in detail the use of Strict and Opportunistic usage
> profiles for DNS-over-(D)TLS.
>
> - It describes domain name based authentication mechanisms using both
> X.509 certificates and DANE as ways that a DNS server can prove its
> identity for authentication purposes.
>
> - It presents a (D)TLS profile which defines the configuration options and
> protocol extensions required to optimise connection establishment and
> session resumption.
>
> - It additionally has guidance on counter measures to DNS traffic analysis
> and server capability probing by clients.
>
> We request review of this document and consideration for adoption by the
> working group.
>
> Regards
>
> Sara.
>
>
Apparently I don't understand certificates...

In section 7, an example SRV record is:
_domain-s._tcp.dns.example.com. SRV 0 1 853 dns1.example.com.

But is section 9 I see:
_domain-s.dns.example.com

Are those related?  I really don't understand why section 9 even suggests
adding
_domain-s.dns.example.com

I also don't understand why the Subject field is not valid to use. I
thought subjectAltName was optional, and only used if there were more than
one domain name in the cert.

-- 
Bob Harold

--001a114c88860e4fe305289b45bd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Mon, Jan 4, 2016 at 4:34 AM, sara <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:sara@sinodun.com" target=3D"_blank">sara@sinodun.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"word-w=
rap:break-word">Hi All,=C2=A0<br><br>As discussed by the working group (in =
Yokohama and on the list) a new draft has been produced<div><br></div><div>=
<a href=3D"https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profil=
es-00" target=3D"_blank">https://tools.ietf.org/html/draft-dgr-dprive-dtls-=
and-tls-profiles-00</a>=C2=A0</div><div><br></div><div>that describes usage=
 profiles, authentication mechanisms and a (D)TLS profile that can be used =
for both DNS-over-TLS and DNS-over-DTLS:<br><br>- It discusses in detail th=
e use of Strict and Opportunistic usage profiles for DNS-over-(D)TLS.<br><b=
r>- It describes domain name based authentication mechanisms using both X.5=
09 certificates and DANE as ways that a DNS server can prove its identity f=
or authentication purposes.=C2=A0<br><br>- It presents a (D)TLS profile whi=
ch defines the configuration options and protocol extensions required to op=
timise connection establishment and session resumption.<br><br>- It additio=
nally has guidance on counter measures to DNS traffic analysis and server c=
apability probing by clients.=C2=A0<div><br></div><div>We request review of=
 this document and consideration for adoption by the working group.<br><div=
><br>Regards<br><br>Sara.</div></div><br></div></div></blockquote><div><br>=
</div><div>Apparently I don&#39;t understand certificates...<br></div><div>=
<br></div>In section 7, an example SRV record is:<br>_domain-s._<a href=3D"=
http://tcp.dns.example.com">tcp.dns.example.com</a>. SRV 0 1 853 <a href=3D=
"http://dns1.example.com">dns1.example.com</a>.<br><br>But is section 9 I s=
ee:<br>_<a href=3D"http://domain-s.dns.example.com">domain-s.dns.example.co=
m</a><br><br>Are those related?=C2=A0 I really don&#39;t understand why sec=
tion 9 even suggests adding<br>_<a href=3D"http://domain-s.dns.example.com"=
>domain-s.dns.example.com</a><br><br>I also don&#39;t understand why the Su=
bject field is not valid to use. I thought subjectAltName was optional, and=
 only used if there were more than one domain name in the cert.<div><br>-- =
<br></div><div>Bob Harold<br><br></div></div></div></div>

--001a114c88860e4fe305289b45bd--


From nobody Tue Jan  5 18:40:51 2016
Return-Path: <shuque@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105FD1A89E1 for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 18:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAX4z-gL0nBy for <dns-privacy@ietfa.amsl.com>; Tue,  5 Jan 2016 18:40:48 -0800 (PST)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8391A89F5 for <dns-privacy@ietf.org>; Tue,  5 Jan 2016 18:40:42 -0800 (PST)
Received: by mail-qk0-x233.google.com with SMTP id q19so92835635qke.3 for <dns-privacy@ietf.org>; Tue, 05 Jan 2016 18:40:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bxTRq4AqxaZ/QEQj2BTP4EM9hD73Kx/vcv/BUlk39XM=; b=ZTlw1Z7IsM05ihd8sOrogh1oqy8VbChcGe/ta2zF0Ys9UFaPx49Oi2iT77C/oAf2fK 1glACP/m8eslY0ZACVgfeBQe8dnm9c5FtSdJH78e9UbRmea4ZgxHotFwWMaNlrQeIHjU iW90plLGORa4Kjvv4smV7TGHOBdtgQJGbz4dr9MFh1FqTBURjpNcP8A4JdhRcaDACExV C4f5qsRX3Vwj2SNLg7MbaXM9FqfSUTVeJidlgg7Rlkw9rriSCKWeuOsKt/i/x9xMXyfW f9FhyArFWK+hQXqEtVrW3rmWA/32xQZEG1BtQcswTmG2sYJKZ0R9LrHBAqMZLM/C5M5i rzXg==
MIME-Version: 1.0
X-Received: by 10.55.212.92 with SMTP id l89mr128661297qki.70.1452048042068; Tue, 05 Jan 2016 18:40:42 -0800 (PST)
Received: by 10.140.102.9 with HTTP; Tue, 5 Jan 2016 18:40:42 -0800 (PST)
In-Reply-To: <CA+nkc8BCQGPZftbaw7FomhYNVEtzygojrPhZ1KrTt2qYZnFVmA@mail.gmail.com>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com> <CA+nkc8BCQGPZftbaw7FomhYNVEtzygojrPhZ1KrTt2qYZnFVmA@mail.gmail.com>
Date: Tue, 5 Jan 2016 21:40:42 -0500
Message-ID: <CAHPuVdXh4VZU1dxP44JowUdtBJHN3Qo4HfGzptTUT7PzCrGd0w@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
To: Bob Harold <rharolde@umich.edu>
Content-Type: multipart/alternative; boundary=001a1149de9cbe91480528a147fc
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/JdwkOoM-pK7IzvM4XDh34T-CLjA>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>, sara <sara@sinodun.com>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 02:40:50 -0000

--001a1149de9cbe91480528a147fc
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 5, 2016 at 2:30 PM, Bob Harold <rharolde@umich.edu> wrote:

>
>> Apparently I don't understand certificates...
>
> In section 7, an example SRV record is:
> _domain-s._tcp.dns.example.com. SRV 0 1 853 dns1.example.com.
>
> But is section 9 I see:
> _domain-s.dns.example.com
>
> Are those related?  I really don't understand why section 9 even suggests
> adding
> _domain-s.dns.example.com
>

Section 7 shows a DNS SRV record.

Section 9 shows a subject identity included in the certificate
corresponding to the SRV record owner name, specifically an SRV-ID (Subject
Alternative Name -> OtherName/SRVName type) - see RFC 4985 and RFC6125 for
details.


> I also don't understand why the Subject field is not valid to use. I
> thought subjectAltName was optional, and only used if there were more than
> one domain name in the cert.
>

Use of domain names in the subject field's Common Name are large deprecated
by current specs (even though they are commonly issued by public CAs). RFC
6125 for example says:

  o  Move away from including and checking strings that look like
      domain names in the subject's Common Name.

   o  Move toward including and checking DNS domain names via the
      subjectAlternativeName extension designed for that purpose:
      dNSName.

   o  Move toward including and checking even more specific
      subjectAlternativeName extensions where appropriate for using the
      protocol (e.g., uniformResourceIdentifier and the otherName form
      SRVName).

Shumon.

--001a1149de9cbe91480528a147fc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Jan 5, 2016 at 2:30 PM, Bob Harold <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:rharolde@umich.edu" target=3D"_blank">rharolde@umich.edu</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border=
-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_ex=
tra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div styl=
e=3D"word-wrap:break-word"><div><br></div></div></blockquote></span><div>Ap=
parently I don&#39;t understand certificates...<br></div><div><br></div>In =
section 7, an example SRV record is:<br>_domain-s._<a href=3D"http://tcp.dn=
s.example.com" target=3D"_blank">tcp.dns.example.com</a>. SRV 0 1 853 <a hr=
ef=3D"http://dns1.example.com" target=3D"_blank">dns1.example.com</a>.<br><=
br>But is section 9 I see:<br>_<a href=3D"http://domain-s.dns.example.com" =
target=3D"_blank">domain-s.dns.example.com</a><br><br>Are those related?=C2=
=A0 I really don&#39;t understand why section 9 even suggests adding<br>_<a=
 href=3D"http://domain-s.dns.example.com" target=3D"_blank">domain-s.dns.ex=
ample.com</a></div></div></div></blockquote><div><br></div><div>Section 7 s=
hows a DNS SRV record.</div><div><br></div><div>Section 9 shows a subject i=
dentity included in the certificate corresponding to the SRV record owner n=
ame, specifically an SRV-ID (Subject Alternative Name -&gt; OtherName/SRVNa=
me type) - see RFC 4985 and RFC6125 for details.</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">I also don&#39;t understand why the Subject field is not valid to =
use. I thought subjectAltName was optional, and only used if there were mor=
e than one domain name in the cert.</div></div></div></blockquote><div><br>=
</div><div>Use of domain names in the subject field&#39;s Common Name are l=
arge deprecated by current specs (even though they are commonly issued by p=
ublic CAs). RFC 6125 for example says:</div><div><br></div><div><div>=C2=A0=
 o =C2=A0Move away from including and checking strings that look like</div>=
<div>=C2=A0 =C2=A0 =C2=A0 domain names in the subject&#39;s Common Name.</d=
iv><div><br></div><div>=C2=A0 =C2=A0o =C2=A0Move toward including and check=
ing DNS domain names via the</div><div>=C2=A0 =C2=A0 =C2=A0 subjectAlternat=
iveName extension designed for that purpose:</div><div>=C2=A0 =C2=A0 =C2=A0=
 dNSName.</div><div><br></div><div>=C2=A0 =C2=A0o =C2=A0Move toward includi=
ng and checking even more specific</div><div>=C2=A0 =C2=A0 =C2=A0 subjectAl=
ternativeName extensions where appropriate for using the</div><div>=C2=A0 =
=C2=A0 =C2=A0 protocol (e.g., uniformResourceIdentifier and the otherName f=
orm</div><div>=C2=A0 =C2=A0 =C2=A0 SRVName).</div></div><div><br></div><div=
>Shumon.</div><div><br></div></div></div></div>

--001a1149de9cbe91480528a147fc--


From nobody Wed Jan  6 09:21:53 2016
Return-Path: <shuque@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4BEC1B2E07 for <dns-privacy@ietfa.amsl.com>; Wed,  6 Jan 2016 09:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOX7fPqu54b0 for <dns-privacy@ietfa.amsl.com>; Wed,  6 Jan 2016 09:21:50 -0800 (PST)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18B641B2E1A for <dns-privacy@ietf.org>; Wed,  6 Jan 2016 09:21:50 -0800 (PST)
Received: by mail-qk0-x234.google.com with SMTP id q19so99457594qke.3 for <dns-privacy@ietf.org>; Wed, 06 Jan 2016 09:21:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f5qj4BOz6ApiTLGuY3lI4FX6S3VmtTvOKdgT1hUo+kk=; b=HQOzT74bdb6ZYrVBzXtgXXfzW8JfXa600vglEh9qLwqHaM78jGVmiACoqJymFw8vXV 6wZytW2yu7ULIkrzvjeakFvmGrbt0o1d0cne9kJQan5+7vt99/+M38OXUkpl0LMPXBGZ Y1sLyfDC7Yic+2SkC8/sy+AXfTLkvjY+3h6eCFqDu+HHdB0YrmARTHH6EvFQ9zDuHaE7 JbS42lOML5XQo6AdRwrXJ/2ZlZsc2q8yTWjPe37Rj4lPBzs1BSx81ywHJQsB0KUzZzqU TTCmA/Krp1I5XwcBvPlkl8XqVB59uUMi8C6B9SbTFtRkxo3WmUZyJnHHSHSYCgpXTLlM 8y4Q==
MIME-Version: 1.0
X-Received: by 10.55.73.69 with SMTP id w66mr130249804qka.39.1452100909232; Wed, 06 Jan 2016 09:21:49 -0800 (PST)
Received: by 10.140.102.9 with HTTP; Wed, 6 Jan 2016 09:21:48 -0800 (PST)
In-Reply-To: <20160105155347.GA30825@nic.fr>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com> <20160105155347.GA30825@nic.fr>
Date: Wed, 6 Jan 2016 12:21:48 -0500
Message-ID: <CAHPuVdVYskH3URSCbWN3A8EAVPoiZZvjxYeQohh=5QmSZK2-Vg@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=001a114a8dc0df7f2d0528ad96ec
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/D_1BXBKziqY8fDcFdU8c40Flv9c>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>, sara <sara@sinodun.com>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 17:21:52 -0000

--001a114a8dc0df7f2d0528ad96ec
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 5, 2016 at 10:53 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Mon, Jan 04, 2016 at 09:34:08AM +0000,
>  sara <sara@sinodun.com> wrote
>  a message of 172 lines which said:
>
> > As discussed by the working group (in Yokohama and on the list) a new
> draft has been produced
> >
> > https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00 <
> https://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00>
>
> I'm confused by section 8.2. It lacks details on how name resolution
> is done. I guess the workflow is the following:
>
> * DNS _service_ resolver name is fetched from the configuration
>
> * DNS lookup is done against the default DNS resolver (probably
> acquired from DHCP or RA), with no privacy, to find the DNS _host_
> resolver name and then its IP address
>
> * Private DNS resolution can now be done against the configured
> privacy-aware resolver.
>
> Am I correct?


Yes, I think this description is mostly correct. Except in the second step,
I
assume you meant that we lookup the DNS resolver name's IP address; we
do not need "to find the DNS _host_ resolver name" since that was obtained
already from static configuration in the prior step.


> If so, the claim of the draft that you can have "a
> DNSSEC validating DNS client configured in this way to do strict DNS
> privacy" is doubtful: it is not strict because of the second step,
> which has no privacy. May be not a big problem in practice but still
> sufficient to avoid labelling it "strict". (Same thing for 9.2, DANE.)
>
> It seems to me that the only way to have really Strict privacy is 8.1.
>

This depends on the definition of the phrase "Strict Privacy". If it can
include
some initial meta queries to (securely) obtain the address mapping of the
DNS over (D)TLS server that to which we subsequently establish an
authenticated & encrypted session, then this can still be considered
strict.

It could also be argued that 'strict' means no unprotected DNS queries
anywhere, in which case a new category would be needed. I am okay
with "Strict" having the meaning in my previous paragraph. We have to
consider practical deployability and usage issues. A 'no unprotected
DNS anywhere' policy may not be deployable in the general case, because
of a range of system bootstrapping issues and other environmental
issues (for example, a system may need to issue a few unprotected DNS
queries in order to gain access to the network beyond a captive portal
etc).

Also, Table 1 is a bit optimistic: against a passive attacker,
> opportunistic privacy provides protection only if the server supports
> TLS. Otherwise, unlike Strict, Opportunistic will fall back. (The text
> in 4.2 is correct, when it speaks of "undetermined privacy guarantee",
> it's just the table which exaggerates.)
>

Yes, I agree.

-- 
Shumon Huque

--001a114a8dc0df7f2d0528ad96ec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Jan 5, 2016 at 10:53 AM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jan 04, 2016 at 0=
9:34:08AM +0000,<br>
=C2=A0sara &lt;<a href=3D"mailto:sara@sinodun.com">sara@sinodun.com</a>&gt;=
 wrote<br>
<span class=3D"">=C2=A0a message of 172 lines which said:<br>
<br>
&gt; As discussed by the working group (in Yokohama and on the list) a new =
draft has been produced<br>
&gt;<br>
</span>&gt; <a href=3D"https://tools.ietf.org/html/draft-dgr-dprive-dtls-an=
d-tls-profiles-00" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.=
org/html/draft-dgr-dprive-dtls-and-tls-profiles-00</a> &lt;<a href=3D"https=
://tools.ietf.org/html/draft-dgr-dprive-dtls-and-tls-profiles-00" rel=3D"no=
referrer" target=3D"_blank">https://tools.ietf.org/html/draft-dgr-dprive-dt=
ls-and-tls-profiles-00</a>&gt;<br>
<br>
I&#39;m confused by section 8.2. It lacks details on how name resolution<br=
>
is done. I guess the workflow is the following:<br>
<br>
* DNS _service_ resolver name is fetched from the configuration<br>
<br>
* DNS lookup is done against the default DNS resolver (probably<br>
acquired from DHCP or RA), with no privacy, to find the DNS _host_<br>
resolver name and then its IP address<br>
<br>
* Private DNS resolution can now be done against the configured<br>
privacy-aware resolver.<br>
<br>
Am I correct? </blockquote><div><br></div><div>Yes, I think this descriptio=
n is mostly correct. Except in the second step, I=C2=A0</div><div>assume yo=
u meant that we lookup the DNS resolver name&#39;s IP address; we=C2=A0</di=
v><div>do not need &quot;to find the DNS _host_ resolver name&quot; since t=
hat was obtained=C2=A0</div><div>already from static configuration in the p=
rior step.</div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If so, =
the claim of the draft that you can have &quot;a<br>
DNSSEC validating DNS client configured in this way to do strict DNS<br>
privacy&quot; is doubtful: it is not strict because of the second step,<br>
which has no privacy. May be not a big problem in practice but still<br>
sufficient to avoid labelling it &quot;strict&quot;. (Same thing for 9.2, D=
ANE.)<br>
<br>
It seems to me that the only way to have really Strict privacy is 8.1.<br><=
/blockquote><div><br></div><div>This depends on the definition of the phras=
e &quot;Strict Privacy&quot;. If it can include</div><div>some initial meta=
 queries to (securely) obtain the address mapping of the</div><div>DNS over=
 (D)TLS server that to which we subsequently establish an</div><div>authent=
icated &amp; encrypted session, then this can still be considered</div><div=
>strict.</div><div><br></div><div>It could also be argued that &#39;strict&=
#39; means no unprotected DNS queries</div><div>anywhere, in which case a n=
ew category would be needed. I am okay</div><div>with &quot;Strict&quot; ha=
ving the meaning in my previous paragraph. We have to</div><div>consider pr=
actical deployability and usage issues. A &#39;no unprotected</div><div>DNS=
 anywhere&#39; policy may not be deployable in the general case, because</d=
iv><div>of a range of system bootstrapping issues and other environmental</=
div><div>issues (for example, a system may need to issue a few unprotected =
DNS=C2=A0</div><div>queries in order to gain access to the network beyond a=
 captive portal</div><div>etc).</div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
Also, Table 1 is a bit optimistic: against a passive attacker,<br>
opportunistic privacy provides protection only if the server supports<br>
TLS. Otherwise, unlike Strict, Opportunistic will fall back. (The text<br>
in 4.2 is correct, when it speaks of &quot;undetermined privacy guarantee&q=
uot;,<br>
it&#39;s just the table which exaggerates.)<br></blockquote><div><br></div>=
<div>Yes, I agree.</div><div><br></div><div>--=C2=A0</div><div>Shumon Huque=
</div><div><br></div></div></div></div>

--001a114a8dc0df7f2d0528ad96ec--


From nobody Thu Jan  7 01:48:56 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99DA1A885F for <dns-privacy@ietfa.amsl.com>; Thu,  7 Jan 2016 01:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level: 
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aeAVdveMQsQE for <dns-privacy@ietfa.amsl.com>; Thu,  7 Jan 2016 01:48:54 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA3531A8861 for <dns-privacy@ietf.org>; Thu,  7 Jan 2016 01:48:49 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id B6B8E28062F; Thu,  7 Jan 2016 10:48:47 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id B17B52803B1; Thu,  7 Jan 2016 10:48:47 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay1.nic.fr (Postfix) with ESMTP id AEB6F4C003D; Thu,  7 Jan 2016 10:48:17 +0100 (CET)
Date: Thu, 7 Jan 2016 10:48:17 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Shumon Huque <shuque@gmail.com>
Message-ID: <20160107094817.GA30426@nic.fr>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com> <20160105155347.GA30825@nic.fr> <CAHPuVdVYskH3URSCbWN3A8EAVPoiZZvjxYeQohh=5QmSZK2-Vg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHPuVdVYskH3URSCbWN3A8EAVPoiZZvjxYeQohh=5QmSZK2-Vg@mail.gmail.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.2.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/56Qhk2zD6dyeWl0_fWp8wekCWwk>
Cc: sara <sara@sinodun.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 09:48:56 -0000

On Wed, Jan 06, 2016 at 12:21:48PM -0500,
 Shumon Huque <shuque@gmail.com> wrote 
 a message of 155 lines which said:

> I assume you meant that we lookup the DNS resolver name's IP
> address; we do not need "to find the DNS _host_ resolver name" since
> that was obtained already from static configuration in the prior
> step.

No. The static configuration has the _service_ name, not the
_host_name.

draft-dgr-dprive-dtls-and-tls-profiles-00, section 8.2, second
paragraph.


From nobody Thu Jan  7 08:17:34 2016
Return-Path: <sara@sinodun.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFA41A907F for <dns-privacy@ietfa.amsl.com>; Thu,  7 Jan 2016 08:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTZCCFF3ED7e for <dns-privacy@ietfa.amsl.com>; Thu,  7 Jan 2016 08:17:28 -0800 (PST)
Received: from shcp01.hosting.zen.net.uk (shcp01.hosting.zen.net.uk [88.98.24.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BC611A9068 for <dns-privacy@ietf.org>; Thu,  7 Jan 2016 08:17:27 -0800 (PST)
Received: from [62.232.251.194] (port=25287 helo=[10.0.0.242]) by shcp01.hosting.zen.net.uk with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from <sara@sinodun.com>) id 1aHDFX-0004HX-16; Thu, 07 Jan 2016 16:17:22 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_77EA3920-95E5-4898-89BE-FDCE72E0AFF9"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: sara <sara@sinodun.com>
In-Reply-To: <CAHPuVdVYskH3URSCbWN3A8EAVPoiZZvjxYeQohh=5QmSZK2-Vg@mail.gmail.com>
Date: Thu, 7 Jan 2016 16:17:21 +0000
Message-Id: <9863322F-78F7-4033-B08F-C27323B53E6A@sinodun.com>
References: <DC16DB31-A6D7-417D-9526-ADBFD950BA7F@sinodun.com> <4AA7F7AA-D66E-41F8-854D-BDCFDD456B3F@sinodun.com> <20160105155347.GA30825@nic.fr> <CAHPuVdVYskH3URSCbWN3A8EAVPoiZZvjxYeQohh=5QmSZK2-Vg@mail.gmail.com>
To: Shumon Huque <shuque@gmail.com>
X-Mailer: Apple Mail (2.2104)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - shcp01.hosting.zen.net.uk
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sinodun.com
X-Get-Message-Sender-Via: shcp01.hosting.zen.net.uk: authenticated_id: sara+sinodun.com/only user confirmed/virtual account not confirmed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/W7CFZ10kRCEyqDluBX17fiVmX2E>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: [dns-privacy] New Version Notification for draft-dgr-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 16:17:32 -0000

--Apple-Mail=_77EA3920-95E5-4898-89BE-FDCE72E0AFF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 6 Jan 2016, at 17:21, Shumon Huque <shuque@gmail.com> wrote:
>=20
> On Tue, Jan 5, 2016 at 10:53 AM, Stephane Bortzmeyer =
<bortzmeyer@nic.fr <mailto:bortzmeyer@nic.fr>> wrote:
>=20

Stephane,=20

Thanks for the review.

>=20
> I'm confused by section 8.2. It lacks details on how name resolution
> is done. I guess the workflow is the following:
>=20
> * DNS _service_ resolver name is fetched from the configuration
>=20
> * DNS lookup is done against the default DNS resolver (probably
> acquired from DHCP or RA), with no privacy, to find the DNS _host_
> resolver name and then its IP address
>=20
> * Private DNS resolution can now be done against the configured
> privacy-aware resolver.
>=20
> Am I correct?

Yes this is correct. We could break the example down as you have done to =
improve clarity if you like.=20

> =20
> If so, the claim of the draft that you can have "a
> DNSSEC validating DNS client configured in this way to do strict DNS
> privacy" is doubtful: it is not strict because of the second step,
> which has no privacy. May be not a big problem in practice but still
> sufficient to avoid labelling it "strict". (Same thing for 9.2, DANE.)
>=20
> It seems to me that the only way to have really Strict privacy is 8.1.
>=20
> This depends on the definition of the phrase "Strict Privacy". If it =
can include
> some initial meta queries to (securely) obtain the address mapping of =
the
> DNS over (D)TLS server that to which we subsequently establish an
> authenticated & encrypted session, then this can still be considered
> strict.
>=20
> It could also be argued that 'strict' means no unprotected DNS queries
> anywhere, in which case a new category would be needed. I am okay
> with "Strict" having the meaning in my previous paragraph. We have to
> consider practical deployability and usage issues. A 'no unprotected
> DNS anywhere' policy may not be deployable in the general case, =
because
> of a range of system bootstrapping issues and other environmental
> issues (for example, a system may need to issue a few unprotected DNS=20=

> queries in order to gain access to the network beyond a captive portal
> etc).

I agree with Shumon=E2=80=99s analysis here, and we did assume the first =
definition in writing this draft. But, agreed, we should discuss this in =
more detail.

But note that section 8.2 does state that your steps 1 and 2 (and DANE =
lookups) can be done opportunistically rather than with no privacy.=20

>=20
> Also, Table 1 is a bit optimistic: against a passive attacker,
> opportunistic privacy provides protection only if the server supports
> TLS. Otherwise, unlike Strict, Opportunistic will fall back. (The text
> in 4.2 is correct, when it speaks of "undetermined privacy guarantee",
> it's just the table which exaggerates.)

Ah, yes. Will improve this.=20

Sara.=20


--Apple-Mail=_77EA3920-95E5-4898-89BE-FDCE72E0AFF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 6 Jan 2016, at 17:21, Shumon Huque &lt;<a =
href=3D"mailto:shuque@gmail.com" class=3D"">shuque@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On Tue, Jan 5, 2016 at 10:53 AM, Stephane =
Bortzmeyer <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:bortzmeyer@nic.fr" target=3D"_blank" =
class=3D"">bortzmeyer@nic.fr</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br =
class=3D""></blockquote></div></div></div></div></blockquote><div><br =
class=3D""></div>Stephane,&nbsp;</div><div><br =
class=3D""></div><div>Thanks for the review.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class=3D"">
I'm confused by section 8.2. It lacks details on how name resolution<br =
class=3D"">
is done. I guess the workflow is the following:<br class=3D"">
<br class=3D"">
* DNS _service_ resolver name is fetched from the configuration<br =
class=3D"">
<br class=3D"">
* DNS lookup is done against the default DNS resolver (probably<br =
class=3D"">
acquired from DHCP or RA), with no privacy, to find the DNS _host_<br =
class=3D"">
resolver name and then its IP address<br class=3D"">
<br class=3D"">
* Private DNS resolution can now be done against the configured<br =
class=3D"">
privacy-aware resolver.<br class=3D"">
<br class=3D"">
Am I correct?</blockquote></div></div></div></blockquote><div><br =
class=3D""></div><div>Yes this is correct. We could break the example =
down as you have done to improve clarity if you like.&nbsp;</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div =
class=3D"">&nbsp;<br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">If so, the claim of the draft that you can have =
"a<br class=3D"">
DNSSEC validating DNS client configured in this way to do strict DNS<br =
class=3D"">
privacy" is doubtful: it is not strict because of the second step,<br =
class=3D"">
which has no privacy. May be not a big problem in practice but still<br =
class=3D"">
sufficient to avoid labelling it "strict". (Same thing for 9.2, =
DANE.)<br class=3D"">
<br class=3D"">
It seems to me that the only way to have really Strict privacy is =
8.1.<br class=3D""></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">This depends on the definition of the phrase "Strict =
Privacy". If it can include</div><div class=3D"">some initial meta =
queries to (securely) obtain the address mapping of the</div><div =
class=3D"">DNS over (D)TLS server that to which we subsequently =
establish an</div><div class=3D"">authenticated &amp; encrypted session, =
then this can still be considered</div><div class=3D"">strict.</div><div =
class=3D""><br class=3D""></div><div class=3D"">It could also be argued =
that 'strict' means no unprotected DNS queries</div><div =
class=3D"">anywhere, in which case a new category would be needed. I am =
okay</div><div class=3D"">with "Strict" having the meaning in my =
previous paragraph. We have to</div><div class=3D"">consider practical =
deployability and usage issues. A 'no unprotected</div><div class=3D"">DNS=
 anywhere' policy may not be deployable in the general case, =
because</div><div class=3D"">of a range of system bootstrapping issues =
and other environmental</div><div class=3D"">issues (for example, a =
system may need to issue a few unprotected DNS&nbsp;</div><div =
class=3D"">queries in order to gain access to the network beyond a =
captive portal</div><div =
class=3D"">etc).</div></div></div></div></blockquote><div><br =
class=3D""></div><div>I agree with Shumon=E2=80=99s analysis here, and =
we did assume the first definition in writing this draft. But, agreed, =
we should discuss this in more detail.</div><div><br =
class=3D""></div><div>But note that section 8.2 does state that your =
steps 1 and 2 (and DANE lookups) can be done opportunistically rather =
than with no privacy.&nbsp;</div><div><br class=3D""></div><blockquote =
type=3D"cite" class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D""><br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Also, Table 1 is a bit optimistic: against a passive attacker,<br =
class=3D"">
opportunistic privacy provides protection only if the server supports<br =
class=3D"">
TLS. Otherwise, unlike Strict, Opportunistic will fall back. (The =
text<br class=3D"">
in 4.2 is correct, when it speaks of "undetermined privacy =
guarantee",<br class=3D"">
it's just the table which =
exaggerates.)</blockquote></div></div></div></blockquote><br =
class=3D""></div><div>Ah, yes. Will improve this.&nbsp;</div><div><br =
class=3D""></div><div>Sara.&nbsp;</div><br class=3D""></body></html>=

--Apple-Mail=_77EA3920-95E5-4898-89BE-FDCE72E0AFF9--


From nobody Fri Jan  8 13:12:51 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 653771B2BCF; Fri,  8 Jan 2016 13:12:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160108211243.29849.28615.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jan 2016 13:12:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/kJs2Y4NADVJSOdfBhXMzK8Z4bss>
Cc: tjw.ietf@gmail.com, dns-privacy@ietf.org, dprive-chairs@ietf.org, terry.manderson@icann.org
Subject: [dns-privacy] dprive - New Meeting Session Request for IETF 95
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jan 2016 21:12:43 -0000

A new meeting session request has just been submitted by Tim Wicinski, a Chair of the dprive working group.


---------------------------------------------------------
Working Group Name: DNS PRIVate Exchange
Area Name: Internet Area
Session Requester: Tim Wicinski

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: dnsop opsawg dane dnssd homenet
 Second Priority: ipsecme



Special Requests:
  
---------------------------------------------------------


From nobody Tue Jan 12 08:17:24 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AEB1A0419; Tue, 12 Jan 2016 08:17:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160112161723.11447.38285.idtracker@ietfa.amsl.com>
Date: Tue, 12 Jan 2016 08:17:23 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/rumOyQKFkPSDlS9nvPYPTB66GdI>
Cc: dns-privacy@ietf.org, dprive-chairs@ietf.org, warren@kumari.net, terry.manderson@icann.org
Subject: [dns-privacy] dprive - Update to a Meeting Session Request for IETF 95
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2016 16:17:24 -0000

An update to a meeting session request has just been submitted by Warren Kumari, a Chair of the dprive working group.


---------------------------------------------------------
Working Group Name: DNS PRIVate Exchange
Area Name: Internet Area
Session Requester: Warren Kumari

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: dnsop opsawg dane dnssd homenet capport
 Second Priority: ipsecme



Special Requests:
  Would be good if scheduled early in the week, DNS-OARC meeting before the IETF, there is overlap between the communities. Give DNSOP priority though.
---------------------------------------------------------


From nobody Tue Jan 12 11:44:30 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C91541A8774; Tue, 12 Jan 2016 11:44:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160112194428.2830.57717.idtracker@ietfa.amsl.com>
Date: Tue, 12 Jan 2016 11:44:28 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/4YqmDlHQfhonPOk9VqtKyks5PSU>
Cc: dns-privacy@ietf.org, dprive-chairs@ietf.org, warren@kumari.net, terry.manderson@icann.org
Subject: [dns-privacy] dprive - Update to a Meeting Session Request for IETF 95
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2016 19:44:28 -0000

An update to a meeting session request has just been submitted by Warren Kumari, a Chair of the dprive working group.


---------------------------------------------------------
Working Group Name: DNS PRIVate Exchange
Area Name: Internet Area
Session Requester: Warren Kumari

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 140
Conflicts to Avoid: 
 First Priority: homenet dnssd dane opsawg dnsop capport
 Second Priority: ipsecme



Special Requests:
  Would be good if scheduled early in the week, DNS-OARC meeting before the IETF, there is overlap between the communities. Give DNSOP priority though.
---------------------------------------------------------


From nobody Tue Jan 12 13:56:45 2016
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED1F1A8A8D for <dns-privacy@ietfa.amsl.com>; Tue, 12 Jan 2016 13:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAQt25yiHvnn for <dns-privacy@ietfa.amsl.com>; Tue, 12 Jan 2016 13:56:42 -0800 (PST)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 452621A8A8B for <dns-privacy@ietf.org>; Tue, 12 Jan 2016 13:56:42 -0800 (PST)
Received: by mail-ig0-x231.google.com with SMTP id h5so98411983igh.0 for <dns-privacy@ietf.org>; Tue, 12 Jan 2016 13:56:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=to:from:subject:message-id:date:user-agent:mime-version :content-type:content-transfer-encoding; bh=P1Bx0xBettz1eeLfd9gATmbKBioTs2a4NTujq7zOPVk=; b=ABaA/YuDdylKnsI3I8pAqw+04mVv4qfaeXXC34va0Z/LPfrk7HnqXtu02ylbs2ll7F rayiV8EmBhX61993dy2swOlBX8pJv0p9O2xQYQD+JjyFbjnxoo2qqNqzqNtzXKNoBetS ZbHDuoutJfj0xIta/OfaoBI9CtGESV7EHh06PLZ2nPCgMkP+CubLmSvsGQl8DGRWw3/v KWBM1kAQ8sVn1LX2rg9hzftPiaQw8THWt5nfIdjR5AJST3EBwwdaoMWG80QiQRPLU/oX /rMAhodWG9XCUTLSZ7OyPWavLCFBSaUNZkArlUIaGgeREAb62OmtYIRflaoaBRo9k1gT Qs6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=P1Bx0xBettz1eeLfd9gATmbKBioTs2a4NTujq7zOPVk=; b=QRI9UZDl7VLfxLU+8qwHcPyz5WsR59qnJAoBKCBqjGvR6J9OAHdo9+Q8/597MfDDkh oq7+zq8KAk/ObpRTx+z9f/XBYCXo4p2SFgg/X9YRyQeniVwq3gnStSVUTFAKWnyPEyCU EnPTiovGN58ClI+yOLeuFVhpV1KwnCBMpGMvbxN15XsOoEpxuD1IrxkgeMK6T+vE8Lud nMAeg23daeBCarTJ5w/EY75r9HBCLN82owm/gRp9LzNPaTbec8AR/E7sW8TroAYe/6Au H1t2SOj40EHhhCJyoA570uGO90gT3ZcBNeHz59kOY+TmUmev7wnQEwSjtEUZi1i+kuvj J+TQ==
X-Gm-Message-State: ALoCoQnRdM+MmRDC4uuKQ47IVH9zoza9ofKOasXo3otrS2zarSjbBGw6AdBWDgNnIKHmUXpjXLQ88H9IoRYkEL2D4rosyQmG2A==
X-Received: by 10.50.55.98 with SMTP id r2mr16410704igp.97.1452635801548; Tue, 12 Jan 2016 13:56:41 -0800 (PST)
Received: from still.local (50-121-215-241.drr03.clbg.wv.frontiernet.net. [50.121.215.241]) by smtp.googlemail.com with ESMTPSA id j136sm25128563ioj.32.2016.01.12.13.56.39 for <dns-privacy@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Jan 2016 13:56:40 -0800 (PST)
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
Date: Tue, 12 Jan 2016 16:56:39 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0a2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/DWyqM52IyNWw8KE82EX6NtgTl3Y>
Subject: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2016 21:56:44 -0000

The chairs realized earlier today that we encouraged this draft to be 
created, but once it was, we forgot to start a formal Call for Adoption. 
  With the feedback already, this document looks ready for adoption and 
being worked on.

This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles

The draft is available here: 
https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/

Please review this draft to see if you think it is suitable for adoption 
by DPRIVE, and comments to the list, clearly stating your view.

Please also indicate if you are willing to contribute text, review, etc.

This call for adoption ends 26 January 2016

Thanks,
tim wicinski
DPRIVE co-chair


From nobody Tue Jan 12 13:57:00 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8351A8A95; Tue, 12 Jan 2016 13:56:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <dns-privacy@ietf.org>, <draft-dgr-dprive-dtls-and-tls-profiles@ietf.org>,  <dprive-chairs@ietf.org>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160112215658.20842.82751.idtracker@ietfa.amsl.com>
Date: Tue, 12 Jan 2016 13:56:58 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/GlPhjfxI3_DKntGrrZfjK3Nc6wg>
Subject: [dns-privacy] The DPRIVE WG has placed draft-dgr-dprive-dtls-and-tls-profiles in state "Candidate for WG Adoption"
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2016 21:56:58 -0000

The DPRIVE WG has placed draft-dgr-dprive-dtls-and-tls-profiles in state 
Candidate for WG Adoption (entered by Tim Wicinski)

The document is available at
https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/


From nobody Wed Jan 13 03:58:07 2016
Return-Path: <tariqsaraj@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAFA91A8714 for <dns-privacy@ietfa.amsl.com>; Wed, 13 Jan 2016 03:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vj1QCyACzN9z for <dns-privacy@ietfa.amsl.com>; Wed, 13 Jan 2016 03:58:04 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62B241A870D for <dns-privacy@ietf.org>; Wed, 13 Jan 2016 03:58:04 -0800 (PST)
Received: by mail-ig0-x22a.google.com with SMTP id t15so143544726igr.0 for <dns-privacy@ietf.org>; Wed, 13 Jan 2016 03:58:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=bTsO+8r3P/pyjH7DTrrmFjy6fGRM6JuMQM4s/CjYCPs=; b=yB4zo1r6jzdAhYXEMZSF1VLGoX/h8XTkPMCNWch5lTaLYxyYGvLCC47P55Btdf7uOS osmLJbpkECEz/CATosQbby/bsDoKdjhR+joKcHPAvgyFSLY9alOPsOnozjqU0+BXkKFF Af6YVaj423muhxsKtloVv5GXGBTRdxVbyu3Jjnt03yViLR3tsGAvn68LT7iP1AH6dn75 AHSUSQQQ78bbfmafxEZn1jKbSoQReWBo6BPjsV6IMYsrkny7k8AGS+Pow7Wi5PRcIftA aCDjA2GxmqnrynK5LPkjT3UwbmUaaDAljIC9El0oSW9qK4mF/nFYQ0p9l6j54ogdwGzX cg+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=bTsO+8r3P/pyjH7DTrrmFjy6fGRM6JuMQM4s/CjYCPs=; b=ISg0Qk1sTeQRiLWOA6vXDyPnSe7lZdlmIpXRrT34nWoPZ+6GX9VnCxmob2P0TZ+AFE RTf086pJLciOZrpFEdE9jGMKRCy/s6AC2fxWT0dfJEMwBD0jNVPjS8BeLAJlZkqZJqJ2 uZjcsLZIInzckdYOvRuYLElVXSC45h7WiYROIhHIw6vBTcDq9OuNnA2tdccbDRQkfHu2 MVhTVLt6WJoHo3f580ifbwPzVb0GEraPY7TPJNRhBkqqZUwQ3pv/eZfO+7jSXTAleu65 DInkm9zNg4F7ksGX/Wo8darlyIKjFnfstPdBguL5yMLklmFP9gx/HiuOy9lZ5lkqJY2n HdPg==
X-Gm-Message-State: ALoCoQlcvTmk5O+phH9DyItbcM1NEtF5tPobk0WbnI3MHehQ1bWrwvisqPIOT+UKxVB7zMeJzTNByMLRrqsxm22PX41ly/nBow==
MIME-Version: 1.0
X-Received: by 10.50.142.67 with SMTP id ru3mr23917768igb.34.1452686283822; Wed, 13 Jan 2016 03:58:03 -0800 (PST)
Received: by 10.36.202.195 with HTTP; Wed, 13 Jan 2016 03:58:03 -0800 (PST)
Date: Wed, 13 Jan 2016 16:58:03 +0500
Message-ID: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com>
From: Tariq Saraj <tariqsaraj@gmail.com>
To: dns-privacy@ietf.org
Content-Type: multipart/alternative; boundary=001a1130d45eeade7c052935e177
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/Bzgy94_xqDhjY5BtWWRqJ_ypRdo>
Subject: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 11:58:05 -0000

--001a1130d45eeade7c052935e177
Content-Type: text/plain; charset=UTF-8

Hi all,
        I am working on my MS(InfoSec) Final Thesis "Lightweight solution
for confidentiality in DNS".
I just want to raise an issue about DNS confidentiality.
Encryption is only strong when we don't know about both decryption key and
plaintext.
In case with DNS, plaintext is always known. It just a matter of couple of
tries with domain names such as google, facebook, twitter, hotmail, yahoo
and youtube etc.
A simple xoring can return original key used for encryption.

-- 
Regards
Tariq Saraj
Center for Research in Networks and Telecom (*CoReNeT*)

--001a1130d45eeade7c052935e177
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hi all,<br></div>=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 I am working on my MS(InfoSec) Final Thesis &qu=
ot;Lightweight solution for confidentiality in DNS&quot;.<br></div>I just w=
ant to raise an issue about DNS confidentiality.<br></div>Encryption is onl=
y strong when we don&#39;t know about both decryption key and plaintext.<br=
></div>In case with DNS, plaintext is always known. It just a matter of cou=
ple of tries with domain names such as google, facebook, twitter, hotmail, =
yahoo and youtube etc.<br></div>A simple xoring can return original key use=
d for encryption.<br clear=3D"all"><div><div><div><div><div><div><div><br>-=
- <br><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div><font face=
=3D"comic sans ms,sans-serif">Regards<br><span style=3D"background-color:rg=
b(255,255,255)"><span style=3D"color:rgb(32,18,77)">Tariq Saraj</span><span=
></span></span><br></font></div><font face=3D"comic sans ms,sans-serif"><sp=
an style=3D"color:rgb(204,0,0)">Center</span> <span style=3D"color:rgb(224,=
102,102)">for </span><span style=3D"color:rgb(102,0,0)">Research</span> in =
<span style=3D"color:rgb(241,194,50)">Networks</span> and <span style=3D"co=
lor:rgb(61,133,198)">Telecom </span>(<b><span style=3D"color:rgb(102,102,10=
2)">CoReNeT</span></b>)<br></font></div><font face=3D"comic sans ms,sans-se=
rif"></font></div></div>
</div></div></div></div></div></div></div></div>

--001a1130d45eeade7c052935e177--


From nobody Wed Jan 13 04:12:23 2016
Return-Path: <shane@time-travellers.org>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A53711A8888 for <dns-privacy@ietfa.amsl.com>; Wed, 13 Jan 2016 04:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJap_qCSQFHC for <dns-privacy@ietfa.amsl.com>; Wed, 13 Jan 2016 04:12:21 -0800 (PST)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CA111A88AF for <dns-privacy@ietf.org>; Wed, 13 Jan 2016 04:12:18 -0800 (PST)
Received: from [2001:470:78c8:2:224:9bff:fe13:3a9c] (helo=pallas.home.time-travellers.org) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1aJKHe-0001M1-Dl; Wed, 13 Jan 2016 12:12:14 +0000
Date: Wed, 13 Jan 2016 13:12:14 +0100
From: Shane Kerr <shane@time-travellers.org>
To: Tariq Saraj <tariqsaraj@gmail.com>
Message-ID: <20160113131214.149f0fee@pallas.home.time-travellers.org>
In-Reply-To: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com>
References: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com>
X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/jHyS2wP4_W8yIDjIbrpXMmC1tEg>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 12:12:22 -0000

Tariq,

At 2016-01-13 16:58:03 +0500
Tariq Saraj <tariqsaraj@gmail.com> wrote:

>         I am working on my MS(InfoSec) Final Thesis "Lightweight solution
> for confidentiality in DNS".
> I just want to raise an issue about DNS confidentiality.
> Encryption is only strong when we don't know about both decryption key and
> plaintext.

I am by no means a cryptographer, but I am pretty certain that this is
not true.

https://en.wikipedia.org/wiki/Known-plaintext_attack

   "Modern ciphers such as Advanced Encryption Standard are not
   currently known to be susceptible to known-plaintext attacks."

> In case with DNS, plaintext is always known. It just a matter of couple of
> tries with domain names such as google, facebook, twitter, hotmail, yahoo
> and youtube etc.
> A simple xoring can return original key used for encryption.

Cheers,

--
Shane


From nobody Thu Jan 14 00:16:56 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482851B2CB6 for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 00:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DoXApCzJ9q-V for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 00:16:55 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB211B2CB4 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 00:16:54 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D86402805C0; Thu, 14 Jan 2016 09:16:52 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id D2D242802D2; Thu, 14 Jan 2016 09:16:52 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id C7046B38052; Thu, 14 Jan 2016 09:16:22 +0100 (CET)
Date: Thu, 14 Jan 2016 09:16:22 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tariq Saraj <tariqsaraj@gmail.com>
Message-ID: <20160114081622.GA2689@nic.fr>
References: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.3.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/Q2FgjTna9K0cZJuh7vj0fvJ5S9I>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 08:16:56 -0000

On Wed, Jan 13, 2016 at 04:58:03PM +0500,
 Tariq Saraj <tariqsaraj@gmail.com> wrote 
 a message of 62 lines which said:

> In case with DNS, plaintext is always known.

No, it is not (otherwise, encryption would be pointless).

> A simple xoring can return original key used for encryption.

:-D


From nobody Thu Jan 14 08:30:26 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558641A1A4F for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 08:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HhF65DfaQB0 for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 08:30:22 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A230C1A0461 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 08:30:22 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 8EB1128062D; Thu, 14 Jan 2016 17:30:20 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 891EC280593; Thu, 14 Jan 2016 17:30:20 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id 7D9D4B38003; Thu, 14 Jan 2016 17:29:50 +0100 (CET)
Date: Thu, 14 Jan 2016 17:29:50 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <20160114162950.GA20600@nic.fr>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.3.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/LRrwAeZKhiIBCH0HfCOMviOHQfA>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 16:30:24 -0000

On Tue, Jan 12, 2016 at 04:56:39PM -0500,
 Tim Wicinski <tjw.ietf@gmail.com> wrote 
 a message of 25 lines which said:

> The draft is available here:
> https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
> 
> Please review this draft to see if you think it is suitable for adoption by
> DPRIVE, and comments to the list, clearly stating your view.

I've read the draft, I think the general idea (having profiles
separated from the two protocols, TLD and DTLS) is sound, IMHO, the
draft is still too difficult to read (the terminology would need some
strictening) but it can be solved. I volunteer for review, also.


From nobody Thu Jan 14 11:07:18 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E27731A92BC for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 11:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mF11WKFEtu6c for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 11:07:15 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F7331A92B6 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 11:07:15 -0800 (PST)
Received: by mail-ig0-x22f.google.com with SMTP id z14so199958938igp.0 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 11:07:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=39zldC6Q4W5KJFO0cIWSEkLEEIFlJA06v89S5KaN0UI=; b=BFLX0qtNQw/RTBENcxRcVNM3o9KLbysdci8/V8JUmf+XI/Amut0Bg7kl7TUU+Y7DjA Pif0fWUlZtNyrbx9/ldTyxu86J8zleXGwZa5696FttY7N+b4K1GmW9C+7H0m3IBQy2m4 6zZU1hB8buNYDSY8F0qqnu36yOutxpO0f+a2h9Gfx/GdnOKHqmS8J0HHJ+GSqy7A5hIM xuz8zubAK8wZ9Vgcd2eJ0qKcWtD3fhCrps6sxDSFk2+HB1mftcUZys5xYvwFr224oGqD E7QBzAf1hkBCPjr/IGNKYktfOZeYs70fgMYb2Mt1L7Fcn2ovFrmC/z+ipUApDrznOPnY b34A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=39zldC6Q4W5KJFO0cIWSEkLEEIFlJA06v89S5KaN0UI=; b=kFWuvt/poqAab3/70vyGjLuojd9VSFhBFz2GP8jLgiZ/0FYWuq8AvQO0oCfJzDH0Dc ZNEP3ONBruPyuaUc0d3Yrnx1aEEk797GI3XbFBwAJ3SGUJU9MJOfiqUGgAepx4FELPnE nQiyfn3cSlsngTjmECVkWQb/UM81yEHL2IiALA4sVf6sbLfEFlC73EDqF6f9anNcVImM PiTjNKY3gEzYTVT1am5vaTH/xe/TS3+1jBdQ6EogdFbx3um5HQIhc+qeP+WtGChIDvIE mVgScOj/sEGxRKihE3E8Hpb/iJatPrZpOkJw+z+aYDLpwKcK3lE94G4DIod2M7FwHuyV EQdA==
X-Gm-Message-State: ALoCoQnCyeTBy2nle3d8PxvseR+SBM87uoIB7F7vDqTVJCVAtRg4dlHZckBkNYSyDurKj7vzrdMwNur8Gd32twRypfps/J3hMA==
MIME-Version: 1.0
X-Received: by 10.50.155.106 with SMTP id vv10mr28369245igb.41.1452798434655;  Thu, 14 Jan 2016 11:07:14 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.129.80 with HTTP; Thu, 14 Jan 2016 11:07:14 -0800 (PST)
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
Date: Thu, 14 Jan 2016 11:07:14 -0800
X-Google-Sender-Auth: I9qU4In4ItZw7ohCHdxwpMD4OlI
Message-ID: <CAJE_bqfsytJL=XwtwvwMPq67bdapy8ZoXhBaw5k6qtJEHMOcQA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/vK1_jqh_UXDqv6iW8r9YYJtsQBY>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 19:07:17 -0000

At Tue, 12 Jan 2016 16:56:39 -0500,
Tim Wicinski <tjw.ietf@gmail.com> wrote:

> The chairs realized earlier today that we encouraged this draft to be
> created, but once it was, we forgot to start a formal Call for Adoption.
>   With the feedback already, this document looks ready for adoption and
> being worked on.
>
> This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>
> Please review this draft to see if you think it is suitable for adoption
> by DPRIVE, and comments to the list, clearly stating your view.

I support the adoption.

Some initial comments on the 00 version follow:

- Section 4.2

      +-----------------------+------------------+-----------------+
      |     Usage Profile     | Passive Attacker | Active Attacker |
      +-----------------------+------------------+-----------------+
      |       No Privacy      |        N         |        N        |
      | Opportunistic Privacy |        P         |      N (D)      |
      |     Strict Privacy    |        P         |        P        |
      +-----------------------+------------------+-----------------+

How can we detect an active attack in Opportunistic Privacy?  For
example, if an active attacker pretends to be the recursive server
that just doesn't support privacy, can't we distinguish it from a
genuine server that actually doesn't support it?  Perhaps it's
described in the following part of Section 5:

   [...]  This is useful for
   detecting (but not preventing) active attack, and for debugging or
   diagnostic purposes if there are means to report the result of the
   authentication attempt.

but it's still not very clear to me.

Editorial matters:

- Section 4.2: s/section Section/Section/

      is discussed in section Section 5

- Section 6: '[dnssec-trigger]' isn't included in the references sections.

   [...]  Techniques such as those used by DNSSEC-trigger [dnssec-
   trigger] MAY be used during network configuration, with the intent to

- Section 8.3: s/purse/pursue/ ? (If it's really 'purse' I don't
  understand what it means...)

   [QUESTION: The authors would like to solicit feedback on the use of
   DHCP to determine whether to purse a new DHCP option in a later
   version of this draft, or defer it.]

--
JINMEI, Tatuya


From nobody Thu Jan 14 19:00:55 2016
Return-Path: <shuque@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0482C1A8876 for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 19:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zP9A0-TlE66A for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 19:00:52 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ECCF1A8873 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 19:00:52 -0800 (PST)
Received: by mail-qg0-x22c.google.com with SMTP id b35so369071717qge.0 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 19:00:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0jbN3lKM4HH7Mv+B1q/wPHLdfKb4+yqnp2V6eNfiyJY=; b=kb6xyzyVeKzvPVDw+jY/Q/0adiHc1zK1fNnlqWVInxvrLek+eBrKvIdyC2JUkNXhcH imID7ROwAE7BbnwPB9lwflcV/3DdBDNG+uYKZTHuvyM2ITnqGbAY+suQ2EPZpSu2zvJ6 ssJqAkP7Y+HGAHFMJ6TLl793MQYgAFC/mB9HzRtOb6lm/tvckfyQqn7AJho5tK+eyF6n XzLqn3GIoa8TvAFRBYiEiZsNyNX7EnJDi2w02ia/BKcBw9opurc0e2tGuNNhnahsqO37 LDO8Th0T25DGnSLPZQwwnZJrVBgeMl5Macm3dZIKBazKAonJPDTLmStrquTTC4C16IeQ LgbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0jbN3lKM4HH7Mv+B1q/wPHLdfKb4+yqnp2V6eNfiyJY=; b=NIEJSQFQC/XXKJw004qZLQu0MJTg2dNM8CBg8nD9SCsDFl3rhv9u8geiLSQwi61ois NFQ+4bEn3fMlgVYHa6D6XMwNwkOHtPkqD9kUTtfe2bqeYPQ0zL1g5fmqnxjwfdkWEIU8 nqYTebKG5B7g0GWrUCO9TIwpfoxkiarsXuaKDfLZ2rPlazksh3GzHcSeHI+egQvRV1NC 7odZmuVgHtr7+EYFnrJXnZmA+aspQi5W8rM6H6hjo8PtyMOO5C4FzO+BNx1PPMDuW+GG LrTk2VNJqnyFe4lnA5ofbhmGZ9Nz+8DVl5W5zN151PWHYHen2+/n9G114QTXvAmFnIZE EPeA==
X-Gm-Message-State: ALoCoQnnK7Hv2II04JRExkH6Htk2mw67NmY4gQJQ18O3bUvp1dyD3ja00a/T0RwQHIkm/Dbq3pQik/772YHo870ikP9Y/blJSQ==
MIME-Version: 1.0
X-Received: by 10.140.100.229 with SMTP id s92mr9768952qge.19.1452826851718; Thu, 14 Jan 2016 19:00:51 -0800 (PST)
Received: by 10.140.102.9 with HTTP; Thu, 14 Jan 2016 19:00:51 -0800 (PST)
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
Date: Thu, 14 Jan 2016 22:00:51 -0500
Message-ID: <CAHPuVdWhkNavFmRwS4zdkOwPOizZSPqBTuxNjDf=mOvne0_LEA@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c165226ac0230529569cf0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/8l2JiqjrMzPPj08c4toAUA7rRjg>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 03:00:54 -0000

--001a11c165226ac0230529569cf0
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 12, 2016 at 4:56 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:

> The chairs realized earlier today that we encouraged this draft to be
> created, but once it was, we forgot to start a formal Call for Adoption.
> With the feedback already, this document looks ready for adoption and being
> worked on.
>
> This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>
> Please review this draft to see if you think it is suitable for adoption
> by DPRIVE, and comments to the list, clearly stating your view.
>
> Please also indicate if you are willing to contribute text, review, etc.
>
> This call for adoption ends 26 January 2016
>
>
I support adoption of this draft. I've reviewed many details of the current
draft with the authors directly in private communication. And offer to
continue reviewing, and/or
contributing text.

-- 
Shumon Huque

--001a11c165226ac0230529569cf0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Jan 12, 2016 at 4:56 PM, Tim Wicinski <span dir=3D"ltr">&lt;<a href=3D"=
mailto:tjw.ietf@gmail.com" target=3D"_blank">tjw.ietf@gmail.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">The chairs realized earlier to=
day that we encouraged this draft to be created, but once it was, we forgot=
 to start a formal Call for Adoption.=C2=A0 With the feedback already, this=
 document looks ready for adoption and being worked on.<br>
<br>
This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles<=
br>
<br>
The draft is available here: <a href=3D"https://datatracker.ietf.org/doc/dr=
aft-dgr-dprive-dtls-and-tls-profiles/" rel=3D"noreferrer" target=3D"_blank"=
>https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/</=
a><br>
<br>
Please review this draft to see if you think it is suitable for adoption by=
 DPRIVE, and comments to the list, clearly stating your view.<br>
<br>
Please also indicate if you are willing to contribute text, review, etc.<br=
>
<br>
This call for adoption ends 26 January 2016<br><br></blockquote><div><br></=
div><div>I support adoption of this draft. I&#39;ve reviewed many details o=
f the current draft with the authors directly in private communication. And=
 offer to continue reviewing, and/or</div><div>contributing text.</div><div=
><br></div><div>--=C2=A0</div><div>Shumon Huque</div><div><br></div></div><=
/div></div>

--001a11c165226ac0230529569cf0--


From nobody Thu Jan 14 22:31:13 2016
Return-Path: <tariqsaraj@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 008741B29E5 for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 22:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_65=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dhDMrj-UjRpN for <dns-privacy@ietfa.amsl.com>; Thu, 14 Jan 2016 22:31:10 -0800 (PST)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEC41B29E4 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 22:31:09 -0800 (PST)
Received: by mail-ig0-x229.google.com with SMTP id t15so5354050igr.0 for <dns-privacy@ietf.org>; Thu, 14 Jan 2016 22:31:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7fFdVz0TulUwr2LSWXw9kh/v/rEVD6YvdmoVwFHCSsM=; b=FDNBZKsGK3EO8WKWgyHY43GKuS+Wy1pLQ9xvbwwEtNN6nfWeW3rL/yK8tvX3HcvYy3 TKf9QZpqZtHyoisYpU/nfgxO5GaE9rla5nSZyyazdleHiMvSKj7heljCDrz6y/zyLiva DH8EYRWHosvSjGSspkN92TwEXzywJrLSiobsioFvtqrE6neZjVev40a4cYbj87orxre4 1gtOyNPYqct7E9kzoxj3VQLp9wOA9hh8bLP9/ENrhGJkScD9MmJaiN9iKpodhrvJeCQU hE7sPgTjhk8Aa8EqmcYNLF95UM3+iPfN6W2fCU9GQjBX409WdrTKar1rabpJWvOl8dW7 P38w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7fFdVz0TulUwr2LSWXw9kh/v/rEVD6YvdmoVwFHCSsM=; b=Z15nh5wzcuYcj5s7m5Z46WRvoBpc1ngv15shUc8Abe/AQ0TkL0xpV318Jn4+KCpIpf eFUIauxacLjP6DxEKeCo7S8c/0E4m1/f1sj5A8APMAGKimQarBXTrfUokDbbnxGGam2P UNQuglX0shX1WkMEYy/KMS0Eb7h7qO9abftcDKWwnbAbLIG5+3qo//2iiraEf5eeaeq2 qg/2ZcvSRzxrkpzSCAWpyAOF8mV5GHiemJSBJKqH3/aEuOv3RLtfnesE8qJdcbhcsSwd ysPKN9aXb7peQE26fj2FDgRISpfE87liOjtkUn6zEqy8XiUP8ZPT/rmHU0Vl2Kcyy72+ 09ig==
X-Gm-Message-State: AG10YOSuObou3Bw6TYZRfsbH5eXg593d0abMf6LlSYi1WR/UsNbIXD8koiaj1zXPvgAhjWEbfKDmJdSI+YLz0A==
MIME-Version: 1.0
X-Received: by 10.50.160.11 with SMTP id xg11mr1536306igb.83.1452839469211; Thu, 14 Jan 2016 22:31:09 -0800 (PST)
Received: by 10.36.202.195 with HTTP; Thu, 14 Jan 2016 22:31:09 -0800 (PST)
In-Reply-To: <20160114081622.GA2689@nic.fr>
References: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com> <20160114081622.GA2689@nic.fr>
Date: Fri, 15 Jan 2016 11:31:09 +0500
Message-ID: <CAAdbxrqMeYpPjdumYL6E02f3vdQDwEy8TeZ0x0T_LNPiy66JWg@mail.gmail.com>
From: Tariq Saraj <tariqsaraj@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=001a1135e2387a6b680529598c1b
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/vDC6bJVWbxIb5BTy8oHatg1Dca8>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 06:31:11 -0000

--001a1135e2387a6b680529598c1b
Content-Type: text/plain; charset=UTF-8

Hi Stephane,
                  Unfortunately plaintext is known, I am going to work on
it once I complete the confidentiality implementation and soon InShaa'ALLAH
will share with the community.
I know there are a number of rounds and SBoxes involved, but currently
nothing have in hands to defend my concern strongly.
Finally, encryption can't prevent the attack completely but simply make it
difficult for the attacker.
Hope will enjoy discussing with you guru's on this issue in future.

On Thu, Jan 14, 2016 at 1:16 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Wed, Jan 13, 2016 at 04:58:03PM +0500,
>  Tariq Saraj <tariqsaraj@gmail.com> wrote
>  a message of 62 lines which said:
>
> > In case with DNS, plaintext is always known.
>
> No, it is not (otherwise, encryption would be pointless).
>
> > A simple xoring can return original key used for encryption.
>
> :-D
>
>


-- 
Regards
Tariq Saraj
Center for Research in Networks and Telecom (*CoReNeT*)

--001a1135e2387a6b680529598c1b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Hi Stephane,<br></div>=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Unfortunately plaintext is known, I am going to work on it onc=
e I complete the confidentiality implementation and soon InShaa&#39;ALLAH w=
ill share with the community. <br></div>I know there are a number of rounds=
 and SBoxes involved, but currently nothing have in hands to defend my conc=
ern strongly.=C2=A0 <br></div>Finally, encryption can&#39;t prevent the att=
ack completely but simply make it difficult for the attacker.<br></div>Hope=
 will enjoy discussing with you guru&#39;s on this issue in future.<br></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jan 14,=
 2016 at 1:16 PM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;<a href=3D"mail=
to:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">On Wed, Jan 13, 2016 at 04:58:03PM +=
0500,<br>
=C2=A0Tariq Saraj &lt;<a href=3D"mailto:tariqsaraj@gmail.com">tariqsaraj@gm=
ail.com</a>&gt; wrote<br>
<span class=3D"">=C2=A0a message of 62 lines which said:<br>
<br>
&gt; In case with DNS, plaintext is always known.<br>
<br>
</span>No, it is not (otherwise, encryption would be pointless).<br>
<span class=3D""><br>
&gt; A simple xoring can return original key used for encryption.<br>
<br>
</span>:-D<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature"><div dir=3D"ltr"><div><div><font face=3D"comic sans ms,sans-serif">=
Regards<br><span style=3D"background-color:rgb(255,255,255)"><span style=3D=
"color:rgb(32,18,77)">Tariq Saraj</span><span></span></span><br></font></di=
v><font face=3D"comic sans ms,sans-serif"><span style=3D"color:rgb(204,0,0)=
">Center</span> <span style=3D"color:rgb(224,102,102)">for </span><span sty=
le=3D"color:rgb(102,0,0)">Research</span> in <span style=3D"color:rgb(241,1=
94,50)">Networks</span> and <span style=3D"color:rgb(61,133,198)">Telecom <=
/span>(<b><span style=3D"color:rgb(102,102,102)">CoReNeT</span></b>)<br></f=
ont></div><font face=3D"comic sans ms,sans-serif"></font></div></div>
</div>

--001a1135e2387a6b680529598c1b--


From nobody Fri Jan 15 01:15:49 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8661A8AEB for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 01:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWWRMm5UZC_s for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 01:15:47 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40FA61A8AED for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 01:15:47 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 768FC2802D2; Fri, 15 Jan 2016 10:15:45 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 70D9A2801B7; Fri, 15 Jan 2016 10:15:45 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay1.nic.fr (Postfix) with ESMTP id 6EB1B4C0034; Fri, 15 Jan 2016 10:15:15 +0100 (CET)
Date: Fri, 15 Jan 2016 10:15:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tariq Saraj <tariqsaraj@gmail.com>
Message-ID: <20160115091515.GA19396@nic.fr>
References: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com> <20160114081622.GA2689@nic.fr> <CAAdbxrqMeYpPjdumYL6E02f3vdQDwEy8TeZ0x0T_LNPiy66JWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAdbxrqMeYpPjdumYL6E02f3vdQDwEy8TeZ0x0T_LNPiy66JWg@mail.gmail.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.3.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/GjS_Q7iIX-VoAbta3ViPQOOC3dg>
Cc: dns-privacy@ietf.org, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 09:15:49 -0000

On Fri, Jan 15, 2016 at 11:31:09AM +0500,
 Tariq Saraj <tariqsaraj@gmail.com> wrote 
 a message of 80 lines which said:

> Unfortunately plaintext is known,

As I said, it is not. You can sometimes *guess* some of the questions
and answers (it is safe to assume that the user's machine will query
google-analytics.com at least from time to time), it does not give you
the full plaintext (query ID, for instance). And, as Shane explained
(you should have read it), modern crypto is not vulnerable to
"known-plaintext attacks".

> I am going to work on it once I complete the confidentiality
> implementation

May I suggest that you learn some crypto first, as well as reading RFC
7626 and the other DPRIVE documents? Check also the implementations
(there are several of DNS-over-TLS, as well as the nonstandard
DNScrypt).




From nobody Fri Jan 15 08:32:05 2016
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB801B2FBB for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 08:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8l5nfrLfAM0g for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 08:32:02 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 094271B2FB9 for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 08:32:02 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 0B317280610 for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 17:32:00 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 06F602802D2 for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 17:32:00 +0100 (CET)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay1.nic.fr (Postfix) with ESMTP id EF5834C0034 for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 17:31:29 +0100 (CET)
Date: Fri, 15 Jan 2016 17:31:29 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dns-privacy@ietf.org
Message-ID: <20160115163129.GA4162@nic.fr>
References: <20160105001118.22772.38119.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160105001118.22772.38119.idtracker@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux stretch/sid
X-Kernel: Linux 4.3.0-1-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/iJNmy2Vj5xYS_YL9hA5Kt4t_MaE>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-03.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 16:32:04 -0000

On Mon, Jan 04, 2016 at 04:11:18PM -0800,
 internet-drafts@ietf.org <internet-drafts@ietf.org> wrote 
 a message of 53 lines which said:

> 	Filename        : draft-ietf-dprive-dns-over-tls-03.txt

A few remarks, nothing to endanger the WG consensus :-)

The draft mentions DNScurve, a resolver-to-auth technique. Because of
the current charter of DPRIVE, I suggest to replace it by DNScrypt
<https://dnscrypt.org/>

Is it a good idea to keep two profiles in this draft (section 4),
rather than to move everything to
draft-dgr-dprive-dtls-and-tls-profiles?


From nobody Fri Jan 15 08:47:52 2016
Return-Path: <edmonds@mycre.ws>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE9D1B2FE3 for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 08:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RwgpRl7txBm8 for <dns-privacy@ietfa.amsl.com>; Fri, 15 Jan 2016 08:47:49 -0800 (PST)
Received: from chase.mycre.ws (chase.mycre.ws [70.89.251.89]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DE201B2FE2 for <dns-privacy@ietf.org>; Fri, 15 Jan 2016 08:47:49 -0800 (PST)
Received: by chase.mycre.ws (Postfix, from userid 1000) id C0E1612C122A; Fri, 15 Jan 2016 11:47:48 -0500 (EST)
Date: Fri, 15 Jan 2016 11:47:48 -0500
From: Robert Edmonds <edmonds@mycre.ws>
To: dns-privacy@ietf.org
Message-ID: <20160115164748.GA6674@mycre.ws>
References: <CAAdbxrr8TuwNys5_hwMLt+abEBMoZfPbCaW_3M-YEwVgRKs4Kw@mail.gmail.com> <20160114081622.GA2689@nic.fr> <CAAdbxrqMeYpPjdumYL6E02f3vdQDwEy8TeZ0x0T_LNPiy66JWg@mail.gmail.com> <20160115091515.GA19396@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160115091515.GA19396@nic.fr>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/nkphfV4ulVSd6NdchRjxX5CYd6A>
Subject: Re: [dns-privacy] DNS PRIVate Exchange
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 16:47:50 -0000

Stephane Bortzmeyer wrote:
> On Fri, Jan 15, 2016 at 11:31:09AM +0500,
>  Tariq Saraj <tariqsaraj@gmail.com> wrote 
>  a message of 80 lines which said:
> 
> > Unfortunately plaintext is known,
> 
> As I said, it is not. You can sometimes *guess* some of the questions
> and answers (it is safe to assume that the user's machine will query
> google-analytics.com at least from time to time), it does not give you
> the full plaintext (query ID, for instance). And, as Shane explained
> (you should have read it), modern crypto is not vulnerable to
> "known-plaintext attacks".

Not just modern crypto, apparently (if you believe Wikipedia), there was
at least one electro-mechanical encryption machine that was "considered
secure against known plaintext attack", at least by its vendor:

    https://en.wikipedia.org/wiki/KL-7

    In 1952, the machine was introduced by AFSA's successor, the U.S.
    National Security Agency, in the US Army, Navy and Air Force. In the
    early 1960s, the AFSAM-7 was renamed TSEC/KL-7, following the new
    standard crypto nomenclature. It was the most widely used crypto
    machine in the US armed forces until the mid-1960s and was the first
    machine capable of supporting large networks that was considered
    secure against known plaintext attack. The KL-7 was also used by
    several NATO countries until 1983.

-- 
Robert Edmonds


From nobody Mon Jan 18 03:29:05 2016
Return-Path: <sara@sinodun.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A70D1B3504 for <dns-privacy@ietfa.amsl.com>; Mon, 18 Jan 2016 03:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XrgCOJcoSd9n for <dns-privacy@ietfa.amsl.com>; Mon, 18 Jan 2016 03:29:02 -0800 (PST)
Received: from shcp01.hosting.zen.net.uk (shcp01.hosting.zen.net.uk [88.98.24.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED4071B3501 for <dns-privacy@ietf.org>; Mon, 18 Jan 2016 03:29:01 -0800 (PST)
Received: from [62.232.251.194] (port=9884 helo=virgo.sinodun.com) by shcp01.hosting.zen.net.uk with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from <sara@sinodun.com>) id 1aL7zY-0004HL-Pg; Mon, 18 Jan 2016 11:29:02 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Sara Dickinson <sara@sinodun.com>
In-Reply-To: <CAJE_bqfsytJL=XwtwvwMPq67bdapy8ZoXhBaw5k6qtJEHMOcQA@mail.gmail.com>
Date: Mon, 18 Jan 2016 11:28:56 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF5CBCFB-78DC-4DD8-91EE-FC6134F6F0B3@sinodun.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com> <CAJE_bqfsytJL=XwtwvwMPq67bdapy8ZoXhBaw5k6qtJEHMOcQA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3112)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - shcp01.hosting.zen.net.uk
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sinodun.com
X-Get-Message-Sender-Via: shcp01.hosting.zen.net.uk: authenticated_id: sara+sinodun.com/only user confirmed/virtual account not confirmed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/aAwXAVy6zClp7U1wDROuOqhvx9Y>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2016 11:29:04 -0000

> On 14 Jan 2016, at 19:07, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> I support the adoption.

Thanks for the review.

>=20
> Some initial comments on the 00 version follow:
>=20
> - Section 4.2
>=20
>      +-----------------------+------------------+-----------------+
>      |     Usage Profile     | Passive Attacker | Active Attacker |
>      +-----------------------+------------------+-----------------+
>      |       No Privacy      |        N         |        N        |
>      | Opportunistic Privacy |        P         |      N (D)      |
>      |     Strict Privacy    |        P         |        P        |
>      +-----------------------+------------------+-----------------+
>=20
> How can we detect an active attack in Opportunistic Privacy?  For
> example, if an active attacker pretends to be the recursive server
> that just doesn't support privacy, can't we distinguish it from a
> genuine server that actually doesn't support it?  Perhaps it's
> described in the following part of Section 5:
>=20
>   [...]  This is useful for
>   detecting (but not preventing) active attack, and for debugging or
>   diagnostic purposes if there are means to report the result of the
>   authentication attempt.
>=20
> but it's still not very clear to me.

Yes you are correct this section touches on the issue. The scenario =
where detection is possible is if a client is configured with either a =
domain name or SPKI pinset for a given server then the expectation is =
that the server _is_ a DNS privacy enabling server. So if the =
authentication fails in Strict Privacy the connection is aborted. =
However in Opportunistic Privacy the client can choose to connect =
anyway, but it is aware that the server does not authenticate and so it =
should consider an active attack in progress (worst case - of course it =
could be a config error=E2=80=A6).

We plan to update the discussion of Opportunistic Privacy in the next =
version - thanks for this comment. =20

>=20
> Editorial matters:
>=20
> - Section 4.2: s/section Section/Section/
>=20
>      is discussed in section Section 5
>=20
> - Section 6: '[dnssec-trigger]' isn't included in the references =
sections.
>=20
>   [...]  Techniques such as those used by DNSSEC-trigger [dnssec-
>   trigger] MAY be used during network configuration, with the intent =
to

Thanks - will fix.=20

>=20
> - Section 8.3: s/purse/pursue/ ? (If it's really 'purse' I don't
>  understand what it means...)
>=20
>   [QUESTION: The authors would like to solicit feedback on the use of
>   DHCP to determine whether to purse a new DHCP option in a later
>   version of this draft, or defer it.]

Ah! Yes this should be pursue!=20

Sara.=20=


From nobody Mon Jan 18 11:36:54 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F1B1B3C59 for <dns-privacy@ietfa.amsl.com>; Mon, 18 Jan 2016 11:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CIpfvxs0-9Hd for <dns-privacy@ietfa.amsl.com>; Mon, 18 Jan 2016 11:36:51 -0800 (PST)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBF3F1B3C57 for <dns-privacy@ietf.org>; Mon, 18 Jan 2016 11:36:50 -0800 (PST)
Received: by mail-io0-x236.google.com with SMTP id 77so527532105ioc.2 for <dns-privacy@ietf.org>; Mon, 18 Jan 2016 11:36:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=Bxb4ytaxfW6SLkYI/BJ/aR6v797fzdvpoQ/gwg5HtBc=; b=TQ0Z8a3jV1++w1SEKZ3ERGy3R6sUIyn4cA8kC2jequnlRdnWbo586F0bT7dGJy0to0 l+nYR6Q+8NPUlXdiRxLpSYuAKMf989wK8/oWmlxhIY/nCi8b0Bo5vd/Tyc4wfLiJT+Mv s5oTHGKJxAJD1aThL/kRkHkQv1CD4T+CWni2HfQojneZe6xzMbuw8rdTUFC0yOJ4EhUY SzaSPGjgIliD9fOq7KLsjQrv5LTwZDr63fqxWZgGYToCSRAH9hsDNTmQ+rHiubx4Cwtj k5LBBt5z0x65n2F3iVhHuq3wwUeOE2MOGGaLdNW/J/kNDG+A/1O2VRh0ntslvaHlePey cPdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Bxb4ytaxfW6SLkYI/BJ/aR6v797fzdvpoQ/gwg5HtBc=; b=YQIg4og+yqChew8w2twYJF1EPU+KVgl2KJW0LOyRcPmOOZJU/AM4HXUIFktpRXUGzD sDSYDJF8jrdb34t+4c+lNT6uqqInUaZlro+EPZYggUTn9qGjCfIb4X/zdKnRJDRUaBo+ 5m2nGJzrmfRJzjPWemwc2D65JS1CAHiTp8aKVCzCbZDqLfL+VgBVaO1IAg3UJUMiw51N X6kmxEOsIokHKCK4e4YqvZ8qWIrOd+L/l/B4vWFXmI9Ey/cas3Qxsfa1YVdpu+7k8Mtz zNE1i5A2fmNden21JxOX+FMHl+R056QNKfTx07OnHrtrdqbadJ0bTU+cF2m4DDvzYupV hhNA==
X-Gm-Message-State: ALoCoQn/f6JjwYF/6UKlPaCmDxt7C+yGxiaEBUWQlwXvupGFAOPGFTS3bu4hQ+bvhNo9+ArLDTUpmLgku8NvvD9W+fVQ4d+izA==
MIME-Version: 1.0
X-Received: by 10.107.184.67 with SMTP id i64mr27060790iof.4.1453145810347; Mon, 18 Jan 2016 11:36:50 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.129.80 with HTTP; Mon, 18 Jan 2016 11:36:50 -0800 (PST)
In-Reply-To: <EF5CBCFB-78DC-4DD8-91EE-FC6134F6F0B3@sinodun.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com> <CAJE_bqfsytJL=XwtwvwMPq67bdapy8ZoXhBaw5k6qtJEHMOcQA@mail.gmail.com> <EF5CBCFB-78DC-4DD8-91EE-FC6134F6F0B3@sinodun.com>
Date: Mon, 18 Jan 2016 11:36:50 -0800
X-Google-Sender-Auth: Hw__QurJAiyXtM24A-00d_LKMcM
Message-ID: <CAJE_bqdm+nhBfy1EckGYYW3twx0mPwrPpODhft6_Y2KZTXuW6g@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sara Dickinson <sara@sinodun.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/xcQd_oArqSwARi-wuNw-nWcIuLw>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2016 19:36:52 -0000

At Mon, 18 Jan 2016 11:28:56 +0000,
Sara Dickinson <sara@sinodun.com> wrote:

> > Some initial comments on the 00 version follow:
> >
> > - Section 4.2
> >
> >      +-----------------------+------------------+-----------------+
> >      |     Usage Profile     | Passive Attacker | Active Attacker |
> >      +-----------------------+------------------+-----------------+
> >      |       No Privacy      |        N         |        N        |
> >      | Opportunistic Privacy |        P         |      N (D)      |
> >      |     Strict Privacy    |        P         |        P        |
> >      +-----------------------+------------------+-----------------+
> >
> > How can we detect an active attack in Opportunistic Privacy?  For
> > example, if an active attacker pretends to be the recursive server
> > that just doesn't support privacy, can't we distinguish it from a
> > genuine server that actually doesn't support it?  Perhaps it's
> > described in the following part of Section 5:
> >
> >   [...]  This is useful for
> >   detecting (but not preventing) active attack, and for debugging or
> >   diagnostic purposes if there are means to report the result of the
> >   authentication attempt.
> >
> > but it's still not very clear to me.
>
> Yes you are correct this section touches on the issue. The scenario where=
 detection is possible is if a client is configured with either a domain na=
me or SPKI pinset for a given server then the expectation is that the serve=
r _is_ a DNS privacy enabling server. So if the authentication fails in Str=
ict Privacy the connection is aborted. However in Opportunistic Privacy the=
 client can choose to connect anyway, but it is aware that the server does =
not authenticate and so it should consider an active attack in progress (wo=
rst case - of course it could be a config error=E2=80=A6).

Maybe it's just a matter of wording, but this doesn't really sound
like "Detection" to me, in that the client can't (100%) know if it's
an attack or not (that's the same for Strict Privacy, but we can
surely say it provides "Protection" in that case due to its hard-fail
nature).  But...

> We plan to update the discussion of Opportunistic Privacy in the next ver=
sion - thanks for this comment.

...since this may be a wording issue, I'll see how the revised version
reads.

--
JINMEI, Tatuya


From nobody Thu Jan 21 14:55:45 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 017371B3447; Thu, 21 Jan 2016 14:55:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160121225542.19734.41463.idtracker@ietfa.amsl.com>
Date: Thu, 21 Jan 2016 14:55:42 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/WBb9a7wxu4Di8LAVrAmBOFB046o>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-04.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 22:55:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : DNS over TLS: Initiation and Performance Considerations
        Authors         : Zi Hu
                          Liang Zhu
                          John Heidemann
                          Allison Mankin
                          Duane Wessels
                          Paul Hoffman
	Filename        : draft-ietf-dprive-dns-over-tls-04.txt
	Pages           : 19
	Date            : 2016-01-21

Abstract:
   This document describes the use of TLS to provide privacy for DNS.
   Encryption provided by TLS eliminates opportunities for eavesdropping
   and on-path tampering with DNS queries in the network, such as
   discussed in RFC 7258.  In addition, this document specifies two
   usage profiles for DNS-over-TLS and provides advice on performance
   considerations to minimize overhead from using TCP and TLS with DNS.

   Note: this document was formerly named
   draft-ietf-dprive-start-tls-for-dns.  Its name has been changed to
   better describe the mechanism now used.  Please refer to working
   group archives under the former name for history and previous
   discussion.  [RFC Editor: please remove this paragraph prior to
   publication]


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dns-over-tls-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan 21 15:11:45 2016
Return-Path: <dwessels@verisign.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57ED1B29CD for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 15:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8TZPX9YOD0F for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 15:11:43 -0800 (PST)
Received: from mail-qg0-x262.google.com (mail-qg0-x262.google.com [IPv6:2607:f8b0:400d:c04::262]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF7B21B29B1 for <dns-privacy@ietf.org>; Thu, 21 Jan 2016 15:11:42 -0800 (PST)
Received: by mail-qg0-x262.google.com with SMTP id 6so3241756qgy.1 for <dns-privacy@ietf.org>; Thu, 21 Jan 2016 15:11:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=XIPasy5XqYMPF3UPT7M6hr6kew2Jvfso2SOigBvnWfc=; b=E1McJb3UPgUz2LOOdGeYBdWoeZlRsaU/vMouUmTHnVBuXbHd9iKtPeckk++Zdna3ZC 0gz57TTGVS7LOGqrccoBi3s1E8cRbbeHHUcnQialPW5g4k5rZERTocN0NS4pdYuIpiB6 eLRyye1Gih+su0AN3syvWzKEqmnHLMAQpHUeBCSAe3Rzwj0v4+ZjKxa7e6o5eSkk9xn7 wYIgDxNcYaOF6v207X2UST0Zt9cbURDYEmcS+lj5HMSMcqValagvL1iYuzkITjBLNiHD NFEkwhpRmD5n8UarkRp7h0MIj10//y6oFL7rBn3StQPI8KCZ4HGjb/itM7OiDwmnLfYO P16w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=XIPasy5XqYMPF3UPT7M6hr6kew2Jvfso2SOigBvnWfc=; b=MxOcADki9LQWDpguylwGQgFmDjR/jMOxgDq7/6xHVrp3tqVRDKW+sTExfvLwbj5pOQ oSKv5I9kHOj+w6I6Dn+BywzHUXTe7vQYcmlOHkIaD5dzOIXFPm4LG9uCna5UkKL5ExnK rVJO7++Gb1oGytapp+QPwHjckcdkEVGLdYEg+X55cJB7x/9/Cz7XjCdqmYkM3QFWTUY3 HFcqPBonLT3vzN7UFbx7XxTMcJ3l7oCs9yocMof0ElyMLpKKOZKj1fatOZgzD7cz3C1Y q0W1GHRsnvafzHn09oESXV5PeDTLRhAQXXYZnGnOeobCEKKE+CQQwMC9nki4XNz8Xz1N C4Dg==
X-Gm-Message-State: ALoCoQmN2VQ5VOdOjDVUDYN1Eo8i215sZxkiU1efTAZOHC4OVhVCJifgENSJfYz7oG2RAc492ak3D/PNzpF1acGjG3EMXH/4OA2kCrMdx4b3dMtCizHPdD0=
X-Received: by 10.140.174.2 with SMTP id u2mr60271325qhu.62.1453417901878; Thu, 21 Jan 2016 15:11:41 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id y16sm526325qka.6.2016.01.21.15.11.41 for <dns-privacy@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 21 Jan 2016 15:11:41 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u0LNBfdM005534 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dns-privacy@ietf.org>; Thu, 21 Jan 2016 18:11:41 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 21 Jan 2016 18:11:39 -0500
From: "Wessels, Duane" <dwessels@verisign.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-04.txt
Thread-Index: AQHRVJ7spHjoWLgcO0yQzH4OFnTA5p8G7LuA
Date: Thu, 21 Jan 2016 23:11:37 +0000
Message-ID: <8ED0559F-E9CA-4D03-AEA7-844F3733A6FC@verisign.com>
References: <20160121225542.19734.41463.idtracker@ietfa.amsl.com>
In-Reply-To: <20160121225542.19734.41463.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E152B5055181C74EA5A8D1554276D706@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/8z0rCHnNjyetps7h5fxIQ9ZAvZ0>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-04.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 23:11:44 -0000

Hi All,

This update to the DNS-over-TLS draft includes the following changes:

- Expanded and strengthened language about NOT mixing encrypted and
  unencrypted data on a TCP/TLS connection.  The need for this came
  about during IESG evaluation of draft-ietf-dnsop-5966bis.

- Added draft-dgr-dprive-dtls-and-tls-profiles as an informative
  reference for additional privacy profiles.

DW




> On Jan 21, 2016, at 2:55 PM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the DNS PRIVate Exchange Working Group of th=
e IETF.
>=20
>        Title           : DNS over TLS: Initiation and Performance Conside=
rations
>        Authors         : Zi Hu
>                          Liang Zhu
>                          John Heidemann
>                          Allison Mankin
>                          Duane Wessels
>                          Paul Hoffman
> 	Filename        : draft-ietf-dprive-dns-over-tls-04.txt
> 	Pages           : 19
> 	Date            : 2016-01-21
>=20
> Abstract:
>   This document describes the use of TLS to provide privacy for DNS.
>   Encryption provided by TLS eliminates opportunities for eavesdropping
>   and on-path tampering with DNS queries in the network, such as
>   discussed in RFC 7258.  In addition, this document specifies two
>   usage profiles for DNS-over-TLS and provides advice on performance
>   considerations to minimize overhead from using TCP and TLS with DNS.
>=20
>   Note: this document was formerly named
>   draft-ietf-dprive-start-tls-for-dns.  Its name has been changed to
>   better describe the mechanism now used.  Please refer to working
>   group archives under the former name for history and previous
>   discussion.  [RFC Editor: please remove this paragraph prior to
>   publication]
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-04
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dprive-dns-over-tls-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy


From nobody Thu Jan 21 21:12:00 2016
Return-Path: <dwing@cisco.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3881B3859 for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 21:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.202
X-Spam-Level: 
X-Spam-Status: No, score=-14.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMLMD2lQaIRd for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 21:11:57 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3E2C1B3858 for <dns-privacy@ietf.org>; Thu, 21 Jan 2016 21:11:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1089; q=dns/txt; s=iport; t=1453439517; x=1454649117; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=DSk6SFVzrtZNe3W3ZrpN/DUHK7TAy9FP7neX7P3Ntjg=; b=OWeV0a5PxSxZjVrfb259ksvhQD5/KLhGDc9yAEP3RrKgUB9pFRQbyuHy hPH2aHykBQVXz8kFyFkF1hXBzf1t5EQBWDwAaMS7Kz3Gz2ZVsGeEvGAXm BJuztkQ/KaH7nR02HYH8dIWMs6KCFL8nV7TRveLU9d6jBmVG40krGp6oY c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AxBQAIuaFW/51dJa1egzpSbYhXtBAYD?= =?us-ascii?q?IVrAoFDOxEBAQEBAQEBgQqEQQEBAQMBAQEBGh00CwULCw4KLiEGMAYTiAYDCgg?= =?us-ascii?q?OuicNg2oBAQEBAQEBAQEBAQEBAQEBAQEBAQERBIY1ggWCbYJJggCDLoEPBY4eh?= =?us-ascii?q?FWEBIVGhhiBeIFehESDBIQ4gRuGfINvg1M2LIQHGy6HIwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.22,329,1449532800"; d="scan'208";a="68792753"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2016 05:11:57 +0000
Received: from [10.24.16.22] ([10.24.16.22]) (authenticated bits=0) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u0M5BtKU018604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jan 2016 05:11:56 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
Date: Thu, 21 Jan 2016 21:11:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAF6C702-C816-46D6-94CF-E065E3D4FAA7@cisco.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.3112)
X-Authenticated-User: dwing
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/fghJBU69-6Q2LtTxvVADSx6qHsc>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 05:11:59 -0000

On 12-Jan-2016 01:56 pm, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>=20
> The chairs realized earlier today that we encouraged this draft to be =
created, but once it was, we forgot to start a formal Call for Adoption. =
 With the feedback already, this document looks ready for adoption and =
being worked on.
>=20
> This starts a Call for Adoption for =
draft-dgr-dprive-dtls-and-tls-profiles
>=20
> The draft is available here: =
https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>=20
> Please review this draft to see if you think it is suitable for =
adoption by DPRIVE, and comments to the list, clearly stating your view.

It should be adopted as a WG document.

> Please also indicate if you are willing to contribute text, review, =
etc.

I am willing to review.

-d


> This call for adoption ends 26 January 2016
>=20
> Thanks,
> tim wicinski
> DPRIVE co-chair
>=20
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy



From nobody Thu Jan 21 21:47:56 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D5B7C1B38BB; Thu, 21 Jan 2016 21:47:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160122054754.30732.9177.idtracker@ietfa.amsl.com>
Date: Thu, 21 Jan 2016 21:47:54 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/D-KIehQWkWq5ylFY5gFt56qkk3U>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dnsodtls-04.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 05:47:55 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : DNS over DTLS (DNSoD)
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
	Filename        : draft-ietf-dprive-dnsodtls-04.txt
	Pages           : 11
	Date            : 2016-01-21

Abstract:
   DNS queries and responses are visible to network elements on the path
   between the DNS client and its server.  These queries and responses
   can contain privacy-sensitive information which is valuable to
   protect.  An active attacker can send bogus responses causing
   misdirection of the subsequent connection.

   To counter passive listening and active attacks, this document
   proposes the use of Datagram Transport Layer Security (DTLS) for DNS,
   to protect against passive listeners and certain active attacks.  As
   DNS needs to remain fast, this proposal also discusses mechanisms to
   reduce DTLS round trips and reduce DTLS handshake size.  The proposed
   mechanism runs over port 853.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsodtls/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dnsodtls-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dnsodtls-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan 21 21:51:26 2016
Return-Path: <tireddy@cisco.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5321B1B38D0 for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 21:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5YLODKgzHwI for <dns-privacy@ietfa.amsl.com>; Thu, 21 Jan 2016 21:51:24 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D19F91B38B9 for <dns-privacy@ietf.org>; Thu, 21 Jan 2016 21:51:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2348; q=dns/txt; s=iport; t=1453441883; x=1454651483; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ThX4MuXDD9eK+n+lwPe//suTlzQC0eX5jpYjTbV+XWw=; b=E6erwrvUiCJB36KG3FUjtd5a8EzlI1gyMG1r2GC2uTUor3ZfxzOZcBzp HSTwBE81vlQL+N10PuWIqVAaEB30K05iVGZ1WgV5tiqg8VpyvzpDsKvN4 3BnAIScD0gluQUBfuo3Q+JQB75qKoxbg0pStBPSLDRzClDX4qovS+ET5f U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgCPwqFW/4sNJK1egzpSbQaIUbIgA?= =?us-ascii?q?Q2BYhgKhW0CgUY4FAEBAQEBAQF/C4RBAQEBBAEBATc0FwQCAQgRBAEBHwkHJws?= =?us-ascii?q?UBwEBBQMCBBMIiBMOviIBAQEBAQEBAQEBAQEBAQEBAQEBAQEVhjWEcoQzhFMFl?= =?us-ascii?q?ncBhUWICYFlSoN6iFeOPQEeAQFCg2Zqhid8AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,329,1449532800"; d="scan'208";a="228442395"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Jan 2016 05:51:22 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u0M5pNJ0015664 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dns-privacy@ietf.org>; Fri, 22 Jan 2016 05:51:23 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 21 Jan 2016 23:51:22 -0600
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1104.009; Thu, 21 Jan 2016 23:51:22 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] I-D Action: draft-ietf-dprive-dnsodtls-04.txt
Thread-Index: AQHRVNh0irgkaZJ3/kGjl1XiIs9t458HB36w
Date: Fri, 22 Jan 2016 05:51:22 +0000
Message-ID: <2fc81367a8d0480eab5f2c886ef20a6b@XCH-RCD-017.cisco.com>
References: <20160122054754.30732.9177.idtracker@ietfa.amsl.com>
In-Reply-To: <20160122054754.30732.9177.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.46.213]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/2-N-SwG8cahpaI9m_uHBsaIBoIA>
Subject: [dns-privacy] FW:  I-D Action: draft-ietf-dprive-dnsodtls-04.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 05:51:25 -0000

This revision addresses comments from Christian and refers to draft-dgr-dpr=
ive-dtls-and-tls-profiles.

-Tiru

-----Original Message-----
From: dns-privacy [mailto:dns-privacy-bounces@ietf.org] On Behalf Of intern=
et-drafts@ietf.org
Sent: Friday, January 22, 2016 11:18 AM
To: i-d-announce@ietf.org
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dnsodtls-04.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the=
 IETF.

        Title           : DNS over DTLS (DNSoD)
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
	Filename        : draft-ietf-dprive-dnsodtls-04.txt
	Pages           : 11
	Date            : 2016-01-21

Abstract:
   DNS queries and responses are visible to network elements on the path
   between the DNS client and its server.  These queries and responses
   can contain privacy-sensitive information which is valuable to
   protect.  An active attacker can send bogus responses causing
   misdirection of the subsequent connection.

   To counter passive listening and active attacks, this document
   proposes the use of Datagram Transport Layer Security (DTLS) for DNS,
   to protect against passive listeners and certain active attacks.  As
   DNS needs to remain fast, this proposal also discusses mechanisms to
   reduce DTLS round trips and reduce DTLS handshake size.  The proposed
   mechanism runs over port 853.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsodtls/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dnsodtls-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dprive-dnsodtls-04


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
dns-privacy mailing list
dns-privacy@ietf.org
https://www.ietf.org/mailman/listinfo/dns-privacy


From nobody Fri Jan 22 13:35:49 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC381A8977; Fri, 22 Jan 2016 13:35:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160122213546.32727.44336.idtracker@ietfa.amsl.com>
Date: Fri, 22 Jan 2016 13:35:46 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/JqTtYGOgz4KY6MobQz2mySoXD_0>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-05.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 21:35:46 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : DNS over TLS: Initiation and Performance Considerations
        Authors         : Zi Hu
                          Liang Zhu
                          John Heidemann
                          Allison Mankin
                          Duane Wessels
                          Paul Hoffman
	Filename        : draft-ietf-dprive-dns-over-tls-05.txt
	Pages           : 19
	Date            : 2016-01-22

Abstract:
   This document describes the use of TLS to provide privacy for DNS.
   Encryption provided by TLS eliminates opportunities for eavesdropping
   and on-path tampering with DNS queries in the network, such as
   discussed in RFC 7258.  In addition, this document specifies two
   usage profiles for DNS-over-TLS and provides advice on performance
   considerations to minimize overhead from using TCP and TLS with DNS.

   Note: this document was formerly named
   draft-ietf-dprive-start-tls-for-dns.  Its name has been changed to
   better describe the mechanism now used.  Please refer to working
   group archives under the former name for history and previous
   discussion.  [RFC Editor: please remove this paragraph prior to
   publication]


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-dns-over-tls-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jan 22 13:42:11 2016
Return-Path: <dwessels@verisign.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2471D1A89FD for <dns-privacy@ietfa.amsl.com>; Fri, 22 Jan 2016 13:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKF0KN7vWGM8 for <dns-privacy@ietfa.amsl.com>; Fri, 22 Jan 2016 13:42:03 -0800 (PST)
Received: from mail-qg0-x262.google.com (mail-qg0-x262.google.com [IPv6:2607:f8b0:400d:c04::262]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0A961A89C6 for <dns-privacy@ietf.org>; Fri, 22 Jan 2016 13:42:02 -0800 (PST)
Received: by mail-qg0-x262.google.com with SMTP id i20so4928805qgd.2 for <dns-privacy@ietf.org>; Fri, 22 Jan 2016 13:42:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=Z9YUvyRssl/ZFixE9zUCdReifTnXkusFqZaiN8SSrok=; b=HtRGnprlZc1eiVVxDIQABoPpbGcW7rcGQlK/gsdMkr2JbgO+oCWXJ5jiyI4DNGZav5 1bZicnG84cuZVUoNwunkCYDPsIdbNWohO5d/6n2puvmW26PtIe5X2Gi7y4FvelAvEBf3 EQn5q6b3RXOY8xbGc/fC77DXMyaxX5jGDjI+3NLlf2dh5CvCHCoKLCpjkPz/ouL0mFIO qn+Co5IkMQUxoXgC+5OjPFOKBUy0R4h64QkeEnKXTtLxb2xO/VJAfglrPYOhlVDirCvU Abs4jenBNcrHaTQcL8rDXFMlBA6UnHIKlk/FVjZKTeBK6oF62cmN6yFwgKlSJQwI3Ick mDVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=Z9YUvyRssl/ZFixE9zUCdReifTnXkusFqZaiN8SSrok=; b=D18o77tyHbX+877IM7HpT9/MbMK5jteFPmqDZbkrXuduRsRdLbBQW3aQH+181pEMe0 562SGCBp6PH0zvreuxcBv24sINqNBJ5l3U6eJWZL/eLqB2nxx9I5jB6E7K5hV6sMyhV5 u3GhK2BRgfulOkSla1EUUKmtxE9qnZXEeTU2/HjytbEkbht+2vCc/NlhVQifm/kmv7O/ 1WEqm4fxkdSS2PncsCbB80scrKy27IG/030gjmo1p2fq8jrm0PMW1x+bgZho2UaMiD0k z/+QBbYu4Et4sKc5r6em//6iOV0tF5tRbI9kMC2fnuhgLcIqK+cC2Puwr6dlY8x9nEls lzSw==
X-Gm-Message-State: AG10YOSgPqNVHaBKdmF4JuR4ugE4e+/JytOx0WefqLEP5GBsXERziRIzKH3usyWMcbYIx6xskTXYWz4IEeyKYYogn098z+Ky
X-Received: by 10.141.0.4 with SMTP id b4mr7042801qhd.23.1453498922146; Fri, 22 Jan 2016 13:42:02 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id w125sm1193958qka.5.2016.01.22.13.42.01 for <dns-privacy@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 22 Jan 2016 13:42:02 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u0MLg1ZF022653 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dns-privacy@ietf.org>; Fri, 22 Jan 2016 16:42:01 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 22 Jan 2016 16:41:58 -0500
From: "Wessels, Duane" <dwessels@verisign.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-05.txt
Thread-Index: AQHRVVztbeQImZYsm02GjEjZZYrCmZ8IZIaA
Date: Fri, 22 Jan 2016 21:41:58 +0000
Message-ID: <C7A730E1-FA56-4389-9C49-3036A216F071@verisign.com>
References: <20160122213546.32727.44336.idtracker@ietfa.amsl.com>
In-Reply-To: <20160122213546.32727.44336.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <430FB3A39AADC94D8FE7A7F1F23F0048@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/jH6_SF6AvIQv5taWHsLxsI_Iz40>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-dns-over-tls-05.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2016 21:42:08 -0000

Hello All,

This update to draft-ietf-dprive-dns-over-tls adds an informative
reference to DNSCrypt as suggested by Stephane Bortzmeyer.  My apologies
for missing it earlier Stephane!

DW


> On Jan 22, 2016, at 1:35 PM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the DNS PRIVate Exchange Working Group of th=
e IETF.
>=20
>        Title           : DNS over TLS: Initiation and Performance Conside=
rations
>        Authors         : Zi Hu
>                          Liang Zhu
>                          John Heidemann
>                          Allison Mankin
>                          Duane Wessels
>                          Paul Hoffman
> 	Filename        : draft-ietf-dprive-dns-over-tls-05.txt
> 	Pages           : 19
> 	Date            : 2016-01-22
>=20
> Abstract:
>   This document describes the use of TLS to provide privacy for DNS.
>   Encryption provided by TLS eliminates opportunities for eavesdropping
>   and on-path tampering with DNS queries in the network, such as
>   discussed in RFC 7258.  In addition, this document specifies two
>   usage profiles for DNS-over-TLS and provides advice on performance
>   considerations to minimize overhead from using TCP and TLS with DNS.
>=20
>   Note: this document was formerly named
>   draft-ietf-dprive-start-tls-for-dns.  Its name has been changed to
>   better describe the mechanism now used.  Please refer to working
>   group archives under the former name for history and previous
>   discussion.  [RFC Editor: please remove this paragraph prior to
>   publication]
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-05
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dprive-dns-over-tls-05
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy


From nobody Sat Jan 23 23:13:53 2016
Return-Path: <huitema@huitema.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C4B1A902F for <dns-privacy@ietfa.amsl.com>; Sat, 23 Jan 2016 23:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0iPMefFjuZZi for <dns-privacy@ietfa.amsl.com>; Sat, 23 Jan 2016 23:13:50 -0800 (PST)
Received: from xsmtp01.mail2web.com (xsmtp01.mail2web.com [168.144.250.230]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551B21A902E for <dns-privacy@ietf.org>; Sat, 23 Jan 2016 23:13:50 -0800 (PST)
Received: from [10.5.2.18] (helo=xmail08.myhosting.com) by xsmtp01.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1aNErp-0007wE-2I for dns-privacy@ietf.org; Sun, 24 Jan 2016 02:13:49 -0500
Received: (qmail 7657 invoked from network); 24 Jan 2016 07:13:44 -0000
Received: from unknown (HELO huitema1) (Authenticated-user:_huitema@huitema.net@[24.16.156.113]) (envelope-sender <huitema@huitema.net>) by xmail08.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dns-privacy@ietf.org>; 24 Jan 2016 07:13:43 -0000
From: "Christian Huitema" <huitema@huitema.net>
To: "'??Dan Wing'" <dwing@cisco.com>, "'Tim Wicinski'" <tjw.ietf@gmail.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com> <FAF6C702-C816-46D6-94CF-E065E3D4FAA7@cisco.com>
In-Reply-To: <FAF6C702-C816-46D6-94CF-E065E3D4FAA7@cisco.com>
Date: Sat, 23 Jan 2016 23:13:47 -0800
Message-ID: <004201d15676$c576ec50$5064c4f0$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQFaJN0jPti+Wa9jTl+8pqaMq8hFQAJWLdQGn+Xu1zA=
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/p3mBQHUuezr4i1ciPuY8zUyWdIk>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2016 07:13:52 -0000

On Thursday, January 21, 2016 9:12 PM, Dan Wing wrote
> 
> On 12-Jan-2016 01:56 pm, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> > ...
> > This starts a Call for Adoption for
> draft-dgr-dprive-dtls-and-tls-profiles
> >
> > The draft is available here:
> https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
> >
> > Please review this draft to see if you think it is suitable for adoption
> by DPRIVE, and comments to the list, clearly stating your view.
> 
> It should be adopted as a WG document.

I believe that too. I also believe that the document will benefit from
reviews and comments.

> > Please also indicate if you are willing to contribute text, review, etc.
> 
> I am willing to review.

Me too.

When I read the current draft, I found too issues that will hopefully be
fixed in the next revisions.

The first issue is the deployment model. I believe that a very common model
will be the connection by client hosts to a trusted recursive resolver. One
has to "read between the lines" of the current draft to find how the
considerations apply to this model. I wish we could have a more explicit
discussion of that scenario.

The other issue is the interaction with "firewall policies" in common use in
enterprise networks. These policies include making internal sites available
to hosts behind the firewall, but not outside it. They also commonly include
barring access to a variety of "not safe for work" domains. Encrypted
connections to a DNS server could traverse these firewalls, and bypass these
policy controls. The issue is documented in CERT Alert (TA15-240A),
"Controlling Outbound DNS Access,"
https://www.us-cert.gov/ncas/alerts/TA15-240A. We should address it.

-- Christian Huitema




From nobody Mon Jan 25 09:12:28 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1653A1B2D57; Mon, 25 Jan 2016 09:12:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160125171226.8527.6923.idtracker@ietfa.amsl.com>
Date: Mon, 25 Jan 2016 09:12:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/c8EfrIkH3rrlNfAQ0x1SuW5NY7Q>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 17:12:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : The EDNS(0) Padding Option
        Author          : Alexander Mayrhofer
	Filename        : draft-ietf-dprive-edns0-padding-02.txt
	Pages           : 6
	Date            : 2016-01-25

Abstract:
   This document specifies the EDNS(0) 'Padding' option, which allows
   DNS clients and servers to pad request and response messages by a
   variable number of octets.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-edns0-padding/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-edns0-padding-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dprive-edns0-padding-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jan 25 09:26:32 2016
Return-Path: <alex.mayrhofer.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D02B1B322D for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 09:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5ZQnaVSTtB5 for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 09:26:29 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B99E1B3229 for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 09:26:29 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id 65so85046484pff.2 for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 09:26:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:subject:message-id:from:to:mime-version:in-reply-to:references :content-type; bh=TFNEeD1nIYKHcdMN4rIX4Ny4Xlk7QD9B7ZWrDUkDXVQ=; b=KF2aJv1bLJx2X/ge1Nh01q1c5WhUkB4ZgNSF1FDSWSTgJtnFyDfC3MpjTpsOqHrvUY nvNwm7bMRADZY4h6MH6GxDBvdlxLgtbr4ZioHxjaH5GifMGmsOf4/FgbWneY/zSPFo5E 0VKKO/+brQV1XtfJ/iHU4fFagGiNSssgwDJCYssFkVhbRzlOIFmrbxHmJ+a4C6PE1/zu U4iMJudQYD3RlpGHBA31bVO8DWD1ZkTGwlrnUJ1itTcUJXHnyz0HYxwqigeVkHTLVwVm GNIbs3/8bRSDqlAY48re5j3zf3he/hZSzJ7HWRGpl9G5TWbC9a94AL8nLkmUT/pljDON lzzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:subject:message-id:from:to:mime-version :in-reply-to:references:content-type; bh=TFNEeD1nIYKHcdMN4rIX4Ny4Xlk7QD9B7ZWrDUkDXVQ=; b=ffpIEyDEtd5MZhKWC14RcFN+xM6SagslQ6zaJPKCTvQxtpm8C6mTyYT+dQ8mzfPZk9 dwn4z3XiQj4WxzwJpWhAVEdlNuFjDCc1NvzA4I5AByOhcLT0CDN2JZ0lPBM6mXYPBl4u sMRWAAVcvQZdjO4rHPQzHbhthPn1fWdzv/DUoCPMRn+YXPPTM+xAImV9fmV2Nn/DfIsK 5zkPTKZRQIJwTo5ZDey9oEvIwuauhAmCinylnrctsrUtGea6OfoqN3dznXhvrRYpaWQE OCiX5t4ZpeUhe5TdTikX2eiJABPMHEWWax9S+SWMFEWmikqlzWeeXWklqzPnGk9m1JDz NewA==
X-Gm-Message-State: AG10YOQ4noG7/1FK3gRpKF+lj+Wxytz9J7+mqUuYM6EBWXNHEtNIHdv7bzFw63D+tWZ8GA==
X-Received: by 10.98.7.74 with SMTP id b71mr27626407pfd.38.1453742788650; Mon, 25 Jan 2016 09:26:28 -0800 (PST)
Received: from [100.70.81.111] ([61.245.173.121]) by smtp.gmail.com with ESMTPSA id tp3sm30033924pac.16.2016.01.25.09.26.25 for <dns-privacy@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Jan 2016 09:26:27 -0800 (PST)
Date: Mon, 25 Jan 2016 22:56:59 +0530
Message-ID: <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com>
From: Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com>
To: dns-privacy@ietf.org
MIME-Version: 1.0
In-Reply-To: <20160125171226.8527.6923.idtracker@ietfa.amsl.com>
References: <20160125171226.8527.6923.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="--_com.android.email_945939224512410"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/_ZEKVKo16PDiPXS-MsHg6qopWrA>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 17:26:31 -0000

----_com.android.email_945939224512410
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGksCgpUaGlzIHZlcnNpb24gYWRkcmVzc2VzIGNvbW1lbnRzIHJlY2VpdmVkIHNpbmNlIHRoZSBw
dWJsaWNhdGlvbiBvZiB0aGUgbGFzdCBkcmFmdCB2ZXJzaW9uLCBpbmNsdWRpbmcgdGhlIFdHTEMg
Y29tbWVudHMuIAoKVGhlIG9ubHkgYmlnZ2VyIGNoYW5nZSBpcyB0aGF0IChpbiBsaW5lIHdpdGgg
dGhlIGNvbW1lbnRzIHJlY2VpdmVkKSBJJ3ZlIGdlbmVyYWxpemVkIHRoZSB0ZXh0IGFib3V0IE5v
bi0weDAwIHBhZGRpbmcgb2N0ZWN0cywgYmFzZWQgb24gdGV4dCBzdWdnZXN0ZWQgYnkgQW5kcmVh
cyBHdXN0YWZmc29uIAoKQWxleCAKCgotLS0tIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBzY2hy
aWViIC0tLS0KCj4KPkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBv
bi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4KPiBUaGlzIGRyYWZ0IGlzIGEgd29y
ayBpdGVtIG9mIHRoZSBETlMgUFJJVmF0ZSBFeGNoYW5nZSBXb3JraW5nIEdyb3VwIG9mIHRoZSBJ
RVRGLgo+Cj4gICAgICAgIFRpdGxlICAgICAgICAgICA6IFRoZSBFRE5TKDApIFBhZGRpbmcgT3B0
aW9uCj4gICAgICAgIEF1dGhvciAgICAgICAgICA6IEFsZXhhbmRlciBNYXlyaG9mZXIKPglGaWxl
bmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLWRwcml2ZS1lZG5zMC1wYWRkaW5nLTAyLnR4dAo+CVBh
Z2VzICAgICAgICAgICA6IDYKPglEYXRlICAgICAgICAgICAgOiAyMDE2LTAxLTI1Cj4KPkFic3Ry
YWN0Ogo+ICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgdGhlIEVETlMoMCkgJ1BhZGRpbmcnIG9w
dGlvbiwgd2hpY2ggYWxsb3dzCj4gICBETlMgY2xpZW50cyBhbmQgc2VydmVycyB0byBwYWQgcmVx
dWVzdCBhbmQgcmVzcG9uc2UgbWVzc2FnZXMgYnkgYQo+ICAgdmFyaWFibGUgbnVtYmVyIG9mIG9j
dGV0cy4KPgo+Cj5UaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFm
dCBpczoKPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtZHByaXZl
LWVkbnMwLXBhZGRpbmcvCj4KPlRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZhaWxh
YmxlIGF0Ogo+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZHByaXZlLWVk
bnMwLXBhZGRpbmctMDIKPgo+QSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZh
aWxhYmxlIGF0Ogo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYt
ZHByaXZlLWVkbnMwLXBhZGRpbmctMDIKPgo+Cj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtl
IGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uCj51bnRpbCB0
aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYu
b3JnLgo+Cj5JbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBG
VFAgYXQ6Cj5mdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLwo+Cj5fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+ZG5zLXByaXZhY3kgbWFpbGlu
ZyBsaXN0Cj5kbnMtcHJpdmFjeUBpZXRmLm9yZwo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9kbnMtcHJpdmFjeQo=
----_com.android.email_945939224512410
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PHAgZGlyPSJsdHIiPkhpLDwvcD4KPHAgZGlyPSJsdHIiPlRoaXMgdmVyc2lvbiBhZGRyZXNzZXMg
Y29tbWVudHMgcmVjZWl2ZWQgc2luY2UgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZSBsYXN0IGRyYWZ0
IHZlcnNpb24sIGluY2x1ZGluZyB0aGUgV0dMQyBjb21tZW50cy4gPC9wPgo8cCBkaXI9Imx0ciI+
VGhlIG9ubHkgYmlnZ2VyIGNoYW5nZSBpcyB0aGF0IChpbiBsaW5lIHdpdGggdGhlIGNvbW1lbnRz
IHJlY2VpdmVkKSBJJ3ZlIGdlbmVyYWxpemVkIHRoZSB0ZXh0IGFib3V0IE5vbi0weDAwIHBhZGRp
bmcgb2N0ZWN0cywgYmFzZWQgb24gdGV4dCBzdWdnZXN0ZWQgYnkgQW5kcmVhcyBHdXN0YWZmc29u
IDwvcD4KPHAgZGlyPSJsdHIiPkFsZXggPGJyPgo8L3A+Cjxicj48YnI+LS0tLSBpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcgc2NocmllYiAtLS0tPGJyPjxicj48YnI+QSBOZXcgSW50ZXJuZXQtRHJh
ZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9y
aWVzLjxicj4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgRE5TIFBSSVZhdGUgRXhj
aGFuZ2UgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi48YnI+PGJyPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBUaXRsZSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA6IFRoZSBFRE5TKDApIFBhZGRpbmcg
T3B0aW9uPGJyPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBBdXRo
b3ImbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
OiBBbGV4YW5kZXIgTWF5cmhvZmVyPGJyPglGaWxlbmFtZSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyA6IDxhIGhyZWY9Imh0dHA6Ly9kcmFmdC1pZXRmLWRwcml2ZS1l
ZG5zMC1wYWRkaW5nLTAyLnR4dCI+ZHJhZnQtaWV0Zi1kcHJpdmUtZWRuczAtcGFkZGluZy0wMi50
eHQ8L2E+PGJyPglQYWdlcyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyA6IDY8YnI+CURhdGUmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgOiA8YSBocmVmPSJ0ZWw6
MjAxNi0wMS0yNSI+MjAxNi0wMS0yNTwvYT48YnI+PGJyPkFic3RyYWN0Ojxicj4mbmJzcDsmbmJz
cDsgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgdGhlIEVETlMoMCkgJ1BhZGRpbmcnIG9wdGlvbiwg
d2hpY2ggYWxsb3dzPGJyPiZuYnNwOyZuYnNwOyBETlMgY2xpZW50cyBhbmQgc2VydmVycyB0byBw
YWQgcmVxdWVzdCBhbmQgcmVzcG9uc2UgbWVzc2FnZXMgYnkgYTxicj4mbmJzcDsmbmJzcDsgdmFy
aWFibGUgbnVtYmVyIG9mIG9jdGV0cy48YnI+PGJyPjxicj5UaGUgSUVURiBkYXRhdHJhY2tlciBz
dGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczo8YnI+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kcHJpdmUtZWRuczAtcGFkZGluZyI+aHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kcHJpdmUtZWRuczAtcGFkZGlu
ZzwvYT4vPGJyPjxicj5UaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBh
dDo8YnI+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZHBy
aXZlLWVkbnMwLXBhZGRpbmctMDIiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLWRwcml2ZS1lZG5zMC1wYWRkaW5nLTAyPC9hPjxicj48YnI+QSBkaWZmIGZyb20gdGhlIHBy
ZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Ojxicj48YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1kcHJpdmUtZWRuczAtcGFkZGluZy0wMiI+
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtZHByaXZlLWVkbnMw
LXBhZGRpbmctMDI8L2E+PGJyPjxicj48YnI+UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBh
IGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbjxicj51bnRpbCB0
aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IDxhIGhyZWY9Imh0
dHA6Ly90b29scy5pZXRmLm9yZyI+dG9vbHMuaWV0Zi5vcmc8L2E+Ljxicj48YnI+SW50ZXJuZXQt
RHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Ojxicj5mdHA6Ly88
YSBocmVmPSJodHRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cyI+ZnRwLmlldGYub3Jn
L2ludGVybmV0LWRyYWZ0czwvYT4vPGJyPjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj5kbnMtcHJpdmFjeSBtYWlsaW5nIGxpc3Q8YnI+PGEgaHJl
Zj0ibWFpbHRvOmRucy1wcml2YWN5QGlldGYub3JnIj5kbnMtcHJpdmFjeUBpZXRmLm9yZzwvYT48
YnI+PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnMtcHJp
dmFjeSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnMtcHJpdmFjeTwv
YT48YnI+
----_com.android.email_945939224512410--


From nobody Mon Jan 25 09:40:45 2016
Return-Path: <dkg@fifthhorseman.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5C91B2DC6 for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 09:40:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rO9TkyMMosaO for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 09:40:42 -0800 (PST)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEC41A1BDC for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 09:40:42 -0800 (PST)
Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 1D250F991; Mon, 25 Jan 2016 12:40:38 -0500 (EST)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 31B8D20085; Mon, 25 Jan 2016 12:40:40 -0500 (EST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com>, dns-privacy@ietf.org
In-Reply-To: <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com>
References: <20160125171226.8527.6923.idtracker@ietfa.amsl.com> <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com>
User-Agent: Notmuch/0.21+72~gd8c4f1c (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Mon, 25 Jan 2016 12:40:40 -0500
Message-ID: <87fuxlblrb.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/J-cqiWf8VqDG8kT0uDUPBSRiy3A>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 17:40:43 -0000

On Mon 2016-01-25 12:26:59 -0500, Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com> wrote:

> This version addresses comments received since the publication of the
> last draft version, including the WGLC comments.
>
> The only bigger change is that (in line with the comments received)
> I've generalized the text about Non-0x00 padding octects, based on
> text suggested by Andreas Gustaffson

Thanks for the update, Alex.  I think the new revision looks fine.

nit-pick: the Introduction now has the phrase "meta data of could
          still", which looks like an editing error.  i think you can
          just drop the word "of".

regards,

     --dkg


From nobody Mon Jan 25 19:46:49 2016
Return-Path: <alex.mayrhofer.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 410491B2DAA for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 19:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-e8CI3ieQ01 for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 19:46:47 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E12951B2D68 for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 19:46:46 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id e65so7739984pfe.0 for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 19:46:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:subject:message-id:from:to:mime-version:in-reply-to:references :content-type; bh=ntbd7ngFksb1GfrYF+YSdIaloKOrN3exiXIp192w41c=; b=C6MICbpXTmb5SeMUnatnI5JzBzdb/2M35L5GO393jGHHUwnJsrYTMbOhmKsPksZUyA odWB7EO14ZPusiHPSK5pV6HtinTzEud2H4H0Wx4bDoVSR9KyNKl6QTFur8Nbr3K30mUX zCTh/dcir8PG2U+OjIm2cJxnQRDposRw+YZfN2Nobht39GdNIHbUGseO/j1H1ioID9GW qV5NlyvITW/weQWK1BJheVpyI17PYr7u+OB9BryxiM0/hEqQ2mujTQ8GyEYITuHi1LGx AIPg4wY5OsqtzxmO8x1Cn5lOe19/doIKNvzZbzKMfU7exERPb4/WH2j1AVAxDX3wkUCC 30zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:subject:message-id:from:to:mime-version :in-reply-to:references:content-type; bh=ntbd7ngFksb1GfrYF+YSdIaloKOrN3exiXIp192w41c=; b=SiN8Nqg84VSmT3y7iS4+NS/eRH4KuYmnqUxNUHtThn8uCK6SZtW/lx9lf2tbGxY5OA Nw9KsHsB0mI5E2L1ipUUhDloG0W/Vr0qKhlrAGYDkc1w3Von+ZaPzd8yfobZ7DXAwGe/ msG6K6+Ic+amhBofDSHoADwObGfQvd4bCSz+fxYmKbnaOizDzeBRvVSYrR6UKlYREys8 SX904z2u7cQTlbdFWMcoEJb7JL7uocCgzmgh7oZxJJ0vtEkN1C88//QvaN5UCI8Ed6uk sypKRUQdhu9HdBG9AaG1DFUPNo+uRAMTr9jt6NRTXbqR+ofxaXp++w/mOh/DlDGqlbyy axqg==
X-Gm-Message-State: AG10YOSNZOdG37QS2DBzWEFTlu6Bm2lP9PtudXBQjmUN8Sp0OpPkJHrWWCvo8F13XemViA==
X-Received: by 10.98.0.150 with SMTP id 144mr30727371pfa.139.1453780006523; Mon, 25 Jan 2016 19:46:46 -0800 (PST)
Received: from [192.168.1.9] ([123.231.122.71]) by smtp.gmail.com with ESMTPSA id f21sm31918509pfd.6.2016.01.25.19.46.43 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Jan 2016 19:46:45 -0800 (PST)
Date: Tue, 26 Jan 2016 09:14:50 +0530
Message-ID: <70vi61i5lp5vrjgop3nnp6ro.1453779890022@email.android.com>
From: Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com>
To: dns-privacy@ietf.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
MIME-Version: 1.0
In-Reply-To: <87fuxlblrb.fsf@alice.fifthhorseman.net>
References: <20160125171226.8527.6923.idtracker@ietfa.amsl.com> <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com> <87fuxlblrb.fsf@alice.fifthhorseman.net>
Content-Type: multipart/alternative; boundary="--_com.android.email_1025416856735751"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/NrYLEMex5XX-hJhFg-Dmt-uL3QQ>
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 03:46:48 -0000

----_com.android.email_1025416856735751
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGksCgpUaGFua3MgZm9yIHNwb3R0aW5nIHRoYXQuLiAgQWdhaW4sIHRoaXMgZHJhZnQgd2FzIGVk
aXRlZCBmcm9tIGEgbW9iaWxlIHBob25lLiAgIEknbGwgbm90ZSB0aGF0IGZvciBhIGZ1dHVyZSBy
ZXZpc2lvbiAoIEknbSBzdXJlIHRoZXJlIHdpbGwgYmUgY29tbWVudHMgZHVyaW5nIGllc2cgcmV2
aWV3IGFzIHdlbGwpLgoKVGhhbmtzIDotKQpBbGV4IAoKLS0tLSBEYW5pZWwgS2FobiBHaWxsbW9y
IHNjaHJpZWIgLS0tLQoKPk9uIE1vbiAyMDE2LTAxLTI1IDEyOjI2OjU5IC0wNTAwLCBBbGV4IE1h
eXJob2ZlciA8YWxleC5tYXlyaG9mZXIuaWV0ZkBnbWFpbC5jb20+IHdyb3RlOgo+Cj4+IFRoaXMg
dmVyc2lvbiBhZGRyZXNzZXMgY29tbWVudHMgcmVjZWl2ZWQgc2luY2UgdGhlIHB1YmxpY2F0aW9u
IG9mIHRoZQo+PiBsYXN0IGRyYWZ0IHZlcnNpb24sIGluY2x1ZGluZyB0aGUgV0dMQyBjb21tZW50
cy4KPj4KPj4gVGhlIG9ubHkgYmlnZ2VyIGNoYW5nZSBpcyB0aGF0IChpbiBsaW5lIHdpdGggdGhl
IGNvbW1lbnRzIHJlY2VpdmVkKQo+PiBJJ3ZlIGdlbmVyYWxpemVkIHRoZSB0ZXh0IGFib3V0IE5v
bi0weDAwIHBhZGRpbmcgb2N0ZWN0cywgYmFzZWQgb24KPj4gdGV4dCBzdWdnZXN0ZWQgYnkgQW5k
cmVhcyBHdXN0YWZmc29uCj4KPlRoYW5rcyBmb3IgdGhlIHVwZGF0ZSwgQWxleC4gIEkgdGhpbmsg
dGhlIG5ldyByZXZpc2lvbiBsb29rcyBmaW5lLgo+Cj5uaXQtcGljazogdGhlIEludHJvZHVjdGlv
biBub3cgaGFzIHRoZSBwaHJhc2UgIm1ldGEgZGF0YSBvZiBjb3VsZAo+ICAgICAgICAgIHN0aWxs
Iiwgd2hpY2ggbG9va3MgbGlrZSBhbiBlZGl0aW5nIGVycm9yLiAgaSB0aGluayB5b3UgY2FuCj4g
ICAgICAgICAganVzdCBkcm9wIHRoZSB3b3JkICJvZiIuCj4KPnJlZ2FyZHMsCj4KPiAgICAgLS1k
a2cK
----_com.android.email_1025416856735751
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PHAgZGlyPSJsdHIiPkhpLDwvcD4KPHAgZGlyPSJsdHIiPlRoYW5rcyBmb3Igc3BvdHRpbmcgdGhh
dC4uJm5ic3A7IEFnYWluLCB0aGlzIGRyYWZ0IHdhcyBlZGl0ZWQgZnJvbSBhIG1vYmlsZSBwaG9u
ZS4mbmJzcDsmbmJzcDsgSSdsbCBub3RlIHRoYXQgZm9yIGEgZnV0dXJlIHJldmlzaW9uICggSSdt
IHN1cmUgdGhlcmUgd2lsbCBiZSBjb21tZW50cyBkdXJpbmcgaWVzZyByZXZpZXcgYXMgd2VsbCku
PC9wPgo8cCBkaXI9Imx0ciI+VGhhbmtzIDotKTxicj4KQWxleCA8L3A+Cjxicj48YnI+LS0tLSBE
YW5pZWwgS2FobiBHaWxsbW9yIHNjaHJpZWIgLS0tLTxicj48YnI+T24gTW9uIDIwMTYtMDEtMjUg
MTI6MjY6PGEgaHJlZj0idGVsOjU5IC0wNTAwIj41OSAtMDUwMDwvYT4sIEFsZXggTWF5cmhvZmVy
ICZsdDs8YSBocmVmPSJtYWlsdG86YWxleC5tYXlyaG9mZXIuaWV0ZkBnbWFpbC5jb20iPmFsZXgu
bWF5cmhvZmVyLmlldGZAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PGJyPjxicj4mZ3Q7IFRoaXMg
dmVyc2lvbiBhZGRyZXNzZXMgY29tbWVudHMgcmVjZWl2ZWQgc2luY2UgdGhlIHB1YmxpY2F0aW9u
IG9mIHRoZTxicj4mZ3Q7IGxhc3QgZHJhZnQgdmVyc2lvbiwgaW5jbHVkaW5nIHRoZSBXR0xDIGNv
bW1lbnRzLjxicj4mZ3Q7PGJyPiZndDsgVGhlIG9ubHkgYmlnZ2VyIGNoYW5nZSBpcyB0aGF0IChp
biBsaW5lIHdpdGggdGhlIGNvbW1lbnRzIHJlY2VpdmVkKTxicj4mZ3Q7IEkndmUgZ2VuZXJhbGl6
ZWQgdGhlIHRleHQgYWJvdXQgTm9uLTB4MDAgcGFkZGluZyBvY3RlY3RzLCBiYXNlZCBvbjxicj4m
Z3Q7IHRleHQgc3VnZ2VzdGVkIGJ5IEFuZHJlYXMgR3VzdGFmZnNvbjxicj48YnI+VGhhbmtzIGZv
ciB0aGUgdXBkYXRlLCBBbGV4LiZuYnNwOyBJIHRoaW5rIHRoZSBuZXcgcmV2aXNpb24gbG9va3Mg
ZmluZS48YnI+PGJyPm5pdC1waWNrOiB0aGUgSW50cm9kdWN0aW9uIG5vdyBoYXMgdGhlIHBocmFz
ZSAibWV0YSBkYXRhIG9mIGNvdWxkPGJyPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBzdGlsbCIsIHdoaWNoIGxvb2tzIGxpa2UgYW4gZWRpdGlu
ZyBlcnJvci4mbmJzcDsgaSB0aGluayB5b3UgY2FuPGJyPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBqdXN0IGRyb3AgdGhlIHdvcmQgIm9mIi48
YnI+PGJyPnJlZ2FyZHMsPGJyPjxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLS1ka2c8YnI+
----_com.android.email_1025416856735751--


From nobody Mon Jan 25 21:50:37 2016
Return-Path: <praspati@cisco.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942971B2F06 for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 21:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kfhdecPT-EL for <dns-privacy@ietfa.amsl.com>; Mon, 25 Jan 2016 21:50:34 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 286A31B2F05 for <dns-privacy@ietf.org>; Mon, 25 Jan 2016 21:50:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1092; q=dns/txt; s=iport; t=1453787434; x=1454997034; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Ii1heZaEbq9wJgLB5LQecdwNv9DsQLNFcoVxlHskRSk=; b=RPKFV/8UsD8MdHCwGw2Bq7zgLj6j2gTY8Rm3+cORMqr3sXaas+aFgNxQ 9HSQfFbvTcXbwZl/ja8F1g+onhWJhiC0sykQyrBqGIMdtBLFqJX1RMs8K WGUx2nXwc2e4xV62hx/1jEXUs479QcYsKMXaOmgjXLqPywuP/+UAchk3T M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAgCKCKdW/4wNJK1egzpSbQaIUbIYA?= =?us-ascii?q?Q2BYxgMhWsCgU44FAEBAQEBAQGBCoRCAQEEAQEBGh00GwIBCA4oECEGCyUCBAE?= =?us-ascii?q?SiAYDEg66IQ2EEAEBAQEBAQEBAQEBAQEBAQEBAQETBIYyhG2CSYY9BZZ5AYVFh?= =?us-ascii?q?hiBeIFehESHPIEbhwGDb4NSAR4BAUKDaWqGQHwBAQE?=
X-IronPort-AV: E=Sophos;i="5.22,348,1449532800"; d="scan'208";a="65165472"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Jan 2016 05:50:33 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u0Q5oWFs006221 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 26 Jan 2016 05:50:33 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 26 Jan 2016 00:50:32 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.009; Tue, 26 Jan 2016 00:50:32 -0500
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Tim Wicinski <tjw.ietf@gmail.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
Thread-Index: AQHRV/14p0x4O0U3PkGr0VyV68Kicw==
Date: Tue, 26 Jan 2016 05:50:32 +0000
Message-ID: <D2CC48F8.FBE5F%praspati@cisco.com>
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.9.151119
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.45.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BABD045945BCC949A74922A71FC53516@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/3UzB1FhqbS5QzoInF2Be7jEmDgY>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 05:50:35 -0000

On 1/12/16, 1:56 PM, "dns-privacy on behalf of Tim Wicinski"
<dns-privacy-bounces@ietf.org on behalf of tjw.ietf@gmail.com> wrote:

>The chairs realized earlier today that we encouraged this draft to be
>created, but once it was, we forgot to start a formal Call for Adoption.
>  With the feedback already, this document looks ready for adoption and
>being worked on.
>
>This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles
>
>The draft is available here:
>https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>
>Please review this draft to see if you think it is suitable for adoption
>by DPRIVE, and comments to the list, clearly stating your view.

I support adoption of the draft.

-Prashanth

>
>Please also indicate if you are willing to contribute text, review, etc.
>
>This call for adoption ends 26 January 2016
>
>Thanks,
>tim wicinski
>DPRIVE co-chair
>
>_______________________________________________
>dns-privacy mailing list
>dns-privacy@ietf.org
>https://www.ietf.org/mailman/listinfo/dns-privacy


From nobody Tue Jan 26 20:32:16 2016
Return-Path: <warren@kumari.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AADE1AC3B2 for <dns-privacy@ietfa.amsl.com>; Tue, 26 Jan 2016 20:32:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxCjlUFgdavI for <dns-privacy@ietfa.amsl.com>; Tue, 26 Jan 2016 20:32:13 -0800 (PST)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3441AC39A for <dns-privacy@ietf.org>; Tue, 26 Jan 2016 20:32:13 -0800 (PST)
Received: by mail-yk0-x233.google.com with SMTP id v14so227510233ykd.3 for <dns-privacy@ietf.org>; Tue, 26 Jan 2016 20:32:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=pWxu2UuN4zct1NNX6ebxkq+43DXzognuPqePXMdsx4Q=; b=s+JR13nxGhdGuVmTdQ6vxEbISJZ8+VfBOq/5u4E+MhEUjhtC2GQgI9RCLs5ckL+IQ1 yZ+lW6uJowEYmlYsxVpXzx3OQRHvzpyB7bcc9PQk58Bg6+cPSmEgmvhWeEqDOvlXQvqz qNXCz1M/7z2a4aH3YJa0ejSj77Ltn7LZP92F2qlMujPUCHaYQERr5Y+BRVLgLQQAc+Li Ix/8AvuQ+DZW3jDkH42e3gg2JDiEnB1SpPdI9U8cE/TAHjJ2qZK85en4Ap38xDldy7jT 62GiFrPmqGg5AkTtTSYupYDmD0TPvUhNTM1NFT010MnxUu7S1SO2nQKLHrz9gLvjQOlA FEjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=pWxu2UuN4zct1NNX6ebxkq+43DXzognuPqePXMdsx4Q=; b=Xm264Pv9eYXSqYUNAOpvZlyT2yGr1RaTM2iphBnKvgfs4KwIORg+SsniNmLmekY97N MsnMPYSVkKnvQ68URekjfiQ9htUBSBmVAXEsVi4hJ1qDtcytffGQN6YaFiiIARAOeNq7 KPsBszbdpYiQgs2OxdTJDLSNMz7tI2CXxDsYEHRfUNsVU7xfdsEx1lJczSwKcGBSP0+G gU9QxN8SZnUf3YKModJWUBw6TeUI1vbkqjtFZZjgwoj7W8U/QI+8YiWQG0HZp4RiYRa8 Q2BciS/mSVJvYaGNTQzVU5bYrApBaNLSwFriTW1XvgdGck1BdbNlyzCdbMvfhRnVlq5V EmRA==
X-Gm-Message-State: AG10YORJY08AjzXlk7ooi/bQIR0vgg5iWUQu35w0vkZATc5mrb9iz0uscsvLX0pNeXoW6lxsi5hzVTP2eRxsch9w
X-Received: by 10.13.227.1 with SMTP id m1mr14933105ywe.249.1453869132427; Tue, 26 Jan 2016 20:32:12 -0800 (PST)
MIME-Version: 1.0
References: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
In-Reply-To: <cb62be23-c6cc-01f9-adff-62a0da0e1bcd@gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 27 Jan 2016 04:32:02 +0000
Message-ID: <CAHw9_iJm9TMjgTF8iDVXmJCg=4GB1oV=kR6qxpx3Rua7D7K-AA@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c07d0fa306b6b052a4949e0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/YaAxW9NY3yE2sIdKJ6Z43L_sTj8>
Subject: Re: [dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2016 04:32:14 -0000

--94eb2c07d0fa306b6b052a4949e0
Content-Type: text/plain; charset=UTF-8

Dear authors,

We see consensus to adopt this document.

Please resubmit as draft-ietf-dprive-dtls-and-tls-profies.

Also, thanks to the WG for review and feedback.
W

On Tue, Jan 12, 2016 at 1:56 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> The chairs realized earlier today that we encouraged this draft to be
> created, but once it was, we forgot to start a formal Call for Adoption.
>   With the feedback already, this document looks ready for adoption and
> being worked on.
>
> This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-profiles/
>
> Please review this draft to see if you think it is suitable for adoption
> by DPRIVE, and comments to the list, clearly stating your view.
>
> Please also indicate if you are willing to contribute text, review, etc.
>
> This call for adoption ends 26 January 2016
>
> Thanks,
> tim wicinski
> DPRIVE co-chair
>
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy
>

--94eb2c07d0fa306b6b052a4949e0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear authors,<div><br></div><div>We see consensus to adopt=
 this document.</div><div><br></div><div>Please resubmit as draft-ietf-dpri=
ve-dtls-and-tls-profies.</div><div><br></div><div>Also, thanks to the WG fo=
r review and feedback.</div><div>W<br><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr">On Tue, Jan 12, 2016 at 1:56 PM Tim Wicinski &lt;<a href=3D"mail=
to:tjw.ietf@gmail.com">tjw.ietf@gmail.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">The chairs realized earlier today that we encouraged =
this draft to be<br>
created, but once it was, we forgot to start a formal Call for Adoption.<br=
>
=C2=A0 With the feedback already, this document looks ready for adoption an=
d<br>
being worked on.<br>
<br>
This starts a Call for Adoption for draft-dgr-dprive-dtls-and-tls-profiles<=
br>
<br>
The draft is available here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-dgr-dprive-dtls-and-tls-p=
rofiles/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/doc/draft-dgr-dprive-dtls-and-tls-profiles/</a><br>
<br>
Please review this draft to see if you think it is suitable for adoption<br=
>
by DPRIVE, and comments to the list, clearly stating your view.<br>
<br>
Please also indicate if you are willing to contribute text, review, etc.<br=
>
<br>
This call for adoption ends 26 January 2016<br>
<br>
Thanks,<br>
tim wicinski<br>
DPRIVE co-chair<br>
<br>
_______________________________________________<br>
dns-privacy mailing list<br>
<a href=3D"mailto:dns-privacy@ietf.org" target=3D"_blank">dns-privacy@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dns-privacy" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dns-privacy</=
a><br>
</blockquote></div></div></div>

--94eb2c07d0fa306b6b052a4949e0--


From nobody Wed Jan 27 17:02:29 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BCD31A001D; Wed, 27 Jan 2016 17:02:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20160128010226.22455.67973.idtracker@ietfa.amsl.com>
Date: Wed, 27 Jan 2016 17:02:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/ZbSlov2-pi-tZ1aLZhfFMOCmaGI>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, draft-ietf-dprive-edns0-padding@ietf.org, terry.manderson@icann.org, dns-privacy@ietf.org, dprive-chairs@ietf.org
Subject: [dns-privacy] Last Call: <draft-ietf-dprive-edns0-padding-02.txt> (The EDNS(0) Padding Option) to Proposed Standard
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 01:02:26 -0000

The IESG has received a request from the DNS PRIVate Exchange WG (dprive)
to consider the following document:
- 'The EDNS(0) Padding Option'
  <draft-ietf-dprive-edns0-padding-02.txt> 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 comments to the
ietf@ietf.org mailing lists by 2016-02-10. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document specifies the EDNS(0) 'Padding' option, which allows
   DNS clients and servers to pad request and response messages by a
   variable number of octets.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dprive-edns0-padding/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dprive-edns0-padding/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Thu Jan 28 02:44:57 2016
Return-Path: <gson@gson.org>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D6B1B34B6 for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 02:44:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1Zehjus0lqA for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 02:44:55 -0800 (PST)
Received: from gusto.araneus.fi (gusto.araneus.fi [185.55.84.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0BDC61B34B5 for <dns-privacy@ietf.org>; Thu, 28 Jan 2016 02:44:54 -0800 (PST)
Received: from guava.gson.org (unknown [10.0.1.240]) by gusto.araneus.fi (Postfix) with ESMTP id BD70E8BE621; Thu, 28 Jan 2016 10:44:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=araneus.fi; s=mail; t=1453977892; bh=iMjjZnZ1s9XrR7xSvXoTohcF+kz7kUlipBd9/j+TzP0=; h=Date:To:Cc:Subject:In-Reply-To:References:From; b=Nn8J0WwqlM4wgZ5fQKPYMJhE9mchLCBMQOKB31iVPmKmksIgaP/IXunr8cEIXPzWi /4gasPjXVKT5ogVlzoBIIrsbKd8c+W5gSDK2C8ekSBVT7++LaAfaGyS9ehaZMEDOP8 KWGnsSPIWABYCckQZoL2MWVNN3kCDK1zLyTFVgoM=
Received: by guava.gson.org (Postfix, from userid 101) id 0A03E74508B; Thu, 28 Jan 2016 12:44:51 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22185.61730.630604.509811@guava.gson.org>
Date: Thu, 28 Jan 2016 12:44:50 +0200
To: Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com>
In-Reply-To: <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com>
References: <20160125171226.8527.6923.idtracker@ietfa.amsl.com> <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
From: Andreas Gustafsson <gson@araneus.fi>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/m5E4elveQByeGg-4h4M47iH1EJw>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 10:44:57 -0000

Alex Mayrhofer wrote:
> This version addresses comments received since the publication of the
> last draft version, including the WGLC comments.

Looks good to me.  Just a couple of nits:

In Section 6, Security Considerations, "provides only a benefit"
should be "only provides a benefit".

In section 7, Acknowledgements, "Gustaffson" should be "Gustafsson".
-- 
Andreas Gustafsson, gson@araneus.fi


From nobody Thu Jan 28 06:05:05 2016
Return-Path: <alex.mayrhofer.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A233E1A7D85 for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 06:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.336
X-Spam-Level: *
X-Spam-Status: No, score=1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oc6aobwqCb-H for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 06:05:03 -0800 (PST)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 922901A6FED for <dns-privacy@ietf.org>; Thu, 28 Jan 2016 06:05:03 -0800 (PST)
Received: by mail-pa0-x22c.google.com with SMTP id yy13so23686664pab.3 for <dns-privacy@ietf.org>; Thu, 28 Jan 2016 06:05:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:subject:message-id:from:to:cc:mime-version:in-reply-to :references:content-type; bh=nmz0vj+0PK6rluOOQRX+AdwVz7tnOqlcl2XENW1WxlY=; b=uAFxTByWjAxOYbL7ArdXzIwPENq4RU4z+aNAH+CFJT4MfIWGUShDHDWnJXim2QiBmN 5IEco7jIHlwIagMAF6wt5vfBBSGfRsh9M3LJbmsCq4rck6gsBrKzSQMWwJ9u+crWTI+T 1xPy3TufRQ4mn5XNVXtkuzibVFgdFezdr9qKqYwIPkw6ImToGWLrAN7WhD4sPuM0GKch ZhN9qZW6yf8txJnKjnL7Q1hQFJpvLHepOn8cEtM/WfUMsQ9yUMBnvGaVudOz24gBLxW6 GnjWMC5caeeZsW6i3JVY7dcROJkFXCTxIlMM5ks0ln/5U1LmsUDzNGVQu4qksM4aDc87 1VQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:subject:message-id:from:to:cc:mime-version :in-reply-to:references:content-type; bh=nmz0vj+0PK6rluOOQRX+AdwVz7tnOqlcl2XENW1WxlY=; b=g0EooZ/4LUl/RX63XnigY7DXDevXM0KXTO6bydMg5tok50gRCM/k5wwdIwPi+k7TKa Vc05YiIGA3W3Wde1ifW2JHz7nkQALRR5IRtuaqbbx+jEcCOJ5RaZNiquFCubbMNKMSNe b5EEc2188LyIV4spUuiMFB+d71FpVS6f6Hj08rPI/j1q85tEe7ybLJ3j7GQz2CGf65um FhU+1HOY7PUe0IXP35O/T2IJTUYYAGZQcQLgrFXL7wCzzg8r2BZa0OTokfiNd9/ckNVf WjNUIjvnjov/+Z5izuZewRt2JAX3x3BlYiOQYIfQMgFZE7OvQEJpwXbh11ZhNWrEV8Hd gxAA==
X-Gm-Message-State: AG10YORYvhjlX808Owg3lLiszCP6pE4g7EDQgIvYOz2j6fVEd/9Y8OM4yDSPxUK73EGCtQ==
X-Received: by 10.66.141.11 with SMTP id rk11mr4569730pab.156.1453989903154; Thu, 28 Jan 2016 06:05:03 -0800 (PST)
Received: from [100.71.89.175] ([61.245.163.218]) by smtp.gmail.com with ESMTPSA id l9sm16789936pfb.29.2016.01.28.06.04.46 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jan 2016 06:05:01 -0800 (PST)
Date: Thu, 28 Jan 2016 18:42:25 +0530
Message-ID: <73ol85g5epcidr9rvtttqacs.1453986745622@email.android.com>
From: Alex Mayrhofer <alex.mayrhofer.ietf@gmail.com>
To: Andreas Gustafsson <gson@araneus.fi>
MIME-Version: 1.0
In-Reply-To: <22185.61730.630604.509811@guava.gson.org>
References: <20160125171226.8527.6923.idtracker@ietfa.amsl.com> <09kou9shvmaq4c6ufk60ha7s.1453742493879@email.android.com> <22185.61730.630604.509811@guava.gson.org>
Content-Type: multipart/alternative; boundary="--_com.android.email_314468437731110"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/Y5BcUv3mm1YKY12nqtHmkx-0D6k>
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] I-D Action: draft-ietf-dprive-edns0-padding-02.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 14:05:04 -0000

----_com.android.email_314468437731110
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

QW5kcmVhcywgCgpUaGFua3MgZm9yIHJldmlld2luZy4gU29ycnkgZm9yIHRoZSB0eXBvIGluIHlv
dXIgbmFtZSAtIEkgd2lsbCBhZGRyZXNzIHRoaXMgdG9nZXRoZXIgd2l0aCBjaGFuZ2VzIGZyb20g
aWVzZyBwcm9jZXNzaW5nIGJlZm9yZSBwdWJsaWNhdGlvbiBvZiB0aGUgcmZjLgoKVGhhbmtzLApB
bGV4IAoKLS0tLSBBbmRyZWFzIEd1c3RhZnNzb24gc2NocmllYiAtLS0tCgo+QWxleCBNYXlyaG9m
ZXIgd3JvdGU6Cj4+IFRoaXMgdmVyc2lvbiBhZGRyZXNzZXMgY29tbWVudHMgcmVjZWl2ZWQgc2lu
Y2UgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZQo+PiBsYXN0IGRyYWZ0IHZlcnNpb24sIGluY2x1ZGlu
ZyB0aGUgV0dMQyBjb21tZW50cy4KPgo+TG9va3MgZ29vZCB0byBtZS4gIEp1c3QgYSBjb3VwbGUg
b2Ygbml0czoKPgo+SW4gU2VjdGlvbiA2LCBTZWN1cml0eSBDb25zaWRlcmF0aW9ucywgInByb3Zp
ZGVzIG9ubHkgYSBiZW5lZml0Igo+c2hvdWxkIGJlICJvbmx5IHByb3ZpZGVzIGEgYmVuZWZpdCIu
Cj4KPkluIHNlY3Rpb24gNywgQWNrbm93bGVkZ2VtZW50cywgIkd1c3RhZmZzb24iIHNob3VsZCBi
ZSAiR3VzdGFmc3NvbiIuCj4tLSAKPkFuZHJlYXMgR3VzdGFmc3NvbiwgZ3NvbkBhcmFuZXVzLmZp
Cg==
----_com.android.email_314468437731110
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PHAgZGlyPSJsdHIiPkFuZHJlYXMsIDwvcD4KPHAgZGlyPSJsdHIiPlRoYW5rcyBmb3IgcmV2aWV3
aW5nLiBTb3JyeSBmb3IgdGhlIHR5cG8gaW4geW91ciBuYW1lIC0gSSB3aWxsIGFkZHJlc3MgdGhp
cyB0b2dldGhlciB3aXRoIGNoYW5nZXMgZnJvbSBpZXNnIHByb2Nlc3NpbmcgYmVmb3JlIHB1Ymxp
Y2F0aW9uIG9mIHRoZSByZmMuPC9wPgo8cCBkaXI9Imx0ciI+VGhhbmtzLDxicj4KQWxleCA8L3A+
Cjxicj48YnI+LS0tLSBBbmRyZWFzIEd1c3RhZnNzb24gc2NocmllYiAtLS0tPGJyPjxicj5BbGV4
IE1heXJob2ZlciB3cm90ZTo8YnI+Jmd0OyBUaGlzIHZlcnNpb24gYWRkcmVzc2VzIGNvbW1lbnRz
IHJlY2VpdmVkIHNpbmNlIHRoZSBwdWJsaWNhdGlvbiBvZiB0aGU8YnI+Jmd0OyBsYXN0IGRyYWZ0
IHZlcnNpb24sIGluY2x1ZGluZyB0aGUgV0dMQyBjb21tZW50cy48YnI+PGJyPkxvb2tzIGdvb2Qg
dG8gbWUuJm5ic3A7IEp1c3QgYSBjb3VwbGUgb2Ygbml0czo8YnI+PGJyPkluIFNlY3Rpb24gNiwg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMsICJwcm92aWRlcyBvbmx5IGEgYmVuZWZpdCI8YnI+c2hv
dWxkIGJlICJvbmx5IHByb3ZpZGVzIGEgYmVuZWZpdCIuPGJyPjxicj5JbiBzZWN0aW9uIDcsIEFj
a25vd2xlZGdlbWVudHMsICJHdXN0YWZmc29uIiBzaG91bGQgYmUgIkd1c3RhZnNzb24iLjxicj4t
LSA8YnI+QW5kcmVhcyBHdXN0YWZzc29uLCA8YSBocmVmPSJtYWlsdG86Z3NvbkBhcmFuZXVzLmZp
Ij5nc29uQGFyYW5ldXMuZmk8L2E+PGJyPg==
----_com.android.email_314468437731110--


From nobody Thu Jan 28 09:29:20 2016
Return-Path: <ted.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9767A1A8AF5 for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 09:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMD0emAVxqqx for <dns-privacy@ietfa.amsl.com>; Thu, 28 Jan 2016 09:29:17 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFA7F1A8AF4 for <dns-privacy@ietf.org>; Thu, 28 Jan 2016 09:29:15 -0800 (PST)
Received: by mail-qg0-x231.google.com with SMTP id 6so44668981qgy.1 for <dns-privacy@ietf.org>; Thu, 28 Jan 2016 09:29:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=5jrI7rx0NJhgKtDwYpG1NvajSD62UeDm0u428kKWeeQ=; b=iHqjhvBF2ED+rjWPNI7tR0frjPL3VDF7tAyRCVpOxhGiQH7mWk5LN2oZE26hbTbqeA K97x9E4OkdoA1rjQXsEUcuuzPXwsIbFwhEu6x4aHEqLvCElWaudGVLEerAThIaKwcPv8 hKnipUDJkwh56pdJJk0IrmKkDEzLq6Tkwk9UA/bvX1l7aU6xLlyaOlnlxZNE1mc7e58H 7ZU00Ip26y7YS4Ml3VYQXcgL6hj7rPUUOddGhoTeUggv09HlFXcFDZGwXbNxstLOMeOX /vtPcJHCstBbQdK7ZKVanbAsZL8kt//q/dzuPXPF49iuvMnSOLv8rJ4ls0czYDcH+s1i CAyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=5jrI7rx0NJhgKtDwYpG1NvajSD62UeDm0u428kKWeeQ=; b=cDRcqpzpokeNLOMS1dV1ZaYOZeEPcxkKRcpmiqU274VsRgt4wxMzq3VsH6sqCEapLv +8BdM8F22ibDi+vnSpOy6VzjlkSX6QYxj1m+X/7/pkqvODUJZPwlj2jlEvZFjncIxWAA v/RfZaBHu7web13AkScp+DYdv0hX6DyUIpoSpP3cLG4RkVlZ7ozPhvOqdcRwFrIJH1fP uRBzHtpheinzq+BrM7MLBFYol/3sH4mzg/Y1eoTexntGOAlu31an0JtgT7LCTzilFno/ TEikA/DcRwvjAMmDO6B2Eq4AaA5x46a3ZxrSrGNJHZSU1QeLMYBAFRd+Gj4rSm6Gl228 mXaw==
X-Gm-Message-State: AG10YOStXAt0tg5Uxf7Vhouhj7R0g0flez1GpNRULqb43K8+VrIuf6CEO+75MHDuLnC9zf3gvPWzFICNlfTR3g==
X-Received: by 10.141.28.149 with SMTP id f143mr5333136qhe.66.1454002155153; Thu, 28 Jan 2016 09:29:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.14.211 with HTTP; Thu, 28 Jan 2016 09:28:55 -0800 (PST)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 28 Jan 2016 09:28:55 -0800
Message-ID: <CA+9kkMB0zL4KwoFk9-9otbWgtu9=uHTNeEiD=-qsStx+NsvBUQ@mail.gmail.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>,  Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary=001a11422e8ef5f8ac052a68414e
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/9wPp2sXZUGmdfhOn_JUCZc74b3w>
Subject: [dns-privacy] ARCING BoF and Mailing list
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 17:29:18 -0000

--001a11422e8ef5f8ac052a68414e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Andrew Sullivan, Suzanne Woolf and I have put a request in for a BoF at
IETF 95 (arcing <http://tools.ietf.org/bof/trac/>) that is trying to take a
slightly different squint at how to manage alternative resolution contexts
like that of mDNS, .onion, or similar.  We're trying to look beyond recent
issues about RFC 6761 and special use name
=E2=80=8B to see if there are different architectural approaches to the gen=
eral
problem.

=E2=80=8B
There's a stab at a problem statement draft
<https://www.ietf.org/internet-drafts/draft-hardie-resolution-contexts-01.t=
xt>
available, building off of work that's already been done in DNSOP and other
places.  There is also a mailing list set up for early discussion (
arcing@ietf.org), and we'd appreciate anyone interested in the topic
joining the discussion there.

Apologies if you get multiple copies; it must mean we *really* want you to
join.

thanks,

Ted, Andrew, Suzanne

--001a11422e8ef5f8ac052a68414e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:garamond=
,serif;font-size:small"><div style=3D"font-family:garamond,serif;font-size:=
small">Andrew Sullivan, Suzanne Woolf and I have put a request in for a BoF=
 at IETF 95 (<a href=3D"http://tools.ietf.org/bof/trac/" target=3D"_blank">=
arcing</a>)
 that is trying to take a slightly different squint at how to manage=20
alternative resolution contexts like that of mDNS, .onion, or similar.=C2=
=A0=20
We&#39;re trying to look beyond recent issues about RFC 6761 and special us=
e
 name<div class=3D"gmail_default" style=3D"font-family:garamond,serif;font-=
size:small;display:inline">=E2=80=8B to see if there are different architec=
tural approaches to the general problem.<br><br>=E2=80=8B</div>There&#39;s =
a stab at<a href=3D"https://www.ietf.org/internet-drafts/draft-hardie-resol=
ution-contexts-01.txt" target=3D"_blank"> a problem statement draft</a>
 available, building off of work that&#39;s already been done in DNSOP and=
=20
other places.=C2=A0 There is also a mailing list set up for early discussio=
n (<a href=3D"mailto:arcing@ietf.org" target=3D"_blank">arcing@ietf.org</a>=
), and we&#39;d appreciate anyone interested in the topic joining the discu=
ssion there. <br><br></div><div style=3D"font-family:garamond,serif;font-si=
ze:small">Apologies if you get multiple copies; it must mean we *really* wa=
nt you to join.<br></div><div style=3D"font-family:garamond,serif;font-size=
:small"><br></div><div style=3D"font-family:garamond,serif;font-size:small"=
>thanks,<br><br></div>Ted, Andrew, Suzanne=C2=A0 </div></div>

--001a11422e8ef5f8ac052a68414e--


From nobody Sat Jan 30 13:02:28 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dns-privacy@ietf.org
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BCF1AC3D6; Sat, 30 Jan 2016 13:02:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160130210227.4558.81648.idtracker@ietfa.amsl.com>
Date: Sat, 30 Jan 2016 13:02:27 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/NiZTS99x3WBzr1thbrfPOsyeLZE>
Cc: dns-privacy@ietf.org
Subject: [dns-privacy] I-D Action: draft-ietf-dprive-dtls-and-tls-profiles-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jan 2016 21:02:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DNS PRIVate Exchange Working Group of the IETF.

        Title           : Authentication and (D)TLS Profile for DNS-over-TLS and DNS-over-DTLS
        Authors         : Sara Dickinson
                          Daniel Kahn Gillmor
                          Tirumaleswar Reddy
	Filename        : draft-ietf-dprive-dtls-and-tls-profiles-00.txt
	Pages           : 17
	Date            : 2016-01-30

Abstract:
   This document describes how a DNS client can use a domain name to
   authenticate a DNS server that uses Transport Layer Security (TLS)
   and Datagram TLS (DTLS).  Additionally, it defines (D)TLS profiles
   for DNS clients and servers implementing DNS-over-TLS and DNS-over-
   DTLS.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dtls-and-tls-profiles/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dprive-dtls-and-tls-profiles-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

