IETF Logo Mail Archive

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

"Livingood, Jason" <Jason_Livingood@comcast.com> Tue, 12 March 2019 16:55 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 66CE2129AA0 for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 09:55:33 -0700 (PDT)
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 YnPCy653ByrK for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 09:55:32 -0700 (PDT)
Received: from copdcmhout01.cable.comcast.com (copdcmhout01.cable.comcast.com [162.150.44.71]) (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 037081277E7 for <doh@ietf.org>; Tue, 12 Mar 2019 09:55:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190220p; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1552409729; x=2416323329; 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=P9uzQ890ufpdRMdjxWYCI1rI0RB0+hjxsfb1TCuvp04=; b=1nGXuRggy4Zfgc2VtaZGiJmbAwfbDsHYVFjqnOrNt2tzGuko2dcTKlAxg202XKcm iXEK2p3ROQsso4BmGimVrpFvNaT7TY4fGW8RRDQl9otQ2ubKgrYoBdFmVaSZUvzw vLVgBozMLOw5z+9kyBFLb/WrehK8SeXqpKYbucQfnccRNnU5fjny9VoJMmHy8k2u cJ/byOrgFXlWJMcoK+/vJRHJlu7E7yzXkVIDfCXmJ5/JjpCjKI+iQvNas27VR39k oDuKXV9EmG8cVQrO3TPaJbBakfQS6ZdGesHrZgyGUwW3E3Cm4LlXR3Tf9lj+uBza 9VXUnfsOSCqJYtp/BbwfAn5i05wnY0WFXTPhg1OYSis0C5lbnORilUzpDX/wDnPc DzbMrEzBiZA5LJawqo3kypr6uddZocU9rv8eQuhjnp0iLHH14z1MCnBFgeh5CRxy fJdWaHO3C2Nuq7Gx10dbZU7qmO3LxVx0OW27FTpem4cXAfV2ibT1j4elHduIrXS/ bfZBaEi3c2YkMf4YNOdLsiXTXws7KlFKME7Bxl+1+IMz0ZkVkz4vcgZ5sJ1h2+wH Z8SHDpZFkoP6u6VUwjjecD+HwsvNEEJ/Jh3+DFP4pVBcBQs+wY2lffMJsuxYLYub TqrgGpmjnYctwYVb1g1Xf5bNleh5+RZ+H8FIph51AcM=;
X-AuditID: a2962c47-fbdff7000001abb1-8f-5c87e48126bf
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 copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 41.E0.43953.184E78C5; Tue, 12 Mar 2019 10:55:29 -0600 (MDT)
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; Tue, 12 Mar 2019 12:55:30 -0400
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; Tue, 12 Mar 2019 12:55:30 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: DoH WG <doh@ietf.org>
Thread-Topic: [EXTERNAL] Re: [Doh] New: draft-livingood-doh-implementation-risks-issues
Thread-Index: AQHU1hbDDNj2GhBc2k6lTCYNWHxRBaYD846AgAG5mICAArbogP//2I+A
Date: Tue, 12 Mar 2019 16:55:29 +0000
Message-ID: <75FFED43-1525-49E1-B598-64969E34E96C@cable.comcast.com>
References: <EA2A119D-06CF-4B0B-8994-86A99CD8AC0B@cable.comcast.com> <20190309182857.GA29321@laperouse.bortzmeyer.org> <BAB74C4B-D93A-4EBA-8F76-FEC4C68FF753@cable.comcast.com> <20190312151639.oqgwgdficezoygfr@nic.fr>
In-Reply-To: <20190312151639.oqgwgdficezoygfr@nic.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.17.0.190309
x-originating-ip: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <56367752B0D00C4B8768DAF60B2C2319@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOKsWRmVeSWpSXmKPExsWSUDRnsm7jk/YYgwsvhS0mLHzJaHHt7kU2 ByaPJUt+MnlM/LeBKYApqoHRpiSjKDWxxCU1LTWvONWOSwED2CSlpuUXpbomFuVUBqXmpCZi VwZSmZKak1mWWqSP1Rh9rOYkdDFl9Ex4zVQwi7viYcs31gbGL1xdjJwcEgImEv8e/mUDsYUE djFJPHqa28XIBWS3MEn8WjWHESJxmlHieH8uiM0mYCZxd+EVZhBbREBbYvLNHrAaZgFJiUfH D7GD2MICERLNx5dC1URKXN0/nRHCdpNY87wNzGYRUJVYevgeWD2vgIvEurMTWSEW32OUuH/z LthFnAKmEmt3TmEFsRkFxCS+n1rDBLFMXOLWk/lMEB8ISCzZc54ZwhaVePn4H1i9qIC+xMZN R9kg4ooSv+ZdAbI5gHo1Jdbv0ocYYyXxc1IfC4StKDGl+yHUPYISJ2c+YYFoFZc4fGQH6wRG yVlINs9CmDQLyaRZSCbNQjJpASPrKkZeQzMjPUNTAz0TEz1zw02MwOSzaJqO+w7GD+djDzEK cDAq8fBOPN8eI8SaWFZcmXuIUYKDWUmE1yIHKMSbklhZlVqUH19UmpNafIhRmoNFSZxXaHNr jJBAemJJanZqakFqEUyWiYNTqoGxciNz1q9H8ec2pT2Z3ra08vKc+KnlXa079k1g9Fo1O+v6 1okTrc4ZHX+Rwj3thsg0H/v973fPdt+suE6ZmeXAcbHCqQZmP1NSdi3+obvAhbf1j/V8y50L dzw6vjNVb6/8slcX377sieJOaApX+FtZpv5Ya5GBVGTdag6NdI5Fs+aHJRyc/OVqnRJLcUai oRZzUXEiAFO7RzY6AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/bbDWXuKtpR19uxmmgAp4xg8SvRA>
Subject: Re: [Doh] [EXTERNAL] Re: 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: Tue, 12 Mar 2019 16:55:34 -0000

On 3/12/19, 11:17 AM, "Stephane Bortzmeyer" <bortzmeyer@nic.fr> wrote:

>    It seems to me there is a more profound issue here: should we (the
    IETF), when creating new protocols, ensure that *all* previous usages
    continue to work? Even if we never condoned them?
    
>    Replying Yes to this question would put a severe burden on IETF
    shoulders; there are so many "creative" uses of the TCP/IP
    technologies that it is impossible to guarantee that everything will
    continue to work as before. Creating new protocols or new variants of
    old protocols will certainly disrupt things. Is it always bad? I don't
    think so.

[JL] The way you frame it, most people would like to say NO of course. But it is not a binary yes/no IMO. In this case we’re not saying consider every single corner case / use, but consider one of the primary use cases. To ignore how a protocol is used by large numbers of implementers when updating/enhancing/replacing the protocol seems silly - we at the IETF can do better.

v2.23.0 | Report a Bug | By Email