Re: [quicwg/base-drafts] Normative Text in Invariants (#3773)

Jana Iyengar <notifications@github.com> Fri, 26 June 2020 01:28 UTC

Return-Path: <noreply@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 E1D543A10CE for <quic-issues@ietfa.amsl.com>; Thu, 25 Jun 2020 18:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.694
X-Spam-Level:
X-Spam-Status: No, score=-1.694 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 GaTNgX5RR2fI for <quic-issues@ietfa.amsl.com>; Thu, 25 Jun 2020 18:28:24 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38B83A10CC for <quic-issues@ietf.org>; Thu, 25 Jun 2020 18:28:24 -0700 (PDT)
Received: from github-lowworker-bb778fb.ash1-iad.github.net (github-lowworker-bb778fb.ash1-iad.github.net [10.56.102.56]) by smtp.github.com (Postfix) with ESMTP id 1FEB112027F for <quic-issues@ietf.org>; Thu, 25 Jun 2020 18:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1593134904; bh=J3aSFy4q6+aXIY4s2RKJcVwt2yzoZcgH8CYA+JLfCLs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CMoo5DDH0TWm2Syhys6pi+HXPpNaisdLnWnXdKL3CNtYQ0bqbS+OzCExUN3kAGc78 W9BXqQcm73f12qIkx90A/Z110cE9v8g7NgYfz5rQyuigcyf/p/nWbZSjigeTsedhRp 14ki4h7lR1llM+z/4G+VZQxCRHzlvU08gCdCXJCo=
Date: Thu, 25 Jun 2020 18:28:23 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK775YGX4VVFBAIHEIF5AEYDPEVBNHHCMMOWIU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3773/649897966@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3773@github.com>
References: <quicwg/base-drafts/issues/3773@github.com>
Subject: Re: [quicwg/base-drafts] Normative Text in Invariants (#3773)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ef54f37ce257_13573fdc1cacd9641014b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/D9-ufFmySKvMsFsQ9bnobwRFBsM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Jun 2020 01:28:26 -0000

My take on the invariants draft is the same as @martinthomson's: That is really about what future protocol versions of QUIC need to adhere to. I don't think we should be specifying what we are making available to intermediaries. That is merely a side-effect, and I don't think we should be changing the scope of the document.

These bits were not made available so intermediaries could use them. They were made available for the endpoints to pivot around, for the receiver to find the necessary information so that it could decrypt or reject the packet. The bits that are visible to third parties is a consequence, and this consequence is equally useful to intermediaries and sniffing tools.

@martinthomson : FWIW, I think the second paragraph in the proposed text is adequate. The first and third explicitly state things that don't really belong in the invariants draft IMO.

-- 
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/3773#issuecomment-649897966