Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID and GOAWAY specify the length of the ID twice (#1620)
Martin Thomson <notifications@github.com> Tue, 31 July 2018 23:44 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 A2B7C130EA4 for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 16:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.11
X-Spam-Level:
X-Spam-Status: No, score=-6.11 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 O_QcqE6xKpta for <quic-issues@ietfa.amsl.com>; Tue, 31 Jul 2018 16:44:45 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5F78130EA3 for <quic-issues@ietf.org>; Tue, 31 Jul 2018 16:44:45 -0700 (PDT)
Date: Tue, 31 Jul 2018 16:44:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533080684; bh=jjXBNuzWo3g9JVaTBV3nkz05yF9hKQA6NMGzbxE8GzQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LGxhXSEpHt1kEMNll7+Ywsa0+9Doom6NrJG7l7Mg0AR2OrsxDSMc91qzNBlO431oV SZvf75fZfNV/tZU46ELXDHaIV7oTUvhUyFdvSS+GKDx2VUOPH2zOLVBmDnGGcOzsnK DphEN4J8m0w/GQbbZe9ZotG6ggD085Ho0E2Fu6yk=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdc92164abff99131191a373c22c0942bd1e92f4292cf000000011778b66c92a169ce14a3a07f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1620/409403052@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1620@github.com>
References: <quicwg/base-drafts/issues/1620@github.com>
Subject: Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID and GOAWAY specify the length of the ID twice (#1620)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b60f46c81452_7f163fa98e0be628942c4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/d7Eso4lFRptT0HJe0slRf_kXNro>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 31 Jul 2018 23:44:48 -0000
The advantage of having that redundancy is consistency. All frame types have a length, which allows us to send frames of unknown types. It seems that QUIC-the-transport leans more heavily toward the schema-aware grammar than hq or TLS, which both have redundant lengths. The transport therefore needs prior agreement for every extension - which is fitting for something at that layer. hq has just two instances of this sort of redundancy that I can identify: frames and settings. I don't think that either is particularly problematic, especially in light of existing needs. That is, you need to be able to send either without knowing that your peer will understand it. I don't think that this needs to change. -- 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/1620#issuecomment-409403052
- Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID… Martin Thomson
- [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID and… afrind
- Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID… afrind
- Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID… Mike Bishop
- Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID… Mark Nottingham
- Re: [quicwg/base-drafts] CANCEL_PUSH, MAX_PUSH_ID… Mark Nottingham