From nobody Thu Feb 16 07:56:09 2017 Return-Path: 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 E10161295ED; Thu, 16 Feb 2017 07:56:07 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.43.0 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <148726056791.15961.5609094243454424445.idtracker@ietfa.amsl.com> Date: Thu, 16 Feb 2017 07:56:07 -0800 Archived-At: Cc: Tim Wicinski , draft-ietf-dprive-dtls-and-tls-profiles@ietf.org, terry.manderson@icann.org, dns-privacy@ietf.org, dprive-chairs@ietf.org Subject: [dns-privacy] Last Call: (Authentication and (D)TLS Profile for DNS-over-(D)TLS) to Proposed Standard X-BeenThere: dns-privacy@ietf.org X-Mailman-Version: 2.1.17 Reply-To: ietf@ietf.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2017 15:56:08 -0000 The IESG has received a request from the DNS PRIVate Exchange WG (dprive) to consider the following document: - 'Authentication and (D)TLS Profile for DNS-over-(D)TLS' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2017-03-02. 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 discusses Usage Profiles, based on one or more authentication mechanisms, which can be used for DNS over Transport Layer Security (TLS) or Datagram TLS (DTLS). This document also specifies new authentication mechanisms - it describes several ways a DNS client can use an authentication domain name to authenticate a DNS server. Additionally, it defines (D)TLS profiles for DNS clients and servers implementing DNS-over-(D)TLS. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dprive-dtls-and-tls-profiles/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-dprive-dtls-and-tls-profiles/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Fri Feb 17 11:21:39 2017 Return-Path: X-Original-To: dns-privacy@ietfa.amsl.com Delivered-To: dns-privacy@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5C5129B32 for ; Fri, 17 Feb 2017 11:21:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com 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 MCUqNt6IxSI4 for ; Fri, 17 Feb 2017 11:21:36 -0800 (PST) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 96807129B2D for ; Fri, 17 Feb 2017 11:21:36 -0800 (PST) Received: by mail-qk0-x235.google.com with SMTP id p22so53232845qka.0 for ; Fri, 17 Feb 2017 11:21:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=bAveKUvhU8h+soakhcdZgD1ST7BhDjLYaw+JPSusXwo=; b=ROa4zSuuLidJS6CBPhl3g8TrupOVHoCnoDVRBESPlIktesQ+KuxdBFccwfTEYnxpsN 6cgJuFmAkak1AcflTYQ3NewdgpAIiFG9zdgbWK8nASJ2FdkebPf346XKEiy428AWUmza HJoHjV7fQbuhAhzoZDqIWJijFJ9a1ge/aAIPN3AwICfA0TqAmyNutTbkNZOqVWh5HjFT hqAPxkNIclDy0373S8M8bGgJpofUaib4ojwVDLRLjK5QarX7INTNDYnVoaj1UUnyPM40 WlcJJ88sNbG/DhzbBYLcBaZcfBe8bvx8UdW7Lt1DYyJ6mFlJnmftrP7aWDgHgiedTMIr HU6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bAveKUvhU8h+soakhcdZgD1ST7BhDjLYaw+JPSusXwo=; b=JT7demRia+x1OJDKDexw1aFdDs/iBaiN8ia3/TXXm2VAcWFgzvDk5/tSTfg+4JPg9z 1kJ1Zq9klkDgQfgtSZEDrBY2oFlblJQAxV/Z5WzOkuRX/swjBTv87qmXIXyYmGQnjtMb uiYnCHe5XjhodbXaI/ZLMOqIrG1lBcO0e4cJw9hGdfLNOnvxY8snfwGIU7EWMRUytO4S ovt48tQhEaV3eVmwszhEZhNqJj92POVcccLuPnx3HauoGiPFK36ZpcU298TJeX2+mfJ5 uApEjFtNXNpn/Rv70IKSfUW17C/U7diRbbpXKWF5QMWpGklETviCaAyqTUKN4TGbIbCH 7+Tw== X-Gm-Message-State: AMke39lUSSvr175RyuzzK+pARLT1zdR2w1sfMrrbpP+xCK79/YLG250AV9Dl5cLBBjYK7DuFruUdoWw4OyEzIQtp X-Received: by 10.55.189.130 with SMTP id n124mr9526206qkf.235.1487359295380; Fri, 17 Feb 2017 11:21:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.179.19 with HTTP; Fri, 17 Feb 2017 11:21:04 -0800 (PST) From: Warren Kumari Date: Fri, 17 Feb 2017 14:21:04 -0500 Message-ID: To: "dns-privacy@ietf.org" Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [dns-privacy] Cancelling Chicago meeting slot. X-BeenThere: dns-privacy@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 19:21:37 -0000 Hi all, We are planning on cancelling the Chicago DPRIVE meeting slot request. Meeting time is very tight these days, and it does not seem that there is sufficient work for us to do / progress since Seoul to justify using a slot. W -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf From nobody Tue Feb 21 09:27:22 2017 Return-Path: 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 5FEAE129517; Tue, 21 Feb 2017 09:27:19 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: X-Test-IDTracker: no X-IETF-IDTracker: 6.45.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148769803936.19017.8275039807218164598.idtracker@ietfa.amsl.com> Date: Tue, 21 Feb 2017 09:27:19 -0800 Archived-At: Cc: dns-privacy@ietf.org, dprive-chairs@ietf.org, smccammon@amsl.com, terry.manderson@icann.org Subject: [dns-privacy] dprive - Cancelling a meeting request for IETF 98 X-BeenThere: dns-privacy@ietf.org X-Mailman-Version: 2.1.17 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 17:27:20 -0000 A request to cancel a meeting session has just been submitted by . From nobody Tue Feb 28 17:17:59 2017 Return-Path: X-Original-To: dns-privacy@ietfa.amsl.com Delivered-To: dns-privacy@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E7112984B; Tue, 28 Feb 2017 17:17:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.202 X-Spam-Level: X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5pJFvpzh8REn; Tue, 28 Feb 2017 17:17:44 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07794129851; Tue, 28 Feb 2017 17:17:28 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id E7E34B820E6; Tue, 28 Feb 2017 17:17:27 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20170301011727.E7E34B820E6@rfc-editor.org> Date: Tue, 28 Feb 2017 17:17:27 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, dns-privacy@ietf.org, rfc-editor@rfc-editor.org Subject: [dns-privacy] RFC 8094 on DNS over Datagram Transport Layer Security (DTLS) X-BeenThere: dns-privacy@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2017 01:17:51 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8094 Title: DNS over Datagram Transport Layer Security (DTLS) Author: T. Reddy, D. Wing, P. Patil Status: Experimental Stream: IETF Date: February 2017 Mailbox: tireddy@cisco.com, dwing-ietf@fuggles.com, praspati@cisco.com Pages: 13 Characters: 31130 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dprive-dnsodtls-15.txt URL: https://www.rfc-editor.org/info/rfc8094 DOI: 10.17487/RFC8094 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. This document proposes the use of Datagram Transport Layer Security (DTLS) for DNS, to protect against passive listeners and certain active attacks. As latency is critical for DNS, this proposal also discusses mechanisms to reduce DTLS round trips and reduce the DTLS handshake size. The proposed mechanism runs over port 853. This document is a product of the DNS PRIVate Exchange Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC