Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2289)
Lucas Pardue <notifications@github.com> Fri, 04 January 2019 01:19 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 8F2E913139E for <quic-issues@ietfa.amsl.com>; Thu, 3 Jan 2019 17:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 Gi1rGSI6O3LC for <quic-issues@ietfa.amsl.com>; Thu, 3 Jan 2019 17:19:02 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15D9013133D for <quic-issues@ietf.org>; Thu, 3 Jan 2019 17:19:02 -0800 (PST)
Date: Thu, 03 Jan 2019 17:19:01 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546564741; bh=Uijly/4p4ERqjioLybNrXJXLvLPg7Ent/8VthrLZHK0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PB2gEP1CFQCIt6mfINQlZec67IAjNjBCcw41t5AZCnq/CYi2reqWRFPzXK29TAZdD /ByKycVRxY9doluxis3y6J509RoPwS46Z94SyKzWj/fMl52v1jCMuQQDvL2aofzqz1 mq3rSMSbzVbxdrCXJxS+pbuRV4VxzUGRb7JwqvWw=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1b00ec8bea0aeb9e2341a1788a26db6a3ee5416e92cf000000011846768592a169ce17971745@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2289/c451329694@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2289@github.com>
References: <quicwg/base-drafts/pull/2289@github.com>
Subject: Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2289)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2eb48565d62_5b093fad412d45b4920fd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/AQBcDI9VHP4CrKpim2j5oiT6nCo>
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, 04 Jan 2019 01:19:04 -0000
I think I get part of the motivation for this but don't understand how this change on it's own allows extensibility with robust interop. Or in other words, how do endpoints make sure they process postfix fields, as expected by the sender, that arent defined anywhere? Channelling the editors, it seems this PR needs an issue to discuss the broader use cases and design. -- 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/pull/2289#issuecomment-451329694
- [quicwg/base-drafts] Allow extra data after self-… David Schinazi
- Re: [quicwg/base-drafts] Allow extra data after s… David Schinazi
- Re: [quicwg/base-drafts] Allow extra data after s… Lucas Pardue
- Re: [quicwg/base-drafts] Allow extra data after s… David Schinazi
- Re: [quicwg/base-drafts] Allow extra data after s… Martin Thomson
- Re: [quicwg/base-drafts] Allow extra data after s… Martin Thomson