[dispatch] Initial version of draft-hoffman-dispatch-dns-over-https
Paul Hoffman <paul.hoffman@icann.org> Sat, 17 June 2017 18:06 UTC
Return-Path: <paul.hoffman@icann.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 599A6129A99 for <dispatch@ietfa.amsl.com>; Sat, 17 Jun 2017 11:06:25 -0700 (PDT)
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 ECKfRD-iJVAy for <dispatch@ietfa.amsl.com>; Sat, 17 Jun 2017 11:06:24 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02CB412957F for <dispatch@ietf.org>; Sat, 17 Jun 2017 11:06:24 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sat, 17 Jun 2017 11:06:21 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Sat, 17 Jun 2017 11:06:21 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: Initial version of draft-hoffman-dispatch-dns-over-https
Thread-Index: AQHS55Rs+VkJj/e1ZkeGqaSt/fzELg==
Date: Sat, 17 Jun 2017 18:06:20 +0000
Message-ID: <59522F59-E46B-4983-A130-F2B51590CF75@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6C43A3F374A2A94D8C91E2D6F7A9DA67@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/yhgobbhHbaHPofZ1A_PDowFQjAE>
Subject: [dispatch] Initial version of draft-hoffman-dispatch-dns-over-https
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Jun 2017 18:06:25 -0000
Greetings. Based on the advice from the chairs, we have given a new filename to our dns-over-https draft. This will hopefully get the draft picked up in the DISPATCH WG tracker page. --Paul and Patrick A new version of I-D, draft-hoffman-dispatch-dns-over-https-00.txt has been successfully submitted by Paul Hoffman and posted to the IETF repository. Name: draft-hoffman-dispatch-dns-over-https Revision: 00 Title: DNS Queries over HTTPS Document date: 2017-06-17 Group: Individual Submission Pages: 12 URL: https://www.ietf.org/id/draft-hoffman-dispatch-dns-over-https-00.txt Status: https://datatracker.ietf.org/doc/draft-hoffman-dispatch-dns-over-https/ Htmlized: https://tools.ietf.org/html/draft-hoffman-dispatch-dns-over-https-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-hoffman-dispatch-dns-over-https-00 Abstract: DNS queries sometimes experience problems with end to end connectivity at times and places where HTTPS flows freely. HTTPS provides the most practical mechanism for reliable end to end communication. Its use of TLS provides integrity and confidentiality guarantees and its use of HTTP allows it to interoperate with proxies, firewalls, and authentication systems where required for transit. This document describes how to run DNS service over HTTP using https:// URIs.
- [dispatch] Initial version of draft-hoffman-dispa… Paul Hoffman