Re: [dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls

Shane Kerr <shane@time-travellers.org> Wed, 27 May 2015 13:58 UTC

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 E29081B29CA for <dns-privacy@ietfa.amsl.com>; Wed, 27 May 2015 06:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 ETWIAZ2dsLgp for <dns-privacy@ietfa.amsl.com>; Wed, 27 May 2015 06:58:18 -0700 (PDT)
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 4E3821ACF5E for <dns-privacy@ietf.org>; Wed, 27 May 2015 06:58:17 -0700 (PDT)
Received: from 143-245-128-083.dynamic.caiway.nl ([83.128.245.143] helo=casual) 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 1YxbqU-0005jx-6v; Wed, 27 May 2015 13:58:10 +0000
Date: Wed, 27 May 2015 13:58:08 +0000
From: Shane Kerr <shane@time-travellers.org>
To: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <20150527135808.64d1bf68@casual>
In-Reply-To: <555C942F.2090007@gmail.com>
References: <555C942F.2090007@gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; 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/4Glk8JQXHXioF8xmgHA1H01AzPk>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls
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: <http://www.ietf.org/mail-archive/web/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 May 2015 13:58:20 -0000

Tim and all,

On Wed, 20 May 2015 10:03:27 -0400
Tim Wicinski <tjw.ietf@gmail.com> wrote:

> During the previous Call for Adoption a number of participants expressed 
> interest in adopting this work.  WG members felt it needed some 
> improvements, but thought it had potential. The authors addressed the 
> issues and feel it meets what the working group was seeking, and have 
> requested that we initiate a call for adoption.
> 
> If the working group adopts this document, it only means it wishes to 
> study this solution more carefully.  The working group may still 
> determine to not move forward with it.
> 
> The draft is available here: 
> https://datatracker.ietf.org/doc/draft-wing-dprive-dnsodtls/
> Please review this draft to see if you think it is suitable for adoption 
> by , and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.

This document is deep and wide, so I doubt that it can actually go
forward as a single document. It seems to contain a mix of ideas,
suggestions, and discussion, some related to DNSoD in particular and
some that will apply to any encrypted DNS transport (for example, the
increased packet size indeed needs to be addressed somehow, the proposal
to multiplex has merit, the issue of which port to use will exist
everywhere, ...).

I think that I support adoption as a discussion piece. My feeling is
that it will end up as 2 or 3 documents in the end - possibly with only
1 or 2 ending up as RFCs, of course. :)

I am willing to review!

Cheers,

--
Shane