Re: [quicwg/base-drafts] Don't haphazardly suggest retrying over TCP (#290)

hardie <notifications@github.com> Wed, 15 February 2017 21:46 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942E5129455 for <quic-issues@ietfa.amsl.com>; Wed, 15 Feb 2017 13:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.187
X-Spam-Level:
X-Spam-Status: No, score=-6.187 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 0stxj9KeixnX for <quic-issues@ietfa.amsl.com>; Wed, 15 Feb 2017 13:46:07 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 4A5AA129847 for <quic-issues@ietf.org>; Wed, 15 Feb 2017 13:46:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=e+xTMJcrgIMsjeUATG1NG4MVIkk=; b=hSTJW0zfibKrU/47 0UBKi4SIND+SA9fdr3LaXCEnIExGGsR6AxX9UJGweuwrN1uz8AmuWMUSGFFOn2JV chfwnO3ob02S7d1VXiAKAAXFBnchG4rsf77O+t1H08jV3aLOLTVwreMxCw9fT80T L97BHyX5iZRuRQYX6NsGrAQEhHo=
Received: by filter0660p1mdw1.sendgrid.net with SMTP id filter0660p1mdw1-7507-58A4CC1B-10 2017-02-15 21:46:03.265267583 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 2NOK5HDLRIqwjsufsN_xwA for <quic-issues@ietf.org>; Wed, 15 Feb 2017 21:46:03.284 +0000 (UTC)
Date: Wed, 15 Feb 2017 13:46:03 -0800
From: hardie <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/290/280149860@github.com>
In-Reply-To: <quicwg/base-drafts/issues/290@github.com>
References: <quicwg/base-drafts/issues/290@github.com>
Subject: Re: [quicwg/base-drafts] Don't haphazardly suggest retrying over TCP (#290)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58a4cc1b322fa_29a23f9275b29138211e8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: hardie
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1QAHzeP7g+tNDFjwLGMYQWfatkQNLNJqtfu9 v2t68dq7HWHVzdzpZfQBzmMsGHdBEKtkSx2CXtj14yRd49sdwPMyvBFHFJOoRHWU1IkADyFKyzX+eO pDZufb/OAwEvThLWfMBJ9GwVLy7HlWvkoD6ncaw5/BIdUEC6Nl90V8RDXQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gsFDIgyz8TIIo-aVxF4NN-imPPQ>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:46:09 -0000

I understand why we don't want to recommend a specific fallback, but there's an implication here we may want to keep.  If you want to use QUIC with a fallback, that fallback should have roughly equivalent security properties or blocking QUIC is a downgrade attack.  So the DNS example might be falling back to DNS over DTLS, but it would *not* be falling back to plaintext UDP.  That may be better expressed in a document about which protocols could theoretically adopt QUIC than here, but I don't want to lose it entirely.

Note that I'm assuming here silent fallback, where the user is never told which protocols are in use under the hood.  I'm sure there are other choices for when the user is looped in, but I don't think those are QUIC's business.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/290#issuecomment-280149860