[dns-privacy] Mirja Kühlewind's No Objection on draft-ietf-dprive-dnsodtls-13: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 12 December 2016 13:14 UTC

Return-Path: <ietf@kuehlewind.net>
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 2E11A129AF5; Mon, 12 Dec 2016 05:14:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.39.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148154847118.22392.76566019423780375.idtracker@ietfa.amsl.com>
Date: Mon, 12 Dec 2016 05:14:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/j4mGFOwve_R1ub6CoBZ3WWrUY24>
Cc: tjw.ietf@gmail.com, dns-privacy@ietf.org, draft-ietf-dprive-dnsodtls@ietf.org, dprive-chairs@ietf.org
Subject: [dns-privacy] Mirja Kühlewind's No Objection on draft-ietf-dprive-dnsodtls-13: (with COMMENT)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Dec 2016 13:14:31 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-dprive-dnsodtls-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dprive-dnsodtls/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Regarding the shepherd write-up: There is no requirement for an
implementation section. There is a recommendation to have one, to track
implementations efforts during the draft's live-time, but such a section
is usually removed on publication as RFC as this information easily
out-dates. There is another recommendation to have a section explaining
the goals and/or next steps after the end of a (successful) experiment. I
personally don't think this is required here, given that I understand the
experiment is to figure out if this will be adopted (given there is
stable reference).

One small question on the text in the draft:
"For the client, state should be destroyed when
   disconnecting from the network (e.g., associated IP interface is
   brought down). "
Does this mean all state including state used for session resumption?