Return-Path: 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 600B01200E3 for ; Mon, 13 Jan 2020 13:07:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8 X-Spam-Level: X-Spam-Status: No, score=-8 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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 6XWRktQ3vV5i for ; Mon, 13 Jan 2020 13:07:19 -0800 (PST) Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A741D12002F for ; Mon, 13 Jan 2020 13:07:19 -0800 (PST) Date: Mon, 13 Jan 2020 13:07:18 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1578949638; bh=U8gaE2s7tPVwQ8oRDFxfON/RhIyKeOTA+7sc+nugZCs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=FlCUjq5Dl6QSOCe+9/Pc06yiidh4H8WH66MWa6Pw6uC6wMjJRJghzaLeCRQqqQtKA 9eCZ3aTACrCMHNtKCHPskMQlOWoqedWOKqHVocgbT6wF1RU6AdqqNUxvRaB4NeyC/Z jPrjNvd+jkXGqY6dTlX8Fq/O0dobwadTojUtpS9U= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Limit fallout of on-stream badness (#3336) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e1cdc06b45d5_e7b3f99286cd968148464"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2020 21:07:21 -0000 ----==_mimepart_5e1cdc06b45d5_e7b3f99286cd968148464 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #3300; closes #3303. Kazuho's point is that individual streams might be relayed by the peer from connections to other parties (multiple origins for a server, multiple user agents for a client). If that peer isn't checking stream contents, they might unintentionally relay something bad; this shouldn't be required to blow up the connection for the other parties (though that's still a permitted and reasonable implementation). This change says that the payload of the request stream never mandates a connection error; contents of the control stream still do. If we want to relax this, I think this is the most sensible way. That "if" is still an open question. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/3336 -- Commit Summary -- * Limit fallout of on-stream badness -- File Changes -- M draft-ietf-quic-http.md (26) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/3336.patch https://github.com/quicwg/base-drafts/pull/3336.diff -- 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/3336 ----==_mimepart_5e1cdc06b45d5_e7b3f99286cd968148464 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #3300; closes #3303.

Kazuho's point is that individual streams might be relayed by the peer from connections to other parties (multiple origins for a server, multiple user agents for a client). If that peer isn't checking stream contents, they might unintentionally relay something bad; this shouldn't be required to blow up the connection for the other parties (though that's still a permitted and reasonable implementation).

This change says that the payload of the request stream never mandates a connection error; contents of the control stream still do.

If we want to relax this, I think this is the most sensible way. That "if" is still an open question.

You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/3336

Commit Summary

  • Limit fallout of on-stream badness

File Changes

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

----==_mimepart_5e1cdc06b45d5_e7b3f99286cd968148464--