[Doh] New: draft-livingood-doh-implementation-risks-issues

"Livingood, Jason" <Jason_Livingood@comcast.com> Sat, 09 March 2019 01:24 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8F3128678 for <doh@ietfa.amsl.com>; Fri, 8 Mar 2019 17:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=comcast.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 lxibitA_XJLp for <doh@ietfa.amsl.com>; Fri, 8 Mar 2019 17:24:00 -0800 (PST)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE7D124B0C for <doh@ietf.org>; Fri, 8 Mar 2019 17:24:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190220p; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1552094639; x=2416008239; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=awVn62Qrm+4DtcSbYq2B+PKW22lYQxdA7i7pzey4o38=; b=npMwcbFl79hGqvapNp3fobAS+1Lg+sw96Vg9rSwL6QSCLIFXTjwLArCON89pnc8B pNtj7LYHQ8S4x+TOlswgYO5ADsNeSYm5btdpzySmJtLyfrQyoVODU7TXSkC1Q1mo JcQkACUs8H/et9XlC145K8J34Ac7d9xHzliwLximvOlDadas0DG3CW0vAzXH0GZb nnYQlor63JB4Nm6FqIpKfpeoCBW3lN1KgflRSos6A4X13I0QcuAL+VNLs6JMAw2r 5xfoQwipGxT+9ZMbQKnP62Rg0JGd7bcYNoqvggdludv4lYujiqcoSACYFa03rzE+ pjzCznwUt358o7uYXEXU3mHRlzIqH2/3fVHUE/1ATBA1AH/R4plQr+g27Sn7cPc5 eS7kOUR140xoG/6dTMnyblJLgmd/HEmO5xsHckaTqNWB9QiFuE70Kd8sQlPPgzKM nWeyZ3ODdb6n8OUrN7tQ23FX0VLkotYuGtvs1ioqmqGuFij5QEthetWGm270ilxI Sowb0uKBmEK6weXPmx3x4mTpWJ03n8aLx7dz9Ag8wUG++afNDcaNdSxdV3XlqMvr uIU9lhPrF6LBSeGfsjiRDsVnyWh3xgIZrM9wC79D3kW60fPYr5L78uV43yoec4Q+ deo002Pj5SokR4HKCfkGe9bpEg2Z1caaJBuk/wEPV9M=;
X-AuditID: 60729ed4-2cdff700000044dc-5d-5c8315add603
Received: from COPDCEXC37.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id D7.B8.17628.EA5138C5; Fri, 8 Mar 2019 18:23:59 -0700 (MST)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC37.cable.comcast.com (147.191.125.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 8 Mar 2019 20:23:56 -0500
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.004; Fri, 8 Mar 2019 20:23:56 -0500
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: DoH WG <doh@ietf.org>
Thread-Topic: draft-livingood-doh-implementation-risks-issues
Thread-Index: AQHU1hbDDNj2GhBc2k6lTCYNWHxRBQ==
Date: Sat, 9 Mar 2019 01:23:56 +0000
Message-ID: <EA2A119D-06CF-4B0B-8994-86A99CD8AC0B@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.15.0.190115
x-originating-ip: [68.87.29.11]
Content-Type: multipart/mixed; boundary="_002_EA2A119D06CF4B0B899486A99CD8AC0Bcablecomcastcom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCKsWRmVeSWpSXmKPExsWSUDRnsu560eYYg10npSyu3b3I5sDosWTJ T6YAxqgGRpuSjKLUxBKX1LTUvOJUOy4FDGCTlJqWX5TqmliUUxmUmpOaiF0ZSGVKak5mWWqR PlZj9LGak9DFlDHzzhOmgtblHBXXPxxjb2Dc2c3RxcjJISFgIvGvbQNrFyMXh5DALiaJp3e3 skM4zUwSd/7PYAKpEhI4xSgx/1Q2iM0mYCZxd+EVZhBbREBS4uLUdyxdjBwcwgK2Ervu+ICY IkDmjEYxiAo9iTfHNzCChFkEVCR+zDUHCfMKuEjsnf6SDcRmFBCT+H5qDdgiZgFxiVtP5jNB nCYi8fDiaTYIW1Ti5eN/rCC2qIC+ROv3H6wgIyUE5CU+zoVqTZQ4duE1C8R4QYmTM5+wQLSK Sxw+soN1AqPILCQbZiFpmYWkZRbQVGYBTYn1u/QhSqwkVnxbAVWuKDGl+yE7REmcxKTz9RBh b4kfs6azQ9jXGCUerJWGaV164TMjstYFjNyrGPkszfQMDU30DE0t9IwMjTYxgtPPvCs7GC9P 9zjEKMDBqMTDu/5XU4wQa2JZcWXuIUYVoAGPNqy+wCjFkpefl6okwpsn3BwjxJuSWFmVWpQf X1Sak1p8iFGag0VJnPd6fWOMkEB6YklqdmpqQWoRTJaJg1OqgVFsDa+L2fF/878+y0vV5fHR NavbEGP20Uh0Ms/WzFaJphDTTtcojw82h4+aMrpuCguUePhyy5c+WVfJK5c+tijqf8zyYP9W /3PCymflczIXJqx+uWve7xUnfcRCRTY9cvVM2nNn0w/vq3s2/CrYyXpi+c/v3/apvjo60zDi 17JZKfNyGb6ULMhVYinOSDTUYi4qTgQAKXFm+kcDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/_J-lTbQB5GUdAuCDucUaTkLwmM8>
Subject: [Doh] New: draft-livingood-doh-implementation-risks-issues
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2019 01:24:02 -0000

FYI that this document has posted. I have requested 10 mins of agenda time in the DOH WG at IETF 104. 

Thanks and have a nice weekend,
Jason
        
On 3/8/19, 7:50 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:
        
            
            A new version of I-D, draft-livingood-doh-implementation-risks-issues-01.txt
            has been successfully submitted by Jason Livingood and posted to the
            IETF repository.
            
            Name:		draft-livingood-doh-implementation-risks-issues
            Revision:	01
            Title:		Centralized DNS over HTTPS (DoH) Implementation Issues and Risks
            Document date:	2019-03-08
            Group:		Individual Submission
            Pages:		24
            URL:            https://www.ietf.org/internet-drafts/draft-livingood-doh-implementation-risks-issues-01.txt
            Status:         https://datatracker.ietf.org/doc/draft-livingood-doh-implementation-risks-issues/
            Htmlized:       https://tools.ietf.org/html/draft-livingood-doh-implementation-risks-issues-01
            Htmlized:       https://datatracker.ietf.org/doc/html/draft-livingood-doh-implementation-risks-issues
            Diff:           https://www.ietf.org/rfcdiff?url2=draft-livingood-doh-implementation-risks-issues-01
            
            Abstract:
               The DNS over HTTPS (DoH) protocol is specified in RFC8484.  This
               document considers Centralized DoH deployment, which seems one likely
               way that DoH may be implemented, based on recent industry discussions
               and testing.  This describes that implementation model, as well the
               potential associated risks and issues.  The document also makes
               recommendations pertaining to the implementation of DoH, as well as
               recommendations for further study prior to widespread adoption.
            
                                                                                              
            
            
            Please note that it may take a couple of minutes from the time of submission
            until the htmlized version and diff are available at tools.ietf.org.
            
            The IETF Secretariat