IETF Logo Mail Archive

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

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Tue, 26 May 2015 04:58 UTC

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 6206A1A1B05 for <dns-privacy@ietfa.amsl.com>; Mon, 25 May 2015 21:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 PjUYRfG9wsSf for <dns-privacy@ietfa.amsl.com>; Mon, 25 May 2015 21:58:28 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7CC91A1ADB for <dns-privacy@ietf.org>; Mon, 25 May 2015 21:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21254; q=dns/txt; s=iport; t=1432616308; x=1433825908; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=R37XomzoosO8r6S1MvAvRGhwBRRDblc8SAInxeB15Xs=; b=OEda4x7+BHRGcdvueXUpNVrjWYIj91MFYZq/aDdH2gNBokYrjf3wxy67 hKw44l0iWQJj/vaHElq+5Swz6+5I98JZH0pDwp0HJFAsR7JWjieZHnP5Y deDbm5n9/X2wvHbtG80rNUEG9fQ4PPsLfypvve1tAfx/yr4Q8MOWd75t4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BYBQBE/GNV/5JdJa1cgkVLVF4Ggxm/DoJIhXcCHIEoOxEBAQEBAQEBgQqEIgEBAQQODwYKOBQQAgEIEQMBAQELHQMCAgIfERQJCAIEAQ0FCBOHfAMSDa8hnj8NhQYBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIs6gk2BbRoWCg0EBgEGgmIvgRYFkEyCPIQ1hQGDAoNxixKDKoNZI4N4b4FGgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,495,1427760000"; d="scan'208,217";a="1727755"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-3.cisco.com with ESMTP; 26 May 2015 04:58:27 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t4Q4wQ0J012467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 May 2015 04:58:26 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.253]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Mon, 25 May 2015 23:58:26 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Guangqing Deng <dengguangqing@cnnic.cn>, dns-privacy <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls
Thread-Index: AQHQkwXTcrT2GoYoDk+dl95RhBVFbJ2FQ4qAgAM+poCABQXbQIAAEqvw
Date: Tue, 26 May 2015 04:58:25 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A4785DD9E@xmb-rcd-x10.cisco.com>
References: <555C942F.2090007@gmail.com>, <CA+nkc8DK8320KAq8xWRbm4B8BLqPSErzyHxYZ6EPk1Uz4Mc6Og@mail.gmail.com>, <8F5C00A9-C218-4470-89C5-3A84DCBF1FA3@cisco.com> <2015052609540607241511@cnnic.cn>
In-Reply-To: <2015052609540607241511@cnnic.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.64.50]
Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A4785DD9Exmbrcdx10ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/fy3_GPEWuhntg5wly35720cDIOw>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, "Dan Wing (dwing)" <dwing@cisco.com>
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: Tue, 26 May 2015 04:58:30 -0000

From: dns-privacy [mailto:dns-privacy-bounces@ietf.org] On Behalf Of Guangqing Deng
Sent: Tuesday, May 26, 2015 7:24 AM
To: dns-privacy
Cc: Tim Wicinski; Dan Wing (dwing)
Subject: Re: [dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls

Resolution latency is very crucial for DNS system and the latency of DNS-over-DTLS is relatively low compared with DNS-over-TLS. I support adoption, and BTW is there any public software library of DTLS for doing DNS-over-DTLS  evaluation?

You can use OpenSSL.

-Tiru

________________________________
Guangqing Deng
CNNIC

From: Dan Wing<mailto:dwing@cisco.com>
Date: 2015-05-23 00:13
To: Bob Harold<mailto:rharolde@umich.edu>
CC: Tim Wicinski<mailto:tjw.ietf@gmail.com>; dns-privacy@ietf.org<mailto:dns-privacy@ietf.org>
Subject: Re: [dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls

On 20-May-2015 07:40 am, Bob Harold <rharolde@umich.edu<mailto:rharolde@umich.edu>> wrote:


On Wed, May 20, 2015 at 10:03 AM, Tim Wicinski <tjw.ietf@gmail.com<mailto: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.

I support adoption, and I will review.

I am unclear on Page 5
6.  Demultiplexing, Polling, Port Usage, and Discovery

"After performing the above steps, the host should determine if the
   DNS server supports DNSoD by sending a DTLS ClientHello message."

It is unclear to me what the "above steps" actually refers to.  Can you clarify?

Section 6 suggests how a DNSoDTLS client can determine that its connected network will work with DNSoDTLS.  The exact method and algorithm will require more discussion in the WG, especially to balance the needs for security and interoperability against implementation flexibility.

-d

v2.23.0 | Report a Bug | By Email