From nobody Fri Jun 1 00:21:15 2018 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 F3E011270AC for ; Fri, 1 Jun 2018 00:21:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 YfayYMRg4H96 for ; Fri, 1 Jun 2018 00:21:12 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 42D3B127077 for ; Fri, 1 Jun 2018 00:21:12 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527837671; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=O62wQu4ONotr4sKJixsPbZHpuZE5nrqn/e9vClGYsSY=; b=oDSilnukKRjgDao5B27UKJLAHX/yjpavok/SOWybVk58f3uPIVTSgkawELXa/ndL4HIjegeN LAhcPK4H6eDT4T1nl7JEUbSs48qqVovi6JtQV6ucWlCv9ek0pb0T8IRliczJXcLkmjUfP8BZ zDYyqetKEX+hcFOQTcwf+uzUqwI= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b10f3e7.7f62681d48d0-smtp-out-n02; Fri, 01 Jun 2018 07:21:11 -0000 (UTC) Date: Fri, 01 Jun 2018 00:21:10 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b10f3e6f1bcd_42fc2b04fc297bfc538d4@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 300fe3: Add interim-18-09 placeholder Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b10f3e6f17e7_42fc2b04fc297bfc5375e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 07:21:14 -0000 ----==_mimepart_5b10f3e6f17e7_42fc2b04fc297bfc5375e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 300fe3bb78432a109e4f4ba5b479148d710f7601 https://github.com/quicwg/wg-materials/commit/300fe3bb78432a109e4f4ba5b479148d710f7601 Author: Lars Eggert Date: 2018-06-01 (Fri, 01 Jun 2018) Changed paths: A interim-18-09/agenda.md A interim-18-09/arrangements.md Log Message: ----------- Add interim-18-09 placeholder **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b10f3e6f17e7_42fc2b04fc297bfc5375e-- From nobody Fri Jun 1 07:39:32 2018 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 5CD9312D88D for ; Fri, 1 Jun 2018 07:39:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1dKvRLYnzCO8 for ; Fri, 1 Jun 2018 07:39:28 -0700 (PDT) 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 6D89E12D883 for ; Fri, 1 Jun 2018 07:39:28 -0700 (PDT) Date: Fri, 01 Jun 2018 07:39:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527863967; bh=krZyfa6UKdkQtADhMGKj0EIfQKrVJlGHe4EkghXBj6E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=loXxqtKNaaR6yjc27rrzJG/yh3SvFZ9TpoSgOkbK55h5wu/X2rvjO/OFRZV2hL2ev tORdCws6CiLmRjp9rFCzzbbkfZp9Vw96ozNMiRUvAcdmGAhfYeIg5XWwrtv4aZRE2L hjP3qlvH2WpTb8ZeJh8EQQWjmoJciMOjnwQpfD5w= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b115a9f63728_78913f93d94d2f7c176179"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.22 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: Fri, 01 Jun 2018 14:39:30 -0000 ----==_mimepart_5b115a9f63728_78913f93d94d2f7c176179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: +: Initial value = 0, incremented when a packet marked ECT(0) is received + +ECT_1: + +: Initial value = 0, incremented when a packet marked ECT(1) is received + +CE: + +: Initial value = 0, incremented when a packet marked CE is received + +Reception of duplicate packets SHOULD NOT increment the counters. Can we count the packet (for all three counters) *before* detecting duplicates instead? IMO, theoretically a receiver should send back all the information it has obtained. Ignoring the CE flag in duplicate packets goes against that principle. Counting packets after detecting duplicates makes sense only when we can assume that duplication happens near to the receiver than where ECN is applied. I do not think that we have such an assumption. In practice, the recovery draft with the proposed changes only uses the CE counter to detect if _any_ congestion was reported by the ACK_ECN frame (it's essentially a binary flag). Considering that, I do not think that changing the moment of counting the packets causes any harm. And lastly but importantly, by changing the rule as such, we can get rid of the requirement to detect duplicates. See also: https://github.com/quicwg/base-drafts/issues/1405#issuecomment-393743048 -- 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/1372#pullrequestreview-125194246 ----==_mimepart_5b115a9f63728_78913f93d94d2f7c176179 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

Can we count the packet (for all three counters) before detecting duplicates instead?

IMO, theoretically a receiver should send back all the information it has obtained. Ignoring the CE flag in duplicate packets goes against that principle.

Counting packets after detecting duplicates makes sense only when we can assume that duplication happens near to the receiver than where ECN is applied. I do not think that we have such an assumption.

In practice, the recovery draft with the proposed changes only uses the CE counter to detect if any congestion was reported by the ACK_ECN frame (it's essentially a binary flag). Considering that, I do not think that changing the moment of counting the packets causes any harm.

And lastly but importantly, by changing the rule as such, we can get rid of the requirement to detect duplicates.

See also: #1405 (comment)

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

----==_mimepart_5b115a9f63728_78913f93d94d2f7c176179-- From nobody Fri Jun 1 09:02:25 2018 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 556A912DA6E for ; Fri, 1 Jun 2018 09:02:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 GcyfhIhaQXtB for ; Fri, 1 Jun 2018 09:02:16 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44CE12DA49 for ; Fri, 1 Jun 2018 09:02:15 -0700 (PDT) Date: Fri, 01 Jun 2018 09:02:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527868934; bh=NM3Ou3VFfdcsLkvKxF579o/qg6KXjokXw8uCPtorxlo=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Fj8xz3ljRSoa5vLx4xQX1CKUIrGeFRdh+ySJXxUAvyCm4ZYmR7ZxO8kcuCibUWzQ4 nC1uGa2uzmmm5gRtYwYziB5W0HcoGqAzVG8i8VO/Ri4A9/dlTWJQZ6/MWUU5E3J1KR ODA8w1rFzbIkqTbSUVveWZIsUWFHhcfBv0fzYiWs= From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b116e06d9147_652c3fa2a50d2f78644ea"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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.22 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: Fri, 01 Jun 2018 16:02:24 -0000 ----==_mimepart_5b116e06d9147_652c3fa2a50d2f78644ea Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1406 -- Commit Summary -- * Clarify 'packet protection' -> 'packet number protection' -- File Changes -- M draft-ietf-quic-tls.md (12) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1406.patch https://github.com/quicwg/base-drafts/pull/1406.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/1406 ----==_mimepart_5b116e06d9147_652c3fa2a50d2f78644ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • Clarify 'packet protection' -> 'packet number protection'

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 mute the thread.

----==_mimepart_5b116e06d9147_652c3fa2a50d2f78644ea-- From nobody Fri Jun 1 09:09:21 2018 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 92C7812D961 for ; Fri, 1 Jun 2018 09:09:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 19uTp1DbEMaX for ; Fri, 1 Jun 2018 09:09:18 -0700 (PDT) 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 1BB311205F0 for ; Fri, 1 Jun 2018 09:09:18 -0700 (PDT) Date: Fri, 01 Jun 2018 09:09:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527869357; bh=2321YNDB9v2BNfAh8bTGrwBCK7K/5gx9ZbArLrxpwDs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=v/EwtCWzWLcv+744MtcKJwfEVz9y9+8XMwXc87eZ1CMSZVg/AqiCmATefxKd0MpuC AmmBrx9X/OdYYKmlcS+qM4ECGecuosgzZCocpqRyz9X6Nxuqr476PKSw1qXN6qo0Ku 2g+kiZLeEuadwJaugOW8HEb368HraSctTuATRvjI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b116fad5084b_33742af847ab2f602004b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.22 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: Fri, 01 Jun 2018 16:09:20 -0000 ----==_mimepart_5b116fad5084b_33742af847ab2f602004b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm not convinced this is a proper change. The packer number protection key in terms of label used, and length, is based on a the packet protection algorithm, not a separate isolated packet number protection algorithm. -- 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/1406#issuecomment-393928608 ----==_mimepart_5b116fad5084b_33742af847ab2f602004b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm not convinced this is a proper change. The packer number protection key in terms of label used, and length, is based on a the packet protection algorithm, not a separate isolated packet number protection algorithm.

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

----==_mimepart_5b116fad5084b_33742af847ab2f602004b7-- From nobody Fri Jun 1 10:13:12 2018 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 1C69B12D969 for ; Fri, 1 Jun 2018 10:13:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 v1RiMSUTUipR for ; Fri, 1 Jun 2018 10:13:08 -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 9D54A12D961 for ; Fri, 1 Jun 2018 10:13:08 -0700 (PDT) Date: Fri, 01 Jun 2018 10:13:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527873187; bh=190tPhiYXWvW0NaDCgTi4F0AXau/PoyphV8m8JP7r70=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OX85JeLmjISAlAiykaejG0sYJQJjTW2QKH/gbqchbMY4kXTKIPVvA1JU4tn2oOSZf SFkNMFTk3Hdr6nX+R7LxDlilDlfjiy/ERJoIB1PVwkLSAvQ2UWtmziCED63SglOxPb BUSRV/biI1spDGGW+KpR1vr0lKZXdVU0U6nW6h/M= From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b117ea3a001_58d43fb890088f801179cb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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.22 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: Fri, 01 Jun 2018 17:13:10 -0000 ----==_mimepart_5b117ea3a001_58d43fb890088f801179cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj I'm not sure I follow, do you mean "The size of the packet number protection key is determined by the packet number protection algorithm" should instead be "The size of the packet number protection key is determined by the packet protection algorithm"? That is, remove the second "number" I added in that sentence? -- 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/1406#issuecomment-393947232 ----==_mimepart_5b117ea3a001_58d43fb890088f801179cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj I'm not sure I follow, d= o you mean "The size of the packet number protection key is determined by= the packet number protection algorithm" should instead be "The size of t= he packet number protection key is determined by the packet protection al= gorithm"? That is, remove the second "number" I added in that sentence?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b117ea3a001_58d43fb890088f801179cb-- From nobody Fri Jun 1 10:15:48 2018 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 69D7312D96A for ; Fri, 1 Jun 2018 10:15:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8f9DhoCYncbh for ; Fri, 1 Jun 2018 10:15:44 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9975C12D969 for ; Fri, 1 Jun 2018 10:15:44 -0700 (PDT) Date: Fri, 01 Jun 2018 10:15:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527873343; bh=D3/fBRVadQOgUxOz3vpxtDb5HvmRAYB91vEENnnnOsA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Gli5J9WCw0yjjhUYWOXPw2MxFwedbRxvexwvf91osHzwzck7tal+S3ozkuyxP+5LT nWx7D+hOnebzaHR9wjL6kWqI+dm3FvXABQxB9tqI2CtUe7QCeAWLzuoB3ozMtxmjRe hFg/xErAMqgtZcakQPfE69ZxB2RQGdhPRCCASBWo= From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Add missing words (#1407) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b117f3febf04_261783fc20ca44f80876ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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.22 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: Fri, 01 Jun 2018 17:15:47 -0000 ----==_mimepart_5b117f3febf04_261783fc20ca44f80876ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nothing major, just missing a 'the' and a 'on'. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1407 -- Commit Summary -- * Add missing words -- File Changes -- M draft-ietf-quic-tls.md (6) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1407.patch https://github.com/quicwg/base-drafts/pull/1407.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/1407 ----==_mimepart_5b117f3febf04_261783fc20ca44f80876ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Nothing major, just missing a 'the' and a 'on'.

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

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

Commit Summary

  • Add missing words

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 mute the thread.

----==_mimepart_5b117f3febf04_261783fc20ca44f80876ac-- From nobody Fri Jun 1 10:41:55 2018 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 2463C12D958 for ; Fri, 1 Jun 2018 10:41:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 EpIAVAa_zsCP for ; Fri, 1 Jun 2018 10:41:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1882A12DA02 for ; Fri, 1 Jun 2018 10:41:51 -0700 (PDT) Date: Fri, 01 Jun 2018 10:41:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527874910; bh=GFO/85uhwIL+iETaA8nBz01Bvtb3YqE8P62SzuE94uo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z8DqAsbQ7Nrq4kI2OMzU84QgChiiKxPVwpNrAB638oF8dUdmBQzCLy6t5RmJTAMV6 Z8q8fN1TZEZZy45O/IxosG/6Z3dIdIHvaQ6100JYPGCmhD9NluMJkXq53mRZ4xxIoU fFd2gLvCkva9K2DwavKCN3/0XWGZTgSYeM1kmIgw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Seek more clarity on Largest Reference/Base Index encoding (#1403) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11855e127a7_3adf3f90f8766f882345fa"; 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.22 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: Fri, 01 Jun 2018 17:41:53 -0000 ----==_mimepart_5b11855e127a7_3adf3f90f8766f882345fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > - baseIndex = largestReference + deltaBaseIndex +To save space, Base Index is encoded relative to Largest Reference using a +one-bit sign and the `Delta Base Index` value. A sign bit of 0 indicates that +the Base Index has a greater absolute index than the Largest Reference; the greater than or equal to, technically. We don't mention the zero case at all until the bottom. -- 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/1403#pullrequestreview-125256789 ----==_mimepart_5b11855e127a7_3adf3f90f8766f882345fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-qpack.md:

>  
-    baseIndex = largestReference + deltaBaseIndex
+To save space, Base Index is encoded relative to Largest Reference using a
+one-bit sign and the `Delta Base Index` value.  A sign bit of 0 indicates that
+the Base Index has a greater absolute index than the Largest Reference; the

greater than or equal to, technically. We don't mention the zero case at all until the bottom.

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

----==_mimepart_5b11855e127a7_3adf3f90f8766f882345fa-- From nobody Fri Jun 1 11:05:24 2018 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 114AA12DA21 for ; Fri, 1 Jun 2018 11:05:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 jhZ4Z7kKSNsH for ; Fri, 1 Jun 2018 11:05:21 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 2612D12DA0D for ; Fri, 1 Jun 2018 11:05:21 -0700 (PDT) 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=Oa9sM8T41J8VPWvQTWYe7RMeZIw=; b=a4X+Usn9C4UAOt3v zXwOETS91CHGcXjDQUtRlyHuRN7T7JEMD2sg3lEZg/O/jI/wPgM5lkSFNVTyOnx+ rgsmtkOS/mhzjJCTo8zqCWcn66Ewguub2nDug6t7kOWeRaZoVrddlwCKUHakFbk0 FGY16OTtgIU0tQu+HsXcJhAwwdY= Received: by filter0897p1las1.sendgrid.net with SMTP id filter0897p1las1-5965-5B118ADF-3C 2018-06-01 18:05:19.864245112 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id fiRo5A6WRcax-HLJ3fzXpg for ; Fri, 01 Jun 2018 18:05:19.660 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id 9E2BEC0147 for ; Fri, 1 Jun 2018 11:05:19 -0700 (PDT) Date: Fri, 01 Jun 2018 18:05:19 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b118adf9ca29_4c3f2abceb71af5c4613b2"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3+aIM6qi0F70XAd1yenqfiFML461vYDZzTyp IcRSbmQqHVJR5B0uCGXWRAZfhCIyV1OXZXL+Px5OQTnG+JlzoS4nWI6TgTbizHerz02pxX5bdbWsoI V7eElrgGKYd2KiWQV9pPHtWUVDA4XQR8wiPWSlZ7MsJdu3dcRPeUIL9sycPHGc1jOdfDrpyvXlnWS1 g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 18:05:23 -0000 ----==_mimepart_5b118adf9ca29_4c3f2abceb71af5c4613b2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. To go by line 940, "packet protection" is the payload encryption, and "packet number protection" is applied afterward. I initially thought you'd confused them, but after re-reading a couple of times, I think all the statements you make in the updated text are correct. I'm not convinced they're equivalent to what the old text was trying to say, however. > @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have N_MIN set to 12). -The size of the packet protection key is determined by the packet protection -algorithm, see {{pn-encrypt}}. +The size of the packet number protection key is determined by the packet number +protection algorithm, see {{pn-encrypt}}. The existing statement is true as well. Perhaps say that the size of both keys depends on the negotiated AEAD? -- 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/1406#pullrequestreview-125264525 ----==_mimepart_5b118adf9ca29_4c3f2abceb71af5c4613b2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

To go by line 940, "packet protection" is the payload encryption, and "packet number protection" is applied afterward. I initially thought you'd confused them, but after re-reading a couple of times, I think all the statements you make in the updated text are correct.

I'm not convinced they're equivalent to what the old text was trying to say, however.

In draft-ietf-quic-tls.md:

> @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see
 Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have
 N_MIN set to 12).
 
-The size of the packet protection key is determined by the packet protection
-algorithm, see {{pn-encrypt}}.
+The size of the packet number protection key is determined by the packet number
+protection algorithm, see {{pn-encrypt}}.

The existing statement is true as well. Perhaps say that the size of both keys depends on the negotiated AEAD?

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

----==_mimepart_5b118adf9ca29_4c3f2abceb71af5c4613b2-- From nobody Fri Jun 1 11:07:02 2018 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 D8A5712DA42 for ; Fri, 1 Jun 2018 11:06:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 TR-z6w3JquIe for ; Fri, 1 Jun 2018 11:06:58 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 8316312DA29 for ; Fri, 1 Jun 2018 11:06:58 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527876417; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=tVHBa1ARI7l0lW9bE6DY0YlJwEbckMSJnYvby/rgf+4=; b=Bh+OFKxC8EnDGR44z5AMCRhVJngOyzd+QQvjXhNjM+kHtAcjPoXp6KORZMq36HgQJH4HraeQ 6h8/FyBr+rVyzrub+eQhgXl2vGi2JQ72ONSZeGp1IYL0Gt/URBJG6qkj3DAy8tmBpH2x0Pl/ UJ+K6GS7YYrjw6kJ7Yc5DdQ172s= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: alessandro=cloudflare.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b118b41.7f376d3b2750-smtp-out-n02; Fri, 01 Jun 2018 18:06:57 -0000 (UTC) Date: Fri, 01 Jun 2018 11:06:57 -0700 From: Alessandro Ghedini Reply-To: Alessandro Ghedini To: quic-issues@ietf.org Message-ID: <5b118b4121aa9_1ec12abff0259c04105068@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b1957c: Add missing words Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b118b41216ed_1ec12abff0259c041049f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 18:07:00 -0000 ----==_mimepart_5b118b41216ed_1ec12abff0259c041049f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: b1957c863eab196230819b381558bc300769b522 https://github.com/quicwg/base-drafts/commit/b1957c863eab196230819b381558bc300769b522 Author: Alessandro Ghedini Date: 2018-06-01 (Fri, 01 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Add missing words Nothing major, just missing a 'the' and a 'on'. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b118b41216ed_1ec12abff0259c041049f8-- From nobody Fri Jun 1 11:07:07 2018 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 55B8F12DA51 for ; Fri, 1 Jun 2018 11:07:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 geksTlkYwcsn for ; Fri, 1 Jun 2018 11:07:01 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96A5812DA29 for ; Fri, 1 Jun 2018 11:07:01 -0700 (PDT) Date: Fri, 01 Jun 2018 11:07:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527876421; bh=f+qk23qm4eIchD85N6zxKKHLywcDH2Yn2r+Pcxz+cvI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=S3oWuBq6IvvkNurTWljUch/AHzDd59bp9NPcyl91PQUrbs/8QydenBmIrQwP6Q13o A59e9TWWMRsbDxA2b4dpv211pSlI3rZ54v+lBuJZCpu5FkOZ8SESiglKbPtJRxJgW7 zGoD1nvm97rzzbzuXXTd5sB7lpIpvUXKitc2C8mQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add missing words (#1407) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b118b44ed146_30712ab6bdf92f603236f2"; 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.22 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: Fri, 01 Jun 2018 18:07:04 -0000 ----==_mimepart_5b118b44ed146_30712ab6bdf92f603236f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1407. -- 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/1407#event-1658889066 ----==_mimepart_5b118b44ed146_30712ab6bdf92f603236f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1407.

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

----==_mimepart_5b118b44ed146_30712ab6bdf92f603236f2-- From nobody Fri Jun 1 11:59:54 2018 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 5A66E126E64 for ; Fri, 1 Jun 2018 11:59:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 r6m24CV5QCIx for ; Fri, 1 Jun 2018 11:59:50 -0700 (PDT) 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 71785126BF3 for ; Fri, 1 Jun 2018 11:59:50 -0700 (PDT) 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=tKRFiq2Y0vSbqIToroFg+mTuxMY=; b=tYw7QKD8y1BiUBti SndS0RFI0JWukQZtA0/gybcFWVEF+ZYZ8Exm51mZoMp6dBiF5vKvxwatOcqpQhWw G6eOEI95hP+lWa6Z3T0uUzWTNDKQMd1i5Rl1pNdTNB1KcSzkeQOEW5n8ZTzcWcmG QpMv/s89ZWows3wvlxXF2FZIj+k= Received: by filter1545p1mdw1.sendgrid.net with SMTP id filter1545p1mdw1-6435-5B1197A5-11 2018-06-01 18:59:49.279724338 +0000 UTC Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 1e04DDy6REmJmMPoTD-kug for ; Fri, 01 Jun 2018 18:59:49.229 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id 3525BAE0291 for ; Fri, 1 Jun 2018 11:59:49 -0700 (PDT) Date: Fri, 01 Jun 2018 18:59:49 +0000 (UTC) From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1197a532e23_be72aba84d8cf5c54555"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2nI+KqfQ78fitAOFAHo/rTlUVbkIL6d/o4c0 fN+PJSHDu0J82X2j6JccJNlP9vTrkytH0/M1up9DuZHKt5ZN95kEDum2Jh3L4mIXbBZ/NBxdx5HjIe z7FUNdA/Byt0SFyShABnTyK9YRTN9B8m15PbKUefazcKYvmwG+oJg6DN8fOsrphUP0EK4o8Ysz+ubg Q= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 18:59:53 -0000 ----==_mimepart_5b1197a532e23_be72aba84d8cf5c54555 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ghedo commented on this pull request. > @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have N_MIN set to 12). -The size of the packet protection key is determined by the packet protection -algorithm, see {{pn-encrypt}}. +The size of the packet number protection key is determined by the packet number +protection algorithm, see {{pn-encrypt}}. So, the way I read it, is that key *and IV* length (i.e. key_length and iv_length) is actually defined in the paragraph before, but nowhere it says how long is the packet number encryption key (i.e. pn_key_length) which is what confused me (also considering the "see {{pn-encrypt}}" which didn't make a whole lot of sense to me since packet number encryption wasn't mentioned at all in that sentence). -- 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/1406#discussion_r192487235 ----==_mimepart_5b1197a532e23_be72aba84d8cf5c54555 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ghedo commented on this pull request.

In draft-ietf-quic-tls.md:

> @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see
 Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have
 N_MIN set to 12).
 
-The size of the packet protection key is determined by the packet protection
-algorithm, see {{pn-encrypt}}.
+The size of the packet number protection key is determined by the packet number
+protection algorithm, see {{pn-encrypt}}.

So, the way I read it, is that key and IV length (i.e. key_length and iv_length) is actually defined in the paragraph before, but nowhere it says how long is the packet number encryption key (i.e. pn_key_length) which is what confused me (also considering the "see {{pn-encrypt}}" which didn't make a whole lot of sense to me since packet number encryption wasn't mentioned at all in that sentence).

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

----==_mimepart_5b1197a532e23_be72aba84d8cf5c54555-- From nobody Fri Jun 1 12:01:52 2018 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 C74F512E865 for ; Fri, 1 Jun 2018 12:01:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Cb6Q-eZ8zbsp for ; Fri, 1 Jun 2018 12:01:41 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BE9D12E047 for ; Fri, 1 Jun 2018 12:01:39 -0700 (PDT) Date: Fri, 01 Jun 2018 12:01:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527879698; bh=Dk1kYLGd9pBKHh59M0w6KQZS3R4yeHjPNQ+cbLnj++M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1EL+ZQE5lSXMWxVg/tCSxSFPV/DARFdx/8kgqMJg7rqhFtncSBa6o9DoMj2Lk4T8e dC9iHzRQJn/xfnh7FZwArhsn3Raf1c+S0B9eIL5txMlNCN+femsTFoZ447D4GDWrVJ tU7uNHZnkAMaq32sV1dWJxGNDZznA/Y3w5ensWmw= From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b119811f30ad_72693f7e5a168f88863d2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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.22 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: Fri, 01 Jun 2018 19:01:51 -0000 ----==_mimepart_5b119811f30ad_72693f7e5a168f88863d2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ghedo commented on this pull request. > @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have N_MIN set to 12). -The size of the packet protection key is determined by the packet protection -algorithm, see {{pn-encrypt}}. +The size of the packet number protection key is determined by the packet number +protection algorithm, see {{pn-encrypt}}. Though I'm fine adding both, it just seems superfluous. -- 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/1406#discussion_r192487720 ----==_mimepart_5b119811f30ad_72693f7e5a168f88863d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ghedo commented on this pull request.

In draft-ietf-quic-tls.md:

> @@ -826,8 +826,8 @@ in Section 5.3 of {{!TLS13}}, the IV length is the larger of 8 or N_MIN (see
 Section 4 of {{!AEAD=RFC5116}}; all ciphersuites defined in {{!TLS13}} have
 N_MIN set to 12).
 
-The size of the packet protection key is determined by the packet protection
-algorithm, see {{pn-encrypt}}.
+The size of the packet number protection key is determined by the packet number
+protection algorithm, see {{pn-encrypt}}.

Though I'm fine adding both, it just seems superfluous.

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

----==_mimepart_5b119811f30ad_72693f7e5a168f88863d2-- From nobody Fri Jun 1 12:09:29 2018 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 8A313126B72 for ; Fri, 1 Jun 2018 12:09:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 bs1qIXQVfxgu for ; Fri, 1 Jun 2018 12:09:25 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 8E72C126B6D for ; Fri, 1 Jun 2018 12:09:25 -0700 (PDT) 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=d/GVkmIwPXwschL4pDtTvL5wQqg=; b=O0v3w9hXYN4ERv2l h86Risd08XwnaHvV+WCRhA0F4/irb6vOEqRDSGRA5af10q0n1cNT8ylX64dwfQ8W 83s4pTiHqGmN4s+Sva0z+udTcdMy9z72UF1wL+65eQLOhlzoyX4qPoJvM69doB3+ jlWfllLoHpyn/2PcvZWa3PbuMRw= Received: by filter0730p1las1.sendgrid.net with SMTP id filter0730p1las1-15214-5B1199DE-2C 2018-06-01 19:09:18.558587257 +0000 UTC Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id ADx4yjOPT1G49CE0OPtKZw for ; Fri, 01 Jun 2018 19:09:18.238 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 35A32C005A for ; Fri, 1 Jun 2018 12:09:18 -0700 (PDT) Date: Fri, 01 Jun 2018 19:09:18 +0000 (UTC) From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1199de33d03_11702af122318f60692e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0/kj3GbpmZhoRVkXOIvdn+8mxhd67gcThnzt DpLdX/dm5lhwF1SLfvrI85c8bbD0oDqQGCK2gQBiHCnZhcJA+vOTUo0+aSHV2SH2UlgLhic4xnjBr2 ytd1M3YdwS2dy6IBBqrjWC9gKEgMVdMkh1w75OAw91xyV7/rjvmyt9UZpvyyiM6ZpdoPcFA7XR2jf1 M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 19:09:28 -0000 ----==_mimepart_5b1199de33d03_11702af122318f60692e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > @mikkelfj I'm not sure I follow, do you mean "The size of the packet number protection key is determined by the packet number protection algorithm" should instead be "The size of the packet number protection key is determined by the packet protection algorithm"? That is, remove the second "number" I added in that sentence? Yes -- 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/1406#issuecomment-393981152 ----==_mimepart_5b1199de33d03_11702af122318f60692e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj I'm not sure I follow, do yo= u mean "The size of the packet number protection key is determined by the p= acket number protection algorithm" should instead be "The size of the packe= t number protection key is determined by the packet protection algorithm"? = That is, remove the second "number" I added in that sentence?

Yes

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b1199de33d03_11702af122318f60692e6-- From nobody Fri Jun 1 12:27:28 2018 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 69B4112D810 for ; Fri, 1 Jun 2018 12:27:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1EV8_UHhErIc for ; Fri, 1 Jun 2018 12:27:24 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17C0812D7F3 for ; Fri, 1 Jun 2018 12:27:24 -0700 (PDT) Date: Fri, 01 Jun 2018 12:27:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527881243; bh=TLOHYWnaSQwL7cr/Xi5OUO/+unSi8dntIaZ/OKcxa94=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WEP+8L2Nen4I2HJXx7hBQAkpGSixLkyK0QKnEPk2E5GhyL4HoH8879I9StkwCN3bj yRGxtrzqNwF3/k9fg8/K/5/dJ0NkesDdkgNGVKYwRJANamOdoZ2u1orrMKQ4c+FCYL SthklT0D8a1Ue77e/idH2wgbsPa47WYvYohX/9r8= From: Alessandro Ghedini Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b119e1af3398_498e3ff973f38f841217e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ghedo 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.22 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: Fri, 01 Jun 2018 19:27:27 -0000 ----==_mimepart_5b119e1af3398_498e3ff973f38f841217e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Yes Ok, so I thought about that too, but "packet number protection algorithm" is explicitly defined in the pn-encrypt section which says "The packet number protection algorithm depends on the negotiated AEAD", so it kind of seemed like a a repetition that the pn protection key length is the same as protection algorithm key length *and* that pn protection algo is also the same as protection algo (that is, negotiated AEAD). Again, don't have a strong opinion and would be happy to change, but seems superfluous. -- 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/1406#issuecomment-393985538 ----==_mimepart_5b119e1af3398_498e3ff973f38f841217e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes

Ok, so I thought about that too, but "packet number protection algorit= hm" is explicitly defined in the pn-encrypt section which says "The packe= t number protection algorithm depends on the negotiated AEAD", so it kind= of seemed like a a repetition that the pn protection key length is the s= ame as protection algorithm key length and that pn protection al= go is also the same as protection algo (that is, negotiated AEAD).

Again, don't have a strong opinion and would be happy to change, but s= eems superfluous.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b119e1af3398_498e3ff973f38f841217e6-- From nobody Fri Jun 1 13:13:20 2018 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 22C6F12D9FE for ; Fri, 1 Jun 2018 13:13:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 FKuTxNhK4ixp for ; Fri, 1 Jun 2018 13:13:17 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491B112D94A for ; Fri, 1 Jun 2018 13:13:17 -0700 (PDT) Date: Fri, 01 Jun 2018 13:13:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527883996; bh=2OHUE8HF9AmlVYYNjHBPDNxljKbCLxRijMAFEZ6aifU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q2P6ryKEenLy/+f/sDmJ/WkNb6Md4xU1pCXcxqQRLQ7EfLsLRaB6qRTK2490ToSCE nN6OG3X8+BNObv+H4IvzjHKqeQkGf+JYJAn7frNUW1geHGXvbX5vlSsGgeOeuCBci+ m7V/5PvzyBUe+wneF6CAKf9AAzhg7GQQrLZgjAKE= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Largest Reference too big (#1404) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11a8dc928b2_62093fe42911ef841031d1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 20:13:19 -0000 ----==_mimepart_5b11a8dc928b2_62093fe42911ef841031d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If tolerance of errors like this is a downward spiral, I guess I don't understand MAY instead of MUST. Then there will be some implementations that don't treat it as an error (perhaps many, because tracking this is annoying), and the buggy encoder can just say "well it works with so-and-so". -- 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/1404#issuecomment-393996538 ----==_mimepart_5b11a8dc928b2_62093fe42911ef841031d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If tolerance of errors like this is a downward spiral, I guess I don't= understand MAY instead of MUST. Then there will be some implementations= that don't treat it as an error (perhaps many, because tracking this is = annoying), and the buggy encoder can just say "well it works with so-and-= so".

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b11a8dc928b2_62093fe42911ef841031d1-- From nobody Fri Jun 1 13:35:13 2018 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 E2DDE12DA19 for ; Fri, 1 Jun 2018 13:35:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Q6SIZG8HRoMF for ; Fri, 1 Jun 2018 13:35:10 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B37B12D9FE for ; Fri, 1 Jun 2018 13:35:10 -0700 (PDT) Date: Fri, 01 Jun 2018 13:35:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527885309; bh=7aMhcivhi8P8+GbBh9+QJG6q5s27ozzLKoERPInL2ro=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Zd9UdK0KGT9Nd2IjuOh/4rLq+fwzPTjKHmR82EohsdLok//+e3+XEF9CJgRrnUDmp 6JvUFNI+7F99nr2EHV1tjzpC+jVtfoFrSXKAtcpyVhkUq6F2SEpL4uOcSOXw004ioS zepttDIgkMHLB0GZmVwChD99SEI0ySJIhyyol82o= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retain use of SETTINGS_ENABLE_PUSH (#718) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11adfd33c01_30ca3fc095108f841837ae"; 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.22 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: Fri, 01 Jun 2018 20:35:12 -0000 ----==_mimepart_5b11adfd33c01_30ca3fc095108f841837ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Following the logic in #1359, if we treat push as being an extension which defines a few frames and a stream type, then clients should have an opt-in setting declaring that all the push-specific things are supported. If that PR gets merged, the only "privileged" thing about push in the core protocol is that PRIORITY can prioritize/depend on a push stream. I'm almost tempted, as part of this and removing Flags, to say that requests can't depend on pushes and split out a PUSH_PRIORITY frame so that it's totally disjoint. -- 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/718#issuecomment-394001534 ----==_mimepart_5b11adfd33c01_30ca3fc095108f841837ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Following the logic in #1359, if we treat push as being an extension which defines = a few frames and a stream type, then clients should have an opt-in settin= g declaring that all the push-specific things are supported. If that PR = gets merged, the only "privileged" thing about push in the core protocol = is that PRIORITY can prioritize/depend on a push stream.

I'm almost tempted, as part of this and removing Flags, to say that re= quests can't depend on pushes and split out a PUSH_PRIORITY frame so that= it's totally disjoint.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b11adfd33c01_30ca3fc095108f841837ae-- From nobody Fri Jun 1 13:49:02 2018 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 911A512E044 for ; Fri, 1 Jun 2018 13:48:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 euEqhUQuJPhe for ; Fri, 1 Jun 2018 13:48:50 -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 7253C12DA6B for ; Fri, 1 Jun 2018 13:48:50 -0700 (PDT) Date: Fri, 01 Jun 2018 13:48:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527886129; bh=uJQzM9xb9AiFTFuvpcU10MI20kDKFwl2T69ldt8wUGg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=GTGw2IX/AOBcn4/Fjqhtkp0yHrNTC6dLwduDES827nLwBybFSxQMU9q7S0catnoU+ 8xWy5BJWDbDr6hKT4/Yplxf+aiovMMAMcY8+wwoGhGOsZnTR5YYl/eTDcNWkaD+rvg mYKEAPN0Tv577QnsUPSonjTS1K7L0UucL5jAt88M= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] qpack: move link to absolute-index to 1st Largest Reference mention (#1408) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11b13168226_578d2ad439ceaf5811688f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.22 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: Fri, 01 Jun 2018 20:49:01 -0000 ----==_mimepart_5b11b13168226_578d2ad439ceaf5811688f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1408 -- Commit Summary -- * qpack: move link to absolute-index to 1st Largest Reference mention -- File Changes -- M draft-ietf-quic-qpack.md (10) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1408.patch https://github.com/quicwg/base-drafts/pull/1408.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/1408 ----==_mimepart_5b11b13168226_578d2ad439ceaf5811688f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • qpack: move link to absolute-index to 1st Largest Reference mention

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 mute the thread.

----==_mimepart_5b11b13168226_578d2ad439ceaf5811688f-- From nobody Fri Jun 1 13:50:43 2018 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 8BA3D12DA27 for ; Fri, 1 Jun 2018 13:50:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 p_FgnsjA8shN for ; Fri, 1 Jun 2018 13:50:39 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6E9C12D9FE for ; Fri, 1 Jun 2018 13:50:39 -0700 (PDT) Date: Fri, 01 Jun 2018 13:50:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527886239; bh=VHJj3frIKZlgxLW2sma8jgbnkGLlHn4qbZycYSEIbWQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nLhCe9TAR84fhIU0weMhcBeIfhhQkWHx+jwwlQsWEQqrIps0kKcOLC79hLYlTASik kRpPN4u4IfkKuRvcdiinC178TzhPX2xy13+ma/IyyxYo8g0kUhXFNl/QQBLZJHJc8m dvNgmY9HG6TE7wBhzH3oCvYnMueuHlDmCf7VNP8Q= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11b19f2e7bf_9913fe65ec26f80980e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 20:50:42 -0000 ----==_mimepart_5b11b19f2e7bf_9913fe65ec26f80980e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the total number of dynamic table inserts and duplications since the last Table State Synchronize, encoded as a 7-bit prefix integer. The encoder uses this value to determine which table entries are vulnerable to head-of-line blocking. -A decoder MAY coalesce multiple synchronization updates into a single update. + +A decoder MAY coalesce multiple synchronization updates into a single update. A +decoder MAY rely on Header Acknowledgement instructions to indirectly +acknowledge changes to the dynamic table. Relying on Header Acknowledgment +instructions exclusively leads to blocking if the encoder waits for an entry to I don't think it would lead to blocking, but it would lead to never using the dynamic table? > @@ -523,6 +530,12 @@ blocks within a stream have been fully processed. ~~~~~~~~~~ {:#fig-header-ack title="Header Acknowledgement"} +An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging +any dynamic table entries that the header block referenced. That is, this +instruction is also processed as a Table Size Synchronize instruction with a +value matching the Largest Reference of the corresponding header block. You mean TSS will be incremental from the largest acknowledged largest reference or most recent TSS? > @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the total number of dynamic table inserts and duplications since the last Table State Synchronize, encoded as a 7-bit prefix integer. The encoder uses this value to determine which table entries are vulnerable to head-of-line blocking. -A decoder MAY coalesce multiple synchronization updates into a single update. + +A decoder MAY coalesce multiple synchronization updates into a single update. A +decoder MAY rely on Header Acknowledgement instructions to indirectly +acknowledge changes to the dynamic table. Relying on Header Acknowledgment +instructions exclusively leads to blocking if the encoder waits for an entry to +be acknowledged before using it. This happens if the encoder wants to avoid the +risk of blocking at the decoder, or the decoder sets the +SETTINGS_QPACK_BLOCKED_STREAMS lower than the number of active streams. I had to read this many times to figure out what you are saying - you are explaining why the encoder might be waiting for acknowledgement before using the headers in the dynamic table. I think it might be more clear if you change the second bit to something like "... or the encoder has already reached the decoder's limit for blocked streams". -- 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/1399#pullrequestreview-125305701 ----==_mimepart_5b11b19f2e7bf_9913fe65ec26f80980e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the
 total number of dynamic table inserts and duplications since the last Table
 State Synchronize, encoded as a 7-bit prefix integer.  The encoder uses this
 value to determine which table entries are vulnerable to head-of-line blocking.
-A decoder MAY coalesce multiple synchronization updates into a single update.
+
+A decoder MAY coalesce multiple synchronization updates into a single update.  A
+decoder MAY rely on Header Acknowledgement instructions to indirectly
+acknowledge changes to the dynamic table.  Relying on Header Acknowledgment
+instructions exclusively leads to blocking if the encoder waits for an entry to

I don't think it would lead to blocking, but it would lead to never using the dynamic table?

In draft-ietf-quic-qpack.md:

> @@ -523,6 +530,12 @@ blocks within a stream have been fully processed.
 ~~~~~~~~~~
 {:#fig-header-ack title="Header Acknowledgement"}
 
+An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging
+any dynamic table entries that the header block referenced.  That is, this
+instruction is also processed as a Table Size Synchronize instruction with a
+value matching the Largest Reference of the corresponding header block.

You mean TSS will be incremental from the largest acknowledged largest reference or most recent TSS?

In draft-ietf-quic-qpack.md:

> @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the
 total number of dynamic table inserts and duplications since the last Table
 State Synchronize, encoded as a 7-bit prefix integer.  The encoder uses this
 value to determine which table entries are vulnerable to head-of-line blocking.
-A decoder MAY coalesce multiple synchronization updates into a single update.
+
+A decoder MAY coalesce multiple synchronization updates into a single update.  A
+decoder MAY rely on Header Acknowledgement instructions to indirectly
+acknowledge changes to the dynamic table.  Relying on Header Acknowledgment
+instructions exclusively leads to blocking if the encoder waits for an entry to
+be acknowledged before using it.  This happens if the encoder wants to avoid the
+risk of blocking at the decoder, or the decoder sets the
+SETTINGS_QPACK_BLOCKED_STREAMS lower than the number of active streams.

I had to read this many times to figure out what you are saying - you are explaining why the encoder might be waiting for acknowledgement before using the headers in the dynamic table. I think it might be more clear if you change the second bit to something like

"... or the encoder has already reached the decoder's limit for blocked streams".

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

----==_mimepart_5b11b19f2e7bf_9913fe65ec26f80980e6-- From nobody Fri Jun 1 14:02:51 2018 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 DA7C312DA19 for ; Fri, 1 Jun 2018 14:02:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7zy5uJCRpBWr for ; Fri, 1 Jun 2018 14:02:48 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19B5112D9FE for ; Fri, 1 Jun 2018 14:02:48 -0700 (PDT) Date: Fri, 01 Jun 2018 14:02:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527886967; bh=WOkn6R5xemufdQomy77KGr12+N1BUreRakp9hg6LGnQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=U0h0V9AUnDMwHdCDGQwfA+ol3MuN/MJcHO+8byunQ70h/nuVltiibrjvWGicAxDO0 roLnZRoHel5f15t2GWUvK7TIcg0csta+vfqUIA6h5qGzhcpOJcDbJGa/obMUH2mwxm ssZw0miV0VYPpqCYpFORotCRcTKP54G+pKv7aakU= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11b47773c62_700a3f8d3989ef80131199"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.22 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: Fri, 01 Jun 2018 21:02:50 -0000 ----==_mimepart_5b11b47773c62_700a3f8d3989ef80131199 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ``` A stream becomes unblocked when the greatest absolute index in the dynamic table becomes greater than or equal to the Largest Reference for all header blocks the decoder has started reading from the stream. ``` The decoder can only read one header block at a time -- what are these _all header blocks_ that the decoder has started reading? If there are multiple header blocks in a stream, the stream can become blocked, unblocked, then blocked again, and so on. -- 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/1409 ----==_mimepart_5b11b47773c62_700a3f8d3989ef80131199 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 
                                                           A stream
   becomes unblocked when the greatest absolute index in the dynamic
   table becomes greater than or equal to the Largest Reference for all
   header blocks the decoder has started reading from the stream.

The decoder can only read one header block at a time -- what are these all header blocks that the decoder has started reading?

If there are multiple header blocks in a stream, the stream can become blocked, unblocked, then blocked again, and so on.

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

----==_mimepart_5b11b47773c62_700a3f8d3989ef80131199-- From nobody Fri Jun 1 14:43:37 2018 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 A53CE12DA54 for ; Fri, 1 Jun 2018 14:43:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ATnwSZr4LIKQ for ; Fri, 1 Jun 2018 14:43:32 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA22112DA1C for ; Fri, 1 Jun 2018 14:43:32 -0700 (PDT) Date: Fri, 01 Jun 2018 14:43:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527889411; bh=bEag79AYjY5CpKPTDHyCGC0SlU2VwxpJLQykK+c0wPw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BER9t8+vfcVF3Yo4eoHfBUmygkLNHzAxtvDbDJjRQntF0TgonvuvsYrwS/KMbQQla Hk49TVBD6NMoCvRcXI9WP/VB+loCRmzGzOnEdQAItMwy0bc9oOKPOWIY7yFvPl5ooJ nUY8ChrO7rHIDyNMXzRa2n07xsKyinI32mgzyqdE= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11be03edd32_6d223fc45b4eef80280a4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 21:43:35 -0000 ----==_mimepart_5b11be03edd32_6d223fc45b4eef80280a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > @@ -536,6 +536,31 @@ instruction is also processed as a Table Size Synchronize instruction with a value matching the Largest Reference of the corresponding header block. +### Stream Cancellation + +A stream that is reset might have multiple outstanding header blocks. A decoder +that receives a stream reset before the end of a stream generates a Stream +Cancellation instruction on the decoder stream. Similarly, a decoder that +abandons reading of a stream needs to signal this using the Stream Cancellation +instruction. This signals to the encoder that all references to the dynamic +table on that stream are no longer outstanding. + +An encoder cannot infer from this acknowledgement that any dynamic table entries +referenced have been received. I think you're trying to say that the encoder can't make any assumptions about the state of the dynamic table, as can be done with header acknowledgement. "...cannot infer from this acknowledgement any updates to the dynamic table have been received" ? -- 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/1400#pullrequestreview-125325455 ----==_mimepart_5b11be03edd32_6d223fc45b4eef80280a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -536,6 +536,31 @@ instruction is also processed as a Table Size Synchronize instruction with a
 value matching the Largest Reference of the corresponding header block.
 
 
+### Stream Cancellation
+
+A stream that is reset might have multiple outstanding header blocks.  A decoder
+that receives a stream reset before the end of a stream generates a Stream
+Cancellation instruction on the decoder stream.  Similarly, a decoder that
+abandons reading of a stream needs to signal this using the Stream Cancellation
+instruction.  This signals to the encoder that all references to the dynamic
+table on that stream are no longer outstanding.
+
+An encoder cannot infer from this acknowledgement that any dynamic table entries
+referenced have been received.

I think you're trying to say that the encoder can't make any assumptions about the state of the dynamic table, as can be done with header acknowledgement.

"...cannot infer from this acknowledgement any updates to the dynamic table have been received" ?

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

----==_mimepart_5b11be03edd32_6d223fc45b4eef80280a4-- From nobody Fri Jun 1 16:04:06 2018 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 0EE3112E03E for ; Fri, 1 Jun 2018 16:04:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 kB-S46YNoa2a for ; Fri, 1 Jun 2018 16:04:03 -0700 (PDT) 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 E367712E03C for ; Fri, 1 Jun 2018 16:04:02 -0700 (PDT) Date: Fri, 01 Jun 2018 16:04:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894241; bh=0UJsPQqjd8Mj2gdW4dJnIB32yxrT47H96OF8RAFQHFA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HNbACZ3soHfwBdLGHsCwHzFdJrZovS0bpNHypT1OjLyjA037qQwcnK7DWN0K7gpfC GkzqLxQOJHsTfgFXW8L5awpTcVH/Xrlv9cH/TQtJgCwb9EzCgOulKu5Drc0TIfW2uh vpQRHq/ZPoC7pxBlLBupFzEksMGGajGfa0JnyY4I= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Seek more clarity on Largest Reference/Base Index encoding (#1403) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d0e1deba6_40b03f87265b8f78638546"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:04:05 -0000 ----==_mimepart_5b11d0e1deba6_40b03f87265b8f78638546 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > - baseIndex = largestReference + deltaBaseIndex +To save space, Base Index is encoded relative to Largest Reference using a +one-bit sign and the `Delta Base Index` value. A sign bit of 0 indicates that +the Base Index has a greater absolute index than the Largest Reference; the Well the sentence says that the encoder added entries. I don't think that it's a problem to not mention the zero case. -- 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/1403#discussion_r192534196 ----==_mimepart_5b11d0e1deba6_40b03f87265b8f78638546 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-qpack.md:

>  
-    baseIndex = largestReference + deltaBaseIndex
+To save space, Base Index is encoded relative to Largest Reference using a
+one-bit sign and the `Delta Base Index` value.  A sign bit of 0 indicates that
+the Base Index has a greater absolute index than the Largest Reference; the

Well the sentence says that the encoder added entries. I don't think that it's a problem to not mention the zero case.

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

----==_mimepart_5b11d0e1deba6_40b03f87265b8f78638546-- From nobody Fri Jun 1 16:05:14 2018 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 6817B12E03C for ; Fri, 1 Jun 2018 16:05:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 WwrGVQrogZvp for ; Fri, 1 Jun 2018 16:05:11 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 D4D4E12E037 for ; Fri, 1 Jun 2018 16:05:10 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527894310; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=+MqcClUlSDBc4ECDsb0/kTlmeT/ZOCqOiVU3dgvth1g=; b=yZbAAJeVBn6VPZk/jvhY6PzqoYbkIXjyTuihhKTgRxyLcfw2KEZezsN62OdDdqLCJINZKOzS qZJtOCyOxQlQQxp+AAt6Of994OVp7ACUV0ZfM8NtBhYsFwdnpZYWrCtBTYEz5dpzZeOnx0h2 pMS2RQL8K/1YmvCanM58SSKMA80= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b11d125.7f9859172390-smtp-out-n03; Fri, 01 Jun 2018 23:05:09 -0000 (UTC) Date: Fri, 01 Jun 2018 16:05:09 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b11d12578697_703b2ae8ad377c0482551@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ca856f: Clarify 'packet protection' -> 'packet number prot... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11d12578245_703b2ae8ad377c04824cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:05:13 -0000 ----==_mimepart_5b11d12578245_703b2ae8ad377c04824cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: ca856fa137ac7c769b14a320deefb2ee8019eccf https://github.com/quicwg/base-drafts/commit/ca856fa137ac7c769b14a320deefb2ee8019eccf Author: Alessandro Ghedini Date: 2018-06-01 (Fri, 01 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Clarify 'packet protection' -> 'packet number protection' Commit: 912dae190fe22d1f8bc07be5a7b0e6d90fc6cae1 https://github.com/quicwg/base-drafts/commit/912dae190fe22d1f8bc07be5a7b0e6d90fc6cae1 Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Merge pull request #1406 from ghedo/tls-pn-fixes Clarify 'packet protection' -> 'packet number protection' Compare: https://github.com/quicwg/base-drafts/compare/b1957c863eab...912dae190fe2 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11d12578245_703b2ae8ad377c04824cf-- From nobody Fri Jun 1 16:05:24 2018 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 AACAE12E056 for ; Fri, 1 Jun 2018 16:05:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 d2McLkWjO1n1 for ; Fri, 1 Jun 2018 16:05:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0312912E03E for ; Fri, 1 Jun 2018 16:05:14 -0700 (PDT) Date: Fri, 01 Jun 2018 16:05:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894312; bh=cZNc1foFsWOefHOS1+JOPe69M3Bwirt2GGkPYFGhm30=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Mmf1xFuu/O11DKl5VIiHpc7rBA2K2/GczNhVkRtorvXY7SmPRSvolPD/0bWMa5Hxw pkYFHClqa6mmqxyxeb9zMJqyxZIWvn6CBxBkJNlMHKsOwQOboJFsKEjYZHkqd5A9W+ mU8bVJXsq5IsD837M2vpxP9ZKBkLgHlyx6laGuBw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d128daa5a_57883fae535bef782027e4"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:05:18 -0000 ----==_mimepart_5b11d128daa5a_57883fae535bef782027e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1406. -- 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/1406#event-1659333573 ----==_mimepart_5b11d128daa5a_57883fae535bef782027e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1406.

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

----==_mimepart_5b11d128daa5a_57883fae535bef782027e4-- From nobody Fri Jun 1 16:05:58 2018 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 7B0D212E03E for ; Fri, 1 Jun 2018 16:05:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fUIIR2My9j4U for ; Fri, 1 Jun 2018 16:05:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF7E412E037 for ; Fri, 1 Jun 2018 16:05:55 -0700 (PDT) Date: Fri, 01 Jun 2018 16:05:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894355; bh=hHwaDGibUvd0pszTdoU8+Sum4ZxEBwcVx3oCEzhfj8s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jZnUphEn/vVV/YhPzPy3cQdZncZ1IUF1YXFR5zGCTtZ0ts6jCEcEVxbF4z9ridYI6 03S4u6g1Iv62G8t8lEldUvTlq7ryMMJGUoSE7i9q9dZDkT3i9Md1JbMlVFyDBsTzMz HcNu8vmaCUTruW/pXNK9WdG03v2oOgvNFiVjGOiI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify 'packet protection' -> 'packet number protection' (#1406) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d15329c1b_8ec2abc93f86f5429447e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:05:57 -0000 ----==_mimepart_5b11d15329c1b_8ec2abc93f86f5429447e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks for clarifying this. We can consider separately improving the description of the packet protection stuff, but given that it's likely to disappear very soon, let's not make extra work for ourselves. -- 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/1406#issuecomment-394031643 ----==_mimepart_5b11d15329c1b_8ec2abc93f86f5429447e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks for clarifying this. We can consider separately improving the description of the packet protection stuff, but given that it's likely to disappear very soon, let's not make extra work for ourselves.

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

----==_mimepart_5b11d15329c1b_8ec2abc93f86f5429447e-- From nobody Fri Jun 1 16:07:32 2018 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 7B58712E037 for ; Fri, 1 Jun 2018 16:07:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 xgfy4oGW3bfF for ; Fri, 1 Jun 2018 16:07:27 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E630612DA48 for ; Fri, 1 Jun 2018 16:07:26 -0700 (PDT) Date: Fri, 01 Jun 2018 16:07:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894446; bh=iSE2KwcJAyKIXLDNWauYolkNjTmtLUeKY2eBpj7t4us=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=J/TzdehYHbMK9QSo/aVPsooJ2Lus4wlF0Ms6+R8InpG6ICvHRCKhnePuC634fS62v O97EX9iAvS9vvxsyRom/xt4Ruex57AZRxTIvfiW/QkQHZRhIPluzU1YW/G8eiJU5qP rtgFN1HKMBhDuii6nq1nKzKuNfTR4AqySnGQff7U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Largest Reference too big (#1404) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d1ae4d89a_20083f9501ca8f844305"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:07:30 -0000 ----==_mimepart_5b11d1ae4d89a_20083f9501ca8f844305 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You only need a few to police these things: https://medium.com/incerto/the-most-intolerant-wins-the-dictatorship-of-the-small-minority-3f1f83ce4e15 In some cases (this might be that case), the mere possibility of enforcement can suffice. -- 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/1404#issuecomment-394031920 ----==_mimepart_5b11d1ae4d89a_20083f9501ca8f844305 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You only need a few to police these things: https://medium.com/incerto/the-most-intolerant-wins-the-dictatorship-of-the-small-minority-3f1f83ce4e15

In some cases (this might be that case), the mere possibility of enforcement can suffice.

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

----==_mimepart_5b11d1ae4d89a_20083f9501ca8f844305-- From nobody Fri Jun 1 16:08:26 2018 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 B772612DB72 for ; Fri, 1 Jun 2018 16:08:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OTcR3-AvXxpV for ; Fri, 1 Jun 2018 16:08:22 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA7D012DA48 for ; Fri, 1 Jun 2018 16:08:22 -0700 (PDT) Date: Fri, 01 Jun 2018 16:08:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894502; bh=Dpy1BMR2t8tXk7puQoREkGcyl2ffziZq7g7t6IHaAms=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=E9Iy4eGtyEy925SysVv/guYzTAdKyP2RfRuqpySa+LcJzbR7Hisa1UUJ1906taBK3 klamDxMTq4/uZyQTD48t+EE2vUmnrFD+CyiP88T7IAqHzFIW9jTV2LeAyhw3YeGBcO jZGEz4byNk6rBvAK+mQk/Cuab4rkSfR1cHl+zntU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retain use of SETTINGS_ENABLE_PUSH (#718) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d1e62b0fc_5633ff27c2faf7c5974e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:08:25 -0000 ----==_mimepart_5b11d1e62b0fc_5633ff27c2faf7c5974e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit PUSH_PRIORITY is tricky, because pushes and responses can be interdependent. You would simplify PRIORITY, but PUSH_PRIORITY still gets 3/4 of the cases. -- 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/718#issuecomment-394032071 ----==_mimepart_5b11d1e62b0fc_5633ff27c2faf7c5974e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

PUSH_PRIORITY is tricky, because pushes and responses can be interdependent. You would simplify PRIORITY, but PUSH_PRIORITY still gets 3/4 of the cases.

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

----==_mimepart_5b11d1e62b0fc_5633ff27c2faf7c5974e-- From nobody Fri Jun 1 16:08:55 2018 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 E89DB12E85E for ; Fri, 1 Jun 2018 16:08:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 Fo3UOrGfKqQU for ; Fri, 1 Jun 2018 16:08:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E16B12E87B for ; Fri, 1 Jun 2018 16:08:45 -0700 (PDT) Date: Fri, 01 Jun 2018 16:08:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894524; bh=NiENt9RwYyLKmb9IOQHssWN+JUF2Aa+EBBjdKho7tU4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fVtIrkeuzp+Ir1NMlWnNZpp51yVA9KyW3DIzHaFG0RuiUgaKS8eyfNBvo23Z0BZ/q 66J7empOR2u9jLCGclxianZI09b4VenKUsTyPvOiccau7g9oSfqwEDvQg/4LeCzoOE KEq6dDLB65PO+HnTpGc/tGtyZ5fK9a4EboiIBuzk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: move link to absolute-index to 1st Largest Reference mention (#1408) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d1fcad3fa_374e3fa863da0f8427360"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:08:55 -0000 ----==_mimepart_5b11d1fcad3fa_374e3fa863da0f8427360 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson approved this pull request. -- 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/1408#pullrequestreview-125339845 ----==_mimepart_5b11d1fcad3fa_374e3fa863da0f8427360 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

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

----==_mimepart_5b11d1fcad3fa_374e3fa863da0f8427360-- From nobody Fri Jun 1 16:10:37 2018 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 46FB812DB72 for ; Fri, 1 Jun 2018 16:10:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 2LkiHStyno22 for ; Fri, 1 Jun 2018 16:10:33 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 538BE12DA48 for ; Fri, 1 Jun 2018 16:10:33 -0700 (PDT) Date: Fri, 01 Jun 2018 16:10:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894632; bh=SyeG8mw2iZtwrJpRpYK9WbbzOWiiK/wQ/b/pEi3UfNw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y0V/Z3CWRHPtLCk8fIMxaGi4OJASXTSV+pEd6q6Jgp2nqNShIVkvNRECnIgtZdaN0 9M+sW8LLlP7XT29ExLlaFmG502EP74J5d2xxlaxprWqqPFt85B19f3Zp3MCYbqAz0p 9QfMjZylCW+glPUOLgJoaGAtJeSBxh+DpexTA3RM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d268a1683_1cad2addec71af58104055"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:10:35 -0000 ----==_mimepart_5b11d268a1683_1cad2addec71af58104055 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -523,6 +530,12 @@ blocks within a stream have been fully processed. ~~~~~~~~~~ {:#fig-header-ack title="Header Acknowledgement"} +An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging +any dynamic table entries that the header block referenced. That is, this +instruction is also processed as a Table Size Synchronize instruction with a +value matching the Largest Reference of the corresponding header block. Yeah. That way you maintain a single value for largest acknowledged entry and that is updated by TSS and header acknowledgment. It's simpler and ensures correctness more directly. -- 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/1399#discussion_r192534928 ----==_mimepart_5b11d268a1683_1cad2addec71af58104055 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -523,6 +530,12 @@ blocks within a stream have been fully processed.
 ~~~~~~~~~~
 {:#fig-header-ack title="Header Acknowledgement"}
 
+An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging
+any dynamic table entries that the header block referenced.  That is, this
+instruction is also processed as a Table Size Synchronize instruction with a
+value matching the Largest Reference of the corresponding header block.

Yeah. That way you maintain a single value for largest acknowledged entry and that is updated by TSS and header acknowledgment. It's simpler and ensures correctness more directly.

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

----==_mimepart_5b11d268a1683_1cad2addec71af58104055-- From nobody Fri Jun 1 16:10:46 2018 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 EDBA012E03B for ; Fri, 1 Jun 2018 16:10:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 LO8JPk5INGvs for ; Fri, 1 Jun 2018 16:10:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146FC12DB72 for ; Fri, 1 Jun 2018 16:10:38 -0700 (PDT) Date: Fri, 01 Jun 2018 16:10:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894637; bh=Qq10X7oTjgAQdaHGMpB+hzPj/cAMRGgt5/YhLtjsP8A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JqvLxIbh7x1G0nGvnMDMXNXkxigL6TPgmXsKK1avU4jPM77gdZGh0vByO4pcWbZgp +4R/n6XOTlWcIfsXwZXjLBporkHUCkYIpj996f6VUWSwpN7Uwe4c8dnhvrBMeDNry2 eNdGzuM6rwIDrUSeewSquaOdXctsRkqAMahkckpY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: move link to absolute-index to 1st Largest Reference mention (#1408) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d26d709d7_599b2b06164a0f501053d9"; 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.22 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: Fri, 01 Jun 2018 23:10:40 -0000 ----==_mimepart_5b11d26d709d7_599b2b06164a0f501053d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. -- 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/1408#pullrequestreview-125340090 ----==_mimepart_5b11d26d709d7_599b2b06164a0f501053d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

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

----==_mimepart_5b11d26d709d7_599b2b06164a0f501053d9-- From nobody Fri Jun 1 16:15:11 2018 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 12EE412DB72 for ; Fri, 1 Jun 2018 16:15:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 vpTHKZh75huU for ; Fri, 1 Jun 2018 16:15:08 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 7970C12DB6C for ; Fri, 1 Jun 2018 16:15:08 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527894907; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5cu/IHgckOu3H6uhjQJ9v4T+MtpPXPPs3Bn4J2m8TTk=; b=A4TpRVllyeqCGuKJByv670TsQ0f0lQ9dspuG1hidWscgWJHMrE2XCVN2b+WQh323qu7J5ERA 4e5L5PHicEd84uOuWuZSoyjJWiW58hfMwnjg8nvk4wsELV1hhp1vniQx6glevlYO6p5SGI+D 0QJAvMFRZV8NoxVRgY10Me1NSSQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b11d37b.7f67a556c390-smtp-out-n02; Fri, 01 Jun 2018 23:15:07 -0000 (UTC) Date: Fri, 01 Jun 2018 16:15:07 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b11d37b93ec1_24732b273864fc14520d8@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 76be58: Make TSS incremental to Header Acknowledgment as w... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11d37b93a6c_24732b273864fc1451997"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:15:10 -0000 ----==_mimepart_5b11d37b93a6c_24732b273864fc1451997 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/implicit-ack-header-block Home: https://github.com/quicwg/base-drafts Commit: 76be585ca759435bcc9e4e74d8e447176646449c https://github.com/quicwg/base-drafts/commit/76be585ca759435bcc9e4e74d8e447176646449c Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Make TSS incremental to Header Acknowledgment as well **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11d37b93a6c_24732b273864fc1451997-- From nobody Fri Jun 1 16:15:18 2018 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 AB6F412E04D for ; Fri, 1 Jun 2018 16:15:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 u4cKC1HW2Bqn for ; Fri, 1 Jun 2018 16:15:11 -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 EDB1A12DB6C for ; Fri, 1 Jun 2018 16:15:10 -0700 (PDT) Date: Fri, 01 Jun 2018 16:15:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894910; bh=v8+rs7HWxEa0X9kCoe1Nm2gyiCJvDwmlbYjG+UpyX8A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1DtCHaCyIjup3NMrTnn+ZYtvEy4o/5wk9Pyb8WPHkanWckhUyz5uJo/aP3ndHCfLk nsJvHGxVi1jBnDQGH8KQ8kuR5EpDG3Rd+Rai5mS6B+PUQANvvMgaJuhBcHbVjLrxW+ crey7JP8FDaZQhDXPji8AXv/Wmie3kXx647XKZEw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d37e5d104_297123fa3e784cf7c1095b8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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: Fri, 01 Jun 2018 23:15:13 -0000 ----==_mimepart_5b11d37e5d104_297123fa3e784cf7c1095b8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 76be585 Make TSS incremental to Header Acknowledgment as well -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1399/files/68d8875981c1a02803dde70ae9038298e1ff7455..76be585ca759435bcc9e4e74d8e447176646449c ----==_mimepart_5b11d37e5d104_297123fa3e784cf7c1095b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 76be585 Make TSS incremental to Header Acknowledgment as well

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b11d37e5d104_297123fa3e784cf7c1095b8-- From nobody Fri Jun 1 16:16:14 2018 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 DA64112E038 for ; Fri, 1 Jun 2018 16:16:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 bdOGjJf1C7mb for ; Fri, 1 Jun 2018 16:16:10 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1001212DB6C for ; Fri, 1 Jun 2018 16:16:10 -0700 (PDT) Date: Fri, 01 Jun 2018 16:16:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527894969; bh=2B0axpK5hgEllbhb+/gXPWoDmh8FMQyif5otg61SGrc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q3EJ/Q45HHAATYPYvplc7E5MKIcCdJK0r79xyI/b3wsMKJW8wyi6O4J/YKkkNFUql fx0Jh1pw30wWL6V3jSLMc4yVpUbVITHl38OCMQ0UWedD8g4Y9oaU5OYuRSDhBpbjDM ZVbRxZlyWSQ8+P5ljTPWTamVqVLT2bDbFNpZ4pJY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d3b94a4f3_5483ff27c2faf7c69880"; 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.22 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: Fri, 01 Jun 2018 23:16:12 -0000 ----==_mimepart_5b11d3b94a4f3_5483ff27c2faf7c69880 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the total number of dynamic table inserts and duplications since the last Table State Synchronize, encoded as a 7-bit prefix integer. The encoder uses this value to determine which table entries are vulnerable to head-of-line blocking. -A decoder MAY coalesce multiple synchronization updates into a single update. + +A decoder MAY coalesce multiple synchronization updates into a single update. A +decoder MAY rely on Header Acknowledgement instructions to indirectly If the meaning of TSS is changing, then it's no longer a MAY for the decoder to let Header Acknowledgement instructions acknowledge changes. The decoder MUST track the encoder's perspective of what has been acknowledged, and SHOULD send TSS in addition if entries have been added that aren't referenced. -- 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/1399#pullrequestreview-125340770 ----==_mimepart_5b11d3b94a4f3_5483ff27c2faf7c69880 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -491,7 +491,14 @@ instruction begins with the '1' one-bit pattern. The instruction specifies the
 total number of dynamic table inserts and duplications since the last Table
 State Synchronize, encoded as a 7-bit prefix integer.  The encoder uses this
 value to determine which table entries are vulnerable to head-of-line blocking.
-A decoder MAY coalesce multiple synchronization updates into a single update.
+
+A decoder MAY coalesce multiple synchronization updates into a single update.  A
+decoder MAY rely on Header Acknowledgement instructions to indirectly

If the meaning of TSS is changing, then it's no longer a MAY for the decoder to let Header Acknowledgement instructions acknowledge changes. The decoder MUST track the encoder's perspective of what has been acknowledged, and SHOULD send TSS in addition if entries have been added that aren't referenced.

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

----==_mimepart_5b11d3b94a4f3_5483ff27c2faf7c69880-- From nobody Fri Jun 1 16:18:51 2018 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 62A0C12DB72 for ; Fri, 1 Jun 2018 16:18:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 XMfnhjGSZ-d2 for ; Fri, 1 Jun 2018 16:18:46 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93ECF12DB6C for ; Fri, 1 Jun 2018 16:18:46 -0700 (PDT) Date: Fri, 01 Jun 2018 16:18:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895125; bh=sLz64KDbLqXJ8AHew44uCUumCaaBLh8DodlNwtVbT/A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VFO1oDPdbdzyCCSOxsU4qEw3oNuY8Ix9BTOO0f/SBDBvBt2YoHr18Hsy1QB8WjmMM wGU97HHcHZ9f/DT68cooZj47b2G468JL9RYNfAV/wOgqaANjO/+fv9c5QlpcOeL6TZ v9rFDUQ9FJaNkden+xfnVoyMJwDqPQqCL/68Vktc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d455ed6fd_549b2ae85d05ef543776a"; 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.22 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: Fri, 01 Jun 2018 23:18:49 -0000 ----==_mimepart_5b11d455ed6fd_549b2ae85d05ef543776a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think this discussion no longer belongs inside the TSS instruction. If the tracking of decoder state involves the encoder combining information from HA and TSS, and the decoder has to track the encoder's inferences from HA to generate TSS, this is a complex enough system to deserve its own subsection. Then TSS simply says that it advances the greatest acknowledged index by however many entries, and references that subsection. -- 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/1399#issuecomment-394033454 ----==_mimepart_5b11d455ed6fd_549b2ae85d05ef543776a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think this discussion no longer belongs inside the TSS instruction. = If the tracking of decoder state involves the encoder combining informat= ion from HA and TSS, and the decoder has to track the encoder's inference= s from HA to generate TSS, this is a complex enough system to deserve its= own subsection.

Then TSS simply says that it advances the greatest acknowledged index = by however many entries, and references that subsection.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b11d455ed6fd_549b2ae85d05ef543776a-- From nobody Fri Jun 1 16:19:37 2018 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 D696B12E038 for ; Fri, 1 Jun 2018 16:19:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ioLaVXwAwBxX for ; Fri, 1 Jun 2018 16:19:33 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B45012DB72 for ; Fri, 1 Jun 2018 16:19:33 -0700 (PDT) Date: Fri, 01 Jun 2018 16:19:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895172; bh=7QnjkJZRCFxmbpwNoZteAczcYR1eh+F112XobgWcT4g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mgHloksG+osrh3FhgwINY4yx6IPjbU6l1VUV5jvkL/GCQBS31QWmaj+cOFf29wqVU sQAocQJ92pB9KewiTqWC2sBucAFHb7joJsgWOosDDbexy67i7dABDHQFloN6XMh68z k6/0sZdgRpUSMUaDPeUWvwPdNgk0IB9LD2sEI1q8= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d48472884_50822ad82b7e6f5c4528a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 23:19:35 -0000 ----==_mimepart_5b11d48472884_50822ad82b7e6f5c4528a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think we discussed this on the original PR. We didn't see a reason to expressly forbid attempting to decode a new header block on a blocked stream. Consider a response stream with several PUSH_PROMISE frames: even though the first one may be blocked, the next one may have fully arrived and be immediately decodable, and perhaps the decoder wants to decode it while waits. -- 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/1409#issuecomment-394033549 ----==_mimepart_5b11d48472884_50822ad82b7e6f5c4528a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think we discussed this on the original PR. We didn't see a reason = to expressly forbid attempting to decode a new header block on a blocked = stream. Consider a response stream with several PUSH_PROMISE frames: eve= n though the first one may be blocked, the next one may have fully arrive= d and be immediately decodable, and perhaps the decoder wants to decode i= t while waits.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b11d48472884_50822ad82b7e6f5c4528a-- From nobody Fri Jun 1 16:20:18 2018 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 0A8F212E038 for ; Fri, 1 Jun 2018 16:20:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ZE_BjXJsbesX for ; Fri, 1 Jun 2018 16:20:15 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D52612DB6C for ; Fri, 1 Jun 2018 16:20:15 -0700 (PDT) Date: Fri, 01 Jun 2018 16:20:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895214; bh=KT/dvWRxQ5lAxYEhwYbkKdII6n3txYHpiYla0hQIsgA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R8KJh2epadhtyLCPkZvm/q9SrAK9xOnoXdoqi+DqSym5Yq4Nz4lB+njaBRhdHhkWw 7sd6i4yylwZcb2oT5L8VwowPAxk2U8KJYirLlqCGJZTzcrGWKBLyblU7b7NAWYF/WM u2Arc9c6NaGqfChTLcRmSL63t21D2hhjp0yiB8fA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d4ae80ab7_3bd03fa863da0f84501eb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:20:17 -0000 ----==_mimepart_5b11d4ae80ab7_3bd03fa863da0f84501eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit OK, that's not going to happen before I leave. Let's continue next week. -- 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/1399#issuecomment-394033641 ----==_mimepart_5b11d4ae80ab7_3bd03fa863da0f84501eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

OK, that's not going to happen before I leave. Let's continue next week.

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

----==_mimepart_5b11d4ae80ab7_3bd03fa863da0f84501eb-- From nobody Fri Jun 1 16:21:10 2018 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 7481712E038 for ; Fri, 1 Jun 2018 16:21:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 QtGVBkq7-mK6 for ; Fri, 1 Jun 2018 16:21:07 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 DAA2C12DB6C for ; Fri, 1 Jun 2018 16:21:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527895266; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=TWp2lKHxsaYEzWN3VSRXXvThAOhiOGt+lTkfcc188Q0=; b=xwRyqbjiZm+V2rQBEK0/mtNHZoouNYjYDpyElBJNBQeDR6Td0ui4Wy8JkNU3QV23iqQPpJgV SpQD9q1ZPKseu1rItXLJC+5JbWYuKfQnMReJxvlS+g4LkBB40yGU5lZU87esG2UzIxFzb5b6 6nwSYDRs/9HOGJBCVxV/bsNLN6I= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b11d4e1.7f29bda175a0-smtp-out-n02; Fri, 01 Jun 2018 23:21:05 -0000 (UTC) Date: Fri, 01 Jun 2018 16:21:05 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b11d4e1280a6_6d9e2b1f0653dc0c487c5@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 74fa83: A start, but not an end Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11d4e127c0a_6d9e2b1f0653dc0c486e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:21:09 -0000 ----==_mimepart_5b11d4e127c0a_6d9e2b1f0653dc0c486e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/implicit-ack-header-block Home: https://github.com/quicwg/base-drafts Commit: 74fa837a81bea44b9f61a14c96342ee0c4c35985 https://github.com/quicwg/base-drafts/commit/74fa837a81bea44b9f61a14c96342ee0c4c35985 Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- A start, but not an end **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11d4e127c0a_6d9e2b1f0653dc0c486e1-- From nobody Fri Jun 1 16:21:19 2018 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 4D42A12E038 for ; Fri, 1 Jun 2018 16:21:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jJblV0Xd0SO8 for ; Fri, 1 Jun 2018 16:21:08 -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 B92D712DB6C for ; Fri, 1 Jun 2018 16:21:08 -0700 (PDT) Date: Fri, 01 Jun 2018 16:21:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895268; bh=+hJ2MX6BRSLZDEaShME6qOD4trGvaKq7UgiyZBJLkAQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z86fFt+tbEKjqvq3I5uJR8ZN8IsuUA52AOj4kt/KRnk6c4bGkPyAwbL1ilHU8uHqf 2Bo3TgRyL2nb+2UCvAOUWN3mvI0hGD8c//WaoQeItqNEQLSWV56pX/rJd9Gst7SnU7 Hmf6rCdWPs/sd7b4rxcN6nMSgaftlwZF6lVdYBjQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d4e422c96_38132abcd65acf5417519"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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: Fri, 01 Jun 2018 23:21:11 -0000 ----==_mimepart_5b11d4e422c96_38132abcd65acf5417519 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 74fa837 A start, but not an end -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1399/files/76be585ca759435bcc9e4e74d8e447176646449c..74fa837a81bea44b9f61a14c96342ee0c4c35985 ----==_mimepart_5b11d4e422c96_38132abcd65acf5417519 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b11d4e422c96_38132abcd65acf5417519-- From nobody Fri Jun 1 16:21:49 2018 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 DC5B812E03B for ; Fri, 1 Jun 2018 16:21:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 9upHkcwcTMAa for ; Fri, 1 Jun 2018 16:21:46 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 84E5812E038 for ; Fri, 1 Jun 2018 16:21:46 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527895305; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9mi0U6AHM6uCbZMdVroIjRC744EaEwvzvLLonh4lXpw=; b=pasrc8g2M/g0I8/EVW4s0xJWJp4S7UruMI2GrWXOlLSu/1dp+1HZlb3N6FrzHLdccjn0nuK6 cQNqHuSdU8M4d1sdSMKYnDu1IDZTDXzHmQ23naTY4K+XAEf7u4oqVAi2uB0qnG5YmCMwcao9 hxJ/+EsaG7sm9l1q8MezrRKbMUo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b11d509.7f32a4d30e70-smtp-out-n01; Fri, 01 Jun 2018 23:21:45 -0000 (UTC) Date: Fri, 01 Jun 2018 16:21:44 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b11d508a6bf8_20152b1d4198bc08665ba@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 8c182f: Editorial Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11d508a662e_20152b1d4198bc08664bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:21:48 -0000 ----==_mimepart_5b11d508a662e_20152b1d4198bc08664bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ack-reset-stream Home: https://github.com/quicwg/base-drafts Commit: 8c182ff699c0041ee68af265b9b033bc9fa13504 https://github.com/quicwg/base-drafts/commit/8c182ff699c0041ee68af265b9b033bc9fa13504 Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Editorial **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11d508a662e_20152b1d4198bc08664bb-- From nobody Fri Jun 1 16:21:58 2018 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 73ADC12E040 for ; Fri, 1 Jun 2018 16:21:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 D9NIoxeAhGKc for ; Fri, 1 Jun 2018 16:21:49 -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 7F42212E03C for ; Fri, 1 Jun 2018 16:21:49 -0700 (PDT) Date: Fri, 01 Jun 2018 16:21:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895308; bh=9t+amhCSy7pkVVvwNqiUL9rF4zo/SsaI7p95vdIzaS0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IN8s0Y6+yNFnBJV3g4Jzyo7G3RrS2RhgGtRT8z0PxSzYI06WmpiIRXH/mMkIV0m1z AXRR8pSl4NVzOmemHPlkcb+Ac0J41i4xJ0il4oPKuH6nIvuAvr/upFDQaE4ZLnR73B kdPEUvxmiaJKUmkjlindnzMAERT6YTTUQHVKPUEw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d50cc5d18_45882b2506c9ef54921a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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: Fri, 01 Jun 2018 23:21:52 -0000 ----==_mimepart_5b11d50cc5d18_45882b2506c9ef54921a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 8c182ff Editorial -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1400/files/79c66215cac75df4d21acf0b8b01bc151942c717..8c182ff699c0041ee68af265b9b033bc9fa13504 ----==_mimepart_5b11d50cc5d18_45882b2506c9ef54921a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b11d50cc5d18_45882b2506c9ef54921a-- From nobody Fri Jun 1 16:22:40 2018 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 1171112E038 for ; Fri, 1 Jun 2018 16:22:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 io_892wjFlXD for ; Fri, 1 Jun 2018 16:22:36 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69A2512E03B for ; Fri, 1 Jun 2018 16:22:36 -0700 (PDT) Date: Fri, 01 Jun 2018 16:22:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895355; bh=AUfGvpdTwQJ5VXp+z8dmEjWr07P35vbbkhkDbXH9vo8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1GZeo+YtgX1zwIQbwcqxFxYhbCYWzUxz0Cd2+KPHNrdjN3GjoLyDW8QfyhtpK/an3 a/apEndFiAiyw2p4ZwYu0ifwCgxsoxUMR6UoZgfRKvcWEeVHm/i9K7gHRManFjFaAd pzNyWazCAJHb74u/tir+4zo7x6N4Z0wBeXtinn7A= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d53bc51fb_3ade2abfa7846f5c253912"; 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.22 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: Fri, 01 Jun 2018 23:22:38 -0000 ----==_mimepart_5b11d53bc51fb_3ade2abfa7846f5c253912 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah, this was added to reduce any ambiguity between number of header blocks and number of streams, in case an overly savvy decoder noticed there are multiple blocked references in different header blocks on the same stream. -- 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/1409#issuecomment-394033949 ----==_mimepart_5b11d53bc51fb_3ade2abfa7846f5c253912 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yeah, this was added to reduce any ambiguity between number of header blocks and number of streams, in case an overly savvy decoder noticed there are multiple blocked references in different header blocks on the same stream.

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

----==_mimepart_5b11d53bc51fb_3ade2abfa7846f5c253912-- From nobody Fri Jun 1 16:27:50 2018 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 5FDB512DB72 for ; Fri, 1 Jun 2018 16:27:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 5r0Zgx9BwcWP for ; Fri, 1 Jun 2018 16:27:47 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14BCF12DB6C for ; Fri, 1 Jun 2018 16:27:47 -0700 (PDT) Date: Fri, 01 Jun 2018 16:27:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895666; bh=tklE9Zir6QPF1nKhpVXhXJ7u3L/+7IOVDeR8fgCDF/A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MF0A7UpmIiCVv3BpTKFNDqgaOXzYlCNJBlLDOqXtzux5gx8YQxPAN9XqqLB9O92Xk bDloxp4jJqd0xrstLCOikniElz50DdIs2k0DkOEuih9kDG6rf74Opbwc4GYbf5zoYc W+AJ4F1OhuTEhln2BDaEepWqjI8vfhXfvtIb7nMQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retain use of SETTINGS_ENABLE_PUSH (#718) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d6726e6f2_7ff33fdd9ef44f78755da"; 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.22 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: Fri, 01 Jun 2018 23:27:48 -0000 ----==_mimepart_5b11d6726e6f2_7ff33fdd9ef44f78755da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm assuming with this that you never want to make a request dependent on a push. So PUSH_PRIORITY always prioritizes a push, and only has to differentiate whether the target is a push or a request. But that's a departure from what H2 technically supports, so it might be out of scope. -- 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/718#issuecomment-394034588 ----==_mimepart_5b11d6726e6f2_7ff33fdd9ef44f78755da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm assuming with this that you never want to make a request dependent= on a push. So PUSH_PRIORITY always prioritizes a push, and only has to = differentiate whether the target is a push or a request. But that's a de= parture from what H2 technically supports, so it might be out of scope.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b11d6726e6f2_7ff33fdd9ef44f78755da-- From nobody Fri Jun 1 16:31:06 2018 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 5E72B12E03F for ; Fri, 1 Jun 2018 16:31:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 LTQhc2fYVKLv for ; Fri, 1 Jun 2018 16:31:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D387F12E03C for ; Fri, 1 Jun 2018 16:31:02 -0700 (PDT) Date: Fri, 01 Jun 2018 16:31:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527895862; bh=+/zC10WMbInP2QsuQkYov3jQqVndIw19x3kDz8otR8I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EorTe7V5kT4nKKVtdMfcmJtm0fasE5eKjw5TPyCCCkpsHonukei3uniQ/lNV8Oypp U4HKE142uvlYhJ/duRSWKwkKKzKNOcrVP1jQ41+yK3rQOEn2yE/opiNhtw27PA7Fz2 VOch8xEHqG4SGx0KSK7Kh4vI+0wFJ3Uy/EARIU0E= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Seek more clarity on Largest Reference/Base Index encoding (#1403) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d736396d8_6d502ac249884f60519de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 23:31:05 -0000 ----==_mimepart_5b11d736396d8_6d502ac249884f60519de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > - baseIndex = largestReference + deltaBaseIndex +To save space, Base Index is encoded relative to Largest Reference using a +one-bit sign and the `Delta Base Index` value. A sign bit of 0 indicates that +the Base Index has a greater absolute index than the Largest Reference; the I don't see where this sentence says it added entries - are you referring to somewhere else? I think Mike's right here - if the Base Index is equal to LR then the sign bit will be 0. The original text had that, and it's included on lines 578-9 below. Is it clearer if we bring it back up here? I agree we don't need to mention the case where they are both 0 here. > - baseIndex = largestReference + deltaBaseIndex +To save space, Base Index is encoded relative to Largest Reference using a +one-bit sign and the `Delta Base Index` value. A sign bit of 0 indicates that +the Base Index has a greater absolute index than the Largest Reference; the +value of Delta Base Index is added to the Largest Reference to determine the +absolute value of the Base Index. A sign bit of 1 indicates that the Base Index +is smaller than the Base Index. That is: Base Index is smaller than the Largest Reference -- 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/1403#pullrequestreview-125342186 ----==_mimepart_5b11d736396d8_6d502ac249884f60519de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

>  
-    baseIndex = largestReference + deltaBaseIndex
+To save space, Base Index is encoded relative to Largest Reference using a
+one-bit sign and the `Delta Base Index` value.  A sign bit of 0 indicates that
+the Base Index has a greater absolute index than the Largest Reference; the

I don't see where this sentence says it added entries - are you referring to somewhere else? I think Mike's right here - if the Base Index is equal to LR then the sign bit will be 0. The original text had that, and it's included on lines 578-9 below. Is it clearer if we bring it back up here?

I agree we don't need to mention the case where they are both 0 here.

In draft-ietf-quic-qpack.md:

>  
-    baseIndex = largestReference + deltaBaseIndex
+To save space, Base Index is encoded relative to Largest Reference using a
+one-bit sign and the `Delta Base Index` value.  A sign bit of 0 indicates that
+the Base Index has a greater absolute index than the Largest Reference; the
+value of Delta Base Index is added to the Largest Reference to determine the
+absolute value of the Base Index.  A sign bit of 1 indicates that the Base Index
+is smaller than the Base Index.  That is:

Base Index is smaller than the Largest Reference

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

----==_mimepart_5b11d736396d8_6d502ac249884f60519de-- From nobody Fri Jun 1 16:33:19 2018 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 24D4A12E03F for ; Fri, 1 Jun 2018 16:33:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 kKOCi6EMvENQ for ; Fri, 1 Jun 2018 16:33:15 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 6868212E03C for ; Fri, 1 Jun 2018 16:33:15 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527895994; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=bCaumy1/jdXP/qqAfq2KVnTxZ14X4f3DNwYc8YM6FBw=; b=z74iJt3+oHIfluAqG3FtMySD+0iwD6SscgclHDa+uebJ0BXsGzGD0WZ4BfU2W8LS9tGGywk2 xaNwP+60CScN2FvKzyy4k/0QIalkcEayRD5Og8LE9c1Wgt7FZPeZHeAY2Msx8Vb4XWmI34Vn g5XlL7nM2MAdEGd4T+SuIc9DBts= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b11d7b9.7f298dd58cf0-smtp-out-n01; Fri, 01 Jun 2018 23:33:13 -0000 (UTC) Date: Fri, 01 Jun 2018 16:33:12 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b11d7b88c77f_6c552b28cb307c0c474cd@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ea857e: WIP: PUSH_PRIORITY Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11d7b88c17d_6c552b28cb307c0c473b3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:33:17 -0000 ----==_mimepart_5b11d7b88c17d_6c552b28cb307c0c473b3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/strike_the_pushes Home: https://github.com/quicwg/base-drafts Commit: ea857e0f6fbf15ebc0febfaaddc2b3f4ffffd458 https://github.com/quicwg/base-drafts/commit/ea857e0f6fbf15ebc0febfaaddc2b3f4ffffd458 Author: Mike Bishop Date: 2018-06-01 (Fri, 01 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- WIP: PUSH_PRIORITY **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11d7b88c17d_6c552b28cb307c0c473b3-- From nobody Fri Jun 1 16:38:14 2018 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 DAAA012E045 for ; Fri, 1 Jun 2018 16:38:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ebaKMl1CU5v1 for ; Fri, 1 Jun 2018 16:38:11 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBC3612E03F for ; Fri, 1 Jun 2018 16:38:10 -0700 (PDT) Date: Fri, 01 Jun 2018 16:38:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527896290; bh=l79Q23KMRuqXL2FR4j1anqVR1zT4gz7btVhKNersIH4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n/0ZZV7fRePy8+eXWTlMgV7idH/EZ7vPfdBLvfldFpXJ6mqJEhsJ6P9dL2mcF2I4y B5w6MCIbqMyEz6WABkfFRu34BlSO0DXqRcZ3nnprbKCrVlwJ/78qgSfnvPOn6lmm8R NXRLkeW+B7tevb4RhPZywdVqV3va3YNt8Vkian0Q= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11d8e2a929_569a2af1add08f58616c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.22 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: Fri, 01 Jun 2018 23:38:13 -0000 ----==_mimepart_5b11d8e2a929_569a2af1add08f58616c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I see. The draft suggests, however, that the blocked header data remain in its stream's flow control window: ``` While blocked, header field data should remain in the blocked stream's flow control window. ``` While it does not say so explicitly, in practice this recommendation means that the header block won't be read (I _think_ -- depends on how it's framed in HQ?), effectively making the stream blocked on a single header block. (By the way, why is the above `should` and not `SHOULD`?) Nevertheless, I agree that, technically, there is no restriction not to read in as many header blocks as one desires and have them all block the stream. I wonder whether the two sentences quoted in the original report could be phrased better. Feel free to close if you think the current verbiage is OK. It confused me, though. -- 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/1409#issuecomment-394035935 ----==_mimepart_5b11d8e2a929_569a2af1add08f58616c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I see. The draft suggests, however, that the blocked header data rema= in in its stream's flow control window:

                                        While blocked, header =
field data
   should remain in the blocked stream's flow control window.

While it does not say so explicitly, in practice this recommendation m= eans that the header block won't be read (I think -- depends on = how it's framed in HQ?), effectively making the stream blocked on a singl= e header block. (By the way, why is the above should and no= t SHOULD?)

Nevertheless, I agree that, technically, there is no restriction not t= o read in as many header blocks as one desires and have them all block th= e stream. I wonder whether the two sentences quoted in the original repo= rt could be phrased better. Feel free to close if you think the current = verbiage is OK. It confused me, though.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b11d8e2a929_569a2af1add08f58616c-- From nobody Fri Jun 1 16:50:01 2018 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 B575A12E03F for ; Fri, 1 Jun 2018 16:49:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 U6s84v0bLk1t for ; Fri, 1 Jun 2018 16:49:58 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 28F2612E045 for ; Fri, 1 Jun 2018 16:49:58 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527896997; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ankEnnsqZYG8JVKMaRkYujhL8J3BQcvuYfB78gwfmOA=; b=M3gsE8bZbwmtYxkBUxeXnNTtb+oCzX5r+JoEZzX7ZXzVZj91PxBR3wKJ/CEGMOsnVWeqtAiC qOOnAX/PrjusGaxncXaYTO8MzYpvRlLoofq2+3yNdI+47y239PuPfXnxfvqqHkgWrGX3XIeY 3T7mcW0Zwia6qeSQupPFPJ40kDQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b11dba5.7f54326c07b0-smtp-out-n01; Fri, 01 Jun 2018 23:49:57 -0000 (UTC) Date: Fri, 01 Jun 2018 16:49:57 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b11dba535af2_7e282abaaf873c0c189d5@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] dae923: Include equal to, can't be less than itself Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11dba534b1b_7e282abaaf873c0c1881f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:50:00 -0000 ----==_mimepart_5b11dba534b1b_7e282abaaf873c0c1881f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/explain-base-lr Home: https://github.com/quicwg/base-drafts Commit: dae9232c00701b824005df6c9df433504ccae585 https://github.com/quicwg/base-drafts/commit/dae9232c00701b824005df6c9df433504ccae585 Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Include equal to, can't be less than itself **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11dba534b1b_7e282abaaf873c0c1881f-- From nobody Fri Jun 1 16:50:10 2018 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 9C76512E05D for ; Fri, 1 Jun 2018 16:50:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0J76jrVG-Mi4 for ; Fri, 1 Jun 2018 16:50:00 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A09D112E03F for ; Fri, 1 Jun 2018 16:50:00 -0700 (PDT) Date: Fri, 01 Jun 2018 16:49:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527896999; bh=g51kIGaBxHiS1AFHsOBoi16fPXorr5rYEYzsrrPewrw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ucGZOLnua97LWGATpvlWXAeSi2FO35yBEiCj/EKMCTchMydEn1S2cD3w+WCj2UKgW 22rnBLI1v245VMdVz0/y9I9K5sG0aCAcWzQG1JLiPZjn8rF8uhaxUfjpKq3wyG/1KW Ahsk7LEmC2l0e88Fm70HaKaUyyyNZD+aFmSYtOOg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Seek more clarity on Largest Reference/Base Index encoding (#1403) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11dba7cabaf_565b2af1add08f58104371"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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: Fri, 01 Jun 2018 23:50:03 -0000 ----==_mimepart_5b11dba7cabaf_565b2af1add08f58104371 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. dae9232 Include equal to, can't be less than itself -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1403/files/fcd33ba69d4a265dcf9a23850fbdb2317171a8fe..dae9232c00701b824005df6c9df433504ccae585 ----==_mimepart_5b11dba7cabaf_565b2af1add08f58104371 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • dae9232 Include equal to, can't be less than itself

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b11dba7cabaf_565b2af1add08f58104371-- From nobody Fri Jun 1 16:51:26 2018 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 3D52412E049 for ; Fri, 1 Jun 2018 16:51:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 K9dz8DMSDlRS for ; Fri, 1 Jun 2018 16:51:23 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB88912E048 for ; Fri, 1 Jun 2018 16:51:22 -0700 (PDT) Date: Fri, 01 Jun 2018 16:51:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527897082; bh=mjNu20LjtekM7n5Ro23EEAJHgSfkYdp2gI/F+NNAHWc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xH6+6UbeTeSrsfM0rHkqaQtwO8kfis14ggag2ZoVzdvGNKOj2M/YQGv15JSrf7B4h uzObH4n7oab968FOzr7XnltIqpin2n+W+syg8VyouLFaP0EJ9nPvCmTh9uzLSYzJdg I6OfpFfqyJ6asg/RvIttxPqyRJPdNGM4Qy+IeHPA= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Largest Reference too big (#1404) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11dbfa1a4b3_42423f8123e9cf8026947e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 23:51:24 -0000 ----==_mimepart_5b11dbfa1a4b3_42423f8123e9cf8026947e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I can't imagine a scenario where a non-buggy, non-malicious encoder would do this on purpose and needs only the threat of an error to prevent it. But I don't want to prevent a server from calling it an error either. If everyone likes MAY I can live with it. Related question: If a decoder is required to treat something as an error and it doesn't, does the encoder treat the decoder's permissiveness as an error? No encoder would ever check that, so it's really just about declaring your implementation conforms to the specification? Or guidance so you don't accidentally get yourself into trouble? -- 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/1404#issuecomment-394037495 ----==_mimepart_5b11dbfa1a4b3_42423f8123e9cf8026947e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I can't imagine a scenario where a non-buggy, non-malicious encoder wo= uld do this on purpose and needs only the threat of an error to prevent i= t. But I don't want to prevent a server from calling it an error either.= If everyone likes MAY I can live with it.

Related question: If a decoder is required to treat something as an er= ror and it doesn't, does the encoder treat the decoder's permissiveness a= s an error? No encoder would ever check that, so it's really just about = declaring your implementation conforms to the specification? Or guidance= so you don't accidentally get yourself into trouble?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b11dbfa1a4b3_42423f8123e9cf8026947e-- From nobody Fri Jun 1 16:52:17 2018 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 B108D12E045 for ; Fri, 1 Jun 2018 16:52:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 ca5jRzH0g0Mw for ; Fri, 1 Jun 2018 16:52:14 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 D82D812E03F for ; Fri, 1 Jun 2018 16:52:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1527897133; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=3R/RpJCCRof10PzHYOmLec1UElmIs5E9Sh6dpjPr9so=; b=GT2CAyOlSvcm8bfhIeMMyee+ZhvfgUMxymkM4eXrXuhw2i6L7JIkMiVDU85hl9olgXJGMq08 EWv2GQW07xpTi3f9owDgZjS/ZjzorlbAmJooPro+pOG8HSU52zUwgbaRF6QGVFYDPsquBTTB VGDxby3Ws4/scn9HSYVFPKyn+YA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: dtikhonov=litespeedtech.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b11dc2c.7f882c03eae0-smtp-out-n01; Fri, 01 Jun 2018 23:52:12 -0000 (UTC) Date: Fri, 01 Jun 2018 16:52:11 -0700 From: Dmitri Tikhonov Reply-To: Dmitri Tikhonov To: quic-issues@ietf.org Message-ID: <5b11dc2b8a288_8522adffd5a7c08157ee@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ac0672: qpack: move link to absolute-index to 1st Largest ... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b11dc2b89c7b_8522adffd5a7c08156ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Fri, 01 Jun 2018 23:52:16 -0000 ----==_mimepart_5b11dc2b89c7b_8522adffd5a7c08156ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: ac0672b5751a376699b47ab5d7de04791983752b https://github.com/quicwg/base-drafts/commit/ac0672b5751a376699b47ab5d7de04791983752b Author: Dmitri Tikhonov Date: 2018-06-01 (Fri, 01 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- qpack: move link to absolute-index to 1st Largest Reference mention **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b11dc2b89c7b_8522adffd5a7c08156ed-- From nobody Fri Jun 1 16:52:31 2018 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 CCD4E12E048 for ; Fri, 1 Jun 2018 16:52:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 vHvDowK-MjAJ for ; Fri, 1 Jun 2018 16:52:16 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04E0012E03F for ; Fri, 1 Jun 2018 16:52:16 -0700 (PDT) Date: Fri, 01 Jun 2018 16:52:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527897135; bh=kdyC9/PTCxSheneN3/Wc/iqOLDdBVI0C//F6bU/pj8Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0sTa8zUef3TLV5ADVMKOOi9fV0yZIO0oZMgw+fKCXATaliqDNGyOAmUqjuRzq0hpz xREyrmgSsmdZaU115Uv73eycGigoeokC/hCYmAaQYhhBE6fpD69K5dlnX/lyG9SZL0 X9z1gZwFLgZ1QFEmOnWEs8he0fbSVAPv8Wcw/xmo= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: move link to absolute-index to 1st Largest Reference mention (#1408) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11dc2f6078f_1ce62ace46e26f5090694"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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: Fri, 01 Jun 2018 23:52:18 -0000 ----==_mimepart_5b11dc2f6078f_1ce62ace46e26f5090694 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1408. -- 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/1408#event-1659369943 ----==_mimepart_5b11dc2f6078f_1ce62ace46e26f5090694 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1408.

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

----==_mimepart_5b11dc2f6078f_1ce62ace46e26f5090694-- From nobody Fri Jun 1 16:53:12 2018 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 1A5DF12E048 for ; Fri, 1 Jun 2018 16:53:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 yCBu7VmjMv93 for ; Fri, 1 Jun 2018 16:53:09 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C313012E045 for ; Fri, 1 Jun 2018 16:53:09 -0700 (PDT) Date: Fri, 01 Jun 2018 16:53:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527897189; bh=i/q4Cz8y4wTd+zH+CwawMHC+FomW+L4q05DF7tWtyS8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tAfLu9euHlju6LJa5a+45YvncDH7E3HJxyg3xJsPn2wuLZxEzRHH8SFnnDltEbUOZ ioEu/9q0HiJHcblPy1r/kplGKBfphiC9UCkKFepxSnrZrbD2tTqzWdaBL4xvc6Yj3X XJvcS/2mMEPGGuxwYXn0xqihD4F0mpjM20ad503U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b11dc652aa64_34cb3fdb87ea4f7819663"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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: Fri, 01 Jun 2018 23:53:11 -0000 ----==_mimepart_5b11dc652aa64_34cb3fdb87ea4f7819663 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit (This is why we don't use "should". This isn't an interoperability requirement, it's a *suggestion*.) If the words can be improved, great. I'm not seeing anything obvious right now. -- 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/1409#issuecomment-394037741 ----==_mimepart_5b11dc652aa64_34cb3fdb87ea4f7819663 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

(This is why we don't use "should". This isn't an interoperability requirement, it's a suggestion.)

If the words can be improved, great. I'm not seeing anything obvious right now.

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

----==_mimepart_5b11dc652aa64_34cb3fdb87ea4f7819663-- From nobody Fri Jun 1 20:51:48 2018 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 2C828124BE8 for ; Fri, 1 Jun 2018 20:51:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 K4B8Wey5ObxQ for ; Fri, 1 Jun 2018 20:51:44 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B213D1200E5 for ; Fri, 1 Jun 2018 20:51:44 -0700 (PDT) Date: Fri, 01 Jun 2018 20:51:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527911503; bh=PoqPSed5KG8PfoIrnAK7uXGrOHjD3AWgTvFWuC8AWM4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vU5vJn/lMI9uvQoQrLNdL/YL4WHtlYeItIc+bNT8hlz/K0kuUVXdiAuax4fdy6ZaA fxcN28yJC/ZzrvRjZImhw54lb0bH31SsdrepoLKDhI4ZQnoMCAPjQ56lJxP2P7P6LY vrRPLGLJ3nGoxkeyrjyMeV+k57iujgYkFYYarn5g= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b12144fb5047_1d2f2aac72bfaf6012054e"; 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.22 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: Sat, 02 Jun 2018 03:51:46 -0000 ----==_mimepart_5b12144fb5047_1d2f2aac72bfaf6012054e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The new BCP14 says that we MAY use "should" to make suggestions, however. ;-) How about an RFC6919 "OUGHT TO"? -- 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/1409#issuecomment-394055620 ----==_mimepart_5b12144fb5047_1d2f2aac72bfaf6012054e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The new BCP14 says that we MAY use "should" to make suggestions, however. ;-) How about an RFC6919 "OUGHT TO"?

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

----==_mimepart_5b12144fb5047_1d2f2aac72bfaf6012054e-- From nobody Fri Jun 1 20:56:19 2018 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 38745124BE8 for ; Fri, 1 Jun 2018 20:56:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Ieqkmh_vgmwo for ; Fri, 1 Jun 2018 20:56:15 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7156E126B7E for ; Fri, 1 Jun 2018 20:56:15 -0700 (PDT) Date: Fri, 01 Jun 2018 20:56:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527911774; bh=7UxRmV2L0RXxuPM/lQlWqYnbmXkZIewasNOJkoV6heM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wTybyND/V90Sel0PbpNh1+URItWNnX+AN+6JrFTiqsLMl1VFLUeCXYtv98xZBhdBl 3/ftT4y/MFpHoutQHf36zxBYW3WuFGBVyJhwMFlPmOmwe+bBOzZZXx2T4Yp/IhPmbz JiBCwdJcx5E9hGTm5vGRilCHdDpbZeHSLa7gAh6g= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Largest Reference too big (#1404) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b12155dc8cbc_40a92af8464a4f5c121090"; 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.22 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: Sat, 02 Jun 2018 03:56:17 -0000 ----==_mimepart_5b12155dc8cbc_40a92af8464a4f5c121090 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit No *production* encoder would ever check that, but there are test suites that intentionally violate certain prohibitions to confirm that the tested peer does, in fact, kill the session. But ultimately, it's about declaring conformance. At Microsoft, there was a procedural step where we had to disclose and document any deviations from the protocol, and complying with MUSTs is part of that. -- 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/1404#issuecomment-394055831 ----==_mimepart_5b12155dc8cbc_40a92af8464a4f5c121090 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

No production encoder would ever check that, but there are te= st suites that intentionally violate certain prohibitions to confirm that= the tested peer does, in fact, kill the session. But ultimately, it's a= bout declaring conformance. At Microsoft, there was a procedural step wh= ere we had to disclose and document any deviations from the protocol, and= complying with MUSTs is part of that.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b12155dc8cbc_40a92af8464a4f5c121090-- From nobody Sat Jun 2 06:43:31 2018 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 8984A12D87C for ; Sat, 2 Jun 2018 06:43:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 q0M2W0UI7QLj for ; Sat, 2 Jun 2018 06:43:28 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2800126CD8 for ; Sat, 2 Jun 2018 06:43:27 -0700 (PDT) Date: Sat, 02 Jun 2018 06:43:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527947006; bh=KB6b//W/6hNQv87wdo/xYGG1qOnA/+YFuxWjXcO+tn4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RkVwEQcxYcLsArC/OMPEUpXPzuGA1evWxy8ECoaP5ayfjT1jn++KGTTKqbOjcJYe6 U4sT2awC5RcI01eIT1nVwzPtkMFERscMqMtufTQvV/hUCo6qxjiu4m3YP96EbDfaSV 3BeWjTn0GRm4Z7P507O1Zz96p6Kvi8Hj34KCpjDI= From: Lars Eggert Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b129efe1a38f_4d142ae2570e2f54139158"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.22 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: Sat, 02 Jun 2018 13:43:30 -0000 ----==_mimepart_5b129efe1a38f_4d142ae2570e2f54139158 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit larseggert commented on this pull request. > + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: +: Initial value = 0, incremented when a packet marked ECT(0) is received + +ECT_1: + +: Initial value = 0, incremented when a packet marked ECT(1) is received + +CE: + +: Initial value = 0, incremented when a packet marked CE is received + +Reception of duplicate packets SHOULD NOT increment the counters. Agree -- 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/1372#discussion_r192559987 ----==_mimepart_5b129efe1a38f_4d142ae2570e2f54139158 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@larseggert commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

Agree

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

----==_mimepart_5b129efe1a38f_4d142ae2570e2f54139158-- From nobody Sat Jun 2 22:10:33 2018 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 161F7124F57 for ; Sat, 2 Jun 2018 22:10:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.263 X-Spam-Level: X-Spam-Status: No, score=-0.263 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 EIq3-fD1x2oG for ; Sat, 2 Jun 2018 22:10:29 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 735E1126579 for ; Sat, 2 Jun 2018 22:10:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528002628; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=krucQNSNk4KI5J84AFyrnGZkFpSAdO8ObT80narfPIc=; b=nYuzouZaz6ymC6yNybwln+/lgH/8vrv0G+xtuOm1Jjqp8sg7dBzpHQuLRf9CvWpu8X5Vqrv5 J0WK5LsHRVnWIjPdNHM0wOR/OCEmntv1YvDusljK6cd8dOmkMtdGr0U2ppWrbI0G7O0zUPbZ Ps+F24+1Od7YWx4BX0k0pXgmjrM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b137844.7f376d50bb10-smtp-out-n02; Sun, 03 Jun 2018 05:10:28 -0000 (UTC) Date: Sat, 02 Jun 2018 22:10:28 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1378444f258_74e52ad558809c086840@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c9cfcf: State Synchronization section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1378444ea90_74e52ad558809c086776"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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: Sun, 03 Jun 2018 05:10:31 -0000 ----==_mimepart_5b1378444ea90_74e52ad558809c086776 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: c9cfcf9159b0a73dd643cef229187eb0cdd8da04 https://github.com/quicwg/base-drafts/commit/c9cfcf9159b0a73dd643cef229187eb0cdd8da04 Author: Mike Bishop Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- State Synchronization section **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1378444ea90_74e52ad558809c086776-- From nobody Sat Jun 2 22:14:39 2018 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 762C5126579 for ; Sat, 2 Jun 2018 22:14:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 t62VRpTHJaKO for ; Sat, 2 Jun 2018 22:14:36 -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 DFA18124F57 for ; Sat, 2 Jun 2018 22:14:35 -0700 (PDT) Date: Sat, 02 Jun 2018 22:14:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528002874; bh=HCR3olAu8i4zwOXrZeyhoyODZ0oDQW9NhzRswN7hhp0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=olfur0ABK99iZNwpSp/PBc1TWkyOLKWr1j3y3CYekhs2RnoNknQADet6Gjl8I2RtO 4Ci/P6s3GXXTnzxcVHrWF+lpr8cZSMx+17rpnGOtbjipAfyXIH1jNoL0eNZe1mPTlv VV1ENv3IFqmRkAGKeNenDff97ZqgGSif3oYYq0d4= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b13793abce5_16c82ad11eb0ef542759f2"; 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.22 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: Sun, 03 Jun 2018 05:14:38 -0000 ----==_mimepart_5b13793abce5_16c82ad11eb0ef542759f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This feels like a huge wall of text, and I could use some help making it more readable. However, it attempts to pull out the text from #1399 into its own section and describe the process of making sure encoder and decoder are on the same page. Closes #1399, because I have those commits in here but have relocated most of the text. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1410 -- Commit Summary -- * Implicit acknowledgment via header block acknowledgment * Make TSS incremental to Header Acknowledgment as well * A start, but not an end * State Synchronization section -- File Changes -- M draft-ietf-quic-qpack.md (60) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1410.patch https://github.com/quicwg/base-drafts/pull/1410.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/1410 ----==_mimepart_5b13793abce5_16c82ad11eb0ef542759f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This feels like a huge wall of text, and I could use some help making it more readable. However, it attempts to pull out the text from #1399 into its own section and describe the process of making sure encoder and decoder are on the same page.

Closes #1399, because I have those commits in here but have relocated most of the text.

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

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

Commit Summary

  • Implicit acknowledgment via header block acknowledgment
  • Make TSS incremental to Header Acknowledgment as well
  • A start, but not an end
  • State Synchronization section

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 mute the thread.

----==_mimepart_5b13793abce5_16c82ad11eb0ef542759f2-- From nobody Sun Jun 3 22:39:56 2018 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 64F49120724 for ; Sun, 3 Jun 2018 22:39:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 YShQ1T67VDwG for ; Sun, 3 Jun 2018 22:39:52 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D317C1200E5 for ; Sun, 3 Jun 2018 22:39:51 -0700 (PDT) Date: Sun, 03 Jun 2018 22:39:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528090789; bh=pS+WJ/wY4gA2zNC/SkIMhPBpaMrENfopHJ/c2aD7Tp4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zbPZpPGAiUGZkn40e9LodLN7MEJqCf3HW7W8T6yZkJsnoj10X7qy1u0WUZOKRt4Hx 9jtmnYc9g48m8HaFMzx00gxO2TTNJ/F+o7Vgr7XQGP1c8bsGVcpoMFkJf+Tbf/+vW6 6BAC7cRWJxYFasCsX6z/LzztYqQh3GC0/GiyvjbQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14d0a5bc90a_7fe73fe09e17ef8090490"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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, 04 Jun 2018 05:39:55 -0000 ----==_mimepart_5b14d0a5bc90a_7fe73fe09e17ef8090490 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 8e8e819 necessary, but not doubly necessary -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1410/files/c9cfcf9159b0a73dd643cef229187eb0cdd8da04..8e8e81900a8f82ee6fa8d3d8ec7e0515d5cb5423 ----==_mimepart_5b14d0a5bc90a_7fe73fe09e17ef8090490 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

  • 8e8e819 necessary, but not doubly necessary

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b14d0a5bc90a_7fe73fe09e17ef8090490-- From nobody Sun Jun 3 22:40:02 2018 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 D315C1200E5 for ; Sun, 3 Jun 2018 22:39:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 Yw9l3rfeLcU2 for ; Sun, 3 Jun 2018 22:39:54 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 09173120454 for ; Sun, 3 Jun 2018 22:39:53 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528090793; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=WLTllQEUAa91Uo109VYYMVGWSWAYh/2GUusezLuIuOA=; b=qB0XQ+JQ/PYmx5EIY4HJNSR5hNMJt8r8ZuhszioSHYJ5p1vr8zvimdQh6G8EsZ7I3Bganju0 Ka1vHxqpePSJZbib1PoLaVfuSLGGG17FebZDCL/j5xlZtJ8H9jZDsn0s0da01nN/cWn4K64L LHIHZ3Nf2wTf+3zGfosikFNJGYs= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b14d0a8.7f7ab337d600-smtp-out-n03; Mon, 04 Jun 2018 05:39:52 -0000 (UTC) Date: Sun, 03 Jun 2018 22:39:51 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b14d0a79c586_29fe2ab79409fc10481@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 8e8e81: necessary, but not doubly necessary Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b14d0a79c11a_29fe2ab79409fc104791"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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, 04 Jun 2018 05:39:56 -0000 ----==_mimepart_5b14d0a79c11a_29fe2ab79409fc104791 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: 8e8e81900a8f82ee6fa8d3d8ec7e0515d5cb5423 https://github.com/quicwg/base-drafts/commit/8e8e81900a8f82ee6fa8d3d8ec7e0515d5cb5423 Author: Mike Bishop Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- necessary, but not doubly necessary **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b14d0a79c11a_29fe2ab79409fc104791-- From nobody Sun Jun 3 22:43:20 2018 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 D5686120713 for ; Sun, 3 Jun 2018 22:43:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 BpezCA9dGVOV for ; Sun, 3 Jun 2018 22:43:16 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 397181200E5 for ; Sun, 3 Jun 2018 22:43:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528090995; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=OOCj9N06aZqmz3O/C7QKCevzd9SesAwrAJlUYHAY0HU=; b=F4CeRw4KWjczhShkgAwltgXTVRnEonmhNfYTTvZIHYjX8TILJKbk8KQyQLhQfrwdbbHwZyLw UY5zubRdE1Reh7DVOxHT/ociRUVMQi7D48ghpmt76TVLif4mQY0TC5fePF6QhmDH6ycLpcf+ ErnuUEA3GoRQCrwNScJN2N9p/xM= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b14d173.7f3384060f90-smtp-out-n03; Mon, 04 Jun 2018 05:43:15 -0000 (UTC) Date: Sun, 03 Jun 2018 22:43:15 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b14d1734d33a_719e2ae7c0309c10283b7@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d6cb88: You know what I meant Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b14d1734ccd6_719e2ae7c0309c1028244"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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, 04 Jun 2018 05:43:18 -0000 ----==_mimepart_5b14d1734ccd6_719e2ae7c0309c1028244 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: d6cb886ad0f38d60440827a92175cbd9812777c5 https://github.com/quicwg/base-drafts/commit/d6cb886ad0f38d60440827a92175cbd9812777c5 Author: Mike Bishop Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- You know what I meant **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b14d1734ccd6_719e2ae7c0309c1028244-- From nobody Sun Jun 3 22:43:29 2018 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 0FE52120713 for ; Sun, 3 Jun 2018 22:43:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3ak3wI3MM1Ew for ; Sun, 3 Jun 2018 22:43:18 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 561C01200E5 for ; Sun, 3 Jun 2018 22:43:18 -0700 (PDT) Date: Sun, 03 Jun 2018 22:43:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528090997; bh=cY2juVRw4p90Cdszi4PJMWaU+sKW/yEj6spC4lg8mQQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Uj7/vDTAZVbGEoddWVtF8hKH8hSEKCEJetqaoLYrNYhq1h7z2yYPXl3uiM7yGL4jt YYWPpuA63gQqX7nxJZ6YWRBH4G61GGZzDipSDe86xm4hQjqTu1wEVdBVCoZCsf2s6h oJfWIf1C30zGYo++UCF54DawiphIhJrLSF4j3vm0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14d175b00ea_21ef3fa127e8cf8010734cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.22 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, 04 Jun 2018 05:43:20 -0000 ----==_mimepart_5b14d175b00ea_21ef3fa127e8cf8010734cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. d6cb886 You know what I meant -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1410/files/8e8e81900a8f82ee6fa8d3d8ec7e0515d5cb5423..d6cb886ad0f38d60440827a92175cbd9812777c5 ----==_mimepart_5b14d175b00ea_21ef3fa127e8cf8010734cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b14d175b00ea_21ef3fa127e8cf8010734cf-- From nobody Mon Jun 4 01:00:26 2018 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 B2D3C12426E for ; Mon, 4 Jun 2018 01:00:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.503 X-Spam-Level: X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 60eJdAqOJiwt for ; Mon, 4 Jun 2018 01:00:23 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 11DE1120726 for ; Mon, 4 Jun 2018 01:00:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528099222; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Sd7VBp3xZsHheP97FJznrnLhrPKLCXCpNuk0yf3kEYA=; b=c2puLQVj1HO1tHWp7SLn8W7cOvHGEHeX7B2lu9RmZJdRbYca6oCzIN2Mb8i2FYu/RKDfGiNq 1UvHAZPgzsAUMKJ9LczagUER+6IWsr/ooamJo2sS/LO+fydgFPuHRm3KFNa+m2cqExDGWAlF 8yrniMHTRodDkAKUgtXrbjFNG1c= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b14f195.7f2523d77c00-smtp-out-n02; Mon, 04 Jun 2018 08:00:21 -0000 (UTC) Date: Mon, 04 Jun 2018 01:00:20 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b14f194b28a1_30812ad1ead53c0c158af@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] dd83b1: Seek more clarity on Largest Reference/Base Index ... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b14f194b23c0_30812ad1ead53c0c157ba"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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, 04 Jun 2018 08:00:25 -0000 ----==_mimepart_5b14f194b23c0_30812ad1ead53c0c157ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: dd83b15aaab55d8dc7190671f7ee2032e3dd342f https://github.com/quicwg/base-drafts/commit/dd83b15aaab55d8dc7190671f7ee2032e3dd342f Author: Martin Thomson Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Seek more clarity on Largest Reference/Base Index encoding (#1403) * Seek more clarify on Largest Reference/Base Index encoding * Tweaks from review * Alan's comments * Include equal to, can't be less than itself **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b14f194b23c0_30812ad1ead53c0c157ba-- From nobody Mon Jun 4 01:00:43 2018 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 3B42C12426E for ; Mon, 4 Jun 2018 01:00:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 T_QLD7cfHH-E for ; Mon, 4 Jun 2018 01:00:26 -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 1F8DD120726 for ; Mon, 4 Jun 2018 01:00:26 -0700 (PDT) Date: Mon, 04 Jun 2018 01:00:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528099225; bh=johsyiqyHZeU/VLdq+VS3uQoWo9GpXQzu4v6lOhCnAM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BnPgCgMs7sc9OHp4n4OlsbAVPyowzgwpy0ogktQufUdfDPJ7NRjits2a7H2i5CTnY dncjsHiHVRGhcPesMcrj4kFlln4dYABD8emdL+61o15/2gd2FX6mZtptao0Dh+md81 ay4vt50mAN0Kk4Jo1tcB8lYDcu3QFew5RSuZgo8s= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Seek more clarity on Largest Reference/Base Index encoding (#1403) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14f199548a6_12872b0e50a98f606607db"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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, 04 Jun 2018 08:00:34 -0000 ----==_mimepart_5b14f199548a6_12872b0e50a98f606607db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1403. -- 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/1403#event-1660634102 ----==_mimepart_5b14f199548a6_12872b0e50a98f606607db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1403.

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

----==_mimepart_5b14f199548a6_12872b0e50a98f606607db-- From nobody Mon Jun 4 01:16:11 2018 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 78C141243F3 for ; Mon, 4 Jun 2018 01:16:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Teusq1hSDoeP for ; Mon, 4 Jun 2018 01:16:07 -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 749371243F6 for ; Mon, 4 Jun 2018 01:16:07 -0700 (PDT) Date: Mon, 04 Jun 2018 01:16:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528100166; bh=XZNSh8AJ9SSaKzRRkvkCTWd88jajyYYgwHMHEoK609Y=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=HKR9HyhMNe/vge+D3nrD6OVgW7euS1Ac437cvPS6gI8TROLOLTLr7nGeOOTDSg7jp w9QjvUfwEW5nq+TLbCargkcABa64yT+G+wJZMDDyWz7pptFKlxZYmFQXtXn387iyep ayhJMNiecTVSW3B04N/jKVbPKoC1CleoIDg3wuZQ= From: Magnus Westerlund Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Added ECN to Agenda (#41) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14f546789d9_3ae3fbb6aa5cf841025037"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.22 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, 04 Jun 2018 08:16:10 -0000 ----==_mimepart_5b14f546789d9_3ae3fbb6aa5cf841025037 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/41 -- Commit Summary -- * Added ECN to Agenda -- File Changes -- M interim-18-06/agenda.md (1) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/41.patch https://github.com/quicwg/wg-materials/pull/41.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/wg-materials/pull/41 ----==_mimepart_5b14f546789d9_3ae3fbb6aa5cf841025037 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/41

Commit Summary

  • Added ECN to Agenda

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 mute the thread.

----==_mimepart_5b14f546789d9_3ae3fbb6aa5cf841025037-- From nobody Mon Jun 4 01:30:29 2018 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 750C81243F3 for ; Mon, 4 Jun 2018 01:30:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 CbYLiaP8ifZE for ; Mon, 4 Jun 2018 01:30:26 -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 0C41B1242F5 for ; Mon, 4 Jun 2018 01:30:25 -0700 (PDT) Date: Mon, 04 Jun 2018 01:30:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528101024; bh=06AKhVhTY8C6Efs/F58p9kfH3T6+p2fr79KoF/J7gPw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=qRgfnm/U5KSh3bY//7enYO/uHswiKPMzP/DTTufv+nq7LrxyrHQeklY06EqDvQ+jB 1AiCITz8wrdfEtFqm/KDS2WZt1+O3ap7Te5tXM+bsqs1D8obIjIJlfOJPwZgtQCvs+ A0eUcv3ObBXoTCpILkAMmnXtaXY1Yf9HMkQkPvhg= From: Magnus Westerlund Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Presentation with local Information for the Interim (#42) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14f8a013a9_60442acab8154f5c91673b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.22 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, 04 Jun 2018 08:30:28 -0000 ----==_mimepart_5b14f8a013a9_60442acab8154f5c91673b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/42 -- Commit Summary -- * Presentation with local Information for the Interim -- File Changes -- A interim-18-06/quic-interim-18-06-Local-Information.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/42.patch https://github.com/quicwg/wg-materials/pull/42.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/wg-materials/pull/42 ----==_mimepart_5b14f8a013a9_60442acab8154f5c91673b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/42

Commit Summary

  • Presentation with local Information for the Interim

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 mute the thread.

----==_mimepart_5b14f8a013a9_60442acab8154f5c91673b-- From nobody Mon Jun 4 01:37:22 2018 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 490D4124BAC for ; Mon, 4 Jun 2018 01:37:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 zqbx3RnIQkXC for ; Mon, 4 Jun 2018 01:37:19 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92CBA1243F3 for ; Mon, 4 Jun 2018 01:37:19 -0700 (PDT) Date: Mon, 04 Jun 2018 01:37:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528101438; bh=8K9lIpx40ONJOmLCt64fXUPqDL3OodXUtGxqkfLyqXk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZXuv++hvfPYEbm1Ypke33v4M2boWFTO+SEvvZEuBXLcHDN20PmyN3JXh9cQLCJash M4qkNVkk+XOtx4V2hlBSNZobFnXX3w6HI2nK1TI5LUCtwwF6nOFg2vnpXsuky4gX93 kMDn015WDTP8+OoqpkPvL4IyxjY5kmBKD+Tb5lTc= From: Lars Eggert Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Presentation with local Information for the Interim (#42) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14fa3ea0bf8_507f2abe15856f5811501a2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.22 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, 04 Jun 2018 08:37:21 -0000 ----==_mimepart_5b14fa3ea0bf8_507f2abe15856f5811501a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #42. -- 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/wg-materials/pull/42#event-1660705097 ----==_mimepart_5b14fa3ea0bf8_507f2abe15856f5811501a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #42.

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

----==_mimepart_5b14fa3ea0bf8_507f2abe15856f5811501a2-- From nobody Mon Jun 4 01:37:28 2018 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 577FA1243F3 for ; Mon, 4 Jun 2018 01:37:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 5hJGfpz1SuVx for ; Mon, 4 Jun 2018 01:37:20 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 10318124B18 for ; Mon, 4 Jun 2018 01:37:20 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528101439; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=n7B2eLfmM75EivNbPL7KXOaubXKo4Lo71r29tge7ilQ=; b=xFVO0znXJucOLNvY8hL2nu7rCTaNIiHEr43YKjqEKVmQw7opmo4N6wP/gKUpqgEKO7j/246D oDb5Oe25p2rdIk91ZNqCToTg6khYbrRLkm6bt7SviyYM7nny8B7R0jLCEbPRTPzTiJMTNYnG pHGhTDyE/Q5P3mKTAD6O+xG6fFY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b14fa3e.7f29c87fb510-smtp-out-n02; Mon, 04 Jun 2018 08:37:18 -0000 (UTC) Date: Mon, 04 Jun 2018 01:37:17 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b14fa3d4f7c3_4c52ac69ec9dc10708a2@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 4f6c45: Presentation with local Information for the Interi... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b14fa3d4f27d_4c52ac69ec9dc107079c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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, 04 Jun 2018 08:37:22 -0000 ----==_mimepart_5b14fa3d4f27d_4c52ac69ec9dc107079c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 4f6c45637ebb87ce3d693720a9252b54d465d4fd https://github.com/quicwg/wg-materials/commit/4f6c45637ebb87ce3d693720a9252b54d465d4fd Author: Magnus Westerlund Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: A interim-18-06/quic-interim-18-06-Local-Information.pdf Log Message: ----------- Presentation with local Information for the Interim Commit: 8b908d4a8ac167268e304fb3217287627c45a479 https://github.com/quicwg/wg-materials/commit/8b908d4a8ac167268e304fb3217287627c45a479 Author: Lars Eggert Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: A interim-18-06/quic-interim-18-06-Local-Information.pdf Log Message: ----------- Merge pull request #42 from gloinul/master Presentation with local Information for the Interim Compare: https://github.com/quicwg/wg-materials/compare/300fe3bb7843...8b908d4a8ac1 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b14fa3d4f27d_4c52ac69ec9dc107079c-- From nobody Mon Jun 4 01:37:37 2018 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 A4F43124B18 for ; Mon, 4 Jun 2018 01:37:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 MMxWCaCIdxLm for ; Mon, 4 Jun 2018 01:37:31 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2E301243FE for ; Mon, 4 Jun 2018 01:37:30 -0700 (PDT) Date: Mon, 04 Jun 2018 01:37:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528101450; bh=uvVJdLsACZz7iTfxDcLPUnFs7/5UNtl/Nx7JfoIyaJE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IuW95C5BW0fT7q5POjXuY2/M5XYnUnBjFd1RP7K9oN1TDHm4JL+AJMVsHaIuuANa0 EnJe2R9A7aIjq3SQjl2Iw7iPbcOoe4r100I/PrfkLkmRL/XA3pCkhp3KqdF4ggJ3FP elXk+ubsyyRPZnf4P7KPVOcxVZrzWHT24J2669Hw= From: Lars Eggert Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Added ECN to Agenda (#41) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14fa4a20d9e_540c3f9126582f7c771443"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.22 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, 04 Jun 2018 08:37:33 -0000 ----==_mimepart_5b14fa4a20d9e_540c3f9126582f7c771443 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #41. -- 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/wg-materials/pull/41#event-1660705484 ----==_mimepart_5b14fa4a20d9e_540c3f9126582f7c771443 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #41.

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

----==_mimepart_5b14fa4a20d9e_540c3f9126582f7c771443-- From nobody Mon Jun 4 01:37:43 2018 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 293E91243FE for ; Mon, 4 Jun 2018 01:37:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 rPuggkQK26Bz for ; Mon, 4 Jun 2018 01:37:30 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 BA6FE1243F3 for ; Mon, 4 Jun 2018 01:37:30 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528101450; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=m/tbmwofRSmtwbr9coZAZ63szVNwStNq5i5ASQC9/tQ=; b=gGic4YyniDt0EEycqM+dKXf6kPYRN2OiMvcywyJD/Te8IIyNW/rFIU1Wjyy6qr6XBTzBMgZi ni7pq+BFsj0YYWaso2k2WuZ5oO8VPb4cygAPUNEg++82q1wp8lUKuE8+Vai7MzQubBgBqIOM oZt/iNB/2SSXbA3dBYrVKS+2AvY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b14fa4a.7f7fea1cdf90-smtp-out-n02; Mon, 04 Jun 2018 08:37:30 -0000 (UTC) Date: Mon, 04 Jun 2018 01:37:29 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b14fa491529d_24de2aebc1a8dc0c46477@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] d58f03: Added ECN to Agenda Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b14fa4914eaa_24de2aebc1a8dc0c46341"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 Precedence: list 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, 04 Jun 2018 08:37:37 -0000 ----==_mimepart_5b14fa4914eaa_24de2aebc1a8dc0c46341 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: d58f035664545b3d389d5e7f9742264856d5c355 https://github.com/quicwg/wg-materials/commit/d58f035664545b3d389d5e7f9742264856d5c355 Author: Magnus Westerlund Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Added ECN to Agenda Commit: 8bd047bb6cb16a7eda4e73f96feb91343e4d3962 https://github.com/quicwg/wg-materials/commit/8bd047bb6cb16a7eda4e73f96feb91343e4d3962 Author: Lars Eggert Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Merge pull request #41 from gloinul/patch-3 Added ECN to Agenda Compare: https://github.com/quicwg/wg-materials/compare/8b908d4a8ac1...8bd047bb6cb1 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b14fa4914eaa_24de2aebc1a8dc0c46341-- From nobody Mon Jun 4 01:45:38 2018 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 235271243F3 for ; Mon, 4 Jun 2018 01:45:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Mpl2jWo8fPcO for ; Mon, 4 Jun 2018 01:45:34 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39BD7124B18 for ; Mon, 4 Jun 2018 01:45:34 -0700 (PDT) Date: Mon, 04 Jun 2018 01:45:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528101933; bh=iqUyryX1fcSMqW4c4+sBoMtT9lwLLz+UZlgZlBEA0EQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UWh24sbbzmwePPUKvwNEwx92I6WA5ouwcm+0B/k36/083sPrvs8HcRK68J5ZeuONA V4uSKJxpnXlNUw2XXanCRq+j8r97JgihEOEv9AzJFPe6X+csMu7u4NQ91jTqJL1x8G Xi8rIkoxsuqCAvvwu1ee2iDgzLFeRVnS7Vd9hM+4= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b14fc2d91fea_3fd62aac7ae24f546403f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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, 04 Jun 2018 08:45:37 -0000 ----==_mimepart_5b14fc2d91fea_3fd62aac7ae24f546403f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > +The decoder stream signals key events at the decoder that permit the encoder to +track the decoder's state. These events are: + +- Successful processing of a header block +- Abandonment of a stream which might have remaining header blocks +- Receipt of new dynamic table entries + +Regardless of whether a header block contained blocking references, the +knowledge that it was processed successfully permits the encoder to avoid +evicting entries while references remain outstanding; see {{blocked-eviction}}. +When a stream is reset or abandoned, the indication that these header blocks +will never be processed serves a similar function. + +For the encoder to identify which dynamic table entries can be safely used +without a stream becoming blocked, the encoder tracks the Largest Known Received +absolute index in the decoder's state. "in the decoder's state" sounds kind of weird. Maybe "the encoder tracks the absolute index of the decoder's Largest Known Received entry. > +- Successful processing of a header block +- Abandonment of a stream which might have remaining header blocks +- Receipt of new dynamic table entries + +Regardless of whether a header block contained blocking references, the +knowledge that it was processed successfully permits the encoder to avoid +evicting entries while references remain outstanding; see {{blocked-eviction}}. +When a stream is reset or abandoned, the indication that these header blocks +will never be processed serves a similar function. + +For the encoder to identify which dynamic table entries can be safely used +without a stream becoming blocked, the encoder tracks the Largest Known Received +absolute index in the decoder's state. + +When blocking references are permitted, the encoder uses acknowledgement of +header blocks for this purpose. If a header block was potentially blocking, the "for this purpose" reads ambiguously to me. > +- Abandonment of a stream which might have remaining header blocks +- Receipt of new dynamic table entries + +Regardless of whether a header block contained blocking references, the +knowledge that it was processed successfully permits the encoder to avoid +evicting entries while references remain outstanding; see {{blocked-eviction}}. +When a stream is reset or abandoned, the indication that these header blocks +will never be processed serves a similar function. + +For the encoder to identify which dynamic table entries can be safely used +without a stream becoming blocked, the encoder tracks the Largest Known Received +absolute index in the decoder's state. + +When blocking references are permitted, the encoder uses acknowledgement of +header blocks for this purpose. If a header block was potentially blocking, the +successful processing of the block by the decoder implies that all dynamic table receipt of a header acknowledgement implies this -- 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/1410#pullrequestreview-125472428 ----==_mimepart_5b14fc2d91fea_3fd62aac7ae24f546403f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

> +The decoder stream signals key events at the decoder that permit the encoder to
+track the decoder's state.  These events are:
+
+- Successful processing of a header block
+- Abandonment of a stream which might have remaining header blocks
+- Receipt of new dynamic table entries
+
+Regardless of whether a header block contained blocking references, the
+knowledge that it was processed successfully permits the encoder to avoid
+evicting entries while references remain outstanding; see {{blocked-eviction}}.
+When a stream is reset or abandoned, the indication that these header blocks
+will never be processed serves a similar function.
+
+For the encoder to identify which dynamic table entries can be safely used
+without a stream becoming blocked, the encoder tracks the Largest Known Received
+absolute index in the decoder's state.

"in the decoder's state" sounds kind of weird. Maybe "the encoder tracks the absolute index of the decoder's Largest Known Received entry.

In draft-ietf-quic-qpack.md:

> +- Successful processing of a header block
+- Abandonment of a stream which might have remaining header blocks
+- Receipt of new dynamic table entries
+
+Regardless of whether a header block contained blocking references, the
+knowledge that it was processed successfully permits the encoder to avoid
+evicting entries while references remain outstanding; see {{blocked-eviction}}.
+When a stream is reset or abandoned, the indication that these header blocks
+will never be processed serves a similar function.
+
+For the encoder to identify which dynamic table entries can be safely used
+without a stream becoming blocked, the encoder tracks the Largest Known Received
+absolute index in the decoder's state.
+
+When blocking references are permitted, the encoder uses acknowledgement of
+header blocks for this purpose.  If a header block was potentially blocking, the

"for this purpose" reads ambiguously to me.

In draft-ietf-quic-qpack.md:

> +- Abandonment of a stream which might have remaining header blocks
+- Receipt of new dynamic table entries
+
+Regardless of whether a header block contained blocking references, the
+knowledge that it was processed successfully permits the encoder to avoid
+evicting entries while references remain outstanding; see {{blocked-eviction}}.
+When a stream is reset or abandoned, the indication that these header blocks
+will never be processed serves a similar function.
+
+For the encoder to identify which dynamic table entries can be safely used
+without a stream becoming blocked, the encoder tracks the Largest Known Received
+absolute index in the decoder's state.
+
+When blocking references are permitted, the encoder uses acknowledgement of
+header blocks for this purpose.  If a header block was potentially blocking, the
+successful processing of the block by the decoder implies that all dynamic table

receipt of a header acknowledgement implies this

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

----==_mimepart_5b14fc2d91fea_3fd62aac7ae24f546403f7-- From nobody Mon Jun 4 04:58:19 2018 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 6949212D943 for ; Mon, 4 Jun 2018 04:58:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oUZLYeheEta1 for ; Mon, 4 Jun 2018 04:58:15 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C9AB126D45 for ; Mon, 4 Jun 2018 04:58:15 -0700 (PDT) Date: Mon, 04 Jun 2018 04:58:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528113494; bh=Pg/ahDRS9Q4OM7sUEifdV+IHZ51OG55+z4x441doPgo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1gbdBGishzjL6d4wEqrGod7mkPAWbcpyIYfzHwtrZ3iMWZgqyMziNsS1wEUl6JxYe iIC8/vjz+lUTPpO3LCQhrDA0ya9pdhqjT14KiwrIqKzcTp7DhhGUac5CGrkoqsnwml vvF2i+kQi7fXHbVDr7C9xnd9WalSFbgQomR6+zMo= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b152956988ca_5def3f7e3d060f7c5467f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.22 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, 04 Jun 2018 11:58:18 -0000 ----==_mimepart_5b152956988ca_5def3f7e3d060f7c5467f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closing -- it seems that I am the only one who thinks the wording is problematic. -- 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/1409#issuecomment-394329720 ----==_mimepart_5b152956988ca_5def3f7e3d060f7c5467f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closing -- it seems that I am the only one who thinks the wording is problematic.

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

----==_mimepart_5b152956988ca_5def3f7e3d060f7c5467f8-- From nobody Mon Jun 4 04:58:25 2018 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 F1D67126D45 for ; Mon, 4 Jun 2018 04:58:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Rb0fVDnvFBOD for ; Mon, 4 Jun 2018 04:58:15 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C7AB124319 for ; Mon, 4 Jun 2018 04:58:15 -0700 (PDT) Date: Mon, 04 Jun 2018 04:58:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528113494; bh=7KSyRyp+8LW9YH6zV/xTrzJcemZfqBW6r9dLuI4+ltQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BJo/MBIZ1Dg3OTsxNJuH8GCnJifv0DgfYSM3qOGokfgNotOckeePdATKtkr3RXcdo Vmis06ie/CHBJT15cdp7tQSpye7cFD2Ag7Ty0k+jxKgvFahIhXSVqHyRLZ//aucgi/ 3V7vIwxzMsDGuKl+2RstMb/3tAnb88IXu19qZ8sc= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b152956a77fd_5f092b1187588f545386e0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.22 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, 04 Jun 2018 11:58:18 -0000 ----==_mimepart_5b152956a77fd_5f092b1187588f545386e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1409. -- 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/1409#event-1661107374 ----==_mimepart_5b152956a77fd_5f092b1187588f545386e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1409.

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

----==_mimepart_5b152956a77fd_5f092b1187588f545386e0-- From nobody Mon Jun 4 05:04:22 2018 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 C3B1812D95F for ; Mon, 4 Jun 2018 05:04:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lCWPdDfXiKsZ for ; Mon, 4 Jun 2018 05:04:10 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4C8512D965 for ; Mon, 4 Jun 2018 05:04:09 -0700 (PDT) Date: Mon, 04 Jun 2018 05:04:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528113848; bh=/5UjVgkHcrr2b9qttxh/z2zatOC8TAeXd2apGb4n+KE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gS2K9RP5T2qQWhTtyqOrnKZEY656ZaPom/i3uO5+2qE1ZR0mkey8khUenTEBpcsSQ N4CYOpa51zavsB7iDHIhh+nJBPh1C+MLIaldYMR2cLzj/ANfZz9jaghVLyHLkJd/ju SkOqzg1EcjQBnkuRVhPG26fK4Z6Z7ixLeHcu+nik= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b152ab8dcc5b_42ba3ff091c02f80638583"; 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.22 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, 04 Jun 2018 12:04:21 -0000 ----==_mimepart_5b152ab8dcc5b_42ba3ff091c02f80638583 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett pointed out that this could also be solved by taking the blocking setting back to a Boolean, and @afrind said he doesn't feel as strongly about the integer limit now that he's implemented it. -- 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/1371#issuecomment-394331148 ----==_mimepart_5b152ab8dcc5b_42ba3ff091c02f80638583 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett pointed out that this could also be solved by taking the blocking setting back to a Boolean, and @afrind said he doesn't feel as strongly about the integer limit now that he's implemented it.

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

----==_mimepart_5b152ab8dcc5b_42ba3ff091c02f80638583-- From nobody Mon Jun 4 05:14:24 2018 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 BB55B126E01 for ; Mon, 4 Jun 2018 05:14:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0nmz7VAZrpQN for ; Mon, 4 Jun 2018 05:14:21 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B829124319 for ; Mon, 4 Jun 2018 05:14:21 -0700 (PDT) Date: Mon, 04 Jun 2018 05:14:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528114460; bh=819rlA6SkZTU71qf8zeNrVSbPTiMUqg4k2JEzrFHHuE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qaJzHlDPBRgkJMQD7vrdZaMVRSzt6o6hPczBR+F+8d81B2JSTBT92v8mT1x5larss btNqbrbW/ajqOsEfCs5w6/FPydeQ9rZB3GiNVpaPnuWnk6gXHVlQhTv0hWghJQ3CtK jlYV7zW3n9VC3N53d9vJ+FizUggJNacIB/S9Ab30= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b152d1c85207_3b193fd167bc4f80275039"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.22 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, 04 Jun 2018 12:14:23 -0000 ----==_mimepart_5b152d1c85207_3b193fd167bc4f80275039 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As Mike said, I prefer getting rid of the limit on blocking refs unless there is a very compelling reason to keep it. -- 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/1371#issuecomment-394333474 ----==_mimepart_5b152d1c85207_3b193fd167bc4f80275039 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

As Mike said, I prefer getting rid of the limit on blocking refs unless there is a very compelling reason to keep it.

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

----==_mimepart_5b152d1c85207_3b193fd167bc4f80275039-- From nobody Mon Jun 4 07:00:36 2018 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 E0D7C12D967 for ; Mon, 4 Jun 2018 07:00:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DaDn_HhgjfQp for ; Mon, 4 Jun 2018 07:00:33 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5903D127058 for ; Mon, 4 Jun 2018 07:00:33 -0700 (PDT) Date: Mon, 04 Jun 2018 07:00:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528120832; bh=1jEtOlqiyS7NNVDq8KxNFN2krYH+OAGJk1ZntYW9pNo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rj22iZvA9f/gZdpp312ooEnyaoozkbnJhieJMebsMoYFPI8qjirk+6NmZJVTOf20W n3WG1cCKQiLFgg5M8dUPjw2fDRFe7JGpeS7DKzOT2QAGV8JCbbBebI3JYq/4LzlaFF l7tK+VsfUSmFwsQ5UdyFGdCFazG55i19i5IAIJMQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rejection of 0-RTT: start over? (#761) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15460060122_55fb3f918f9f2f801626ed"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:00:35 -0000 ----==_mimepart_5b15460060122_55fb3f918f9f2f801626ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Duplicate of #390. -- 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/761#issuecomment-394364880 ----==_mimepart_5b15460060122_55fb3f918f9f2f801626ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Duplicate of #390.

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

----==_mimepart_5b15460060122_55fb3f918f9f2f801626ed-- From nobody Mon Jun 4 07:00:46 2018 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 784BA12D969 for ; Mon, 4 Jun 2018 07:00:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 O7JxG7A2JNaQ for ; Mon, 4 Jun 2018 07:00:34 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E35812D964 for ; Mon, 4 Jun 2018 07:00:33 -0700 (PDT) Date: Mon, 04 Jun 2018 07:00:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528120832; bh=hYLA/SvXAlTtyoX1mX9g1R5itZagtvZdDdBDNu0mLMA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AMTMpGWIebQ4OoP1wTXlWQmJi6z9WhJvqrQ9C3QfguJK7fDeDTPzMCW52NY/M2WUO qccVIoMPUacR7NviFuPAZsXT553zNlD0nrDtBe7bVBKqTZNAF02ZVwESOtPB9lt1dI DhmvSI9KqO/Bt1otIp2Jb5tWgLOS+V10exAOkDz8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rejection of 0-RTT: start over? (#761) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b154600ac3f0_39632abf7f156f58243982"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:00:37 -0000 ----==_mimepart_5b154600ac3f0_39632abf7f156f58243982 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #761. -- 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/761#event-1661370468 ----==_mimepart_5b154600ac3f0_39632abf7f156f58243982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #761.

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

----==_mimepart_5b154600ac3f0_39632abf7f156f58243982-- From nobody Mon Jun 4 07:05:32 2018 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 E952C127076 for ; Mon, 4 Jun 2018 07:05:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7TOOAR7ihpfV for ; Mon, 4 Jun 2018 07:05:30 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765F6127058 for ; Mon, 4 Jun 2018 07:05:30 -0700 (PDT) Date: Mon, 04 Jun 2018 07:05:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528121129; bh=Sn+ACIuRJ/G5whLGAeWKIh7MKFANpM/D+47aARzM094=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QkEG97gn/EuSEINCsVjCgmpgO7IKF3n7a63ww8IAb05ivWnG6fHjAvC7YZRpi4KJQ mbJZyKSLSrKeK01O64wbhEjJyDJGGGVo847ntadrS6qNrNUOs8nltcm5mZwZKxiwso D5x1fc7QNcXHLLVM8MKGITVL1Da7pENPm/+oUyKw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Writing after closed frame enqueued (#777) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b154729d4159_33282b2a7a4a8f60197964"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:05:32 -0000 ----==_mimepart_5b154729d4159_33282b2a7a4a8f60197964 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Editors discussed this and while there might be some value in having states that reflect this internally in an API, but we probably don't need to do anything for this in the spec. -- 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/777#issuecomment-394366615 ----==_mimepart_5b154729d4159_33282b2a7a4a8f60197964 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Editors discussed this and while there might be some value in having states that reflect this internally in an API, but we probably don't need to do anything for this in the spec.

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

----==_mimepart_5b154729d4159_33282b2a7a4a8f60197964-- From nobody Mon Jun 4 07:05:45 2018 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 BC4CB127076 for ; Mon, 4 Jun 2018 07:05:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 TXpYVn5HhpAr for ; Mon, 4 Jun 2018 07:05:37 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D4C1127058 for ; Mon, 4 Jun 2018 07:05:37 -0700 (PDT) Date: Mon, 04 Jun 2018 07:05:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528121136; bh=hWsbknJKWoD02ProCOgmqAjasrq8wfNtWNQkxUA6fgI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oEJTuhYA4/S5YwP3/bCbS68rsUthoUJ+JZIeUCoaFJcxooOpv78eOVrdzEr9DqJFt YXojxAsxJBCmXVtpAZfofP8ss8wlp03gSpHBrsmyPuAgB4s2MdqOKpSI2wWoIPJzhn slAFbnorxOIfKkbcxwjR87RJpY2utbkWjR6RFwQw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Send streams with an enqueued close (#1189) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b154730578b3_55b13f8f600e4f7822744b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:05:39 -0000 ----==_mimepart_5b154730578b3_55b13f8f600e4f7822744b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1189. -- 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/1189#event-1661383420 ----==_mimepart_5b154730578b3_55b13f8f600e4f7822744b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1189.

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

----==_mimepart_5b154730578b3_55b13f8f600e4f7822744b-- From nobody Mon Jun 4 07:05:51 2018 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 0C067127058 for ; Mon, 4 Jun 2018 07:05:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 h-zXf9DvS5RV for ; Mon, 4 Jun 2018 07:05:47 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 5B6EA12DA01 for ; Mon, 4 Jun 2018 07:05:47 -0700 (PDT) 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=VqoXpe1NaK2Dv5ACB1RzARrTwjM=; b=GRPLlzcJOYXz99ru r9+gWz+a5fmvNT7ITYuNUGBaAGHqJCw6zBxWdtIgnGRQP28DQ2z5cKljB12jcxOu hVta/a7sh8WVK6bs3VTakG3OGBpZ+TJ33/+5gfMJPGokQerwcWKiqsrNLHv0Q2g+ ZISTl4R8A7LStjhxHVj81b/x4Xg= Received: by filter1770p1mdw1.sendgrid.net with SMTP id filter1770p1mdw1-6225-5B154729-81 2018-06-04 14:05:29.899322877 +0000 UTC Received: from github-lowworker18-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id gTZDALprRwOdm2SkhZ50og for ; Mon, 04 Jun 2018 14:05:29.783 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker18-cp1-prd.iad.github.net (Postfix) with ESMTP id BCF3520BD9 for ; Mon, 4 Jun 2018 07:05:29 -0700 (PDT) Date: Mon, 04 Jun 2018 14:05:29 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Writing after closed frame enqueued (#777) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b154729bb8b4_3e763fa396512f8819549a"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0wzYgtaPaQ+0+e9qGZSfxFvMNmKb8KcIGjp7 D814Hc5ocKa+VKG9hK37GILqetBLSty8V7aXeuZIIvvN0S7F2eDcJz9hT2oPlFZfqoLswqcXXZfAWN UAB3uzcF7V3S6md1TviZ4lF2M3UuJ9BV+CHD40nEvb3Yzi6noIV42OWnTE4qVorELxelFYs0SpTUdt g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:05:49 -0000 ----==_mimepart_5b154729bb8b4_3e763fa396512f8819549a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #777. -- 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/777#event-1661383150 ----==_mimepart_5b154729bb8b4_3e763fa396512f8819549a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #777.

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

----==_mimepart_5b154729bb8b4_3e763fa396512f8819549a-- From nobody Mon Jun 4 07:05:59 2018 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 28FB112D964 for ; Mon, 4 Jun 2018 07:05:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 45cC1OmFuFzi for ; Mon, 4 Jun 2018 07:05:52 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A6112DA0C for ; Mon, 4 Jun 2018 07:05:52 -0700 (PDT) Date: Mon, 04 Jun 2018 07:05:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528121152; bh=e8RgIHXm/v2WaUSjtl5mohNLXpFrQWCydrEN2vPptac=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GvTYFBzuxrqSvdvuJNvbIhD+Ck9+cCEMYgHYV2QcyV8Y4ONYfWoklrJr6s6jdPJXa srb5CNKQ0arWMV0T532H7GBVNWsFxZ4p12AkIxysWSDTY3akfQ1QY1amA4n3ZiezmU DNzOE3pBTl3T9HE8SGZUJ3kEm2d8GA6a7jrMTJG0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Send streams with an enqueued close (#1189) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15474018ba4_63b12b15bc10ef5811712a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:05:54 -0000 ----==_mimepart_5b15474018ba4_63b12b15bc10ef5811712a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit See #777 conclusion. -- 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/1189#issuecomment-394366725 ----==_mimepart_5b15474018ba4_63b12b15bc10ef5811712a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

See #777 conclusion.

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

----==_mimepart_5b15474018ba4_63b12b15bc10ef5811712a-- From nobody Mon Jun 4 07:11:43 2018 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 A4A2F12D964 for ; Mon, 4 Jun 2018 07:11:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KQKT88OqBTX5 for ; Mon, 4 Jun 2018 07:11:40 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53169127058 for ; Mon, 4 Jun 2018 07:11:40 -0700 (PDT) Date: Mon, 04 Jun 2018 07:11:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528121499; bh=HzCjwMVXPNuzH40ijBgz7934bzSANW1T/q6GUoFH1HM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BUUyJ+N7tk91bPme/HXld3Snuf+SYN15lR5cplVoExqsm96LD/fU5MT9YV0uVQoUy aeyO0I685GexAiltVxzOYeKDt58A5YdatdoCEQi+RNX5lvAgHeMgaVYQwAZ9pGNGE7 LOw9/Y3oE9uz+N+nVZQM4A8MmqeUm5G5kawvPFo8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15489b96be4_42ae2b0be6a52f5430521d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 14:11:42 -0000 ----==_mimepart_5b15489b96be4_42ae2b0be6a52f5430521d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit PADDING doesn't elicit ACK. PING does. A packet containing only ACK and PADDING counts towards bytes-in-flight. But that means that you will consume bytes-in-flight by sending these, and maybe never an ACK. So, send a PING sometimes, and you get your bytes-in-flight back. -- 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/838#issuecomment-394368550 ----==_mimepart_5b15489b96be4_42ae2b0be6a52f5430521d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

PADDING doesn't elicit ACK. PING does.

A packet containing only ACK and PADDING counts towards bytes-in-fligh= t. But that means that you will consume bytes-in-flight by sending these= , and maybe never an ACK. So, send a PING sometimes, and you get your by= tes-in-flight back.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b15489b96be4_42ae2b0be6a52f5430521d-- From nobody Mon Jun 4 08:08:41 2018 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 8DDC912DA12 for ; Mon, 4 Jun 2018 08:08:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 24w-KmXwXnWG for ; Mon, 4 Jun 2018 08:08:37 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 842E312DA3D for ; Mon, 4 Jun 2018 08:08:37 -0700 (PDT) Date: Mon, 04 Jun 2018 08:08:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528124916; bh=kX6mMScBoXYjgtZMb0KAjJPyL/OJj7aRBaFSTdKHjS4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=e3b9ypc1HGwaiWu1VYRRmG4whgeLCbkgcMTWdvPhh86bioinMjvU74mDR5Il7gbdQ NR8kLr8tAFZEcPIDrOxeLI3B4J6HrHozHnLaPh9jhtcwfA39XrdxUVzPu+8uiS1HFz CVsA6R+oBeqc09H7uskGr5BKG3kXb0LusvT7grTM= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace HPACK integer encoding (#1148) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1555f44cf42_b4d3fcdee1c0f88538a1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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, 04 Jun 2018 15:08:40 -0000 ----==_mimepart_5b1555f44cf42_b4d3fcdee1c0f88538a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit QPACK seems to have met its goal of being close to HPACK without this additional complexity. -- 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/1148#issuecomment-394389121 ----==_mimepart_5b1555f44cf42_b4d3fcdee1c0f88538a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

QPACK seems to have met its goal of being close to HPACK without this additional complexity.

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

----==_mimepart_5b1555f44cf42_b4d3fcdee1c0f88538a1-- From nobody Mon Jun 4 08:08:47 2018 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 C94F612DA13 for ; Mon, 4 Jun 2018 08:08:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 maM4v7fQ-Ol9 for ; Mon, 4 Jun 2018 08:08:38 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F38C12DA4C for ; Mon, 4 Jun 2018 08:08:38 -0700 (PDT) Date: Mon, 04 Jun 2018 08:08:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528124917; bh=BwAWzU0nNca4UGwRN1jpOctwPiaFALxoeJRiqxy98sA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uDK9mUKkw/wIXQ5eYBrR31NsB09XJlA9UX0IIAwYyCkzOQa7MtrPBe9bbuquKqdYb 5pHcPFa5ilwO5/A0a3KPWtv2svyALs8mo49Pg55hRyEjdYflZXNMeEuLQU20iS5bvF k3TUXGfvM7FvX/AyY2jn9K9XdHYQIHrbaTAXDB4g= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace HPACK integer encoding (#1148) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1555f53a5e7_4bff2afa138caf541370ab"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.22 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, 04 Jun 2018 15:08:40 -0000 ----==_mimepart_5b1555f53a5e7_4bff2afa138caf541370ab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1148. -- 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/1148#event-1661545848 ----==_mimepart_5b1555f53a5e7_4bff2afa138caf541370ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1148.

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

----==_mimepart_5b1555f53a5e7_4bff2afa138caf541370ab-- From nobody Mon Jun 4 08:13:38 2018 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 B1F1712DA0A for ; Mon, 4 Jun 2018 08:13:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 ZYzAIE1eBLo4 for ; Mon, 4 Jun 2018 08:13:35 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D4F312DA08 for ; Mon, 4 Jun 2018 08:13:35 -0700 (PDT) Date: Mon, 04 Jun 2018 08:13:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125215; bh=2BBdbwsTdpKOKOxpRPZ2yDrtrhbMd/gPcY1ecOfu7Q0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NKYj/ihKOfPGpfnhZ/faXjaS4e7/fHHESFEppFt49VDDznKz3zn7PLFIjxuW3Ogcz EwT2nGXMnlotWZO0LGM2KJH6H0FZlU+N/+68mc1jbe7H+oYKrxsGkwWIZws1pRYHVj U6ra7kJS6nKW1XEHUg7hWSROWr+iNhSJn6ZjHCnE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use Conservative Initial Packet Size (#1209) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15571f19217_184093fc8f40aef7c13472d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:13:37 -0000 ----==_mimepart_5b15571f19217_184093fc8f40aef7c13472d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1209. -- 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/1209#event-1661558585 ----==_mimepart_5b15571f19217_184093fc8f40aef7c13472d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1209.

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

----==_mimepart_5b15571f19217_184093fc8f40aef7c13472d-- From nobody Mon Jun 4 08:13:44 2018 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 9020012DA0D for ; Mon, 4 Jun 2018 08:13:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 9T692sHEa6to for ; Mon, 4 Jun 2018 08:13:36 -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 892DC12D965 for ; Mon, 4 Jun 2018 08:13:35 -0700 (PDT) Date: Mon, 04 Jun 2018 08:13:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125214; bh=RhyTilRZ+3KMKSWmMF7id17z0aogtmPkiFxOFAWWggA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xnCTNYH3gBLlAJkSwLaCnacKGvjz1YuCmNK2stVnly9kxoWJ2sfqw6bZ+mybMAzf9 6Ew/DLkGbOIezMqzv4iQdmhLKopaJfTpbI4Xd1msw6b1B1WOrgLnnYjC5JThjQasYk K77BnG3aFvF7kVX30FY/QGfAaz/6eZLpVd/FE0aY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use Conservative Initial Packet Size (#1209) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15571e5931c_7023ff98b1c2f7c120771"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:13:40 -0000 ----==_mimepart_5b15571e5931c_7023ff98b1c2f7c120771 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The path needs to support v6, and this suggests that the path might not support v6. -- 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/1209#issuecomment-394390869 ----==_mimepart_5b15571e5931c_7023ff98b1c2f7c120771 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The path needs to support v6, and this suggests that the path might not support v6.

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

----==_mimepart_5b15571e5931c_7023ff98b1c2f7c120771-- From nobody Mon Jun 4 08:15:59 2018 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 6632112DA0A for ; Mon, 4 Jun 2018 08:15:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 iiHCtqmoIUm1 for ; Mon, 4 Jun 2018 08:15:56 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4298127077 for ; Mon, 4 Jun 2018 08:15:56 -0700 (PDT) Date: Mon, 04 Jun 2018 08:15:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125356; bh=776w6BORFqCa/g3tmq03LHWa8jJz9aK3gcHj4ccCzYQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qkA5TSLmUrOTeXGEBt6cFYv2CVS/m6rMtLkIqjrF1Ab9+gm2rvNUx/7hiaphaJ0v0 o5hIzulUs0te3h/5PxSBUfAM8uXhxW/JG6Y2MtVxfCjMAdWYYBXf1ATSAzeH1PUFsH jDugHJT5J6VpsEEpH4xQ5ygsIqiE0bdJHfjFPo0U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ACKs for receiver-only (#1232) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1557ac29b52_6c53fd25f32ef802462e8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:15:59 -0000 ----==_mimepart_5b1557ac29b52_6c53fd25f32ef802462e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed by #1231. -- 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/1232#issuecomment-394391676 ----==_mimepart_5b1557ac29b52_6c53fd25f32ef802462e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed by #1231.

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

----==_mimepart_5b1557ac29b52_6c53fd25f32ef802462e8-- From nobody Mon Jun 4 08:16:08 2018 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 0B30912DA0D for ; Mon, 4 Jun 2018 08:15:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 cAeayO9HSpdp for ; Mon, 4 Jun 2018 08:15:57 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D811912D965 for ; Mon, 4 Jun 2018 08:15:56 -0700 (PDT) Date: Mon, 04 Jun 2018 08:15:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125356; bh=UOc9nRAKnMO8/KuapyzANOpgeOxwHH8C5/13SB3wttQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SpPZ+j8nzi/ZXvHXCbpZD/SCvAyWTP4q2JReqchmc1ZaNe7k+S09w6Q9eZD5B/x7S jUHdhymXPg5ic21ckR7WrNpdptnGomYUZ0yWjEIi4XTnOiaXvtklb2+SG5aDkycY2y Dd9qPJuvcAPCKojvbZoPIen9DNSFEa/meAbKcTy8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ACKs for receiver-only (#1232) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1557ac235bf_7a5f2b152a00ef50124273"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:15:59 -0000 ----==_mimepart_5b1557ac235bf_7a5f2b152a00ef50124273 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1232. -- 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/1232#event-1661564195 ----==_mimepart_5b1557ac235bf_7a5f2b152a00ef50124273 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1232.

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

----==_mimepart_5b1557ac235bf_7a5f2b152a00ef50124273-- From nobody Mon Jun 4 08:19:24 2018 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 D7FC012DA05 for ; Mon, 4 Jun 2018 08:19:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mUqN3Gt-gzAG for ; Mon, 4 Jun 2018 08:19:21 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BCD5127077 for ; Mon, 4 Jun 2018 08:19:21 -0700 (PDT) Date: Mon, 04 Jun 2018 08:19:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125560; bh=zL2G/COQ71pbz7ceohEQX+KLaxmPxY4zFQVyCKQUBcA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QRTlLqPeJYNQ5f7RRsvzxBhQ3KFXjwaVDyriw8e2gDFAcZTfU9h7gYyCyjzVHHNU7 l5V2dmcHgPmZWd/wxeJH6K7zrfUs2TQmL7WPlBaVIWgykWSkZcanyMZ4mmq5lBYe4v +vhclmK2hJzxvX/g0+wzqZBO/hDhKw4YWjnp+QeY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow repeat ACK's (#1234) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15587880856_1bdb3ff5f8adaf882831e5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:19:23 -0000 ----==_mimepart_5b15587880856_1bdb3ff5f8adaf882831e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The text uses a SHOULD, which is entirely appropriate here. If you have an idea of how to codify more concrete advice, we would be interested in receiving a PR. -- 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/1234#issuecomment-394392963 ----==_mimepart_5b15587880856_1bdb3ff5f8adaf882831e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The text uses a SHOULD, which is entirely appropriate here. If you have an idea of how to codify more concrete advice, we would be interested in receiving a PR.

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

----==_mimepart_5b15587880856_1bdb3ff5f8adaf882831e5-- From nobody Mon Jun 4 08:19:30 2018 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 2A12D127077 for ; Mon, 4 Jun 2018 08:19:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 tHq4_kMXGXva for ; Mon, 4 Jun 2018 08:19:22 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 564DA12DA08 for ; Mon, 4 Jun 2018 08:19:22 -0700 (PDT) Date: Mon, 04 Jun 2018 08:19:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125561; bh=eSu1+58X4nsN4P5V9JbiQCJarScpEEWQFkA8/2jpCkU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zgSam0EmoQV/CygwzRqVzbwQLLIDcEq3Qis6HQrWiAZfLrcXDYaJERFBUQ1uzv5Uj v7+uL2kFqEqGrhp+4FUVdJBAEZ40uMU6+kj489pQkgR8ZK2tfHuk/tx7jAuOa1xtaW tgp0e22vFOa8W5Oz6XjNVzjNffxpcSwJci1oBXQo= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow repeat ACK's (#1234) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b155879b1972_b203fcdee1c0f881175bb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:19:24 -0000 ----==_mimepart_5b155879b1972_b203fcdee1c0f881175bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1234. -- 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/1234#event-1661573252 ----==_mimepart_5b155879b1972_b203fcdee1c0f881175bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1234.

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

----==_mimepart_5b155879b1972_b203fcdee1c0f881175bb-- From nobody Mon Jun 4 08:22:38 2018 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 D5DDF12DA0A for ; Mon, 4 Jun 2018 08:22:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 RnnQUBp15wWZ for ; Mon, 4 Jun 2018 08:22:35 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 525CC127078 for ; Mon, 4 Jun 2018 08:22:35 -0700 (PDT) Date: Mon, 04 Jun 2018 08:22:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125754; bh=NkvZ0lFvYuJbdUUPTnHyMMIvIE7O7O5If09VTw5PGe4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=O4Or1oSbpESxN9Sj6xH/KpM0RjFwGBfEZ7/5BD8bUfo2A908iRoiHp/P9W//6OBcm IQFLPzEsZiz8o2/LrPcsaznHR1wH2d15Q+heMZe9B0SckyhqqwlW4ijTb0vICVrrKh CZE+vEDxXyInAKt696B/tSO8O/S+Po46/wbX/shU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15593aa4446_24892aba906eef5410243f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:22:37 -0000 ----==_mimepart_5b15593aa4446_24892aba906eef5410243f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @enygren, @igorlord, the solutions that you are contemplating here are fairly disruptive to the design. If you feel strongly about this, you should take it to the list and get the attention of the working group. -- 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/1243#issuecomment-394394203 ----==_mimepart_5b15593aa4446_24892aba906eef5410243f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@enygren, @igorlord, the solutions that you are contemplating here are fairly disruptive to the design. If you feel strongly about this, you should take it to the list and get the attention of the working group.

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

----==_mimepart_5b15593aa4446_24892aba906eef5410243f-- From nobody Mon Jun 4 08:24:46 2018 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 6292C12DA11 for ; Mon, 4 Jun 2018 08:24:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 xSZWV9e4i5qG for ; Mon, 4 Jun 2018 08:24:43 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26A32127078 for ; Mon, 4 Jun 2018 08:24:43 -0700 (PDT) Date: Mon, 04 Jun 2018 08:24:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125882; bh=ghjWv7pe2oYgupXKxw+wplO2FYJdQNP5amjXMlG0ccg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=c32Iiyb1w4+byhQ98M2t4cn5nivoxTOVipDymmt56D+M5xIkdl2UzXFo3vFmIG2PQ 0fR4KjdUbctIidT5cy/RT9XGBvcGBqPeQfH0A58xFOiq9n+SDtXKuuRc/jaGcMN0Bv EMD2Au3doC6Ta9jLA+2fVAd+Ws9AwRQA0AGjSzmY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset during Path Migration (#1258) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1559babcf34_7ae52adc42792f54177556"; 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.22 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, 04 Jun 2018 15:24:45 -0000 ----==_mimepart_5b1559babcf34_7ae52adc42792f54177556 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1258. -- 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/1258#event-1661586959 ----==_mimepart_5b1559babcf34_7ae52adc42792f54177556 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1258.

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

----==_mimepart_5b1559babcf34_7ae52adc42792f54177556-- From nobody Mon Jun 4 08:24:53 2018 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 60096127078 for ; Mon, 4 Jun 2018 08:24:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 d4fFR0LHDiwM for ; Mon, 4 Jun 2018 08:24:44 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB87D12DA0C for ; Mon, 4 Jun 2018 08:24:43 -0700 (PDT) Date: Mon, 04 Jun 2018 08:24:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528125883; bh=p3vz4J7vCpC2sGTrZ1OyXcOp2K824737nARjaqDV/DU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lCvlJw8H9SHTGU7GQzP19Z6yZKC5OqRpkEU4TvBlh+bSmvSDPr4HG5sJ9VB5XFDvZ Vpw7hUXLKERxOBjA0yUdwBRJcWv9NdiU/+b+VxQFUQkmuWQjFq4r3OVf62R6M8kDZU O5FkPaPBL5ix1Kd3XnccVrl6RZ31l6B7VF8qACjw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset during Path Migration (#1258) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1559bb37509_4c322afa138caf54189084"; 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.22 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, 04 Jun 2018 15:24:46 -0000 ----==_mimepart_5b1559bb37509_4c322afa138caf54189084 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Same as #1386. -- 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/1258#issuecomment-394395005 ----==_mimepart_5b1559bb37509_4c322afa138caf54189084 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Same as #1386.

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

----==_mimepart_5b1559bb37509_4c322afa138caf54189084-- From nobody Mon Jun 4 08:30:23 2018 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 55A6112DA73 for ; Mon, 4 Jun 2018 08:30:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 anTY7tJwf1Yj for ; Mon, 4 Jun 2018 08:30:10 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B97B412DA25 for ; Mon, 4 Jun 2018 08:30:09 -0700 (PDT) Date: Mon, 04 Jun 2018 08:30:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528126209; bh=tAWhenNM+s0EtnolAzlbUhygJFcKn60QtoDtHR5svJ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0gxp5Ylw4dtNHVtqTFLfDxJoasTR4pxyubHGsxX2TUfnUa6ArPoFr4xTkTg2mK+3p dT9/l0RkA6KUmeqlSd7MMB4Gd/M8udN+EgQsxvFf3+Md+iyUW0yIavjZtnJUhXge65 SAsU9J1yHpszkFguua701WQ+NxZHBEG8juPWzR50= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Invariants extensbility (#1260) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b155b011ab99_4bde2ae00d6f8f5c2264b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:30:21 -0000 ----==_mimepart_5b155b011ab99_4bde2ae00d6f8f5c2264b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1260. -- 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/1260#event-1661601540 ----==_mimepart_5b155b011ab99_4bde2ae00d6f8f5c2264b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1260.

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

----==_mimepart_5b155b011ab99_4bde2ae00d6f8f5c2264b-- From nobody Mon Jun 4 08:30:27 2018 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 E124612DA50 for ; Mon, 4 Jun 2018 08:30:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 xSmaiVMClE-c for ; Mon, 4 Jun 2018 08:30:11 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 76E1B12DA28 for ; Mon, 4 Jun 2018 08:30:10 -0700 (PDT) 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=wyVmbMoVX5MvhNbIPmEqBaa5fCw=; b=qUvF8EFl+C7oFlhu pm2nXdnmZYHaQcTsa2BPIjGPbxvrjAOCKGmRaEZ4CLbGpr57WFeLid9Oatp9WgVv YB/1ey08COooqsbBa6zqumjdXq9cMHgedXkzgZqSWZ4e4jaDB6BR9n+UQHGld17m wdvzhz+BcrNpnXk0229g1jVCwT0= Received: by filter0817p1las1.sendgrid.net with SMTP id filter0817p1las1-3465-5B155B00-18 2018-06-04 15:30:08.569723242 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id hNpfo3adQRSd8a2-ZMhn6w for ; Mon, 04 Jun 2018 15:30:08.301 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id 46AA041080 for ; Mon, 4 Jun 2018 08:30:08 -0700 (PDT) Date: Mon, 04 Jun 2018 15:30:08 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Invariants extensbility (#1260) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b155b0044b19_6a13fd25f32ef802703ef"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2Te4SHPE9nmg+uFtseRmgCRNgVgI4UjSXu3G N/+8kKDKcb0CPrYAkg/GGUwB2gGWIJmdDVWgdJQstmXBY/3XyG6w3RlZy566DShD97wIb6/1W2U1OJ 9DyOzYM0uyTvTi/gVueAicmDR3Db+WwtrV1UvWZtXQ2ujYKRNb8X78Azn7q9Ys0xr4DAynNfGsXjc+ w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:30:22 -0000 ----==_mimepart_5b155b0044b19_6a13fd25f32ef802703ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Based on the discussion here, I'm not seeing a concrete problem. If there are some editorial changes that would improve clarity, we would consider editorial pull requests that did that. If @MikeBishop would like to distill his comment about any future invariants wouldn't really be invariant, then that would be appreciated. -- 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/1260#issuecomment-394397045 ----==_mimepart_5b155b0044b19_6a13fd25f32ef802703ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Based on the discussion here, I'm not seeing a concrete problem.

If there are some editorial changes that would improve clarity, we would= consider editorial pull requests that did that. If @MikeBishop would like to distill his comment about any future= invariants wouldn't really be invariant, then that would be appreciated.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b155b0044b19_6a13fd25f32ef802703ef-- From nobody Mon Jun 4 08:33:10 2018 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 CA045123FC8 for ; Mon, 4 Jun 2018 08:33:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 BPPPj2pzLquM for ; Mon, 4 Jun 2018 08:33:06 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29910122E2F for ; Mon, 4 Jun 2018 08:33:06 -0700 (PDT) Date: Mon, 04 Jun 2018 08:33:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528126385; bh=/axW8a1xEqx9Md14UyvpGqaGtR4vNgR1YpAYrLYoOL4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ohrYd3aCCoetJrwwdRBuhQjhq/+II2FdfrancyNZwU77KlPmcD8RjnYMVKQyj2r7Q 4ETqMEM554fFtSclcCt2MEluYfxHT0nc03aTLd9g4AlQpSBH215fe4DOE2wCT2VxcZ jEh1RFTGI9yAbVR8Gufv5gEneRpMY15xje69dbbE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset processing must be path-bound (#1264) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b155bb180444_70ca2af8e2b9af543437f5"; 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.22 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, 04 Jun 2018 15:33:08 -0000 ----==_mimepart_5b155bb180444_70ca2af8e2b9af543437f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1264. -- 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/1264#event-1661609651 ----==_mimepart_5b155bb180444_70ca2af8e2b9af543437f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1264.

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

----==_mimepart_5b155bb180444_70ca2af8e2b9af543437f5-- From nobody Mon Jun 4 08:33:19 2018 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 69B93123FC8 for ; Mon, 4 Jun 2018 08:33:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 voI7HRz8nH2m for ; Mon, 4 Jun 2018 08:33:10 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 6BA2D122E2F for ; Mon, 4 Jun 2018 08:33:09 -0700 (PDT) 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=zNKHQPAJJ2Jj7VAhD0h0DQ2GspI=; b=KdMRwQycILHdLlT/ vt9uTyUb/MbYn6zI8WQ8jmKAgSaRtVS7p5GjftPEbslVe5NjS7qElKVoW4bglWnZ Fek+m5mELzDdXxyLxgBW7MVEAFr3m7i8GbZeT7vBHmg2WJYcZ1gudp0OTF+IfOlB erMgAUYLlqcHiRn35L7viGtauQk= Received: by filter1233p1las1.sendgrid.net with SMTP id filter1233p1las1-22162-5B155BB0-26 2018-06-04 15:33:04.499411916 +0000 UTC Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id -B2Aond2SxCoat_7xqAYhQ for ; Mon, 04 Jun 2018 15:33:04.389 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id 5C62A3E0281 for ; Mon, 4 Jun 2018 08:33:04 -0700 (PDT) Date: Mon, 04 Jun 2018 15:33:04 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset processing must be path-bound (#1264) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b155bb05a1ab_1c802ac21bbc8f602652fd"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak01B682KK0wfq/V8JVnCLOpHOJ3dbDW9Qq39F N3XV9TKFGQ+P8/m7CuIAzJ+WJUFbcfVbtYv2i6t9bB5/G6OZNGDl1pwPTF2d+i+U+QkiMdk+aclc8N OoSk9e0B+jis2kfxV143vRguUHm2izwRxEUKw52Jw42Tmb0NAjJLre/dwLEHDSzFW3mqYaZLIw17Gf o= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.22 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, 04 Jun 2018 15:33:13 -0000 ----==_mimepart_5b155bb05a1ab_1c802ac21bbc8f602652fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson is reasonably convincing that if a valid SR has been created, the token has leaked and the connection needs to be destroyed even if it's faked. -- 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/1264#issuecomment-394398250 ----==_mimepart_5b155bb05a1ab_1c802ac21bbc8f602652fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson is reasonably convincing that if a valid SR has been created, the token has leaked and the connection needs to be destroyed even if it's faked.

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

----==_mimepart_5b155bb05a1ab_1c802ac21bbc8f602652fd-- From nobody Mon Jun 4 09:11:56 2018 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 17084129452 for ; Mon, 4 Jun 2018 09:11:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 YgkLVRGd1GHo for ; Mon, 4 Jun 2018 09:11:52 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50FDA12071F for ; Mon, 4 Jun 2018 09:11:52 -0700 (PDT) Date: Mon, 04 Jun 2018 09:11:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528128710; bh=pJ2H6aaDBd1WXXvyPha2oSqVIQjjjZJlSWSysG7Rq2I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0drS4Gx9fcPGBWvmuo8WEptDn4WnjkW3MmBdj8eY13kCWBVLUNzHGKRgZlt0aIg+Y qdgfc4VCK8eCZzTSdsllBCiYyVyTOaEuZ8QmDhMRCR22f9Bk32dvhNSk/mvwcOkZOt tX2L1lhZMyGUEqqL1bDxs/wVnFdII7OEcR56//3g= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Invariants extensbility (#1260) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1564c656954_1c752ac21bbc8f604644e4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.22 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, 04 Jun 2018 16:11:55 -0000 ----==_mimepart_5b1564c656954_1c752ac21bbc8f604644e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agree with closing. Same request to @MikeBishop as @martinthomson. -- 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/1260#issuecomment-394411683 ----==_mimepart_5b1564c656954_1c752ac21bbc8f604644e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Agree with closing. Same request to @MikeBishop as @martinthomson.

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

----==_mimepart_5b1564c656954_1c752ac21bbc8f604644e4-- From nobody Mon Jun 4 11:44:53 2018 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 E3833130DEF for ; Mon, 4 Jun 2018 11:44:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 y6aZFAN57bBu for ; Mon, 4 Jun 2018 11:44:43 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 D596E130DD1 for ; Mon, 4 Jun 2018 11:44:43 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528137883; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=S58UDcIViZfxum8MhOLzplzE819st01NhmkkK89OmYQ=; b=fQkwhF5fUt5+m4twljh7EhyLeoQy7fIvePfwgcMp483L7vxTfr9s3n/fk8puJp4Q81jZ9S6i WpncuRyK5rDjwtMAaff/q7a7zP3smJSq4XZEd+/Jo8nK3qXPdFjsm3ZAIVhXswNMDS+GAsde G3V9eMbb3Z8LI07JLeOXUFZssBw= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b15889a.7fc0a4ff02d0-smtp-out-n01; Mon, 04 Jun 2018 18:44:42 -0000 (UTC) Date: Mon, 04 Jun 2018 11:44:41 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b158899d8865_6e0e2b0f212b5c049575b@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 8cb0d2: What if invariants change? Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b158899d84f1_6e0e2b0f212b5c049566"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 04 Jun 2018 18:44:52 -0000 ----==_mimepart_5b158899d84f1_6e0e2b0f212b5c049566 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/change_invariants Home: https://github.com/quicwg/base-drafts Commit: 8cb0d2086381ce815748793eb61ad79b7c9bf9f0 https://github.com/quicwg/base-drafts/commit/8cb0d2086381ce815748793eb61ad79b7c9bf9f0 Author: Mike Bishop Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- What if invariants change? **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b158899d84f1_6e0e2b0f212b5c049566-- From nobody Mon Jun 4 11:46:22 2018 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 98DC8130DC7 for ; Mon, 4 Jun 2018 11:46:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 TAlY-phmcu3G for ; Mon, 4 Jun 2018 11:46:16 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 96E29130DCC for ; Mon, 4 Jun 2018 11:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=NEXkt9ZOxSxGv/08roYB94a06MQ=; b=ikVCwoTcVEDniUBW QGSaDa2y+oPpBijMRX/QiGKRnmqz6uR7TUiq1t6n20GXUM5uHisKbpZQg52cGZzW jEVye291h39AkF//Pl3o+GhA4UtrvA3LINuWWsuy1DpnxkIGZgOhDEuGZDF1cHGd dbV90c72nmSQrOgi3YiZTKcCWzk= Received: by filter1570p1mdw1.sendgrid.net with SMTP id filter1570p1mdw1-31946-5B1588F6-20 2018-06-04 18:46:14.553393349 +0000 UTC Received: from github-lowworker-cbd19a4.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id QrEcrk9HQsKT5g32MWLg3g for ; Mon, 04 Jun 2018 18:46:14.403 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cbd19a4.cp1-iad.github.net (Postfix) with ESMTP id 608A758069C for ; Mon, 4 Jun 2018 11:46:14 -0700 (PDT) Date: Mon, 04 Jun 2018 18:46:14 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1588f65efa6_2678c3f8c3eea2f7c154116e"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0QtkHREufQCU73ML3YwdCDe9pwnBK90QxAAx YEFz9acmtScCybqi8RG8l8Ii6AR66ouif2qomiGEm5h4AqFVqLCbsCGhtYnaRWejpndcGJXbNJf9jU TFKTltyqAVs47hG+pguyNXk0lKT94KRQQNAmjz367t1Y9eQwbb3r2EZo1T59k5LvXFI7ZZ57ffTVmY I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jun 2018 18:46:21 -0000 ----==_mimepart_5b1588f65efa6_2678c3f8c3eea2f7c154116e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1260. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1411 -- Commit Summary -- * What if invariants change? -- File Changes -- M draft-ietf-quic-invariants.md (4) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1411.patch https://github.com/quicwg/base-drafts/pull/1411.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/1411 ----==_mimepart_5b1588f65efa6_2678c3f8c3eea2f7c154116e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1260.

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

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

Commit Summary

  • What if invariants change?

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 mute the thread.

----==_mimepart_5b1588f65efa6_2678c3f8c3eea2f7c154116e-- From nobody Mon Jun 4 12:19:10 2018 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 C86BD130DCE for ; Mon, 4 Jun 2018 12:19:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 T8kddlF2MH2u for ; Mon, 4 Jun 2018 12:19:06 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AEEF130DCC for ; Mon, 4 Jun 2018 12:19:06 -0700 (PDT) Date: Mon, 04 Jun 2018 12:19:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528139945; bh=zjELPcmreTXkRzIVhAhaK2nEZRORE7f9rnOdqOnJiLY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mjNE6EGo8vDgVGU65s9yH8OeDaQ9Ue/NOyWr0HlAPCkLglwpF5ZP+ipL8E4bPApz3 nSncOL6lCzFytUyBDFB6x4pNRFyBZwfgvgp9C0vwtFvHTMxaj/BTW9SqbTiyE6tZJ+ MCtNIU1bBc6dExuctCYbsVaMY19FC0QrtMPmPuic= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1590a938cd_4cf42ac21bbc8f601446413"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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, 04 Jun 2018 19:19:08 -0000 ----==_mimepart_5b1590a938cd_4cf42ac21bbc8f601446413 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Looks good to me. Just a nit on text that this commit isn't changing. > The primary goal of this document is to ensure that it is possible to deploy new versions of QUIC. By documenting the _things_ that can't change It would perhaps be cleaner to say documenting the _properties_ that can't change instead. -- 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/1411#issuecomment-394467705 ----==_mimepart_5b1590a938cd_4cf42ac21bbc8f601446413 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Looks good to me.

Just a nit on text that this commit isn't changing.

The primary goal of this document is to ensure that it is possible to = deploy new versions of QUIC. By documenting the things that can'= t change
It would perhaps be cleaner to say documenting the properties th= at can't change instead.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1590a938cd_4cf42ac21bbc8f601446413-- From nobody Mon Jun 4 12:19:34 2018 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 0332F130DCE for ; Mon, 4 Jun 2018 12:19:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 AgTPu3k35csl for ; Mon, 4 Jun 2018 12:19:30 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F4D6130DCC for ; Mon, 4 Jun 2018 12:19:30 -0700 (PDT) Date: Mon, 04 Jun 2018 12:19:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528139969; bh=+e7+C9vc8Mvj3yxSmcz5JdaRHNhMl+jaLRVV6xF5Z0U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TwWGY2crAjCJqiCPxCaJDW7OpwYAUf0XiGJaWqzREjJI/gr9PNj0WuAdPIJRCAl1m Kjedt/yFkHMeS+Q4MTzA9hcih4NXNh4YxM6Hfet7NO1Qw6onpeGG0j8o9UjfjDMXpQ OsCPvv+8debxMUdEno6WqziuamCo+JYPS3CipWAo= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1590c184b3f_78a32abe83ef8f5015338ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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, 04 Jun 2018 19:19:32 -0000 ----==_mimepart_5b1590c184b3f_78a32abe83ef8f5015338ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit pravb approved this pull request. -- 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/1411#pullrequestreview-125707928 ----==_mimepart_5b1590c184b3f_78a32abe83ef8f5015338ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@pravb approved this pull request.

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

----==_mimepart_5b1590c184b3f_78a32abe83ef8f5015338ac-- From nobody Mon Jun 4 14:47:21 2018 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 D2241130DFE for ; Mon, 4 Jun 2018 14:47:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 rh7gnB0Hwggh for ; Mon, 4 Jun 2018 14:47:18 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 DE80F130E02 for ; Mon, 4 Jun 2018 14:47:17 -0700 (PDT) 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=yP3ZhRm3c6wqWPGtfoXHavrQ09M=; b=deNzBRCcgIBK+5l+ WX0JjRYv4YhZTY7n8D3b4ZJsyEWOu6TiYQX+P4V39vKu/Q7hSdN88K4hKIpKx1+y CGqTqA3Ib/LZRTLNVCfH9L010AWp4/GjcxPPxzfxO/JqsczgiTKCIRG7neoKiCYY r6PNqCFBrSnk7sQkCRjbEhNI/CA= Received: by filter1203p1las1.sendgrid.net with SMTP id filter1203p1las1-32506-5B15B364-11 2018-06-04 21:47:16.236002936 +0000 UTC Received: from github-lowworker-5909e27.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id K5sDlg9eTYi7IGrsiRbJgA for ; Mon, 04 Jun 2018 21:47:16.128 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-5909e27.cp1-iad.github.net (Postfix) with ESMTP id 1C6B33E193B for ; Mon, 4 Jun 2018 14:47:16 -0700 (PDT) Date: Mon, 04 Jun 2018 21:47:16 +0000 (UTC) From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Alarm vs. timeout (#1383) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15b3641aa6b_76602ac7c17faf543281b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak25IuAF8pA4uaFj7u1AFl+wjmYgSo8ygDVSV8 7CVXnhtZszjdiy0Vua7Ax4+NDklqqsBL/xaI9+R9KBq1luVpEuigkdU33sEcdrsLgGIqU8GcpKzOl0 LdGycHjHkiNIdmO4/UWdCaCNSbxsMG5oRRSzCNfpVfwcepbFDXC7dsdZTN4OUuSUbUU2iw2V5+kzOs A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jun 2018 21:47:20 -0000 ----==_mimepart_5b15b3641aa6b_76602ac7c17faf543281b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Also, I just realized the loss/congestion doc has the same problem. -- 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/1383#issuecomment-394510686 ----==_mimepart_5b15b3641aa6b_76602ac7c17faf543281b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Also, I just realized the loss/congestion doc has the same problem.

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

----==_mimepart_5b15b3641aa6b_76602ac7c17faf543281b1-- From nobody Mon Jun 4 15:28:07 2018 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 7A2F7130E02 for ; Mon, 4 Jun 2018 15:28:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 LUT607hPX49D for ; Mon, 4 Jun 2018 15:28:03 -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 9F5A0130E05 for ; Mon, 4 Jun 2018 15:28:03 -0700 (PDT) Date: Mon, 04 Jun 2018 15:28:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528151282; bh=sw8afBEbMOM4eOLZa805JowLNPoOIV65A+1R/J6AXSk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uQMRppRvOcAeJUTreuHBxBTlN7Bg6epk8NxAJqEZLbA5s438HFwe5ol6myFwKHUi1 tj6CoPvJqTTSc+o5/Gt6GJsHETC/K9p2ycgojJSja7vtGswqihIaxQGnuUyHY6kXMF lYHBixTL6xPWZTFWNWSfzhWu3oRcHEk56BL3VLdg= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify PADDING vs PING frames (#838) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15bcf267605_45e2b07dcaccf604556a8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 04 Jun 2018 22:28:06 -0000 ----==_mimepart_5b15bcf267605_45e2b07dcaccf604556a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok. This is not what "Special Considerations for Packetization Layer PMTU Discovery" section says. I'll s/PADDING/PING/g in that section in my PR. -- 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/838#issuecomment-394520542 ----==_mimepart_5b15bcf267605_45e2b07dcaccf604556a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Ok. This is not what "Special Considerations for Packetization Layer PMTU Discovery" section says. I'll s/PADDING/PING/g in that section in my PR.

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

----==_mimepart_5b15bcf267605_45e2b07dcaccf604556a8-- From nobody Mon Jun 4 17:56:33 2018 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 83526130E29 for ; Mon, 4 Jun 2018 17:56:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nFsWQM-lKJoQ for ; Mon, 4 Jun 2018 17:56:29 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C11F130E3C for ; Mon, 4 Jun 2018 17:56:29 -0700 (PDT) Date: Mon, 04 Jun 2018 17:56:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528160188; bh=PhlhbNlot1GB6oXRIX1icldqU9kVyzDtgPJe041ASmo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cBOtVCG9DofT+4mYpRJO+Vku7QielaZC+sczoyuCaGqm4UUqQ2f99jeWNMc3MlNbf Blhg1aoFWVTSlqkcsGllY459gs265nAOVTvcCn3U7J/sCheNPbHlBtgypiQzWXFV0W VAt2Sjs7PcE+2sPUNXWZmX1BhVPyk+C57Q3JFeEc= From: bobdug Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet number transform should be negotiated (#1296) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15dfbc90d9d_30922b1dcf808f5031099"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: bobdug 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.26 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: Tue, 05 Jun 2018 00:56:32 -0000 ----==_mimepart_5b15dfbc90d9d_30922b1dcf808f5031099 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable With the rapid increase in Ethernet and bus speeds, the need for hardware= offload has become critical in encryption applications. Besides the rea= sons stated by @pravb, from this hardware vendor=E2=80=99s point of view,= requiring packet number encryption makes the QUIC protocol less friendly= to offload. It requires an added pass through the hardware crypto engin= e and depending on the hardware implementation, this can result in a loss= of performance or additional complexity. It would hence be ideal to mak= e this feature optional. That would have the added benefit of allowing t= he hardware ecosystem time to mature to support this feature, especially = at higher speeds. -- = 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/1296#issuecomment-394546103= ----==_mimepart_5b15dfbc90d9d_30922b1dcf808f5031099 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

With the rapid increase in Ethernet and bus speeds, the need for hardw= are offload has become critical in encryption applications. Besides the = reasons stated by @pravb, from this ha= rdware vendor=E2=80=99s point of view, requiring packet number encryption= makes the QUIC protocol less friendly to offload. It requires an added = pass through the hardware crypto engine and depending on the hardware imp= lementation, this can result in a loss of performance or additional compl= exity. It would hence be ideal to make this feature optional. That woul= d have the added benefit of allowing the hardware ecosystem time to matur= e to support this feature, especially at higher speeds.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b15dfbc90d9d_30922b1dcf808f5031099-- From nobody Mon Jun 4 19:54:44 2018 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 4603E130E84 for ; Mon, 4 Jun 2018 19:54:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 9Ozwxwp_0jhx for ; Mon, 4 Jun 2018 19:54:42 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18CE130E81 for ; Mon, 4 Jun 2018 19:54:41 -0700 (PDT) Date: Mon, 04 Jun 2018 19:54:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528167280; bh=j+Cus0KmPcGCXASoO3Wbs3CWXr+PM2UjTrIk8ZXSTSI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=eFoJKkNK33PlcLC9iVeRuaW+vToL0alKRpw+4bEg6XldrUQNVIym5oS0zIpjE6ZeK R3VZzhdfsduhkuOFZuvVgl50kq3wM56EjIce0TLufImC0HVtOfuQ1fhmCl0/WN9k72 okX/GC105T0UhRtci4BEjxUIBxRuT4HaawC6MW6o= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b15fb70c0650_586a2b04a82b4f587974b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Tue, 05 Jun 2018 02:54:43 -0000 ----==_mimepart_5b15fb70c0650_586a2b04a82b4f587974b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Per request of the editors, here is a draft PR for ICMP PMTU section. I am deliberately not including text for #1243 here. (That can be a subsequent PR.) You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1412 -- Commit Summary -- * Updated ICMP PMTU section -- File Changes -- M draft-ietf-quic-transport.md (101) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1412.patch https://github.com/quicwg/base-drafts/pull/1412.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/1412 ----==_mimepart_5b15fb70c0650_586a2b04a82b4f587974b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Per request of the editors, here is a draft PR for ICMP PMTU section.
I am deliberately not including text for #1243 here. (That can be a subsequent PR.)

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

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

Commit Summary

  • Updated ICMP PMTU section

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 mute the thread.

----==_mimepart_5b15fb70c0650_586a2b04a82b4f587974b9-- From nobody Mon Jun 4 21:44:49 2018 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 B6CA8130EBC for ; Mon, 4 Jun 2018 21:44:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 UZ4h05Shdsrk for ; Mon, 4 Jun 2018 21:44:46 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8993130EB9 for ; Mon, 4 Jun 2018 21:44:45 -0700 (PDT) Date: Mon, 04 Jun 2018 21:44:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528173884; bh=uZNj3WVdsS/Prd1aZ33zlrXji2VY6dr2l+A7i+XXcYo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fAoOkKvHPYpFuHs/xX7AUphYJL8BkDRF3zhqN1SHv6RxWCafARmdVp3nLrQUfYKcq 4mZr/0QxA0zAfGt4qgS5OvlOAr2CCMIjfBxkZw7+WXHn4We7K+Rec/FLl3VfrI6k5d 7kasPNh+fHu6lzacdj5HDv3I5WVKEeMqMu4/KNok= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16153cc714e_62012ad420e56f5428819a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 05 Jun 2018 04:44:48 -0000 ----==_mimepart_5b16153cc714e_62012ad420e56f5428819a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FWIW, let me point out that under the current draft it is possible for an endpoint to send a long header packet at any time it wants to observe the MTU, even after the handshake is complete. It's just that the long header packet will be ignored by the client in case it reaches the client. And with the introduction of coalesced packets, the cost of doing this type of PMTUD has become small. Whenever an endpoint wants to do PMTUD and it has some outstanding data, is creates a datagram that consists of the following two QUIC packets: * a long header packet with zero-length payload that contains the server CID (or some other payload that is sufficient to route the ICMP response back to the origin server) * a short header packet carrying outstanding data This type of datagram never harms the conncection, because the draft requires the receiver to process each QUIC packet as if it was received as a separate datagram. Assuming that the server will be performing PMTUD and assuming that the client's CID is zero-sized, the overhead of the long header packet is: 1 (type) + 4 (version) + 1 (cidl) + len(server_CID) + 1 (payload-length). Actually, this approach (i.e. sending a compound datagram to contain arbitrary information) is flexible enough to carry any data that needs to be exposed to an on-path device. We could use it to expose packet drop rate for example. I'm not saying we should support these kinds of exposures, but we cannot prohibit such thing to happen, because the receiver cannot determine if an incoming packet was sent from the peer (to expose signal to on-path devices) or from an attacker (to disrupt connection). -- 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/1243#issuecomment-394580024 ----==_mimepart_5b16153cc714e_62012ad420e56f5428819a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

FWIW, let me point out that under the current draft it is possible for= an endpoint to send a long header packet at any time it wants to observe= the MTU, even after the handshake is complete. It's just that the long h= eader packet will be ignored by the client in case it reaches the client.=

And with the introduction of coalesced packets, the cost of doing this= type of PMTUD has become small.

Whenever an endpoint wants to do PMTUD and it has some outstanding dat= a, is creates a datagram that consists of the following two QUIC packets:=

  • a long header packet with zero-length payload that contains the serve= r CID (or some other payload that is sufficient to route the ICMP respons= e back to the origin server)
  • a short header packet carrying outstanding data

This type of datagram never harms the conncection, because the draft r= equires the receiver to process each QUIC packet as if it was received as= a separate datagram.

Assuming that the server will be performing PMTUD and assuming that th= e client's CID is zero-sized, the overhead of the long header packet is: = 1 (type) + 4 (version) + 1 (cidl) + len(server_CID) + 1 (payload-length).=

Actually, this approach (i.e. sending a compound datagram to contain a= rbitrary information) is flexible enough to carry any data that needs to = be exposed to an on-path device. We could use it to expose packet drop ra= te for example.

I'm not saying we should support these kinds of exposures, but we cann= ot prohibit such thing to happen, because the receiver cannot determine i= f an incoming packet was sent from the peer (to expose signal to on-path = devices) or from an attacker (to disrupt connection).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16153cc714e_62012ad420e56f5428819a-- From nobody Mon Jun 4 23:31:49 2018 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 2BA57130EDE for ; Mon, 4 Jun 2018 23:31:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 sX0zNZ-wcDqV for ; Mon, 4 Jun 2018 23:31:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B568F130EBD for ; Mon, 4 Jun 2018 23:31:45 -0700 (PDT) Date: Mon, 04 Jun 2018 23:31:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528180304; bh=9qytvRMqsaFDkNl07BxN0MVxSiC2JEw/rdzbvf6YRKE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l5QrNazTMtN1RAXb0E/p8a3CfAQqoL2gS7zPq3YtriBuOGdrQ+Uz2fGADyYDVGIyN /I9KZvEAVDwTbt9QrUOPANg+wRfLmOEGtHyBWmllN2K2BhX21QjtLN7KQxD3KXbvio OEWWj7gCU6L0YFZzMSN240pRKQo/PNyn32TkIwgg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b162e50ce183_350a3fa0cf4aaf88435976"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 06:31:47 -0000 ----==_mimepart_5b162e50ce183_350a3fa0cf4aaf88435976 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Your use of "which" isn't CMOS, but this is good. -- 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/1411#pullrequestreview-125834647 ----==_mimepart_5b162e50ce183_350a3fa0cf4aaf88435976 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Your use of "which" isn't CMOS, but this is good.

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

----==_mimepart_5b162e50ce183_350a3fa0cf4aaf88435976-- From nobody Tue Jun 5 00:00:39 2018 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 77088130F03 for ; Tue, 5 Jun 2018 00:00:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 T-cGwZq1qeX0 for ; Tue, 5 Jun 2018 00:00:34 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 870D7130EFF for ; Tue, 5 Jun 2018 00:00:34 -0700 (PDT) Date: Tue, 05 Jun 2018 00:00:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528182033; bh=rmO3SkghgYl6qKWPLx3pzXz6XXe+DQINBxi81FL9yLA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Bemv6umR6zwk7XhCAreOiwyh8eXG8IPbmd0r3OH7cS46kKDKxX1dgcOhVYv8AqYNK PRVqPArdro0hUWms2uZ0WcQVSbY82t3Z7xLwLqFbwfibyfxAEXO4w0Hjd9SN0srhuy RbNf7/Y3+V6zaR25gkO8c1vng4463aSzKRh7XIgI= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b163511db56f_678a3f80e6266f7869111"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 07:00:37 -0000 ----==_mimepart_5b163511db56f_678a3f80e6266f7869111 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. Same nit on "which", but LG. -- 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/1411#pullrequestreview-125840996 ----==_mimepart_5b163511db56f_678a3f80e6266f7869111 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

Same nit on "which", but LG.

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

----==_mimepart_5b163511db56f_678a3f80e6266f7869111-- From nobody Tue Jun 5 00:08:14 2018 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 93E6B130F03 for ; Tue, 5 Jun 2018 00:08:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 odozIM4dHn0o for ; Tue, 5 Jun 2018 00:08:07 -0700 (PDT) Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31F4E130EE6 for ; Tue, 5 Jun 2018 00:08:07 -0700 (PDT) Date: Tue, 05 Jun 2018 00:08:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528182486; bh=IBRdyutYx19odthC46gjOMGZ8r4VhIWrEAc+mnKLwJs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HDTCK4g6q6yqXXPVrR8/+Sd1DCFLjdqlKcYQO7EbwydaQTuk4ijXmweObT0PAz96q CkochgQR821g5BWaG9LGdquc9nvPjPxQ8HfuocP7VhZf7M+eZ5DEHcYjw+Nr/+H8lO Vhkqnx8VUPqRZF6knw/AFGVPdOamy4YsS5Yun1wI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1636d6a192f_7b2b2ae693064f6014281b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 05 Jun 2018 07:08:14 -0000 ----==_mimepart_5b1636d6a192f_7b2b2ae693064f6014281b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > This type of datagram never harms the conncection, because the draft requires the receiver to process each QUIC packet as if it was received as a separate datagram. That is not necessarily true because that is under a cooperative assumption. Any party that keeps dumping invalid packets might be flagged, also otherwise competent QUIC peers. Seeing something suspect in a packet is reasonable cause for rejecting the entire transmission. Hence, if this is considered a good idea, both endpoints should understand and agree on this and avoid confusing each other. -- 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/1243#issuecomment-394604499 ----==_mimepart_5b1636d6a192f_7b2b2ae693064f6014281b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This type of datagram never harms the conncection, because the draft r= equires the receiver to process each QUIC packet as if it was received as= a separate datagram.

That is not necessarily true because that is under a cooperative assum= ption. Any party that keeps dumping invalid packets might be flagged, als= o otherwise competent QUIC peers. Seeing something suspect in a packet is= reasonable cause for rejecting the entire transmission.

Hence, if this is considered a good idea, both endpoints should unders= tand and agree on this and avoid confusing each other.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1636d6a192f_7b2b2ae693064f6014281b-- From nobody Tue Jun 5 00:19:54 2018 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 EBAF0130F08 for ; Tue, 5 Jun 2018 00:19:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 GpbB6t3RTtxN for ; Tue, 5 Jun 2018 00:19:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AC20130F0E for ; Tue, 5 Jun 2018 00:19:51 -0700 (PDT) Date: Tue, 05 Jun 2018 00:19:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528183189; bh=1KqlTiADc7a3os0UC+fhU8d47yRhHe+xSUsoWJSYvAw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ls+kX3K1L6vKWq29eN7U34yz5Butlv7Gfzm0x5vWYnjLwVRm5o8a6+eb2GhScRGji YnWHp0c2GXbqzqM8gkOTyCladuFDxqvVD/A7Hai0pSxKWANFsmx5m73H/r5Fgg4Yru v2LItKQHfl7S0UwP+kDXWeClYvDSKgpvTYSr2SMs= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1639958f5e3_21e42acab7510f5c10279a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 05 Jun 2018 07:19:53 -0000 ----==_mimepart_5b1639958f5e3_21e42acab7510f5c10279a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Any party that keeps dumping invalid packets might be flagged, also otherwise competent QUIC peers. Seeing something suspect in a packet is reasonable cause for rejecting the entire transmission. I disagree. As stated in my comment above, terminating the connection due to seeing suspicious QUIC packets is equal to allowing attackers reset the connection. That goes against our principal of having "authenticated reset." I believe that the same holds for coalesced packets. An attacker can break the packet by modifying it. But that should not lead to the connection being terminated. FWIW, section 4.6 of the transport draft says: "The receiver of coalesced QUIC packets MUST individually process each QUIC packet and separately acknowledge them, as if they were received as the payload of different UDP datagrams." -- 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/1243#issuecomment-394607390 ----==_mimepart_5b1639958f5e3_21e42acab7510f5c10279a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Any party that keeps dumping invalid packets might be flagged, also ot= herwise competent QUIC peers. Seeing something suspect in a packet is rea= sonable cause for rejecting the entire transmission.

I disagree. As stated in my comment above, terminating the connection = due to seeing suspicious QUIC packets is equal to allowing attackers rese= t the connection. That goes against our principal of having "authenticate= d reset."

I believe that the same holds for coalesced packets. An attacker can b= reak the packet by modifying it. But that should not lead to the connecti= on being terminated.

FWIW, section 4.6 of the transport draft says: "The receiver of coales= ced QUIC packets MUST individually process each QUIC packet and separatel= y acknowledge them, as if they were received as the payload of different = UDP datagrams."

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1639958f5e3_21e42acab7510f5c10279a-- From nobody Tue Jun 5 00:39:31 2018 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 D6DD0130F0A for ; Tue, 5 Jun 2018 00:39:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 IsqENDPir38k for ; Tue, 5 Jun 2018 00:39:27 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C42130F07 for ; Tue, 5 Jun 2018 00:39:27 -0700 (PDT) Date: Tue, 05 Jun 2018 00:39:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528184366; bh=nZEjBrOlL0qZPlibIaa9iLmP8YwqrN6Mll47GAGbMNM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TQspLyqcF/VhCkgD4Py6OrmnIXJfg56DU3jp3G5bqDQIjRagjFNSk08rOrkTwkSY6 KVvG6TwJWKaQsrU2xlKaeiQTNCH1lnHgZLWYcS7xIkq09Oq0QisT2Ct2GSqpdsJgoV UI3653OKEegCHRCxqHTCgcQ7JKq0MrhnSnGUMn0k= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b163e2eb7495_32853f98c6ab4f843344f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 05 Jun 2018 07:39:30 -0000 ----==_mimepart_5b163e2eb7495_32853f98c6ab4f843344f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I didn't mean to say dump the connection. By dump transmission I meant the single UDP datagram - either someone messed with it, or the peer is misbehaving. In that case it makes limited sense to further process the datagram since it is obviously not up to specs. This opens up to an on-path attack where a third party can attach content to a datagram and here you are right, but compound packets are only used during the early handshake, no? And here the best approach is to reject as much nonsense as possible. If the peer volunteers to sign a packet that makes non sense it becomes suspecious and repeat offences might lead to disconnection and black listing. Therefore it is IMO not a good idea to use invalid packets for path discovery or any other purpose. -- 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/1243#issuecomment-394612529 ----==_mimepart_5b163e2eb7495_32853f98c6ab4f843344f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I didn't mean to say dump the connection. By dump transmission I meant= the single UDP datagram - either someone messed with it, or the peer is = misbehaving. In that case it makes limited sense to further process the d= atagram since it is obviously not up to specs.

This opens up to an on-path attack where a third party can attach cont= ent to a datagram and here you are right, but compound packets are only u= sed during the early handshake, no? And here the best approach is to reje= ct as much nonsense as possible.

If the peer volunteers to sign a packet that makes non sense it become= s suspecious and repeat offences might lead to disconnection and black li= sting. Therefore it is IMO not a good idea to use invalid packets for pat= h discovery or any other purpose.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b163e2eb7495_32853f98c6ab4f843344f7-- From nobody Tue Jun 5 01:52:08 2018 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 90E94130F1F for ; Tue, 5 Jun 2018 01:52:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rSR0QOffk3Lo for ; Tue, 5 Jun 2018 01:52:03 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AB69130F1D for ; Tue, 5 Jun 2018 01:52:03 -0700 (PDT) Date: Tue, 05 Jun 2018 01:52:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528188722; bh=2v5rBIwZVH3V8r4HaXNNS7gxlrh0Nkvxz95/jm2JBW0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=gY4Y9WMa7zT+QPB2eQBfNM3o1O61xUpFuKtPln1xu0mKlG5LU5OuRS13oSxTnyOCK d+tXiCicu7lLC6HporMsSyZmrU0l1dJBTU1OcU96yROigVVyh3dAOKAGGiMQWznRuF xtWIhOyM9AHQ/52hO05O7YszJ9UXI7cXD1gfLQLo= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b164f3284a91_2e82b2350772f6014917a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 08:52:06 -0000 ----==_mimepart_5b164f3284a91_2e82b2350772f6014917a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Currently the recovery draft indicates you should use fast retransmit to declare packets lost, even if there's no evidence the peer can decrypt the packet. A simple example is if the first client initial is sent with 0RTT and then the Initial is lost; Then the client Initial is retransmitted and acked, 0RTT packets will be declared lost via early and/or fast retransmit. If QUIC sticks with a single packet number space, then encryption level will have to be added to each outstanding packet we'll have to not declare packets at an encryption level lost until at least one packet at that level has been acked. -- 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/1413 ----==_mimepart_5b164f3284a91_2e82b2350772f6014917a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Currently the recovery draft indicates you should use fast retransmit to declare packets lost, even if there's no evidence the peer can decrypt the packet.

A simple example is if the first client initial is sent with 0RTT and then the Initial is lost; Then the client Initial is retransmitted and acked, 0RTT packets will be declared lost via early and/or fast retransmit.

If QUIC sticks with a single packet number space, then encryption level will have to be added to each outstanding packet we'll have to not declare packets at an encryption level lost until at least one packet at that level has been acked.

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

----==_mimepart_5b164f3284a91_2e82b2350772f6014917a-- From nobody Tue Jun 5 02:12:13 2018 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 8F8EC130F9C for ; Tue, 5 Jun 2018 02:12:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 5qeyYB8yAV4Q for ; Tue, 5 Jun 2018 02:12:10 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 10E98130F81 for ; Tue, 5 Jun 2018 02:12:10 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528189929; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nldwXlC4FQFUmXJWKYJkANk/dM+EHfLRuQv4drvgXkY=; b=BZnGLl7UzBhhQLntIl1Zk/kgYtzRcKJ1bDEtpQqnuyr717BRTHZcdlx7ynMzsVeovsWBiqF4 QVoQw+KjUoWAlQ7BAbuKFrB7mS2MpUBdvn5eLuw37Iv4L+HOGBvFQLQMv03Af33cjRrme1v5 DWc5+qgzTbBp8Vl9Y4wKgAuNbGA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b1653e8.7f0a7608fcf0-smtp-out-n01; Tue, 05 Jun 2018 09:12:08 -0000 (UTC) Date: Tue, 05 Jun 2018 02:12:06 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b1653e6c4561_1552adeb8419c1099784@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] a37e2e: add quic load balancers Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1653e6c40df_1552adeb8419c1099677"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 09:12:12 -0000 ----==_mimepart_5b1653e6c40df_1552adeb8419c1099677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: a37e2eae0df1f0fd6a13d45dd1dfec66b93ed5e1 https://github.com/quicwg/wg-materials/commit/a37e2eae0df1f0fd6a13d45dd1dfec66b93ed5e1 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/quic-load-balancers.pdf Log Message: ----------- add quic load balancers **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1653e6c40df_1552adeb8419c1099677-- From nobody Tue Jun 5 02:12:19 2018 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 35479130F2A for ; Tue, 5 Jun 2018 02:12:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oUvsLatPvKuC for ; Tue, 5 Jun 2018 02:12:14 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46DA3130F3F for ; Tue, 5 Jun 2018 02:12:14 -0700 (PDT) Date: Tue, 05 Jun 2018 02:12:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528189933; bh=mtwhK1gQCDIYl5Tk3hjGsrNASyazS2zYA/ieiSLhKfw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=IozECe+4MH6GU1imj/+CoEAn0afG7gJxb0JgiumLEOzr1fMt024BPuOlVw3pX+cKg hEhAnn2KC/FS7RppnP5RVV6ZBqiWWntRxD7A4NJEYKuyFmjx5MjSHVe+VG73thvI64 ruG1wz/WTcp9RCP1DQG0c1vEwUSMH1+bCVRUkCvM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Speed handshake recovery when only undecryptable packets arrive (#1414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1653ed4a580_2fb2b2350772f60135150"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 09:12:17 -0000 ----==_mimepart_5b1653ed4a580_2fb2b2350772f60135150 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit There are a few cases in the handshake where the decryptable packets may be lost, but undecryptable packets may arrive. Examples include the client Initial followed by 0RTT packets and the server's Handshake packets followed by 1(/2)RTT packets. In those cases, no packets can be acknowledged because packets must be decrypted and processed before being acknowledged, but it is possible to indicate to the peer that something has arrived. DTLS uses an empty ack frame to instigate a faster than standard retransmission of handshake data. QUIC could adopt a similar mechanism or come up with something slightly different, depending upon how much feedback it wants to provide. One question is whether the encrypted packet number of the undecryptable packet should be provided in a feedback frame. -- 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/1414 ----==_mimepart_5b1653ed4a580_2fb2b2350772f60135150 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

There are a few cases in the handshake where the decryptable packets may be lost, but undecryptable packets may arrive.

Examples include the client Initial followed by 0RTT packets and the server's Handshake packets followed by 1(/2)RTT packets.

In those cases, no packets can be acknowledged because packets must be decrypted and processed before being acknowledged, but it is possible to indicate to the peer that something has arrived.

DTLS uses an empty ack frame to instigate a faster than standard retransmission of handshake data. QUIC could adopt a similar mechanism or come up with something slightly different, depending upon how much feedback it wants to provide. One question is whether the encrypted packet number of the undecryptable packet should be provided in a feedback frame.

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

----==_mimepart_5b1653ed4a580_2fb2b2350772f60135150-- From nobody Tue Jun 5 04:59:27 2018 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 AFC72130FED for ; Tue, 5 Jun 2018 04:59:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 C-T2-G1Y9mCx for ; Tue, 5 Jun 2018 04:59:17 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 E5372130FEB for ; Tue, 5 Jun 2018 04:59:10 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528199949; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=CUw47Ap/GWsDewF4CrX7eM0EJcf8QSDxFdw7u2y5m1I=; b=Ee2coOyll5ucINe5HdkyX8KLlTTUm3brnjeCJujODaolCjm5sWy7YceT1Jxgm9YYkTqTpxJ6 NZegMHz5y1pmawRbVQ8XIl1UEHsP1WERyBJ5+4+JT5f/frfq6hgewmu4+mPyUTZv+qfaWYFx ScgfUUMUsQ2PFaZSXbHZJOjbqZU= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b167b0d.7f2816298a20-smtp-out-n01; Tue, 05 Jun 2018 11:59:09 -0000 (UTC) Date: Tue, 05 Jun 2018 04:59:09 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b167b0da5c64_259c2ad3b2f05c0c489a8@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 17b7a2: add editors' report Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b167b0da4eae_259c2ad3b2f05c0c4883d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 11:59:25 -0000 ----==_mimepart_5b167b0da4eae_259c2ad3b2f05c0c4883d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 17b7a2a48bef6a224325875e0161eabbcf662f2c https://github.com/quicwg/wg-materials/commit/17b7a2a48bef6a224325875e0161eabbcf662f2c Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add editors' report **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b167b0da4eae_259c2ad3b2f05c0c4883d-- From nobody Tue Jun 5 05:02:22 2018 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 528A9130FEE for ; Tue, 5 Jun 2018 05:02:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 7IQhvYqH3uy1 for ; Tue, 5 Jun 2018 05:02:18 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 85D5E130FEA for ; Tue, 5 Jun 2018 05:02:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528200137; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=KA5wkGATS10ahbU8GX6O9HPq7xCurAZ/zyWMybch9nM=; b=HUfcY7NhI1kyakKOYYQ30bMn2PjG1aMNBP06tEyn9RhHey3277dlYYWWTefPlSId7pVdYM+S e+Bj9kiOS7F26tGSGM6240x47ewzPmkRSYx4wzrpdajWpxSr7nH7ByREvdVt4rC/rVZ9mQJR qrWNTRxA2VbYvhf0vUK7hOlMLBo= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b167bc9.7fe6ffb57a80-smtp-out-n01; Tue, 05 Jun 2018 12:02:17 -0000 (UTC) Date: Tue, 05 Jun 2018 05:02:16 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b167bc85b033_754b2ab6faccfc142793f@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 1e4492: Which witch? Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b167bc85abb0_754b2ab6faccfc1427866"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 12:02:21 -0000 ----==_mimepart_5b167bc85abb0_754b2ab6faccfc1427866 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/change_invariants Home: https://github.com/quicwg/base-drafts Commit: 1e4492c9480dce3308e890fe66c4f3ab88c0bc78 https://github.com/quicwg/base-drafts/commit/1e4492c9480dce3308e890fe66c4f3ab88c0bc78 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Which witch? Commit: 3429fcf2095175dd8204ecccc4997c1a9ac453d1 https://github.com/quicwg/base-drafts/commit/3429fcf2095175dd8204ecccc4997c1a9ac453d1 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Things, properties Compare: https://github.com/quicwg/base-drafts/compare/8cb0d2086381...3429fcf20951 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b167bc85abb0_754b2ab6faccfc1427866-- From nobody Tue Jun 5 05:02:29 2018 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 A4F84130FEE for ; Tue, 5 Jun 2018 05:02:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ilk7kmM73CqK for ; Tue, 5 Jun 2018 05:02:21 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AC6130FEA for ; Tue, 5 Jun 2018 05:02:20 -0700 (PDT) Date: Tue, 05 Jun 2018 05:02:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528200140; bh=PDkGvo8EaL1f8kdNFJdedYCDR5POvbdZJ+loA983dYk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wHA3fRLvEi0rA6IOQOBtrVsefcALxTM7ZwM1/Tmh0azMH5lFBWufrUdddpK6MD0S8 NU9WTl4XCG2EhucdjF4m32xn0K+ph9yoWRDnX8h/ZFckXM3TazfwekrBaMpIK26Kpg 7xa5zMEvAEGuPz35Vk89XSBcv9mX6OEb969sosIE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b167bcc18129_218f3f90e2f8cf842222fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 05 Jun 2018 12:02:23 -0000 ----==_mimepart_5b167bcc18129_218f3f90e2f8cf842222fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 2 commits. 1e4492c Which witch? 3429fcf Things, properties -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1411/files/8cb0d2086381ce815748793eb61ad79b7c9bf9f0..3429fcf2095175dd8204ecccc4997c1a9ac453d1 ----==_mimepart_5b167bcc18129_218f3f90e2f8cf842222fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 2 commits.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b167bcc18129_218f3f90e2f8cf842222fa-- From nobody Tue Jun 5 06:08:26 2018 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 6F1D3130DF3 for ; Tue, 5 Jun 2018 06:08:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 BmDVwZtQeaqR for ; Tue, 5 Jun 2018 06:08:23 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 047C213100F for ; Tue, 5 Jun 2018 06:08:22 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528204102; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=go3WPLbRNpf4ToAAaR+6AQ1vWL74+oO9oMUkUChXNIw=; b=ps7oQAK1s0TVNs+y4uKQWJG99G2f97NN02LSK4fgkjrSMxwluq5xMQFguBLxqFKvi8e8vJDo ijEZajBSzdbYlgS6J28GIcIP6sBFWN4/Lxdt0doaAQwU9LGZimC6EdtDpuSqhWN1ur1gZbf8 jKq3cwXcX6CTtMzPdEyJOoFo+3I= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: sean=sn3rd.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b168b45.7f94c84492a0-smtp-out-n02; Tue, 05 Jun 2018 13:08:21 -0000 (UTC) Date: Tue, 05 Jun 2018 06:08:21 -0700 From: Sean Turner Reply-To: Sean Turner To: quic-issues@ietf.org Message-ID: <5b168b45c3a9a_42b72b1354101c1490357@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 64ff82: Set TLS extension codepoint to 0xffa5 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168b45c36de_42b72b1354101c1490216"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:08:25 -0000 ----==_mimepart_5b168b45c36de_42b72b1354101c1490216 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 64ff827f3c19b4dd9f39065e7caf4e43184c03c7 https://github.com/quicwg/base-drafts/commit/64ff827f3c19b4dd9f39065e7caf4e43184c03c7 Author: Martin Thomson Date: 2018-05-30 (Wed, 30 May 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Set TLS extension codepoint to 0xffa5 Closes #1395. Commit: 5a4dc49dd7c6845a995d612a025686151d776bd9 https://github.com/quicwg/base-drafts/commit/5a4dc49dd7c6845a995d612a025686151d776bd9 Author: Sean Turner Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Merge pull request #1402 from quicwg/tls-extension-ffa5 Set TLS extension codepoint to 0xffa5 Compare: https://github.com/quicwg/base-drafts/compare/dd83b15aaab5...5a4dc49dd7c6 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168b45c36de_42b72b1354101c1490216-- From nobody Tue Jun 5 06:08:32 2018 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 2F973131060 for ; Tue, 5 Jun 2018 06:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DH5poNuEFhOl for ; Tue, 5 Jun 2018 06:08:26 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E69DF131012 for ; Tue, 5 Jun 2018 06:08:25 -0700 (PDT) Date: Tue, 05 Jun 2018 06:08:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528204105; bh=5HDn99aqN6B/gGHnssLU//ldCc7btos6bZIgrVKMN/w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BiUQcKOrBN2IAgP+IlUuNMQj1lBC9UUTnyyEQ4nVixJAdP2RMjbhEMMMhi3a3+cWI DUxRSvt/71OoqeNQfO2eTpQ0ey9dqkNWCGCUn/iAtvvvFpAEVWbCc71T9iELQhb1CK 121d+xWGBsM2hXSO5sR6duMPEEntybQC9nepqewQ= From: Sean Turner Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] quic_transport_parameters code point (#1395) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168b4921e04_17933fb51c622f80164137"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: seanturner 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.26 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: Tue, 05 Jun 2018 13:08:29 -0000 ----==_mimepart_5b168b4921e04_17933fb51c622f80164137 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1395 via #1402. -- 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/1395#event-1663649065 ----==_mimepart_5b168b4921e04_17933fb51c622f80164137 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1395 via #1402.

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

----==_mimepart_5b168b4921e04_17933fb51c622f80164137-- From nobody Tue Jun 5 06:08:38 2018 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 5450E130DF3 for ; Tue, 5 Jun 2018 06:08:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 QkrOd0Hm5rbB for ; Tue, 5 Jun 2018 06:08:26 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7E5413100F for ; Tue, 5 Jun 2018 06:08:25 -0700 (PDT) Date: Tue, 05 Jun 2018 06:08:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528204105; bh=V7ZMWp9ELjoi1JRXO0zNMX1TK3eYOxdgwIGCejdXU88=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nu9tSm+/SyGf9wbjFAWYADOvEYsAcEnOK0I/VIzp1vROShgfSsEScUYVeQbs3U/7W Fnf8KU5hOIPyLl/5+aE2YFMZuNWPKDgPY4foC40DlBcv9ph5t+rDN5KcsykDe+gogr ZK+SVzMmZsKlk0ISESGLrLSJa1tQ6oK05xcl8KNM= From: Sean Turner Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Set TLS extension codepoint to 0xffa5 (#1402) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168b4919478_66333f93c1554f801048b8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: seanturner 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.26 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: Tue, 05 Jun 2018 13:08:29 -0000 ----==_mimepart_5b168b4919478_66333f93c1554f801048b8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1402. -- 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/1402#event-1663649048 ----==_mimepart_5b168b4919478_66333f93c1554f801048b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1402.

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

----==_mimepart_5b168b4919478_66333f93c1554f801048b8-- From nobody Tue Jun 5 06:11:11 2018 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 2B715131012 for ; Tue, 5 Jun 2018 06:11:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 bG50WlEhMXVQ for ; Tue, 5 Jun 2018 06:11:08 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 A3E32130DF3 for ; Tue, 5 Jun 2018 06:11:08 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528204267; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=+VUltzrPAnjdN0NVzaoKKxQrYHdUM/2Gd4lAhnmIsWg=; b=BjAChi8g46rHfilepNlVw/jc0ptrACe0iAiWeAoKvqeEgu1mNHJjXOcnTePyUl1Cafo10nWg M7pA9TdmrIWgbsIsk+xL4Hnq50ny0Ln8+TE84S7GIcfhf/MXrbFWz7wyk5TbVrmhFEZj2DTI W8HWPQWieeWf78Di/hAFC/lg9H0= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b168beb.7fea50595090-smtp-out-n02; Tue, 05 Jun 2018 13:11:07 -0000 (UTC) Date: Tue, 05 Jun 2018 06:11:06 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168bea46386_6f22ade75e83c0c505c@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] f740be: add some talk owners Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168bea4600c_6f22ade75e83c0c504e3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:11:10 -0000 ----==_mimepart_5b168bea4600c_6f22ade75e83c0c504e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: f740becff3673a316eaddba2aeacdda14c104099 https://github.com/quicwg/wg-materials/commit/f740becff3673a316eaddba2aeacdda14c104099 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add some talk owners **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168bea4600c_6f22ade75e83c0c504e3-- From nobody Tue Jun 5 06:14:36 2018 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 2BFF2131012 for ; Tue, 5 Jun 2018 06:14:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 eKEQblHZo44l for ; Tue, 5 Jun 2018 06:14:32 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 79C23130DF3 for ; Tue, 5 Jun 2018 06:14:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528204471; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ycZ45UNW8bl1JilS+pDh5DbXeHgelRkMIySuYN3RKJQ=; b=FQ8jtxeG4hy04TyL/zueJ0Yax/fjfr51cQMJ0lxAMdiQuJfiEfHDdAyOPHtS/2YhFe6vEFJY Svc7ebOTbhH0nefpOllPqIMqLt/jLySRhbR452A66Qq/FQ6Afb+/oRPwMUmUUTheY7vcLfMF bW/Jio725U3jwbYuv94Awt9sR3g= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b168cb7.7f9371d4aae0-smtp-out-n01; Tue, 05 Jun 2018 13:14:31 -0000 (UTC) Date: Tue, 05 Jun 2018 06:14:30 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168cb6d16f1_75ed2b0cabce7c047692d@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 02cb28: add Magnus as an owner for ECN proposal Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168cb6d1358_75ed2b0cabce7c0476818"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:14:35 -0000 ----==_mimepart_5b168cb6d1358_75ed2b0cabce7c0476818 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 02cb28111f1fe6f4d3423527281a6074c660b251 https://github.com/quicwg/wg-materials/commit/02cb28111f1fe6f4d3423527281a6074c660b251 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add Magnus as an owner for ECN proposal **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168cb6d1358_75ed2b0cabce7c0476818-- From nobody Tue Jun 5 06:15:21 2018 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 32A4113100D for ; Tue, 5 Jun 2018 06:15:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 kYvAJnhcUND1 for ; Tue, 5 Jun 2018 06:15:17 -0700 (PDT) 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 953FE130EE6 for ; Tue, 5 Jun 2018 06:15:17 -0700 (PDT) Date: Tue, 05 Jun 2018 06:15:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528204516; bh=UGMfRyRj76XJVQcVSSo+B+QAsH6ti/OZ6558FC0q64E=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Wlk/g5x7qL8b5vnbXs6DBCRnsr9junOS51CXY8wK1w4MjXbHbwVjD/ax2aAuEBcRs H41KOlfLmj/XP1uDMRj3Jyw7yRfrc70pl8ObL8iUH1fTqizBpuBSXkGdVDFxN8dcDN BTZbEpXkrHXP0uroj+dTo+riZHHI83/wXY3eHOpw= From: Magnus Westerlund Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Adding presentation on ECN (#43) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168ce4c012a_42c53fabeca52f8092078"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 05 Jun 2018 13:15:20 -0000 ----==_mimepart_5b168ce4c012a_42c53fabeca52f8092078 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/43 -- Commit Summary -- * Adding presentation for ECN in QUIC. * Merge branch 'master' of https://github.com/quicwg/wg-materials -- File Changes -- A interim-18-06/ECN for QUIC - interim-18-06.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/43.patch https://github.com/quicwg/wg-materials/pull/43.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/wg-materials/pull/43 ----==_mimepart_5b168ce4c012a_42c53fabeca52f8092078 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/43

Commit Summary

  • Adding presentation for ECN in QUIC.
  • Merge branch 'master' of https://github.com/quicwg/wg-materials

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 mute the thread.

----==_mimepart_5b168ce4c012a_42c53fabeca52f8092078-- From nobody Tue Jun 5 06:18:40 2018 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 0AAA613100F for ; Tue, 5 Jun 2018 06:18:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 n16B9AN2oEz7 for ; Tue, 5 Jun 2018 06:18:36 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 D3A82130FED for ; Tue, 5 Jun 2018 06:18:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528204716; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=pUP7uv8SKM0bnB7tGPpvqHhaXYjC7QfMmswABHynGHw=; b=bEVOC+Sqzbd1dbeiZV9SpR1lnmwM2W1pwYUdkf4P93HgxKwym+t5kaBnbT8auYw9oldXXNHy Psq2OgAs8moo+jkPhDcvIQH4QcecQ5/z/hwq40VfBSLl1xgMxJSjeDhpo01FQuYemu0djL+M x0ezFv4OiQKDFzMTlBkYsri9XHc= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b168dac.7fda4a715750-smtp-out-n03; Tue, 05 Jun 2018 13:18:36 -0000 (UTC) Date: Tue, 05 Jun 2018 06:18:35 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168dab1d87c_19442ac3bc711c04534be@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 794992: Adding presentation for ECN in QUIC. Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168dab1d255_19442ac3bc711c04533b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:18:39 -0000 ----==_mimepart_5b168dab1d255_19442ac3bc711c04533b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 79499270010f46f2f071bbb30895965e015c1946 https://github.com/quicwg/wg-materials/commit/79499270010f46f2f071bbb30895965e015c1946 Author: gloinul Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/ECN for QUIC - interim-18-06.pdf Log Message: ----------- Adding presentation for ECN in QUIC. Commit: a47c20ee14e2d9acca23701f5d8478375d50d814 https://github.com/quicwg/wg-materials/commit/a47c20ee14e2d9acca23701f5d8478375d50d814 Author: gloinul Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A ietf101/QUIC-ECN-IETF-101.pdf A ietf101/Stream0-EKR.pdf A ietf101/agenda.md A ietf101/editors-update.pdf A ietf101/ietf101-datagram-plpmtud-quic.key A ietf101/invariants.pdf A ietf101/lightning-quic-in-the-wild.pdf A ietf101/minutes.md A ietf101/spin-101.key A ietf101/spin-101.pdf M interim-18-06/agenda.md M interim-18-06/arrangements.md A interim-18-06/misc-issues.pdf A interim-18-06/quic-load-balancers.pdf A interim-18-09/agenda.md A interim-18-09/arrangements.md Log Message: ----------- Merge branch 'master' of https://github.com/quicwg/wg-materials Commit: c79807cec35307b5f5ab239493bd90fe67b385b3 https://github.com/quicwg/wg-materials/commit/c79807cec35307b5f5ab239493bd90fe67b385b3 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/ECN for QUIC - interim-18-06.pdf Log Message: ----------- Merge pull request #43 from gloinul/master Adding presentation on ECN Compare: https://github.com/quicwg/wg-materials/compare/c99ce1bd8557...c79807cec353 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168dab1d255_19442ac3bc711c04533b9-- From nobody Tue Jun 5 06:18:47 2018 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 9CFFD130FED for ; Tue, 5 Jun 2018 06:18:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xfuHE4Px2E1A for ; Tue, 5 Jun 2018 06:18:38 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A42713100D for ; Tue, 5 Jun 2018 06:18:37 -0700 (PDT) Date: Tue, 05 Jun 2018 06:18:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528204716; bh=LxcIJ5YxXxxwk3oXCXi44nL33c0q6sevRzlShaz4nlw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=InfK4jX1Bgag8hHS6XxVBiO69d+nxoazxeOSqImIkn3GKdh8VMT1NB67GFb1e7AOj QZOmQC9mL+/8SIn9E/KtjsZ5cOrFpAl3InWV83mRP8DmEg/okGq41JLaZ16cxLGJzj K4ShfJ1zpa8Oq84GI8CdcKNhuiLrrMvJ/g7w25GQ= From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Adding presentation on ECN (#43) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168dacca860_58722ac67233af5026995"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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.26 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: Tue, 05 Jun 2018 13:18:40 -0000 ----==_mimepart_5b168dacca860_58722ac67233af5026995 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #43. -- 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/wg-materials/pull/43#event-1663673361 ----==_mimepart_5b168dacca860_58722ac67233af5026995 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #43.

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

----==_mimepart_5b168dacca860_58722ac67233af5026995-- From nobody Tue Jun 5 06:21:24 2018 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 6A69813104D for ; Tue, 5 Jun 2018 06:21:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 JfNxxbvJXX3e for ; Tue, 5 Jun 2018 06:21:21 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 5985A13104B for ; Tue, 5 Jun 2018 06:21:21 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528204880; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=8mM0/rM3W3hPf4WYOXpWijzDofOvKrVUQvNSOQvZVAI=; b=kF2U3obLckDFI2BEt4ydGWr8u5clhiAi+jzmFMs44fdu+2gYkU0E9RHzVl69KJvC/Lm7XgpD wmKvTPYJEXSz7yLgsJEDFHo8AdQjEPRyKR06N+q6A5WKpSCnmZWwJiaCUvGMcpjlXgcgDROz l+uvJ92nOtT7mhpqL1ZQi7gOJiY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b168e50.7f0d91ae58d0-smtp-out-n02; Tue, 05 Jun 2018 13:21:20 -0000 (UTC) Date: Tue, 05 Jun 2018 06:21:20 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168e505e097_4f392b282c991c0c622ab@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 600e99: add load balancers link Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168e505dc77_4f392b282c991c0c621df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:21:23 -0000 ----==_mimepart_5b168e505dc77_4f392b282c991c0c621df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 600e996069c9590f79fe5acecefbca0c98954c87 https://github.com/quicwg/wg-materials/commit/600e996069c9590f79fe5acecefbca0c98954c87 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add load balancers link **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168e505dc77_4f392b282c991c0c621df-- From nobody Tue Jun 5 06:23:16 2018 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 5F443131054 for ; Tue, 5 Jun 2018 06:23:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 k7599DcgLP2v for ; Tue, 5 Jun 2018 06:23:12 -0700 (PDT) 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 9A31613104B for ; Tue, 5 Jun 2018 06:23:12 -0700 (PDT) Date: Tue, 05 Jun 2018 06:23:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528204991; bh=idMZlXFYM6e3dvRy7LYiIJCU2nyRdxcOyO0dBRGR0bQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=sGf78p1w857Fe/RHSJvcGktmPgPzMBZPLI6B8HQfze0T4DznzY1+mgQlZDjkDyptM WfX1Vh8LUd/+y0qadoLqCIKlSYgfZABEvso/o4WHU3r/Jvvr58lOfA0rakJCdM7+8x J+I0aCjXcLoQjY3QohurN3kyruErpSNuSTmjUAgE= From: afrind Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] qpack update 2018.06 (#44) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168ebfde2d1_1bbf2af600254f601418d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Tue, 05 Jun 2018 13:23:15 -0000 ----==_mimepart_5b168ebfde2d1_1bbf2af600254f601418d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/44 -- Commit Summary -- * Add files via upload -- File Changes -- A interim-18-06/qpack update 06.18.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/44.patch https://github.com/quicwg/wg-materials/pull/44.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/wg-materials/pull/44 ----==_mimepart_5b168ebfde2d1_1bbf2af600254f601418d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/44

Commit Summary

  • Add files via upload

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 mute the thread.

----==_mimepart_5b168ebfde2d1_1bbf2af600254f601418d-- From nobody Tue Jun 5 06:23:49 2018 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 32C6C131068 for ; Tue, 5 Jun 2018 06:23:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 kE-c1Q5ECHxW for ; Tue, 5 Jun 2018 06:23:45 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 73FEB13104B for ; Tue, 5 Jun 2018 06:23:45 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205024; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=dJjaW6yMSSmwVnGwaWAUlewGCEtXDZZETEvVKAVLeWs=; b=dDB7AmyV5JBIi9Ol2XiSXtlV5MGZ3fSRoC9rIFZvNBln+nqc3C2t6c68uD5jp6DVkcsysMDc KR5CCX7nyJElNOxpgS4TGts1xg8jfitQq8QUFSRMrLHUwTXbtzVj74SJPT2fKiFBhUPdt2gK m1wtr7ffxrjqEWWblGZQJoLcDGg= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b168ee0.7fb696ca08d0-smtp-out-n03; Tue, 05 Jun 2018 13:23:44 -0000 (UTC) Date: Tue, 05 Jun 2018 06:23:43 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168edf904f9_2fbc2afedf561c0c5496c@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] df5a2c: Add files via upload Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168edf90184_2fbc2afedf561c0c5484f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:23:47 -0000 ----==_mimepart_5b168edf90184_2fbc2afedf561c0c5484f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: df5a2c44d0b561e54145bb0e98aeb82b3ae6c2ac https://github.com/quicwg/wg-materials/commit/df5a2c44d0b561e54145bb0e98aeb82b3ae6c2ac Author: afrind Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/qpack update 06.18.pdf Log Message: ----------- Add files via upload Commit: ede9b8addfb04b48f094e5369934568151378a50 https://github.com/quicwg/wg-materials/commit/ede9b8addfb04b48f094e5369934568151378a50 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/qpack update 06.18.pdf Log Message: ----------- Merge pull request #44 from afrind/master qpack update 2018.06 Compare: https://github.com/quicwg/wg-materials/compare/600e996069c9...ede9b8addfb0 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168edf90184_2fbc2afedf561c0c5484f-- From nobody Tue Jun 5 06:23:56 2018 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 5825513104B for ; Tue, 5 Jun 2018 06:23:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 q0jmwQcTlMF1 for ; Tue, 5 Jun 2018 06:23:46 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B812C131054 for ; Tue, 5 Jun 2018 06:23:46 -0700 (PDT) Date: Tue, 05 Jun 2018 06:23:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528205026; bh=b9USsVT3lkpWkzE6EP5+upqzhdskxLNuh/aClNfZYwU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gf5Ah0W5G2gVHvgHee8DNCFlsoUXUcdh8aLujPF/bArI+jl3RkUmUtDxFlx2YF8JF Br76CMxSVAca17/WrR3EVUCizr4dQ4Ze4cK3BXG2zS1FRRafx+ZlzrJ5Zxe8doivcV wDfZaa6FqxwEEjzlknbbtgf8jil1KurPXHq7jVeU= From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] qpack update 2018.06 (#44) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b168ee22273c_15012ad58828ef501105dd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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.26 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: Tue, 05 Jun 2018 13:23:49 -0000 ----==_mimepart_5b168ee22273c_15012ad58828ef501105dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #44. -- 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/wg-materials/pull/44#event-1663685824 ----==_mimepart_5b168ee22273c_15012ad58828ef501105dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #44.

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

----==_mimepart_5b168ee22273c_15012ad58828ef501105dd-- From nobody Tue Jun 5 06:24:38 2018 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 C3312131054 for ; Tue, 5 Jun 2018 06:24:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 q9zEVTL02iZv for ; Tue, 5 Jun 2018 06:24:35 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 9EADB13104B for ; Tue, 5 Jun 2018 06:24:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205075; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=lchFoYH1AqPj9nNHzRbS5KW2rMVEIQbtIpdtwakmx4I=; b=IKcXzImXZcIS8l2kaDKIJ8JM9S9yu9MeodP+Gh4QaPAhPkHBlq3crdMmrJvi+nMwW+MifyDH qGoPVIcvUz4yDY80+mHzEVk1kF+jA4WAQXCRucBUCRNFVaifvqmc+DLJmwPcum8hAmXszVgx 5pt6t6Lvwplmd3UHPbKs/SRX/0E= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b168f12.7feb8746a630-smtp-out-n03; Tue, 05 Jun 2018 13:24:34 -0000 (UTC) Date: Tue, 05 Jun 2018 06:24:34 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168f12d3baa_795d2ac80f72bc1048020@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 73953a: add QPACK link Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168f12d32ec_795d2ac80f72bc10479a4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:24:37 -0000 ----==_mimepart_5b168f12d32ec_795d2ac80f72bc10479a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 73953a2cecb1cbe219023c72b8491af81faf04b0 https://github.com/quicwg/wg-materials/commit/73953a2cecb1cbe219023c72b8491af81faf04b0 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add QPACK link **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168f12d32ec_795d2ac80f72bc10479a4-- From nobody Tue Jun 5 06:25:27 2018 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 0E52F131068 for ; Tue, 5 Jun 2018 06:25:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 BN6prMu8nYCb for ; Tue, 5 Jun 2018 06:25:23 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 C6C0F13104B for ; Tue, 5 Jun 2018 06:25:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205123; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=8whEmwoXUdQYVcxHZFX21QZNkwwzt/TaQUFnj7HCxHY=; b=CcCC8YvtpUS3ggIPmsrsP7xleLZxB+3T2jV2d6EakNrNDUcCKWgAP1CFZg0xth296cVaDG6m RRv2BDC0xgxS6iTp83fpm1qxexVoZQlmqJX3AQLpvBZ9YBLZfxYNfJ9S6J47D6HxI2zepWFW GuvOnbdns1xxcYX7yWS+Ao3NtZM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b168f42.7f9ff8d1cf90-smtp-out-n03; Tue, 05 Jun 2018 13:25:22 -0000 (UTC) Date: Tue, 05 Jun 2018 06:25:22 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168f427889d_1fd62abcb6543c04102ed@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 52a132: shift slides link Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168f42784e2_1fd62abcb6543c041014a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:25:25 -0000 ----==_mimepart_5b168f42784e2_1fd62abcb6543c041014a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 52a132e70b387d4631abb146ed8fa721dde663e6 https://github.com/quicwg/wg-materials/commit/52a132e70b387d4631abb146ed8fa721dde663e6 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- shift slides link **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168f42784e2_1fd62abcb6543c041014a-- From nobody Tue Jun 5 06:27:00 2018 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 BE70613106A for ; Tue, 5 Jun 2018 06:26:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Y5U75yfcCLqu for ; Tue, 5 Jun 2018 06:26:57 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 2641313104B for ; Tue, 5 Jun 2018 06:26:57 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205216; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=UvwSWLVKJPONcR73kJqip2OYewf06/D/9Prti20MswA=; b=vbHCiIUYR9TdostnmMTsJciFNKlDLRDIRw4JHYqZeyvAfjFdKyvGnuOVTLbpkYgUAltNTRyL xZ60vx9sfyuPpXUWnc7Nj0fOmDvKkM+WXoN7QgiYCvclU21zTKg9rtMyodzEJZkqcHu3N8X0 /6y4l5Dv+yHxG+9Odlwgga/zBRk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b168f9f.7f6cc487c5a0-smtp-out-n01; Tue, 05 Jun 2018 13:26:55 -0000 (UTC) Date: Tue, 05 Jun 2018 06:26:55 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168f9fae3d6_6f3b2ac9618d1bfc53788@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 2418a9: links for issues Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168f9fae02f_6f3b2ac9618d1bfc536ba"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:26:59 -0000 ----==_mimepart_5b168f9fae02f_6f3b2ac9618d1bfc536ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 2418a9a9a6c756cdeb8f22ae2d0f0cfd35a67477 https://github.com/quicwg/wg-materials/commit/2418a9a9a6c756cdeb8f22ae2d0f0cfd35a67477 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- links for issues **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168f9fae02f_6f3b2ac9618d1bfc536ba-- From nobody Tue Jun 5 06:33:51 2018 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 B00A2131071 for ; Tue, 5 Jun 2018 06:33:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FfDoG5IyXDZT for ; Tue, 5 Jun 2018 06:33:48 -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 012A8130DCA for ; Tue, 5 Jun 2018 06:33:47 -0700 (PDT) Date: Tue, 05 Jun 2018 06:33:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528205627; bh=ubNwYVtR7N3WojZ71tGFU7bm4mTSaXO4u/WHdmqRUVg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=LNPot20GF3//JXsUhbFWoE6Jujarz59uXKFE/A/FeNeXMSDBcTmMPKpYKUHPkXKIQ xRGG6k4rm284gBwMob2LHoezW7N6/11Xx+zaKw756RK0FjfJqZUuJeMCCqPGB54eCH /JGDydr7Cq1EwIgRiWiEi6SPXltOJF+IVyIno5ZY= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] HTTP/QUIC: Enhance guidance of using "hq" (#1415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16913b59c7e_2a973fa71b8bef78108247"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 13:33:50 -0000 ----==_mimepart_5b16913b59c7e_2a973fa71b8bef78108247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Section 2 deals with HTTP/QUIC connection establishment and touches on the "hq" Alt-Svc APLN value. However, it's not until section 2.2.1 is it made clear that "hq" should only be used for the *final* RFC version. Do you think it would help to add a short forward reference to 2.2.1, to help mitigate wasted cycles caused by the wrong ALPN getting used when broader interop happens? -- 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/1415 ----==_mimepart_5b16913b59c7e_2a973fa71b8bef78108247 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Section 2 deals with HTTP/QUIC connection establishment and touches on the "hq" Alt-Svc APLN value. However, it's not until section 2.2.1 is it made clear that "hq" should only be used for the final RFC version.

Do you think it would help to add a short forward reference to 2.2.1, to help mitigate wasted cycles caused by the wrong ALPN getting used when broader interop happens?

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

----==_mimepart_5b16913b59c7e_2a973fa71b8bef78108247-- From nobody Tue Jun 5 06:34:43 2018 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 A3618130DCA for ; Tue, 5 Jun 2018 06:34:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 L9qtTVrV7Y2y for ; Tue, 5 Jun 2018 06:34:40 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 F167D131071 for ; Tue, 5 Jun 2018 06:34:39 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205679; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=BNn6ye3hm20T/2HjgitDpubv2PPBjxOc+MILU7bDyqU=; b=DRt19dZFiTPGrZO362Ku3osSMcXnAlzXDyGTmLFelBFICUqzHvZfsutLywaoHs3GryKalDbz 5/q+j5r4Z6crmvEmCttFcnlBpGoDHrer+9OqYCC9RpUbbjThBFw5B9vgRKyU/cdASfyZL0So CIN5iCPufPrWusfzbPjmX6KByOk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b16916f.7f62e71b3720-smtp-out-n02; Tue, 05 Jun 2018 13:34:39 -0000 (UTC) Date: Tue, 05 Jun 2018 06:34:38 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b16916e3afe3_25c42aff8f015c0c141e3@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 065a6e: Fix variable-length fields in picture Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16916e3ab59_25c42aff8f015c0c14028"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:34:42 -0000 ----==_mimepart_5b16916e3ab59_25c42aff8f015c0c14028 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 065a6e68fbbc5727efc59aa30579367ec14fe802 https://github.com/quicwg/base-drafts/commit/065a6e68fbbc5727efc59aa30579367ec14fe802 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Fix variable-length fields in picture **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16916e3ab59_25c42aff8f015c0c14028-- From nobody Tue Jun 5 06:35:27 2018 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 75192131071 for ; Tue, 5 Jun 2018 06:35:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vKC-zD17WzGt for ; Tue, 5 Jun 2018 06:35:23 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D651130DCA for ; Tue, 5 Jun 2018 06:35:23 -0700 (PDT) Date: Tue, 05 Jun 2018 06:35:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528205722; bh=TdLUMK6RnVWvzX3/uTlId+W8IiRrtD1+SeJcTR1Vp7o=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=KJrva2MJhsUGLV3TtEqlIIe1nn5xfece681eM2B0dfDGnC5ILUhq/nHIFw2RnIgLs Wtnpu/MlsrparnI9dhAcyWSjTLW9Hd2LENM1KthQXhSPrRMfbxGDFq9K3LSt3qLioE S3TlaUJeAdnQLGGNGUgg5hTsNRYAxY/pnDCYQ7iE= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] HTTP/QUIC: are SETTINGS HTTP/QUIC specific? (#1416) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16919abd957_7a5d2b14a7538f541036e4"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 13:35:26 -0000 ----==_mimepart_5b16919abd957_7a5d2b14a7538f541036e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Section 2.2 says: > While connection-level options pertaining to the core QUIC protocol are set in the initial crypto handshake, HTTP-specific settings are conveyed in the SETTINGS frame. I think it is more correct to say "HTTP/QUIC-specific settings are conveyed in the SETTINGS frame.". -- 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/1416 ----==_mimepart_5b16919abd957_7a5d2b14a7538f541036e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Section 2.2 says:

While connection-level options pertaining to the core QUIC protocol are set in the initial crypto handshake, HTTP-specific settings are conveyed in the SETTINGS frame.

I think it is more correct to say "HTTP/QUIC-specific settings are conveyed in the SETTINGS frame.".

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

----==_mimepart_5b16919abd957_7a5d2b14a7538f541036e4-- From nobody Tue Jun 5 06:38:23 2018 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 07326131071 for ; Tue, 5 Jun 2018 06:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 9lnFRztDccbF for ; Tue, 5 Jun 2018 06:38:20 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60FFC130DCA for ; Tue, 5 Jun 2018 06:38:20 -0700 (PDT) Date: Tue, 05 Jun 2018 06:38:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528205899; bh=FpNccRfuwC1H+H8Q8VyAr7TWEoEaESGaF8vQMWlIca8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M8g9jLF0Xnvn/GsZtBz7drsg8ghDB24e1A0qkEbOD08owDHFzVEowobiIU+vnDl6t HZhxCZSlAzJRCpku5YqduxWNmDJWiPXrg7M7GO+vZoUHjJN4gWyflWTa7b8E2o0sM7 0UjhUM/UNcY3wiQlkUNkueEdioMaZ6rmAzBD2kAQ= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16924bbc5e0_6f602abb417f8f6022365"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 05 Jun 2018 13:38:22 -0000 ----==_mimepart_5b16924bbc5e0_6f602abb417f8f6022365 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From my perspective processing the later arriving duplicate has risks. If this is an intentional attack based on duplicating and modifying a packet, but where the original can't be removed, then likely the attack packet will arrive after the original. Secondly, trying to combine the ECN response of multiple packets is less than straightforward and exposes one to the risk above. It can also make one more likely to treat a specific ECN number as CE than none duplicated packets. Also the downside of dropping any duplicate packet even if CE marked is not significant. If you have a congestion event that results in the next packet is marked also, then the CE event will be reported one packet later. ECN for RTP (https://www.rfc-editor.org/rfc/rfc6679.txt) actually tracks duplication and loss as seen by receiver to give all variables, but the retrospective on that RFC is that is overly causes. I would argue that QUIC need a basic duplication handling, and that ECN processing happens after the packet has been decrypted and authenticated to avoid any type of injection attacks, and require additional checking mechanism for it being a valid source sent packet. -- 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/1405#issuecomment-394712102 ----==_mimepart_5b16924bbc5e0_6f602abb417f8f6022365 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From my perspective processing the later arriving duplicate has risks.= If this is an intentional attack based on duplicating and modifying a p= acket, but where the original can't be removed, then likely the attack pa= cket will arrive after the original.

Secondly, trying to combine the ECN response of multiple packets is le= ss than straightforward and exposes one to the risk above. It can also ma= ke one more likely to treat a specific ECN number as CE than none duplica= ted packets. Also the downside of dropping any duplicate packet even if C= E marked is not significant. If you have a congestion event that results = in the next packet is marked also, then the CE event will be reported one= packet later.

ECN for RTP (https://www.rfc-editor.org/rfc/rfc6679.txt) actually t= racks duplication and loss as seen by receiver to give all variables, but= the retrospective on that RFC is that is overly causes.

I would argue that QUIC need a basic duplication handling, and that EC= N processing happens after the packet has been decrypted and authenticate= d to avoid any type of injection attacks, and require additional checking= mechanism for it being a valid source sent packet.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16924bbc5e0_6f602abb417f8f6022365-- From nobody Tue Jun 5 06:39:46 2018 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 8E7291310AE for ; Tue, 5 Jun 2018 06:39:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 FXK1SY84pf-i for ; Tue, 5 Jun 2018 06:39:35 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 92D9313107B for ; Tue, 5 Jun 2018 06:39:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528205972; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=INsgYzkXH/a5aBj23giEFhaXEdnetewmtNsoMy7vbHw=; b=brUk3lTVloDFQXbOC8e+PO0aRnT+k74Hs2sKfLLMiqRmGmb0DDPhE3BNrKsy5F8+jZcJYwRQ FOMqt4XMZI/8d/JOsDXnuiaebPcCFBj7DGLHH308LmPaiJQtsIwDACfy57SZbGi3rw+gbsTl qMI4PZrSKbM1fhzAaJd4meoYa8M= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b169293.7f4c7b7ba9c0-smtp-out-n03; Tue, 05 Jun 2018 13:39:31 -0000 (UTC) Date: Tue, 05 Jun 2018 06:39:31 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b169293bf8e3_53ee2aea66e0bc0061735@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] f72c11: Kazuho is going to talk about -12 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b169293bf338_53ee2aea66e0bc00616c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:39:43 -0000 ----==_mimepart_5b169293bf338_53ee2aea66e0bc00616c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: f72c113d6ef61cfec47b19e4225f79453b31dfc5 https://github.com/quicwg/wg-materials/commit/f72c113d6ef61cfec47b19e4225f79453b31dfc5 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Kazuho is going to talk about -12 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b169293bf338_53ee2aea66e0bc00616c8-- From nobody Tue Jun 5 06:40:48 2018 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 5AE16131071 for ; Tue, 5 Jun 2018 06:40:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Hoo9lA1x3758 for ; Tue, 5 Jun 2018 06:40:44 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 C5DF313104C for ; Tue, 5 Jun 2018 06:40:44 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528206044; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=BavM0a9C8MVAzieP/LVjDKICw5gq3gNtNc9w88dF4v4=; b=aq8yrZ6AEQhuaJCoPq4+/iQ6lYamIWaA5h1OgjOfb229fCsrKq2RIldUL9AYCuiKpNITmAnu eFG3Rt4wi9ilrUcJDPz/3sahG78Z7tzNxYohXyLHMnHfyudOmc6DmkmK9KQ2wjMXvNv7626K Gh8UZWXb4yQxr6xyBwKUxz6rGwg= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b168cff.7f3cd8c20900-smtp-out-n03; Tue, 05 Jun 2018 13:15:43 -0000 (UTC) Date: Tue, 05 Jun 2018 06:15:43 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b168cffc0563_67462acd0a36fc0c2301d@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] c99ce1: add Stream0 DT report URL Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b168cffc00c1_67462acd0a36fc0c229f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:40:47 -0000 ----==_mimepart_5b168cffc00c1_67462acd0a36fc0c229f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: c99ce1bd85577359d5c3418b8a70851f72d86d10 https://github.com/quicwg/wg-materials/commit/c99ce1bd85577359d5c3418b8a70851f72d86d10 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- add Stream0 DT report URL **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b168cffc00c1_67462acd0a36fc0c229f3-- From nobody Tue Jun 5 06:46:18 2018 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 B1790130E31 for ; Tue, 5 Jun 2018 06:46:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 tCNeL-p5oYZR for ; Tue, 5 Jun 2018 06:46:15 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29A55130DCA for ; Tue, 5 Jun 2018 06:46:15 -0700 (PDT) Date: Tue, 05 Jun 2018 06:46:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528206374; bh=US6CMHRMxjugqQH3HnfP3kfFO/3nMj9I8Rko8gqqo1k=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZM1F7MlV0f8sDP/aoXodyDZz3T7IP4UhiAimmSgzoygx8yZI7SqVhcjhtTyO2nAEC jWSUPuWyo/jw9T2axPgNR1ADC62iGiPvZZtaYyzF26EcpFyJPxAMnSayYdTAUwpryF 88yeLQu4wVPf3QJEMUVJHfeY2/UGoct0VJ5OIaTQ= From: Mike Bishop Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Add HTTP slides (#45) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16942671cbd_3a613fb4d7082f8456312"; 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.26 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: Tue, 05 Jun 2018 13:46:17 -0000 ----==_mimepart_5b16942671cbd_3a613fb4d7082f8456312 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/45 -- Commit Summary -- * Add HTTP slides -- File Changes -- A interim-18-06/HTTP.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/45.patch https://github.com/quicwg/wg-materials/pull/45.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/wg-materials/pull/45 ----==_mimepart_5b16942671cbd_3a613fb4d7082f8456312 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/45

Commit Summary

  • Add HTTP slides

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 mute the thread.

----==_mimepart_5b16942671cbd_3a613fb4d7082f8456312-- From nobody Tue Jun 5 06:46:24 2018 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 A2BCA130E31 for ; Tue, 5 Jun 2018 06:46:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 FoU8sRZjHOhk for ; Tue, 5 Jun 2018 06:46:17 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 58FC0130DCA for ; Tue, 5 Jun 2018 06:46:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528206376; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=DhSYr/O0mE9A8TqNnQdLGakXaubncxTTta1zZzRLX6A=; b=aSxWMJX+yp50YRrXhcT4IXltce32naXw5+XnInbI1jsLE4qBbLZytr8rzY/7vhTNweRyWvHg sBSjtfRLafXhX3JzS7kZZtqYvwQJtdvyOyy/DQF3Z2jv9rLohPL82oPkZocuFouNIq+7pFr5 RFU+iLdF61cgFIvCTq6WhEPpUy0= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b1691d0.7f67e79776f0-smtp-out-n02; Tue, 05 Jun 2018 13:36:16 -0000 (UTC) Date: Tue, 05 Jun 2018 06:36:15 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b1691cff1135_6d22b21e3ec9c1414990@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 0a9922: it's Issue Discussion Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1691cff0c39_6d22b21e3ec9c14148fd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:46:19 -0000 ----==_mimepart_5b1691cff0c39_6d22b21e3ec9c14148fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 0a992240a0e25d3d69796b3f832975bb82db8502 https://github.com/quicwg/wg-materials/commit/0a992240a0e25d3d69796b3f832975bb82db8502 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- it's Issue Discussion **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1691cff0c39_6d22b21e3ec9c14148fd-- From nobody Tue Jun 5 06:48:09 2018 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 E7379130E31 for ; Tue, 5 Jun 2018 06:48:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xg36ycNUpOGr for ; Tue, 5 Jun 2018 06:48:05 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D79FD130DCA for ; Tue, 5 Jun 2018 06:48:04 -0700 (PDT) Date: Tue, 05 Jun 2018 06:48:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528206484; bh=TNVZl6K9wkawxB9EMq7mTSocbHTM6XQdxKQ6W7PwtxM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=YG2sThomLSFEkQqkP0ipk68q7L4d+x1wgA1J07NNMJYiuGQ7GHi5UvenEJvWcRggs kbC+tpSnU4J896q/qOZ1b/oP1PvBlFobyZWtuWRZ+ZqYHgC9qnoNRa01aTRMqzPj/M DgG6ARKehzl5CAE+qh8ALHn6PU1IDiXIzdt4a87I= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16949435ff5_b7d3f8df6fb6f808276f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 13:48:07 -0000 ----==_mimepart_5b16949435ff5_b7d3f8df6fb6f808276f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit With a pedant hat on. Section 3 discusses stream mapping and usage. The following sentence stands alone, but follows discussion on stream identifier usage. > Streams SHOULD be used sequentially, with no gaps. I presume this means that stream identifiers should be used sequentially, rather than lower-lever STREAM offset gaps? -- 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/1417 ----==_mimepart_5b16949435ff5_b7d3f8df6fb6f808276f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

With a pedant hat on.

Section 3 discusses stream mapping and usage. The following sentence stands alone, but follows discussion on stream identifier usage.

Streams SHOULD be used sequentially, with no gaps.

I presume this means that stream identifiers should be used sequentially, rather than lower-lever STREAM offset gaps?

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

----==_mimepart_5b16949435ff5_b7d3f8df6fb6f808276f-- From nobody Tue Jun 5 06:48:23 2018 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 7066E130FC2 for ; Tue, 5 Jun 2018 06:48:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 tLShOCFrhy7H for ; Tue, 5 Jun 2018 06:48:16 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2864C130DCA for ; Tue, 5 Jun 2018 06:48:16 -0700 (PDT) Date: Tue, 05 Jun 2018 06:48:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528206495; bh=/g16Y5DBGhuzbXgoDHjebVexlwsJTsvjhIAsszivuOU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EhgQ4fHnu2SuLWMcj7lpX8fh3ZLehrmUwOJ5OSG1yD7ZHaASPzkkMuZ8PVOQbuPlG d6UWbs62wkW2VUX2y4sCUgL08yeW92f6j6I/bRCPiXPNr/MPIsVUV/C02SOAse0CrN LSB3pDmwZCnYaj3db5OhgPZLg98y9ul1BVddrTMY= From: Mike Bishop Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Add HTTP slides (#45) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16949f7b996_8582adf6e702f60242165"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 05 Jun 2018 13:48:20 -0000 ----==_mimepart_5b16949f7b996_8582adf6e702f60242165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. e2afad3 Link slides in agenda -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/wg-materials/pull/45/files/1c3323449c3269b7fcd946071eb84bb508ce6b2b..e2afad387036ce937c7995e67a95b5c7fc5420c3 ----==_mimepart_5b16949f7b996_8582adf6e702f60242165 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b16949f7b996_8582adf6e702f60242165-- From nobody Tue Jun 5 06:50:09 2018 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 D1D4B130FC2 for ; Tue, 5 Jun 2018 06:50:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 DT2o-yj0l0WP for ; Tue, 5 Jun 2018 06:50:05 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0F33B130DCA for ; Tue, 5 Jun 2018 06:50:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528206604; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=gQMc+xY99Y3CxqnucA6LFDQKu9DITEggcjl5jqKgHsU=; b=moZvUC2IpI4KpgqhN3ngdUEdOQmc/Kqu864asuvbkBzrQWXi+lLLwh9Gz7OlcvoxQDgCnUNb cNG+KkIwX/QjHfYCQPc5dMDo4eCzLuE262AIc8NF70+lkAzFfP7p4PNbTw84J/Ej9yobkRbf oPUZHvNXzlt+ZnubZWd8kl8fFaA= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b16950c.7f6f32e85810-smtp-out-n03; Tue, 05 Jun 2018 13:50:04 -0000 (UTC) Date: Tue, 05 Jun 2018 06:50:03 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b16950b321c3_3fab2b2a24b25c042333e@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 1c3323: Add HTTP slides Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16950b31e41_3fab2b2a24b25c04232bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:50:07 -0000 ----==_mimepart_5b16950b31e41_3fab2b2a24b25c04232bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 1c3323449c3269b7fcd946071eb84bb508ce6b2b https://github.com/quicwg/wg-materials/commit/1c3323449c3269b7fcd946071eb84bb508ce6b2b Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/HTTP.pdf Log Message: ----------- Add HTTP slides Commit: e2afad387036ce937c7995e67a95b5c7fc5420c3 https://github.com/quicwg/wg-materials/commit/e2afad387036ce937c7995e67a95b5c7fc5420c3 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A http-wg M interim-18-06/agenda.md Log Message: ----------- Link slides in agenda Commit: 3eab7a9753feb8119346ae0090a49ea2fb7a566e https://github.com/quicwg/wg-materials/commit/3eab7a9753feb8119346ae0090a49ea2fb7a566e Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A http-wg A interim-18-06/HTTP.pdf M interim-18-06/agenda.md Log Message: ----------- Merge pull request #45 from MikeBishop/http_1806 Add HTTP slides Compare: https://github.com/quicwg/wg-materials/compare/f72c113d6ef6...3eab7a9753fe **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16950b31e41_3fab2b2a24b25c04232bf-- From nobody Tue Jun 5 06:50:15 2018 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 F278B130DCA for ; Tue, 5 Jun 2018 06:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JuEylMdtQ6IP for ; Tue, 5 Jun 2018 06:50:06 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 C2B9C130E31 for ; Tue, 5 Jun 2018 06:50:05 -0700 (PDT) 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=tR8D2suUTXZN14bZ6TIVFKOhAbI=; b=o+T904QCPS+Fw01F 0vmu4jecpFaLfuXuWOnUAmK1g+2rLPDHXlpkFFSUtDyH8PqESLXj6Q9al6Gmp9Rq wTV2xuOuilVErPghL9CZp3yA7OMcXruPOReshzCLzNU1h0I22n/b2ln/2k8R3q6C 3F5R/UpIFauf8ogMRiKbEGm0WZw= Received: by filter0999p1las1.sendgrid.net with SMTP id filter0999p1las1-32183-5B16950C-2A 2018-06-05 13:50:04.663658468 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id FKnnOLWTTua8mHtcvJBK0w for ; Tue, 05 Jun 2018 13:50:04.517 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id 7B7D58162C for ; Tue, 5 Jun 2018 06:50:04 -0700 (PDT) Date: Tue, 05 Jun 2018 13:50:04 +0000 (UTC) From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Add HTTP slides (#45) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16950c73cb1_8142adf6e702f6010756d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3hd9IWCuYlu0Ay7EXBR+sQlBlJYxbQVIWkHr FyG74WMtfwBcwIDVGHdQSMdwSMvd5eNAdELome4j5fluiO4HGI3Uo1uGXT/8NhHlQjZx3WbeOfYorU GM53EXI+HlXZaSRtaG9eSnQgkPhneyLCCETRG/MoTTrN+yjlS9UA0Qvn3J05dm2+2qGFAwoIjT5qgZ Y= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 13:50:08 -0000 ----==_mimepart_5b16950c73cb1_8142adf6e702f6010756d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #45. -- 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/wg-materials/pull/45#event-1663751828 ----==_mimepart_5b16950c73cb1_8142adf6e702f6010756d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #45.

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

----==_mimepart_5b16950c73cb1_8142adf6e702f6010756d-- From nobody Tue Jun 5 06:53:39 2018 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 CD6CB130FC2 for ; Tue, 5 Jun 2018 06:53:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 tJkGw0FuzloZ for ; Tue, 5 Jun 2018 06:53:36 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 7CB54130E31 for ; Tue, 5 Jun 2018 06:53:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528206815; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=/Emm4VaNmd4BFm04h4YCbG5Pgbm8xu99TcrWuiIuB5U=; b=SOLvxbUQNYE236mX6NCGhPK5Eerq3IZiquxsgsRIOTE5qqSHbCyvd60cCGFA+mCw5pP3WofS 5uu1T2KpdfmQdk4G5QO4sXQCb5DN1WcLnsKrZFIy6XpjR4YJBKpW4lNgFYzYqwQpamZnGhij qZThcbwULfnOO9R7AN25DSlmhuY= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b1695df.7f3c4e1ca8d0-smtp-out-n03; Tue, 05 Jun 2018 13:53:35 -0000 (UTC) Date: Tue, 05 Jun 2018 06:53:35 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b1695df8d759_240c2aec1481fc1047333@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 69d968: remove spurious submodule Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1695df8cd2f_240c2aec1481fc10472c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 13:53:38 -0000 ----==_mimepart_5b1695df8cd2f_240c2aec1481fc10472c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 69d968998bc2a58b8a6aec0bbce67e1a5625b467 https://github.com/quicwg/wg-materials/commit/69d968998bc2a58b8a6aec0bbce67e1a5625b467 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: R http-wg Log Message: ----------- remove spurious submodule **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1695df8cd2f_240c2aec1481fc10472c-- From nobody Tue Jun 5 06:59:47 2018 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 40CC6130FC2 for ; Tue, 5 Jun 2018 06:59:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 y3TAc5X_DieK for ; Tue, 5 Jun 2018 06:59:43 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84BA813107B for ; Tue, 5 Jun 2018 06:59:43 -0700 (PDT) Date: Tue, 05 Jun 2018 06:59:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528207182; bh=3JaCq2Tbumg4B4/MskXUbZu0f79P5VxdxVJw9gI2Feg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=KKJDkO2/byS5obobKxawniFSqKloH3BaaiA1+IR9U80KRDava3wZM0FgLIDAVAhVT inJNuAU5BwaFw+UPrFW0ojemqQSxJjkM6Jrjux0TwC5C+f54o9x14KbiF9S9Pw9oxm GGsPtBdZxmXJ6hUMjdV4c2Gh/Nk14o41Vbp9Im8Q= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Add PUSH_PROMISE xref (#1418) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16974e8a5b2_7a0b3fb3f67aaf7893669"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 13:59:46 -0000 ----==_mimepart_5b16974e8a5b2_7a0b3fb3f67aaf7893669 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1418 -- Commit Summary -- * Add PUSH_PROMISE xref -- File Changes -- M draft-ietf-quic-http.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1418.patch https://github.com/quicwg/base-drafts/pull/1418.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/1418 ----==_mimepart_5b16974e8a5b2_7a0b3fb3f67aaf7893669 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • Add PUSH_PROMISE xref

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 mute the thread.

----==_mimepart_5b16974e8a5b2_7a0b3fb3f67aaf7893669-- From nobody Tue Jun 5 07:28:15 2018 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 7B1F713103F for ; Tue, 5 Jun 2018 07:28:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 c2ehcPzXTbwe for ; Tue, 5 Jun 2018 07:28:11 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 83E6C131002 for ; Tue, 5 Jun 2018 07:28:11 -0700 (PDT) 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=WrextxU0vDFaa5H2VJhnD1kcNFM=; b=wJ/3MTFYtCB5xX25 Epw3sRRBUlYIIXmjkfZINYmqTIAlotic9P+4CYlAQhN2jw1OQnU4WxG7DKP0/Pab DvmwsbCt1VHZ5c0sm5QHbhQ+3+/kQW6nAXRjXrYTO94aMs8qyXsgF8otPHEK63Wz NYZf6yZuw5kjPIdlD9OzQyoLifE= Received: by filter0888p1las1.sendgrid.net with SMTP id filter0888p1las1-26540-5B169DFA-12 2018-06-05 14:28:10.320505306 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id DSWjV0iUTQisR9TcVcyCBw for ; Tue, 05 Jun 2018 14:28:10.178 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id 2966F41075 for ; Tue, 5 Jun 2018 07:28:10 -0700 (PDT) Date: Tue, 05 Jun 2018 14:28:10 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add PUSH_PROMISE xref (#1418) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b169dfa27512_d7b3fad32afef7813018c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0xaIfMYs5qgLrP5FLUjSWZa6zV4TGoX+B9s2 NgmR95zbqFIpnPTfYYMoj8pz7hhD9TVWijJnb1rGk7sYmtUpeB5pMqqTc5A18dA0xqd1nBusGIFga2 mjtN6S1fP8YcPjyOPFBSzGzy7lf7hizvHWHVJUBQAGWT3c1Zz3yJLu0ML53dxCDvU/B9K3sSVjxLIH k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:28:14 -0000 ----==_mimepart_5b169dfa27512_d7b3fad32afef7813018c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. b7e49f6 Rewrap -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1418/files/fd1a03e08d9f060b38afd5c390a2fe0bcc7ce47d..b7e49f6755d9381ebb482713811ed439bb763add ----==_mimepart_5b169dfa27512_d7b3fad32afef7813018c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b169dfa27512_d7b3fad32afef7813018c-- From nobody Tue Jun 5 07:29:58 2018 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 4B44B13103F for ; Tue, 5 Jun 2018 07:29:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 uIyKUVQRQUoQ for ; Tue, 5 Jun 2018 07:29:54 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88F5D131002 for ; Tue, 5 Jun 2018 07:29:54 -0700 (PDT) Date: Tue, 05 Jun 2018 07:29:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528208993; bh=Q24k71DXvzG1QOi6puz2foRbVGDnurClpDLR/3XIkP4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q/fxKQuuqDI3I5GwD+H8MYnIUWG5Bl6csYDqU9Z2EpJiH3OtMngtNaMY91g9jOTP/ GT5MOchNp3+Aa9EeetJVjRItRzKgqAEn1pERs8bvBSD6Nr5jon0Wh5XL1uuSl/ATBX B/XueZTGdDnuGTn2NGLgfKyins7W3QJ87Gr5JqkQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b169e6196eee_57012b04a5466f5c186786"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 05 Jun 2018 14:29:57 -0000 ----==_mimepart_5b169e6196eee_57012b04a5466f5c186786 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thank you for the explanation. I now see that we need to decrypt the packet before updating the ECN counter. And I think that detecting duplicates on an endpoint is not that complicated now that we have PNE, which means that we can assume that packet numbers will be used mostly contiguously (we might need to specify how frequently packet numbers can be skipped to detect optimistic ack attacks). -- 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/1405#issuecomment-394731145 ----==_mimepart_5b169e6196eee_57012b04a5466f5c186786 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thank you for the explanation.

I now see that we need to decrypt the packet before updating the ECN c= ounter.

And I think that detecting duplicates on an endpoint is not that compl= icated now that we have PNE, which means that we can assume that packet n= umbers will be used mostly contiguously (we might need to specify how fre= quently packet numbers can be skipped to detect optimistic ack attacks).<= /p>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b169e6196eee_57012b04a5466f5c186786-- From nobody Tue Jun 5 07:30:42 2018 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 0E0B41310AF for ; Tue, 5 Jun 2018 07:30:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 FtZRaNDhkF6X for ; Tue, 5 Jun 2018 07:30:37 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 AD6641310B0 for ; Tue, 5 Jun 2018 07:30:37 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528209036; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=NMq8TfcY1Z4tV8dH4feID7U1KlDwUn19jNQcYPLu1nc=; b=MxtQ5T7Ve7UJdD5K6RtnjXnYq2R/KImqwIBKmicnRPp4o2CbmkjOB4MG1/TaM90zmwbY2tdz VWUlp67y7hLbR5WdwInMUW2sLNaFmsdtoJYwPn5REbdXqR4dexdUeXOynKvKvPqxLD2r3Y1D 3AE9NM4BMBt5Ru75rc4L2jcs7lA= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b169e8c.7f62b72d4210-smtp-out-n02; Tue, 05 Jun 2018 14:30:36 -0000 (UTC) Date: Tue, 05 Jun 2018 07:30:35 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b169e8bbc4d2_f712b23713a9c148708c@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] fd8f3e: Add PUSH_PROMISE xref Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b169e8bbc0ec_f712b23713a9c14869e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 14:30:40 -0000 ----==_mimepart_5b169e8bbc0ec_f712b23713a9c14869e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: fd8f3ea08e1d8c7a381f1355edf670f36eba8f08 https://github.com/quicwg/base-drafts/commit/fd8f3ea08e1d8c7a381f1355edf670f36eba8f08 Author: Lucas Pardue Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Add PUSH_PROMISE xref Commit: 8284fa674aafec2c4da8daf0e3441d4113aa03dc https://github.com/quicwg/base-drafts/commit/8284fa674aafec2c4da8daf0e3441d4113aa03dc Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Rewrap Compare: https://github.com/quicwg/base-drafts/compare/065a6e68fbbc...8284fa674aaf **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b169e8bbc0ec_f712b23713a9c14869e-- From nobody Tue Jun 5 07:30:50 2018 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 DBC271310B0 for ; Tue, 5 Jun 2018 07:30:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Mi52OMPN9lyj for ; Tue, 5 Jun 2018 07:30:43 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 0FE131310B4 for ; Tue, 5 Jun 2018 07:30:42 -0700 (PDT) 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=U4yIV7zXJiwrgZqs/GiMWNHHNV4=; b=l6iCkwT6rNpkv0i7 Iivms5J9sO0HgPSAvTi4IeLNDroZWewFuPdz25KE53f840qMN+1rvlswLg55zWDc l3cE1vjiqGvDSGZKN3IImFeWsJpY1cr/MYZwcG39P87UACeonws+5hoDY47Iu7yN 3oN1+pjUxmtwbJBPi/LWtPLp29w= Received: by filter1645p1mdw1.sendgrid.net with SMTP id filter1645p1mdw1-27481-5B169E90-37 2018-06-05 14:30:40.976914876 +0000 UTC Received: from github-lowworker16-cp1-prd.iad.github.net (unknown [192.30.252.40]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id zd8xJCXZRm6I9nSRd7XaCg for ; Tue, 05 Jun 2018 14:30:40.894 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker16-cp1-prd.iad.github.net (Postfix) with ESMTP id D8BE9210A2 for ; Tue, 5 Jun 2018 07:30:40 -0700 (PDT) Date: Tue, 05 Jun 2018 14:30:41 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add PUSH_PROMISE xref (#1418) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b169e90d65e3_2a983f7e21e66f84122441"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3gRAJgK68RcsYnTGMfg6bHzxV3c2x5okBqrM rLF45s6OP40+z9BXguKQV7k/Co4a5X50bUbHgU2iwo6j6U79yrmIhjgbQOAwGg3BVvg5OC5W80uLQH 9MAvh+yAjlxHko38HkZ+a49tXU6GAwTCZs447NOIi3Rh2CXNqSHHdh+4XwD2X1AT4AmR1dhWulOq3W I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:30:46 -0000 ----==_mimepart_5b169e90d65e3_2a983f7e21e66f84122441 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1418. -- 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/1418#event-1663861804 ----==_mimepart_5b169e90d65e3_2a983f7e21e66f84122441 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1418.

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

----==_mimepart_5b169e90d65e3_2a983f7e21e66f84122441-- From nobody Tue Jun 5 07:47:51 2018 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 30366131002 for ; Tue, 5 Jun 2018 07:47:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ji2OVGrIRTuE for ; Tue, 5 Jun 2018 07:47:48 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 029AE13103F for ; Tue, 5 Jun 2018 07:47:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=QnbWutrZbvfY7YiGQVyABzGu+OA=; b=lzwz51KHmQ23k02q r1CmHCgN5vBL7121j7PDqKxm+DC3GDdBeM5Ed/zLCdd1tWdGE2f1JVVXwdGC8HV8 YDs5WiBjvosVmIiKtDmnVGhN7Q1JDd4V+RZSlVfo2nQwWHhs9Q9o0TkUClTXtVq8 8i9j6PDvmaWjuctljuzvNbPAbjc= Received: by filter1855p1mdw1.sendgrid.net with SMTP id filter1855p1mdw1-14429-5B16A28F-4A 2018-06-05 14:47:43.883949957 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id qN7Ukda9RGWYXwkXSqOl5g for ; Tue, 05 Jun 2018 14:47:43.798 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id BF0EFC0140 for ; Tue, 5 Jun 2018 07:47:43 -0700 (PDT) Date: Tue, 05 Jun 2018 14:47:44 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Add editors summary (#46) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a28fbd5ab_53922b22ebe20f5c531c5"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1VF8uSSzC+Za0NNezlfa33hKX1+d/SDfzphC ojhloqAx0d8OnqqLu+EQreLe6zFaOEo+zTU4H9WoIpYDfA8MBL+YNQG+c2/wxzQnPspDj5896RDS2T XFoEE3px/lWTy1Y7CSbY9FuMvoS1b+R6yr9xqSM39bJGLHFL6e+noIdyPxZep21q4zYHZ3u35Dh00a E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:47:50 -0000 ----==_mimepart_5b16a28fbd5ab_53922b22ebe20f5c531c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/46 -- Commit Summary -- * Add editors summary -- File Changes -- A interim-18-06/editors.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/46.patch https://github.com/quicwg/wg-materials/pull/46.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/wg-materials/pull/46 ----==_mimepart_5b16a28fbd5ab_53922b22ebe20f5c531c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/46

Commit Summary

  • Add editors summary

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 mute the thread.

----==_mimepart_5b16a28fbd5ab_53922b22ebe20f5c531c5-- From nobody Tue Jun 5 07:52:22 2018 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 235A01310C3 for ; Tue, 5 Jun 2018 07:52:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 BrmrhXjszYMi for ; Tue, 5 Jun 2018 07:52:18 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F18C1310A2 for ; Tue, 5 Jun 2018 07:52:18 -0700 (PDT) Date: Tue, 05 Jun 2018 07:52:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210337; bh=t8vkofCXSxg7FeGzdyrD/mm/0+ChKFz1MyEVtH8Jbgw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=145az85zCDBRqsvNB7UIGfl9PFJeUqmQW+HoqvbCx0WSoaZpDYY9hNuQR4hJLZEIK U+RFZ8sLqkRSN7A3drzVf2Qs4zSHn/cS+ppa+/om/Rs7gAmiqZaFYRRWfcSok+pcY7 SKK92aZlvmsbBVLn/cwklph7a0icl0Am8LZbWeIs= From: Martin Thomson Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Add editors summary (#46) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a3a16783f_15803f9ff6eb8f7c133d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 05 Jun 2018 14:52:21 -0000 ----==_mimepart_5b16a3a16783f_15803f9ff6eb8f7c133d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 3a6869d Other changes -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/wg-materials/pull/46/files/b033d2a82708e5d6708a3ec870024f471da3104a..3a6869d4d78fae1ab532d37628630205673d1be9 ----==_mimepart_5b16a3a16783f_15803f9ff6eb8f7c133d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b16a3a16783f_15803f9ff6eb8f7c133d5-- From nobody Tue Jun 5 07:53:34 2018 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 89FEA1310A6 for ; Tue, 5 Jun 2018 07:53:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 I3ALdPNTBgsp for ; Tue, 5 Jun 2018 07:53:30 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3FD61310A2 for ; Tue, 5 Jun 2018 07:53:30 -0700 (PDT) Date: Tue, 05 Jun 2018 07:53:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210409; bh=sajBPowzWjJLRvVZOoRUeAbPjbXhNFMl7nwEWpufMpI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l1TR4w3FCirsGgb12Zqn/DydGW5PhJ+I5J0bZrPvTR+t0qwT3gnvNTYGMkiXpC96J N3WUWgBkppGwSCVdw0PdS/S1ZkiWrDnCzvTPrrzF0mb0yYl0Ap9p5OMWDyB2vYNfch xzABj6tpHxjFUC1oV2gjzK78JJhCCU5ivY5vsnGI= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a3e9a0c3_a073fa846fc8f7c1543e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 05 Jun 2018 14:53:33 -0000 ----==_mimepart_5b16a3e9a0c3_a073fa846fc8f7c1543e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > This opens up to an on-path attack where a third party can attach content to a datagram and here you are right, but compound packets are only used during the early handshake, no? And here the best approach is to reject as much nonsense as possible. It is true that compound packets are only used during the handshake. OTOH I do not see why we should reject compound packets after the handshake even though we agree that doing so creates an attack vector. -- 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/1243#issuecomment-394740045 ----==_mimepart_5b16a3e9a0c3_a073fa846fc8f7c1543e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This opens up to an on-path attack where a third party can attach cont= ent to a datagram and here you are right, but compound packets are only u= sed during the early handshake, no? And here the best approach is to reje= ct as much nonsense as possible.

It is true that compound packets are only used during the handshake. O= TOH I do not see why we should reject compound packets after the handshak= e even though we agree that doing so creates an attack vector.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16a3e9a0c3_a073fa846fc8f7c1543e-- From nobody Tue Jun 5 07:55:27 2018 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 157BB1310D9 for ; Tue, 5 Jun 2018 07:55:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1WeDSZmCJIHj for ; Tue, 5 Jun 2018 07:55:17 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6DA21310C3 for ; Tue, 5 Jun 2018 07:55:16 -0700 (PDT) Date: Tue, 05 Jun 2018 07:55:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210516; bh=Mbw6EfDJlrkjyi9aoTQxHWnV/oDsJSyz/vvJr4C47kM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EvlcpHCsY34tNSJY++i/LhbBWaDWyvvnzgaP6bjlF376kOe5RW+xGzlt5ypH8iv4y c3wxK2v9UQFdKuBT1z45bWFz+cSk4atPG6wUcInvDTUhGjDUEZXbUrvLA/7dPJEfZl BJd32nLuFHLnvIcG+Q++3oyPxJSeijwZqUW+an/A= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Public Packet Number Echo (#269) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a4544bef2_790b3f832f1b2f78983ce"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 14:55:20 -0000 ----==_mimepart_5b16a4544bef2_790b3f832f1b2f78983ce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is superseded by the reservation of bits for experimentation and future work is tracked in #631 and #632 -- 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/269#issuecomment-394740735 ----==_mimepart_5b16a4544bef2_790b3f832f1b2f78983ce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is superseded by the reservation of bits for experimentation and future work is tracked in #631 and #632

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

----==_mimepart_5b16a4544bef2_790b3f832f1b2f78983ce-- From nobody Tue Jun 5 07:55:32 2018 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 EA9451310EA for ; Tue, 5 Jun 2018 07:55:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JbZNqSVJLDoU for ; Tue, 5 Jun 2018 07:55:17 -0700 (PDT) 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 373FE1310C6 for ; Tue, 5 Jun 2018 07:55:17 -0700 (PDT) Date: Tue, 05 Jun 2018 07:55:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210516; bh=v8/XwWOIW9HZUL9dhnD0vIR08AlOfWAQQ1+I/fJ0IAA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RY5WKqsGi1viwMrnT80huQhwuPBKRl0cClo8/m/QuxaUzEje4+auLwKK2/usozjQs iVhIjY+4HaCuBd4E1IJ9C8h7SJm53bM7kCzVd1+Obivx4lkrJX4wa0bze4djnKrDQ+ Ap3I5u8YdzS19wHhOyFW7IXOB4lRckHajIOvoScI= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Public Packet Number Echo (#269) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a45469f07_3a0a3fadb913cf80216016"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 14:55:22 -0000 ----==_mimepart_5b16a45469f07_3a0a3fadb913cf80216016 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #269. -- 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/269#event-1663930960 ----==_mimepart_5b16a45469f07_3a0a3fadb913cf80216016 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #269.

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

----==_mimepart_5b16a45469f07_3a0a3fadb913cf80216016-- From nobody Tue Jun 5 07:58:03 2018 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 6DC9E1310D3 for ; Tue, 5 Jun 2018 07:58:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 OvzFWMHumFea for ; Tue, 5 Jun 2018 07:58:00 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3BA51310C9 for ; Tue, 5 Jun 2018 07:58:00 -0700 (PDT) Date: Tue, 05 Jun 2018 07:58:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210680; bh=BNvSEswjxsTwWot8oTWsPHeaMw54Zauhd2/6nxQZZC8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VkaSl+8yuylpPNi8J+ieWDgisvIA3zQdtd7AFvk0FXrJWSor9ZU+/jU7mgY7ZYOmE d5YKjG03b/ibHf4FYwViummjVrEVwCYLKs3aKtccX4AQVHaED5c8rL0WrPx6MCKiB0 xIYo8x5kK1xS9g6n195kWtgyDh3N/cOP45lnIQ9A= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] error handling for path_response (#1265) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a4f813bfa_45be2adff68a8f581412c3"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:58:03 -0000 ----==_mimepart_5b16a4f813bfa_45be2adff68a8f581412c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This seems fine. I don't think the error gives us much anyways. -- 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/1265#issuecomment-394741817 ----==_mimepart_5b16a4f813bfa_45be2adff68a8f581412c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This seems fine. I don't think the error gives us much anyways.

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

----==_mimepart_5b16a4f813bfa_45be2adff68a8f581412c3-- From nobody Tue Jun 5 07:59:41 2018 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 5B2D31310D1 for ; Tue, 5 Jun 2018 07:59:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 UU_Np6WFn97l for ; Tue, 5 Jun 2018 07:59:37 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 CD3C11310C9 for ; Tue, 5 Jun 2018 07:59:37 -0700 (PDT) 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=R86tmtmiHE4iWsOQxuli8/GW3yg=; b=l9P2ya09324YpT/t XKGpq3HxNdRkeHJLAg/y0UB+1BXlw29AiVPENZFSRiHAgszSgZRlv7FLFQRgZMAK PjtJTHeI2LDcYEartkmlx53v3ZwdNMAF0OgodVdjMpBPGXpeNt9Hk6fuyqhh9CSU 2qHh9G8a105s6pQIwtG/MAv30f4= Received: by filter1624p1mdw1.sendgrid.net with SMTP id filter1624p1mdw1-14983-5B16A558-32 2018-06-05 14:59:36.929664905 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id C2lGmBDxROGajUeGM-_5WA for ; Tue, 05 Jun 2018 14:59:36.844 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id CC0DCC10F0 for ; Tue, 5 Jun 2018 07:59:36 -0700 (PDT) Date: Tue, 05 Jun 2018 14:59:37 +0000 (UTC) From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet protection keys not CID-based (#1267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a558ca214_156d3f9ff6eb8f7c36561"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2iwb2SAH7wEhzhP6EVmzbLl5SIk6gsjiCJNb kZBFU2SO8LRoBx/wUEGQlvFOKK3j4BhL/5NCvjse7folF2IALP7ED2swbgwkBiq/BkxXZDqKRCWoIx NbDm0k1u+y0wNUcpZblJEGKQnt9pmx1yNJi7An2rWgETTHn/xgt/D2MgQ1jvVWmrTWVE3itrrM766V w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:59:40 -0000 ----==_mimepart_5b16a558ca214_156d3f9ff6eb8f7c36561 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From editors' meeting: This is moot with PNE. Closing. -- 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/1267#issuecomment-394742421 ----==_mimepart_5b16a558ca214_156d3f9ff6eb8f7c36561 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

From editors' meeting: This is moot with PNE. Closing.

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

----==_mimepart_5b16a558ca214_156d3f9ff6eb8f7c36561-- From nobody Tue Jun 5 07:59:47 2018 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 826DC1310C9 for ; Tue, 5 Jun 2018 07:59:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 UOD37gb2aFlS for ; Tue, 5 Jun 2018 07:59:38 -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 8BCCA1310CC for ; Tue, 5 Jun 2018 07:59:38 -0700 (PDT) Date: Tue, 05 Jun 2018 07:59:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210777; bh=xLMDRNGpkUKwR0CrM+lIu1oZfsvntB8U+oC6TUHUQjI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JkE/Gl/EB/85eoD7Q2QNlwsyX6VQ9AevPBDvFImwhW7TCQVQLwo/VNL1QIa10GMqH oVgyxQy1BNNd8tQRLrKwEFTJtHrg8by5No7sInsDAZOPUGPFfEv66eAvJeQ6OiDnB/ Gcesw7F1iCKnwAF6RzLLayiLuxGhxUPlE/wZcTeM= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet protection keys not CID-based (#1267) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a559e41e3_4a022b22ebe20f5c880b8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 14:59:41 -0000 ----==_mimepart_5b16a559e41e3_4a022b22ebe20f5c880b8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1267. -- 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/1267#event-1663943121 ----==_mimepart_5b16a559e41e3_4a022b22ebe20f5c880b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1267.

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

----==_mimepart_5b16a559e41e3_4a022b22ebe20f5c880b8-- From nobody Tue Jun 5 08:03:09 2018 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 D9ABF1310D7 for ; Tue, 5 Jun 2018 08:03:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 JyX_PiDQMSE0 for ; Tue, 5 Jun 2018 08:03:05 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 5664B1310D1 for ; Tue, 5 Jun 2018 08:03:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528210984; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=AX9dvAbRH81pEj3sVsYQ3rIHOxHI2GPUV+mrHNB0hOA=; b=UbaMKlbGxDr1/+dTOLJvz9lFURS53tQcQrB05/pcDE5yAt2Jyrl2nZSBaLUXR32440ToTiJn bZT31GpnpWKuHcwC4kyGZFBV1pj/nbPWF9FZb7IHtb14byihrUWnGAHzkva1zsqAi9JbY+2u ErJdyAZssLdctSC1Kp7yjuyoqEE= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b16a628.7fa72a8bd720-smtp-out-n02; Tue, 05 Jun 2018 15:03:04 -0000 (UTC) Date: Tue, 05 Jun 2018 08:03:03 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b16a627e16dc_69a72aae8475dc00735c6@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] b033d2: Add editors summary Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16a627e12fb_69a72aae8475dc007342d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 15:03:08 -0000 ----==_mimepart_5b16a627e12fb_69a72aae8475dc007342d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: b033d2a82708e5d6708a3ec870024f471da3104a https://github.com/quicwg/wg-materials/commit/b033d2a82708e5d6708a3ec870024f471da3104a Author: Martin Thomson Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/editors.pdf Log Message: ----------- Add editors summary Commit: 3a6869d4d78fae1ab532d37628630205673d1be9 https://github.com/quicwg/wg-materials/commit/3a6869d4d78fae1ab532d37628630205673d1be9 Author: Martin Thomson Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/misc-issues.pdf Log Message: ----------- Other changes Commit: 52cbeaa3da98ac43149880d8634364f7810cd28a https://github.com/quicwg/wg-materials/commit/52cbeaa3da98ac43149880d8634364f7810cd28a Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: A interim-18-06/editors.pdf M interim-18-06/misc-issues.pdf Log Message: ----------- Merge pull request #46 from martinthomson/editors-18-06 Add editors summary Compare: https://github.com/quicwg/wg-materials/compare/69d968998bc2...52cbeaa3da98 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16a627e12fb_69a72aae8475dc007342d-- From nobody Tue Jun 5 08:03:13 2018 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 9DD1B1310D8 for ; Tue, 5 Jun 2018 08:03:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 y3hRIq_8nbh9 for ; Tue, 5 Jun 2018 08:03:06 -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 C7A6F1310D3 for ; Tue, 5 Jun 2018 08:03:05 -0700 (PDT) Date: Tue, 05 Jun 2018 08:03:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528210985; bh=1ZcOE7yH5x72Ent5oyU7wRjgWLAreOoZHPVJiGXC+1I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jxuwF95IETPCumERaIoL3b4cWQiH6q60EXDvpR2+WMB8Mz20arFeY+GxPzcIDIdka OSdduuPPsSqd3i6bbbnN09aosvSVLnpSJGud/rkgKFDxC3HDUxshBaOgWnr9dkMsU7 dl9Yisx6rPUE8O9Rew0z/DP/FEFB3G/xLCvNn0wU= From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Add editors summary (#46) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a629261b3_40b43f84975a6f8063787"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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.26 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: Tue, 05 Jun 2018 15:03:08 -0000 ----==_mimepart_5b16a629261b3_40b43f84975a6f8063787 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #46. -- 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/wg-materials/pull/46#event-1663952657 ----==_mimepart_5b16a629261b3_40b43f84975a6f8063787 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #46.

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

----==_mimepart_5b16a629261b3_40b43f84975a6f8063787-- From nobody Tue Jun 5 08:14:02 2018 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 33A361310DA for ; Tue, 5 Jun 2018 08:13:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 vAhY1l4QQksi for ; Tue, 5 Jun 2018 08:13:57 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 884A31310AE for ; Tue, 5 Jun 2018 08:13:57 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528211636; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=boJS9wwpUIEknUl6w/Y4THwbAvDgpPCpz7YoueklEVw=; b=h404PHz7cajixpC5XJeVwdXAFQ/PowG16LjT/uvLAvYb/Y/Zy6+saivyjI+hJkwIHmjQBMM1 YLdFxk9NAVX4PNg4CTY44xp3WgC7Z1z8jvwbhR5m38ifSMVjNXKlN60B98rGVEZE/GwkPLTb zM0YG7W0zwCPKkJw1g1jZaJWy2E= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b16a65c.7f6b540da030-smtp-out-n01; Tue, 05 Jun 2018 15:03:56 -0000 (UTC) Date: Tue, 05 Jun 2018 08:03:55 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b16a65baf95_30af2ad0ff62fc147909e@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 5fc609: Link for editors' report Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16a65ba9d9_30af2ad0ff62fc14789fe"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 15:14:00 -0000 ----==_mimepart_5b16a65ba9d9_30af2ad0ff62fc14789fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 5fc609df95569a390daf075c663a399f0f32bd15 https://github.com/quicwg/wg-materials/commit/5fc609df95569a390daf075c663a399f0f32bd15 Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Link for editors' report **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16a65ba9d9_30af2ad0ff62fc14789fe-- From nobody Tue Jun 5 08:14:46 2018 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 5E2E91310D7 for ; Tue, 5 Jun 2018 08:14:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4wvI4648C-kK for ; Tue, 5 Jun 2018 08:14:43 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6281310AE for ; Tue, 5 Jun 2018 08:14:42 -0700 (PDT) Date: Tue, 05 Jun 2018 08:14:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528211681; bh=GkNQXiORijD6xyFOV68ByfN2WzU0vVKv6NVHz6PLuzI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YSP34au63uFRzdPgzXwFC/HjNa6yijb0MIKkmjgb+MN2ME20TLH4SGFZC/RVJ4/W/ pCOVO1IUWNw0OhT3m0uS2G3mwry2d7gtmOKrAJm26IHz++6p7xmrKE+lcN/kdTnkwt qXRzcwSe/uMpW35cerJdXaNa/+IdekI9QfdYPBn0= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Exhausting a supply of connection IDs (#1276) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16a8e1cff71_77282b278b440f6083720"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:14:45 -0000 ----==_mimepart_5b16a8e1cff71_77282b278b440f6083720 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Proposal from editors' meeting: Each endpoint ensures that it sends at least one additional CID if it has at least one spare CID from the peer. -- 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/1276#issuecomment-394748141 ----==_mimepart_5b16a8e1cff71_77282b278b440f6083720 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Proposal from editors' meeting: Each endpoint ensures that it sends at least one additional CID if it has at least one spare CID from the peer.

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

----==_mimepart_5b16a8e1cff71_77282b278b440f6083720-- From nobody Tue Jun 5 08:28:26 2018 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 894D11310F4 for ; Tue, 5 Jun 2018 08:28:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 p0gI_0L5tbeS for ; Tue, 5 Jun 2018 08:28:22 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DA0B1310F2 for ; Tue, 5 Jun 2018 08:28:22 -0700 (PDT) Date: Tue, 05 Jun 2018 08:28:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528212501; bh=DIO1dvab8i7aXu31ev6gOf2zk6AxTAL18r374nObbq8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1AjewPr4CEEEVOK7GwT+vrwh03zFdUXR5SlhG44Vuqc6lWqLn1ov5QLk/NOV2Asan zRucOpTIVg+J562aD7X+QhEy2ibbaHK2+Rhc8KY3rlgqkQ23WWc9CR+foqtehssPny 9pTiLOKZS/5CuhZvh0E8YbOSgMK2y4gE9OF67ooM= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration failure mode (#1278) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16ac157247f_29ac3f8b2e16ef8818469e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:28:24 -0000 ----==_mimepart_5b16ac157247f_29ac3f8b2e16ef8818469e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From editors' meeting: 1. A MITM can cause migration to fail by modifying or dropping path validation packets. 2. Change text to reflect that endpoints MUST ignore PATH_RESPONSE frames that do not satisfy any outstanding PATH_CHALLENGE frames. This also resolves #1265 and #1277. -- 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/1278#issuecomment-394753339 ----==_mimepart_5b16ac157247f_29ac3f8b2e16ef8818469e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From editors' meeting:

  1. A MITM can cause migration to fail by modifying or dropping path vali= dation packets.
  2. Change text to reflect that endpoints MUST ignore PATH_RESPONSE frame= s that do not satisfy any outstanding PATH_CHALLENGE frames.

This also resolves #1265 and #1277.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16ac157247f_29ac3f8b2e16ef8818469e-- From nobody Tue Jun 5 08:31:15 2018 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 8BBF91310DF for ; Tue, 5 Jun 2018 08:31:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FPjCh6wgv9MM for ; Tue, 5 Jun 2018 08:31:12 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A4061310FC for ; Tue, 5 Jun 2018 08:31:12 -0700 (PDT) Date: Tue, 05 Jun 2018 08:31:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528212670; bh=33YdBhGDjbFvfJqBn6RNj5BOtlvT8RT4UD83nitUwdI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z2CEUQB1jYksKftv5rIwpicTrlC/qfdhKGNTPgtMt0JKi4r2dI08+vWsedz5jbomE G085qp7EA0mihNTnQFIufMqBwUs+w7xzypi06LrhPP0L/HOTw3nQ9pluRvi4Qbh/j4 7gJPrVCSSMbgrUo8gScAkcV9U4Ecqec7690oPnR0= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HoLB from NCID frames (#1280) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16acbe87b81_34d72b05f7d22f582210cf"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:31:14 -0000 ----==_mimepart_5b16acbe87b81_34d72b05f7d22f582210cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Now that PNE is done, we should remove the sequence number. -- 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/1280#issuecomment-394754465 ----==_mimepart_5b16acbe87b81_34d72b05f7d22f582210cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Now that PNE is done, we should remove the sequence number.

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

----==_mimepart_5b16acbe87b81_34d72b05f7d22f582210cf-- From nobody Tue Jun 5 08:47:10 2018 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 241211310F2 for ; Tue, 5 Jun 2018 08:47:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2vRV-VDRqU-C for ; Tue, 5 Jun 2018 08:47:06 -0700 (PDT) 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 21B1A131092 for ; Tue, 5 Jun 2018 08:47:06 -0700 (PDT) Date: Tue, 05 Jun 2018 08:47:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528213625; bh=wR5bIVkr+TlB5Kl/QnxLO5K2OxdaaYD1YrTjMFm1BEM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vNlWTJIjLDRdLzfLFnn5PwHNr9w1tEPG3PU1BgkWcfPavRetXR+iOxLWqPCth0T5q dVmsnBVmYgN+IsebjGKs7nm9ZHgoJofuzUAHqJTIX5M/6E8NMlQAwLrRc11G/imQre nas6rt/lXCfPK0GYnXn5mb6HHvudn05h8Db6Jcsg= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b0792869b_71f93fdb22c60f88114978"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:47:09 -0000 ----==_mimepart_5b16b0792869b_71f93fdb22c60f88114978 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho: Is this resolved now that we have PNE? If so, can you close this? -- 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/1317#issuecomment-394760400 ----==_mimepart_5b16b0792869b_71f93fdb22c60f88114978 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho: Is this resolved now that we have PNE? If so, can you close this?

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

----==_mimepart_5b16b0792869b_71f93fdb22c60f88114978-- From nobody Tue Jun 5 08:49:17 2018 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 45B291310D3 for ; Tue, 5 Jun 2018 08:49:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pTft-ePqy2-T for ; Tue, 5 Jun 2018 08:49:14 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 DE53313105F for ; Tue, 5 Jun 2018 08:49:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528213753; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=HLtfzijdVMcDTT3rFbnLbTx1VVQg0BUZqCVbfTvwkjo=; b=zZ6EmHLK9mR6s6n27vw/dq9tYV5thBsds9Lq5HCMQ0ZtAUlbdoC12vzLp+xZUUZuTUM6nIMj 2B01m1aBBmKY20w5ur/vsO0tOXbptheEilTcxRZC/qk6WnJXok/eWo+N4A9+6ynLhMd6aV96 LY7DVOsKIYTSyiolMmnkaXfM/hc= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b16b0f8.7fdb6c6758a0-smtp-out-n02; Tue, 05 Jun 2018 15:49:12 -0000 (UTC) Date: Tue, 05 Jun 2018 08:49:11 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b16b0f780e10_3f1e2b06ff691c087194f@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 2eee0d: Remove sequence number from NEW_CONNECTION_ID Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16b0f780893_3f1e2b06ff691c0871891"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 15:49:16 -0000 ----==_mimepart_5b16b0f780893_3f1e2b06ff691c0871891 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/NCID-seq Home: https://github.com/quicwg/base-drafts Commit: 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6 https://github.com/quicwg/base-drafts/commit/2eee0d82ee9557a79a888dcf4097ce0c8e70ece6 Author: Martin Thomson Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove sequence number from NEW_CONNECTION_ID Closes #1280. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16b0f780893_3f1e2b06ff691c0871891-- From nobody Tue Jun 5 08:49:43 2018 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 CB5D21310D3 for ; Tue, 5 Jun 2018 08:49:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 PiSVqUcKk_Ub for ; Tue, 5 Jun 2018 08:49:39 -0700 (PDT) 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 9F66913105F for ; Tue, 5 Jun 2018 08:49:39 -0700 (PDT) Date: Tue, 05 Jun 2018 08:49:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528213778; bh=BQCTsx10YI7L6jJqCWBRNYHova21Sus5Vpe18psfwBI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XxhJJiKE4c5lC0jsqTTnPXeJcQOA0HbyqjhsAvkuF4THxCnknGofNX2lmETOKh1e9 pA854KVKQeN/Smt1eZ/X2cseLWIOZbNzcKAwaQVFWFTwt8V9fTBKBSgm6J6yj6hVHu 2ZhBbMrRAsgoyVQ6P7kCVkpRb9HXeb1fA0ksCnxI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Remove sequence number from NEW_CONNECTION_ID (#1419) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b112b4370_17ff3fecf598ef7810477"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:49:42 -0000 ----==_mimepart_5b16b112b4370_17ff3fecf598ef7810477 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closes #1280. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1419 -- Commit Summary -- * Remove sequence number from NEW_CONNECTION_ID -- File Changes -- M draft-ietf-quic-transport.md (14) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1419.patch https://github.com/quicwg/base-drafts/pull/1419.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/1419 ----==_mimepart_5b16b112b4370_17ff3fecf598ef7810477 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closes #1280.

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

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

Commit Summary

  • Remove sequence number from NEW_CONNECTION_ID

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 mute the thread.

----==_mimepart_5b16b112b4370_17ff3fecf598ef7810477-- From nobody Tue Jun 5 08:50:37 2018 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 D3C1B1310D3 for ; Tue, 5 Jun 2018 08:50:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 pnQKLkVtJdyH for ; Tue, 5 Jun 2018 08:50:34 -0700 (PDT) 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 2EDD813105F for ; Tue, 5 Jun 2018 08:50:34 -0700 (PDT) Date: Tue, 05 Jun 2018 08:50:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528213833; bh=R2c85pmf9E7UZbQC2Rci+LJenYjf6S7SuOYwkOeGvho=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RGuRdVYE8a16rZpiNUgUn41HLXLhyJ9BqLAz4B347HMUOnzKKg3fiEyMe1t0aVlFA nTxzu8OjXj3GjuWKeHdll5JSh4dSopBBcefEsh6KYbOu+0Fa5eOyjE7Y9udciFCvio OK25rjiRWLgh3VXFipwlTcynYAXlheMWHUbWOAYU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove sequence number from NEW_CONNECTION_ID (#1419) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b1497c557_17ee3f8e77f72f841349ae"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:50:36 -0000 ----==_mimepart_5b16b1497c557_17ee3f8e77f72f841349ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Just to clarify intent here. I tried to find text to add back, but I just can't see there being any value in it. I could say explicitly that any connection ID can be used, but the text remaining effectively implies that. -- 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/1419#issuecomment-394761633 ----==_mimepart_5b16b1497c557_17ee3f8e77f72f841349ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Just to clarify intent here. I tried to find text to add back, but I just can't see there being any value in it. I could say explicitly that any connection ID can be used, but the text remaining effectively implies that.

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

----==_mimepart_5b16b1497c557_17ee3f8e77f72f841349ae-- From nobody Tue Jun 5 08:54:21 2018 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 EF3D31310D3 for ; Tue, 5 Jun 2018 08:54:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gWb0vfYn1IOx for ; Tue, 5 Jun 2018 08:54:17 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A2451310C5 for ; Tue, 5 Jun 2018 08:54:17 -0700 (PDT) Date: Tue, 05 Jun 2018 08:54:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528214056; bh=+7cqabVWqxRviZiF1RWQ+mlLVJgDQW7QLELQDDlXp34=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UksczVSmXcIioxtSqO4nqKeWQNedVHsfDPWmepkQiWCxVWn0rM/3sseTWhz+9/efc k+LcRlq3PSQmohGm3ofB0usbpmzxexnkYuccKIxMyYLrChXmMol+LgHxzIbtWVdPfE FBYPv1EAtBtc6Mxh18cZ/lY0j0sDITN9XVdkq00w= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: Enhance guidance of using "hq" (#1415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b228714b7_33922b03d2046f54309079"; 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.26 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: Tue, 05 Jun 2018 15:54:19 -0000 ----==_mimepart_5b16b228714b7_33922b03d2046f54309079 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Perhaps, but it's easier to ask the RFC Editor to drop an entire section than to delete a forward reference to the section, and I'm worried we'd end up with an erratum from a hanging reference. Let me see if I can move 2.2.1 earlier in the section instead. -- 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/1415#issuecomment-394763028 ----==_mimepart_5b16b228714b7_33922b03d2046f54309079 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Perhaps, but it's easier to ask the RFC Editor to drop an entire section than to delete a forward reference to the section, and I'm worried we'd end up with an erratum from a hanging reference. Let me see if I can move 2.2.1 earlier in the section instead.

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

----==_mimepart_5b16b228714b7_33922b03d2046f54309079-- From nobody Tue Jun 5 08:55:46 2018 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 E1DA813111F for ; Tue, 5 Jun 2018 08:55:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 RkTzmlHQfF_a for ; Tue, 5 Jun 2018 08:55:35 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C02DE1310F2 for ; Tue, 5 Jun 2018 08:55:35 -0700 (PDT) Date: Tue, 05 Jun 2018 08:55:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528214135; bh=quz9YuxXIEzv0v7nZ0r/KZsJV+sVoz8Qbp7uiV482DY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xH6Iph1EaV1Gsw59mt5//TIp9FyJlebaKh+2pvNQSCJTU1gOWhbQ0DOoBtivHOHeJ 5Ay6bSdDjNbFbGqwtJ5eUvUvAJPdM7tB3BZ7QGcCnQgvnY8jYMA6loECNQHH2cgnDP tbFuA2beWsOLIwgpkNTteiaXRUGJc/Lky3QiUzYQ= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b277264e3_75292b08664f8f50124016"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:55:45 -0000 ----==_mimepart_5b16b277264e3_75292b08664f8f50124016 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From editors' meeting: The original issue describes various representations of CIDs, that are all intentional. There's no clear value in making the long header longer (by using 8-bit lengths), and the NEW_CONNECTION_ID frame is not visible on the wire anyways. Closing, but please open this if anyone thinks there's something to be done. -- 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/1336#issuecomment-394763477 ----==_mimepart_5b16b277264e3_75292b08664f8f50124016 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From editors' meeting: The original issue describes various representa= tions of CIDs, that are all intentional. There's no clear value in making= the long header longer (by using 8-bit lengths), and the NEW_CONNECTION_= ID frame is not visible on the wire anyways. Closing, but please open thi= s if anyone thinks there's something to be done.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16b277264e3_75292b08664f8f50124016-- From nobody Tue Jun 5 08:55:51 2018 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 895341310FA for ; Tue, 5 Jun 2018 08:55:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 u7vvFXqeHgmn for ; Tue, 5 Jun 2018 08:55:37 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B750C131116 for ; Tue, 5 Jun 2018 08:55:37 -0700 (PDT) Date: Tue, 05 Jun 2018 08:55:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528214137; bh=cE9fAc9RTIlbIKfQBJuSaRFMrIqXtVyKXFFz1Fkb12s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HQiNsmD7pfzEa+nVskeooMuxLciBgPwo/we6R5TFE2ofC1AN5/sG7Mc0S4SPtibjS 8RR5z33+XyEbmwzQJGc0/KgGuy9SopZR5gXkxZ69LDtcg01PW7rLy+rdTC0IeTRORM Kd5RaRR2KprbFXQkdLIDdp+PvDhErBPErtGA9U0Q= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b2791d97_78fd2af6fba90f5c12174e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 15:55:47 -0000 ----==_mimepart_5b16b2791d97_78fd2af6fba90f5c12174e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1336. -- 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/1336#event-1664091688 ----==_mimepart_5b16b2791d97_78fd2af6fba90f5c12174e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1336.

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

----==_mimepart_5b16b2791d97_78fd2af6fba90f5c12174e-- From nobody Tue Jun 5 09:01:53 2018 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 273291310D5 for ; Tue, 5 Jun 2018 09:01:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 mTr31iktbj39 for ; Tue, 5 Jun 2018 09:01:49 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 410E71310AD for ; Tue, 5 Jun 2018 09:01:49 -0700 (PDT) Date: Tue, 05 Jun 2018 09:01:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528214507; bh=S0YNjcfJh53hYd7B9MkOLskqIO91IUusE2uClnh2ATk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Ek5/BxowbYsjJkEJttmPjUQEthFiXZsBimnLJguF5q1H0WhIbkOgLiQLKVl7txt4g SDt882sCwV+z9TZcdrwL0sEzxQb5k2vYACWW88VxG4IO0ScL1N3PlEU8GH+ykVCoSz IagVAi2XGrCsdAgszE0EBSOj6PO7rY6ncgAgxBnc= From: ianswett Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Publish Stream0 Link (#47) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b3eb70d08_466e3ff8754b2f78214053"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 05 Jun 2018 16:01:51 -0000 ----==_mimepart_5b16b3eb70d08_466e3ff8754b2f78214053 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/47 -- Commit Summary -- * Publish Stream0 Link -- File Changes -- M interim-18-06/agenda.md (2) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/47.patch https://github.com/quicwg/wg-materials/pull/47.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/wg-materials/pull/47 ----==_mimepart_5b16b3eb70d08_466e3ff8754b2f78214053 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/47

Commit Summary

  • Publish Stream0 Link

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 mute the thread.

----==_mimepart_5b16b3eb70d08_466e3ff8754b2f78214053-- From nobody Tue Jun 5 09:14:55 2018 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 21D861310DD for ; Tue, 5 Jun 2018 09:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 sERlE-72wxsY for ; Tue, 5 Jun 2018 09:14:51 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C6344130FA0 for ; Tue, 5 Jun 2018 09:14:51 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528215291; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=guaJadxyYa9kPssVMY7HB2G+78Ut97F4jL54bleiNfo=; b=er376heNF8kfQOSZk0BMB/REwlJE4nkRIPciW3csfhbCU4Fti1N9IRvctvfTQjPA6vp3jfJq 8kgGJMVtGY5liE+wx8lpps/2q4HcaobXYSkvaRAfmwpYSsT9DOGVw1vvZ6wvKmDFcUnrsxyP AsIAsKW8Ao9MfKPyWoE5PN54kGQ= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b16b6fb.7f453d85ed20-smtp-out-n03; Tue, 05 Jun 2018 16:14:51 -0000 (UTC) Date: Tue, 05 Jun 2018 09:14:50 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b16b6fac4a09_300e2ae4a1859c14461be@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 613ec0: Publish Stream0 Link Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b16b6fac4673_300e2ae4a1859c144602f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 05 Jun 2018 16:14:53 -0000 ----==_mimepart_5b16b6fac4673_300e2ae4a1859c144602f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 613ec0e2721893d8ad9d1f13c1d31ac1230b2eee https://github.com/quicwg/wg-materials/commit/613ec0e2721893d8ad9d1f13c1d31ac1230b2eee Author: ianswett Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Publish Stream0 Link Commit: 7ad4d397115480f08b99d9102ceaa91fb7a26d2c https://github.com/quicwg/wg-materials/commit/7ad4d397115480f08b99d9102ceaa91fb7a26d2c Author: Mark Nottingham Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- Merge pull request #47 from ianswett/patch-1 Publish Stream0 Link Compare: https://github.com/quicwg/wg-materials/compare/5fc609df9556...7ad4d3971154 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b16b6fac4673_300e2ae4a1859c144602f-- From nobody Tue Jun 5 09:15:02 2018 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 4E6EE130FA0 for ; Tue, 5 Jun 2018 09:14:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 KoRy9aMVg5f8 for ; Tue, 5 Jun 2018 09:14:53 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F801310D3 for ; Tue, 5 Jun 2018 09:14:52 -0700 (PDT) Date: Tue, 05 Jun 2018 09:14:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528215292; bh=tbqUZA+pM4K1c06xPEEa0hAuN84ztOEJWqP+jPPQxak=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q7gu+tbqq8dH/TWJYfoDIMbG6KUZFT8ZCi1zj6Z9irJnPX0uVFJ46K7yTZ42e17iq 5EFVupZFlWtf1UMsBR1h9E1Z9yQi278slnQEHCNsArUudkoKS3Iyh/vU8XuSD+2W4+ KZAnjhavFqxvJDZ2F3jbaBBh9SLIr+cfW5UPtnE0= From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Publish Stream0 Link (#47) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b6fc82782_638d2afc2e53ef582509b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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.26 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: Tue, 05 Jun 2018 16:14:55 -0000 ----==_mimepart_5b16b6fc82782_638d2afc2e53ef582509b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #47. -- 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/wg-materials/pull/47#event-1664135812 ----==_mimepart_5b16b6fc82782_638d2afc2e53ef582509b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #47.

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

----==_mimepart_5b16b6fc82782_638d2afc2e53ef582509b5-- From nobody Tue Jun 5 09:22:05 2018 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 28C56131092 for ; Tue, 5 Jun 2018 09:22:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xoE4TAsMSZqf for ; Tue, 5 Jun 2018 09:22:01 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71DB71310D3 for ; Tue, 5 Jun 2018 09:22:01 -0700 (PDT) Date: Tue, 05 Jun 2018 09:22:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528215720; bh=4rN89kz0T+uS6cmtH+qKxtU13YVKRkpv6j4Fzs/BHOk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Bw7aMfyI44FPk3BJeh57pz7kF4DX8grBkRg/GR7WVzIBZ08Khf+dyPFi3lb9iUxFg 2OeILnm5ioRNmsv7scZbkB05KMkS21q37SlUtK2J4wmCoNsY8dwUgvS/5c3+Vkt02m 1QCPbXwcW1ORc6XY85BTDOkbnUXxUYpntJy04Hp4= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet number transform should be negotiated (#1296) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b16b8a89d0a5_70ab2b25f2dd8f5480733"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Tue, 05 Jun 2018 16:22:03 -0000 ----==_mimepart_5b16b8a89d0a5_70ab2b25f2dd8f5480733 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson I see that the issue is on the agenda to be discussed. PNE aims to solve two problems - ossification and unlinkability for voluntary migration. The primary motivation for making it optional is that there are deployments where one or both of these problems do not exist. Using versions does not help if the version number is not standardized and it also effectively halves the version space. I would prefer that we use a transport parameter for this. Always encrypting PNE for long headers is not a concern since the TLS handshake is already many orders of magnitude costlier. The primary concern around PNE is performance and hardware offloads, so making it optional for short headers solves this issue and can be negotiated in transport parameters. -- 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/1296#issuecomment-394772384 ----==_mimepart_5b16b8a89d0a5_70ab2b25f2dd8f5480733 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson I see that the = issue is on the agenda to be discussed. PNE aims to solve two problems - = ossification and unlinkability for voluntary migration. The primary motiv= ation for making it optional is that there are deployments where one or b= oth of these problems do not exist. Using versions does not help if the v= ersion number is not standardized and it also effectively halves the vers= ion space. I would prefer that we use a transport parameter for this. Alw= ays encrypting PNE for long headers is not a concern since the TLS handsh= ake is already many orders of magnitude costlier. The primary concern aro= und PNE is performance and hardware offloads, so making it optional for s= hort headers solves this issue and can be negotiated in transport paramet= ers.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b16b8a89d0a5_70ab2b25f2dd8f5480733-- From nobody Wed Jun 6 00:13:10 2018 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 47BE2130EBC for ; Wed, 6 Jun 2018 00:13:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 jhn6UDjt52qa for ; Wed, 6 Jun 2018 00:13:06 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 1267812426A for ; Wed, 6 Jun 2018 00:13:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528269185; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=CauHMpGibgK6gtYvVk8bnENOWezAJnNb51w7yIqpgQE=; b=agopu34Gfj87qDACdc61M+yAfWNZfoN/ZPYxanahcreYJYYIqcCQ2g7GkJRfgKTtf4Fh7yyP DsrXub0kMQTvA1DR5mW7KDlbC/oLDGKt4R2ORHQq5qhrM6WrULkQgc8H+cSr4oCOyUbN1pM+ i6wzgBfkVrkkMQSac20WYpR6dE4= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b178980.7fbb76f3bc30-smtp-out-n01; Wed, 06 Jun 2018 07:13:04 -0000 (UTC) Date: Wed, 06 Jun 2018 00:13:03 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b17897f76538_338b2ae4994c7c0c37289@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 24ffac: extra 'h' Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b17897f76182_338b2ae4994c7c0c371e8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 07:13:08 -0000 ----==_mimepart_5b17897f76182_338b2ae4994c7c0c371e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 24ffac058af543a1e1facbc5c069d422edebc927 https://github.com/quicwg/wg-materials/commit/24ffac058af543a1e1facbc5c069d422edebc927 Author: Mark Nottingham Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- extra 'h' **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b17897f76182_338b2ae4994c7c0c371e8-- From nobody Wed Jun 6 00:25:17 2018 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 17413130EC7 for ; Wed, 6 Jun 2018 00:25:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 nK4ho6pHH4q3 for ; Wed, 6 Jun 2018 00:25:13 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 65CAC130EC3 for ; Wed, 6 Jun 2018 00:25:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528269912; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=j+vxuyuSkq3C+oON/Lq9s98tXUzCbTv0zJgJnLE30Hc=; b=g9+ZotRC1xfOEgsrQUcGUCLPjt3ptyx3PrzuG1QkFB+V9+B/d08bj/TPgD6hPlkE2DDdrYYe 0Dzbc4VPop+sFEikiCIWziFoVZkC4WHsjS+nzsfsWiCi22PdVh1WlLts05j3m5Ad3feOx2AS nrFcJUI9DJgG1rlgdBIuDIQVAok= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b178c58.7f1c83ee9b10-smtp-out-n02; Wed, 06 Jun 2018 07:25:12 -0000 (UTC) Date: Wed, 06 Jun 2018 00:25:11 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b178c576ef14_5d182aeb66cfdc04371bb@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] fb2eb3: update stream0 link Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b178c576eaf2_5d182aeb66cfdc043702f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 07:25:16 -0000 ----==_mimepart_5b178c576eaf2_5d182aeb66cfdc043702f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: fb2eb30633374f41328ec47e1cb80839ca1caf12 https://github.com/quicwg/wg-materials/commit/fb2eb30633374f41328ec47e1cb80839ca1caf12 Author: Mark Nottingham Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M interim-18-06/agenda.md Log Message: ----------- update stream0 link **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b178c576eaf2_5d182aeb66cfdc043702f-- From nobody Wed Jun 6 00:46:22 2018 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 209BB130ECA for ; Wed, 6 Jun 2018 00:46:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 k4-TLqk8o6Ub for ; Wed, 6 Jun 2018 00:46:17 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ADD8130EC7 for ; Wed, 6 Jun 2018 00:46:17 -0700 (PDT) Date: Wed, 06 Jun 2018 00:46:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528271176; bh=LUs/owT7qoHGvISkMBVosN+uCVnxGF82ZX3BOF/tfbY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XGrX0MqAYKvdeblfvFOCvsQemUl2fs+cvlj4fPO3emd4whmXaN055j7VIpkNKcGc9 miHzKgqSkn+h8DJRcuHFUxnd4XKYGq8MSpaZ1WwO5U7t4Ds700ghf4zkFpXuj2I0l4 9SUjNVZ6E1vIz0zc+ew6soiuzTDl3sdUUvAFyBdM= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: Enhance guidance of using "hq" (#1415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1791482ce01_6fe13fd948feaf7c140821"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 07:46:21 -0000 ----==_mimepart_5b1791482ce01_6fe13fd948feaf7c140821 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah I'm sympathetic with making the RFC editor life easier (and mitigating future problems). -- 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/1415#issuecomment-394973901 ----==_mimepart_5b1791482ce01_6fe13fd948feaf7c140821 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yeah I'm sympathetic with making the RFC editor life easier (and mitigating future problems).

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

----==_mimepart_5b1791482ce01_6fe13fd948feaf7c140821-- From nobody Wed Jun 6 02:34:42 2018 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 52E8E130EDE for ; Wed, 6 Jun 2018 02:34:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 B4jpqjvulbSR for ; Wed, 6 Jun 2018 02:34:32 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B5E0130EDB for ; Wed, 6 Jun 2018 02:34:32 -0700 (PDT) Date: Wed, 06 Jun 2018 02:34:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528277669; bh=IlKF0QfQvQZzIwqkGXus7y1kL+22W2qzze3ihbcFhHM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yl+aRReqoPyq20XlQH7u7KsU3YtIMvhRFtMafYPYOZtD1eRA0goEXnumiBU3GI2TD KXfubcnCMUUgkGKcUlEIxkSss3brGK15PpvZCc+0KPfIvRMOHXdz201pRp7p6HD+fy ayoRLL7pM/N0ja1BfsBYTufoewgwgwYBuC+s+aDo= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17aaa59e4fd_1bb32ac5ecb7cf50161074"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 09:34:41 -0000 ----==_mimepart_5b17aaa59e4fd_1bb32ac5ecb7cf50161074 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinduke made a good point about this, which made me reconsider this idea. A man-on-the-side attacker can copy whatever details they need from packets an endpoint sends in its use of a stateless reset oracle. That is, if the stateless reset depends on data in a packet that an endpoint sends (and it can't depend on anything more than that), then the attacker simply copies whatever it needs from a genuine packet. A liveness check therefore only really makes the attackers job harder. Since the fix here that forces the attacker to be live is to make the stateless reset more complex, we should be very careful to consider the trade-off. -- 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/1230#issuecomment-395007821 ----==_mimepart_5b17aaa59e4fd_1bb32ac5ecb7cf50161074 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinduke made a good point = about this, which made me reconsider this idea. A man-on-the-side attack= er can copy whatever details they need from packets an endpoint sends in = its use of a stateless reset oracle. That is, if the stateless reset dep= ends on data in a packet that an endpoint sends (and it can't depend on a= nything more than that), then the attacker simply copies whatever it need= s from a genuine packet. A liveness check therefore only really makes th= e attackers job harder. Since the fix here that forces the attacker to b= e live is to make the stateless reset more complex, we should be very car= eful to consider the trade-off.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b17aaa59e4fd_1bb32ac5ecb7cf50161074-- From nobody Wed Jun 6 02:51:49 2018 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 5A0E4130EDB for ; Wed, 6 Jun 2018 02:51:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 K8C2ddZ2WwcQ for ; Wed, 6 Jun 2018 02:51:43 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B517130ED0 for ; Wed, 6 Jun 2018 02:51:43 -0700 (PDT) Date: Wed, 06 Jun 2018 02:51:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528278702; bh=GBk1iKyQ/5LL1JP76pUfBzZZ1k1+cuNcu+O4TM3KXM8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=X5HmS6O+kES0OZ6gh8yCv6W7E17vfPiM06ewxFVyDh25aPXlVoVEJRT38nKRDY9Ud 0KR8v2k78IddeGcg3R6B6Ql+oV8kYzCaa7gzZmtLNLTzA0nw26l4XoudQoZgYDi/nK hIrwhmQ05S2kSf1cCU4EJkb+KU3hb6zczcYJcMKY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17aeae2bd14_3de93fd8da534f8845359"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 06 Jun 2018 09:51:47 -0000 ----==_mimepart_5b17aeae2bd14_3de93fd8da534f8845359 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A loose thought, but intuition suggests: With more roundtrips it would probably be possible to design a challenge response scheme. Dead endpoint issues a stateless reset challenge. Live endpoint responds by hashing the challenge with a negotiated reset key. Dead end point issues a new reset by hashing the live response. MITM cannot use observed packets to issue new resets without triggering a roundtrip with proper routing between the endpoints, and the supposedly dead endpoint would not cooperate if it isn't dead. -- 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/1230#issuecomment-395012757 ----==_mimepart_5b17aeae2bd14_3de93fd8da534f8845359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A loose thought, but intuition suggests:

With more roundtrips it would probably be possible to design a challen= ge response scheme. Dead endpoint issues a stateless reset challenge. Liv= e endpoint responds by hashing the challenge with a negotiated reset key.= Dead end point issues a new reset by hashing the live response.

MITM cannot use observed packets to issue new resets without triggerin= g a roundtrip with proper routing between the endpoints, and the supposed= ly dead endpoint would not cooperate if it isn't dead.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b17aeae2bd14_3de93fd8da534f8845359-- From nobody Wed Jun 6 03:07:46 2018 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 18A14130EDB for ; Wed, 6 Jun 2018 03:07:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 cSXlagyUqKIa for ; Wed, 6 Jun 2018 03:07:40 -0700 (PDT) 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 77D16130ED0 for ; Wed, 6 Jun 2018 03:07:40 -0700 (PDT) Date: Wed, 06 Jun 2018 03:07:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528279659; bh=4DxGQScQv98Tqcv8FH1Js8hwbAXG5c8EqiyGQpYF/Sw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r/IcfqyiEgMtfPQz+H85wFFe4Wi0pHHl5z4Uy8dE6lht7yOmx7sF/YWNVSsZl4WCK AopIzfoELp74X9/fmO/9BTxfjvbFNmhop3SJYJqcLIGcA2rS6F0ka780Ac8+Q7iHzk nvFkSE5DHsCR3mH+GWC1IOX/6w/KLwENigeNOWls= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Speed handshake recovery when only undecryptable packets arrive (#1414) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17b26b7612c_155e3ffd063a2f801045e7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 10:07:45 -0000 ----==_mimepart_5b17b26b7612c_155e3ffd063a2f801045e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista and the consensus of the room was to punt this to v2. -- 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/1414#issuecomment-395017180 ----==_mimepart_5b17b26b7612c_155e3ffd063a2f801045e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Discussed in Kista and the consensus of the room was to punt this to v2.

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

----==_mimepart_5b17b26b7612c_155e3ffd063a2f801045e7-- From nobody Wed Jun 6 03:10:03 2018 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 20071130ED0 for ; Wed, 6 Jun 2018 03:10:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OFBMhCjmuKaU for ; Wed, 6 Jun 2018 03:09:58 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB13128BAC for ; Wed, 6 Jun 2018 03:09:57 -0700 (PDT) Date: Wed, 06 Jun 2018 03:09:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528279796; bh=dIKdvuh6e3GoGRB0rXmVVGvA+Tj87DAjrIMo+R5ZWHM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n92svmF0E5We6eD+Hdwq4sI6N0dob5V5q3P/6n9uRIDuKM2nBQykmvjfckHGA0h83 ZkDg9G5xI0XrvtlJT2EaoWfkJphvIIrM8oIxHX3G4zcve4HY+olI4pAT6MsSRo+8Pg vKfxV1pxqLPubdfgdTC5v4TC3OR/HssbiVI4CCSY= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17b2f4d832b_1a112acac2848f5c143443"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Wed, 06 Jun 2018 10:10:01 -0000 ----==_mimepart_5b17b2f4d832b_1a112acac2848f5c143443 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: +: Initial value = 0, incremented when a packet marked ECT(0) is received + +ECT_1: + +: Initial value = 0, incremented when a packet marked ECT(1) is received + +CE: + +: Initial value = 0, incremented when a packet marked CE is received + +Reception of duplicate packets SHOULD NOT increment the counters. Disagree, see my answer on issue #1405 -- 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/1372#discussion_r193360841 ----==_mimepart_5b17b2f4d832b_1a112acac2848f5c143443 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

Disagree, see my answer on issue #1405

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

----==_mimepart_5b17b2f4d832b_1a112acac2848f5c143443-- From nobody Wed Jun 6 05:08:40 2018 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 A5783130EDD for ; Wed, 6 Jun 2018 05:08:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 hArocree0qA5 for ; Wed, 6 Jun 2018 05:08:30 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBC3130EE8 for ; Wed, 6 Jun 2018 05:08:29 -0700 (PDT) Date: Wed, 06 Jun 2018 05:08:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528286908; bh=gXwAdvkgU8AJltK+MTQlNHOSCygiG4uolO1UPcTc7TM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wtGvMw4hsfH3YuboGVhOyY5FX1/ZFBEa67uxyAhub9vcrBmKNdBh6hfveyfI30s5d rhhgWOWmg3y+xlCfR4vzrHjQ+BnJvAsRPk2IaRd1VDvGiFGHTzC3oaIeEXm+4R0nPL lt94aXE2eWAUGjxZHtOGQbxwEdiimqVMLLHUSfxs= From: Lars Eggert Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17cebc3b57f_16fd23f80f97a4f7c2687a4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.26 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: Wed, 06 Jun 2018 12:08:36 -0000 ----==_mimepart_5b17cebc3b57f_16fd23f80f97a4f7c2687a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit larseggert commented on this pull request. > + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: +: Initial value = 0, incremented when a packet marked ECT(0) is received + +ECT_1: + +: Initial value = 0, incremented when a packet marked ECT(1) is received + +CE: + +: Initial value = 0, incremented when a packet marked CE is received + +Reception of duplicate packets SHOULD NOT increment the counters. ah, yes -- 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/1372#discussion_r193386151 ----==_mimepart_5b17cebc3b57f_16fd23f80f97a4f7c2687a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@larseggert commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

ah, yes

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

----==_mimepart_5b17cebc3b57f_16fd23f80f97a4f7c2687a4-- From nobody Wed Jun 6 05:12:01 2018 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 D4EAF130EF2 for ; Wed, 6 Jun 2018 05:11:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 JrA11-GKa8hA for ; Wed, 6 Jun 2018 05:11:54 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7300D130EEC for ; Wed, 6 Jun 2018 05:11:47 -0700 (PDT) Date: Wed, 06 Jun 2018 05:11:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528287106; bh=9KB6Cg8sqzdWQzpF8USTVxfkV9w5xXl5pKxXZW5OO4I=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=n5o57rVMTsL2OzhqzGR4RBsnAKLfNGQp9UCojLn3kOB6YpLZyuuqiszt+LUrEPFhY 0w1jkND+aN65BnOnx6gstR6JptGMWOwqK+1qMWwdYHAuuM9UY7DaCKzfIt8/NVyi79 2ZEue3q3fKnSj6VIJEFaKbUjXENqHNJaAK0Eac2A= From: ekr Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Add example flows (#48) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17cf82b5b75_5e232ac55dd5ef604822fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 06 Jun 2018 12:12:00 -0000 ----==_mimepart_5b17cf82b5b75_5e232ac55dd5ef604822fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/48 -- Commit Summary -- * Add example flows -- File Changes -- A interim-18-06/quic-flow.pdf (0) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/48.patch https://github.com/quicwg/wg-materials/pull/48.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/wg-materials/pull/48 ----==_mimepart_5b17cf82b5b75_5e232ac55dd5ef604822fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/48

Commit Summary

  • Add example flows

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 mute the thread.

----==_mimepart_5b17cf82b5b75_5e232ac55dd5ef604822fa-- From nobody Wed Jun 6 05:22:31 2018 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 79A50130F15 for ; Wed, 6 Jun 2018 05:22:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 cVNtdaCP3Mev for ; Wed, 6 Jun 2018 05:22:25 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 88A40130EFE for ; Wed, 6 Jun 2018 05:22:25 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528287744; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=VTYngrF34K7v5yk+Vs7XUGWvU5gtwVix9dsuPYQvYWc=; b=zdx5lJzInG16Tb8+8XjNJr36FibK+FlZv8o52z83h9kUfqWPv0/5eTx7u6BNH8g+ukSjCNGS UiIBui8u54PA65u9ILNoXZVAZ8VuEhvQOXmq0ToAiixrPUqP1uLhIRMFAIb5GjCxVdCEcWKa q5a7BZFk9s/XW7XhWVWRi8yHcwo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b17d200.7f498599ac90-smtp-out-n01; Wed, 06 Jun 2018 12:22:24 -0000 (UTC) Date: Wed, 06 Jun 2018 05:22:23 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b17d1ff98363_740f2ad1d4929c00114013@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 6c3022: Add example flows Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b17d1ff97c76_740f2ad1d4929c001139fc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 12:22:29 -0000 ----==_mimepart_5b17d1ff97c76_740f2ad1d4929c001139fc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 6c3022058f655a53bc60e20abe49504057142450 https://github.com/quicwg/wg-materials/commit/6c3022058f655a53bc60e20abe49504057142450 Author: EKR Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: A interim-18-06/quic-flow.pdf Log Message: ----------- Add example flows Commit: 9a7068a616ac4682686da32747f5f678c19b4e3a https://github.com/quicwg/wg-materials/commit/9a7068a616ac4682686da32747f5f678c19b4e3a Author: Lars Eggert Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: A interim-18-06/quic-flow.pdf Log Message: ----------- Merge pull request #48 from ekr/example_flows Add example flows Compare: https://github.com/quicwg/wg-materials/compare/fb2eb3063337...9a7068a616ac **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b17d1ff97c76_740f2ad1d4929c001139fc-- From nobody Wed Jun 6 05:22:36 2018 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 1A7C7130EF5 for ; Wed, 6 Jun 2018 05:22:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 dHkN4qc_S0II for ; Wed, 6 Jun 2018 05:22:25 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DFD8130EF7 for ; Wed, 6 Jun 2018 05:22:25 -0700 (PDT) Date: Wed, 06 Jun 2018 05:22:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528287744; bh=LAutOh7hzD/D5zu1y3jW5a/h+W+lbaJNvBp44+6PpW8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZWDVlILHxtJIzus7xZCyt28zLDTvCjXkif3gw6KhyPNWcH4Dg7UVNKl9WQDUit6q4 tLJAA80lANWVBAVR13T3NA5sQ19P3GswdiER12POIEitpqEyAOTBMeD8Nz9LXcmr68 Fc6+n3rjokKoXH382pCOpgr+zIpkDG5NRRTTynfg= From: Lars Eggert Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Add example flows (#48) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17d200cfdc3_497c3fc089026f7838119f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.26 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: Wed, 06 Jun 2018 12:22:30 -0000 ----==_mimepart_5b17d200cfdc3_497c3fc089026f7838119f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #48. -- 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/wg-materials/pull/48#event-1665981861 ----==_mimepart_5b17d200cfdc3_497c3fc089026f7838119f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #48.

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

----==_mimepart_5b17d200cfdc3_497c3fc089026f7838119f-- From nobody Wed Jun 6 05:41:42 2018 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 4ABFA130EED for ; Wed, 6 Jun 2018 05:41:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 RGjflU3nlorp for ; Wed, 6 Jun 2018 05:41:34 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01508130EFD for ; Wed, 6 Jun 2018 05:41:33 -0700 (PDT) Date: Wed, 06 Jun 2018 05:41:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528288893; bh=saetMJ0IK/K+hUvOeYgddErn9x0EDoj1ucoVKgGniD4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FCzxjttpdkkv5mi6w7rz9+wsDnzHw9G9mAE9iopOXANM2AEcOqVnEGn1w2xV44uT0 8movLQEI0c9aDmhxnHT7ly03V76UBvs4y0ZLSp1ZqE1LPjAKjSz2BlrP6Zq0T2z29i khbMzYrEtshuUe42CND6NIwiV8SpmK7HAEU0fM3Q= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17d67d10c0d_23d13f7ee671af80839b1"; 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.26 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: Wed, 06 Jun 2018 12:41:39 -0000 ----==_mimepart_5b17d67d10c0d_23d13f7ee671af80839b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista: Sender SHOULD coalesce in order of encryption level, but receiver MUST NOT stop processing packets in a datagram if it encounters one it cannot currently process. An implementation could either skip (and drop) the unreadable portion, or could buffer it for when the keys are available, just as if the packets were received out-of-order. -- 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/1287#issuecomment-395054332 ----==_mimepart_5b17d67d10c0d_23d13f7ee671af80839b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Discussed in Kista: Sender SHOULD coalesce in order of encryption lev= el, but receiver MUST NOT stop processing packets in a datagram if it enc= ounters one it cannot currently process. An implementation could either = skip (and drop) the unreadable portion, or could buffer it for when the k= eys are available, just as if the packets were received out-of-order.

=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b17d67d10c0d_23d13f7ee671af80839b1-- From nobody Wed Jun 6 06:00:05 2018 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 902F3130F03 for ; Wed, 6 Jun 2018 06:00:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 e5hX5l-q0XkA for ; Wed, 6 Jun 2018 05:59:58 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20970130EFD for ; Wed, 6 Jun 2018 05:59:58 -0700 (PDT) Date: Wed, 06 Jun 2018 05:59:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528289997; bh=Mpdsissh+0feJXBlb069oobkuQLPcBxeiuHsUGFIuwM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1hJ/lG6DkFxTTeHcAIjMimfB3A5bHz2nVqk4Qv15JyDQ2Vy4VsnBGlrxmxYDfVUX2 rv0IO5EhY70hvRqFt8xm7gravJ4qGVTVyuXAM+noV8ESEY8rgE9m5N4hxEVjMWLBdr 5WDOtO+KXNmpkQXiyMcOX2jdlS4aAv61YOrvgfz4= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17dacd4c6cc_57e03fcdc4a64f88136188"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 06 Jun 2018 13:00:02 -0000 ----==_mimepart_5b17dacd4c6cc_57e03fcdc4a64f88136188 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What if the length if the bad portion cannot be derived (other than byte for byte trial decryption of next embedded packet)? Or what if the unencerypted header section makes no sense? -- 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/1287#issuecomment-395059534 ----==_mimepart_5b17dacd4c6cc_57e03fcdc4a64f88136188 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

What if the length if the bad portion cannot be derived (other than byte for byte trial decryption of next embedded packet)? Or what if the unencerypted header section makes no sense?

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

----==_mimepart_5b17dacd4c6cc_57e03fcdc4a64f88136188-- From nobody Wed Jun 6 06:04:28 2018 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 A6186130EFB for ; Wed, 6 Jun 2018 06:04:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 k1nrHlzJ0wIO for ; Wed, 6 Jun 2018 06:04:18 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBE34130E8D for ; Wed, 6 Jun 2018 06:04:16 -0700 (PDT) Date: Wed, 06 Jun 2018 06:04:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528290256; bh=ix0E9C7xnVIMTnEZAuRqQs99qxXzPTrgcEMam+BFRnc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aAQj9sqeNTl7XoEBNLhtR3/1vCo314r6QLd9VcBiNaKgNWVfYGDmFRczSqNFlwuCt xa8ilr+yNAQf6sAcud2W8MKx7LivXRdlcq0Gbg//MzgDZmffMTo+0L+Z1UHutf7+xN sNzePAFgJCPFg+FfrpujzsstxkKTtyRTa0do91zU= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17dbd0f520_4e3d3f9f78eccf78693c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 06 Jun 2018 13:04:26 -0000 ----==_mimepart_5b17dbd0f520_4e3d3f9f78eccf78693c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If something is wrong with a first (only?) packet header, then you can't even know there is another coalesced packet after it. You can only just throw it all away. -- 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/1287#issuecomment-395060731 ----==_mimepart_5b17dbd0f520_4e3d3f9f78eccf78693c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If something is wrong with a first (only?) packet header, then you can't even know there is another coalesced packet after it. You can only just throw it all away.

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

----==_mimepart_5b17dbd0f520_4e3d3f9f78eccf78693c5-- From nobody Wed Jun 6 06:08:30 2018 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 F1F49130E8D for ; Wed, 6 Jun 2018 06:08:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bU8z5aZ5UI8d for ; Wed, 6 Jun 2018 06:08:23 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6B83130EFB for ; Wed, 6 Jun 2018 06:08:23 -0700 (PDT) Date: Wed, 06 Jun 2018 06:08:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528290503; bh=ltNu6uAImvii548RD+hZwgZ/xxpIsERXtvIgQ2pQyt0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VVWigoVTL+I4qVGoeecTFeUHk++AIn6Q3jhKitsQd3m5AvcKsG2E0XzrnI/MNGQVp SXZ39QVJHU9NpMviVLaOZLzspqZSakBhrWkw3xS7PUZ5QCoMOu/c48/jM6IoZz/KmQ qIeOKaC4Bbz+XwEjTIVXzo5qfo09VQBtKSYSZFvM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17dcc75f25_4e4c3f9f78eccf7810559b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 06 Jun 2018 13:08:29 -0000 ----==_mimepart_5b17dcc75f25_4e4c3f9f78eccf7810559b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Exactly, so you cannot adhere to the MUST. The same applies if something is wrong in the second packet. -- 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/1287#issuecomment-395062022 ----==_mimepart_5b17dcc75f25_4e4c3f9f78eccf7810559b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Exactly, so you cannot adhere to the MUST. The same applies if something is wrong in the second packet.

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

----==_mimepart_5b17dcc75f25_4e4c3f9f78eccf7810559b-- From nobody Wed Jun 6 06:11:57 2018 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 2B47D130E8D for ; Wed, 6 Jun 2018 06:11:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 Y1_Ld0mQ5u6f for ; Wed, 6 Jun 2018 06:11:50 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237AD130EFB for ; Wed, 6 Jun 2018 06:11:50 -0700 (PDT) Date: Wed, 06 Jun 2018 06:11:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528290709; bh=R1/6/yln3XuawClliGT9XWjOmNpMbpqLtvtgpptpW0A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DI2PZX6PedLEyDPHm/aAGvDfxzIblem99s1TlMWOWKDq/rbqzIoucJo64DJA1ZFGO 9ZjAe5eQjpi7gN1Vkg/bWCeRuKMYeQ9/zmkacMpt8d2Y4j2NR006ov8wbvEw7+/BwV Gje9PGtlDBWZ6l/ZpOxve84dDnowksp9MeJ/f2kY= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17dd9578e49_693b3fbd92c90f8822227b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 06 Jun 2018 13:11:55 -0000 ----==_mimepart_5b17dd9578e49_693b3fbd92c90f8822227b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think it's a bit of a semantic issue at this point. In my mind, as the receiver of the packet, if something is wrong with the header, I can only assume there were no more packets and I am therefore not violating the MUST by throwing it away. Either way, the MUST is not enforceable as far as I can tell. -- 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/1287#issuecomment-395063052 ----==_mimepart_5b17dd9578e49_693b3fbd92c90f8822227b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think it's a bit of a semantic issue at this point. In my mind, as t= he receiver of the packet, if something is wrong with the header, I can o= nly assume there were no more packets and I am therefore not violating th= e MUST by throwing it away. Either way, the MUST is not enforceable as fa= r as I can tell.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b17dd9578e49_693b3fbd92c90f8822227b-- From nobody Wed Jun 6 07:11:57 2018 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 94768130F2A for ; Wed, 6 Jun 2018 07:11:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 GjhQ8efkFoXe for ; Wed, 6 Jun 2018 07:11:51 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 22C33130F27 for ; Wed, 6 Jun 2018 07:11:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ri/GXCcOi7dGy3FKODUPhDvWiBI=; b=rC6pwCButUvsYibf sRUEFqR+SkEd4psZWKNrf/z5nbE5dv37L8+SqNLyM7wqhFW11n99cSaJm5SpBUvK hc6l2boUEG6C9ltqOzTNH5Phg01XwJpZTpENV2DMLjViEaCRJixENYjPROxaPIv1 vmylK5jwr4EY5eUM3CAKhdCAbQI= Received: by filter1094p1las1.sendgrid.net with SMTP id filter1094p1las1-16558-5B17EBA4-41 2018-06-06 14:11:48.641601043 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id aGHcpqUFSzOnGfHvvS2I7w for ; Wed, 06 Jun 2018 14:11:48.541 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id 821A4C014A for ; Wed, 6 Jun 2018 07:11:48 -0700 (PDT) Date: Wed, 06 Jun 2018 14:11:48 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] encoder stream can deadlock (#1420) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b17eba4802e8_305a2ab5cb532f5433518e"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2N+uL7VvBBJTXNqzgLej+O2cL4nH6CJdiZRD fRJS/wcOs4JNuwuLzZ7SEZL33tT3K4DcFqRLbv1HhRJ+pgMLY694GfIr3iulqJk2KX8MDi3BnP8RQ4 NXueNhhBekSyEUH/xIeVPA/1w8SqA4o9NcIZOAtpd/Hy8losrhnByi72+lcfeP/8FGcI7FEIJFlKvl M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 14:11:55 -0000 ----==_mimepart_5b17eba4802e8_305a2ab5cb532f5433518e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If the encoder sends a large block that is bigger than the flow control limit AND the decoder doesn't read the block until all the data is present, THEN the decoder never releases flow control credit for the block, but the encoder can't complete sending of the block. Deadlock. Advise caution. -- 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/1420 ----==_mimepart_5b17eba4802e8_305a2ab5cb532f5433518e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If the encoder sends a large block that is bigger than the flow control limit AND the decoder doesn't read the block until all the data is present, THEN the decoder never releases flow control credit for the block, but the encoder can't complete sending of the block. Deadlock. Advise caution.

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

----==_mimepart_5b17eba4802e8_305a2ab5cb532f5433518e-- From nobody Wed Jun 6 09:15:25 2018 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 3E5D9130F78 for ; Wed, 6 Jun 2018 09:15:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0gQ_7KrNj-6B for ; Wed, 6 Jun 2018 09:15:19 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1AA130F72 for ; Wed, 6 Jun 2018 09:15:19 -0700 (PDT) Date: Wed, 06 Jun 2018 09:15:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301718; bh=9ZZLXqJ/4xN14ZhLYipUsrKnns2qWnhJghflSvJOLzI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=auLjztqG9BM/prr3CwiKrRkA2rPnO/kNBS4o2hwsljPiOhp6GCW0s1h7ZA+IhELpE wvAEiwzh63d8D0cmqGl4JXUXyhaMq3IFtxjglKwAbyx4+smVBwb/Pz/jT03Ov/NKAj ShNdUVo5WuEO2qzQVSYXMwST9qNZ8GrCLjvuv7Is= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output ready (#1377) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18089655467_e653ffcfed8af78122772"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 06 Jun 2018 16:15:23 -0000 ----==_mimepart_5b18089655467_e653ffcfed8af78122772 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under [TODO: Table needed here?]. When multiple packets of Done. -- 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/1377#discussion_r193470927 ----==_mimepart_5b18089655467_e653ffcfed8af78122772 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under [TODO: Table needed here?]. When multiple packets of

Done.

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

----==_mimepart_5b18089655467_e653ffcfed8af78122772-- From nobody Wed Jun 6 09:15:33 2018 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 A8877130F90 for ; Wed, 6 Jun 2018 09:15:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 YR7gFfhxcAsS for ; Wed, 6 Jun 2018 09:15:25 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 517DF130F78 for ; Wed, 6 Jun 2018 09:15:25 -0700 (PDT) Date: Wed, 06 Jun 2018 09:15:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301724; bh=w++hW5al+GQONpg2Emk7BLGFpxupfiJfceQlwb0OJ14=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i3ELMDlcQ3N8uYetZ6zayMzGHlhWhQp7TGKBrGAjlusnR7PNdv/b0pU5iTgyEy5Wz VXu55G9W/VXz8nuxlBqoIVqIa4S9GpKlIE8DSlGMXrk92u+HWD37g8vsQ5SXZDSAMy tFgLB4Pz5kZWrtmb92Rq0NhlUaJFLjdB8QyCnHxk= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output ready (#1377) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18089c7dcaa_e7b3ffcfed8af7810601c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 06 Jun 2018 16:15:29 -0000 ----==_mimepart_5b18089c7dcaa_e7b3ffcfed8af7810601c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > -If 0-RTT is not attempted, then the client does not send packets protected by -the 0-RTT key (@0). In that case, the only key transition on the client is from -handshake packets (@H) to 1-RTT protection (@1), which happens after it sends -its final set of TLS handshake messages. +~~~ +{: #quic-tls-handshake title="QUIC Handshake"} I will add a new diagram. -- 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/1377#discussion_r193470962 ----==_mimepart_5b18089c7dcaa_e7b3ffcfed8af7810601c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

>  
-If 0-RTT is not attempted, then the client does not send packets protected by
-the 0-RTT key (@0).  In that case, the only key transition on the client is from
-handshake packets (@H) to 1-RTT protection (@1), which happens after it sends
-its final set of TLS handshake messages.
+~~~
+{: #quic-tls-handshake title="QUIC Handshake"}

I will add a new diagram.

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

----==_mimepart_5b18089c7dcaa_e7b3ffcfed8af7810601c-- From nobody Wed Jun 6 09:16:40 2018 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 6D580130F96 for ; Wed, 6 Jun 2018 09:16:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NbmE0T7_mRQ8 for ; Wed, 6 Jun 2018 09:16:20 -0700 (PDT) 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 A851D130F99 for ; Wed, 6 Jun 2018 09:16:20 -0700 (PDT) Date: Wed, 06 Jun 2018 09:16:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301780; bh=2vi4Kz7GBAzj1P3HIVhO3n6PJZSUx0sGf5L77JyXqqE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wQ1r987S91P0TcKLwiu2uFdes39HLjQarfe7vbs8EpfmAUy2ShFoWKt939+tKtpBY 1U7Mwa01MNciAIPhRsfz1dilm2ev8AxH8130LevV2CHpGxnk/mrKCMa/An1fK9Gs2X Whmm1aFBa7/zClxv64LNgF+fe/FgtYuM4cDWtEb0= From: krasic Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] encoder stream can deadlock (#1420) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1808d45aa3_2b6273fb27c90ef84799e3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: krasic 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.26 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: Wed, 06 Jun 2018 16:16:39 -0000 ----==_mimepart_5b1808d45aa3_2b6273fb27c90ef84799e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A decoder shouldn't do that. The same kind of deadlock would be possible for any app protocol that precedes app level messages with a length where the message length is allowed to be larger than flow control window. [Blocked decoding](https://quicwg.org/base-drafts/draft-ietf-quic-qpack.html#rfc.section.6.3.2) is only for dependencies . -- 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/1420#issuecomment-395127280 ----==_mimepart_5b1808d45aa3_2b6273fb27c90ef84799e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A decoder shouldn't do that. The same kind of deadlock would be poss= ible for any app protocol that precedes app level messages with a length = where the message length is allowed to be larger than flow control window= .

Blocked decoding is only for depen= dencies .

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1808d45aa3_2b6273fb27c90ef84799e3-- From nobody Wed Jun 6 09:19:57 2018 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 03B78130F74 for ; Wed, 6 Jun 2018 09:19:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ZeaTyMkp4LuG for ; Wed, 6 Jun 2018 09:19:53 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9BCE130F78 for ; Wed, 6 Jun 2018 09:19:52 -0700 (PDT) Date: Wed, 06 Jun 2018 09:19:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301992; bh=+dPm72zOHn+di4kWzY1NE9JYUPS6OUUBysNupBJMbJI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GEVI/3PYGSgqmUwQvlCbU9EJuW+y+sloG9yTGOYGY1FJXOtIw65C/we5cId+Ib500 V2C07ZInhRvqNWcjHjuUWIBW/X7zU5vJ5+3On1Tzif7VHAj0j7f/Fc6QnI7AXPne2R 02KEwdpw7KzYnIQbfgrILZZkpQfcArlGCrDcIQ30= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1809a8e2e_31223fa9b9548f8896427"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 06 Jun 2018 16:19:55 -0000 ----==_mimepart_5b1809a8e2e_31223fa9b9548f8896427 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @janaiyengar Yes. Let's close. Thank you for the ping. -- 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/1317#issuecomment-395128402 ----==_mimepart_5b1809a8e2e_31223fa9b9548f8896427 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar Yes. Let's close. Thank you for the ping.

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

----==_mimepart_5b1809a8e2e_31223fa9b9548f8896427-- From nobody Wed Jun 6 09:20:03 2018 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 97C02130F83 for ; Wed, 6 Jun 2018 09:19:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 SoKUr-DiR7Mg for ; Wed, 6 Jun 2018 09:19:56 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B5A5130F78 for ; Wed, 6 Jun 2018 09:19:56 -0700 (PDT) Date: Wed, 06 Jun 2018 09:19:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301995; bh=Bpo7PezIalbuOP7arIGkk8D7cInqV3zDPR+JqEakFGY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r8MrprWpBCphcDGUPt2Fo7i5UHaw8na0Up4GnjiUM1eHgpv102/0baNK4h0qcAQ6q 1ZrK6CS+3PQVR7hD16/TQmjiKgqFHnfY+1/y9RyFfE5Hzxkbw7mpurn1k5JqHI/qso J8YePX20h8FPQZPa6JBuLFrun3y3QBEV3SzPTz84= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1809ab5e923_15db2abd8d512f50125157"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 06 Jun 2018 16:20:01 -0000 ----==_mimepart_5b1809ab5e923_15db2abd8d512f50125157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1317. -- 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/1317#event-1666568887 ----==_mimepart_5b1809ab5e923_15db2abd8d512f50125157 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1317.

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

----==_mimepart_5b1809ab5e923_15db2abd8d512f50125157-- From nobody Wed Jun 6 12:32:16 2018 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 55574126F72 for ; Wed, 6 Jun 2018 12:32:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0d-JAiqiYtJ0 for ; Wed, 6 Jun 2018 12:32:12 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B05C120049 for ; Wed, 6 Jun 2018 12:32:12 -0700 (PDT) Date: Wed, 06 Jun 2018 12:32:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528313530; bh=RjZuWLdm/WjzAnzp7O5NNYMsDDzlPrhU8T8EalF91ig=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ifyFjvaTLg6vkste2MhXfGKiYr/agXd3TDczGpK0MYg1GhomY3ag29uMCe4BtlXjT QqlnxdHLaqhXxK3z9vYSNCwtJKMDOxIeR9nEhc1mXu/cuZSgSopNeMyE5T+ZdZvzK1 k5RJD137j+udFh5CTOC+z0LUEbsf63UOzx3MI5l0= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] encoder stream can deadlock (#1420) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1836ba918f9_4e592aae1402af5c1343b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Wed, 06 Jun 2018 19:32:16 -0000 ----==_mimepart_5b1836ba918f9_4e592aae1402af5c1343b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Right, if the decoder only wants to process the block in its entirety, it needs to buffer this data in application space and release the flow control. -- 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/1420#issuecomment-395186933 ----==_mimepart_5b1836ba918f9_4e592aae1402af5c1343b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Right, if the decoder only wants to process the block in its entirety, it needs to buffer this data in application space and release the flow control.

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

----==_mimepart_5b1836ba918f9_4e592aae1402af5c1343b9-- From nobody Wed Jun 6 13:10:18 2018 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 F15FA130DDF for ; Wed, 6 Jun 2018 13:10:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 2l545r25szTX for ; Wed, 6 Jun 2018 13:10:12 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 231A01292AD for ; Wed, 6 Jun 2018 13:10:12 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528315811; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=m0D4wYkjQL1WkCwxpTMHJHqGpmsUIwc4S8U2Sb/r1x0=; b=glxUmDwIkGRYL0wBbgwMoH/5HMty7iARjBK9Wf5D92yQHlTrcnGQSV7Hv6EBEbdCp+YNsSQW 46plm9VtNU6DQEOFh8shr8c0/E5uChFHnWpHNGcPLQ3zp3Jfilq/Fu9Xkmskn7/e+5W2btWr CvU1ZyBwtJxCfTdJzjjcYF08OO4= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b183fa3.7f9a30b90de0-smtp-out-n03; Wed, 06 Jun 2018 20:10:11 -0000 (UTC) Date: Wed, 06 Jun 2018 13:10:10 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b183fa285783_49812afc9f4b7c1c554a4@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 37874f: Placeholder, first pass Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b183fa28523d_49812afc9f4b7c1c55368"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:10:15 -0000 ----==_mimepart_5b183fa28523d_49812afc9f4b7c1c55368 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: 37874f580e9906af793ee74298ac2c0e34ac27d6 https://github.com/quicwg/base-drafts/commit/37874f580e9906af793ee74298ac2c0e34ac27d6 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Placeholder, first pass Commit: 4d5edc3945b508fdbe519cf15ebf594ca10cdbbd https://github.com/quicwg/base-drafts/commit/4d5edc3945b508fdbe519cf15ebf594ca10cdbbd Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Clean up types Compare: https://github.com/quicwg/base-drafts/compare/37874f580e99^...4d5edc3945b5 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b183fa28523d_49812afc9f4b7c1c55368-- From nobody Wed Jun 6 13:14:41 2018 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 DEF5B130DCE for ; Wed, 6 Jun 2018 13:14:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 C4B6E_Fpmrdd for ; Wed, 6 Jun 2018 13:14:33 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F39BB1292AD for ; Wed, 6 Jun 2018 13:14:32 -0700 (PDT) Date: Wed, 06 Jun 2018 13:14:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528316071; bh=hd9R/1zNL2AGEd8s5Wgg+13Oe8+0Jr1yN3GDmN3riWc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=W2thawJqr6wh5CCzgMmjrsYOe6IeeZOu/gc/roKQRqqbbJHeY6EcdySp1pDgKoZ5F +ZQytWrfIINtpii6cuOMaMnWOZUo/IA0rS+mu0VmEnFT2MWz/RskkQLGLqy5FFarVZ QIcgPCcJhOvWwPNUIzV9uLDQ8FmDv+C7a0ghDhAo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Stream 0 DT proposal conflicts with PRIORITY (#1421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1840a7c7be7_46a82ae718ef6f58453b7"; 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.26 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: Wed, 06 Jun 2018 20:14:37 -0000 ----==_mimepart_5b1840a7c7be7_46a82ae718ef6f58453b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit After the design team output, all client-initiated bidirectional streams are used for requests, including Stream 0. Since Stream 0 will be a valid, actual client request, this creates a conflict with the use of Stream ID 0 in PRIORITY to indicate the root of the priority tree. -- 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/1421 ----==_mimepart_5b1840a7c7be7_46a82ae718ef6f58453b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

After the design team output, all client-initiated bidirectional streams are used for requests, including Stream 0. Since Stream 0 will be a valid, actual client request, this creates a conflict with the use of Stream ID 0 in PRIORITY to indicate the root of the priority tree.

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

----==_mimepart_5b1840a7c7be7_46a82ae718ef6f58453b7-- From nobody Wed Jun 6 13:16:40 2018 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 B827E130DEE for ; Wed, 6 Jun 2018 13:16:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 jw2ymPbsbN4j for ; Wed, 6 Jun 2018 13:16:35 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 417751292AD for ; Wed, 6 Jun 2018 13:16:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528316194; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=B4hU+ribataH46aLW/njn5y24wnUwmlrUYCaYRZOl8A=; b=V5B8ZUL3pUdQyyOhFeWYFt3KLtUxS8hn5aYfIPeg3FMmTUJ7GQ4PGb4rRkgye6ct+UyxUwBZ zCxrE/vywpaE8n3b3iJu/7n3sY+Jqa7oUynTPScvLjJxh027096Ql/TRQyk/pmuzT1Q1zWL9 +YGQww0RDZAEyTwRy5l5UsVyqGk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b184121.7fa08e0864b0-smtp-out-n02; Wed, 06 Jun 2018 20:16:33 -0000 (UTC) Date: Wed, 06 Jun 2018 13:16:32 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b184120ed7ad_51b32aba6ca4bc0c6157@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 0e5047: 0 is a stream now Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b184120ed1c2_51b32aba6ca4bc0c6078"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:16:37 -0000 ----==_mimepart_5b184120ed1c2_51b32aba6ca4bc0c6078 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: 0e50479cd45573598565995f11e512afb2cb2b2a https://github.com/quicwg/base-drafts/commit/0e50479cd45573598565995f11e512afb2cb2b2a Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- 0 is a stream now **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b184120ed1c2_51b32aba6ca4bc0c6078-- From nobody Wed Jun 6 13:18:50 2018 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 97D3C130DEE for ; Wed, 6 Jun 2018 13:18:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 ab1oDxZMAuEY for ; Wed, 6 Jun 2018 13:18:44 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 4F1F71292AD for ; Wed, 6 Jun 2018 13:18:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=btJ+Lx9hZ9IS45sxmAlZ0wqe2l0=; b=cM8MjxmOfcHIt+kB u0q+JQY6WUb55s2iWIZQThPjXG/khuVEN+wCDOcy2D0VCsXIogLrqod0u8darDVF 1DnkQoFFQCb/jCFMw4bm27i1NcC/hRWj/IbIea1KFtO/AFdsA+R0f7/aoJRBAsLG tAGYJTyYDijLLdBYiHmJBc239aM= Received: by filter1363p1mdw1.sendgrid.net with SMTP id filter1363p1mdw1-27071-5B1841A3-1E 2018-06-06 20:18:43.492803678 +0000 UTC Received: from github-lowworker11-cp1-prd.iad.github.net (unknown [192.30.252.35]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id mYe_dbMSSmiZvJ-Fby3BqA for ; Wed, 06 Jun 2018 20:18:43.400 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker11-cp1-prd.iad.github.net (Postfix) with ESMTP id 57DA3E04B3 for ; Wed, 6 Jun 2018 13:18:43 -0700 (PDT) Date: Wed, 06 Jun 2018 20:18:43 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1841a356664_52853ff6f634ef7c9882a"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3TlVBqO9quzkz+pISiZWE3SQq6XRc/BP7yKw pTCfF3BTE0benvrD1VAHa75WF2oKFz/sQya9EbUX0U9LmRHCrbnhc7JYkJvUxmcsUnbf/4Ys++oCFh ISTidBRNSgCGe7ZcFPLCCtWQ2PCnfqgRb6uH3Bp9sw+BNaCUvnyYaLCfpegjLZdb2gCmMUWBeyYg9+ c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 20:18:48 -0000 ----==_mimepart_5b1841a356664_52853ff6f634ef7c9882a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit **DO NOT MERGE**: Dependent on #1398. Fixes #441, fixes #1421. Primarily for illustrative purposes, this is what I envision the addition of placeholders to the PRIORITY scheme would look like. Key points: - Flags for Stream ID vs. Push ID are now a two-bit type field - Filled in the fourth value as "root of the tree," fixing #1421, since Stream 0 is now a valid request stream - Server has a setting to declare how many placeholders you get - Client can use placeholders 0..N-1 - Server can prune closed streams aggressively (after 2 RTT to ensure client knows they're closed) You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1422 -- Commit Summary -- * Placeholder, first pass * Clean up types * 0 is a stream now -- File Changes -- M draft-ietf-quic-http.md (269) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1422.patch https://github.com/quicwg/base-drafts/pull/1422.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/1422 ----==_mimepart_5b1841a356664_52853ff6f634ef7c9882a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

DO NOT MERGE: Dependent on #1398. Fixes #441, fixes #1421.

Primarily for illustrative purposes, this is what I envision the additio= n of placeholders to the PRIORITY scheme would look like. Key points:

  • Flags for Stream ID vs. Push ID are now a two-bit type field
  • Filled in the fourth value as "root of the tree," fixing #1421, since Stream 0 is now a v= alid request stream
  • Server has a setting to declare how many placeholders you get
  • Client can use placeholders 0..N-1
  • Server can prune closed streams aggressively (after 2 RTT to ensure cli= ent knows they're closed)

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

  = https://github.com/quicwg/base-drafts/pull/1422

Commit Summary

  • Placeholder, first pass
  • Clean up types
  • 0 is a stream now

File Changes

Patch Links:

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

----==_mimepart_5b1841a356664_52853ff6f634ef7c9882a-- From nobody Wed Jun 6 13:21:32 2018 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 A61CD130F7F for ; Wed, 6 Jun 2018 13:21:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 jSNbcI9zgTgX for ; Wed, 6 Jun 2018 13:21:27 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 227061292AD for ; Wed, 6 Jun 2018 13:21:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528316486; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=x8bwOGpU1KNyvLe67C6goWkXLka5ckSBPTGE757h1LA=; b=PtCRfX9Ch5cZXFppCbKgPEgRhMSumVAEkmxUyGiDlYrbbEQGofkYds42+se9iHRWhz0176ug lvkvdW1RLZzNiJOvHOSqOrQjL9+4OLikBz9D4Y2aFmxMFkAL9shHoMxw/rJ7nKtwTw/n6LXp gEPLrPRv6+omc2p7GXfUkp0tINg= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b184246.7fe47564c750-smtp-out-n02; Wed, 06 Jun 2018 20:21:26 -0000 (UTC) Date: Wed, 06 Jun 2018 13:21:26 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b18424615120_41a42ab5ee39fc001641b@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 731c15: 0 is a stream now Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18424614d44_41a42ab5ee39fc00163cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:21:29 -0000 ----==_mimepart_5b18424614d44_41a42ab5ee39fc00163cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: 731c155c50ff35d7fedc41da49e2df107c36fa63 https://github.com/quicwg/base-drafts/commit/731c155c50ff35d7fedc41da49e2df107c36fa63 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- 0 is a stream now **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18424614d44_41a42ab5ee39fc00163cf-- From nobody Wed Jun 6 13:31:18 2018 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 A8A99130FD0 for ; Wed, 6 Jun 2018 13:31:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 AY2x8PVnzgf1 for ; Wed, 6 Jun 2018 13:31:14 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2065B130F94 for ; Wed, 6 Jun 2018 13:31:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528317073; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=7c0JsBqjswqHYDwGgThUDebwJ5kuC+c2GVIPuWJLM08=; b=BYCvL27QhUtKlSM6WoMAvtNWRQEkc4/o9O4+a1lqHnuEoA1Y/uykoYcsM1oh/IZKc4hERLnX UUuBvSF774Hh5yaNUIIp8OjtWMroefLOU5938zmA1KC4IHX1aE2vSKxQyJICXfORiFakbdHV WFTAYNwdgL3MREZxO0TtHe5mqLw= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b184491.7f9e5c29eed0-smtp-out-n03; Wed, 06 Jun 2018 20:31:13 -0000 (UTC) Date: Wed, 06 Jun 2018 13:31:11 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b18448fe3386_479c2af0ad39dc08760e3@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] af56f4: Remove Flags Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18448fe2d1d_479c2af0ad39dc087598e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:31:16 -0000 ----==_mimepart_5b18448fe2d1d_479c2af0ad39dc087598e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/strike_the_colors Home: https://github.com/quicwg/base-drafts Commit: af56f4137e1b8dfe95e70002f5319bacc0d914e0 https://github.com/quicwg/base-drafts/commit/af56f4137e1b8dfe95e70002f5319bacc0d914e0 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Remove Flags Commit: 6dd5822982c7c683b73627d344260e91eb2bccea https://github.com/quicwg/base-drafts/commit/6dd5822982c7c683b73627d344260e91eb2bccea Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Zero on send, ignored on receipt Compare: https://github.com/quicwg/base-drafts/compare/a6d2443d7a92...6dd5822982c7 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18448fe2d1d_479c2af0ad39dc087598e-- From nobody Wed Jun 6 13:32:57 2018 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 72121130FD6 for ; Wed, 6 Jun 2018 13:32:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 dcQ-CcDO4eUa for ; Wed, 6 Jun 2018 13:32:53 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18519130FD0 for ; Wed, 6 Jun 2018 13:32:53 -0700 (PDT) Date: Wed, 06 Jun 2018 13:32:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528317172; bh=VFf6EGZ6XHf9iG05xVH/r1k50RKrGQApcK0yJYaS7Bo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1EoLU8TycnBF1C0BskpYTSmrGo7hWvx+wRUJ4dl3HgV3cfqSHKrBpD+gKxOaGZ/sj TV9HgET95DoG9x3WMdcptxKvFCllwCLvy9H0cWJkcqIZHeK3AbtRfqfbNJbNbadKVi D7MIca8C816UFhdAMkgK/R6pICjw+UorNZo8woiU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Flags in HTTP/QUIC frames are wasted space (#1388) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1844f461a36_37c33fa764c4cf8490642"; 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.26 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: Wed, 06 Jun 2018 20:32:56 -0000 ----==_mimepart_5b1844f461a36_37c33fa764c4cf8490642 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1388 via #1398. -- 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/1388#event-1667077108 ----==_mimepart_5b1844f461a36_37c33fa764c4cf8490642 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1388 via #1398.

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

----==_mimepart_5b1844f461a36_37c33fa764c4cf8490642-- From nobody Wed Jun 6 13:33:03 2018 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 0ED46130FD0 for ; Wed, 6 Jun 2018 13:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 RXlYuKcyFpel for ; Wed, 6 Jun 2018 13:32:54 -0700 (PDT) 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 427D2130F94 for ; Wed, 6 Jun 2018 13:32:54 -0700 (PDT) Date: Wed, 06 Jun 2018 13:32:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528317173; bh=ul6Tfe8tC45LrMgG8b2GLDwo1aYGr7mOP31v9xN6mlw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ds4g46e5MkcYGjJd/U24+ynyohMpqspdU63KJcnweWOud8LS/PHIiS9Pu5doxsTjn vZeigE6uqJsEvL9Qf6hyKgdAfvLeR0tM4axUEMQok9PMApVosu+y/jn4TdbVIqnYkx AAKvgzjCmJcD0a9GKDeymFsLWDfKBsdZApKIo8Lg= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove Flags (#1398) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1844f58ab70_3db82af485f9cf5028278d"; 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.26 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: Wed, 06 Jun 2018 20:32:58 -0000 ----==_mimepart_5b1844f58ab70_3db82af485f9cf5028278d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1398. -- 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/1398#event-1667077105 ----==_mimepart_5b1844f58ab70_3db82af485f9cf5028278d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1398.

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

----==_mimepart_5b1844f58ab70_3db82af485f9cf5028278d-- From nobody Wed Jun 6 13:36:17 2018 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 D6B20130FD0 for ; Wed, 6 Jun 2018 13:36:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 GWcJo40XiSls for ; Wed, 6 Jun 2018 13:36:12 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 04D29130F94 for ; Wed, 6 Jun 2018 13:36:11 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528317371; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=DthUkmvjomvBxOZZ8wVXoocOq1xBEATwr+0xazV59+o=; b=zW8Jl2ppKetJr2F2TqLQ/9+SNq4RHWSt/CWvDsShLeTIIHYLKPddhkdm7WvilkzkiOuM4hiX BXyVD9xLMWgMO2CutiRM0+Bsh1p+ZOZ/uZjJO8+lEM+A2guA2YqZ1hyLtkhABlrQrOgmohBA g4uVlaBEcP4mZ98zBJIkUEV84fU= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b1845bb.7f23f5d52720-smtp-out-n02; Wed, 06 Jun 2018 20:36:11 -0000 (UTC) Date: Wed, 06 Jun 2018 13:36:11 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1845bb4d98d_612f2b072d569c082063a@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e492de: Placeholder, first pass Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1845bb4d3ee_612f2b072d569c08205da"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:36:14 -0000 ----==_mimepart_5b1845bb4d3ee_612f2b072d569c08205da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: e492de72f386495389f413dc03b425e550e9ba5c https://github.com/quicwg/base-drafts/commit/e492de72f386495389f413dc03b425e550e9ba5c Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Placeholder, first pass Commit: a38c84f700b89c430ecde17731af0aa0e6da1969 https://github.com/quicwg/base-drafts/commit/a38c84f700b89c430ecde17731af0aa0e6da1969 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Clean up types Commit: c236d1b2fcbc34df59a46a077ec5c5f40fe5eeb9 https://github.com/quicwg/base-drafts/commit/c236d1b2fcbc34df59a46a077ec5c5f40fe5eeb9 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- 0 is a stream now Compare: https://github.com/quicwg/base-drafts/compare/731c155c50ff...c236d1b2fcbc **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1845bb4d3ee_612f2b072d569c08205da-- From nobody Wed Jun 6 13:38:53 2018 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 A01E1131008 for ; Wed, 6 Jun 2018 13:38:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Hi3afwP-UwEm for ; Wed, 6 Jun 2018 13:38:41 -0700 (PDT) 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 389FD13102B for ; Wed, 6 Jun 2018 13:38:41 -0700 (PDT) Date: Wed, 06 Jun 2018 13:38:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528317520; bh=E9OfyIYb16qhYuj42/ZLE++90BiyHS1jhTu9Kz3dTv4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jaRyLTzYu5miFDrXkIw5t4U0YmDf4Cn3O/wrceOX4QvzIfNGEqNAlOtEDqe1LiGst TAkKKPG9BQVhp8vCUdEj7FpiOXIqYs3OfUWc92elpijGuG0ngW8L7yURtcqg91ZuNB rtNNZ3zGBefGgakv3smKU8jJrRGE+PvyyizLUl+s= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18465092318_35dd3f90e926ef80507a1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 06 Jun 2018 20:38:50 -0000 ----==_mimepart_5b18465092318_35dd3f90e926ef80507a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 8169543 Word order -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1422/files/c236d1b2fcbc34df59a46a077ec5c5f40fe5eeb9..816954348632ec64e91946351af3512da2ce498e ----==_mimepart_5b18465092318_35dd3f90e926ef80507a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b18465092318_35dd3f90e926ef80507a1-- From nobody Wed Jun 6 13:38:59 2018 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 3F9BB13101B for ; Wed, 6 Jun 2018 13:38:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 GzJRsDO4AgdH for ; Wed, 6 Jun 2018 13:38:38 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 59ABC131023 for ; Wed, 6 Jun 2018 13:38:38 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528317517; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=jnwyxAUaupQt5ZLcMZtHLM3172bnUXSEHhlIuaZi4Kw=; b=QFxamiP0XD+GyG6AbLvSTEESlYYMtdehgfyT+VADWMXncclM9+w/KH8koDO2aFepsxNNlQyw rCKvgEoAlgCvxjXCvnT+WqmcyGAgO1NVI7ZFyB9eJWGKTUtigwAl3JFBFF2PDGtEz1o0Y7Vv nOpQAxnBvUXHB2oaC8I/s1IJVBw= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b18464d.7f9da77e4300-smtp-out-n01; Wed, 06 Jun 2018 20:38:37 -0000 (UTC) Date: Wed, 06 Jun 2018 13:38:37 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b18464d808cf_4c0b2ab55b4a5c141537@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 816954: Word order Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18464d804df_4c0b2ab55b4a5c1414b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:38:50 -0000 ----==_mimepart_5b18464d804df_4c0b2ab55b4a5c1414b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: 816954348632ec64e91946351af3512da2ce498e https://github.com/quicwg/base-drafts/commit/816954348632ec64e91946351af3512da2ce498e Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Word order **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18464d804df_4c0b2ab55b4a5c1414b-- From nobody Wed Jun 6 13:42:54 2018 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 21449130FDA for ; Wed, 6 Jun 2018 13:42:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 NiIHU_fRdVxI for ; Wed, 6 Jun 2018 13:42:50 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 D6AE7130DD0 for ; Wed, 6 Jun 2018 13:42:49 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528317769; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=frxEdRo3ecGS+11kEQjL5I0SARrWG+HIkOvg6rLFtZI=; b=JCTD52gEmaOX8ZmPKC5fjWWCgBXyOwjMAtek094iJPyHl2M2z3te5RGEMzi0ZkhgCcbhZqHm 4D7pDjcpszfGHmF6VDZuGSeSvarAEglrQWTfPQkNi/ur/TqiIpdUehQ4nFdCj1M8g8yZzMHH 9oa3PQvjE4JQvMq7KTAm3UdtD7w= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b1844f1.7f60928e1ea0-smtp-out-n03; Wed, 06 Jun 2018 20:32:49 -0000 (UTC) Date: Wed, 06 Jun 2018 13:32:48 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1844f073f5d_23222af33a3dfc043616a@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 35e7e7: Remove Flags (#1398) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1844f07390c_23222af33a3dfc04360e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 20:42:52 -0000 ----==_mimepart_5b1844f07390c_23222af33a3dfc04360e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 35e7e7f6c02df3902c7db6f2d1b8b9de0d2d54dc https://github.com/quicwg/base-drafts/commit/35e7e7f6c02df3902c7db6f2d1b8b9de0d2d54dc Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Remove Flags (#1398) * Remove Flags * Zero on send, ignored on receipt **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1844f07390c_23222af33a3dfc04360e7-- From nobody Wed Jun 6 13:44:43 2018 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 6D3FA130FFA for ; Wed, 6 Jun 2018 13:44:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 0op6iVs55uY4 for ; Wed, 6 Jun 2018 13:44:25 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 6298F131006 for ; Wed, 6 Jun 2018 13:44:25 -0700 (PDT) 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=cP762lucv48opAqYBmT3IOoxWFk=; b=AyJT81Atocb2ciYI 8KL+xaU23YX9nyPkBz1oBg5HqEmJWB7w/5r2olJIVMmtF4GPG0fJgqCHIlrnBjlj FukU4YzsNY165Wt/Un7KQjWK2xbQRaZT+xfp1gvr+Vg2I3JQssGv93MW7RQWtBfn CfqrCG8JzD9Jk+0CcFMgxYafzGs= Received: by filter1401p1mdw1.sendgrid.net with SMTP id filter1401p1mdw1-6181-5B1847A8-2A 2018-06-06 20:44:24.655226334 +0000 UTC Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id N0wEFbh-ShiP0gEOEGKM1w for ; Wed, 06 Jun 2018 20:44:24.597 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id 81559C11A6 for ; Wed, 6 Jun 2018 13:44:24 -0700 (PDT) Date: Wed, 06 Jun 2018 20:44:24 +0000 (UTC) From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit stream open (#1342) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1847a87eb4b_7b1a2b1c145bcf6076074"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2S96XxF8RISXZ2+2gfRFWu0af2rC+wgXPRiH oas+VcOmxc2mt3Bcb44ObCC5scOh1kTZAee04v3No006N/KPLhVCuVyMl7stE6SQPQhGYND2LgHBNQ lzsHHEACDdzyayaFp3L70cUN6KYCL/kXvrAHeNm/EWzzi9GDmcQTDHNSx0WBC3uuIuTSibrLVvS0By A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 20:44:42 -0000 ----==_mimepart_5b1847a87eb4b_7b1a2b1c145bcf6076074 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Background: [original email](https://www.ietf.org/mail-archive/web/quic/current/msg01679.html), issue #634, issue #896, pr #1193. -- 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/1342#issuecomment-395207542 ----==_mimepart_5b1847a87eb4b_7b1a2b1c145bcf6076074 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Background: original email, issue #634, issue #896, pr #1193.

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

----==_mimepart_5b1847a87eb4b_7b1a2b1c145bcf6076074-- From nobody Wed Jun 6 13:49:39 2018 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 63E61130FD6 for ; Wed, 6 Jun 2018 13:49:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fFew28ULE3ls for ; Wed, 6 Jun 2018 13:49:34 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA92F130DD0 for ; Wed, 6 Jun 2018 13:49:33 -0700 (PDT) Date: Wed, 06 Jun 2018 13:49:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528318172; bh=pzYDfJNbykArU7DvYxWAN5d1ScthCbJDUsnEOwrtlME=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ioW2kvyMvXUaA72Bmmwe2J0Or/Ye+4yWZrZ0k+hbrPyfRwTt9il7C0Cp7HvzOqlrM RfeYHHIBUSS+t0eVLjaQD5JI5dRyBw1Por9T/C3hYibLqVb18/Ie3Mreo77Ovo31hu YGKm8hO7PBOfITfEu33DT07SfBvt3oS0IannpdlE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1848dcd0a0e_2b2e3fc56728ef8097463"; 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.26 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: Wed, 06 Jun 2018 20:49:37 -0000 ----==_mimepart_5b1848dcd0a0e_2b2e3fc56728ef8097463 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's enforceable insofar as, if you violate it, a peer that persistently violates the SHOULD NOT will never interop with you. It is required for compatibility that one side or the other comply with these recommendations; which one is a SHOULD and which a MUST is strictly a tiebreak. -- 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/1287#issuecomment-395208946 ----==_mimepart_5b1848dcd0a0e_2b2e3fc56728ef8097463 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's enforceable insofar as, if you violate it, a peer that persistent= ly violates the SHOULD NOT will never interop with you. It is required f= or compatibility that one side or the other comply with these recommendat= ions; which one is a SHOULD and which a MUST is strictly a tiebreak.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1848dcd0a0e_2b2e3fc56728ef8097463-- From nobody Wed Jun 6 13:55:47 2018 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 9DC7B130DD1 for ; Wed, 6 Jun 2018 13:55:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QHUzzehNBLS0 for ; Wed, 6 Jun 2018 13:55:43 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B16130DD0 for ; Wed, 6 Jun 2018 13:55:43 -0700 (PDT) Date: Wed, 06 Jun 2018 13:55:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528318542; bh=LsKBgSjYpRjiAYLRQE1GSTezbgoyw/iWKxDFJ8TLLTc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rVluFauoKFMwrjxm0GDfDyQ0Ms1vol2dDOxmRDgNcbTVCpoOqQLvAXe7ilPOoEa0S J1UotXuZ1gElICEjsl3FwWLZvhBOon1jwogOfXg+YyhZ78HcLFgp/jtej95EWNJe7Q Xf4McfDrscIPylfmMvAAX8Fe/8ULSBsRSh1oncTQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b184a4eaf839_60b53fc6c252af80504c1"; 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.26 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: Wed, 06 Jun 2018 20:55:46 -0000 ----==_mimepart_5b184a4eaf839_60b53fc6c252af80504c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj, this isn't targeted at a corrupted packet, but a well-formed one where you can tell from the headers that you don't yet have the keys. For example, a coalesced packet containing (0-RTT | Initial) -- the server won't be able to read the 0-RTT portion. It MUST skip to the second packet and process the Initial, though it is free to discard or return to the 0-RTT packet once that's done. -- 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/1287#issuecomment-395210799 ----==_mimepart_5b184a4eaf839_60b53fc6c252af80504c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj, this isn't targeted at = a corrupted packet, but a well-formed one where you can tell from the hea= ders that you don't yet have the keys. For example, a coalesced packet c= ontaining (0-RTT | Initial) -- the server won't be able to read the 0-RTT= portion. It MUST skip to the second packet and process the Initial, tho= ugh it is free to discard or return to the 0-RTT packet once that's done.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b184a4eaf839_60b53fc6c252af80504c1-- From nobody Wed Jun 6 14:03:04 2018 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 1BE8B130DD2 for ; Wed, 6 Jun 2018 14:03:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 sN3zR7EuGxVw for ; Wed, 6 Jun 2018 14:02:59 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 714E6130DCF for ; Wed, 6 Jun 2018 14:02:59 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528318978; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rHnWz0PSu16fzxrozEIDj6TahL+vqowlf31vbUZs37U=; b=G2wyydQ9sq4+TXOA7Nihv7ghbOzBquHOiFY/zdyBsX0rDn0cRd44St3twqXSDggCViStcoWJ 9lgooPfIP773kmkQzgnTKJ3or8N/EcWtOaRBXQp4IaJHDjpcV5Bnw8HPiIgwrpT/NL0no8eV hsEIY2WZHWiQSYh9iCP6wXI8IEg= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b184c02.7f9e5e44e1e0-smtp-out-n03; Wed, 06 Jun 2018 21:02:58 -0000 (UTC) Date: Wed, 06 Jun 2018 14:02:57 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b184c0130e45_14bf2af08c6d9c1c633a7@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 195f14: Coalescing guidance Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b184c0130ad5_14bf2af08c6d9c1c6321"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 06 Jun 2018 21:03:01 -0000 ----==_mimepart_5b184c0130ad5_14bf2af08c6d9c1c6321 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts Commit: 195f144870a810fff9e4e1518f52f779d384ea41 https://github.com/quicwg/base-drafts/commit/195f144870a810fff9e4e1518f52f779d384ea41 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Coalescing guidance **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b184c0130ad5_14bf2af08c6d9c1c6321-- From nobody Wed Jun 6 14:04:52 2018 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 B9AF0130DD8 for ; Wed, 6 Jun 2018 14:04:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3LgHZUf00Hig for ; Wed, 6 Jun 2018 14:04:44 -0700 (PDT) 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 5D8E6130DD2 for ; Wed, 6 Jun 2018 14:04:44 -0700 (PDT) Date: Wed, 06 Jun 2018 14:04:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528319083; bh=qEoD5SRszkPXosl3wiqPCUHC+UIHQNRMdmhTMnXqe9o=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=YcntTFnfcW6mH6lfWdp6K/BFw0Fi1cTjnXNF/bO5t+Q5BcUoZEWwcgnZp3wDJxTTG OxhYFcms3uiXXkQyutYDCVQbg9mD+I50rQ/x9RuRaxLBkuIckRrIq7e0YDwAFa3Lhe uiepFxCgh6qXRt3lsZQ8ra74WshZONhwcBK/Y02g= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b184c6bb6e6f_2f5f2aad0ba26f601513ca"; 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.26 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: Wed, 06 Jun 2018 21:04:48 -0000 ----==_mimepart_5b184c6bb6e6f_2f5f2aad0ba26f601513ca Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1287. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1423 -- Commit Summary -- * Coalescing guidance -- File Changes -- M draft-ietf-quic-transport.md (14) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1423.patch https://github.com/quicwg/base-drafts/pull/1423.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/1423 ----==_mimepart_5b184c6bb6e6f_2f5f2aad0ba26f601513ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1287.

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

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

Commit Summary

  • Coalescing guidance

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 mute the thread.

----==_mimepart_5b184c6bb6e6f_2f5f2aad0ba26f601513ca-- From nobody Wed Jun 6 14:20:03 2018 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 9448B130DD8 for ; Wed, 6 Jun 2018 14:20:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uOgR4v4CjVSH for ; Wed, 6 Jun 2018 14:19:58 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3725130DCF for ; Wed, 6 Jun 2018 14:19:57 -0700 (PDT) Date: Wed, 06 Jun 2018 14:19:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528319996; bh=tGDocKUGtJz2rBd1+ScICpRhhH0dlC8efbh+pwbjsOs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HSTvwGZOg/PIAp+m1DP5dEjgLtprevQ+alt2lTl6J9Jl8pqfrlz4/DWnnnhwfA/sc CtDz850QVrO/faOI4XcslyeKuoTUE4RAgfbC7kJHOnCu41dbyKFV1NzQASVp+XOJuH uf+GlQNAuEEFByNz+89wMkMj68vK2hJ/yDsJ9rWg= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] encoder stream can deadlock (#1420) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b184ffcc0bf8_58052b12193e6f601106d3"; 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.26 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: Wed, 06 Jun 2018 21:20:01 -0000 ----==_mimepart_5b184ffcc0bf8_58052b12193e6f601106d3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's also worth noting that we really have two situations here: On the encoder stream, nothing says the encoder has to send all updates in a single block. It can query for available flow control, write that much, and wait for more credit. The only time it deadlocks with this approach is when a single header is bigger than the flow control credit being issued, in which case don't put those huge Kerberos tickets in your dynamic table, for the love of God. On the request stream, you do have to send the whole header set all at once, which is harder. However, you're also bounding the size of headers you'll accept on any given stream; we can recommend that the flow control window be large enough to transfer the expected header set or that you be willing to buffer as needed. -- 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/1420#issuecomment-395217431 ----==_mimepart_5b184ffcc0bf8_58052b12193e6f601106d3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's also worth noting that we really have two situations here:

On the encoder stream, nothing says the encoder has to send all update= s in a single block. It can query for available flow control, write that= much, and wait for more credit. The only time it deadlocks with this ap= proach is when a single header is bigger than the flow control credit bei= ng issued, in which case don't put those huge Kerberos tickets in your dy= namic table, for the love of God.

On the request stream, you do have to send the whole header set all at= once, which is harder. However, you're also bounding the size of header= s you'll accept on any given stream; we can recommend that the flow contr= ol window be large enough to transfer the expected header set or that you= be willing to buffer as needed.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b184ffcc0bf8_58052b12193e6f601106d3-- From nobody Wed Jun 6 14:22:41 2018 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 93F15130DD8 for ; Wed, 6 Jun 2018 14:22:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 Q5rZh3rr18tq for ; Wed, 6 Jun 2018 14:22:32 -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 D78EC130DD3 for ; Wed, 6 Jun 2018 14:22:31 -0700 (PDT) Date: Wed, 06 Jun 2018 14:22:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528320151; bh=oY3ICLaIRujTOhkfCo+g4ERg2Mjdnh28bXrwp/ZPvpg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=W+1AI2TiSBQeYSFW1Rn9bAs1uAbWFUMWJxqYsFJdAETwQtsHRzV5CxID6CHR7BQHQ lriwo1PgajE1W+epWj1dhfM8v+XL8FXc9TGxD4bjRJCfFWDmgxTa9FcDrboQR4DaBf I8GQ/G2JztoTvIlfGADVpOvFJKFdNRXew6rTjxIQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove sequence number from NEW_CONNECTION_ID (#1419) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18509716e51_d892adaea242f588182d"; 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.26 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: Wed, 06 Jun 2018 21:22:39 -0000 ----==_mimepart_5b18509716e51_d892adaea242f588182d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. -- 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/1419#pullrequestreview-126560699 ----==_mimepart_5b18509716e51_d892adaea242f588182d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

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

----==_mimepart_5b18509716e51_d892adaea242f588182d-- From nobody Wed Jun 6 14:36:00 2018 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 B5872130DDC for ; Wed, 6 Jun 2018 14:35:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 J6686Mu273Kb for ; Wed, 6 Jun 2018 14:35:52 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96264130DD3 for ; Wed, 6 Jun 2018 14:35:52 -0700 (PDT) Date: Wed, 06 Jun 2018 14:35:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528320951; bh=84pqLZqgyvHWTODnYi5EaEeQVVz2xCi0fDywp9n40a4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=EmgLLZi/rCrccJWmLWYcEvANcD/HJtB5uThjzdN6yDmO2Fh29xnXmMUozAn0zTFpw WhpD9PvRhGeaWc189JGp7uTt8LYl0ut2oDffecG1fXnYsvm+Bl3JVnUDtSs2d9/mtn d/hI8mF0Ki1wFBu5WgCjjU5QwQFq3EJmtYnuy/Is= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1853b7e70df_590f2acb26242f54931c3"; 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.26 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: Wed, 06 Jun 2018 21:35:56 -0000 ----==_mimepart_5b1853b7e70df_590f2acb26242f54931c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In the repeated discussions of duplicated packets and what happens if an implementation accidentally processes them, it has become clear that an important property of QUIC in this respect is that every frame type is idempotent. It doesn't matter if you receive them once or a dozen times, nor how they are reordered (only provided they're not received before they're sent, of course). All that matters is that each reliable frame, or the information it carries, is received. This is perhaps an important property to document, both for future iterations of the WG who are expanding QUIC, and for extension frames as they will need to have this property as well. -- 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/1424 ----==_mimepart_5b1853b7e70df_590f2acb26242f54931c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In the repeated discussions of duplicated packets and what happens if an implementation accidentally processes them, it has become clear that an important property of QUIC in this respect is that every frame type is idempotent. It doesn't matter if you receive them once or a dozen times, nor how they are reordered (only provided they're not received before they're sent, of course). All that matters is that each reliable frame, or the information it carries, is received.

This is perhaps an important property to document, both for future iterations of the WG who are expanding QUIC, and for extension frames as they will need to have this property as well.

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

----==_mimepart_5b1853b7e70df_590f2acb26242f54931c3-- From nobody Wed Jun 6 14:49:14 2018 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 59EFC130DDC for ; Wed, 6 Jun 2018 14:49:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6sxWIpSw57uL for ; Wed, 6 Jun 2018 14:49:05 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AC55130DDD for ; Wed, 6 Jun 2018 14:49:05 -0700 (PDT) Date: Wed, 06 Jun 2018 14:49:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528321744; bh=WUT60pfrybw/uUD+oob2hFhgSXAIPRnLp61cBLSzLM4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PCdfko0SeWn0RtxBKw/yJt3Bccb0icbVIC72c2yJhWeFIKyrtTcO1aVsO+o2fl2wQ SOqUh9cWZVC/slEq05+iDkZVmK5c74+ty+15NtetJNoe0Se5FFE5ydM2Yv4jTb8JkQ 8DjNxgAXPWkVZLZB3D0FV8T5ktlFX5Ma6D007+Sk= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1856d052117_3d913fe75e56cf7c1107d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 06 Jun 2018 21:49:11 -0000 ----==_mimepart_5b1856d052117_3d913fe75e56cf7c1107d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > (only provided they're not received before they're sent, of course) I once had a discussion with a well-known danish physicist who seriously argued that it might be possible to receive data before they were transmitted and he considered had been contemplating putting up an experiment. -- 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/1424#issuecomment-395225071 ----==_mimepart_5b1856d052117_3d913fe75e56cf7c1107d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

(only provided they're not received before they're sent, of course) I once had a discussion with a well-known danish physicist who seriously = argued that it might be possible to receive data before they were transmi= tted and he considered had been contemplating putting up an experiment.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1856d052117_3d913fe75e56cf7c1107d5-- From nobody Wed Jun 6 15:31:40 2018 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 CE8A6130FF4 for ; Wed, 6 Jun 2018 15:31:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.606 X-Spam-Level: X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 g5WtyACAq-hw for ; Wed, 6 Jun 2018 15:31:35 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 645AF130DF0 for ; Wed, 6 Jun 2018 15:31:35 -0700 (PDT) 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=etUTj5FbK8Ls3a6StXlmC5x2HdM=; b=kqS2dwUkxyXgfwEe 5M+oNr3Jac810IEeIlb14NO3Y6nZBf6XgxLI73KZnjs9Ni/kGu7zPy7oKUhD4aTv 5XUO9Apa9oK2ik9bW4y/nd9a/Qhr/Nc1dYvgXjourBOXVACkpFaBQ4/WR118sJp0 z7fr1GJuoSotIKML6VnIofiT/XI= Received: by filter0209p1iad2.sendgrid.net with SMTP id filter0209p1iad2-7945-5B1860C6-11 2018-06-06 22:31:34.424845815 +0000 UTC Received: from github-lowworker-fc273f0.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0023p1mdw1.sendgrid.net (SG) with ESMTP id JpQbF-1BS8-mzMeTtRg7xg for ; Wed, 06 Jun 2018 22:31:34.182 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-fc273f0.cp1-iad.github.net (Postfix) with ESMTP id A15F5C00B3 for ; Wed, 6 Jun 2018 15:31:33 -0700 (PDT) Date: Wed, 06 Jun 2018 22:31:34 +0000 (UTC) From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1860c593c72_27ff2af9b2b9cf5423146a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1TzBnlxEiSjSqNuigaOJTGahbmqOcy53V7f9 NgOVCFl+GoJsrKny803dIjGS93AyA0B6E5gLHLyH1GhAdZVwMYjVpIES0QosbpBxlv32vtU5Lx5N1i Ea54C0gJANe5b9Vitk0UoAamswG9g3Ks2hqK3fTGfG2VTPLwHTK+BMUYF/pCCamHeRz46g1npRmIpT 4= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 06 Jun 2018 22:31:38 -0000 ----==_mimepart_5b1860c593c72_27ff2af9b2b9cf5423146a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks approved this pull request. LGTM -- 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/1423#pullrequestreview-126579441 ----==_mimepart_5b1860c593c72_27ff2af9b2b9cf5423146a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks approved this pull request.

LGTM

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

----==_mimepart_5b1860c593c72_27ff2af9b2b9cf5423146a-- From nobody Wed Jun 6 21:57:34 2018 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 9A7BC130E6A for ; Wed, 6 Jun 2018 21:57:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 X0xoP7xnmPlZ for ; Wed, 6 Jun 2018 21:57:29 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69CB0130E21 for ; Wed, 6 Jun 2018 21:57:29 -0700 (PDT) Date: Wed, 06 Jun 2018 21:57:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528347447; bh=l/yDEdo0941KfHPVhnkWCTf0xHzcGUAf31F/7ruIiks=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jysYnzRXmTLBOsy3GobtoySigCE89SE+tTVI6x5O/2H94K7IQo52Jmy8CZVloeHge /JehzbbQ0RNqeS+xmCVHZBkWcOVW5PRhOh9b+PRj8vGiA0BsS/MfT0scCVK0irLESs lS7hZUjTgXT78T1O/9nmcyDX1AToGa27crNhAcds= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18bb37a08ab_489c3f93c4dccf8412771a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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: Thu, 07 Jun 2018 04:57:32 -0000 ----==_mimepart_5b18bb37a08ab_489c3f93c4dccf8412771a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Don't you need to mark the packet level anyhow? In my implementation, I mark packet in the retransmission queue with their original encryption type, such as CI/0RTT/HS/1RTT. I need that to implement the acknowledgement checks (HS cannot ack 0RTT), and I use that to avoid spurious retransmission of 0RTT packet, pretty much the way you describe. -- 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/1413#issuecomment-395293026 ----==_mimepart_5b18bb37a08ab_489c3f93c4dccf8412771a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Don't you need to mark the packet level anyhow? In my implementation, = I mark packet in the retransmission queue with their original encryption = type, such as CI/0RTT/HS/1RTT. I need that to implement the acknowledgeme= nt checks (HS cannot ack 0RTT), and I use that to avoid spurious retransm= ission of 0RTT packet, pretty much the way you describe.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18bb37a08ab_489c3f93c4dccf8412771a-- From nobody Wed Jun 6 22:09:09 2018 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 BED88130DDA for ; Wed, 6 Jun 2018 22:09:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 3qvA6RBEq00i for ; Wed, 6 Jun 2018 22:09:04 -0700 (PDT) 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 6BCD812777C for ; Wed, 6 Jun 2018 22:09:04 -0700 (PDT) Date: Wed, 06 Jun 2018 22:09:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528348143; bh=0q2tC3ebPuZxWQGVfogigj1M4N83aOlqCc9M74BOuyo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OARhZ1r0LmbJxMxns6G6QYPamZ+bxk0GNB1fTyFN32wutRF1O4aqKPyo+JLaqS8mU bzl8ox+G4RX2xW3DhAAq3h4DxpYolbwEL0JlGJsxEcrIAZ2or+2KpNKWZkzebh5sjB 1bsZBLUxHi8woMqdFtvDNC7se6GwLzqmCN+N/3dM= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18bdefc9a34_4dbf2b116eca4f548728b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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: Thu, 07 Jun 2018 05:09:07 -0000 ----==_mimepart_5b18bdefc9a34_4dbf2b116eca4f548728b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think this discussion of duplicates illustrates a more fundamental issue with ECN: it is a signal from outside the encryption envelope that affects the behavior of the encrypted communication. In theory, all kinds of games are possible: adversarial ECN marking by an on-path device; copying of packets and reinjection with adversarial ECN markings by a man-on-the-side; copying of packets and reinjection with different IP headers and ports by an on-path device or a man on the side, possibly with the goal of messing up per-path ECN behavior. IMHO, the handling of ECN should be robust against these attacks, and the protection of ECN should not come from assumptions about how devices might or might not filter duplicate packets. -- 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/1405#issuecomment-395294672 ----==_mimepart_5b18bdefc9a34_4dbf2b116eca4f548728b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think this discussion of duplicates illustrates a more fundamental i= ssue with ECN: it is a signal from outside the encryption envelope that a= ffects the behavior of the encrypted communication. In theory, all kinds = of games are possible: adversarial ECN marking by an on-path device; copy= ing of packets and reinjection with adversarial ECN markings by a man-on-= the-side; copying of packets and reinjection with different IP headers an= d ports by an on-path device or a man on the side, possibly with the goal= of messing up per-path ECN behavior. IMHO, the handling of ECN should be= robust against these attacks, and the protection of ECN should not come = from assumptions about how devices might or might not filter duplicate pa= ckets.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18bdefc9a34_4dbf2b116eca4f548728b-- From nobody Wed Jun 6 22:11:08 2018 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 3EC0D130DDA for ; Wed, 6 Jun 2018 22:11:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 g8D3mLkb3LJO for ; Wed, 6 Jun 2018 22:11:03 -0700 (PDT) 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 5A36612777C for ; Wed, 6 Jun 2018 22:11:03 -0700 (PDT) Date: Wed, 06 Jun 2018 22:11:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528348262; bh=c62rkQ+BkRUU0oX+CVLXk2zeXg/nyxldc75k2WVJWMY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qphAdqmJnqaeOx8GeDldf+hbMHSjAwXpX4//thBSF/OQ1VI0VElxuAG3JWV1nNtkv Bz8uuLG7O7BS3Ik7vjmLji7u4rtsPvHV+nq/JYmrXlOtCR2uusTDKVPWZinbLHbI2B 7fDPZlPmjeImuo6D125SFoh4wl0kmlY4y965Rs9M= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18be668d0b9_2fb63ff101868f806801b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 07 Jun 2018 05:11:07 -0000 ----==_mimepart_5b18be668d0b9_2fb63ff101868f806801b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Could that be delaying loss detection for peers that do not buffer packets they do not understand? -- 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/1413#issuecomment-395294991 ----==_mimepart_5b18be668d0b9_2fb63ff101868f806801b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Could that be delaying loss detection for peers that do not buffer packets they do not understand?

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

----==_mimepart_5b18be668d0b9_2fb63ff101868f806801b-- From nobody Wed Jun 6 22:52:13 2018 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 8586B130E75 for ; Wed, 6 Jun 2018 22:52:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Lm1S-dG3SB-P for ; Wed, 6 Jun 2018 22:52:06 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0638E130E27 for ; Wed, 6 Jun 2018 22:52:06 -0700 (PDT) Date: Wed, 06 Jun 2018 22:52:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528350725; bh=h4G84EzB9GwIEfIVWhnwEPG8zIT32JZ4ouiPbCY4Brw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=G83Yl4dlLHhLM2Moxg02RE3TRPujI2oT1thDk214Evpm4qw2Z0y0kvXpJoitRaqqP eIp9F9zV16KaYy1lcuJMmex/4RWtXvpltoX92gXvu/0EG1qxV4iqz+SmvQ4K3bZdLz JHUrb5/WbEccU4Rm/w0ORux4yflmoSt48Jy3Ghc4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Duplicate detection (#1425) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18c8052393b_62c3fe7b557af80127193"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 05:52:09 -0000 ----==_mimepart_5b18c8052393b_62c3fe7b557af80127193 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We don't really lay out our expectations here. The protocol doesn't break in obvious ways if a duplicate packet is accepted, but things like ECN somewhat rely on duplicates being dropped. -- 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/1425 ----==_mimepart_5b18c8052393b_62c3fe7b557af80127193 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We don't really lay out our expectations here. The protocol doesn't break in obvious ways if a duplicate packet is accepted, but things like ECN somewhat rely on duplicates being dropped.

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

----==_mimepart_5b18c8052393b_62c3fe7b557af80127193-- From nobody Wed Jun 6 23:54:01 2018 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 645ED130E7E for ; Wed, 6 Jun 2018 23:53:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oBnrLS0gQTVs for ; Wed, 6 Jun 2018 23:53:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0297012777C for ; Wed, 6 Jun 2018 23:53:55 -0700 (PDT) Date: Wed, 06 Jun 2018 23:53:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528354434; bh=mRQ3h7YJJD1SxJ/2U9yP1djkAEabaKvpUQiL4G5DM84=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sC3/P9yKUKaEEECh6OFC/wycCGOtl01KpGaRELXb5U2pg4IyKtLWZmO2QFTBhe0iJ OLI4347L37h7KXzANAh2YdcxMXQkDC1TOwUcCbJ1bDOLQjaqZp9kxi9F929bSoYPTE fWa9Nr8JubSPQ0PHa0VOEl4u/sWirbXDrgcstalk= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18d682ee7c9_5033f91921f4f882368f1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 07 Jun 2018 06:53:59 -0000 ----==_mimepart_5b18d682ee7c9_5033f91921f4f882368f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, my implementation has encryption level as well and you need it somewhere in practice, but it's not documented in the recovery draft. @mikkelfj Can you clarify the exact concern about delaying loss detection? -- 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/1413#issuecomment-395313139 ----==_mimepart_5b18d682ee7c9_5033f91921f4f882368f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, my implementation has encryption level as well and you need it somewhere in practice, but it's not documented in the recovery draft.

@mikkelfj Can you clarify the exact concern about delaying loss detection?

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

----==_mimepart_5b18d682ee7c9_5033f91921f4f882368f1-- From nobody Wed Jun 6 23:58:02 2018 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 109BC130E7E for ; Wed, 6 Jun 2018 23:57:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gxOdZc5IA1G0 for ; Wed, 6 Jun 2018 23:57:56 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8969130E80 for ; Wed, 6 Jun 2018 23:57:55 -0700 (PDT) Date: Wed, 06 Jun 2018 23:57:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528354674; bh=1p6QgNPMVEHN0YaYfUt1CIFJZeEkjkbh7oeXsL3qFOs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IzltkRxAdYy2brpiIv32GzFQE5Af3vIPgQVQO2cgaIKuEeHGhSU9bXPdvqP+SX+Jv ipYPyPPtCSxzaSMf8XG+zq508/8wwdHRb8NMRGQnf7Fe3BLUC++ckpt8yIjxgDMjQ9 Wx07MSytbbQS2UmAHHiBbWFiiWIGDphVNLjBkgTs= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18d772e4cba_2a912ac6d90e0f543756f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 07 Jun 2018 06:58:00 -0000 ----==_mimepart_5b18d772e4cba_2a912ac6d90e0f543756f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett My concern was mostly a question because I don't have the full overview, but the concern is for example that a server will not retransmit 1-RTT data for several roundtrips while it is waiting for client finished while the client is a small IoT device with limited buffering so it drops anything it cannot consume. I'm not stating this would be a problem, merely asking. -- 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/1413#issuecomment-395314047 ----==_mimepart_5b18d772e4cba_2a912ac6d90e0f543756f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett My concern was mostly = a question because I don't have the full overview, but the concern is for= example that a server will not retransmit 1-RTT data for several roundtr= ips while it is waiting for client finished while the client is a small I= oT device with limited buffering so it drops anything it cannot consume. = I'm not stating this would be a problem, merely asking.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18d772e4cba_2a912ac6d90e0f543756f6-- From nobody Thu Jun 7 00:14:31 2018 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 41386130E8C for ; Thu, 7 Jun 2018 00:14:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 ExvoN161Jd0I for ; Thu, 7 Jun 2018 00:14:24 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 4B6AB130E7E for ; Thu, 7 Jun 2018 00:14:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528355663; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=JmrXsQXpKdzxiu7K4vxwM/uqtv0ChsgQgHXL+5d4x+s=; b=m0WwHUeNOaL2N2vtMI88Dm4L+sObu7JhfVvYVXoMcq8tf9SQH7ujcuxU1X+/K6BvUgUJJwXV 9YQUPVj+BAQHUVy1S5uvr5FZH3PyI1Sh+KYgbvbKtGPuqOrBgUfFTzxubkmqY15hBltuNuer h5S8qxFyPF95j7eaKbAtJ35d+Iw= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b18db4e.7f1cb43322d0-smtp-out-n02; Thu, 07 Jun 2018 07:14:22 -0000 (UTC) Date: Thu, 07 Jun 2018 00:14:22 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b18db4e742_6b912aee6fd67bfc24990@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 285884: Add files via upload Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18db4e429_6b912aee6fd67bfc248f0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 07 Jun 2018 07:14:28 -0000 ----==_mimepart_5b18db4e429_6b912aee6fd67bfc248f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 285884080d4b7469485eb347be1e45a9083ea60d https://github.com/quicwg/wg-materials/commit/285884080d4b7469485eb347be1e45a9083ea60d Author: Lars Eggert Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: A interim-18-06/mvfst.pdf Log Message: ----------- Add files via upload **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18db4e429_6b912aee6fd67bfc248f0-- From nobody Thu Jun 7 00:35:55 2018 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 B1AD3130E9A for ; Thu, 7 Jun 2018 00:35:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rwOM_4SgafdV for ; Thu, 7 Jun 2018 00:35:47 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66103130E91 for ; Thu, 7 Jun 2018 00:35:47 -0700 (PDT) Date: Thu, 07 Jun 2018 00:35:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528356946; bh=sbZN6AoAVGXTsn3i4nmznDU7OwfPbErZWU6KbTazM4U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lhE5ZYnPB8PfbDB8ffPUB2guBncIsQN3ujmNZk1xs+tFh4ku04UFFPfbrAN2rEuZ1 QLoFzPGQI5j1mMkhtlcR0mYebkAkKgERODilxvRYBcm68kGKcV9P9swlbQBEvy4Vij 8DiG01EQorfSGbr3i8jel6kfjovTPIAPmg5ioQCc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate detection (#1425) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18e05282175_68d13fe1f0ad6f801658d5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 07:35:52 -0000 ----==_mimepart_5b18e05282175_68d13fe1f0ad6f801658d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dupe: #1405. -- 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/1425#issuecomment-395322889 ----==_mimepart_5b18e05282175_68d13fe1f0ad6f801658d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Dupe: #1405.

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

----==_mimepart_5b18e05282175_68d13fe1f0ad6f801658d5-- From nobody Thu Jun 7 00:36:03 2018 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 F2D6E130EA4 for ; Thu, 7 Jun 2018 00:35:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rEJWZiZE6Lsf for ; Thu, 7 Jun 2018 00:35:47 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86478130E94 for ; Thu, 7 Jun 2018 00:35:47 -0700 (PDT) Date: Thu, 07 Jun 2018 00:35:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528356946; bh=btFJ9Iwi2cVNqNtyC37xOeIZoi9XroRHTRkOYCEDSHQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QUN8ofeLGH0FyuKi/Pf8nZukLRL1y99ZTAkoytvTe9o0umtAuRpgRlVjAqu4kcRYo dObERJq38PXJOKJ/fY/Ww8IJZz/wY1qXMXnrWQBVSfwfLDdD4LfvYRCNYKlhAmJ9ao H9LufxDkaeX4oDON08lqhZFMAb1V6p9Sjp4RtPXw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate detection (#1425) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18e0528f872_8e93fe14b38cf7c191394"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 07:35:52 -0000 ----==_mimepart_5b18e0528f872_8e93fe14b38cf7c191394 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1425. -- 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/1425#event-1667840362 ----==_mimepart_5b18e0528f872_8e93fe14b38cf7c191394 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1425.

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

----==_mimepart_5b18e0528f872_8e93fe14b38cf7c191394-- From nobody Thu Jun 7 01:15:41 2018 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 3CA35130E8F for ; Thu, 7 Jun 2018 01:15:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7mkQYqeQNDad for ; Thu, 7 Jun 2018 01:15:36 -0700 (PDT) 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 7B33E12F18C for ; Thu, 7 Jun 2018 01:15:36 -0700 (PDT) Date: Thu, 07 Jun 2018 01:15:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528359334; bh=1l6GxDJzuNgyQK84TVla8wMCIXOdppI7qhklbQUfp8k=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=daZpSUfuvMG0YC9sUHNwzQTQ5lT0m7eVMs/DM9AWEjdLVOsITlSL40A8rsrob/qTR EGhfRwlyBkJigW2KpTPeolDCRvXgwPPwqLYFk91EfgKM+3+LhyPOsm1Loy0qKoMqhE +mQyqkfWXI9AeE+bzTxLKXreJFur4FR8Co2WjVoA= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Detect adversarial ECN reporting (#1426) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18e9a697a5e_12ce3fe14b38cf7c3687c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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: Thu, 07 Jun 2018 08:15:40 -0000 ----==_mimepart_5b18e9a697a5e_12ce3fe14b38cf7c3687c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In the ECN proposal, the sender relies on the recipient to send back an honest count of ECN marks. A client who wants the sender to overshoot the network capacity will be able to just avoid reporting the "congestion experienced" marks, pretending that there never is congestion. This is similar to the "optimistic ack" problem that is mitigated by leaving holes in the sequence of packet numbers. If a bad client acks a hole, the sender notices it and can terminate the connection. We should consider a similar mechanism for ECN. The sender normally marks packets as ECT(0) or ECT(1). It could also at some random intervals mark a packet as "CE", and then verify that the CE is reflected in the counters sent by the recipient. The downside is that the sender-set CE may "mask" a congestion in the network. But if only a small fraction of the packets are used for this probing mechanism, it should not be too much of a problem. -- 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/1426 ----==_mimepart_5b18e9a697a5e_12ce3fe14b38cf7c3687c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In the ECN proposal, the sender relies on the recipient to send back an honest count of ECN marks. A client who wants the sender to overshoot the network capacity will be able to just avoid reporting the "congestion experienced" marks, pretending that there never is congestion.

This is similar to the "optimistic ack" problem that is mitigated by leaving holes in the sequence of packet numbers. If a bad client acks a hole, the sender notices it and can terminate the connection.

We should consider a similar mechanism for ECN. The sender normally marks packets as ECT(0) or ECT(1). It could also at some random intervals mark a packet as "CE", and then verify that the CE is reflected in the counters sent by the recipient.

The downside is that the sender-set CE may "mask" a congestion in the network. But if only a small fraction of the packets are used for this probing mechanism, it should not be too much of a problem.

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

----==_mimepart_5b18e9a697a5e_12ce3fe14b38cf7c3687c5-- From nobody Thu Jun 7 01:21:24 2018 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 2C005130E91 for ; Thu, 7 Jun 2018 01:21:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nFrtsMyh39ZU for ; Thu, 7 Jun 2018 01:21:17 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA7912F18C for ; Thu, 7 Jun 2018 01:21:17 -0700 (PDT) Date: Thu, 07 Jun 2018 01:21:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528359676; bh=2ggeJ3jGRjtC1rGdh00xJa8ESMmvZvgfOUHhs/pcoPY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m5/SEQyxd/P7CVV70ACF3F60TTP08Ym6IiBcWNSYbsMP7L5to8sf6kpOqQsDjfHa+ uL8/zHQIGfBzBUmfinDeYul2YEygQEKDSnpSV61NZNKj7GFGx1WDxhrZI+biKWt6vF bq9YTB83XcyFaMgT33SesE2+uoR0X0BIHuGSlzJg= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18eafcdbe7f_5a0b2af61939af5035969b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 07 Jun 2018 08:21:21 -0000 ----==_mimepart_5b18eafcdbe7f_5a0b2af61939af5035969b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, a server would not retransmit 1RTT data until the peer had the keys the ACK them. As you said, a peer may drop packets it can't immediately process, so I don't know of a way to improve upon this case. -- 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/1413#issuecomment-395335198 ----==_mimepart_5b18eafcdbe7f_5a0b2af61939af5035969b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, a server would not retransmit 1RTT data until the peer had the keys the ACK them. As you said, a peer may drop packets it can't immediately process, so I don't know of a way to improve upon this case.

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

----==_mimepart_5b18eafcdbe7f_5a0b2af61939af5035969b-- From nobody Thu Jun 7 01:23:46 2018 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 701D7130E93 for ; Thu, 7 Jun 2018 01:23:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Wr85ypPnEiD5 for ; Thu, 7 Jun 2018 01:23:40 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4910412F18C for ; Thu, 7 Jun 2018 01:23:40 -0700 (PDT) Date: Thu, 07 Jun 2018 01:23:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528359819; bh=1FHI8lSoWI3uCv/QRbgWnACNjCfeERsfLRITs3jWbAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BsNc8J/fuH1AbtxGGZVW1QUHE/x9zDzwMZFTL+vulxSyOL+X4/iVDQY1ZwOE5O4c6 LH/1FVfbYruH9GieXwDS8jfTeMDUmTvb+oqTfskp2TcWMWk49bUalV1h4YxS92H2uY TU+DsQjxDRxK2LTHBLDbISK5dO2cJRkjIFYuc3ws= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Detect adversarial ECN reporting (#1426) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18eb8bc2aa5_40de2ab25d326f6034083f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair 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.26 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: Thu, 07 Jun 2018 08:23:43 -0000 ----==_mimepart_5b18eb8bc2aa5_40de2ab25d326f6034083f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is not a unique issue to QUIC! = Setting ECN-CE is something I routinely do in ECN measurement work and we= have talked about adding this to TCP, and it's mentioned in TSVWG docs -= To do it with TCP requires accurate ECN feedback - which is similar to w= hat is being proposed by the DT for QUIC - so this should be OK. A sender should not set CE often (if they are going to ignore markings), = but as an infrequent probe I think it has useful properties=E2=80=A6 If i= t masks one CE mark every now and again, it's not a big deal - if the con= gestion marking rate is really that low, it is OK - if the sender sees ot= her CE marks it knows to react. Since this is a generic ECN comment, I'd = encourage discussion within TSVWG - where you may also attract more feedb= ack from people with understanding of ECN. -- = 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/1426#issuecomment-395335864= ----==_mimepart_5b18eb8bc2aa5_40de2ab25d326f6034083f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This is not a unique issue to QUIC!

Setting ECN-CE is something I routinely do in ECN measurement work and= we have talked about adding this to TCP, and it's mentioned in TSVWG doc= s - To do it with TCP requires accurate ECN feedback - which is similar t= o what is being proposed by the DT for QUIC - so this should be OK.

A sender should not set CE often (if they are going to ignore markings= ), but as an infrequent probe I think it has useful properties=E2=80=A6 I= f it masks one CE mark every now and again, it's not a big deal - if the = congestion marking rate is really that low, it is OK - if the sender sees= other CE marks it knows to react. Since this is a generic ECN comment, I= 'd encourage discussion within TSVWG - where you may also attract more fe= edback from people with understanding of ECN.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18eb8bc2aa5_40de2ab25d326f6034083f-- From nobody Thu Jun 7 01:24:08 2018 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 87A23130E93 for ; Thu, 7 Jun 2018 01:24:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 CvWq-00U0GrQ for ; Thu, 7 Jun 2018 01:24:03 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 24E6E12F18C for ; Thu, 7 Jun 2018 01:24:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528359842; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=uyRZDo5PheVEVGOFQQHCWf8h2lIy6uvAy96YnFVCEUc=; b=iOx/lEGDFEOlPbjAs06gR+b8CTXJ+Te9ISrzv4rjVrw2JsKAQBaUqSBUorf1+f5/be1zNWYk SHqNsm7s92O+RmwQvLC6Zhe0uHS7S41h/Elk2ZSnKr0ZyJePyBq/blh2c3KTTSmDnE+xeWiP hx07iUWECg5EnnFWq6jlcj5KPJE= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b18eba1.7f0ec7962c30-smtp-out-n01; Thu, 07 Jun 2018 08:24:01 -0000 (UTC) Date: Thu, 07 Jun 2018 01:24:01 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b18eba147768_4b0c2afc9c8b1c086105c@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 96493c: Move Draft Version Identification section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18eba14711f_4b0c2afc9c8b1c08609d1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 07 Jun 2018 08:24:05 -0000 ----==_mimepart_5b18eba14711f_4b0c2afc9c8b1c08609d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/move_draft_id Home: https://github.com/quicwg/base-drafts Commit: 96493c3fad881bfab72893d081ffa29a0303143e https://github.com/quicwg/base-drafts/commit/96493c3fad881bfab72893d081ffa29a0303143e Author: Mike Bishop Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Move Draft Version Identification section Fixes #1415 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18eba14711f_4b0c2afc9c8b1c08609d1-- From nobody Thu Jun 7 01:24:52 2018 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 D71F912F18C for ; Thu, 7 Jun 2018 01:24:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JRI2249on1-p for ; Thu, 7 Jun 2018 01:24:46 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C798B130E93 for ; Thu, 7 Jun 2018 01:24:46 -0700 (PDT) Date: Thu, 07 Jun 2018 01:24:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528359886; bh=DOchOOG1oozCReVDHCf8GZc2m/W2+T6l7JdGajco5pA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZPLi8T19Z+WF0qiYCrWieWfhGcyZWIRPX8M8tJHVRK+HTzEQTPPBzU7bf9MvpLk5u E/D0bU+d+FCsoaS/sFhCpSB79y/ui0yeTmQUuSIJzjML9QoFEVKvorKQlFg5WYe9Vn D8zWBzRTOIV/aeSVp4PQcF445H3yi9if4g462dPU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Move Draft Version Identification section (#1427) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18ebce20bd7_5fe12b1c8c174f5c4914c3"; 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.26 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: Thu, 07 Jun 2018 08:24:49 -0000 ----==_mimepart_5b18ebce20bd7_5fe12b1c8c174f5c4914c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1415 You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1427 -- Commit Summary -- * Move Draft Version Identification section -- File Changes -- M draft-ietf-quic-http.md (43) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1427.patch https://github.com/quicwg/base-drafts/pull/1427.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/1427 ----==_mimepart_5b18ebce20bd7_5fe12b1c8c174f5c4914c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1415

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

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

Commit Summary

  • Move Draft Version Identification section

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 mute the thread.

----==_mimepart_5b18ebce20bd7_5fe12b1c8c174f5c4914c3-- From nobody Thu Jun 7 01:27:16 2018 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 4A3DC130E96 for ; Thu, 7 Jun 2018 01:27:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 OhT7WEQaoLDC for ; Thu, 7 Jun 2018 01:27:11 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 979BC12F18C for ; Thu, 7 Jun 2018 01:27:11 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528360030; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=XQq5pJJXoHuJH0uIYZOZwUObgKQQFp1WVxsG1ek0iYA=; b=vWviWKR4Q9N1WZ8BkjJvKomr9DXRdhM8ZcfmJKVH7xb80KAaWXUk7r+QDZFMn3j6CfWdEt4A OrcCr+Jv1lh9Ucc13pgQMcqmhgMD00GWRlsNOovhe/d99CaVsjwj6272/u2fZKL6fL3IOyMJ buoGzJmkbZLf1LjdIEPvZWApTS0= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b18ec5e.7f5e2e1067b0-smtp-out-n01; Thu, 07 Jun 2018 08:27:10 -0000 (UTC) Date: Thu, 07 Jun 2018 01:27:10 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b18ec5e75ca6_4f7f2b282058fc14219bb@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 3a154b: HTTP/QUIC specific, not HTTP-specific Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b18ec5e75840_4f7f2b282058fc14218f9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 07 Jun 2018 08:27:14 -0000 ----==_mimepart_5b18ec5e75840_4f7f2b282058fc14218f9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 3a154be781a6a51cd1335fba345bb4a9f35fe2dc https://github.com/quicwg/base-drafts/commit/3a154be781a6a51cd1335fba345bb4a9f35fe2dc Author: Mike Bishop Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- HTTP/QUIC specific, not HTTP-specific Fixes #1416 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b18ec5e75840_4f7f2b282058fc14218f9-- From nobody Thu Jun 7 01:27:22 2018 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 48F9812F18C for ; Thu, 7 Jun 2018 01:27:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 i8HtfxCSBrhx for ; Thu, 7 Jun 2018 01:27:18 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C43A130E97 for ; Thu, 7 Jun 2018 01:27:18 -0700 (PDT) Date: Thu, 07 Jun 2018 01:27:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528360037; bh=HEL51l1xk3R3uPEEy4UGGGw+lv3rNo7j7+1MpJSPSOo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rdlFsej2XOHIN6YArwkygOpZH4qbV6j7kfcU+nafoSYuR5+Oq4fXY27jdg0o2D7sD R70j9Ey8PzbidXNGXkBgjmTj2UciREVxsQasvFIJaAjuVmV7RKWveAQUQk/7YWS+1d G0n4XcKzWKiSpTSYZOuOoXOOzsMNSwkPWDqwq0UQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: are SETTINGS HTTP/QUIC specific? (#1416) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18ec65989d4_48a3f8150a3cf80376364"; 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.26 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: Thu, 07 Jun 2018 08:27:21 -0000 ----==_mimepart_5b18ec65989d4_48a3f8150a3cf80376364 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1416 via 3a154be781a6a51cd1335fba345bb4a9f35fe2dc. -- 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/1416#event-1667938456 ----==_mimepart_5b18ec65989d4_48a3f8150a3cf80376364 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1416 via 3a154be.

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

----==_mimepart_5b18ec65989d4_48a3f8150a3cf80376364-- From nobody Thu Jun 7 01:28:29 2018 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 4AB21130E96 for ; Thu, 7 Jun 2018 01:28:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jZXE2WVMLq55 for ; Thu, 7 Jun 2018 01:28:23 -0700 (PDT) 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 A8ABE130E97 for ; Thu, 7 Jun 2018 01:28:23 -0700 (PDT) Date: Thu, 07 Jun 2018 01:28:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528360102; bh=D9lbttgaxoJzs4WlGt4qC+QdxMmsjLqlZLupp+wIr0s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GF5t0Z0G3oBJ2UqPy3/vreA+i8rbzlCFIWDH2rt26YbcuCZqTwncdTD/Imu73rdnc PT/aL6wwjBadJ5+yKkcuFZ6LAIfjWeyJXms5wot6vOYN9/WlGEBw8wa0lZ5vBFXNzr MBPyZTaRH8VKKrGlwBuo8fFnUrO4vcnU9FNEMuCk= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP header compression: static table fit for QUIC (#904) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18eca6e27f6_6e543f827f1e2f80420357"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 07 Jun 2018 08:28:27 -0000 ----==_mimepart_5b18eca6e27f6_6e543f827f1e2f80420357 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista. Mark recommended pruning the static table down to ~62 entries, biased towards request headers and against unregistered headers. It's also been mentioned we should be sure to include headers which are not common now but may be more common in the future (DoH, Alt-Svc, Early-Data, etc). -- 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/904#issuecomment-395337267 ----==_mimepart_5b18eca6e27f6_6e543f827f1e2f80420357 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Discussed in Kista. Mark recommended pruning the static table down to= ~62 entries, biased towards request headers and against unregistered hea= ders.

It's also been mentioned we should be sure to include headers which ar= e not common now but may be more common in the future (DoH, Alt-Svc, Earl= y-Data, etc).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b18eca6e27f6_6e543f827f1e2f80420357-- From nobody Thu Jun 7 01:29:10 2018 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 C56B7130E96 for ; Thu, 7 Jun 2018 01:29:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jj5t_XJybGiv for ; Thu, 7 Jun 2018 01:29:03 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF82412F18C for ; Thu, 7 Jun 2018 01:29:03 -0700 (PDT) Date: Thu, 07 Jun 2018 01:29:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528360143; bh=9cQ9RIXkBMxS8bHodBKXWW1g+eSjfrQAHi4aPEKCpwI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z9aADfn1K8YLuiND3D1Zdhe22mGqwvIlg0M1YviXyA9n5ivejvD/jNKhkvQrh5vA7 lfdXyVffWMmDr/7pW27jZitVGuSdjyDr1CKIoIUgaq/UJR38QpsxCxBMRSN+nH43vo gHH5Qh1vTRs2Qkn3tQrQZOaVnFfhYW5eQA4OdZGc= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Static table negotiation (#1343) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18eccf20a52_8e93fe14b38cf7c433277"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 07 Jun 2018 08:29:06 -0000 ----==_mimepart_5b18eccf20a52_8e93fe14b38cf7c433277 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista. Recommendation is to pick a single table for v1 and revisit this in v2 -- 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/1343#issuecomment-395337470 ----==_mimepart_5b18eccf20a52_8e93fe14b38cf7c433277 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Discussed in Kista. Recommendation is to pick a single table for v1 and revisit this in v2

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

----==_mimepart_5b18eccf20a52_8e93fe14b38cf7c433277-- From nobody Thu Jun 7 01:30:29 2018 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 762BE130E97 for ; Thu, 7 Jun 2018 01:30:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 p21XKZD427US for ; Thu, 7 Jun 2018 01:30:21 -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 B29BC12F18C for ; Thu, 7 Jun 2018 01:30:21 -0700 (PDT) Date: Thu, 07 Jun 2018 01:30:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528360221; bh=s3ju5e0/yW1kqcWCbip3MPtpzcIT/VAaS8eRADIsNbc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1YzQEmsxFo9ESQRASGHMYPNSajw/LR9YcF/BqfeTxatME4py6MJKygCYpCagewBgK NtaXsVVhk+Weu047GMKi6W1iMBhNDRcGwx+aEDsV8BNqECyGpXtyQojQXBFkjGs20V 9ITjZM9yypkGgPGlH6nw430sho2qG1J4VdGQgcUw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18ed1d16e11_26192af61939af503515da"; 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.26 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: Thu, 07 Jun 2018 08:30:27 -0000 ----==_mimepart_5b18ed1d16e11_26192af61939af503515da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Saying that Stream IDs should be used sequentially feels a little odd, since the application doesn't actually have control on the Stream IDs themselves. I'm having trouble coming up with a better wording; perhaps when I'm back on my own time zone. ;-) Suggestions welcome. -- 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/1417#issuecomment-395337879 ----==_mimepart_5b18ed1d16e11_26192af61939af503515da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Saying that Stream IDs should be used sequentially feels a little odd,= since the application doesn't actually have control on the Stream IDs th= emselves. I'm having trouble coming up with a better wording; perhaps wh= en I'm back on my own time zone. ;-)

Suggestions welcome.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18ed1d16e11_26192af61939af503515da-- From nobody Thu Jun 7 01:31:54 2018 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 AC487130E97 for ; Thu, 7 Jun 2018 01:31:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hGI7Wy6WBDlu for ; Thu, 7 Jun 2018 01:31:49 -0700 (PDT) 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 0618612F18C for ; Thu, 7 Jun 2018 01:31:49 -0700 (PDT) Date: Thu, 07 Jun 2018 01:31:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528360308; bh=uRLYxa4fCioIRN3VpKMdjd2XaEhIDXydT8xsKTArwf8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Yje6+X7DQAVjX2nMcRgIm9eiIYJkhcD8eu/K84QVhI8kfPJmhg+PcUK1nHT271lvc 9GjSHTR31oET2cv2dXAsobcmQGsGr2hi9V6TLa2ykDu/k/ZDIUdV04hkgJMVKPsfuK ugkftQZGhRRSRK/toTpTjtO06k0ehUdz94uK+cLI= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18ed7454874_10f42ad231bc6f50577432"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 07 Jun 2018 08:31:52 -0000 ----==_mimepart_5b18ed7454874_10f42ad231bc6f50577432 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista. Because the problem exists for eviction races as well, and those stream level errors MAY be promoted to a connection level error at the decoder's discretion, we need to have application level acks for reset streams, which will solve both problems. If there is strong sentiment to replace MAX_BLOCKED_STREAMS with a boolean, please open a separate issue. -- 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/1371#issuecomment-395338310 ----==_mimepart_5b18ed7454874_10f42ad231bc6f50577432 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Discussed in Kista. Because the problem exists for eviction races as = well, and those stream level errors MAY be promoted to a connection level= error at the decoder's discretion, we need to have application level ack= s for reset streams, which will solve both problems. If there is strong = sentiment to replace MAX_BLOCKED_STREAMS with a boolean, please open a se= parate issue.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b18ed7454874_10f42ad231bc6f50577432-- From nobody Thu Jun 7 01:47:23 2018 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 9BB21130EAB for ; Thu, 7 Jun 2018 01:47:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 qppnAIrLcMNY for ; Thu, 7 Jun 2018 01:47:18 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04FFC130EAA for ; Thu, 7 Jun 2018 01:47:16 -0700 (PDT) Date: Thu, 07 Jun 2018 01:47:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528361235; bh=7NGhML3DO2NEBNW2CmBK8N7NcbJd9tuuV75vxjIVH/s=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=f22w5DDlTFbBh/gfKFgEC9FLHQU2BY82PNHQSebHfeeUdPdHgeVzjS6ewbMTpd9Os pQtX5MoVLwdjehVHkfJ5NR9Ks3MSpol+M4lp+YuPjNMr4K2BDhPPcM+uRE+H1eMq0k JjHkDUVnfk1JaJiAyGRb8lqn2KeRx5fN1UE7skFw= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18f113a162f_1df8d3fe5ee6f8f88611840"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 07 Jun 2018 08:47:21 -0000 ----==_mimepart_5b18f113a162f_1df8d3fe5ee6f8f88611840 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We should recommend acking every 2 packets or something similar when the sender is using Reno or another window based congestion control like Cubic. Other congestion controllers like BBR are able to tolerate less frequent acking, but those controllers are not standardized and quite a bit more complex. This makes me a bit sad, since I like acking less frequently, but the recovery doc should be self-consistent. -- 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/1428 ----==_mimepart_5b18f113a162f_1df8d3fe5ee6f8f88611840 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We should recommend acking every 2 packets or something similar when the sender is using Reno or another window based congestion control like Cubic.

Other congestion controllers like BBR are able to tolerate less frequent acking, but those controllers are not standardized and quite a bit more complex.

This makes me a bit sad, since I like acking less frequently, but the recovery doc should be self-consistent.

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

----==_mimepart_5b18f113a162f_1df8d3fe5ee6f8f88611840-- From nobody Thu Jun 7 02:26:24 2018 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 227E81310CD for ; Thu, 7 Jun 2018 02:26:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 LH4dxZpgGFAR for ; Thu, 7 Jun 2018 02:26:14 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15229130EBE for ; Thu, 7 Jun 2018 02:26:14 -0700 (PDT) Date: Thu, 07 Jun 2018 02:26:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528363572; bh=P2QZmOdiCRgIyxI7P4qNui/HMl9MPwjMI0kx/pQ7UTY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RFqWolyUgyABAd4YBlicnXUnsQeKjx8a2JSJHPqfbXtQPtG+QkcwRdcjv4jPzfuSk 3+GXtyTn0stCdrL94An983Mq1z0IoXOevQ8a9MHH208TQ3Rfn/boi1AneVe62+D7h8 CqxP76qRzrlz0JmwQS1KVIXqs5KJOr+DGQyv+njc= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP header compression: static table fit for QUIC (#904) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18fa34ecbfe_f3e2ade5dc38f5013195d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 09:26:20 -0000 ----==_mimepart_5b18fa34ecbfe_f3e2ade5dc38f5013195d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > It's also been mentioned we should be sure to include headers which are not common now but may be more common in the future (DoH, Alt-Svc, Early-Data, etc). I'm not familiar with all of these, which are request headers? I still think there will be issues of trying to define Alt-Svc with a value. -- 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/904#issuecomment-395354827 ----==_mimepart_5b18fa34ecbfe_f3e2ade5dc38f5013195d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's also been mentioned we should be sure to include headers which ar= e not common now but may be more common in the future (DoH, Alt-Svc, Earl= y-Data, etc).

I'm not familiar with all of these, which are request headers?

I still think there will be issues of trying to define Alt-Svc with a = value.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b18fa34ecbfe_f3e2ade5dc38f5013195d-- From nobody Thu Jun 7 02:29:36 2018 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 982B3130EBE for ; Thu, 7 Jun 2018 02:29:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 91NiszJnRFiM for ; Thu, 7 Jun 2018 02:29:32 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 27030130E86 for ; Thu, 7 Jun 2018 02:29:32 -0700 (PDT) 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=K27axc7dRZ+yZF3Zn9stjCQF2Pg=; b=Vy/ioqnptv4S5+N1 QdEJkOA2MbkiAUaNHNzHBC0B/yh37ruqHLYvc8b2J+b/v1rkOnr2xgQ5C2HMehzN zpDhNxxqe7s5aFil0TYZW50tM4ckX1HbL504XVKdJOS9uXXNTy90mV+4Jfnx+3PV WW7cZ2AhqVWndhiIize7Y3TJkXE= Received: by filter1756p1mdw1.sendgrid.net with SMTP id filter1756p1mdw1-12885-5B18FAFA-10 2018-06-07 09:29:30.876157696 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id M3RT753AQ6C1ofSg2YILJg for ; Thu, 07 Jun 2018 09:29:30.858 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id CFA343E1A43 for ; Thu, 7 Jun 2018 02:29:30 -0700 (PDT) Date: Thu, 07 Jun 2018 09:29:31 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b18fafacd7fc_304b2ab23b63cf50121542"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3a65OGQfthxNRnF0eomzBUTBOYAjnG0pBBkd 8+xVMuJJTJFqGUNgni7EujY5/Z+3K6AhHwuhVzAOsde/49CTw48pLcMxTSjFZSFzInBpLzgDGsdpRX oe5TRWb/83W7sMZC3abq0oyb/dUlLec3sbSzVG5S1wLcnGhJTEYcjQKVNyvkQWzB6n48qFS4Arrv3o w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 09:29:35 -0000 ----==_mimepart_5b18fafacd7fc_304b2ab23b63cf50121542 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 3 commits. 0f94847 Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn 0e7d43b Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn 822aded Changed so that additional ECN-CE marks are sent in immediate ACKs to avoid unclarity in regards to CE marks and receovery period. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/0bb5bad97e1d13094463938fcefaa8917f23ffb6..822aded3768e1a1a49a8e9632fe9cc96cbd8fe00 ----==_mimepart_5b18fafacd7fc_304b2ab23b63cf50121542 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 3 commits.

  • 0f94847 Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • 0e7d43b Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • 822aded Changed so that additional ECN-CE marks are sent in immediate ACKs to avoid unclarity in regards to CE marks and receovery period.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b18fafacd7fc_304b2ab23b63cf50121542-- From nobody Thu Jun 7 03:13:47 2018 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 0584C130ECE for ; Thu, 7 Jun 2018 03:13:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 wrH0QorJrWzt for ; Thu, 7 Jun 2018 03:13:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6FF130DFF for ; Thu, 7 Jun 2018 03:13:41 -0700 (PDT) Date: Thu, 07 Jun 2018 03:13:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528366421; bh=aw/G2YvKFn5Hks2CemMCm4NHeJHDmEVGvfnD/frsSKg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LmtbPfH4F6uj8qphK2c5bikxQKbxaGlQlgRFC0idAmovf3gh/yv1J7/ZgeUXP7N0y lhAbbrVkA3LUhJy5vDhZ8bVtsDsWtlYmJwD5yzVQWa4vlnB2yBtV62UGyEiSi7NFKn inwP/1dBHzmmXRUqcwTWyZ5pXW5a2virC79I1ZmM= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b190555e3bf_6b872aeddcb20f589188"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 07 Jun 2018 10:13:44 -0000 ----==_mimepart_5b190555e3bf_6b872aeddcb20f589188 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 345f593 Fixed lint issues -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/822aded3768e1a1a49a8e9632fe9cc96cbd8fe00..345f593a92e4455989ada8ff7029e3935f5696d8 ----==_mimepart_5b190555e3bf_6b872aeddcb20f589188 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b190555e3bf_6b872aeddcb20f589188-- From nobody Thu Jun 7 06:23:58 2018 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 AB154130EF5 for ; Thu, 7 Jun 2018 06:23:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 B6_PU9pPMm6B for ; Thu, 7 Jun 2018 06:23:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CE37130EEE for ; Thu, 7 Jun 2018 06:23:51 -0700 (PDT) Date: Thu, 07 Jun 2018 06:23:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528377830; bh=qZ3EodWxR+dWGbrnQl1RoLq5PPpdl5Zz8Yd2QznFPVg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=G24by5Tcme+nuBaoP/B7NtQ8/wNrM2sIZZeZW34AxVL/sycEsne/1UAtFmLlx4/KN VizbjI7YH6S0Wroxj4jzfrmIx1Ebe8oED4WLUi101pjb+LPDo4aVMorq+vYY96xedN 7e9HAP38e8Nj4sklUsX8dhhZW0qm4RQMfwAO6N9s= From: Subodh Iyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1931e63debc_46c42b2177d4af587733b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: siyengar 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.26 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: Thu, 07 Jun 2018 13:23:57 -0000 ----==_mimepart_5b1931e63debc_46c42b2177d4af587733b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit When RTO timer is active, idle timeout only fires when idle timeout goes over RTO. This is because we specify that idle timeout is reset whenever a packet is sent or received. RTO will trigger packet transmission. We should do something better about this. -- 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/1429 ----==_mimepart_5b1931e63debc_46c42b2177d4af587733b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

When RTO timer is active, idle timeout only fires when idle timeout goes over RTO. This is because we specify that idle timeout is reset whenever a packet is sent or received. RTO will trigger packet transmission. We should do something better about this.

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

----==_mimepart_5b1931e63debc_46c42b2177d4af587733b1-- From nobody Thu Jun 7 06:40:12 2018 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 EC5841310CD for ; Thu, 7 Jun 2018 06:40:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zmXM8iHZm6M6 for ; Thu, 7 Jun 2018 06:40:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E069E1310CC for ; Thu, 7 Jun 2018 06:40:06 -0700 (PDT) Date: Thu, 07 Jun 2018 06:40:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528378805; bh=OZ0GnbGzYywUh7Iwh2CWao+DnI9UhFkuxi2zUcH2oLw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lYnCMB3f/zzC6rL+Np9rSIkD0OvLekt6AK2V2UuodZxNd/sDd67obzgNG0Ykaj5KG OQ0e4uwM2aQjzrguVP1OqjcN2KT9KUnKqUgJ115z33fqXDdPWQ23RNJNEEnYjlX+Ij +08E6iFLn64yxjKZYZoudnkQEELcDSHk0i7IrZz8= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1935b5dd050_7a183f86b0834f84590564"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Thu, 07 Jun 2018 13:40:10 -0000 ----==_mimepart_5b1935b5dd050_7a183f86b0834f84590564 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If RTO is active that means you are actively trying to send something, and therefore, in my mind, means you are not idle. I'd never expect the idle timeout to fire while in this state. -- 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/1429#issuecomment-395423804 ----==_mimepart_5b1935b5dd050_7a183f86b0834f84590564 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If RTO is active that means you are actively trying to send something, and therefore, in my mind, means you are not idle. I'd never expect the idle timeout to fire while in this state.

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

----==_mimepart_5b1935b5dd050_7a183f86b0834f84590564-- From nobody Thu Jun 7 08:58:39 2018 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 7CDCD131136 for ; Thu, 7 Jun 2018 08:58:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 IIlFPl0qAt3A for ; Thu, 7 Jun 2018 08:58:28 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 0E820130F65 for ; Thu, 7 Jun 2018 08:58:26 -0700 (PDT) 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=lrd0xwqUmOcYUvTLOr6mFeYpNpQ=; b=TtW82TLTazZBVusx m2QIQna5HV9FdykgC/awbfWjpe/Y68v3VO5o/Co29xbk/u9Cocwr0vPpkpNUikMK LbZj7xfT6KuLmyPYeQBE0kaKuwI9T5Gm3dbeO02CfZvwRr+tjxnkjjRDDsPntVQo XcwtDAUaXh2imuZmHOxrtCDxLDU= Received: by filter1714p1mdw1.sendgrid.net with SMTP id filter1714p1mdw1-16011-5B195622-B 2018-06-07 15:58:26.357899796 +0000 UTC Received: from github-lowworker7-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id UiVfLVrVRl2TU2PggtVAWw for ; Thu, 07 Jun 2018 15:58:26.304 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker7-cp1-prd.iad.github.net (Postfix) with ESMTP id 3A795A23BA for ; Thu, 7 Jun 2018 08:58:26 -0700 (PDT) Date: Thu, 07 Jun 2018 15:58:26 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b19562238e37_4f243f8fc5066f781020d1"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak39PZ0Lh9inTeG59Fu6os9R0J+j5Z9s2PLZ8q khwzUYtNx3Q/ckOunHll3O2rofSj9T9cZVoYGn91SN+aRIbm95yeXXBAn2uJ5mKZ5eA92Sq4W5b8WP 8SMbZnr4WjKvwYLyDYePZRnHBqKOnyZ1CuU/w5sD45/kiERWqtXFd+7FSzmgN70hbvjZmD/cxBzeFA 4= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 07 Jun 2018 15:58:35 -0000 ----==_mimepart_5b19562238e37_4f243f8fc5066f781020d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I seem to recall an algorithm for detecting a peer was gone, to close the connection. I also recall an assertion that either that timer or the idle timer, but never both, would be running. Did that ever turn into text? But yes, I agree with Nick - if you're actively retransmitting, you're not idle and this timer shouldn't be running. If you're retransmitting and it's not getting through, the connection might still time out, but it won't be an idle timeout. -- 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/1429#issuecomment-395473778 ----==_mimepart_5b19562238e37_4f243f8fc5066f781020d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I seem to recall an algorithm for detecting a peer was gone, to close th= e connection. I also recall an assertion that either that timer or the idle= timer, but never both, would be running. Did that ever turn into text?

But yes, I agree with Nick - if you're actively retransmitting, you're n= ot idle and this timer shouldn't be running. If you're retransmitting and i= t's not getting through, the connection might still time out, but it won't = be an idle timeout.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b19562238e37_4f243f8fc5066f781020d1-- From nobody Fri Jun 8 04:23:05 2018 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 B2C09130E78 for ; Fri, 8 Jun 2018 04:23:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 mZaStYgwmqXz for ; Fri, 8 Jun 2018 04:23:02 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 1C1D4130E79 for ; Fri, 8 Jun 2018 04:23:01 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528456981; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=OPm248Y+P7jhOoFjlEgIs1cV68ch5kcHEueGtQ7pCpc=; b=WEqDdDP1gvj1aoEp6OazDQENGGXW1/1Ni9OaEY3cJ+WFAysXzyUyodsRZ6uQg7NzxI7w0261 +MM7Bofs8JhJAXACK7FHrGzpxJSlW2lXFQJl6dbvWKiqMFZzS120QiWOglazUzRtzQfJDEbU PIVucTduOV3IriWCofvgVfWFL4Y= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b1a6714.7f10fc1393c0-smtp-out-n03; Fri, 08 Jun 2018 11:23:00 -0000 (UTC) Date: Fri, 08 Jun 2018 04:23:00 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1a67144864e_196d2aef42301c0c3076c@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c5765f: Move stream type into frame type Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1a671448235_196d2aef42301c0c30692"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 08 Jun 2018 11:23:04 -0000 ----==_mimepart_5b1a671448235_196d2aef42301c0c30692 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/stream_types Home: https://github.com/quicwg/base-drafts Commit: c5765f40dccc1a8bdd1fb5eacbd0d1ccc850f2e3 https://github.com/quicwg/base-drafts/commit/c5765f40dccc1a8bdd1fb5eacbd0d1ccc850f2e3 Author: Mike Bishop Date: 2018-06-08 (Fri, 08 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Move stream type into frame type **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1a671448235_196d2aef42301c0c30692-- From nobody Fri Jun 8 04:25:33 2018 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 BE9E3130E79 for ; Fri, 8 Jun 2018 04:25:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nKOyWYH_6BD1 for ; Fri, 8 Jun 2018 04:25:28 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B5FA130E78 for ; Fri, 8 Jun 2018 04:25:28 -0700 (PDT) Date: Fri, 08 Jun 2018 04:25:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528457127; bh=PHVO0/tWrFKQVSq7nXEHJHtvmq7ZfEAAV3h6ZPYEtuA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XG873M6JZtibjqjt5wgEQkUnrvbfAixkJ52P8bud9DOroBhVcbE4RrDDgisI7YE8L KASKqbxaTBKDWfgiDV9SJcLqLDv5xoPGvcNw7mtU3bzq2AA5um+dQnPSsoBUUot0G0 8/843JZ0OerRk7ls/fB5p8UymRRW3OyKLe+/RuSQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a67a77a6e7_b733fbf1fc8cf803211a9"; 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.26 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: Fri, 08 Jun 2018 11:25:32 -0000 ----==_mimepart_5b1a67a77a6e7_b733fbf1fc8cf803211a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In case we hadn't noticed before, at the Kista interim it became very clear how we all trip over the N/N+4 progression of stream IDs of the same type. It's quite awkward. As someone said, we'll all eventually get used to it, and so will the world... unless we don't have to. It's possible to envision the lowest two bits of the Stream ID as flags which indicate the type, leaving the "real" ID as the upper bits. However, by encoding them in the low bits of an integer, that becomes annoying to represent and work with easily. If they were the high-order bits, that would be more convenient, but would of course blow out the varint encoding. (Of course, two high-order bits of stream type and a 62-bit Stream ID fit nicely into a 64-bit variable assuming that implementations want to store them together once the varint is expanded.) If varint could start mid-byte, that would also be an option, but that makes the varint parser more annoying. The obvious solution, if we want to bite the bullet and go there, is to move the stream type being referenced into the frame type. This was awkward when client-initiated bidirectional stream 0 was special, but now that crypto is moving to a special stream outside the Stream ID space, I think this transition makes more sense. (Crypto is essentially a fifth type of stream with special properties: there can be only one, and most stream management frames don't apply to it.) Besides making Stream IDs easier to keep track of, this resolves the inconsistency between `initial_max_(uni|bidi)_streams` and MAX_STREAM_ID -- the Stream ID and the count are the same thing, if the type is specified separately. By reclaiming two bits per stream reference, this also saves a small number of bytes on the wire -- every STREAM, STOP_SENDING, RST_STREAM, etc. becomes a byte shorter for streams 16-63, 4096-16384, etc. of each stream type. The same benefits will accrue to HTTP PRIORITY frames, where the stream type is already known from the fact that it's a stream carrying an HTTP request. The biggest cost comes in combination with our decision to make frame types varint: By spending two bits of frame type to indicate length and moving stream types into the type byte as well, there are only two frame types values left before we spill into a second byte, and we'll those for CRYPTO and CRYPTO_CLOSE. (If we add something else and something has to spill over, I'd start with things that are sent only once per connection, like the *_CLOSE frames.) -- 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/1430 ----==_mimepart_5b1a67a77a6e7_b733fbf1fc8cf803211a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In case we hadn't noticed before, at the Kista interim it became very clear how we all trip over the N/N+4 progression of stream IDs of the same type. It's quite awkward. As someone said, we'll all eventually get used to it, and so will the world... unless we don't have to.

It's possible to envision the lowest two bits of the Stream ID as flags which indicate the type, leaving the "real" ID as the upper bits. However, by encoding them in the low bits of an integer, that becomes annoying to represent and work with easily.

If they were the high-order bits, that would be more convenient, but would of course blow out the varint encoding. (Of course, two high-order bits of stream type and a 62-bit Stream ID fit nicely into a 64-bit variable assuming that implementations want to store them together once the varint is expanded.) If varint could start mid-byte, that would also be an option, but that makes the varint parser more annoying.

The obvious solution, if we want to bite the bullet and go there, is to move the stream type being referenced into the frame type. This was awkward when client-initiated bidirectional stream 0 was special, but now that crypto is moving to a special stream outside the Stream ID space, I think this transition makes more sense. (Crypto is essentially a fifth type of stream with special properties: there can be only one, and most stream management frames don't apply to it.)

Besides making Stream IDs easier to keep track of, this resolves the inconsistency between initial_max_(uni|bidi)_streams and MAX_STREAM_ID -- the Stream ID and the count are the same thing, if the type is specified separately. By reclaiming two bits per stream reference, this also saves a small number of bytes on the wire -- every STREAM, STOP_SENDING, RST_STREAM, etc. becomes a byte shorter for streams 16-63, 4096-16384, etc. of each stream type. The same benefits will accrue to HTTP PRIORITY frames, where the stream type is already known from the fact that it's a stream carrying an HTTP request.

The biggest cost comes in combination with our decision to make frame types varint: By spending two bits of frame type to indicate length and moving stream types into the type byte as well, there are only two frame types values left before we spill into a second byte, and we'll those for CRYPTO and CRYPTO_CLOSE. (If we add something else and something has to spill over, I'd start with things that are sent only once per connection, like the *_CLOSE frames.)

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

----==_mimepart_5b1a67a77a6e7_b733fbf1fc8cf803211a9-- From nobody Fri Jun 8 04:29:44 2018 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 700C2130E7A for ; Fri, 8 Jun 2018 04:29:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 fgRDGyxY2JTd for ; Fri, 8 Jun 2018 04:29:41 -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 E9674130E78 for ; Fri, 8 Jun 2018 04:29:40 -0700 (PDT) Date: Fri, 08 Jun 2018 04:29:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528457380; bh=S7r0cYqS3D1z/W1kYZH4362XNHCobGq1/+36zwKm9gE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=LXh6cVB+QG0Io0DpIEZG0bdqs8GTEWOAqzIcznJ+DVWTC/wAHm5tKeqzE8UF9WjFJ /4ES7vaLI1+kfamLRzVepc1qmCaUgndz11PEBFHVjNRjkCRCnVCr5lgcQvseO8c7ma dRMBsVCaV3KvvV7TctO8YW9n0KgFiw/9Sish50ro= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a68a468a3f_7a6a2aef3307cf542720e6"; 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.26 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: Fri, 08 Jun 2018 11:29:43 -0000 ----==_mimepart_5b1a68a468a3f_7a6a2aef3307cf542720e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit During the discussion that became #1430 in Kista, @janaiyengar asked me to write this up, just so we could see what it looks like. As the issue mentions, this becomes more viable now that the crypto stream won't be part of any of the stream type spaces, but off on its own. To keep this sensible, I've deleted the stream 0 carve-outs where they were in the way of this change, but it won't actually be fully consistent until #1377 lands as well. Fixes #1430. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1431 -- Commit Summary -- * Move stream type into frame type -- File Changes -- M draft-ietf-quic-transport.md (253) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1431.patch https://github.com/quicwg/base-drafts/pull/1431.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/1431 ----==_mimepart_5b1a68a468a3f_7a6a2aef3307cf542720e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

During the discussion that became #1430 in Kista, @janaiyengar asked me to write this up, just so we could see what it looks like.

As the issue mentions, this becomes more viable now that the crypto stream won't be part of any of the stream type spaces, but off on its own. To keep this sensible, I've deleted the stream 0 carve-outs where they were in the way of this change, but it won't actually be fully consistent until #1377 lands as well.

Fixes #1430.

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

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

Commit Summary

  • Move stream type into frame type

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 mute the thread.

----==_mimepart_5b1a68a468a3f_7a6a2aef3307cf542720e6-- From nobody Fri Jun 8 04:35:30 2018 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 BED8C130E79 for ; Fri, 8 Jun 2018 04:35:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 k5eVmRZ2TA6i for ; Fri, 8 Jun 2018 04:35:26 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 22F73130E78 for ; Fri, 8 Jun 2018 04:35:26 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528457725; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=BHiHncbNi6V+vKzZDOMsaTRUdjJQ3sGRCr+JEWS3vVw=; b=GzsJViT98Nit8DfJwUiWeczq3e77043fS8z9eFf5qnQGNLtwmN5XgRfbE5szx6ONJZ2dmHhN XKbKBpGx060dGxzr308+vLHxQo/yP6p/BEmP+gxH560BpGnIcaYBtet+zy73luIddGMqtYk7 rlDANfZG3LjYcqG3/Z8jXybeCJM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b1a69fd.7f30a04f30c0-smtp-out-n01; Fri, 08 Jun 2018 11:35:25 -0000 (UTC) Date: Fri, 08 Jun 2018 04:35:24 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1a69fc1b285_75672abf7eba3c001619b@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e77227: Include decryption failures Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1a69fc1af37_75672abf7eba3c0016053"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 08 Jun 2018 11:35:28 -0000 ----==_mimepart_5b1a69fc1af37_75672abf7eba3c0016053 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts Commit: e77227596318c72d844707655d68bf59dc5c0bfb https://github.com/quicwg/base-drafts/commit/e77227596318c72d844707655d68bf59dc5c0bfb Author: Mike Bishop Date: 2018-06-08 (Fri, 08 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Include decryption failures **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1a69fc1af37_75672abf7eba3c0016053-- From nobody Fri Jun 8 04:35:39 2018 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 685F5130E7A for ; Fri, 8 Jun 2018 04:35:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4xyUwZd0lSY1 for ; Fri, 8 Jun 2018 04:35:31 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7F9B130E82 for ; Fri, 8 Jun 2018 04:35:31 -0700 (PDT) Date: Fri, 08 Jun 2018 04:35:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528457730; bh=lr7BYxwla1O0qua+c7aDtCW1thKc/QKmwhFxUQS/Hv4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zP8weLdUiCKY/Wq0SiWRv2VlvKOBbmEIgVNaTML7Rms2KaryGVvNUzfHhBlGqG/73 NywiquV57T8pOuE5kO0yCKMiff308GY5HV9LDXYk6/uwfl1t29gP6JAQNKdE5CNI/7 8oxKKQRJbyWXB3ztCJxoZPJLu6w8no+kruR7lKxw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a6a02ea455_433a3fd2d5e00f7821849"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 08 Jun 2018 11:35:34 -0000 ----==_mimepart_5b1a6a02ea455_433a3fd2d5e00f7821849 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. e772275 Include decryption failures -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1423/files/195f144870a810fff9e4e1518f52f779d384ea41..e77227596318c72d844707655d68bf59dc5c0bfb ----==_mimepart_5b1a6a02ea455_433a3fd2d5e00f7821849 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

  • e772275 Include decryption failures

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1a6a02ea455_433a3fd2d5e00f7821849-- From nobody Fri Jun 8 04:37:08 2018 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 AF97E130E79 for ; Fri, 8 Jun 2018 04:37:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lIZoQh5iyp5g for ; Fri, 8 Jun 2018 04:37:05 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03CCB130E78 for ; Fri, 8 Jun 2018 04:37:05 -0700 (PDT) Date: Fri, 08 Jun 2018 04:37:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528457824; bh=F0s4mJqS15970EfnlyS5UYK8xTDDFnp1BiOJVQgwGNc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rfGddcoIkzeo50AwDB+iExgXHxWVgcs4n9I7XPnEyHvLbZyUPeXPmPZkFexCM4/8r nIibSI7c8vu5IV6lPQ4cLbkcVriHzDPl8OMD5mLsYEJ6L5v9FGnq9iXIiK5z169Sz+ HCZeuyT+Mb2UZ4ToE7hYrmAC+z5YyiSQ8uECvWJA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a6a60462eb_38da2b0592ae6f604166b9"; 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.26 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: Fri, 08 Jun 2018 11:37:07 -0000 ----==_mimepart_5b1a6a60462eb_38da2b0592ae6f604166b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Updated to reflect suggestion from second day of Kista interim: Should also apply to packets that fail decryption, as there are cases an implementation will want to put a long header with a junk payload followed by a short header packet. -- 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/1423#issuecomment-395734738 ----==_mimepart_5b1a6a60462eb_38da2b0592ae6f604166b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Updated to reflect suggestion from second day of Kista interim: Should also apply to packets that fail decryption, as there are cases an implementation will want to put a long header with a junk payload followed by a short header packet.

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

----==_mimepart_5b1a6a60462eb_38da2b0592ae6f604166b9-- From nobody Fri Jun 8 04:40:40 2018 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 C7391130E78 for ; Fri, 8 Jun 2018 04:40:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 a7wSU28HNm8Z for ; Fri, 8 Jun 2018 04:40:36 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 5A904130E61 for ; Fri, 8 Jun 2018 04:40:36 -0700 (PDT) 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=DTaaqnNlDjjq5iYOCBni8d5EMxk=; b=UVki64ml0MuHKU4l gPo34MNpghsRCGOqf0u31EHriMbIf/SKohmkfOSkYs1PZzEzI1qLlYfKN/MGOwg5 h+M5vH5cmTCyh11cDDH4/VfxVm+aYh8NFyEJiPAaWcHQDmcQJxYfbfpyR53ijJa9 k8DXOpo0RGCmF4/QjL4uNt/A7Ik= Received: by filter1625p1mdw1.sendgrid.net with SMTP id filter1625p1mdw1-25288-5B1A6B32-25 2018-06-08 11:40:34.90295259 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id OAEGYJY3RUCYmRgPPLsDTA for ; Fri, 08 Jun 2018 11:40:34.868 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id D2B02812BE for ; Fri, 8 Jun 2018 04:40:34 -0700 (PDT) Date: Fri, 08 Jun 2018 11:40:35 +0000 (UTC) From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a6b32d04ee_4d482af30933cf5825229f"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0wNr9hKjO53y0n/wmevbCFjv2jddS/esnEGC M9G40YDtf0VTdC7v4T2ZlEw4cOz8qjPUxn3bUMbXYCHwrB1HP/AdiI04vrzI3KIuFVG7vHxtqQpzrk 2lM7gQ5cBF5Tz8rxlesbzMdaMlyiFm8AzxjDqAefJ8IAZKyQSW/F3fbj/O3GKsXQfgRqMWIKogbF99 k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 11:40:39 -0000 ----==_mimepart_5b1a6b32d04ee_4d482af30933cf5825229f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Clarification: does this mean the stream intent at the QUIC layer as opposed to application layer mapping type? -- 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/1431#issuecomment-395735449 ----==_mimepart_5b1a6b32d04ee_4d482af30933cf5825229f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Clarification: does this mean the stream intent at the QUIC layer as opposed to application layer mapping type?

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

----==_mimepart_5b1a6b32d04ee_4d482af30933cf5825229f-- From nobody Fri Jun 8 04:43:35 2018 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 28E67130E7C for ; Fri, 8 Jun 2018 04:43:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 tWBtDhRGKNWH for ; Fri, 8 Jun 2018 04:43:32 -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 B9731130E79 for ; Fri, 8 Jun 2018 04:43:32 -0700 (PDT) Date: Fri, 08 Jun 2018 04:43:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528458212; bh=4lYzwJEfbURaDszoY2eO47/oywpHQ3HcObT2mOGfDkg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=B6Wua8GUKAiLveB6NTBo8GIZX2utFHZ9SqO79GazIK1pHv9hIohjGWLQeVlT9lqWk qXbbrA5VdpysM1GhSYcpLCEH5pXwpbcFvd7duz7RnoTshOXiTb2/88J/9eCtRWdjSU I2xYK5YY2fp50JIRs8l9nKjM/P0Fr3FfHbZkmmvM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a6be4194f5_28672b221aabaf60157659"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 11:43:35 -0000 ----==_mimepart_5b1a6be4194f5_28672b221aabaf60157659 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Finally !!! but > The biggest cost comes in combination with our decision to make frame types varint: By spending two bits of frame type to indicate length and moving stream types into the type byte as well, there are only two frame types values left before we spill into a second byte, why do you want to do this? If you want an extensible frame type, use 0xff for extensions. Waisting two bits just to use the same varint encoding as for 62 bit integers makes little sense. -- 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/1430#issuecomment-395736075 ----==_mimepart_5b1a6be4194f5_28672b221aabaf60157659 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Finally !!!

but

The biggest cost comes in combination with our decision to make frame = types varint: By spending two bits of frame type to indicate length and m= oving stream types into the type byte as well, there are only two frame t= ypes values left before we spill into a second byte,

why do you want to do this? If you want an extensible frame type, use = 0xff for extensions. Waisting two bits just to use the same varint encodi= ng as for 62 bit integers makes little sense.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1a6be4194f5_28672b221aabaf60157659-- From nobody Fri Jun 8 04:51:21 2018 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 4EF76130E80 for ; Fri, 8 Jun 2018 04:51:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HzkqKU8-8CNO for ; Fri, 8 Jun 2018 04:51:17 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F6CA130E7D for ; Fri, 8 Jun 2018 04:51:17 -0700 (PDT) Date: Fri, 08 Jun 2018 04:51:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528458676; bh=WomQreFG714aWKtNxDBnjizWHWtAxa/WwoB5DuAB4Wk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M1AWKLOGYJZCHztPE2ArwPrxZnfuwlT2g+i653Ag38jRQVgrRzFzyIgFjMFqktgVS Wa/lq3W9b34+BNW+mxHMc6Nc0V1sYKUGZRM2Bnrry9faiEYlAODdZpkKaZrt0fQgMv X48OIbqIH/7iHL+K0cBU922Geuks1DLCKcuJ3yUE= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a6db49f80b_7ab2adbeb6a0f587399"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 11:51:20 -0000 ----==_mimepart_5b1a6db49f80b_7ab2adbeb6a0f587399 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On frame type extensions: more specifically, if you later want to add partial reliable frames or single frame messages, these would benefit the most from short frame types, but they will be forced into a two byte frame type. This can be avoided by using 0xff (or similar to encode extensions). On second byte 0xff could again code for extensions, or you could use varint encoding in the second byte. -- 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/1430#issuecomment-395737681 ----==_mimepart_5b1a6db49f80b_7ab2adbeb6a0f587399 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On frame type extensions:
more specifically, if you later want to add partial reliable frames or si= ngle frame messages, these would benefit the most from short frame types,= but they will be forced into a two byte frame type. This can be avoided = by using 0xff (or similar to encode extensions). On second byte 0xff coul= d again code for extensions, or you could use varint encoding in the seco= nd byte.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1a6db49f80b_7ab2adbeb6a0f587399-- From nobody Fri Jun 8 05:03:52 2018 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 9D105130E83 for ; Fri, 8 Jun 2018 05:03:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1iYzpTt3TY6Z for ; Fri, 8 Jun 2018 05:03:49 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34025130E80 for ; Fri, 8 Jun 2018 05:03:49 -0700 (PDT) Date: Fri, 08 Jun 2018 05:03:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528459428; bh=MoXBgKoGqo4hYZBRlmDKtO6ko3GFu4sVqZbYAb26Q90=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CNMkiCW7otRplxnNhPRUfBF9JeHeUNaxSfOb/55WSshS6tFzHY29ujHI6jr60gG4B jP8eajLkc5LLNUM/P7kq627tX7d+TFvqvatNd96orFvkx4GjgomnWO+cDvabw0igB6 JyNSJGMslzAOXnc23AgeOpQHyHAZ/cu8dQiVrvd0= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a70a48e0ec_1f092b00a2df8f5468292"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 12:03:51 -0000 ----==_mimepart_5b1a70a48e0ec_1f092b00a2df8f5468292 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Clarification: does this mean the stream intent at the QUIC layer as opposed to application layer mapping type? As I read it, this is clearly at the QUIC layer, and QUIC (transport) doesn't really deal much with the application layer. It might be good with some additional formal naming conventions such as peer initiated bidi stream, locally initiated uni stream, etc. such that HTTP QUIC and friends has a meaningful language and possibly also assign a number to the stream type as a value in 0 .. 3 but keeping the actual stream id specific to the stream type at both layers. -- 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/1431#issuecomment-395740360 ----==_mimepart_5b1a70a48e0ec_1f092b00a2df8f5468292 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Clarification: does this mean the stream intent at the QUIC layer as o= pposed to application layer mapping type?

As I read it, this is clearly at the QUIC layer, and QUIC (transport) = doesn't really deal much with the application layer.

It might be good with some additional formal naming conventions such a= s peer initiated bidi stream, locally initiated uni stream, etc. such tha= t HTTP QUIC and friends has a meaningful language and possibly also assig= n a number to the stream type as a value in 0 .. 3 but keeping the actual= stream id specific to the stream type at both layers.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1a70a48e0ec_1f092b00a2df8f5468292-- From nobody Fri Jun 8 05:36:28 2018 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 DE4E3130EA1 for ; Fri, 8 Jun 2018 05:36:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 EBnyfbuBP1BU for ; Fri, 8 Jun 2018 05:36:24 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 B0943130E9B for ; Fri, 8 Jun 2018 05:36:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=rgXMuy5Pps2Y8LEH1+Mi6AYhNZA=; b=Sh6lLGJE19Q2/v9d 5HV91+3acy/8FjAkEA1U8gxZzYdt4k2Cj5bUkg5izx2JNs/4XNlj1ty7GZ4nSspr vfOI6G8viHxtye28RogY7X3hKoX4wfpks5uc+JOiXEt0CTF7EZ+0fDHz+FX7NB4a sqOSo596Ohkrd9OevJOaLJwqvdU= Received: by filter0410p1iad2.sendgrid.net with SMTP id filter0410p1iad2-7245-5B1A7845-1B 2018-06-08 12:36:21.547021817 +0000 UTC Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id xNxc1CZsTemdmGCTB8qmGg for ; Fri, 08 Jun 2018 12:36:21.525 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 7BCB0C0073 for ; Fri, 8 Jun 2018 05:36:21 -0700 (PDT) Date: Fri, 08 Jun 2018 12:36:22 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a7845797e0_18c12ae46514ef5077776"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak38yAT9zZHymQctXJpF+BbsUr1cpXjcrN/KWh nB7FzMzVsmRAEYbS6E0Y2hkJtUgwRmDiboBoAMC3HDouA3CS2QBCmhXuZmGTGqpqZ+DI2eh5JVWj1H SCDkcchTSilQRJcYEhyAP+B5Hpwfx5U798aWSUaDLW8m5t+AQViTZQViUj/WB/+BUvaM9XHGwFmNWu o= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 12:36:27 -0000 ----==_mimepart_5b1a7845797e0_18c12ae46514ef5077776 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit HTTP/QUIC has a particular example of a pattern that seems likely to be usable in many other contexts. A block of data is preceded by a length field. The receiver of that block might read the length field then await the arrival of the entire block before processing the block. During that time, the block is left unread so that the data can sit in the receive buffer of the transport. This ensures that the data counts towards the flow control limits of the receiver. This can prevent the sender from adding more messages that would only consume additional memory at the receiver. In an extreme case, this leads to a deadlock. The receiver is waiting for the end of a block. The sender cannot send the remainder of the block because it does not have enough flow control credit. This impasse doesn't naturally resolve in this case. Worse, even if flow control might allow a single stream to make progress because the receiver ensures that it provides credit for the largest possible message or more, multiple concurrent streams could each consume a small part of the available flow control credit without allowing any single one to make progress. Ultimately, there isn't an easy fix for this. We could recommend a new input for prioritization: favour the sending of data for streams that are in the middle of sending a chunk, but that requires the transport be informed of message boundaries. Relying on RST_STREAM to cancel streams until the logjam clears might work in some cases, but we have some examples already of streams that cannot be safely cancelled. So this will always be a danger. We gain some insight into what is going on with BLOCKED and friends, but ultimately this is just *hard*. Not sure how much advice we can give here, or whether saying anything is even needed. -- 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/1432 ----==_mimepart_5b1a7845797e0_18c12ae46514ef5077776 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

HTTP/QUIC has a particular example of a pattern that seems likely to be usable in many other contexts. A block of data is preceded by a length field. The receiver of that block might read the length field then await the arrival of the entire block before processing the block. During that time, the block is left unread so that the data can sit in the receive buffer of the transport. This ensures that the data counts towards the flow control limits of the receiver. This can prevent the sender from adding more messages that would only consume additional memory at the receiver.

In an extreme case, this leads to a deadlock. The receiver is waiting for the end of a block. The sender cannot send the remainder of the block because it does not have enough flow control credit.

This impasse doesn't naturally resolve in this case. Worse, even if flow control might allow a single stream to make progress because the receiver ensures that it provides credit for the largest possible message or more, multiple concurrent streams could each consume a small part of the available flow control credit without allowing any single one to make progress.

Ultimately, there isn't an easy fix for this. We could recommend a new input for prioritization: favour the sending of data for streams that are in the middle of sending a chunk, but that requires the transport be informed of message boundaries. Relying on RST_STREAM to cancel streams until the logjam clears might work in some cases, but we have some examples already of streams that cannot be safely cancelled. So this will always be a danger. We gain some insight into what is going on with BLOCKED and friends, but ultimately this is just hard.

Not sure how much advice we can give here, or whether saying anything is even needed.

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

----==_mimepart_5b1a7845797e0_18c12ae46514ef5077776-- From nobody Fri Jun 8 05:48:01 2018 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 1D12D130EA6 for ; Fri, 8 Jun 2018 05:47:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1233F2X6Pu7O for ; Fri, 8 Jun 2018 05:47:46 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6393130ED1 for ; Fri, 8 Jun 2018 05:47:46 -0700 (PDT) Date: Fri, 08 Jun 2018 05:47:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528462066; bh=l7fxzSqUfqHbHzxVsSbGuLKEMwyTgvWjprYOA7SAnTk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EmhdeoiApfCvzkz8TvZcK322iJapD9VujCTENEDl9gRxQ5o1e2AC3BXlRIGsWwtJ1 qcXsLaDfXSZdudp12YRL5DAOabJZ80K+rlIbD5xixmNaJMsEKCGTjra5ET0QORRBT+ Byb0EYp+1+iT83tFH0gsvF3FeJyT7z3FwfeOn6Fg= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a7af223ebe_4dc12afb1914ef58969b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 12:48:00 -0000 ----==_mimepart_5b1a7af223ebe_4dc12afb1914ef58969b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit How big is a block in this context? It can't be arbitrary because then strategy of waiting until the end before crediting flow won't work. If it isn't arbitrary, could flow be reserved for the reminder such that new streams can't be created if they cannot reserve enough flow? -- 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/1432#issuecomment-395750375 ----==_mimepart_5b1a7af223ebe_4dc12afb1914ef58969b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

How big is a block in this context? It can't be arbitrary because then strategy of waiting until the end before crediting flow won't work. If it isn't arbitrary, could flow be reserved for the reminder such that new streams can't be created if they cannot reserve enough flow?

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

----==_mimepart_5b1a7af223ebe_4dc12afb1914ef58969b7-- From nobody Fri Jun 8 06:07:10 2018 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 6FF17130E5F for ; Fri, 8 Jun 2018 06:07:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vmlFQP6c32HR for ; Fri, 8 Jun 2018 06:07:07 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D104012D949 for ; Fri, 8 Jun 2018 06:07:06 -0700 (PDT) Date: Fri, 08 Jun 2018 06:07:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528463226; bh=+bU624sVr+xGTH0mTW0bK9UQ1WZLlAqPfD/E6eg7B7g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UNZxFOGgdnM236PLpCabnOV4vIQCkf4kJq91sQ8cEUrs4++hsCX52+PNT3nmVmbUI xHiXjZDiqLZupV9brhCdpZd+qOrKslpnEdCKSOktqTag0oHXmMXnqsHPsFjPvV85RS szno9dh2kLR+P4JTfIz8fHheQtIcyitdEjwgNFtk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a7f7a369e6_2c413fc08f502f78296dc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:07:09 -0000 ----==_mimepart_5b1a7f7a369e6_2c413fc08f502f78296dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is the fun bit, I don't know. We have frames in hq that are like this. Some of those could be very large (think DATA), others small. Some are naturally suited to streaming (DATA again), others not at all (HEADERS). Smaller sizes change the odds, but they don't prevent the problem completely until the size hits zero. I don't think that we're going to create a technical solution to this one. I suspect that it will remain as one of the bits of the protocol that will be hard to get right. -- 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/1432#issuecomment-395755024 ----==_mimepart_5b1a7f7a369e6_2c413fc08f502f78296dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This is the fun bit, I don't know. We have frames in hq that are like= this. Some of those could be very large (think DATA), others small. So= me are naturally suited to streaming (DATA again), others not at all (HEA= DERS). Smaller sizes change the odds, but they don't prevent the problem= completely until the size hits zero.

I don't think that we're going to create a technical solution to this = one. I suspect that it will remain as one of the bits of the protocol th= at will be hard to get right.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1a7f7a369e6_2c413fc08f502f78296dc-- From nobody Fri Jun 8 06:31:28 2018 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 10E3F130EDE for ; Fri, 8 Jun 2018 06:31:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 az-HyCA8Bb-p for ; Fri, 8 Jun 2018 06:31:13 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 1F314130ED8 for ; Fri, 8 Jun 2018 06:31:13 -0700 (PDT) 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=nHP1GG5uFepznqhf56Hv4P2csbo=; b=s0WxyTFM79qKwUvn M4XIXslzXEJMPpyPnP23AhgmNgZNynnVRWqS/0NgjtN/lb+4Ta9qn03F6EcIH88d 9kbK5kdTlgxCmVAx6G7hVHnD8mmBIRDUgTctmnb8mg5VzsMJWLv7GhxmrniF8lVx XXCptoIJh9CSfI+BRme5wu7FFuc= Received: by filter0001p1iad2.sendgrid.net with SMTP id filter0001p1iad2-16863-5B1A851F-33 2018-06-08 13:31:11.633038269 +0000 UTC Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id exzE5qEbQCOT3_Z9s_sO4g for ; Fri, 08 Jun 2018 13:31:11.565 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id 882A0C1196 for ; Fri, 8 Jun 2018 06:31:11 -0700 (PDT) Date: Fri, 08 Jun 2018 13:31:11 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream 0 DT proposal conflicts with PRIORITY (#1421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a851f8682e_4e372ab1ad1acf5079676"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3bf9/h7P9DLAYDVkPBHcSu/97eO7X3a8skfK 5Xw9Vs0H1d4CCqD7m/XVwKiw4nSq5NvJ0M7o3uP+rwmRiUKBkpiZaOdkXW2KuFfn439yB+Z7ZBXVN/ zKRYWdkBfgrgETsdGB7MNPp6pX9OqMWA4Xzld/gPVrobPgvMgImBY8U/xiM4c6ySVhVFcsvtLShHu0 I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:31:27 -0000 ----==_mimepart_5b1a851f8682e_4e372ab1ad1acf5079676 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yep, placeholders FTW. -- 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/1421#issuecomment-395761401 ----==_mimepart_5b1a851f8682e_4e372ab1ad1acf5079676 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yep, placeholders FTW.

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

----==_mimepart_5b1a851f8682e_4e372ab1ad1acf5079676-- From nobody Fri Jun 8 06:31:54 2018 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 3758F130EE3 for ; Fri, 8 Jun 2018 06:31:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 gmXR65UcpUcp for ; Fri, 8 Jun 2018 06:31:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ED86130EBB for ; Fri, 8 Jun 2018 06:31:42 -0700 (PDT) Date: Fri, 08 Jun 2018 06:31:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528464701; bh=7pdZt0mI4onLc7P3S67qOY3PWpGaPDX/zBQjrFfMoM4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QVDspgEVr7JUqNx32MychsdMxKfGbn3AdM3ESDXM9JWSfWpA6GHM6KHjrzJDcbkSe TP9BmilkUlLrPrRgtqGb8bXuPMnUykGBpVNn7lP1wKI5umyV9c/lEk9hzRIbk74n3/ h83OOsInZJiat2v0B5dpGInosfEkmNPUlLDopN50= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a853d39e14_cd33f8e31232f7c1163e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 13:31:53 -0000 ----==_mimepart_5b1a853d39e14_cd33f8e31232f7c1163e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You could define a negotiable, but fixed, block size and require the application to drain after receiving that much, and prevent too many streams without additional block credits. This can still deadlock if the app won't buffer the block or it needs to create more streams, but it is not as arbitrary as random deadlocks. -- 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/1432#issuecomment-395761561 ----==_mimepart_5b1a853d39e14_cd33f8e31232f7c1163e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

You could define a negotiable, but fixed, block size and require the a= pplication to drain after receiving that much, and prevent too many strea= ms without additional block credits. This can still deadlock if the app w= on't buffer the block or it needs to create more streams, but it is not a= s arbitrary as random deadlocks.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1a853d39e14_cd33f8e31232f7c1163e7-- From nobody Fri Jun 8 06:39:30 2018 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 B1A2E130EA6 for ; Fri, 8 Jun 2018 06:39:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 YpkxZSX4iPHH for ; Fri, 8 Jun 2018 06:39:25 -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 B15F5130EA3 for ; Fri, 8 Jun 2018 06:39:25 -0700 (PDT) Date: Fri, 08 Jun 2018 06:39:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528465165; bh=IPjnA+OrurlaA/cnpt5EQc0oGUstqFKUYgLqaCECXMk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eYNPqZzj2DU6QLTLqqUsQ3elL3rXPXgk/m7RA5EWY82zA7KlifRwBpU4SwiWvzgx6 MT2mnTMHjToHxJDBpfP3Jfwhcg+ZnYcPJ3X9zmf6Ej/MF5WuX7IvJQe3JTeGpCtx3o KQeLo3sC8DgwHPGsPLH9bry0zqSI0/l6L3S9Ccqc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a870df8b0_29313ffba1b88f8028229"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:39:28 -0000 ----==_mimepart_5b1a870df8b0_29313ffba1b88f8028229 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. This looks broadly OK, but I wonder if we can't exploit the properties of stream identifiers to our advantage here. Stream ID modulo 4 of a request stream will always be 0. That leaves 3/4 of the entire space of identifiers available to us. Maybe we could drop the dependency and priority types and encode the type in the last octets of the "stream ID": * 00 is a request stream (it happens to also match the stream ID) * 11 is a push stream, identified by push ID shifted left by 2 (this might result in the push ID matching the push stream ID, which might be confusing, so we might choose not to use this) * 01 is a placeholder * 10 is the root (and we would reserve/prohibit values other than 0 for the remaining bits of the identifier) Then the only bit remaining in the flags is the Exclusive bit. You could also use a flag for the root and omit the dependency identifier in that case, leaving the odd single-valued encoding untouched. It seems like we'd have plenty of space in the flags if that was what was wanted. -- 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/1422#pullrequestreview-127164641 ----==_mimepart_5b1a870df8b0_29313ffba1b88f8028229 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson commented on this pull request.

This looks broadly OK, but I wonder if we can't exploit the properties= of stream identifiers to our advantage here.

Stream ID modulo 4 of a request stream will always be 0. That leaves = 3/4 of the entire space of identifiers available to us. Maybe we could d= rop the dependency and priority types and encode the type in the last oct= ets of the "stream ID":

  • 00 is a request stream (it happens to also match the stream ID)
  • 11 is a push stream, identified by push ID shifted left by 2 (this mi= ght result in the push ID matching the push stream ID, which might be con= fusing, so we might choose not to use this)
  • 01 is a placeholder
  • 10 is the root (and we would reserve/prohibit values other than 0 for= the remaining bits of the identifier)

Then the only bit remaining in the flags is the Exclusive bit.

You could also use a flag for the root and omit the dependency identif= ier in that case, leaving the odd single-valued encoding untouched. It s= eems like we'd have plenty of space in the flags if that was what was wan= ted.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

= = ----==_mimepart_5b1a870df8b0_29313ffba1b88f8028229-- From nobody Fri Jun 8 06:41:21 2018 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 E9D78130EA7 for ; Fri, 8 Jun 2018 06:41:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fnb9GkQ9B0oI for ; Fri, 8 Jun 2018 06:41:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ED5F130EA3 for ; Fri, 8 Jun 2018 06:41:18 -0700 (PDT) Date: Fri, 08 Jun 2018 06:41:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528465277; bh=hNHeo7LqMuCeFW6Eu43O1qOzvveqZPKWGnUCI94rg+c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mSff2JDlHNaglBkqqdIz6nDQDxhufHVocbnd697u07nAWnKL7zZHP9ip1GHMxfP3t LK2BjXYeALnASoJ5xbG7ADfDJE7STRU/RTQK05M2M/NexvaCKpYa/ppUu2K/CKoD5L 4cOgo31TlnGYIn6e9n0zn339YHvA+CLU2y8um1Ik= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit stream open (#1342) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a877db04a6_57d82aad62b70f548283c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:41:21 -0000 ----==_mimepart_5b1a877db04a6_57d82aad62b70f548283c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We discussed this in Kista and on balance implicit open was preferred. -- 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/1342#issuecomment-395764109 ----==_mimepart_5b1a877db04a6_57d82aad62b70f548283c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We discussed this in Kista and on balance implicit open was preferred.

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

----==_mimepart_5b1a877db04a6_57d82aad62b70f548283c-- From nobody Fri Jun 8 06:48:03 2018 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 B8C8A130EAE for ; Fri, 8 Jun 2018 06:48:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BolS53wRTZCV for ; Fri, 8 Jun 2018 06:47:59 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1F39126CC7 for ; Fri, 8 Jun 2018 06:47:59 -0700 (PDT) Date: Fri, 08 Jun 2018 06:47:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528465678; bh=q/51AjcKb44HDpcXpJxA7nIucjcGE9kpKecGpimFT2I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AylN5MLUDWqeY4kzo3spKOy6SLvuLfmPPq6vACq4po+629U0j0vFoEd91VO+b466C BOCbFufUrrto6t8FSHG0uno0ipD0W6+Pg+GpBGXbt4FswCn8AhqwFUQ8mCL6rtJWpr h2VUu9hLFZA3wOZw+EzCs2PBiDoRFEtVkoOtlHOE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a890ec3a2f_60b3f7e61f38f80200723"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:48:02 -0000 ----==_mimepart_5b1a890ec3a2f_60b3f7e61f38f80200723 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A packet can always be decoded as though it were valid. A short header will either be too short or it will be sent to the AEAD to fail decryption. Long headers are a little trickier, but not overly so. If it is too short, it is discarded. The difference is that it has an explicit length. If the length is too short or too long, it is discarded. Then you pass to the AEAD to fail decryption. Only in that case do you need to worry about what comes after. My question is: if the connection ID doesn't match, can the recipient discard the entire datagram? We require that the connection IDs are consistent across the entire datagram. I think that it would be reasonable to discard in that case. -- 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/1287#issuecomment-395765891 ----==_mimepart_5b1a890ec3a2f_60b3f7e61f38f80200723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A packet can always be decoded as though it were valid.

A short header will either be too short or it will be sent to the AEAD= to fail decryption.

Long headers are a little trickier, but not overly so. If it is too s= hort, it is discarded. The difference is that it has an explicit length.= If the length is too short or too long, it is discarded. Then you pass= to the AEAD to fail decryption. Only in that case do you need to worry = about what comes after.

My question is: if the connection ID doesn't match, can the recipient = discard the entire datagram? We require that the connection IDs are cons= istent across the entire datagram. I think that it would be reasonable t= o discard in that case.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1a890ec3a2f_60b3f7e61f38f80200723-- From nobody Fri Jun 8 06:48:31 2018 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 A9997130EAF for ; Fri, 8 Jun 2018 06:48:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 qi5LvmF8GsoU for ; Fri, 8 Jun 2018 06:48:27 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 59463130EAE for ; Fri, 8 Jun 2018 06:48:27 -0700 (PDT) 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=9QsXXypHfMqt+h2v0lyEsUMbfhE=; b=s2BYgkdht/CyE1FU Cwiv4JezRQozx4VUMbiLmFcRUZ2i32Z7kE5wC3Sb4V5QvABB02Zce1ex/hr5FuKw 4k623RqOXor9i3y9RCyx2dS8iiRkdXH6n7PuhWBTVOh2D7GnCBvrS7fivVVy+tYR 0Qxo7iDuWo6zmHY2EJaXF5Dimg8= Received: by filter0574p1iad2.sendgrid.net with SMTP id filter0574p1iad2-10526-5B1A892A-4 2018-06-08 13:48:26.127773136 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id wi1qxV4ZQeeIMZbeH-KOGQ for ; Fri, 08 Jun 2018 13:48:26.083 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id 118E9C0A22 for ; Fri, 8 Jun 2018 06:48:26 -0700 (PDT) Date: Fri, 08 Jun 2018 13:48:26 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a892af082_34702af6d06e4f50610d7"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3icr7rtSi9+xbEYK7JkahrhRZY38WYOmqMD3 QAEnSPTyXkMbYmDlvH9cVKZx5QwYA31brjAkITsFXB2Jbo70P+c7lEMAAcgjAGB2eStFzhMC/sEKbo nAazRwb/t7VQKMI5c8ATze0tkMMuSNiqFtoEw9QY9FLoCd4Q8loCiX79osq/Y1+pwW5VWwlM4xVAcx M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:48:30 -0000 ----==_mimepart_5b1a892af082_34702af6d06e4f50610d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. This is missing text on what to do if the connection ID doesn't match. I think that we need to be explicit about that. Otherwise, this looks great. -- 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/1423#pullrequestreview-127168018 ----==_mimepart_5b1a892af082_34702af6d06e4f50610d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

This is missing text on what to do if the connection ID doesn't match. I think that we need to be explicit about that. Otherwise, this looks great.

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

----==_mimepart_5b1a892af082_34702af6d06e4f50610d7-- From nobody Fri Jun 8 06:55:38 2018 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 50FEE130EAF for ; Fri, 8 Jun 2018 06:55:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 WVSo6c05qTGd for ; Fri, 8 Jun 2018 06:55:33 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CF02126CC7 for ; Fri, 8 Jun 2018 06:55:33 -0700 (PDT) Date: Fri, 08 Jun 2018 06:55:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528466133; bh=QReflXg9GPDiylzb8ZC+DCP90EXH5A0W+8fwlviIXkw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZN5w8CnjDPXSEluxkS9IQZ3ZeJeO3Ha38ca+bh/jeV++JxGcsQGW22gs758DZ5yVG EQoBEDcbOC4JR1gsLFLf94FB/wo8/i0w7WPtCP/59iyOkjMyuZ1kSKT7Q1dP3RSaID Kr5S5crsHI63TB+G76tLVLjmU9jfRfEqWWszZAJ4= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a8ad57f15_7ab32ae3f0a24f50117830"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 13:55:36 -0000 ----==_mimepart_5b1a8ad57f15_7ab32ae3f0a24f50117830 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't think connection ID is special. Anything that is a protocol error is in the same boat. E.g. MUST discard the rest of the datagram, and MAY discard the entire datagram. Assuming pre-handshake. Post handshake it would be a protocol violation error with connection close. -- 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/1423#issuecomment-395768194 ----==_mimepart_5b1a8ad57f15_7ab32ae3f0a24f50117830 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I don't think connection ID is special. Anything that is a protocol er= ror is in the same boat. E.g. MUST discard the rest of the datagram, and = MAY discard the entire datagram. Assuming pre-handshake. Post handshake i= t would be a protocol violation error with connection close.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1a8ad57f15_7ab32ae3f0a24f50117830-- From nobody Fri Jun 8 06:59:01 2018 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 3D740130EAF for ; Fri, 8 Jun 2018 06:59:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 Ev_cCJaDkAZi for ; Fri, 8 Jun 2018 06:58:58 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 2E70E126CC7 for ; Fri, 8 Jun 2018 06:58:58 -0700 (PDT) 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=wm7tMdg5n29RTJWHj2kbDddVDHw=; b=ozoBfpxHUnC+3lqx 4EPcF7tx7YnAIRwVUE3IMQdTLwnMF8vrAGi6YMCjqfyNHe7jSIiq57IS3fSilFUP tKzs/wgj11vHrEAMNIOpPGj2QB54XlvcGZkrMhmjhofvkpYjoaiZJOWtvLym0Goc y8k/aDwDVCx0eJscKAiOzTUJmkE= Received: by filter0113p1iad2.sendgrid.net with SMTP id filter0113p1iad2-13491-5B1A8BA1-F 2018-06-08 13:58:57.27820528 +0000 UTC Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id k7x4hILfQRiksE6fa72UBw for ; Fri, 08 Jun 2018 13:58:57.176 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id 28BA4C132B for ; Fri, 8 Jun 2018 06:58:57 -0700 (PDT) Date: Fri, 08 Jun 2018 13:58:57 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a8ba126c0b_12a82ae01f73af588200"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0nOU8/kb7AnS3m50w+KDZw+vWXrEoNd4ZKY+ sz027L9RWqnjXLFcw/5aM6Wh50h7+XbhzKDbSC2n0Vy5XwOj78xkbs0y//N3vkTkaQFZz56nsqV+uk 618RDEftWMsT25ki8o+IzeCz61lcL5Kp9BViU3EpycCZN8qVA9vHoA9+VcwDSdzR4Wj8ryq+bWqPqt M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 13:59:01 -0000 ----==_mimepart_5b1a8ba126c0b_12a82ae01f73af588200 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Funny. @janaiyengar was a strong proponent of the current design and argued against this approach when I suggested it. I was convinced by that argument, and remain so. Creating 4 of each type is a little unwieldy. Worse when you consider that a server can never send 0x13 and a client can never send 0x12. It isn't any more complicated to implement, but it isn't without costs. Mostly, it is the secondary things that matter here. When you are debugging, you need extra information to distinguish between stream 2 and stream 2 and stream 2 and stream 2. Talking about streams requires that you are more explicit. Yeah, it fixes the problem where people say N+1 and mean N+4, but is it really that useful a change? Also, it ruins suggestions I made regarding PRIORITY, but that's not that important :) -- 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/1431#pullrequestreview-127172177 ----==_mimepart_5b1a8ba126c0b_12a82ae01f73af588200 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Funny. @janaiyengar was a strong proponent of the current design and argued against this approach when I suggested it. I was convinced by that argument, and remain so.

Creating 4 of each type is a little unwieldy. Worse when you consider that a server can never send 0x13 and a client can never send 0x12. It isn't any more complicated to implement, but it isn't without costs.

Mostly, it is the secondary things that matter here. When you are debugging, you need extra information to distinguish between stream 2 and stream 2 and stream 2 and stream 2. Talking about streams requires that you are more explicit. Yeah, it fixes the problem where people say N+1 and mean N+4, but is it really that useful a change?

Also, it ruins suggestions I made regarding PRIORITY, but that's not that important :)

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

----==_mimepart_5b1a8ba126c0b_12a82ae01f73af588200-- From nobody Fri Jun 8 07:25:52 2018 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 78434130EBF for ; Fri, 8 Jun 2018 07:25:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pHMZlV7TVgdm for ; Fri, 8 Jun 2018 07:25:48 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CE7F130EB7 for ; Fri, 8 Jun 2018 07:25:48 -0700 (PDT) Date: Fri, 08 Jun 2018 07:25:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528467947; bh=hKFA9QMyl9nBpOrszz8/t6D+9DgFdypx7DodCb/lZZg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Uhk2qxU/z2Ih7fdjQ5zUc6GCNG5AHOEAMfaDTrOS2YLVrdsB23U0hL6GMkRstZ0T3 E/q9DxidFELxoY7+FQRxZLS9GQw2ETeFixpex2MxkwZllAz90y/S98Gcav98maq7Uf fGIQm4kUH8apfz84tZy8wX2V4xacjBSrYh5vfNNY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a91eb9754b_7def2aaab3f0ef501324e8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 14:25:51 -0000 ----==_mimepart_5b1a91eb9754b_7def2aaab3f0ef501324e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit For debugging and documentation, the streams could be designated a suffix like stream 2bc, stream 2uc, stream 2bs, and stream 2us. This is far easier than the stream 2, 3, 4, 5 which says little about context. -- 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/1431#issuecomment-395777394 ----==_mimepart_5b1a91eb9754b_7def2aaab3f0ef501324e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

For debugging and documentation, the streams could be designated a suffix like stream 2bc, stream 2uc, stream 2bs, and stream 2us. This is far easier than the stream 2, 3, 4, 5 which says little about context.

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

----==_mimepart_5b1a91eb9754b_7def2aaab3f0ef501324e8-- From nobody Fri Jun 8 07:36:22 2018 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 DEF31130EDA for ; Fri, 8 Jun 2018 07:36:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lnWREZr1D1SQ for ; Fri, 8 Jun 2018 07:36:06 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9652130F0F for ; Fri, 8 Jun 2018 07:36:05 -0700 (PDT) Date: Fri, 08 Jun 2018 07:36:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528468565; bh=7QrgbAQoGn2qY3XeJJFJSBq++WAOA0PN4cqlPKvMu4U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FKWnEI7yd0lWaWuifuJs3+KYGXlAkNbzKXqvxigTLT4U/4anPOfT06xPKIqSsjjA6 t/a5BFw5myU56fzfEp+K4Kh3MQ86KbEbDdnCP5LNySa8q5JHiPrcnENlj+B0m8N/u+ sILQ1iAOo1y/3nYJbJbABKpi4g5vXRPwKHbXqsew= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a945515c96_65042ac2c4944f60103763"; 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.26 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: Fri, 08 Jun 2018 14:36:20 -0000 ----==_mimepart_5b1a945515c96_65042ac2c4944f60103763 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The debugging aspect is mitigated if you stick the type in the top two bits of a 64-bit integer locally. So you'd see 0x00000002, 0x40000002, 0x80000002, or 0xc0000002. Or you'd output with a prefix, e.g. CU2, SB2, etc. But you can't encode that way on the wire, or only one of the types can be less than 4 bytes. Yeah, I thought about trying to condense it to three types per frame, where one of them means "the only unidirectional stream I could be talking about" and the interpretation varies based on who's sending it. It's only a step further than the two-type frames that imply directionality based on the sender and only provide bi/uni in a bit. But I feel like the cost in consistent representation outweighed saving the frame types. We already have the language that says you need to reject a frame that talks about a stream the sender isn't allowed to talk about, so that's no worse, even if no better. How does it ruin PRIORITY again? -- 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/1431#issuecomment-395780478 ----==_mimepart_5b1a945515c96_65042ac2c4944f60103763 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The debugging aspect is mitigated if you stick the type in the top two= bits of a 64-bit integer locally. So you'd see 0x00000002, 0x40000002, = 0x80000002, or 0xc0000002. Or you'd output with a prefix, e.g. CU2, SB2,= etc. But you can't encode that way on the wire, or only one of the type= s can be less than 4 bytes.

Yeah, I thought about trying to condense it to three types per frame, = where one of them means "the only unidirectional stream I could be talkin= g about" and the interpretation varies based on who's sending it. It's o= nly a step further than the two-type frames that imply directionality bas= ed on the sender and only provide bi/uni in a bit. But I feel like the c= ost in consistent representation outweighed saving the frame types. We a= lready have the language that says you need to reject a frame that talks = about a stream the sender isn't allowed to talk about, so that's no worse= , even if no better.

How does it ruin PRIORITY again?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1a945515c96_65042ac2c4944f60103763-- From nobody Fri Jun 8 07:39:52 2018 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 798E7130EF4 for ; Fri, 8 Jun 2018 07:39:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 f9umJRxlxcgS for ; Fri, 8 Jun 2018 07:39:40 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB38D130F02 for ; Fri, 8 Jun 2018 07:39:38 -0700 (PDT) Date: Fri, 08 Jun 2018 07:39:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528468777; bh=HI05o5PVQD7zASgNj8K1Si4Rz801sreBB7y9UMAsFZ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=f+VYVvitQx3ZHk2zWHnIXwwkD7trFZCKCn6u9T2ib4Kht35Wlh44c3JO7CZkCS8Lb gdTlzUsT9TU3tTseTUw5Z0lJxliGREAkMXV6mDiCqs2gzP45YH7ldrksy6c1C1AR0m 4ciwpx94rxTRARnBcM/URI4kKznrHuqlA3s7eYwg= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a9529cd92a_62543f92f1dc6f7c5384d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 08 Jun 2018 14:39:50 -0000 ----==_mimepart_5b1a9529cd92a_62543f92f1dc6f7c5384d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. e60cc8f Adding security consideration around ECN into transport. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/345f593a92e4455989ada8ff7029e3935f5696d8..e60cc8fed8dc5b1d5d819b3ae3013715fcbbda5f ----==_mimepart_5b1a9529cd92a_62543f92f1dc6f7c5384d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • e60cc8f Adding security consideration around ECN into transport.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1a9529cd92a_62543f92f1dc6f7c5384d-- From nobody Fri Jun 8 09:01:35 2018 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 323AD130F0E for ; Fri, 8 Jun 2018 09:01:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.606 X-Spam-Level: X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 5Pu_Q1mRrvKt for ; Fri, 8 Jun 2018 09:01:15 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 AD865130F50 for ; Fri, 8 Jun 2018 09:01:15 -0700 (PDT) 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=7vMl/qUiJPH6UO9pEfUHFhjhCmU=; b=CYsbTJYO5LtpuXKP wVd+WIWuUhyv4JcMi9pQQYpCLA2NUA0tcOuB006Vvw+1B/30xpj+cNaImVZ+SRDa /wadxTye9munavXATYSYqTppGEyGLqis5tBzKC8wWg8XQqk+Hr0DGVn3jxHHogRj NAGPfelSjylXClhmdF/KWYfLIws= Received: by filter0261p1iad2.sendgrid.net with SMTP id filter0261p1iad2-3807-5B1AA84A-4 2018-06-08 16:01:14.186923753 +0000 UTC Received: from github-lowworker-fc273f0.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id HLj-Qog7R2CTm14IiPnFkA for ; Fri, 08 Jun 2018 16:01:14.057 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-fc273f0.cp1-iad.github.net (Postfix) with ESMTP id 0BA81C12ED for ; Fri, 8 Jun 2018 09:01:14 -0700 (PDT) Date: Fri, 08 Jun 2018 16:01:14 +0000 (UTC) From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move Draft Version Identification section (#1427) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1aa84aa037_16822ad00f482f60243613"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2eMX1kNHu1lcwHwG4vSn81p6WkNTtvbYIwEI JyxXRMFjWfStSBM7H0PzINukzaENacMrmgoL+Zfn9jAMDGWoQqYJJ85F6BeImeeVNPOf8qoxW8ZGB7 +labVxHAdDTkJYmM3XUmc8fpAtdlm5gkUqNZfJhFGaJa2PF/LXg7W00wtDNulSDJ3ZGH2t9ZEurbW1 A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 16:01:34 -0000 ----==_mimepart_5b1aa84aa037_16822ad00f482f60243613 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit LPardue approved this pull request. -- 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/1427#pullrequestreview-127221387 ----==_mimepart_5b1aa84aa037_16822ad00f482f60243613 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue approved this pull request.

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

----==_mimepart_5b1aa84aa037_16822ad00f482f60243613-- From nobody Fri Jun 8 13:30:47 2018 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 8DE8A131024 for ; Fri, 8 Jun 2018 13:30:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 9MOfT1xMumws for ; Fri, 8 Jun 2018 13:30:43 -0700 (PDT) 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 78FA2130FCB for ; Fri, 8 Jun 2018 13:30:43 -0700 (PDT) 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=DGt277t91h6bVbcyAei5ZBW17hw=; b=sGaeoA7kIRChORJz iQToL7nVvRYPX7Xhilc8jLClaWCA/QSvi1TCT8UIwFSbg9u65u2qvc3r3tGmcWYx JyDyajGamaz7bN2aJ3yBkcIfl4+YCP8H3iaqiT732Ack1Q4W8dp18Px/5pCq0rjp dZH4NN9L0yTTlWLWt5lLlXvw+M8= Received: by filter0344p1iad2.sendgrid.net with SMTP id filter0344p1iad2-25062-5B1AE771-2A 2018-06-08 20:30:41.76278911 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id 2PBqRDr9TbC7Rtott7v-sw for ; Fri, 08 Jun 2018 20:30:41.738 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id B23D6C1A10 for ; Fri, 8 Jun 2018 13:30:41 -0700 (PDT) Date: Fri, 08 Jun 2018 20:30:41 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream 0 DT proposal conflicts with PRIORITY (#1421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ae771b0ad2_4e782abfabf7af54242121"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0rt3fBXx7fWpQ/1S/11E8xQ2Np7mtQhYEVJS wFL/k04zY4jEYmShKdF/BP4/LGCmujhM2772aF6n91uDnFt9kNAxC+6zJcrrGQyza7QQiKKFtJB/M/ g9THJLkOvpsVU+h6SCiVvS8zQ6Kk1DhQJARLxsCEIDV/qQyVtBA8O/iOp3Ue4QXHhO9vvM4SeO14Kt E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 08 Jun 2018 20:30:46 -0000 ----==_mimepart_5b1ae771b0ad2_4e782abfabf7af54242121 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Or/And we can start stream IDs at 1. -- 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/1421#issuecomment-395881547 ----==_mimepart_5b1ae771b0ad2_4e782abfabf7af54242121 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Or/And we can start stream IDs at 1.

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

----==_mimepart_5b1ae771b0ad2_4e782abfabf7af54242121-- From nobody Fri Jun 8 13:46:53 2018 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 A9939130DC7 for ; Fri, 8 Jun 2018 13:46:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 LZbAVnvLUtfm for ; Fri, 8 Jun 2018 13:46:50 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC22C12F1A5 for ; Fri, 8 Jun 2018 13:46:49 -0700 (PDT) Date: Fri, 08 Jun 2018 13:46:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528490809; bh=rajjHgHRETogGOGvZ0QI34Yd6FjURtTNyAyTCO+Nvq4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=umK8AfW+aatU4al9ZIkVCUKBedd3yv8P9ckh4jytpcVcJJKEvxE9WAEgY+0BGtxbr +q7muohocOd6VZ4bQwm3qAYot9Mhz2gLaChMBnd4PspywrzWbiepibS1U0yaDKN1ck 77Gz1vpPR9p/bezOabgDhRlQVuG8GIufTqVh9rUY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream 0 DT proposal conflicts with PRIORITY (#1421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1aeb38f2a33_42dd3fc0eead2f8471775"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 08 Jun 2018 20:46:52 -0000 ----==_mimepart_5b1aeb38f2a33_42dd3fc0eead2f8471775 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit if SID >= 1 at http level, that would be require handling stream 0 actually being used. If enforced at transport layer then max stream ID = 0 as default suddenly enables not allowing any streams without resorting to stream counts in TP. That could be a good thing. -- 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/1421#issuecomment-395885453 ----==_mimepart_5b1aeb38f2a33_42dd3fc0eead2f8471775 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

if SID >= 1 at http level, that would be require handling stream 0 actually being used.

If enforced at transport layer then max stream ID = 0 as default suddenly enables not allowing any streams without resorting to stream counts in TP. That could be a good thing.

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

----==_mimepart_5b1aeb38f2a33_42dd3fc0eead2f8471775-- From nobody Fri Jun 8 23:42:21 2018 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 E18F21310D7 for ; Fri, 8 Jun 2018 23:42:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cThX2s41O26w for ; Fri, 8 Jun 2018 23:42:17 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C56C130DEF for ; Fri, 8 Jun 2018 23:42:17 -0700 (PDT) Date: Fri, 08 Jun 2018 23:42:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528526536; bh=WvIj8XsdtEIrb2t5k3fz8CAyVYQHq8HbdNgTR1ny+Rw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ejKzhHbsF8Q7quaoeCg6ipHQ+68+H+tkMswTFdqcWhDHtpiMB8n4/MLgCkzzrOGAW TN8cC6Juk3dKjsKuTGonZzV/k8j93guwqBs7cLGp2wO1jWSP0dZHKs32kQ0AFyezQX tWUnfk2dclVlBatZvnjjyplwS8h3KOCxGMb1yMAU= From: Daiki AMINAKA Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] fix typo (#1433) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1b76c8120dc_6b6f2aaf1c368f58178bc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ami-GS 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.26 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: Sat, 09 Jun 2018 06:42:19 -0000 ----==_mimepart_5b1b76c8120dc_6b6f2aaf1c368f58178bc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1433 -- Commit Summary -- * fix typo -- File Changes -- M draft-ietf-quic-transport.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1433.patch https://github.com/quicwg/base-drafts/pull/1433.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/1433 ----==_mimepart_5b1b76c8120dc_6b6f2aaf1c368f58178bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • fix typo

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 mute the thread.

----==_mimepart_5b1b76c8120dc_6b6f2aaf1c368f58178bc-- From nobody Sat Jun 9 05:15:19 2018 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 A642C130E62 for ; Sat, 9 Jun 2018 05:15:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.109 X-Spam-Level: X-Spam-Status: No, score=-6.109 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, 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 Y-SZz6087XiX for ; Sat, 9 Jun 2018 05:15:15 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39108130E5E for ; Sat, 9 Jun 2018 05:15:15 -0700 (PDT) Date: Sat, 09 Jun 2018 05:15:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528546513; bh=aEM4buDnKYz/t136XZqGO0Q0b6FGjhlH7VKCF9YLmIs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QA20KnAJWW6G9Fb941gKVVsqN3krKcIiDMAgcLeZtw3UbpiXknEtaYRuW85EPs+wm Ay3ujAs7qVvfdQxPX7zYNg6F76XOxnKkk4ub0jrPjnZaNjlZmIM6FlCspD8xh0il1a jE5NOEA9kVR/wTY022zTrLwArlIA7Vzg8DYqedeY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bc4d1d26b3_30452b08a3066f542947ac"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 12:15:17 -0000 ----==_mimepart_5b1bc4d1d26b3_30452b08a3066f542947ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Having the extra space turns out to be handy: https://github.com/quicwg/base-drafts/pull/1422#pullrequestreview-127164641 -- 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/1431#issuecomment-395964810 ----==_mimepart_5b1bc4d1d26b3_30452b08a3066f542947ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Having the extra space turns out to be handy: #1422 (review)

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

----==_mimepart_5b1bc4d1d26b3_30452b08a3066f542947ac-- From nobody Sat Jun 9 05:17:17 2018 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 15079130E62 for ; Sat, 9 Jun 2018 05:17:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zh9tBEM0Q15e for ; Sat, 9 Jun 2018 05:17:13 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADAC5130E5E for ; Sat, 9 Jun 2018 05:17:13 -0700 (PDT) Date: Sat, 09 Jun 2018 05:17:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528546632; bh=ivfMqEzU3afvu3AdgQldkvKDHoWt1YpvXBmGTpuUfQU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DEmcBIYWVssIQwmbeCMz5/5oPr96uH5EP3uic8XmUmxZKFpOMlgj8uH54VJDkz8ba BijmaRUZFGRSn2u8ELClUgKtn19N6cB87uHx0YT163dgrJTo6KXYHAZPwR8alN2Ycj 57vXzcXe5hEMeBPq9BVKETJQU/Z2GkxJtz797HkQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move Draft Version Identification section (#1427) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bc548b866c_46243f97cabccf7c936dc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 12:17:15 -0000 ----==_mimepart_5b1bc548b866c_46243f97cabccf7c936dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson approved this pull request. -- 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/1427#pullrequestreview-127364362 ----==_mimepart_5b1bc548b866c_46243f97cabccf7c936dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

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

----==_mimepart_5b1bc548b866c_46243f97cabccf7c936dc-- From nobody Sat Jun 9 05:18:23 2018 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 7D145130E63 for ; Sat, 9 Jun 2018 05:18:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.7 X-Spam-Level: * X-Spam-Status: No, score=1.7 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 itf49XCFIoeb for ; Sat, 9 Jun 2018 05:18:20 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 1D029130E5E for ; Sat, 9 Jun 2018 05:18:20 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528546699; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ly+4EFnd8a93plYHwZOW+6HprTlG2nqDsb0EyRyVzs8=; b=uTESHp9N2kglr9HR7QeNpo1tTO/iKz1aQPmIUXwd/CJQQPOGbqn57PjC4NXTTXEWy+BhzroJ sl8w0mkE3oG/So5Sah/SIPRvsp7/tsSRGJ5yJIpgSP+HRke8nnWT+5ApRB38rDtRiv1PTsiw LuPHYDM2X/5xiQB5Qq3I2So6h/w= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b1bc58b.7fb3a8e3ab40-smtp-out-n03; Sat, 09 Jun 2018 12:18:19 -0000 (UTC) Date: Sat, 09 Jun 2018 05:18:18 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b1bc58aca38d_29522b0a53325c0c5004a@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b62dc7: fix typo Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1bc58ac9e71_29522b0a53325c0c49993"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Sat, 09 Jun 2018 12:18:22 -0000 ----==_mimepart_5b1bc58ac9e71_29522b0a53325c0c49993 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: b62dc737a7f56590d414104bf92122caf7252036 https://github.com/quicwg/base-drafts/commit/b62dc737a7f56590d414104bf92122caf7252036 Author: ami-GS <1991.daiki@gmail.com> Date: 2018-06-09 (Sat, 09 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- fix typo Commit: 0df29f755ec6e1a525d35655b18819f41ce044bd https://github.com/quicwg/base-drafts/commit/0df29f755ec6e1a525d35655b18819f41ce044bd Author: Martin Thomson Date: 2018-06-09 (Sat, 09 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1433 from ami-GS/typo fix typo Compare: https://github.com/quicwg/base-drafts/compare/3a154be781a6...0df29f755ec6 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1bc58ac9e71_29522b0a53325c0c49993-- From nobody Sat Jun 9 05:18:29 2018 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 2DBEA130E5E for ; Sat, 9 Jun 2018 05:18:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.108 X-Spam-Level: X-Spam-Status: No, score=-6.108 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xIJ71kZddzTY for ; Sat, 9 Jun 2018 05:18:22 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A7E130E62 for ; Sat, 9 Jun 2018 05:18:21 -0700 (PDT) Date: Sat, 09 Jun 2018 05:18:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528546701; bh=H5jpPQ6KpXveSCNnsFvNirUnjR4yH61s8EFlwLHgjlU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0NwPWPB7iQCNOZwS1I8YylKk2i1NvJD6LOIf7aI9ycTESAJfUs1dznaPwzjF6YCiJ JdscDXRnV/e0zOiid8ZyjB6nZNu8jUZCbjqy5eCLK8Y7vQHjuctT+ncRzh1WFMx5Zr ATpI13KtjVJgU1aITzXTC89ZaTRHvrmjeByoYh20= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] fix typo (#1433) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bc58d242e3_3d5f3fd1fe25ef803955d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 12:18:23 -0000 ----==_mimepart_5b1bc58d242e3_3d5f3fd1fe25ef803955d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1433. -- 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/1433#event-1672229196 ----==_mimepart_5b1bc58d242e3_3d5f3fd1fe25ef803955d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1433.

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

----==_mimepart_5b1bc58d242e3_3d5f3fd1fe25ef803955d-- From nobody Sat Jun 9 05:20:38 2018 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 7407C130E6B for ; Sat, 9 Jun 2018 05:20:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.108 X-Spam-Level: X-Spam-Status: No, score=-6.108 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AAPUF-s2yG2V for ; Sat, 9 Jun 2018 05:20:34 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9574130E62 for ; Sat, 9 Jun 2018 05:20:33 -0700 (PDT) Date: Sat, 09 Jun 2018 05:20:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528546833; bh=b8EZPnRRC3MuIy2LKREH2vo3bxXISJfSRSHtAo+l66s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z4A7+XGU3KBg5N4ADKfWXlFaiQTGBaR3nlSaNtFnkMOrspRpnQ48RIIUNZsASmgSR 1H/jBBRbn26+skU9IgcUFuPJx2cmK1II/9LFxZCpKQfv82ChlYMF35qFaPBt0TM7yV JsTh1M3R1ouV211ou93cM0IwaZCj2CfXVesTgtH4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HoLB from NCID frames (#1280) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bc6111aab3_31953fdd996c6f7c4176f4"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 12:20:36 -0000 ----==_mimepart_5b1bc6111aab3_31953fdd996c6f7c4176f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1280 via #1419. -- 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/1280#event-1672229840 ----==_mimepart_5b1bc6111aab3_31953fdd996c6f7c4176f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1280 via #1419.

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

----==_mimepart_5b1bc6111aab3_31953fdd996c6f7c4176f4-- From nobody Sat Jun 9 05:20:42 2018 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 94048130E62 for ; Sat, 9 Jun 2018 05:20:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.108 X-Spam-Level: X-Spam-Status: No, score=-6.108 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EdGt05gj65mB for ; Sat, 9 Jun 2018 05:20:34 -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 1775A130E6A for ; Sat, 9 Jun 2018 05:20:34 -0700 (PDT) Date: Sat, 09 Jun 2018 05:20:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528546833; bh=cn6GEJ0V2808xs/Poo42iOBgXjkrxAddZgHyfzAdI/4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Fq359uC1aB48cAyd1BL9JeuyvqpYRDVFtanEpwc2BhjtRppSdKNZK17UW7ghY4F/C 8JYzMW03s/+jFo2afPU2Qf7evf17Teo3uOYyYe5MaojsMrNLY8Leo24OWgeUu2YVs2 cKpJ4zwYQXn5InJFGuZZqgXiVExhY67wIxhIbL28= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove sequence number from NEW_CONNECTION_ID (#1419) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bc6113e21a_1eee2ad78c4c0f5c4039e9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 12:20:37 -0000 ----==_mimepart_5b1bc6113e21a_1eee2ad78c4c0f5c4039e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1419. -- 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/1419#event-1672229838 ----==_mimepart_5b1bc6113e21a_1eee2ad78c4c0f5c4039e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1419.

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

----==_mimepart_5b1bc6113e21a_1eee2ad78c4c0f5c4039e9-- From nobody Sat Jun 9 05:30:35 2018 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 498D8130E6A for ; Sat, 9 Jun 2018 05:30:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.7 X-Spam-Level: * X-Spam-Status: No, score=1.7 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 GGa1r19NK5Mz for ; Sat, 9 Jun 2018 05:30:32 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 D9B41130E62 for ; Sat, 9 Jun 2018 05:30:31 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528547431; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=AusmclyEaaaESMr4YijOGYR7bXB1JgBB8kNffCwnzKw=; b=qWH6/WC67Jdk2EU4/KIjuk2yoUNamq/RynP0dPIMwM3gi0GLJhcfeuFbZh470xpmzdHnlS4x wFyzUZCEGNs02XFBqZCt2tNAOo3goTDyHONOWuSuE4zuoPoIg9L9d8NzkeMT7insbgOi8/7L EuYZyz3qbgXGK6ndMGNNkppy4fI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b1bc60f.7f6c280208d0-smtp-out-n01; Sat, 09 Jun 2018 12:20:31 -0000 (UTC) Date: Sat, 09 Jun 2018 05:20:30 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b1bc60e14682_317b2acbd3f7bc1830657@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 2eee0d: Remove sequence number from NEW_CONNECTION_ID Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1bc60e141bb_317b2acbd3f7bc18305ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Sat, 09 Jun 2018 12:30:34 -0000 ----==_mimepart_5b1bc60e141bb_317b2acbd3f7bc18305ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6 https://github.com/quicwg/base-drafts/commit/2eee0d82ee9557a79a888dcf4097ce0c8e70ece6 Author: Martin Thomson Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove sequence number from NEW_CONNECTION_ID Closes #1280. Commit: ef2caa70addfe0c1fcbe95bcf33322bf2d80c1ad https://github.com/quicwg/base-drafts/commit/ef2caa70addfe0c1fcbe95bcf33322bf2d80c1ad Author: Martin Thomson Date: 2018-06-09 (Sat, 09 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1419 from quicwg/NCID-seq Remove sequence number from NEW_CONNECTION_ID Compare: https://github.com/quicwg/base-drafts/compare/0df29f755ec6...ef2caa70addf **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1bc60e141bb_317b2acbd3f7bc18305ef-- From nobody Sat Jun 9 05:45:52 2018 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 9136B130E6C for ; Sat, 9 Jun 2018 05:45:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.7 X-Spam-Level: * X-Spam-Status: No, score=1.7 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 z3kzbN7PaQGy for ; Sat, 9 Jun 2018 05:45:49 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 53D3A129C6B for ; Sat, 9 Jun 2018 05:45:49 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528548348; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=3tQwptQObuv5adxn/HpkC+qlb6cqZ0DZIA5q4luFzYk=; b=fzOupFBm5Zg0+FsMaYvz0Wu8wAHV1nr+SBRHMM59BsVudRh7pqDZvjQY9Enp8crggrrjnML0 SJGsXsRWOYaGez40lV5pjlDG8eFSlO+ShlZfWh5JUaV84Ig141R/aqkKmFeEXEiT+5YbM152 4l9FUQUTupB8mloG0I65LrOlcMs= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b1bc61f.7f6b3bf32180-smtp-out-n01; Sat, 09 Jun 2018 12:20:47 -0000 (UTC) Date: Sat, 09 Jun 2018 05:20:46 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b1bc61ea5cc7_375a2b1c62ddbc0c38713@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1bc61ea5829_375a2b1c62ddbc0c3862f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Sat, 09 Jun 2018 12:45:51 -0000 ----==_mimepart_5b1bc61ea5829_375a2b1c62ddbc0c3862f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/NCID-seq Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1bc61ea5829_375a2b1c62ddbc0c3862f-- From nobody Sat Jun 9 07:21:00 2018 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 B773A130E5A for ; Sat, 9 Jun 2018 07:20:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.109 X-Spam-Level: X-Spam-Status: No, score=-6.109 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, 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 u_HlycicTzkF for ; Sat, 9 Jun 2018 07:20:57 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F92E130E39 for ; Sat, 9 Jun 2018 07:20:57 -0700 (PDT) Date: Sat, 09 Jun 2018 07:20:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528554056; bh=28GYLEQc9znzSCh8G6SlxVt2NUcjDIdH132cK0JYxF4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=orfYNv28pSgqmo7PdzZNAwEtT6OmXL9J//QVDswxyhiiDgfdMXShJJOY1EV6stTgi ehWl97k7AaiPGBFsYnbb+x2iWEvlMAFNb8BqhVvObSVAmieVb9cklNpdxjf38o6N6d 1naLAzHJW5jI+0P0owTF7NhFZKiiW1rJ0+SFnUj8= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1be248bdaaa_3add3fe41377af88126937"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sat, 09 Jun 2018 14:20:59 -0000 ----==_mimepart_5b1be248bdaaa_3add3fe41377af88126937 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thinking through this further, I think unidirectional streams *need* to be typed, otherwise you severely limit the use of non-reserved stream IDs. Without this change, the early streams are reserved for control and QPACK. All other server-initated unidirectional streams effectively end up belonging to Server Push. The first byte will attempt to be parsed as a Push ID, and probably pass! This prohibits my unbound server push extension, which would like to send PUSH_PROMISE frames on server-initiated streams. -- 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/1359#issuecomment-395972975 ----==_mimepart_5b1be248bdaaa_3add3fe41377af88126937 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thinking through this further, I think unidirectional streams need= to be typed, otherwise you severely limit the use of non-reserved s= tream IDs.

Without this change, the early streams are reserved for control and QP= ACK. All other server-initated unidirectional streams effectively end up = belonging to Server Push. The first byte will attempt to be parsed as a P= ush ID, and probably pass! This prohibits my unbound server push extensio= n, which would like to send PUSH_PROMISE frames on server-initiated strea= ms.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1be248bdaaa_3add3fe41377af88126937-- From nobody Sat Jun 9 08:54:17 2018 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 8880D130EAF for ; Sat, 9 Jun 2018 08:54:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.383 X-Spam-Level: X-Spam-Status: No, score=-5.383 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cA5UsqgfiWAi for ; Sat, 9 Jun 2018 08:54:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB42C126DBF for ; Sat, 9 Jun 2018 08:54:13 -0700 (PDT) Date: Sat, 09 Jun 2018 08:54:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528559652; bh=D+NujS1nkHPr5h4z7jW3vkJfVgPYxZYByPt6RFVaYsc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rgeSa5/9DFHv9P+Rmcj2BIY0tsfvPxq8x7wl5Qx1wtz97eYz2s7OybkyHhpS0acL9 ANTJT5nPcevmBJn8QTGCFgB196mjx/L3FcC6nTVGZV/KcqSWvhewpshes6RXnhpE3O tjPLZ1JcBWvURz7ib+FE8I0bbUUOVQVCuFoqSqFw= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bf824df2ef_196b2addcfd06f60403846"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Sat, 09 Jun 2018 15:54:16 -0000 ----==_mimepart_5b1bf824df2ef_196b2addcfd06f60403846 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. -- 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/1411#pullrequestreview-127371158 ----==_mimepart_5b1bf824df2ef_196b2addcfd06f60403846 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

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

----==_mimepart_5b1bf824df2ef_196b2addcfd06f60403846-- From nobody Sat Jun 9 09:13:04 2018 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 AB18E130E8D for ; Sat, 9 Jun 2018 09:13:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.109 X-Spam-Level: X-Spam-Status: No, score=-6.109 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, 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 dR2CFgbIHsZz for ; Sat, 9 Jun 2018 09:13:00 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FB2112426A for ; Sat, 9 Jun 2018 09:13:00 -0700 (PDT) Date: Sat, 09 Jun 2018 09:12:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528560779; bh=KiMibrkUE7vs6oqUWX4LyGhXtZrNCehxkW5rV16puPY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jmT8gUIvd1/eguK4EWMpIg5o7bFu9qqXAGLr8A9MyFC3pfqvDw0BI/HmuUfTucXky hPq2QqI8NMnGIl+ukBrs2BGAggmDbYZwqEbPp2Dj1R5wun5s275w65A9ZG55/Z9K2W a+mUczTtuA6sHgKJWYOhh8pGdjQiD1Z/ru+btgRE= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bfc8b8111b_521b3ff017378f88628bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Sat, 09 Jun 2018 16:13:02 -0000 ----==_mimepart_5b1bfc8b8111b_521b3ff017378f88628bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. This looks good, but I'd like someone who's more of an expert in ICMP to read it, so I'm adding @martinduke > @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain application data, aggressive increases in probe size carry fewer consequences. +## Responding to ICMP "Unreachable" messages {#icmp-unreach} + +When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake, +the response SHOULD be identical to receiving an ICMP TPB message that announces +a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}). + +When an ICMP "Unreachable" message is received after the handshake, the QUIC +endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}). Sending +PATH_CHALLENGE frames on the same path due to ICMP "Unreachable" messages should +be rate limited. To what? How about one outstanding PATH_CHALLENGE at once? > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by this endpoint with at least 1-2^32 +probability and it is still outstanding (not acknowledged and not deemed lost). +If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the +packet as an ICMP message without an on-path proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. + +Even ICMP messages without an on-path proof SHOULD undergo some validation, such +as: * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that I thought we were recommending setting DF on all packets? -- 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/1412#pullrequestreview-127371213 ----==_mimepart_5b1bfc8b8111b_521b3ff017378f88628bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

This looks good, but I'd like someone who's more of an expert in ICMP to read it, so I'm adding @martinduke

In draft-ietf-quic-transport.md:

> @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain
 application data, aggressive increases in probe size carry fewer consequences.
 
 
+## Responding to ICMP "Unreachable" messages {#icmp-unreach}
+
+When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake,
+the response SHOULD be identical to receiving an ICMP TPB message that announces
+a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}).
+
+When an ICMP "Unreachable" message is received after the handshake, the QUIC
+endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}).  Sending
+PATH_CHALLENGE frames on the same path due to ICMP "Unreachable" messages should
+be rate limited.

To what? How about one outstanding PATH_CHALLENGE at once?

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by this endpoint with at least 1-2^32
+probability and it is still outstanding (not acknowledged and not deemed lost).
+If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the
+packet as an ICMP message without an on-path proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.
+
+Even ICMP messages without an on-path proof SHOULD undergo some validation, such
+as:
 
 * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that

I thought we were recommending setting DF on all packets?

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

----==_mimepart_5b1bfc8b8111b_521b3ff017378f88628bf-- From nobody Sat Jun 9 09:19:26 2018 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 868ED130EBA for ; Sat, 9 Jun 2018 09:19:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.109 X-Spam-Level: X-Spam-Status: No, score=-6.109 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, 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 3FzOgJCieDK7 for ; Sat, 9 Jun 2018 09:19:23 -0700 (PDT) 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 E476E126CB6 for ; Sat, 9 Jun 2018 09:19:22 -0700 (PDT) Date: Sat, 09 Jun 2018 09:19:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528561162; bh=HSZ7s/5waYf36yh9XWYoAYAdjk79MI18Zw6a41qvRTo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lyHZrzHB+kuvOoDzV2vW+AmB7H0y5g6INisQKlUSOzyyAzoNcnrK4ftf5F/YZHo/S lafUpTlrMllfnHJB85o7pVvmtG7xoUkURmjQ5aZAzb/kBoUpnN5WbueN4Shwhw4dKk il2oyt99fZtheVhRccWQaojbHIJJ+cNF9nW0Brr8= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1bfe0a3da49_27352aea40b78f542287b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Sat, 09 Jun 2018 16:19:25 -0000 ----==_mimepart_5b1bfe0a3da49_27352aea40b78f542287b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's interesting to see this, but I favor the current approach unless this fixes some important issue I'm unaware of. I don't think something being awkward reaches the bar of "important issue" at this point in the process. -- 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/1431#issuecomment-395981088 ----==_mimepart_5b1bfe0a3da49_27352aea40b78f542287b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It's interesting to see this, but I favor the current approach unless this fixes some important issue I'm unaware of. I don't think something being awkward reaches the bar of "important issue" at this point in the process.

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

----==_mimepart_5b1bfe0a3da49_27352aea40b78f542287b9-- From nobody Sat Jun 9 23:33:09 2018 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 C9C74130E13 for ; Sat, 9 Jun 2018 23:33:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.31 X-Spam-Level: X-Spam-Status: No, score=-5.31 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 CYB2urxklPhZ for ; Sat, 9 Jun 2018 23:33:05 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBCB6130E12 for ; Sat, 9 Jun 2018 23:33:05 -0700 (PDT) Date: Sat, 09 Jun 2018 23:33:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528612383; bh=jqWrOsnr5kvA4CCBpCM8ocNjTPgR4MhBoiI9uPj8bmU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=L2ORNWJrf6zJDi60pX9xVc5mkPyaIMch6D7eaRIyzb+mMCAn3gWKYMo9mSTOTfKEq MpLCS7XOXcXk/4AkbTyl3nyR33HRmdQj225X140M3RSDXYEa1VzZNQ/lkfvUXrGdpZ FchNLeNz6g4daXY5F8SPwkkoH5LuAt2wdrWplwJA= From: Daiki AMINAKA Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] fix typo (#1434) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1cc61f80267_657e2ad50012ef58289d9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ami-GS 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.26 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: Sun, 10 Jun 2018 06:33:08 -0000 ----==_mimepart_5b1cc61f80267_657e2ad50012ef58289d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit - "frames send the the" -> "frames send the" - adjust line length You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1434 -- Commit Summary -- * fix typo -- File Changes -- M draft-ietf-quic-transport.md (7) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1434.patch https://github.com/quicwg/base-drafts/pull/1434.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/1434 ----==_mimepart_5b1cc61f80267_657e2ad50012ef58289d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
  • "frames send the the" -> "frames send the"
  • adjust line length

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

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

Commit Summary

  • fix typo

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 mute the thread.

----==_mimepart_5b1cc61f80267_657e2ad50012ef58289d9-- From nobody Sat Jun 9 23:38:32 2018 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 0D303130E19 for ; Sat, 9 Jun 2018 23:38:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.61 X-Spam-Level: X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 2oU5v_rcDhNf for ; Sat, 9 Jun 2018 23:38:29 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 538C4130E18 for ; Sat, 9 Jun 2018 23:38:29 -0700 (PDT) Date: Sat, 09 Jun 2018 23:38:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528612708; bh=xphzUJF1+Xwd3/q5wbx+EpnnX7U8k1AXtaoTRMKY3DM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=O46Cw5hhiWaDSVRxrziEpZj0LkauAlxFtKPL+A5F9tbUWvTO1tIDRBwgjYvfXn/ID Cf3kLc3A3J47NILr1VR2qJC+zKwqja02f87hi30pzBOJXv1Dcl/epEtdzeVPmi6VdX 2WaUNEiMZIHIyn9UuqArsIIJ/eY7+/s8WapIM9Xo= From: borisPis Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet number transform should be negotiated (#1296) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1cc764b6777_9622aeeb510af58956a0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: borisPis 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.26 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: Sun, 10 Jun 2018 06:38:31 -0000 ----==_mimepart_5b1cc764b6777_9622aeeb510af58956a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From another hardware vendor's perspective. It is not only additional complexity or performance loss. QUIC will be the only protocol to require a second pass over encrypted data. It means that this hardware circuitry must be implemented exclusively for QUIC, and it is unlikely to be reused. IPsec has plaintext sequence numbers, and IPsec crypto offload in the data path increases performance by about 5x. Is there any indication of IPsec sequence numbers being ossified? I would assume that QUIC sequence numbers wouldn't be any different. -- 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/1296#issuecomment-396024817 ----==_mimepart_5b1cc764b6777_9622aeeb510af58956a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

From another hardware vendor's perspective. It is not only additional = complexity or performance loss. QUIC will be the only protocol to require= a second pass over encrypted data. It means that this hardware circuitry= must be implemented exclusively for QUIC, and it is unlikely to be reuse= d.

IPsec has plaintext sequence numbers, and IPsec crypto offload in the = data path increases performance by about 5x. Is there any indication of I= Psec sequence numbers being ossified? I would assume that QUIC sequence n= umbers wouldn't be any different.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1cc764b6777_9622aeeb510af58956a0-- From nobody Sun Jun 10 10:26:20 2018 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 F056F130EB5 for ; Sun, 10 Jun 2018 10:26:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8LPFJ1b0l6nB for ; Sun, 10 Jun 2018 10:26:16 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E33D130EA5 for ; Sun, 10 Jun 2018 10:26:15 -0700 (PDT) Date: Sun, 10 Jun 2018 10:26:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528651574; bh=hM1mWk/VOisdE6iSwF05FUcln8C5Op31t0A0EpZYNsE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1xdls12R0ZGesiafQjaY1DN+pohH2dfwUiLxuY7YHYvsm3dW8iIzEMDO9CWphYtgx fekQVnBdp/CmOdD50Z8moMWgxwPviiBWyxQOepMDS0C47JJR2PVEKofVtTsjnbwVLN geIQuZTDLAYSwEbbtEyiN6xXbvgsXGwIRUUNHN/s= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet number transform should be negotiated (#1296) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1d5f36109c_2dd22b236885af502676ec"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 10 Jun 2018 17:26:18 -0000 ----==_mimepart_5b1d5f36109c_2dd22b236885af502676ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable IPsec isn't exactly suffering problems that come with being wildly successful. PNE solves at least two problems; ossification is just one of them, linka= ge across connection migration is the other one. On Sat, Jun 9, 2018 at 11:38 PM borisPis wrote= : > From another hardware vendor's perspective. It is not only additional > complexity or performance loss. QUIC will be the only protocol to requi= re a > second pass over encrypted data. It means that this hardware circuitry = must > be implemented exclusively for QUIC, and it is unlikely to be reused. > > IPsec has plaintext sequence numbers, and IPsec crypto offload in the d= ata > path increases performance by about 5x. Is there any indication of IPse= c > sequence numbers being ossified? I would assume that QUIC sequence numb= ers > wouldn't be any different. > > =E2=80=94 > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = 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/1296#issuecomment-396066372= ----==_mimepart_5b1d5f36109c_2dd22b236885af502676ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable IPsec isn't exactly suffering problems that come with being wildly successful.
PNE solves at least two problems; ossification is just one of them, linka= ge
across connection migration is the other one.

On Sat, Jun 9, 2018 at 11:38 PM borisPis <notifications@github.com>= wrote:

> From another hardware vendor's perspective. It is not only addit= ional
> complexity or performance loss. QUIC will be the only protocol to re= quire a
> second pass over encrypted data. It means that this hardware circuit= ry must
> be implemented exclusively for QUIC, and it is unlikely to be reused= .
>
> IPsec has plaintext sequence numbers, and IPsec crypto offload in th= e data
> path increases performance by about 5x. Is there any indication of I= Psec
> sequence numbers being ossified? I would assume that QUIC sequence n= umbers
> wouldn't be any different.
>
> =E2=80=94
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1296#issuecomment-3= 96024817>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AKjg1N2sQqW6b6= EEKchUhCWVsolNLR1Xks5t7L7kgaJpZM4TY4b4>
> .
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1d5f36109c_2dd22b236885af502676ec-- From nobody Sun Jun 10 10:27:15 2018 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 26816130EB9 for ; Sun, 10 Jun 2018 10:27:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 HKbQNhqTGbkn for ; Sun, 10 Jun 2018 10:27:13 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0E51130EBA for ; Sun, 10 Jun 2018 10:27:12 -0700 (PDT) Date: Sun, 10 Jun 2018 10:27:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528651632; bh=FaFbfudnr9niuhpUegK3Rn6vOItxSz7UG6DhhG6LIKo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oULnTQVWtIJ8wqBhF4vHqxED2ILC/86T7m8XhObHxjjTUslIgP5Cz4Zr+Jt7Babxe PHf63tSn3HaJtGHFrIthF0Kn2Fo4X5V5Cq9MEcBXaoecFjfXxpNfd+JjneCGK0tyKr Fld0BRzeonNoNctOp7MjWg/QPS+pTBYJVW9a8Kiw= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] fix typo (#1434) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1d5f7034b8b_2d083fd88bd24f80169428"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 10 Jun 2018 17:27:14 -0000 ----==_mimepart_5b1d5f7034b8b_2d083fd88bd24f80169428 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1434. -- 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/1434#event-1672707097 ----==_mimepart_5b1d5f7034b8b_2d083fd88bd24f80169428 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1434.

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

----==_mimepart_5b1d5f7034b8b_2d083fd88bd24f80169428-- From nobody Sun Jun 10 10:41:01 2018 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 40042130EC5 for ; Sun, 10 Jun 2018 10:41:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FupEhTXkl6hb for ; Sun, 10 Jun 2018 10:40:58 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42D97130EB5 for ; Sun, 10 Jun 2018 10:40:58 -0700 (PDT) Date: Sun, 10 Jun 2018 10:40:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528652456; bh=iGS6xGnoD4KTA1KxbwttVORgLKMvSerl97tT5Fdy4zQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a9JkNmxaNCfLnlP6TUIcjK1FeByLHsYPziY6eHygetT0lvVLTqlpoUPbe7scccesF YNPDBS+43MOl38WiXBnYTZc003IwIwlyNws2fdMol7gC/RxzM6vqtLDYXoioZQGklO sArt0LYDGH1Byzv1ddimk7vAViIjtkF4oV4r03Hk= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1d62a89abbe_51203f8737e0af8018213c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 10 Jun 2018 17:41:01 -0000 ----==_mimepart_5b1d62a89abbe_51203f8737e0af8018213c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The receiver doesn't know the sender's congestion controller, so that recommendation is not going to be useful in practice. The receiver is usually capable of sending acks as frequently as necessary, in response to packet receive events. The sender knows how sensitive it is to the ack ratio, so it needs to suggest the max ratio. I think we need a transport param for this. -- 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/1428#issuecomment-396067343 ----==_mimepart_5b1d62a89abbe_51203f8737e0af8018213c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The receiver doesn't know the sender's congestion controller, so that = recommendation is not going to be useful in practice.

The receiver is usually capable of sending acks as frequently as neces= sary, in response to packet receive events. The sender knows how sensitiv= e it is to the ack ratio, so it needs to suggest the max ratio. I think w= e need a transport param for this.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1d62a89abbe_51203f8737e0af8018213c-- From nobody Sun Jun 10 10:46:12 2018 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 C60EA130EB8 for ; Sun, 10 Jun 2018 10:27:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.237 X-Spam-Level: X-Spam-Status: No, score=0.237 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, FROM_STARTS_WITH_NUMS=0.738, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 ZvoojLmWV07V for ; Sun, 10 Jun 2018 10:27:10 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 11245130EA5 for ; Sun, 10 Jun 2018 10:27:10 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528651629; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=qKV8NGIMijUfxiFvxHhnwjljQ0/4OSWmbQazsNYHVaA=; b=FaK1ZlVkrR6MPvg2bZtPDfyEFw0PbHADNl9HMoS7pNzUF80TV2NTSCKNEV0ebiz4vfiS7LtY bomJxNdEN+D8BpORcXYdWzlvpkcia3f2yWtSeZgnGSognECA887Qtl1SFIBcU0Tc8qhC/yFO 3ZWM1DITFo8+HJ1NlI9bDDPJbf8= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: 1991.daiki=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b1d5f6d.7fc9ab97f690-smtp-out-n01; Sun, 10 Jun 2018 17:27:09 -0000 (UTC) Date: Sun, 10 Jun 2018 10:27:09 -0700 From: Daiki AMINAKA <1991.daiki@gmail.com> Reply-To: Daiki AMINAKA <1991.daiki@gmail.com> To: quic-issues@ietf.org Message-ID: <5b1d5f6d1535b_415f2b1c6c8cdc1091913@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 7c2d24: fix typo (#1434) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1d5f6d14f19_415f2b1c6c8cdc1091815"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-Mailman-Approved-At: Sun, 10 Jun 2018 10:46:11 -0700 X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Sun, 10 Jun 2018 17:27:12 -0000 ----==_mimepart_5b1d5f6d14f19_415f2b1c6c8cdc1091815 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 7c2d2495b9fd9f3840118e1fe1ac405cf5742722 https://github.com/quicwg/base-drafts/commit/7c2d2495b9fd9f3840118e1fe1ac405cf5742722 Author: Daiki AMINAKA <1991.daiki@gmail.com> Date: 2018-06-10 (Sun, 10 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- fix typo (#1434) **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1d5f6d14f19_415f2b1c6c8cdc1091815-- From nobody Sun Jun 10 11:40:55 2018 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 3EDF8130EC9 for ; Sun, 10 Jun 2018 11:40:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 sGFFHQQ1S95n for ; Sun, 10 Jun 2018 11:40:51 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A23EC130DDE for ; Sun, 10 Jun 2018 11:40:51 -0700 (PDT) Date: Sun, 10 Jun 2018 11:40:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528656050; bh=wu9ieeaAPif9y6yWxN7CmB5nAcWxfr9dcQecRfDsm2U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QI1x3xh5FON+1pbvUB1NkWEUV4wGwadtUrSVXwrCFdTfNMf40KqMef3bCCM5sN9Dq DNcOWEWgPww4IKj+TVaj//9ijyldpXnrdbcEQPP9U+OmMwr2etP1T53pdJ5dEFnT0J DYFl9d65pr4j/vFPUUuGvzRZoEI7ZkMunbdEPeB0= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet number transform should be negotiated (#1296) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1d70b2ad502_42333fcc70c2cf782129e9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Sun, 10 Jun 2018 18:40:54 -0000 ----==_mimepart_5b1d70b2ad502_42333fcc70c2cf782129e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Connection migration cannot be incrementally deployed without changing load balancers and not all QUIC connections need migration support. So one could limit PNE to connections needing gratuitous migration by adding negotiation. Ossification is a concern and I would prefer lower cost alternatives compared to encryption if possible. That said, my main interest in adding the transport parameter is for backend connections and connections within DC with neither of these two problems exist. -- 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/1296#issuecomment-396071399 ----==_mimepart_5b1d70b2ad502_42333fcc70c2cf782129e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Connection migration cannot be incrementally deployed without changing= load balancers and not all QUIC connections need migration support. So o= ne could limit PNE to connections needing gratuitous migration by adding = negotiation. Ossification is a concern and I would prefer lower cost alte= rnatives compared to encryption if possible. That said, my main interest = in adding the transport parameter is for backend connections and connecti= ons within DC with neither of these two problems exist.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1d70b2ad502_42333fcc70c2cf782129e9-- From nobody Sun Jun 10 15:38:46 2018 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 D2B52130F03 for ; Sun, 10 Jun 2018 15:38:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 Aw7ffGpYrarh for ; Sun, 10 Jun 2018 15:38:43 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109EE127332 for ; Sun, 10 Jun 2018 15:38:43 -0700 (PDT) Date: Sun, 10 Jun 2018 15:38:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528670322; bh=yjzQ5rMm7u7tPbh8F7oJT7kYqMntCZ4sDMvgUyya7ns=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CTTjC2JaQEx0ZrKWdH/pw7W4BAHck03KgZCkLov0JlkJvbaXqjZJVdZ77YLsWh50U vn3stZm8faEw2EfPU5qitoIA/1VvWvzZeN2aFwZitTXgqFEqD8z0RSp/ErHiTGc87W ztQrGWGtAKOhNcanCsOfhMCsIb4fe2ImswBZ2abU= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1da87282ea4_2a902aacccd98f5c264bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Sun, 10 Jun 2018 22:38:45 -0000 ----==_mimepart_5b1da87282ea4_2a902aacccd98f5c264bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To clarify, my proposal is that we should document an acknowledgement approach we expect to work well with the described congestion controller, Reno. Do you think that would not be useful? If we want to add a mechanism to indicate to the receiver that acknowledging packets less frequently is ok, then as you said, we need one or more transport parameters. What transport parameter(s) do you have in mind? The two I can think of are the max number of packets newly acked at once and the interval between acks in fraction of an RTT or absolute time. The current BBR approach is very adaptive, so it doesn't need to know the details of the receiver's behavior. It's not clear to me how other congestion controllers will adapt to this, so it's not clear to me what information they need? -- 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/1428#issuecomment-396087604 ----==_mimepart_5b1da87282ea4_2a902aacccd98f5c264bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

To clarify, my proposal is that we should document an acknowledgement = approach we expect to work well with the described congestion controller,= Reno. Do you think that would not be useful?

If we want to add a mechanism to indicate to the receiver that acknowl= edging packets less frequently is ok, then as you said, we need one or mo= re transport parameters.

What transport parameter(s) do you have in mind? The two I can think o= f are the max number of packets newly acked at once and the interval betw= een acks in fraction of an RTT or absolute time. The current BBR approac= h is very adaptive, so it doesn't need to know the details of the receive= r's behavior. It's not clear to me how other congestion controllers will= adapt to this, so it's not clear to me what information they need?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1da87282ea4_2a902aacccd98f5c264bf-- From nobody Sun Jun 10 17:38:07 2018 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 7F368130DCF for ; Sun, 10 Jun 2018 17:38:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KCxCNT_C96xQ for ; Sun, 10 Jun 2018 17:38:03 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABDD130DCC for ; Sun, 10 Jun 2018 17:38:03 -0700 (PDT) Date: Sun, 10 Jun 2018 17:38:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528677482; bh=bk1ktagVJM/ZRvNAcAfjun/ty35u+LckGJc4VOBd+78=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VnlbFIZxj4veQBAxoqNg4cUeoOenl27OGkHLplDpXhQkQe3fjwCr9OfF60XeeGNJi cwSvyuwsNYnakn9x9ItZHEIwDwO2jQs+jlL40wsLE61kVo6Mm6c+vxjdpTCLintINQ ZsTRsfuNnTF+IkIsXZkcsPDwIiu6uukdvtb8KTg0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1dc46a7c0a4_66a3faa6f9bcf7c17282e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 00:38:06 -0000 ----==_mimepart_5b1dc46a7c0a4_66a3faa6f9bcf7c17282e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Connection ID could be special. Keep in mind that a datagram is routed based solely on the value of the first destination connection ID. If the first packet in the datagram contains the wrong connection ID, then I would assume that it would be OK to treat that by routing it to /dev/null. -- 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/1423#issuecomment-396094869 ----==_mimepart_5b1dc46a7c0a4_66a3faa6f9bcf7c17282e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Connection ID could be special. Keep in mind that a datagram is route= d based solely on the value of the first destination connection ID. If t= he first packet in the datagram contains the wrong connection ID, then I = would assume that it would be OK to treat that by routing it to /dev/null= .

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1dc46a7c0a4_66a3faa6f9bcf7c17282e-- From nobody Sun Jun 10 22:56:31 2018 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 09D12130EE6 for ; Sun, 10 Jun 2018 22:56:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nOhfxmNjXpHm for ; Sun, 10 Jun 2018 22:56:22 -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 10B24130EFD for ; Sun, 10 Jun 2018 22:56:22 -0700 (PDT) Date: Sun, 10 Jun 2018 22:56:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528696581; bh=Otn0WNZOdRTRvlNuzDTBxxmaZFKXLk+37jyqU1TJg9g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jWwgBnuEfJ6HKCcsrnD3iYkmYtB7R0HIVQy63zqlkFtM/tBulQQkZDRJSn3jXwd0J ojmBAyb/6o0sjGxh/PNmwD0zxy0qBSW9S+5prOV2YtGwtYLYFE6/spruzhkCVU080u OZcvLRZ8P5tS/X7uFiBzF4RYbZfvoaN36a/5WufI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e0f05fab_22663febd6998f842721cb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 05:56:25 -0000 ----==_mimepart_5b1e0f05fab_22663febd6998f842721cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That argument might be used to require typing of bidirectional streams. What do you think of that @LPardue ? -- 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/1359#issuecomment-396130143 ----==_mimepart_5b1e0f05fab_22663febd6998f842721cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

That argument might be used to require typing of bidirectional streams. What do you think of that @LPardue ?

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

----==_mimepart_5b1e0f05fab_22663febd6998f842721cb-- From nobody Mon Jun 11 01:03:47 2018 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 D0241130E15 for ; Mon, 11 Jun 2018 01:03:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rZEjLzVQzvBC for ; Mon, 11 Jun 2018 01:03:44 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B6DD130E11 for ; Mon, 11 Jun 2018 01:03:44 -0700 (PDT) Date: Mon, 11 Jun 2018 01:03:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528704223; bh=2i7OURzrPwEYr1uKmiW/vEOkpB1sSdjRYAbnjG7YGyc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q2zKpKLDFC779RUG4mqUcSAAEroqzaj/A0GPCcq0AiLJgrCPQQW1bVw22IcltNp3i C23nGPwmNUqR8sWt2V1Ni9EoELTvfJ0sXHxBDZjqaLgtiTNxnSghgiXIM3jHtong4d t2iN/FF5IlwGQNvvY6y/fyb4drrFjR8wfScCY4dU= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e2cdfc4262_1f982adb671f2f582986fd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 08:03:46 -0000 ----==_mimepart_5b1e2cdfc4262_1f982adb671f2f582986fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit For hq is think bidirectional type is not required. The prime interaction pattern is request/response and bidi suits that well. H2 sets a precedent for reserving a bidi stream for other uses via the CONNECT method, the WebSocket extension is an example in practice. So, a hq extension that needs 2-way comms could either use a pair of unidi streams, or emulate/enhance CONNECT. -- 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/1359#issuecomment-396156953 ----==_mimepart_5b1e2cdfc4262_1f982adb671f2f582986fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

For hq is think bidirectional type is not required. The prime interact= ion pattern is request/response and bidi suits that well.

H2 sets a precedent for reserving a bidi stream for other uses via the= CONNECT method, the WebSocket extension is an example in practice.

So, a hq extension that needs 2-way comms could either use a pair of u= nidi streams, or emulate/enhance CONNECT.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1e2cdfc4262_1f982adb671f2f582986fd-- From nobody Mon Jun 11 02:41:27 2018 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 14599130F59 for ; Mon, 11 Jun 2018 02:41:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 N2J9-OvJR9Yq for ; Mon, 11 Jun 2018 02:41:23 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1678130F5C for ; Mon, 11 Jun 2018 02:41:23 -0700 (PDT) Date: Mon, 11 Jun 2018 02:41:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528710081; bh=pACJi1t/pYwZQ4i3Tt0qBSaSxgJG4V/6kuG5HHwJpe4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=g6wRGJixqoAiCYgh2l0L/8QPv3wsC65lYc16yu55JVwHWwOKsb/5k1FEUB7craspV /IN4JNGnQQyRIMOtyQKpA7UJ8/ON7bL/6xgpXkh6D74dvSRCgsn9Yu8V5kAuUKomF3 0buCHRc6JRAWdf4BbzWUHrGB2ABsKEkwDoWIZky8= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] QPACK: Huffman string compression (#1435) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e43c1d4293_104463f91244a6f8812142c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 09:41:26 -0000 ----==_mimepart_5b1e43c1d4293_104463f91244a6f8812142c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Does QPACK use the same Huffman coding table that is defined in HTTP/2 (https://tools.ietf.org/html/rfc7541#appendix-B)? If so, there is no reference to it. -- 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/1435 ----==_mimepart_5b1e43c1d4293_104463f91244a6f8812142c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Does QPACK use the same Huffman coding table that is defined in HTTP/2 (https://tools.ietf.org/html/rfc7541#appendix-B)?

If so, there is no reference to it.

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

----==_mimepart_5b1e43c1d4293_104463f91244a6f8812142c-- From nobody Mon Jun 11 04:20:01 2018 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 6C67F130E2D for ; Mon, 11 Jun 2018 04:19:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 xHzNQ6ROWrJD for ; Mon, 11 Jun 2018 04:19:58 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D50ED12777C for ; Mon, 11 Jun 2018 04:19:57 -0700 (PDT) Date: Mon, 11 Jun 2018 04:19:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528715996; bh=FEHMqWWkipFBTeKoNguLmOiBQ4/NJDKz+GTTKXSxwoY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l8nkuANgvuq4BMrc+2DZAC3Y86wDc6tAKqq7+DGkTCGYNyTKrK/EXvkMskYTudqDb Lj/FL2Qv1jpht3NW9P1r+YXyII+kR/JyWHcVcnyIfR37cEVjXuJrt6Ov2U223qfE3D TmAd4Smo3/cYXisbAXVeJKu8TxjM8sS25547u0fU= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e5adcdc695_7b902ab1ae6d4f5412957c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 11:20:00 -0000 ----==_mimepart_5b1e5adcdc695_7b902ab1ae6d4f5412957c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This seems like an important property to capture. Some of the HTTP/QUIC text sort of falls into this category but would benefit from clearer language in the transport. The only question I have is: is this an invariant? -- 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/1424#issuecomment-396209491 ----==_mimepart_5b1e5adcdc695_7b902ab1ae6d4f5412957c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This seems like an important property to capture. Some of the HTTP/QUIC text sort of falls into this category but would benefit from clearer language in the transport.

The only question I have is: is this an invariant?

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

----==_mimepart_5b1e5adcdc695_7b902ab1ae6d4f5412957c-- From nobody Mon Jun 11 04:24:02 2018 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 3841B130F78 for ; Mon, 11 Jun 2018 04:24:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 odAsICB62ZMk for ; Mon, 11 Jun 2018 04:23:58 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76AD912777C for ; Mon, 11 Jun 2018 04:23:58 -0700 (PDT) Date: Mon, 11 Jun 2018 04:23:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528716237; bh=O+s94KtPyNOaZdBXWmk+lVIAaxmd3wzLk0OPBc41oe8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FWjK/MhH1rXa+lzSqETPqgcbc48WF9a6sEZ68SUjYADEA3nI09yhcqfym+YJW1edz 5NIlfOQSR+f9x132LhpNg/Pfgm19OP0c3Fpfj4QSnNIH3auJWiecax9nvIp4tP6Uo/ VCXasnAP5+xMtmmAjFRi55iG6QLjOvQ22p0vMtXM= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e5bcd9d092_2f492ab61eef6f6056518d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 11:24:01 -0000 ----==_mimepart_5b1e5bcd9d092_2f492ab61eef6f6056518d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit One idea (discussed in-person) is to simply remove the offending statement. However, that seems to lose some of context. Perhaps we could join this sentance with earlier paragraph > When HTTP headers and data are sent over QUIC, the QUIC layer handles most of the stream management. and some fluffier text might help? -- 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/1417#issuecomment-396210365 ----==_mimepart_5b1e5bcd9d092_2f492ab61eef6f6056518d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One idea (discussed in-person) is to simply remove the offending state= ment. However, that seems to lose some of context.

Perhaps we could join this sentance with earlier paragraph

When HTTP headers and data are sent over QUIC, the QUIC layer handles = most of the stream management.

and some fluffier text might help?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1e5bcd9d092_2f492ab61eef6f6056518d-- From nobody Mon Jun 11 04:53:05 2018 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 11E1A130E3F for ; Mon, 11 Jun 2018 04:53:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 XMkEhF5R50_a for ; Mon, 11 Jun 2018 04:53:02 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D116130F91 for ; Mon, 11 Jun 2018 04:53:01 -0700 (PDT) Date: Mon, 11 Jun 2018 04:53:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528717980; bh=BsGYyFo6QZ8p//NDQEE6KkMWcM9A0DMu55yBcmwGsig=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sFIGVk88GRe6mV853cCt5gQ7ZoMCz2pYRgp2w4tDormRlnbFld+YjjUQo3akH8gzY 2YQcvdM2VE3A7jliWbODJs6R16V4HkUdpBShBJWv08V1ofiEXmkG26HBKw2J1RzNNG I0FcN55eVpHze0ERT0W3zn+YTCJa0waTAFKqZI3g= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Detect adversarial ECN reporting (#1426) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e629c9680f_5dca3fb0a1d40f802050f9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 11 Jun 2018 11:53:04 -0000 ----==_mimepart_5b1e629c9680f_5dca3fb0a1d40f802050f9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agree with @gorryfair that this is a generic issue for ECN. On the higher level clearly a sender should be able to test the response of the receiver by marking ECN-CE from the sender side. I think this falls into the same optional possibilities as the intentional sequence number gaps. So, I think it would be good if there could be a general recommendation for this type of receiver behavior verification. The masking of actual CE marks are one issue. The others I see, is any API limitations on certain platforms. On the other side one can question the value of lying about the CE marks. Being none-responsive to CE-marks may result in pushing other flows out of the way, at the same time it does build queue, especially if one-self is the main flow. Also, in certain networks, one could be penalized for not being responsive to CE marks. -- 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/1426#issuecomment-396217066 ----==_mimepart_5b1e629c9680f_5dca3fb0a1d40f802050f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Agree with @gorryfair that this = is a generic issue for ECN. On the higher level clearly a sender should b= e able to test the response of the receiver by marking ECN-CE from the se= nder side. I think this falls into the same optional possibilities as the= intentional sequence number gaps.

So, I think it would be good if there could be a general recommendatio= n for this type of receiver behavior verification. The masking of actual = CE marks are one issue. The others I see, is any API limitations on certa= in platforms.

On the other side one can question the value of lying about the CE mar= ks. Being none-responsive to CE-marks may result in pushing other flows o= ut of the way, at the same time it does build queue, especially if one-se= lf is the main flow. Also, in certain networks, one could be penalized fo= r not being responsive to CE marks.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1e629c9680f_5dca3fb0a1d40f802050f9-- From nobody Mon Jun 11 05:19:16 2018 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 C3F44130FAC for ; Mon, 11 Jun 2018 05:19:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 5-498LiXHQBE for ; Mon, 11 Jun 2018 05:19:12 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109AE130F9D for ; Mon, 11 Jun 2018 05:19:12 -0700 (PDT) Date: Mon, 11 Jun 2018 05:19:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528719551; bh=q+6XbmhMcYdq7bn7TjWt0WoIoGzVHebvSg4uG9g5Efg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ktdlCfuYvqYAt4/3TsgcCCKC5T5LitdhaBgynmT6ZhNDeTqaZQUirjuZSH7RsHJPx L8de713h3XLBWXsrPY2nbUlrzkPclBBSQLYqlxae2BfLvBECqNxj4dud/hUQlqs3tM NBdJe/z93VezurTsSmI3xV0bFiKSFz37bFGkLOBk= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e68bf270ca_79752b1f276bef60166257"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 12:19:15 -0000 ----==_mimepart_5b1e68bf270ca_79752b1f276bef60166257 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In most architectures, I'd expect that if the connection ID is different for the second QUIC packet, the receiver will drop it, since it is likely for a different host. The alternative would be to expect receivers to process the first packet, and if the next one has a different connection ID for a different host, have it redirect the packet. Which seems pretty crazy to me. -- 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/1423#issuecomment-396223935 ----==_mimepart_5b1e68bf270ca_79752b1f276bef60166257 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In most architectures, I'd expect that if the connection ID is differe= nt for the second QUIC packet, the receiver will drop it, since it is lik= ely for a different host.

The alternative would be to expect receivers to process the first pack= et, and if the next one has a different connection ID for a different hos= t, have it redirect the packet. Which seems pretty crazy to me.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1e68bf270ca_79752b1f276bef60166257-- From nobody Mon Jun 11 05:21:15 2018 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 4BDE8130FAE for ; Mon, 11 Jun 2018 05:21:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QOLV69LcCAQP for ; Mon, 11 Jun 2018 05:21:07 -0700 (PDT) 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 DED2D130FAB for ; Mon, 11 Jun 2018 05:21:06 -0700 (PDT) Date: Mon, 11 Jun 2018 05:21:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528719666; bh=GYvBwG8WbwfqR/dsRj9qf0JGIdrNow2oCEGBjBLBP1w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=If01WLhvI+GD2iannkSIs/FqZ6g8gtRN95uDdhbcPf0aBtlSYCoUuXtRX6vqvnUzG eh8bIXO4ZAMS5fmnda9m/92GlSRPq+QrCUJyWLGO33xr0VD9Ln5+HBXOLY3iedbsN0 o+SjWmxR9PlNFhVnF8SFLT65wjEF+sLWVWPe2I6E= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e6932315e6_55422addfa7def581592ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 12:21:14 -0000 ----==_mimepart_5b1e6932315e6_55422addfa7def581592ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed this would be useful to explicitly state. I don't think we'd benefit from making this an invariant, though I would expect it to continue to be true in future versions. -- 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/1424#issuecomment-396224405 ----==_mimepart_5b1e6932315e6_55422addfa7def581592ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Agreed this would be useful to explicitly state.

I don't think we'd benefit from making this an invariant, though I would expect it to continue to be true in future versions.

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

----==_mimepart_5b1e6932315e6_55422addfa7def581592ef-- From nobody Mon Jun 11 07:11:04 2018 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 13825130E54 for ; Mon, 11 Jun 2018 07:11:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jYib6PB5Rujp for ; Mon, 11 Jun 2018 07:10:59 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51AD91294D0 for ; Mon, 11 Jun 2018 07:10:59 -0700 (PDT) Date: Mon, 11 Jun 2018 07:10:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528726258; bh=4MfuxtXL2R/gHkYQg1AIzUePYiRIa3J37oeo8XTenEI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YAFXyUgcnsOoM3QZfQ8hEvAmiEaYdG9atpLoWnn1p4cXfrjdI5TdOwJfelW/nsbqh uqGatZAKtwA2GmpPfmTTXIoUiooi0MVD3pmUNPg2vRIQkWjExxfMQL2CgBXJKqEx+v 41sIbPjY6K0W5besiiCNsUiASLkhPDTfP+ViJFN0= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e82f248fb0_3bf83fc81e25cf80734cd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 14:11:03 -0000 ----==_mimepart_5b1e82f248fb0_3bf83fc81e25cf80734cd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. Looks good, some editorial comments. > @@ -417,6 +417,13 @@ to accelerate loss recovery. The receiver SHOULD send an immediate ACK when it receives a new packet which is not one greater than the largest received packet number. +Also, reception of an packet marked as ECN Congestion Experience +(ECN-CE) SHOULD be acknowledged immediately to quicker react to +congesiton events. Additional ECN-CE marks received during the same congesiton -> congestion > @@ -417,6 +417,13 @@ to accelerate loss recovery. The receiver SHOULD send an immediate ACK when it receives a new packet which is not one greater than the largest received packet number. +Also, reception of an packet marked as ECN Congestion Experience I might say "Similarly," instead of "Also," since this is similar to the preceding paragraph. > @@ -880,13 +892,31 @@ QUIC hosts MUST NOT send packets if they would increase bytes_in_flight the packet is a probe packet sent after the TLP or RTO alarm fires, as described in {{tlp}} and {{rto}}. +## Explicit Congestion Notification {#congestion-ecn} + +If ECN {!RFC3168} has been verified to work for the current path QUIC +will use the ECN Congestion Experienced (ECN-CE) IP packet marking as a +signal of congestion as a complement to packet loss. This document +specifies to use the classical ECN-CE response, i.e. the same response +as for packet loss. However, there exist potential for future +experimentation in using other response functions as discussed in +{!RFC8311}. + +The ACK_ECN frame defined in {{QUIC-TRANSPORT}} does not provide +information on which of the newly acknowledged packets that +was marked with ECN-CE. Therefore, it will be assumed that I would suggest rewriting as: "Because newly received marks cause an ACK_ECN be sent immediately, is is assumed the congestion event starts at the highest newly acknowledged packet number." > @@ -977,6 +1009,12 @@ kLossReductionFactor (default 0.5): Variables required to implement the congestion control mechanisms are described in this section. +ack_ce_cntr: +: The ACK_ECN counter for ECN-CE marks previously processed. Used to + determine when one or more packet acknowledged by the ACK_ECN frame + was marked with ECN-CE. + extra linebreak? > @@ -977,6 +1009,12 @@ kLossReductionFactor (default 0.5): Variables required to implement the congestion control mechanisms are described in this section. +ack_ce_cntr: +: The ACK_ECN counter for ECN-CE marks previously processed. Used to I might suggest calling this previous_ecn_ce or previous_ecn_ce_ctr > @@ -1042,6 +1081,26 @@ acked_packet from sent_packets. kDefaultMss * acked_packet.bytes / congestion_window ~~~ +### On Packets Marked + +Invoked by an increment in the number of CE marked packets, as +indicated by a newly received ACK_ECN frame when compared to +ack_ce_cntr. + +~~~ + OnPacketsMarked(ce_counter): + if (ce_counter > ack_ce_cntr): + // update ack_ce_cntr + ack_ce_cntr = ce_counter + if (!InRecovery(largest_acked_packet)): I think we want to use largest newly acked packet ideally. Also, possibly create a single method like "MaybeStartCongestionEvent" to avoid the code duplication between these methods. > @@ -1061,20 +1063,21 @@ negotiation, which is the same no matter which reserved version was sent. A server MAY therefore send different reserved version numbers in the Version Negotiation Packet and in its transport parameters. -A client MAY send a packet using a reserved version number. This can be used to -solicit a list of supported versions from a server. +A client MAY send a packet using a reserved version number. This can be This change and many that follow are unrelated to this PR. Can you revert them to make this PR smaller? > @@ -1410,6 +1416,71 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN capability check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for +non-destructive congestion notification by a network node. That is, packets are +marked instead of being discarded by routers and other devices along a network +path. QUIC endpoints perform capability verification on connection establishment +as well as connection migration. The feature can be used unidirectional or This sentence is awkward, maybe "ECN can be used unidirectionally, bidirectionally, or disabled depending on endpoint and path capabilities."? > +endpoint individually performs an ECN capability check for its send path. The +check is performed by attempting to set the ECN bits in the IP header to either +ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with +the Initial packet ({{packet-initial}}) and servers with the Handshake packet +(server) ({{packet-handshake}}). Note that Retry Packets ({{packet-retry}}) can +be marked as ECT, but as they are not acknowledged by the peer, they provide no +capability verification. + +The choice if ECT(0) and ECT(1) should be used is as per the guidelines in +{{!RFC8311}}. ECT(0) is the default, if no ECN experiments are run. Upon +reception of a packet with ECT(0), ECT(1) or ECN-CE marking by the peer +endpoint, an ACK_ECN frame is transmitted back. This ACK_ECN frame indicates how +many packets that are marked ECT(0), ECT(1) or ECN-CE. Thus the endpoint can +determine if the endpoints and path is ECN capable. + +The ACK_ECN frame will, when received, confirm that the path direction supports How about: "When ACK_ECN is received, the counter values can be used to confirm the expected number of marks were received." > +packets that was marked as ECT in the sender, or if the comparision of the +counters with the total of acknolwedged packets indicates that not all packets +arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN +Capable. If the endpoint determine the path as currently not ECN capable it +SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + +It is expected that QUIC discards duplicate packets early, however if that is +not the case **\[ED note, have not seen any clear statement in the drafts]**, +then it should be verified that the number of ECT marked packets are equal to or +larger that the amount of ECT marked packets that have been transmitted. + +### Continous Verification of ECN {#ecn-continous-verification} + +If the ECN capabiity check was successful and the endpoint continus to send ECT continues > +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + +It is expected that QUIC discards duplicate packets early, however if that is +not the case **\[ED note, have not seen any clear statement in the drafts]**, +then it should be verified that the number of ECT marked packets are equal to or +larger that the amount of ECT marked packets that have been transmitted. + +### Continous Verification of ECN {#ecn-continous-verification} + +If the ECN capabiity check was successful and the endpoint continus to send ECT +marked packets then continous verification is applied. This is to detect any +cases when ECN field is bleached, that is, zeroed out by a network node, likely +as the result of a routing changes since the ECN capability check. + +For each ACK_ECN frame that is received, the total number of ACKed packets are Suggestion: "For each received ACK_ECN frame, the total number of newly acknowledged packets can be compared to the total increase in ECN counters. If the increase in ECN counters is larger, then an ECN failure has occurred and ECN should be disabled." > @@ -2816,6 +2960,10 @@ ACK Block (repeated): ### Sending ACK Frames +ACK Frames MAY be sent when all packets to be acknowledge had an IP header with acknowledged > @@ -2816,6 +2960,10 @@ ACK Block (repeated): ### Sending ACK Frames +ACK Frames MAY be sent when all packets to be acknowledge had an IP header with +the ECN field marked as Not-ECT. If any packets where marked as ECT or ECN-CE where -> were > @@ -2816,6 +2960,10 @@ ACK Block (repeated): ### Sending ACK Frames +ACK Frames MAY be sent when all packets to be acknowledge had an IP header with Also, I think leading with this paragraph here is a bit confusing. I would prefer not adding anything here about ACK_ECN and placing text in the ACK_ECN section that must be used when new marks are received. > @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks + +The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An +on-path attacker may manipulate the value of the field. Thus, affecting the I think this reads more clearly as one sentence. ie: "An on-path attacker may manipulate the value of the field, affecting the congestion avoidance behavior of the sender." > @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks + +The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An +on-path attacker may manipulate the value of the field. Thus, affecting the +congestion avoidance behavior of the sender. By clearing any CE marks the +connection can help drive a bottle neck queue into a loss regime. By setting +the ECN field to CE marking it can drive down the senders congestion window +thus resulting in reduced throughput. The later could equally be accomplished +by dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} +discusses the effects of undesired manipulation of the ECN field in more +details. + +If a receiver would not have packet duplication detection and not discard any How about "If a receiver does not discard duplicate packets, an off-path attacker can retransmit packets with ECN bits set and manipulate the senders congestion avoidance state." > @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks + +The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An +on-path attacker may manipulate the value of the field. Thus, affecting the +congestion avoidance behavior of the sender. By clearing any CE marks the +connection can help drive a bottle neck queue into a loss regime. By setting +the ECN field to CE marking it can drive down the senders congestion window +thus resulting in reduced throughput. The later could equally be accomplished +by dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} +discusses the effects of undesired manipulation of the ECN field in more +details. + +If a receiver would not have packet duplication detection and not discard any +duplicates an off-path attacker that can receive copies of the connection's +packets can manipulate the senders congestion avoidance state. If packet packet duplicates -> duplicate packets -- 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/1372#pullrequestreview-127544398 ----==_mimepart_5b1e82f248fb0_3bf83fc81e25cf80734cd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

Looks good, some editorial comments.

In draft-ietf-quic-recovery.md:

> @@ -417,6 +417,13 @@ to accelerate loss recovery.  The receiver SHOULD send an immediate ACK
 when it receives a new packet which is not one greater than the
 largest received packet number.
 
+Also, reception of an packet marked as ECN Congestion Experience
+(ECN-CE) SHOULD be acknowledged immediately to quicker react to
+congesiton events. Additional ECN-CE marks received during the same

congesiton -> congestion

In draft-ietf-quic-recovery.md:

> @@ -417,6 +417,13 @@ to accelerate loss recovery.  The receiver SHOULD send an immediate ACK
 when it receives a new packet which is not one greater than the
 largest received packet number.
 
+Also, reception of an packet marked as ECN Congestion Experience

I might say "Similarly," instead of "Also," since this is similar to the preceding paragraph.

In draft-ietf-quic-recovery.md:

> @@ -880,13 +892,31 @@ QUIC hosts MUST NOT send packets if they would increase bytes_in_flight
 the packet is a probe packet sent after the TLP or RTO alarm fires, as described
 in {{tlp}} and {{rto}}.
 
+## Explicit Congestion Notification {#congestion-ecn}
+
+If ECN {!RFC3168} has been verified to work for the current path QUIC
+will use the ECN Congestion Experienced (ECN-CE) IP packet marking as a
+signal of congestion as a complement to packet loss. This document
+specifies to use the classical ECN-CE response, i.e. the same response
+as for packet loss. However, there exist potential for future
+experimentation in using other response functions as discussed in
+{!RFC8311}.
+
+The ACK_ECN frame defined in {{QUIC-TRANSPORT}} does not provide
+information on which of the newly acknowledged packets that
+was marked with ECN-CE. Therefore, it will be assumed that

I would suggest rewriting as: "Because newly received marks cause an ACK_ECN be sent immediately, is is assumed the congestion event starts at the highest newly acknowledged packet number."

In draft-ietf-quic-recovery.md:

> @@ -977,6 +1009,12 @@ kLossReductionFactor (default 0.5):
 Variables required to implement the congestion control mechanisms
 are described in this section.
 
+ack_ce_cntr:
+: The ACK_ECN counter for ECN-CE marks previously processed. Used to
+  determine when one or more packet acknowledged by the ACK_ECN frame
+  was marked with ECN-CE.
+

extra linebreak?

In draft-ietf-quic-recovery.md:

> @@ -977,6 +1009,12 @@ kLossReductionFactor (default 0.5):
 Variables required to implement the congestion control mechanisms
 are described in this section.
 
+ack_ce_cntr:
+: The ACK_ECN counter for ECN-CE marks previously processed. Used to

I might suggest calling this previous_ecn_ce or previous_ecn_ce_ctr

In draft-ietf-quic-recovery.md:

> @@ -1042,6 +1081,26 @@ acked_packet from sent_packets.
          kDefaultMss * acked_packet.bytes / congestion_window
 ~~~
 
+### On Packets Marked
+
+Invoked by an increment in the number of CE marked packets, as
+indicated by a newly received ACK_ECN frame when compared to
+ack_ce_cntr.
+
+~~~
+   OnPacketsMarked(ce_counter):
+     if (ce_counter > ack_ce_cntr):
+       // update ack_ce_cntr
+       ack_ce_cntr = ce_counter
+     if (!InRecovery(largest_acked_packet)):

I think we want to use largest newly acked packet ideally.

Also, possibly create a single method like "MaybeStartCongestionEvent" to avoid the code duplication between these methods.

In draft-ietf-quic-transport.md:

> @@ -1061,20 +1063,21 @@ negotiation, which is the same no matter which reserved version was sent.
 A server MAY therefore send different reserved version numbers in the Version
 Negotiation Packet and in its transport parameters.
 
-A client MAY send a packet using a reserved version number.  This can be used to
-solicit a list of supported versions from a server.
+A client MAY send a packet using a reserved version number. This can be

This change and many that follow are unrelated to this PR. Can you revert them to make this PR smaller?

In draft-ietf-quic-transport.md:

> @@ -1410,6 +1416,71 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN capability check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for
+non-destructive congestion notification by a network node.  That is, packets are
+marked instead of being discarded by routers and other devices along a network
+path. QUIC endpoints perform capability verification on connection establishment
+as well as connection migration. The feature can be used unidirectional or

This sentence is awkward, maybe "ECN can be used unidirectionally, bidirectionally, or disabled depending on endpoint and path capabilities."?

In draft-ietf-quic-transport.md:

> +endpoint individually performs an ECN capability check for its send path. The
+check is performed by attempting to set the ECN bits in the IP header to either
+ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with
+the Initial packet ({{packet-initial}}) and servers with the Handshake packet
+(server) ({{packet-handshake}}). Note that Retry Packets ({{packet-retry}}) can
+be marked as ECT, but as they are not acknowledged by the peer, they provide no
+capability verification.
+
+The choice if ECT(0) and ECT(1) should be used is as per the guidelines in
+{{!RFC8311}}. ECT(0) is the default, if no ECN experiments are run. Upon
+reception of a packet with ECT(0), ECT(1) or ECN-CE marking by the peer
+endpoint, an ACK_ECN frame is transmitted back. This ACK_ECN frame indicates how
+many packets that are marked ECT(0), ECT(1) or ECN-CE. Thus the endpoint can
+determine if the endpoints and path is ECN capable.
+
+The ACK_ECN frame will, when received, confirm that the path direction supports

How about: "When ACK_ECN is received, the counter values can be used to confirm the expected number of marks were received."

In draft-ietf-quic-transport.md:

> +packets that was marked as ECT in the sender, or if the comparision of the
+counters with the total of acknolwedged packets indicates that not all packets
+arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN
+Capable.  If the endpoint determine the path as currently not ECN capable it
+SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the
+connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+It is expected that QUIC discards duplicate packets early, however if that is
+not the case **\[ED note, have not seen any clear statement in the drafts]**,
+then it should be verified that the number of ECT marked packets are equal to or
+larger that the amount of ECT marked packets that have been transmitted.
+
+### Continous Verification of ECN {#ecn-continous-verification}
+
+If the ECN capabiity check was successful and the endpoint continus to send ECT

continues

In draft-ietf-quic-transport.md:

> +connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+It is expected that QUIC discards duplicate packets early, however if that is
+not the case **\[ED note, have not seen any clear statement in the drafts]**,
+then it should be verified that the number of ECT marked packets are equal to or
+larger that the amount of ECT marked packets that have been transmitted.
+
+### Continous Verification of ECN {#ecn-continous-verification}
+
+If the ECN capabiity check was successful and the endpoint continus to send ECT
+marked packets then continous verification is applied. This is to detect any
+cases when ECN field is bleached, that is, zeroed out by a network node, likely
+as the result of a routing changes since the ECN capability check.
+
+For each ACK_ECN frame that is received, the total number of ACKed packets are

Suggestion: "For each received ACK_ECN frame, the total number of newly acknowledged packets can be compared to the total increase in ECN counters. If the increase in ECN counters is larger, then an ECN failure has occurred and ECN should be disabled."

In draft-ietf-quic-transport.md:

> @@ -2816,6 +2960,10 @@ ACK Block (repeated):
 
 ### Sending ACK Frames
 
+ACK Frames MAY be sent when all packets to be acknowledge had an IP header with

acknowledged

In draft-ietf-quic-transport.md:

> @@ -2816,6 +2960,10 @@ ACK Block (repeated):
 
 ### Sending ACK Frames
 
+ACK Frames MAY be sent when all packets to be acknowledge had an IP header with
+the ECN field marked as Not-ECT. If any packets where marked as ECT or ECN-CE

where -> were

In draft-ietf-quic-transport.md:

> @@ -2816,6 +2960,10 @@ ACK Block (repeated):
 
 ### Sending ACK Frames
 
+ACK Frames MAY be sent when all packets to be acknowledge had an IP header with

Also, I think leading with this paragraph here is a bit confusing. I would prefer not adding anything here about ACK_ECN and placing text in the ACK_ECN section that must be used when new marks are received.

In draft-ietf-quic-transport.md:

> @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks
+
+The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An
+on-path attacker may manipulate the value of the field. Thus, affecting the

I think this reads more clearly as one sentence. ie: "An on-path attacker may manipulate the value of the field, affecting the congestion avoidance behavior of the sender."

In draft-ietf-quic-transport.md:

> @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks
+
+The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An
+on-path attacker may manipulate the value of the field. Thus, affecting the
+congestion avoidance behavior of the sender. By clearing any CE marks the
+connection can help drive a bottle neck queue into a loss regime. By setting
+the ECN field to CE marking it can drive down the senders congestion window
+thus resulting in reduced throughput. The later could equally be accomplished
+by dropping packets for the connection. Section 18 and 19 of {{!RFC3168}}
+discusses the effects of undesired manipulation of the ECN field in more
+details.
+
+If a receiver would not have packet duplication detection and not discard any

How about "If a receiver does not discard duplicate packets, an off-path attacker can retransmit packets with ECN bits set and manipulate the senders congestion avoidance state."

In draft-ietf-quic-transport.md:

> @@ -4196,6 +4416,23 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks
+
+The ECN bits {{!RFC3168}} are an unauthenticated signal from the network. An
+on-path attacker may manipulate the value of the field. Thus, affecting the
+congestion avoidance behavior of the sender. By clearing any CE marks the
+connection can help drive a bottle neck queue into a loss regime. By setting
+the ECN field to CE marking it can drive down the senders congestion window
+thus resulting in reduced throughput. The later could equally be accomplished
+by dropping packets for the connection. Section 18 and 19 of {{!RFC3168}}
+discusses the effects of undesired manipulation of the ECN field in more
+details.
+
+If a receiver would not have packet duplication detection and not discard any
+duplicates an off-path attacker that can receive copies of the connection's
+packets can manipulate the senders congestion avoidance state. If packet

packet duplicates -> duplicate packets

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

----==_mimepart_5b1e82f248fb0_3bf83fc81e25cf80734cd-- From nobody Mon Jun 11 07:41:40 2018 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 9131C130FDC for ; Mon, 11 Jun 2018 07:41:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ELFAvbhQv6ik for ; Mon, 11 Jun 2018 07:41:36 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE8DB124D68 for ; Mon, 11 Jun 2018 07:41:36 -0700 (PDT) Date: Mon, 11 Jun 2018 07:41:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528728095; bh=1ZiynDvxOsKJjT1VwU6KlnyFe+nyNtHrn+4Gc0mTlkk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=1PkmKwDPf4HmpUXuNwTyII2vwcLW6lXtQTeZcGCJ+GowugR3bZbOItvMM5tFCAH3I v+KPwtJA9NzSi+o31/3DvjRuzz/jmbMkU2KSPPhK5RpeaY93oPSXS+JjpTb8yGHLLY qKNOEZxx0WbU09lDAngMsXX9SbTehCdLMfqKLCXQ= From: David Wong Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] octet 1 of Long Header (#1436) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e8a1fa46b8_5a832aae7bc8cf549335b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mimoo 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.26 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, 11 Jun 2018 14:41:39 -0000 ----==_mimepart_5b1e8a1fa46b8_5a832aae7bc8cf549335b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In https://github.com/quicwg/base-drafts/blob/master/draft-ietf-quic-transport.md#long-header-long-header It says that octet 1 of the long header contains the DCIL/SCIL values, but the diagram above has the beginning of the Version in octet 1. -- 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/1436 ----==_mimepart_5b1e8a1fa46b8_5a832aae7bc8cf549335b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In https://github.com/quicwg/base-drafts/blob/master/draft-ietf-quic-transport.md#long-header-long-header

It says that octet 1 of the long header contains the DCIL/SCIL values, but the diagram above has the beginning of the Version in octet 1.

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

----==_mimepart_5b1e8a1fa46b8_5a832aae7bc8cf549335b-- From nobody Mon Jun 11 08:55:31 2018 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 0156C130E5F for ; Mon, 11 Jun 2018 08:55:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rgDk2_zJeyqa for ; Mon, 11 Jun 2018 08:55:28 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10280130E3B for ; Mon, 11 Jun 2018 08:55:28 -0700 (PDT) Date: Mon, 11 Jun 2018 08:55:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528732526; bh=kFsB3VeQqOfrZpS7JfAxQ0gzCP4JlUsVvz1Ez41Y+mU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lFWPmRl2+r1AqrnfokGQr6jqAy51zrufYWjy1sI1lOK9ntlWzvm4OqHpODwkQyVLP UMuGAkf6wofHOT/dbMTZlW9oCUwFZkjag4yd9iDrpEiBtE4p31kOtPxnKFPym9O0hC nkub+5MV6C8KETClPenN9fEFAoVQ0vDDHhj6gxUs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e9b6e672b0_249b3fc1bceecf8819084d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 15:55:31 -0000 ----==_mimepart_5b1e9b6e672b0_249b3fc1bceecf8819084d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree with Ian here. What we have isn't ideal, but you can get used to it. It would be easier if people didn't feel that it was necessary to correct someone every time they say N+1 but mean N+4, when intent is otherwise clear, but that is a small tax to pay. FWIW, I experimented with an encoding for stream identifiers that used a 2 bit prefix and a varint that was 4/12/28/60. The performance hit was considerable. -- 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/1431#issuecomment-396293329 ----==_mimepart_5b1e9b6e672b0_249b3fc1bceecf8819084d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I agree with Ian here. What we have isn't ideal, but you can get used= to it. It would be easier if people didn't feel that it was necessary t= o correct someone every time they say N+1 but mean N+4, when intent is ot= herwise clear, but that is a small tax to pay.

FWIW, I experimented with an encoding for stream identifiers that used= a 2 bit prefix and a varint that was 4/12/28/60. The performance hit wa= s considerable.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1e9b6e672b0_249b3fc1bceecf8819084d-- From nobody Mon Jun 11 09:11:05 2018 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 6289613104C for ; Mon, 11 Jun 2018 09:10:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 92ZnpeSvhYe2 for ; Mon, 11 Jun 2018 09:10:55 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98C7C1310B1 for ; Mon, 11 Jun 2018 09:10:23 -0700 (PDT) Date: Mon, 11 Jun 2018 09:10:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528733422; bh=bTKbI3LfdQo/vewV2lWnApy/mBlv9d0ER1GMOwqLSug=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cWlci3q7oNXXKsugggUOgt4ui1l03osaSBT6ktw2IR7uoEL+q6dcRGlIWJ9KKtsq8 eOLf/OawbuanulMW9LwpCfyCPSqtbVpKNvk4EHgRZHpY7OEP0iNMG6zFrnSa5eV0jj UW6hn8FPdmrGapp5FI+QTyLynZvPSWVvU07dKI84= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e9eeed57d6_7ebe3f8ea5a2af8091696"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:11:03 -0000 ----==_mimepart_5b1e9eeed57d6_7ebe3f8ea5a2af8091696 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed in Kista. Conclusion was that the marginal benefit was minor, if not non-existent, and the cost was significant. A man-on-the-side could build the oracle. We will instead concentrate on documenting the constraints on the routing infrastructure. -- 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/1230#issuecomment-396298189 ----==_mimepart_5b1e9eeed57d6_7ebe3f8ea5a2af8091696 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Discussed in Kista. Conclusion was that the marginal benefit was minor, if not non-existent, and the cost was significant. A man-on-the-side could build the oracle. We will instead concentrate on documenting the constraints on the routing infrastructure.

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

----==_mimepart_5b1e9eeed57d6_7ebe3f8ea5a2af8091696-- From nobody Mon Jun 11 09:11:23 2018 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 451C5131063 for ; Mon, 11 Jun 2018 09:10:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 pkgAv0r8nHti for ; Mon, 11 Jun 2018 09:10:57 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 EE4BD1310C2 for ; Mon, 11 Jun 2018 09:10:24 -0700 (PDT) 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=CcXwDF+ODZcryEMeI8egcXLJn24=; b=MalMIXkxwTLY6Ut+ oUbLltxUWF3b8DJOLbIJlbreL4Ulke26AlMKDzbhNxCL4JTdftyhBsdd9PzEw7hx NWzQV/xYJ1kBDIFnTH+23nYhs9eg93P2frkH5+F6ooasfMnybONBjP1mGqRv/FvT KOuyd+rwaWq6xEzwotfce5+Efg4= Received: by filter0890p1las1.sendgrid.net with SMTP id filter0890p1las1-25155-5B1E9EEF-6 2018-06-11 16:10:23.122652149 +0000 UTC Received: from github-lowworker-0be93ae.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id NOZPmQeVRi2MvkBYrhZb1A for ; Mon, 11 Jun 2018 16:10:22.903 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-0be93ae.cp1-iad.github.net (Postfix) with ESMTP id DBF143E0995 for ; Mon, 11 Jun 2018 09:10:22 -0700 (PDT) Date: Mon, 11 Jun 2018 16:10:23 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1e9eeedae15_e0d13f9a229dcf78503d8"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1JfPfgFDq7ZN0ljnp4aqYZbx1Hfb0vMFIae6 TClJ58d6ZOwGvvxo3DFH2FM8tYAhRrl6/r35Eg84c9eypIMD41hGpPZ8yp3K1DU+FiyMpfaQJiExLN rflBZh93DUXGwKikDD/Oa12BnLJtLu+t1MqKjUbpSzD7NUxdn88pg2I0P5/sUNwsK2ZhlcUbP8FXGM 0= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:11:04 -0000 ----==_mimepart_5b1e9eeedae15_e0d13f9a229dcf78503d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1230. -- 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/1230#event-1674290442 ----==_mimepart_5b1e9eeedae15_e0d13f9a229dcf78503d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1230.

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

----==_mimepart_5b1e9eeedae15_e0d13f9a229dcf78503d8-- From nobody Mon Jun 11 09:14:31 2018 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 35812130E75 for ; Mon, 11 Jun 2018 09:14:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 mkT8dW13zKda for ; Mon, 11 Jun 2018 09:14:27 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 C5D13130E72 for ; Mon, 11 Jun 2018 09:14:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528733666; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=l6SYHhhRq2eDrKWOoPNvQa1ayjyjhp/vZsI+RAeNmIM=; b=wDBERtMwexcfuJg+M5POsbRpBjwy9Ubxjfix+sj6v3vP7MC0YvRqxn238kPrRqpMePLZnWmj IM7ixrdaa24blI79EmV25QGj6iyuzkVm4z/XbcSUAhu/pyhceZBqkMRq7F0qvHni+a8zjZiL zhTAI1bcgMKgXldFKSQKKX2tvvI= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b1e9fe2.7f7202eb2db0-smtp-out-n02; Mon, 11 Jun 2018 16:14:26 -0000 (UTC) Date: Mon, 11 Jun 2018 09:14:25 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b1e9fe1b7078_77752af87e511c0062832@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e7f7c5: Don't cite octet indices any more Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1e9fe1b6d0d_77752af87e511c006277d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 16:14:30 -0000 ----==_mimepart_5b1e9fe1b6d0d_77752af87e511c006277d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/issue1436 Home: https://github.com/quicwg/base-drafts Commit: e7f7c5f023f419f43aaaa9ec8b6d323af6e01232 https://github.com/quicwg/base-drafts/commit/e7f7c5f023f419f43aaaa9ec8b6d323af6e01232 Author: Martin Thomson Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Don't cite octet indices any more Also reflow. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1e9fe1b6d0d_77752af87e511c006277d-- From nobody Mon Jun 11 09:15:51 2018 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 950B6130FD4 for ; Mon, 11 Jun 2018 09:15:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 D5Ra20qkFrS5 for ; Mon, 11 Jun 2018 09:15:42 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 15E2C1277BB for ; Mon, 11 Jun 2018 09:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=wBMkiRfMjETddMHu6HWWi6iQRYM=; b=EcGN+mF5+9A5RcFF 17OIzMchjKdOjctbeE+JsTyMYIVYNFVUNdQBbQEOUIx9CfY9ywUBjcHTufWoO+eE 6YjWr2TP6gMo/sZesHK3qfpzcnUdUtJkk9ZwQytzRHdVjphRPBNMnMpwjxgqeoTp gMbUMsF8KnmQgU0CiADHmaYIqQc= Received: by filter1445p1mdw1.sendgrid.net with SMTP id filter1445p1mdw1-2036-5B1EA02D-7 2018-06-11 16:15:41.09176847 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id ggdUIeTuThiTyPo3XQV7yQ for ; Mon, 11 Jun 2018 16:15:41.046 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id 0908241083 for ; Mon, 11 Jun 2018 09:15:41 -0700 (PDT) Date: Mon, 11 Jun 2018 16:15:41 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Don't cite octet indices any more (#1437) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea02d6bf6_ffd3fa653a5af8062520"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2Q3NVOS2PAI/Bp5QqRTQim43syE615k6+4HV LfLYGZhL9Ee3Uw9FJqUmR1QlLEqT+MRyy6aTSksNcI0mGpWgwdOb2z/+KhHV4+2M73cBTiW3tXZKQw 8pX3B9qXaT1gR0gD9Hl2b+Y4QZY5UIaJRBQh8VFnK6/9yObmh6eMyMDA/JjorfQXCbSNJIJQzHdsG1 8= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:15:50 -0000 ----==_mimepart_5b1ea02d6bf6_ffd3fa653a5af8062520 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Also reflow. Closes #1436. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1437 -- Commit Summary -- * Don't cite octet indices any more -- File Changes -- M draft-ietf-quic-transport.md (27) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1437.patch https://github.com/quicwg/base-drafts/pull/1437.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/1437 ----==_mimepart_5b1ea02d6bf6_ffd3fa653a5af8062520 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Also reflow.

Closes #1436.

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

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

Commit Summary

  • Don't cite octet indices any more

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 mute the thread.

----==_mimepart_5b1ea02d6bf6_ffd3fa653a5af8062520-- From nobody Mon Jun 11 09:20:06 2018 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 65011131016 for ; Mon, 11 Jun 2018 09:19:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 NprjW2rjoYli for ; Mon, 11 Jun 2018 09:19:55 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D76A8130FF1 for ; Mon, 11 Jun 2018 09:19:54 -0700 (PDT) Date: Mon, 11 Jun 2018 09:19:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528733994; bh=Z5/TvmyJ2FPfYSWYqM/XdTg0AxH+hnXEbuxQ/QheE8U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zl1rZrPR5jhwBZV5H/vxIA/CuJWbiLoafT11B6HgqSjvM0VGQnS1rJ5pYCwuCGn7Y Jc2/syKjvPuaIsHvtn5Wd7x2KOoBNxY0VPL5PgrSLYFxMlBnO9ZoCHKx09EyzODsZE k1VjogxsnhjigGe3H/RdMXaa7COo+SofdH9fBy4k= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't cite octet indices any more (#1437) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea12a12107_16792ade70bdef601226c0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 16:19:58 -0000 ----==_mimepart_5b1ea12a12107_16792ade70bdef601226c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. -- 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/1437#pullrequestreview-127640424 ----==_mimepart_5b1ea12a12107_16792ade70bdef601226c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

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

----==_mimepart_5b1ea12a12107_16792ade70bdef601226c0-- From nobody Mon Jun 11 09:25:07 2018 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 925FA131057 for ; Mon, 11 Jun 2018 09:25:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 qGDzyup8WmfA for ; Mon, 11 Jun 2018 09:25:00 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 ED17D1310A9 for ; Mon, 11 Jun 2018 09:24:59 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528734299; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=xJaR3q1iTIFcmWojCpiVORFkljcIWR1X/jtCbzPIUdY=; b=czKAnbUe1opC3wwfakwEo2lvm8r00i3sMFPuTYK6N01wicKLwigHVZJi3HJMLj3IzxWFStFj VdIpGim5Mntkici5Ig0ZO//iSZjhjW9l3bQwP9BP8fRz+pFPObZf38pqrpX68rOYe58/+b6/ ocMoTZHaG65y8uh1BRhgmJFj1rE= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b1ea002.7fb6ecaa5330-smtp-out-n03; Mon, 11 Jun 2018 16:14:58 -0000 (UTC) Date: Mon, 11 Jun 2018 09:14:57 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b1ea00114077_70de2ad5d8ae7c1040483@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] f1be41: Don't cite octet indices any more Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1ea00113c8c_70de2ad5d8ae7c104038d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 16:25:07 -0000 ----==_mimepart_5b1ea00113c8c_70de2ad5d8ae7c104038d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/issue1436 Home: https://github.com/quicwg/base-drafts Commit: f1be4128b8eb32575cf4c5f1915deed935488f11 https://github.com/quicwg/base-drafts/commit/f1be4128b8eb32575cf4c5f1915deed935488f11 Author: Martin Thomson Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Don't cite octet indices any more Also reflow. Closes #1436. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1ea00113c8c_70de2ad5d8ae7c104038d-- From nobody Mon Jun 11 09:29:21 2018 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 B51D4130FD4 for ; Mon, 11 Jun 2018 09:29:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 mkQqe9--YLI3 for ; Mon, 11 Jun 2018 09:29:18 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D2A6130E72 for ; Mon, 11 Jun 2018 09:29:18 -0700 (PDT) Date: Mon, 11 Jun 2018 09:29:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528734558; bh=L3bifPrH7/TkONbsvRXdHtiUZRhF0WquaLKaklOhSbE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wy6aocN+m/cdwg//y7ICFxanJ2+akga2XnyATZIGpLmyiryZNrUawM/lKst1k5zUq 3M0eXL9KB7PDwNCkSBcNBtaH6n+2yCyxuefAwfwUzvPN+ydrMcGUboU5OEHQRSYYSM 072Ntd34nTKmj+3KpZdlqGNrIYptgoD3ThvETPQs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea35dcd848_24a72b1615ad6f50234419"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:29:20 -0000 ----==_mimepart_5b1ea35dcd848_24a72b1615ad6f50234419 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We don't actually define idleness. Big surprise. @ianswett had a more concise answer and I can't remember it right now. It might be reasonable to define it as not including TLP or RTO (for sending). Then RTO has a hard limit. -- 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/1429#issuecomment-396303809 ----==_mimepart_5b1ea35dcd848_24a72b1615ad6f50234419 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We don't actually define idleness. Big surprise.

@ianswett had a more concise answer and I can't remember it right now.

It might be reasonable to define it as not including TLP or RTO (for sending). Then RTO has a hard limit.

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

----==_mimepart_5b1ea35dcd848_24a72b1615ad6f50234419-- From nobody Mon Jun 11 09:36:05 2018 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 AABD6130DFF for ; Mon, 11 Jun 2018 09:36:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 8HF7vnKXJPob for ; Mon, 11 Jun 2018 09:36:02 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E7D7E130FD4 for ; Mon, 11 Jun 2018 09:36:01 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528734961; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zVBJv76MTGArwjw/6I807t0CeGhtPrlw0gExaw0UxGM=; b=vtNIRtC4XD3+5GwtO1ld7fajlV3fpg18LfLKSW0mnXJ7N01AVIIa8dBmColu4tE0eeWL39WJ AtsaUuq54wWwdYMgjeMXZ98f0h9B7v/hGk6buZ1wewXh0xXYGftJWTayp8X+ZsaYVFlC8bjz LpxCF8V4LIYN39cIDg1pWrQRfVM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b1ea4f0.7febf6af2090-smtp-out-n01; Mon, 11 Jun 2018 16:36:00 -0000 (UTC) Date: Mon, 11 Jun 2018 09:35:59 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b1ea4ef57f4a_2fc6e2b0f77d53c14969b1@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] f1be41: Don't cite octet indices any more Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1ea4ef57adf_2fc6e2b0f77d53c14968f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 16:36:04 -0000 ----==_mimepart_5b1ea4ef57adf_2fc6e2b0f77d53c14968f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: f1be4128b8eb32575cf4c5f1915deed935488f11 https://github.com/quicwg/base-drafts/commit/f1be4128b8eb32575cf4c5f1915deed935488f11 Author: Martin Thomson Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Don't cite octet indices any more Also reflow. Closes #1436. Commit: 09ddfcfaac573872bd1adaeed99e58b7a8f16be7 https://github.com/quicwg/base-drafts/commit/09ddfcfaac573872bd1adaeed99e58b7a8f16be7 Author: Martin Thomson Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1437 from quicwg/issue1436 Don't cite octet indices any more Compare: https://github.com/quicwg/base-drafts/compare/7c2d2495b9fd...09ddfcfaac57 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1ea4ef57adf_2fc6e2b0f77d53c14968f8-- From nobody Mon Jun 11 09:36:16 2018 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 57B31130FF1 for ; Mon, 11 Jun 2018 09:36:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 kNdcyNvEQx0x for ; Mon, 11 Jun 2018 09:36:03 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15C58130FE5 for ; Mon, 11 Jun 2018 09:36:03 -0700 (PDT) Date: Mon, 11 Jun 2018 09:36:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528734962; bh=jAofuFO3uF7xi1sIwR0k/LiId7wMnQ/Rat1a9To0Tlc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ju0rRR5Jc25REGk9PNZ2C0S0hSo6osLCiPCtn4ZDACANDtgAhV90tTjkL+FJIvGQf L18P1ZJIDRLBEN/vno10eoZZ04PhdM90Vp6dufRd4Qzyb99Zs8nh6pPwlvgpSavESa NqK5+oxV0iMqxjX5iE9ptcLTyGrsIy7aGxEJkfR0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't cite octet indices any more (#1437) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea4f23990b_4ce83faa12ab6f8425845b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:36:06 -0000 ----==_mimepart_5b1ea4f23990b_4ce83faa12ab6f8425845b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1437. -- 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/1437#event-1674345688 ----==_mimepart_5b1ea4f23990b_4ce83faa12ab6f8425845b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1437.

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

----==_mimepart_5b1ea4f23990b_4ce83faa12ab6f8425845b-- From nobody Mon Jun 11 09:36:21 2018 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 902D6131006 for ; Mon, 11 Jun 2018 09:36:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.899 X-Spam-Level: X-Spam-Status: No, score=0.899 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 tZur2ayVwaoT for ; Mon, 11 Jun 2018 09:36:05 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 B3611130DFF for ; Mon, 11 Jun 2018 09:36:04 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528734964; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=r0sRnOoVk5WwY0Af67eb2nhBQxsJG9wIzlImEIQPf2Y=; b=iLfa8rkK6euO3frMsPpIR6izUQ4CziN3w/nYG9MMz2Ae7ct+oB6zlIHblDpubl/V6lMtHuOD fBBwJgUJe6/hXZ4KJzIGD0U3nV56ELw64h8HY4Z9HlpiBNfCj6HvjqfU013rtnYsotayUiD+ gT7y+h3X1UGTcvxlvZN7lrkovcY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b1ea4f4.7f82b84dab70-smtp-out-n03; Mon, 11 Jun 2018 16:36:04 -0000 (UTC) Date: Mon, 11 Jun 2018 09:36:03 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b1ea4f32c5c1_2f62f2aab3f549c04956fb@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1ea4f32c29d_2f62f2aab3f549c0495557"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 16:36:08 -0000 ----==_mimepart_5b1ea4f32c29d_2f62f2aab3f549c0495557 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/issue1436 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1ea4f32c29d_2f62f2aab3f549c0495557-- From nobody Mon Jun 11 09:36:27 2018 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 1657013100F for ; Mon, 11 Jun 2018 09:36:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 at_GLtJ8msR1 for ; Mon, 11 Jun 2018 09:36:04 -0700 (PDT) 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 DEE7C130FD4 for ; Mon, 11 Jun 2018 09:36:03 -0700 (PDT) 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=8LqgCJ03Yc3BrfSJbUIOQFMB0Ec=; b=ZbsSBCQ+xW370yyl REKOGvxBLsOIHqfugLE4PeQgfpm9S/WN6hCtHWdnyI6jt6IRfWSk+0hzw/4R+jQ4 MvMlvIBhmXQAGRPi/AktDh0zEzkNEsVo4z43ngy66NOb4UB9gHV4mvfkTo/pYvMe TkilaLOH1z3a2xeWOB+EgrfOyfc= Received: by filter1339p1mdw1.sendgrid.net with SMTP id filter1339p1mdw1-3863-5B1EA4F3-2 2018-06-11 16:36:03.032199723 +0000 UTC Received: from github-lowworker16-cp1-prd.iad.github.net (unknown [192.30.252.40]) by ismtpd0048p1mdw1.sendgrid.net (SG) with ESMTP id Jmm5aPIcQi6vabZom0CvYA for ; Mon, 11 Jun 2018 16:36:02.922 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker16-cp1-prd.iad.github.net (Postfix) with ESMTP id BD842210A1 for ; Mon, 11 Jun 2018 09:36:02 -0700 (PDT) Date: Mon, 11 Jun 2018 16:36:03 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] octet 1 of Long Header (#1436) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea4f2bbe3c_56893ffbdb618f84273447"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3MLXYpr7CpncI3bDKx/KDaSSopH7AZEPTt9Y p9ST3YG9eamGEZvT0Kb1gNlNTDX4gH4QQIILYWLlPmjzENFZ2s2G/F9lTkEMFhwafjElfckq5OeWUJ sc/CghmS4Y9tNuVzRoC6zUGXBJDQqjqpjQAgH4cnvkQW5Bw3PdbUmMeJZA6oie3gS2edsaK+Jurjn9 Y= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:36:08 -0000 ----==_mimepart_5b1ea4f2bbe3c_56893ffbdb618f84273447 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1436 via #1437. -- 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/1436#event-1674345696 ----==_mimepart_5b1ea4f2bbe3c_56893ffbdb618f84273447 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1436 via #1437.

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

----==_mimepart_5b1ea4f2bbe3c_56893ffbdb618f84273447-- From nobody Mon Jun 11 09:51:25 2018 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 44233131012 for ; Mon, 11 Jun 2018 09:51:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FHvAmbX_cTiN for ; Mon, 11 Jun 2018 09:51:20 -0700 (PDT) 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 9BF7313100F for ; Mon, 11 Jun 2018 09:51:20 -0700 (PDT) Date: Mon, 11 Jun 2018 09:51:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528735878; bh=c4GUAZWUMgdtH/7NdvIrfG61cW8UCpWeuz7LRzMZQcQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JeGGBftzT80X7O1BYzq26k63I2TLDqth+jOXLHn9VHmBvTSq0x//eYUh09SxDn3Y1 rVvhR098dg3r2YH6d6ojRogZD6SRHR3yAGC4UYA4+qaHSexoVKOsEp1awndoE3LwTD 5pAcaw6mO21QyKxLXKyOWu7jubuNCMpZWrgCOILc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea886dba60_15142ac965198f5832533a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 16:51:24 -0000 ----==_mimepart_5b1ea886dba60_15142ac965198f5832533a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Thanks for doing this Igor. This is a lot of new words, but generally good. I think that we probably need to do something to break this up a little. I also think that implementations will not be able to save anything of the IP ID, and won't be inclined to save anything from the packet. So we might want to suggest a mode switch when a packet is received. > @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields. All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP fragmentation or packet drops. To optimize bandwidth efficiency, endpoints SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}). Endpoints -MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for -detecting the PMTU, setting the PMTU appropriately, and storing the result of -previous PMTU determinations. +MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) "classical" isn't a useful description of the mechanism. If you need to distinguish this between PLPMTUD, talk about using ICMP feedback. > -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially -vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and -reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this -risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP -message to validate the TCP sequence number as valid for the current -connection. However, as QUIC operates over UDP, in IPv4 the echoed information -could consist only of the IP and UDP headers, which usually has insufficient -entropy to mitigate off-path attacks. +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}}, +which requires ICMPv6 error messages to contain "as much of invoking packet as +possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and +{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMP messages without an on-path prooff are sent in typo: prooff > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by this endpoint with at least 1-2^32 +probability and it is still outstanding (not acknowledged and not deemed lost). How does one make this determination? > * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that -most invalid ICMP messages arrive when there are no DF packets outstanding, and -can therefore be identified as spurious. + most invalid ICMP messages arrive when there are no DF packets outstanding, + and can therefore be identified as spurious. + +* Store IP ID field of the sent datagrams to validate that ICMP message is + refering to an outstanding packet. More IPv4 advice, which should be called out as such. I don't think that senders will remember this if it is not predictable. > + most invalid ICMP messages arrive when there are no DF packets outstanding, + and can therefore be identified as spurious. + +* Store IP ID field of the sent datagrams to validate that ICMP message is + refering to an outstanding packet. + +Any ICMP messages that fail validation MUST be discarded. + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP Packet Too Big (PTB) message during a handshake, +unless then would cause a reduction to a Path MTU value smaller than 1280 +octets. + +If during a handshake a client receives an ICMP TPB message that requests it to PTB? > + refering to an outstanding packet. + +Any ICMP messages that fail validation MUST be discarded. + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP Packet Too Big (PTB) message during a handshake, +unless then would cause a reduction to a Path MTU value smaller than 1280 +octets. + +If during a handshake a client receives an ICMP TPB message that requests it to +reduce Path MTU to a value smaller than 1280 octets, then: + +* If the client has another IP address for the server to try, the client should + restart the connection to another IP. SHOULD? > + and can therefore be identified as spurious. + +* Store IP ID field of the sent datagrams to validate that ICMP message is + refering to an outstanding packet. + +Any ICMP messages that fail validation MUST be discarded. + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP Packet Too Big (PTB) message during a handshake, +unless then would cause a reduction to a Path MTU value smaller than 1280 +octets. + +If during a handshake a client receives an ICMP TPB message that requests it to +reduce Path MTU to a value smaller than 1280 octets, then: I think that this disagrees with the conclusion of the working group - we agreed that a PMTU of 1280 was necessary to support QUIC and that the response to a reduction in size was to ignore the signal. If the signal is true, this causes the connection to fail, but that's OK. > -* Any reduction in PMTU due to a report contained in an ICMP packet is +If an ICMP PTB message is received after handshake, and the claimed Path MTU is +at least 1280 octets for messages with on-path validation or 1392 for messages Where did this 1392 come from? > @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain application data, aggressive increases in probe size carry fewer consequences. +## Responding to ICMP "Unreachable" messages {#icmp-unreach} + +When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake, +the response SHOULD be identical to receiving an ICMP TPB message that announces +a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}). + +When an ICMP "Unreachable" message is received after the handshake, the QUIC +endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}). Sending SHOULD? If "SHOULD", how does an endpoint decide to do this (or not). If it is purely a rate-limiting thing, then maybe different words would help. -- 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/1412#pullrequestreview-127640520 ----==_mimepart_5b1ea886dba60_15142ac965198f5832533a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Thanks for doing this Igor.

This is a lot of new words, but generally good. I think that we probably need to do something to break this up a little.

I also think that implementations will not be able to save anything of the IP ID, and won't be inclined to save anything from the packet. So we might want to suggest a mode switch when a packet is received.

In draft-ietf-quic-transport.md:

> @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields.
 All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP
 fragmentation or packet drops. To optimize bandwidth efficiency, endpoints
 SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}).  Endpoints
-MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for
-detecting the PMTU, setting the PMTU appropriately, and storing the result of
-previous PMTU determinations.
+MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}})

"classical" isn't a useful description of the mechanism. If you need to distinguish this between PLPMTUD, talk about using ICMP feedback.

In draft-ietf-quic-transport.md:

> -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially
-vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and
-reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this
-risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP
-message to validate the TCP sequence number as valid for the current
-connection. However, as QUIC operates over UDP, in IPv4 the echoed information
-could consist only of the IP and UDP headers, which usually has insufficient
-entropy to mitigate off-path attacks.
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with
+an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}},
+which requires ICMPv6 error messages to contain "as much of invoking packet as
+possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and
+{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of
+the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMP messages without an on-path prooff are sent in

typo: prooff

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by this endpoint with at least 1-2^32
+probability and it is still outstanding (not acknowledged and not deemed lost).

How does one make this determination?

In draft-ietf-quic-transport.md:

>  
 * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that
-most invalid ICMP messages arrive when there are no DF packets outstanding, and
-can therefore be identified as spurious.
+  most invalid ICMP messages arrive when there are no DF packets outstanding,
+  and can therefore be identified as spurious.
+
+* Store IP ID field of the sent datagrams to validate that ICMP message is
+  refering to an outstanding packet.

More IPv4 advice, which should be called out as such. I don't think that senders will remember this if it is not predictable.

In draft-ietf-quic-transport.md:

> +  most invalid ICMP messages arrive when there are no DF packets outstanding,
+  and can therefore be identified as spurious.
+
+* Store IP ID field of the sent datagrams to validate that ICMP message is
+  refering to an outstanding packet.
+
+Any ICMP messages that fail validation MUST be discarded.
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP Packet Too Big (PTB) message during a handshake,
+unless then would cause a reduction to a Path MTU value smaller than 1280
+octets.
+
+If during a handshake a client receives an ICMP TPB message that requests it to

PTB?

In draft-ietf-quic-transport.md:

> +  refering to an outstanding packet.
+
+Any ICMP messages that fail validation MUST be discarded.
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP Packet Too Big (PTB) message during a handshake,
+unless then would cause a reduction to a Path MTU value smaller than 1280
+octets.
+
+If during a handshake a client receives an ICMP TPB message that requests it to
+reduce Path MTU to a value smaller than 1280 octets, then:
+
+* If the client has another IP address for the server to try, the client should
+  restart the connection to another IP.

SHOULD?

In draft-ietf-quic-transport.md:

> +  and can therefore be identified as spurious.
+
+* Store IP ID field of the sent datagrams to validate that ICMP message is
+  refering to an outstanding packet.
+
+Any ICMP messages that fail validation MUST be discarded.
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP Packet Too Big (PTB) message during a handshake,
+unless then would cause a reduction to a Path MTU value smaller than 1280
+octets.
+
+If during a handshake a client receives an ICMP TPB message that requests it to
+reduce Path MTU to a value smaller than 1280 octets, then:

I think that this disagrees with the conclusion of the working group - we agreed that a PMTU of 1280 was necessary to support QUIC and that the response to a reduction in size was to ignore the signal. If the signal is true, this causes the connection to fail, but that's OK.

In draft-ietf-quic-transport.md:

>  
-* Any reduction in PMTU due to a report contained in an ICMP packet is
+If an ICMP PTB message is received after handshake, and the claimed Path MTU is
+at least 1280 octets for messages with on-path validation or 1392 for messages

Where did this 1392 come from?

In draft-ietf-quic-transport.md:

> @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain
 application data, aggressive increases in probe size carry fewer consequences.
 
 
+## Responding to ICMP "Unreachable" messages {#icmp-unreach}
+
+When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake,
+the response SHOULD be identical to receiving an ICMP TPB message that announces
+a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}).
+
+When an ICMP "Unreachable" message is received after the handshake, the QUIC
+endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}).  Sending

SHOULD?

If "SHOULD", how does an endpoint decide to do this (or not). If it is purely a rate-limiting thing, then maybe different words would help.

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

----==_mimepart_5b1ea886dba60_15142ac965198f5832533a-- From nobody Mon Jun 11 09:55:49 2018 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 A081A13100F for ; Mon, 11 Jun 2018 09:55:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DOo8oNcLWGWX for ; Mon, 11 Jun 2018 09:55:44 -0700 (PDT) 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 5F725131007 for ; Mon, 11 Jun 2018 09:55:44 -0700 (PDT) Date: Mon, 11 Jun 2018 09:55:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528736143; bh=dwoHquzFVAD7nvzKYvytjMhbVhKwr2/NqOMyjVIeS/o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JpOlCFsV21aZbAcX4HhcUloWdHXIzqfhmJSkkiIXKwWkmacWDUTLEqCyuiffGHK/o A+urSdcLd9QvmMsAnQCtv/om3vJjER9G2kcohNrOeXDEG061ooDp4Q0WIGb+lmLOP1 1xdeqliVR5CW9jn/ZzartNo7CfMwUAubwYpwXo3o= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ea98f8103d_671e3fb445800f7843248b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 16:55:47 -0000 ----==_mimepart_5b1ea98f8103d_671e3fb445800f7843248b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit One fairly good definition of the start of idleness is the max(time of last received packet, time of last sent packet after a packet was received). The latter is there to ensure you don't idle timeout immediately after sending a request. Though if you're RTOing packets you're not technically idle, there's no proof the connection is still alive, so extending the idle timeout when sending timer based retransmissions is quite dangerous. There is some inherent asymmetry between when you should no longer send new data vs when you should stop receiving data. Ideally you'd continue processing incoming data for at least an RTT longer than you would send new data. There are definitely some potential benefits in timing out the connection earlier when you believe it's dead, such as after 5RTOs or another criteria, but I'd be hesitant to recommend a uniform approach to dead connection detection for all applications and circumstances. I think H2 commonly bundles a ping with new requests and then there's a subsequent timeout? In QUIC, the PING wouldn't be necessary, since the request gets acknowledged. -- 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/1429#issuecomment-396311683 ----==_mimepart_5b1ea98f8103d_671e3fb445800f7843248b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One fairly good definition of the start of idleness is the max(time of= last received packet, time of last sent packet after a packet was receiv= ed). The latter is there to ensure you don't idle timeout immediately af= ter sending a request.

Though if you're RTOing packets you're not technically idle, there's n= o proof the connection is still alive, so extending the idle timeout when= sending timer based retransmissions is quite dangerous.

There is some inherent asymmetry between when you should no longer sen= d new data vs when you should stop receiving data. Ideally you'd continu= e processing incoming data for at least an RTT longer than you would send= new data.

There are definitely some potential benefits in timing out the connect= ion earlier when you believe it's dead, such as after 5RTOs or another cr= iteria, but I'd be hesitant to recommend a uniform approach to dead conne= ction detection for all applications and circumstances. I think H2 commo= nly bundles a ping with new requests and then there's a subsequent timeou= t? In QUIC, the PING wouldn't be necessary, since the request gets ackno= wledged.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1ea98f8103d_671e3fb445800f7843248b-- From nobody Mon Jun 11 09:59:51 2018 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 9B3E01310DA for ; Mon, 11 Jun 2018 09:59:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qSmJ1tAzj6_d for ; Mon, 11 Jun 2018 09:59:27 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92FB31310B7 for ; Mon, 11 Jun 2018 09:59:27 -0700 (PDT) Date: Mon, 11 Jun 2018 09:59:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528736366; bh=urdSOXx4C23sWqY4cR329/mgT44v6ij9UNjZLJNdG50=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=D4OlSop5W6iEqmEDBQqu5ocJCOFNmAJpUFsyCegSlCsM0jdiORHRTuFvQDBa6CKba TgrPN/B1CqJ+h2c3JLDdPGAUCNo/XBpDqWT5u/EzUvo2D4kWdKQGmkUhHkLwPZeWYt JUyfTy9grVuQzfujcb4kqv0T/slU5Z4DcxnIToIo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eaa6ed7b51_10123fa653a5af803112f8"; 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.26 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, 11 Jun 2018 16:59:37 -0000 ----==_mimepart_5b1eaa6ed7b51_10123fa653a5af803112f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Because the possible sizes on HQ frames are so very large, I tend to think of them as being "regions" in the stream. Some are have to be received entire before you can do much useful with them (HEADERS, PRIORITY); others can reasonably be streamed (DATA). HEADERS are the easiest place to deadlock, and one of the holdovers from HTTP/2 is an explicit communication of the largest header payload you're willing to process. -- 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/1432#issuecomment-396312823 ----==_mimepart_5b1eaa6ed7b51_10123fa653a5af803112f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Because the possible sizes on HQ frames are so very large, I tend to t= hink of them as being "regions" in the stream. Some are have to be recei= ved entire before you can do much useful with them (HEADERS, PRIORITY); o= thers can reasonably be streamed (DATA). HEADERS are the easiest place t= o deadlock, and one of the holdovers from HTTP/2 is an explicit communica= tion of the largest header payload you're willing to process.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1eaa6ed7b51_10123fa653a5af803112f8-- From nobody Mon Jun 11 10:12:00 2018 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 3AC36130E3A for ; Mon, 11 Jun 2018 10:11:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Gs6yPprgMACq for ; Mon, 11 Jun 2018 10:11:56 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57699126CB6 for ; Mon, 11 Jun 2018 10:11:56 -0700 (PDT) Date: Mon, 11 Jun 2018 10:11:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528737115; bh=xEIsuZraUpmO0D+KrDqArfuRzfqaX712WnUYV//c2FY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wCyKJFlX2H+8Wicb/WTVb1+m8Au5mv3kk9OW1PUa6PaNptdq47m0J9UeaANv+IpvR vvlLRhnWvt/9vwN/6Ktpk+0+EaPBXowB3p+iHS2+CRZOcVY9YmXp2iIpg7edLWXz2b JbXOHe2EgsCQQsJQ6JDrFnuKoVBqCq9uYAHiJ3zw= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ead5b89526_10123fa653a5af803722e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 11 Jun 2018 17:11:59 -0000 ----==_mimepart_5b1ead5b89526_10123fa653a5af803722e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by this endpoint with at least 1-2^32 +probability and it is still outstanding (not acknowledged and not deemed lost). +If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the +packet as an ICMP message without an on-path proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. + +Even ICMP messages without an on-path proof SHOULD undergo some validation, such +as: * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that I also wondered ... -- 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/1412#discussion_r194478406 ----==_mimepart_5b1ead5b89526_10123fa653a5af803722e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by this endpoint with at least 1-2^32
+probability and it is still outstanding (not acknowledged and not deemed lost).
+If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the
+packet as an ICMP message without an on-path proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.
+
+Even ICMP messages without an on-path proof SHOULD undergo some validation, such
+as:
 
 * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that

I also wondered ...

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

----==_mimepart_5b1ead5b89526_10123fa653a5af803722e7-- From nobody Mon Jun 11 10:14:36 2018 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 8B4E0130E70 for ; Mon, 11 Jun 2018 10:14:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 ejnfdCsaQ4ja for ; Mon, 11 Jun 2018 10:14:33 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 319DE130E3A for ; Mon, 11 Jun 2018 10:14:33 -0700 (PDT) Date: Mon, 11 Jun 2018 10:14:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528737272; bh=lG89cgfGkfn3i2TTdh3kPrf+q6gqSyjS0qEbAP1bnhs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vqx5WIkacqzBR+u6HHmoEuXw/dMrvnVkLnLn3KtC4jA1dk4Nd0EHouo8ienyf2qyx x6ux8gBqZgWj6MjPrLJOgqWaDdl2Q1XWeVKQfAM/Rk4zVCYpVjwLTiqIAFfLTckzcn cYcu+Vhebl8U4OjBD3in9TKUNSpn5XmWz+VdH2lY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't cite octet indices any more (#1437) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eadf865e0b_3e552acf29810f603625ed"; 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.26 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, 11 Jun 2018 17:14:35 -0000 ----==_mimepart_5b1eadf865e0b_3e552acf29810f603625ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -443,7 +444,7 @@ Google QUIC Demultipexing Bit: Reserved: : The sixth, seventh, and eighth bits (0x7) of octet 0 are reserved for You've removed "octet 1" above, but still have "octet 0" here. -- 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/1437#pullrequestreview-127659775 ----==_mimepart_5b1eadf865e0b_3e552acf29810f603625ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -443,7 +444,7 @@ Google QUIC Demultipexing Bit:
 Reserved:
 
 : The sixth, seventh, and eighth bits (0x7) of octet 0 are reserved for

You've removed "octet 1" above, but still have "octet 0" here.

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

----==_mimepart_5b1eadf865e0b_3e552acf29810f603625ed-- From nobody Mon Jun 11 10:17:50 2018 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 888CB131052 for ; Mon, 11 Jun 2018 10:17:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 IpMHrJ6CwJCM for ; Mon, 11 Jun 2018 10:17:38 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9119B130FF9 for ; Mon, 11 Jun 2018 10:17:38 -0700 (PDT) Date: Mon, 11 Jun 2018 10:17:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528737458; bh=FcryaUGKFejGoDWzvW+5xMSM4316d454JvBi/+Rn7B4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u5hTRv4oCKAA7uyWHby+UxlWBsTMZ5+OHxn0iS6ZO79uGn3YIIrMhNprTKvtJIDlV wuQx40qO76f4MDlnzCro2FxW1mvVgXkgbfHpuRIHzBWc6UU7tuNw3IHqtMI0WohfKF Lecdq52mHUWRl7VPS8kSnvLYsljih1b0eq86a6mQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eaeb2137ab_63293fd30eed4f88625868"; 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.26 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, 11 Jun 2018 17:17:48 -0000 ----==_mimepart_5b1eaeb2137ab_63293fd30eed4f88625868 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Can't be an invariant; the existence of frames isn't an invariant, so their properties are even less so. -- 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/1424#issuecomment-396318233 ----==_mimepart_5b1eaeb2137ab_63293fd30eed4f88625868 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Can't be an invariant; the existence of frames isn't an invariant, so their properties are even less so.

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

----==_mimepart_5b1eaeb2137ab_63293fd30eed4f88625868-- From nobody Mon Jun 11 10:22:55 2018 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 14A9F130E85 for ; Mon, 11 Jun 2018 10:22:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8L0P-bVLfqfC for ; Mon, 11 Jun 2018 10:22:52 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B194A130E83 for ; Mon, 11 Jun 2018 10:22:52 -0700 (PDT) Date: Mon, 11 Jun 2018 10:22:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528737772; bh=4ZiETzmuIBybvZnYMc8ZeBTQK/VanAwd/EWIMacCg70=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FNypKCp0jtGyCb76hMqS/ztqhlndNdlJdsiRfRtXIG5HKPoGLRhUj7IkdvNFYscTi r52hugWERyQC0pBor+zFRGSCnPQVC5+Z70Wi9r3gaKMZIMQ9aXJqHZpIGz8JbQKW7u 2VaeBPy0ElkOttlYlA40kKVPWwoNktQIU8CWaUWw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eafec18fc5_12a83f9e37c04f803468d8"; 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.26 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, 11 Jun 2018 17:22:54 -0000 ----==_mimepart_5b1eafec18fc5_12a83f9e37c04f803468d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The case where the second CID is from a different host is relatively benign -- the receiver would process it and discard it anyway. More insidious is when the two CIDs are both from the same connection -- you've just given a pretty strong linkability signal. I'm inclined to say that you MUST NOT send different CIDs, and receivers SHOULD skip any subsequent packet whose DCID differs from that of the first packet. -- 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/1423#issuecomment-396319677 ----==_mimepart_5b1eafec18fc5_12a83f9e37c04f803468d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The case where the second CID is from a different host is relatively b= enign -- the receiver would process it and discard it anyway. More insid= ious is when the two CIDs are both from the same connection -- you've jus= t given a pretty strong linkability signal.

I'm inclined to say that you MUST NOT send different CIDs, and receive= rs SHOULD skip any subsequent packet whose DCID differs from that of the = first packet.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b1eafec18fc5_12a83f9e37c04f803468d8-- From nobody Mon Jun 11 10:30:40 2018 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 763C4130E86 for ; Mon, 11 Jun 2018 10:30:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 4ZRUR69kKqnd for ; Mon, 11 Jun 2018 10:30:36 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 F2555130E7D for ; Mon, 11 Jun 2018 10:30:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528738235; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=MI//0PKP4d0XCllThD6mr234fGaE7cxdP8uP7lvOW+0=; b=ITk9/XjGvCd79UQurVINP5wSI8tlji7Shm6Kr1oGRoQZGHjmF50y0ePoF7OigFCMT0D3P6NM AYhuOHK+Qw2NSZs9GGTKpr+8K4f/n9uQiRB6YjBtaPiihV3vbrJdTWUXKCP9iDCLb0Ckk+CR kQbENC4q+0aNqPHjIX29mtxnXAw= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b1eb1ba.7fae9a907bd0-smtp-out-n01; Mon, 11 Jun 2018 17:30:34 -0000 (UTC) Date: Mon, 11 Jun 2018 10:30:34 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1eb1ba250e8_7d42b25f9735c18541ac@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 26c5b7: No mixing CIDs Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1eb1ba24b82_7d42b25f9735c185407"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 17:30:38 -0000 ----==_mimepart_5b1eb1ba24b82_7d42b25f9735c185407 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts Commit: 26c5b742d37f6adbf84fecec5e0abf0d29563484 https://github.com/quicwg/base-drafts/commit/26c5b742d37f6adbf84fecec5e0abf0d29563484 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- No mixing CIDs **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1eb1ba24b82_7d42b25f9735c185407-- From nobody Mon Jun 11 10:30:47 2018 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 A61FB126CB6 for ; Mon, 11 Jun 2018 10:30:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 R8xdD_XE_wBK for ; Mon, 11 Jun 2018 10:30:38 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 E0084130E7D for ; Mon, 11 Jun 2018 10:30:37 -0700 (PDT) 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=X864tOvFel7QGzjARymu2wmxTl8=; b=QAvCJzAHTxKU9og0 C5BxtyPbuDU5IZWmH5DtzqrTzLeVIx9+FQ/aAARRR6aNdJXTC9/gibDmeziEE766 CI8wVtni/XCrKM/xoyG1dc3N4zeRh8j5ikv9Rw0kmj/YwPBt0iATw7zRpG69DOUy 6lP5kG/FT4DTkGmYY1PlBbuaS1k= Received: by filter1338p1mdw1.sendgrid.net with SMTP id filter1338p1mdw1-5422-5B1EB1BD-8 2018-06-11 17:30:37.203079512 +0000 UTC Received: from github-lowworker-d2dd71d.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id 2ya9bwh-Tga9AnHIlE7VPQ for ; Mon, 11 Jun 2018 17:30:37.153 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-d2dd71d.cp1-iad.github.net (Postfix) with ESMTP id 20054881414 for ; Mon, 11 Jun 2018 10:30:37 -0700 (PDT) Date: Mon, 11 Jun 2018 17:30:37 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb1bd1e47f_4c533faa12ab6f845804d4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3tYoiZ1PmRfwGP6/G1aQ6aCKG1HCZZ5GHs92 xNWxCobmVsXdEVVLv6SIea3qCV5n3gB0se5rLeKGE6nDXbFWcTv4inkSsmAbuHEN4M0g8yNHpXMill wKosBBE1ciThKIuliWWBrT9AQz4da5Oz5vBA31GVvWrrvKWzo5hCkJl4Ez9fi5UXm9pY1e4kOcJT0K w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 17:30:40 -0000 ----==_mimepart_5b1eb1bd1e47f_4c533faa12ab6f845804d4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 26c5b74 No mixing CIDs -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1423/files/e77227596318c72d844707655d68bf59dc5c0bfb..26c5b742d37f6adbf84fecec5e0abf0d29563484 ----==_mimepart_5b1eb1bd1e47f_4c533faa12ab6f845804d4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1eb1bd1e47f_4c533faa12ab6f845804d4-- From nobody Mon Jun 11 10:36:30 2018 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 34FA6130E7E for ; Mon, 11 Jun 2018 10:36:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 J5KU_587r2xt for ; Mon, 11 Jun 2018 10:36:26 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99376130E7D for ; Mon, 11 Jun 2018 10:36:26 -0700 (PDT) Date: Mon, 11 Jun 2018 10:36:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528738585; bh=qmkPrVGEX/fmeSgeD0WHTLmzbWRTgIwul2nFWuRXDCI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aPUfgUbiUcL0jI+lG0/D9S7Kf+3nxQXAV9geHiXZW/TM4kKF+AKAu//zi2iZpiGF+ sn2coFnba7fJdb4q56419VhBC+x6mZhadULOKmbNFuRvZ0mtY14MnQSslGD+Vo4y8y sXv2i3pHr8xz5hz0rAd9WspdUENNSFHzt4lvKZWc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb319d1357_49a92ad076ad6f586159df"; 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.26 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, 11 Jun 2018 17:36:29 -0000 ----==_mimepart_5b1eb319d1357_49a92ad076ad6f586159df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree with the general premise that if we want to retain the flexibility to do something other than push with these streams in this version, there has to be a type indicator. -- 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/1359#issuecomment-396323980 ----==_mimepart_5b1eb319d1357_49a92ad076ad6f586159df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I agree with the general premise that if we want to retain the flexibility to do something other than push with these streams in this version, there has to be a type indicator.

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

----==_mimepart_5b1eb319d1357_49a92ad076ad6f586159df-- From nobody Mon Jun 11 10:38:40 2018 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 8119A130E7E for ; Mon, 11 Jun 2018 10:38:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 E5GHOz8poLLI for ; Mon, 11 Jun 2018 10:38:36 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 0F0BC130E7D for ; Mon, 11 Jun 2018 10:38:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528738715; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=+nBxpPVtrhXofe5H7B4szH+WycC7/D9jSOeMhsOfrs8=; b=Aa5wIFWFwRZ2pR9aWcJ2DneYoZqTz5YMpxfEZRBhwHurWN13h8YI8leaUV+FyLDte7Y9GYr0 3ZknEemMnPHnfOSduDALHJXmmrWFWB3sznuGJl8f+rc9AATOu6Lhp2aPh72VaFqXGFMbZy5C Y6svlYm/lowSy+P4WHoxAZMj17M= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b1eb39b.7fd60d947750-smtp-out-n02; Mon, 11 Jun 2018 17:38:35 -0000 (UTC) Date: Mon, 11 Jun 2018 10:38:34 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1eb39ae0e3e_43ab2af74617bc141046d4@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 493a2b: WIP: Unidirectional stream headers Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1eb39ae09ff_43ab2af74617bc14104581"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 17:38:38 -0000 ----==_mimepart_5b1eb39ae09ff_43ab2af74617bc14104581 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http_unidirectional Home: https://github.com/quicwg/base-drafts Commit: 493a2bb40501917d0dfad5ed1947f941f7522105 https://github.com/quicwg/base-drafts/commit/493a2bb40501917d0dfad5ed1947f941f7522105 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- WIP: Unidirectional stream headers Commit: 4cf7775253c40b7f1201b6aa6e64bf953fdfe51f https://github.com/quicwg/base-drafts/commit/4cf7775253c40b7f1201b6aa6e64bf953fdfe51f Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Fixups Commit: 42ef1fb2f366047535a213c96c31dbe8541b344b https://github.com/quicwg/base-drafts/commit/42ef1fb2f366047535a213c96c31dbe8541b344b Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Critical streams Commit: 076bb27e2fdcd7aa93c1d1d7b954272d656e3621 https://github.com/quicwg/base-drafts/commit/076bb27e2fdcd7aa93c1d1d7b954272d656e3621 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- QPACK control streams Commit: 3c06399e10d03812db4241c45b5dec18643d7995 https://github.com/quicwg/base-drafts/commit/3c06399e10d03812db4241c45b5dec18643d7995 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- IANA registration Commit: f61a81124e717585370781de51f81f2e2062f7a6 https://github.com/quicwg/base-drafts/commit/f61a81124e717585370781de51f81f2e2062f7a6 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Review feedback Commit: 52329e67a1e02fab573975eab0a7a53b5524ac59 https://github.com/quicwg/base-drafts/commit/52329e67a1e02fab573975eab0a7a53b5524ac59 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Introduce stream terms Commit: 99f70462b2dff5a9891825030aefca5d383ea9b0 https://github.com/quicwg/base-drafts/commit/99f70462b2dff5a9891825030aefca5d383ea9b0 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- ASCII codes Commit: 7a21428cf0bf12c6028e756543337e0f56f3ef3f https://github.com/quicwg/base-drafts/commit/7a21428cf0bf12c6028e756543337e0f56f3ef3f Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Martin's comments Commit: b4ac757c321bee984d14f358ad22c7e14dc07527 https://github.com/quicwg/base-drafts/commit/b4ac757c321bee984d14f358ad22c7e14dc07527 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix ref breakage, again Commit: e425c3e9cee9f71fb9f26eace53eda6d011ebf03 https://github.com/quicwg/base-drafts/commit/e425c3e9cee9f71fb9f26eace53eda6d011ebf03 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Stray assumptions of control stream ID Compare: https://github.com/quicwg/base-drafts/compare/552d328a57a4...e425c3e9cee9 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1eb39ae09ff_43ab2af74617bc14104581-- From nobody Mon Jun 11 10:44:06 2018 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 81264130E86 for ; Mon, 11 Jun 2018 10:44:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lqty8MaDnMRg for ; Mon, 11 Jun 2018 10:44:02 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3618130E7E for ; Mon, 11 Jun 2018 10:44:02 -0700 (PDT) Date: Mon, 11 Jun 2018 10:44:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528739041; bh=yfS39d65Z0C+/TPs5CCzI22q2TF4sptCXPp2gYKqC+w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=H16k28BpDSBQRyggWxEeZ2EcSJSat91mxcw6HeIDkI0BIMQE3pUXByS1O9HVUPc8u pf4op8oToqMbNYgE7AjlaIAYqJERoI6+6mYy6qgdGAQpuZE0qERVE1eM616PRWS1mJ YIdrCCYQbxaLOF2nwigOOH9WG2Ri3/JI8JRd1nqA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb4e1c38f9_16972ade70bdef607168b5"; 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.26 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, 11 Jun 2018 17:44:05 -0000 ----==_mimepart_5b1eb4e1c38f9_16972ade70bdef607168b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Critical flaw with this proposal: If extra unidirectional stream types are no longer a breaking protocol change, the "rickroll" variant described in "Draft Version Guidance" is no longer a valid example of an incompatible experiment. ;-) -- 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/1359#issuecomment-396326390 ----==_mimepart_5b1eb4e1c38f9_16972ade70bdef607168b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Critical flaw with this proposal: If extra unidirectional stream types are no longer a breaking protocol change, the "rickroll" variant described in "Draft Version Guidance" is no longer a valid example of an incompatible experiment. ;-)

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

----==_mimepart_5b1eb4e1c38f9_16972ade70bdef607168b5-- From nobody Mon Jun 11 10:45:18 2018 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 DAD5B130E81 for ; Mon, 11 Jun 2018 10:45:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 HvfF7aio0J49 for ; Mon, 11 Jun 2018 10:45:14 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 95084130E7E for ; Mon, 11 Jun 2018 10:45:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528739114; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=C8qqUuAwQDKAq2DoQ3zobkQPw2kOcAjgS64lVcN8QW8=; b=IzLZPTL90QLNMzKcVXIlCQkeFke5qTNXl92xKv9IaP6JFbEcn6FfVFIZrS1EKQzMi7xC3nma AWK+TDBsj3BqrH5XeZT8WwvJOiOPckE7+36pXVCP1gYhFMh2WqjwOuAg7gQrJ/NrOOrv8JCR 82k4OCGeQeW4B/6vMFb1NUk8wzQ= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b1eb529.7f4ade6509f0-smtp-out-n01; Mon, 11 Jun 2018 17:45:13 -0000 (UTC) Date: Mon, 11 Jun 2018 10:45:12 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1eb528f17fc_7b9d2ac46ccd7c0066212@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 360886: Move Draft Version Identification section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1eb528f142e_7b9d2ac46ccd7c006611e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 17:45:16 -0000 ----==_mimepart_5b1eb528f142e_7b9d2ac46ccd7c006611e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 360886e613d3399ae61bec2568229fffc711924f https://github.com/quicwg/base-drafts/commit/360886e613d3399ae61bec2568229fffc711924f Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Move Draft Version Identification section Fixes #1415 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1eb528f142e_7b9d2ac46ccd7c006611e-- From nobody Mon Jun 11 10:45:25 2018 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 A2641130FBE for ; Mon, 11 Jun 2018 10:45:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 voQyXhqjR0nF for ; Mon, 11 Jun 2018 10:45:18 -0700 (PDT) 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 DF622130E7E for ; Mon, 11 Jun 2018 10:45:17 -0700 (PDT) Date: Mon, 11 Jun 2018 10:45:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528739116; bh=IBG0JI91V71SKfmnG/w1Xz7X/JmqVgIT2EFdJiu8QjY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ihvcxyD7EHlR36YbB8l6SCZTVML0TuW+PnuJMYzKctO7Fq3tXHXe56Qz1Ak0eUIJL 28Z5fvQDH6e9jYB5wYfjRBLVBoXTftfavXv9NdQ6N+ZS1LfRjwrRjS20I+HWL7wm6v nGA3VDSFKP3cVKnyM7+vfeW8EZhF73ca365r69EM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move Draft Version Identification section (#1427) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb52c76a80_4b912b08ca33af6057141c"; 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.26 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, 11 Jun 2018 17:45:20 -0000 ----==_mimepart_5b1eb52c76a80_4b912b08ca33af6057141c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1427. -- 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/1427#event-1674488340 ----==_mimepart_5b1eb52c76a80_4b912b08ca33af6057141c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1427.

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

----==_mimepart_5b1eb52c76a80_4b912b08ca33af6057141c-- From nobody Mon Jun 11 10:45:30 2018 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 C821F130E8C for ; Mon, 11 Jun 2018 10:45:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.262 X-Spam-Level: X-Spam-Status: No, score=-0.262 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 9aK29XvcinRI for ; Mon, 11 Jun 2018 10:45:19 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 56764130E81 for ; Mon, 11 Jun 2018 10:45:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528739117; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=CpKLoSvHHBr4syrkT3Nz3kzf90V/Qg1pxp5EJD/CtSg=; b=q4BCwGp3LMW5OUpfh0tu9+JnqS5YLgZAZc4eQdi7zxRBxilgy4RdTf0X0yGCxO/olpMA3k4d oudEgFvfjpw9Dac94NqIecNcGRp3D0nZ6QckbLc2WyrGFGQNa6Os9Fc+xvkUh5XbsUTZrkFW AK3gEveaBrBDFnODruHDqtusAJI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b1eb52d.7f105d47e4e0-smtp-out-n03; Mon, 11 Jun 2018 17:45:17 -0000 (UTC) Date: Mon, 11 Jun 2018 10:45:16 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b1eb52cf0968_36102b23ed01fc0c72463@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1eb52cf0523_36102b23ed01fc0c72394"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 17:45:21 -0000 ----==_mimepart_5b1eb52cf0523_36102b23ed01fc0c72394 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/move_draft_id Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1eb52cf0523_36102b23ed01fc0c72394-- From nobody Mon Jun 11 10:45:35 2018 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 5D6F1130E7E for ; Mon, 11 Jun 2018 10:45:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 OiUqqOHMNVuF for ; Mon, 11 Jun 2018 10:45:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2760130E7F for ; Mon, 11 Jun 2018 10:45:17 -0700 (PDT) Date: Mon, 11 Jun 2018 10:45:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528739116; bh=OAilzpOpnXES7vXoPqmBPhan7C4dC6MLh8tskDA75bc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fjx1a1F2l1iWiSKwPmhsJktsAZdjME0L35J3kkWpTAfnt7yBqP/nXW2E6f57N8GBe E53Ku1FjhPtqjDeH0w8lvB1pDkc0LrMSeYIRC8YzVRZgQ1qL4kC6FIk4zTXZvhP2zu DoRd7Z6qV03EYGexq1IzFBrLYwvsOBB1tCa9Bal8= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: Enhance guidance of using "hq" (#1415) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb52c15cd6_26943fa653a5af8014843b"; 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.26 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, 11 Jun 2018 17:45:22 -0000 ----==_mimepart_5b1eb52c15cd6_26943fa653a5af8014843b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1415 via #1427. -- 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/1415#event-1674488345 ----==_mimepart_5b1eb52c15cd6_26943fa653a5af8014843b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1415 via #1427.

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

----==_mimepart_5b1eb52c15cd6_26943fa653a5af8014843b-- From nobody Mon Jun 11 10:51:00 2018 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 C132D130E8F for ; Mon, 11 Jun 2018 10:50:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6nIizIm3yYSD for ; Mon, 11 Jun 2018 10:50:56 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11AAC130E8B for ; Mon, 11 Jun 2018 10:50:56 -0700 (PDT) Date: Mon, 11 Jun 2018 10:50:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528739455; bh=3s8aQPpzaUf7KcA1/yzq5OZWr55UL1coROwoHsYslMg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=acdV1eKzap1NbFWFEn9J2dRAXEc+ATPQ+L1AOVVnpEP/kRtXYkHDt6DdLqXHr2WvM 38NfYJSgtoBjZxNguEU3uscLIyQMAHpqxmcfWMVoKxG+xg/ipoJUPF3+r8NM5JhV/M tdv0eQjL+XeJKhBOnB8DoI9mdSTdXTPOJ26t6TlQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1eb67f65460_1ccb3fca5249ef8857641"; 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.26 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, 11 Jun 2018 17:50:58 -0000 ----==_mimepart_5b1eb67f65460_1ccb3fca5249ef8857641 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'd prefer not to do that because HTTP/QUIC doesn't currently have a hard dependency on QUICv1, and the properties of the Stream ID space could easily change across versions. -- 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/1422#issuecomment-396328595 ----==_mimepart_5b1eb67f65460_1ccb3fca5249ef8857641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'd prefer not to do that because HTTP/QUIC doesn't currently have a hard dependency on QUICv1, and the properties of the Stream ID space could easily change across versions.

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

----==_mimepart_5b1eb67f65460_1ccb3fca5249ef8857641-- From nobody Mon Jun 11 11:19:20 2018 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 73B53130EA3 for ; Mon, 11 Jun 2018 11:19:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QBQdtZd5brEE for ; Mon, 11 Jun 2018 11:19:16 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0F00130EA2 for ; Mon, 11 Jun 2018 11:19:16 -0700 (PDT) Date: Mon, 11 Jun 2018 11:19:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528741155; bh=VQNAvtdZ2Ku731Kb9jZ6EQ034X97SVBidqM8snE/Kq4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dire5dO5pEfTecDOEEJ7qsENxMBauIvSb1gsOzGGBH0h93oZbZ7OVlc9R76n+peyx 1X5GCU6ygtSMVcwHsgIpGGDQcnsGunMrqp+Z/w1jLAWxip4uzZ2tq/JqmZkAMGy/TX 3neTiMjxgyHWkXxdMnbQydZMjS0DHxK5nl8x2Jyw= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ebd239f5b5_2fac3ff082070f78256de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 11 Jun 2018 18:19:19 -0000 ----==_mimepart_5b1ebd239f5b5_2fac3ff082070f78256de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by this endpoint with at least 1-2^32 +probability and it is still outstanding (not acknowledged and not deemed lost). +If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the +packet as an ICMP message without an on-path proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. + +Even ICMP messages without an on-path proof SHOULD undergo some validation, such +as: * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that That was one of the original proposals. But I agree -- this is not the best idea. I'll revise. -- 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/1412#discussion_r194499005 ----==_mimepart_5b1ebd239f5b5_2fac3ff082070f78256de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by this endpoint with at least 1-2^32
+probability and it is still outstanding (not acknowledged and not deemed lost).
+If a QUIC endpoint does not perform this minimum validation, it SHOULD treat the
+packet as an ICMP message without an on-path proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.
+
+Even ICMP messages without an on-path proof SHOULD undergo some validation, such
+as:
 
 * Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that

That was one of the original proposals. But I agree -- this is not the best idea. I'll revise.

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

----==_mimepart_5b1ebd239f5b5_2fac3ff082070f78256de-- From nobody Mon Jun 11 14:09:26 2018 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 4884F130ED0 for ; Mon, 11 Jun 2018 14:09:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 A4XfdDY6_4sc for ; Mon, 11 Jun 2018 14:09:22 -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 73E81127598 for ; Mon, 11 Jun 2018 14:09:22 -0700 (PDT) Date: Mon, 11 Jun 2018 14:09:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528751361; bh=M2dkP9h7ObWZVD6PrDE+OWHPY5HC8SO8zFAW1YbLUu4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VdIq7XeFsTF7LQesXIcMI2Tv5iBjNaDCJtPHXPtK1qad46bLOn0rtcp6y6emvXIIf p/h+6WJto3q6FyLZNR0/FYw9R3f21poaZyAXrvNVLSce0rC5OlhDK/67ZVhVAZ/NU8 Js4e5Bb8aNmN37jOj+c7ZnTEQMbVLHiwZOWum3SU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ee501613c3_2fcb3faf91a16f7898431"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 21:09:25 -0000 ----==_mimepart_5b1ee501613c3_2fcb3faf91a16f7898431 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You mean the first packet you sent after the last received packet? I think that works reasonably well. It does fail to capture the request you might have spontaneously sent a millisecond ago, but I think that is a good thing. -- 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/1429#issuecomment-396388119 ----==_mimepart_5b1ee501613c3_2fcb3faf91a16f7898431 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You mean the first packet you sent after the last received packet? I think that works reasonably well.

It does fail to capture the request you might have spontaneously sent a millisecond ago, but I think that is a good thing.

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

----==_mimepart_5b1ee501613c3_2fcb3faf91a16f7898431-- From nobody Mon Jun 11 14:21:21 2018 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 D7D45130EE3 for ; Mon, 11 Jun 2018 14:21:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 zFkXscHbvhmI for ; Mon, 11 Jun 2018 14:21:16 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E2528130ED8 for ; Mon, 11 Jun 2018 14:21:15 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528752075; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zyDESt5EWvq3VvNV2ppJCReapjdz8e3fgRxRedrvrjs=; b=hHOPc7jkWbStVr5xRi5gTwlc3E0T4Rji7dIfX3R83oWm+Ez7JRvShmefGKumDXjyPBp+rCVI pl/+HOXplFO4+eU8W20Ne0UAn/NdYytkNCghBjKWmFhHITgJfAhoVLBF1S+fdET10CG+OZGw 6/lu5koJ/CnMhS3xw7mkakOQu9c= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b1ee7ca.7fc0bf1493f0-smtp-out-n02; Mon, 11 Jun 2018 21:21:14 -0000 (UTC) Date: Mon, 11 Jun 2018 14:21:13 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b1ee7c97470c_7eae2ac06e4ebc141654@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 06fcf4: Multiple settings Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1ee7c9740dc_7eae2ac06e4ebc14164bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 11 Jun 2018 21:21:19 -0000 ----==_mimepart_5b1ee7c9740dc_7eae2ac06e4ebc14164bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/placeholders Home: https://github.com/quicwg/base-drafts Commit: 06fcf4d56fa0fc6ba613e95cc5438c0b73a31a70 https://github.com/quicwg/base-drafts/commit/06fcf4d56fa0fc6ba613e95cc5438c0b73a31a70 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Multiple settings **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1ee7c9740dc_7eae2ac06e4ebc14164bb-- From nobody Mon Jun 11 14:21:26 2018 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 4ADFA130ED8 for ; Mon, 11 Jun 2018 14:21:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7uFzPzLEvsqh for ; Mon, 11 Jun 2018 14:21:18 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0DD130EE1 for ; Mon, 11 Jun 2018 14:21:18 -0700 (PDT) Date: Mon, 11 Jun 2018 14:21:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528752077; bh=SwHDdCoTYjwRfQVkcMKQ3GE6oBm3h1SOiybll8Fr4k4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CmRAYT5tIEDEIfpstJK1cg4BiEDMM5aKMBPkptUMPqGxyJdhMB4erHV17CFb5XiD/ a/ZDS1U7Q+pejW71QGs7KZ6B79HfmOa2kefX8z1WOkiRGyXcZ7d6+J5WFx/h2UJKh0 ZDu/f5G3vObywoSMqxWTNsFSZptIXcz3aHwLZ0+c= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ee7cddbce4_2ecc2abfb4f26f5410146d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 11 Jun 2018 21:21:21 -0000 ----==_mimepart_5b1ee7cddbce4_2ecc2abfb4f26f5410146d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 06fcf4d Multiple settings -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1422/files/816954348632ec64e91946351af3512da2ce498e..06fcf4d56fa0fc6ba613e95cc5438c0b73a31a70 ----==_mimepart_5b1ee7cddbce4_2ecc2abfb4f26f5410146d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1ee7cddbce4_2ecc2abfb4f26f5410146d-- From nobody Mon Jun 11 15:04:52 2018 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 BF17A130ED4 for ; Mon, 11 Jun 2018 15:04:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4Mm16LIBeeEm for ; Mon, 11 Jun 2018 15:04:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28A9D127598 for ; Mon, 11 Jun 2018 15:04:48 -0700 (PDT) Date: Mon, 11 Jun 2018 15:04:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528754686; bh=gvVvowJ4Orb+qUMH8wJN8WVD3Tz4CV5FWY1+tfg0wrw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wdDHuN7j1M4qhLq91ToXhIHAAS9Uz1DPdCoh1RdgIH2OALo8em6wrZ5b9hkL0aieq uOx60bsQfPYLOJMxEnkKIiAq+e4j3x50AIKDnsfB4cVcPepHtvmQdqCM6+9R2CQWsx iJ4VLaCHX0zmcHWskrAFtFLpwsmcNnjeOhVAsB+E= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ef1fee32b3_3de42b1a4d04cf589655c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 11 Jun 2018 22:04:50 -0000 ----==_mimepart_5b1ef1fee32b3_3de42b1a4d04cf589655c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @RyanAtGoogle may remember some details I'm forgetting, but yes, first packet you sent after the last received packet. -- 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/1429#issuecomment-396402139 ----==_mimepart_5b1ef1fee32b3_3de42b1a4d04cf589655c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@RyanAtGoogle may remember some details I'm forgetting, but yes, first packet you sent after the last received packet.

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

----==_mimepart_5b1ef1fee32b3_3de42b1a4d04cf589655c-- From nobody Mon Jun 11 15:11:47 2018 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 C7FB9130EB4 for ; Mon, 11 Jun 2018 15:11:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 F2MKAXSjV02Q for ; Mon, 11 Jun 2018 15:11:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09B12130ED4 for ; Mon, 11 Jun 2018 15:11:38 -0700 (PDT) Date: Mon, 11 Jun 2018 15:11:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528755097; bh=XPp4/N9U8K1Mu1vHXPRtGIFSBlYyELhTm0DA79gaps8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=htyoe0s6ydvPtFh/5NXi253spbyNVXXu4H64cuuGrs1CXWrS1x7tPdYOGmme5FE3Q aJaX5f/k5WB2KHLsma2HPeO/Xadi7iwJVpHAMG22rTelNLw6B3bDltKocO8eqJg7aU KmFOWbu4UlLFPpcdf0gHJ5/p7tWyDmubx6qDwByY= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ef3992c2e3_48af3fadd4caef88107346"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 11 Jun 2018 22:11:41 -0000 ----==_mimepart_5b1ef3992c2e3_48af3fadd4caef88107346 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit IMO, this is also an issue with TCP applications using _peek_ to see if a complete set of data is available in the receive buffer. The reason that it has not been considered as an issue is because TCP has expected applications to read data as they arrive, rather than using peek. Considering that, could we recommend the same approach in the transport draft? Does doing so have a severe impact on HQ? -- 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/1432#issuecomment-396403735 ----==_mimepart_5b1ef3992c2e3_48af3fadd4caef88107346 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

IMO, this is also an issue with TCP applications using peek t= o see if a complete set of data is available in the receive buffer. The r= eason that it has not been considered as an issue is because TCP has expe= cted applications to read data as they arrive, rather than using peek.

Considering that, could we recommend the same approach in the transpor= t draft? Does doing so have a severe impact on HQ?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1ef3992c2e3_48af3fadd4caef88107346-- From nobody Mon Jun 11 15:12:17 2018 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 1CADD130EB4 for ; Mon, 11 Jun 2018 15:12:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 dw5B5PG_UmnK for ; Mon, 11 Jun 2018 15:12:12 -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 CD627130ED8 for ; Mon, 11 Jun 2018 15:12:11 -0700 (PDT) Date: Mon, 11 Jun 2018 15:12:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528755131; bh=HgycouaEzBV3BlNp4TLGxMo79Z5PZ9QRvEj7gXnwBgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a6OxCjc8jVv0gx++jONtCo3HHwlzoZ5hkVP5pfX6oreGuZbAWsi08exp6ibTuZ2YT abxgB8hCwJpq/+SjyipXEX2mY8O1nNCbecWipw8tJZd/uBmONCiqvIjOwcjSZd6+PD 6TYDzI0uYZpC99sI3eMl0983U71kmVJad1eT5tfw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ef3bb1c507_15572af5b838cf6055573"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 22:12:15 -0000 ----==_mimepart_5b1ef3bb1c507_15572af5b838cf6055573 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit How does that work when a client receives an ACK (which doesn't generate any response), then has a long quiescent period after which it sends a request? That doesn't seem right. Is there a limit on the time between receipt and sending? -- 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/1429#issuecomment-396403848 ----==_mimepart_5b1ef3bb1c507_15572af5b838cf6055573 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

How does that work when a client receives an ACK (which doesn't generate any response), then has a long quiescent period after which it sends a request? That doesn't seem right. Is there a limit on the time between receipt and sending?

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

----==_mimepart_5b1ef3bb1c507_15572af5b838cf6055573-- From nobody Mon Jun 11 15:23:28 2018 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 2AFDE130EE3 for ; Mon, 11 Jun 2018 15:23:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 4_qlRIKQCgGK for ; Mon, 11 Jun 2018 15:23:24 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E557E130ED8 for ; Mon, 11 Jun 2018 15:23:24 -0700 (PDT) Date: Mon, 11 Jun 2018 15:23:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528755804; bh=Z1wcR5z4siXCJSWjRc6BNAr/SB3AkLppFRmP5Ppu+/c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=feUuuNpnBCFMrZEMMAm9ToPkWEaK8BjP3lfhsBt6tx2PiXTXC3RxpcKzWO+x+zrRV qbfEXPH491Fxcer+CK1MHgecqQpxcHZY2wTgZlNYOPQ3fVIaM+6sBRQ/FzdmphnzZa QF93v+MIJOWbr4n4QXiriWEyVuxqREdMRSfkmu/M= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1ef65bdc224_3fee3fddf624ef78250788"; 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.26 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, 11 Jun 2018 22:23:27 -0000 ----==_mimepart_5b1ef65bdc224_3fee3fddf624ef78250788 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The issue is cross-stream dependencies. If you craft a very large message which requires data from another stream to process it, if the application sucks up the large message anyway, then it will explode its memory. The point of flow control is to limit this, by constraining the *unprocessed* data at any time. We're using unread as a stand-in for unprocessed, and the corollary is that you shouldn't read something you know you won't be able to process. The guidance in HQ is to read far enough to decide whether you can process the message, and if not, stop reading until you can. -- 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/1432#issuecomment-396406206 ----==_mimepart_5b1ef65bdc224_3fee3fddf624ef78250788 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The issue is cross-stream dependencies. If you craft a very large mes= sage which requires data from another stream to process it, if the applic= ation sucks up the large message anyway, then it will explode its memory.= The point of flow control is to limit this, by constraining the unp= rocessed data at any time. We're using unread as a stand-in for unp= rocessed, and the corollary is that you shouldn't read something you know= you won't be able to process. The guidance in HQ is to read far enough = to decide whether you can process the message, and if not, stop reading u= ntil you can.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= = ----==_mimepart_5b1ef65bdc224_3fee3fddf624ef78250788-- From nobody Mon Jun 11 15:51:16 2018 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 22900128CF3 for ; Mon, 11 Jun 2018 15:51:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 n_HNLxj9TftZ for ; Mon, 11 Jun 2018 15:51:09 -0700 (PDT) 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 19C9212F1A5 for ; Mon, 11 Jun 2018 15:51:09 -0700 (PDT) Date: Mon, 11 Jun 2018 15:51:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528757468; bh=jfA//AZNv2h45gcf4YK30obXxoBYZje9cRjUZcvBHPE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=V/3UxYCXX4aWbvbbGOBttpxWmXTTuKk/QvyFKr3cc5NHKWP+flyFfCcdHGwr1rUvr U/6T8LYUPtyzKI/zmS9W5E5X0QNrO49k584DG/V6knYv4xj1yoyB52VlQIy51vXVJM vrG5J0HAsy/rFp8Akk7iLgAVFJhjMAAfsjmbBc1Q= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Resending ACK frames increases max_ack_delay unnecessarily (#1438) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1efcdc16d5a_63ad3fadf2d90f7843191"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 22:51:14 -0000 ----==_mimepart_5b1efcdc16d5a_63ad3fadf2d90f7843191 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subodh notes that when a receiver simply resends old ACK frames, the ack_delay field keeps on increasing, which unnecessarily inflates max_ack_delay. From email thread: My concern is this situation: a "receiver" had not seen the original ACK (the packet was lost), then the sender rtos and sends a large ack delay to compensate for the rto, the max filter for max ack delay would inflate the delay for future packet. if latest_rtt - min_rtt > ack_delay: max_ack_delay = max(max_ack_delay, ack_delay) latest_rtt in this case would be rto_timer + rtt because the sender sends an ack after an rto. -- 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/1438 ----==_mimepart_5b1efcdc16d5a_63ad3fadf2d90f7843191 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Subodh notes that when a receiver simply resends old ACK frames, the ack_delay field keeps on increasing, which unnecessarily inflates max_ack_delay. From email thread:

My concern is this situation: a "receiver" had not seen the original ACK (the packet was lost), then the sender rtos and sends a large ack delay to compensate for the rto, the max filter for max ack delay would inflate the delay for future packet.

if latest_rtt - min_rtt > ack_delay:

max_ack_delay = max(max_ack_delay, ack_delay)

latest_rtt in this case would be rto_timer + rtt because the sender sends an ack after an rto.

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

----==_mimepart_5b1efcdc16d5a_63ad3fadf2d90f7843191-- From nobody Mon Jun 11 16:34:19 2018 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 0B12212E039 for ; Mon, 11 Jun 2018 16:34:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1Co58wFWQvni for ; Mon, 11 Jun 2018 16:34:13 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3301D127598 for ; Mon, 11 Jun 2018 16:34:13 -0700 (PDT) Date: Mon, 11 Jun 2018 16:34:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528760052; bh=unkolfl0QZb5lxtzBTGELsw4iwKzEfu4dl+tAt0mkmA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GfJg/+XrZUvwR0jhXgR40tdWDnJ53kGK+9QdZLvbPiVNJct6o58u5YPjdrzHoKSg9 aYWlMUY3H33lio8Go7iZoH+5cVDfXNn0JwgRks2MKK9Vu01ut3NNU+CAX1HFaxxDY7 3ASruMXO45k4dHrB7gDEeq1RhoXtw2aAHEUQzCjE= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f06f48fa3_7b223ff583d0ef7c522aa"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 23:34:16 -0000 ----==_mimepart_5b1f06f48fa3_7b223ff583d0ef7c522aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The Reno spec is a simple CC for those senders who need something simple and reasonably effective to implement on the send side. I don't think we can afford to specify a receiver that assumes only Reno senders though. Given that senders (such as Google's servers, for instance) will use non-Reno CCs right off the ground, we would want receivers to do something better than simply ack every two packets right off the ground. Any sender should be adaptive to this, but it's useful to have a knob by which we can control receiver behavior and reduce the number of ACK-only packets that are being sent on the wire. The point of acking every other packet is basically an attempt to reduce the number of ACK-only packets, and we ought to be able to make it more generalizable. As I mentioned in my earlier comment, I think the sender can specify something like: ack_ratio: number of retransmittable packets received after which an ack must be sent. 2 by default. We can also additionally have an ack_delay param that the receiver tells the sender about, but I think that can be a separate issue (and there's already #981). -- 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/1428#issuecomment-396419114 ----==_mimepart_5b1f06f48fa3_7b223ff583d0ef7c522aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The Reno spec is a simple CC for those senders who need something simp= le and reasonably effective to implement on the send side. I don't think = we can afford to specify a receiver that assumes only Reno senders though= . Given that senders (such as Google's servers, for instance) will use no= n-Reno CCs right off the ground, we would want receivers to do something = better than simply ack every two packets right off the ground.

Any sender should be adaptive to this, but it's useful to have a knob = by which we can control receiver behavior and reduce the number of ACK-on= ly packets that are being sent on the wire. The point of acking every oth= er packet is basically an attempt to reduce the number of ACK-only packet= s, and we ought to be able to make it more generalizable.

As I mentioned in my earlier comment, I think the sender can specify s= omething like:
ack_ratio: number of retransmittable packets received after which an ack = must be sent. 2 by default.

We can also additionally have an ack_delay param that the receiver tel= ls the sender about, but I think that can be a separate issue (and there'= s already #981).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f06f48fa3_7b223ff583d0ef7c522aa-- From nobody Mon Jun 11 16:35:52 2018 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 637E6127598 for ; Mon, 11 Jun 2018 16:35:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Vv7wYAttpqBd for ; Mon, 11 Jun 2018 16:35:45 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F422712F1AB for ; Mon, 11 Jun 2018 16:35:44 -0700 (PDT) Date: Mon, 11 Jun 2018 16:35:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528760144; bh=DTSC4HsGSKoWnG5QSA2rndvhxiBSWTScX0UHI4hU2Uo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TkKmAhD3VNnQbC34oPabHMoXBDnK7J7MmdtwHiUa0PRwQenFzEMZfw+CTg/AKr1TS XEZTLHojeWClIeBdMvKfMITxEiju1Cmgom4B+mkT/s1+1J6j2OhfSAOLHKdkq+Vrh9 JVmc//I3kohZA4c9OjgbjxOLJqZy8Oj+Un+J0PCM= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f075018c0e_39d82ac3c02e4f60747f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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, 11 Jun 2018 23:35:49 -0000 ----==_mimepart_5b1f075018c0e_39d82ac3c02e4f60747f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Pick your poison. If you don't increase the ACK delay, you will overestimate the RTT sample. I think the increased ACK delay is a better reflection of reality. -- 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/1438#issuecomment-396419329 ----==_mimepart_5b1f075018c0e_39d82ac3c02e4f60747f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Pick your poison. If you don't increase the ACK delay, you will overestimate the RTT sample. I think the increased ACK delay is a better reflection of reality.

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

----==_mimepart_5b1f075018c0e_39d82ac3c02e4f60747f6-- From nobody Mon Jun 11 16:52:57 2018 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 D15A212F1AB for ; Mon, 11 Jun 2018 16:52:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 urU8cFpR1oA1 for ; Mon, 11 Jun 2018 16:52:52 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4CED127598 for ; Mon, 11 Jun 2018 16:52:52 -0700 (PDT) Date: Mon, 11 Jun 2018 16:52:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528761172; bh=7K9jpjIfS9/PUUsmwK8NmdbyL1fedV3ZfDxhGT0EXYY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z1/vLpNVvQj6waWS6Mgzes6vCqtra3+nLe4cKuMttwPzQxORBGrehNE/+YvhThnSK hVJvkjKLLirOmyQlKZY5wZ9gA8g+mi1AUaLuqWQT8YK8tKT/BGIFpiI5mhVHkcBnjC L5NCmBBz2dM4rXPsrkpnY7aMj9DgCFlfalcBZvsI= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f0b543a06e_2362b3f960a386f78861dd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 11 Jun 2018 23:52:55 -0000 ----==_mimepart_5b1f0b543a06e_2362b3f960a386f78861dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What @kazuho said. This is something that an application ought to be aware of when treating QUIC's stream buffers as storage. The problem is caused by something broader than the structure in the application data bytes -- an application could choose to not read data from the buffer until, for instance, the next consumer is ready for it. In all these cases, I think it is not a good idea for an app to assume that the stream's buffers are a good place to store data, since that can interfere with network throughput and with resource allocation for other streams. -- 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/1432#issuecomment-396422059 ----==_mimepart_5b1f0b543a06e_2362b3f960a386f78861dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

What @kazuho said. This is something = that an application ought to be aware of when treating QUIC's stream buff= ers as storage.

The problem is caused by something broader than the structure in the a= pplication data bytes -- an application could choose to not read data fro= m the buffer until, for instance, the next consumer is ready for it.

In all these cases, I think it is not a good idea for an app to assume= that the stream's buffers are a good place to store data, since that can= interfere with network throughput and with resource allocation for other= streams.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f0b543a06e_2362b3f960a386f78861dd-- From nobody Mon Jun 11 17:09:33 2018 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 E742E130DC6 for ; Mon, 11 Jun 2018 17:09:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ir7YiwyR0gFI for ; Mon, 11 Jun 2018 17:09:26 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17BA12F1AB for ; Mon, 11 Jun 2018 17:09:26 -0700 (PDT) Date: Mon, 11 Jun 2018 17:09:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528762165; bh=FE7TtFyES2rmx4OFy2BGHhz1jK2UpyiiHgv4/bOE0JI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QyJeSKRtNUJHOLZ2SXFROjEpZ9keXBLaKsk7/A3/VQLQJB23c3lNn+jL11F4/AHd2 w35rmxeTPBeEu8LzYXfs8O69QNm0gtwR/CL5/dCcP6ejwzVCwpwwFH4DZcNjihyy+i ZyWutQIeaWqXyqBsuZsdfPQ56X8PPrE/n0lzaio4= From: krasic Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f0f35c2dcf_42923f8173406f80167088"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: krasic 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.26 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: Tue, 12 Jun 2018 00:09:31 -0000 ----==_mimepart_5b1f0f35c2dcf_42923f8173406f80167088 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar@ if an app isn't to use stream buffers for storage, what does it do in your example when the next consumer isn't keeping up? if it drains all data from the stream, it may blow up its own memory, unless it implements its own flow control protocol at the app level? that seems.. unsatisfactory. -- 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/1432#issuecomment-396424815 ----==_mimepart_5b1f0f35c2dcf_42923f8173406f80167088 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

janaiyengar@ if an app isn't to use stream buffers for storage, what = does it do in your example when the next consumer isn't keeping up? if = it drains all data from the stream, it may blow up its own memory, unless= it implements its own flow control protocol at the app level? that see= ms.. unsatisfactory.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f0f35c2dcf_42923f8173406f80167088-- From nobody Mon Jun 11 17:23:23 2018 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 07E3B130E99 for ; Mon, 11 Jun 2018 17:23:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 WnATNeBn_R_M for ; Mon, 11 Jun 2018 17:23:17 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45D46130DC6 for ; Mon, 11 Jun 2018 17:23:08 -0700 (PDT) Date: Mon, 11 Jun 2018 17:23:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528762987; bh=Hmg+OFVg1P35zLtPDiXDnMDeuzcVTjF/iQOnJvdkaAk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ARChVm7+3Le+ADQCC7HWFEehEqogcoaHDtmF6yg0l6ETEw3pcFAPHBtaw4LZW4NKg BeRZ3YUjcUzkbquotfy8G7jyjZiMYbYSE+DoDRNmpMNvse2SxWXUW5jySuNqAhnNE/ Bed9lrPSwjVcVIDWHArHr50reB4gatJuX6eUTtHI= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f126b6f323_2b0d3fb704d58f7c2043a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 00:23:21 -0000 ----==_mimepart_5b1f126b6f323_2b0d3fb704d58f7c2043a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We shouldn't assume only Reno, but as EKR pointed out, the text should describe something we expect to perform reasonably well. Yes, let's keep ack delay is a separate issue. And I completely agree that we don't want to specify only acking every two packets. If we specify ack ratio, I tend to think it should be in bytes, not packets, but possibly it doesn't really matter? However, it seems like min number of acks per RTT is just as valuable as max number of bytes received before sending an acknowledgement. At the moment, I'm fairly concerned that we are only aware of one congestion controller that deals well with intentional receiver-side aggregation/decimation, and it is ok with any value of ack_ratio. More important to BBR is getting somewhat regular feedback, ie: at least once per RTT, ideally more often. -- 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/1428#issuecomment-396427016 ----==_mimepart_5b1f126b6f323_2b0d3fb704d58f7c2043a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

We shouldn't assume only Reno, but as EKR pointed out, the text should= describe something we expect to perform reasonably well.

Yes, let's keep ack delay is a separate issue. And I completely agree= that we don't want to specify only acking every two packets.

If we specify ack ratio, I tend to think it should be in bytes, not pa= ckets, but possibly it doesn't really matter? However, it seems like min= number of acks per RTT is just as valuable as max number of bytes receiv= ed before sending an acknowledgement.

At the moment, I'm fairly concerned that we are only aware of one cong= estion controller that deals well with intentional receiver-side aggregat= ion/decimation, and it is ok with any value of ack_ratio. More important= to BBR is getting somewhat regular feedback, ie: at least once per RTT, = ideally more often.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f126b6f323_2b0d3fb704d58f7c2043a6-- From nobody Mon Jun 11 17:30:31 2018 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 DDD3B130DC7 for ; Mon, 11 Jun 2018 17:30:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 M7qSCfunH1BR for ; Mon, 11 Jun 2018 17:30:28 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E528C130DC3 for ; Mon, 11 Jun 2018 17:30:27 -0700 (PDT) Date: Mon, 11 Jun 2018 17:30:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763427; bh=+FbDHd6vqx0z3rug1QBa5ftTYRMB7lt5rTDdIgsay8o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=moJo7QvQ/qes4+9RLGR36EbWlJcJ1CZFsi6d8g+EwoZWsot9zPuOyR5MnlDh26ps4 ey0mXIVkGoLQ6C2QCKOoGUwCeeO8YhmjNrHb+zGPlaMupto1icF853j9U352ltC72U h1hustbuuJpjrgDx7/H92Yt7hlVZ0QVE11u7KJRI= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f14236e8_56d92adf7f656f606296c9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 00:30:30 -0000 ----==_mimepart_5b1f14236e8_56d92adf7f656f606296c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree with Christian that this seems like it's working as intended, but it's another reason I'm a bit concerned about not having explicit max ack delay in transport params. -- 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/1438#issuecomment-396428122 ----==_mimepart_5b1f14236e8_56d92adf7f656f606296c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I agree with Christian that this seems like it's working as intended, but it's another reason I'm a bit concerned about not having explicit max ack delay in transport params.

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

----==_mimepart_5b1f14236e8_56d92adf7f656f606296c9-- From nobody Mon Jun 11 17:32:26 2018 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 E5AFA130DC3 for ; Mon, 11 Jun 2018 17:32:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 IC3pq2X5KRHA for ; Mon, 11 Jun 2018 17:32:18 -0700 (PDT) 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 E81E0130E86 for ; Mon, 11 Jun 2018 17:32:17 -0700 (PDT) Date: Mon, 11 Jun 2018 17:32:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763537; bh=yNtN0sKXn+/r0Ws4LF6IKDXP8bz+n6wHfgWUX7vu4ks=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bixhg4oBt2E4/qe5GV+V2xeoc9yZIaIxA7WOt9GYSe9SLwmBb6HS2DwGXiuo6Mmsj rteR9nYJPwuSbNd2TrV5Y+Qu/Zi5T8qCBuprNQYcrsqgYKSzJdo3qSLVfs+X41nSeq lqKGPSe2rab4aZZ9gEaLNLsvSWihjCi+jh5L3JXM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f149153fc7_518b3fbc65ea6f8018504c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 00:32:21 -0000 ----==_mimepart_5b1f149153fc7_518b3fbc65ea6f8018504c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit There's no limit in the existing Chromium code, except the idle timeout. -- 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/1429#issuecomment-396428356 ----==_mimepart_5b1f149153fc7_518b3fbc65ea6f8018504c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

There's no limit in the existing Chromium code, except the idle timeout.

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

----==_mimepart_5b1f149153fc7_518b3fbc65ea6f8018504c-- From nobody Mon Jun 11 17:33:11 2018 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 1C3E2130EAB for ; Mon, 11 Jun 2018 17:33:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1g08VJM1ad-0 for ; Mon, 11 Jun 2018 17:33:03 -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 72395130EE8 for ; Mon, 11 Jun 2018 17:33:03 -0700 (PDT) Date: Mon, 11 Jun 2018 17:33:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763582; bh=47tPAXYEtsnjC4e3drwj1GccXIWDbezEHJlsJ1ZXvBI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Zyu2JSkNV4jrzMHbVvw5PXRwlriwzFScBFsTYiQLKRlIMw3lrIcVWZz8XdV3CSUN5 l6nyjfgxFZk+H3put6gToL++INh7O3PSbYFJuZuxw2dnyTSUSSUOyE98pRZAQNiImM GVroRJcmG8kjrPsbAiuIF3vHufr7t8W8Q1iR8KTQ= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f14beccd32_2b203fb704d58f7c213651"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 00:33:07 -0000 ----==_mimepart_5b1f14beccd32_2b203fb704d58f7c213651 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett: It seems like that second part (time of last sent packet after a packet was received) captures the RTO cases, so that you don't keep restarting this timer if the sender keeps RTOing with no ACKs being received. @martinthomson: I think this works ok in your example right? The client receives an ACK which causes it to count the next packet, whenever it is sent, as a new start of the idle timeout period. That said, idle timeout should not be used when the endpoint is RTOing into the void. That is a failure, and ought to be captured by a different constant, since it's about how long we're willing to keep trying before giving up on the connection, and will be f(RTO). Idle timeout does not have anything to do with the RTO period. -- 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/1429#issuecomment-396428459 ----==_mimepart_5b1f14beccd32_2b203fb704d58f7c213651 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett: It seems like that se= cond part (time of last sent packet after a packet was received) captures= the RTO cases, so that you don't keep restarting this timer if the sende= r keeps RTOing with no ACKs being received.

@martinthomson: I think this w= orks ok in your example right? The client receives an ACK which causes it= to count the next packet, whenever it is sent, as a new start of the idl= e timeout period.

That said, idle timeout should not be used when the endpoint is RTOing= into the void. That is a failure, and ought to be captured by a differen= t constant, since it's about how long we're willing to keep trying before= giving up on the connection, and will be f(RTO). Idle timeout does not h= ave anything to do with the RTO period.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f14beccd32_2b203fb704d58f7c213651-- From nobody Mon Jun 11 17:34:07 2018 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 8AC64130E99 for ; Mon, 11 Jun 2018 17:34:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DRHeMSOhUdF2 for ; Mon, 11 Jun 2018 17:33:59 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4783130E7D for ; Mon, 11 Jun 2018 17:33:59 -0700 (PDT) Date: Mon, 11 Jun 2018 17:33:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763639; bh=tj5VKJRAZEPjJp35oYFiDHCJVQUlyTD9O6dgAZE/pmM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sz0irrOi2nCy5Fe4RZCVvoww2Ob0F6KpXeZPZ39MsBnO/nEAmNNdBJzOzX9EZKeHi Ig1Foi8I7n5AtnqxFTx/cDOE7GUj588gsKJ9t2NuNq7IgaNRB4RPDQr0sO6baNSLh3 tJ47XXgV8fRqxDzAB8MTNreFZXlt114SHQk0afY4= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f14f75d25f_394e3fa91d49ef84356d9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 00:34:04 -0000 ----==_mimepart_5b1f14f75d25f_394e3fa91d49ef84356d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett : The Chromium code is incomplete currently, IIRC. It doesn't have this notion of a network timeout as distinct from application idle timeout. We need to separate those timeouts. -- 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/1429#issuecomment-396428607 ----==_mimepart_5b1f14f75d25f_394e3fa91d49ef84356d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett : The Chromium code is incomplete currently, IIRC. It doesn't have this notion of a network timeout as distinct from application idle timeout. We need to separate those timeouts.

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

----==_mimepart_5b1f14f75d25f_394e3fa91d49ef84356d9-- From nobody Mon Jun 11 17:34:21 2018 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 71169130E99 for ; Mon, 11 Jun 2018 17:34:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rp-hygWJrf7D for ; Mon, 11 Jun 2018 17:34:14 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A22EB130E7D for ; Mon, 11 Jun 2018 17:34:14 -0700 (PDT) Date: Mon, 11 Jun 2018 17:34:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763653; bh=vBZMPgvfVqu6uxpBq6G4bJiz3TbqKYgfHjkWoluHLd0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XkO1Hkz7Ftzeq8YPlAYv6+XqpRjmBf5P0ED4zzMMov0/6Wp/0lVfX3tcShbju7Pu1 T3QYAlARcs/4K3XpGFQGoPVIPTb+ZYB6cB5tRPMC1VctK/3RwONGvAXmkyAyl2hQYY vFDO6c4PWs6pmvl5+WnO2PYSofGHPyYuYNNypfmE= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f1505d18be_be12b04728baf501511ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.26 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: Tue, 12 Jun 2018 00:34:18 -0000 ----==_mimepart_5b1f1505d18be_be12b04728baf501511ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Side note: the Huffman coding does have the EOS symbol. -- 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/1432#issuecomment-396428644 ----==_mimepart_5b1f1505d18be_be12b04728baf501511ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Side note: the Huffman coding does have the EOS symbol.

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

----==_mimepart_5b1f1505d18be_be12b04728baf501511ac-- From nobody Mon Jun 11 17:36:54 2018 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 63465130EAB for ; Mon, 11 Jun 2018 17:36:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Xmz1PpEbO7DL for ; Mon, 11 Jun 2018 17:36:49 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75881130E99 for ; Mon, 11 Jun 2018 17:36:49 -0700 (PDT) Date: Mon, 11 Jun 2018 17:36:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528763808; bh=5QHTtjzKyQsOFCdr3sD66GU5Z1XqPdYiBgW73P9ZoUU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nod+RPhvYPc/jaZxEfB6ulR0n16nP7uVNn65unoeI2zWDEmcnLCYkKPTdW1STzrF+ w8uDCC1NvYUSJ5xjQfHbzizhJFvrioELXrm4tKK2YxoySDAgzvZHC3BPNZf0yFxru7 Iudk/JcmP7wnXNCiNfLLmYslfccJ4Eban+sQTPyg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f15a0d8a32_46c72b20988eef5c289037"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 00:36:53 -0000 ----==_mimepart_5b1f15a0d8a32_46c72b20988eef5c289037 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah, @krasic has it right. The entire point of this thing is to apply back pressure - if you can't read, ensure that you don't get more of stuff you can't read that consumes more of the memory you don't have. On the other hand, it is reasonable to say that applications (and application protocols) can't rely on QUIC providing them with any concrete amount of storage. But we can't force people to read or we undermine the entire purpose of providing flow control. (Here I'm assuming that reading releases flow control, but the key point is that you only release flow control once you are done with the octets, and for many of these cases, the point is that you can't be done with the octets until some external condition is met, or all the octets are in, or something like that.) I don't think that this is something we have to provide a concrete solution for. Flow control is fundamentally hard because it is about managing access to a finite resource and contention can occur, sometimes in sub-optimal ways. What we can do is signpost the obvious pitfalls. Like the case where you have 10 octets of connection flow control, 10 streams and 1 octet arrives for every stream, but you need to have >1 to make progress. Using `peek()` is just an example, and not a necessary one. The problem is that we're creating ways for an application to learn whether it wants to read octets before it reads them. A length-prefixed encoding does that inherently, but it's just an example of a general class of things that a reader might use to decide to defer consumption of data. That length-prefixes are also a great way to optimize processing of data means that we won't ever avoid using them, and nor can we avoid cases where atomic units take more than one octet to express. If I get @dtikhonov's point, it seems like a suggestion that we might avoid a length-prefix, but I think that only makes reading harder, and doesn't avoid other styles of atomic processing over multi-octet fields. It probably drives implementation complexity up, and it (unfortunately) uses a lot more bytes than a length prefix in many cases. -- 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/1432#issuecomment-396429043 ----==_mimepart_5b1f15a0d8a32_46c72b20988eef5c289037 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yeah, @krasic has it right. The en= tire point of this thing is to apply back pressure - if you can't read, e= nsure that you don't get more of stuff you can't read that consumes more = of the memory you don't have.

On the other hand, it is reasonable to say that applications (and appl= ication protocols) can't rely on QUIC providing them with any concrete am= ount of storage. But we can't force people to read or we undermine the = entire purpose of providing flow control. (Here I'm assuming that readin= g releases flow control, but the key point is that you only release flow = control once you are done with the octets, and for many of these cases, t= he point is that you can't be done with the octets until some external co= ndition is met, or all the octets are in, or something like that.)

I don't think that this is something we have to provide a concrete sol= ution for. Flow control is fundamentally hard because it is about managi= ng access to a finite resource and contention can occur, sometimes in sub= -optimal ways. What we can do is signpost the obvious pitfalls. Like th= e case where you have 10 octets of connection flow control, 10 streams an= d 1 octet arrives for every stream, but you need to have >1 to make pr= ogress.

Using peek() is just an example, and not a necessary one.= The problem is that we're creating ways for an application to learn whe= ther it wants to read octets before it reads them. A length-prefixed enc= oding does that inherently, but it's just an example of a general class o= f things that a reader might use to decide to defer consumption of data. = That length-prefixes are also a great way to optimize processing of data= means that we won't ever avoid using them, and nor can we avoid cases wh= ere atomic units take more than one octet to express.

If I get @dtikhonov's point, it = seems like a suggestion that we might avoid a length-prefix, but I think = that only makes reading harder, and doesn't avoid other styles of atomic = processing over multi-octet fields. It probably drives implementation co= mplexity up, and it (unfortunately) uses a lot more bytes than a length p= refix in many cases.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f15a0d8a32_46c72b20988eef5c289037-- From nobody Mon Jun 11 17:42:58 2018 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 04811130E7D for ; Mon, 11 Jun 2018 17:42:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TkvBDTdamoDx for ; Mon, 11 Jun 2018 17:42:52 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D224130DC3 for ; Mon, 11 Jun 2018 17:42:52 -0700 (PDT) Date: Mon, 11 Jun 2018 17:42:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528764171; bh=jtIEoxv8lqjLRT2Mi2OTWxk1/6cl2j+23q7812wR1Zw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qWXFA9oEPc6cw9981qDzUUcBMouvFNFkiwk05sItEVXZksZyO3GVU6kJUxQcETzA9 8ynyRywytVy8Wxfatslnhf/c86DuXxR1rI4NkS6UXMxk5EFs2QI/g6EQsNB0fIA4GB +DgRij6vFbQtXEUS3bekoCvKIKUFLTUVZlvCBLXc= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f170b440cd_96e3f9313018f841822c6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.26 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: Tue, 12 Jun 2018 00:42:55 -0000 ----==_mimepart_5b1f170b440cd_96e3f9313018f841822c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson, mine wasn't a suggestion, but rather something to keep in mind as we weigh different options. That is, there is a way to not use prefix length at all. Your analysis is correct. The biggest downside to me is that the EOS symbol is so long. -- 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/1432#issuecomment-396429945 ----==_mimepart_5b1f170b440cd_96e3f9313018f841822c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson, mine wasn't a suggestion, but rather something to keep in mind as we weigh different options. That is, there is a way to not use prefix length at all. Your analysis is correct. The biggest downside to me is that the EOS symbol is so long.

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

----==_mimepart_5b1f170b440cd_96e3f9313018f841822c6-- From nobody Mon Jun 11 17:47:47 2018 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 8F973130DEE for ; Mon, 11 Jun 2018 17:47:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Ns1ImNNRufVH for ; Mon, 11 Jun 2018 17:47:41 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF29A130DC3 for ; Mon, 11 Jun 2018 17:47:40 -0700 (PDT) Date: Mon, 11 Jun 2018 17:47:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528764460; bh=3bzoVLE4GOx76beeBsgsGrSEhrKCzhwdMw3CuRLzeL8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CjnBI6ORFQRv9fvFtIGkOixZ92hzYzf/mT/47bHB2BlwvESYXUkQOaULPP7gUZCja oc2ZHwf788ZMDabCVosLtk/LT5IwHHa/gmg0MOzTAywTMuDlhljTzfalx/s28Eo1Qo goFhAlrNTpHY78QwSuXzxpcBZz4Q6hGYcx+0RcAk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f182c37c46_236303f960a386f782046e2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 00:47:45 -0000 ----==_mimepart_5b1f182c37c46_236303f960a386f782046e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Here's the example: Idle timeout is 10s. You send a packet and subsequently receive an ACK at t=0. You send a new message at T=10-sRTT. You are now no longer idle, but the message you sent is going to arrive at the peer too late with ~50% probability of arriving before the idle timeout fires on their end. During that last sRTT (and maybe a little before), you have a very good chance of not keeping the connection alive, but you will persist nonetheless and what will happen is that requests will fail. The worst thing is that requests will fail in unrecoverable ways. It's very clear that you don't want to count an RTO here. A dead path is a common reason that you are hitting an RTO and restarting the idle timer just makes detecting the dead path that much harder (if not impossible as Subodh discovered). I suspect that you want proof of life - that is, packets inbound - and to only rely on that. You probably also need some advice about avoiding idle timeout by doing a liveness check once you reach `idle_timeout-sRTT-n*rtt_var` for some value of `n` that you tune based on your tolerance toward losing the messages you are about to send (for an idempotent message, `n` might be zero, for instance). -- 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/1429#issuecomment-396430649 ----==_mimepart_5b1f182c37c46_236303f960a386f782046e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Here's the example: Idle timeout is 10s. You send a packet and subseq= uently receive an ACK at t=3D0. You send a new message at T=3D10-sRTT. = You are now no longer idle, but the message you sent is going to arrive a= t the peer too late with ~50% probability of arriving before the idle tim= eout fires on their end. During that last sRTT (and maybe a little befor= e), you have a very good chance of not keeping the connection alive, but = you will persist nonetheless and what will happen is that requests will f= ail. The worst thing is that requests will fail in unrecoverable ways.

It's very clear that you don't want to count an RTO here. A dead path= is a common reason that you are hitting an RTO and restarting the idle t= imer just makes detecting the dead path that much harder (if not impossib= le as Subodh discovered).

I suspect that you want proof of life - that is, packets inbound - and= to only rely on that. You probably also need some advice about avoiding= idle timeout by doing a liveness check once you reach idle_timeout= -sRTT-n*rtt_var for some value of n that you tune bas= ed on your tolerance toward losing the messages you are about to send (fo= r an idempotent message, n might be zero, for instance).

=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f182c37c46_236303f960a386f782046e2-- From nobody Mon Jun 11 17:56:53 2018 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 A5F3F130DC3 for ; Mon, 11 Jun 2018 17:56:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oWGkRMp9kkWk for ; Mon, 11 Jun 2018 17:56:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AABC8130E7D for ; Mon, 11 Jun 2018 17:56:48 -0700 (PDT) Date: Mon, 11 Jun 2018 17:56:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528765008; bh=jkxdaoVV/cTLFhmbmCi6SNTT1S0myGAUS85Nk/m/ctg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gNCZFFEnxprl1KMy/L+39zFF5KPAuWV7szLtwqbTqrvwTvVA2W2hUL8mjDh0najx0 EfScLwZnnyd0pIGeYDg3TtKafaGi9EDCkJTEEKOaprbIPMX+wGs74tDWfsP0L1s3xf Mos4tQaL6zVYNKRkBqy4SbQ+wK2MZe9V1Hgs7Koc= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f1a50bf2e_62412ae1a435cf54494638"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 00:56:52 -0000 ----==_mimepart_5b1f1a50bf2e_62412ae1a435cf54494638 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Chromium now has them separated(see: the PathDegradingAlarm and the RetransmittableOnWireAlarm https://cs.chromium.org/chromium/src/net/third_party/quic/core/quic_connection.cc?sq=package:chromium&g=0&l=281) Path degrading is there solely for connection migration at the moment, and RetransmittableOnWireAlarm really should be able to be combined with the existing ping alarm. You're right that separating idle timeout from dead path detection is a good choice in the long term. We might only want to wait 15 seconds before declaring the path dead when we're retransmitting data, but a connection may have a 5 or 10 minute idle timeout. My concern about dead path detection is that I don't have enough data to support a particular choice of when to consider a path dead. 5RTOs worked fairly well in the one experiment, but I have no comparison data with 4 or 6RTOs, and all of these are magic numbers. -- 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/1429#issuecomment-396431948 ----==_mimepart_5b1f1a50bf2e_62412ae1a435cf54494638 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Chromium now has them separated(see: the PathDegradingAlarm and the Re= transmittableOnWireAlarm https://cs.chromium.org/chromium/src/net/= third_party/quic/core/quic_connection.cc?sq=3Dpackage:chromium&g=3D0&= amp;l=3D281) Path degrading is there solely for connection migration= at the moment, and RetransmittableOnWireAlarm really should be able to b= e combined with the existing ping alarm.

You're right that separating idle timeout from dead path detection is = a good choice in the long term. We might only want to wait 15 seconds be= fore declaring the path dead when we're retransmitting data, but a connec= tion may have a 5 or 10 minute idle timeout.

My concern about dead path detection is that I don't have enough data = to support a particular choice of when to consider a path dead. 5RTOs wo= rked fairly well in the one experiment, but I have no comparison data wit= h 4 or 6RTOs, and all of these are magic numbers.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f1a50bf2e_62412ae1a435cf54494638-- From nobody Mon Jun 11 18:01:40 2018 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 B7289130E99 for ; Mon, 11 Jun 2018 18:01:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 OvuEUyNsMN1e for ; Mon, 11 Jun 2018 18:01:33 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ACC5130E7D for ; Mon, 11 Jun 2018 18:01:33 -0700 (PDT) Date: Mon, 11 Jun 2018 18:01:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528765293; bh=viNPMVYQxbiGOeuvdv3nCDHhdW9O83F+WuBuN49gQX0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GSKzc1pQZXXMdkYs9venXAVKrUaINv0UHgZsCSBRfrW//oA5yazghzHs7cXh80b0i BZHXYIieKvO4K7/FLpc2soUPJgwe27WqooSG4DLg3pT3v7ZpDPO4ntrc7qZF5Mw/mj W9+y5f4UQXqzQlGRW6UTkl/jqPPQ4LjrNXHH20go= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f1b6cd5508_9733f9313018f844164d7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 01:01:36 -0000 ----==_mimepart_5b1f1b6cd5508_9733f9313018f844164d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @krasic Yes, you're right, and I wasn't being precise. It's not always a problem, but it can become one, based on how the application manages its data. @martinthomson: I agree that we shouldn't be looking to provide a concrete solution for, but we can generally say something about the potential implications of consuming stream buffers for data that can be read. Beyond that, I think trying to capture this application design pattern -- worthy as it is of noting somewhere -- might be reaching too far for HTTP/QUIC or QUIC docs, since it applies to not just QUIC. -- 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/1432#issuecomment-396432664 ----==_mimepart_5b1f1b6cd5508_9733f9313018f844164d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@krasic Yes, you're right, and I wa= sn't being precise. It's not always a problem, but it can become one, bas= ed on how the application manages its data.

@martinthomson: I agree that w= e shouldn't be looking to provide a concrete solution for, but we can gen= erally say something about the potential implications of consuming stream= buffers for data that can be read. Beyond that, I think trying to captur= e this application design pattern -- worthy as it is of noting somewhere = -- might be reaching too far for HTTP/QUIC or QUIC docs, since it applies= to not just QUIC.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f1b6cd5508_9733f9313018f844164d7-- From nobody Mon Jun 11 18:08:43 2018 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 D20E7130DC3 for ; Mon, 11 Jun 2018 18:08:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ndfuLtInIyod for ; Mon, 11 Jun 2018 18:08:35 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A104212D7F8 for ; Mon, 11 Jun 2018 18:08:35 -0700 (PDT) Date: Mon, 11 Jun 2018 18:08:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528765714; bh=gBDXBzoaspF708InL7/J2SPsRLNs9p09hrouwnF/OAo=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=gdRaZkiZ61jxicStj94C8oWqo63BGTFUGvVJbursJU6Jt+QaTattHM1qtSrL2YCv6 I3Qx2nuUBLkDm+jfAuFRAYk2gryGkRYOwLpPMKAGs5FHYrSO+puK7IyQl4OBPkNHXF wpgyUYadLTRByMip/2DnhP0LxVo3DYPncJIAdJ10= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f1d1288275_6f403fb78a97cf80780a7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 12 Jun 2018 01:08:40 -0000 ----==_mimepart_5b1f1d1288275_6f403fb78a97cf80780a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The encoding of ACK_ECN frame (proposed in #1372) has following issues. * size of ACK_ECN frame becomes bigger as more and more packets are exchanged, since the counters represent the total number of packets being exchanged using the connection * requires the receiver of the ACK_ECN frames to detect duplicates to avoid duplicate packet injection attacks * does not have full protection against duplicate packet injection attacks, since detection on the receiver cannot be deterministic As discussed in Kista, these issues are not blockers for merging #1372, but we might want to consider adopting different encoding scheme to address them. -- 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/1439 ----==_mimepart_5b1f1d1288275_6f403fb78a97cf80780a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The encoding of ACK_ECN frame (proposed in #1372) has following issues.

  • size of ACK_ECN frame becomes bigger as more and more packets are exchanged, since the counters represent the total number of packets being exchanged using the connection
  • requires the receiver of the ACK_ECN frames to detect duplicates to avoid duplicate packet injection attacks
  • does not have full protection against duplicate packet injection attacks, since detection on the receiver cannot be deterministic

As discussed in Kista, these issues are not blockers for merging #1372, but we might want to consider adopting different encoding scheme to address them.

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

----==_mimepart_5b1f1d1288275_6f403fb78a97cf80780a7-- From nobody Mon Jun 11 18:11:28 2018 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 3D413130DC3 for ; Mon, 11 Jun 2018 18:11:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4BIMvhNlay0J for ; Mon, 11 Jun 2018 18:11:17 -0700 (PDT) Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8A7A12D7F8 for ; Mon, 11 Jun 2018 18:11:17 -0700 (PDT) Date: Mon, 11 Jun 2018 18:11:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528765875; bh=H2viN3Y6Lt1+qyTgHG82Dbvb9TlOwltzvd7ZCNJk16Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z1rdUmgM499uf5zL65pcZLRFHDTcOzMRbGUX5FCUPrSS9UNARx6DyP82bJkrFM2ir /wOpXbuwm6WMgjcCAj4yENe2sx1PuQ1LjfysjEDCjQkwdkTJYqhO53Eztju2lYhgkm +qRuIOy3xWj/6qTW29s3wHABRZ25CZOwyfLEo8uo= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f1db396926_13813fdfc2806f8844120"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 12 Jun 2018 01:11:26 -0000 ----==_mimepart_5b1f1db396926_13813fdfc2806f8844120 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A straw-man that addresses the issues is to use a bit-vector for marking CE packets. Instead of carrying three counters, an ACK_ECN frame will carry a bit-vector that indicates which PNs in the ACK were CE-marked. For example, when 3 packets (PN=8,3,2) are acknowledged, the bit vector will contain three bits that indicate whether the packet identified by the PN was CE-marked. A bit vector with a value 100 will indicate that PN=8 was CE-marked. The straw-man addresses all of the three issues. Re space efficiency of the encoding, the proposed approach consumes one bit per packet, whereas #1372 consumes 3 to 17 octets1 even when only one packet is being acknowledged. Duplicate detection becomes the responsibility of the sender of the packet rather than that of the receiver. It also becomes reliable. While processing an acknowledgement, an endpoint consults it's inflight packet map to see which packets have been newly acknowledged. With the proposed encoding, the endpoint can see if the CE bit has been set as part of that process, and only utilize the CE bits associated to a newly acknowledged packet. The downside of the straw-man is that ACK_ECN frame does not indicate how many packets were ECN(1) marked. If we need to communicate that, we could for either retain the counter for ECN(1) marked packets, or use a different encoding in the bit vector (i.e. 0 - ECN(0), 10 - ECN(1), 11 - ECN-CE). [1] It is assumed that the number of ECN(1) marked packets would remain zero. -- 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/1439#issuecomment-396433945 ----==_mimepart_5b1f1db396926_13813fdfc2806f8844120 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A straw-man that addresses the issues is to use a bit-vector for marki= ng CE packets.

Instead of carrying three counters, an ACK_ECN frame will carry a bit-= vector that indicates which PNs in the ACK were CE-marked.

For example, when 3 packets (PN=3D8,3,2) are acknowledged, the bit vec= tor will contain three bits that indicate whether the packet identified b= y the PN was CE-marked. A bit vector with a value 100 will indicate that = PN=3D8 was CE-marked.

The straw-man addresses all of the three issues.

Re space efficiency of the encoding, the proposed approach consumes on= e bit per packet, whereas #1372 consumes 3 to 17 octets1 even when only one= packet is being acknowledged.

Duplicate detection becomes the responsibility of the sender of the pa= cket rather than that of the receiver. It also becomes reliable.

While processing an acknowledgement, an endpoint consults it's infligh= t packet map to see which packets have been newly acknowledged. With the = proposed encoding, the endpoint can see if the CE bit has been set as par= t of that process, and only utilize the CE bits associated to a newly ack= nowledged packet.

The downside of the straw-man is that ACK_ECN frame does not indicate = how many packets were ECN(1) marked. If we need to communicate that, we c= ould for either retain the counter for ECN(1) marked packets, or use a di= fferent encoding in the bit vector (i.e. 0 - ECN(0), 10 - ECN(1), 11 - EC= N-CE).

[1] It is assumed that the number of ECN(1) marked packets would remai= n zero.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f1db396926_13813fdfc2806f8844120-- From nobody Mon Jun 11 18:28:41 2018 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 BC7ED130DCC for ; Mon, 11 Jun 2018 18:28:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 I5wKvCN2tRus for ; Mon, 11 Jun 2018 18:28:34 -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 C322C130EB2 for ; Mon, 11 Jun 2018 18:28:34 -0700 (PDT) Date: Mon, 11 Jun 2018 18:28:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528766913; bh=4H0bRhCrPxFF0PvQc0PCRBiVZFS6TV/dFVuw+Tft/pM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vnohbiw3yCW/IbH1/gwLq1czK00PxlWQFLw3TUT5ShtjhO/kKdad0mtM0ejB79QDw q2cpBN+xQV5lXzPiVVWStFeEzSBuz+7iSU8t40s37nHtHWj29nkN/XEJx2oT/JGj3K 3L600hwxyjoNAlP5MLn7ZbepeefvalpkbU9Guby0= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f21c1dec19_ea333fa0d892ef88284164"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 12 Jun 2018 01:28:38 -0000 ----==_mimepart_5b1f21c1dec19_ea333fa0d892ef88284164 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop Thank you for the clarification. I can understand the fact that we want to have a way to signal back-pressure when more than one stream is involved. OTOH, as we all agree, using back-pressure has the danger of seeing a deadlock. It makes sense to have the implications being clarified in the documents. And I would like to second @martinthomson's argument that the issue is not related to length-prefixes. Consider using HTTP/1 on QUIC. It makes perfect sense for an application to keep the response headers in the receive buffer until CR-LF-CR-LF arrives. -- 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/1432#issuecomment-396436567 ----==_mimepart_5b1f21c1dec19_ea333fa0d892ef88284164 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@MikeBishop Thank you for the c= larification. I can understand the fact that we want to have a way to sig= nal back-pressure when more than one stream is involved.

OTOH, as we all agree, using back-pressure has the danger of seeing a = deadlock. It makes sense to have the implications being clarified in the = documents.

And I would like to second @martin= thomson's argument that the issue is not related to length-prefixes. = Consider using HTTP/1 on QUIC. It makes perfect sense for an application = to keep the response headers in the receive buffer until CR-LF-CR-LF arri= ves.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f21c1dec19_ea333fa0d892ef88284164-- From nobody Mon Jun 11 18:34:13 2018 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 B5393130EB2 for ; Mon, 11 Jun 2018 18:34:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yQZGn-hEBlKA for ; Mon, 11 Jun 2018 18:34:08 -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 E730D130EAC for ; Mon, 11 Jun 2018 18:34:07 -0700 (PDT) Date: Mon, 11 Jun 2018 18:34:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528767246; bh=h+pxUNB5h/kJe4ODO+oXrVSQi/rj+mpuefHXc8V6u3Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NF4nKMpehRwSgXgge8KwM8v19YykUL5Oy3kFt/SAmkmtWvFvUpoq/WwXI5loMaZwS aDQgeLUH9c2Hz+DWTSG1v2PDM2/fTbWJPqYkh4qna5NQEo3aQfr/kLSiLPFWQAxaBB bmMZVzuaDvrl+2H4+exZNk9HLi/O95FsBy09XhbI= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f230ef10e0_6f4f3fb78a97cf8012868c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 12 Jun 2018 01:34:11 -0000 ----==_mimepart_5b1f230ef10e0_6f4f3fb78a97cf8012868c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: +: Initial value = 0, incremented when a packet marked ECT(0) is received + +ECT_1: + +: Initial value = 0, incremented when a packet marked ECT(1) is received + +CE: + +: Initial value = 0, incremented when a packet marked CE is received + +Reception of duplicate packets SHOULD NOT increment the counters. #1439 proposes a different scheme that removes the requirement on the receiver-side to detect duplicates. -- 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/1372#discussion_r194593812 ----==_mimepart_5b1f230ef10e0_6f4f3fb78a97cf8012868c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:
+: Initial value = 0, incremented when a packet marked ECT(0) is received
+
+ECT_1:
+
+: Initial value = 0, incremented when a packet marked ECT(1) is received
+
+CE:
+
+: Initial value = 0, incremented when a packet marked CE is received
+
+Reception of duplicate packets SHOULD NOT increment the counters.

#1439 proposes a different scheme that removes the requirement on the receiver-side to detect duplicates.

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

----==_mimepart_5b1f230ef10e0_6f4f3fb78a97cf8012868c-- From nobody Mon Jun 11 20:57:00 2018 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 39EED130F1B for ; Mon, 11 Jun 2018 20:56:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 bGsojQzsi4n9 for ; Mon, 11 Jun 2018 20:56:54 -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 D8CD5130DCE for ; Mon, 11 Jun 2018 20:56:53 -0700 (PDT) Date: Mon, 11 Jun 2018 20:56:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528775813; bh=DjMFibohyQmhPjDrUkjJ5F5O8EaB6DOxHA+l/ZMm5iU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1LTkQD7J8rVMORXkQqQoRt67lDWpzrTCqE9SGdDGWiZjcwBmyeoLhnRKrvf379E1E cCqNlBhlYxcIIqxDzrE5KINOhHrpxGKgU4tUUn8x7rFZyXEs6oy7b4zWDQQA+Laguh IwHH2fCUgi8of7G9nsgGD82NfzFLqM1NVucIFPwI= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f4485b811_13192b1213334f50425348"; 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.26 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: Tue, 12 Jun 2018 03:56:58 -0000 ----==_mimepart_5b1f4485b811_13192b1213334f50425348 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable IIRC, HPACK EOS is so long because you never actually send all of it =E2=80= =93 if the Huffman-encoded string doesn=E2=80=99t end on a byte boundary = (and it probably doesn=E2=80=99t), you put as many bits of the EOS symbol= as needed to reach the byte boundary. The whole thing should never appe= ar on the wire; at most seven bits of it. Of course, if you=E2=80=99re d= epending on recognizing it as it goes by, that requires parsing each symb= ol as it passes; the length prefix makes it much easier. From: Dmitri Tikhonov Sent: Monday, June 11, 2018 5:43 PM To: quicwg/base-drafts Cc: Mike Bishop ; Comment Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432= ) @martinthomson, mine wasn't a suggestio= n, but rather something to keep in mind as we weigh different options. Th= at is, there is a way to not use prefix length at all. Your analysis is c= orrect. The biggest downside to me is that the EOS symbol is so long. =E2=80=94 You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. -- = 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/1432#issuecomment-396458126= ----==_mimepart_5b1f4485b811_13192b1213334f50425348 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable IIRC, HPACK EOS is so long because you never actually send all of it =E2=80= =93 if the Huffman-encoded string doesn=E2=80=99t end on a byte boundary = (and it probably doesn=E2=80=99t), you put as many bits of the EOS symbol= as needed to reach the byte boundary. The whole thing should never appe= ar on the wire; at most seven bits of it. Of course, if you=E2=80=99re d= epending on recognizing it as it goes by, that requires parsing each symb= ol as it passes; the length prefix makes it much easier.

From: Dmitri Tikhonov <notifications@github.com>
Sent: Monday, June 11, 2018 5:43 PM
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Mike Bishop <mbishop@evequefou.be>; Comment <comment@noreply= .github.com>
Subject: Re: [quicwg/base-drafts] Length-prefixes and flow control (#1432= )


@martinthomson<https://github.com/martinthomson>, mine wasn't a= suggestion, but rather something to keep in mind as we weigh different o= ptions. That is, there is a way to not use prefix length at all. Your ana= lysis is correct. The biggest downside to me is that the EOS symbol is so= long.

=E2=80=94
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/qui= cwg/base-drafts/issues/1432#issuecomment-396429945>, or mute the threa= d<https://github.com/notifications/unsubscribe-auth/AEE2ha2hZGTKuCUGPv= Axuog8eYQzTuTCks5t7w6KgaJpZM4UgCd3>.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1f4485b811_13192b1213334f50425348-- From nobody Mon Jun 11 23:57:22 2018 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 9C2B1130E0C for ; Mon, 11 Jun 2018 23:57:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 huHAkLJy8VE1 for ; Mon, 11 Jun 2018 23:57:17 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA91912F1A6 for ; Mon, 11 Jun 2018 23:57:15 -0700 (PDT) Date: Mon, 11 Jun 2018 23:57:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528786634; bh=PbD+IoMHDtltHsELucxQAq1oQw8EfViWHF2uxtIqrPE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HxgLa0nto00PC9pkjSoUP6kCS3+Fo02I/083L+bJVIknA4Lf2oXP4X1sciG33pzit BbHWa6NM1d7QFzQ4QpfwllhytkfDM/L+dqzqs/ua3thw73lgJpFblYphx6Bze/ZWhA cbQknsQVDmHMssaV77uNckjgQ/Nr9PMaMaA6uxKA= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f6ecaeae42_43a12b269031ef5c2508e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 12 Jun 2018 06:57:20 -0000 ----==_mimepart_5b1f6ecaeae42_43a12b269031ef5c2508e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > Every QUIC packet that is coalesced into a single UDP datagram is separate and complete. Though the values of some fields in the packet header might be redundant, no fields are omitted. The receiver of coalesced QUIC packets MUST individually process each QUIC packet and separately acknowledge them, as if -they were received as the payload of different UDP datagrams. +they were received as the payload of different UDP datagrams. If one or more +packets in a datagram cannot be processed, either because the keys are not yet +available or because decryption fails, the receiver MUST still attempt to It might make sense to add the case where the long header type is invalid. Explicitly allowing a sender to emit an invalid long header type will help us grease the first octet. -- 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/1423#pullrequestreview-127837762 ----==_mimepart_5b1f6ecaeae42_43a12b269031ef5c2508e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

>  
 Every QUIC packet that is coalesced into a single UDP datagram is separate and
 complete.  Though the values of some fields in the packet header might be
 redundant, no fields are omitted.  The receiver of coalesced QUIC packets MUST
 individually process each QUIC packet and separately acknowledge them, as if
-they were received as the payload of different UDP datagrams.
+they were received as the payload of different UDP datagrams.  If one or more
+packets in a datagram cannot be processed, either because the keys are not yet
+available or because decryption fails, the receiver MUST still attempt to

It might make sense to add the case where the long header type is invalid. Explicitly allowing a sender to emit an invalid long header type will help us grease the first octet.

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

----==_mimepart_5b1f6ecaeae42_43a12b269031ef5c2508e1-- From nobody Tue Jun 12 01:58:36 2018 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 26C3E13111A for ; Tue, 12 Jun 2018 01:58:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 36rsXwhPKnZU for ; Tue, 12 Jun 2018 01:58:32 -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 23FB7130E32 for ; Tue, 12 Jun 2018 01:58:32 -0700 (PDT) Date: Tue, 12 Jun 2018 01:58:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528793909; bh=W0BLTjdYx2KF07Q5sNwXDaP6bUM8dZufPktewOOj+JA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=s0P+Bc88H7tZEKnB+wN1/5c0Qbv961VroRDLlP7KGescH6SQRymVyIJiPvQRD55P2 8DD+t7DRyjbxu0lb2qbXPdP4bsdwVVOt+x+9w01hBRdURrRMbn0HMZ8vZiw0oPM5x4 nc8vNAI8MRTILG1fhJlRc7MqT02ExX66Ru9dTwsE= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f8b35b589f_57e13fbb9d3c8f78431026"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 08:58:35 -0000 ----==_mimepart_5b1f8b35b589f_57e13fbb9d3c8f78431026 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. fdf9df7 Reverting some rewrapping that are not necessary to reduce clutter. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/e60cc8fed8dc5b1d5d819b3ae3013715fcbbda5f..fdf9df7f91ea314d4e42e246150e2341001d84f8 ----==_mimepart_5b1f8b35b589f_57e13fbb9d3c8f78431026 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • fdf9df7 Reverting some rewrapping that are not necessary to reduce clutter.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1f8b35b589f_57e13fbb9d3c8f78431026-- From nobody Tue Jun 12 01:59:17 2018 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 A1C04131113 for ; Tue, 12 Jun 2018 01:59:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DtYq4Hn5bhSc for ; Tue, 12 Jun 2018 01:59:12 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4283F130E32 for ; Tue, 12 Jun 2018 01:59:12 -0700 (PDT) Date: Tue, 12 Jun 2018 01:59:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528793951; bh=V56QJQm5qqj9qTTM7wRFC/JF68c4obUzDHDG96B1cMo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=auBH9KVYOZXSMm9pR2QclhNMVBhgnc5O3QwsJwUoM6HRm72cfwoQbJZC2rlmE7Ozi /H02VsibNf/mVQUyRF1GYlLPp9F3oZLCELhYF1ctIMWN6yPHDui3FQORwBMRcwVuer NY7t2KPF8/WyKvKq0sdpJHY/CPzZWGDtzZhjfgXo= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f8b5f67d74_594b3facf9754f783548ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 12 Jun 2018 08:59:15 -0000 ----==_mimepart_5b1f8b5f67d74_594b3facf9754f783548ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -1061,20 +1063,21 @@ negotiation, which is the same no matter which reserved version was sent. A server MAY therefore send different reserved version numbers in the Version Negotiation Packet and in its transport parameters. -A client MAY send a packet using a reserved version number. This can be used to -solicit a list of supported versions from a server. +A client MAY send a packet using a reserved version number. This can be I have reverted those that aren't necessary to make lint happy. -- 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/1372#discussion_r194663034 ----==_mimepart_5b1f8b5f67d74_594b3facf9754f783548ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1061,20 +1063,21 @@ negotiation, which is the same no matter which reserved version was sent.
 A server MAY therefore send different reserved version numbers in the Version
 Negotiation Packet and in its transport parameters.
 
-A client MAY send a packet using a reserved version number.  This can be used to
-solicit a list of supported versions from a server.
+A client MAY send a packet using a reserved version number. This can be

I have reverted those that aren't necessary to make lint happy.

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

----==_mimepart_5b1f8b5f67d74_594b3facf9754f783548ed-- From nobody Tue Jun 12 02:25:13 2018 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 8E78C13112B for ; Tue, 12 Jun 2018 02:25:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 14x9j_fxTWAD for ; Tue, 12 Jun 2018 02:25:08 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC2CA13112A for ; Tue, 12 Jun 2018 02:25:07 -0700 (PDT) Date: Tue, 12 Jun 2018 02:25:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528795507; bh=QzQfIFkYp7YuE9pD02m082Ih4fCB8yKLXxOJVNXYclo=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=TvFyA1mvFpV+K2eguXJ6Km9AOWVd6KrkXO5a88f0Ac1RgUogGKAKQ0m2E+iQKLx4q 96r/qGoD/2KYbEXAtnBMoBTsnFuobcUdeeJdGYotq2Up3yqXx+IL42hUq3BnONUeK+ giIwUTOcpDHIlFNeiLYc30UOPaC2AT1JunAXEpRk= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Current Code for Recovery period misscounts (#1440) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f917333b00_594b3facf9754f78526040"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 12 Jun 2018 09:25:11 -0000 ----==_mimepart_5b1f917333b00_594b3facf9754f78526040 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Recovery draft: InRecovery(packet_number): return packet_number <= end_of_recovery end_of_recovery = largest_sent_packet To my understanding the end of recovery will be when one ACKs the packet that is one larger than the largest sent when the congestion event happens. Thus, the InRecovery function should use only < as long as end_of_recovery is not assigned to largest_sent_packet+1 (assuming all PNs are used). -- 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/1440 ----==_mimepart_5b1f917333b00_594b3facf9754f78526040 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Recovery draft:

InRecovery(packet_number):
return packet_number <= end_of_recovery

end_of_recovery = largest_sent_packet

To my understanding the end of recovery will be when one ACKs the packet that is one larger than the largest sent when the congestion event happens. Thus, the InRecovery function should use only < as long as end_of_recovery is not assigned to largest_sent_packet+1 (assuming all PNs are used).

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

----==_mimepart_5b1f917333b00_594b3facf9754f78526040-- From nobody Tue Jun 12 02:26:38 2018 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 862A0131126 for ; Tue, 12 Jun 2018 02:26:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7DeEE6uG8SuH for ; Tue, 12 Jun 2018 02:26:33 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9185131128 for ; Tue, 12 Jun 2018 02:26:33 -0700 (PDT) Date: Tue, 12 Jun 2018 02:26:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528795593; bh=rx2IcsLH3NAz6MFjNTwF/1xDkFxSO9PkmUPIHMNw67g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1AWzqFoFiAtOz1sNYpdBZqRrUhftXl5/aSG7A+2OeoXiekOl8ADWhRzuychZtHzqI ARjRgXBCIF4GhqyqlaOkz2uGvVIlZ5Aym9rz0PWXwk+NzqhiIKWaqL5jvHKbA4epkh FNifvB+dW9/GSngTG1huhIT7XLn5kaVuX5Jy3vxY= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f91c935533_61443fd7f07cef7c4391c7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 12 Jun 2018 09:26:37 -0000 ----==_mimepart_5b1f91c935533_61443fd7f07cef7c4391c7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -1042,6 +1081,26 @@ acked_packet from sent_packets. kDefaultMss * acked_packet.bytes / congestion_window ~~~ +### On Packets Marked + +Invoked by an increment in the number of CE marked packets, as +indicated by a newly received ACK_ECN frame when compared to +ack_ce_cntr. + +~~~ + OnPacketsMarked(ce_counter): + if (ce_counter > ack_ce_cntr): + // update ack_ce_cntr + ack_ce_cntr = ce_counter + if (!InRecovery(largest_acked_packet)): Agreed on both, I have reshuffled the pseudocode and introduced a function CongestionEvent. I also noticed that InRecovery appears to be ending one packet to early: https://github.com/quicwg/base-drafts/issues/1440 -- 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/1372#discussion_r194671437 ----==_mimepart_5b1f91c935533_61443fd7f07cef7c4391c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -1042,6 +1081,26 @@ acked_packet from sent_packets.
          kDefaultMss * acked_packet.bytes / congestion_window
 ~~~
 
+### On Packets Marked
+
+Invoked by an increment in the number of CE marked packets, as
+indicated by a newly received ACK_ECN frame when compared to
+ack_ce_cntr.
+
+~~~
+   OnPacketsMarked(ce_counter):
+     if (ce_counter > ack_ce_cntr):
+       // update ack_ce_cntr
+       ack_ce_cntr = ce_counter
+     if (!InRecovery(largest_acked_packet)):

Agreed on both, I have reshuffled the pseudocode and introduced a function CongestionEvent. I also noticed that InRecovery appears to be ending one packet to early: #1440

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

----==_mimepart_5b1f91c935533_61443fd7f07cef7c4391c7-- From nobody Tue Jun 12 02:33:59 2018 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 61FD113112B for ; Tue, 12 Jun 2018 02:33:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 aebkI_h2ITDH for ; Tue, 12 Jun 2018 02:33:53 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 7EE1D130F6D for ; Tue, 12 Jun 2018 02:33:53 -0700 (PDT) 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=gWTyHZph7RgvsOyJwfpTSP1ljXY=; b=vcvieqXuAHzhTnlg NbCVKlNz+fJ64k/eQMsK5Hsm9pS18r5vPTSRP+TL9ma33uGM92/TIL/hbVntQKgC Xty+8EdI8zqm11ixG01cFz54Ut2ad92ypqGdfBY05lTaZH6ygzFb+m3MAjRkGxMl hp3q8B8PK61rOrnDQs61wJGV/+w= Received: by filter0823p1las1.sendgrid.net with SMTP id filter0823p1las1-22504-5B1F9380-4 2018-06-12 09:33:52.226351567 +0000 UTC Received: from github-lowworker11-cp1-prd.iad.github.net (unknown [192.30.252.35]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id -5H4_jA_SAO1rYfMU53ZmQ for ; Tue, 12 Jun 2018 09:33:52.163 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker11-cp1-prd.iad.github.net (Postfix) with ESMTP id 2691BE1080 for ; Tue, 12 Jun 2018 02:33:52 -0700 (PDT) Date: Tue, 12 Jun 2018 09:33:52 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f938025156_3deb3fd7f07cef7c5585c3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2HoRSTcTZq9YgF2GF3llJlUQ1dJCHuM7n8Nf vZRtH8Dr0Nocd3mpnOCpsncw2QetO8U0gEV+IQAHuSvGlWGofirVSP6QEOcwolID1X0DvEZIA7kKvE IS/ziFxJ9T1YJtW5ZSC1jAeXwuALt76sXKbUC5/u2zY530s9MaWTlLbq9kweQAmeTy7XQGSG5mwirp M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 09:33:57 -0000 ----==_mimepart_5b1f938025156_3deb3fd7f07cef7c5585c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + +It is expected that QUIC discards duplicate packets early, however if that is +not the case **\[ED note, have not seen any clear statement in the drafts]**, +then it should be verified that the number of ECT marked packets are equal to or +larger that the amount of ECT marked packets that have been transmitted. + +### Continous Verification of ECN {#ecn-continous-verification} + +If the ECN capabiity check was successful and the endpoint continus to send ECT +marked packets then continous verification is applied. This is to detect any +cases when ECN field is bleached, that is, zeroed out by a network node, likely +as the result of a routing changes since the ECN capability check. + +For each ACK_ECN frame that is received, the total number of ACKed packets are Yes, except that larger needs to be less in this case. -- 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/1372#discussion_r194673645 ----==_mimepart_5b1f938025156_3deb3fd7f07cef7c5585c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+It is expected that QUIC discards duplicate packets early, however if that is
+not the case **\[ED note, have not seen any clear statement in the drafts]**,
+then it should be verified that the number of ECT marked packets are equal to or
+larger that the amount of ECT marked packets that have been transmitted.
+
+### Continous Verification of ECN {#ecn-continous-verification}
+
+If the ECN capabiity check was successful and the endpoint continus to send ECT
+marked packets then continous verification is applied. This is to detect any
+cases when ECN field is bleached, that is, zeroed out by a network node, likely
+as the result of a routing changes since the ECN capability check.
+
+For each ACK_ECN frame that is received, the total number of ACKed packets are

Yes, except that larger needs to be less in this case.

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

----==_mimepart_5b1f938025156_3deb3fd7f07cef7c5585c3-- From nobody Tue Jun 12 02:41:15 2018 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 C678813112B for ; Tue, 12 Jun 2018 02:41:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zDHtLIrRtwDq for ; Tue, 12 Jun 2018 02:41:10 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 2B57A131130 for ; Tue, 12 Jun 2018 02:41:10 -0700 (PDT) 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=uXcWZK3ri78Frc0zgLkugxwgMFI=; b=a9MN5k7xSMYegDmD A/40BNNj8LXNgTOPOiz1SZZ+DNlp6v8VtXz2Hfnn7yvwhEfsVPz/1Dqpwy3BaleS 8gKuZG3lWzGHcPKwe7XcoR8RzqJieUEg09ucYskp7q6K5xK5gV7md+yZcut6XC3Q Oh8rdmYpcHlbsSBIHcxKuOZcVik= Received: by filter1738p1mdw1.sendgrid.net with SMTP id filter1738p1mdw1-6990-5B1F9534-F 2018-06-12 09:41:08.360791258 +0000 UTC Received: from github-lowworker-baaab27.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id L5Y0AKYgRMqiYhFPbaMkmQ for ; Tue, 12 Jun 2018 09:41:08.326 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-baaab27.cp1-iad.github.net (Postfix) with ESMTP id 4C40880313 for ; Tue, 12 Jun 2018 02:41:08 -0700 (PDT) Date: Tue, 12 Jun 2018 09:41:08 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f95344a802_5dbc2ac927400f54882790"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1HE/NjVuLSKOsfVN7lHL8JEzJiJj+YNzanTD qLO2DoGI2Om14cW04q+ozCDlKncwGjtRKlZiB/I6UEM965nhJSiGO0vQvC6eTAPpWmU9GGcmmkhlnx 3dONGeRGjW+xWPwGprCuogTM7OcpwSM2CAkC7aTPOWLEryKL44nD913eNpWrxN8F0dOgg62uiUn63p w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 09:41:14 -0000 ----==_mimepart_5b1f95344a802_5dbc2ac927400f54882790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -2816,6 +2960,10 @@ ACK Block (repeated): ### Sending ACK Frames +ACK Frames MAY be sent when all packets to be acknowledge had an IP header with Okay, I removed this paragraph, and moved the MAY statement to the ACK_ECN frame, the MUST statement was already present. -- 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/1372#discussion_r194675822 ----==_mimepart_5b1f95344a802_5dbc2ac927400f54882790 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2816,6 +2960,10 @@ ACK Block (repeated):
 
 ### Sending ACK Frames
 
+ACK Frames MAY be sent when all packets to be acknowledge had an IP header with

Okay, I removed this paragraph, and moved the MAY statement to the ACK_ECN frame, the MUST statement was already present.

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

----==_mimepart_5b1f95344a802_5dbc2ac927400f54882790-- From nobody Tue Jun 12 02:48:34 2018 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 36CFC131110 for ; Tue, 12 Jun 2018 02:48:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 V6Qt8DO5nYjf for ; Tue, 12 Jun 2018 02:48:29 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 19152130E0D for ; Tue, 12 Jun 2018 02:48:29 -0700 (PDT) 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=fzOdbfWi3Lwd1GILg6TQ+xK9Hco=; b=j6kUZGgQtLO4d7/8 2EzEkvMRiHSd5ODtvUHu1rzXyv8MdmKvaa2yGo/YmsoegCT+7xE7xhJRWqOghXPO zE2q6BjMYGjxQYoe+WdYvJ9Wcowavbd4376ndsr05HxIqT93Fge3Ff/pwOVLxrZZ FZzYdo3f3H7Kv9YP4rom9h1Q/7I= Received: by filter0813p1las1.sendgrid.net with SMTP id filter0813p1las1-13152-5B1F96EB-13 2018-06-12 09:48:28.037147563 +0000 UTC Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id bKCtIs-7TUWRkaWu46sdzQ for ; Tue, 12 Jun 2018 09:48:27.941 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id E3E24422F1 for ; Tue, 12 Jun 2018 02:48:27 -0700 (PDT) Date: Tue, 12 Jun 2018 09:48:28 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1f96ebe2043_54853f95ab89cf806974a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0N0MXOu3uis/44KZOWLnXrM/9CU0t02LRdni BNh6Cen1FwZzSONe4wCxjyJFcEC+xMGvBZbybMZXDRS3zTULa0aCT6yP2YMLYRAKilm+YzImO+OI66 yYPdycKRrUoDTS56JaM8XsMhOVf9l3IMPVBE1utZr4VAX4IQClAfPAeQ5im3SEGCrtY2VM2zLUtgcx w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 09:48:31 -0000 ----==_mimepart_5b1f96ebe2043_54853f95ab89cf806974a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. ec97fd8 Addressing issues raised by Ian Sweet on 180611. Editorial improvements, new psuedo code function. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/fdf9df7f91ea314d4e42e246150e2341001d84f8..ec97fd81158d29261e3ea4bb6e80a64efc0aa7a2 ----==_mimepart_5b1f96ebe2043_54853f95ab89cf806974a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • ec97fd8 Addressing issues raised by Ian Sweet on 180611. Editorial improvements, new psuedo code function.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1f96ebe2043_54853f95ab89cf806974a-- From nobody Tue Jun 12 04:56:51 2018 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 52651130E44 for ; Tue, 12 Jun 2018 04:56:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 t2grA9VLTMzY for ; Tue, 12 Jun 2018 04:56:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F89A130E27 for ; Tue, 12 Jun 2018 04:56:42 -0700 (PDT) Date: Tue, 12 Jun 2018 04:56:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528804601; bh=PxyDEZtKV/WVQQ4HepNfk74UBS4J8KowFPRauaVJQZU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NmQFxVZ4ShVSFMv0e7w+7pVrn4aDR3/iYmEvu89D5TiuvFrzk0uBSk6RpFh+kD2/Q yWFnpjb5/PRSsZ+oJQnCsoNcLGbNiwL7bqboKZGBuCo7YeGMkSKnWiGs/9875A5KNZ 4sZW/g4rPg2Kbp0KJiNj00aRXdpk2nW2LesCNU+8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fb4f959111_18172ac1a3ab2f54784b6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 12 Jun 2018 11:56:48 -0000 ----==_mimepart_5b1fb4f959111_18172ac1a3ab2f54784b6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't know that much about congestion control algorithms, but at some point I made a note of the following: http://modong.github.io/pcc-page/ -- 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/1428#issuecomment-396563553 ----==_mimepart_5b1fb4f959111_18172ac1a3ab2f54784b6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I don't know that much about congestion control algorithms, but at some point I made a note of the following:

http://modong.github.io/pcc-page/

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

----==_mimepart_5b1fb4f959111_18172ac1a3ab2f54784b6-- From nobody Tue Jun 12 05:35:43 2018 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 9EFC6130E8D for ; Tue, 12 Jun 2018 05:35:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 pVADh6XHZZc0 for ; Tue, 12 Jun 2018 05:35:39 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1253C130E27 for ; Tue, 12 Jun 2018 05:35:39 -0700 (PDT) Date: Tue, 12 Jun 2018 05:35:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528806938; bh=ogWq/gqSy7NB9/gKJ8C6WfrbVqAzw6SdUkL+9DEsTrI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ne5SSaxDeQE+ZTu4UnYIbMuk+9LqS1GkDF78NipeGJzQo19GJoTmVbC+t6TXvfIIi boFn0bb6lSMKkEW5leUSkVl6hx3VtU9gxxcb5eLaXc99rjEJH2HhDm/iV55Ki81ob6 Cs1rZ3+UjEA54q63NECpRNN8wKoOmrWcXA7+gSwg= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fbe1a3c4c7_96b2adff0f38f54756a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 12:35:42 -0000 ----==_mimepart_5b1fbe1a3c4c7_96b2adff0f38f54756a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good point, I think PCC(or any other primarily rate based algorithm) would still perform well with a significantly reduced ack rate. -- 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/1428#issuecomment-396573284 ----==_mimepart_5b1fbe1a3c4c7_96b2adff0f38f54756a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Good point, I think PCC(or any other primarily rate based algorithm) would still perform well with a significantly reduced ack rate.

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

----==_mimepart_5b1fbe1a3c4c7_96b2adff0f38f54756a6-- From nobody Tue Jun 12 05:41:51 2018 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 A289F130E59 for ; Tue, 12 Jun 2018 05:41:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 LR2Jz0u4MmtO for ; Tue, 12 Jun 2018 05:41:45 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F15130E27 for ; Tue, 12 Jun 2018 05:41:45 -0700 (PDT) Date: Tue, 12 Jun 2018 05:41:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528807304; bh=61cnjATc7VpARSQoNY1lqryjCrTFbUx9jnqOj4CAv8w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TFvKyo2MUMR36d46eTM3E8xp//L1AuC4O2W9lJ4Q/9EcSoiHBO1W33D3hqMhViCUf 9QSh8hFQg89xhHLMa4baJqXPvqdaAeKNeMYtOBnAGTp7HBId3UtLlNss9yNpnoVVNI QefYIc000OLOwllEOJu31TNnEm53kgRYhAvq2YjY= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Current Code for Recovery period misscounts (#1440) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fbf8852758_11993fbf87e94f7c10227b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 12:41:48 -0000 ----==_mimepart_5b1fbf8852758_11993fbf87e94f7c10227b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit So end_of_recovery is assigned to the largest sent when recovery starts, as you said. Say the largest sent when recovery starts is 10. So when 11 is acked, we are no longer in recovery. InRecovery(10) returns true, and InRecovery(11) returns false, so I believe it's correct? -- 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/1440#issuecomment-396575169 ----==_mimepart_5b1fbf8852758_11993fbf87e94f7c10227b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So end_of_recovery is assigned to the largest sent when recovery start= s, as you said.

Say the largest sent when recovery starts is 10. So when 11 is acked,= we are no longer in recovery.

InRecovery(10) returns true, and InRecovery(11) returns false, so I be= lieve it's correct?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1fbf8852758_11993fbf87e94f7c10227b-- From nobody Tue Jun 12 05:49:18 2018 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 E5F08130E3F for ; Tue, 12 Jun 2018 05:49:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 u3fFvqDyuOxY for ; Tue, 12 Jun 2018 05:49:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00DB130E27 for ; Tue, 12 Jun 2018 05:49:06 -0700 (PDT) Date: Tue, 12 Jun 2018 05:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528807745; bh=j8u7Bvagj9ffdlZ/gw/iCc4CBOJ7KK2COpUKLTGna5M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=e+Sb9yyDSY5fftq3e4uPsBW5k/NRIPJS21o6UaLVbS+rLWWBTjb4v7z5WRV5nxzr3 V1c5pNihCaouR3fC0xmwsopphj2D3KRZKVVDXfuyxhaqITjokQDxpEtK6X17PztcTW rG7tEu0gNmx3YGhBITnNmQsmV3cIwdIYdn7p2FYo= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fc1412efbc_9782adff0f38f54141027"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 12 Jun 2018 12:49:15 -0000 ----==_mimepart_5b1fc1412efbc_9782adff0f38f54141027 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I don't understand how the sender will be able to handle duplications: "D= uplicate detection becomes the responsibility of the sender of the packet= rather than that of the receiver. It also becomes reliable." = To my understanding the current ACK practice to include all packets whose= ACK hasn't been ACKed already. Thus, a single PN will thus can be includ= ed in multiple consecutive ACK frames. Even without duplication a receive= d CE will thus be included in several packets. = Next this doesn't suppress or explain how a sender can suppress a duplica= te packet arriving to be ACKed in the same ACK frame. If a packet first a= rrives with a ECT(0) marking and then a duplicate with ECN-CE mark, the l= ater triggering an immediate ACK. Then how is it accounted that both has = been received? This is the particular scenario where the second CE mark m= ay be on-the-side attack or not. = When it comes to efficiency, one could apply the older Packet Number enco= ding format to the ECT counters. Thus include the N lowest bits of the co= unters using the variable length format. Requiring the sender to track th= e higher bits based on the lower bits. The receiver will have to use enou= gh bit-depth that the counter field doesn't wrap until multiple counter v= alues in different ACKs have been ACKed by the sender. That way the count= er's size would relate to the congestion window and RTT rather than conne= ction lifetime. = And as you say the ECN-CE marks are not sufficient to make the verificati= on to work. The ECT counters are still needed to track that ECN is workin= g properly and not are bleached by the network. Thus, you need at least c= ounters and a CE bit-vector. From my perspective, the CE bit-vector needs= to be compared only with the CE counter, not all the counters. = I would also note that the size of the bit-vector is very much depending = on the throughput and the RTT. = An implementation doing fully reliable ACKing will result in the ACKs con= taining all the packets sent the last RTT. Under this assumption the bit-= vector actually will be worse then even the max length CE counters (8 byt= es) in a variety of bandwidths and RTT as can be seen in below table. Ev= en if not using full reliable ACKing, then we still likely have several A= CKing intervals worth of information. How many packets that is very depen= dent on the ACK strategy regarding delayed ACKs. = Assuming 1200 bytes packet, the below table indicates packets per RTT for= a combination of RTT and bandwidth =C2=A0 | RTT (ms) | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 -- | -- | -- | -- | -- | -- Bandwidth (Mbps) | 1 | 10 | 50 | 100 | 200 0,1 | 0,01 | 0,10 | 0,52 | 1,04 | 2,08 1 | 0,10 | 1,04 | 5,21 | 10,42 | 20,83 5 | 0,52 | 5,21 | 26,04 | 52,08 | 104,17 10 | 1,04 | 10,42 | 52,08 | 104,17 | 208,33 25 | 2,60 | 26,04 | 130,21 | 260,42 | 520,83 50 | 5,21 | 52,08 | 260,42 | 520,83 | 1041,67 100 | 10,42 | 104,17 | 520,83 | 1041,67 | 2083,33 250 | 26,04 | 260,42 | 1302,08 | 2604,17 | 5208,33 500 | 52,08 | 520,83 | 2604,17 | 5208,33 | 10416,67 1000 | 104,17 | 1041,67 | 5208,33 | 10416,67 | 20833,33 2500 | 260,42 | 2604,17 | 13020,83 | 26041,67 | 52083,33 5000 | 520,83 | 5208,33 | 26041,67 | 52083,33 | 104166,67 10000 | 1041,67 | 10416,67 | 52083,33 | 104166,67 | 208333,33 -- = 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/1439#issuecomment-396577276= ----==_mimepart_5b1fc1412efbc_9782adff0f38f54141027 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I don't understand how the sender will be able to handle duplications:= "Duplicate detection becomes the responsibility of the sender of the pac= ket rather than that of the receiver. It also becomes reliable."

To my understanding the current ACK practice to include all packets wh= ose ACK hasn't been ACKed already. Thus, a single PN will thus can be inc= luded in multiple consecutive ACK frames. Even without duplication a rece= ived CE will thus be included in several packets.

Next this doesn't suppress or explain how a sender can suppress a dupl= icate packet arriving to be ACKed in the same ACK frame. If a packet firs= t arrives with a ECT(0) marking and then a duplicate with ECN-CE mark, th= e later triggering an immediate ACK. Then how is it accounted that both h= as been received? This is the particular scenario where the second CE mar= k may be on-the-side attack or not.

When it comes to efficiency, one could apply the older Packet Number e= ncoding format to the ECT counters. Thus include the N lowest bits of the= counters using the variable length format. Requiring the sender to track= the higher bits based on the lower bits. The receiver will have to use e= nough bit-depth that the counter field doesn't wrap until multiple counte= r values in different ACKs have been ACKed by the sender. That way the co= unter's size would relate to the congestion window and RTT rather than co= nnection lifetime.

And as you say the ECN-CE marks are not sufficient to make the verific= ation to work. The ECT counters are still needed to track that ECN is wor= king properly and not are bleached by the network. Thus, you need at leas= t counters and a CE bit-vector. From my perspective, the CE bit-vector ne= eds to be compared only with the CE counter, not all the counters.

I would also note that the size of the bit-vector is very much dependi= ng on the throughput and the RTT.
An implementation doing fully reliable ACKing will result in the ACKs con= taining all the packets sent the last RTT. Under this assumption the bit-= vector actually will be worse then even the max length CE counters (8 byt= es) in a variety of bandwidths and RTT as can be seen in below table. Ev= en if not using full reliable ACKing, then we still likely have several A= CKing intervals worth of information. How many packets that is very depen= dent on the ACK strategy regarding delayed ACKs.

Assuming 1200 bytes packet, the below table indicates packets per RTT = for a combination of RTT and bandwidth
=C2=A0 | RTT (ms) | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0
-- | -- | -- | -- | -- | --
Bandwidth (Mbps) | 1 | 10 | 50 | 100 | 200
0,1 | 0,01 | 0,10 | 0,52 | 1,04 | 2,08
1 | 0,10 | 1,04 | 5,21 | 10,42 | 20,83
5 | 0,52 | 5,21 | 26,04 | 52,08 | 104,17
10 | 1,04 | 10,42 | 52,08 | 104,17 | 208,33
25 | 2,60 | 26,04 | 130,21 | 260,42 | 520,83
50 | 5,21 | 52,08 | 260,42 | 520,83 | 1041,67
100 | 10,42 | 104,17 | 520,83 | 1041,67 | 2083,33
250 | 26,04 | 260,42 | 1302,08 | 2604,17 | 5208,33
500 | 52,08 | 520,83 | 2604,17 | 5208,33 | 10416,67
1000 | 104,17 | 1041,67 | 5208,33 | 10416,67 | 20833,33
2500 | 260,42 | 2604,17 | 13020,83 | 26041,67 | 52083,33
5000 | 520,83 | 5208,33 | 26041,67 | 52083,33 | 104166,67
10000 | 1041,67 | 10416,67 | 52083,33 | 104166,67 | 208333,33

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1fc1412efbc_9782adff0f38f54141027-- From nobody Tue Jun 12 06:16:30 2018 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 14074130EED for ; Tue, 12 Jun 2018 06:16:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 J_z-j3udj29k for ; Tue, 12 Jun 2018 06:16:25 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0DEA130E30 for ; Tue, 12 Jun 2018 06:16:24 -0700 (PDT) Date: Tue, 12 Jun 2018 06:16:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528809383; bh=tg9W+uweHCDZL+Wi1CoQ3F0q6BpGBRsFNTvjNUf3Tvk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OlRFW1SilYVD2aqHyTyXH0zsDED42fJRPeHyuj1cfYyf8TWjaJvAJPyAqqibtWpOf xely/nuZSPc5LpPqmsyeYuEoWSBv9PjBugmuOPE+Xg+Jkq0zEx77EY6eVKI5fGADtU OUo71DJR16PcDlupty0WBiETguBmFvwESX+IEbqw= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fc7a741b8e_207a3fbdc5ed4f78191250"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 13:16:27 -0000 ----==_mimepart_5b1fc7a741b8e_207a3fbdc5ed4f78191250 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Understood, thanks. -- 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/1424#issuecomment-396585178 ----==_mimepart_5b1fc7a741b8e_207a3fbdc5ed4f78191250 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Understood, thanks.

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

----==_mimepart_5b1fc7a741b8e_207a3fbdc5ed4f78191250-- From nobody Tue Jun 12 06:33:01 2018 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 0005E130EF7 for ; Tue, 12 Jun 2018 06:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 LJyhUZ4Puvgz for ; Tue, 12 Jun 2018 06:32:56 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40FFE130E3C for ; Tue, 12 Jun 2018 06:32:56 -0700 (PDT) Date: Tue, 12 Jun 2018 06:32:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528810375; bh=/MlQVVi25+ncP1p1sYGcQNDKwpTsFfunkBO5zEEUYVA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EUvi4ZzxgscGqBs60/8LZvtaHK2S35sGx1gty6fi30mPL3wvQDK87CPMHTKf0TxrR MYjoSD4Iz0AgECrHHFRH/NuWqLK1Gkk9kzcRteOiCuiR+iRzpvXwfRxZOvIRADvTLq GHBM+FS3GdDoNXPUOF5HMD4se5uO0hYgajQplj14= From: Lars Eggert Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fcb876223d_cc22b1f4a1a2f54133221"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.26 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: Tue, 12 Jun 2018 13:32:58 -0000 ----==_mimepart_5b1fcb876223d_cc22b1f4a1a2f54133221 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Half-baked idea: can we send Bloom filters instead of counts? -- 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/1439#issuecomment-396590257 ----==_mimepart_5b1fcb876223d_cc22b1f4a1a2f54133221 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Half-baked idea: can we send Bloom filters instead of counts?

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

----==_mimepart_5b1fcb876223d_cc22b1f4a1a2f54133221-- From nobody Tue Jun 12 07:06:18 2018 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 31736130F9A for ; Tue, 12 Jun 2018 07:06:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_SUMOF=5, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yH2DMnsYl-TU for ; Tue, 12 Jun 2018 07:05:59 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 449E1130E26 for ; Tue, 12 Jun 2018 07:05:59 -0700 (PDT) Date: Tue, 12 Jun 2018 07:05:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528812358; bh=cNoTDNTugpKL/4qxmpMeJiGp8/Fxyd8RYrYZQnfEKHI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hY0J0orEiXZPW1ANDGJ0zLToM454y17OMy3Ko1v745sPuyGXo6vuKG6s48/aw4p+c nCKXLkj/p2GP8cpPW+F+kQ+S1H1IpSaWR9JQEicct77K9utS5uURyruV1xra0JuVO5 EJD5QaTSmapoZWUGm9LS8abdaBIHev9qL9OKVvZM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fd34640eed_17943f8980438f8421448"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 14:06:14 -0000 ----==_mimepart_5b1fd34640eed_17943f8980438f8421448 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. Some small comments, but I think this looks good > (ECN-CE) SHOULD be acknowledged immediately to quicker react to -congesiton events. Additional ECN-CE marks received during the same +congestion events. Additional ECN-CE marks received during the same I don't think you need to say "during the same recovery period" since we're not proscribing any receiver side behavior corresponding to whether the marks are received within the same recovery period. > @@ -904,9 +904,9 @@ experimentation in using other response functions as discussed in The ACK_ECN frame defined in {{QUIC-TRANSPORT}} does not provide information on which of the newly acknowledged packets that nit: remove "that" > ~~~ - OnPacketsMarked(ce_counter): - if (ce_counter > ack_ce_cntr): - // update ack_ce_cntr - ack_ce_cntr = ce_counter - if (!InRecovery(largest_acked_packet)): + CongestionEvent(packet_number): I'd prefer OnCongestionEvent to be consistent with the other names. > @@ -1442,16 +1441,15 @@ endpoint, an ACK_ECN frame is transmitted back. This ACK_ECN frame indicates how many packets that are marked ECT(0), ECT(1) or ECN-CE. Thus the endpoint can determine if the endpoints and path is ECN capable. -The ACK_ECN frame will, when received, confirm that the path direction supports -ECN if the counters show a correct amount of packets received for a valid and -expected counter combination. ECT marked packets can become remarked as CE along -the path between the peers. The ACK_ECN counters are added together and compared -to total number of ACKed packets, if the sum of the counters are equal too or -larger than the number of ACKed packets then the path is ECN capable. This -capability check thus has verified that one direction of the path between the -peers is free from issues with ECN bleaching and that the application does not -experience problems with access to the ECN field in the IP header. In this case -the marking of the generated packets with ECT continues. +When ACK_ECN is received, the counter values can be used to confirm the expected +number of marks were received. ECT marked packets can become remarked as CE +along the path between the peers. The ACK_ECN counters are added together and +compared to total number of ACKed packets, if the sum of the counters are equal +too or larger than the number of ACKed packets then the path is ECN capable. too -> to, or just remove the too entirely -- 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/1372#pullrequestreview-127977693 ----==_mimepart_5b1fd34640eed_17943f8980438f8421448 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

Some small comments, but I think this looks good

In draft-ietf-quic-recovery.md:

>  (ECN-CE) SHOULD be acknowledged immediately to quicker react to
-congesiton events. Additional ECN-CE marks received during the same
+congestion events. Additional ECN-CE marks received during the same

I don't think you need to say "during the same recovery period" since we're not proscribing any receiver side behavior corresponding to whether the marks are received within the same recovery period.

In draft-ietf-quic-recovery.md:

> @@ -904,9 +904,9 @@ experimentation in using other response functions as discussed in
 
 The ACK_ECN frame defined in {{QUIC-TRANSPORT}} does not provide
 information on which of the newly acknowledged packets that

nit: remove "that"

In draft-ietf-quic-recovery.md:

>  
 ~~~
-   OnPacketsMarked(ce_counter):
-     if (ce_counter > ack_ce_cntr):
-       // update ack_ce_cntr
-       ack_ce_cntr = ce_counter
-     if (!InRecovery(largest_acked_packet)):
+   CongestionEvent(packet_number):

I'd prefer OnCongestionEvent to be consistent with the other names.

In draft-ietf-quic-transport.md:

> @@ -1442,16 +1441,15 @@ endpoint, an ACK_ECN frame is transmitted back. This ACK_ECN frame indicates how
 many packets that are marked ECT(0), ECT(1) or ECN-CE. Thus the endpoint can
 determine if the endpoints and path is ECN capable.
 
-The ACK_ECN frame will, when received, confirm that the path direction supports
-ECN if the counters show a correct amount of packets received for a valid and
-expected counter combination. ECT marked packets can become remarked as CE along
-the path between the peers. The ACK_ECN counters are added together and compared
-to total number of ACKed packets, if the sum of the counters are equal too or
-larger than the number of ACKed packets then the path is ECN capable. This
-capability check thus has verified that one direction of the path between the
-peers is free from issues with ECN bleaching and that the application does not
-experience problems with access to the ECN field in the IP header. In this case
-the marking of the generated packets with ECT continues.
+When ACK_ECN is received, the counter values can be used to confirm the expected
+number of marks were received. ECT marked packets can become remarked as CE
+along the path between the peers. The ACK_ECN counters are added together and
+compared to total number of ACKed packets, if the sum of the counters are equal
+too or larger than the number of ACKed packets then the path is ECN capable.

too -> to, or just remove the too entirely

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

----==_mimepart_5b1fd34640eed_17943f8980438f8421448-- From nobody Tue Jun 12 07:14:22 2018 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 21451130E51 for ; Tue, 12 Jun 2018 07:14:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 29pVM2shXxS9 for ; Tue, 12 Jun 2018 07:14:16 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A73D130E3D for ; Tue, 12 Jun 2018 07:14:16 -0700 (PDT) Date: Tue, 12 Jun 2018 07:14:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528812855; bh=b2/lW33vLwgLeaEiLWkGPjEx3EgMSu8N0uDHE6Rq7Dc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p+bHs9OICLNbctEFVBwvSwX7rxDRIZj4UNQ7mIZxKux8xYkdiLIBPXheAH69wRgTI ZSjHtqancG7VRJpilLlz7n5qOArEYH/TKlE+PUxdF64tDv2+AtPvFugOuIaV/u7KWb VdGRL7PfR/8EbGsKcVix4XdM8epawGN3DdR9fuVE= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fd537bbc35_32dc3fd063a3ef801690ec"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 12 Jun 2018 14:14:20 -0000 ----==_mimepart_5b1fd537bbc35_32dc3fd063a3ef801690ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Half-baked idea: can we send Bloom filters instead of counts? Not likely, they are not very precise and take up a lot of space, though there are compressed forms. There are various compressed bitmap forms mixing runlength encoding. One consideration could be to send small bitmaps of 8 to 64-bits mixed with RLE. That is largely how I keep track of duplicates internally. -- 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/1439#issuecomment-396604773 ----==_mimepart_5b1fd537bbc35_32dc3fd063a3ef801690ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Half-baked idea: can we send Bloom filters instead of counts?

Not likely, they are not very precise and take up a lot of space, thou= gh there are compressed forms.

There are various compressed bitmap forms mixing runlength encoding. O= ne consideration could be to send small bitmaps of 8 to 64-bits mixed wit= h RLE. That is largely how I keep track of duplicates internally.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b1fd537bbc35_32dc3fd063a3ef801690ec-- From nobody Tue Jun 12 07:42:13 2018 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 57519130F7E for ; Tue, 12 Jun 2018 07:42:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 tUlLeaV4OK1U for ; Tue, 12 Jun 2018 07:42:04 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 DD4DC130F7B for ; Tue, 12 Jun 2018 07:42:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528814523; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=0kafFk/8t4egNlmWnwJpMhbCzL3fgq6WrzEHojgHF4s=; b=M5PptlaN81zhc+6biAda4OGAfpiNZ7xW30n9LuPRGqbtG8v3611v9qoaAlkq2PCx6pwJFE9/ YF2vduQuQ2hG27ZCsVBXDpZQcdsRwmEDENkUAJRJfl+hJfDiKj4pFYSCrCWL3o04kTemLPKc kWwphKQ7WxXL5WkLVOqB0ob/vBQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lars=eggert.org@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b1fdbba.7f4aa0d87810-smtp-out-n03; Tue, 12 Jun 2018 14:42:02 -0000 (UTC) Date: Tue, 12 Jun 2018 07:42:02 -0700 From: Lars Eggert Reply-To: Lars Eggert To: quic-issues@ietf.org Message-ID: <5b1fdbbabe238_52de2ad25589dbfc35129@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] cec91e: Updates to NYC arrangements Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b1fdbbabdee3_52de2ad25589dbfc35041"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 14:42:10 -0000 ----==_mimepart_5b1fdbbabdee3_52de2ad25589dbfc35041 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: cec91e61b125da86cee6d0195c4178104ef143cb https://github.com/quicwg/wg-materials/commit/cec91e61b125da86cee6d0195c4178104ef143cb Author: Lars Eggert Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M interim-18-09/arrangements.md Log Message: ----------- Updates to NYC arrangements **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b1fdbbabdee3_52de2ad25589dbfc35041-- From nobody Tue Jun 12 07:44:15 2018 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 12029130F3E for ; Tue, 12 Jun 2018 07:44:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EGKCj2reIf-B for ; Tue, 12 Jun 2018 07:44:10 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 87EF3130E46 for ; Tue, 12 Jun 2018 07:44:09 -0700 (PDT) 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=Sa3sj6hKbuJ5dypr93TyChBzv8s=; b=q3i4x3Hk83hPJs5I l/oFDT8EHaI5jDB9FwhfjLZCuRR3AujM8lP0OkozS8sWhJAr3jvO0oB4Y6RRua84 Al60t7UFui2GmniNNLHNzwEhW2VZyX9p8XKrDLkXVtfBk/EViS+L6Q8zO60gXaqB E+qIj06oxzqaRSAzwO1PEHxvYTk= Received: by filter1842p1mdw1.sendgrid.net with SMTP id filter1842p1mdw1-22252-5B1FDC37-68 2018-06-12 14:44:07.997554876 +0000 UTC Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id TUSqpH-KSDSrGA4jnntsKA for ; Tue, 12 Jun 2018 14:44:07.949 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id E55DAA80526 for ; Tue, 12 Jun 2018 07:44:07 -0700 (PDT) Date: Tue, 12 Jun 2018 14:44:08 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fdc37e3660_3dfc2ab3ec276f582542ab"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3gUIs6m75LdIrWo3mDgUvaHSRNN5o9P2+ZZI L4RqTOEAsUeZMFNaEhgkP+cidzT/Cs/1w9xSeSapTlfXuNSJNumj+7kRm2eCT2RoqclvO74jMrl5t8 Qonyb4mtKDCp9R5we/qmjrDNNXgtXtRpf/MulAQXvFx37cYPlx9rYxlirj1ExZWBvhvEjhS+YicXxr I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 14:44:14 -0000 ----==_mimepart_5b1fdc37e3660_3dfc2ab3ec276f582542ab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If the concern is too many bits in the frame for high throughput scenarios, the bitmask could be capped at 64. In those high throughput cases, you should have enough ACKs to reassemble the markings, it's just that you wouldn't have a whole lot of redundancy for the marking signal. That bounds the size of the frame. -- 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/1439#issuecomment-396615367 ----==_mimepart_5b1fdc37e3660_3dfc2ab3ec276f582542ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If the concern is too many bits in the frame for high throughput scenari= os, the bitmask could be capped at 64. In those high throughput cases, you= should have enough ACKs to reassemble the markings, it's just that you wou= ldn't have a whole lot of redundancy for the marking signal. That bounds t= he size of the frame.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b1fdc37e3660_3dfc2ab3ec276f582542ab-- From nobody Tue Jun 12 08:44:01 2018 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 BAD28130E62 for ; Tue, 12 Jun 2018 08:43:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gVkD50Z6UYbv for ; Tue, 12 Jun 2018 08:43:55 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAA62130E61 for ; Tue, 12 Jun 2018 08:43:55 -0700 (PDT) Date: Tue, 12 Jun 2018 08:43:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528818234; bh=xTMvGZLHWvQHm7dBbwEL6Zn3zelUrWlSFee5QH11jNY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=by6hWaerUGwAJFICg020wEL1ucNsCXhZ5QvG+o9osq0R9sUx6DUqD8l71Zc9eezWN /SopjPupVGclY/9S8PwzommY7ODFwmo4fjmCNY8uKAxa42UIHx/YrRzgts/vq1Nae/ WwxVQCDanz0Su+IFC1P1NMQsRDfnA6hRAsQT0URI= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1fea3aaadbc_3b8c2ab19a354f50104466"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 15:43:58 -0000 ----==_mimepart_5b1fea3aaadbc_3b8c2ab19a354f50104466 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. bf30190 Clarifying that both cases are capability checks. Correcting a number of editorial things. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/ec97fd81158d29261e3ea4bb6e80a64efc0aa7a2..bf30190128543f0349d8d0b8391b1213c7ebeb3f ----==_mimepart_5b1fea3aaadbc_3b8c2ab19a354f50104466 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • bf30190 Clarifying that both cases are capability checks. Correcting a number of editorial things.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1fea3aaadbc_3b8c2ab19a354f50104466-- From nobody Tue Jun 12 08:58:46 2018 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 0C300130FA0 for ; Tue, 12 Jun 2018 08:58:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oJ9Ihq2WSTuF for ; Tue, 12 Jun 2018 08:58:30 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 E1FB4130E89 for ; Tue, 12 Jun 2018 08:58:29 -0700 (PDT) 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=he2Oh2hHFtXXSbPZeIbKLhf66Pw=; b=UYNC3IWfYIt2P/5T 33AQHmkl6Spi8GUhI/YBWbPBZx6s+EP71GcvEiy9XeyyoQvYUQN7adEGF4iA+AdB Ncr/H3v30JkcQMtl3pig/hIQ8weJCraWjtK8gIHukH2js67AuY35l60ODstXF2ht aSjQ7w/0u+cRCstKa6+xLTJ2M/o= Received: by filter0701p1las1.sendgrid.net with SMTP id filter0701p1las1-19254-5B1FEDA4-19 2018-06-12 15:58:28.469508163 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 3HwQTTkrS9mnFEY5noEUnw for ; Tue, 12 Jun 2018 15:58:28.414 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id 636A580094 for ; Tue, 12 Jun 2018 08:58:28 -0700 (PDT) Date: Tue, 12 Jun 2018 15:58:28 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b1feda461f46_698d2ab675150f5858896"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak23Q2QH6dS1Kd/mSytnRXJVCzNsRXLQCaRZaq 9Upth4OPUvTb5qzHpw3hbigCpo3qy2BjgB3ZCHXEKwUARcIBFv4a1rGpFZ9WO7hXQ3T1m1htmfFwBj d+7bmJWHF6kcLn7fPLF5I3XMk3rEm/jV8lFOCVmbVjlzKaJzAX+zjSfGxPhgBm462I3nzVk45Smzj+ U= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 15:58:43 -0000 ----==_mimepart_5b1feda461f46_698d2ab675150f5858896 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 60468a7 Fixed a too too much -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/bf30190128543f0349d8d0b8391b1213c7ebeb3f..60468a79507a1d36a07825b80222da03773e571b ----==_mimepart_5b1feda461f46_698d2ab675150f5858896 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b1feda461f46_698d2ab675150f5858896-- From nobody Tue Jun 12 10:36:48 2018 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 269B0130F86 for ; Tue, 12 Jun 2018 10:36:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zEVyDm_miiU1 for ; Tue, 12 Jun 2018 10:36:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8B41130F79 for ; Tue, 12 Jun 2018 10:36:42 -0700 (PDT) Date: Tue, 12 Jun 2018 10:36:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528825001; bh=MaoKbdVZWigIRqDVW7dTU04u/1DGMGQtLnG+O8pwC9g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qHqgZwSxmCOnA1LFcA21AdW4Q82OVv66OtWuWko+vIPpO+AZwnZOSdOMDQuY9r4Cl 6FMsTYMuI3NRedfGic4YTcm1KKvoE/6oX+Ox22XVOYpI5s7ySOBkBvQHclVI2zdyvw Y5Z8LpQLEQgOGPd+R6ls9+GrR5s7GqAIHPTxFkCw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2004a98677d_44f2b0ea1f4ef54248439"; 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.26 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: Tue, 12 Jun 2018 17:36:46 -0000 ----==_mimepart_5b2004a98677d_44f2b0ea1f4ef54248439 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > Every QUIC packet that is coalesced into a single UDP datagram is separate and complete. Though the values of some fields in the packet header might be redundant, no fields are omitted. The receiver of coalesced QUIC packets MUST individually process each QUIC packet and separately acknowledge them, as if -they were received as the payload of different UDP datagrams. +they were received as the payload of different UDP datagrams. If one or more +packets in a datagram cannot be processed, either because the keys are not yet +available or because decryption fails, the receiver MUST still attempt to I was initially dubious about this, thinking that the Length field is type-specific. But it appears to only be version-specific, which means you can still trust the Length on an unknown type. Done, though the wording feels a little awkward; suggestions for improved flow welcome. -- 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/1423#discussion_r194827321 ----==_mimepart_5b2004a98677d_44f2b0ea1f4ef54248439 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

>  
 Every QUIC packet that is coalesced into a single UDP datagram is separate and
 complete.  Though the values of some fields in the packet header might be
 redundant, no fields are omitted.  The receiver of coalesced QUIC packets MUST
 individually process each QUIC packet and separately acknowledge them, as if
-they were received as the payload of different UDP datagrams.
+they were received as the payload of different UDP datagrams.  If one or more
+packets in a datagram cannot be processed, either because the keys are not yet
+available or because decryption fails, the receiver MUST still attempt to

I was initially dubious about this, thinking that the Length field is type-specific. But it appears to only be version-specific, which means you can still trust the Length on an unknown type.

Done, though the wording feels a little awkward; suggestions for improved flow welcome.

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

----==_mimepart_5b2004a98677d_44f2b0ea1f4ef54248439-- From nobody Tue Jun 12 10:37:11 2018 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 6BC24130F86 for ; Tue, 12 Jun 2018 10:37:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 t2VO_UiepYf3 for ; Tue, 12 Jun 2018 10:37:06 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 2964C130F83 for ; Tue, 12 Jun 2018 10:37:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528825025; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=8ujOMAv8mkC1tVJHycUsxFVKRLMxO4T+9jC6WRxj2lk=; b=NYuYg47LTPp4ccGmSqe3ln3rrDrAjoHc7ddrkQtUskVhvSQ5uR4DLYK3D4ltShxboJ33WtaD G4bKD5N14RcHjodecJ9x8cLeCjuW3anSsulj7LokdOCeRToDX/rP/qDGkSEvZw4h9BTXdgIa j3tNwWH3LFEV4Bflqmxg7n4V3+g= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b2004c0.7f7e0a395e70-smtp-out-n03; Tue, 12 Jun 2018 17:37:04 -0000 (UTC) Date: Tue, 12 Jun 2018 10:37:04 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2004c04fe0_d752b08ebed3c0c59799@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 3f3da7: Kazuho's suggestion Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2004c04c67_d752b08ebed3c0c596a2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 17:37:09 -0000 ----==_mimepart_5b2004c04c67_d752b08ebed3c0c596a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts Commit: 3f3da757b33e58fd112cb69f8d3f7d396a298f39 https://github.com/quicwg/base-drafts/commit/3f3da757b33e58fd112cb69f8d3f7d396a298f39 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Kazuho's suggestion **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2004c04c67_d752b08ebed3c0c596a2-- From nobody Tue Jun 12 10:37:20 2018 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 49504130F94 for ; Tue, 12 Jun 2018 10:37:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zzBMAzDAJBMz for ; Tue, 12 Jun 2018 10:37:09 -0700 (PDT) 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 DC939130F83 for ; Tue, 12 Jun 2018 10:37:08 -0700 (PDT) Date: Tue, 12 Jun 2018 10:37:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528825027; bh=0nZuPL50HYOOUtXXjBQ08CCx5VpHt6uVO50Hg7HWpbg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ijmb60DPZ81SF7SZ3AN+eTloc8q+W0sspxl5BQFx3yh7x4L4zGEVHqzB7A/lQxQVp Qk/RAWge4ACG99invPHoSp0QKiXSpgNI61kIj3kVIHBMVTl0MnExVnPEdmsqqtWzGS 2MPbtNbgdbV1ipPEky+agd91bf9qSB7KPzpkWv24= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2004c3e440c_1ad33f8bee3bcf7c26962d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 17:37:14 -0000 ----==_mimepart_5b2004c3e440c_1ad33f8bee3bcf7c26962d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 3f3da75 Kazuho's suggestion -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1423/files/26c5b742d37f6adbf84fecec5e0abf0d29563484..3f3da757b33e58fd112cb69f8d3f7d396a298f39 ----==_mimepart_5b2004c3e440c_1ad33f8bee3bcf7c26962d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2004c3e440c_1ad33f8bee3bcf7c26962d-- From nobody Tue Jun 12 10:53:00 2018 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 DDB4A130F9C for ; Tue, 12 Jun 2018 10:52:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 B2iB6Y7iFzxd for ; Tue, 12 Jun 2018 10:52:53 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABB33130FB5 for ; Tue, 12 Jun 2018 10:51:49 -0700 (PDT) Date: Tue, 12 Jun 2018 10:51:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528825908; bh=m+B8+8vEs3UecYBrAXOnR+exTNO5CBoLEgUF/vhiB2I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oQPHNMbvRz/Rb9Frv50uFLHQpyL094/x73UbEbzpXt5/9jvCJiTe3Uhs0vClkjV+A kGMs1wzH5uCw1Om+buI3uyUqvZyH3wLggcKSzMFflPWyb4pLs7aY3Q//KkGOCO8+ro 33pNj4fCQHr5tdxd2Yns9qWzRGXyjZizVZqzSsaU= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b200834ed35b_ce42ab7b3beef5c780e8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 17:52:58 -0000 ----==_mimepart_5b200834ed35b_ce42ab7b3beef5c780e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. -- 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/1372#pullrequestreview-128078553 ----==_mimepart_5b200834ed35b_ce42ab7b3beef5c780e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

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

----==_mimepart_5b200834ed35b_ce42ab7b3beef5c780e8-- From nobody Tue Jun 12 11:15:40 2018 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 C9A07130FA2 for ; Tue, 12 Jun 2018 11:15:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 RZtQStixPoRm for ; Tue, 12 Jun 2018 11:15:35 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 9DB58130E7B for ; Tue, 12 Jun 2018 11:15:35 -0700 (PDT) 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=mnqFg7KPfTzacQ4s400EWPu7NZQ=; b=RpRhh6nHDG4PY4zi kuFG8JRyvrSvwwpbfP0pIB8r2hAU5Rfs0zp/qqp62U8jh8dwac+KXhqND02mv9+w +YzQdXWtWWmqep96Q7izfaKV06F90gG6/8KLyZ6G3JGFVc4+nBDOb+z2m52wpcj3 1tQayVtdyTEMss3wG0QwXW3//Gk= Received: by filter0826p1las1.sendgrid.net with SMTP id filter0826p1las1-12651-5B200DC5-15 2018-06-12 18:15:33.465409865 +0000 UTC Received: from github-lowworker9-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id jWP7N6sKRRaeSKwnL9k0Uw for ; Tue, 12 Jun 2018 18:15:33.434 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker9-cp1-prd.iad.github.net (Postfix) with ESMTP id 6848DA0265 for ; Tue, 12 Jun 2018 11:15:33 -0700 (PDT) Date: Tue, 12 Jun 2018 18:15:33 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b200dc5667bd_79093fb6837d0f7c21178f"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ARmRCLoTfw52YbL9xARAKgbrrRv2VNfbKlu EcEptjF8+qV+kNEyrgTb7Zd8Qtm3+HxiRxaBjTgpd41NgQbtN/X9/0gC4siD+QU9pafZmhZmYL4/UO SBpqvOlYVMISQPvfjglxV0iTPAK+CHZBomaHLZh9sex+8GFO6v/Ul8BQ/PLlvJD+w0gJCq1s1eyrK2 k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 18:15:38 -0000 ----==_mimepart_5b200dc5667bd_79093fb6837d0f7c21178f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson, I'm curious about the source of the performance hit. Was it simply from using a non-byte-aligned varint? If so, that seems separate from this. -- 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/1431#issuecomment-396684983 ----==_mimepart_5b200dc5667bd_79093fb6837d0f7c21178f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson, I'm curious about the source of the performance hit. Was it simply from using a non-byte-aligned varint? If so, that seems separate from this.

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

----==_mimepart_5b200dc5667bd_79093fb6837d0f7c21178f-- From nobody Tue Jun 12 11:20:43 2018 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 912B3130E7B for ; Tue, 12 Jun 2018 11:20:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 fJKPSOxg75of for ; Tue, 12 Jun 2018 11:20:33 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 7FC8C130FA2 for ; Tue, 12 Jun 2018 11:20:33 -0700 (PDT) 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=izRG3sRbwwCsWaAViMQUeFi6wyA=; b=oLvo8ooFaWZoPqgf pmnVsSVbng6aAblkoCEQfQMmjAcu2l+5auCH4oZOSgMrJmc0CR0Ms5UgUc4oa9+F aclQ0I5amoh5rYvqfUexcFClaU91hT0PTyGaUxCdZZdyM7UnMDyuK77fUXYePd6T mcxjzIQTjhjZx2GKR+TwU/djLc8= Received: by filter1479p1mdw1.sendgrid.net with SMTP id filter1479p1mdw1-31187-5B200EF0-8 2018-06-12 18:20:32.178595683 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id PF5SliQLTNucGa02ZCELrw for ; Tue, 12 Jun 2018 18:20:32.098 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id 1657244B05 for ; Tue, 12 Jun 2018 11:20:32 -0700 (PDT) Date: Tue, 12 Jun 2018 18:20:32 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b200ef014c8c_dbb3f9153fa0f7c267362"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2AOCNq0BVzuWm1HgWkRjI1Jx8zeJjMNSkKyZ ZCVPIsbR7McZCO9XCwEb/lqCa4oJIel2eTlSOCMamruMg23uh/WFTRIuDLhlbbco2x/bQXNeWoYlUs upwwwxOxlK/CCor0CUxtQZGxWeQ4SQzExiOtKiXn2W6tVCvw1d8KnuEivtztU0qqBeiqsx6Nq/iOHi c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 18:20:39 -0000 ----==_mimepart_5b200ef014c8c_dbb3f9153fa0f7c267362 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm wondering whether we could alternatively fix this in text only. If we say that the stream type is indicated by the two low bits of the field, and the Stream ID within the type is indicated by the remaining upper bits of the number, then you get to the same place (indicating streams as 1us, 3bc, etc.) without modifying the bits on the wire. That's basically just codifying a change in presentation / reference terminology. It doesn't get the same small byte savings as #1431, because you're not effectively expanding the varint by two bits, but those savings are modest anyway. -- 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/1430#issuecomment-396686466 ----==_mimepart_5b200ef014c8c_dbb3f9153fa0f7c267362 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm wondering whether we could alternatively fix this in text only. If = we say that the stream type is indicated by the two low bits of the field, = and the Stream ID within the type is indicated by the remaining upper bits = of the number, then you get to the same place (indicating streams as 1us, 3= bc, etc.) without modifying the bits on the wire. That's basically just co= difying a change in presentation / reference terminology.

It doesn't get the same small byte savings as #1431, because you're not effectively expanding= the varint by two bits, but those savings are modest anyway.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b200ef014c8c_dbb3f9153fa0f7c267362-- From nobody Tue Jun 12 11:30:28 2018 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 96831130FAB for ; Tue, 12 Jun 2018 11:30:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 6pPj0KgIHQH7 for ; Tue, 12 Jun 2018 11:30:23 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 ED11D130E7B for ; Tue, 12 Jun 2018 11:30:22 -0700 (PDT) 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=6awAAom9WXzu6e0meHrGGbi4iAY=; b=HZYAURjk5wSjwSQi QawHtHGgI0A86lJ75nzhyufx9mgoCICRSC4u6I95XXG09FJSPGh++TkjFyTcFL8u KeTZ7JWrMNEehefqgR/UH1X2zhDCC5hr94Zg0VPqMNGJcCeCriIvRtkPBF9Sxo1q sRmuERUXfICvL1VDwhFTtWPzzEY= Received: by filter0720p1las1.sendgrid.net with SMTP id filter0720p1las1-3697-5B20113D-22 2018-06-12 18:30:21.759880382 +0000 UTC Received: from github-lowworker13-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id 3YIV8C9lTJKvoXeO5_l5jg for ; Tue, 12 Jun 2018 18:30:21.681 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker13-cp1-prd.iad.github.net (Postfix) with ESMTP id A521622373 for ; Tue, 12 Jun 2018 11:30:21 -0700 (PDT) Date: Tue, 12 Jun 2018 18:30:22 +0000 (UTC) From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20113da2e32_5fe63fbcd856af841084e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak03FFQNVkNnwBKFBIeyAq1EaYuwEiEukdVhui kivlr2cn5lgR4OAbwfjounfEFLZTylH1/1ggdij6CRpukes8ubCXUIqVwCfK5LJGnIrtbgcbZZlnVw pz8mPCUj8JboyzM5w9BbTx1dKOofjVAknt3VZ3oevNMkm4LD3LlL/MLVFA== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 18:30:26 -0000 ----==_mimepart_5b20113da2e32_5fe63fbcd856af841084e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's beneficial to have the stream type detectable in the frame type because it is then possible to dispatch to separate handler logic before reading the frame and that logic then doesn't have to do special bit magic and branch on what it discovers. OTOH separate handlers can easily call shared support functions for streams. -- 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/1430#issuecomment-396689436 ----==_mimepart_5b20113da2e32_5fe63fbcd856af841084e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's beneficial to have the stream type detectable in the frame type bec= ause it is then possible to dispatch to separate handler logic before readi= ng the frame and that logic then doesn't have to do special bit magic and b= ranch on what it discovers. OTOH separate handlers can easily call shared s= upport functions for streams.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b20113da2e32_5fe63fbcd856af841084e2-- From nobody Tue Jun 12 11:43:30 2018 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 97090130E91 for ; Tue, 12 Jun 2018 11:43:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 uOPZ-YSfeqW1 for ; Tue, 12 Jun 2018 11:43:26 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 AEC37130E77 for ; Tue, 12 Jun 2018 11:43:26 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528829006; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=tJPTHu/tKpVHbtDukyaReDQS3Oq30eUKzdXDBO7n7Jc=; b=TgV6Jcgo43MZ/5AjORl+IrLGy27rv8ljnVRW+vCcXkH5+dHscjSrHb+4Cw2Ts8vBbXIwFjwC s3uxD2bXOYM7fgRS5U7KSbRxZQF595yQog9OohkSI2iaKbw8Neg7/3JtdnTqW2UMc2lDufkb tshx4T14aEAuE/QbFnIGKnzABqc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b20144d.7fc6b7f33330-smtp-out-n01; Tue, 12 Jun 2018 18:43:25 -0000 (UTC) Date: Tue, 12 Jun 2018 11:43:24 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b20144c381fd_29172abda5a3fc18519d7@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] a15bf2: Alan's feedback Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b20144c37e73_29172abda5a3fc1851897"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 18:43:29 -0000 ----==_mimepart_5b20144c37e73_29172abda5a3fc1851897 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: a15bf2576ca8db80c00896e4b2b2c1c13adee342 https://github.com/quicwg/base-drafts/commit/a15bf2576ca8db80c00896e4b2b2c1c13adee342 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Alan's feedback **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b20144c37e73_29172abda5a3fc1851897-- From nobody Tue Jun 12 11:43:44 2018 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 7D430130E91 for ; Tue, 12 Jun 2018 11:43:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HIheWYn4Bof9 for ; Tue, 12 Jun 2018 11:43:38 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E248E130E77 for ; Tue, 12 Jun 2018 11:43:38 -0700 (PDT) Date: Tue, 12 Jun 2018 11:43:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528829017; bh=wgOV/i1+4sINYcCcNH2PRA36LhQOLrdGJ4jBslEeBjw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QA9p/60QEaIZGfK3WjX0tVlTFo60Zmt4bvc+mBksKat2ZzDaM0CowHYh01V0dAkpZ FPxnNU3irSUTF53yi7wU8DXq1A/oBe9Q4P/90yCYo0BHw67IhVA6axPLzOwqexUUlH XOE5LZTC0TFpCLwxHxh4gepX2SHEv2mECsfwh798= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b201459235b0_13fb3f835611ef7c50154"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 18:43:41 -0000 ----==_mimepart_5b201459235b0_13fb3f835611ef7c50154 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. a15bf25 Alan's feedback -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1410/files/d6cb886ad0f38d60440827a92175cbd9812777c5..a15bf2576ca8db80c00896e4b2b2c1c13adee342 ----==_mimepart_5b201459235b0_13fb3f835611ef7c50154 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b201459235b0_13fb3f835611ef7c50154-- From nobody Tue Jun 12 14:55:35 2018 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 984E6130EC1 for ; Tue, 12 Jun 2018 14:55:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 GM_IUriyWCeN for ; Tue, 12 Jun 2018 14:55:31 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 B8EC7130ED0 for ; Tue, 12 Jun 2018 14:55:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528840528; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nw+468BPKwRY8LGoxSgoZeqAPq10RxmWoNG4ixkI1qQ=; b=K5XePQdUstArLdLakiVZUNxPqfskzF2ExqJ+Y0fwGFKj6qSL8WnntCuAU2QLhGPltXbQJI6Y jk9ANiqD0EPidAByewU0cjJfbeNyAgk5Lh3Hav829NwgjZYTWKa6E/StzlV8BhlBytmctJJw yrCwE4mqfNBlMmdCu+bZznUi/lk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b20414f.7f5720e3abd0-smtp-out-n01; Tue, 12 Jun 2018 21:55:27 -0000 (UTC) Date: Tue, 12 Jun 2018 14:55:27 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b20414f4ab92_729e2af2e1cddbfc97163@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 411966: Statement of idempotency Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b20414f4a267_729e2af2e1cddbfc9703b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 21:55:33 -0000 ----==_mimepart_5b20414f4a267_729e2af2e1cddbfc9703b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/frame_idempotency Home: https://github.com/quicwg/base-drafts Commit: 411966117c5b2a7d235273dda5a587c341bb5376 https://github.com/quicwg/base-drafts/commit/411966117c5b2a7d235273dda5a587c341bb5376 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Statement of idempotency **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b20414f4a267_729e2af2e1cddbfc9703b-- From nobody Tue Jun 12 14:59:06 2018 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 939B1130FAC for ; Tue, 12 Jun 2018 14:59:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 OISPpN2s9eL4 for ; Tue, 12 Jun 2018 14:59:01 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0A49130FC1 for ; Tue, 12 Jun 2018 14:59:01 -0700 (PDT) Date: Tue, 12 Jun 2018 14:59:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528840740; bh=YsCkcFokr/LdMzZcACpPjADyDlPHcFJY430F2a8XnSM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=mOfjg7pUr3Ia1/rJydq3V1ES0NCj9q5cNqWYD96tci3SUU548PrSZMyltNM6dC/nn otjqsH3aq7KF/qiSfRO9GOuhwC7wS7rq0a06Dw81EkMtM0VUexegTr4TVl+wIyr3Gm VjtehMlUgyhrDypyk+0FIJ7muGAIgZCOTQ9O7PoE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204224b67d7_763c2af82b2c0f5834689"; 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.26 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: Tue, 12 Jun 2018 21:59:05 -0000 ----==_mimepart_5b204224b67d7_763c2af82b2c0f5834689 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1424. Marked as editorial, since this is just a statement of what is already true about all frames anyway. However, it's implicit that this should also be true of frames defined in the future or in extensions, so it's a bit broader than the usual editorial change. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1441 -- Commit Summary -- * Statement of idempotency -- File Changes -- M draft-ietf-quic-transport.md (5) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1441.patch https://github.com/quicwg/base-drafts/pull/1441.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/1441 ----==_mimepart_5b204224b67d7_763c2af82b2c0f5834689 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1424.

Marked as editorial, since this is just a statement of what is already true about all frames anyway. However, it's implicit that this should also be true of frames defined in the future or in extensions, so it's a bit broader than the usual editorial change.

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

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

Commit Summary

  • Statement of idempotency

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 mute the thread.

----==_mimepart_5b204224b67d7_763c2af82b2c0f5834689-- From nobody Tue Jun 12 15:05:37 2018 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 E9690130FD1 for ; Tue, 12 Jun 2018 15:05:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ZVqo_i8Zjzw8 for ; Tue, 12 Jun 2018 15:05:32 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6EFF130FC4 for ; Tue, 12 Jun 2018 15:05:31 -0700 (PDT) Date: Tue, 12 Jun 2018 15:05:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841131; bh=ab4y4jggb4l+vOjyRio9KFsvN2wxkiN0zP9GtYdM5a0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RT6ALPp5w11pwjHi3qdaf8SL+bH4c+eCnl0XsJYfozJ+C7gJC4CsNsbPoD51EFEmS h76ikHRdHLI0C0E9Y1+xRNBFi4+9XsvNa7Hvert8zFlgRDqv3pavo7zd/eVEg+LBX3 HLIeIuMsizA080rJnGQS4LeBRgCaF2Dv+wcZRVuM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2043ab2b6de_34332acafbf1cf5c8002fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 12 Jun 2018 22:05:34 -0000 ----==_mimepart_5b2043ab2b6de_34332acafbf1cf5c8002fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, +and a frame can be received and processed without error at any point between the Not all frames are processed without errors, so this is a bit awkward -- 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/1441#pullrequestreview-128166406 ----==_mimepart_5b2043ab2b6de_34332acafbf1cf5c8002fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,
+and a frame can be received and processed without error at any point between the

Not all frames are processed without errors, so this is a bit awkward

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

----==_mimepart_5b2043ab2b6de_34332acafbf1cf5c8002fa-- From nobody Tue Jun 12 15:09:12 2018 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 58A81130FC4 for ; Tue, 12 Jun 2018 15:09:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 VqEaTZLDWWnH for ; Tue, 12 Jun 2018 15:09:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4F5130EE8 for ; Tue, 12 Jun 2018 15:09:06 -0700 (PDT) Date: Tue, 12 Jun 2018 15:09:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841345; bh=U38p8jdTLU6T0IZb6p6yhqSUnGz6G94MGd8m+hYPioI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KBgoyc0Ca1lCScd3sJeMT21XQUEQwhxjH3+i0Bd6djIXpS5RieNM2Is5VtHAS8z5p D/TdvLv9MKj/F5z+9mmCn+WgMJZG1fUJLGVbjpbK0S3Z/U1z/R8r6Udebz7PAnSdP7 LdvmOdMgJGPSOd7tqVIPvLFyvu3wLYjOnCFUx4Nc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204481d7715_77883f8d528bcf80114791c"; 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.26 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: Tue, 12 Jun 2018 22:09:10 -0000 ----==_mimepart_5b204481d7715_77883f8d528bcf80114791c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, +and a frame can be received and processed without error at any point between the Perhaps that it never produces an error on a subsequent processing that it didn't produce the first time? -- 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/1441#discussion_r194903957 ----==_mimepart_5b204481d7715_77883f8d528bcf80114791c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,
+and a frame can be received and processed without error at any point between the

Perhaps that it never produces an error on a subsequent processing that it didn't produce the first time?

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

----==_mimepart_5b204481d7715_77883f8d528bcf80114791c-- From nobody Tue Jun 12 15:12:22 2018 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 97CE7130FC4 for ; Tue, 12 Jun 2018 15:12:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vNMzTUUrUIgf for ; Tue, 12 Jun 2018 15:12:17 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA552130EE8 for ; Tue, 12 Jun 2018 15:12:16 -0700 (PDT) Date: Tue, 12 Jun 2018 15:12:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841536; bh=T2d/VGG241Ao3Qruz1cXMNRbJnUXwpKwG9c1+jd8mdw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iilpce70SrIQ3wQXqEBCJEWSI1sBUCHGTcxCMytp1qCdmBe9L/7pfuWasChwNd2Ly uypKHXF9NJTwaoL5mhTck6qu9JXUIJeyTWc8CSsN/2Y6bwOpLMee2ADmLA2ZqVvn6Q j+mPrTm6gAO1f2qRS/R7gC3vWYHjV1XAMSVKzAYs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204540495d6_4a322ad538f9af5058310"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:12:20 -0000 ----==_mimepart_5b204540495d6_4a322ad538f9af5058310 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, How about: A valid frame does not change the state of the connection as a result of being received more than once. -- 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/1441#pullrequestreview-128168050 ----==_mimepart_5b204540495d6_4a322ad538f9af5058310 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

How about: A valid frame does not change the state of the connection as a result of being received more than once.

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

----==_mimepart_5b204540495d6_4a322ad538f9af5058310-- From nobody Tue Jun 12 15:13:42 2018 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 1BF95130FDF for ; Tue, 12 Jun 2018 15:13:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 c5uoOvA3PlGc for ; Tue, 12 Jun 2018 15:13:33 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 41711130EE8 for ; Tue, 12 Jun 2018 15:13:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528841612; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=lJgDtmDYBVaE3g8uZfddErT1m6ZSFMy8y8T096KVkUU=; b=S0mfS2ggzdyrX3wND0LKzaFkewi6Zq1NXgW9/Kn23rlrbDO6aTZF5ycdSdD43DFN1ut+Dd6r 5dXDXw+ftibHCn2D3twlYeLmGCV3GplD7nVpP2YIIEFrAmClZvz7BWEx3MkFiEGgFMZtd7/c vd8UusDnZ4Na9+vQ1oNvdxcViKc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b20458b.7f7c4e9a3a20-smtp-out-n02; Tue, 12 Jun 2018 22:13:31 -0000 (UTC) Date: Tue, 12 Jun 2018 15:13:30 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b20458abce2c_79bf2b16f17e5c1017241@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 8cb0d2: What if invariants change? Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b20458abc962_79bf2b16f17e5c101713d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 22:13:36 -0000 ----==_mimepart_5b20458abc962_79bf2b16f17e5c101713d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 8cb0d2086381ce815748793eb61ad79b7c9bf9f0 https://github.com/quicwg/base-drafts/commit/8cb0d2086381ce815748793eb61ad79b7c9bf9f0 Author: Mike Bishop Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- What if invariants change? Commit: 1e4492c9480dce3308e890fe66c4f3ab88c0bc78 https://github.com/quicwg/base-drafts/commit/1e4492c9480dce3308e890fe66c4f3ab88c0bc78 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Which witch? Commit: 3429fcf2095175dd8204ecccc4997c1a9ac453d1 https://github.com/quicwg/base-drafts/commit/3429fcf2095175dd8204ecccc4997c1a9ac453d1 Author: Mike Bishop Date: 2018-06-05 (Tue, 05 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Things, properties Commit: 342a4b88ac819bd287d9b7bf22b462de38de1b6a https://github.com/quicwg/base-drafts/commit/342a4b88ac819bd287d9b7bf22b462de38de1b6a Author: Martin Thomson Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Merge pull request #1411 from quicwg/change_invariants What if invariants change? Compare: https://github.com/quicwg/base-drafts/compare/360886e613d3...342a4b88ac81 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b20458abc962_79bf2b16f17e5c101713d-- From nobody Tue Jun 12 15:13:47 2018 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 6DD23130EE8 for ; Tue, 12 Jun 2018 15:13:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.9 X-Spam-Level: X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 SAuRIB6h7NM0 for ; Tue, 12 Jun 2018 15:13:35 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0F0F5130FDC for ; Tue, 12 Jun 2018 15:13:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528841614; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=WRtk3q08dWvu/eXBIrcPslnrmH7DBq3mJ3E1av5s7Co=; b=lHuSwDDJwqDB4Jlpz3JLltGVJgKdbDqGFYzhshH6+9Gna+6P+78cIskn3PLf52LGERB6VQ4L PHAp6l+oRrX3rEGeE+dEi/E5MA4/8+G77rTILqSK3TQslKscUJnr7a6DmpRuc83Sdl9QSBbH eyrHGeWXaVQHOn98K2sNSgtP9qo= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b20458e.7f5d154fb840-smtp-out-n01; Tue, 12 Jun 2018 22:13:34 -0000 (UTC) Date: Tue, 12 Jun 2018 15:13:34 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b20458e4b508_24f62b09dc6abc18312d4@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b20458e4b074_24f62b09dc6abc1831119"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 22:13:38 -0000 ----==_mimepart_5b20458e4b074_24f62b09dc6abc1831119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/change_invariants Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b20458e4b074_24f62b09dc6abc1831119-- From nobody Tue Jun 12 15:13:50 2018 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 EC15B130FDC for ; Tue, 12 Jun 2018 15:13:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hcRIm9bqzUM1 for ; Tue, 12 Jun 2018 15:13:35 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C3C7130FE4 for ; Tue, 12 Jun 2018 15:13:35 -0700 (PDT) Date: Tue, 12 Jun 2018 15:13:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841614; bh=+F3Z1jCU/n0bSfC3IQmPy0F5sdELcXEqyVDTCPCJWqQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=keuugs3yRGV2+PReToaQrUvxSTfvbVizhgmSxNadu0EDquCUtEqR36WPCH6CrfDzM CjORGSMgJN1wcxrd2YF3W/DQMxTc1FgWttIPqsIFjjCy7CArb3zKtDidFDBqoByurp HMLHKa+/nUs5BoS92kQWVwTPG2WCOmIuyjF0SH3U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if invariants change? (#1411) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20458e4b9ea_4a542ad538f9af50599e3"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:13:38 -0000 ----==_mimepart_5b20458e4b9ea_4a542ad538f9af50599e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1411. -- 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/1411#event-1677433415 ----==_mimepart_5b20458e4b9ea_4a542ad538f9af50599e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1411.

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

----==_mimepart_5b20458e4b9ea_4a542ad538f9af50599e3-- From nobody Tue Jun 12 15:15:01 2018 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 824E2130FE4 for ; Tue, 12 Jun 2018 15:14:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 jHUYPFb6kSvX for ; Tue, 12 Jun 2018 15:14:58 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 20B37130EE8 for ; Tue, 12 Jun 2018 15:14:58 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528841697; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=WjF8aiE8u1YEXvixJnAN1IfVHwkOCVxYB7u0cfviz/M=; b=Quw3BSCpgmT3NOtKUiZNkvTI6bu7YhQ7ICJ/ZbE17HJgoEXPiqcLObfaLmDm3ZYoTlR2Yvfy CrSZTQ27628rxjU/nrl5Lb7H24S4d5K2Io/Y0jlin3SzlAxa1mkYzXoI/3l/6pmjdd5OIQtm VPFZM0sRtMxk1XepDId4LhxsiNM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2045e0.7f8975c0a870-smtp-out-n01; Tue, 12 Jun 2018 22:14:56 -0000 (UTC) Date: Tue, 12 Jun 2018 15:14:55 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b2045df9862b_23d42ab5d1387c087518a@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 76be58: Make TSS incremental to Header Acknowledgment as w... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2045df981fe_23d42ab5d1387c087504c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 22:15:00 -0000 ----==_mimepart_5b2045df981fe_23d42ab5d1387c087504c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ack-reset-stream Home: https://github.com/quicwg/base-drafts Commit: 76be585ca759435bcc9e4e74d8e447176646449c https://github.com/quicwg/base-drafts/commit/76be585ca759435bcc9e4e74d8e447176646449c Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Make TSS incremental to Header Acknowledgment as well Commit: 74fa837a81bea44b9f61a14c96342ee0c4c35985 https://github.com/quicwg/base-drafts/commit/74fa837a81bea44b9f61a14c96342ee0c4c35985 Author: Martin Thomson Date: 2018-06-02 (Sat, 02 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- A start, but not an end Commit: 50383e497f42be8be9c1b244838422006cc08cf9 https://github.com/quicwg/base-drafts/commit/50383e497f42be8be9c1b244838422006cc08cf9 Author: Martin Thomson Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Merge branch 'implicit-ack-header-block' into ack-reset-stream Compare: https://github.com/quicwg/base-drafts/compare/8c182ff699c0...50383e497f42 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2045df981fe_23d42ab5d1387c087504c-- From nobody Tue Jun 12 15:15:09 2018 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 2F906130FE9 for ; Tue, 12 Jun 2018 15:15:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nGgjowa81oaW for ; Tue, 12 Jun 2018 15:15:00 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20390130EE8 for ; Tue, 12 Jun 2018 15:15:00 -0700 (PDT) Date: Tue, 12 Jun 2018 15:14:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841699; bh=xm3nyWv+1k6mYjgMSRWeD6pPv34hgLmK2p3oTYMMnM8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Kt+7oNfhgyAsu8f4jz87Lm6Blw4xEqFwV407OTBddqH85pB1WQQR9jDE86/cZgmHa u5bDXZRWxO5TLG5xgg6Bq7FHIP2SYRyJ6uUK9FD6tyMAYNrx72qM5zZhDQsfosqxxJ 6uUxdIrkAB1K8ufC9TRWjfWhc8P48U98UMOvRh4U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2045e366a5f_26a52b1a995d6f5413862b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 22:15:04 -0000 ----==_mimepart_5b2045e366a5f_26a52b1a995d6f5413862b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 50383e4 Merge branch 'implicit-ack-header-block' into ack-reset-stream -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1400/files/8c182ff699c0041ee68af265b9b033bc9fa13504..50383e497f42be8be9c1b244838422006cc08cf9 ----==_mimepart_5b2045e366a5f_26a52b1a995d6f5413862b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 50383e4 Merge branch 'implicit-ack-header-block' into ack-reset-stream

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2045e366a5f_26a52b1a995d6f5413862b-- From nobody Tue Jun 12 15:18:23 2018 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 6D2C9130FDC for ; Tue, 12 Jun 2018 15:18:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 uKCcng4yKohT for ; Tue, 12 Jun 2018 15:18:18 -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 489DA130EE8 for ; Tue, 12 Jun 2018 15:18:18 -0700 (PDT) Date: Tue, 12 Jun 2018 15:18:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528841897; bh=7uMg9UOyBVkbJeJRy/9+liO2okQ0pPUghWZPhzEQI6c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U+ABYgTZ3bhQdcc8tmuBlwJPveijlaYQd+sWrGz03OeOC/mHxJls+HRFXb/MUARY6 oG+fwNrZ7S6qO+K0n/MXIbABjrebFim+ArOxhMPlk8lM9vzVmBEQnE4lvy72CeyTZp 0vhLpNiV87599mUlEpemi/eTDIEEwYvE+CDOOHwk= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2046a99cd7d_4f913faed92d4f8491260"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 12 Jun 2018 22:18:21 -0000 ----==_mimepart_5b2046a99cd7d_4f913faed92d4f8491260 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, It could affect the state in terms of congestion logic and timeouts. -- 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/1441#discussion_r194905820 ----==_mimepart_5b2046a99cd7d_4f913faed92d4f8491260 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

It could affect the state in terms of congestion logic and timeouts.

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

----==_mimepart_5b2046a99cd7d_4f913faed92d4f8491260-- From nobody Tue Jun 12 15:38:59 2018 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 2BD0B1310B0 for ; Tue, 12 Jun 2018 15:38:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 9eE9cPSXstrP for ; Tue, 12 Jun 2018 15:38:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67051131072 for ; Tue, 12 Jun 2018 15:38:48 -0700 (PDT) Date: Tue, 12 Jun 2018 15:38:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843127; bh=Rh+6tCjbawTQpRbfWoz90oPYo0QJOYIlV/WFuugJiMs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z6GXzKUv4JpIG6Htda2/6PnCWXQ4+tKf+S8XF3scLrzoLj/xodokKHYilYuMeLLr4 NBte/BDCj1sWl5Gel5qAQH+RwL5iI2NGJgpycQLIJgZHSvTwM0r5rpiKkl4/YYBbJg GoM9vUmqr2Tl28wUMWZmwWpZOy0symDP7esDYrps= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204b77c0677_73113fc25ab40f802161e5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:38:53 -0000 ----==_mimepart_5b204b77c0677_73113fc25ab40f802161e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, I think that it's packets and (specifically) ACKs that affect congestion and loss recovery state. -- 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/1441#discussion_r194909930 ----==_mimepart_5b204b77c0677_73113fc25ab40f802161e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

I think that it's packets and (specifically) ACKs that affect congestion and loss recovery state.

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

----==_mimepart_5b204b77c0677_73113fc25ab40f802161e5-- From nobody Tue Jun 12 15:43:13 2018 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 C0DE0130FF9 for ; Tue, 12 Jun 2018 15:43:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2ZJAZ9YQFhkP for ; Tue, 12 Jun 2018 15:43:06 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75E00130EA4 for ; Tue, 12 Jun 2018 15:43:06 -0700 (PDT) Date: Tue, 12 Jun 2018 15:43:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843385; bh=tzUdklOkQgYaZ+LeTmVWHu8GvzRolxOAlxh+75AbyZI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=teJOIH2/mP2cQlyktX/SpuBVcntEBq0olNJd4qRWbL4YZbXwlmuT6dQadOy4yaR4C tDaHtk17OUSK7z98I5mSNVPjRC5Qarui3uJ6imNfka0HI07q26piU+Xzq/LBAoPP93 FOsnk3xf81lIBnlwGiS9yMYIBp3LbDsnhKlgWpvA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204c797e163_1da03fe972d58f7c29918"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:43:10 -0000 ----==_mimepart_5b204c797e163_1da03fe972d58f7c29918 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, A valid frame does not cause undesirable side effects or errors when received more than once. -- 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/1441#discussion_r194910785 ----==_mimepart_5b204c797e163_1da03fe972d58f7c29918 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

A valid frame does not cause undesirable side effects or errors when received more than once.

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

----==_mimepart_5b204c797e163_1da03fe972d58f7c29918-- From nobody Tue Jun 12 15:43:48 2018 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 C718A130FF9 for ; Tue, 12 Jun 2018 15:43:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Crfp_gKAWuS4 for ; Tue, 12 Jun 2018 15:43:39 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7812C130EA4 for ; Tue, 12 Jun 2018 15:43:39 -0700 (PDT) Date: Tue, 12 Jun 2018 15:43:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843418; bh=Y+oSlmBvvLGjwuKuSIj06QIXXhCYEJ5+oBnN/uQURpA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PumkGchjFnHJFlZbfYBu1KeJOjSmQatEY4RRARAMtnzXMjDV5WpO1Y6Evfc7geNiP c467l3pXOog7oKF1Ahl++BcP8Izbwl7EGt0q/nr7zxyXGOQbX3gnRy95XCtk6O5XxK rHV32my5Cf2hzH2C4/G3qxRsAD17xrAryaXONAN4= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204c9acfd27_459b2af1d90c0f58121270"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:43:43 -0000 ----==_mimepart_5b204c9acfd27_459b2af1d90c0f58121270 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, @mikkelfj, presumably you are talking about receiving ACK frames. It shouldn't affect the state of congestion control or timeouts, since it all relies on whether an ACK frame has new information or not. -- 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/1441#discussion_r194909040 ----==_mimepart_5b204c9acfd27_459b2af1d90c0f58121270 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

@mikkelfj, presumably you are talking about receiving ACK frames. It shouldn't affect the state of congestion control or timeouts, since it all relies on whether an ACK frame has new information or not.

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

----==_mimepart_5b204c9acfd27_459b2af1d90c0f58121270-- From nobody Tue Jun 12 15:44:22 2018 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 C44B1130FF9 for ; Tue, 12 Jun 2018 15:44:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 m17elMKGkbA2 for ; Tue, 12 Jun 2018 15:44:14 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78D32130EA4 for ; Tue, 12 Jun 2018 15:44:14 -0700 (PDT) Date: Tue, 12 Jun 2018 15:44:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843453; bh=K3tS+I798JD9ik/6UWOFz62mwzjEb1xOibv5amQTP5Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0mkLkq3/GJtPIn8XspXHuy/1ZLg2tJUjJ89a/+BPDN7ooqp/LIwSR3jt1jE5s5xhS SXkFWP3fnPxOzscc9WV5VHxaFnJ2gx7NbbA+GgHd4X6HgLZnObAemOBeFh2QtmX8e3 UFBEBA4ne7f1BOWPhYXN+Q2rd0zHDBu+I4X5Firg= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204cbda5dba_2a8e2b26649bcf5c535868"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:44:18 -0000 ----==_mimepart_5b204cbda5dba_2a8e2b26649bcf5c535868 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, I like this last re"framing" -- 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/1441#discussion_r194910977 ----==_mimepart_5b204cbda5dba_2a8e2b26649bcf5c535868 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

I like this last re"framing"

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

----==_mimepart_5b204cbda5dba_2a8e2b26649bcf5c535868-- From nobody Tue Jun 12 15:45:45 2018 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 B79CE131071 for ; Tue, 12 Jun 2018 15:45:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EklvhSKkHto9 for ; Tue, 12 Jun 2018 15:45:30 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58D6F13105F for ; Tue, 12 Jun 2018 15:45:30 -0700 (PDT) Date: Tue, 12 Jun 2018 15:45:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843529; bh=j6bEMQIsoefFpGQFfLdXW5SYIc239o68oAL2Sxb5vrY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ndqQkqncL9QOWJLeG0H/nncWniXDB2lZZPVZwG3qW3pcsT/6kyQWdQ7MQpvF91arQ +ABFK3VfthsfvefGlRAMsCle9SlyEdC4YucMnfWWKXeg4pgVI+bqLvdR+Q9LbEHYnU 3GtpPXkPpiH0SLPzSKaePWLn1OX8CByei/0WLKNc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Cleanup (#1328) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204d09880bb_2be22b0dcd16ef5893482"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:45:41 -0000 ----==_mimepart_5b204d09880bb_2be22b0dcd16ef5893482 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1328. -- 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/1328#event-1677474875 ----==_mimepart_5b204d09880bb_2be22b0dcd16ef5893482 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1328.

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

----==_mimepart_5b204d09880bb_2be22b0dcd16ef5893482-- From nobody Tue Jun 12 15:45:51 2018 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 89F3E131054 for ; Tue, 12 Jun 2018 15:45:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 BnGU886zgAO3 for ; Tue, 12 Jun 2018 15:45:38 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BCD013107B for ; Tue, 12 Jun 2018 15:45:38 -0700 (PDT) Date: Tue, 12 Jun 2018 15:45:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843537; bh=ybIz9GiJLJ+GWvAS0F+2B953g2S32AG10e0rVENV/ug=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EsXfohDr3oOARloSzs7bY63e54Xi8i02cRR2HCx3jdCCuvkd8NyTsCtd3ccpG6YnM tvPgH4A4GWuNSTXxddLinJ4DyMWp4SOlm0zM5s9e06CbNVApuEMj+sCnb6BEIvCwVA UbKiWC8+pT7K3ZwS1kwxTFtbAlQRz+rwgmaN6Qk8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Cleanup (#1328) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204d11a569a_1a453fcbd09caf78714b9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 22:45:42 -0000 ----==_mimepart_5b204d11a569a_1a453fcbd09caf78714b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit OBE -- 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/1328#issuecomment-396758249 ----==_mimepart_5b204d11a569a_1a453fcbd09caf78714b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

OBE

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

----==_mimepart_5b204d11a569a_1a453fcbd09caf78714b9-- From nobody Tue Jun 12 15:51:44 2018 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 C35D9130EA4 for ; Tue, 12 Jun 2018 15:51:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 fKoEpinCD2_C for ; Tue, 12 Jun 2018 15:51:39 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 450C4130F04 for ; Tue, 12 Jun 2018 15:51:39 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528843898; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=PoDi6IZZ1Akz085u+J6e0y6erm0/wKbBNf/FEMGdl+8=; b=VMfwaoSs+6BkKDDJkWrDhZpPRFsgJVyYkdPV/v9kiS6SDcvz2oTmj+CVeSdTSdcCxop6ZSwX IS0y7wrWEtLOxXqweqyrvrJB2DkjunVYrO1a+Bkkx1N17iBh7HRw4Er+mIZqivYzmV3BVhdz dy3d3QAFmPHaMn0XsdZYQC/4RAU= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b204e7a.7fbe054ad120-smtp-out-n01; Tue, 12 Jun 2018 22:51:38 -0000 (UTC) Date: Tue, 12 Jun 2018 15:51:37 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b204e7959539_e652ab9da9c1c10221be@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 065337: Say why Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b204e7958bf4_e652ab9da9c1c10220aa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 22:51:41 -0000 ----==_mimepart_5b204e7958bf4_e652ab9da9c1c10220aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts Commit: 0653378aedad324bdbc299d4c1f87060928eb066 https://github.com/quicwg/base-drafts/commit/0653378aedad324bdbc299d4c1f87060928eb066 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Say why **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b204e7958bf4_e652ab9da9c1c10220aa-- From nobody Tue Jun 12 15:51:51 2018 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 BE015130EA4 for ; Tue, 12 Jun 2018 15:51:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 qfAoedkdoKUg for ; Tue, 12 Jun 2018 15:51:41 -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 16640130F04 for ; Tue, 12 Jun 2018 15:51:41 -0700 (PDT) Date: Tue, 12 Jun 2018 15:51:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528843900; bh=4Ty7TPGDE1QsdVh/cfX/810SYJpIsUtDUww0yM/E5UI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V+0FmPQOGhpgvDKKQM/b2WlIOpSIqGmFbdvSGNIoo1WMWRiMWjpGVs1hET/HTiZK/ bSQYjXbDyr+b77m73dzG8O5MaNZ3KgiGyPXdxhqi5znAs26Nq0x0cV4K/gjN+Lsqcb +C5FuCmHf2GCWXvAmTLJpQpJN96PSleqYILLYhug= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b204e7c626dd_4fed2b084238cf501345c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 12 Jun 2018 22:51:44 -0000 ----==_mimepart_5b204e7c626dd_4fed2b084238cf501345c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 0653378 Say why -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1423/files/3f3da757b33e58fd112cb69f8d3f7d396a298f39..0653378aedad324bdbc299d4c1f87060928eb066 ----==_mimepart_5b204e7c626dd_4fed2b084238cf501345c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b204e7c626dd_4fed2b084238cf501345c-- From nobody Tue Jun 12 16:05:35 2018 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 3CFEA130ED8 for ; Tue, 12 Jun 2018 16:05:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 p3-ytOi8rj-s for ; Tue, 12 Jun 2018 16:05:29 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C96FD128CF3 for ; Tue, 12 Jun 2018 16:05:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528844729; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5FyQNvNzVl43JdzG0jwgF9vSGE+LOd6lPqvG5BMVLCo=; b=xBP2kzdW4FpWa0jPoFxYw+XvTpEZzKQ5noNFXYsO+apeoPl0JNzMdJ9jeqwpGvguQmzURPPj KeoXD8orNIxQlDLW94S5IMz9cVh8IvqDke8cyNdJXqT1HsSIERUExj7hZAkONCxdzx59e6Tg DirNCIBQi3I147HJl1X16ILViH0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b2051b9.7f0a795b1ae0-smtp-out-n02; Tue, 12 Jun 2018 23:05:29 -0000 (UTC) Date: Tue, 12 Jun 2018 16:05:28 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b2051b81efb9_131c2b1d9491dc00329a1@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 195f14: Coalescing guidance Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2051b81e5c1_131c2b1d9491dc003286d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 23:05:31 -0000 ----==_mimepart_5b2051b81e5c1_131c2b1d9491dc003286d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 195f144870a810fff9e4e1518f52f779d384ea41 https://github.com/quicwg/base-drafts/commit/195f144870a810fff9e4e1518f52f779d384ea41 Author: Mike Bishop Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Coalescing guidance Commit: e77227596318c72d844707655d68bf59dc5c0bfb https://github.com/quicwg/base-drafts/commit/e77227596318c72d844707655d68bf59dc5c0bfb Author: Mike Bishop Date: 2018-06-08 (Fri, 08 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Include decryption failures Commit: 26c5b742d37f6adbf84fecec5e0abf0d29563484 https://github.com/quicwg/base-drafts/commit/26c5b742d37f6adbf84fecec5e0abf0d29563484 Author: Mike Bishop Date: 2018-06-11 (Mon, 11 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- No mixing CIDs Commit: 3f3da757b33e58fd112cb69f8d3f7d396a298f39 https://github.com/quicwg/base-drafts/commit/3f3da757b33e58fd112cb69f8d3f7d396a298f39 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Kazuho's suggestion Commit: 0653378aedad324bdbc299d4c1f87060928eb066 https://github.com/quicwg/base-drafts/commit/0653378aedad324bdbc299d4c1f87060928eb066 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Say why Commit: 38ca59051f419661f9681575caefb51ec34932d7 https://github.com/quicwg/base-drafts/commit/38ca59051f419661f9681575caefb51ec34932d7 Author: Martin Thomson Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1423 from quicwg/skip_coalesced Coalescing guidance Compare: https://github.com/quicwg/base-drafts/compare/342a4b88ac81...38ca59051f41 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2051b81e5c1_131c2b1d9491dc003286d-- From nobody Tue Jun 12 16:05:40 2018 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 AF5B9130F1C for ; Tue, 12 Jun 2018 16:05:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 RWIBti_GpsWH for ; Tue, 12 Jun 2018 16:05:31 -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 6B971128CF3 for ; Tue, 12 Jun 2018 16:05:31 -0700 (PDT) Date: Tue, 12 Jun 2018 16:05:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528844730; bh=g1NunadnTX+ltj2Iw9sVx5E1JFchvQg+IPQdaRiDEBg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pTnWOJLaJHkOXitJY3hkzYiEBSBcIkeTjQnRhLrtsfvLHWFvibDOJMg1sPOp5UttT 8bIkyDAAQbd/8H8ici7ltzuxtqfQDnZNbbwrfpi68aRYYAirYVOMakgA9TTBYNg/Us idmsJU0xk7kwlawemNm2j0cZDQlKVxxeAqLnedRE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Order of Coalesced Packets (#1287) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2051ba9ffe7_50182b084238cf503100f1"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 23:05:34 -0000 ----==_mimepart_5b2051ba9ffe7_50182b084238cf503100f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1287 via #1423. -- 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/1287#event-1677500472 ----==_mimepart_5b2051ba9ffe7_50182b084238cf503100f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1287 via #1423.

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

----==_mimepart_5b2051ba9ffe7_50182b084238cf503100f1-- From nobody Tue Jun 12 16:05:46 2018 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 0DAD113101B for ; Tue, 12 Jun 2018 16:05:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.399 X-Spam-Level: * X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 woKwLkeL-B9l for ; Tue, 12 Jun 2018 16:05:33 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 F2D91130ED8 for ; Tue, 12 Jun 2018 16:05:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528844732; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=V7hNZBr/kI4/QXqv3Ta9JWUfNvoSMY2HJ+/xgQLMZwU=; b=frlIfqLxcUbl5rATYRw9NqVXxaE5p5BxvNZOQ6rSeHcpOt4Y/b6qLyqApLqvtfMGkBsPPN5j quLnqItka8+7tBTX3FL0oawxuuUV+wjwjTB7uxzuO5lYch9YgGVI9R/q+Xys7oVTzZ/5CyKR 66hiATFqKbNui/MkdoavjQVm7sQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b2051bc.7f7ee548ca20-smtp-out-n03; Tue, 12 Jun 2018 23:05:32 -0000 (UTC) Date: Tue, 12 Jun 2018 16:05:32 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b2051bc1d36e_44552ad87537bc0c2468@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2051bc1ca68_44552ad87537bc0c23a7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 12 Jun 2018 23:05:37 -0000 ----==_mimepart_5b2051bc1ca68_44552ad87537bc0c23a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/skip_coalesced Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2051bc1ca68_44552ad87537bc0c23a7-- From nobody Tue Jun 12 16:05:49 2018 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 A54CE13102B for ; Tue, 12 Jun 2018 16:05:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2fn9kDVaVX5L for ; Tue, 12 Jun 2018 16:05:31 -0700 (PDT) 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 781D6130EDC for ; Tue, 12 Jun 2018 16:05:31 -0700 (PDT) Date: Tue, 12 Jun 2018 16:05:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528844730; bh=Atg2Qxyc/b4Qyh8ksWiv358/RD58tPccbNESc/Prxyc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T6fJ45fyLNnS4wm5pVlDaYaWub09FlY3felipPeuL0gjP4tNITPTHYOBW50nD3t0s Em9ATnkEdv2I8EEfgtF0WnxWBz9qMCDfH72j7/+6mna7tz42DEkWKAq2stXg5Zifcc AeRFkZZTOzKaYUtXrEJftpcotaeUTeXVF6XtkAEY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalescing guidance (#1423) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2051baa8bd3_4b193f993d17af78169740"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 23:05:37 -0000 ----==_mimepart_5b2051baa8bd3_4b193f993d17af78169740 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1423. -- 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/1423#event-1677500469 ----==_mimepart_5b2051baa8bd3_4b193f993d17af78169740 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1423.

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

----==_mimepart_5b2051baa8bd3_4b193f993d17af78169740-- From nobody Tue Jun 12 16:09:52 2018 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 62E5A130E75 for ; Tue, 12 Jun 2018 16:09:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1nqEFDIinZ-m for ; Tue, 12 Jun 2018 16:09:46 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4EE5128CF3 for ; Tue, 12 Jun 2018 16:09:45 -0700 (PDT) Date: Tue, 12 Jun 2018 16:09:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528844985; bh=AEglGdNo2Eeqpeoc4PnkWi+xSTiAsDSzwmE5xwSWh7A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=x1+oFsEcX7zHi0xU/2lUzzJqsijQUpC9V4XEhn3lZsjkNgk6W6q9RiwEIvtVHZs5s psnnvRA0+Wbt4eWkLTAfwnDatpV8lf5HZlvwpmb2tVwWXIaz0GrBFrXF6POMdPEKQQ Uy4+svta+YO7IMWRXu7WHfYz/tMXlN3LH1n+67Ok= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2052b8f162f_7bd12adac5e50f5499415"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 12 Jun 2018 23:09:50 -0000 ----==_mimepart_5b2052b8f162f_7bd12adac5e50f5499415 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > Details of how TLS is integrated with QUIC is provided in more detail in {{QUIC-TLS}}. ## Transport Parameters -During connection establishment, both endpoints make authenticated declarations -of their transport parameters. These declarations are made unilaterally by each -endpoint. Endpoints are required to comply with the restrictions implied by -these parameters; the description of each parameter includes rules for its -handling. +During connection establishment, both endpoints make authenticated +declarations of their transport parameters. These declarations are made +unilaterally by each endpoint. Endpoints are required to comply with the +restrictions implied by these parameters; the description of each +parameter includes rules for its handling. + Please keep to one blank line between paragraphs. > @@ -1410,6 +1416,68 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN capability check {#ecn-capability-check} Title Case for Headings > @@ -2882,6 +3020,83 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in +the IP header. If the header is not readable from the application, the +codepoint 00 (Not-ECT) MUST be assumed. + +ACK_ECN Frame MUST be used when when an endpoint is acknowledging a packet were +the IP header ECN field was marked as ECT(0), ECT(1) or ECN-CE when received. oxford comma > @@ -4196,6 +4410,21 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks + +An on-path attacker may manipulate the value of the field, affecting the +congestion avoidance behavior of the sender. By clearing any CE marks the +connection can help drive a bottle neck queue into a loss regime. By setting Removing any ECN-CE marking causes senders to maintain or increase their sending rate beyond that the path can sustain, which will eventually result in loss. Adding an ECN-CE marking causes senders to reduce their sending rate. > +| Number of ECT(0) marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Number of ECT(1) marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Number of ECN-CE marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #ECN-BLOCK-FIG title="ECN Block"} + + +### ECN counters + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: + +ECT_0: Please make these match the diagram. "ECT(0) Count" might be more concise. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Number of ECT(0) marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Number of ECT(1) marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Number of ECN-CE marked packets (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #ECN-BLOCK-FIG title="ECN Block"} + + +### ECN counters + +The receiver side should implement three 64-bit counters that are copied to the +ECN block when an ACK_ECN frame is generated: Rather than phrase this as "implement these counters" just define the fields in the frame. -- 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/1372#pullrequestreview-128169112 ----==_mimepart_5b2052b8f162f_7bd12adac5e50f5499415 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

>  
 Details of how TLS is integrated with QUIC is provided in more detail in
 {{QUIC-TLS}}.
 
 
 ## Transport Parameters
 
-During connection establishment, both endpoints make authenticated declarations
-of their transport parameters.  These declarations are made unilaterally by each
-endpoint.  Endpoints are required to comply with the restrictions implied by
-these parameters; the description of each parameter includes rules for its
-handling.
+During connection establishment, both endpoints make authenticated
+declarations of their transport parameters. These declarations are made
+unilaterally by each endpoint. Endpoints are required to comply with the
+restrictions implied by these parameters; the description of each
+parameter includes rules for its handling.
+

Please keep to one blank line between paragraphs.

In draft-ietf-quic-transport.md:

> @@ -1410,6 +1416,68 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN capability check {#ecn-capability-check}

Title Case for Headings

In draft-ietf-quic-transport.md:

> @@ -2882,6 +3020,83 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in
+the IP header. If the header is not readable from the application, the
+codepoint 00 (Not-ECT) MUST be assumed.
+
+ACK_ECN Frame MUST be used when when an endpoint is acknowledging a packet were
+the IP header ECN field was marked as ECT(0), ECT(1) or ECN-CE when received.

oxford comma

In draft-ietf-quic-transport.md:

> @@ -4196,6 +4410,21 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks
+
+An on-path attacker may manipulate the value of the field, affecting the
+congestion avoidance behavior of the sender. By clearing any CE marks the
+connection can help drive a bottle neck queue into a loss regime. By setting

Removing any ECN-CE marking causes senders to maintain or increase their sending rate beyond that the path can sustain, which will eventually result in loss. Adding an ECN-CE marking causes senders to reduce their sending rate.

In draft-ietf-quic-transport.md:

> +|              Number of ECT(0) marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|              Number of ECT(1) marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|              Number of ECN-CE marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #ECN-BLOCK-FIG title="ECN Block"}
+
+
+### ECN counters
+
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:
+
+ECT_0:

Please make these match the diagram. "ECT(0) Count" might be more concise.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|              Number of ECT(0) marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|              Number of ECT(1) marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|              Number of ECN-CE marked packets (i)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #ECN-BLOCK-FIG title="ECN Block"}
+
+
+### ECN counters
+
+The receiver side should implement three 64-bit counters that are copied to the
+ECN block when an ACK_ECN frame is generated:

Rather than phrase this as "implement these counters" just define the fields in the frame.

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

----==_mimepart_5b2052b8f162f_7bd12adac5e50f5499415-- From nobody Tue Jun 12 17:43:21 2018 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 25FC3130DC4 for ; Tue, 12 Jun 2018 17:43:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uZ706DXM86Nc for ; Tue, 12 Jun 2018 17:43:14 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EAC2129619 for ; Tue, 12 Jun 2018 17:43:14 -0700 (PDT) Date: Tue, 12 Jun 2018 17:43:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528850593; bh=qL3Xp3SEB+mV4k1AAVrKKsKhQ4PafExeZFPOiSeMPdo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iT0Bw5ZQmWPjy9EjnfnFk94EDpZjMX0ScbmPn1/IxharlxrssQvOaBu/yvyhEI+rR GYbNXU+WJq8liRcD3OE+KiPlsGz0xUZ1RbItKm/EFfrm32PuSBx5DMyWbYHlXT6D2b fJUYcXb5qgI7n3pJGEwObyHOrDXzwa3tbw46YtII= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2068a1a5cd8_2a792ab32df3af6061479"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 13 Jun 2018 00:43:19 -0000 ----==_mimepart_5b2068a1a5cd8_2a792ab32df3af6061479 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul > I don't understand how the sender will be able to handle duplications: "Duplicate detection becomes the responsibility of the sender of the packet rather than that of the receiver. It also becomes reliable." It is possible, because the sender has the list of unacknowledged packets that it has sent. When receiving an acknowledgement, the sender updates the list at the same time using the information to update the connection state (e.g., retire acknowledged data from send buffer). The core idea here is to use that mechanism to determine if a PN with the CE bit set is acknowledged for the first time. Use of a bit-vector is one of the possible approaches. > And as you say the ECN-CE marks are not sufficient to make the verification to work. The ECT counters are still needed to track that ECN is working properly and not are bleached by the network. I would suggest detecting bleaching on the receiver side. If the receiver notices bleaching, it can send an ACK frame instead. I'd assume that that could (or should) be done in the encoding proposed in #1372 as well. > I would also note that the size of the bit-vector is very much depending on the throughput and the RTT. I agree that the size of the ACK frames could be an issue on high bandwidth connection, although I am not sure if we need to care about spending 0.01% of bandwidth (1 bit / 1280 octets) in response to a high-speed flow. But if we do care about that, capping the bitmask to certain size as @martinthomson suggests can be a solution. -- 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/1439#issuecomment-396777979 ----==_mimepart_5b2068a1a5cd8_2a792ab32df3af6061479 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

I don't understand how the sender will be able to handle duplications:= "Duplicate detection becomes the responsibility of the sender of the pac= ket rather than that of the receiver. It also becomes reliable."

It is possible, because the sender has the list of unacknowledged pack= ets that it has sent. When receiving an acknowledgement, the sender updat= es the list at the same time using the information to update the connecti= on state (e.g., retire acknowledged data from send buffer).

The core idea here is to use that mechanism to determine if a PN with = the CE bit set is acknowledged for the first time. Use of a bit-vector is= one of the possible approaches.

And as you say the ECN-CE marks are not sufficient to make the verific= ation to work. The ECT counters are still needed to track that ECN is wor= king properly and not are bleached by the network.

I would suggest detecting bleaching on the receiver side. If the recei= ver notices bleaching, it can send an ACK frame instead. I'd assume that = that could (or should) be done in the encoding proposed in #1372 as well.

I would also note that the size of the bit-vector is very much dependi= ng on the throughput and the RTT.

I agree that the size of the ACK frames could be an issue on high band= width connection, although I am not sure if we need to care about spendin= g 0.01% of bandwidth (1 bit / 1280 octets) in response to a high-speed fl= ow. But if we do care about that, capping the bitmask to certain size as = @martinthomson suggests can be a s= olution.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2068a1a5cd8_2a792ab32df3af6061479-- From nobody Tue Jun 12 19:29:19 2018 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 01EAE130EC2 for ; Tue, 12 Jun 2018 19:29:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BMkmw_bBya4x for ; Tue, 12 Jun 2018 19:29:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68B813102D for ; Tue, 12 Jun 2018 19:29:03 -0700 (PDT) Date: Tue, 12 Jun 2018 19:29:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528856943; bh=0z+PtdxA2lKp/MbZOX9/J6dBZCJ/YPB4spa44Lj0ipU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KCnV+sDloGsFBEFPRXceZ2d9jGgfK05QRrTqeNYknB0xYi4Ai3wtMXE+dduEF5UNL Fdn0vgk3fI1tuJJUWT2ZmK4O0mGzuxZ0BcjK8+JLFWdVKaV/h0FgAU/FcihkFzuBpl N+u8FR1ASCY5F7Kfsj5/V8Fbw3VK2DgOQOfMwpSY= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20816fd65c_78a53fc84cda2f88672345"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 13 Jun 2018 02:29:17 -0000 ----==_mimepart_5b20816fd65c_78a53fc84cda2f88672345 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > I'm wondering whether we could alternatively fix this in text only. If we say that the stream type is indicated by the two low bits of the field, and the Stream ID within the type is indicated by the remaining upper bits of the number, then you get to the same place (indicating streams as 1us, 3bc, etc.) without modifying the bits on the wire. That's basically just codifying a change in presentation / reference terminology. @MikeBishop I am not sure if I like the approach. Within the implementation, I would like to use an integral type to determine a stream. I'd assume that would be the same for others. Using the low-bits for determining the type will mean that we will be calling, for example, a stream represented by a number of `4` as `1bc`. To me, it is more confusing than the current scheme. -- 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/1430#issuecomment-396793738 ----==_mimepart_5b20816fd65c_78a53fc84cda2f88672345 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm wondering whether we could alternatively fix this in text only. If= we say that the stream type is indicated by the two low bits of the fiel= d, and the Stream ID within the type is indicated by the remaining upper = bits of the number, then you get to the same place (indicating streams as= 1us, 3bc, etc.) without modifying the bits on the wire. That's basically= just codifying a change in presentation / reference terminology.

@MikeBishop I am not sure if I = like the approach. Within the implementation, I would like to use an inte= gral type to determine a stream. I'd assume that would be the same for ot= hers.

Using the low-bits for determining the type will mean that we will be = calling, for example, a stream represented by a number of 4 = as 1bc. To me, it is more confusing than the current scheme.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b20816fd65c_78a53fc84cda2f88672345-- From nobody Tue Jun 12 21:57:02 2018 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 7596A130DDC for ; Tue, 12 Jun 2018 21:57:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 HZJfwZbSU0WZ for ; Tue, 12 Jun 2018 21:56:58 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 C5896130DCE for ; Tue, 12 Jun 2018 21:56:58 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528865817; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=HGFFjVLWNS+PpjzuApY13bH/5VvhSrLNgZEic9/Hh2w=; b=IE/E2/d76SMici5zDJuWBklVDgzR3ZLD7jE5xRAC0ZSHifhAUoRjWNjLQ19dEdlZxy5lnIKP ZfFEDaxbJ1RgCddEmZVvayRhXnr/fbcCsxwGM+d18pkJGZXJYvoNVFicB3vZYBLyX5rZGZ1F qCWWZpVCVVMTmM+bTCGlEL4WkcA= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b20a419.7fc68a515c90-smtp-out-n01; Wed, 13 Jun 2018 04:56:57 -0000 (UTC) Date: Tue, 12 Jun 2018 21:56:56 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b20a4189da08_7b3c2b08ad14fc182149@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] b41492: Raw minutes Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b20a4189d5c9_7b3c2b08ad14fc18207a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 04:57:01 -0000 ----==_mimepart_5b20a4189d5c9_7b3c2b08ad14fc18207a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: b41492874eea5d53341ef4d71b316f715dab1b4c https://github.com/quicwg/wg-materials/commit/b41492874eea5d53341ef4d71b316f715dab1b4c Author: Mark Nottingham Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: A interim-18-06/minutes.md Log Message: ----------- Raw minutes Commit: 180f4370e95960c2d8b647056bdcfc2b7c51eb99 https://github.com/quicwg/wg-materials/commit/180f4370e95960c2d8b647056bdcfc2b7c51eb99 Author: Mark Nottingham Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M interim-18-06/minutes.md Log Message: ----------- Markdown-ise Commit: fb1b50731aad1fc3183584869ea51fe7223372ae https://github.com/quicwg/wg-materials/commit/fb1b50731aad1fc3183584869ea51fe7223372ae Author: Mark Nottingham Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M interim-18-06/minutes.md Log Message: ----------- doctoc Commit: eb2fc00973b97ec493653866375b6c33674d61a4 https://github.com/quicwg/wg-materials/commit/eb2fc00973b97ec493653866375b6c33674d61a4 Author: Mark Nottingham Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M interim-18-09/arrangements.md Log Message: ----------- Merge branch 'master' of github.com:quicwg/wg-materials Compare: https://github.com/quicwg/wg-materials/compare/cec91e61b125...eb2fc00973b9 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b20a4189d5c9_7b3c2b08ad14fc18207a-- From nobody Tue Jun 12 22:19:01 2018 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 ED105130DCE for ; Tue, 12 Jun 2018 22:18:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 qb46dK6PXFWK for ; Tue, 12 Jun 2018 22:18:56 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A52C3126F72 for ; Tue, 12 Jun 2018 22:18:56 -0700 (PDT) Date: Tue, 12 Jun 2018 22:18:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528867135; bh=/aCLk16sShChOTgfdEjoqncpLyVLDTekjMw5Pw7XNvQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jjE5Qr7UPVA2fBmmjcq0iZ0Q2c8oLtIMLHZsO/kb4bpsb6MuuMfrGggYDF5wMaNng kEfPU05p5T4FLdyBooFcHo06yUHP2OONca9GxMdtBpQm4iDVQ9aKyVPALISNF4boB3 e2JMfyPw5FJtts6fiyNdbt+9KkECYja3dbp/Chac= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20a93fa57b3_19062aaf7d3d6f601195ad"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 13 Jun 2018 05:18:59 -0000 ----==_mimepart_5b20a93fa57b3_19062aaf7d3d6f601195ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document. | 0x10 - 0x17 | STREAM | {{frame-stream}} | {: #frame-types title="Frame Types"} +All QUIC frames are idempotent. That is, the state of the connection is +unchanged regardless of whether a frame is processed one time or multiple times, Idle timeout? -- 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/1441#discussion_r194958210 ----==_mimepart_5b20a93fa57b3_19062aaf7d3d6f601195ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -906,6 +906,11 @@ explained in more detail as they are referenced later in the document.
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 {: #frame-types title="Frame Types"}
 
+All QUIC frames are idempotent.  That is, the state of the connection is
+unchanged regardless of whether a frame is processed one time or multiple times,

Idle timeout?

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

----==_mimepart_5b20a93fa57b3_19062aaf7d3d6f601195ad-- From nobody Tue Jun 12 22:29:30 2018 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 71D50130F02 for ; Tue, 12 Jun 2018 22:29:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 MFx80eUWEihl for ; Tue, 12 Jun 2018 22:29:25 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1C14130F19 for ; Tue, 12 Jun 2018 22:29:24 -0700 (PDT) Date: Tue, 12 Jun 2018 22:29:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528867764; bh=5Xy3jXy0VWZ/sHuZFO/lU09SGAlQ2+ynJ3NkEtO3T1Q=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=R1P+mJpaMOMhVXN5cn0/LbccQkliBgQECgl7VYYiK9lSR/cdWNdTwJyG0VB0qBq+L wl9/33Hj1BgC7brdxph2ByRT30jmaNZOzgntJWS3qeobQ4NY5zEkJK8G/G/7TmxJFf jHmWdJHM8u/JxlpPM218Nkdeo71bOrGgWJLXVeYk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Remove reference to "End Header Block" (#1442) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20abb439f1e_6e4f2aefec1d0f5462115"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 13 Jun 2018 05:29:29 -0000 ----==_mimepart_5b20abb439f1e_6e4f2aefec1d0f5462115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It is not defined, and such a flag is unnecessary because hq does not allow using a sequence HEADERS frame to represent one header block. Maybe that was possible in the previous versions of the draft. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1442 -- Commit Summary -- * "End Header Block" does not exist -- File Changes -- M draft-ietf-quic-http.md (5) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1442.patch https://github.com/quicwg/base-drafts/pull/1442.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/1442 ----==_mimepart_5b20abb439f1e_6e4f2aefec1d0f5462115 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It is not defined, and such a flag is unnecessary because hq does not allow using a sequence HEADERS frame to represent one header block. Maybe that was possible in the previous versions of the draft.

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

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

Commit Summary

  • "End Header Block" does not exist

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 mute the thread.

----==_mimepart_5b20abb439f1e_6e4f2aefec1d0f5462115-- From nobody Tue Jun 12 22:53:40 2018 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 EFF92130DE5 for ; Tue, 12 Jun 2018 22:53:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vzUaQzIOQjff for ; Tue, 12 Jun 2018 22:53:37 -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 1445F130DE4 for ; Tue, 12 Jun 2018 22:53:37 -0700 (PDT) Date: Tue, 12 Jun 2018 22:53:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528869215; bh=7e+CN0MD+qHFMKjZSBUqg6AoxZM5KGacoGXkWuCrUA0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=SNEJIehAlDSEQkar+z0Mbq9KGFIxP0IBKmmksLAiioPaOf2odOI/vurntYOa4wBAV HKlMoWM6ztD2AW8bR99gJCkGxAOfP2FulxY2iB8WiLimZsoY/DpqRlPo/pmu7okT4J 4yaqxwb3t+gUUferjMRFyqdSGAHq4DANoWQmAmg8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20b15f130c9_36062aca46c7af5c113289"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 13 Jun 2018 05:53:39 -0000 ----==_mimepart_5b20b15f130c9_36062aca46c7af5c113289 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Two p2p server systems with compatible CID formats might accidently have a stateless reset routed back and forth between two are more servers that do not understand the packet context and consequently respond with a new reset. This can leave zombie resets spinning forever. An advanced attacker might be able to take advantage of the above. What is the motivation for making the reset undetectable in the first place? -- 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/1443 ----==_mimepart_5b20b15f130c9_36062aca46c7af5c113289 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Two p2p server systems with compatible CID formats might accidently have a stateless reset routed back and forth between two are more servers that do not understand the packet context and consequently respond with a new reset. This can leave zombie resets spinning forever.

An advanced attacker might be able to take advantage of the above.

What is the motivation for making the reset undetectable in the first place?

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

----==_mimepart_5b20b15f130c9_36062aca46c7af5c113289-- From nobody Tue Jun 12 23:09:56 2018 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 9C4FC130DE4 for ; Tue, 12 Jun 2018 23:09:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zQq0abXau5WS for ; Tue, 12 Jun 2018 23:09:51 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81605130DE5 for ; Tue, 12 Jun 2018 23:09:51 -0700 (PDT) Date: Tue, 12 Jun 2018 23:09:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528870190; bh=Sy2AV9y0y0DaaAslaNx5En6oRch9V159XMG0QO5W2bE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wEvwJp4d8qL1tTZZUIoHSQ9RWNGw38Q5BwGoDciGuFP+FwhQ8963BNZNdsuoL6P5U FvPWKza42mOSFDGAID5zp+LVs/yECyqs7RzPfePtisHenJll9I15YyEIZKh3krcOu0 vDu+2W912/HMp2CV/mVwX/0h5LIbU5d0JzM14TDI= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20b52eab0fe_2c143f8b71bd2f7c100429"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 13 Jun 2018 06:09:55 -0000 ----==_mimepart_5b20b52eab0fe_2c143f8b71bd2f7c100429 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > If the concern is too many bits in the frame for high throughput scenarios, the bitmask could be capped at 64. In those high throughput cases, you should have enough ACKs to reassemble the markings, it's just that you wouldn't have a whole lot of redundancy for the marking signal. That bounds the size of the frame. @martinthomson Or, considering the fact that we are requiring recipients of the ECN-CE flag to send back the information as soon as possible, and that we also want to restrict the frequency of feeding in the CE event to the congestion controller to maybe once per RTT, defining an ACK_WITH_CE frame that carries just one PN that had the CE bit set might be sufficient. ```fe + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Largest Acknowledged (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Delay (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CE ACK Index (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` In case of this example, "CE ACK Index" will designate the index of the PN among the PNs that were carried using the ACK_WITH_CE frame. Ordinary ACK frame can be used when none of the packets being acknowledged had the ECN-CE bit set. -- 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/1439#issuecomment-396824602 ----==_mimepart_5b20b52eab0fe_2c143f8b71bd2f7c100429 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If the concern is too many bits in the frame for high throughput scena= rios, the bitmask could be capped at 64. In those high throughput cases, = you should have enough ACKs to reassemble the markings, it's just that yo= u wouldn't have a whole lot of redundancy for the marking signal. That bo= unds the size of the frame.

@martinthomson Or, considering= the fact that we are requiring recipients of the ECN-CE flag to send bac= k the information as soon as possible, and that we also want to restrict = the frequency of feeding in the CE event to the congestion controller to = maybe once per RTT, defining an ACK_WITH_CE frame that carries just one P= N that had the CE bit set might be sufficient.

+ 0                   1                   2       =
            3
		=

+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

+|                     Largest Acknowledged (i)                ...
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

+|                          ACK Delay (i)                      ...
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

+|                       ACK Block Count (i)                   ...
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

+|                          ACK Blocks (*)                     ...
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

+|                         CE ACK Index (i)                    ...
		=

++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		=

In case of this example, "CE ACK Index" will designate the index of th= e PN among the PNs that were carried using the ACK_WITH_CE frame. Ordinar= y ACK frame can be used when none of the packets being acknowledged had t= he ECN-CE bit set.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b20b52eab0fe_2c143f8b71bd2f7c100429-- From nobody Tue Jun 12 23:14:23 2018 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 09FE9130DE4 for ; Tue, 12 Jun 2018 23:14:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zt6aj2C-fFeV for ; Tue, 12 Jun 2018 23:14:19 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CC2B130DF6 for ; Tue, 12 Jun 2018 23:14:19 -0700 (PDT) Date: Tue, 12 Jun 2018 23:14:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528870458; bh=b0q8VnbVHnlKzagOILXALLHYEdv0SfKKmqem9z6QCAI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0Q5c8Nv5Zs/GP/W3d6Z8ioreLGj/oqmKqiCtU+4gpdB/ZmwsCujUyLGeFLOwpFNQe wghfhvwyhYyp1MqQui31N1XmbSrsTa+1fm63jFBrIpzzbaAxxPGTDgyf1tBUh4nMJv 0LzS9ECXkUfy4eYR8t09GxLlYJhgQRZq4+mkTgkI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20b63a3ee7a_6d853fb5a75eaf78260371"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 13 Jun 2018 06:14:22 -0000 ----==_mimepart_5b20b63a3ee7a_6d853fb5a75eaf78260371 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This could interfere with redundancy in repeat ACK frames: if there is a new CE bit the old PN cannot be present or would have CE cleared. But then again, recent ACK design tends toward not sending redundant ACK's in favor of retransmission on ACK loss, so ...? What is the take in this? -- 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/1439#issuecomment-396825416 ----==_mimepart_5b20b63a3ee7a_6d853fb5a75eaf78260371 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This could interfere with redundancy in repeat ACK frames: if there is= a new CE bit the old PN cannot be present or would have CE cleared. But = then again, recent ACK design tends toward not sending redundant ACK's in= favor of retransmission on ACK loss, so ...? What is the take in this?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b20b63a3ee7a_6d853fb5a75eaf78260371-- From nobody Tue Jun 12 23:44:37 2018 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 8DFA7130DFB for ; Tue, 12 Jun 2018 23:44:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 ts0KnhDO6pMX for ; Tue, 12 Jun 2018 23:44:31 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 AED49130DF0 for ; Tue, 12 Jun 2018 23:44:31 -0700 (PDT) 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=0gp+fWmQDFpHIo8OWgJhg0xJnU8=; b=YRtO6xNSMr1jHQwW DWgqg1PSDaPS3gr+KRDvMoWgWRbQ+1QN+XN642HSKH2LxLoFyhUGsUN01hSOAzC/ Ocx8Xe5kB56HEXYxCzXcP3phQQHNxaaHtyvQkwQyoGZAk8keK7XDWK8xlfdkHjW7 GhHWJkRbXczgMyIfyABn3k+Ez3s= Received: by filter1028p1las1.sendgrid.net with SMTP id filter1028p1las1-8911-5B20BD4E-D 2018-06-13 06:44:30.278967579 +0000 UTC Received: from github-lowworker-643483b.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0025p1mdw1.sendgrid.net (SG) with ESMTP id RLL4BeO3Tz-LMMk1yCQZ6g for ; Wed, 13 Jun 2018 06:44:30.068 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-643483b.cp1-iad.github.net (Postfix) with ESMTP id E5DD66C1AB9 for ; Tue, 12 Jun 2018 23:44:29 -0700 (PDT) Date: Wed, 13 Jun 2018 06:44:30 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Current Code for Recovery period misscounts (#1440) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20bd4de4b2c_2f733fc1d659cf7c3302f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1YGIMgjKQQR9EwNYNLr9VWvJw9d8ageDIFiO PnBv01WZJwNqv3WMlQs/tdG48c5/uPNNt9ivsndIh721JhWk7x1vxQDMOjPRtwn6mXTxXVvfLDgX0I AxaNvRkqUaEkvK/bySF3NsK3OMPpnkM+cpTKcOGjJ4B22cqEsbcCzQgwI/6c6gbVfZf82V7AcYMhLZ k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 13 Jun 2018 06:44:34 -0000 ----==_mimepart_5b20bd4de4b2c_2f733fc1d659cf7c3302f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1440. -- 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/1440#event-1677929358 ----==_mimepart_5b20bd4de4b2c_2f733fc1d659cf7c3302f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1440.

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

----==_mimepart_5b20bd4de4b2c_2f733fc1d659cf7c3302f-- From nobody Tue Jun 12 23:44:42 2018 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 BCFDA130E99 for ; Tue, 12 Jun 2018 23:44:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 C3g-10IvKjd9 for ; Tue, 12 Jun 2018 23:44:31 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 BAF51130DFA for ; Tue, 12 Jun 2018 23:44:31 -0700 (PDT) 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=TVesS7n/kGjkXfZKqZx2ecQGMXs=; b=WbsyWhk+zs6jdv4E ytuWcEdlssPkmWPR20/NA6HF7ktibrfspjoLv3O8xY8rLMxCeRXud1wQUHbvUcwN AOuV/QZlo07/ljAkbpEP0zzNpJTo4DGuOiikonD7uNcmjUde6xh4PjtiDpG+B/iw lpmZCjw+SRZWsOZB8ugXN3B6JuQ= Received: by filter1792p1mdw1.sendgrid.net with SMTP id filter1792p1mdw1-12734-5B20BD4E-1 2018-06-13 06:44:30.040293115 +0000 UTC Received: from github-lowworker-e8fa9ff.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id e2IukYtgTNOo_4zWQAR2Dw for ; Wed, 13 Jun 2018 06:44:30.012 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e8fa9ff.cp1-iad.github.net (Postfix) with ESMTP id 00D1E42025E for ; Tue, 12 Jun 2018 23:44:30 -0700 (PDT) Date: Wed, 13 Jun 2018 06:44:30 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Current Code for Recovery period misscounts (#1440) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20bd4df3744_47de2ac9155bcf582858f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3hz8WpDsXpyt7rN80yEz1kUSJqD3Vr+l9zWL mqOyPubLyjDtn/MVKnE1Mhpk7EiYzQBYPVQ/aPtbh8RJdEDsK88M0kP4k+EuPLGux/G2/MpU5W+hPx +3ZvUybwYy4DEP5eWF/fB2p/ygNed28ivZtecUuRgc4oqkuS1NwQlDCbjth/CcbsdYjfOkQrxpwQuq Q= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 13 Jun 2018 06:44:35 -0000 ----==_mimepart_5b20bd4df3744_47de2ac9155bcf582858f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, you are correct. Closing. -- 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/1440#issuecomment-396831410 ----==_mimepart_5b20bd4df3744_47de2ac9155bcf582858f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, you are correct. Closing.

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

----==_mimepart_5b20bd4df3744_47de2ac9155bcf582858f7-- From nobody Wed Jun 13 00:33:38 2018 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 E15BC130DFB for ; Wed, 13 Jun 2018 00:33:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Qw-3KxWorYYr for ; Wed, 13 Jun 2018 00:33:31 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0DAE130DF9 for ; Wed, 13 Jun 2018 00:33:31 -0700 (PDT) Date: Wed, 13 Jun 2018 00:33:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528875210; bh=M/Jdgi3vE4vGdCs/eHYYEspU6zsENJgsM3E5XXuW5Jo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KR+o+2H+SifGgJbgXYhTJOVcJc3G8BiJ4jXWpjvSTnS6RkUKu9s0ao6VmdQTbMwqX JoHlyRKtD7Z+zNEGFhE+bPfficSvcsLiEhLEmkb8mq505zgRiCaZfVnC9Nt1dM0x7R 7dtPfpib7pC46OphwrHz0A7Gw2+OAHJnhJO2r/wc= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20c8cab9925_52092ad1d264af54620418"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Wed, 13 Jun 2018 07:33:36 -0000 ----==_mimepart_5b20c8cab9925_52092ad1d264af54620418 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho > The core idea here is to use that mechanism to determine if a PN with the CE bit set is acknowledged for the first time. Use of a bit-vector is one of the possible approaches. But, that doesn't work unless you are able to ACK each duplication in separate ACKs, as well as having no redundancy in the ACKing. I think that will make QUIC work very poorly if any ACK packet loss is experienced. There need to be some redundancy to ensure that ACK loss, doesn't equal forward loss from the senders perspective. > I would suggest detecting bleaching on the receiver side. If the receiver notices bleaching, it can send an ACK frame instead. I'd assume that that could (or should) be done in the encoding proposed in #1372 as well. I don't see that working reliably during capability checking, especially not when we add ECN black hole mitigation into the mix. It is the sender that knows which of the packets that are marked during the capability check. If all packets are marked, then yes a trustworthy receiver could detect bleaching. But then we need a signal where the receiver tells the sender to stop mark. I think I see one advantage for something like the bit-vector reporting of CE marks. That is in cases where one doesn't use the normal ECN marking scheme, such as L4S. L4S marks at much higher frequency, thus more CE marks will be received. In this case immediate ACK on CE marks will result in a bit excessive ACK rates. So, from my perspective this would be a reason for a solution with more detailed CE information. However, I don't see your proposal working out when it comes to duplication handling nor the capability checks. My strawman if one like to address providing more detailed information on which packets are CE marked, ensure robustness around recovery periods and ensure that sender side verifications work is the following: * Receiver side suppression of duplicates * An ACK format for ECN where - ECT(0) and ECT(1) are counters. However, they are variable encoding only the least number of bits needed to detect roll over, i.e. receiver track ACKs of ACKs to determine how many bits this needs to be. - ECN-CE marks as bit-vector. Only needing to go as far back as there are CE marks. i.e. bit-vector may be shorter than full PN space covered by ACK. Truncation can be considered. * ACKs are assumed to have redundancy, either all the way to latest ACK of ACKs or at least across the last couple of ACKs. * ACK loss handling for when there are wholes in ACK information received by the sender due to ACK loss and ECN-CE vector truncation. This is to handle continuous verification. ACK holes will trigger loss response also. I would note that these changes would be geared toward making ACKing possible to be delayed in general to as happen as seldom as only four times per RTT assuming having something to ACK in each interval. -- 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/1439#issuecomment-396842800 ----==_mimepart_5b20c8cab9925_52092ad1d264af54620418 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho

The core idea here is to use that mechanism to determine if a PN with = the CE bit set is acknowledged for the first time. Use of a bit-vector is= one of the possible approaches.

But, that doesn't work unless you are able to ACK each duplication in = separate ACKs, as well as having no redundancy in the ACKing. I think tha= t will make QUIC work very poorly if any ACK packet loss is experienced. = There need to be some redundancy to ensure that ACK loss, doesn't equal f= orward loss from the senders perspective.

I would suggest detecting bleaching on the receiver side. If the recei= ver notices bleaching, it can send an ACK frame instead. I'd assume that = that could (or should) be done in the encoding proposed in #1372 as well.

I don't see that working reliably during capability checking, especial= ly not when we add ECN black hole mitigation into the mix. It is the send= er that knows which of the packets that are marked during the capability = check. If all packets are marked, then yes a trustworthy receiver could d= etect bleaching. But then we need a signal where the receiver tells the s= ender to stop mark.

I think I see one advantage for something like the bit-vector reportin= g of CE marks. That is in cases where one doesn't use the normal ECN mark= ing scheme, such as L4S. L4S marks at much higher frequency, thus more CE= marks will be received. In this case immediate ACK on CE marks will resu= lt in a bit excessive ACK rates. So, from my perspective this would be a = reason for a solution with more detailed CE information. However, I don't= see your proposal working out when it comes to duplication handling nor = the capability checks.

My strawman if one like to address providing more detailed information= on which packets are CE marked, ensure robustness around recovery period= s and ensure that sender side verifications work is the following:

  • Receiver side suppression of duplicates
  • An ACK format for ECN where
    • ECT(0) and ECT(1) are counters. However, they are variable encoding o= nly the least number of bits needed to detect roll over, i.e. receiver tr= ack ACKs of ACKs to determine how many bits this needs to be.
    • ECN-CE marks as bit-vector. Only needing to go as far back as there a= re CE marks. i.e. bit-vector may be shorter than full PN space covered by= ACK. Truncation can be considered.
  • ACKs are assumed to have redundancy, either all the way to latest ACK= of ACKs or at least across the last couple of ACKs.
  • ACK loss handling for when there are wholes in ACK information receiv= ed by the sender due to ACK loss and ECN-CE vector truncation. This is to= handle continuous verification. ACK holes will trigger loss response als= o.

I would note that these changes would be geared toward making ACKing p= ossible to be delayed in general to as happen as seldom as only four time= s per RTT assuming having something to ACK in each interval.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b20c8cab9925_52092ad1d264af54620418-- From nobody Wed Jun 13 01:27:44 2018 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 E1160130E0F for ; Wed, 13 Jun 2018 01:27:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 k_An8HjI1lhh for ; Wed, 13 Jun 2018 01:27:37 -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 9E46D130E05 for ; Wed, 13 Jun 2018 01:27:37 -0700 (PDT) Date: Wed, 13 Jun 2018 01:27:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528878456; bh=mDmKJKuQTmmZbu4h/e9GJwTRK1lYWMTzdYee7tqLzIM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k9eN+LkRratH3sm9v5ebBTeOzXoMlZw2pLHFsW6gFlWvMXYghdIQynrZLiGajocZ9 gloC/6WTigo5vBO6y05RDvppSGPzCnEIMfSjrloEu0hbmHgu0DzOb+vHzWXkRha9sW lpLNzFjG+zkS7MV3EVmlBg8kjUW6+PsiHdgJCQro= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b20d578c7001_c402b13e1468f50114289"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 13 Jun 2018 08:27:41 -0000 ----==_mimepart_5b20d578c7001_c402b13e1468f50114289 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. f577c8e Addressing Martin Thomson's comments. Several editorial changes. The biggest on the ECN block definition. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/60468a79507a1d36a07825b80222da03773e571b..f577c8e94d32848feb5cd1582b3ad4b2cc32999c ----==_mimepart_5b20d578c7001_c402b13e1468f50114289 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • f577c8e Addressing Martin Thomson's comments. Several editorial changes. The biggest on the ECN block definition.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b20d578c7001_c402b13e1468f50114289-- From nobody Wed Jun 13 06:51:53 2018 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 992E6130E33 for ; Wed, 13 Jun 2018 06:51:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 GFA87gT5Knat for ; Wed, 13 Jun 2018 06:51:49 -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 113B0130E29 for ; Wed, 13 Jun 2018 06:51:49 -0700 (PDT) Date: Wed, 13 Jun 2018 06:51:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528897907; bh=sU46o9vahV7X36P27F3u7fgwXG4o9eNlAIMppaU29PE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j1r94ZudH9vA3S4k8jNpEOtoN4HXT4hVP96uZosjhkETla8jE/p/Bx/UOFdGMRNzP AnTf2b8xh/ld76l/flQMf8LA+5DgjsMA+OdvnbZ8DB67ugXj28dxGicSsaDGSP4nIz IOY75ryVFR8MwpklY1R6+FFDXncFxS9reQx5inkU= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b212173d2c81_90d2ae2077a0f58103146"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 13 Jun 2018 13:51:51 -0000 ----==_mimepart_5b212173d2c81_90d2ae2077a0f58103146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 2d76935 Added paragraph on dealing with persistent loss of acknowledgement of some sent packets. Removed editorial note that are covered by issue #1402. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/f577c8e94d32848feb5cd1582b3ad4b2cc32999c..2d76935cb8b2f96c4378e86852ae7376cbbb5f91 ----==_mimepart_5b212173d2c81_90d2ae2077a0f58103146 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • 2d76935 Added paragraph on dealing with persistent loss of acknowledgement of some sent packets. Removed editorial note that are covered by issue #1402.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b212173d2c81_90d2ae2077a0f58103146-- From nobody Wed Jun 13 06:57:13 2018 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 44D81130E33 for ; Wed, 13 Jun 2018 06:57:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 xRUosgX002KW for ; Wed, 13 Jun 2018 06:57:09 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 4FC9712F18C for ; Wed, 13 Jun 2018 06:57:09 -0700 (PDT) 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=7KDBCUHk7w1IJYgKrQa0l8dOg7g=; b=uxDNrTTu/aq7n18D 46QnLzIENlofsgU3ysBA+OmES86N71iHjmV+cITUGCWwADBfvWGVPr+umnf71yQJ xr5sOJpqcX8l9TGjOI06MOVQYdzt804UbY8bKSgVxHK9W06t9Xa06b7/kz0zpCLb N6JnfqkVS3H2F/MVNMlN2zV3ZsI= Received: by filter0854p1las1.sendgrid.net with SMTP id filter0854p1las1-753-5B2122B3-36 2018-06-13 13:57:07.915209059 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id g88Va_AERO261g6jU_5aUA for ; Wed, 13 Jun 2018 13:57:07.812 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id C4DBFBFAC8 for ; Wed, 13 Jun 2018 06:57:07 -0700 (PDT) Date: Wed, 13 Jun 2018 13:57:08 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2122b3c3756_646c3f86c8f14f8065690"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1Y827PP78X79+Hr2NiF55gvQpNpKY1p77Gvc TJo8ZyM/4MD1poud5mYZIWLjE01uNvozuYPaF/qfpAFU58qSl9ByMyvT9xo1zHt2nBYoeAUFFLo3Zx T9PyYj82eypONH16IkGpjBd4BpY2kDncLxI1hoEAMz+pxaYLvwqX28cfnJHZubEqluu3X/Ihlw3abh I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 13 Jun 2018 13:57:12 -0000 ----==_mimepart_5b2122b3c3756_646c3f86c8f14f8065690 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Note, I have just added a paragraph for an issue related to persistent ACK loss for some packets. Such events causes an insensitiveness in the continuous verification equal to the number of packets that the receiver seen with ECN markings and never acknowledged in the sender. Please review this late addition. -- 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/1372#issuecomment-396946546 ----==_mimepart_5b2122b3c3756_646c3f86c8f14f8065690 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Note, I have just added a paragraph for an issue related to persistent A= CK loss for some packets. Such events causes an insensitiveness in the cont= inuous verification equal to the number of packets that the receiver seen w= ith ECN markings and never acknowledged in the sender. Please review this l= ate addition.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b2122b3c3756_646c3f86c8f14f8065690-- From nobody Wed Jun 13 07:03:10 2018 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 4534E130F3B for ; Wed, 13 Jun 2018 07:02:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Vn9u4rDmX0FK for ; Wed, 13 Jun 2018 07:02:54 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9819130E81 for ; Wed, 13 Jun 2018 07:02:53 -0700 (PDT) Date: Wed, 13 Jun 2018 07:02:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528898573; bh=x1n90McTrE9c43f02f1VZMhg0lJ06+eS/Wu8AvcsogA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qXp7nB7/aLbxCj7KshOGDbMYJsi0XxOgMqFetdf+aQrd6Rr0Li5lajvy1mEk7JXS/ 2wky8h2oqvInzFPwnnS9Ya6vcuYU1vMZQd2aDb7Fb/W0ZQdKLiNtfLPPM1asJVddlR OqWSGlBR9mP45kU2qmFX3Wdw0cwrLvjVI2vnTZbM= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21240d1cf2b_49703fd58b01ef781046a9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 13 Jun 2018 14:03:08 -0000 ----==_mimepart_5b21240d1cf2b_49703fd58b01ef781046a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 4af108c Fixing typo in new paragraph. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/2d76935cb8b2f96c4378e86852ae7376cbbb5f91..4af108c47fd2cbaea42b6b83c8d19f1d52513443 ----==_mimepart_5b21240d1cf2b_49703fd58b01ef781046a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • 4af108c Fixing typo in new paragraph.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b21240d1cf2b_49703fd58b01ef781046a9-- From nobody Wed Jun 13 07:13:00 2018 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 D09A1130E31 for ; Wed, 13 Jun 2018 07:12:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 AtixfgVK0jZo for ; Wed, 13 Jun 2018 07:12:53 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C9A130E29 for ; Wed, 13 Jun 2018 07:12:53 -0700 (PDT) Date: Wed, 13 Jun 2018 07:12:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528899172; bh=uiw63rVmkZtAyavuWfK6Zz+G1ixPQBCvm5m46yl9Xm0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=OSbDJ3nb/iAu6oS5NFmlSDFWykdVMrJf1q5sh/obuShlWjK2bERYJ228S9wzh9VTO r8QBjy45aJ8L85uPX3K/6xWyJmTwscbkC2sSw5jfXCrDTK3Tax/oO8eND+Dv2CAkjQ QjVEwtWfd0R0F+JNWgqvyStiyjXVqH2mSbbChgN0= From: Lucas Pardue Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: Subject: [quicwg/wg-materials] Expand detail on HTTP flags discussion (#49) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2126645b072_2d143f95244d2f80160826"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 13 Jun 2018 14:12:55 -0000 ----==_mimepart_5b2126645b072_2d143f95244d2f80160826 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/wg-materials/pull/49 -- Commit Summary -- * Expand detail on HTTP flags discussion -- File Changes -- M interim-18-06/minutes.md (6) -- Patch Links -- https://github.com/quicwg/wg-materials/pull/49.patch https://github.com/quicwg/wg-materials/pull/49.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/wg-materials/pull/49 ----==_mimepart_5b2126645b072_2d143f95244d2f80160826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

  https://github.com/quicwg/wg-materials/pull/49

Commit Summary

  • Expand detail on HTTP flags discussion

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 mute the thread.

----==_mimepart_5b2126645b072_2d143f95244d2f80160826-- From nobody Wed Jun 13 14:10:49 2018 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 44BDB130DFC for ; Wed, 13 Jun 2018 14:10:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 tA30QOK8fcmn for ; Wed, 13 Jun 2018 14:10:38 -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 AACD9130DF1 for ; Wed, 13 Jun 2018 14:10:38 -0700 (PDT) Date: Wed, 13 Jun 2018 14:10:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528924237; bh=c8bVp5aIren8ltiJDhp9HWEpzvRH8AfXg1dYzPBu15k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1itpM8iyL6hF0OJCnz5AGkrjgBjtYJcsdQid4qDtQXCsDG58uSRmJDzv+PEuMKceB qS9iay3unFig0Lm5aeINweAgeUD8rtVfuOMQrWciS7f38Qe8DjnbfnEYSrmeT8WUtT thKMz0sFn1rUjWAjujrcbxai/+U0GH6Ga/x4mwC0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK: Huffman string compression (#1435) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21884d9c3b7_d0f33fa99518cf80275691"; 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.26 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: Wed, 13 Jun 2018 21:10:47 -0000 ----==_mimepart_5b21884d9c3b7_d0f33fa99518cf80275691 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Technically, it says that it uses the string literal format from HPACK, and mentions that that format includes a bit to indicate Huffman or not. Would it suffice to expand that reference to explicitly call out that the format includes Huffman encoding? -- 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/1435#issuecomment-397087993 ----==_mimepart_5b21884d9c3b7_d0f33fa99518cf80275691 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Technically, it says that it uses the string literal format from HPACK, and mentions that that format includes a bit to indicate Huffman or not. Would it suffice to expand that reference to explicitly call out that the format includes Huffman encoding?

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

----==_mimepart_5b21884d9c3b7_d0f33fa99518cf80275691-- From nobody Wed Jun 13 14:19:07 2018 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 B776D130FA0 for ; Wed, 13 Jun 2018 14:19:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 3hCug0fDv7ee for ; Wed, 13 Jun 2018 14:19:03 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 AF449130F9A for ; Wed, 13 Jun 2018 14:19:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528924742; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=oJ+lME2xkbYPJXjfSklumSsAPk2wBI6/DfkzCS6nCiA=; b=ypxJHYgELTvwmH5tzFWM9WHPB3GbBbenUWiztRGf1CrP9vVAbWj83eVOiY9yeXVlZU21lhdp znBV5/Wt2Bn1DXOa+S1p7PX4FN5F4Om6VCB7h+u9JDYsOvj+4IyF8rUHYSA5TZ9HYH67nEC7 AvxYD8HYJoj2z7CEeDx4Q8aSeWE= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b218a46.7f0aa7e5c840-smtp-out-n02; Wed, 13 Jun 2018 21:19:02 -0000 (UTC) Date: Wed, 13 Jun 2018 14:19:01 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b218a457f2d6_9402b25a4bf7c108234@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 7e78a5: Expand Primitives section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b218a457eb84_9402b25a4bf7c10822c4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 21:19:06 -0000 ----==_mimepart_5b218a457eb84_9402b25a4bf7c10822c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack/explicit_huffman Home: https://github.com/quicwg/base-drafts Commit: 7e78a56476f4f60f518505786a4183b8bed792ee https://github.com/quicwg/base-drafts/commit/7e78a56476f4f60f518505786a4183b8bed792ee Author: Mike Bishop Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Expand Primitives section **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b218a457eb84_9402b25a4bf7c10822c4-- From nobody Wed Jun 13 14:19:51 2018 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 C0B36130FA3 for ; Wed, 13 Jun 2018 14:19:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Z5_irnrtrTlS for ; Wed, 13 Jun 2018 14:19:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48ABD130FA0 for ; Wed, 13 Jun 2018 14:19:48 -0700 (PDT) Date: Wed, 13 Jun 2018 14:19:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528924787; bh=GXE7+/UZiWEjJyqVek+/ZbzJ9xeVJ+6qme1aTbMhtmg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bqqMkxvEfnzMIaPH35Uxi7Nely434ybhT0aWMv2LRJSGOUg/lOvc4jIFQJgeT4kYa xrDsBBneJ4EvzMm9hd5JznCW4Pz+mtU5fgGKqAWzO7tBMmhbqBVi0d5OLVGjqCkwDr zajLvoiDHSNyi/FNO6GBRFWnuE7l99YbFjwioAd4= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Expand Primitives section (#1444) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b218a73a9a75_58033fb6f5430f80257927"; 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.26 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: Wed, 13 Jun 2018 21:19:50 -0000 ----==_mimepart_5b218a73a9a75_58033fb6f5430f80257927 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1435. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1444 -- Commit Summary -- * Expand Primitives section -- File Changes -- M draft-ietf-quic-qpack.md (20) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1444.patch https://github.com/quicwg/base-drafts/pull/1444.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/1444 ----==_mimepart_5b218a73a9a75_58033fb6f5430f80257927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1435.

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

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

Commit Summary

  • Expand Primitives section

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 mute the thread.

----==_mimepart_5b218a73a9a75_58033fb6f5430f80257927-- From nobody Wed Jun 13 14:20:51 2018 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 4A7BD130FA0 for ; Wed, 13 Jun 2018 14:20:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 tyO79G16Oquc for ; Wed, 13 Jun 2018 14:20:48 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C166F130F9A for ; Wed, 13 Jun 2018 14:20:48 -0700 (PDT) Date: Wed, 13 Jun 2018 14:20:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528924848; bh=rZouUZmkcGkHQ7DpByqtwPVS+GVZVBeIVbUJB22obY8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nQA0CKgGHjqFSfxNrE5olhS3LT5wH4fjUsnCnV5yy5a8Xzg7VNmWJGABU4N1UXba7 CItN/sm/M/X/B+GqlHfj8lWOCAI6GGs/WHqrJDm3VOIG27JeSe0e1j6Fve8gGnutuu XaMuOpubCmPMvgf6Q3uWzjpIafp8EcwDKSMOITkA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b218ab0183d4_2cc3fe4d0800f80179150"; 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.26 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: Wed, 13 Jun 2018 21:20:50 -0000 ----==_mimepart_5b218ab0183d4_2cc3fe4d0800f80179150 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Given that QUIC will be swinging back to implicit-open streams, this requirement at the application layer seems unnecessary. -- 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/1417#issuecomment-397090754 ----==_mimepart_5b218ab0183d4_2cc3fe4d0800f80179150 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Given that QUIC will be swinging back to implicit-open streams, this requirement at the application layer seems unnecessary.

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

----==_mimepart_5b218ab0183d4_2cc3fe4d0800f80179150-- From nobody Wed Jun 13 14:22:39 2018 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 E22F9131008 for ; Wed, 13 Jun 2018 14:22:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 nHiHcMhwBMRV for ; Wed, 13 Jun 2018 14:22:28 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 1FD01130FA6 for ; Wed, 13 Jun 2018 14:22:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528924947; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=MoVDhXJgaw2++J9gmLe5e2B1pel+iEaa7aSmfPqOxhY=; b=A+5XfBW65yKRth6kHZEpuRDjSgElJPijRutGqPtXXz7qBYMQz3rk2f+HEfL45gsYBdUFVXI/ xk/Ivrz9oUSE3FcnRn2LefL6T/ddLqmIvWbjnsDq/ZF6qiY2TLrr+wNqwVOGIe6JhS8LtN5Y UJut1gth3Hfyqbwwy/p3RUVuC88= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b218b13.7fe1714423c0-smtp-out-n01; Wed, 13 Jun 2018 21:22:27 -0000 (UTC) Date: Wed, 13 Jun 2018 14:22:26 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b218b12616cc_38bb2b280b3a5bfc9862e@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 5245f6: Remove stream sequencing requirement; obsoleted by... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b218b126131c_38bb2b280b3a5bfc985f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 21:22:36 -0000 ----==_mimepart_5b218b126131c_38bb2b280b3a5bfc985f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 5245f6b901660842f6bee198c9f18a4e1cddf64b https://github.com/quicwg/base-drafts/commit/5245f6b901660842f6bee198c9f18a4e1cddf64b Author: Mike Bishop Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Remove stream sequencing requirement; obsoleted by implicit-open of streams Fixes #1417. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b218b126131c_38bb2b280b3a5bfc985f3-- From nobody Wed Jun 13 14:22:47 2018 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 55B1713102E for ; Wed, 13 Jun 2018 14:22:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 CEO23SoDbP43 for ; Wed, 13 Jun 2018 14:22:33 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E62B130FDE for ; Wed, 13 Jun 2018 14:22:33 -0700 (PDT) Date: Wed, 13 Jun 2018 14:22:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528924952; bh=M2hPQF35820U2MOgCksEVwNkbaKk8/lRLSb9bjZGMNQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=igVlMpQnB+xbvnI9yi1pGZ13RUauxYrJ0/nFe/cNIX9glwRpDi709pDUCiWa8SoJZ h96Xq/pL9cU4Qd26Ti2f2Wh1PWqRO9aNTPZklhJ+B2mRauRi7hiVXs1o+2P6x3ugfe Eu6nYPVcTu1rGEzBdS45mnAquRzgC5I0wn7CQVwQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] HTTP/QUIC: "Streams SHOULD be used sequentially, with no gaps." ambiguity. (#1417) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b218b18d1042_607c3fa117740f8457004d"; 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.26 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: Wed, 13 Jun 2018 21:22:42 -0000 ----==_mimepart_5b218b18d1042_607c3fa117740f8457004d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1417 via 5245f6b901660842f6bee198c9f18a4e1cddf64b. -- 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/1417#event-1679782666 ----==_mimepart_5b218b18d1042_607c3fa117740f8457004d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1417 via 5245f6b.

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

----==_mimepart_5b218b18d1042_607c3fa117740f8457004d-- From nobody Wed Jun 13 14:28:41 2018 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 E1ADE131024 for ; Wed, 13 Jun 2018 14:28:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rwmlY_-ZBCtv for ; Wed, 13 Jun 2018 14:28:33 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14069130FCF for ; Wed, 13 Jun 2018 14:28:33 -0700 (PDT) Date: Wed, 13 Jun 2018 14:28:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528925312; bh=GtapWjo49ilyCV22b/6BjYvfjQG7uX6ALUKIKlCbPgc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CnnKinnHcwFdMpwfmSzDmtDnCm2VJxx3e2g2n+kwOvI5gjo3uvigdlOLESWO+b4tz KihlhbCR4vQKxPDo0wf+x0eJj8JDwtexfl8P5FOM9NwMQyD/s0xKMTyTDomHADOrzz Dj2u46KhCsPznFejyRF0MAvSMv3F7IzdaL28h6Dc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b218c80338e4_576a2aecebb62f584056d"; 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.26 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: Wed, 13 Jun 2018 21:28:39 -0000 ----==_mimepart_5b218c80338e4_576a2aecebb62f584056d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The definition of idle given in the Seattle slides (which note that spec text is needed) is the time since any of the following: - Last *new* app data sent or received - Last PING sent, retransmissions excluded - Last PING received The definition of path timeout, separately, is the time since the first unacked packet for which an ACK is expected (i.e. not ACK-only) *and* whose packet number is greater than the largest ever acked. -- 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/1429#issuecomment-397093223 ----==_mimepart_5b218c80338e4_576a2aecebb62f584056d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The definition of idle given in the Seattle slides (which note that sp= ec text is needed) is the time since any of the following:

  • Last new app data sent or received
  • Last PING sent, retransmissions excluded
  • Last PING received

The definition of path timeout, separately, is the time since the firs= t unacked packet for which an ACK is expected (i.e. not ACK-only) and= whose packet number is greater than the largest ever acked.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b218c80338e4_576a2aecebb62f584056d-- From nobody Wed Jun 13 14:52:49 2018 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 B35BD130DE3 for ; Wed, 13 Jun 2018 14:52:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 r-HQYEag5m_E for ; Wed, 13 Jun 2018 14:52:46 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 1AED71271FF for ; Wed, 13 Jun 2018 14:52:45 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528926765; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=jnn8OEzeO0EqPoQtSKv3bGjyNpsnLoZ+tXk8XAqCwKE=; b=KwW2+yGXvn8cgtfYfcWuDegLrjL8sXUERhCxgbUNDEVHdNSzKZ5Uo0DkvniuJri1hHThaQPl 0AMZVCtmr0fabOKxhp1IS2qrkH05cK48rNARDHpYdGS4tR5P85x5P4bCISUgsIyqJurHfcEX nkTMB5wlrkdPYYvmBZjER1lkUt4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b21922d.7fa1081beb10-smtp-out-n02; Wed, 13 Jun 2018 21:52:45 -0000 (UTC) Date: Wed, 13 Jun 2018 14:52:43 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b21922bdf84d_47302ab09fc15c08190c1@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 10c5e8: Re-"framing" Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21922bdf3d5_47302ab09fc15c08189d3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 21:52:48 -0000 ----==_mimepart_5b21922bdf3d5_47302ab09fc15c08189d3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/frame_idempotency Home: https://github.com/quicwg/base-drafts Commit: 10c5e89d9f0a1d0ddaceb70332d35951070f9b26 https://github.com/quicwg/base-drafts/commit/10c5e89d9f0a1d0ddaceb70332d35951070f9b26 Author: Mike Bishop Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Re-"framing" **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21922bdf3d5_47302ab09fc15c08189d3-- From nobody Wed Jun 13 14:52:56 2018 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 9C9E2130FCF for ; Wed, 13 Jun 2018 14:52:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 JYa4Sdw4Zj1S for ; Wed, 13 Jun 2018 14:52:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5BEB1271FF for ; Wed, 13 Jun 2018 14:52:48 -0700 (PDT) Date: Wed, 13 Jun 2018 14:52:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528926767; bh=C1vByO+DUSwGJA8Klh4KctoWqG3xV30cll76uhT79FA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cdLi7qgFVMyG6Gu7pQibT/hltrERG580KwnBTu7ShbbRM2U1PCv9HsldGXNTOSBQK 9oWHO9ibx/nKbJBQEBatG/oIb1wMAihTtF2qCrc/bCh/xOBHdM5zcmThuRDGKxIzH2 JAeAHVsgh1GeebUN4ek4uNO2Jol8KDXUThM5UO3o= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21922f43a0f_37f3fa2fa5daf8419152a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 13 Jun 2018 21:52:51 -0000 ----==_mimepart_5b21922f43a0f_37f3fa2fa5daf8419152a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 10c5e89 Re-"framing" -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1441/files/411966117c5b2a7d235273dda5a587c341bb5376..10c5e89d9f0a1d0ddaceb70332d35951070f9b26 ----==_mimepart_5b21922f43a0f_37f3fa2fa5daf8419152a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b21922f43a0f_37f3fa2fa5daf8419152a-- From nobody Wed Jun 13 14:57:27 2018 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 1F20E130F9F for ; Wed, 13 Jun 2018 14:57:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 KUVBC2Dj4Gjx for ; Wed, 13 Jun 2018 14:57:20 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 9749F130DDE for ; Wed, 13 Jun 2018 14:57:20 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528927040; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=lq9HLxltQCqdvf6FT4VzoE/s/69dYnHipwVieOdYF58=; b=rEOUPD9Eb3pBcSpRAxfq+INlxINsMyFaOCkykTW/r8v4EGtSW5lT1r2cYHnSFTgpjuPh8ugh GqfIkj7OUE2HzXDgx6iVsoI1v0SRstGAQJ1dgcs6Lq8uFYIdlRnYf9MguhiesSaI1rFMirIJ MzYaFr/XeLfEVAarmxVZdqro6Mo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: kazuhooku=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b21933f.7f523b80d990-smtp-out-n01; Wed, 13 Jun 2018 21:57:19 -0000 (UTC) Date: Wed, 13 Jun 2018 14:57:19 -0700 From: Kazuho Oku Reply-To: Kazuho Oku To: quic-issues@ietf.org Message-ID: <5b21933f12a2a_5ff62ae4021c9c043951a@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b4521e: "End Header Block" does not exist Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21933f126ef_5ff62ae4021c9c043942"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 21:57:25 -0000 ----==_mimepart_5b21933f126ef_5ff62ae4021c9c043942 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: b4521e2932e1fca352c6378ced27c12b2d66e2c0 https://github.com/quicwg/base-drafts/commit/b4521e2932e1fca352c6378ced27c12b2d66e2c0 Author: Kazuho Oku Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- "End Header Block" does not exist **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21933f126ef_5ff62ae4021c9c043942-- From nobody Wed Jun 13 14:57:35 2018 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 554C7130FFB for ; Wed, 13 Jun 2018 14:57:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 skzUoPpd00Mf for ; Wed, 13 Jun 2018 14:57:23 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 4DA01130FE6 for ; Wed, 13 Jun 2018 14:57:23 -0700 (PDT) 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=pGciC8MlmUXIvo3PGpvC0uaa+Ls=; b=ALpo4sHc/dVsDgMd h/LFHmwXMSWknxurA1T3giLPc6D+ZLsyxDDbSpJMRli8uX/NG6/RF8tYvH8HBn85 uuzeDUOY9vxntMt4j+MCa9U13Zn+046JeVO8d19QQTYNlXBjBIckqtC2MidbdkKj rVKn1NYUgHDqJxEKLEqg6kMbgqg= Received: by filter0654p1las1.sendgrid.net with SMTP id filter0654p1las1-21948-5B219341-36 2018-06-13 21:57:21.99944239 +0000 UTC Received: from github-lowworker-643483b.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id RoHxMB6uTYip6GAyhyXjTQ for ; Wed, 13 Jun 2018 21:57:21.853 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-643483b.cp1-iad.github.net (Postfix) with ESMTP id CE7116C13AB for ; Wed, 13 Jun 2018 14:57:21 -0700 (PDT) Date: Wed, 13 Jun 2018 21:57:22 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove reference to "End Header Block" (#1442) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b219341cd101_2ee13fb75c66af7823439"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3yIBXONx/AmaQ3VU6h2HzaHXyTNJjmoGiPST izLuQr99opPmdtufTr+b8FZ8RZLOrnsAfsQTiEKfKiv9/kOxJsFaT+p5TwgffAdXmKBU2XzuEWoCki 47g8vOjpPqDwuDRwVwDof2go4uUz8KNKCemDTyNCIBaWQcg7nX25osdFvku8MJK5x33M+sjIdQaRo/ g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 13 Jun 2018 21:57:33 -0000 ----==_mimepart_5b219341cd101_2ee13fb75c66af7823439 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1442. -- 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/1442#event-1679845550 ----==_mimepart_5b219341cd101_2ee13fb75c66af7823439 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1442.

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

----==_mimepart_5b219341cd101_2ee13fb75c66af7823439-- From nobody Wed Jun 13 15:43:25 2018 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 0FC32130E96 for ; Wed, 13 Jun 2018 15:43:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 Gy__NaI3bsSq for ; Wed, 13 Jun 2018 15:43:21 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 B72B6124BE5 for ; Wed, 13 Jun 2018 15:43:21 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528929801; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=mTnT0ezUh/PD3d+Z9iO+3hkxyCb08Iq9snYEQo9HoV8=; b=XyLtHuyueUOf42HFyKA3KUUtTBf/ONXss2lzwn+t1nejgQqQUczFQLGvjnDv/W4bOIHqsTUU jlLH+S/Pis2S0XhR2E2kw1HPYz/aM6gTHcg4D8ESGUOnZpmC53OASNosTROEsXrYoQJOCoiW gIvRCu81HiHU3cqEaOcdfyIgy7k= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b219e08.7f00ff87a300-smtp-out-n03; Wed, 13 Jun 2018 22:43:20 -0000 (UTC) Date: Wed, 13 Jun 2018 15:43:19 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b219e075479f_55c62af443303c1853351@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 17a9fa: Expand detail on HTTP flags discussion Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b219e07543f9_55c62af443303c185326b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 13 Jun 2018 22:43:23 -0000 ----==_mimepart_5b219e07543f9_55c62af443303c185326b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 17a9fafcad9e138aaa0bf4495326c7a7f8bfd381 https://github.com/quicwg/wg-materials/commit/17a9fafcad9e138aaa0bf4495326c7a7f8bfd381 Author: Lucas Pardue Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M interim-18-06/minutes.md Log Message: ----------- Expand detail on HTTP flags discussion Commit: 33152788611c0449fbdb24bfc06641467ff4aded https://github.com/quicwg/wg-materials/commit/33152788611c0449fbdb24bfc06641467ff4aded Author: Mark Nottingham Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M interim-18-06/minutes.md Log Message: ----------- Merge pull request #49 from LPardue/patch-1 Expand detail on HTTP flags discussion Compare: https://github.com/quicwg/wg-materials/compare/eb2fc00973b9...33152788611c **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b219e07543f9_55c62af443303c185326b-- From nobody Wed Jun 13 15:43:33 2018 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 70753124BE5 for ; Wed, 13 Jun 2018 15:43:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 uJk9zOYU-H6Y for ; Wed, 13 Jun 2018 15:43:22 -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 E2D5B130DC9 for ; Wed, 13 Jun 2018 15:43:21 -0700 (PDT) Date: Wed, 13 Jun 2018 15:43:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528929800; bh=ALd+ZbnWptdvwqhSLdV8HBr9VwvXuaDGIJQTfTTHVzA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1lQKWTQuPhA+J9eNp6MpY7/BakUCRFAGQlkUD48UCXvd3SRQ8d9IV95ZSFVWHGe36 LWprPtRO/E4MV9xjzv1Y0vzAj7F+CMKZJrM0u0+iLuhE+ix1eGSLO9g6BVJm4WbXoI jOOHG9Cw6Hmy2aj+h8S79H50aGJ3kVZ0ezLRmZRs= From: Mark Nottingham Reply-To: quicwg/wg-materials To: quicwg/wg-materials Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/wg-materials] Expand detail on HTTP flags discussion (#49) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b219e0892eac_1cb73ffdef302f787047e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot 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.26 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: Wed, 13 Jun 2018 22:43:24 -0000 ----==_mimepart_5b219e0892eac_1cb73ffdef302f787047e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #49. -- 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/wg-materials/pull/49#event-1679914637 ----==_mimepart_5b219e0892eac_1cb73ffdef302f787047e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #49.

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

----==_mimepart_5b219e0892eac_1cb73ffdef302f787047e-- From nobody Wed Jun 13 17:23:19 2018 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 85300130EC8 for ; Wed, 13 Jun 2018 17:23:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 SvITIIiic6nl for ; Wed, 13 Jun 2018 17:23:16 -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 16E38130EBD for ; Wed, 13 Jun 2018 17:23:16 -0700 (PDT) Date: Wed, 13 Jun 2018 17:23:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528935794; bh=y3t6XQpmY8MzCgSLCqr/DFmYjhqupJX9yWFZ/zo0nK8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IoMQaUuCfO8k/8tjGzEJ5akFDnxq5ts1Pq0iyBEtsGWy1fX1BU7SukIJvzoQ29el1 xxsq+ARVTF90Vi+/0IkxIf9LDuYbPrezOIO6byec3x3o3LOi02S/g1DAWDCYFyJUiA GSL3/iU/+fIk9XYOEqYMSSdh7qXuSjUOWLlUekYQ= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21b572c66a0_66ae2ab4e5cccf5854542"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 14 Jun 2018 00:23:18 -0000 ----==_mimepart_5b21b572c66a0_66ae2ab4e5cccf5854542 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > @@ -523,6 +532,16 @@ blocks within a stream have been fully processed. ~~~~~~~~~~ {:#fig-header-ack title="Header Acknowledgement"} +An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging +any dynamic table entries that the header block referenced. That is, this +instruction is also processed as a Table Size Synchronize instruction with a Table *State* Synchronize. It's wrong in the figure from that section also. > @@ -489,9 +489,18 @@ After processing a set of instructions on the encoder stream, the decoder will emit a Table State Synchronize instruction on the decoder stream. The instruction begins with the '1' one-bit pattern. The instruction specifies the total number of dynamic table inserts and duplications since the last Table -State Synchronize, encoded as a 7-bit prefix integer. The encoder uses this -value to determine which table entries are vulnerable to head-of-line blocking. -A decoder MAY coalesce multiple synchronization updates into a single update. +State Synchronize or Header Acknowledgement that increased the largest Reading the section here makes me think perhaps having Header Acknowledgement described before TSS. -- 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/1399#pullrequestreview-128607377 ----==_mimepart_5b21b572c66a0_66ae2ab4e5cccf5854542 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -523,6 +532,16 @@ blocks within a stream have been fully processed.
 ~~~~~~~~~~
 {:#fig-header-ack title="Header Acknowledgement"}
 
+An encoder MUST treat receipt of a Header Acknowledgment as also acknowledging
+any dynamic table entries that the header block referenced.  That is, this
+instruction is also processed as a Table Size Synchronize instruction with a

Table State Synchronize. It's wrong in the figure from that section also.

In draft-ietf-quic-qpack.md:

> @@ -489,9 +489,18 @@ After processing a set of instructions on the encoder stream, the decoder will
 emit a Table State Synchronize instruction on the decoder stream.  The
 instruction begins with the '1' one-bit pattern. The instruction specifies the
 total number of dynamic table inserts and duplications since the last Table
-State Synchronize, encoded as a 7-bit prefix integer.  The encoder uses this
-value to determine which table entries are vulnerable to head-of-line blocking.
-A decoder MAY coalesce multiple synchronization updates into a single update.
+State Synchronize or Header Acknowledgement that increased the largest

Reading the section here makes me think perhaps having Header Acknowledgement described before TSS.

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

----==_mimepart_5b21b572c66a0_66ae2ab4e5cccf5854542-- From nobody Wed Jun 13 17:29:42 2018 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 C481C131052 for ; Wed, 13 Jun 2018 17:29:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xloTmo9xIanO for ; Wed, 13 Jun 2018 17:29:31 -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 2FBB3131032 for ; Wed, 13 Jun 2018 17:29:31 -0700 (PDT) Date: Wed, 13 Jun 2018 17:29:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528936170; bh=xzcQyDpzAsSVCQkUJJbkThLioQa+LAI6SvMqgKp7JBs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tpae4YPnuBX38L4ibINQcP712qpTlZ85XjNM1kFd61ZKDlwyqayfY0mFw3+pc8uws ztpXkOourLAppFsYkcu3GMTUuFuaquJrTjzeiaRPSTnxMDAJ3h4qh5zbLEhSV7TBkW oL+kRFXfTAdl4L+oKP8Krdx/V6LM91rl9EnFmoVo= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21b6ea86d28_1abd2b02bcd18f50819f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 14 Jun 2018 00:29:41 -0000 ----==_mimepart_5b21b6ea86d28_1abd2b02bcd18f50819f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. This subsumes 1399 but I'm not sure there's a dependency between them? Might it be cleaner to only change the instruction bits and introduce stream cancellation? > + +A decoder MUST track increases to the largest acknowledged dynamic table entry +caused by acknowledging a header block so that it can correctly generate the +Table State Synchronize instruction. + + +### Stream Cancellation + +A stream that is reset might have multiple outstanding header blocks. A decoder +that receives a stream reset before the end of a stream generates a Stream +Cancellation instruction on the decoder stream. Similarly, a decoder that +abandons reading of a stream needs to signal this using the Stream Cancellation +instruction. This signals to the encoder that all references to the dynamic +table on that stream are no longer outstanding. + +An encoder cannot infer from this acknowledgement that any updates to the s/acknowledgement/instruction/ ? -- 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/1400#pullrequestreview-128608973 ----==_mimepart_5b21b6ea86d28_1abd2b02bcd18f50819f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

This subsumes 1399 but I'm not sure there's a dependency between them? Might it be cleaner to only change the instruction bits and introduce stream cancellation?

In draft-ietf-quic-qpack.md:

> +
+A decoder MUST track increases to the largest acknowledged dynamic table entry
+caused by acknowledging a header block so that it can correctly generate the
+Table State Synchronize instruction.
+
+
+### Stream Cancellation
+
+A stream that is reset might have multiple outstanding header blocks.  A decoder
+that receives a stream reset before the end of a stream generates a Stream
+Cancellation instruction on the decoder stream.  Similarly, a decoder that
+abandons reading of a stream needs to signal this using the Stream Cancellation
+instruction.  This signals to the encoder that all references to the dynamic
+table on that stream are no longer outstanding.
+
+An encoder cannot infer from this acknowledgement that any updates to the

s/acknowledgement/instruction/ ?

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

----==_mimepart_5b21b6ea86d28_1abd2b02bcd18f50819f3-- From nobody Wed Jun 13 17:35:28 2018 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 3E741130FB5 for ; Wed, 13 Jun 2018 17:35:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 khUxlFUX9stu for ; Wed, 13 Jun 2018 17:35:23 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 5E6D9130EBD for ; Wed, 13 Jun 2018 17:35:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528936522; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zJzIq2riUSlcFqeDij4yWNYjNhv3dv4O0XFjFr2ov1k=; b=H9Cju3K3vzVjd7IjgKlVtsP7EarYKDNRo2ogB9TKSvYi3Ggthxnx2qxyQGFVgv7cBd5YNxmv OjUgqZOIxZ8DqxHGUdzis3AiX41ZirwHKEUpQebtDOCAo047Iho0d+/8AP4Icwvhu/FWMFxm NwlSH+H/D0HS/nx/Zrvh2xU9lqM= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b21b849.7f82c6c14630-smtp-out-n03; Thu, 14 Jun 2018 00:35:21 -0000 (UTC) Date: Wed, 13 Jun 2018 17:35:20 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b21b848cc492_76cc2afff9e9fc048298b@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 2fb1a4: Expand Primitives section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21b848cbecf_76cc2afff9e9fc048287a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 00:35:26 -0000 ----==_mimepart_5b21b848cbecf_76cc2afff9e9fc048287a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 2fb1a46449afe7cef6ef01a085ab4e193f1cab4f https://github.com/quicwg/base-drafts/commit/2fb1a46449afe7cef6ef01a085ab4e193f1cab4f Author: Mike Bishop Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Expand Primitives section **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21b848cbecf_76cc2afff9e9fc048287a-- From nobody Wed Jun 13 17:35:33 2018 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 C7AF8130EBD for ; Wed, 13 Jun 2018 17:35:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7XmYP8vWsgtn for ; Wed, 13 Jun 2018 17:35:24 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81C3130EC9 for ; Wed, 13 Jun 2018 17:35:23 -0700 (PDT) Date: Wed, 13 Jun 2018 17:35:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528936523; bh=N4MK+dUhMaG14GEzj02IduxYia2u9nbZfWvnYznB2CE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F86RjpRoYN3/5xi7G6aW66YUZ/vep63FTsVIfjvXI97fxt4/CHGBcVmV3UrGuWxOM BhvI9jTOC+gCM744CWGhC15mxEM81FJgwGnWobhgcEzE7dDQuFCPbwAHkr3RfDTORa nvs+vwtV2R6NYjL4RilBmh8qLWUkKoEFIZGO+DGc= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK: Huffman string compression (#1435) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21b84b2537e_56e52ade765c2f541982b6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 14 Jun 2018 00:35:26 -0000 ----==_mimepart_5b21b84b2537e_56e52ade765c2f541982b6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1435 via #1444. -- 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/1435#event-1680033177 ----==_mimepart_5b21b84b2537e_56e52ade765c2f541982b6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1435 via #1444.

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

----==_mimepart_5b21b84b2537e_56e52ade765c2f541982b6-- From nobody Wed Jun 13 17:35:40 2018 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 2D6DC130EBD for ; Wed, 13 Jun 2018 17:35:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 H_1xXtrMtwsr for ; Wed, 13 Jun 2018 17:35:25 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9936130FAC for ; Wed, 13 Jun 2018 17:35:23 -0700 (PDT) Date: Wed, 13 Jun 2018 17:35:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528936523; bh=cMXbUoFKIZ6PgGJw4YlgQtc0JFe5uMdplBU9NvbjOyc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ftD8XwQ1/1vQGyQeyYPiX6Ugr47hqrfJHNZ4I/PZ8knGMqFI8TKxXNTgIapNb9hIl /AlUwb5Dni207uS6ReCZv/OFuP+MctuYcwghOh45LWey1u5bpcA+dGT6l+gWcuO90W VzQ0wdCjrLcXOtf2E2AJhEwFEH4g7EvbkKQWTEFU= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Expand Primitives section (#1444) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21b84b52035_6e3e2b0314864f60755c9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 14 Jun 2018 00:35:28 -0000 ----==_mimepart_5b21b84b52035_6e3e2b0314864f60755c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1444. -- 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/1444#event-1680033176 ----==_mimepart_5b21b84b52035_6e3e2b0314864f60755c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1444.

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

----==_mimepart_5b21b84b52035_6e3e2b0314864f60755c9-- From nobody Wed Jun 13 17:59:16 2018 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 66DD2130EE1 for ; Wed, 13 Jun 2018 17:59:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Nzo-zg4LVOK0 for ; Wed, 13 Jun 2018 17:59:13 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDDFF128CF3 for ; Wed, 13 Jun 2018 17:59:12 -0700 (PDT) Date: Wed, 13 Jun 2018 17:59:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528937952; bh=gz/MC7CiveNZIPBDthLMq6EoO+TE5cgFaShzSXFnz3I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IvM5wdKbOzLVWmhqpOZg23agguGSSkoxyIqqJ5CG2Gf6UFUbQd/sC9/9Ls5kCzOBb KxNcEWjQnnUxS7DYr33SoBJcWhqpasLrsx9lggp9QRctIuASEX+CAx1H9/8ZAVL5C/ tzmp4s1VAPUD6XUH44eE6Emq1lnmo5un3zc4TuC0= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21bddfebea0_2d922ac14f502f541141b8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 14 Jun 2018 00:59:15 -0000 ----==_mimepart_5b21bddfebea0_2d922ac14f502f541141b8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul >> The core idea here is to use that mechanism to determine if a PN with the CE bit set is acknowledged for the first time. Use of a bit-vector is one of the possible approaches. > > But, that doesn't work unless you are able to ACK each duplication in separate ACKs, as well as having no redundancy in the ACKing. I think that will make QUIC work very poorly if any ACK packet loss is experienced. There need to be some redundancy to ensure that ACK loss, doesn't equal forward loss from the senders perspective. I do not see why you think that it does not work when folding duplication into single ACK. That is something that should have been handled by existing implementations. Folding of the CE bit is a natural extension to that. If I sounded like there would be no deduplication on the receiver side, then I apologize. The requirement to send exactly which PN arrived to with the CE bit _enforces_ the receiver to deduplicate using the ACK queue. Re your second point, the proposed encoding does work under loss, because the sender can tell exactly which newly acknowledged packet was received by the peer with the CE bit set. Consider the case you are sending an ACK_ECN frame for PN 2,3,4 where 3 had the CE bit. The bit vector of the ACK_ECN frame will be 010. When the ACK_ECN frame is retransmitted, the bit vector will once again contain 010. Either of the two ACK_ECN frames that first reaches the sender will be considered as the frame that newly acknowledges PN 3, and the CE bit will be taken into consideration. If the receiver has no duplication detection and an attacker injects a duplicate of packet 4 with CE bit set, the receiver will send ACK_ECN frame with the bit vector set to 011. If that packet reaches the sender first, the sender will take that bit into consideration. However, this is not an issue. It is just that where deduplication is applied is changing from the receiver to the server. And as stated in my first comment, detecting duplication on the sender side is a better guard against an injection attack, because the sender has the logic to recognize an acknowledgement at most once for every one packet it sends, whereas it is hard to implement such complete guard on the receiver side. > I don't see that working reliably during capability checking, especially not when we add ECN black hole mitigation into the mix. It is the sender that knows which of the packets that are marked during the capability check. If all packets are marked, then yes a trustworthy receiver could detect bleaching. But then we need a signal where the receiver tells the sender to stop mark. Sorry for my confusion. Bleaching here is the term that means ECN-CE turning into ECN-CT(0) or ECN-CT(1). For that case and also for blackhole detection, what you would do in the proposed encoding scheme is this: * sender remembers in it's inflight packet map which packets were sent with ECN or with the CE bit set * if sender receives an ACK frame or an ACK_ECN frame that does not indicate that packet had the CE bit set, bleaching is happening * if sender detects loss of the packet that was sent with ECN, there is a blackhole As you can see, support for ECN can be nicely tied to the inflight packet map and the detection of issues become accurate, if we allow the receiver to send back exactly which packet was received with the CE bit set. Note that we do not even need to have a separate phase for detecting these issues. Sender can just periodically send packets with CE bit set, and ignore the signal from receiver expressing that a certain packet was received with the CE bit set, if that packet was sent with the CE bit set. Or if the sender detects a consecutive loss of the packet that had the CE bit set, there is a blackhole. And, thank you for the strawman. My comments in-line. > My strawman if one like to address providing more detailed information on which packets are CE marked, ensure robustness around recovery periods and ensure that sender side verifications work is the following: > * Receiver side suppression of duplicates A limited form of that is inherently part of the bit-vector-based approach. Please see the first lines of this comment. > * An ACK format for ECN where > * ECT(0) and ECT(1) are counters. However, they are variable encoding only the least number of bits needed to detect roll over, i.e. receiver track ACKs of ACKs to determine how many bits this needs to be. Assuming that the sender needs to know the breakdown of the number of packets received without the CE bit set, I would prefer sending that information rather than using a counter, because it simplifies (or eliminates the need for) the logic to detect bleaching / blackhole. > * ECN-CE marks as bit-vector. Only needing to go as far back as there are CE marks. i.e. bit-vector may be shorter than full PN space covered by ACK. Truncation can be considered. > * ACKs are assumed to have redundancy, either all the way to latest ACK of ACKs or at least across the last couple of ACKs. > * ACK loss handling for when there are wholes in ACK information received by the sender due to ACK loss and ECN-CE vector truncation. This is to handle continuous verification. ACK holes will trigger loss response also. I can understand the tendency to have those requirements. Having all that said, let me propose another encoding, that IMO will have all the properties both of us have been looking for. How about expressing ECN information the same way we express gaps? In the current draft, ACK Block is a repetition of two types of "blocks": PNs that are acked and PNs that are not acked (i.e. gap). We can extend it to express 5 types of "blocks": non-ECT acked, ECT(0) acked, ECT(1) acked, ECN-CE acked, gap. In the approach, the definition of ACK Block will become: ``` 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Block (i) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The value of the Block will be calculated as: block_mode = gap (0), non-ECT (1), ECT0 (2), ECT1 (3), ECT-CE(4) block_size = the number of contiguous PNs that were received (or not) under the block_mode block_value = ((block_size - 1) << 3) | block_mode ``` For example, ACK frame that is encoded as `04 00 03 0a 00 04` means: * Largest Acknowledged: 4 * ACK Delay: 0 * ACK Block Count: 3 * first Block (0a): PN 4 and 3 received with ECT0 * second Block (00): gap for one packet * third Block (04): PN 1 received with ECT-CE The benefits of this encoding are: * sender will have complete information on how the packets were received * therefore it is easy to see if there is bleaching / blackhole (see the discussion above) * the overhead of sending ECN information is as same as sending gap * therefore the overhead will be a non-issue, assuming that ECN bit flips will happen as likely as gaps will appear on ECN-unaware networks * no *additional* overhead for supporting ECN * only one ACK frame type * definition of the ACK frame becomes simpler! The downside is that a single-octet Block can only express up to 8 packet numbers, because block_mode takes 3 bits and the varint length bits take 2 bits. I do not think that is an issue considering the fact that the ACK_ECN frame proposed in #1372 increases the size of an acknowlegement by at least 3 octets. But if we want to optimize, we can adopt the PN encoding used in the packet header. -- 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/1439#issuecomment-397133920 ----==_mimepart_5b21bddfebea0_2d922ac14f502f541141b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

The core idea here is to use that mechanism to determine if a PN with = the CE bit set is acknowledged for the first time. Use of a bit-vector is= one of the possible approaches.

But, that doesn't work unless you are able to ACK each duplication in = separate ACKs, as well as having no redundancy in the ACKing. I think tha= t will make QUIC work very poorly if any ACK packet loss is experienced. = There need to be some redundancy to ensure that ACK loss, doesn't equal f= orward loss from the senders perspective.

I do not see why you think that it does not work when folding duplicat= ion into single ACK. That is something that should have been handled by e= xisting implementations. Folding of the CE bit is a natural extension to = that. If I sounded like there would be no deduplication on the receiver s= ide, then I apologize. The requirement to send exactly which PN arrived t= o with the CE bit enforces the receiver to deduplicate using the= ACK queue.

Re your second point, the proposed encoding does work under loss, beca= use the sender can tell exactly which newly acknowledged packet was recei= ved by the peer with the CE bit set.

Consider the case you are sending an ACK_ECN frame for PN 2,3,4 where = 3 had the CE bit. The bit vector of the ACK_ECN frame will be 010. When t= he ACK_ECN frame is retransmitted, the bit vector will once again contain= 010. Either of the two ACK_ECN frames that first reaches the sender will= be considered as the frame that newly acknowledges PN 3, and the CE bit = will be taken into consideration.

If the receiver has no duplication detection and an attacker injects a= duplicate of packet 4 with CE bit set, the receiver will send ACK_ECN fr= ame with the bit vector set to 011. If that packet reaches the sender fir= st, the sender will take that bit into consideration.

However, this is not an issue. It is just that where deduplication is = applied is changing from the receiver to the server. And as stated in my = first comment, detecting duplication on the sender side is a better guard= against an injection attack, because the sender has the logic to recogni= ze an acknowledgement at most once for every one packet it sends, whereas= it is hard to implement such complete guard on the receiver side.

I don't see that working reliably during capability checking, especial= ly not when we add ECN black hole mitigation into the mix. It is the send= er that knows which of the packets that are marked during the capability = check. If all packets are marked, then yes a trustworthy receiver could d= etect bleaching. But then we need a signal where the receiver tells the s= ender to stop mark.

Sorry for my confusion. Bleaching here is the term that means ECN-CE t= urning into ECN-CT(0) or ECN-CT(1).

For that case and also for blackhole detection, what you would do in t= he proposed encoding scheme is this:

  • sender remembers in it's inflight packet map which packets were sent = with ECN or with the CE bit set
  • if sender receives an ACK frame or an ACK_ECN frame that does not ind= icate that packet had the CE bit set, bleaching is happening
  • if sender detects loss of the packet that was sent with ECN, there is= a blackhole

As you can see, support for ECN can be nicely tied to the inflight pac= ket map and the detection of issues become accurate, if we allow the rece= iver to send back exactly which packet was received with the CE bit set.<= /p>

Note that we do not even need to have a separate phase for detecting t= hese issues. Sender can just periodically send packets with CE bit set, a= nd ignore the signal from receiver expressing that a certain packet was r= eceived with the CE bit set, if that packet was sent with the CE bit set.= Or if the sender detects a consecutive loss of the packet that had the C= E bit set, there is a blackhole.

And, thank you for the strawman. My comments in-line.

My strawman if one like to address providing more detailed information= on which packets are CE marked, ensure robustness around recovery period= s and ensure that sender side verifications work is the following:

  • Receiver side suppression of duplicates

A limited form of that is inherently part of the bit-vector-based appr= oach. Please see the first lines of this comment.

  • An ACK format for ECN where
    • ECT(0) and ECT(1) are counters. However, they are variable encoding o= nly the least number of bits needed to detect roll over, i.e. receiver tr= ack ACKs of ACKs to determine how many bits this needs to be.

Assuming that the sender needs to know the breakdown of the number of = packets received without the CE bit set, I would prefer sending that info= rmation rather than using a counter, because it simplifies (or eliminates= the need for) the logic to detect bleaching / blackhole.

* ECN-CE marks as bit-vector. Only needing to go as far back a=
s there are CE marks. i.e. bit-vector may be shorter than full PN space c=
overed by ACK. Truncation can be considered.
  • ACKs are assumed to have redundancy, either all the way to latest ACK= of ACKs or at least across the last couple of ACKs.
  • ACK loss handling for when there are wholes in ACK information receiv= ed by the sender due to ACK loss and ECN-CE vector truncation. This is to= handle continuous verification. ACK holes will trigger loss response als= o.

I can understand the tendency to have those requirements.

Having all that said, let me propose another encoding, that IMO will h= ave all the properties both of us have been looking for. How about expres= sing ECN information the same way we express gaps?

In the current draft, ACK Block is a repetition of two types of "block= s": PNs that are acked and PNs that are not acked (i.e. gap). We can exte= nd it to express 5 types of "blocks": non-ECT acked, ECT(0) acked, ECT(1)= acked, ECN-CE acked, gap.

In the approach, the definition of ACK Block will become:

 0                   1                   2                   3=

 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                          Block (i)                        ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The value of the Block will be calculated as:
block_mode =3D gap (0), non-ECT (1), ECT0 (2), ECT1 (3), ECT-CE(4)
block_size =3D the number of contiguous PNs that were received (or not) u=
nder the block_mode
block_value =3D ((block_size - 1) << 3) | block_mode

For example, ACK frame that is encoded as 04 00 03 0a 00 04 means:

  • Largest Acknowledged: 4
  • ACK Delay: 0
  • ACK Block Count: 3
  • first Block (0a): PN 4 and 3 received with ECT0
  • second Block (00): gap for one packet
  • third Block (04): PN 1 received with ECT-CE

The benefits of this encoding are:

  • sender will have complete information on how the packets were receive= d
    • therefore it is easy to see if there is bleaching / blackhole (see th= e discussion above)
  • the overhead of sending ECN information is as same as sending gap
    • therefore the overhead will be a non-issue, assuming that ECN bit fli= ps will happen as likely as gaps will appear on ECN-unaware networks
      • =
  • no additional overhead for supporting ECN
  • only one ACK frame type
  • definition of the ACK frame becomes simpler!

The downside is that a single-octet Block can only express up to 8 pac= ket numbers, because block_mode takes 3 bits and the varint length bits t= ake 2 bits. I do not think that is an issue considering the fact that the= ACK_ECN frame proposed in #1372 increases the size of an acknowlegement by at least 3= octets. But if we want to optimize, we can adopt the PN encoding used in= the packet header.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b21bddfebea0_2d922ac14f502f541141b8-- From nobody Wed Jun 13 18:28:56 2018 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 C8D13130DC5 for ; Wed, 13 Jun 2018 18:28:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HeDzKZO_ugnb for ; Wed, 13 Jun 2018 18:28:52 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84A1A127598 for ; Wed, 13 Jun 2018 18:28:52 -0700 (PDT) Date: Wed, 13 Jun 2018 18:28:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528939731; bh=TqP9ZFpI+MNA5bJLgqZ7kGf0EZCBaKRpB+Lc7WuVQgI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=A/s7psIVdEGenC9h8Zo7bR/DCnNBGpr4QwM4U0PhbGRFaCBQz1kXAj4/7ZZjkeJ6G X6HwHX1eaCQxcGfqAYe3zWU5D0eda88NQV0e0u2Jdesr5FEyGkcyb4wGPRpW3/mqU5 vdsyxAXSknRhwXXNPuJNG+HrAEotpVdFOS7mb/3c= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21c4d3c2159_50473fd835a0cf88165343"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 01:28:55 -0000 ----==_mimepart_5b21c4d3c2159_50473fd835a0cf88165343 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit So I don't know for certain, I just had the numbers in the end. I suspect that it was just the extra code needed to pull two lots of two bits from the first octet. Obviously having an extra field is more work, but it was more costly than I anticipated. I probably have the code on a branch still... -- 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/1431#issuecomment-397138052 ----==_mimepart_5b21c4d3c2159_50473fd835a0cf88165343 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So I don't know for certain, I just had the numbers in the end. I sus= pect that it was just the extra code needed to pull two lots of two bits = from the first octet. Obviously having an extra field is more work, but = it was more costly than I anticipated. I probably have the code on a bra= nch still...

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b21c4d3c2159_50473fd835a0cf88165343-- From nobody Wed Jun 13 19:08:55 2018 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 17CB9130FBA for ; Wed, 13 Jun 2018 19:08:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 LCE8___8XnR1 for ; Wed, 13 Jun 2018 19:08:50 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BDE71292AD for ; Wed, 13 Jun 2018 19:08:50 -0700 (PDT) Date: Wed, 13 Jun 2018 19:08:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528942129; bh=tibqCNUiS8DnrJ1mYiHqXQcimzlOBqleHn7EHHKo7oM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Hq5Bz+fGn/Q+OmFhfYlSnKbcr965wuaIyZvtqyKWh2QguftbMv1tHmd6JQs4531ak YW30FJP7rc/KySJA5SfnMy4h/ke3vc1Fvvi4PkRm+KzKk2tw+8g8Ks2X6zMqLISu2L O6essx8x1YWY0PgDjGtMoqDzx4eMqfIYcO1WmDy8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21ce31639ac_42502b03f8c96f5431614"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 02:08:54 -0000 ----==_mimepart_5b21ce31639ac_42502b03f8c96f5431614 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The requirement to distinguish new vs. retransmitted is hard. I think that last received is simple and effective enough - any data you send will be acknowledged, and retransmitted if it is not, so the start of the timer is close enough to the point that activity ceases. The other thing to consider here is whether we allow the idle timeout to be asymmetric. That is, it is in effect a statement of "if I don't see a packet from you in N seconds, I will drop state for this connection." On face value, that doesn't help, because the peer with the shorter timer ultimately determines when the connection goes away, but it could allow - for example - a client to make a request without having to worry about a server's idle timeout. Say the client has a 10s timeout and the server has a 30s timeout. Rather than having to probe to see if the connection is still live when the connection gets close to 10s of idleness, the client can just send a request because it knows that the server will still be there (the network path, less so, but it's wise to keep that separate from this). -- 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/1429#issuecomment-397143976 ----==_mimepart_5b21ce31639ac_42502b03f8c96f5431614 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The requirement to distinguish new vs. retransmitted is hard. I think= that last received is simple and effective enough - any data you send wi= ll be acknowledged, and retransmitted if it is not, so the start of the t= imer is close enough to the point that activity ceases.

The other thing to consider here is whether we allow the idle timeout = to be asymmetric. That is, it is in effect a statement of "if I don't se= e a packet from you in N seconds, I will drop state for this connection."= On face value, that doesn't help, because the peer with the shorter tim= er ultimately determines when the connection goes away, but it could allo= w - for example - a client to make a request without having to worry abou= t a server's idle timeout. Say the client has a 10s timeout and the serv= er has a 30s timeout. Rather than having to probe to see if the connecti= on is still live when the connection gets close to 10s of idleness, the c= lient can just send a request because it knows that the server will still= be there (the network path, less so, but it's wise to keep that separate= from this).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b21ce31639ac_42502b03f8c96f5431614-- From nobody Wed Jun 13 19:50:48 2018 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 26B4812D7F8 for ; Wed, 13 Jun 2018 19:50:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 sFRZb575cr1w for ; Wed, 13 Jun 2018 19:50:44 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C786C127332 for ; Wed, 13 Jun 2018 19:50:44 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528944644; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=6UuuN8ywWQG0SMNOdWdYa1Fckqakz0kUTsvgG/hKG+o=; b=dsHolRnjqLjdiXbq1fCWgcHyZYSiaXF3BecT19d62uKH3ZhUhen0ECLaHYObAdP8sCgxDfbv d3/FTujnA/QUzIkpLDfFuHUtVSzzqm8JwwpsyNJRAyaatvxhMxAR3fb77lJQDq5/fLdPEhIx iSilLVeM1fvvDW2YwBc6Z/p/6B4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b21d803.7f453e16f870-smtp-out-n02; Thu, 14 Jun 2018 02:50:43 -0000 (UTC) Date: Wed, 13 Jun 2018 19:50:42 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b21d802dc749_62202b0714c41c108544a@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c80562: exercise editorial discretion Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21d802dc150_62202b0714c41c10853f4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 02:50:47 -0000 ----==_mimepart_5b21d802dc150_62202b0714c41c10853f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/frame_idempotency Home: https://github.com/quicwg/base-drafts Commit: c805623cc0d1984756edea4d21f60cc5e030625f https://github.com/quicwg/base-drafts/commit/c805623cc0d1984756edea4d21f60cc5e030625f Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- exercise editorial discretion Yes, this is probably true, but it isn't necessary. Also, frames that arrive super late aren't generally all that interesting. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21d802dc150_62202b0714c41c10853f4-- From nobody Wed Jun 13 19:50:57 2018 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 1090D12D7F8 for ; Wed, 13 Jun 2018 19:50:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AFTiWpberROA for ; Wed, 13 Jun 2018 19:50:46 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E29C127332 for ; Wed, 13 Jun 2018 19:50:46 -0700 (PDT) Date: Wed, 13 Jun 2018 19:50:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528944645; bh=PgyjG+zzNdHrLPk1DQYMSWYgH6Y1EWatE+/KNlU7q4A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AN7QpNzh7pBxC7uLyl3ifFdmp2HLxnwH3wwYUdDd+1EG7TXREu7hc7sf47Cp2FKSI rOMFhzHs4Pib/0BCoNRPSj7bU2bnVG08ZqI2MECjZlKhWHuwZ9r9SkIwUo5wOe2mSv kxMnhj9rCJx2WSyMDy2C4yNkQzKV5qMhG7YmVqhI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d80592c1c_19432b1d3a5a6f54675a3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 14 Jun 2018 02:50:49 -0000 ----==_mimepart_5b21d80592c1c_19432b1d3a5a6f54675a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. c805623 exercise editorial discretion -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1441/files/10c5e89d9f0a1d0ddaceb70332d35951070f9b26..c805623cc0d1984756edea4d21f60cc5e030625f ----==_mimepart_5b21d80592c1c_19432b1d3a5a6f54675a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • c805623 exercise editorial discretion

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b21d80592c1c_19432b1d3a5a6f54675a3-- From nobody Wed Jun 13 19:51:11 2018 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 81EB1130FF6 for ; Wed, 13 Jun 2018 19:51:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 XOdxni7opcnS for ; Wed, 13 Jun 2018 19:51:09 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0FED127332 for ; Wed, 13 Jun 2018 19:51:08 -0700 (PDT) Date: Wed, 13 Jun 2018 19:51:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528944668; bh=i1a4yg4ObPMjXvlcJdhm7dQoZu6O8oAVODVhnbM0GT4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pEr4FJZ1VluGbI2p9KoEBqPKKPcF2r8MvBL/nrYePzBu/jJfmBcgGNU39FoDQ4nUw VL2TTSXM6d7PZ81iisqQGDI/DJ36Zs3pDrtx3MEnam3AGMFSeeAYgxNGONUWqHX72S v3UBysSrP92PcuvAmstAjQilSB8x+mbIsRByqo8s= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idempotency of Frame Types (#1424) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d81c1da8d_1f883fa95c96af88299fb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 02:51:11 -0000 ----==_mimepart_5b21d81c1da8d_1f883fa95c96af88299fb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1424 via #1441. -- 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/1424#event-1680163158 ----==_mimepart_5b21d81c1da8d_1f883fa95c96af88299fb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1424 via #1441.

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

----==_mimepart_5b21d81c1da8d_1f883fa95c96af88299fb-- From nobody Wed Jun 13 19:51:19 2018 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 BB866130FF2 for ; Wed, 13 Jun 2018 19:51:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.9 X-Spam-Level: X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 QiYF26m5-aHZ for ; Wed, 13 Jun 2018 19:51:11 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 B3290130FF3 for ; Wed, 13 Jun 2018 19:51:09 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528944669; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=xZZWkCj3LCsOpyIP0LlzYcBQRcS04BnZAMC/iG0J0dQ=; b=pgsbdEZV88I7SyPdyZEV7SMiARqU0tXIWIPIgWo+4tuUuV/7w2PhCvp4VSJVI7DZ/Fc4HJFh jdtI17uU0sUsHYkuiagrwDgwK5jEMFjj0swYygGkHlwqyuYDAOWUYGOpZm0F6/HKCpAR3YrF r6DqZaPyTKKhQoVYfL1e9DVosrI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b21d81c.7f0370dc0990-smtp-out-n02; Thu, 14 Jun 2018 02:51:08 -0000 (UTC) Date: Wed, 13 Jun 2018 19:51:08 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b21d81ca8f13_7f832aee1bb8dc041353e@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21d81ca8811_7f832aee1bb8dc041347e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 02:51:14 -0000 ----==_mimepart_5b21d81ca8811_7f832aee1bb8dc041347e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/frame_idempotency Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21d81ca8811_7f832aee1bb8dc041347e-- From nobody Wed Jun 13 19:51:25 2018 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 A6781130FF7 for ; Wed, 13 Jun 2018 19:51:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zJOtu43PvIlL for ; Wed, 13 Jun 2018 19:51:10 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A582130FF2 for ; Wed, 13 Jun 2018 19:51:09 -0700 (PDT) Date: Wed, 13 Jun 2018 19:51:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528944668; bh=fLvKk3EXBdvd5NYFUU7GU5Ti61AEkWYE0q5ycUi5Wd8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yvfEXMPA/C1clVtENLkhNxI6QZoIaUPl1zvBWFFsVRPOEgzIwrA6XWzcj3EGbNs4q dfAMLo65kk8JLJ6Eq3RWpae4gI0d0z5Y2xpQVS9QFIAQoAWvIfmAsT/YWHaeBR1HGr hqeJH7PvGYOr4j74ukhI3JnbdGWQgkW80SSeeWWQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Statement of idempotency (#1441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d81c69be1_3f222b02be0e8f582704"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 02:51:14 -0000 ----==_mimepart_5b21d81c69be1_3f222b02be0e8f582704 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1441. -- 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/1441#event-1680163157 ----==_mimepart_5b21d81c69be1_3f222b02be0e8f582704 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1441.

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

----==_mimepart_5b21d81c69be1_3f222b02be0e8f582704-- From nobody Wed Jun 13 19:53:06 2018 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 A333F130FF2 for ; Wed, 13 Jun 2018 19:53:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FdJG0JYFMCMh for ; Wed, 13 Jun 2018 19:53:03 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A7A812D7F8 for ; Wed, 13 Jun 2018 19:53:03 -0700 (PDT) Date: Wed, 13 Jun 2018 19:53:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528944782; bh=P9uJemicKA9puHwo/sqKI+7CV82/fcjozeUK/X3pBgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KVI7XfCT7HuAr07urY0NO6LY61MpA+nD0e+RxHcLkilREpsy3h2ztaLf/lGhO9gee prt0UB2RnJW4Tp/5Fm89JREJfba6CirSjnSO/mc7yB5nRe2VHdFySpI1UlJ9wbLTxo dN/hUEmtLJMkHDoSQr2X86BNmoj33xUsm6pc7WLA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d88e6c7e7_27362ad1f7916f606921a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 02:53:05 -0000 ----==_mimepart_5b21d88e6c7e7_27362ad1f7916f606921a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -489,9 +489,18 @@ After processing a set of instructions on the encoder stream, the decoder will emit a Table State Synchronize instruction on the decoder stream. The instruction begins with the '1' one-bit pattern. The instruction specifies the total number of dynamic table inserts and duplications since the last Table -State Synchronize, encoded as a 7-bit prefix integer. The encoder uses this -value to determine which table entries are vulnerable to head-of-line blocking. -A decoder MAY coalesce multiple synchronization updates into a single update. +State Synchronize or Header Acknowledgement that increased the largest Yes, but I want to do that later. -- 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/1399#discussion_r195290416 ----==_mimepart_5b21d88e6c7e7_27362ad1f7916f606921a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-qpack.md:

> @@ -489,9 +489,18 @@ After processing a set of instructions on the encoder stream, the decoder will
 emit a Table State Synchronize instruction on the decoder stream.  The
 instruction begins with the '1' one-bit pattern. The instruction specifies the
 total number of dynamic table inserts and duplications since the last Table
-State Synchronize, encoded as a 7-bit prefix integer.  The encoder uses this
-value to determine which table entries are vulnerable to head-of-line blocking.
-A decoder MAY coalesce multiple synchronization updates into a single update.
+State Synchronize or Header Acknowledgement that increased the largest

Yes, but I want to do that later.

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

----==_mimepart_5b21d88e6c7e7_27362ad1f7916f606921a-- From nobody Wed Jun 13 19:54:01 2018 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 72BFC130FF2 for ; Wed, 13 Jun 2018 19:53:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 8ZVtfOEGupCi for ; Wed, 13 Jun 2018 19:53:58 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 0CCAA12D7F8 for ; Wed, 13 Jun 2018 19:53:57 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528944837; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=uQznuIPK0TQ3SehXj2XN4EDIPopIUS/h7Q5ijKPX7+Y=; b=StYjIey0pntAo7Y7U/vVVB19GdMQkpP/3qj7Ad/enxwhtQU3KBirvbKXUeG7T6AknOxUDCAq grc/Q+/mxaZ31uo0wY07ilSCeB8AmBsHLqz3UClnAbXKRQifYlLFyFIJsGa37xoLMP7ZQCBN wCZ08XwqUHooKSSOg6afmqosbDI= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b21d8c4.7f93d11ca2d0-smtp-out-n03; Thu, 14 Jun 2018 02:53:56 -0000 (UTC) Date: Wed, 13 Jun 2018 19:53:55 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b21d8c3a75e7_412f2ac9ec859c0c6689c@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 386d62: State sync, not size sync Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21d8c3a719c_412f2ac9ec859c0c6677"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 02:54:00 -0000 ----==_mimepart_5b21d8c3a719c_412f2ac9ec859c0c6677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/implicit-ack-header-block Home: https://github.com/quicwg/base-drafts Commit: 386d6289be06efc70265e953f2bef3b095b14b65 https://github.com/quicwg/base-drafts/commit/386d6289be06efc70265e953f2bef3b095b14b65 Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- State sync, not size sync **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21d8c3a719c_412f2ac9ec859c0c6677-- From nobody Wed Jun 13 19:54:09 2018 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 98152130FF3 for ; Wed, 13 Jun 2018 19:54:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jnS1Py6ebTx1 for ; Wed, 13 Jun 2018 19:54:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22753131002 for ; Wed, 13 Jun 2018 19:54:03 -0700 (PDT) Date: Wed, 13 Jun 2018 19:54:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528944842; bh=0IQQLvDsT6jvjDEz2ufBUwor0Roi7kz4dQSeDAAD7KU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TJOyfn+JqCzX6E2ol6Bzws2V/DCQA6Xm3tjsVXqmQ46ASZfIACKsldyVL9kNAPRjc D5YW/SZaMyMSF/z8Pi9NN+t0zDxdj3edhIAFG5o2YAZ32N4WW56QWej3lzz/RWMP97 ZxHV1ovHCWqycPMeMHw+q3guJAevTtUP5I8/XmyE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d8ca52452_29a13fd149fe8f80264d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 14 Jun 2018 02:54:05 -0000 ----==_mimepart_5b21d8ca52452_29a13fd149fe8f80264d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 386d628 State sync, not size sync -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1399/files/74fa837a81bea44b9f61a14c96342ee0c4c35985..386d6289be06efc70265e953f2bef3b095b14b65 ----==_mimepart_5b21d8ca52452_29a13fd149fe8f80264d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 386d628 State sync, not size sync

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b21d8ca52452_29a13fd149fe8f80264d5-- From nobody Wed Jun 13 19:57:43 2018 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 3970E130FF2 for ; Wed, 13 Jun 2018 19:57:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JPZRhgob1bQ3 for ; Wed, 13 Jun 2018 19:57:40 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51D0912D7F8 for ; Wed, 13 Jun 2018 19:57:40 -0700 (PDT) Date: Wed, 13 Jun 2018 19:57:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528945059; bh=5fPc74NE85paoskZXdMQBxJYWr4gYeBsPAmfulYbHJw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AznOjj3mJPYbIsqyNN556M0vvj6Bq6JLTcWZoSU6BhP3noCidYXb4VWLZ7jQOcLrU CA4UWl0yH8TFUQhzU32tV47qCXQi/jjgi0evOSlGWT6f0c4TII4GebrgloH5vrQhF2 NcjL8Qb11bT36PQeZ99/26QF1ktl8Cq6qx8T9vSM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21d9a3adcab_26a8f3fd3a017ef7c437fd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 02:57:42 -0000 ----==_mimepart_5b21d9a3adcab_26a8f3fd3a017ef7c437fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > + +A decoder MUST track increases to the largest acknowledged dynamic table entry +caused by acknowledging a header block so that it can correctly generate the +Table State Synchronize instruction. + + +### Stream Cancellation + +A stream that is reset might have multiple outstanding header blocks. A decoder +that receives a stream reset before the end of a stream generates a Stream +Cancellation instruction on the decoder stream. Similarly, a decoder that +abandons reading of a stream needs to signal this using the Stream Cancellation +instruction. This signals to the encoder that all references to the dynamic +table on that stream are no longer outstanding. + +An encoder cannot infer from this acknowledgement that any updates to the This builds on top of #1399 (You can view the changes here: https://github.com/quicwg/base-drafts/compare/implicit-ack-header-block...ack-reset-stream I assumed - incorrectly - that you had already seen these changes, so pointed this at master rather than the other PR. -- 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/1400#discussion_r195290927 ----==_mimepart_5b21d9a3adcab_26a8f3fd3a017ef7c437fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-qpack.md:

> +
+A decoder MUST track increases to the largest acknowledged dynamic table entry
+caused by acknowledging a header block so that it can correctly generate the
+Table State Synchronize instruction.
+
+
+### Stream Cancellation
+
+A stream that is reset might have multiple outstanding header blocks.  A decoder
+that receives a stream reset before the end of a stream generates a Stream
+Cancellation instruction on the decoder stream.  Similarly, a decoder that
+abandons reading of a stream needs to signal this using the Stream Cancellation
+instruction.  This signals to the encoder that all references to the dynamic
+table on that stream are no longer outstanding.
+
+An encoder cannot infer from this acknowledgement that any updates to the

This builds on top of #1399 (You can view the changes here: implicit-ack-header-block...ack-reset-stream I assumed - incorrectly - that you had already seen these changes, so pointed this at master rather than the other PR.

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

----==_mimepart_5b21d9a3adcab_26a8f3fd3a017ef7c437fd-- From nobody Wed Jun 13 19:59:36 2018 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 875D3130FF6 for ; Wed, 13 Jun 2018 19:59:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 JpZc-C7gE43D for ; Wed, 13 Jun 2018 19:59:33 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 E4D4712D7F8 for ; Wed, 13 Jun 2018 19:59:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528945172; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5YVplYrPFYcJZa+V3nDnSaA1+WrV040EOMaM8BMpLKI=; b=QOmA+OYD0oztQ7mXa9ledZmC4rykWeJNA/zeUTbPCNCGkOfZi7IbGXjW2pNbKTIg8gJNY1od EsTieaGq/zGSkssuMHD3l6e7RygQPisa5koMLUbIFzvYJDfpwvTUpqv75jJgcm9Vqo9cnWhe 2fh3mxYdUVV4KUKzwsDoKKy85BE= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b21da13.7f462fa9e090-smtp-out-n02; Thu, 14 Jun 2018 02:59:31 -0000 (UTC) Date: Wed, 13 Jun 2018 19:59:30 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b21da1296a98_78d32b2377e7dc0c651e0@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] f5415c: Itsan instruction Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21da129651f_78d32b2377e7dc0c6506a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 02:59:35 -0000 ----==_mimepart_5b21da129651f_78d32b2377e7dc0c6506a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ack-reset-stream Home: https://github.com/quicwg/base-drafts Commit: f5415c7539d3bfe03c862de9763709b9ad707bb5 https://github.com/quicwg/base-drafts/commit/f5415c7539d3bfe03c862de9763709b9ad707bb5 Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Itsan instruction **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21da129651f_78d32b2377e7dc0c6506a-- From nobody Wed Jun 13 19:59:42 2018 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 A22DD12D7F8 for ; Wed, 13 Jun 2018 19:59:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HXzaBPxSw2Ag for ; Wed, 13 Jun 2018 19:59:34 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A19F130FF3 for ; Wed, 13 Jun 2018 19:59:34 -0700 (PDT) Date: Wed, 13 Jun 2018 19:59:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528945173; bh=lX9y2VqIT4NoyxRcQEzhB4tzgIS1xUVjhG2kDyp8ppY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qnFpNlirJXcFsoT0x6cWZQlfDufyeRRDl+ItBRrDWLXkOIVYOsNBZb1NZvabTLNv1 37PvJHzCBC2JQrkOLYaw/ccqnCHPDRDsf83yS20V8BSCcUWOjDaVDu8ns76yl/dUu8 +xnImywaPpPeEnHmj+F2G0zVO5Zbzgw/BqOxMeSc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21da153c43b_58462aec671c4f5c3196a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 14 Jun 2018 02:59:36 -0000 ----==_mimepart_5b21da153c43b_58462aec671c4f5c3196a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. f5415c7 Itsan instruction -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1400/files/522e81fdd181aca6bfd919aca30633ad35644b31..f5415c7539d3bfe03c862de9763709b9ad707bb5 ----==_mimepart_5b21da153c43b_58462aec671c4f5c3196a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b21da153c43b_58462aec671c4f5c3196a-- From nobody Wed Jun 13 20:05:29 2018 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 B4D1C13101B for ; Wed, 13 Jun 2018 20:05:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 te10XAbCugc4 for ; Wed, 13 Jun 2018 20:05:26 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 3D9F0131004 for ; Wed, 13 Jun 2018 20:05:25 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528945524; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zac0yBrla/w8UbDXZQXg9EtKce422RiOqNW3ZEGzvM4=; b=pigwdSnkv2Nf+JkZi2tS+qsZ+NpF1IkbCP28tz7hILnRYVLSfLoDLOaaPTqawYRY3jw5Urxu 0bbYprr9OGFTZm72Ud6gAIrk8vV0Z8e1R2xGeWqMllCU/m7MMKsA8gGKC93uhfGRzzMWfpYr 6gVURe168HGki7G1CUO7WKSyZE4= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b21d91b.7fd30ad68930-smtp-out-n02; Thu, 14 Jun 2018 02:55:23 -0000 (UTC) Date: Wed, 13 Jun 2018 19:55:23 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b21d91b6ebba_408b2aac9b335c084425a@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 9eb9fd: Acknowledge stream resets too Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21d91b6e4ee_408b2aac9b335c0844177"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 03:05:28 -0000 ----==_mimepart_5b21d91b6e4ee_408b2aac9b335c0844177 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ack-reset-stream Home: https://github.com/quicwg/base-drafts Commit: 9eb9fd5eca8d1c3fc2e02babefa13f930dbbd05b https://github.com/quicwg/base-drafts/commit/9eb9fd5eca8d1c3fc2e02babefa13f930dbbd05b Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Acknowledge stream resets too Closes #1371. Commit: c69c55c2ee72aeef4b30e49d20308e640a7a2fa3 https://github.com/quicwg/base-drafts/commit/c69c55c2ee72aeef4b30e49d20308e640a7a2fa3 Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix figure Commit: e2673ab455141708d25163251ebafefb25f0525a https://github.com/quicwg/base-drafts/commit/e2673ab455141708d25163251ebafefb25f0525a Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Genericize Commit: 969c77bb8ee37f5823f93a77e945f48b68166d4a https://github.com/quicwg/base-drafts/commit/969c77bb8ee37f5823f93a77e945f48b68166d4a Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Plural, not plural Commit: 522e81fdd181aca6bfd919aca30633ad35644b31 https://github.com/quicwg/base-drafts/commit/522e81fdd181aca6bfd919aca30633ad35644b31 Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Editorial Compare: https://github.com/quicwg/base-drafts/compare/50383e497f42...522e81fdd181 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21d91b6e4ee_408b2aac9b335c0844177-- From nobody Wed Jun 13 20:16:09 2018 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 C639513101E for ; Wed, 13 Jun 2018 20:16:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 HgYqqEwxGyEC for ; Wed, 13 Jun 2018 20:16:06 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 0F8C4130FB7 for ; Wed, 13 Jun 2018 20:16:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1528946165; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=/UkZ3anIucfKUzZTYy4Rz0emE3/KP3HaI1k7rjEN0BI=; b=x/m4Imwjp1axK1vHhBIKsAVuKFs7lFA6w7KsZhKnNmxTLMgcLSf6E/3CzCG8MDzAZ7O6mhtI Y0yEAWRZ9uA+GPqoymJfkubrN6iHfG3wqX9qjXyNHThRSEuSabnd1M6dqcBB6EwUq/oZiwP2 MdROwMlqZPHnd1HM45KA9bJNJDk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b21d818.7f7ef15d5c60-smtp-out-n03; Thu, 14 Jun 2018 02:51:04 -0000 (UTC) Date: Wed, 13 Jun 2018 19:51:04 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b21d818df57c_40242afbf1369c10695a6@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 411966: Statement of idempotency Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b21d818df0d9_40242afbf1369c10694d6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 03:16:08 -0000 ----==_mimepart_5b21d818df0d9_40242afbf1369c10694d6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 411966117c5b2a7d235273dda5a587c341bb5376 https://github.com/quicwg/base-drafts/commit/411966117c5b2a7d235273dda5a587c341bb5376 Author: Mike Bishop Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Statement of idempotency Commit: 10c5e89d9f0a1d0ddaceb70332d35951070f9b26 https://github.com/quicwg/base-drafts/commit/10c5e89d9f0a1d0ddaceb70332d35951070f9b26 Author: Mike Bishop Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Re-"framing" Commit: c805623cc0d1984756edea4d21f60cc5e030625f https://github.com/quicwg/base-drafts/commit/c805623cc0d1984756edea4d21f60cc5e030625f Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- exercise editorial discretion Yes, this is probably true, but it isn't necessary. Also, frames that arrive super late aren't generally all that interesting. Commit: 5cdb2b2025706fa92880bce8e6e86a19073e60bf https://github.com/quicwg/base-drafts/commit/5cdb2b2025706fa92880bce8e6e86a19073e60bf Author: Martin Thomson Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1441 from quicwg/transport/frame_idempotency Statement of idempotency Compare: https://github.com/quicwg/base-drafts/compare/2fb1a46449af...5cdb2b202570 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b21d818df0d9_40242afbf1369c10694d6-- From nobody Wed Jun 13 20:17:09 2018 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 87DD313101B for ; Wed, 13 Jun 2018 20:17:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rma5q36ZP7t0 for ; Wed, 13 Jun 2018 20:17:05 -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 B3835130FB7 for ; Wed, 13 Jun 2018 20:17:05 -0700 (PDT) Date: Wed, 13 Jun 2018 20:17:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528946224; bh=k7XvgDqZQM0hmk2qMeOH6fW9UMlkLOQUcTSUED/jFJs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yj+Nz4Ej30GtRfmTcU4lVtd/UIf07NZ16MNGn6UiDGu4HUcrOH9CAjH9uuYCSJCAw tmuV3FC5sTA42pWM+ZNNKexgkzLn76nhDNpSlS9gRXdcK/sxkk27S5jIywsa3gMnNk EGMs8dLvT2xSccvBpSsgjLz4ciyxCkA/2LJOnMlI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21de30e1eb9_75162b1161842f5410062"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 03:17:08 -0000 ----==_mimepart_5b21de30e1eb9_75162b1161842f5410062 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm not sure that this is simpler. If we were going this way, maybe it needs a better encoding than bit-stuffing a varint. Not sure what that looks like though. You could save a whole bit by making it impossible to send two blocks of the same type in a row and encoding the mode as `n = (next_mode - last_mode + 4) % 5` and decoding with `next_mode = (last_mode + n + 6) % 5`. The cost here is that a single ECN-CE-marked datagram costs 3 octets to encode. The benefit is that you have one ACK frame; and if you don't have ECN markings, the overhead is limited to a slightly less efficient encoding of longer sequences of packets (>16 with my hack). ![Seems a little complicated](http://memedad.com/memes/1378271.jpg) -- 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/1439#issuecomment-397157328 ----==_mimepart_5b21de30e1eb9_75162b1161842f5410062 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm not sure that this is simpler. If we were going this way, maybe i= t needs a better encoding than bit-stuffing a varint. Not sure what that= looks like though.

You could save a whole bit by making it impossible to send two blocks = of the same type in a row and encoding the mode as n =3D (next_mode= - last_mode + 4) % 5 and decoding with next_mode =3D (last_= mode + n + 6) % 5. The cost here is that a single ECN-CE-marked d= atagram costs 3 octets to encode. The benefit is that you have one ACK f= rame; and if you don't have ECN markings, the overhead is limited to a sl= ightly less efficient encoding of longer sequences of packets (>16 wit= h my hack).

3D"Seems

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b21de30e1eb9_75162b1161842f5410062-- From nobody Wed Jun 13 20:51:12 2018 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 BD1CD130DCF for ; Wed, 13 Jun 2018 20:51:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 5XpsTMsPCjbx for ; Wed, 13 Jun 2018 20:51:09 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EB45130DC1 for ; Wed, 13 Jun 2018 20:51:09 -0700 (PDT) Date: Wed, 13 Jun 2018 20:51:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528948267; bh=tQe4F0NpH5yORYoPPyRKFrX4psZmiQuqKiSsOmE3pOw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R7XWz7ir+dFddvmWDhV0QyjI2gPsP9K76WFLATLYan6NaPKRELm0hPsYIIT0g6AFn X5S93UzmqSBvjf+OrGTVv2zAXr+zvRzaXkkKn1rLe3hk6zojfg67WZs9ubQ1dxF6vK LNFcTFrhhZOupF1fgmPgG/oBQb3GpHOazLCCmISs= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b21e62be1e2c_1f8e3fa95c96af882717fe"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 14 Jun 2018 03:51:11 -0000 ----==_mimepart_5b21e62be1e2c_1f8e3fa95c96af882717fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson > I'm not sure that this is simpler. Yeah. What I was trying to say by stating that the ACK frame becomes simpler is that we can eliminate the distinction between "first ack block", "additional ack block", "gap" by having type assigned to each block. > You could save a whole bit by making it impossible to send two blocks of the same type in a row and encoding the mode as `n = (next_mode - last_mode + 4) % 5` and decoding with `next_mode = (last_mode + n + 1) % 5`. That definitely works. I had some hesitation against making the interpretation of the mode depend on the mode of the previous block, but that might be fine considering the fact that where the block begins depends on the bit pattern of the previous block (which is a varint). > The cost here is that a single ECN-CE-marked datagram costs 3 octets to encode. The benefit is that you have one ACK frame; and if you don't have ECN markings, the overhead is limited to a slightly less efficient encoding of longer sequences of packets (>16 with my hack). Yes. And my argument regarding the cost is that spending 3 octets should be fine, because we spend the same amount to express a gap. If it is not fine, we should reconsider how we express gaps. -- 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/1439#issuecomment-397162080 ----==_mimepart_5b21e62be1e2c_1f8e3fa95c96af882717fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson

I'm not sure that this is simpler.

Yeah. What I was trying to say by stating that the ACK frame becomes s= impler is that we can eliminate the distinction between "first ack block"= , "additional ack block", "gap" by having type assigned to each block.

You could save a whole bit by making it impossible to send two blocks = of the same type in a row and encoding the mode as n =3D (next_mode= - last_mode + 4) % 5 and decoding with next_mode =3D (last_= mode + n + 1) % 5.

That definitely works. I had some hesitation against making the interp= retation of the mode depend on the mode of the previous block, but that m= ight be fine considering the fact that where the block begins depends on = the bit pattern of the previous block (which is a varint).

The cost here is that a single ECN-CE-marked datagram costs 3 octets t= o encode. The benefit is that you have one ACK frame; and if you don't ha= ve ECN markings, the overhead is limited to a slightly less efficient enc= oding of longer sequences of packets (>16 with my hack).

Yes. And my argument regarding the cost is that spending 3 octets shou= ld be fine, because we spend the same amount to express a gap. If it is n= ot fine, we should reconsider how we express gaps.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b21e62be1e2c_1f8e3fa95c96af882717fe-- From nobody Thu Jun 14 03:23:08 2018 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 BC5A5130EEC for ; Thu, 14 Jun 2018 03:23:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DvsG28WQChFk for ; Thu, 14 Jun 2018 03:23:04 -0700 (PDT) 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 B1C1F130EBE for ; Thu, 14 Jun 2018 03:23:04 -0700 (PDT) Date: Thu, 14 Jun 2018 03:23:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528971783; bh=scQ9rsCGipd8GgOD6NjekNSoIy660LdIl9sS5pJONyM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pU/wF15/Zw1bqv6egDVA5n+qw57t6rRM+7PtrYSW7hVYiG2iaT+8Jd++V/Y4lro78 Sq9MPSo0p4O4m7UrjqvHhTj46DELA1GpcpeGIVUduKinvg/UsVjyhLK9FbXXsjbIqL h87ygi5QsutpjArvP7UlQr2pcxUtecAwcjf7uXW8= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b224207c0bb5_5f953ff865acaf88333388"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Thu, 14 Jun 2018 10:23:07 -0000 ----==_mimepart_5b224207c0bb5_5f953ff865acaf88333388 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho I think I better understand your thinking, but I am still uncertain that I fully understand. So lets see if I understand correctly how the receiver would act in the case of a packet duplications happening. So the receiver at the point of sending an ACK has received PN=2,3,4 where 4 has a CE mark. Then the ACK will say: Largest PN=4, length=3, CE vector = 001. But then arrives PN=4, 5, 5 before it is time to send the next ACK. So the duplicate of PN=4 has ECN=ECT(0), and first 5 has ECT(0) and second ECN-CE set. Thus the ACK will be: Largest PN=5, length 4, CE vector 0001? In this case the sender doesn't see that PN=5 was duplicated with different CE values. Or do you say that this must be sent as two ACKs, where the first is: Largest PN=5, length 4, CE vector 0000 and the next: Largest PN=5, length 4, CE vector 0001 So any duplication must trigger ACKing? The issues I see with this, if I have correctly understood it are: * Packet duplication results in additional ACKs * In the first case where the CE marks are in the first arrival and then not in the late coming duplication an ACK loss of the first will mask the CE mark. * Also in the case of ACK loss of the first PN=5 ACK will result in that the sender can't know if this CE mark was present in the lost ACK or not, thus resulting in an uncertainty for a sender if an CE mark is more likely an attack packet. As late remarked packets a bigger risk for the attack included in the security consideration. When it comes to bleaching, we are not only considering ECN-CE to ECT but also ECT to Not-ECT. The later more relevant when it comes to the capability check as networks that don't handle ECN correctly usually sets all the ECN bits to Not-ECT independently of value. Thus we do need to determine also when some packets has not been marked at the receiver. So, I see your proposed format work for the purpose of the sender learn the received value as long as there are no packet duplication. I still don't see this format helping with the issues that arise with packet duplication. Then you would need yet another set of modes saying duplicate with which of the 4 ECN values. >From my perspective receiver suppressing duplicated packets are a work saver for the receiver. It doesn't need to do more than PN decryption for the packet. The ECN field of the later packets are of very limited value. And the receiver requirement for implementing this is very low. And if you are not suppressing duplicated packets early, then you will have to consider what you do with each individual frame type. Is it safe to process a duplicate or do you need to suppress it at frame type level. To me it opens up the implementation to much more attacks. -- 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/1439#issuecomment-397246970 ----==_mimepart_5b224207c0bb5_5f953ff865acaf88333388 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho I think I better understand y= our thinking, but I am still uncertain that I fully understand. So lets s= ee if I understand correctly how the receiver would act in the case of a = packet duplications happening.

So the receiver at the point of sending an ACK has received PN=3D2,3,4= where 4 has a CE mark. Then the ACK will say: Largest PN=3D4, length=3D= 3, CE vector =3D 001.

But then arrives PN=3D4, 5, 5 before it is time to send the next ACK. = So the duplicate of PN=3D4 has ECN=3DECT(0), and first 5 has ECT(0) and s= econd ECN-CE set. Thus the ACK will be:
Largest PN=3D5, length 4, CE vector 0001?

In this case the sender doesn't see that PN=3D5 was duplicated with di= fferent CE values. Or do you say that this must be sent as two ACKs, wher= e the first is:
Largest PN=3D5, length 4, CE vector 0000 and the next:
Largest PN=3D5, length 4, CE vector 0001
So any duplication must trigger ACKing?

The issues I see with this, if I have correctly understood it are:

=
  • Packet duplication results in additional ACKs
  • In the first case where the CE marks are in the first arrival and the= n not in the late coming duplication an ACK loss of the first will mask t= he CE mark.
  • Also in the case of ACK loss of the first PN=3D5 ACK will result in t= hat the sender can't know if this CE mark was present in the lost ACK or = not, thus resulting in an uncertainty for a sender if an CE mark is more = likely an attack packet. As late remarked packets a bigger risk for the a= ttack included in the security consideration.

When it comes to bleaching, we are not only considering ECN-CE to ECT = but also ECT to Not-ECT. The later more relevant when it comes to the cap= ability check as networks that don't handle ECN correctly usually sets al= l the ECN bits to Not-ECT independently of value. Thus we do need to dete= rmine also when some packets has not been marked at the receiver. So, I s= ee your proposed format work for the purpose of the sender learn the rece= ived value as long as there are no packet duplication. I still don't see = this format helping with the issues that arise with packet duplication. T= hen you would need yet another set of modes saying duplicate with which o= f the 4 ECN values.

From my perspective receiver suppressing duplicated packets are a work= saver for the receiver. It doesn't need to do more than PN decryption fo= r the packet. The ECN field of the later packets are of very limited valu= e. And the receiver requirement for implementing this is very low. And if= you are not suppressing duplicated packets early, then you will have to = consider what you do with each individual frame type. Is it safe to proce= ss a duplicate or do you need to suppress it at frame type level. To me i= t opens up the implementation to much more attacks.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b224207c0bb5_5f953ff865acaf88333388-- From nobody Thu Jun 14 04:05:52 2018 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 C5F6E130E11 for ; Thu, 14 Jun 2018 04:05:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 pvg4O4JDSjRm for ; Thu, 14 Jun 2018 04:05:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDF09130E0A for ; Thu, 14 Jun 2018 04:05:48 -0700 (PDT) Date: Thu, 14 Jun 2018 04:05:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528974347; bh=GlWjF3R7wKevnyL8Ao3ZakFSPdxvhR1aFbAupm68XRo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=awdmWS3h4cYhxYLc5WYxR2sHXqgwQuuO86KpnviSqF3/qb1FIdHYYASvrR9bMKCyM hOMCfyqNu1PwbTnYQFJnWHg7u6QDv+Dme6uZ067Ie50HhVGWuq0GJqQw7s+jrznrzU MhNmJNcekaBLBhZDDYCHBADONPJh2/FsACTa79LY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b224c0bc325b_4d6d3fd9feb8ef8011249a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 11:05:51 -0000 ----==_mimepart_5b224c0bc325b_4d6d3fd9feb8ef8011249a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't thank I get the entire concept here but I'm wondering: Assume receiver does not detect or reject duplicate packets, but it does track an ACK backlog and there has some natural ACK dectection capability. If packet 4 in the above example first sets CE, this will be visible in the backlog. A second packet 4 without CE can then see that 4 is already pending ACK and can choose to a) overwrite the CE bit, b) do nothing since a packet is present, or c) use inclusive OR on the CE bit. If packet 4 is not in the backlog when packet 4 v2 arrives then it has already been ACK'ed leaving it to the sender, or it never received packet 4 v1. In either case it it business as usual. Now, assume the receiver does reject duplicates by tracking more than the latest ACK backlog and that it simply drops any later receiver packets. In this case this corresponds to case b) in the above. The question is then - if the above is reasonable - how should a second update to the CE bit be handled receiver side, when the sender is prepared to handle duplicate ACKS / CE. Is replace, drop, or OR the proper approach? -- 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/1439#issuecomment-397256856 ----==_mimepart_5b224c0bc325b_4d6d3fd9feb8ef8011249a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I don't thank I get the entire concept here but I'm wondering:

Assume receiver does not detect or reject duplicate packets, but it do= es track an ACK backlog and there has some natural ACK dectection capabil= ity.

If packet 4 in the above example first sets CE, this will be visible i= n the backlog. A second packet 4 without CE can then see that 4 is alread= y pending ACK and can choose to a) overwrite the CE bit, b) do nothing si= nce a packet is present, or c) use inclusive OR on the CE bit.

If packet 4 is not in the backlog when packet 4 v2 arrives then it has= already been ACK'ed leaving it to the sender, or it never received packe= t 4 v1. In either case it it business as usual.

Now, assume the receiver does reject duplicates by tracking more than = the latest ACK backlog and that it simply drops any later receiver packet= s. In this case this corresponds to case b) in the above.

The question is then - if the above is reasonable - how should a secon= d update to the CE bit be handled receiver side, when the sender is prepa= red to handle duplicate ACKS / CE. Is replace, drop, or OR the proper app= roach?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b224c0bc325b_4d6d3fd9feb8ef8011249a-- From nobody Thu Jun 14 04:12:15 2018 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 28395130E0A for ; Thu, 14 Jun 2018 04:12:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EqGlqeu0voyl for ; Thu, 14 Jun 2018 04:12:11 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C18130F3F for ; Thu, 14 Jun 2018 04:12:11 -0700 (PDT) Date: Thu, 14 Jun 2018 04:12:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528974730; bh=JjPQuQzYPKk+/vjjrHntc5TQAuIc8d/FShgEqtMrITo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F20ua33L7CJl3c/pXBSnQXD5iMliLwe2JhpcItjKIAI/8w0wVy94bjxxVLPU7kfUS +DdLbQhTVciB42wjnv+YPtPmMSoN887ozyBH3YCaFGePkoPVK2mohRGjmZhwA1nw+L Xse1zeexKBrWH9ZEklMXy7IO38rLFFXBXwQTstvs= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b224d8a95956_45d12b06e8faaf545417c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 11:12:15 -0000 ----==_mimepart_5b224d8a95956_45d12b06e8faaf545417c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On the more general question of receiver duplicate tracking: yes I agree that not tracking duplicates probably opens up a lot of vulnerabilities and places an additional burden on the implementation (though a hostile peer could just repeat frames in new packets, so some robustness is required regardless). That said, duplicate detection is a major burden of the receiver because packet numbers can in principle have arbitrary gaps so a hash table is not safe, a lookup table will not cover the full range, and a binary tree/range tree can consume a lot of memory if every second packet is a gap. By allowing duplicates to slip through, a duplicate filter can be made much simpler, for example by hashing the last N packets and dropping any hash table collisions, or use any other simplified robust imprecise detector. The sender generally has more book-keeping, but it knows exactly which packets it sends can therefore optimize its data structure accordingly. Only the ACKs add some uncertainty. -- 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/1439#issuecomment-397258455 ----==_mimepart_5b224d8a95956_45d12b06e8faaf545417c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On the more general question of receiver duplicate tracking: yes I agr= ee that not tracking duplicates probably opens up a lot of vulnerabilitie= s and places an additional burden on the implementation (though a hostile= peer could just repeat frames in new packets, so some robustness is requ= ired regardless).

That said, duplicate detection is a major burden of the receiver becau= se packet numbers can in principle have arbitrary gaps so a hash table is= not safe, a lookup table will not cover the full range, and a binary tre= e/range tree can consume a lot of memory if every second packet is a gap.=

By allowing duplicates to slip through, a duplicate filter can be made= much simpler, for example by hashing the last N packets and dropping any= hash table collisions, or use any other simplified robust imprecise dete= ctor.

The sender generally has more book-keeping, but it knows exactly which= packets it sends can therefore optimize its data structure accordingly. = Only the ACKs add some uncertainty.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b224d8a95956_45d12b06e8faaf545417c-- From nobody Thu Jun 14 05:47:37 2018 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 B3B54131136 for ; Thu, 14 Jun 2018 05:47:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TI8x5875PMwI for ; Thu, 14 Jun 2018 05:47:33 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 891A0130F53 for ; Thu, 14 Jun 2018 05:47:33 -0700 (PDT) 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=aVIuy79pef7pUg3QufrcciY7CKo=; b=kDf3OUQ9JJ6rGW3b 300burzPL1yv7CaXaM4cTjqgPLtbuOBN7a4S6QHHLxQUe59dmxx+GaIHITOYdBd5 7FM3MfGdn7xt6yd5pbDQecrGCevRUK4MhrFcIC/YUselivXCciBSnIPUQZy3WHLC fiL4zKVb1DhoONgyfxo+bNtt7W4= Received: by filter0649p1las1.sendgrid.net with SMTP id filter0649p1las1-5953-5B2263E3-31 2018-06-14 12:47:31.701553714 +0000 UTC Received: from github-lowworker7-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0023p1mdw1.sendgrid.net (SG) with ESMTP id WOw1z9QbTc--6FNNSnmrZw for ; Thu, 14 Jun 2018 12:47:30.955 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker7-cp1-prd.iad.github.net (Postfix) with ESMTP id 974FAA1D3C for ; Thu, 14 Jun 2018 05:47:30 -0700 (PDT) Date: Thu, 14 Jun 2018 12:47:31 +0000 (UTC) From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2263e2956de_30ea3fc4087daf804688e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0NTR3+nrjXOLGliO+o+W73ZEC0nsLnDOPGet fb97H7kiVxtiDbO3A7sfbbtkSYAMIbPIg6VbsZUPCvTu5P86vaISxbXkbjIb1iFfe/OLmuZL+tQRob HW4/GAiwgbbG+NHOBU0RmpVL6hJRLxC59As4yXjKXavzwaer5VrrMeSIn3nXgfbTHJC1pl18nL3x1o A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 12:47:36 -0000 ----==_mimepart_5b2263e2956de_30ea3fc4087daf804688e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > So the receiver at the point of sending an ACK has received PN=2,3,4 where 4 has a CE mark. Then the ACK will say: Largest PN=4, length=3, CE vector = 001. > > But then arrives PN=4, 5, 5 before it is time to send the next ACK. So the duplicate of PN=4 has ECN=ECT(0), and first 5 has ECT(0) and second ECN-CE set. Thus the ACK will be: Largest PN=5, length 4, CE vector 0001? > https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397246970 by @gloinul I'd assume that the second ACK will contain CE vector of 0010. Quoting what @mikkelfj says, the specification can require one of the three behaviors. My understanding is that _b_ is the behavior we want in order to mitigate the impact of injection attacks racing against the original packet. > Assume receiver does not detect or reject duplicate packets, but it does track an ACK backlog and there has some natural ACK dectection capability. > If packet 4 in the above example first sets CE, this will be visible in the backlog. A second packet 4 without CE can then see that 4 is already pending ACK and can choose to a) overwrite the CE bit, b) do nothing since a packet is present, or c) use inclusive OR on the CE bit. > https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397256856 @mikkelfj > From my perspective receiver suppressing duplicated packets are a work saver for the receiver. > https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397246970 @gloinul A receiver can suppress duplicates to some extent, but it can never be perfect. I do not think it is a good idea to require receivers to implement complicated countermeasures against packet injection attacks for two reasons: 1) it's not enforceable 2) having complex requirement will take people away from implementing ECN support. Sending back the signal that tells which PN arrived with CE bit set simplifies the architecture at the same time giving us a guaranteed level of protection. See https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397258455 by @mikkelfj. > It doesn't need to do more than PN decryption for the packet. > https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397246970 by @gloinul The receiver is required to decrypt the payload even if it has seen the PN before, unless it knows that the payload is identical in some other ways (e.g. by comparing the hash of the payload). Please refer to [QUIC-TLS draft section 10.3](https://quicwg.org/base-drafts/draft-ietf-quic-tls.html#rfc.section.10.3). > And if you are not suppressing duplicated packets early, then you will have to consider what you do with each individual frame type. Is it safe to process a duplicate or do you need to suppress it at frame type level. To me it opens up the implementation to much more attacks. > https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397246970 by @gloinul It does not. Frames are guaranteed to be idempotent. See #1424. They need to be idempotent because there is no reliable way for a receiver to tell if a packet it has received is a duplicate. -- 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/1439#issuecomment-397281950 ----==_mimepart_5b2263e2956de_30ea3fc4087daf804688e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So the receiver at the point of sending an ACK has received PN=3D2,3,4 w= here 4 has a CE mark. Then the ACK will say: Largest PN=3D4, length=3D3, CE= vector =3D 001.

But then arrives PN=3D4, 5, 5 before it is time to send the next ACK. So= the duplicate of PN=3D4 has ECN=3DECT(0), and first 5 has ECT(0) and secon= d ECN-CE set. Thus the ACK will be:
Largest PN=3D5, length 4, CE vector 0001?
= #1439 (comment) by @gloinul

I'd assume that the second ACK will contain CE vector of 0010.

Quoting what @mikkelfj says, the specifi= cation can require one of the three behaviors. My understanding is that b is the behavior we want in order to mitigate the impact of injectio= n attacks racing against the original packet.

Assume receiver does not detect or reject duplicate packets, but it does= track an ACK backlog and there has some natural ACK dectection capability.=
If packet 4 in the above example first sets CE, this will be visible in the= backlog. A second packet 4 without CE can then see that 4 is already pendi= ng ACK and can choose to a) overwrite the CE bit, b) do nothing since a pac= ket is present, or c) use inclusive OR on the CE bit.
= #1439 (comment) @mikkelfj

From my perspective receiver suppressing duplicated packets are a work s= aver for the receiver.
= #1439 (comment) @gloinul

A receiver can suppress duplicates to some extent, but it can never be p= erfect.

I do not think it is a good idea to require receivers to implement compl= icated countermeasures against packet injection attacks for two reasons: 1)= it's not enforceable 2) having complex requirement will take people away f= rom implementing ECN support.

Sending back the signal that tells which PN arrived with CE bit set simp= lifies the architecture at the same time giving us a guaranteed level of pr= otection. See #1439 (comment) by @mikkelfj<= /a>.

It doesn't need to do more than PN decryption for the packet.
= #1439 (comment) by @gloinul

The receiver is required to decrypt the payload even if it has seen the = PN before, unless it knows that the payload is identical in some other ways= (e.g. by comparing the hash of the payload). Please refer to QUIC-TLS draft section 10.3.

And if you are not suppressing duplicated packets early, then you will h= ave to consider what you do with each individual frame type. Is it safe to = process a duplicate or do you need to suppress it at frame type level. To m= e it opens up the implementation to much more attacks.
= #1439 (comment) by @gloinul

It does not. Frames are guaranteed to be idempotent. See #1424.

They need to be idempotent because there is no reliable way for a receiv= er to tell if a packet it has received is a duplicate.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b2263e2956de_30ea3fc4087daf804688e1-- From nobody Thu Jun 14 06:03:38 2018 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 968DF13114C for ; Thu, 14 Jun 2018 06:03:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jwqVklJi5fuz for ; Thu, 14 Jun 2018 06:03:35 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F31C5131152 for ; Thu, 14 Jun 2018 06:03:31 -0700 (PDT) Date: Thu, 14 Jun 2018 06:03:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528981409; bh=5IMjm2wd75V0qq1vv4X60B/BSkKqz9GIX30iXB6hOCQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lIuyRqejoA+xbrrRXbmyb/CXm+ZRzkZNm4WjMhImw08EIDYYa0a+Rd81mQcddpxGb q6cgZ15z+ATy2g3zm4HmIPEQ+a7TJRpkFmPdCzULsksXxMZTp2VaZ8LhLVoYiCBqDL krldiDD1rf88VkVl8F4E3lh/F+CYq6Yj7QIAoiDI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2267a1bc390_5f6d3f945102af88236e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 13:03:37 -0000 ----==_mimepart_5b2267a1bc390_5f6d3f945102af88236e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > A receiver can suppress duplicates to some extent, but it can never be perfect. and > They need to be idempotent because there is no reliable way for a receiver to tell if a packet it has received is a duplicate. this is not quite true if one choose not to receive packets with packet numbers below a certain threshold. Above the threshold duplicates can be perfectly filtered and below the threshold they can also be perfectly filtered, but below the threshold non-duplicates might also get filtered. However, in this case fast retransmission will likely already have a new packet inbound with similar content. -- 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/1439#issuecomment-397287841 ----==_mimepart_5b2267a1bc390_5f6d3f945102af88236e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A receiver can suppress duplicates to some extent, but it can never be= perfect.

and

They need to be idempotent because there is no reliable way for a rece= iver to tell if a packet it has received is a duplicate.

this is not quite true if one choose not to receive packets with packe= t numbers below a certain threshold. Above the threshold duplicates can b= e perfectly filtered and below the threshold they can also be perfectly f= iltered, but below the threshold non-duplicates might also get filtered. = However, in this case fast retransmission will likely already have a new = packet inbound with similar content.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2267a1bc390_5f6d3f945102af88236e5-- From nobody Thu Jun 14 06:11:57 2018 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 0D7C213114C for ; Thu, 14 Jun 2018 06:11:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ujseug4JtCbN for ; Thu, 14 Jun 2018 06:11:53 -0700 (PDT) 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 9D124131156 for ; Thu, 14 Jun 2018 06:11:52 -0700 (PDT) Date: Thu, 14 Jun 2018 06:11:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528981911; bh=Q4nQNC1JVjr4rf/EbQkJrTy0wW6WLVgVLcCQFutpr9w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=axkIOMyvIGWm9DnzmA5gSEZY3Wp1y/BwJtrgDrpwmxAevYQO11gdxAuZt80VxoVg2 fjdUR0uoqpz+VVNDthUnEN4/fwsvIWJsJbANxdjovj0uslSwjzW+4bVqZxTdnAszo1 L5KD8xRyMoNswpOwBLShbjkKiygyWgL5RqB7IOqA= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b226997ac47e_1bda2aace732af5018052b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 14 Jun 2018 13:11:57 -0000 ----==_mimepart_5b226997ac47e_1bda2aace732af5018052b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj That's true. Thank you for pointing that out. OTOH, I would argue that we do not want every QUIC stack to implement such duplication detection logic, because it is complex, memory-consuming, and fragile (i.e. there is a risk of triggering a loss event if you set the threshold too small). -- 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/1439#issuecomment-397290749 ----==_mimepart_5b226997ac47e_1bda2aace732af5018052b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj That's true. Thank you f= or pointing that out. OTOH, I would argue that we do not want every QUIC = stack to implement such duplication detection logic, because it is comple= x, memory-consuming, and fragile (i.e. there is a risk of triggering a lo= ss event if you set the threshold too small).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b226997ac47e_1bda2aace732af5018052b-- From nobody Thu Jun 14 06:20:46 2018 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 78825130E21 for ; Thu, 14 Jun 2018 06:20:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7kEOL8mVdhfs for ; Thu, 14 Jun 2018 06:20:43 -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 A76CE130DEF for ; Thu, 14 Jun 2018 06:20:43 -0700 (PDT) Date: Thu, 14 Jun 2018 06:20:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528982443; bh=3Fj8FplHd5gCwoif6liF/a9wFQTUSrb7Cutq61BL3HU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p1P7Y3cjiGmtL7rPN1h/a4opBoZvE+Ba9Fxi6y0eGqOYHV3hIY757DdAjxiLRuaHM /jYFUpRxrUmRqaN5dWtbwnrpv+gpoCqoCs/sqQxmqFHRWPczLZJd8WvUEO8CCxnFhd WkXBQUBWGsIanV6OYujdsViLjmo+m14X/8c3NVEI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b226bab89aa_22abd3fbc05d9af844592a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 13:20:46 -0000 ----==_mimepart_5b226bab89aa_22abd3fbc05d9af844592a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Right, just pointing out facts. It is new to me that an hash table based cache could filter duplicates becuase frames are now idempotent. I think this could be a really good solution, but it does require that CE does not require filtering, or at least that it is tolerant to a degree. -- 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/1439#issuecomment-397293558 ----==_mimepart_5b226bab89aa_22abd3fbc05d9af844592a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Right, just pointing out facts. It is new to me that an hash table bas= ed cache could filter duplicates becuase frames are now idempotent. I thi= nk this could be a really good solution, but it does require that CE does= not require filtering, or at least that it is tolerant to a degree.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b226bab89aa_22abd3fbc05d9af844592a-- From nobody Thu Jun 14 06:26:59 2018 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 B144F13114C for ; Thu, 14 Jun 2018 06:26:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 8KFSg7wvzLqe for ; Thu, 14 Jun 2018 06:26:46 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4813130E21 for ; Thu, 14 Jun 2018 06:26:45 -0700 (PDT) Date: Thu, 14 Jun 2018 06:26:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528982804; bh=mrKQNEr4M4J9PqJQxXS9ggMSPxOJPju0PewoIRYJR1Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dRDNtNsagWlJdbUmlR58r5CdocvieFd0NGhPxVwz1oXfszDsulsHZe9xTyzIldMwH HGOZYg/ExveAdqryy5NmZj0fhTXhhNJAxgabZPWw8uSpcsjX/p+fkjz7/6M5SDsOUl 21lyJhuAR/viK/11INUhv4awhadYbaUUsPNjqyrU= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b226d14d77fd_489c3fdd499bef7c1228cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 13:26:57 -0000 ----==_mimepart_5b226d14d77fd_489c3fdd499bef7c1228cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @larseggert this is where your bloom filter comes in handy: just define epochs for the filters lifetime and check duplicates against the two most recent bloom filter epochs and let idempentency deal with false positives. Any encrypted bits could be used directly to index a bloom filter. For example if you have width 256 bits, you can choose the first four encrypted bytes to index a bit in the bloom filter (do some math to get the probabilities right). Eventually the filter gets too densely populated and a new epoch is needed. -- 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/1439#issuecomment-397295271 ----==_mimepart_5b226d14d77fd_489c3fdd499bef7c1228cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@larseggert this is where your b= loom filter comes in handy: just define epochs for the filters lifetime a= nd check duplicates against the two most recent bloom filter epochs and l= et idempentency deal with false positives. Any encrypted bits could be us= ed directly to index a bloom filter. For example if you have width 256 bi= ts, you can choose the first four encrypted bytes to index a bit in the b= loom filter (do some math to get the probabilities right). Eventually the= filter gets too densely populated and a new epoch is needed.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b226d14d77fd_489c3fdd499bef7c1228cf-- From nobody Thu Jun 14 06:32:07 2018 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 0F440130E78 for ; Thu, 14 Jun 2018 06:32:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 SoHvu-C9G8DU for ; Thu, 14 Jun 2018 06:32:03 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EE48130E25 for ; Thu, 14 Jun 2018 06:32:03 -0700 (PDT) Date: Thu, 14 Jun 2018 06:32:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528983122; bh=LBtn76G/5vkAFQBiOP+8Kc5HZZti4YaL6TR0n7w3Km8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cxTPO5yuDZ9MxHdf14LviZ6iW+crLqPPrau9seGknX5+xVcVsdbBMJaOK3rKvCaJs iSSKu4U2n17GpfayPESEw+A+R78785ZDNbkJ5uey+AcqMqusYoFMZkGQOpQB2xqbGh YoXSKmfHDM50ixkSMQbEGDtwQz+/2m3X4xugLtlM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b226e529f70d_64c3fb9dbf74f8410477b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 13:32:06 -0000 ----==_mimepart_5b226e529f70d_64c3fb9dbf74f8410477b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit doh - bloomfitlers won't work. A filter can have false negatives, but not false positives unless one wants to increase packet loss. -- 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/1439#issuecomment-397296986 ----==_mimepart_5b226e529f70d_64c3fb9dbf74f8410477b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

doh - bloomfitlers won't work. A filter can have false negatives, but not false positives unless one wants to increase packet loss.

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

----==_mimepart_5b226e529f70d_64c3fb9dbf74f8410477b-- From nobody Thu Jun 14 07:11:58 2018 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 726D4130DCA for ; Thu, 14 Jun 2018 07:11:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 9L_CUZBOM8ur for ; Thu, 14 Jun 2018 07:11:54 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23B9612777C for ; Thu, 14 Jun 2018 07:11:54 -0700 (PDT) Date: Thu, 14 Jun 2018 07:11:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528985513; bh=90RhRXjC6Ft9/rWQCImLoc+NBL0apRrfIkY8HbB32RU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pVLr/hGszOxJLKJxoem7lEr8CiV5qtuQsVgD7zCQ3GZnv6Aevgq5adEdD3CUnQyAd yoCHKmrBErVoycYsi/aQpoLiv9Sw1xHwd8FFiyD8x1XSsBpRZ+wwHOlGkWqZaNbhtt qtuNhKoPiOIaqoNp7OipSsfpi3pSRtHNDqL8Zk4M= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2277a955a33_4e0f3f9fc2864f881944e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 14 Jun 2018 14:11:57 -0000 ----==_mimepart_5b2277a955a33_4e0f3f9fc2864f881944e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm going to reiterate: I don't think duplicate detection is a hard problem. You have an IntervalSet that is used to generate an ack. That goes back some distance in packet number space. At some point, you drop older/smaller blocks off that data structure. When you do, I'm suggesting you stop trying to decrypt packets with packet numbers than whatever packet number you've decided you're no longer waiting for(whether due to acks of acks or some other algorithm). There might be some cases when this InteralSet needs to be a bit larger than what you serialize to an ack frame, but that's not too difficult to deal with. The truncated packet number encoding is designed with increasing packet numbers in mind, so the only thing we're trying to allow is accepting packets within some reordering threshold. Certainly a receiver can decide to have a longer reordering threshold than an RTT, but at some point not too much longer than an RTT, it's reasonable to assume the peer retransmitted the data anyway. -- 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/1439#issuecomment-397310140 ----==_mimepart_5b2277a955a33_4e0f3f9fc2864f881944e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm going to reiterate: I don't think duplicate detection is a hard pr= oblem. You have an IntervalSet that is used to generate an ack. That go= es back some distance in packet number space. At some point, you drop ol= der/smaller blocks off that data structure. When you do, I'm suggesting = you stop trying to decrypt packets with packet numbers than whatever pack= et number you've decided you're no longer waiting for(whether due to acks= of acks or some other algorithm). There might be some cases when this I= nteralSet needs to be a bit larger than what you serialize to an ack fram= e, but that's not too difficult to deal with.

The truncated packet number encoding is designed with increasing packe= t numbers in mind, so the only thing we're trying to allow is accepting p= ackets within some reordering threshold. Certainly a receiver can decide= to have a longer reordering threshold than an RTT, but at some point not= too much longer than an RTT, it's reasonable to assume the peer retransm= itted the data anyway.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2277a955a33_4e0f3f9fc2864f881944e-- From nobody Thu Jun 14 07:39:30 2018 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 F3E5B13117A for ; Thu, 14 Jun 2018 07:39:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rAOtczzWJ6cs for ; Thu, 14 Jun 2018 07:39:20 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C43130EC6 for ; Thu, 14 Jun 2018 07:39:19 -0700 (PDT) Date: Thu, 14 Jun 2018 07:39:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528987159; bh=W0ZPWwOWV9cF11mmc+ryYousVCnV1WEqZVhNWyBttn4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=waH8c6zwb6lxITu+/7d4fcBeilQkWL4l0hQO1OdJuZAeJFWncV52QCveKfBbD+4tS W+lHql5KCZHWRNZJCOLY2AI7nirzxVGmD0NjPDTuFITNt7WfcAWklguBa7XWvKWnIH mM3CklCYbWKL8OMdQwhWTlzUb+HRA7nXXutfvrNs= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b227e1732e3_71732aabca512f5c1124d8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 14 Jun 2018 14:39:30 -0000 ----==_mimepart_5b227e1732e3_71732aabca512f5c1124d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Your last point about asymmetric-ness is important. The Chromium implementation does something like what you described with asymmetric timeouts. I would prefer to document a more general approach I briefly mentioned above, where you can't send new data within some time of the idle timeout, but you will continue to process and respond to incoming data until the timeout is hit, or maybe even a bit longer. I think this works well for non-HTTP applications, whereas picking a shorter timeout on the client side only really works well for client driven apps like HTTP. A simple approach might be: "New data must be sent with at least one RTO timeout remaining, and data should be received, processed and responded to for at least one RTO timeout after the specified idle timeout expires."? Receiving and processing a new packet resets the idle timeout, so there's no special case necessary for sending in response to a packet received at the very end of the connection. -- 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/1429#issuecomment-397319588 ----==_mimepart_5b227e1732e3_71732aabca512f5c1124d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Your last point about asymmetric-ness is important. The Chromium impl= ementation does something like what you described with asymmetric timeout= s.

I would prefer to document a more general approach I briefly mentioned= above, where you can't send new data within some time of the idle timeou= t, but you will continue to process and respond to incoming data until th= e timeout is hit, or maybe even a bit longer. I think this works well fo= r non-HTTP applications, whereas picking a shorter timeout on the client = side only really works well for client driven apps like HTTP.

A simple approach might be: "New data must be sent with at least one R= TO timeout remaining, and data should be received, processed and responde= d to for at least one RTO timeout after the specified idle timeout expire= s."? Receiving and processing a new packet resets the idle timeout, so t= here's no special case necessary for sending in response to a packet rece= ived at the very end of the connection.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b227e1732e3_71732aabca512f5c1124d8-- From nobody Thu Jun 14 07:46:20 2018 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 A290B12777C for ; Thu, 14 Jun 2018 07:46:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4yKYTDtwLskH for ; Thu, 14 Jun 2018 07:46:16 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C34BD130DC0 for ; Thu, 14 Jun 2018 07:46:16 -0700 (PDT) Date: Thu, 14 Jun 2018 07:46:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528987576; bh=/g4pSPgYVg5N4c2XHJlgWoqL2jncWOnN3cWv+iFPR5Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PzBEddHIQalglo2IYWcV2MeA9EiOyYhIN9irUWsOqnzQPt1JPtSojLpLOFWfhzMNu XCa7bfrp8APsHOl2BTXGFa0HNpJXBc/G6pUxMLTUtMaTNlad8XS6KsjpOExUjmd9P5 b3/M6as+dCsoBnUTrsWk8V13cBuO1zs7xk6hGxn8= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b227fb84c6a_3ba83fc72c4fcf8044989"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 14 Jun 2018 14:46:19 -0000 ----==_mimepart_5b227fb84c6a_3ba83fc72c4fcf8044989 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett > I'm going to reiterate: I don't think duplicate detection is a hard problem. You have an IntervalSet that is used to generate an ack. That is true, however I do not think that the fact that we can have a bullet-proof duplicate detection means that we should require every QUIC stack to have it, or that the fact justifies the encoding proposed in #1372. Using the ACK frame (or ACK_ECN frame) to notify which PN had the CE flag set (or other bits of ECN) will simplify the sender implementation, because you can use the signal to determine certain things that the encoding proposed in #1372 cannot (or hard to) tell; e.g., when 1-RTT passes since you've seen the last CE, if there was a consecutive loss of a ECN packet (i.e. blackhole detection). On the receiver side, I might argue that reapplying the frames without detecting a duplicate could also be a valid approach, considering the fact that we cannot decide to skip decrypting the payload just by checking if the decrypted PN collides with a previously seen PN (see [QUIC-TLS draft section 10.3](https://quicwg.org/base-drafts/draft-ietf-quic-tls.html#rfc.section.10.3)). Using the ACK frame that carries PNs with their ECN flags attached allows this kind of approach. To summarize, I still think that we should consider one of the following encodings, assuming that the size of the ACK (or ACK_ECN) frame will be acceptable, if not smaller. * use bit-vector (https://github.com/quicwg/base-drafts/issues/1439#issuecomment-396433945) * use truncated bit-vector (https://github.com/quicwg/base-drafts/issues/1439#issuecomment-396615367) * use typed blocks (bottom of https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397133920, https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397157328) -- 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/1439#issuecomment-397321982 ----==_mimepart_5b227fb84c6a_3ba83fc72c4fcf8044989 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett

I'm going to reiterate: I don't think duplicate detection is a hard pr= oblem. You have an IntervalSet that is used to generate an ack.

That is true, however I do not think that the fact that we can have a = bullet-proof duplicate detection means that we should require every QUIC = stack to have it, or that the fact justifies the encoding proposed in #1372.

Using the ACK frame (or ACK_ECN frame) to notify which PN had the CE f= lag set (or other bits of ECN) will simplify the sender implementation, b= ecause you can use the signal to determine certain things that the encodi= ng proposed in #1= 372 cannot (or hard to) tell; e.g., when 1-RTT passes since you've se= en the last CE, if there was a consecutive loss of a ECN packet (i.e. bla= ckhole detection).

On the receiver side, I might argue that reapplying the frames without= detecting a duplicate could also be a valid approach, considering the fa= ct that we cannot decide to skip decrypting the payload just by checking = if the decrypted PN collides with a previously seen PN (see QUIC-TLS draft section 10.3). Using the ACK frame tha= t carries PNs with their ECN flags attached allows this kind of approach.=

To summarize, I still think that we should consider one of the followi= ng encodings, assuming that the size of the ACK (or ACK_ECN) frame will b= e acceptable, if not smaller.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b227fb84c6a_3ba83fc72c4fcf8044989-- From nobody Thu Jun 14 07:47:33 2018 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 9514212777C for ; Thu, 14 Jun 2018 07:47:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 d5R_F6cI7ohh for ; Thu, 14 Jun 2018 07:47:27 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5222C130E46 for ; Thu, 14 Jun 2018 07:47:27 -0700 (PDT) Date: Thu, 14 Jun 2018 07:47:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528987646; bh=35cREUuvFjO38QoiGBUwrTn6sZH605f10YmfPKFKhwI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iffzPH3vUe0yycYUeTGNcpfznPs1WmqiCWQiYGhN1BES9uX5+xC6rnG7PWj3OXrWO /4cx4KLOK04c1DgLal/rG90mqWXOySi+0OAWlsOFEeK7r6mvR0mjrqac3ynk9nBH4f Qv/HXPWRDbTfrfp/eG7C7aK6/43FHsGcskdQ/4ZA= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b227ffe609b7_5fbc2aead8da8f5c916f0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 14:47:32 -0000 ----==_mimepart_5b227ffe609b7_5fbc2aead8da8f5c916f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A 10Gbps link with 1500 byte packets would have 10**9 / 1500 / 10 bytes in flight if RTT is 100ms which equals 2/3 * 100,000. If each duplicate entry is 32 bytes in a RB tree (left, right, color, PN) as is a common representation, a single connection consumes 32 * 2/3 * 100,000 = 2MB. Even if range maps are more efficient, they do not handle malicious gaps and they actually consume more space in that case. Other data strutures are more effective, but also more complex and less likely to be implemented. Granted, it is limited how many 10Gbps connections you can maintain concurrently with current tech, so 2MB might not be that bad but why place such a constraint if it can be avoided? -- 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/1439#issuecomment-397322424 ----==_mimepart_5b227ffe609b7_5fbc2aead8da8f5c916f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A 10Gbps link with 1500 byte packets would have 10**9 / 1500 / 10 byte= s in flight if RTT is 100ms which equals 2/3 * 100,000. If each duplicate= entry is 32 bytes in a RB tree (left, right, color, PN) as is a common = representation, a single connection consumes 32 * 2/3 * 100,000 =3D 2MB.<= /p>

Even if range maps are more efficient, they do not handle malicious ga= ps and they actually consume more space in that case. Other data struture= s are more effective, but also more complex and less likely to be impleme= nted.

Granted, it is limited how many 10Gbps connections you can maintain co= ncurrently with current tech, so 2MB might not be that bad but why place = such a constraint if it can be avoided?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b227ffe609b7_5fbc2aead8da8f5c916f0-- From nobody Thu Jun 14 07:49:16 2018 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 7DB92130DC0 for ; Thu, 14 Jun 2018 07:49:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 o8tUAclhAmjd for ; Thu, 14 Jun 2018 07:49:13 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 064C512777C for ; Thu, 14 Jun 2018 07:49:13 -0700 (PDT) Date: Thu, 14 Jun 2018 07:49:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528987752; bh=DgglEclz6hPYmk0riZkE0fpGiWYmf7D7y4aTG67OVbY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=I9cNQpn27RHkcLV2uKl7zk7keMI9nshWL/zriL7T0sB9jSANpvuvZypZFyvZs4QGK litrgvLrcdlrdhswtCeZBQSxm8H7N3PUDnSx0JwmKn7PKbq87DECVi5Ck3B4RNz9s/ DCGfs6l+8H2YW+T1gesEQEdNwakvLdKslTnmlByo= From: Antoine Delignat-Lavaud Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2280685e7f5_f8e2af92d5d0f607822"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ad-l 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.26 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: Thu, 14 Jun 2018 14:49:15 -0000 ----==_mimepart_5b2280685e7f5_f8e2af92d5d0f607822 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Throwing away a packet after decrypting its packet number is quite clearly forbidden by the spec. > An attacker can guess values for packet numbers and have an endpoint > confirm guesses through timing side channels. If the recipient of a > packet discards packets with duplicate packet numbers without > attempting to remove packet protection they could reveal through > timing side-channels that the packet number matches a received > packet. For authentication to be free from side-channels, the entire > process of packet number protection removal, packet number recovery, > and packet protection removal MUST be applied together without timing > and other side-channels. This text is there for a reason - packet number encryption (which is already very brittle) becomes mostly useless if you do this. In any case, @kazuho ECN proposal does not require packet deduplication from what I understand. -- 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/1439#issuecomment-397323088 ----==_mimepart_5b2280685e7f5_f8e2af92d5d0f607822 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Throwing away a packet after decrypting its packet number is quite cle= arly forbidden by the spec.

An attacker can guess values for packet numbers and have an endpoint confirm guesses through timing side channels. If the recipient of a
packet discards packets with duplicate packet numbers without
attempting to remove packet protection they could reveal through
timing side-channels that the packet number matches a received
packet. For authentication to be free from side-channels, the entire
= process of packet number protection removal, packet number recovery,
and packet protection removal MUST be applied together without timing
= and other side-channels.

This text is there for a reason - packet number encryption (which is a= lready very brittle) becomes mostly useless if you do this. In any case, = @kazuho ECN proposal does not require pac= ket deduplication from what I understand.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2280685e7f5_f8e2af92d5d0f607822-- From nobody Thu Jun 14 07:52:02 2018 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 E683F130E78 for ; Thu, 14 Jun 2018 07:51:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sk_qjDN-lRTQ for ; Thu, 14 Jun 2018 07:51:58 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1522D130E68 for ; Thu, 14 Jun 2018 07:51:58 -0700 (PDT) Date: Thu, 14 Jun 2018 07:51:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528987917; bh=EgoeuS/vwHr9+JofnpiN0Xk6gkRPFfqb/2U4oqFaE5E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PJz7rbK323kmq3ekoI/uME1gg8CylzXczS/KReq5QtTHukbOzQH3aoQ8CUzO09NZU 37RDTCxMg9HiFNe7vkwEOVyyrgAaempT24ia1U+iCYV09B/adaqWqlJAm4XUcZWtJS J7npBGNUf1oRDjO5ST/oLlNYKKK4x8ZSFQK2nxLg= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22810d59ebc_7d873fd8f8014f80114946"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 14 Jun 2018 14:52:01 -0000 ----==_mimepart_5b22810d59ebc_7d873fd8f8014f80114946 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj I'm ok with 2MB per connection given I'd be spending a lot more than that on send/retransmit buffer. And if I wanted to limit state for malicious attackers, I can just limit the number of ranges and the only cost is some very old packets(ie: 1000 ranges means over 2000 packets ago) will not be decryptable, which seems fine. -- 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/1439#issuecomment-397324055 ----==_mimepart_5b22810d59ebc_7d873fd8f8014f80114946 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj I'm ok with 2MB per conn= ection given I'd be spending a lot more than that on send/retransmit buff= er. And if I wanted to limit state for malicious attackers, I can just l= imit the number of ranges and the only cost is some very old packets(ie: = 1000 ranges means over 2000 packets ago) will not be decryptable, which s= eems fine.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b22810d59ebc_7d873fd8f8014f80114946-- From nobody Thu Jun 14 07:54:28 2018 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 5AD16130EDF for ; Thu, 14 Jun 2018 07:54:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 P2fRYpXnSeSU for ; Thu, 14 Jun 2018 07:54:25 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 5D2E8130E62 for ; Thu, 14 Jun 2018 07:54:25 -0700 (PDT) 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=SCUDeBTHJE1oh7Zo80wHHw1Ec3s=; b=GVeLqsNRaHCVvKBX 1LgStUSOMnlL3xfyw8pLP8gRv2KZRrL/HG/oevhXb3PH/eGpaUCpwjcJg3DW/bLI vub1a7zAeH34zpmhod3ZO39faFQvXpDNWgSafB2d3IoiEhAVxgWNz/75GDUy+YI6 2vdFMmPNeWYvCpBEpOEAA4SP0/g= Received: by filter1525p1mdw1.sendgrid.net with SMTP id filter1525p1mdw1-11426-5B2281A0-17 2018-06-14 14:54:24.480667814 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id kLI8ycQPT-2YVS-RwDxSOA for ; Thu, 14 Jun 2018 14:54:24.479 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id 732E9C0B01 for ; Thu, 14 Jun 2018 07:54:24 -0700 (PDT) Date: Thu, 14 Jun 2018 14:54:24 +0000 (UTC) From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2281a071f49_55183ff7497c6f841973eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3X/T5JgsdxtXZvuTbrfoxJy3TRJZ9LqL2mAc hOqIpUilC+FkKGkbXQHkiPrcT9l/F1S9qiAPsUOGopGcNOod/oH0rwepXNrHMOuTNdWZvs1lZsoSFO r3jfAJA30WtOmmHsNuT4fTaYbiZKBxUTzZw0CByOULMnpfy+zor+DqVRrOdigQZQEc4Cxdeew0mgyo 4= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 14:54:28 -0000 ----==_mimepart_5b2281a071f49_55183ff7497c6f841973eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ad-l That's true. OTOH, I assume that we do not disallow throwing the packet away after decrypting the payload when observing a PN collision? -- 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/1439#issuecomment-397324950 ----==_mimepart_5b2281a071f49_55183ff7497c6f841973eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ad-l That's true. OTOH, I assume that we do not disallow throwing the packet away after decrypting the payload when observing a PN collision?

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

----==_mimepart_5b2281a071f49_55183ff7497c6f841973eb-- From nobody Thu Jun 14 08:06:39 2018 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 2AFAA130E43 for ; Thu, 14 Jun 2018 08:06:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yENyZdsmaLAg for ; Thu, 14 Jun 2018 08:06:35 -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 C4C6E130E29 for ; Thu, 14 Jun 2018 08:06:35 -0700 (PDT) Date: Thu, 14 Jun 2018 08:06:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528988795; bh=b5B3NNLPRDpkY0hGFJE3vKcGhkw83KSuDJIvA6O0ZMI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VY4UAY0aytAgt9xpQ/zN/x3aFCxH1qYG9XJs2+/leQDkOSm4F0QBPsMa3ndWrK5LU 1wQHC1j2o+SNGxDDibrxeyrRA+N1VDhGwwvFLDRcjc2asNv0/fbjVal7Efd+mjMS1s CnWpJuXDuvp/K7PMWMD4xZw4yXD8IiIIzRAhihLM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22847b44ed0_1e5d2ab17a824f50441638"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 14 Jun 2018 15:06:38 -0000 ----==_mimepart_5b22847b44ed0_1e5d2ab17a824f50441638 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 2000 packets is then 3% of the inflight data. -- 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/1439#issuecomment-397329286 ----==_mimepart_5b22847b44ed0_1e5d2ab17a824f50441638 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

2000 packets is then 3% of the inflight data.

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

----==_mimepart_5b22847b44ed0_1e5d2ab17a824f50441638-- From nobody Thu Jun 14 09:03:59 2018 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 66D2D131178 for ; Thu, 14 Jun 2018 09:03:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yYz_du2UaDD0 for ; Thu, 14 Jun 2018 09:03:45 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE9DC131165 for ; Thu, 14 Jun 2018 09:03:44 -0700 (PDT) Date: Thu, 14 Jun 2018 09:03:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528992223; bh=1OUvJtYRZURWvDIbkXDBEfZ7e0LVYE7hni0Y68J7duY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=R9NKgkyo/Qi/NCY54rtskoDYSIJarSEafi9KbM53YLxRlf5mw8GdUr39IpY54TOwg UbDI8ilEbG3jshpHzq5PTwF9jBTtFQgtnfHuBe8pRKneCoWMi+fGwMaD8zn/rf3wbS YD5c2izJkBI2yS1SlpSXNKS4uEC5NAC6f6Br4TYI= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Fix sentence: make clear what fails with PROTOCOL_VIOLATION code (#1445) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2291dfbacb6_5a8a2ae3f7be6f58566ab"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.26 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: Thu, 14 Jun 2018 16:03:57 -0000 ----==_mimepart_5b2291dfbacb6_5a8a2ae3f7be6f58566ab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1445 -- Commit Summary -- * Fix sentence: make clear what fails with PROTOCOL_VIOLATION code -- File Changes -- M draft-ietf-quic-transport.md (4) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1445.patch https://github.com/quicwg/base-drafts/pull/1445.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/1445 ----==_mimepart_5b2291dfbacb6_5a8a2ae3f7be6f58566ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • Fix sentence: make clear what fails with PROTOCOL_VIOLATION code

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 mute the thread.

----==_mimepart_5b2291dfbacb6_5a8a2ae3f7be6f58566ab-- From nobody Thu Jun 14 09:55:22 2018 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 B856F1310A1 for ; Thu, 14 Jun 2018 09:55:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 GMIejFoV3dm5 for ; Thu, 14 Jun 2018 09:55:09 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8416E13116A for ; Thu, 14 Jun 2018 09:55:09 -0700 (PDT) Date: Thu, 14 Jun 2018 09:55:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528995308; bh=W8DjP9LyGzLPGAlR5qhYQAAelIqnYRVjZhL9Vr9agR4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uEVQGe4E7DjSwt3GwFYyFzrb5mmnh2rGTokbBjV5O9F1HMxF9otN3AlZVenU4svpk kJmKh7BkjjKiPH89rmdkA9fPK37wb4Ag8bnbvEG2UvaEBtXr/8x4DqMAsLVBc9EmaQ 9ov4dFNQbSwAaF5RQLBTf2YB916/KVCyrrVfj92s= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b229decaeb1d_47e03fefe1afef7c1080a0"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 16:55:21 -0000 ----==_mimepart_5b229decaeb1d_47e03fefe1afef7c1080a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That seems reasonable. I'm not inclined to go with MUST here, but instead note that sending within an RTO of the timeout is risky. -- 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/1429#issuecomment-397365067 ----==_mimepart_5b229decaeb1d_47e03fefe1afef7c1080a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

That seems reasonable. I'm not inclined to go with MUST here, but instead note that sending within an RTO of the timeout is risky.

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

----==_mimepart_5b229decaeb1d_47e03fefe1afef7c1080a0-- From nobody Thu Jun 14 10:00:38 2018 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 6E08D130E44 for ; Thu, 14 Jun 2018 10:00:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DPamXdIDGrNj for ; Thu, 14 Jun 2018 10:00:32 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4B411294D0 for ; Thu, 14 Jun 2018 10:00:31 -0700 (PDT) Date: Thu, 14 Jun 2018 10:00:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528995631; bh=ezzJ0vDC/S0AVoo1pb/Px92HJ43YTd4Hju7a/ADMxMU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vHxMlH/P3WXK514KIUU8OBtDo3Gm5ilU+z8XixwezqGGC6wiRxFAkp6WmBFZB/wcP JVh2uZIhV9K48MXPkih4jGgWTIc2INLU+Y5KyJal5hhLp/4rwoehLSK2qpf+2JipVA 50uhqk6VDljJXcCo7tsMPwiDoYatMduvf5LSNxY0= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Idle timeout interaction with RTO (#1429) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b229f2f29309_30582b125acbcf54148940"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 14 Jun 2018 17:00:36 -0000 ----==_mimepart_5b229f2f29309_30582b125acbcf54148940 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed, I think a MUST is too strong. -- 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/1429#issuecomment-397366644 ----==_mimepart_5b229f2f29309_30582b125acbcf54148940 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Agreed, I think a MUST is too strong.

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

----==_mimepart_5b229f2f29309_30582b125acbcf54148940-- From nobody Thu Jun 14 11:59:36 2018 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 2E919130E6D for ; Thu, 14 Jun 2018 11:59:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 NeLJpxTk4H5N for ; Thu, 14 Jun 2018 11:59:31 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 87608130E1D for ; Thu, 14 Jun 2018 11:59:31 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529002770; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=angElYvSh8TOJsB/Hd4LWo14ImF+u0j5lITL4rDwcXs=; b=rTe0fWagt6XHF7TR5d43KqFSFwWWlQbf2+ajDYDOdpXwiWU44dYyeEwok+r8sCxI8aSOZ2/s iA/b1BBd7i3w9NyofLRZQVgX0tXxxf9fdvcfxt0QY5By3pAlwKWcKS05tDIMofHgly/3NcmQ sD7fSKazExZ4kyfVSAfxxvridFs= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22bb12.7fbd5734d600-smtp-out-n03; Thu, 14 Jun 2018 18:59:30 -0000 (UTC) Date: Thu, 14 Jun 2018 11:59:29 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b22bb113c9e7_8d72afc6bac7c0857627@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b4ed7e: QPACK Feedback with forward references Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22bb113c620_8d72afc6bac7c085757d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 18:59:34 -0000 ----==_mimepart_5b22bb113c620_8d72afc6bac7c085757d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: b4ed7e487dd2c0d828f0f4422bd5044ab195674d https://github.com/quicwg/base-drafts/commit/b4ed7e487dd2c0d828f0f4422bd5044ab195674d Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- QPACK Feedback with forward references **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22bb113c620_8d72afc6bac7c085757d-- From nobody Thu Jun 14 12:02:25 2018 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 18942130F70 for ; Thu, 14 Jun 2018 12:02:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 lxzyPp34nmPK for ; Thu, 14 Jun 2018 12:02:12 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D676B130F72 for ; Thu, 14 Jun 2018 12:02:07 -0700 (PDT) Date: Thu, 14 Jun 2018 12:02:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529002927; bh=PYHYBf99BBFfQHvOkaV0dwQ6bKQcs0kgBjzb5b3z8Ks=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xx5fxOAJqthpNi07+vWPBLjsXRQBYtMnBoGL4IBcFexTMwfagzjCnU5Pgjb7F8DxO dkppRsxOypP3cXmeVb7FJd2BFd//+Ky1OkbBuzIfGPRZ4b2UNMMnP0v1tTFolgvJF5 XghengzJZ3Bth/V5Wu8Zv/OJAXZsylVIDX1bpEXE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22bbaf3f80_39312af7641f0f501292af"; 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.26 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: Thu, 14 Jun 2018 19:02:24 -0000 ----==_mimepart_5b22bbaf3f80_39312af7641f0f501292af Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Redone on top of #1400; look at the most recent commit if you want to see just this change. The suggestion to land the text in the appropriate instructions and just forward-reference from the intro section does substantially reduce the "wall of text," and I think it reads much better. -- 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/1410#issuecomment-397404112 ----==_mimepart_5b22bbaf3f80_39312af7641f0f501292af Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Redone on top of #1400; look at the most recent commit if you want to see just this= change. The suggestion to land the text in the appropriate instructions= and just forward-reference from the intro section does substantially red= uce the "wall of text," and I think it reads much better.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b22bbaf3f80_39312af7641f0f501292af-- From nobody Thu Jun 14 15:25:41 2018 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 8A42B130E8F for ; Thu, 14 Jun 2018 15:25:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 F-Sjo4YwJutr for ; Thu, 14 Jun 2018 15:25:38 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 5C342130E12 for ; Thu, 14 Jun 2018 15:25:38 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529015137; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=PldO9hY6WC77X73sOxUVg/d0pPDFf++kd/awxbAfDHk=; b=Zs2P9BPBkkFek1Pg5UMGLwKcIrPdloMjF2IVSWjRX/G6g9F+KseD4nww8YOqm/Ll9J7icld7 /q6n+urv/jX30EKQjo5BXQ8uQNWjOFSuwh+3fZSiWWzlyXB42N7owH/zBfkhImt9Wa6HXWVC ac87mcODQn4fb/vEoHanJiNCtw0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b22eb61.7fd74dc3f810-smtp-out-n02; Thu, 14 Jun 2018 22:25:37 -0000 (UTC) Date: Thu, 14 Jun 2018 15:25:36 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b22eb603d40e_3c902b043ef5bc0895878@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 205e53: Fix sentence: make clear what fails with PROTOCOL_... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22eb603cdd3_3c902b043ef5bc0895790"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 22:25:40 -0000 ----==_mimepart_5b22eb603cdd3_3c902b043ef5bc0895790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 205e5325fa62e4bc321b4e70a210b14bd50db436 https://github.com/quicwg/base-drafts/commit/205e5325fa62e4bc321b4e70a210b14bd50db436 Author: Dmitri Tikhonov Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fix sentence: make clear what fails with PROTOCOL_VIOLATION code Commit: f3bfed7b115ab06edc831dd06e093349cb5798c5 https://github.com/quicwg/base-drafts/commit/f3bfed7b115ab06edc831dd06e093349cb5798c5 Author: Martin Thomson Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1445 from dtikhonov/201806141202-fix-integrity-check-sentence Fix sentence: make clear what fails with PROTOCOL_VIOLATION code Compare: https://github.com/quicwg/base-drafts/compare/5cdb2b202570...f3bfed7b115a **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22eb603cdd3_3c902b043ef5bc0895790-- From nobody Thu Jun 14 15:25:48 2018 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 A0FE9130F7C for ; Thu, 14 Jun 2018 15:25:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 CduLa4Yq5r2O for ; Thu, 14 Jun 2018 15:25:41 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DBE9130E12 for ; Thu, 14 Jun 2018 15:25:41 -0700 (PDT) Date: Thu, 14 Jun 2018 15:25:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529015140; bh=YQCqRn5eONFpeUJ1eCBju9kc1+0aaGQ0A2fqHeyZYgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ec51qZFTlj/r4EK0bjbGknCx3SH0SVvXhKHWvgVQaNbcctHtcu5YQCozUvgmuQlDD qjGUYBHY3UsAAm5BteZ0tpa4SqCzELiPuWvLuSHcliEDYyoCsgaP391zh0egsiYExr CWwb/FXF8+yxCcmW4qZgeQ5YgaxOxt0ELKktACUI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fix sentence: make clear what fails with PROTOCOL_VIOLATION code (#1445) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22eb648f67f_20e32b182b348f50103067"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 22:25:44 -0000 ----==_mimepart_5b22eb648f67f_20e32b182b348f50103067 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1445. -- 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/1445#event-1682289527 ----==_mimepart_5b22eb648f67f_20e32b182b348f50103067 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1445.

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

----==_mimepart_5b22eb648f67f_20e32b182b348f50103067-- From nobody Thu Jun 14 15:25:56 2018 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 B39B4130F6C for ; Thu, 14 Jun 2018 15:25:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 tDVz10NO-_vb for ; Thu, 14 Jun 2018 15:25:47 -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 2BED2130E12 for ; Thu, 14 Jun 2018 15:25:47 -0700 (PDT) Date: Thu, 14 Jun 2018 15:25:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529015146; bh=Sc/XyDwSUhAP4BSpIB3MevR5fYd4sW/AhPNZPwz5Sig=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xKIjkyvJhQivUW3qv6MHg4RqSIGQL7O8q1hmMrZuNBmKVtHj6AqOuvGA2TkkJ6YT1 7Mrib92MrWrdUdU4Ef+dqxU/WsXMyDMx70FRfJAYHINhwaTa9TP+2LWzuQTVEbkOQl G9wrLAFzAthif0JrKdCD10OvXDPI1TmRhRU9/v6M= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fix sentence: make clear what fails with PROTOCOL_VIOLATION code (#1445) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22eb6a802a4_7de13fa20d38af8819249c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 22:25:51 -0000 ----==_mimepart_5b22eb6a802a4_7de13fa20d38af8819249c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks. Much better. -- 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/1445#issuecomment-397456961 ----==_mimepart_5b22eb6a802a4_7de13fa20d38af8819249c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks. Much better.

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

----==_mimepart_5b22eb6a802a4_7de13fa20d38af8819249c-- From nobody Thu Jun 14 15:53:07 2018 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 252F5130EA6 for ; Thu, 14 Jun 2018 15:53:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 D6V9TTtrygSE for ; Thu, 14 Jun 2018 15:53:03 -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 9D7D1130E97 for ; Thu, 14 Jun 2018 15:53:03 -0700 (PDT) Date: Thu, 14 Jun 2018 15:53:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529016782; bh=rsAcVeJR5VNDdxXVu5EFOSZeWjTTf1rSUOuaZKAtCiM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HqqXTqUwmHQ69EzOEHIZ7uIMefNGL8AQy8yBY5hec3E58RSQgul9afasUspcSk9fr rq4lmrayNPMJB2gbuYPLLtWC2Y4En993a6gDPMmE3ejQaIbh7lUT18DJOIzDNdLSZQ 6rPQdrxyDeKYux0C39EpLZYevMtBU4Q8aIz9ynlQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b22f1ceeb105_2de22ae2d0d06f501031da"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 14 Jun 2018 22:53:06 -0000 ----==_mimepart_5b22f1ceeb105_2de22ae2d0d06f501031da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson approved this pull request. Yep, this looks good. -- 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/1410#pullrequestreview-128997170 ----==_mimepart_5b22f1ceeb105_2de22ae2d0d06f501031da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

Yep, this looks good.

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

----==_mimepart_5b22f1ceeb105_2de22ae2d0d06f501031da-- From nobody Thu Jun 14 16:37:04 2018 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 66621130FAF for ; Thu, 14 Jun 2018 16:37:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 TFlETQiQHqlF for ; Thu, 14 Jun 2018 16:37:01 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 31E05130E9D for ; Thu, 14 Jun 2018 16:37:01 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019420; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=hkPB6INsmeTXHNDK8gysL5JF6NtWezLpwkp5DwOAhuU=; b=iOKT93ca7IH6CTyS9V41RPQ5HyNlk0gim9Q9xN/jaN2QCmUcNR55YyFwP6xUZpcn5/jYNQFt PobKxU1JOu0SDvhNsEIgc/8uYLXMtjlIy9++45xYMo8sNhZ9VPP+b6TEWP/Mc7Sfi8GG/0lB +zf+uvFMEYy59yLwkpIJKaXa2oo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b22fc1c.7fe4b6e19ae0-smtp-out-n02; Thu, 14 Jun 2018 23:37:00 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:00 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc1c4de5e_ecb2af7b0b63c08982de@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc1c4dadc_ecb2af7b0b63c089814e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:37:03 -0000 ----==_mimepart_5b22fc1c4dadc_ecb2af7b0b63c089814e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack/explicit_huffman Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc1c4dadc_ecb2af7b0b63c089814e-- From nobody Thu Jun 14 16:37:15 2018 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 724DB130FAF for ; Thu, 14 Jun 2018 16:37:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Ho5BfqOxPsJs for ; Thu, 14 Jun 2018 16:37:11 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 62432130E9D for ; Thu, 14 Jun 2018 16:37:11 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019430; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=7H2rjetu80y8jTKRhiZAQL4pPhcH/wLlMdHfCjpn0/M=; b=jN8Ea5KPPAt79Erzu1etJTPxdMf+Lve8rhr4hrjS0RsUSC9GrXzU1zcVPt75Gk3RaLrPsyJ0 KHXyWXFyeFYBpK+erEuPGaYCrSY/HbdDNb0V75im0vlG47cbMOnrrY3VvfGN/GAADX3ohukO +73SxhNOkJunCOidNzyByo1Fu9s= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fc26.7fd382f05f90-smtp-out-n01; Thu, 14 Jun 2018 23:37:10 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:09 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc259d84e_69a32aedbe4bfc049571f@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc259cee8_69a32aedbe4bfc04956f1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:37:13 -0000 ----==_mimepart_5b22fc259cee8_69a32aedbe4bfc04956f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/strike_the_colors Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc259cee8_69a32aedbe4bfc04956f1-- From nobody Thu Jun 14 16:37:24 2018 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 83DC9130FB2 for ; Thu, 14 Jun 2018 16:37:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 JOdarHZGwY7D for ; Thu, 14 Jun 2018 16:37:14 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 419B8130FAF for ; Thu, 14 Jun 2018 16:37:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019434; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rei8S5DH/nuwzg+3b49Hjy3indl3/wqIBY00Y4kdzEw=; b=MBV6wjTDoU7lc3vw8X61qCjtykg+kE9BSHMTRAg/IX/B5Wi4QXrgtkbzFRqfZk86Mx0FKusj P08NkdW/LrAT9GaTn7Kp5S3sZMnUnFqRW9UMWslw2er5B9Yh2qMrpUEumARdDI3gpDor6DZi LYTjoZeb2LVdctW3MPzSTVMUaeo= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b22fc29.7efdd183bf90-smtp-out-n03; Thu, 14 Jun 2018 23:37:13 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:12 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc282249a_5bf42af6f5f3fc0c867ac@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc2821eec_5bf42af6f5f3fc0c8661e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:37:16 -0000 ----==_mimepart_5b22fc2821eec_5bf42af6f5f3fc0c8661e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_independent Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc2821eec_5bf42af6f5f3fc0c8661e-- From nobody Thu Jun 14 16:37:30 2018 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 2EC79130FBD for ; Thu, 14 Jun 2018 16:37:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 gGE8YEb8zgyG for ; Thu, 14 Jun 2018 16:37:19 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E5D4E130E9D for ; Thu, 14 Jun 2018 16:37:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019438; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=lHXHZ9ovFbrzyWWKnS5oVZPFonQa6ZS2bJzl9pNnKGs=; b=mGJkt+2Bc9N2gRhuEBMp5XSgUtUO7Un/tiugVZ+onnNEJsRxyxvzO1xJboEX4rkAtAdviDQi TiE9Kr5+ovG3TSo2fEzoeqKS8a/NOLMr3W1P2uYYb5hcI8mwufPpZ9rhoN8Do2e3jNrJaIyl V6dmQFI7e5hint1+vaVVs/ro184= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fc2e.7fe4c023a2d0-smtp-out-n02; Thu, 14 Jun 2018 23:37:18 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:18 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc2e2279a_55c2ab7977bdc10304d9@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc2e220e9_55c2ab7977bdc10303a8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:37:20 -0000 ----==_mimepart_5b22fc2e220e9_55c2ab7977bdc10303a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/duplicate-name Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc2e220e9_55c2ab7977bdc10303a8-- From nobody Thu Jun 14 16:37:35 2018 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 4C306130E9D for ; Thu, 14 Jun 2018 16:37:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.261 X-Spam-Level: X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 f5adBWzlf4JL for ; Thu, 14 Jun 2018 16:37:20 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2825E130FAF for ; Thu, 14 Jun 2018 16:37:20 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019439; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=u4+vEN1qIGMQGE/KPTSBKfIPjV2Dx54G7P5b5BDK9Ms=; b=giH7F0WmoR3xg2nGYPD8qBadJY33stja+JpSxMAl4lF2z91VzHED1QODQ2hj94P8Qqjk3vAh d4cxh+tk7+znxVV1fIWb2ogGGWnF/b1e66CuFpzGJky6udZHnyDmrx0sOqRRb7uGdEVamVXI Ww2gqd0ix09TXld/M3sbn+7DXPo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b22fc2f.7fb87284bd80-smtp-out-n01; Thu, 14 Jun 2018 23:37:19 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:19 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc2f50627_7b212ab314109c0c27078@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc2f50280_7b212ab314109c0c2693d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:37:22 -0000 ----==_mimepart_5b22fc2f50280_7b212ab314109c0c2693d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-onepass2 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc2f50280_7b212ab314109c0c2693d-- From nobody Thu Jun 14 16:38:59 2018 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 2F23E130FB1 for ; Thu, 14 Jun 2018 16:38:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 nT0YaF9sEE2L for ; Thu, 14 Jun 2018 16:38:54 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 49855130E9D for ; Thu, 14 Jun 2018 16:38:54 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019533; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=EA3AmRMoSu6goHYl+UM28fjUSycqn0846F+8cctmRfg=; b=jAQ0kpCQzOrzdiKmDoJ5CmU3+b8ZYHxeZraZqiwiZa3dqmRFPwc62qZCprfP4fecJYpN0+Rf F0SwIICXzYrIeIr2Ee9KEGM78+BRb4cBdkgLo6F3G4LbU/7KGCsQvEJMLQIf6CRCx5MxttPi Y+dqTRHnLvwyUGUByqMx9qaVYFo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fc8d.7f03f71612d0-smtp-out-n02; Thu, 14 Jun 2018 23:38:53 -0000 (UTC) Date: Thu, 14 Jun 2018 16:38:52 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc8c41595_62c2b0546883c1074051@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc8c40f30_62c2b0546883c1073929"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:38:57 -0000 ----==_mimepart_5b22fc8c40f30_62c2b0546883c1073929 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sr-during-pv Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc8c40f30_62c2b0546883c1073929-- From nobody Thu Jun 14 16:39:04 2018 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 B15FD130E9D for ; Thu, 14 Jun 2018 16:38:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 FPNHfK_6idBE for ; Thu, 14 Jun 2018 16:38:54 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 BBD55130FAF for ; Thu, 14 Jun 2018 16:38:54 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019534; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=pYCl3jB3pc+IlmzP80rsVh2Ac4olt/XTbr7QkLnHjcs=; b=un6vWOZlIdixmmqV3kj/6+97GZD/75X5T984+yaIVbr5o7maYOdMo3Z908IugAqiyvqo/YeC VQHh7kuA87MeVCgjXPRZxcbZD/2wwGE0iC9EWOXKO8fKCiGnzr2lW+0acbiAw0KTstv8xgJc GqThA5jRwb4bAWW06KZqUQFF48Y= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b22fc8e.7ff05916b300-smtp-out-n02; Thu, 14 Jun 2018 23:38:54 -0000 (UTC) Date: Thu, 14 Jun 2018 16:38:53 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc8d732e2_647c2aacdb13fc1027175@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc8d72423_647c2aacdb13fc102708b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:38:57 -0000 ----==_mimepart_5b22fc8d72423_647c2aacdb13fc102708b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/why_ports Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc8d72423_647c2aacdb13fc102708b-- From nobody Thu Jun 14 16:39:25 2018 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 5BDF2130FAF for ; Thu, 14 Jun 2018 16:39:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 cPwzX9tRooxc for ; Thu, 14 Jun 2018 16:39:22 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 08B42130E9D for ; Thu, 14 Jun 2018 16:39:21 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019561; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=PGuQhiJ1d+/mvAn+6p2UnMxCW4e4zshK7L4UtrQhxB4=; b=Js5KbZ46hLzJ6QNvxrr1DHgANkmWUL1drXRBGnEsN+LyLpPgiDa3SKb9yXuAwUlsepYnXGdr +hKpH8kmeiwuSIL+w3/yLW0swwRy+8ZIguaw/2XF4InkQRBjQit9y2KNb72avdXUR1+6kQSm XY9gihzOeC1+XZWmzNE6QtkQnRw= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fca9.7f4460bfa9c0-smtp-out-n03; Thu, 14 Jun 2018 23:39:21 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:20 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fca8e86c7_46b42aec7b159c0c8544c@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fca8e8330_46b42aec7b159c0c853ec"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:24 -0000 ----==_mimepart_5b22fca8e8330_46b42aec7b159c0c853ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/key-schedule-cleanup Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fca8e8330_46b42aec7b159c0c853ec-- From nobody Thu Jun 14 16:39:31 2018 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 A6F4C130E9D for ; Thu, 14 Jun 2018 16:39:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 4fI95JoTNKug for ; Thu, 14 Jun 2018 16:39:22 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 4C178130F16 for ; Thu, 14 Jun 2018 16:39:22 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019562; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=0qFolgS3N02xu3kfSNEiOc5a9nGaXfVgacIELliC5dk=; b=WMZ2i1KIuNZXLjcFXysGEgT27WlZFcd0h9nwaDZ3i9jJn9/smPW64kXv93onYTrKFs+mAJ3s Md3+8wsPCjffjC1mBHHec9pakV/YLwCZsixolQF6ufXuLcoCpqiJltFqSCuz7Z537mQlLS2C EBm/iIImuCOiN1r2OUGQZnqLq4Q= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b22fca9.7f43b0eb3720-smtp-out-n03; Thu, 14 Jun 2018 23:39:21 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:21 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fca9c85c1_7d6c2af40438fc0c530fd@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fca9c8030_7d6c2af40438fc0c52949"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:24 -0000 ----==_mimepart_5b22fca9c8030_7d6c2af40438fc0c52949 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/nitty_nits Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fca9c8030_7d6c2af40438fc0c52949-- From nobody Thu Jun 14 16:39:37 2018 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 D4C03130FBB for ; Thu, 14 Jun 2018 16:39:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 UR9Efc6LXelw for ; Thu, 14 Jun 2018 16:39:29 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 785DB130FB1 for ; Thu, 14 Jun 2018 16:39:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019569; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=obVz0xpALjGSRhggm4MHB+umnI8mSgCYFJHiXnfMKnE=; b=vEUTqvXg/1OZdP3YxRyW0g4ZCTSClqzjwGGBtNpqXUQBJZWoggbkJUROjYUkY8FALL+sUJUr KxvBdhAl/lqcasUkIt6+vK/5GBrM2yUs5A7jzJZy04XqOMfCcENDwuS2/yPKgTW9WCgx2Jdj 16FvJOIHekRml0vCi7GBDulbIUI= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b22fcb1.7fb87292b600-smtp-out-n01; Thu, 14 Jun 2018 23:39:29 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:29 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb141825_5ee32afe2e8ebc08525e4@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb14142b_5ee32afe2e8ebc0852423"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:31 -0000 ----==_mimepart_5b22fcb14142b_5ee32afe2e8ebc0852423 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-ack-optimization Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb14142b_5ee32afe2e8ebc0852423-- From nobody Thu Jun 14 16:39:50 2018 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 305E0130E9D for ; Thu, 14 Jun 2018 16:39:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 SBM4erDCCeuS for ; Thu, 14 Jun 2018 16:39:30 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E5B0E130FAF for ; Thu, 14 Jun 2018 16:39:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019569; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=lHKQWj3inoQamwuh3D0RyKvseZjN0yIk3LNVvJcMw34=; b=QBLjmON5wxmTTzNDYv/BB1hWUpmJxDkEDyfREFI/DuTskfMnYPb97OBLxfLHjUPdRS2LUsy/ Uis8VLGLhapOI/xYUtwFlIB7SSZwqBdcdMZQqGvwsXassOU+rwKKDsiw0wY1BKtCrWaYGitc MWZdQApe1A7Py3wHp6Q96KByUyw= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b22fcb0.7f9e18c53ab0-smtp-out-n03; Thu, 14 Jun 2018 23:39:28 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:27 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcafc81b6_36ad2af78a2b1c0c104150@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcafc7daf_36ad2af78a2b1c0c104099"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:32 -0000 ----==_mimepart_5b22fcafc7daf_36ad2af78a2b1c0c104099 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/vn-dont-decrypt Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcafc7daf_36ad2af78a2b1c0c104099-- From nobody Thu Jun 14 16:39:56 2018 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 C6282130F16 for ; Thu, 14 Jun 2018 16:39:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 KGXteIui4JSK for ; Thu, 14 Jun 2018 16:39:30 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 B7665130FB4 for ; Thu, 14 Jun 2018 16:39:30 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019570; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9ll/1OHToC1jJuyzzs/k25IyuqFqJa6G+LLoL7TTESk=; b=TDvzLN20mdOhotX9TaLIJO8aMBa4Gp9XycCs3klPL97rexVelUlNusgUuj9mZgw2XNEV3mui cvxu4OgozR93StqjZmbEDW3iga286JqXOhNiWr5PvURSFD6denHdpMzBxTsP9yrqNDVfTT9g Gp/bI9BO409lzz65XX3pMM4V7R0= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b22fcb2.7f239f088930-smtp-out-n01; Thu, 14 Jun 2018 23:39:30 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:30 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb26e90d_49f42adabd0c7c147658a@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb26e56b_49f42adabd0c7c14764c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:33 -0000 ----==_mimepart_5b22fcb26e56b_49f42adabd0c7c14764c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qcram_rename Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb26e56b_49f42adabd0c7c14764c5-- From nobody Thu Jun 14 16:40:01 2018 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 C29BC130F16 for ; Thu, 14 Jun 2018 16:39:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.261 X-Spam-Level: X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 uPkm0kDSmiYN for ; Thu, 14 Jun 2018 16:39:33 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 A2F2C130E9D for ; Thu, 14 Jun 2018 16:39:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019573; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=qhvBU51c4EMsknhjCToL5wfteiptEA3OLq4cbRxvmbI=; b=VaXwxGHqZDnhLfr8mrLByJiI4yo0VYFKhFyE/XRUeZ5tzdoFfdevi+hY6W+QvjXn3gq49+Nv kTnsg6Vr3h+aZ8/2PO6PHu+6L5PDuDTPhauLOJ/PWbUlTvtUbu9puBYTxXerBYKrylTRNO+W rfJiPx5L/6RruWm1g7vVXXEdqBg= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b22fcb5.7f931ea1a150-smtp-out-n03; Thu, 14 Jun 2018 23:39:33 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:32 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb487cc5_3cea2af5d9565c081011a4@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb4878cb_3cea2af5d9565c08101062"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:35 -0000 ----==_mimepart_5b22fcb4878cb_3cea2af5d9565c08101062 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-handshake-retransmit Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb4878cb_3cea2af5d9565c08101062-- From nobody Thu Jun 14 16:40:06 2018 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 97478130F16 for ; Thu, 14 Jun 2018 16:39:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 jZ5ZYJcoSCYw for ; Thu, 14 Jun 2018 16:39:35 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 6E8BF130E9D for ; Thu, 14 Jun 2018 16:39:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019575; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=YUFNDOJH2AXU4lGDIK8r7I5wQaZNlEBGl3lGyuLRCzc=; b=GbfC6UjoDSNin9mOTr9MSNLquymqmudBCrvmhfXczgb8bRnS+3wykEhh7V0ASLuBSH+jQ2SX YWCINTE4iE84PXd93endD6OXiMPDaG1NqeRW6nZR6jWBfCZ14+Utyf7YuP7wENzCKYaeTLKh fRx9gXnJHoqpzOlqI8eDaoYhDiY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fcb7.7f235416b3f0-smtp-out-n01; Thu, 14 Jun 2018 23:39:35 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:34 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb6ea421_62422b1f14ba1c0c231da@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb6e9fdb_62422b1f14ba1c0c23037"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:37 -0000 ----==_mimepart_5b22fcb6e9fdb_62422b1f14ba1c0c23037 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/nitty_nits2 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb6e9fdb_62422b1f14ba1c0c23037-- From nobody Thu Jun 14 16:40:12 2018 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 BE5F1130E9D for ; Thu, 14 Jun 2018 16:39:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 sNpCkRFUiCPL for ; Thu, 14 Jun 2018 16:39:38 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 472E1130FB4 for ; Thu, 14 Jun 2018 16:39:38 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019577; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=SggP3B0i2YWzEy06nVTqw19KAemk065PbhWne9iEI3o=; b=E9IXcFLlSudwN0K36EpNrtqqpEFL3HYfW137bhAAf40xG0KQEj5wh3GnrR7APWmjLlspcv6y wqaHtO1v72ObOKnOAelLPJjjf94B/zJ67Fk4yYoE3tyFlZ2/biqLIDopAl0G//JwswU2M6Mf h1qniOlDgLJ0Oi+njRra7qtxXsc= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fcb9.7fa2779820f0-smtp-out-n03; Thu, 14 Jun 2018 23:39:37 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:36 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb85f747_7c582b25a52efc0c9673@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb85f333_7c582b25a52efc0c96661"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:40 -0000 ----==_mimepart_5b22fcb85f333_7c582b25a52efc0c96661 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/error-code Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb85f333_7c582b25a52efc0c96661-- From nobody Thu Jun 14 16:40:17 2018 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 D267C130F16 for ; Thu, 14 Jun 2018 16:39:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 f1VnluR946YY for ; Thu, 14 Jun 2018 16:39:42 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 BCDE7130E9D for ; Thu, 14 Jun 2018 16:39:42 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019582; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=TDM6LOt+flNiekfZHwFZJiM8Ys/pDpMPkTYIC0D2mo4=; b=RROhd4PkfcfqXhyXClJht9/BtfIG6wmEdTIAMD7ZNs0MEdMxcsnGVhuhe5xHan6K7jd3i4Br EHQOvvugpkQvT25X3EWmvqx54yAQiY/9/OUTnlDX6V2pNccFR3zNIyfP0DahakFXeWh620sz tCteSrHackM8DQZOfvqzMsJSt88= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fcbe.7f0e89fb7e70-smtp-out-n02; Thu, 14 Jun 2018 23:39:42 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:42 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcbe49b8e_42e42b0cd2fa7c109448@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcbe49837_42e42b0cd2fa7c109356"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:44 -0000 ----==_mimepart_5b22fcbe49837_42e42b0cd2fa7c109356 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/migration2 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcbe49837_42e42b0cd2fa7c109356-- From nobody Thu Jun 14 16:40:28 2018 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 417B7130FBB for ; Thu, 14 Jun 2018 16:39:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 G91sh8d2PKPi for ; Thu, 14 Jun 2018 16:39:51 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 00DC7131165 for ; Thu, 14 Jun 2018 16:39:50 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019590; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Nv/LWasQn7/o90zp4ur1gIqIv2Z3UZMzqtRLxN/0loE=; b=EFwBhTHVIKMvRextmYMZRuumPveGqd63hOby9Iom3TGTUHwzOYKs92HAJCHUZNTCV1+90fWG jGxZKtSDR6FpBi/8sBEkXVeP4SZoYs/FQNlX7nXKV2+OIpjOAHrnWdJn/X0ckdsRSFlIUOqK bDbgN59qEq7MMS5atm6QGyBjV/o= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b22fcc6.7fc5915fef60-smtp-out-n03; Thu, 14 Jun 2018 23:39:50 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:50 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcc6bb68b_5ac52aaaad589c103942d@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcc6bb2be_5ac52aaaad589c10393cd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:56 -0000 ----==_mimepart_5b22fcc6bb2be_5ac52aaaad589c10393cd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/recovery_refs Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcc6bb2be_5ac52aaaad589c10393cd-- From nobody Thu Jun 14 16:40:33 2018 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 91E7A1310E0 for ; Thu, 14 Jun 2018 16:39:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Ntmffka6NePI for ; Thu, 14 Jun 2018 16:39:47 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 EA4E4131001 for ; Thu, 14 Jun 2018 16:39:46 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019586; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=jeLcOVbIqT+I0LpDHJpJYKpeavvTHBxU0YjnJBWwCow=; b=KmL+UpYHG13rtg+yypCfzZ97CHtpsDLaE1fsH5jacOl0PDHJTugX3jtHS5SxsEbGxZqM3Wjc dpxPXFdCCsdfyDPR7q6yGOkmR2SKCcTs7bTCDZn6Plb8wk5qEoRiLSBGQURiS023Dys99MTI fjh2pAgCc9EDQEGjNFuszjQj1hs= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fcc2.7f19d9ec7f00-smtp-out-n02; Thu, 14 Jun 2018 23:39:46 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:46 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcc218500_47382adf077b9c04251ab@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcc218131_47382adf077b9c0425093"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:52 -0000 ----==_mimepart_5b22fcc218131_47382adf077b9c0425093 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/client-bad-version Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcc218131_47382adf077b9c0425093-- From nobody Thu Jun 14 16:40:38 2018 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 AE24813101C for ; Thu, 14 Jun 2018 16:39:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 S5eAV6e4YY2u for ; Thu, 14 Jun 2018 16:39:49 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 047F0131024 for ; Thu, 14 Jun 2018 16:39:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019588; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ZX6FpHkCLYCDAPTJUINO5evRZyGDblE8YkC2yBo5MNk=; b=A6BPYD13CKrpVJAK5YQRE8374t3A7xZ9y1X86y30g5HFe+iCTYggHOYv6ZT/y9vpgImCAbpj wC7xQc+8pcCMJ0j5YkUicU1mfNPSui6zyf+OmcvDm3N5RguKbSvmTnIY9tBleNFpFTLaKP8y KU4DLr1q1zirONUnvOVKtMegwQ8= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fcc4.7fe58d36c600-smtp-out-n02; Thu, 14 Jun 2018 23:39:48 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:48 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcc42b976_44122ad389b47c10105374@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcc42b55b_44122ad389b47c1010529c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:39:56 -0000 ----==_mimepart_5b22fcc42b55b_44122ad389b47c1010529c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-allow-length-0 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcc42b55b_44122ad389b47c1010529c-- From nobody Thu Jun 14 16:40:42 2018 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 8A279130FB1 for ; Thu, 14 Jun 2018 16:40:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 w3pOyDRhoOuh for ; Thu, 14 Jun 2018 16:40:03 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 3AE40130F16 for ; Thu, 14 Jun 2018 16:40:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019603; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=w499jxT/Q0uxMrMJgtPScOqYKOyE7VOIQshPVX8lUnY=; b=Uyj/r9+EuQcIkW3CFE1wIHw29cQ7B80RJIm3YA8RLAtYUcKEtyCU7og/bfxoHAw3x8CoCu6q rfPZC5bGXm2zUNNF0832D8wRMioI02UL609onGUgbYI07UPiFT6Ztt0Rp1PksmH76WM+7vPE 26+8XjzCQhNofw+6fvzyvVtIBKY= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b22fcd2.7fdfefc8a570-smtp-out-n01; Thu, 14 Jun 2018 23:40:02 -0000 (UTC) Date: Thu, 14 Jun 2018 16:40:01 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcd1933dd_6062b285a3ebc0c103287@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcd193066_6062b285a3ebc0c103147"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:40:05 -0000 ----==_mimepart_5b22fcd193066_6062b285a3ebc0c103147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-tlp Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcd193066_6062b285a3ebc0c103147-- From nobody Thu Jun 14 16:41:30 2018 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 A29E1130F16 for ; Thu, 14 Jun 2018 16:41:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 t1u9qZnucE83 for ; Thu, 14 Jun 2018 16:41:26 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2D161130E9D for ; Thu, 14 Jun 2018 16:41:26 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019685; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=gXR/ok8oIxf7BN50oxHLcURTuav/wOHgWmK8VlKJkko=; b=vwf/++h6xkfQq+7swI8yewQKb3OfTdxNPMHLK0OV7o7F0z5/PgXDBRT0NeffZiLwKn4tSdif j5BkeLSsbp+MRP+3w85CT+b7zCBARZVuQ2ewYF/mpAuaEsOPE1TyM3KuKzxyV2/epnVeI6Mo W+FKiA2vG1veTfNLHXO19Qw7LP0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd25.7fb5b23e0570-smtp-out-n02; Thu, 14 Jun 2018 23:41:25 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:25 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd257a451_1622ac339a05c18351de@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd2579f9f_1622ac339a05c183507e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:41:28 -0000 ----==_mimepart_5b22fd2579f9f_1622ac339a05c183507e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/no-ack-table-size-changes Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd2579f9f_1622ac339a05c183507e-- From nobody Thu Jun 14 16:41:39 2018 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 688FF130F16 for ; Thu, 14 Jun 2018 16:41:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 puS5VDoNRuDe for ; Thu, 14 Jun 2018 16:41:28 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 22A7A130E9D for ; Thu, 14 Jun 2018 16:41:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019687; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=O80Cy//a2ToUceFLW76Lyf23egjAtv9sPDMrx6nt59U=; b=ypRoDAaRC00dHYn6HBLi8yUiaPTBYSEFOSe5CQ4kP1WqObrAHJs2UDFhSqeiflpbHzVE6k0V QBGJLfyTax97/OjfaRnb1zrjc/tzuEtEl0G1tRSIrmAyeTjkxRo9QFSI2006Voy7ocoYL5pK om1dMzl5Pw8wb4TJfv0JrG1OZQE= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b22fd27.7f8c0be7c120-smtp-out-n01; Thu, 14 Jun 2018 23:41:27 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:26 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd26876c3_7a512b1a818a7c1414735@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd2686fe4_7a512b1a818a7c14146e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:41:30 -0000 ----==_mimepart_5b22fd2686fe4_7a512b1a818a7c14146e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/tls-extension-ffa5 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd2686fe4_7a512b1a818a7c14146e7-- From nobody Thu Jun 14 16:41:47 2018 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 2CE81130FBE for ; Thu, 14 Jun 2018 16:41:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 75sFt5IUYo9H for ; Thu, 14 Jun 2018 16:41:38 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 DDC6B130E9D for ; Thu, 14 Jun 2018 16:41:37 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019697; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zkMtHdBLvkuhqpDmEFdR1Grr1ChPAf1qvMpBkMrQDlk=; b=Vr3AoAo3O91O561GTdsmtKOHHir+BxIjJBZ+NtH6l/ZSJ7PfK1n07SIceEo232zZlQqMIKO7 p8L5ZxMd/2/q7xDS11QJmEgll+bp5G9f6OWE+1JI6w8m49L9Tvxgcq9qH2dm97ANNwSkuOBf sB5ZeV/f5FihaTVoK2vJOx32/Ns= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b22fd31.7f723651b510-smtp-out-n03; Thu, 14 Jun 2018 23:41:37 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:37 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd31a8e24_5ca12aadeecbfc0c873d4@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd31a8966_5ca12aadeecbfc0c87279"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:41:41 -0000 ----==_mimepart_5b22fd31a8966_5ca12aadeecbfc0c87279 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/with-tls Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd31a8966_5ca12aadeecbfc0c87279-- From nobody Thu Jun 14 16:41:52 2018 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 BEB33130E9D for ; Thu, 14 Jun 2018 16:41:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 d92v1yISD66d for ; Thu, 14 Jun 2018 16:41:40 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 61DA1131024 for ; Thu, 14 Jun 2018 16:41:40 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019699; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=oxP0UJflGCBvAJs5EZW18n13slRIaDCikdutzSsMmcE=; b=iGJ/d0mqIy7eS/c4IfOGHxXVCwbzDliHd8GWS6Ud9CpS09tUwJn2SzRvOOlar070DaPftGCR 1PG53CLKV6omodoLYhzPVOpAi2kqxBiv2L7LZ3tvS6ryisFmuaBRAZihnS60NYSENps1lXKR xI4mDfl8mCuPuErPA4eZ6n77I5M= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd33.7fb1b0a5b7e0-smtp-out-n01; Thu, 14 Jun 2018 23:41:39 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:39 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd33b1fe1_6342ae23696dc08290ef@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd33b18d3_6342ae23696dc08289cd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:41:42 -0000 ----==_mimepart_5b22fd33b18d3_6342ae23696dc08289cd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/padding Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd33b18d3_6342ae23696dc08289cd-- From nobody Thu Jun 14 16:42:00 2018 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 AF810130F16 for ; Thu, 14 Jun 2018 16:41:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 nZvxC94HI-IC for ; Thu, 14 Jun 2018 16:41:56 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 64D30130E9D for ; Thu, 14 Jun 2018 16:41:56 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019715; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=3XdTJO8YfI/mnWZjZivavADtVqtUQJtMlkI9JRp6EmU=; b=QlAWZdUSSn4c2poNs5HUEGTfpjfWmGEpUkE7vYaipk0kpz1wbXw8ydCFLR/A1udomrfYQH9F KgDgM1ksaAfY2hU0EwE4Xg4J7J4VaqNlgcumOlrHBHBym9SOHetX/uH0UaVfKS2G8tckmHAk CIVXzfnE8RMe4SPlidVh/IQke9A= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b22fd43.7f51b0d77420-smtp-out-n01; Thu, 14 Jun 2018 23:41:55 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:54 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd42632c6_58372acc23eafc1c1039f7@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd4262d0f_58372acc23eafc1c1038c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:41:58 -0000 ----==_mimepart_5b22fd4262d0f_58372acc23eafc1c1038c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-pace-retransmittable Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd4262d0f_58372acc23eafc1c1038c-- From nobody Thu Jun 14 16:42:10 2018 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 4A313130F16 for ; Thu, 14 Jun 2018 16:42:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 27RUNXOs_H1v for ; Thu, 14 Jun 2018 16:41:59 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 54C1C130E9D for ; Thu, 14 Jun 2018 16:41:59 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019719; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=kfbRvoeQ4QaWJDIVMd0zaIZ0ClzApVqvwWZOMRjAIl8=; b=ayyjeTjZH5NlyMxIJ8DmAg4+5CaUOvKPyrc6ODHTl6gqEnfros+wA8viHOkd6yZjxHdP2fPz 0a6jueSTBNPzlgOUH/balZ8H6x5WUf8qqgrwbxApBd0od3EgphpvvztZw3h4uQRiul5HXe+b Q0tSYLjwTX8S28bNhUzdKKKYAtQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd47.7f8295a3c960-smtp-out-n03; Thu, 14 Jun 2018 23:41:59 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:58 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd46a5ce_55c2ae7decddc148873b@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd46948e_55c2ae7decddc148863b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:01 -0000 ----==_mimepart_5b22fd46948e_55c2ae7decddc148863b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-duplicate-instruction Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd46948e_55c2ae7decddc148863b-- From nobody Thu Jun 14 16:42:16 2018 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 8033E130E9D for ; Thu, 14 Jun 2018 16:42:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 CmBzRs8X7LA9 for ; Thu, 14 Jun 2018 16:42:01 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 59DBC130FBB for ; Thu, 14 Jun 2018 16:42:01 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019721; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=07y57DpGUnvNISfs5cplNnOwv0BDTskTxoiM0FGV4K4=; b=dC4MzSEYp+u2/JeWq1eqY2DWWiWKNcWJ5Ef09tecR2GErnclRLMiBWwZ6Y9SDG+xiUwu5nrS SgzBzXIjzn2XAJ+GWtj/Pfe6sn4Y4iMw963FwhLclwokmmvuFzF72nkq5INKOVf5muzZPwpa rSq25xmYH/D6gW4fBeFMibp54Dk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b22fd48.7fdd2074d810-smtp-out-n01; Thu, 14 Jun 2018 23:42:00 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:59 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd4759eb1_5b5c2b0f07813c101022dc@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd4759915_5b5c2b0f07813c101021b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:03 -0000 ----==_mimepart_5b22fd4759915_5b5c2b0f07813c101021b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-acknowledgement-tracking Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd4759915_5b5c2b0f07813c101021b5-- From nobody Thu Jun 14 16:42:20 2018 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 88497130DBE for ; Thu, 14 Jun 2018 16:42:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 nJttV3OaQFBY for ; Thu, 14 Jun 2018 16:42:05 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 124E7130E9D for ; Thu, 14 Jun 2018 16:42:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019724; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rHLP6DmZsbjAPWFzyHlRxrgRX0TOfYdQG+GhE6WL3+Y=; b=Y58USKNadE11w+2EI5urufi/u+ua2lpTkp+RSLRgMdWffJGm0Y/UHNRNCU355ssLJO3jDL/X p6Bh5bthQ36sF+CFfYNr8G+4T1BkoJiz3Pj4oShTFQyNzzWmOe116s7t9HyA6ZcJTAorkkLn ZI2fg4AMFaNHqQXalQRrqKmV1sk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd4c.7f88012cd4b0-smtp-out-n03; Thu, 14 Jun 2018 23:42:04 -0000 (UTC) Date: Thu, 14 Jun 2018 16:42:03 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd4bd50a1_7de42ab67971dc0c42538@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd4bd4b6b_7de42ab67971dc0c42425"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:07 -0000 ----==_mimepart_5b22fd4bd4b6b_7de42ab67971dc0c42425 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-retransmit-handshake Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd4bd4b6b_7de42ab67971dc0c42425-- From nobody Thu Jun 14 16:42:29 2018 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 DCD11130F16 for ; Thu, 14 Jun 2018 16:42:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 rd_dIfsuRIBm for ; Thu, 14 Jun 2018 16:42:15 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 BA17A130E9D for ; Thu, 14 Jun 2018 16:42:15 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019735; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nExdydgcpNmSrlGtljvTUsj0yY7f73ki/4Gh6WnzSz0=; b=cV+4IVvv70U5j48HHe1O0ctjpHMJNfii2X95dkm7DqpE66n35ES/WWcvKxhTn49YdlHJfpFO OaCfq5nt3yxW5c0SM2J3eJlenjR+ht9HGJrw7H13zxnzy+5kp62dOLbZk7ECf2QOd19oqtHy PLRyERfQybpYBcc7awl+T0H9lv4= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b22fd57.7f72403e3240-smtp-out-n03; Thu, 14 Jun 2018 23:42:15 -0000 (UTC) Date: Thu, 14 Jun 2018 16:42:14 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd5632024_21602ae14d8b1c041055cd@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd5631c9b_21602ae14d8b1c0410549c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:18 -0000 ----==_mimepart_5b22fd5631c9b_21602ae14d8b1c0410549c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/might-vn Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd5631c9b_21602ae14d8b1c0410549c-- From nobody Thu Jun 14 16:42:34 2018 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 83AED130F16 for ; Thu, 14 Jun 2018 16:42:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 C2iDyg_FX-GB for ; Thu, 14 Jun 2018 16:42:17 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 20DCF130E9D for ; Thu, 14 Jun 2018 16:42:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019736; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=yUnou4dvf0r9TXLUBs5EL+sPBSkCZixwrGB6Fh6lNwU=; b=V0aoAS76wLID6NmAX+dOkwEh4E5M9DZ8SykcLXgugnJ8qdmnaFY3NjMdsiuQuqDeu0UGBQMU SjBKnDaqw1HXn0gPv8UpzoQxTk89/p1g4GD0D3wlxEOZOKDAG7hh9xYnCzGy2l0Ne5B5XMgp rpbhnMx7425hLhEKTcwmQmpSdkg= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd58.7f8c0b89c630-smtp-out-n01; Thu, 14 Jun 2018 23:42:16 -0000 (UTC) Date: Thu, 14 Jun 2018 16:42:15 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd574b187_7bfe2afd6a9c1c14179c2@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd574ad8f_7bfe2afd6a9c1c141786a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:19 -0000 ----==_mimepart_5b22fd574ad8f_7bfe2afd6a9c1c141786a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/cross-version-resumption Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd574ad8f_7bfe2afd6a9c1c141786a-- From nobody Thu Jun 14 16:42:39 2018 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 8A7ED130F16 for ; Thu, 14 Jun 2018 16:42:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 J5lyEG4qZgMh for ; Thu, 14 Jun 2018 16:42:18 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 8F8BC130E9D for ; Thu, 14 Jun 2018 16:42:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529019738; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=cPQZRgHGeIw1ZozH3PjvHvT8t8pHCb4dVRg1YmI7VbQ=; b=N/b/gzHgeXSnZ1DCGqFCLpxv6OQSWDdqurXYv0Vp1WTtFV6LrAFn9vPKjuwya+O4EewQOFpJ UussTKbOXKb2V8GQwqITZ4VOrS0ouvfG+nsyrQwAdMBz/fYW9GqWgPPU54sV+cxHpsDH8kHB JUFUmTsTqVbZabtE2SHjeNz7eLU= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b22fd5a.7fab98cdefc0-smtp-out-n03; Thu, 14 Jun 2018 23:42:18 -0000 (UTC) Date: Thu, 14 Jun 2018 16:42:17 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd596d94e_22852aed370cbbfc978e6@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd596d1e9_22852aed370cbbfc977a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:42:20 -0000 ----==_mimepart_5b22fd596d1e9_22852aed370cbbfc977a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/0rtt-after-retry Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd596d1e9_22852aed370cbbfc977a-- From nobody Thu Jun 14 16:47:23 2018 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 4C80C130DBE for ; Thu, 14 Jun 2018 16:47:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Rh9lKyLNpL5b for ; Thu, 14 Jun 2018 16:47:18 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 34B64130E96 for ; Thu, 14 Jun 2018 16:47:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020037; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=u/KG5Gwf/gfrNr6bxcYZot+wkLiKIC4bTOPqP/2VHvc=; b=iUMIGsdOqzUDtJirqQzuYyV168LJNHZcKY87lPSO6JQMu4Ua0n5nZ5IGk/gyRN+xdKrZCRG/ 0Im+IGVPoapRSW0kl+WIcj9h3hanQqf8Hs9u0eMTqZXxVkCjosjloiQJ7B+WT+zerFWUIhw3 u0CaCULi1nAI3VfrYAzFMZQxhao= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fc2c.7f20883fa630-smtp-out-n02; Thu, 14 Jun 2018 23:37:16 -0000 (UTC) Date: Thu, 14 Jun 2018 16:37:16 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc2cdb066_43562ae6fcac5c0c901e1@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc2cdac88_43562ae6fcac5c0c90034"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:47:21 -0000 ----==_mimepart_5b22fc2cdac88_43562ae6fcac5c0c90034 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_boilerplate Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc2cdac88_43562ae6fcac5c0c90034-- From nobody Thu Jun 14 16:48:37 2018 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 4FA99130E96 for ; Thu, 14 Jun 2018 16:48:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Uzrtp38Md3y5 for ; Thu, 14 Jun 2018 16:48:34 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 E2C61130DBE for ; Thu, 14 Jun 2018 16:48:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020113; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ubJkMvDQESHWafhCt6I1vw/l2VzRhKaC2byPjEay974=; b=rpQtt8JbzLFjUgTu+t1Udw7eC+97mJJk86b22FjOggb7V7gg3LSchE37Aiqte7zRwaQl4fDH jRHsHiKyh9HorD8cThz1aRSV/aMFFDh0dkwaVOyAJ7Je8bHdAieSvE/FOOZrqnjfD0MVBSv8 ycmZHDvK+JeZtlwDEsaRl1WqPwA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fc79.7f508d5aa060-smtp-out-n01; Thu, 14 Jun 2018 23:38:33 -0000 (UTC) Date: Thu, 14 Jun 2018 16:38:32 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc78180ab_cd22ae2168adc0c5994b@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc7817cc0_cd22ae2168adc0c598a9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:48:36 -0000 ----==_mimepart_5b22fc7817cc0_cd22ae2168adc0c598a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_indexing Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc7817cc0_cd22ae2168adc0c598a9-- From nobody Thu Jun 14 16:48:51 2018 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 8F1F2130E96 for ; Thu, 14 Jun 2018 16:48:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 JQ0bJtBltBm8 for ; Thu, 14 Jun 2018 16:48:48 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 58C3F130DBE for ; Thu, 14 Jun 2018 16:48:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020127; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Cwk+7jS2A71KnRIALTqAy1vOGYV7yrVTC2fcfAoAFfY=; b=IU8Kpi1O7Xw6q5eN5QnhJ7cgt6jNdS/Rb/QR+rBPt/PZKAgCbnSEPOxi/2tjcp7mBQ5bfMLl qUmXxAzrUMh23Cdpfx6s3OnMt9mlfJy1/IlCvfzckH2N5EDaGCO64c3CLg5GgEVz/LvR3rBW ae1cIAQFH/KyeAUv7kdrK2LXbVk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b22fc86.7fa06977c7b0-smtp-out-n02; Thu, 14 Jun 2018 23:38:46 -0000 (UTC) Date: Thu, 14 Jun 2018 16:38:46 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fc86c9d9e_4d802b15ca68fc089852c@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fc86c9a07_4d802b15ca68fc08984a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:48:50 -0000 ----==_mimepart_5b22fc86c9a07_4d802b15ca68fc08984a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/preferred_address Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fc86c9a07_4d802b15ca68fc08984a6-- From nobody Thu Jun 14 16:51:28 2018 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 55AE9130FAF for ; Thu, 14 Jun 2018 16:51:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.261 X-Spam-Level: X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 z5iW1fWmM0pW for ; Thu, 14 Jun 2018 16:51:25 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 24BCF130DBE for ; Thu, 14 Jun 2018 16:51:25 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020284; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=vPKdHctQxPKKgjYQ3F30rmBdZcV+nHl9CVEgZMi5QQE=; b=sOPU9cZWNE6K2HqHdoy9V6MMySIcWcMz+kT2fLKIk1S0kirHGUTdUEyOBPBz8mO4Z/TzJ/8O huz9Cr3v0wU3V595HbXsbNjrAUrNuz47ddSRqkzPD+xxrmHCG2ZfM+oY9S1efRm9mksyIXAZ x982ci9NVJEqMZYvEidqvsCt7xk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b22fd23.7f98580e45a0-smtp-out-n03; Thu, 14 Jun 2018 23:41:23 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:22 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd22d706e_1c742afc8861fc107112a@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd22d6943_1c742afc8861fc10710ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:51:27 -0000 ----==_mimepart_5b22fd22d6943_1c742afc8861fc10710ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/explain-base-lr Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd22d6943_1c742afc8861fc10710ac-- From nobody Thu Jun 14 16:51:41 2018 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 08B04130FAF for ; Thu, 14 Jun 2018 16:51:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 M8_FDdPyHIUO for ; Thu, 14 Jun 2018 16:51:37 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 B2AD2130DBE for ; Thu, 14 Jun 2018 16:51:37 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020297; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=AHTtfXEgSJovzoEG0wYfLg9GA3vdduoVVujZ9t3M05Y=; b=vI20NLn+8JD2VMwMwkGIRHHfMJOVtdztGfMsDDccqQcNx71QdPkDD+X214LqzNxyv2GI5e27 9c6b2SBdrl7Hf8xa1uMq+8V7ElCa28ycNCR3Nlm9RJKVTtUuRIEajZ+AOKXP+Jbi2+kvb01Q 4V/NbHgz7ik+alAHvneKZh7PZzA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b22fd31.7f8338845ae0-smtp-out-n03; Thu, 14 Jun 2018 23:41:37 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:36 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd3072acd_c5f2b05fd441c082006a@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd30725f7_c5f2b05fd441c0819942"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:51:39 -0000 ----==_mimepart_5b22fd30725f7_c5f2b05fd441c0819942 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/encrypt-key-phase Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd30725f7_c5f2b05fd441c0819942-- From nobody Thu Jun 14 16:51:47 2018 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 E3C24130DBE for ; Thu, 14 Jun 2018 16:51:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 cB00iVcS5BS8 for ; Thu, 14 Jun 2018 16:51:43 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 D0EAD130FAF for ; Thu, 14 Jun 2018 16:51:43 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020303; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9rAt86WjUdM6Q8B2blISXBIk+mjQVYrCzAWlwN2HS+Y=; b=LEcc2tFLAtPuQiuZN1up/PIO6iXECqhM25Rn4tu3BFOZXjSniC8htHdfq5MNjmCp7KwqXsXT Wke2fLLfRS3ZmkIuSdkwwELWKZ6EJNPoh72JP7WRWoHR1rOHunYZId2KWyZHFuTYBSU4gp+9 HPx81I+7QMVLwRSDg8CbX5p1oHE= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fd37.7fb661d74210-smtp-out-n02; Thu, 14 Jun 2018 23:41:43 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:43 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd37aea63_69a32aedbe4bfc04961fa@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd37ae62e_69a32aedbe4bfc04960c4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:51:45 -0000 ----==_mimepart_5b22fd37ae62e_69a32aedbe4bfc04960c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/mnot-patch-spin Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd37ae62e_69a32aedbe4bfc04960c4-- From nobody Thu Jun 14 16:51:59 2018 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 76C86130FAF for ; Thu, 14 Jun 2018 16:51:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 kU5CiojePzuF for ; Thu, 14 Jun 2018 16:51:54 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 27A19130DBE for ; Thu, 14 Jun 2018 16:51:54 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020313; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=TGm54S/TqSsNkJxKlbMmejsw2tsi+LebLJlVVGm8vjE=; b=WoXhvXoezMSaGoGk7XEpg9eC4qCncVOmMCDb34MhoV0P94xLif+dj9okijtZEupzFF5HQrVk CMDwXlmWznvz2zLgZNmwnDWq7ewl4LZIfnCvj8X0QWyXkEEs1ROxPW8dSZqtBwXUQ7KXavlr 506MYji58exUhxx8cI/ES5ZdRls= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b22fd40.7f8cb80544b0-smtp-out-n01; Thu, 14 Jun 2018 23:41:52 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:51 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd3f5615a_8422b11724ddc0438631@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd3f55e05_8422b11724ddc04385a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:51:56 -0000 ----==_mimepart_5b22fd3f55e05_8422b11724ddc04385a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/probing Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd3f55e05_8422b11724ddc04385a-- From nobody Thu Jun 14 16:57:14 2018 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 9B795130FB2 for ; Thu, 14 Jun 2018 16:57:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 YA6_SGLB-vEC for ; Thu, 14 Jun 2018 16:57:10 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0FFF9130DBE for ; Thu, 14 Jun 2018 16:57:10 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529020629; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=t55odakj1Kxqj9GlqeE2d3m8hAiOpz0v4MdcZvew2lg=; b=Hk03M6lzfa8kXUdp+wv5lJGI429Smyc9dH3m/lDw81EUWcVSkB0aMXrS341cJLhuqEiE7uA6 gIfRgDiiDRBajysPcK1W8k8O0PyH1Y2YYGPweuxCOU8WVGEhV5th2WCpJpDkg5FfUsatACaS mS4OdSvO1uvHUmntlh5eYq4lIY0= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b2300d5.7fa29dbc3cc0-smtp-out-n03; Thu, 14 Jun 2018 23:57:09 -0000 (UTC) Date: Thu, 14 Jun 2018 16:57:08 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2300d48230b_274b2ad797819c0c25426@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] f5fd01: HTTP/QUIC doesn't give settings initial values Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2300d481b17_274b2ad797819c0c2536a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 14 Jun 2018 23:57:12 -0000 ----==_mimepart_5b2300d481b17_274b2ad797819c0c2536a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http/grease Home: https://github.com/quicwg/base-drafts Commit: f5fd0135c5b8e10db6c5313304dcdb3232d93ca6 https://github.com/quicwg/base-drafts/commit/f5fd0135c5b8e10db6c5313304dcdb3232d93ca6 Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- HTTP/QUIC doesn't give settings initial values **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2300d481b17_274b2ad797819c0c2536a-- From nobody Thu Jun 14 16:57:21 2018 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 C6B91131001 for ; Thu, 14 Jun 2018 16:57:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HmVT_5aeTj4b for ; Thu, 14 Jun 2018 16:57:15 -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 E772D130DBE for ; Thu, 14 Jun 2018 16:57:14 -0700 (PDT) Date: Thu, 14 Jun 2018 16:57:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529020633; bh=mNPDJKA6RGM9iYz/iSP2a/Mk/A6gO+uK7I0L7QhtNik=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=YGYZ23jinGXhCpJN8233i71cAgSxzI2aOVxEE8u6nlsfKyM483pNYs70hsgG5UJK9 ioHS0+YIoLGwyJo2thacHJOUYxoRdvPCfLvnYatwi/JIm7QsdGKP9WvHm9bcgC+8aT Mu4k1Q2DnU2W7X81Ss3rdCNY33Obo/No8tn9CwpU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2300d9e9568_75bb3ff7bc712f8482434"; 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.26 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: Thu, 14 Jun 2018 23:57:17 -0000 ----==_mimepart_5b2300d9e9568_75bb3ff7bc712f8482434 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1333. Imports text from draft-bishop-httpbis-grease, since feedback has been that we should do this in HQ regardless of what HTTPbis decides. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1446 -- Commit Summary -- * Import grease recommendations * HTTP/QUIC doesn't give settings initial values -- File Changes -- M draft-ietf-quic-http.md (38) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1446.patch https://github.com/quicwg/base-drafts/pull/1446.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/1446 ----==_mimepart_5b2300d9e9568_75bb3ff7bc712f8482434 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1333. Imports text from draft-bishop-httpbis-grease, since feedback has been that we should do this in HQ regardless of what HTTPbis decides.

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

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

Commit Summary

  • Import grease recommendations
  • HTTP/QUIC doesn't give settings initial values

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 mute the thread.

----==_mimepart_5b2300d9e9568_75bb3ff7bc712f8482434-- From nobody Thu Jun 14 17:03:53 2018 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 061EF130EAA for ; Thu, 14 Jun 2018 17:03:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 6x-cbbMmtyQX for ; Thu, 14 Jun 2018 17:03:49 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 6CE9E130DBE for ; Thu, 14 Jun 2018 17:03:49 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529021028; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=6Ii+maoEGnKazvifRv8BmC0Za6eqd7VbO+2NGHfQwKY=; b=fiytFp47POsjX8NTYxcwCjcem+wMyaqRR07CVbQdYqAkSBB/eSjLl6SLlWHZZBLs8GoGcVj8 DC5rbYNRE7+aZn9tEV9WIle6GG890unzsmzkqAxXunUqP5yUchYgERXaji490R0PHsLtt2nU 8u18Nm3jXChpIJKYfcDvAMXgmFI= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b23000b.7fe58d421270-smtp-out-n02; Thu, 14 Jun 2018 23:53:47 -0000 (UTC) Date: Thu, 14 Jun 2018 16:53:47 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b23000bda1c2_4cb92b274c445c0c76372@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 3a20d9: Import grease recommendations Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b23000bd9b6c_4cb92b274c445c0c762ae"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:03:51 -0000 ----==_mimepart_5b23000bd9b6c_4cb92b274c445c0c762ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http/grease Home: https://github.com/quicwg/base-drafts Commit: 3a20d98477c8b3dd03650379974d1a877c1e6cec https://github.com/quicwg/base-drafts/commit/3a20d98477c8b3dd03650379974d1a877c1e6cec Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Import grease recommendations **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b23000bd9b6c_4cb92b274c445c0c762ae-- From nobody Thu Jun 14 17:04:37 2018 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 CE846130EAA for ; Thu, 14 Jun 2018 17:04:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 xjWxC8Z0yAxX for ; Thu, 14 Jun 2018 17:04:34 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 8B74F130DBE for ; Thu, 14 Jun 2018 17:04:34 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529021074; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=01nA5qpaXOiqYvt+Rgz9ZmFOweMJ9OuxXdaSAvAfRTo=; b=Hmq7dKu1ghVhZaEFaAl71GG1r97BzKlKz/iw9IVr1xmpntX/AdhvPc66GqWBE7uaa00C+W/r 7PvhZ1iNT7aE5DIy4kdQlEMArVALYH3lQFGOTuPkX+igzF2MHPJ4jyEnJc8BcfZjoeg0NMo7 RBT6ea1WrVqGGPy10kSDg/v+fXk= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b22fcb5.7f6a2d4eac30-smtp-out-n03; Thu, 14 Jun 2018 23:39:33 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:33 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcb5d9837_52e32ad9d5855c08976ac@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcb5d928f_52e32ad9d5855c08975ab"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:04:36 -0000 ----==_mimepart_5b22fcb5d928f_52e32ad9d5855c08975ab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/symmetric-connection-id Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcb5d928f_52e32ad9d5855c08975ab-- From nobody Thu Jun 14 17:06:01 2018 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 4A080130DBE for ; Thu, 14 Jun 2018 17:05:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 kF891ztgdx0I for ; Thu, 14 Jun 2018 17:05:57 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0DE23130EAA for ; Thu, 14 Jun 2018 17:05:56 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529021156; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=N8KxkdyCOZ2MuBoNUgG4IEYJwYvBET+NFcxe9Rn6Ejs=; b=y9ELpQp0l/YOqQoilcK6l2+oimmY/SNnjgxHqrLELwSNroz2yRTucxP9RiCno6eQsHeTlHbF zhTlKTFwciFIDZrmkD7mNe7GMfgVyt+r7XW89L8vjPhPMrOJkFA4BdV5VHX2O278mZNeSI4q qYKdC0FKxaXf/BONuYcBaq0PJhk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2302e3.7fe4c2037900-smtp-out-n02; Fri, 15 Jun 2018 00:05:55 -0000 (UTC) Date: Thu, 14 Jun 2018 17:05:55 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2302e3b53df_7eb22b171afc5c185419e@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ec94b6: TP to disable migration Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2302e3b4df8_7eb22b171afc5c1854038"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:05:58 -0000 ----==_mimepart_5b2302e3b4df8_7eb22b171afc5c1854038 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/disable_migration Home: https://github.com/quicwg/base-drafts Commit: ec94b63b140ea2d92417a6c9c674d10cb1d6f001 https://github.com/quicwg/base-drafts/commit/ec94b63b140ea2d92417a6c9c674d10cb1d6f001 Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- TP to disable migration **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2302e3b4df8_7eb22b171afc5c1854038-- From nobody Thu Jun 14 17:06:09 2018 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 3A93F130EAA for ; Thu, 14 Jun 2018 17:06:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 svV5larVSGLL for ; Thu, 14 Jun 2018 17:06:07 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 322C7130DBE for ; Thu, 14 Jun 2018 17:06:07 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529021166; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=sBgaJ8o66ofqgjKky0c+CoscynTf7PUZeo19phHd6kY=; b=npXu9L3twif32MsS93BEIrhvRiHsyickjVouIMYn0raJyLc2uya3uHDxxk8/60KKxyeGPy78 7LSeVaVFBFSaTqTCcbo4kdM/E+/ZB2Oe7El81mTTEUde9wxbZxBoHKbQyMYYjLFHeXsqSbNK /xo7FbXWosSb/SL3JSlNtdKVba0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b22fd12.7fac4068fb70-smtp-out-n03; Thu, 14 Jun 2018 23:41:06 -0000 (UTC) Date: Thu, 14 Jun 2018 16:41:05 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd118da76_38c82aca87935c0c34449@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd118d6a6_38c82aca87935c0c3436f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:06:08 -0000 ----==_mimepart_5b22fd118d6a6_38c82aca87935c0c3436f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/simplify-uploads Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd118d6a6_38c82aca87935c0c3436f-- From nobody Thu Jun 14 17:06:56 2018 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 1EBA6130EAA for ; Thu, 14 Jun 2018 17:06:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vHkDqk6BJviM for ; Thu, 14 Jun 2018 17:06:52 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B00AE130DBE for ; Thu, 14 Jun 2018 17:06:52 -0700 (PDT) Date: Thu, 14 Jun 2018 17:06:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529021211; bh=DD4o0/NOxpGyrBWIgmt3o/PF9xSNHzpjvAMKGzUJTyY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=MkkuQoGH10fTYRqQ4oYdiYh09cDFvpDtPR740k1bdLJCzpvRF0F6BOkN543o2sXXS pL63EglI2vSAKKhWIWY7M+DnmYsYjALUJ0/OQ0FSRMUeLzB58+vjvI282oaGP8g5DZ UybpWUGkLI+ZVwxOS1++rqCmZcHV0+eN7YLzzNCQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23031bdff5d_405b2ab4b0992f5c12687"; 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.26 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: Fri, 15 Jun 2018 00:06:54 -0000 ----==_mimepart_5b23031bdff5d_405b2ab4b0992f5c12687 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1271. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1447 -- Commit Summary -- * TP to disable migration -- File Changes -- M draft-ietf-quic-transport.md (12) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1447.patch https://github.com/quicwg/base-drafts/pull/1447.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/1447 ----==_mimepart_5b23031bdff5d_405b2ab4b0992f5c12687 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1271.

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

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

Commit Summary

  • TP to disable migration

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 mute the thread.

----==_mimepart_5b23031bdff5d_405b2ab4b0992f5c12687-- From nobody Thu Jun 14 17:24:56 2018 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 3E5A0130EAA for ; Thu, 14 Jun 2018 17:24:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 83Wj4N5Hxsh2 for ; Thu, 14 Jun 2018 17:24:50 -0700 (PDT) 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 7AC0D130E1A for ; Thu, 14 Jun 2018 17:24:50 -0700 (PDT) Date: Thu, 14 Jun 2018 17:24:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529022289; bh=E8R88ItRBM1Hnknru2OzAfLqhLJJkRpJrm7rt3uqCPU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZPzqD3ZA2VnibH+jXYrVNfHqam5Ojou/9PhzH/0138/m939YncP4ikn1USisVKkJU AIwN4J4DNff8TOtxeHJm/3/3oaGfNfzCEPzBX2GT3TKkelU40n3EHorYMhnLR3EQ8R pbWYOFfy0T61JNG+TbJWWbPos42u0IBs+Db9uMvs= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2307518059f_2ebc2ae287cccf601796"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 00:24:54 -0000 ----==_mimepart_5b2307518059f_2ebc2ae287cccf601796 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit LGTM. An observation: we have discussed unidirectional stream type as an extension point. If that PR lands then it would make sense to grease the type byte too. I can live with that being defined in a separate PR if it helps. -- 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/1446#issuecomment-397477249 ----==_mimepart_5b2307518059f_2ebc2ae287cccf601796 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

LGTM.

An observation: we have discussed unidirectional stream type as an extension point. If that PR lands then it would make sense to grease the type byte too. I can live with that being defined in a separate PR if it helps.

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

----==_mimepart_5b2307518059f_2ebc2ae287cccf601796-- From nobody Thu Jun 14 17:32:16 2018 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 8B213130EC5 for ; Thu, 14 Jun 2018 17:32:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nFFvwO3_SxNk for ; Thu, 14 Jun 2018 17:32:12 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABFD0130E1A for ; Thu, 14 Jun 2018 17:32:12 -0700 (PDT) Date: Thu, 14 Jun 2018 17:32:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529022731; bh=kmsT48CvS6AyX92su3yDF/E3WJCu5GW+t1Alf6vbc84=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=b1QWvK3a7b1qMCFvyCsJIsI/OXa7ycAteghH5vNiM3LVXuKrIM+9tyMr4yJKAjgl+ xCP/mw4rwl+dAQD9uLZvQJojvGnowrVRzJZ2ssLm8qYf2Cm68Ofo4IlRUFRANAya6z BjBrGW31jKsL3iBbhlFmeDKCl/yyeX+OxygLE2lY= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23090bd1fa6_44732adb6bcf6f54720c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Fri, 15 Jun 2018 00:32:15 -0000 ----==_mimepart_5b23090bd1fa6_44732adb6bcf6f54720c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Looks good to me but I wonder if we should make this transport parameter agnostic of client / server (i.e. who initiates the connection first) and just refer to a peer disabling migration. If we want to address server migration and peer-to-peer, then we may need to make it apply in both directions. @MikeBishop you may want to add @ianswett as a reviewer as he also requested this TP. -- 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/1447#issuecomment-397478506 ----==_mimepart_5b23090bd1fa6_44732adb6bcf6f54720c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Looks good to me but I wonder if we should make this transport paramet= er agnostic of client / server (i.e. who initiates the connection first) = and just refer to a peer disabling migration. If we want to address serve= r migration and peer-to-peer, then we may need to make it apply in both d= irections. @MikeBishop you may wan= t to add @ianswett as a reviewer as= he also requested this TP.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23090bd1fa6_44732adb6bcf6f54720c8-- From nobody Thu Jun 14 17:34:27 2018 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 41B0D130EC5 for ; Thu, 14 Jun 2018 17:34:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 i9UDKQsy9jCS for ; Thu, 14 Jun 2018 17:34:24 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 02C7A130E1A for ; Thu, 14 Jun 2018 17:34:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529022863; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=AGBMYwiSm4ULPpT7NDRFYVLOwM2VvtpU/G5uW3GNmhk=; b=yPSRgmLp0Q8e3E77S3nTgqdQp35dmN7l7pF7/0/bgI5N910vyWXDpklMYhKm1E03jB52lyYc +on/S+S7RpSi674c9CeDef6mlgWbQjTZAUmG7GlS3+IOItuj16Uzw0EFQUgUjf1KH74UzzUX J+ZbukDOHBnI8MosiBLv412nORA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b22fcab.7f4771d04d20-smtp-out-n02; Thu, 14 Jun 2018 23:39:23 -0000 (UTC) Date: Thu, 14 Jun 2018 16:39:22 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fcaaefa11_4d012ac268afbc0c676ef@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fcaaef5c4_4d012ac268afbc0c67552"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:34:26 -0000 ----==_mimepart_5b22fcaaef5c4_4d012ac268afbc0c67552 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-generating-acks Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fcaaef5c4_4d012ac268afbc0c67552-- From nobody Thu Jun 14 17:37:07 2018 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 B4535130EC5 for ; Thu, 14 Jun 2018 17:37:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 OmeOcme92dgp for ; Thu, 14 Jun 2018 17:37:03 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 924A1130E1A for ; Thu, 14 Jun 2018 17:37:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529023022; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=WdKNpbVmfrIbJ7QxqrvQpz0DHgH7597KUQh1H9qLi8A=; b=FFI+oNbEh86Xa4aonKITVjW+bA/I6Su1BYsSxYVSlzMLm7hxdzzIgsiIhzTqnjv66ZrefIkl VJ3xpwU+LWHFifR5m20ysHtPQnoRFKepp4C1fRo6TaOSuZznt0pZT6LG4CXtLrIpz3jNdRDP ImR3IB/Yb+kuU6ye8O6WlU3ew+I= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b22fd4a.7fcad02f5720-smtp-out-n01; Thu, 14 Jun 2018 23:42:02 -0000 (UTC) Date: Thu, 14 Jun 2018 16:42:01 -0700 From: MikeBishop Reply-To: MikeBishop To: quic-issues@ietf.org Message-ID: <5b22fd49f17d7_62562b0b852a7c0c91244@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b22fd49f1332_62562b0b852a7c0c91133"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 00:37:05 -0000 ----==_mimepart_5b22fd49f1332_62562b0b852a7c0c91133 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-onepass Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b22fd49f1332_62562b0b852a7c0c91133-- From nobody Thu Jun 14 17:37:32 2018 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 D4D74130EC5 for ; Thu, 14 Jun 2018 17:37:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 6sUFIc2RFukk for ; Thu, 14 Jun 2018 17:37:28 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 607F8130E1A for ; Thu, 14 Jun 2018 17:37:28 -0700 (PDT) Date: Thu, 14 Jun 2018 17:37:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529023047; bh=U9I5/XwTOKpHLTm3qkTfmA2jUrvWPIojnpl7vMsDNO4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wxFFnv9bZ+iN7Bxkq8yMVnZGf3NV2CUCr6fDDc0Qbat+WGAd1dBJ7ZPjRK4I3EnB1 cQbSQor3IXCu/P0xRcX9S8At8rueImkTpERBteu88G7vLi/rkXZ3ixoI6LMsnDhkjl jTj4HiSNanVI02ZCrqvjAP+DDCakQ7h75SKEJJ/Y= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b230a47915e2_52672ad2fc522f5c5160"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 00:37:30 -0000 ----==_mimepart_5b230a47915e2_52672ad2fc522f5c5160 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks requested changes on this pull request. I agree with @pravb here. I don't think we should make this server specific. -- 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/1447#pullrequestreview-129014332 ----==_mimepart_5b230a47915e2_52672ad2fc522f5c5160 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks requested changes on this pull request.

I agree with @pravb here. I don't think we should make this server specific.

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

----==_mimepart_5b230a47915e2_52672ad2fc522f5c5160-- From nobody Thu Jun 14 18:50:10 2018 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 C3F4E130EC0 for ; Thu, 14 Jun 2018 18:50:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jSSO5Yf93I5n for ; Thu, 14 Jun 2018 18:50:07 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27290129385 for ; Thu, 14 Jun 2018 18:50:07 -0700 (PDT) Date: Thu, 14 Jun 2018 18:50:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529027406; bh=peaVMCNbSBMQrBiLqEKMDcZqV+PRp/6oajAfFdsMdWs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rCavM7NgxH1UmOYoHe+Q/WURzeQ2TjnmsrK/XEz/7K3GTnPEhYxTkH/HASnxzktIP 68MT+ELOPbzfiS05fvPT4eErCO5cwImvNxsV0Af3KSIwc+y5s7cJiHhaeGCtqnfk+G N00CP77XUMMLYUNZix2MMxk18QFVH+P2j2PT4hDw= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b231b4e1db29_2a493fe281d7af84100548"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 15 Jun 2018 01:50:09 -0000 ----==_mimepart_5b231b4e1db29_2a493fe281d7af84100548 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit erickinnear commented on this pull request. > @@ -1289,6 +1290,13 @@ preferred_address (0x0004): : The server's Preferred Address is used to effect a change in server address at the end of the handshake, as described in {{preferred-address}}. +disable_migration (0x0009): + +: The server does not support migration of connections to a different IP + address. Clients MUST NOT send any packets, including probing packets, from an + IP address other than that used to perform the handshake. This parameter This seems mildly ambiguous -- isn't there a scenario where the client doesn't necessarily have control over that IP? I'm not saying that that's the common case, but it could happen that the client doesn't just have a different port after a NAT rebinding, but that it actually shows up as coming from a different address entirely depending on how things are routed between NATs, especially after inactivity. -- 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/1447#pullrequestreview-129022900 ----==_mimepart_5b231b4e1db29_2a493fe281d7af84100548 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@erickinnear commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1289,6 +1290,13 @@ preferred_address (0x0004):
 : The server's Preferred Address is used to effect a change in server address at
   the end of the handshake, as described in {{preferred-address}}.
 
+disable_migration (0x0009):
+
+: The server does not support migration of connections to a different IP
+  address. Clients MUST NOT send any packets, including probing packets, from an
+  IP address other than that used to perform the handshake.  This parameter

This seems mildly ambiguous -- isn't there a scenario where the client doesn't necessarily have control over that IP? I'm not saying that that's the common case, but it could happen that the client doesn't just have a different port after a NAT rebinding, but that it actually shows up as coming from a different address entirely depending on how things are routed between NATs, especially after inactivity.

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

----==_mimepart_5b231b4e1db29_2a493fe281d7af84100548-- From nobody Thu Jun 14 18:52:25 2018 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 2A48312F1AB for ; Thu, 14 Jun 2018 18:52:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QMF3akNA-6s9 for ; Thu, 14 Jun 2018 18:52:22 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C720129385 for ; Thu, 14 Jun 2018 18:52:22 -0700 (PDT) Date: Thu, 14 Jun 2018 18:52:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529027541; bh=gFmfCzdvRpeFUKv1ZJNwaqczCMPvzoMvkDq6eMlwnGE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FO3mjdQs/8zOH8pYj2iW9Pj8ztWKV7U7VwLnxH8Coh9icmvyJZ4+aU/shTsdB3nFQ 1+cJL4pCQQHO8Zcv9pBfdoZcb98kv/QLu/N0IZawJ7H32XmTvIY5rBig75UR6EROuu 3qp6WQnC8GqLWf8ZqWX8V0oQVo2GrQA/ZIdLSg/A= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b231bd591d0c_2a503fe281d7af84105422"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 15 Jun 2018 01:52:24 -0000 ----==_mimepart_5b231bd591d0c_2a503fe281d7af84105422 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit There's still the issue that many expected migrations aren't explicitly initiated by the client but rather by the network (NAT rebinding, etc). If we want clients to be able to switch connection IDs on the same path, and we also want to be resilient to the path changing out from underneath the client, then we need to be very careful how we specify such a transport parameter. -- 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/1271#issuecomment-397489893 ----==_mimepart_5b231bd591d0c_2a503fe281d7af84105422 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

There's still the issue that many expected migrations aren't explicitl= y initiated by the client but rather by the network (NAT rebinding, etc).= If we want clients to be able to switch connection IDs on the same path,= and we also want to be resilient to the path changing out from underneat= h the client, then we need to be very careful how we specify such a trans= port parameter.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b231bd591d0c_2a503fe281d7af84105422-- From nobody Thu Jun 14 19:06:32 2018 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 63667128CF3 for ; Thu, 14 Jun 2018 19:06:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mdW_KzVzn2Bu for ; Thu, 14 Jun 2018 19:06:28 -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 7D427127AC2 for ; Thu, 14 Jun 2018 19:06:28 -0700 (PDT) Date: Thu, 14 Jun 2018 19:06:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529028387; bh=s3XXcC75fHwimVMdCd/5tEV09BcRg+bHB2xYJ6smGxg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w76FE+5+DI4jZy7y4C1LF2erUdddvZVUw2TpRttMoah0ZbiCd9fvwUFj7uNznejP9 qU3Mu0zYvn94v+1q34TmPdGMFZ1bGBZRBXf8VQhJuAUMKNt7XBSi2hEV92fLtL5bmM 6WX0aTndWwRjhfpBkbnKmMuQS9u72RwF5zkh1ks4= From: Tommy Pauly Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b231f23c7ffa_340f3f9820726f801095d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: tfpauly 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.26 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: Fri, 15 Jun 2018 02:06:31 -0000 ----==_mimepart_5b231f23c7ffa_340f3f9820726f801095d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If the option is explicitly to disable migration, and migration is assumed to be supported by default, I think the text can be written sufficiently carefully. We want to allow the default case for clients to work. The peer-to-peer case of one peer being stuck behind a NAT, signaling that the other peer shouldn't migrate is an interesting point, and one of the points I find more compelling for not migrating automatically to the same address. It is a bit comparable to the NAT detection mechanisms used by IKE, which determine some later protocol behavior. Let's make sure to call out this scenario in the text, as well as others, perhaps specifying that deployments that don't fall into these scenarios in which migration is not useful SHOULD NOT disable migration, so as to encourage mobility of clients. Doing the negotiation in the handshake as a TP is preferable to version indication in this case, I'd argue. -- 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/1271#issuecomment-397492029 ----==_mimepart_5b231f23c7ffa_340f3f9820726f801095d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If the option is explicitly to disable migration, and migration is ass= umed to be supported by default, I think the text can be written sufficie= ntly carefully. We want to allow the default case for clients to work.

The peer-to-peer case of one peer being stuck behind a NAT, signaling = that the other peer shouldn't migrate is an interesting point, and one of= the points I find more compelling for not migrating automatically to the= same address. It is a bit comparable to the NAT detection mechanisms use= d by IKE, which determine some later protocol behavior. Let's make sure t= o call out this scenario in the text, as well as others, perhaps specifyi= ng that deployments that don't fall into these scenarios in which migrati= on is not useful SHOULD NOT disable migration, so as to encourage mobilit= y of clients.

Doing the negotiation in the handshake as a TP is preferable to versio= n indication in this case, I'd argue.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b231f23c7ffa_340f3f9820726f801095d-- From nobody Thu Jun 14 20:36:00 2018 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 3E036127332 for ; Thu, 14 Jun 2018 20:35:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3IkETGjciWMy for ; Thu, 14 Jun 2018 20:35:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ECD1130ED1 for ; Thu, 14 Jun 2018 20:35:52 -0700 (PDT) Date: Thu, 14 Jun 2018 20:35:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529033751; bh=dviBe1oJ3uHvNEXyKDOcD9XAnE03obVMtGlAUf51MKs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=OF5UZiHIfJxSyv9QiA1gQXFnvASDyim6yJkftzcU63SLu+7X/k56ejnF0ARnEL1AY r6O8wkurRe4aVY99Bf9l3xEoUEmbgrVEHbojfdCxyRkmeqU3c4h8Vu9UVs9J3UQloc ob16oI7ywn7XsU9ZwjgA/Umed7TnvnllGXvBxzIs= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] What if the packet number of a retry packet is not zero? (#1448) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23341740823_3b793fb433c7ef802860c7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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: Fri, 15 Jun 2018 03:35:59 -0000 ----==_mimepart_5b23341740823_3b793fb433c7ef802860c7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The draft-12 spec says: ``` The Packet Number field of a Retry packet MUST be set to 0. This value is subsequently protected as normal. [[Editor's Note: This isn't ideal, because it creates a "cheat" where the client assumes a value. That's a problem, so I'm tempted to suggest that this include any value less than 2^30 so that normal processing works - and can be properly exercised.]] ``` I understand the requirement on the sender side, but what about receivers? Does it mean that the number is ignored by receivers, or that packets with non-zero numbers are just dropped on the floor, or that this is treated like a protocol error and a connection close is sent? Oh, wait, this is a retry packet, the sender side connection is already closed! Of course, if the receivers do not somehow enforce the requirement, broken senders will have no incentive to fix their code. But then, if receivers do enforce the requirement by dropping the packet, they will end up repeating the Client Hello 4 times, receive an incorrect retry each time, ignore it, and finally release the connection after the last timer elapsed. Not ideal either. My proposal would be to add text. "Clients who receive an otherwise valid Retry packet with a non-zero PN value should treat this as a protocol error and immediately terminate the connection." -- 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/1448 ----==_mimepart_5b23341740823_3b793fb433c7ef802860c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The draft-12 spec says:

   The Packet Number field of a Retry packet MUST be set to 0.  This
   value is subsequently protected as normal.  [[Editor's Note: This
   isn't ideal, because it creates a "cheat" where the client assumes a
   value.  That's a problem, so I'm tempted to suggest that this include
   any value less than 2^30 so that normal processing works - and can be
   properly exercised.]]

I understand the requirement on the sender side, but what about receivers? Does it mean that the number is ignored by receivers, or that packets with non-zero numbers are just dropped on the floor, or that this is treated like a protocol error and a connection close is sent? Oh, wait, this is a retry packet, the sender side connection is already closed!

Of course, if the receivers do not somehow enforce the requirement, broken senders will have no incentive to fix their code. But then, if receivers do enforce the requirement by dropping the packet, they will end up repeating the Client Hello 4 times, receive an incorrect retry each time, ignore it, and finally release the connection after the last timer elapsed. Not ideal either.

My proposal would be to add text. "Clients who receive an otherwise valid Retry packet with a non-zero PN value should treat this as a protocol error and immediately terminate the connection."

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

----==_mimepart_5b23341740823_3b793fb433c7ef802860c7-- From nobody Thu Jun 14 22:13:04 2018 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 6C482130DC3 for ; Thu, 14 Jun 2018 22:13:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oP9nWXrTCHpR for ; Thu, 14 Jun 2018 22:13:00 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 820D1130DC2 for ; Thu, 14 Jun 2018 22:13:00 -0700 (PDT) Date: Thu, 14 Jun 2018 22:12:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529039579; bh=rMyX0Kl7LuIJIcm+NrGcvhd8RiakjGA0xfzb8Og6U+k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hHdsLLfgxUKw2f7cx97evw1X57dDmurh+XM7qPFkwezDMXfZp1LAkPHj8gVtWBHIl +W4GPqcq5ScFn/AFDZs/XAn4uXIrIiKaVAz7XQMa3kFLRe14Cx0jNUq+YelFFoOgvs pczQD9f5FMHkBOR0MBmGxX47mz2hmovhas14rv0k= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b234adb7fc8b_3d913f89903e2f842173d7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Fri, 15 Jun 2018 05:13:03 -0000 ----==_mimepart_5b234adb7fc8b_3d913f89903e2f842173d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @erickinnear supporting connection migration on server side requires updating of load balancers to be QUIC aware which will not be possible in many deployments for a while especially when the web server and the load balancer are not under the same administrative domain. In these cases even NAT rebinding will not work correctly and the solution is to use keep-alives if connections become inactive and want to be long-lived. So if the server doesn't negotiate the TP then the client can automatically turn on keep-alives. @tfpauly I am fine making the default as enabled and the TP flips it to disabled. The goal is to allow incremental deployment until load balancers can be upgraded. -- 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/1271#issuecomment-397515603 ----==_mimepart_5b234adb7fc8b_3d913f89903e2f842173d7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@erickinnear supporting conne= ction migration on server side requires updating of load balancers to be = QUIC aware which will not be possible in many deployments for a while esp= ecially when the web server and the load balancer are not under the same = administrative domain. In these cases even NAT rebinding will not work co= rrectly and the solution is to use keep-alives if connections become inac= tive and want to be long-lived. So if the server doesn't negotiate the T= P then the client can automatically turn on keep-alives.

@tfpauly I am fine making the defa= ult as enabled and the TP flips it to disabled. The goal is to allow incr= emental deployment until load balancers can be upgraded.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b234adb7fc8b_3d913f89903e2f842173d7-- From nobody Thu Jun 14 22:29:13 2018 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 5B13D130DC5 for ; Thu, 14 Jun 2018 22:29:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8rSVGQ-e-EDg for ; Thu, 14 Jun 2018 22:29:09 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D797130E4C for ; Thu, 14 Jun 2018 22:29:09 -0700 (PDT) Date: Thu, 14 Jun 2018 22:29:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529040548; bh=+NoQjF8E/zQIOojsdVFnXTtVxur+5PhGrVgY2YuQ8uM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0WUrF3f6XDDA5OltefYRbU4CTh4+Yw5//1q2UcGxxYZKl2sby8mAjs0rJEEWxlv2q RkyEa7Clnx66Y/5zX/qXewk3JiQOd9Lwf44GVk6hBqEZPVuEM8s0yf6Uyl5VvSjONw q6I3jzq3OL1diYOTM7NFm6ziJkeTaDCTOha26lOE= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b234ea4a395d_5ee12ad927cb0f542587d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 15 Jun 2018 05:29:12 -0000 ----==_mimepart_5b234ea4a395d_5ee12ad927cb0f542587d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, I think we're in agreement that it will be useful to have a transport parameter, I just want to make sure that we're careful not to back clients into a corner where they cannot behave correctly due to influences outside of their control. A client that is behind a NAT might be surprised that the server thinks it's behaving incorrectly if it wasn't aware that some portion of the routing/NAT binding changed significantly. That's mostly a wording issue, I think, not a problem with the concept itself. It almost seems like it could be as simple as using the same terminology that we used previously ("local address" vs. "from an IP address"): ``` The server does not support connection migration (link to the other section). Clients MUST NOT send any packets, including probing packets (probably use the real name from later), from a local address other than that used to perform the handshake. ``` It might be interesting to add, either in the definition or later where the second reference is made, a note that clients may wish to be more aggressive about using keepalives if connection migration is disabled. -- 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/1271#issuecomment-397517679 ----==_mimepart_5b234ea4a395d_5ee12ad927cb0f542587d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, I think we're in agreement that it will be useful to have a trans= port parameter, I just want to make sure that we're careful not to back c= lients into a corner where they cannot behave correctly due to influences= outside of their control. A client that is behind a NAT might be surpris= ed that the server thinks it's behaving incorrectly if it wasn't aware th= at some portion of the routing/NAT binding changed significantly.

That's mostly a wording issue, I think, not a problem with the concept= itself.

It almost seems like it could be as simple as using the same terminolo= gy that we used previously ("local address" vs. "from an IP address"): 

The server does not support connection migration (link to the =
other section). =

Clients MUST NOT send any packets, including probing packets (probably =

use the real name from later), from a local address other than that =

used to perform the handshake.

It might be interesting to add, either in the definition or later wher= e the second reference is made, a note that clients may wish to be more a= ggressive about using keepalives if connection migration is disabled.

=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b234ea4a395d_5ee12ad927cb0f542587d0-- From nobody Thu Jun 14 22:34:05 2018 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 BB695130DC3 for ; Thu, 14 Jun 2018 22:34:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 g_ZSAY3FBv5Y for ; Thu, 14 Jun 2018 22:34:01 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA0E1130DC2 for ; Thu, 14 Jun 2018 22:34:01 -0700 (PDT) Date: Thu, 14 Jun 2018 22:34:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529040841; bh=GHRTKuZaJyl9e6d2L1OC8zbuJFojMiJ+fHXA5VL3m3U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Emv/w25HoTqNdKUPtXbkPSng9rj4zpsIO5CxXk19a1ZmkUUGdZnMJn3Ma4+QqSRgu CIXP0ZXCj9r+JtbwRQ1D78dAN5Z8lmp2uWxW9Sm7BmfKy1G/W/m6e3WLluNOcD+pD/ MlSsnKzX149EYsvPkh/Sw2GsQv5JZAgeQeO7UCAg= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if the packet number of a retry packet is not zero? (#1448) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b234fc92696c_57353fc8d1134f78206452"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 15 Jun 2018 05:34:04 -0000 ----==_mimepart_5b234fc92696c_57353fc8d1134f78206452 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Since the sender can=E2=80=99t be trusted it is better to drop the packet= . In non-zero value is theoretical and therefore most likely abuse. -- = 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/1448#issuecomment-397518267= ----==_mimepart_5b234fc92696c_57353fc8d1134f78206452 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Since the sender can=E2=80=99t be trusted it is better to drop the pac= ket. In non-zero value is theoretical and therefore most likely abuse.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b234fc92696c_57353fc8d1134f78206452-- From nobody Thu Jun 14 22:35:33 2018 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 6F57B130DC3 for ; Thu, 14 Jun 2018 22:35:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 o5zlQ8T0AZdF for ; Thu, 14 Jun 2018 22:35:30 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9BA4130DC2 for ; Thu, 14 Jun 2018 22:35:29 -0700 (PDT) Date: Thu, 14 Jun 2018 22:35:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529040929; bh=XlRz/wZb42olxXwdzK0J9973Na0gRJZp3kH5JkFyTeA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IjRuzyRqNMGXty/XPoUT+ljcKhhoQr/Ws5YUGH4GxVUKXsVZ9gx3JrTHQZ21mFUCn HXRxSbI8GC7OuXA4tOl11qF2+n7HmwUZsoFS+HMsoyBvz8pXB6H7FO5PklajfKspqK 82N1oPfITKT/Da/VxFDzXCy21uA0mK5AaWBXvZu8= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2350211a5aa_6c412b17ff2aef58123320"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 15 Jun 2018 05:35:32 -0000 ----==_mimepart_5b2350211a5aa_6c412b17ff2aef58123320 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit erickinnear commented on this pull request. > @@ -1289,6 +1290,13 @@ preferred_address (0x0004): : The server's Preferred Address is used to effect a change in server address at the end of the handshake, as described in {{preferred-address}}. +disable_migration (0x0009): + +: The server does not support migration of connections to a different IP + address. Clients MUST NOT send any packets, including probing packets, from an + IP address other than that used to perform the handshake. This parameter I think most of my objection here relates to terminology. Perhaps: ``` The server does not support connection migration ({{migration}}). Clients MUST NOT send any packets, including those intended for path validation ({{migrate-validate}}), from a local endpoint other than that used to perform the handshake. ... ``` -- 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/1447#discussion_r195636668 ----==_mimepart_5b2350211a5aa_6c412b17ff2aef58123320 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@erickinnear commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1289,6 +1290,13 @@ preferred_address (0x0004):
 : The server's Preferred Address is used to effect a change in server address at
   the end of the handshake, as described in {{preferred-address}}.
 
+disable_migration (0x0009):
+
+: The server does not support migration of connections to a different IP
+  address. Clients MUST NOT send any packets, including probing packets, from an
+  IP address other than that used to perform the handshake.  This parameter

I think most of my objection here relates to terminology. Perhaps:

The server does not support connection migration ({{migration}}). 
Clients MUST NOT send any packets, including those intended for 
path validation ({{migrate-validate}}), from a local endpoint other
than that used to perform the handshake. ...

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

----==_mimepart_5b2350211a5aa_6c412b17ff2aef58123320-- From nobody Thu Jun 14 22:52:46 2018 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 8B0C2126DBF for ; Thu, 14 Jun 2018 22:52:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 so5w8pW7vCfY for ; Thu, 14 Jun 2018 22:52:42 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39444130DC3 for ; Thu, 14 Jun 2018 22:52:42 -0700 (PDT) Date: Thu, 14 Jun 2018 22:52:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529041961; bh=P/uyS7f2Zt13XOzz3RJZWvx/GOu/Mgw4hoy+JE6kkdA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KkZwyZtmtdph15j1oW4oDejARpNU9u0t3XeVG3TimctMRHswBFDKJ/AvYsTfwrfpM Pf7kJ5v9bs96rY0UfylHdDx9suzqbMEZhS5LSsS6bHbllQYkpG9UF/o3oad8ttWR9u Z3Ot4VQHnSIZ0JseEZvo4nx3u2cv4HlZlnTW1tKk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2354295ba27_2dd2aaae207af5010819b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 15 Jun 2018 05:52:45 -0000 ----==_mimepart_5b2354295ba27_2dd2aaae207af5010819b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > @@ -1289,6 +1290,13 @@ preferred_address (0x0004): : The server's Preferred Address is used to effect a change in server address at the end of the handshake, as described in {{preferred-address}}. +disable_migration (0x0009): + +: The server does not support migration of connections to a different IP + address. Clients MUST NOT send any packets, including probing packets, from an + IP address other than that used to perform the handshake. This parameter My understanding is that one of the motives of having this option is to allow running QUIC servers behind a load balancer that distributes the load based on the 5-tuple. Assuming that is true, it is necessary to minimize the chance of client rebinding to not only a different IP address but to a different port as well. -- 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/1447#discussion_r195638485 ----==_mimepart_5b2354295ba27_2dd2aaae207af5010819b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1289,6 +1290,13 @@ preferred_address (0x0004):
 : The server's Preferred Address is used to effect a change in server address at
   the end of the handshake, as described in {{preferred-address}}.
 
+disable_migration (0x0009):
+
+: The server does not support migration of connections to a different IP
+  address. Clients MUST NOT send any packets, including probing packets, from an
+  IP address other than that used to perform the handshake.  This parameter

My understanding is that one of the motives of having this option is to allow running QUIC servers behind a load balancer that distributes the load based on the 5-tuple.

Assuming that is true, it is necessary to minimize the chance of client rebinding to not only a different IP address but to a different port as well.

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

----==_mimepart_5b2354295ba27_2dd2aaae207af5010819b-- From nobody Fri Jun 15 00:34:36 2018 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 F0FA7130DD3 for ; Fri, 15 Jun 2018 00:34:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HF8SNMVshk-H for ; Fri, 15 Jun 2018 00:34:32 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB870130DC2 for ; Fri, 15 Jun 2018 00:34:31 -0700 (PDT) Date: Fri, 15 Jun 2018 00:34:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529048070; bh=IYRGMV0XJsBqHQsHP+eW1CbKzjS8o21JYU7898OXOiM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fBoxo6KhpN18MCE96A/VZ3mzU2Tc4WBnzqXnrt+0ODCjbmTPqX/SyGdmyVyxITCd4 upY4zkQkIO4FQLF0JNHrUejoIUYkUCmuQ6HBE6ZpgNqNEyZ5JAxRMJmCebZAehjw2u yDO9tX9bm6UusQBNom8QVEW0J3a+rng9I59wCQuo= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b236c06ec103_6ddb2ab392d7cf601276272"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Fri, 15 Jun 2018 07:34:35 -0000 ----==_mimepart_5b236c06ec103_6ddb2ab392d7cf601276272 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho >> So the receiver at the point of sending an ACK has received PN=2,3,4 where 4 has a CE mark. Then the ACK will say: Largest PN=4, length=3, CE vector = 001. But then arrives PN=4, 5, 5 before it is time to send the next ACK. So the duplicate of PN=4 has ECN=ECT(0), and first 5 has ECT(0) and second ECN-CE set. Thus the ACK will be: Largest PN=5, length 4, CE vector 0001? #1439 (comment) by @gloinul > I'd assume that the second ACK will contain CE vector of 0010. So the receiver would thus indicate that for PN=4 you still have a CE mark, and report only on the first PN=5 packet that it is not marked. And then send an additional ACK with a CE vector of 0011? Sorry, I find your duplication handling to be very inconsistent. It appears to do suppression in some cases, and reporting others. I don't quite see what rules you have. Could you please clarify what rules the receiver uses and what the reporting and ACKing rules truly are? I had missed the side channel attack, if the protection against this is to spend cycles on verifying the packet, so be it then. I still don't see why throwing it away directly after that is not simply the easiest option. Handling ACKs that are duplicate, sure due to the tracking of "newly" acked should yield 0 new ACKed packets and thus no impact on the congestion window state. The data is supposed to be the same, so if you copy it to the same buffer the result should be the same, except what happens is that receiver buffer is already consumed by the application? Which I guess means tracking and knowing that the buffer is not any longer available. I think this shows that although it is possible to handle duplicated packets on a frame type basis, one still need to consider what checks against existing state one has to do to avoid affecting that state again. When it comes to the requirement on packet duplication handling in QUIC, from my perspective the ECN part is only a minor part of this. I think it would be good to settle that, and that has its own issue #1405. ECN can be made to cope with counting packet duplicates the things needed are: * Avoiding the duplicates causing slack in the verification mechanisms. For a counter mechanism this works as long as one also know how many duplicates has been counted. This is either its own counter or another mechanism in the ACK indicating which PNs has been received multiple times. * Being able to determine in which order different markings has been received. This to combat the attacker on the side that receives copies of stream packets and then manipulates the packets and forwards them. So the requirement on the encoding for ECN will be dependent if duplicated packets are processed or not. However, it is something that can be dealt with, but it will affect the required overhead. -- 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/1439#issuecomment-397538830 ----==_mimepart_5b236c06ec103_6ddb2ab392d7cf601276272 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho

So the receiver at the point of sending an ACK has received PN=3D2,3,4= where 4 has a CE mark. Then the ACK will say: Largest PN=3D4, length=3D3= , CE vector =3D 001.

But then arrives PN=3D4, 5, 5 before it is time to send the ne=
xt ACK. So the duplicate of PN=3D4 has ECN=3DECT(0), and first 5 has ECT(=
0) and second ECN-CE set. Thus the ACK will be:
Largest PN=3D5, length 4, CE vector 0001?
#1439 (comment) by @gloinul

I'd assume that the second ACK will contain CE vector of 0010.

So the receiver would thus indicate that for PN=3D4 you still have a C= E mark, and report only on the first PN=3D5 packet that it is not marked.= And then send an additional ACK with a CE vector of 0011?

Sorry, I find your duplication handling to be very inconsistent. It ap= pears to do suppression in some cases, and reporting others. I don't quit= e see what rules you have. Could you please clarify what rules the receiv= er uses and what the reporting and ACKing rules truly are?

I had missed the side channel attack, if the protection against this i= s to spend cycles on verifying the packet, so be it then. I still don't s= ee why throwing it away directly after that is not simply the easiest opt= ion. Handling ACKs that are duplicate, sure due to the tracking of "newly= " acked should yield 0 new ACKed packets and thus no impact on the conges= tion window state. The data is supposed to be the same, so if you copy it= to the same buffer the result should be the same, except what happens is= that receiver buffer is already consumed by the application? Which I gue= ss means tracking and knowing that the buffer is not any longer available= . I think this shows that although it is possible to handle duplicated pa= ckets on a frame type basis, one still need to consider what checks again= st existing state one has to do to avoid affecting that state again.

When it comes to the requirement on packet duplication handling in QUI= C, from my perspective the ECN part is only a minor part of this. I think= it would be good to settle that, and that has its own issue #1405. ECN can be made = to cope with counting packet duplicates the things needed are:

  • Avoiding the duplicates causing slack in the verification mechanisms.= For a counter mechanism this works as long as one also know how many dup= licates has been counted. This is either its own counter or another mecha= nism in the ACK indicating which PNs has been received multiple times.
  • Being able to determine in which order different markings has been re= ceived. This to combat the attacker on the side that receives copies of s= tream packets and then manipulates the packets and forwards them.

So the requirement on the encoding for ECN will be dependent if duplic= ated packets are processed or not. However, it is something that can be d= ealt with, but it will affect the required overhead.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b236c06ec103_6ddb2ab392d7cf601276272-- From nobody Fri Jun 15 01:11:04 2018 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 AA1BA130DDC for ; Fri, 15 Jun 2018 01:11:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 WbIjm5Uf_DIb for ; Fri, 15 Jun 2018 01:11:00 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1DAF130DC2 for ; Fri, 15 Jun 2018 01:11:00 -0700 (PDT) Date: Fri, 15 Jun 2018 01:10:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529050259; bh=p4oxRaNv80Sj5VnwFNJG9rVA9wlOu1U+HzrVMHnUvqk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EIJDAjPHXvX1qMZ2uajSvEbjG9x3kcABAugcoMvyd2j8gIb0shlMbExTKyTYwHgc7 ODX6NNTZSWingLd1QeLHBbF//jbXrgMx0iAdHx2TnTqviVchesZhULmQGQsVK25NXl oBpARagLY8/ixWycoSyOW8ZadtcDXFPkRJku5XsM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b237493ba86a_6bab3fd95231cf8483068"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 15 Jun 2018 08:11:03 -0000 ----==_mimepart_5b237493ba86a_6bab3fd95231cf8483068 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > The data is supposed to be the same, so if you copy it to the same buffer the result should be the same, except what happens is that receiver buffer is already consumed by the application? Which I guess means tracking and knowing that the buffer is not any longer available. I think this shows that although it is possible to handle duplicated packets on a frame type basis, one still need to consider what checks against existing state one has to do to avoid affecting that state again. Same content in the receive buffer of a stream happens frequently with retransmissions in new packets so duplicate packets are just a special case of this. Therefore frame based deduplication is a must have and does not get any easier with duplicate packet filtering. -- 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/1439#issuecomment-397547356 ----==_mimepart_5b237493ba86a_6bab3fd95231cf8483068 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The data is supposed to be the same, so if you copy it to the same buf= fer the result should be the same, except what happens is that receiver b= uffer is already consumed by the application? Which I guess means trackin= g and knowing that the buffer is not any longer available. I think this s= hows that although it is possible to handle duplicated packets on a frame= type basis, one still need to consider what checks against existing stat= e one has to do to avoid affecting that state again.

Same content in the receive buffer of a stream happens frequently with= retransmissions in new packets so duplicate packets are just a special c= ase of this. Therefore frame based deduplication is a must have and does = not get any easier with duplicate packet filtering.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b237493ba86a_6bab3fd95231cf8483068-- From nobody Fri Jun 15 04:09:28 2018 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 5C0DD130DE1 for ; Fri, 15 Jun 2018 04:09:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 yRhn7iwPcd6Y for ; Fri, 15 Jun 2018 04:09:25 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41B4F130DDD for ; Fri, 15 Jun 2018 04:09:25 -0700 (PDT) Date: Fri, 15 Jun 2018 04:09:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529060963; bh=zTl7/rWyotGtadDNNUlblEpj0iTwr/bmI1rL3fxSMh8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yG7USegQ/suYGvwc54y6aLaVJyem12v1FAzlKd6KHCfJNfCebJlKU4BofK0FnowR1 CGIoU24LYpy/FWSclu/Pl4ochdnbpPeXetSWTlzj35KjMqvss3r4BmT9oLXLF3RZis vOcYqpUyz+BLv2mmRttdaapu7qRI+McrRAhdJnIw= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b239e63891dc_3acb3fa7f3148f7c220982"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 15 Jun 2018 11:09:27 -0000 ----==_mimepart_5b239e63891dc_3acb3fa7f3148f7c220982 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul > Sorry, I find your duplication handling to be very inconsistent. It appears to do suppression in some cases, and reporting others. I don't quite see what rules you have. Could you please clarify what rules the receiver uses and what the reporting and ACKing rules truly are? I would argue that what truly matters is if sender recognizes a congestion event. Not what is sent in ACK. By using ACK frames to carry the PNs along with their CE bits, it is possible for the sender to find and reject duplicate signals. The information that reaches the sender first is adopted (in contrast to the approach of #1372 that adopts the information that reaches the receiver first). That is the principle. But note that the encodings proposed on this issue does not forbid receivers from detecting and rejecting duplicates the same way that is required in #1372. It is just that such behavior becomes optional. > When it comes to the requirement on packet duplication handling in QUIC, from my perspective the ECN part is only a minor part of this. I think it would be good to settle that, and that has its own issue #1405. I disagree. My understanding is that the encoding introduced in #1372 is the only thing that _requires_ the receiver to implement duplication detection. Part of my motivation for proposing an alternative encoding is to remove that requirement, thereby closing #1405 or relaxing the requirements that will be introduced there. -- 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/1439#issuecomment-397589048 ----==_mimepart_5b239e63891dc_3acb3fa7f3148f7c220982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

Sorry, I find your duplication handling to be very inconsistent. It ap= pears to do suppression in some cases, and reporting others. I don't quit= e see what rules you have. Could you please clarify what rules the receiv= er uses and what the reporting and ACKing rules truly are?

I would argue that what truly matters is if sender recognizes a conges= tion event. Not what is sent in ACK.

By using ACK frames to carry the PNs along with their CE bits, it is p= ossible for the sender to find and reject duplicate signals. The informat= ion that reaches the sender first is adopted (in contrast to the approach= of #1372 tha= t adopts the information that reaches the receiver first). That is the pr= inciple.

But note that the encodings proposed on this issue does not forbid rec= eivers from detecting and rejecting duplicates the same way that is requi= red in #1372.= It is just that such behavior becomes optional.

When it comes to the requirement on packet duplication handling in QUI= C, from my perspective the ECN part is only a minor part of this. I think= it would be good to settle that, and that has its own issue #1405.

I disagree.

My understanding is that the encoding introduced in #1372 is the only thing that = requires the receiver to implement duplication detection. Part of my= motivation for proposing an alternative encoding is to remove that requi= rement, thereby closing #1405 or relaxing the requirements that will be introduced t= here.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b239e63891dc_3acb3fa7f3148f7c220982-- From nobody Fri Jun 15 04:15:44 2018 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 D96FE130DED for ; Fri, 15 Jun 2018 04:15:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QHT0S4RHFZGA for ; Fri, 15 Jun 2018 04:15:40 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A97130DEC for ; Fri, 15 Jun 2018 04:15:40 -0700 (PDT) Date: Fri, 15 Jun 2018 04:15:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529061339; bh=JUzxs5ZUdirgqMuIN9hshawjKV2Cm5dZIXKw4rON5xo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TbNZ9QUihn9kJBYNBSz51SXwEuse/ttcQPNwyZLXgNNzS8/5Mor1uWJT9SUqo7PkW uTtfs44luPsM8QAG1exnjeIAGg0yL7XB9lnwrBeHfc51W8dNHLWvubLF/0O4Ih5vT/ sxd/T7N6wk680545BgRaf25kgjC0ceXM25K8p2o8= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b239fdb53610_a952b220145cf602240a5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 15 Jun 2018 11:15:42 -0000 ----==_mimepart_5b239fdb53610_a952b220145cf602240a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As discussed in https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397589048, my understanding is that the ECN support in the form proposed in #1372 is the only issue that makes duplicate detection a requirement rather than an option. Considering that, I think that we have a chance of closing the issue without adding any requirements if we adopt a different encoding scheme that lets the sender detect duplicates as discussed #1439. -- 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/1405#issuecomment-397590223 ----==_mimepart_5b239fdb53610_a952b220145cf602240a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As discussed in #1439 (comment), my understanding is that the= ECN support in the form proposed in #1372 is the only issue that makes duplicate dete= ction a requirement rather than an option.

Considering that, I think that we have a chance of closing the issue w= ithout adding any requirements if we adopt a different encoding scheme th= at lets the sender detect duplicates as discussed #1439.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b239fdb53610_a952b220145cf602240a5-- From nobody Fri Jun 15 04:34:06 2018 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 10EAC130DE8 for ; Fri, 15 Jun 2018 04:34:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 i0GoKQOxEyAT for ; Fri, 15 Jun 2018 04:34:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61446120049 for ; Fri, 15 Jun 2018 04:34:03 -0700 (PDT) Date: Fri, 15 Jun 2018 04:34:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529062442; bh=//obS79Bcvwdbw3J3WR32nj2hDmdrMxxdyzfrHkHHGc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yXgy0758Owhy3FYA2/rY7n5ovbnGszwwl9sjBOQsv7tqLS81qMptOCTIsjUvcPhiA OoClSPfxcAr4JMeqTi68DsDVvanf5KLjLYY+k0Ic0v0QCtGGYm2CySQz3JX3ljr+Ug lIPJybZ7svC7gcKtd+K+HDZ/JBUzMotWxbOHR8dQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23a42a88040_58b23f878fa7cf782147e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 15 Jun 2018 11:34:05 -0000 ----==_mimepart_5b23a42a88040_58b23f878fa7cf782147e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson > If we were going this way, maybe it needs a better encoding than bit-stuffing a varint. Not sure what that looks like though. An alternative approach will be to use something similar to the 6+ encoding of HPACK / QPACK, like below: ``` 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+ |M M| Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | [Additional Length (i)] ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` In this example, * next mode is represented as two bits (M), using the formula proposed in https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397157328. * block length between 1 to 63 is directly encoded using the 6 bits of the Length field. In that case, the Additional Length field is omitted. * if the block length is greater than 63, then Length field is encoded as zero, and `block_length - 64` is encoded as a varint in the Additional Length field. There will be no additional overhead on a non-ECN-capable path for short blocks (blocks below 64), and one octet overhead for longer blocks. And the encoding overhead of ECN flags will be exactly the same as what we have with gaps. If we consider mode depending on the previous mode is an issue, we could split the first octet into 5*51 instead of 4*64. -- 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/1439#issuecomment-397593919 ----==_mimepart_5b23a42a88040_58b23f878fa7cf782147e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson

If we were going this way, maybe it needs a better encoding than bit-s= tuffing a varint. Not sure what that looks like though.

An alternative approach will be to use something similar to the 6+ enc= oding of HPACK / QPACK, like below:

 0                   1                   2                   3=

 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|M M|  Length   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    [Additional Length (i)]                  ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In this example,

  • next mode is represented as two bits (M), using the formula proposed = in #1439 (comment).
  • block length between 1 to 63 is directly encoded using the 6 bits of = the Length field. In that case, the Additional Length field is omitted.
  • if the block length is greater than 63, then Length field is encoded = as zero, and block_length - 64 is encoded as a varint in the= Additional Length field.

There will be no additional overhead on a non-ECN-capable path for sho= rt blocks (blocks below 64), and one octet overhead for longer blocks. An= d the encoding overhead of ECN flags will be exactly the same as what we = have with gaps.

If we consider mode depending on the previous mode is an issue, we cou= ld split the first octet into 551 instead of 464.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23a42a88040_58b23f878fa7cf782147e1-- From nobody Fri Jun 15 07:08:11 2018 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 EF924130E19 for ; Fri, 15 Jun 2018 07:08:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 B5xjAtgACycz for ; Fri, 15 Jun 2018 07:08:06 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64778130DDA for ; Fri, 15 Jun 2018 07:08:06 -0700 (PDT) Date: Fri, 15 Jun 2018 07:08:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529071685; bh=aDLa1BXEt1ZuiAc33SxsjelfEO3lcbiFatrPjMQlNxQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Abqt9fLrdsdzB75VcTOHI6/o0Nk+/7nLEIk3usK5vgrYZS4ykWhpqQzRmbvWdPjPW UUBP+/CysJWoWAZGArin/I8VVIUzRxw2XRivFI3KJ9cw9E4IEr/nnUeJMD1bE89ySF VnyqUrWSXruvoq8JptvnsBJM2h7RRi9IxxWGUg7g= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23c84542e90_55472af96d590f602184c9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 14:08:10 -0000 ----==_mimepart_5b23c84542e90_55472af96d590f602184c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Generally looks good. A few places where this SHOUTS unnecessarily though. > @@ -526,6 +526,16 @@ A frame includes the following fields: ## Frame Definitions {#frames} +Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the +requirement that unknown types be ignored. These frames have no semantic +meaning, and SHOULD be sent when application-layer padding is desired. They MAY s/SHOULD/can/ > @@ -526,6 +526,16 @@ A frame includes the following fields: ## Frame Definitions {#frames} +Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the +requirement that unknown types be ignored. These frames have no semantic +meaning, and SHOULD be sent when application-layer padding is desired. They MAY +also be sent on connections where no request data is currently being +transferred. Endpoints MUST NOT consider these frames to have any meaning upon +receipt. + +Both the payload and length of the frames SHOULD be selected randomly, subject You can't select the length randomly if the purpose is to pad. Exposing the state of your RNG is considered bad practice now, so don't suggest random content either. Maybe instead just say that the length and contents of the frame can be anything and no more than that. > @@ -776,6 +786,14 @@ The following setting is defined in HTTP/QUIC: : An integer with a maximum value of 2^30 - 1. The default value is unlimited. +Settings values of the format `0x?a?a` are reserved to exercise the requirement +that unknown parameters be ignored. Such settings have no defined meaning. +Endpoints SHOULD include at least one such setting in their SETTINGS frame. +Endpoints MUST NOT consider such settings to have any meaning upon receipt. + +Because the setting has no defined meaning, the value of the setting SHOULD be +selected randomly, subject to implementation-defined limits on the size. s/SHOULD/can be set to any value/ > @@ -1418,6 +1446,16 @@ The entries in the following table are registered by this document. | MAX_HEADER_LIST_SIZE | 0x6 | {{settings-parameters}} | |----------------------------|------|-------------------------| +Additionally, each code of the format `0x?a?a` where each `?` is any octet (that ? isn't an octet -- 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/1446#pullrequestreview-129161979 ----==_mimepart_5b23c84542e90_55472af96d590f602184c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Generally looks good. A few places where this SHOUTS unnecessarily though.

In draft-ietf-quic-http.md:

> @@ -526,6 +526,16 @@ A frame includes the following fields:
 
 ## Frame Definitions {#frames}
 
+Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the
+requirement that unknown types be ignored. These frames have no semantic
+meaning, and SHOULD be sent when application-layer padding is desired.  They MAY

s/SHOULD/can/

In draft-ietf-quic-http.md:

> @@ -526,6 +526,16 @@ A frame includes the following fields:
 
 ## Frame Definitions {#frames}
 
+Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the
+requirement that unknown types be ignored. These frames have no semantic
+meaning, and SHOULD be sent when application-layer padding is desired.  They MAY
+also be sent on connections where no request data is currently being
+transferred. Endpoints MUST NOT consider these frames to have any meaning upon
+receipt.
+
+Both the payload and length of the frames SHOULD be selected randomly, subject

You can't select the length randomly if the purpose is to pad. Exposing the state of your RNG is considered bad practice now, so don't suggest random content either. Maybe instead just say that the length and contents of the frame can be anything and no more than that.

In draft-ietf-quic-http.md:

> @@ -776,6 +786,14 @@ The following setting is defined in HTTP/QUIC:
   : An integer with a maximum value of 2^30 - 1.  The default value is
     unlimited.
 
+Settings values of the format `0x?a?a` are reserved to exercise the requirement
+that unknown parameters be ignored.  Such settings have no defined meaning.
+Endpoints SHOULD include at least one such setting in their SETTINGS frame.
+Endpoints MUST NOT consider such settings to have any meaning upon receipt.
+
+Because the setting has no defined meaning, the value of the setting SHOULD be
+selected randomly, subject to implementation-defined limits on the size.

s/SHOULD/can be set to any value/

In draft-ietf-quic-http.md:

> @@ -1418,6 +1446,16 @@ The entries in the following table are registered by this document.
 | MAX_HEADER_LIST_SIZE       | 0x6  | {{settings-parameters}} |
 |----------------------------|------|-------------------------|
 
+Additionally, each code of the format `0x?a?a` where each `?` is any octet (that

? isn't an octet

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

----==_mimepart_5b23c84542e90_55472af96d590f602184c9-- From nobody Fri Jun 15 08:07:52 2018 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 2F1E2130E1F for ; Fri, 15 Jun 2018 08:07:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Qn0KWXodR0ez for ; Fri, 15 Jun 2018 08:07:48 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01D88130DC0 for ; Fri, 15 Jun 2018 08:07:47 -0700 (PDT) Date: Fri, 15 Jun 2018 08:07:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529075266; bh=1Lv4p6eW4JkESD1+Woh2WMdleEhD+da/GG+lQph4Uh8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=qGAlJFbqebuk8dbUVAwEeJhEBdb7sxIxWpN8NeGHrkAaVjFUnwEh/Qkui1PkNhdnA SFapSju153a2H0rOzEFv90chiO7iYLgJ3a764UbRoQLHZKMLqbS3JfOYbA2q2ElYjL jMhqHwsaqHIFQe3Qex4hVDWIuJ6ESUCjiz5yhZ94= From: Robin Marx Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23d6427ac96_6d623fe929130f7c134920"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rmarx 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.26 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: Fri, 15 Jun 2018 15:07:52 -0000 ----==_mimepart_5b23d6427ac96_6d623fe929130f7c134920 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am quite new to the whole RFC stuff, so I am sorry for using hopelessly= wrong names for things. = I had some trouble today understanding some of the pseudocode in the tran= sport draft, more specifically at https://tools.ietf.org/html/draft-ietf-= quic-transport-12#section-6.4 : ``` struct { TransportParameterId parameter; opaque value<0..2^16-1>; } TransportParameter; struct { select (Handshake.msg_type) { case client_hello: QuicVersion initial_version; case encrypted_extensions: QuicVersion negotiated_version; QuicVersion supported_versions<4..2^8-4>; }; TransportParameter parameters<22..2^16-1>; } TransportParameters; ``` For example the 'supported_versions' field: is that supposed to be an arr= ay prefixed with a length? Current implementations seem to think so. The = 'value' field above is a single value prefixed with a length. But then th= e 'parameters' field below is very similar in syntax, but is not prefixed= by length in the implementations (or I'm reading some things wrong, alwa= ys possible). I asked @larseggert about this, and he secretly admitted "Nobody but ekr = understands the TLS syntax. It=E2=80=99s a huge pain.". Even if I'm misin= terpreting some things, an alternative syntax or at least a clear explana= tion would be welcome (if that is already in there somewhere, possibly li= nk it in https://tools.ietf.org/html/draft-ietf-quic-transport-12#section= -2.1?) -- = 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/1449= ----==_mimepart_5b23d6427ac96_6d623fe929130f7c134920 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I am quite new to the whole RFC stuff, so I am sorry for using hopeles= sly wrong names for things.

I had some trouble today understanding some of the pseudocode in the t= ransport draft, more specifically at https://too= ls.ietf.org/html/draft-ietf-quic-transport-12#section-6.4 :

struct {
 TransportParameterId parameter;
 opaque value<0..2^16-1>;
} TransportParameter;

struct {
 select (Handshake.msg_type) {
	case client_hello:
	   QuicVersion initial_version;

	case encrypted_extensions:
	   QuicVersion negotiated_version;
	   QuicVersion supported_versions<4..2^8-4>;
 };
 TransportParameter parameters<22..2^16-1>;
} TransportParameters;

For example the 'supported_versions' field: is that supposed to be an = array prefixed with a length? Current implementations seem to think so. T= he 'value' field above is a single value prefixed with a length. But then= the 'parameters' field below is very similar in syntax, but is not prefi= xed by length in the implementations (or I'm reading some things wrong, a= lways possible).

I asked @larseggert about this, = and he secretly admitted "Nobody but ekr understands the TLS syntax. It=E2= =80=99s a huge pain.". Even if I'm misinterpreting some things, an altern= ative syntax or at least a clear explanation would be welcome (if that is= already in there somewhere, possibly link it in https://tools.ietf.org/html/draft-ietf-quic-transport-12#section-2.1= ?)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b23d6427ac96_6d623fe929130f7c134920-- From nobody Fri Jun 15 08:14:19 2018 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 DC825130E4F for ; Fri, 15 Jun 2018 08:14:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nRWAV-BtpyNW for ; Fri, 15 Jun 2018 08:14:15 -0700 (PDT) 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 3884E130E1F for ; Fri, 15 Jun 2018 08:14:15 -0700 (PDT) Date: Fri, 15 Jun 2018 08:14:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529075654; bh=/blTCgcQ928BmycvFMopNEDwdM5S/xOawdXCd269IQY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U5J5bYaln6yq0xCZCir6XeCpCmYpeoI6eIz/ej0ewNgJYdkyz8STbKkLbWmk0MNKh SdnY3QOHCapXnszvdBZ+rcJa29H1H3ARgwSmvE7Mq4QJx1ct15c4abvZ/8V8HwbyI8 puaR2Bq8xYtKgjVW0Qn4AZobpSOvi19Yd41V/g5I= From: Dmitri Tikhonov Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23d7c65d716_40833ff4a95a8f886587f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: dtikhonov 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.26 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: Fri, 15 Jun 2018 15:14:17 -0000 ----==_mimepart_5b23d7c65d716_40833ff4a95a8f886587f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Gee, way to keep a secret! =F0=9F=98=83 >From the second paragraph of the draft: ``` -- = 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/1449#issuecomment-397653456= ----==_mimepart_5b23d7c65d716_40833ff4a95a8f886587f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Gee, way to keep a secret! =F0=9F=98=83

From the second paragraph of the draft:

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23d7c65d716_40833ff4a95a8f886587f-- From nobody Fri Jun 15 08:24:47 2018 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 45971130E2D for ; Fri, 15 Jun 2018 08:24:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 b_VXB_53CbGq for ; Fri, 15 Jun 2018 08:24:43 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91FBD130E2C for ; Fri, 15 Jun 2018 08:24:43 -0700 (PDT) Date: Fri, 15 Jun 2018 08:24:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529076282; bh=+JTvn0+YzMCHUQc91c380L4I+PtzTDhoSPETlY90ft0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CWXMq+qQKydeytXfovKisRk349oVGpowze713wVZnBKh/TNUW+c5iJFUPXcJa82Me uwwqh3Nj/GZNdwklkArB8wL4lEvZM3JBOBcQPmiZF9X9NWpjsbPyUsp/gc8ESS8TV+ GWbLMiKcpU1qlYx9WcwiUwYWXDQYz/PL1gKHhwMg= From: Robin Marx Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23da3ad4b56_7cad2b1da656cf5440706d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rmarx 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.26 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: Fri, 15 Jun 2018 15:24:46 -0000 ----==_mimepart_5b23da3ad4b56_7cad2b1da656cf5440706d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok, Friday afternoon is not the best time for me to read specs, clearly... that's a lot clearer now, thanks. I do think the overall question of keeping this syntax still stands though, as it's not very intuitive, and @larseggert mentioned meaning to open an issue about this himself. -- 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/1449#issuecomment-397656593 ----==_mimepart_5b23da3ad4b56_7cad2b1da656cf5440706d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ok, Friday afternoon is not the best time for me to read specs, clearl= y... that's a lot clearer now, thanks.

I do think the overall question of keeping this syntax still stands th= ough, as it's not very intuitive, and @= larseggert mentioned meaning to open an issue about this himself.

=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23da3ad4b56_7cad2b1da656cf5440706d-- From nobody Fri Jun 15 08:27:17 2018 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 70300130E63 for ; Fri, 15 Jun 2018 08:27:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4ZdaK661BtNk for ; Fri, 15 Jun 2018 08:27:02 -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 E0B14130F1C for ; Fri, 15 Jun 2018 08:27:01 -0700 (PDT) Date: Fri, 15 Jun 2018 08:27:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529076421; bh=48taOLz1bgxHyNImjztlG7cqVLZqm/RHhsuPEnLLNgw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XZpWtm1CeyPPA67q3noexrq+76AjnOXAiManB0KfVGKogc+8te6WllswojTVs2eEK k+oSmmc3fcKCTE2bWUMC1fpED293ASpuiMh32gPphT5duDTfuZylOY6Fw+GavHVJui iWp0ee7rzOkFC7VjZZcRlqKZsGwW0SwMIh4/L4l0= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23dac51ba57_5d793fe559cf4f801741a4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Fri, 15 Jun 2018 15:27:15 -0000 ----==_mimepart_5b23dac51ba57_5d793fe559cf4f801741a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit pravb commented on this pull request. > @@ -1289,6 +1290,13 @@ preferred_address (0x0004): : The server's Preferred Address is used to effect a change in server address at the end of the handshake, as described in {{preferred-address}}. +disable_migration (0x0009): + +: The server does not support migration of connections to a different IP + address. Clients MUST NOT send any packets, including probing packets, from an + IP address other than that used to perform the handshake. This parameter @kazuho yes 5-tuple or 3-tuple i.e. only IP addresses. Load balancers can operate in both modes for UDP (the latter for handling IP fragmented UDP flows). In the latter case port changes will not cause an issue. Regardless as I said if the server indicates no support for migration then automatically turning on keep-alives should be recommended to deal with NAT rebinding. -- 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/1447#discussion_r195776760 ----==_mimepart_5b23dac51ba57_5d793fe559cf4f801741a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@pravb commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1289,6 +1290,13 @@ preferred_address (0x0004):
 : The server's Preferred Address is used to effect a change in server address at
   the end of the handshake, as described in {{preferred-address}}.
 
+disable_migration (0x0009):
+
+: The server does not support migration of connections to a different IP
+  address. Clients MUST NOT send any packets, including probing packets, from an
+  IP address other than that used to perform the handshake.  This parameter

@kazuho yes 5-tuple or 3-tuple i.e. only IP addresses. Load balancers can operate in both modes for UDP (the latter for handling IP fragmented UDP flows). In the latter case port changes will not cause an issue. Regardless as I said if the server indicates no support for migration then automatically turning on keep-alives should be recommended to deal with NAT rebinding.

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

----==_mimepart_5b23dac51ba57_5d793fe559cf4f801741a4-- From nobody Fri Jun 15 08:39:47 2018 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 0DCBE130E2E for ; Fri, 15 Jun 2018 08:39:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.989 X-Spam-Level: X-Spam-Status: No, score=-2.989 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, MAILING_LIST_MULTI=-1, T_DKIMWL_WL_HIGH=-0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=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 FFvsl4IiEHzK for ; Fri, 15 Jun 2018 08:39:44 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 F22B512777C for ; Fri, 15 Jun 2018 08:39:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Hz+fh2xBsoDmaI6ikcEP0Y/5u/o=; b=eb0+Lb+WPNNAWsg6 cpfZzC9bdJBaTXtKvAIxfnGZLLoHP7HZup8ZuVELruTJ1VS5kXAu1Q5/TMkPBvhF LzZF4Kc6Vz7SXkEJG4sThSp/sgHdT24yBhCNOwB8slWfrqwvysbwCecUDhTrvm/Q Nt0+kqVSv1P81Wpfvj3+J7XWmUc= Received: by filter0757p1las1.sendgrid.net with SMTP id filter0757p1las1-25158-5B23DDBE-B 2018-06-15 15:39:42.576164434 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0004p1iad2.sendgrid.net (SG) with ESMTP id _TwcfGHJRLmJSJ-u0DLZcg for ; Fri, 15 Jun 2018 15:39:42.534 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id 8273B80023 for ; Fri, 15 Jun 2018 08:39:42 -0700 (PDT) Date: Fri, 15 Jun 2018 15:39:42 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ddbe80de9_fa52b073f64af5c11321a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2KZnmijmZURuyzLy/JfhWkT8ucq8DH4Oat1M K2h7s2K5qimnSb3siY6ODvqLw4+8a+TbUCekBddANseMO2c3pcz51o4KrFDBpbG/HaUYWKEhc2q+mV 0lYO2ZE3DGBBhm97Luqh0FfUIeNVAWZ3SyDdG5StO3K1RpAuNfEkCGZ6RQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 15:39:47 -0000 ----==_mimepart_5b23ddbe80de9_fa52b073f64af5c11321a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1450 -- Commit Summary -- * Output of Stream 0 Design Team. * Fix changelog * Fix whitespace * Offset and length fields in CRYPTO_HS are not optional * Remove EMPTY_ACK * Incorporate the comments from PR#1377 * Remove EMPTY_ACK * Update draft-ietf-quic-transport.md * Add the TLS diagrams * Redact diagram from the TLS doc * Ian Swett's comments * server-initiated streams start from 1 * Remove last TODO * Minor editorial * Remove the advice on how to use coalesced packets for recovery. * Self-review, ready to submit * Some more cleanup -- File Changes -- M draft-ietf-quic-recovery.md (146) M draft-ietf-quic-tls.md (1384) M draft-ietf-quic-transport.md (793) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1450.patch https://github.com/quicwg/base-drafts/pull/1450.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/1450 ----==_mimepart_5b23ddbe80de9_fa52b073f64af5c11321a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson

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

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

Commit Summary

  • Output of Stream 0 Design Team.
  • Fix changelog
  • Fix whitespace
  • Offset and length fields in CRYPTO_HS are not optional
  • Remove EMPTY_ACK
  • Incorporate the comments from PR#1377
  • Remove EMPTY_ACK
  • Update draft-ietf-quic-transport.md
  • Add the TLS diagrams
  • Redact diagram from the TLS doc
  • Ian Swett's comments
  • server-initiated streams start from 1
  • Remove last TODO
  • Minor editorial
  • Remove the advice on how to use coalesced packets for recovery.
  • Self-review, ready to submit
  • Some more cleanup

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 mute the thread.

----==_mimepart_5b23ddbe80de9_fa52b073f64af5c11321a-- From nobody Fri Jun 15 08:41:35 2018 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 277FC130E2C for ; Fri, 15 Jun 2018 08:41:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 wWKz79WxiJI1 for ; Fri, 15 Jun 2018 08:41:32 -0700 (PDT) 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 914A712777C for ; Fri, 15 Jun 2018 08:41:32 -0700 (PDT) Date: Fri, 15 Jun 2018 08:41:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529077291; bh=4Q5GGNjC6qvNOXVV5lPFlxW9LS0vLUBqGSenc1CKlwQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wtcGhJFQDCht+UejPyYpOfycfwCiQof7wHazDqsPXN6+2opRRUL+iUvAFxvPzbwnf cIS6a94uH+qmxh5nUR7OzmcTs+JiucVBsmeqECpPM+aQhQm8mJN7C+7hxQB7dWy+3p d4n2xV4xGTcRgDyCPwrzt42EL+hf+iialMn5Jc5g= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23de2bb4ea4_433c3f9d76eb0f847562a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Fri, 15 Jun 2018 15:41:35 -0000 ----==_mimepart_5b23de2bb4ea4_433c3f9d76eb0f847562a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable chris-wood commented on this pull request. > @@ -107,7 +111,7 @@ important to the loss detection and congestion cont= rol machinery below. * Retransmittable packets are those that contain at least one retransmittable frame. = -* Crypto handshake data is sent on stream 0, and uses the reliability +* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliab= ility =F0=9F=91=8D = -- = 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/1450#pullrequestreview-1292185= 38= ----==_mimepart_5b23de2bb4ea4_433c3f9d76eb0f847562a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@chris-wood commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -107,7 +111,7 @@ important to the loss =
detection and congestion control machinery below.
 * Retransmittable packets are those that contain at least one
   retransmittable frame.
 =

-* Crypto handshake data is sent on stream 0, and uses the reliability
+* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliab=
ility

=F0=9F=91=8D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

= = ----==_mimepart_5b23de2bb4ea4_433c3f9d76eb0f847562a-- From nobody Fri Jun 15 08:47:27 2018 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 D9729130DC0 for ; Fri, 15 Jun 2018 08:47:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 GIDspKqxTWXX for ; Fri, 15 Jun 2018 08:47:24 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 0518412F18C for ; Fri, 15 Jun 2018 08:47:23 -0700 (PDT) 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=YEWsbSIHCA4E2PwDGUJzEVbXCyM=; b=Kr+KAtuwAE7K2APH 7M6+jEVg1rCBEp8h6ZkixO6M5g1D8SfAJ1E9ilewNqA1iB+IuWwSL3D+q9EWsyne 4p+h7UlPaWnZia3JusjZic2kvUy+SnrvixhwSycHs06rdS4FirJX/Z36FtrMmo+x spCks/Ent1DeIOloA3cRISgPAGM= Received: by filter0307p1iad2.sendgrid.net with SMTP id filter0307p1iad2-24862-5B23DF8A-2F 2018-06-15 15:47:22.917482962 +0000 UTC Received: from github-lowworker7-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id OJ6hbXogSUWx5odzG8kP-g for ; Fri, 15 Jun 2018 15:47:22.974 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker7-cp1-prd.iad.github.net (Postfix) with ESMTP id E0918A2319 for ; Fri, 15 Jun 2018 08:47:22 -0700 (PDT) Date: Fri, 15 Jun 2018 15:47:23 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23df8adeb6e_1c083f8daf434f781585b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1sFXNiumEiy4b3lbnlDX1HF2qdjH7eabMvvb Q+dwCMM2/N/vOVCjPOM4lvmGOXkp0C7Ltidnejm1iXEP+iTf1aXieG8JJzThoS9Eazi1rtKmJvyX/d Hcj/hWlQB5HKdpPEsPcaqkGt4zZVaEE4vQrJdJtpqX99xflpJtH55Z4yWQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 15:47:26 -0000 ----==_mimepart_5b23df8adeb6e_1c083f8daf434f781585b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ekr pushed 1 commit. 777114a Fix compile errors -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/396c318dabd73952ee44b4bf1826aa28ebd19d8b..777114ac355c7a4b15dabd67122ca21c164e2e17 ----==_mimepart_5b23df8adeb6e_1c083f8daf434f781585b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b23df8adeb6e_1c083f8daf434f781585b5-- From nobody Fri Jun 15 08:59:05 2018 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 5A9EB130E29 for ; Fri, 15 Jun 2018 08:59:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jOLsXtzlr__A for ; Fri, 15 Jun 2018 08:59:01 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38B5012F18C for ; Fri, 15 Jun 2018 08:59:01 -0700 (PDT) Date: Fri, 15 Jun 2018 08:59:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529078340; bh=SxPN+2P1+OCMteXDALwsEZKXn5Emnihx6bfmFULjnjg=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=PO7eww75g+FXqGFa5boo3fhMZv1UJIGgAUIXYsKLGNmU7McCLupxtfEEMQppzirt8 15yOw5VrLGUT5+1UFm6IB9KNBhhN8IrhQhqXdG3TkQRu9nyaSLhiKGN4Pn1SD1Fao/ ZF13cd6ngkEis+5dVyomztYz74XOLs4yL5CeXLUs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e24435d7d_20b33fb40e52cf7c25543"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 15:59:04 -0000 ----==_mimepart_5b23e24435d7d_20b33fb40e52cf7c25543 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Allowing multiple Retry packets creates a potential for regression of the address validation tokens. Say that a client retransmits its first Initial packet without a token. The server responds to both with the same token. The second of these packets is delayed. The client receives the first, sends another Initial packet and receives a second token in response. Then the Retry that the server sent in response to the retransmission of the first Initial is received. The client switches to that token as though it were new, but it's back to the first token. If the server relies on multiple Retry packets and the progressive validation of the address using those tokens, then this will revert any progress that was made. Because Retry can't be sent indefinitely (it has this arbitrary limit of 3 changes), this might cause that connection to fail. -- 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/1451 ----==_mimepart_5b23e24435d7d_20b33fb40e52cf7c25543 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Allowing multiple Retry packets creates a potential for regression of the address validation tokens.

Say that a client retransmits its first Initial packet without a token. The server responds to both with the same token. The second of these packets is delayed.

The client receives the first, sends another Initial packet and receives a second token in response.

Then the Retry that the server sent in response to the retransmission of the first Initial is received. The client switches to that token as though it were new, but it's back to the first token.

If the server relies on multiple Retry packets and the progressive validation of the address using those tokens, then this will revert any progress that was made. Because Retry can't be sent indefinitely (it has this arbitrary limit of 3 changes), this might cause that connection to fail.

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

----==_mimepart_5b23e24435d7d_20b33fb40e52cf7c25543-- From nobody Fri Jun 15 09:04:50 2018 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 7F5DD130E29 for ; Fri, 15 Jun 2018 09:04:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 LSbbMq5Ikg1w for ; Fri, 15 Jun 2018 09:04:46 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 A0A2512F18C for ; Fri, 15 Jun 2018 09:04:46 -0700 (PDT) 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=/rtrScId6f22IMQBPS/eSdXoV6k=; b=JYQkkg4f1+v0worV 85B6IW+qLlwgdsM/+fgujuqoXlHL6qTuv0qe8A/BsMpbxUHB5vCMQoQJm0F4wySP RMjFpkVLDh3abOQbAyIOA5vSeahlZzLQan7zEX7k6yLmqv3VyX2P58oeeBxNJPK+ 9Q5Il59iQLPlojtAJbQX9MhnlbY= Received: by filter0371p1iad2.sendgrid.net with SMTP id filter0371p1iad2-20130-5B23E39D-27 2018-06-15 16:04:45.346203917 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0020p1iad2.sendgrid.net (SG) with ESMTP id kQ6UFkd8SPWI0FC4xaLY4Q for ; Fri, 15 Jun 2018 16:04:45.387 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id 62A95C1600 for ; Fri, 15 Jun 2018 09:04:45 -0700 (PDT) Date: Fri, 15 Jun 2018 16:04:45 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e39d60bd1_115a3fc19bb1cf78104217"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1MheyLmluSNj5SOsXSQgQFL4udYU6HN9D8SN FMm6G3Ag1IkfxdyLoXMWVgpq6fU+qLeKlB3+XG5/Wfo+wk/q7iJU/iiGlGDL+LGgqCRCfoOUeFR1WI OE8Gmr0XhdlbFBntadEucnYiVj3N2mDdkfP/wM4otyI/W183uWI8z+9cOg== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:04:49 -0000 ----==_mimepart_5b23e39d60bd1_115a3fc19bb1cf78104217 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It comes as a surprise to me that @larseggert thinks that nobody but me understands the syntax, given that we have a pile of independent interoperable TLS 1.3 stacks. Regardless, this is the appropriate syntax because these are PDUs that go into the TLS stack, which already uses that syntax. We don't need to explicitly state the size of the parameters because the protocol definition language tells youl -- 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/1449#issuecomment-397667623 ----==_mimepart_5b23e39d60bd1_115a3fc19bb1cf78104217 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It comes as a surprise to me that @larsegg= ert thinks that nobody but me understands the syntax, given that we ha= ve a pile of independent interoperable TLS 1.3 stacks.

Regardless, this is the appropriate syntax because these are PDUs that g= o into the TLS stack, which already uses that syntax. We don't need to expl= icitly state the size of the parameters because the protocol definition lan= guage tells youl

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b23e39d60bd1_115a3fc19bb1cf78104217-- From nobody Fri Jun 15 09:17:04 2018 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 25EC1130F0D for ; Fri, 15 Jun 2018 09:16:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lTUG9l8FhCPl for ; Fri, 15 Jun 2018 09:16:51 -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 620F7130FED for ; Fri, 15 Jun 2018 09:16:24 -0700 (PDT) Date: Fri, 15 Jun 2018 09:16:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529079383; bh=Y8eVGM6GNe7fwCwUgcMn/FVjLuDSxKX4PnwtC/4BZgw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AhiBRxzHbekzwr4Zi4O/ATqvMVv/8nnUgnAUOwm1c4iep24Fv5qN8/OXcsNUM9YYg qQdY412OqX+DWpLPw7zdIp2d8vj+fvualP+R+cX/XlMBe0KVDnAdfMmNvjCyU3MVJn S+DLHVbSQesvovACWl4Z7Ojf6ZXj31nlGPJ60yWc= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e6576a3d8_61e42ac304360f50116346"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 15 Jun 2018 16:17:02 -0000 ----==_mimepart_5b23e6576a3d8_61e42ac304360f50116346 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A client should know the initial CID used whether it is retry or not. If an old retry lands, its destinition CID would not match the ongoing session. Client could choose to opt for the originally based on an informed decision - which could be if a handshake, rather than a retry is received. But otherwise I don't see how the client can get confused (except if extremely unfortunate to get a random collision). If the client does multiple retry sequences using a received CID, then there is a potential conflict, but I don't think multiple retries is a good idea, nor necessary. -- 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/1451#issuecomment-397671032 ----==_mimepart_5b23e6576a3d8_61e42ac304360f50116346 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A client should know the initial CID used whether it is retry or not. = If an old retry lands, its destinition CID would not match the ongoing se= ssion.

Client could choose to opt for the originally based on an informed dec= ision - which could be if a handshake, rather than a retry is received. B= ut otherwise I don't see how the client can get confused (except if extre= mely unfortunate to get a random collision).

If the client does multiple retry sequences using a received CID, then= there is a potential conflict, but I don't think multiple retries is a g= ood idea, nor necessary.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23e6576a3d8_61e42ac304360f50116346-- From nobody Fri Jun 15 09:22:40 2018 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 7FD4D130EF9 for ; Fri, 15 Jun 2018 09:22:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 B3FE8xxJ-1Eu for ; Fri, 15 Jun 2018 09:22:08 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 911EC130F73 for ; Fri, 15 Jun 2018 09:21:50 -0700 (PDT) Date: Fri, 15 Jun 2018 09:21:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529079709; bh=drSgx1Cpmm/FdVbemGHgdU/oAcpECqa7P9KGkQA3Bmw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gVjh4ysb2V+iE2BxWTbOHKAhsI2Gfh2+aX2G1jR5ac2hzXyPjSblL1hJFEfVoDKi+ WNMXtjVntq0hzQ+a/UQlDLXeE/Ev+1VzxwmLMFmNLlwCsgrgBI5S2W1l1Gnxf8rDCB WPVHLDyrYeI5X4Y1VqJ+ceMUwf2aFvHItHSa3ozY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e79de833f_a2f3ff5ce658f8434967c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:22:12 -0000 ----==_mimepart_5b23e79de833f_a2f3ff5ce658f8434967c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I really don't understand this PR. If you don't want someone to use a new connection ID, then don't give them one. I'd be happier saying that endpoints MUST NOT knowingly use a new IP address without a new connection ID. -- 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/1447#issuecomment-397672427 ----==_mimepart_5b23e79de833f_a2f3ff5ce658f8434967c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I really don't understand this PR. If you don't want someone to use a new connection ID, then don't give them one. I'd be happier saying that endpoints MUST NOT knowingly use a new IP address without a new connection ID.

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

----==_mimepart_5b23e79de833f_a2f3ff5ce658f8434967c-- From nobody Fri Jun 15 09:23:17 2018 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 3E53E130F37 for ; Fri, 15 Jun 2018 09:23:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zWRrSIlo685D for ; Fri, 15 Jun 2018 09:23:05 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88407130E35 for ; Fri, 15 Jun 2018 09:22:55 -0700 (PDT) Date: Fri, 15 Jun 2018 09:22:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529079774; bh=Kq+R6m/KdxWV8Z4sUIWUoQkYN3duiQsZTDnfpU9kkJU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=I/uglYF3eM9fKQPmtNNX7dz3DLzvdKZAY5EQ/1WYVdacG29CC9nBG6ReK7qSgBYgK KzTxl/2wInjw5bBBBt/xtzyEAFGjzmsw+yvVBusOUL4NUezdr2AULUEOXYy2IWwOv4 G/VMLYNIdvPMtvBPYxZqjLNSNyg+9tlVR/EQsJDs= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e7dee51b0_6c9a2ab9f3952f54214386"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 16:23:15 -0000 ----==_mimepart_5b23e7dee51b0_6c9a2ab9f3952f54214386 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The number one scenario I personally want to make sure we support (and requires multiple retry support possibly) is an independent DDoS protection device/component sitting in front of a QUIC server. One of the main reasons for the redesign of the Retry mechanics in the new Stream 0 design is this. When this device is in path, it is possible that it sends a Retry for the first client Initial packet, and then lets the second Initial packet through. The QUIC server receives the second client Initial, it may (for whatever reason) decide it wants to do a Retry. The client needs to be able to handle this scenario and respond to the second Retry packet with a third client Initial packet. Now obviously, it would be best if the QUIC server doesn't need to send the second Retry packet but it might not (probably won't) know about the DDoS protection device sitting in front of it. If it does know about it, it could just assume all client Initial packets are validated, but I don't want to depend on this, as it's dependent on a particular deployment and infrastructure. -- 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/1451#issuecomment-397672726 ----==_mimepart_5b23e7dee51b0_6c9a2ab9f3952f54214386 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The number one scenario I personally want to make sure we support (and= requires multiple retry support possibly) is an independent DDoS protect= ion device/component sitting in front of a QUIC server. One of the main r= easons for the redesign of the Retry mechanics in the new Stream 0 design= is this. When this device is in path, it is possible that it sends a Ret= ry for the first client Initial packet, and then lets the second Initial = packet through. The QUIC server receives the second client Initial, it ma= y (for whatever reason) decide it wants to do a Retry. The client needs t= o be able to handle this scenario and respond to the second Retry packet = with a third client Initial packet.

Now obviously, it would be best if the QUIC server doesn't need to sen= d the second Retry packet but it might not (probably won't) know about th= e DDoS protection device sitting in front of it. If it does know about it= , it could just assume all client Initial packets are validated, but I do= n't want to depend on this, as it's dependent on a particular deployment = and infrastructure.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23e7dee51b0_6c9a2ab9f3952f54214386-- From nobody Fri Jun 15 09:25:25 2018 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 0A8B9130DC0 for ; Fri, 15 Jun 2018 09:24:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ItyvltYUhc5J for ; Fri, 15 Jun 2018 09:24:49 -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 6F18E130E4F for ; Fri, 15 Jun 2018 09:24:47 -0700 (PDT) Date: Fri, 15 Jun 2018 09:24:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529079886; bh=q5WPreUD3BZB+UxpZC/CDDUqa0USlcdERmgZCFgHA98=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ecWuHo8+FkagPqeEr+EP5+UB490DzulnXbxpD02OTqSJLoQHWFhN8XihhFN5hICM6 RIzpMoVOMHgJTZjkuBYN7ncB1QPD6+f9qDlGsqv4k7DPst10f5FR+GtoZQNKUlCrh5 FUZvZ13iU10dMsBBikqAV+anuUb7Op99OcWhFAFU= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e84e9ab49_36643fb4d93baf8826979e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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: Fri, 15 Jun 2018 16:24:51 -0000 ----==_mimepart_5b23e84e9ab49_36643fb4d93baf8826979e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson are we ruling out use of multiple connection IDs on the same address? That seems too restrictive. I always prefer explicit mechanisms compared to inferred behavior for most flexibility. I also like this PR because it allows the client to automatically turn on keep-alives to protect against NAT rebinding when the server states that it is not capable of supporting migration. -- 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/1447#issuecomment-397673268 ----==_mimepart_5b23e84e9ab49_36643fb4d93baf8826979e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson are we ruling o= ut use of multiple connection IDs on the same address? That seems too res= trictive. I always prefer explicit mechanisms compared to inferred behavi= or for most flexibility. I also like this PR because it allows the client= to automatically turn on keep-alives to protect against NAT rebinding wh= en the server states that it is not capable of supporting migration.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23e84e9ab49_36643fb4d93baf8826979e-- From nobody Fri Jun 15 09:25:31 2018 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 A842B130E35 for ; Fri, 15 Jun 2018 09:25:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 O3ER-EgukCz1 for ; Fri, 15 Jun 2018 09:25:17 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23819130DC0 for ; Fri, 15 Jun 2018 09:25:17 -0700 (PDT) Date: Fri, 15 Jun 2018 09:25:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529079916; bh=4La1LZBZTtGpa52Ddm38aG8uifvY0Kw6pl+5ESm0XWQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=h95UGtl9sI9honXiIQ841+R5SsbkbIUlqVEBHc/Oyk0HGZPavb7IWgGVH6pANxJv5 lPHswp1nrIKA35jlEITBgb9yX9wr4Vkhqw04pLqwl7mHVA+h+DUA06AfJ3GWifAh/3 aldG8HavA6hHfw8FydUIJP0i2vbRAWN1SfIJMqyc= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e86c7b11e_627a2b21bad6af541450e9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 16:25:21 -0000 ----==_mimepart_5b23e86c7b11e_627a2b21bad6af541450e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson if you go the route of depending on CID availability, it doesn't necessarily give you the indication that even NAT rebinding won't work and that the client should use a more aggressive keep alive timer for long standing connections. I personally prefer the explicit design of this PR. -- 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/1447#issuecomment-397673439 ----==_mimepart_5b23e86c7b11e_627a2b21bad6af541450e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson if you go the r= oute of depending on CID availability, it doesn't necessarily give you th= e indication that even NAT rebinding won't work and that the client shoul= d use a more aggressive keep alive timer for long standing connections. I= personally prefer the explicit design of this PR.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23e86c7b11e_627a2b21bad6af541450e9-- From nobody Fri Jun 15 09:28:46 2018 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 9CBA0130F3F for ; Fri, 15 Jun 2018 09:28:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QoVqS1VdLOTj for ; Fri, 15 Jun 2018 09:28:31 -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 DAC51130F29 for ; Fri, 15 Jun 2018 09:28:30 -0700 (PDT) Date: Fri, 15 Jun 2018 09:28:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080110; bh=grDmn0rOB+1RHxLOr2DAxNXzD8jKb8Qc0thaJY/cbfc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KvtpkJ+xOU4upXSyy8TPYQ3SISdjysdvJw+uR7rmDe3TTmaDZmJX9GpmKc0CNzWfl qCFcFe0QZSjKXyRlEeA8luzU8G4yo56tjfFU33s6EOoG5Hyu8sJfr4RxDPhP19O0RQ uMi2WdeReuDZwvvPNlgNut90fypAWb4nK3PQ/Bvg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e92e23139_2a902ab78ded0f5c2465c2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:28:43 -0000 ----==_mimepart_5b23e92e23139_2a902ab78ded0f5c2465c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What @ekr said. Also, this is the most complicated part of the protocol grammar and using pictures and words would be much more verbose and likely less precise. -- 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/1449#issuecomment-397674409 ----==_mimepart_5b23e92e23139_2a902ab78ded0f5c2465c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

What @ekr said. Also, this is the most complicated part of the protocol grammar and using pictures and words would be much more verbose and likely less precise.

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

----==_mimepart_5b23e92e23139_2a902ab78ded0f5c2465c2-- From nobody Fri Jun 15 09:28:52 2018 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 1B9BF130EF9 for ; Fri, 15 Jun 2018 09:28:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 NveADDvQSlOm for ; Fri, 15 Jun 2018 09:28:31 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5531130F27 for ; Fri, 15 Jun 2018 09:28:30 -0700 (PDT) Date: Fri, 15 Jun 2018 09:28:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080110; bh=EZDc37mqy0ZdOeISjUocgJZ9o9FzNBozWXb0YhvNON4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qKeTQwIQVsNWpGOvElysTrWzzda0632Wia+92nH/FjQgvp8bxDcpZztjLiPJrO5TF jos1/VSmhj4GvIdsYXdPDRYq/P0wyYkXsOVjsv58LkqpKkpsId7i4eVWIBM0M32peb HfZOVpeI8sUsS+RJ+K3BBqMaJxi7SH9r+0J29dHg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23e92e33d5b_2d493fe727204f8814419d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:28:44 -0000 ----==_mimepart_5b23e92e33d5b_2d493fe727204f8814419d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1449. -- 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/1449#event-1683806465 ----==_mimepart_5b23e92e33d5b_2d493fe727204f8814419d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1449.

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

----==_mimepart_5b23e92e33d5b_2d493fe727204f8814419d-- From nobody Fri Jun 15 09:33:08 2018 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 C0850130E3D for ; Fri, 15 Jun 2018 09:33:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DSdJWTAmbs1y for ; Fri, 15 Jun 2018 09:33:05 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D351130DC0 for ; Fri, 15 Jun 2018 09:33:05 -0700 (PDT) Date: Fri, 15 Jun 2018 09:33:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080384; bh=jo+DkDb5QfMPwZe7cPhqQ9QTS+qMsJUOJ+wDqljUJyo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=olc8QjcWVr3/CRdrzSgguPIfd2Gk2JRMNL45nXlFgCqXyxh+D8Xmm8GJ7ogaKgISu W0jhsGlT8Kbp6nS1q2yjRxxjI9bvQKstZZs5TM0fOvSt3yohkMtOC47Kearil7DFOu ZmwUVR22E3SJG/PKW4MHER42QRB08X8VT9kdx7lI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ea406048d_c2f2acf94204f5c18265c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:33:07 -0000 ----==_mimepart_5b23ea406048d_c2f2acf94204f5c18265c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj, yes, a connection ID might allow this to be detected. However, add one iteration and the problem remains. @nibanks, you seem to have described a scenario where this gets even worse. The retransmission has effectively forked the connection. One of those forks is going to die, but you can't be certain which one. We're reduced to relying on chance for having the connection complete. -- 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/1451#issuecomment-397675631 ----==_mimepart_5b23ea406048d_c2f2acf94204f5c18265c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj, yes, a connection ID mi= ght allow this to be detected. However, add one iteration and the proble= m remains.

@nibanks, you seem to have descri= bed a scenario where this gets even worse. The retransmission has effect= ively forked the connection. One of those forks is going to die, but you= can't be certain which one. We're reduced to relying on chance for havi= ng the connection complete.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23ea406048d_c2f2acf94204f5c18265c-- From nobody Fri Jun 15 09:33:27 2018 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 B8752130E22 for ; Fri, 15 Jun 2018 09:33:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 818jHXKgNcdu for ; Fri, 15 Jun 2018 09:33:21 -0700 (PDT) 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 6D3D0130F0D for ; Fri, 15 Jun 2018 09:33:21 -0700 (PDT) Date: Fri, 15 Jun 2018 09:33:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080400; bh=7gaS/ieZY3vKC7teXv6tL0LAa28QqPXM5Zk2xMDVJH0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iiNkmJQ3Jn4ZJO/YY/hC5zxs/i7Vy7c2Ov6IC1w4AAtUyeua9Pr+ubbRUjktbwKeO jG20Uddjo2y1afeoFwjrMT2AuD6Ei1n7yAGNxPHY75v983gyfV+TkHhMusSd59Xr9d rhKwce7rbcZo+YDL3KOzoD1OM6jqP7HXMFtdhI4Q= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ea50bf7d4_29be2ab78ded0f5c33041c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 16:33:25 -0000 ----==_mimepart_5b23ea50bf7d4_29be2ab78ded0f5c33041c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > ~~~~~~~~~~ -{:#fig-size-sync title="Table Size Synchronize"} +{:#fig-size-sync title="Table State Synchronize"} + +A decoder SHOULD emit a Table State Synchronize after receiving new dynamic +table entries if the most recently inserted entry was not the Largest Reference Since we are going to remove length prefix, 'entries' here is vague. How many entries? I think in the common case the inserts will get processed before the references, but a blocking decoder would not want to send TSS without delaying to check for a referencing header block, so perhaps the SHOULD here is misleading? Maybe it would help to describe the tradeoff - A decoder chooses when to emit TSS instructions. Emitting a TSS after adding each new dynamic table entry will provide the most timely feedback to the encoder, but could be redundant with other decoder feedback. By delaying a TSS, a decoder might be able to coalesce multiple TSS instructions, or replace them entirely with Header Acknowledgements. However, delaying too long may lead to compression inefficiencies if the encoder waits for an entry to be acknowledged before using it. -- 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/1410#pullrequestreview-129227518 ----==_mimepart_5b23ea50bf7d4_29be2ab78ded0f5c33041c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

>  ~~~~~~~~~~
-{:#fig-size-sync title="Table Size Synchronize"}
+{:#fig-size-sync title="Table State Synchronize"}
+
+A decoder SHOULD emit a Table State Synchronize after receiving new dynamic
+table entries if the most recently inserted entry was not the Largest Reference

Since we are going to remove length prefix, 'entries' here is vague. How many entries? I think in the common case the inserts will get processed before the references, but a blocking decoder would not want to send TSS without delaying to check for a referencing header block, so perhaps the SHOULD here is misleading?

Maybe it would help to describe the tradeoff -

A decoder chooses when to emit TSS instructions. Emitting a TSS after adding each new dynamic table entry will provide the most timely feedback to the encoder, but could be redundant with other decoder feedback. By delaying a TSS, a decoder might be able to coalesce multiple TSS instructions, or replace them entirely with Header Acknowledgements. However, delaying too long may lead to compression inefficiencies if the encoder waits for an entry to be acknowledged before using it.

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

----==_mimepart_5b23ea50bf7d4_29be2ab78ded0f5c33041c-- From nobody Fri Jun 15 09:37:05 2018 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 CE850130E22 for ; Fri, 15 Jun 2018 09:37:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3wi0PDIWiw5j for ; Fri, 15 Jun 2018 09:37:01 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DCD5130DC0 for ; Fri, 15 Jun 2018 09:37:01 -0700 (PDT) Date: Fri, 15 Jun 2018 09:37:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080620; bh=d5hn2yELAvt7hCymTXupzfzQCEsJEFy4s5JXbTctisg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QP4qcBdPZGlOyFpJjgC/J/Kh3f58T/9N9yAXF5+QwyfwLqfrvLMdIhGrdidsF2gyd ce02rnv37m2MpIdLOLyp4Q2/di/rLv8o1l+1tMKdGl0IEWFHYzWIxbI0h6Zi4I8ylV mhKLijnsprftrnkWzmmZW6FCPvO+eHBad3Q/o8ZQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23eb2c866b3_5b2e2b2222eeef5c347270"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 16:37:03 -0000 ----==_mimepart_5b23eb2c866b3_5b2e2b2222eeef5c347270 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @pravb, I didn't say anything about multiple connection IDs on the same address. I'm not sure how it has any bearing on this, other than to say that if you don't provide connection IDs, this won't happen. But here's the thing I don't get: if you are routing based solely on 5-tuple, why use connection IDs at all? If we want a keep-alive function, then we should explicitly build one. -- 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/1447#issuecomment-397676602 ----==_mimepart_5b23eb2c866b3_5b2e2b2222eeef5c347270 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@pravb, I didn't say anything about= multiple connection IDs on the same address. I'm not sure how it has an= y bearing on this, other than to say that if you don't provide connection= IDs, this won't happen. But here's the thing I don't get: if you are ro= uting based solely on 5-tuple, why use connection IDs at all?

If we want a keep-alive function, then we should explicitly build one.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23eb2c866b3_5b2e2b2222eeef5c347270-- From nobody Fri Jun 15 09:44:08 2018 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 CEF27130DFB for ; Fri, 15 Jun 2018 09:44:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 AW220SqoZUpf for ; Fri, 15 Jun 2018 09:44:04 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED0B12F18C for ; Fri, 15 Jun 2018 09:44:04 -0700 (PDT) Date: Fri, 15 Jun 2018 09:44:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529081043; bh=hVDle+lPZsOmiecgW45trblokHzU6YGc5Zy+hg0cLLQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zDBW5wOYDAfDZazdpXjP/+wxtI9kdCRd1N1T+N6HapCkFDxBkETN7ucEHUvppTyzd RrOC25rqaprQUuUaPdExP2/K4KyYyq+NUz8cPS0/Qh8tCI3xzLoUNo/akU1nRcKBGz XfADGrURz5r9zQubgY4X3I5RfaCQuA5qD+uw1jsI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ecd3bc1db_721e3f8513f60f7c16235b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 15 Jun 2018 16:44:07 -0000 ----==_mimepart_5b23ecd3bc1db_721e3f8513f60f7c16235b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson yes - what if the source ID must be different from the previous source ID when responding to a retry? The initial SCID could be zero-length, but first, second etc. attempts cannot. The client can later revert to 0-length SCID. This could mess with P2P server load balancers but then SCID would not be zero-length anyway. -- 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/1451#issuecomment-397678272 ----==_mimepart_5b23ecd3bc1db_721e3f8513f60f7c16235b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson yes - what if t= he source ID must be different from the previous source ID when respondin= g to a retry? The initial SCID could be zero-length, but first, second et= c. attempts cannot. The client can later revert to 0-length SCID.

This could mess with P2P server load balancers but then SCID would not= be zero-length anyway.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b23ecd3bc1db_721e3f8513f60f7c16235b-- From nobody Fri Jun 15 09:50:10 2018 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 2B24112F18C for ; Fri, 15 Jun 2018 09:50:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 URYxPc1ky-6V for ; Fri, 15 Jun 2018 09:50:06 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A60D124D68 for ; Fri, 15 Jun 2018 09:50:06 -0700 (PDT) Date: Fri, 15 Jun 2018 09:50:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529081405; bh=9jFfJkPOGTyNyWEV2TUFCxH7VHRe2Fx2c0M0oVDcevU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GBUaXJLe4FurFrz+NswqeJw6oU38obBy1evKyQyFCvjwoFzqi/rmI6pxLouHrH3ak Tz9UCHBxTvFv4lhhHkpjS+rGfTKMC98g2nedrw2wTWkcrELDebt5V/EkEg9YQ7F16X 9HX2gy/0UVMhVjvfLlkfYrFYYSWfihb8pKPUoGzc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ee3d8a3c4_74643fd65159ef7c1069b5"; 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.26 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: Fri, 15 Jun 2018 16:50:09 -0000 ----==_mimepart_5b23ee3d8a3c4_74643fd65159ef7c1069b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Without connection IDs, you're limited to a single session per server per client IP, which aligns poorly with multiple clients behind a NAT. So simply omitting CIDs isn't the best choice. Not supplying additional CIDs is certainly an option - pick one and use it for the lifetime of the connection. But that goes against our existing advice to rotate CIDs after a period of quiescence. Keeping the mechanics of CID choice and the client's ability to change its source address separate feels cleanest to me. -- 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/1447#issuecomment-397680274 ----==_mimepart_5b23ee3d8a3c4_74643fd65159ef7c1069b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Without connection IDs, you're limited to a single session per server = per client IP, which aligns poorly with multiple clients behind a NAT. So= simply omitting CIDs isn't the best choice.

Not supplying additional CIDs is certainly an option - pick one and us= e it for the lifetime of the connection. But that goes against our existi= ng advice to rotate CIDs after a period of quiescence.

Keeping the mechanics of CID choice and the client's ability to change= its source address separate feels cleanest to me.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23ee3d8a3c4_74643fd65159ef7c1069b5-- From nobody Fri Jun 15 09:57:45 2018 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 5AFB3130E22 for ; Fri, 15 Jun 2018 09:57:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 l7rcq57iFXbI for ; Fri, 15 Jun 2018 09:57:41 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB93130DFB for ; Fri, 15 Jun 2018 09:57:41 -0700 (PDT) Date: Fri, 15 Jun 2018 09:57:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529081861; bh=EZgNlHWYtZZRBX6NJOCuC2B96Gp1ZB4WmbU2UH3QLJ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=coqZ4IZIbhdI2woGO/xcNR3e1avbMNpIWNx+EotEw4WZBPYTKdovbhZIwkXBHt/1e ysIDEIG7SsK3/6UYzxJtNhP2XkLFQnFhs7ssL+wILpUnuDwNM9AIZyrm7GddLZK375 9L7jPDyx6tRTmHNQ1pAzQ76KdG8nXC9QfxSHuhAU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clearer pseudocode/TLS syntax specification (#1449) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23f00568e12_6e892ad2f0b02f50218753"; 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.26 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: Fri, 15 Jun 2018 16:57:44 -0000 ----==_mimepart_5b23f00568e12_6e892ad2f0b02f50218753 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit QuicVersion is explicitly defined as a uint32, so references to that type are already a known size. The other things with explicit sizes given are arrays (albeit sometimes arrays of bytes that represent a single value), and arrays are length-prefixed. -- 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/1449#issuecomment-397682236 ----==_mimepart_5b23f00568e12_6e892ad2f0b02f50218753 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

QuicVersion is explicitly defined as a uint32, so references to that type are already a known size. The other things with explicit sizes given are arrays (albeit sometimes arrays of bytes that represent a single value), and arrays are length-prefixed.

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

----==_mimepart_5b23f00568e12_6e892ad2f0b02f50218753-- From nobody Fri Jun 15 10:13:51 2018 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 DB478130DFB for ; Fri, 15 Jun 2018 10:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jGpACXTqASDG for ; Fri, 15 Jun 2018 10:13:47 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 000C212F18C for ; Fri, 15 Jun 2018 10:13:46 -0700 (PDT) Date: Fri, 15 Jun 2018 10:13:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529082826; bh=J/tZqoKKqJ+qCIZXd8yLkykPy3emYZrUYv+Y2bydLTw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kT5sSGuKqxVpwPkt5EjhFAEWgBgXqm9pQ/a0dzkIXIRiyGgPsEsCVqZiGbJfWOnZc KyoDdvPxSZ4iPXDDbVXSvSkJHem0pUka0vX8rupmcOKjLE1OpDWWxtAbLkZYohSrsi X6g985jJXT5jNwqGDjRgQ8iV2UbNc2rALVxqctl8= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23f3c9e6fa1_1d092ac02763ef546482e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 17:13:49 -0000 ----==_mimepart_5b23f3c9e6fa1_1d092ac02763ef546482e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. Would it be reasonable to allow the BLOCKED frames in 0-RTT, assuming the previous connection set very small limits in it's TP? For instance, what if the previous connection set the initial maximum number of bidirectional streams to 1, and the client would like to open 2 streams in 0-RTT. Should it be allowed to open 1 stream and include a `STREAM_ID_BLOCKED` frame? -- 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/1450#pullrequestreview-129251838 ----==_mimepart_5b23f3c9e6fa1_1d092ac02763ef546482e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-tls.md:

> +same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.

Would it be reasonable to allow the BLOCKED frames in 0-RTT, assuming the previous connection set very small limits in it's TP? For instance, what if the previous connection set the initial maximum number of bidirectional streams to 1, and the client would like to open 2 streams in 0-RTT. Should it be allowed to open 1 stream and include a STREAM_ID_BLOCKED frame?

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

----==_mimepart_5b23f3c9e6fa1_1d092ac02763ef546482e-- From nobody Fri Jun 15 10:19:02 2018 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 58CA7130E26 for ; Fri, 15 Jun 2018 10:19:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 B8a2xjQKnYOW for ; Fri, 15 Jun 2018 10:19:00 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00780124D68 for ; Fri, 15 Jun 2018 10:18:59 -0700 (PDT) Date: Fri, 15 Jun 2018 10:18:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529083139; bh=OzTF1/h2PDSp5S7cPOI11reiOwpP1VGancTCWTYq26I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qeMdFL6mthWysr7BhDfBtqoiuEg0SiS1Wc7j715qEIgDE3ZJk3MdlZIdyZtCOngY7 vt7S5zs6fj0e5lY4n3fPvVQNmZYsOF/yPTtKMVl+AZg1G1EOqGU5hBUr9h9B5Ro/FU xn43OO+zSh0mWwQaug9pMbgO8Dp1mD6nSKS3M44U= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23f5031cf4f_663a3fa9bf7c2f88190829"; 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.26 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: Fri, 15 Jun 2018 17:19:02 -0000 ----==_mimepart_5b23f5031cf4f_663a3fa9bf7c2f88190829 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As to polarity - in this version of QUIC, at least, clients initiate all migrations. The most a server can do is suggest a different IP address to which the client should migrate, which the client can opt not to do. If a client doesn't support migration, it need not tell the server -- it just doesn't migrate. Should a future / different version of QUIC enable spontaneous server migration or provide a mechanism to *force* peer migration, it would make sense for this parameter to be bilateral in that version. -- 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/1447#issuecomment-397687470 ----==_mimepart_5b23f5031cf4f_663a3fa9bf7c2f88190829 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As to polarity - in this version of QUIC, at least, clients initiate a= ll migrations. The most a server can do is suggest a different IP addres= s to which the client should migrate, which the client can opt not to do.= If a client doesn't support migration, it need not tell the server -- i= t just doesn't migrate.

Should a future / different version of QUIC enable spontaneous server = migration or provide a mechanism to force peer migration, it wou= ld make sense for this parameter to be bilateral in that version.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b23f5031cf4f_663a3fa9bf7c2f88190829-- From nobody Fri Jun 15 10:26:34 2018 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 0F31F12872C for ; Fri, 15 Jun 2018 10:26:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 klBL1ewrbkTX for ; Fri, 15 Jun 2018 10:26:31 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 26696124C04 for ; Fri, 15 Jun 2018 10:26:31 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529083590; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=UVeQpzp6JeTloCOcwCOGE/KVUGeH9LyP++8APieknww=; b=y8Ri1oQXCsoCiGfzcET7AMvESsXzn/R+Gm4U9NdEYh9dcKyqNHsR2N5jBn4ML8A7ld87QPb3 C9YFTA6DsB7h5qyIdS8xKXxjJO0thN9I61wmrYj/238dxBp1g35tEZwqhqzkavqknNFcZmkm wuWYuIg8ufZrPiXNTsU3o9a6ni8= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b23f6c5.7fa370e796f0-smtp-out-n03; Fri, 15 Jun 2018 17:26:29 -0000 (UTC) Date: Fri, 15 Jun 2018 10:26:28 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b23f6c48b2fc_5d882aab105e7c1c73936@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b789dd: local address Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b23f6c48ae1b_5d882aab105e7c1c7381b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 17:26:33 -0000 ----==_mimepart_5b23f6c48ae1b_5d882aab105e7c1c7381b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/disable_migration Home: https://github.com/quicwg/base-drafts Commit: b789dd84f3b9dbd0182f8b674411368824afb22b https://github.com/quicwg/base-drafts/commit/b789dd84f3b9dbd0182f8b674411368824afb22b Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- local address **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b23f6c48ae1b_5d882aab105e7c1c7381b-- From nobody Fri Jun 15 10:26:39 2018 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 64A8F124C04 for ; Fri, 15 Jun 2018 10:26:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 68FpT_bveudd for ; Fri, 15 Jun 2018 10:26:33 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1E59124D68 for ; Fri, 15 Jun 2018 10:26:32 -0700 (PDT) Date: Fri, 15 Jun 2018 10:26:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529083592; bh=fH/FojZtTmTuzbrcX/gQTHZAwlVC262+ZUfSb16ec0A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ajPazcLYuVqGDWDw0czxawNszw/pI4XKNx7t4HG0NWBjnpIUHqtwp22LAJXfenmM4 DtSu9yj/85INR9i/7ETUNQgC7t9SzLfoogYokMeRovkuJCve8kFwO8FxJbtYi99ARm cbDBrXMLcDM4RHkaE28g6mUeowomwl4vz3ywiAB8= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23f6c8d839_3fc72b1520a54f501193c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 15 Jun 2018 17:26:35 -0000 ----==_mimepart_5b23f6c8d839_3fc72b1520a54f501193c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. b789dd8 local address -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1447/files/ec94b63b140ea2d92417a6c9c674d10cb1d6f001..b789dd84f3b9dbd0182f8b674411368824afb22b ----==_mimepart_5b23f6c8d839_3fc72b1520a54f501193c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b23f6c8d839_3fc72b1520a54f501193c8-- From nobody Fri Jun 15 10:38:28 2018 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 C9AEA12872C for ; Fri, 15 Jun 2018 10:38:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 nGedzK6Xr7yk for ; Fri, 15 Jun 2018 10:38:24 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 4018C124D68 for ; Fri, 15 Jun 2018 10:38:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529084303; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=oGth66sSv6hLySm/u5qm8tVQpsnpSRzWmXxfb3mJxMI=; b=RGxzvE+MPP/Q4qV+1sqYNORL5He9roVZUGSTovdK7Dq7qUiCtcqtfI+Jsd6FZT9mkQ9gZldW USab0aGI3141GkZYF0FTGC0LPi3cqYPjd02q0d6c0anFyti22JynK9xJsMJNaVM0hL+ikVr2 onvM6zLFdELTAYq2mXUjyEiCWh4= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b23f98f.7f9e9b77d9f0-smtp-out-n02; Fri, 15 Jun 2018 17:38:23 -0000 (UTC) Date: Fri, 15 Jun 2018 10:38:23 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b23f98f7e3b8_1cb2ac5b76e7c0420022@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 56990a: Expand CID ratchet text Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b23f98f7dffa_1cb2ac5b76e7c0419954"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 17:38:26 -0000 ----==_mimepart_5b23f98f7dffa_1cb2ac5b76e7c0419954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/cids_not_ordered Home: https://github.com/quicwg/base-drafts Commit: 56990a07efaa84b592838961544e3211c7d926e5 https://github.com/quicwg/base-drafts/commit/56990a07efaa84b592838961544e3211c7d926e5 Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Expand CID ratchet text **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b23f98f7dffa_1cb2ac5b76e7c0419954-- From nobody Fri Jun 15 10:45:16 2018 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 EE25812872C for ; Fri, 15 Jun 2018 10:45:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 A_aVgvmY49T4 for ; Fri, 15 Jun 2018 10:45:12 -0700 (PDT) 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 3D812124D68 for ; Fri, 15 Jun 2018 10:45:12 -0700 (PDT) Date: Fri, 15 Jun 2018 10:45:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529084711; bh=mpClrXqi+MKbNljFSJzSZzO/7DFXu7qr3op3l5BaTFE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=LuQ2bPYTSN/S5IIfp1MaQv6/gNgi7wbIYG6KAfDjv1hCTgAsNmSf4YBxb4ZVEWmdJ efzexICnv2hVpGIxOaTaWf6LdS8R4n2VTgcVkq8cVS43tQ4npQYyKgijvqxdgzoE5o 9zSvj4SLAUx9b2X0MStr8jBhA9t2qxIHqye+UISU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] CID ratcheting language is imprecise (#1452) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fb27637ec_5b913fe6f3b20f8881014"; 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.26 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: Fri, 15 Jun 2018 17:45:14 -0000 ----==_mimepart_5b23fb27637ec_5b913fe6f3b20f8881014 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As currently written, each endpoint MUST switch to a new CID when it sees its peer do so. If taken literally by each peer, this will cause a change of CID by each peer every round trip; unless a sufficient stream of NCID frames is kept up, they'll exhaust the supply and #1276 would have the connection be closed. That seems both unnecessarily fragile and not actually the intent of this requirement. Intuitively, you want to switch when: - You see the peer do so - It's not in response to your own switch Not marking this design, because I'm fairly sure this is the intent of the existing text, albeit not what it actually says. I'm having trouble coming up with a concise way of wording the second piece of the condition, however. Ironically, this would have been simple when CIDs had sequence numbers -- you MUST always use a CID with a sequence number >= the sequence number of the CID you're receiving from the peer. But we weren't actually using them for that. We could do something similar, though, saying you must count the number of times the peer has changed CIDs post-handshake and you must have changed at least as many times. -- 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/1452 ----==_mimepart_5b23fb27637ec_5b913fe6f3b20f8881014 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

As currently written, each endpoint MUST switch to a new CID when it sees its peer do so. If taken literally by each peer, this will cause a change of CID by each peer every round trip; unless a sufficient stream of NCID frames is kept up, they'll exhaust the supply and #1276 would have the connection be closed. That seems both unnecessarily fragile and not actually the intent of this requirement.

Intuitively, you want to switch when:

  • You see the peer do so
  • It's not in response to your own switch

Not marking this design, because I'm fairly sure this is the intent of the existing text, albeit not what it actually says. I'm having trouble coming up with a concise way of wording the second piece of the condition, however.

Ironically, this would have been simple when CIDs had sequence numbers -- you MUST always use a CID with a sequence number >= the sequence number of the CID you're receiving from the peer. But we weren't actually using them for that. We could do something similar, though, saying you must count the number of times the peer has changed CIDs post-handshake and you must have changed at least as many times.

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

----==_mimepart_5b23fb27637ec_5b913fe6f3b20f8881014-- From nobody Fri Jun 15 10:46:57 2018 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 AD7AD12F18C for ; Fri, 15 Jun 2018 10:46:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 8gTipf4_M9XT for ; Fri, 15 Jun 2018 10:46:53 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 6E53B124D68 for ; Fri, 15 Jun 2018 10:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=k4tzza4oTErJ4U72Go0jDa4Zcig=; b=Ak5eyKimJZ7hzZEk lKeghfXcpaPsTbf3yl7ypZEEiTMY27ijqtny3IQdEgtGgPYgCYy18sK8v9bbmIRX G/ABR4iENb09zozWGK1qklc6CMaIjADB851Elb1p18kBzx1milWmd7PZ9eRkSWF1 ANQmo+1JNTxfYohJ8SgdlvvAK3I= Received: by filter0005p1iad2.sendgrid.net with SMTP id filter0005p1iad2-13671-5B23FB8C-7 2018-06-15 17:46:52.229612472 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id dloAJNeFRcON_OSK5kmYtA for ; Fri, 15 Jun 2018 17:46:52.180 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 2A2223E006B for ; Fri, 15 Jun 2018 10:46:52 -0700 (PDT) Date: Fri, 15 Jun 2018 17:46:52 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Expand CID ratchet text (#1453) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fb8c28c1f_4012af613280f58782b4"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2bbHFSPG5mYiA95HL0BU0frygBYKveNhBTMZ zPCcdFbbT2H2Jt1vMsyEr9o+RTLvDN4VYQ9gE4OpOX6iOg0BvtR+q2WRxHSX/6ROhhySMFYft/p7gI ev24qScj0X5r6wch7Qt6QswNR2jPhJidYKCPdDY5t8TG7Ibo5ZsuyI2QXH2aON1X1tNdUp3BKh8NgD c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 17:46:56 -0000 ----==_mimepart_5b23fb8c28c1f_4012af613280f58782b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1276, plus removes a stray reference to CIDs being used in sequential order. Encountered #1452 while writing this; if we come to a resolution quickly I can incorporate that here as well. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1453 -- Commit Summary -- * Expand CID ratchet text -- File Changes -- M draft-ietf-quic-transport.md (13) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1453.patch https://github.com/quicwg/base-drafts/pull/1453.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/1453 ----==_mimepart_5b23fb8c28c1f_4012af613280f58782b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1276, plus removes a stray reference to CIDs being used in sequential order. Encountered #1452 while writing this; if we come to a resolution quickly I can incorporate that here as well.

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

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

Commit Summary

  • Expand CID ratchet text

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 mute the thread.

----==_mimepart_5b23fb8c28c1f_4012af613280f58782b4-- From nobody Fri Jun 15 10:47:31 2018 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 EB38612F18C for ; Fri, 15 Jun 2018 10:47:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 m6CRvOosBerb for ; Fri, 15 Jun 2018 10:47:27 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27827124D68 for ; Fri, 15 Jun 2018 10:47:27 -0700 (PDT) Date: Fri, 15 Jun 2018 10:47:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529084845; bh=BIqF2gJXpajd9Gfnykhy9O1QRZ7JHbmK8P1riIvSjPI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UJaLvXlooBXbb74gv9ORNN9+UrvvF9ZYd0LQSNTpLpe2XW6doR5XVnx9KzXePCnab Azz7BBcVmV1+OD8Vaorv0kz4d3gBicjKd2ESCohpEejt1qRb/rTmcwSgVnIu3+8PdW wKwR8X41fLmcW2i/jRdUGG6WRDokiGGXXkzBNY9Y= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fbad98560_36f32b1994666f601129a0"; 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.26 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: Fri, 15 Jun 2018 17:47:30 -0000 ----==_mimepart_5b23fbad98560_36f32b1994666f601129a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @erickinnear, what do you mean by "use the real name from later"? "Probing packets" is a defined term later in the document. However, I like the remainder of these updates and have made them, plus a forward reference to the definition of probing packets. -- 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/1271#issuecomment-397694837 ----==_mimepart_5b23fbad98560_36f32b1994666f601129a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@erickinnear, what do you mean by "use the real name from later"? "Probing packets" is a defined term later in the document.

However, I like the remainder of these updates and have made them, plus a forward reference to the definition of probing packets.

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

----==_mimepart_5b23fbad98560_36f32b1994666f601129a0-- From nobody Fri Jun 15 10:50:14 2018 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 11086124D68 for ; Fri, 15 Jun 2018 10:50:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 FdlMDwxThJQr for ; Fri, 15 Jun 2018 10:50:09 -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 4BC9012F18C for ; Fri, 15 Jun 2018 10:50:09 -0700 (PDT) Date: Fri, 15 Jun 2018 10:50:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529085008; bh=FJFRfaRcn0TRTI2wLEutJTJAXDCxFzdxMpUas6KrILg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XrmNXpEicTg3+dbsuNxW2d18j48MdDlNt83TxZXdEl/ou4erEatf6JVD5pJxym+He 36qSMamWZ3FDj4BR/l+ODqMkfkv61A+AxT92duUACU4uteqJh5dOg6bV7qvAHk2QLd lOhX/X2xIhyj7nFM+aiQPXZm5F4IL96Lr7HDJlt4= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fc508a2d3_4952acd5010af5c123165"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 17:50:13 -0000 ----==_mimepart_5b23fc508a2d3_4952acd5010af5c123165 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks approved this pull request. LGTM -- 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/1447#pullrequestreview-129263031 ----==_mimepart_5b23fc508a2d3_4952acd5010af5c123165 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks approved this pull request.

LGTM

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

----==_mimepart_5b23fc508a2d3_4952acd5010af5c123165-- From nobody Fri Jun 15 10:55:07 2018 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 8936312F18C for ; Fri, 15 Jun 2018 10:55:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 Rdnk6OQ-6fHd for ; Fri, 15 Jun 2018 10:55:03 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 7CC39124D68 for ; Fri, 15 Jun 2018 10:55:03 -0700 (PDT) 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=pYjJg/vpluKt7NCL0JTReAQi3Os=; b=ZCmRYTmLo5555cbB lVOx6ZtFDrm2PrN4ZvcBOT+MOToio0S55RnvxxOXueZLVMjgFAc6fPU0hSvfHf0N L56r3ynPFZ6L3tp9YrDLJ7KfdQ7PHu3OWCpuhFIiY95A0A+44mnTKh/6ykunwP4b d5W34eaWcbFbWRp4JTlNfHuQu7E= Received: by filter0761p1las1.sendgrid.net with SMTP id filter0761p1las1-30648-5B23FD75-1E 2018-06-15 17:55:01.911574162 +0000 UTC Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0011p1iad2.sendgrid.net (SG) with ESMTP id SYs7eMZfRwCJKl1dobOZyQ for ; Fri, 15 Jun 2018 17:55:01.926 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id CD857C0A71 for ; Fri, 15 Jun 2018 10:55:01 -0700 (PDT) Date: Fri, 15 Jun 2018 17:55:02 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fd75cad63_5e8f2abaa522cf6015358b"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2KeQVHURTbvosf207S12+EAVi3NiGXy2YOnc CL4M9G27cEECX2UbcoHwxFsUca8tCaBiUwndeN1D/o9kF9gX0cZj259Vd9uiXm77Q+NLkUQbc2NUIe MGyWf1hhHMKZ/YLHBVmIy05nG43A/62nH0EfBCJ84a5BQCsxW2IccjzFvex8IDOxx5Ugrgv3UMmahp 0= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 17:55:06 -0000 ----==_mimepart_5b23fd75cad63_5e8f2abaa522cf6015358b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. Of course, now I have to incorporate these into the HTTPbis draft, too. ;-) > @@ -526,6 +526,16 @@ A frame includes the following fields: ## Frame Definitions {#frames} +Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the +requirement that unknown types be ignored. These frames have no semantic +meaning, and SHOULD be sent when application-layer padding is desired. They MAY Holdover from the HTTP draft, since that's recommending this in preference to padding fields on HEADERS/DATA. I agree, the normative isn't needed here. > @@ -1418,6 +1446,16 @@ The entries in the following table are registered by this document. | MAX_HEADER_LIST_SIZE | 0x6 | {{settings-parameters}} | |----------------------------|------|-------------------------| +Additionally, each code of the format `0x?a?a` where each `?` is any octet (that Bah. -- 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/1446#pullrequestreview-129263573 ----==_mimepart_5b23fd75cad63_5e8f2abaa522cf6015358b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

Of course, now I have to incorporate these into the HTTPbis draft, too. ;-)

In draft-ietf-quic-http.md:

> @@ -526,6 +526,16 @@ A frame includes the following fields:
 
 ## Frame Definitions {#frames}
 
+Frame types of the format `0xb + (0x1f * N)` are reserved to exercise the
+requirement that unknown types be ignored. These frames have no semantic
+meaning, and SHOULD be sent when application-layer padding is desired.  They MAY

Holdover from the HTTP draft, since that's recommending this in preference to padding fields on HEADERS/DATA. I agree, the normative isn't needed here.

In draft-ietf-quic-http.md:

> @@ -1418,6 +1446,16 @@ The entries in the following table are registered by this document.
 | MAX_HEADER_LIST_SIZE       | 0x6  | {{settings-parameters}} |
 |----------------------------|------|-------------------------|
 
+Additionally, each code of the format `0x?a?a` where each `?` is any octet (that

Bah.

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

----==_mimepart_5b23fd75cad63_5e8f2abaa522cf6015358b-- From nobody Fri Jun 15 10:56:10 2018 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 3AB3212F18C for ; Fri, 15 Jun 2018 10:56:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 8n5cdrRVX03L for ; Fri, 15 Jun 2018 10:56:05 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 96BCA124D68 for ; Fri, 15 Jun 2018 10:56:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529085365; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=JGIqqJRwbSNaGtOVpfBvJc1O5hZZHxAEREv2gufD3aw=; b=Qs7bOU/HQX4eg3vjOkk2HZHFlvz02Mia5y28QWD/UzcL3mEDutdmSEGURc8XHto0bnXYMiB1 vO+dM/BLchq+UDhTN6FUtfvyUPBDT5nSt+CnI/kGNqWefva2s/lc+qDY5hNN99mJVe0to0bV WIYj2Gp2dQXu5bRcdAlBu+sxzqk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b23fdb4.7ff05a7f6810-smtp-out-n02; Fri, 15 Jun 2018 17:56:04 -0000 (UTC) Date: Fri, 15 Jun 2018 10:56:03 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b23fdb3c28c6_5652ad87b03fc04484fb@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 8115e0: Martin's feedback Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b23fdb3c2464_5652ad87b03fc044837a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 17:56:08 -0000 ----==_mimepart_5b23fdb3c2464_5652ad87b03fc044837a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http/grease Home: https://github.com/quicwg/base-drafts Commit: 8115e0bd2e03ab11ff42e78d39b016688ac73c79 https://github.com/quicwg/base-drafts/commit/8115e0bd2e03ab11ff42e78d39b016688ac73c79 Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Martin's feedback Commit: f8b89904b6a1794713d885d0c8de4ea009e85acd https://github.com/quicwg/base-drafts/commit/f8b89904b6a1794713d885d0c8de4ea009e85acd Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Grease section header Compare: https://github.com/quicwg/base-drafts/compare/f5fd0135c5b8...f8b89904b6a1 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b23fdb3c2464_5652ad87b03fc044837a-- From nobody Fri Jun 15 10:56:16 2018 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 40F1D130E7A for ; Fri, 15 Jun 2018 10:56:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 phYA4cMhC3A3 for ; Fri, 15 Jun 2018 10:56:09 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 8341C124D68 for ; Fri, 15 Jun 2018 10:56:09 -0700 (PDT) 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=XyBRL9uCRmapZIYSmDtBNiIxVr0=; b=ezHd627ct0Cwwfro qjVcHDWLE5o7uRyrqc9J/1BNT2LI6fZlthkN3YazMWVBmVn7ALkcXVriyklMGc+w lVs/WQgZhTphm0LRROehsjDZ5UpjA3hpGjP+deUXcEQA0F0XLQu/WalbRfpEz7T1 bKeGqJ9upupk9l5eeoift93Ao6k= Received: by filter0035p1iad2.sendgrid.net with SMTP id filter0035p1iad2-14059-5B23FDB8-4 2018-06-15 17:56:08.300337251 +0000 UTC Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id mwPpZShARvCR82ZA6OA9Cw for ; Fri, 15 Jun 2018 17:56:08.333 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id 543D6A8149F for ; Fri, 15 Jun 2018 10:56:08 -0700 (PDT) Date: Fri, 15 Jun 2018 17:56:08 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fdb852b71_296a2b1810294f5c18984c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak28JLUT1xC0bIk1Ecn/wqjWN0HtTnXZTflWaJ bHbeaUoViaQiQbmSheKs+JmHOgxCxaqh9+m3sFZ4Zahb0Z2+CsvlLJ1j6ha+h82Xe/X1wFDgR8Hxo1 4EVRRUAfvZf1asg1bo2PSGNTcXfA+zTao5WMLauwAV5t7K7vEqzJoiyP/PcfPnESaIyd7xLbsqJPzU 0= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 17:56:12 -0000 ----==_mimepart_5b23fdb852b71_296a2b1810294f5c18984c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 2 commits. 8115e0b Martin's feedback f8b8990 Grease section header -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1446/files/f5fd0135c5b8e10db6c5313304dcdb3232d93ca6..f8b89904b6a1794713d885d0c8de4ea009e85acd ----==_mimepart_5b23fdb852b71_296a2b1810294f5c18984c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 2 commits.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b23fdb852b71_296a2b1810294f5c18984c-- From nobody Fri Jun 15 10:57:32 2018 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 2268E130E37 for ; Fri, 15 Jun 2018 10:57:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fPNkCPh5Ro0n for ; Fri, 15 Jun 2018 10:57:28 -0700 (PDT) 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 0EE2D12F18C for ; Fri, 15 Jun 2018 10:57:28 -0700 (PDT) Date: Fri, 15 Jun 2018 10:57:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529085447; bh=1Nl0/rT/WICdviYiOJbFvgfoiVLWe3g3M5Vbdv3RdU8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZPOcTgxHVskjYhHPuWMakCgvTIQH3mrq/W+z+Q0JI5gI16ns/t0ZNmF3MvLaq7RTB mus+ES1w0a0GOYev4qXmb1IIEHj1HLcAIfUfr0qxybIQmtT5rcp3u6PA71UGfv6I/S /1VHTu0gKemxExY3lnd/Yiv54O24VHa5Qe7GWOZs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23fe074c5a3_33a93fc8b899af782501d9"; 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.26 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: Fri, 15 Jun 2018 17:57:31 -0000 ----==_mimepart_5b23fe074c5a3_33a93fc8b899af782501d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue, that can't be in this PR without taking a dependency on the other. If this lands first, I'll add it to #1359; if the other lands first, I'll expand this one; if they land mostly-together, it'll be a follow-up. -- 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/1446#issuecomment-397697816 ----==_mimepart_5b23fe074c5a3_33a93fc8b899af782501d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue, that can't be in this PR without taking a dependency on the other. If this lands first, I'll add it to #1359; if the other lands first, I'll expand this one; if they land mostly-together, it'll be a follow-up.

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

----==_mimepart_5b23fe074c5a3_33a93fc8b899af782501d9-- From nobody Fri Jun 15 11:05:06 2018 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 CEEB912F18C for ; Fri, 15 Jun 2018 11:05:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 IcWewzr0G0ms for ; Fri, 15 Jun 2018 11:05:02 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE1C130DBE for ; Fri, 15 Jun 2018 11:05:00 -0700 (PDT) Date: Fri, 15 Jun 2018 11:05:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529085900; bh=02yCBXnqdu8b+c4yfVQit8ElZS0VJRRuva68y0uE5us=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ySl7+OovJj6XZYxIS4qPXK0Jrs7eQFWmI65YJkIDUbkYz9pZJZXPXHH+JICo0h0Oj Mrnn0pTQRaYainRkpWthJfP2s5fLSLF5EXJQPulFvZdZo+5Eoxjq9qrxYdk2o/3Twn 8f7eInUueAbjfnV9k5KoAfDvfWSKieYsWHOab7YQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Expand CID ratchet text (#1453) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b23ffcc2223a_39d73fa037908f78295d0"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 18:05:04 -0000 ----==_mimepart_5b23ffcc2223a_39d73fa037908f78295d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -1857,13 +1857,20 @@ congestion state (see {{migration-cc}}), so the port SHOULD only be changed infrequently. An endpoint that receives a successfully authenticated packet with a previously -unused connection ID MUST use the next available connection ID for any packets -it sends to that address. To avoid changing connection IDs multiple times when +unused connection ID MUST use a new connection ID for any future packets it +sends to that address. To avoid changing connection IDs multiple times when Isn't the point of this PR to cover the case you describe in the issue? That is, you need to say "unless it is likely that the peer changed its connection ID in response to the endpoint changing." Or something like that. I don't know how to implement that other than to block switches when you change, unless there is a path change. This is tricky. -- 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/1453#pullrequestreview-129267698 ----==_mimepart_5b23ffcc2223a_39d73fa037908f78295d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1857,13 +1857,20 @@ congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
 An endpoint that receives a successfully authenticated packet with a previously
-unused connection ID MUST use the next available connection ID for any packets
-it sends to that address.  To avoid changing connection IDs multiple times when
+unused connection ID MUST use a new connection ID for any future packets it
+sends to that address.  To avoid changing connection IDs multiple times when

Isn't the point of this PR to cover the case you describe in the issue? That is, you need to say "unless it is likely that the peer changed its connection ID in response to the endpoint changing." Or something like that. I don't know how to implement that other than to block switches when you change, unless there is a path change. This is tricky.

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

----==_mimepart_5b23ffcc2223a_39d73fa037908f78295d0-- From nobody Fri Jun 15 11:06:34 2018 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 979F1130F39 for ; Fri, 15 Jun 2018 11:06:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 5RRiVISO5mnJ for ; Fri, 15 Jun 2018 11:06:22 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 668BA130FAC for ; Fri, 15 Jun 2018 11:06:22 -0700 (PDT) Date: Fri, 15 Jun 2018 11:06:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529085981; bh=I5Vb+PM0otzbmCrXece4ELaijx00+bCxWUW1N81KR8c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fKW9o/rOQpeERLpDc2LafcEjEtp08yIE1ufN/8yPHcNAaI7Rw370/n3HEVHLWXfqW G+JVNE0W40c4pq0eeaCdwFNI7Frp7FhyuJTkiNWP1b65iYOfmCaQRfzVBbv5ysDf3P K15zL+PxiUaMZxv2yma7Ye6eg2EphbHdfBQKafk0= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24001dbe662_51223fe418508f8410073b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 15 Jun 2018 18:06:32 -0000 ----==_mimepart_5b24001dbe662_51223fe418508f8410073b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. Some small comments. > If 0-RTT is possible, it is ready after the client sends a TLS ClientHello message or the server receives that message. After providing a QUIC client with -the first handshake octets, the TLS stack might signal that 0-RTT keys are -ready. On the server, after receiving handshake octets that contain a +the first handshake octets, the TLS stack might signal the change to the +the 0-RTT keys. On the server, after receiving handshake octets that contain a `the` is included twice here. > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; +Section 4.4.3). Finally, because ACKs of Handshake packets +are authenticated, a blind attacker cannot forge them Missing a `.` after "forge them". > + +#### Tokens + +If the client has a suitable token available from a previous connection, +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID to +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated I feel this `SHOULD` needs to be a `MUST`. If QUIC is support independent DDoS protection devices in path, then the QUIC server cannot drop Initial packets with tokens it doesn't understand. -- 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/1450#pullrequestreview-129252601 ----==_mimepart_5b24001dbe662_51223fe418508f8410073b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

Some small comments.

In draft-ietf-quic-tls.md:

>  If 0-RTT is possible, it is ready after the client sends a TLS ClientHello
 message or the server receives that message.  After providing a QUIC client with
-the first handshake octets, the TLS stack might signal that 0-RTT keys are
-ready.  On the server, after receiving handshake octets that contain a
+the first handshake octets, the TLS stack might signal the change to the
+the 0-RTT keys. On the server, after receiving handshake octets that contain a

the is included twice here.

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};
+Section 4.4.3). Finally, because ACKs of Handshake packets
+are authenticated, a blind attacker cannot forge them

Missing a . after "forge them".

In draft-ietf-quic-transport.md:

> +
+#### Tokens
+
+If the client has a suitable token available from a previous connection,
+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID to
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated

I feel this SHOULD needs to be a MUST. If QUIC is support independent DDoS protection devices in path, then the QUIC server cannot drop Initial packets with tokens it doesn't understand.

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

----==_mimepart_5b24001dbe662_51223fe418508f8410073b-- From nobody Fri Jun 15 11:25:31 2018 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 D2B6B12F18C for ; Fri, 15 Jun 2018 11:25:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 AYjkzJAdNp8y for ; Fri, 15 Jun 2018 11:25:25 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 455BB130E69 for ; Fri, 15 Jun 2018 11:25:25 -0700 (PDT) Date: Fri, 15 Jun 2018 11:25:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529087124; bh=YimPbUSCInK4DiF1u0L34xl4dtLTQAfikfG7qMOYw2Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tHnxpkyiz3Pvfg8xCKJ3HEReny2k0OVe0OYutUCORHKoNKo3fbXHBKlrVqbwX/E0m KxXqpJIMFnA/6ucIK0TWgfEQLieoMNhO39VU+MdqkuQDweGNONRCAf63Q0GJuglXWp ISh9+zv3v/voRAFqNwMVe8Bf8tN71u1G0BdRu3UQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24049483bbc_1a952b2146860f505092d"; 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.26 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: Fri, 15 Jun 2018 18:25:29 -0000 ----==_mimepart_5b24049483bbc_1a952b2146860f505092d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > ~~~~~~~~~~ -{:#fig-size-sync title="Table Size Synchronize"} +{:#fig-size-sync title="Table State Synchronize"} + +A decoder SHOULD emit a Table State Synchronize after receiving new dynamic +table entries if the most recently inserted entry was not the Largest Reference Works for me. -- 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/1410#discussion_r195826783 ----==_mimepart_5b24049483bbc_1a952b2146860f505092d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-qpack.md:

>  ~~~~~~~~~~
-{:#fig-size-sync title="Table Size Synchronize"}
+{:#fig-size-sync title="Table State Synchronize"}
+
+A decoder SHOULD emit a Table State Synchronize after receiving new dynamic
+table entries if the most recently inserted entry was not the Largest Reference

Works for me.

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

----==_mimepart_5b24049483bbc_1a952b2146860f505092d-- From nobody Fri Jun 15 11:25:39 2018 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 86F93130EF9 for ; Fri, 15 Jun 2018 11:25:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 Zayb4TUHlM9q for ; Fri, 15 Jun 2018 11:25:31 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 B03DA12F18C for ; Fri, 15 Jun 2018 11:25:31 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529087131; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=g7EgHaMBcmfxJKJ3TqqgkM3ZgP+IEAuBbgozPPMfJB0=; b=syjLMd+yKC015AtnirauR1YdGisORg/Gh2jG5MU765vvCPFWNEKfcsEY6OfcoDnNin2lN3GM Q8D1gkJ9SA0e85NVlGH8RtcaLUHIcXE3DdfneJP9LoLyeXBCVnnTsjCm3WpFAJEU7nlByplU Hl/WMG78Ly8AwnxffIYZ0pvbbtc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b24049b.7f87c7b62ea0-smtp-out-n03; Fri, 15 Jun 2018 18:25:31 -0000 (UTC) Date: Fri, 15 Jun 2018 11:25:30 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b24049ad21a_3002aabe75c1c1091c3@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 93aadb: Alan's text Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b24049ace61_3002aabe75c1c109010"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 18:25:34 -0000 ----==_mimepart_5b24049ace61_3002aabe75c1c109010 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts Commit: 93aadb7e0f356d8e595db9e2cffd15504b13f86e https://github.com/quicwg/base-drafts/commit/93aadb7e0f356d8e595db9e2cffd15504b13f86e Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Alan's text **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b24049ace61_3002aabe75c1c109010-- From nobody Fri Jun 15 11:25:45 2018 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 2975612F18C for ; Fri, 15 Jun 2018 11:25:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uW023j7lYHLb for ; Fri, 15 Jun 2018 11:25:34 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA327130E4F for ; Fri, 15 Jun 2018 11:25:34 -0700 (PDT) Date: Fri, 15 Jun 2018 11:25:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529087133; bh=VsLS0dDyBukHkY6xENsavSUDJ5paZJe1STETGrLx8sI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=udbNowEv3TIadCCYmRg+T5usfPWLFKt1Ao4x5SO1JJHm9isEVVKYEj8x+q/lYdg1u FsQjeLl4eCMNjQhsq6MSsy7FMO6enli73pCqigiPqWpAbbNKghi75/Iuc/KPbwjnw5 VQYod40WTuqCx/4nrqNI4Aw2KbKMfewAXNt8/g6Q= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24049dd08a0_1a9c2b2146860f505663b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 15 Jun 2018 18:25:37 -0000 ----==_mimepart_5b24049dd08a0_1a9c2b2146860f505663b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 93aadb7 Alan's text -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1410/files/b4ed7e487dd2c0d828f0f4422bd5044ab195674d..93aadb7e0f356d8e595db9e2cffd15504b13f86e ----==_mimepart_5b24049dd08a0_1a9c2b2146860f505663b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b24049dd08a0_1a9c2b2146860f505663b-- From nobody Fri Jun 15 11:29:33 2018 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 DB7F2130DBE for ; Fri, 15 Jun 2018 11:29:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Y_B0ZHo0ABuZ for ; Fri, 15 Jun 2018 11:29:21 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14B3B130F05 for ; Fri, 15 Jun 2018 11:29:21 -0700 (PDT) Date: Fri, 15 Jun 2018 11:29:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529087360; bh=WXimYSFLwZIdHOwOefaovjmQML+bHWNubgYIz5Hy6lo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Zpr6HQOyku+aIaWlP6r2LJhDwr4b/FpOlSuxzvn7KilvmkOunnWGPf9RScyIWGhBr e9vD01LeRvOXMTxNs7TqX8w3YdgjkMQnYggNo46VRAVrCKuObwUfRESDNmmBPtP7RD VF7S6x5QolJEJdxTzY9kJ4V6tyMTrDDjawbx4n1Y= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Expand CID ratchet text (#1453) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24058035bff_76752ab824ebcf601201fe"; 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.26 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: Fri, 15 Jun 2018 18:29:32 -0000 ----==_mimepart_5b24058035bff_76752ab824ebcf601201fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -1857,13 +1857,20 @@ congestion state (see {{migration-cc}}), so the port SHOULD only be changed infrequently. An endpoint that receives a successfully authenticated packet with a previously -unused connection ID MUST use the next available connection ID for any packets -it sends to that address. To avoid changing connection IDs multiple times when +unused connection ID MUST use a new connection ID for any future packets it +sends to that address. To avoid changing connection IDs multiple times when The point of the PR grew as I worked on it. :-) Initially, it was to replace "the next available" with "a new" now that sequence numbers are gone. Then, while I was at it, I decided to pick up #1276 (what happens if you're out of CIDs?). But then I ran into the fact that the existing text will lead you into that spiral. -- 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/1453#discussion_r195827758 ----==_mimepart_5b24058035bff_76752ab824ebcf601201fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1857,13 +1857,20 @@ congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
 An endpoint that receives a successfully authenticated packet with a previously
-unused connection ID MUST use the next available connection ID for any packets
-it sends to that address.  To avoid changing connection IDs multiple times when
+unused connection ID MUST use a new connection ID for any future packets it
+sends to that address.  To avoid changing connection IDs multiple times when

The point of the PR grew as I worked on it. :-) Initially, it was to replace "the next available" with "a new" now that sequence numbers are gone. Then, while I was at it, I decided to pick up #1276 (what happens if you're out of CIDs?). But then I ran into the fact that the existing text will lead you into that spiral.

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

----==_mimepart_5b24058035bff_76752ab824ebcf601201fe-- From nobody Fri Jun 15 11:49:22 2018 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 A35DA130E4B for ; Fri, 15 Jun 2018 11:49:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 eC3H3cyeZVqo for ; Fri, 15 Jun 2018 11:49:17 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 5705B130DBE for ; Fri, 15 Jun 2018 11:49:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529088556; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=neYzp2BVQyPvQBdV5SbaHe9OtoV4sAWPLBcKBTI9UyM=; b=Fbdc832lBzAiysolTE2tkdRq9SfyM80PE/B7mTs4Gy3f6oz/RIn8/Mzwiz5AGHBMWwfWioC7 1Nr2aXdRMxjGsqimPcFQmaLSLxPJmlaFcEuS85qC0YBj7ffmSfq2KiF8P32QY22EYz0NYfiZ sLlJYhzPRyoibLzbF6g9x9IVDV4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b240a2c.7fab8abc6fc0-smtp-out-n03; Fri, 15 Jun 2018 18:49:16 -0000 (UTC) Date: Fri, 15 Jun 2018 11:49:15 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b240a2bb82f3_56602ac89706fc18110665@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 031f07: Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b240a2bb7c81_56602ac89706fc18110517"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 15 Jun 2018 18:49:20 -0000 ----==_mimepart_5b240a2bb7c81_56602ac89706fc18110517 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 031f07f40bf91b8d13f0a766cf22fcc10e7e5cec https://github.com/quicwg/base-drafts/commit/031f07f40bf91b8d13f0a766cf22fcc10e7e5cec Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Describe QPACK Feedback mechanisms (#1410) * Implicit acknowledgment via header block acknowledgment Closes #1370. * Make TSS incremental to Header Acknowledgment as well * A start, but not an end * State sync, not size sync * Acknowledge stream resets too Closes #1371. * Fix figure * Genericize * Plural, not plural * Editorial * Itsan instruction * QPACK Feedback with forward references * Alan's text **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b240a2bb7c81_56602ac89706fc18110517-- From nobody Fri Jun 15 11:49:33 2018 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 F2277130DBE for ; Fri, 15 Jun 2018 11:49:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 cgJNC-zD1eFR for ; Fri, 15 Jun 2018 11:49:20 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52370130E4D for ; Fri, 15 Jun 2018 11:49:20 -0700 (PDT) Date: Fri, 15 Jun 2018 11:49:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529088559; bh=j5wu8wWtz1EVMMBK9HpMVM0yN9d07A7JhTga2tK4zU4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ucAFBFZ+THiktB6cpTzqnwusUGEivb1Wmyo5STNd5yXsPbAoDGfoRKxyw2c6/knf8 NpCHeV/FCw7o0XreoubWjWSOXWafsxxp0C1c2VFFcbT60ipb0UYgb5qrZ9l0nSZ/F2 YxiQGaqRJMgKvs+f6c7WUBWl+UR3p/4y3wWiSHBA= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment via header block acknowledgment (#1399) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b240a2f81706_4f63ff70e0bef88840bd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 18:49:23 -0000 ----==_mimepart_5b240a2f81706_4f63ff70e0bef88840bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1399 via #1410. -- 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/1399#event-1684058128 ----==_mimepart_5b240a2f81706_4f63ff70e0bef88840bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1399 via #1410.

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

----==_mimepart_5b240a2f81706_4f63ff70e0bef88840bd-- From nobody Fri Jun 15 11:49:37 2018 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 F0ABB130E64 for ; Fri, 15 Jun 2018 11:49:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 YRytAINU0PUB for ; Fri, 15 Jun 2018 11:49:21 -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 6758E130E4F for ; Fri, 15 Jun 2018 11:49:20 -0700 (PDT) Date: Fri, 15 Jun 2018 11:49:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529088559; bh=u13zxjLR/olnDYcpKDwRZeNZKEwWhmblmfGl3ezjBA4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lKM5dpRvCNEulq+sQfGex4luZOebvYu8csLUVnhCAI1FFrwUIAv+nDsR3kOmGDAK8 /wGd6MuJbMdatYt6mxKmN3vwi0+KwBoAUHgzssI7xCylffJSXUepo3gu0+tpwpOpsc AqD4Nzfo4bpVzS9Hp6N9T1Du7WfKWXejcCZHdK+A= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Describe QPACK Feedback mechanisms (#1410) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b240a2f9aba1_64732ad3fdc44f5433818"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 18:49:24 -0000 ----==_mimepart_5b240a2f9aba1_64732ad3fdc44f5433818 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1410. -- 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/1410#event-1684058120 ----==_mimepart_5b240a2f9aba1_64732ad3fdc44f5433818 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1410.

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

----==_mimepart_5b240a2f9aba1_64732ad3fdc44f5433818-- From nobody Fri Jun 15 11:49:42 2018 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 A3086130E5D for ; Fri, 15 Jun 2018 11:49:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 dW3jybD8FVR5 for ; Fri, 15 Jun 2018 11:49:22 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 2627A130E4B for ; Fri, 15 Jun 2018 11:49:21 -0700 (PDT) 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=XE7HbiQhFNo8/85jjaUSJXSoBrw=; b=KRmCufHooE9DLw45 sp1zOzHklY3JyWllja7vP1TFPPjqO3OCblzUTDkbDupYkter0I9lNuijA/LBAda2 vZhLpDdonlezO2oFYVPkeTdhykPA/aaMXtKxzXcuf+GFmK0SSwuSuS66j5stX+Qr UigsxJfKgX4vm/f+l7h3NlkfxSI= Received: by filter1077p1las1.sendgrid.net with SMTP id filter1077p1las1-25010-5B240A2F-34 2018-06-15 18:49:19.924335852 +0000 UTC Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0010p1iad2.sendgrid.net (SG) with ESMTP id mo5aUzeHTJWQ1hPeFkz7JA for ; Fri, 15 Jun 2018 18:49:19.839 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id CAADBC0171 for ; Fri, 15 Jun 2018 11:49:19 -0700 (PDT) Date: Fri, 15 Jun 2018 18:49:20 +0000 (UTC) From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Acknowledge stream resets too (#1400) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b240a2fc8f37_73232af654326f5c20018"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3sIdRHL2/VEv18fvzObWfHCXidwYhGGchLce kC36LnsysMdrSTbAepga7mXqe1gYevSp3uocSxIBzRvGo003jGCCTgxJuzb9dWKocRnsW29cqNRPYg nKtDtTA1kfeZWIkJlA6kVqM8iDGRIzEUPOKYTWRUwYYcltT4TmJT4PDIQw== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 18:49:24 -0000 ----==_mimepart_5b240a2fc8f37_73232af654326f5c20018 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1400 via #1410. -- 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/1400#event-1684058132 ----==_mimepart_5b240a2fc8f37_73232af654326f5c20018 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1400 via #1410.

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

----==_mimepart_5b240a2fc8f37_73232af654326f5c20018-- From nobody Fri Jun 15 11:49:48 2018 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 7A566130E4B for ; Fri, 15 Jun 2018 11:49:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Ms1FCAAq4GbP for ; Fri, 15 Jun 2018 11:49:24 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3D5C130E52 for ; Fri, 15 Jun 2018 11:49:23 -0700 (PDT) Date: Fri, 15 Jun 2018 11:49:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529088563; bh=PRk7V/uRbS8NW/+UE6WXZyX1vptSy26r5i+njhvli2M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vEVWAKv0xyb08yqWuOXml/NaUHOGLT3HxXEDeIsKJtWGug5WmAjTVUnPEd/QeW6+f Zq2bZNJjHxl6t557qxnyqzSNbMVuvqR5nSRi/YD9JOJi2+r1BLNIukiBcdupI+CRbc /C82Nc1zf77WHAe2qVETjIQpVMdlT5pDAZRa3wKo= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Tracking of header blocks for reset streams (#1371) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b240a334b40b_4ff73fcfa3100f88335df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 18:49:26 -0000 ----==_mimepart_5b240a334b40b_4ff73fcfa3100f88335df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1371 via 031f07f40bf91b8d13f0a766cf22fcc10e7e5cec. -- 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/1371#event-1684058241 ----==_mimepart_5b240a334b40b_4ff73fcfa3100f88335df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1371 via 031f07f.

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

----==_mimepart_5b240a334b40b_4ff73fcfa3100f88335df-- From nobody Fri Jun 15 11:49:55 2018 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 02119130E4D for ; Fri, 15 Jun 2018 11:49:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Cf6B2TfFjTF8 for ; Fri, 15 Jun 2018 11:49:24 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15C4F130E62 for ; Fri, 15 Jun 2018 11:49:24 -0700 (PDT) Date: Fri, 15 Jun 2018 11:49:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529088563; bh=RACzwGMnsG/tm0S0+RWMlDmr1GmEOjPkR/AVrWCORFI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mSNUTN4dwlUer90UtxK5VxBXfvo+xRb395FR9LC4lBE0yH+9KojEQr6eGqXx/kvwe cZnoxMhs0aZrX3NMgg8lXeHjM+O9cd6lkJUcNsJ6U94KH0ZuwHluEFbM+4yifeLXoE ZTk3+VWlzzJGPLVZL1nnTD48byi2xl45PGSbU+HY= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicitly acknowledging table updates by acknowleding header blocks (#1370) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b240a3370ef9_4fcd3fcfa3100f882948e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 18:49:26 -0000 ----==_mimepart_5b240a3370ef9_4fcd3fcfa3100f882948e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1370 via 031f07f40bf91b8d13f0a766cf22fcc10e7e5cec. -- 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/1370#event-1684058235 ----==_mimepart_5b240a3370ef9_4fcd3fcfa3100f882948e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1370 via 031f07f.

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

----==_mimepart_5b240a3370ef9_4fcd3fcfa3100f882948e-- From nobody Fri Jun 15 15:01:09 2018 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 8C8CE130E59 for ; Fri, 15 Jun 2018 15:01:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, 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 ye_X-A01OLht for ; Fri, 15 Jun 2018 15:01:02 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 1591E130E7C for ; Fri, 15 Jun 2018 15:01:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Jrs38GEfNK2OFAyDjmAaZfMR/os=; b=eF0MZ1JFMrwH/I9y vg6Mpve6tbIY34wibGl6PLduB9NdB1+zDHVS7BU5/1+X6PbovTBmV2zAZJevL4Kc no2CKiCYuJ38CM5iR4Fs7CN/R+V1jIzLu9YBaK8Q3NuYXfHeXrVHMlbAOKEpsyJi Evdx7VG7uYDGOdwdjKisSPPzNRs= Received: by filter1029p1las1.sendgrid.net with SMTP id filter1029p1las1-32340-5B24371C-1F 2018-06-15 22:01:00.862119641 +0000 UTC Received: from github-lowworker11-cp1-prd.iad.github.net (unknown [192.30.252.35]) by ismtpd0017p1iad2.sendgrid.net (SG) with ESMTP id nQOs5sXtQoOLO1YybMYndg for ; Fri, 15 Jun 2018 22:01:00.848 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker11-cp1-prd.iad.github.net (Postfix) with ESMTP id AD05CE0FB5 for ; Fri, 15 Jun 2018 15:01:00 -0700 (PDT) Date: Fri, 15 Jun 2018 22:01:01 +0000 (UTC) From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] QPACK could use some examples (#1454) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24371cab998_6ddb3fd58cdd4f7c1134dd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0I4Dnc4gEJmUBlMP6+Z0rrJkd2S1HULKUR0f rFQxKgewOu6FSgYit5WaFI2gxTAWNXyoITqANVcjxKo7XTYhvAoSPpj/XWVw8hSjYoX8k8rI23UYl6 PcxwWae+Ta1i7wtlHMeGujZGwdhpJvrjOmby+qCNnEzWUUSC3h6eGFiD2A== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 22:01:08 -0000 ----==_mimepart_5b24371cab998_6ddb3fd58cdd4f7c1134dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From an external researcher hoping to build an implementation: "The HPACK RFC authors made a wise choice to include several carefully crafted examples. I managed to create a HPACK implementation and to verify it using those examples. A similar list of examples could be considered for QPACK to make it easy to verify QPACK implementations. However, QPACK has some extra signaling, meaning constructing the examples list may not be as easy as it is for HPACK." -- 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/1454 ----==_mimepart_5b24371cab998_6ddb3fd58cdd4f7c1134dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

From an external researcher hoping to build an implementation:

"The HPACK RFC authors made a wise choice to include several carefully crafted examples. I managed to create a HPACK implementation and to verify it using those examples. A similar list of examples could be considered for QPACK to make it easy to verify QPACK implementations. However, QPACK has some extra signaling, meaning constructing the examples list may not be as easy as it is for HPACK."

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

----==_mimepart_5b24371cab998_6ddb3fd58cdd4f7c1134dd-- From nobody Fri Jun 15 15:04:48 2018 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 91169130E6F for ; Fri, 15 Jun 2018 15:04:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 co3KFCBCZk9z for ; Fri, 15 Jun 2018 15:04:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8203130E59 for ; Fri, 15 Jun 2018 15:04:44 -0700 (PDT) Date: Fri, 15 Jun 2018 15:04:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529100283; bh=N1EnfJMz3lIwgkd3+9r3goETzFRhPg/7Nv7rNU+ScD4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=MEQ2oNUp9xivmkmOAzqrlEKSfPUnE4jCyO1eL8g3hJPIgEPytBRcsaQ6G9QcGCH0E 36X04f3Del1GrYVXeVDHjEzoUl7J1qFxhz6EbUcGldN7Ls/D1/YkriOm0V4TobdSsD q5JzdWM8QR78TbcYRdjf9GkY45Sx3fPPm1ZowFEk= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] QPACK sample encoder bug (#1455) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2437fb1507d_12353f9796914f84155082"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 22:04:47 -0000 ----==_mimepart_5b2437fb1507d_12353f9796914f84155082 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ``` delta = largestReference - baseIndex sign = delta > 0 ? 0x80 : 0 encodeInteger(prefixBuffer, sign, delta, 7) ``` encodeInteger is meant to be an HPACK integer encoder, which cannot encode negative numbers. It should be `encodeInteger(prefixBuffer, sign, abs(delta), 7)` Another option is to use a more explicit conditional: ``` if baseIndex >= largestReference: encodeInteger(prefixBuffer, 0, baseIndex - largestReference, 7) else: encodeInteger(prefixBuffer, 0x80, largestReference - baseIndex, 7) ``` -- 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/1455 ----==_mimepart_5b2437fb1507d_12353f9796914f84155082 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 
delta = largestReference - baseIndex
sign = delta > 0 ? 0x80 : 0
encodeInteger(prefixBuffer, sign, delta, 7)

encodeInteger is meant to be an HPACK integer encoder, which cannot encode negative numbers. It should be

encodeInteger(prefixBuffer, sign, abs(delta), 7)

Another option is to use a more explicit conditional:

if baseIndex >= largestReference:
  encodeInteger(prefixBuffer, 0, baseIndex - largestReference, 7)
else:
  encodeInteger(prefixBuffer, 0x80, largestReference  - baseIndex, 7)

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

----==_mimepart_5b2437fb1507d_12353f9796914f84155082-- From nobody Fri Jun 15 15:04:56 2018 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 1EB7B130E81 for ; Fri, 15 Jun 2018 15:04:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 iiizxoB0doQc for ; Fri, 15 Jun 2018 15:04:48 -0700 (PDT) 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 3D5BC130E59 for ; Fri, 15 Jun 2018 15:04:48 -0700 (PDT) Date: Fri, 15 Jun 2018 15:04:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529100287; bh=qLcX7QdaLpaEbjJjbx39orR6UV3WoN86AXedBO5XVz4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KeRwdbOU55F8NQzik9guiyyqoYp1Ggz8BSApqma+kHIXtndn6Ap8Y4RqPntB22/0Y 8VE+TTELMnJ0VO4zs933X6b+rK3IoE7c9L2zcwboFhTqZgVEO6ccBwzF90tvlF3h25 a9stA9b6kYU0dgDQ1OhDUQ4ekzyGvMOJoLNBaAUI= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK could use some examples (#1454) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2437ff46e60_79be3fbc1983af801654ef"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 15 Jun 2018 22:04:51 -0000 ----==_mimepart_5b2437ff46e60_79be3fbc1983af801654ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That is good feedback. Examples are non-normative, so one angle is to provide test vectors (outside of documentation) that helps implementers -- 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/1454#issuecomment-397753884 ----==_mimepart_5b2437ff46e60_79be3fbc1983af801654ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

That is good feedback. Examples are non-normative, so one angle is to provide test vectors (outside of documentation) that helps implementers

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

----==_mimepart_5b2437ff46e60_79be3fbc1983af801654ef-- From nobody Fri Jun 15 15:06:23 2018 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 C7CA1130E71 for ; Fri, 15 Jun 2018 15:06:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lmMpmBtJ3mDl for ; Fri, 15 Jun 2018 15:06:20 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ABDA130E59 for ; Fri, 15 Jun 2018 15:06:20 -0700 (PDT) Date: Fri, 15 Jun 2018 15:06:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529100379; bh=2N46LY8Rz4lxuLkXwXQWprrJ+BY9hdH1deeeomw2HGQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jsHUWahu1CGQX6iGhwDwm4nw7PZ94SIPSFLOU56+g0SAVkNeU8lVM4ObXPO5OUNvl uLF6mPWToks9qaregXEJOrxs0QG0MZeeAJgHybKfF2Ep6JUtf2fl0tOnxE5WfLm7M8 bfuL8KUtzulM0QtIkX81yg5UXDHU+jaWZK93ybtM= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK could use some examples (#1454) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b24385b8d893_6dc63fd58cdd4f7c688b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 15 Jun 2018 22:06:22 -0000 ----==_mimepart_5b24385b8d893_6dc63fd58cdd4f7c688b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit See also: https://github.com/quicwg/base-drafts/wiki/QPACK-Offline-Interop I'm planning to put up some sample HAR files and their QPACK encodings under various params and assumptions. -- 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/1454#issuecomment-397754143 ----==_mimepart_5b24385b8d893_6dc63fd58cdd4f7c688b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

See also: https://github.com/quicwg/base-drafts/wiki/QPACK-Offline-Interop

I'm planning to put up some sample HAR files and their QPACK encodings under various params and assumptions.

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

----==_mimepart_5b24385b8d893_6dc63fd58cdd4f7c688b7-- From nobody Sun Jun 17 03:27:18 2018 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 9A85D130EB4 for ; Sun, 17 Jun 2018 03:27:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 sX9x692zEfpC for ; Sun, 17 Jun 2018 03:27:15 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E931130EA3 for ; Sun, 17 Jun 2018 03:27:15 -0700 (PDT) Date: Sun, 17 Jun 2018 03:27:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529231234; bh=NHu5PHUvEw8oq+D1itbTmhbr7gJ/Fz9mcK7OiB13seg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fy6WPAE3E3X6BsY98rAzBj9aytuDwWT+P9//eR1ogqFnYj1aSPlmH/ZiXG+5B/cwU 5ojmFUxBNrKe6lDK36UMUfeXqmmcN7J/IQdpVQMT9WxV3/NQZEQd/17LN8Ok481O1F IuFhggdeZWXgnK8wbmYRqkuTRXbdRJIy6oUSSpNE= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] wrong MSS value in congestion avoidance phase (#1102) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b26378249a48_a442aeaa6058f5065907d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair 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.26 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: Sun, 17 Jun 2018 10:27:17 -0000 ----==_mimepart_5b26378249a48_a442aeaa6058f5065907d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Seems correct to take the Min. And this is consistent with what dplpmtud expects. Gorry -- 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/1102#issuecomment-397869356 ----==_mimepart_5b26378249a48_a442aeaa6058f5065907d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Seems correct to take the Min. And this is consistent with what dplpmtud expects.

Gorry

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

----==_mimepart_5b26378249a48_a442aeaa6058f5065907d-- From nobody Sun Jun 17 03:40:49 2018 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 B7BB0130EB8 for ; Sun, 17 Jun 2018 03:40:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6fkuE7qrbq02 for ; Sun, 17 Jun 2018 03:40:46 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B024130E2A for ; Sun, 17 Jun 2018 03:40:46 -0700 (PDT) Date: Sun, 17 Jun 2018 03:40:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529232045; bh=tYLkx0h1PeShVb6oEW96U0hN5eFI5c/PDilKq1k+f3U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LZYuXRRo9Naav8I57MtXwH9mxgwEwCxnC5eAuh8UXlfP+7z5rPMjrlQ//e/jxc0mW ve0Rh+Qawrv7/bWoeqrqo9jOnwpVN9yizCUOjWcsw+gRI97ikOyQvd1oV2nyT+eZcW tvkbng5FpyaWuohXS+0jVfWZhA3pHOmSE65gQtp4= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b263aad196cc_15773fbd1c55cf8020096e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair 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.26 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: Sun, 17 Jun 2018 10:40:48 -0000 ----==_mimepart_5b263aad196cc_15773fbd1c55cf8020096e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Maybe it is worth identifying this design consideration in dplpmtud - some of this is generic to working with icmp with any cooperating middle-boxes -- 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/1243#issuecomment-397869951 ----==_mimepart_5b263aad196cc_15773fbd1c55cf8020096e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Maybe it is worth identifying this design consideration in dplpmtud - some of this is generic to working with icmp with any cooperating middle-boxes

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

----==_mimepart_5b263aad196cc_15773fbd1c55cf8020096e-- From nobody Sun Jun 17 23:16:47 2018 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 70527130DE6 for ; Sun, 17 Jun 2018 23:16:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OHQaZ0p0ykjc for ; Sun, 17 Jun 2018 23:16:43 -0700 (PDT) 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 B545E127598 for ; Sun, 17 Jun 2018 23:16:43 -0700 (PDT) Date: Sun, 17 Jun 2018 23:16:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529302601; bh=WlZsGUk3Hm7IZJyztx2XAG/mDgCr6tOF+OZP15XmVTE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NJWKbbqpzcMrv8WBgul6cOnh9C+uZcHU/5FZqA18rr8dYC5jJP5iEvdPg5Ea7MZBl QzRsHXi0wjYMmJoBhmmXdh3U4G5hOycZgBgOB41xJxcWS+VGhHCIFg10hhAH8n+HWq HSNzvLhGgOorUjSk6LshVxoMe8yqSGlZVNEiIZ84= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b274e49cd4d1_7afe2b073d040f502285eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 18 Jun 2018 06:16:46 -0000 ----==_mimepart_5b274e49cd4d1_7afe2b073d040f502285eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @nibanks Your architectural description makes sense, but it doesn't seem that difficult to tell a server not to send RETRY if it's behind such a device. Not only should it be possible, I think it's necessary for ideal performance? Requiring a different source ID seems to fix the immediate issue here, but we'd also have to limit the number of RETRYs to 2, which may be sensible anyway? -- 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/1451#issuecomment-397952286 ----==_mimepart_5b274e49cd4d1_7afe2b073d040f502285eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@nibanks Your architectural descr= iption makes sense, but it doesn't seem that difficult to tell a server n= ot to send RETRY if it's behind such a device. Not only should it be pos= sible, I think it's necessary for ideal performance?

Requiring a different source ID seems to fix the immediate issue here,= but we'd also have to limit the number of RETRYs to 2, which may be sens= ible anyway?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b274e49cd4d1_7afe2b073d040f502285eb-- From nobody Sun Jun 17 23:46:57 2018 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 D3DAD1292AD for ; Sun, 17 Jun 2018 23:46:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 ydZnGhhnvmQ0 for ; Sun, 17 Jun 2018 23:46:54 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BE73127598 for ; Sun, 17 Jun 2018 23:46:54 -0700 (PDT) Date: Sun, 17 Jun 2018 23:46:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529304413; bh=wDY4ipGi/BvmuLlbBfXbvNQ+3sqC1MVct89uRmdXb3U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pPzE0Ue/s2plU1laBRTWkPkPA9P0mYlDpc5mWQ0BkPNYXaFYe4liacWwNF8GsybPQ lITsqTVimgHoYsnvd5UKI5OfeP7L6JQ357kjZnX6B5TtuR+xyJwjt9pNxAVvP3zUUT guBUct1LLfC96ezEhInhltPUuCZuomOIZgLmkz1s= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27555d2d5d3_1b082ac41adaef54269426"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 18 Jun 2018 06:46:56 -0000 ----==_mimepart_5b27555d2d5d3_1b082ac41adaef54269426 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. Looks good. Not giving out connection Ids seems clever, but if that's the only mechanism for disabling migration, then it would seem to discourage people for giving them out for other reasons. -- 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/1447#pullrequestreview-129441251 ----==_mimepart_5b27555d2d5d3_1b082ac41adaef54269426 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

Looks good. Not giving out connection Ids seems clever, but if that's the only mechanism for disabling migration, then it would seem to discourage people for giving them out for other reasons.

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

----==_mimepart_5b27555d2d5d3_1b082ac41adaef54269426-- From nobody Mon Jun 18 00:00:57 2018 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 AA79A130DE6 for ; Mon, 18 Jun 2018 00:00:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 IoMtAEdgs5jV for ; Mon, 18 Jun 2018 00:00:53 -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 4DB1D127598 for ; Mon, 18 Jun 2018 00:00:53 -0700 (PDT) Date: Mon, 18 Jun 2018 00:00:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529305252; bh=j+iSN1p/5ynNkQscRkJGsaCo4LOlvj8Dkt243nh4mwo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HGS2O1jJq8N+p4B0g1a2D18gYuTjpFn/KhjdTHzW4THKfTPgw1cVjYn3TvaLymaif l/XYMLYD6Y+UQklZfyx5AJGKvUwTFa7DVKd9C9LR98auuKsw/cdpuhL/rne80TgXN5 OUTdbsS7NftSXVftS8jPGcce3KRervLoEpQBUtBQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2758a44bb5c_222fb3fd996f90f8830488"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 07:00:55 -0000 ----==_mimepart_5b2758a44bb5c_222fb3fd996f90f8830488 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > +The keys for the remaining encryption level are computed in the same +fashion as the corresponding TLS keys (see {{TLS13}}; Section 7), +except that the label for HKDF-Expand-Label uses the prefix "quic " +rather than "tls 13". The purpose of this change is to provide key `"tls 13"` should be `"tls13 "` (notice the position of the whitespace) -- 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/1450#pullrequestreview-129444035 ----==_mimepart_5b2758a44bb5c_222fb3fd996f90f8830488 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-tls.md:

>  
+The keys for the remaining encryption level are computed in the same
+fashion as the corresponding TLS keys (see {{TLS13}}; Section 7),
+except that the label for HKDF-Expand-Label uses the prefix "quic "
+rather than "tls 13". The purpose of this change is to provide key

"tls 13" should be "tls13 " (notice the position of the whitespace)

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

----==_mimepart_5b2758a44bb5c_222fb3fd996f90f8830488-- From nobody Mon Jun 18 00:34:28 2018 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 78408130DE6 for ; Mon, 18 Jun 2018 00:34:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 cavlPidZZnwf for ; Mon, 18 Jun 2018 00:34:23 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9D3E130D7A for ; Mon, 18 Jun 2018 00:34:23 -0700 (PDT) Date: Mon, 18 Jun 2018 00:34:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529307262; bh=kH3FhC7BNeiZaqj29J6XXRSihoix1sT/2rtjVE1JIG8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wBM/TSyNK3nQMhaRolmsmJU0xzenuR0hTjz+GIzdkEfaP7p3qqB68QItqI+JdveK+ EYdH7j9qGBTSJmil5VD+UaTKfq9y3xqvArhigfjq90DOoTBvj8gWiB8nhhzff78H9G k9EszJ+f7yx3h6lGkp15cQ/tzK9wA9p7kHwlIv4E= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27607ed1abd_2552ac8ab8bcf605021ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 07:34:26 -0000 ----==_mimepart_5b27607ed1abd_2552ac8ab8bcf605021ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > -Once 1-RTT keys are available to an endpoint, it no longer needs the TLS -handshake messages that are carried in unprotected packets. However, a server -might need to retransmit its TLS handshake messages in response to receiving an -unprotected packet that contains ACK frames. A server MUST process ACK frames -in unprotected packets until the TLS handshake is reported as complete, or it -receives an ACK frame in a protected packet that acknowledges all of its -handshake messages. +Receiving and verifying the TLS Finished message is critical in +ensuring the integrity of the TLS handshake. A server MUST NOT use +1-RTT protected packets from the client prior to verifying the client +Finished message if its response depends on client authentication. This paragraph seems redundant. The PR already has the following text starting from line 843, ``` However, a server MUST NOT process data from incoming 1-RTT protected packets before verifying either the client Finished message or - in the case that the server has chosen to use a pre-shared key - the pre-shared key binder (see Section 4.2.8 of {{!TLS13}}). ``` -- 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/1450#pullrequestreview-129451533 ----==_mimepart_5b27607ed1abd_2552ac8ab8bcf605021ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-tls.md:

>  
-Once 1-RTT keys are available to an endpoint, it no longer needs the TLS
-handshake messages that are carried in unprotected packets.  However, a server
-might need to retransmit its TLS handshake messages in response to receiving an
-unprotected packet that contains ACK frames.  A server MUST process ACK frames
-in unprotected packets until the TLS handshake is reported as complete, or it
-receives an ACK frame in a protected packet that acknowledges all of its
-handshake messages.
+Receiving and verifying the TLS Finished message is critical in
+ensuring the integrity of the TLS handshake.  A server MUST NOT use
+1-RTT protected packets from the client prior to verifying the client
+Finished message if its response depends on client authentication.

This paragraph seems redundant. The PR already has the following text starting from line 843,

However,
a server MUST NOT process data from incoming 1-RTT protected packets
before verifying either the client Finished message or - in the case that the
server has chosen to use a pre-shared key - the pre-shared key binder (see
Section 4.2.8 of {{!TLS13}}).

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

----==_mimepart_5b27607ed1abd_2552ac8ab8bcf605021ac-- From nobody Mon Jun 18 02:37:59 2018 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 3D59F130ED8 for ; Mon, 18 Jun 2018 02:37:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0GBtaZjGEQMy for ; Mon, 18 Jun 2018 02:37:42 -0700 (PDT) Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8698B130E77 for ; Mon, 18 Jun 2018 02:37:42 -0700 (PDT) Date: Mon, 18 Jun 2018 02:37:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529314662; bh=/h/4mZTairYOm6t54dhiP99edsr2WdLsbiRxscM5q9s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0STQHwI5pT/IAMxbe5GOgGaphBHvCDJqKppoRuLl4EqYJoFu3bdVJE/qbDkXjlVNz e4onHC3z+3ViKRuFFtuw8OIhCQfv53YD7RDqBSohUjB5LK9OQMPxRtftPV3niScO1q ZZ713WmX5wtBQCwTAKOl3RZe3IExcLRBz4DoXD38= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b277d65d29bf_95363fddf0686f8865611"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 09:37:57 -0000 ----==_mimepart_5b277d65d29bf_95363fddf0686f8865611 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho > By using ACK frames to carry the PNs along with their CE bits, it is possible for the sender to find and reject duplicate signals. The information that reaches the sender first is adopted (in contrast to the approach of #1372 that adopts the information that reaches the receiver first). That is the principle. Okay, if that is the general principle to make this work, you can't only provide CE to PN mappings. You need to indicate which packets get ECT or not-ECT marks also. i.e. you need to provide the ECN field value for all the packets included in the ACK. Then the other mechanisms needed for ECN than congestion event detection also will work. Yes, as long as we have any counters in the ECN encoding, the receiver will need to either suppress the duplicates from being counted, or include a counter for how many duplicate packets it has included in the counters for the various ECN field values received. So in regards to duplicated packets, what is your policy for handling that truly when a receiver don't suppress the duplicate prior to ECN processing? [Additional required for counter handling when have CE vector and counters for ECT] A) The receiver reports what was first received for a PN, i.e. a duplicate is not allowed to overwrite any already stored ECN field value. [Any duplicate ECN field value is not added to counters] B) The receiver reports what is stored in receiver when generating the ACK, i.e. the latest received information. Thus duplicates may overwrite ECN field values of the first, if ACK hasn't been sent yet. [Added to counter in the interest of simplicity] C) Reception of an ECN field value that is different from what already exists forces an ACK, then the field value is overwritten and reported in the next ACK packet. [Counter values added for all packets] D) The ACK reports the ECN Field values explicit for first received and then any duplicates making it clear that this is multiple received packets for the PN? [Using counters this require a counter for duplicates] My comment on these policies are the following: A) Works and is an ECN level suppression of duplicate packets B) Sensitive to on-the-side ECN field value attacks. [Duplication causes slack in detection] C) Forces a more complex handling of packets and triggering of ACKs and in cases of ACK loss an on-the-side attack may get its information in. [Duplication causes slack in detection when subject to ACK loss] D) Full capability for sender to interpret information, more complex encoding the ECN information to enable multiple copies of a PN to be correctly represented. [Works when counting duplicates] So beyond the primary purpose of ECN to detect congestion events, the mechanism needs to have capability also to: * Detect working paths * Detect bleaching in mid-connection * Detect working path after connection migration * Mitigate attacks, at least off-path or on-side attacks. On path attackers can cause the same response as well as additional issues by dropping packets for a connection. I hope this clarifies my view why I don't think CE vectors are sufficient. For a solution that doesn't suppress duplicates prior to ECN processing, one either need explicit counting of number of duplicates if using counters, or a per packet information that that includes both bits of the ECN field as well as indicating any duplicates not suppressed by the receiver. I think a efficiency comparison both in regards to size of ACKs as well as implementation complexity between these two are fine and should be done. -- 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/1439#issuecomment-397998222 ----==_mimepart_5b277d65d29bf_95363fddf0686f8865611 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho

By using ACK frames to carry the PNs along with their CE bits, it is p= ossible for the sender to find and reject duplicate signals. The informat= ion that reaches the sender first is adopted (in contrast to the approach= of #1372 tha= t adopts the information that reaches the receiver first). That is the pr= inciple.

Okay, if that is the general principle to make this work, you can't on= ly provide CE to PN mappings. You need to indicate which packets get ECT = or not-ECT marks also. i.e. you need to provide the ECN field value for a= ll the packets included in the ACK. Then the other mechanisms needed for = ECN than congestion event detection also will work.

Yes, as long as we have any counters in the ECN encoding, the receiver= will need to either suppress the duplicates from being counted, or inclu= de a counter for how many duplicate packets it has included in the counte= rs for the various ECN field values received.

So in regards to duplicated packets, what is your policy for handling = that truly when a receiver don't suppress the duplicate prior to ECN proc= essing? [Additional required for counter handling when have CE vector and= counters for ECT]
A) The receiver reports what was first received for a PN, i.e. a duplicat= e is not allowed to overwrite any already stored ECN field value. [Any du= plicate ECN field value is not added to counters]
B) The receiver reports what is stored in receiver when generating the AC= K, i.e. the latest received information. Thus duplicates may overwrite EC= N field values of the first, if ACK hasn't been sent yet. [Added to count= er in the interest of simplicity]
C) Reception of an ECN field value that is different from what already ex= ists forces an ACK, then the field value is overwritten and reported in t= he next ACK packet. [Counter values added for all packets]
D) The ACK reports the ECN Field values explicit for first received and t= hen any duplicates making it clear that this is multiple received packets= for the PN? [Using counters this require a counter for duplicates]

My comment on these policies are the following:
A) Works and is an ECN level suppression of duplicate packets
B) Sensitive to on-the-side ECN field value attacks. [Duplication causes = slack in detection]
C) Forces a more complex handling of packets and triggering of ACKs and i= n cases of ACK loss an on-the-side attack may get its information in. [Du= plication causes slack in detection when subject to ACK loss]
D) Full capability for sender to interpret information, more complex enco= ding the ECN information to enable multiple copies of a PN to be correctl= y represented. [Works when counting duplicates]

So beyond the primary purpose of ECN to detect congestion events, the = mechanism needs to have capability also to:

  • Detect working paths
  • Detect bleaching in mid-connection
  • Detect working path after connection migration
  • Mitigate attacks, at least off-path or on-side attacks. On path attac= kers can cause the same response as well as additional issues by dropping= packets for a connection.

I hope this clarifies my view why I don't think CE vectors are suffici= ent. For a solution that doesn't suppress duplicates prior to ECN process= ing, one either need explicit counting of number of duplicates if using c= ounters, or a per packet information that that includes both bits of the = ECN field as well as indicating any duplicates not suppressed by the rece= iver. I think a efficiency comparison both in regards to size of ACKs as = well as implementation complexity between these two are fine and should b= e done.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b277d65d29bf_95363fddf0686f8865611-- From nobody Mon Jun 18 03:46:13 2018 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 DDD72130E95 for ; Mon, 18 Jun 2018 03:46:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1FlPra0oeaEo for ; Mon, 18 Jun 2018 03:46:00 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6646E130E8F for ; Mon, 18 Jun 2018 03:46:00 -0700 (PDT) Date: Mon, 18 Jun 2018 03:45:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529318759; bh=uEA7ymqj8FIv83Y7k5qnue0HgZT9+wjDZrwh2GAjSXs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d+ozu/ZnJmHlIe8VjtSVbrZqubFDNwDx34ivuhl+TRYakiwzu+NV9OharLWwZG+B1 hkoOMmNIeuInkvLiR1f9i+mLC1KVE8TOgX8qlvI+/8aQ59UG+sQYEVrt5CkxYQo+Aw D6CYZG194kBBS5wYiwB08XfsrogEhEQ+QjTn1oGw= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b278d6755928_66be2abc41f76f5c11846f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 10:46:12 -0000 ----==_mimepart_5b278d6755928_66be2abc41f76f5c11846f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In regards to @kazuho comment: = > As discussed in #1439 (comment), my understanding is that the ECN suppo= rt in the form proposed in #1372 is the only issue that makes duplicate d= etection a requirement rather than an option. So, do I assume correctly, that you will still throw away packets that ar= e several RTTs old, i.e. that have a PN number older than any state? Or d= o you generate an ACK for that old packet that is so old, and try to find= if there is any unconsumed buffers to put any data in? = You might be right in that all existing frames have a behavior that if on= e applies it twice it already have the handling rules to suppress the dup= licate or not cause any downside of being applied twice. I looked through= the frame types and the only ones that I think have some impact are: * Path_Challenge: A non duplication detecting receiver, will issue two Pa= th_Response frames in response to a single PN. The sender of the Path_Cha= llenge should not react badly to this. = Also, I haven't considered if there are any new requirements with the han= dshake packets and the interaction with TLS? = I would note that AES-GCM do have this weakness (Fergueson http://csrc.n= ist.gov/groups/ST/toolkit/BCM/documents/comments/CWC-GCM/Ferguson2.pdf) t= hat if one manage to know that one successfully forged a packet so that i= t passed the authentication verification, then one learns a number of bit= s of the authentication key, making the next forgery simpler. If it is po= ssible to run such an attack by sending modified duplicates with forged a= uthentication tags resulting in a response, then this can be exploited (h= ttps://link.springer.com/chapter/10.1007/978-3-319-31517-1_7). So QUIC wi= ll not use truncated tags, but QUIC connections may be very long lived in= certain environments. Thus making it possible to maintain an attack for = a sufficient time to possible have any result. Thus, I think for safety r= easons packet duplication suppression after decryption should be mandator= y to prevent this information leakage and not put that onto the individua= l frame types to consider if they will result in reveal of a successful f= orgery of a modified duplicate packet. = I also noted that when we discussed this at the Interim it appeared that = most, if not all except @kazuho was thinking that duplication suppression= was expected in the receiver. If this is not required, then think the ac= tual requirements on each frame type individually needs to be very clear.= = It would be good to come to a conclusion on this issue so that we can det= ermine what is needed for the ECN addition (#1372). = -- = 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/1405#issuecomment-398014741= ----==_mimepart_5b278d6755928_66be2abc41f76f5c11846f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In regards to @kazuho comment:

As discussed in #1439 (comment), my understanding is that the ECN support in the for= m proposed in #13= 72 is the only issue that makes duplicate detection a requirement rat= her than an option.

So, do I assume correctly, that you will still throw away packets that= are several RTTs old, i.e. that have a PN number older than any state? O= r do you generate an ACK for that old packet that is so old, and try to f= ind if there is any unconsumed buffers to put any data in?

You might be right in that all existing frames have a behavior that if= one applies it twice it already have the handling rules to suppress the = duplicate or not cause any downside of being applied twice. I looked thro= ugh the frame types and the only ones that I think have some impact are:<= /p>

  • Path_Challenge: A non duplication detecting receiver, will issue two = Path_Response frames in response to a single PN. The sender of the Path_C= hallenge should not react badly to this.

Also, I haven't considered if there are any new requirements with the = handshake packets and the interaction with TLS?

I would note that AES-GCM do have this weakness (Fergueson http://csrc.nist.gov/groups/ST/toolkit/BCM/= documents/comments/CWC-GCM/Ferguson2.pdf) that if one manage to know = that one successfully forged a packet so that it passed the authenticatio= n verification, then one learns a number of bits of the authentication ke= y, making the next forgery simpler. If it is possible to run such an atta= ck by sending modified duplicates with forged authentication tags resulti= ng in a response, then this can be exploited (https://l= ink.springer.com/chapter/10.1007/978-3-319-31517-1_7). So QUIC will n= ot use truncated tags, but QUIC connections may be very long lived in cer= tain environments. Thus making it possible to maintain an attack for a su= fficient time to possible have any result. Thus, I think for safety reaso= ns packet duplication suppression after decryption should be mandatory to= prevent this information leakage and not put that onto the individual fr= ame types to consider if they will result in reveal of a successful forge= ry of a modified duplicate packet.

I also noted that when we discussed this at the Interim it appeared th= at most, if not all except @kazuho was t= hinking that duplication suppression was expected in the receiver. If thi= s is not required, then think the actual requirements on each frame type = individually needs to be very clear.

It would be good to come to a conclusion on this issue so that we can = determine what is needed for the ECN addition (#1372).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b278d6755928_66be2abc41f76f5c11846f-- From nobody Mon Jun 18 03:55:37 2018 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 CCE2A130EA5 for ; Mon, 18 Jun 2018 03:55:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pgTsOg4CIeBi for ; Mon, 18 Jun 2018 03:55:33 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3CA01277CC for ; Mon, 18 Jun 2018 03:55:32 -0700 (PDT) Date: Mon, 18 Jun 2018 03:55:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529319332; bh=QVspZh81vPd0B5ioHbmpzfDJSz0r+W9GX5Sb0GEYxTI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=THBFG8TGJx3jV96pqTi+3KFx1IAvh7s4wG2UYXlpxcBsc78Hs7bIgJbwsLZcB4hjE LJS1uxDGIMcn1/vSoxhx+26zdiCYHsxTzzTw/bqR902/xY1rrvi7pA1fvTJDhqUV7/ ZgJoLsDPUuMftzzONXLnd8mSFy7ezvekjvTZB8cY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b278fa44b978_37622ad83e1c4f581664d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 18 Jun 2018 10:55:35 -0000 ----==_mimepart_5b278fa44b978_37622ad83e1c4f581664d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Thus, I think for safety reasons packet duplication suppression after decryption should be mandatory to prevent this information leakage and not put that onto the individual frame types to consider if they will result in reveal of a successful forgery of a modified duplicate packet. Rekeying must happen before that point. -- 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/1405#issuecomment-398016919 ----==_mimepart_5b278fa44b978_37622ad83e1c4f581664d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thus, I think for safety reasons packet duplication suppression after = decryption should be mandatory to prevent this information leakage and no= t put that onto the individual frame types to consider if they will resul= t in reveal of a successful forgery of a modified duplicate packet.

Rekeying must happen before that point.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b278fa44b978_37622ad83e1c4f581664d0-- From nobody Mon Jun 18 04:02:41 2018 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 B3B63130E8F for ; Mon, 18 Jun 2018 04:02:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 XBPJWt5fg65O for ; Mon, 18 Jun 2018 04:02:35 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 355FC130DDF for ; Mon, 18 Jun 2018 04:02:35 -0700 (PDT) Date: Mon, 18 Jun 2018 04:02:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529319754; bh=1Y3oitzAI8OCksSa0bBszpjgl2o6ETtDHyonFVqIqoc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZVQKNQVCS72tUVq15pOAHTWWDBWCmyFhaw+0kYX0ltcmWlFb1bksICfrOMOXZQcAH EON+m9bGWl/XOuXoqCSoli65uXUAZkupVEE24lib0bA0SPBr/g3wUZzKWtVo4odmr/ 08wVnxh0Qng1MxLfMMppZsCnf/eHl9QX3vXMgt4k= From: Juha-Matti Tilli Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27914a5f838_31bf2aed8654cf60370091"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jmtilli 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.26 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, 18 Jun 2018 11:02:39 -0000 ----==_mimepart_5b27914a5f838_31bf2aed8654cf60370091 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I read the QUIC specifications, aiming to add QUIC support to a layer 2 TCP SYN proxy I have implemented (https://github.com/Aalto5G/nmsynproxy). I realized it may very well require supporting multiple RETRY packets (I'm not 100% certain about this yet), which the latest QUIC Internet Draft does not permit. I'm not at all convinced by the suggestion of @ianswett that servers could be told to not send RETRY if behind a DoS protection device. If you want to deploy such a DoS protection device to a network having hundreds or thousands of server machines, surely you cannot turn the switch on all servers that RETRY is not required, exactly at the same second you deploy the DoS protection device! Worse, some of the servers may not be in your control (think about Amazon AWS), and some QUIC implementations may lack a switch to turn off sending of the RETRY. Furthermore, limiting the number of retries to 2 might work badly if such DoS protection devices are nested. It may be the case that there will be a RETRY from first DoS protection device, from second DoS protection device, ..., from N:th DoS protecton device and then eventually from the server. Performance is going to suck, but such a deployment should in my opinion be supported by QUIC. Such a deployment works perfectly well with TCP (you can nest TCP SYN proxies), and I don't believe QUIC should be a step backwards from TCP. I hope QUIC can support a DoS protection middlebox, like TCP already does. I also hope such DoS protection middleboxes could be nested nearly infinitely (ok, TTL issues might affect you once you have dozens of such middleboxes, if operating on layer 3, but there are solutions such as layer 2 middleboxes that don't decrement TTL). Remember that firewalls are a very common form of middlebox. Today, a firewall can implement TCP SYN proxy, meaning it doesn't have to keep state for connections from unvalidated addresses. With QUIC, the firewall could use normal UDP support without special support for QUIC, but then a UDP flood will fill the state tables of the firewall (and only the endpoint server's state tables will be protected from exhaustion by the RETRY mechanism). The only possibility to save from memory exhaustion is for the firewall to send a RETRY packet with cryptographically validated token the client should repeat, and then after validating the client's address, add the connection to the state table. Many enterprises have nested firewalls. Some of the nested firewalls may be in control of different entities (operator's firewall, common company firewall, some department's firewall). I'm not going to implement a full firewall, but I'm definitely looking forward to be able to add QUIC support to my TCP SYN proxy that lacks the rulesets and other features of a firewall, but has fully functional SYN proxy features. I'm also looking forward to be able to nest the QUIC version of the SYN proxy semi-infinitely. Now, the following kind of architecture might (or might not) work, I have to investigate it further: [client] -> ClientHello -> [middlebox] [server] [client] <- RETRY <- [middlebox] [server] [client] -> ClientHello -> [middlebox] [server] [client] [middlebox] -> ClientHello -> [server] [client] [middlebox] <- RETRY <- [server] [client] [middlebox] -> ClientHello -> [server] ... This architecture would work without having to fully propagate the RETRY back to the client. I'm not certain if some of the cryptographic mechanisms would make this architecture invalid. -- 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/1451#issuecomment-398018381 ----==_mimepart_5b27914a5f838_31bf2aed8654cf60370091 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I read the QUIC specifications, aiming to add QUIC support to a layer = 2 TCP SYN proxy I have implemented (https://github.com/Aalto5G/nmsynproxy). I realized it ma= y very well require supporting multiple RETRY packets (I'm not 100% certa= in about this yet), which the latest QUIC Internet Draft does not permit.=

I'm not at all convinced by the suggestion of @ianswett that servers could be told to not send RETRY if b= ehind a DoS protection device. If you want to deploy such a DoS protectio= n device to a network having hundreds or thousands of server machines, su= rely you cannot turn the switch on all servers that RETRY is not required= , exactly at the same second you deploy the DoS protection device! Worse,= some of the servers may not be in your control (think about Amazon AWS),= and some QUIC implementations may lack a switch to turn off sending of t= he RETRY.

Furthermore, limiting the number of retries to 2 might work badly if s= uch DoS protection devices are nested. It may be the case that there will= be a RETRY from first DoS protection device, from second DoS protection = device, ..., from N:th DoS protecton device and then eventually from the = server. Performance is going to suck, but such a deployment should in my = opinion be supported by QUIC. Such a deployment works perfectly well with= TCP (you can nest TCP SYN proxies), and I don't believe QUIC should be a= step backwards from TCP.

I hope QUIC can support a DoS protection middlebox, like TCP already d= oes. I also hope such DoS protection middleboxes could be nested nearly i= nfinitely (ok, TTL issues might affect you once you have dozens of such m= iddleboxes, if operating on layer 3, but there are solutions such as laye= r 2 middleboxes that don't decrement TTL).

Remember that firewalls are a very common form of middlebox. Today, a = firewall can implement TCP SYN proxy, meaning it doesn't have to keep sta= te for connections from unvalidated addresses. With QUIC, the firewall co= uld use normal UDP support without special support for QUIC, but then a U= DP flood will fill the state tables of the firewall (and only the endpoin= t server's state tables will be protected from exhaustion by the RETRY me= chanism). The only possibility to save from memory exhaustion is for the = firewall to send a RETRY packet with cryptographically validated token th= e client should repeat, and then after validating the client's address, a= dd the connection to the state table. Many enterprises have nested firewa= lls. Some of the nested firewalls may be in control of different entities= (operator's firewall, common company firewall, some department's firewal= l).

I'm not going to implement a full firewall, but I'm definitely looking= forward to be able to add QUIC support to my TCP SYN proxy that lacks th= e rulesets and other features of a firewall, but has fully functional SYN= proxy features. I'm also looking forward to be able to nest the QUIC ver= sion of the SYN proxy semi-infinitely.

Now, the following kind of architecture might (or might not) work, I h= ave to investigate it further:

[client] -> ClientHello -> [middlebox]                  =
 [server]
[client] <- RETRY       <- [middlebox]                   [server]
[client] -> ClientHello -> [middlebox]                   [server]
[client]                   [middlebox] -> ClientHello -> [server]
[client]                   [middlebox] <- RETRY       <- [server]
[client]                   [middlebox] -> ClientHello -> [server]
...

This architecture would work without having to fully propagate the RET= RY back to the client. I'm not certain if some of the cryptographic mecha= nisms would make this architecture invalid.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27914a5f838_31bf2aed8654cf60370091-- From nobody Mon Jun 18 04:23:28 2018 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 605A3130E96 for ; Mon, 18 Jun 2018 04:23:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 9xZpfqwFuhuO for ; Mon, 18 Jun 2018 04:23:22 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C53C124BE5 for ; Mon, 18 Jun 2018 04:23:22 -0700 (PDT) Date: Mon, 18 Jun 2018 04:23:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529321001; bh=omLdYLYhFm7V1XNRsW7XFoxX93oTY7B9pJQcxWP204E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AC5laH7lnmkqbgplEHFWHIov1F/ucZMOnkLJsL20M8EuU+J4edJgO1nQAf6M3h6+L +eFWzZpBifKQ5u9q7IYa76AN2hts6rKMcITEDZbhU7b/EsFyLOHXlz9WCfiDjLpYRZ RlKLAIsINOHR/oGQf1f7GI+U3IQZSTVW8iBYnabg= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2796294dd8b_78d3ffbaebc0f7c1365c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 11:23:25 -0000 ----==_mimepart_5b2796294dd8b_78d3ffbaebc0f7c1365c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj I am uncertain if that happens in a way that will prevent this attack. My assumption when this attack would be possible would be a low rate management connection where any rekeying based on number of legit sent packets may occur very infrequently. I don't find what the rekeying frequency requirements are, does someone have pointer? The number of tested forges will be dependent on the number of forged duplicate packets the attacker manage to send without raising an alarm that the connection is under attack. But, if there are no such warnings then an attacker could potentially send a large number of attack packets without the target noticing other than it drops a lot of packets due to authentication failure. The attack only consumes PN and thus packets until rekeying when a successful forge has been accomplished. To my understanding the protection against this type of attack, is to prevent that a successful forge results in a response. If there are no general duplication protection then using a recently sent packet as attack packet is makes it simpler to cause a response. In fact the response to ECN-CE marks can actually be one thing that provides such a proof if some of the response discussed in #1372 would be allowed. Modifying the payload forging the authentication tag and setting the ECN bits to CE could then trigger an ACK on successful forge. For a connection that mostly idle that ACK will be a good signal for a forge. However, for this type of connection one can likely also target packets with a PING frame. Thus, also getting an ACK response on successful forge. -- 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/1405#issuecomment-398022746 ----==_mimepart_5b2796294dd8b_78d3ffbaebc0f7c1365c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj I am uncertain if that h= appens in a way that will prevent this attack. My assumption when this at= tack would be possible would be a low rate management connection where an= y rekeying based on number of legit sent packets may occur very infrequen= tly. I don't find what the rekeying frequency requirements are, does some= one have pointer?

The number of tested forges will be dependent on the number of forged = duplicate packets the attacker manage to send without raising an alarm th= at the connection is under attack. But, if there are no such warnings the= n an attacker could potentially send a large number of attack packets wit= hout the target noticing other than it drops a lot of packets due to auth= entication failure. The attack only consumes PN and thus packets until re= keying when a successful forge has been accomplished.

To my understanding the protection against this type of attack, is to = prevent that a successful forge results in a response. If there are no ge= neral duplication protection then using a recently sent packet as attack = packet is makes it simpler to cause a response. In fact the response to E= CN-CE marks can actually be one thing that provides such a proof if some = of the response discussed in #1372 would be allowed. Modifying the payload forging the= authentication tag and setting the ECN bits to CE could then trigger an = ACK on successful forge. For a connection that mostly idle that ACK will = be a good signal for a forge. However, for this type of connection one ca= n likely also target packets with a PING frame. Thus, also getting an ACK= response on successful forge.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2796294dd8b_78d3ffbaebc0f7c1365c-- From nobody Mon Jun 18 04:40:30 2018 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 54A33130E8F for ; Mon, 18 Jun 2018 04:40:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 xqekRgK8C7OI for ; Mon, 18 Jun 2018 04:40:26 -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 28E20130E23 for ; Mon, 18 Jun 2018 04:40:26 -0700 (PDT) Date: Mon, 18 Jun 2018 04:40:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529322025; bh=qf3kr1rFXwXHEA9AKuIdu8JdVH1Bj7jXV+41Y7ryQlc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xFcsWeHMgQL+17P26q7/ghhbfYFKsgKIyFkOb3CSPE5J3BuIbhTJm/573Plm+icja GaxJKDNXCy7iHGFPhwnKvAOxdjSgx/HwOAUuKXkNySiTXXovAAqInK5ikGpfK43H/k JWykjRwNiMfNpxJa65n4KJ9A+qnTnfytvlKW2Zzg= From: Juha-Matti Tilli Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b279a29a6bb_356a2ab7455aef5c1603de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jmtilli 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.26 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, 18 Jun 2018 11:40:28 -0000 ----==_mimepart_5b279a29a6bb_356a2ab7455aef5c1603de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit IPv4 address exhaustion is a reality, and the truth is that IPv6 will not be deployed fast enough to be a complete solution. I have an idea where QUIC could be used to solve the IPv4 address exhaustion problem by using multiplexing middleboxes, with minimal modifications to QUIC. The idea is that the client is forced to provide a server name indication (SNI) if the user provided the client with a DNS name instead of a raw IP address. A NAT middlebox then shares one IPv4 address for multiple servers. The middlebox makes a decision based on the SNI which internal private IPv4 address will be used. The connection will always, reliably, be forwarded to the correct internal private IPv4 address, because the client would be required to always supply an SNI. Nested middleboxes may be supported by configuring SNI matches with wildcards (e.g. server1.department1.company.com will match *.department1.company.com at the company's middlebox and server1.department.company.com at the department's middlebox). The most common application of QUIC, web browsing, typically uses DNS names and not IP addresses. The most important of the eventual applications of QUIC will probably be: * E-mail: SMTP over QUIC * Remote access: SSH over QUIC, VNC over QUIC, etc. For SMTP, the MX records already use DNS names instead of IP addresses. SSH and VNC are also typically executed with DNS names. The only change to QUIC would be to add the following to draft-ietf-quic-tls-12 somewhere:
A client MUST provide a server name indication, as defined in RFC6066, if the user of the client specified the connection destination as a DNS name instead of an IP address.
I don't see any mention of SNI in QUIC specifications now, so I assume the proposed requirement is not a requirement now. TLS 1.3 apparently allows servers to require a client to use SNI (https://tools.ietf.org/html/draft-ietf-tls-tls13-28), but I believe the same should be explicitly specified in the QUIC specifications as well. According to TLS 1.3 draft:
Additionally, all implementations MUST support use of the "server_name" extension with applications capable of using it. Servers MAY require clients to send a valid "server_name" extension. Servers requiring this extension SHOULD respond to a ClientHello lacking a "server_name" extension by terminating the connection with a "missing_extension" alert.
I hope the same will be true with QUIC's use of TLS. Otherwise QUIC will be a step backwards from TLS+TCP that allows a transparent proxy to operate as a NAT multiplexing device offering access to multiple servers. If QUIC makes SNI necessary, then QUIC will be much better than TCP+TLS because you don't need a full transparent proxy to do said multiplexing (as the first packet already contains the SNI). I hope this is the correct venue for this modification proposal (this is my first QUIC related issue). I'm not part of any QUIC mailing list, but if a mailing list is a more appropriate venue for discussing this modification, I could join. -- 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/1456 ----==_mimepart_5b279a29a6bb_356a2ab7455aef5c1603de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

IPv4 address exhaustion is a reality, and the truth is that IPv6 will not be deployed fast enough to be a complete solution. I have an idea where QUIC could be used to solve the IPv4 address exhaustion problem by using multiplexing middleboxes, with minimal modifications to QUIC.

The idea is that the client is forced to provide a server name indication (SNI) if the user provided the client with a DNS name instead of a raw IP address. A NAT middlebox then shares one IPv4 address for multiple servers. The middlebox makes a decision based on the SNI which internal private IPv4 address will be used. The connection will always, reliably, be forwarded to the correct internal private IPv4 address, because the client would be required to always supply an SNI. Nested middleboxes may be supported by configuring SNI matches with wildcards (e.g. server1.department1.company.com will match *.department1.company.com at the company's middlebox and server1.department.company.com at the department's middlebox).

The most common application of QUIC, web browsing, typically uses DNS names and not IP addresses.

The most important of the eventual applications of QUIC will probably be:

  • E-mail: SMTP over QUIC
  • Remote access: SSH over QUIC, VNC over QUIC, etc.

For SMTP, the MX records already use DNS names instead of IP addresses. SSH and VNC are also typically executed with DNS names.

The only change to QUIC would be to add the following to draft-ietf-quic-tls-12 somewhere:

A client MUST provide a server name indication, as defined in RFC6066, if the user of the client specified the connection destination as a DNS name instead of an IP address.

I don't see any mention of SNI in QUIC specifications now, so I assume the proposed requirement is not a requirement now.

TLS 1.3 apparently allows servers to require a client to use SNI (https://tools.ietf.org/html/draft-ietf-tls-tls13-28), but I believe the same should be explicitly specified in the QUIC specifications as well. According to TLS 1.3 draft:

Additionally, all implementations MUST support use of the "server_name" extension with applications capable of using it. Servers MAY require clients to send a valid "server_name" extension. Servers requiring this extension SHOULD respond to a ClientHello lacking a "server_name" extension by terminating the connection with a "missing_extension" alert.

I hope the same will be true with QUIC's use of TLS. Otherwise QUIC will be a step backwards from TLS+TCP that allows a transparent proxy to operate as a NAT multiplexing device offering access to multiple servers.

If QUIC makes SNI necessary, then QUIC will be much better than TCP+TLS because you don't need a full transparent proxy to do said multiplexing (as the first packet already contains the SNI).

I hope this is the correct venue for this modification proposal (this is my first QUIC related issue). I'm not part of any QUIC mailing list, but if a mailing list is a more appropriate venue for discussing this modification, I could join.

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

----==_mimepart_5b279a29a6bb_356a2ab7455aef5c1603de-- From nobody Mon Jun 18 04:44:26 2018 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 F3601130E23 for ; Mon, 18 Jun 2018 04:44:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oGrVUuoQg_EI for ; Mon, 18 Jun 2018 04:44:22 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0912E130E96 for ; Mon, 18 Jun 2018 04:44:22 -0700 (PDT) Date: Mon, 18 Jun 2018 04:44:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529322261; bh=74zV0Z4dFy8NkW5eOAdZ+vqT1VfzAMfqhQIwg41J3pI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R4iIsBvYmYEdqcbFq3YtWtxmqFdnGynmaZkxKwNAfLB+Bjse+mC/w0Pkp4PaCL+SQ f4/CHyhxYc5GR7QgI5EVgHKlXmEYEqCvQc7Rj47Vlu1BqXnmtKOUtKy7FI7000MUgd fRBa/3SMVhv4CaHz/JoFD597Q3k1T+p5bGktcKPE= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b279b15680e4_58202afa54322f5c157862"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 18 Jun 2018 11:44:24 -0000 ----==_mimepart_5b279b15680e4_58202afa54322f5c157862 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If keys are not updated within about 2^32 packets one might might as well introduce a new plain text option because it would achieve the same with less overhead. - https://quicwg.org/base-drafts/draft-ietf-quic-tls.html#rfc.section.6.2 - https://tlswg.github.io/tls13-spec/draft-ietf-tls-tls13.html#rfc.section.5.5 - https://tlswg.github.io/tls13-spec/draft-ietf-tls-tls13.html#AEAD-LIMITS - http://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf -- 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/1405#issuecomment-398027221 ----==_mimepart_5b279b15680e4_58202afa54322f5c157862 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If keys are not updated within about 2^32 packets one might might as w= ell introduce a new plain text option because it would achieve the same w= ith less overhead.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b279b15680e4_58202afa54322f5c157862-- From nobody Mon Jun 18 04:45:34 2018 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 9CCB5130EA6 for ; Mon, 18 Jun 2018 04:45:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 wDmZ6EYoL96s for ; Mon, 18 Jun 2018 04:45:29 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 2D422130E96 for ; Mon, 18 Jun 2018 04:45:29 -0700 (PDT) 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=lcRaoaR+j5XGYApvYKujcTInJgY=; b=RDDsEV78+SNh+kjQ UdZKCEs/6L4Pc4P6J/B/ohs5Fzdgl0KoaKNJ3ADVTV59UkgFRawuut95f8RQ5hU+ Ddny7AsX2TIxT0vn9uiZxqjhc4K+DLQEPX5vow6Kj+S1hK9uUhoiCu1LoamGM/ss 0CGk0+08VhadZkFJtnmoKU4oIkI= Received: by filter0057p1iad2.sendgrid.net with SMTP id filter0057p1iad2-28055-5B279B57-36 2018-06-18 11:45:27.950805116 +0000 UTC Received: from github-lowworker13-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id wALj4WDfQtaZ49SGRAjmkw for ; Mon, 18 Jun 2018 11:45:27.867 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker13-cp1-prd.iad.github.net (Postfix) with ESMTP id D294920CC6 for ; Mon, 18 Jun 2018 04:45:27 -0700 (PDT) Date: Mon, 18 Jun 2018 11:45:28 +0000 (UTC) From: Juha-Matti Tilli Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] SNI encryption (#795) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b279b57d13ab_4fb73feb66296f802966e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jmtilli 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3PAom0XouGKFILrM6wmvGCnZKP9rCXYhSh67 QHTQOMG9dgyhVFpf9zQ1HaLceTIwERZr3JExTjJmYBdHbT4lWxnIRYYMZWPNajTS8tffInVRevqXOn DDEewTD5fJbO38yTV06KDSyE245KdepSz93U1Wxn33nU9Mnhy/QK6KihfwJ2ZYlIJmHh5tSQHydC29 U= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 11:45:32 -0000 ----==_mimepart_5b279b57d13ab_4fb73feb66296f802966e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I hope people here realize that this proposal of encrypting the SNI will make multiplexing connections on a NAT middlebox (see Issue #1456) practically impossible. The IPv4 address exhaustion is a reality, and IPv6 adoption will probably be much slower than QUIC adoption, so QUIC should not contribute to the IPv4 address shortage problem by encrypting the only piece of information about the server (i.e. the DNS name) in addition to the IPv4 address. In contrast, if SNI remains unencrypted, a NAT middlebox can share an IPv4 address for multiple servers and choose the correct server based on the SNI. -- 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/795#issuecomment-398027461 ----==_mimepart_5b279b57d13ab_4fb73feb66296f802966e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I hope people here realize that this proposal of encrypting the SNI will= make multiplexing connections on a NAT middlebox (see Issue #1456) practically impossible.

The IPv4 address exhaustion is a reality, and IPv6 adoption will probabl= y be much slower than QUIC adoption, so QUIC should not contribute to the I= Pv4 address shortage problem by encrypting the only piece of information ab= out the server (i.e. the DNS name) in addition to the IPv4 address.

In contrast, if SNI remains unencrypted, a NAT middlebox can share an IP= v4 address for multiple servers and choose the correct server based on the = SNI.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b279b57d13ab_4fb73feb66296f802966e1-- From nobody Mon Jun 18 04:57:16 2018 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 62B12130EB5 for ; Mon, 18 Jun 2018 04:57:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 q_XVC69VhjvD for ; Mon, 18 Jun 2018 04:57:04 -0700 (PDT) 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 83384130F3C for ; Mon, 18 Jun 2018 04:57:04 -0700 (PDT) Date: Mon, 18 Jun 2018 04:57:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529323023; bh=ZWaeaS6FHrtwSBS4iLOG+o5OrCCK5JW2LHPOTja0tHo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hCfk/iEU8mBdp+qmKyZ+zcbe/i5tF6Ej8u1JCLuufIi6Oj2ZAmxoSEO9THXPmTqvR YAVuJqMu3SZhfe3MXr7p4N1F+nxROEta/PAcrO9GeL32fpN0umxDhvEWQjHGCEqN3P 6ptcPG+C9b6uw9Ppr8YgpeNbyYEU8zC0733wjWlI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b279e0fa74cd_65342adf9d4a2f5c191946"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 18 Jun 2018 11:57:15 -0000 ----==_mimepart_5b279e0fa74cd_65342adf9d4a2f5c191946 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This probably should be discussed on the mailing list rather than as an issue. Aren't there privacy concerns here? One could imagine a DNS like mapping from SNI to connection ID similar to a stateless retry, but where a SNI drives the retry. This could be a sort-of separate service external to QUIC. -- 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/1456#issuecomment-398029983 ----==_mimepart_5b279e0fa74cd_65342adf9d4a2f5c191946 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This probably should be discussed on the mailing list rather than as a= n issue.

Aren't there privacy concerns here? One could imagine a DNS like mappi= ng from SNI to connection ID similar to a stateless retry, but where a SN= I drives the retry. This could be a sort-of separate service external to = QUIC.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b279e0fa74cd_65342adf9d4a2f5c191946-- From nobody Mon Jun 18 05:03:39 2018 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 BF41E130EA5 for ; Mon, 18 Jun 2018 05:03:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zxoVbDbaiUaP for ; Mon, 18 Jun 2018 05:03:37 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57352130E96 for ; Mon, 18 Jun 2018 05:03:37 -0700 (PDT) Date: Mon, 18 Jun 2018 05:03:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529323416; bh=cZ0IFuYhvnRqpIR8brewObnmOuGPB2Mbb9Cit6nFjRw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PiFTk87DpHlol4dFpVpADk1c/twkL+3aFdkZn4ClQ5zsgJALGWAJdlzUBCSE6bmVT BmpkiDnf21PHJvEMLwf9P2J8i9MDDVO7A/mgQ/tFTWhqmwDUP5gbeAv81XPRn8nozU zsn4sucSiGOYfkMRJ+UVh+zq0VQdWvVpNB3AqXzQ= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b279f988bf77_73d73ff644322f88332182"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 18 Jun 2018 12:03:39 -0000 ----==_mimepart_5b279f988bf77_73d73ff644322f88332182 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit But I think you are right that QUIC should much more prominently document such a rekeying requirement. For example that a key update MUST happen no later than after 2^32 packet exhanges or earlier if specific AEAD mode requires this (but such modes probably shouldn't be permitted). While some crypto modes could surve much more than 2^32 other modes would eventually fail badly (AES-GCM). By forcing an update no later than 2^32 it is easy to avoid implementation mistakes and for the peer to do a hard disconnect if keys are not updated. Silent crypto errors are really bad. -- 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/1405#issuecomment-398031584 ----==_mimepart_5b279f988bf77_73d73ff644322f88332182 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

But I think you are right that QUIC should much more prominently docum= ent such a rekeying requirement. For example that a key update MUST happe= n no later than after 2^32 packet exhanges or earlier if specific AEAD mo= de requires this (but such modes probably shouldn't be permitted).

While some crypto modes could surve much more than 2^32 other modes wo= uld eventually fail badly (AES-GCM). By forcing an update no later than 2= ^32 it is easy to avoid implementation mistakes and for the peer to do a = hard disconnect if keys are not updated. Silent crypto errors are really = bad.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b279f988bf77_73d73ff644322f88332182-- From nobody Mon Jun 18 05:24:31 2018 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 BECA2130EBF for ; Mon, 18 Jun 2018 05:24:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bw53JpoLVPT7 for ; Mon, 18 Jun 2018 05:24:28 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C322130EBD for ; Mon, 18 Jun 2018 05:24:28 -0700 (PDT) Date: Mon, 18 Jun 2018 05:24:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529324667; bh=g+q6KQPRVcBDC2UGbVwqhyWFINUuTaNMzh+A+xhaYm0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mFKJPgXWOC4Vw/ZeDCXimgcXO5IMz81vxCB0tI3f870RzVPpBbStAYgt6U5TQWWj8 2/lb83mN+FPUEbT4DHwN8DBAR3LzNkJwhZQYzHrvbLL1Az08kk/r1LGzbY/UDWdm1H rJhF8dfY0aCtGA1llfxPxVW+sLTwcj8zmR6DIL+E= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] SNI encryption (#795) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27a47b40d54_27b42add28938f5c3637ae"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 18 Jun 2018 12:24:30 -0000 ----==_mimepart_5b27a47b40d54_27b42add28938f5c3637ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My feeling is we've officially punted this to the TLS WG and I expect we'll do whatever they do, so the TLS WG is probably a better forum to discuss this, but as MikkelFJ said on the other issue, feel free to email the list. I'm also not 100% clear on how you're using SNI in a NAT. Is there a full explanation somewhere? -- 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/795#issuecomment-398036461 ----==_mimepart_5b27a47b40d54_27b42add28938f5c3637ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

My feeling is we've officially punted this to the TLS WG and I expect = we'll do whatever they do, so the TLS WG is probably a better forum to di= scuss this, but as MikkelFJ said on the other issue, feel free to email t= he list.

I'm also not 100% clear on how you're using SNI in a NAT. Is there a = full explanation somewhere?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b27a47b40d54_27b42add28938f5c3637ae-- From nobody Mon Jun 18 05:44:03 2018 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 15912130EDB for ; Mon, 18 Jun 2018 05:43:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 m41UGtd98j46 for ; Mon, 18 Jun 2018 05:43:55 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C963B130DDD for ; Mon, 18 Jun 2018 05:43:54 -0700 (PDT) Date: Mon, 18 Jun 2018 05:43:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529325834; bh=7PNFo1yXmslPCnxYW4o5wYfMp/8xMWN0vFHcMgRwtxs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z23/T3zC6hmkoqrXUuPXkKwPAlgQDOGHH1DEcp/chtZJbPW44dkwy0qaXIgxjIZwG mDeWCRaetOUJ97bPn29vwJ85GaNR81xyuNXQ6c8XrGDzQMQh94YVvuvGttWP8otx4W Xi2/rPxw1YyV+tEnLIrWqFdjmfTfuOJWPxFxvkZE= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27a90a1c6f5_19823fb466efaf88244f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 12:44:00 -0000 ----==_mimepart_5b27a90a1c6f5_19823fb466efaf88244f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul >> As discussed in #1439 (comment), my understanding is that the ECN support in the form proposed in #1372 is the only issue that makes duplicate detection a requirement rather than an option. > > So, do I assume correctly, that you will still throw away packets that are several RTTs old, i.e. that have a PN number older than any state? Or do you generate an ACK for that old packet that is so old, and try to find if there is any unconsumed buffers to put any data in? My argument is that doing either would be fine. > I looked through the frame types and the only ones that I think have some impact are: > * Path_Challenge: A non duplication detecting receiver, will issue two Path_Response frames in response to a single PN. The sender of the Path_Challenge should not react badly to this. My understanding is that the following statement in the transport draft section 5 covers this: "All QUIC frames are idempotent. That is, a valid frame does not cause undesirable side effects or errors when received more than once." > I would note that AES-GCM do have this weakness (Fergueson http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/comments/CWC-GCM/Ferguson2.pdf) that if one manage to know that one successfully forged a packet so that it passed the authentication verification, then one learns a number of bits of the authentication key, making the next forgery simpler. If it is possible to run such an attack by sending modified duplicates with forged authentication tags resulting in a response, then this can be exploited (https://link.springer.com/chapter/10.1007/978-3-319-31517-1_7). If such attack is possible, it would be a vulnerability of the AEAD algorithm. It would be unrelated to if we detect duplicates. It is the task of the AEAD to provide authentication. > I also noted that when we discussed this at the Interim it appeared that most, if not all except @kazuho was thinking that duplication suppression was expected in the receiver. If this is not required, then think the actual requirements on each frame type individually needs to be very clear. My understanding is that the discussion was based on our understanding (at that point) that duplication detection on the receiver is a prerequisite for ECN to work, and that we did not agree on how strictly we should require that to be implemented on the receiver. Considering that, I think that it would be fair to argue for looking into if duplication detection is actually required, considering the fact that now we now that ECN can be supported without it. -- 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/1405#issuecomment-398041417 ----==_mimepart_5b27a90a1c6f5_19823fb466efaf88244f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

As discussed in #1439 (comment), my understanding is that the ECN support in the for= m proposed in #13= 72 is the only issue that makes duplicate detection a requirement rat= her than an option.

So, do I assume correctly, that you will still throw away packets that= are several RTTs old, i.e. that have a PN number older than any state? O= r do you generate an ACK for that old packet that is so old, and try to f= ind if there is any unconsumed buffers to put any data in?

My argument is that doing either would be fine.

I looked through the frame types and the only ones that I think have s= ome impact are:

  • Path_Challenge: A non duplication detecting receiver, will issue two = Path_Response frames in response to a single PN. The sender of the Path_C= hallenge should not react badly to this.

My understanding is that the following statement in the transport draf= t section 5 covers this: "All QUIC frames are idempotent. That is, a vali= d frame does not cause undesirable side effects or errors when received m= ore than once."

I would note that AES-GCM do have this weakness (Fergueson http://csrc.nist.gov/groups/ST/toolkit/BCM/d= ocuments/comments/CWC-GCM/Ferguson2.pdf) that if one manage to know t= hat one successfully forged a packet so that it passed the authentication= verification, then one learns a number of bits of the authentication key= , making the next forgery simpler. If it is possible to run such an attac= k by sending modified duplicates with forged authentication tags resultin= g in a response, then this can be exploited (https://li= nk.springer.com/chapter/10.1007/978-3-319-31517-1_7).

If such attack is possible, it would be a vulnerability of the AEAD al= gorithm. It would be unrelated to if we detect duplicates. It is the task= of the AEAD to provide authentication.

I also noted that when we discussed this at the Interim it appeared th= at most, if not all except @kazuho was t= hinking that duplication suppression was expected in the receiver. If thi= s is not required, then think the actual requirements on each frame type = individually needs to be very clear.

My understanding is that the discussion was based on our understanding= (at that point) that duplication detection on the receiver is a prerequi= site for ECN to work, and that we did not agree on how strictly we should= require that to be implemented on the receiver.

Considering that, I think that it would be fair to argue for looking i= nto if duplication detection is actually required, considering the fact t= hat now we now that ECN can be supported without it.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27a90a1c6f5_19823fb466efaf88244f3-- From nobody Mon Jun 18 05:44:54 2018 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 48E12130E9A for ; Mon, 18 Jun 2018 05:44:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 4krxwGCJpIcu for ; Mon, 18 Jun 2018 05:44:50 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 DB17812F1A6 for ; Mon, 18 Jun 2018 05:44:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=wFt3K3TYEh9/dD5aDhQnF4Jhe1k=; b=fNauSZdrQCPuaPtJ tEHnOAy0aZokV27vOJmzkjBmN7+Br0OuFYdap5v7YGRLg2waCNWkQuFQHDcgphHS LBeoEb/y0RWFUaSOmi/u+fkeMXvnaBUbRPk+e8T2mh9A13F7iqzGMYjADJuf81Jh Q8BAQHnyUEcukFmJZlaQYAhomgY= Received: by filter1049p1las1.sendgrid.net with SMTP id filter1049p1las1-11010-5B27A93F-1 2018-06-18 12:44:47.081228234 +0000 UTC Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0011p1iad2.sendgrid.net (SG) with ESMTP id hA_mV0eEQR2AYzBbBsGdug for ; Mon, 18 Jun 2018 12:44:46.817 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id EB7EE3E02E0 for ; Mon, 18 Jun 2018 05:44:46 -0700 (PDT) Date: Mon, 18 Jun 2018 12:44:47 +0000 (UTC) From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Clarify and strengthen key update requirements (#1457) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27a93eea07a_5062b03cf454f54907be"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2N9Qx4/0CxV8hvDu+CaeAwOgsB5hs/xjY7aB KryM/iuS/Xao4qsjC+GY/1VFKpRoSjslqLPPF3aZGYR4428HNP13PBmWMrbmJCK72xgB3JnH4bP9YH NuO1upgS2EoW6AJQWqCjPnR7jNubUjrhOWM4rwJ37kfwzMB5wrcYkj0dog== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:44:53 -0000 ----==_mimepart_5b27a93eea07a_5062b03cf454f54907be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit >From several discussions it appears that the importance of key updates are not well understand and the consequences can be fatal. The requirement are in place via numerous indirect links over TLS 1.3 spec and further documents. Some crypto modes can handle a large number of pakcets safely while others break down statistically, including AES-GCM. A solution could be to require key updates no later than after 2^32 packets and require a protocol error shutdown if peer does not rekey in time. While 2^32 may be early in some cases, it is not realy burden, and the alternative might be that implementations skip handling key updates. See also discussion here: https://github.com/quicwg/base-drafts/issues/1405#issuecomment-398022746 -- 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/1457 ----==_mimepart_5b27a93eea07a_5062b03cf454f54907be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

From several discussions it appears that the importance of key updates are not well understand and the consequences can be fatal. The requirement are in place via numerous indirect links over TLS 1.3 spec and further documents.

Some crypto modes can handle a large number of pakcets safely while others break down statistically, including AES-GCM.

A solution could be to require key updates no later than after 2^32 packets and require a protocol error shutdown if peer does not rekey in time. While 2^32 may be early in some cases, it is not realy burden, and the alternative might be that implementations skip handling key updates.

See also discussion here:
#1405 (comment)

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

----==_mimepart_5b27a93eea07a_5062b03cf454f54907be-- From nobody Mon Jun 18 05:45:16 2018 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 2131E130DDD for ; Mon, 18 Jun 2018 05:45:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 wYhXs2KXVAYd for ; Mon, 18 Jun 2018 05:45:09 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 786D812F1A6 for ; Mon, 18 Jun 2018 05:45:09 -0700 (PDT) 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=vuKiQqzWSy8fMzwaYezjw0BzqMU=; b=kn2cORYruFhh9wP/ lgoYaaMET5wU45pJUP9GpgBiM7Fwn0yUHREYhIxYI0xNnp5r1mIAwy3k4AEJCcsT NOpce6DkqaFd88/asGycsCGV14lYjO4VrsfzvkQt3BvVRoSSdV7sD4tEWBa7t3PH UyfML9r7y5t22ymMAIHvp6j2C9I= Received: by filter0326p1iad2.sendgrid.net with SMTP id filter0326p1iad2-3778-5B27A954-F 2018-06-18 12:45:08.215599286 +0000 UTC Received: from github-lowworker-5909e27.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id rtGl8HBPSs2_GpMt2gfySg for ; Mon, 18 Jun 2018 12:45:08.177 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-5909e27.cp1-iad.github.net (Postfix) with ESMTP id 287863E1A36 for ; Mon, 18 Jun 2018 05:45:08 -0700 (PDT) Date: Mon, 18 Jun 2018 12:45:08 +0000 (UTC) From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27a95426552_29562aab3dbf2f589911d"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1+KcnrEy5pX6LzFcwoALR1B2vgXCrcg4YIpd 9qJYBWUjk58C8ONK6EdEXqQt1dbdrJ7XWz29VC4tpQGz8l5CUH73V1PMzxBGRh6WB28j8St/hRPExp 1+TwKbcYkDjNhDPfNz95/m/IXymQBvS4In5Yozap8S5NNOypeIZcVppecPWsHsy5NLHi3PQr3IfJUJ I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:45:15 -0000 ----==_mimepart_5b27a95426552_29562aab3dbf2f589911d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Would a forward proxy approach help alleviate your concerns? @bemasc and I are putting together some ideas on how a User Agent could explicitly opt-in to passing non-TCP traffic via a proxy, in a similar way to how HTTP proxies work now. This takes place after secure session establishment. -- 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/1456#issuecomment-398041749 ----==_mimepart_5b27a95426552_29562aab3dbf2f589911d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Would a forward proxy approach help alleviate your concerns?

@bemasc and I are putting together some = ideas on how a User Agent could explicitly opt-in to passing non-TCP traffi= c via a proxy, in a similar way to how HTTP proxies work now. This takes pl= ace after secure session establishment.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b27a95426552_29562aab3dbf2f589911d-- From nobody Mon Jun 18 05:49:55 2018 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 679B3130EBF for ; Mon, 18 Jun 2018 05:49:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 y3CLADKsImGG for ; Mon, 18 Jun 2018 05:49:49 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D36E8126DBF for ; Mon, 18 Jun 2018 05:49:49 -0700 (PDT) Date: Mon, 18 Jun 2018 05:49:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529326189; bh=1fUpJ7QPUnLy2lVjvrZT6+wV+BSJxrSoGt0J23pu6yY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=h8DAZXW+IcPA+uHOJ/ej4E6Z8Fe3T+YU6JFnmrlPRbtOfu1wj7Qw/gXYHKoXDdbv5 JhMZAsMzW19aMFpeiZ15YlJAZOARYSgSPmPiEpzF3ZXwsy/2xHduMcKL6GlJ/Vf4Xp kixtYBZZBCjsQfWpPx/XYV2JM8tToL6T1GeBY7js= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27aa6d2b6d6_223e2b14f7640f50113499"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 12:49:53 -0000 ----==_mimepart_5b27aa6d2b6d6_223e2b14f7640f50113499 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The main point I like to stress, is that there will be a number of long lived connections that never will rekey if they are only based on sent packets. Even if one send 136 packets per second, the sender rekeys only once every year. And there are plenty of applications that will send less than a packet a second on average. The attack outlined is not affecting the number of sent packets by the sender in any significant way, it will only result in sending a lot of packets to the receiver and watch for signs of successful forgery by monitoring what the receiver emits back to the sender. Thus, if one can send 10000 packets a second to the receiver, then one will have had the possibility of sending ~2^38 packet by the time of rekeying. So still a low probability of success but not insignificant. -- 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/1405#issuecomment-398042975 ----==_mimepart_5b27aa6d2b6d6_223e2b14f7640f50113499 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The main point I like to stress, is that there will be a number of lon= g lived connections that never will rekey if they are only based on sent = packets. Even if one send 136 packets per second, the sender rekeys only = once every year. And there are plenty of applications that will send less= than a packet a second on average. The attack outlined is not affecting = the number of sent packets by the sender in any significant way, it will = only result in sending a lot of packets to the receiver and watch for sig= ns of successful forgery by monitoring what the receiver emits back to th= e sender. Thus, if one can send 10000 packets a second to the receiver, t= hen one will have had the possibility of sending ~2^38 packet by the time= of rekeying. So still a low probability of success but not insignificant= .

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27aa6d2b6d6_223e2b14f7640f50113499-- From nobody Mon Jun 18 06:00:07 2018 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 93CAE130DE2 for ; Mon, 18 Jun 2018 06:00:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 q8Q3gB3NUCnt for ; Mon, 18 Jun 2018 06:00:02 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2E2F126DBF for ; Mon, 18 Jun 2018 06:00:01 -0700 (PDT) Date: Mon, 18 Jun 2018 06:00:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529326800; bh=01ZuEpga1qbmpl03UwNhTQ/y/LqBgkcPmyKxaHKJkOU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bYTk+p9wH7ZfR2JojxANWpsxwSmfgwVF1WASX1y5lUnCii0vSx/PM/JE2/LBTQ+Rm Ar3OEkTxAQw40FN8bWObTInrBt7E/XZZawKTjAmfQZ0bx1yDTkxdXWg/JG2R+epZ4P mbZOnEVMxojvWO7s6Ns9gm2iEP8dC8s3cwCszIqc= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27acd0df70a_203403fa77b588f88977c7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 18 Jun 2018 13:00:06 -0000 ----==_mimepart_5b27acd0df70a_203403fa77b588f88977c7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A forward proxy is useful but it cannot safely operate at the cloud provider level load balancer because privacy is compromised. -- 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/1456#issuecomment-398045612 ----==_mimepart_5b27acd0df70a_203403fa77b588f88977c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

A forward proxy is useful but it cannot safely operate at the cloud provider level load balancer because privacy is compromised.

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

----==_mimepart_5b27acd0df70a_203403fa77b588f88977c7-- From nobody Mon Jun 18 06:27:13 2018 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 78019130DE5 for ; Mon, 18 Jun 2018 06:27:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7WRoTWTspep0 for ; Mon, 18 Jun 2018 06:27:09 -0700 (PDT) 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 A98B4130DE2 for ; Mon, 18 Jun 2018 06:27:09 -0700 (PDT) Date: Mon, 18 Jun 2018 06:27:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529328428; bh=v5iGiZnHdJiaomrNwEJq37GHbausBjj4JTqayzcDV/k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LnrOOhunbV2AKMS5v52tog3VfJxAqdkzv+4oQFJxBYcrFpwD0InfF04yRd0xpAIiY ZZP1DlcZPgkSfzxo7L17uxD1NHzSTC1tKWfpbSE+H3oEj9gFVGLx7ig22w33IRJ05f QUB/xLFygYaAZKBTERBAfxirh6VY+Tqaqr8rIcN0= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b32c932a5_5ec2b09bc392f601648c3"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 13:27:12 -0000 ----==_mimepart_5b27b32c932a5_5ec2b09bc392f601648c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I guess it depends where the exhaustion concerns are. A reverse proxy for the cloud case, i.e. a request router, is something I'm familiar with. Some have scalability concerns with these. -- 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/1456#issuecomment-398053344 ----==_mimepart_5b27b32c932a5_5ec2b09bc392f601648c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I guess it depends where the exhaustion concerns are.

A reverse proxy for the cloud case, i.e. a request router, is something I'm familiar with. Some have scalability concerns with these.

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

----==_mimepart_5b27b32c932a5_5ec2b09bc392f601648c3-- From nobody Mon Jun 18 06:27:35 2018 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 B2ACC130DE2 for ; Mon, 18 Jun 2018 06:27:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pzoHbhegBqxO for ; Mon, 18 Jun 2018 06:27:30 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A22C812F1A5 for ; Mon, 18 Jun 2018 06:27:30 -0700 (PDT) Date: Mon, 18 Jun 2018 06:27:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529328450; bh=8SSjBdHGRgZvSHoT9HAH9nu1ZBxShJpsOu9EAHZSDHs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hvqEz6auMQPn3C1ua/NwLAWmmmiRJXwIDL2Max125YPDOpuZuCh3wdfVyK4L7uzyR sLH41HSr3q9L21DhCmDVXY4r/3wA9De79RKuXwB8TztMwBfatVJXlG9TVXtK7sSODm 77M5XEMYFjLUuG3wzx5gCySVu5IO2t2gVPvH/0fo= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b342d4b5_7b073faa1435ef781918d8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 13:27:33 -0000 ----==_mimepart_5b27b342d4b5_7b073faa1435ef781918d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit An important clarification about this attack: The attack on AES-GCM is definitely valid for truncated authentication tags. However, my co-author clarified to me that this is not an issue for untruncated tags. So as long as QUIC uses 128 bit authentication tags for AES-GCM we should have no issue from a cryptographic perspective. I still think not having any requirement on replay protection at the main protocol level puts a lot of responsibility on the designers of extensions as well as implementers to ensure that things truly are idempotent when sent input. @kazuho > My understanding is that the following statement in the transport draft section 5 covers this: "All QUIC frames are idempotent. That is, a valid frame does not cause undesirable side effects or errors when received more than once." This text is only in master and was not in -12, so I didn't see it at the time I wrote the ECN PR. I think the extensibility text probably needs an RFC 2119 requirement on that any new frame types needs to fulfill that requirement. But, to fulfill that for ECN, at least if there are no strict requirement on duplication suppression do requires the ECN specification to change. Either to do receiver side suppression of the ECN field value so that it doesn't matter, or change the encoding so that one handles the duplicated packets correctly. -- 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/1405#issuecomment-398053419 ----==_mimepart_5b27b342d4b5_7b073faa1435ef781918d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

An important clarification about this attack: The attack on AES-GCM is= definitely valid for truncated authentication tags. However, my co-autho= r clarified to me that this is not an issue for untruncated tags. So as l= ong as QUIC uses 128 bit authentication tags for AES-GCM we should have n= o issue from a cryptographic perspective.

I still think not having any requirement on replay protection at the m= ain protocol level puts a lot of responsibility on the designers of exten= sions as well as implementers to ensure that things truly are idempotent = when sent input.

@kazuho

My understanding is that the following statement in the transport draf= t section 5 covers this: "All QUIC frames are idempotent. That is, a vali= d frame does not cause undesirable side effects or errors when received m= ore than once."

This text is only in master and was not in -12, so I didn't see it at = the time I wrote the ECN PR. I think the extensibility text probably need= s an RFC 2119 requirement on that any new frame types needs to fulfill th= at requirement. But, to fulfill that for ECN, at least if there are no st= rict requirement on duplication suppression do requires the ECN specifica= tion to change. Either to do receiver side suppression of the ECN field v= alue so that it doesn't matter, or change the encoding so that one handle= s the duplicated packets correctly.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27b342d4b5_7b073faa1435ef781918d8-- From nobody Mon Jun 18 06:32:53 2018 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 C5285130F15 for ; Mon, 18 Jun 2018 06:32:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 u2-XETlH0maX for ; Mon, 18 Jun 2018 06:32:39 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1507130ED2 for ; Mon, 18 Jun 2018 06:32:39 -0700 (PDT) Date: Mon, 18 Jun 2018 06:32:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529328758; bh=0K0lGN8RnYyubcZhGDyfYHrLNHdf0n3Zil8Eed+OeUs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RheY14EoEYSiUODYuUHPEptaOgwjDzey8xwZ0lGpanbHzwrCtPJUq0sG/5IrKw8bs lAzSSPZLMlzQI91lLcQ5ao0st23AF7TxpcmmpVz2wZJ6497PR0VsOe7DIP/CllCWjS XNNd6lC3KiJn8EUvV59mnkRiDU/qmcDXCotF8IbI= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b476a6cd3_2a893f7e49070f887173e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 13:32:52 -0000 ----==_mimepart_5b27b476a6cd3_2a893f7e49070f887173e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul > Okay, if that is the general principle to make this work, you can't only provide CE to PN mappings. You need to indicate which packets get ECT or not-ECT marks also. i.e. you need to provide the ECN field value for all the packets included in the ACK. Then the other mechanisms needed for ECN than congestion event detection also will work. @gloinul > Okay, if that is the general principle to make this work, you can't only provide CE to PN mappings. You need to indicate which packets get ECT or not-ECT marks also. i.e. you need to provide the ECN field value for all the packets included in the ACK. Then the other mechanisms needed for ECN than congestion event detection also will work. That's a fair point. And I think that the two approaches being discussed in this issue are capable of carrying the necessary signal. In [the bit-vector approach](https://github.com/quicwg/base-drafts/issues/1439#issuecomment-396433945), assuming that only the distinction between three types (i.e. non-ECT, ECT, ECT-CE) is necessary, a receiver can send an ACK frame (instead of an ACK_ECN frame) when it receives a packet (that carries a not-yet-processed PN) with a non-ECT mark. ACK_ECN frame that carries the bit vector (that uses 1-bit per PN showing the distinction between ECT and ECT-CE) will be used only when all the packets that the receiver has received with one of the ECT flags set are being acknowledged. In the ACK-block-with-mode approach ([1](https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397133920), [2](https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397157328), [3](https://github.com/quicwg/base-drafts/issues/1439#issuecomment-397593919)), all 4 types (ECT, ECT(0), ECT(1), ECT-CE) are carried in the ACK frame for each PN. > So in regards to duplicated packets, what is your policy for handling that truly when a receiver don't suppress the duplicate prior to ECN processing? The "sender" of the packet uses the ECN information that was first reported for the PN that it has sent, which is provided by ACK (or ACK_ECN) frame that is sent back from the receiver. This is very simple to implement, because a sender iterates though the PNs found in an ACK frame to see if each of them has been newly reported, to process acknowledgements. > So beyond the primary purpose of ECN to detect congestion events, the mechanism needs to have capability also to: > * Detect working paths Assuming that you are referring to ECN blackhole, this is something that can be detected in either of the two schemes proposed in this PR. Note that you can detect a blackhole in any ECN scheme, because not seeing an ACK for a packet that was sent with a ECN flag is the signal we will be looking for. > * Detect bleaching in mid-connection This can be done in either of the two schemes proposed in this PR. Please refer to the discussion on top of this comment. > * Detect working path after connection migration This would be indifferent from the process we would run for the initial path. > * Mitigate attacks, at least off-path or on-side attacks. On path attackers can cause the same response as well as additional issues by dropping packets for a connection. I agree that we do not need to care about on-path attacks. My understanding is that for off-path and on-side attacks, detecting duplicates on the "sender" side is sufficient. Besides, note that I am not opposed to implementations detecting duplicates on the receiver-side. In fact, we can expect that even a naive QUIC stack, would delay sending an ACK. And if such stack receives a packet that carries the same PN as one that is found in the ACK queue, it can discard the newly received packet along with the ECN information. Let me restate that transmitting PNs along with their ECN bits has benefits. It improves the quality of the signal at the same time simplifying the sender code (because the sender can accurately tell which packet carried which ECN flag), and also has the chance of making the ACK frame encoding smaller / simpler. -- 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/1439#issuecomment-398055003 ----==_mimepart_5b27b476a6cd3_2a893f7e49070f887173e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

Okay, if that is the general principle to make this work, you can't on= ly provide CE to PN mappings. You need to indicate which packets get ECT = or not-ECT marks also. i.e. you need to provide the ECN field value for a= ll the packets included in the ACK. Then the other mechanisms needed for = ECN than congestion event detection also will work.

@gloinul

Okay, if that is the general principle to make this work, you can't on= ly provide CE to PN mappings. You need to indicate which packets get ECT = or not-ECT marks also. i.e. you need to provide the ECN field value for a= ll the packets included in the ACK. Then the other mechanisms needed for = ECN than congestion event detection also will work.

That's a fair point. And I think that the two approaches being discuss= ed in this issue are capable of carrying the necessary signal.

In the bit-vector approach, assuming that only the dis= tinction between three types (i.e. non-ECT, ECT, ECT-CE) is necessary, a = receiver can send an ACK frame (instead of an ACK_ECN frame) when it rece= ives a packet (that carries a not-yet-processed PN) with a non-ECT mark. = ACK_ECN frame that carries the bit vector (that uses 1-bit per PN showing= the distinction between ECT and ECT-CE) will be used only when all the p= ackets that the receiver has received with one of the ECT flags set are b= eing acknowledged.

In the ACK-block-with-mode approach (1, 2<= /a>, 3), all 4 types (ECT, ECT(0), ECT(1), ECT-CE) are ca= rried in the ACK frame for each PN.

So in regards to duplicated packets, what is your policy for handling = that truly when a receiver don't suppress the duplicate prior to ECN proc= essing?

The "sender" of the packet uses the ECN information that was first rep= orted for the PN that it has sent, which is provided by ACK (or ACK_ECN) = frame that is sent back from the receiver.

This is very simple to implement, because a sender iterates though the= PNs found in an ACK frame to see if each of them has been newly reported= , to process acknowledgements.

So beyond the primary purpose of ECN to detect congestion events, the = mechanism needs to have capability also to:

  • Detect working paths

Assuming that you are referring to ECN blackhole, this is something th= at can be detected in either of the two schemes proposed in this PR. Note= that you can detect a blackhole in any ECN scheme, because not seeing an= ACK for a packet that was sent with a ECN flag is the signal we will be = looking for.

  • Detect bleaching in mid-connection

This can be done in either of the two schemes proposed in this PR. Ple= ase refer to the discussion on top of this comment.

  • Detect working path after connection migration

This would be indifferent from the process we would run for the initia= l path.

  • Mitigate attacks, at least off-path or on-side attacks. On path attac= kers can cause the same response as well as additional issues by dropping= packets for a connection.

I agree that we do not need to care about on-path attacks. My understa= nding is that for off-path and on-side attacks, detecting duplicates on t= he "sender" side is sufficient.

Besides, note that I am not opposed to implementations detecting dupli= cates on the receiver-side. In fact, we can expect that even a naive QUIC= stack, would delay sending an ACK. And if such stack receives a packet t= hat carries the same PN as one that is found in the ACK queue, it can dis= card the newly received packet along with the ECN information.

Let me restate that transmitting PNs along with their ECN bits has ben= efits. It improves the quality of the signal at the same time simplifying= the sender code (because the sender can accurately tell which packet car= ried which ECN flag), and also has the chance of making the ACK frame enc= oding smaller / simpler.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27b476a6cd3_2a893f7e49070f887173e-- From nobody Mon Jun 18 06:34:07 2018 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 0E23B130DE7 for ; Mon, 18 Jun 2018 06:34:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 RuwoLvj092sN for ; Mon, 18 Jun 2018 06:34:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D996130DE2 for ; Mon, 18 Jun 2018 06:34:03 -0700 (PDT) Date: Mon, 18 Jun 2018 06:34:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529328842; bh=mpMcQlAJ+EBAk5Dn4tIAgzHR2kUD0KlJe+EPYfiRHOE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a8omnFiJwY0aSiRtwe4HPGDhFVyZlZSO2b0MWyjU8AM2ZNl3kjEkW5+kd5hX4VgLu BWmCDMG5LRGswPy500E0TXD4V/jooPF5gliragLqHPcPHnONHa3y5XrfLsSh1HSdg5 AMlW8EDXWvtaThlAtO6SO/5bMGlXPLGbJmkM2dvc= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b4cad2ba5_18652b04aa902f5c615be"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 13:34:06 -0000 ----==_mimepart_5b27b4cad2ba5_18652b04aa902f5c615be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Based on the discussion in #1405 and the text that is in master branch towards next version requiring frame types to be idempotent I will add text so that the ACK_ECN frame will have this property even if packet duplication occurs. I will do so in what I consider a straight forward and simple way. I will require that only the first received ECN field for an packet number is added to the counters. This should be straightforward as the receiver's ACK data structure should allow one to determine if a packet is older than anything retained, new or duplicate. -- 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/1372#issuecomment-398055463 ----==_mimepart_5b27b4cad2ba5_18652b04aa902f5c615be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Based on the discussion in #1405 and the text that is in master branch towards ne= xt version requiring frame types to be idempotent I will add text so that= the ACK_ECN frame will have this property even if packet duplication occ= urs. I will do so in what I consider a straight forward and simple way. I= will require that only the first received ECN field for an packet number= is added to the counters. This should be straightforward as the receiver= 's ACK data structure should allow one to determine if a packet is older = than anything retained, new or duplicate.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b27b4cad2ba5_18652b04aa902f5c615be-- From nobody Mon Jun 18 06:36:47 2018 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 876FC130DEC for ; Mon, 18 Jun 2018 06:36:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jwck9p_s3jXS for ; Mon, 18 Jun 2018 06:36:44 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E7D9130DE2 for ; Mon, 18 Jun 2018 06:36:44 -0700 (PDT) Date: Mon, 18 Jun 2018 06:36:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529329003; bh=vYHdbrE/qTCizsLAzIAgrbfhVBf2TFq2vz8P17t9HQA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n8LGF8NQSQMyrwrUDZI/j9RIN9TuPTUrB1zAvF8P9yafDBdczBA2FaPpyVCMB6igX tzHg80+CcOVxPQgvmoCjvBx3beHJNSPrPofkJM+XyqNO7+OmP3Jw3EH/+DlEcMnkd5 D6d9TejcP20jl4KrvLNEXIWaWNdpwJR2Ti7kULKk= From: mirjak Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b56bd64b_527c3f8ea1a58f882005eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mirjak 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.26 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, 18 Jun 2018 13:36:46 -0000 ----==_mimepart_5b27b56bd64b_527c3f8ea1a58f882005eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually if possible, CE should never be ignored because a network node setting CE does not know if a packet is a duplicate or not... -- 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/1372#issuecomment-398056289 ----==_mimepart_5b27b56bd64b_527c3f8ea1a58f882005eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Actually if possible, CE should never be ignored because a network node setting CE does not know if a packet is a duplicate or not...

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

----==_mimepart_5b27b56bd64b_527c3f8ea1a58f882005eb-- From nobody Mon Jun 18 06:39:43 2018 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 223B4130EC6 for ; Mon, 18 Jun 2018 06:39:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 XXKhrvpsvknH for ; Mon, 18 Jun 2018 06:39:32 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2018D130ED7 for ; Mon, 18 Jun 2018 06:39:32 -0700 (PDT) Date: Mon, 18 Jun 2018 06:39:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529329171; bh=cQnnDyg78hZuaKAm3vGwMSyTDJ3mHLBl8ABx4Kw8/p4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ieg/qogrJ5gHU1Ru62zXaNHsu6CF/5QHwLYoQtlAQcXuv+Rg2Yl/J9yspAuTSa/zV xe6oTVcHoKHAB7fDeck1QA1mFjdaNFj8PMKnMvxYSRx7S3Vju3KN3M74LXWyOtCJoL V1pUjAqDv5HyJ8UjqmwTDAFNpCT9N5736bcJ6l2g= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b61379a00_1c30c3fc489910f7c89449"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 13:39:42 -0000 ----==_mimepart_5b27b61379a00_1c30c3fc489910f7c89449 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul > But, to fulfill that for ECN, at least if there are no strict requirement on duplication suppression do requires the ECN specification to change. That's correct. Duplication suppression will be required if we adopt the encoding proposed in #1372. I am merely pointing out that #1372 is the only thing that requires suppression, and that we have a chance of dropping the requirement if we adopt an alternative encoding as we have been discussing in #1439. -- 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/1405#issuecomment-398057102 ----==_mimepart_5b27b61379a00_1c30c3fc489910f7c89449 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul

But, to fulfill that for ECN, at least if there are no strict requirem= ent on duplication suppression do requires the ECN specification to chang= e.

That's correct. Duplication suppression will be required if we adopt t= he encoding proposed in #1372.

I am merely pointing out that #1372 is the only thing that requires suppression, an= d that we have a chance of dropping the requirement if we adopt an altern= ative encoding as we have been discussing in #1439.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27b61379a00_1c30c3fc489910f7c89449-- From nobody Mon Jun 18 06:45:09 2018 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 74104130DE5 for ; Mon, 18 Jun 2018 06:45:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 MIJGC4qmQRXF for ; Mon, 18 Jun 2018 06:45:03 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 34933124C04 for ; Mon, 18 Jun 2018 06:44:57 -0700 (PDT) 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=haTBojl62zg5fjLtB1u/r8/yt2Y=; b=PM0IOJKgA9ButYtU GiIbVlcumkhPtAFDnFIJ12B4nGSs4bDuOTiF6QJCjX2zaLsyy6eoX0EkwMYbKH79 SQ2D9NJ2AG9FQ7V4Fvqy13xeyEiWMy3RX0zlNC05nlziaZt7BiK6HYYIp2GNEfdy 0WMgNwfxWeXbcm9aBI3K4o/6gHY= Received: by filter0601p1iad2.sendgrid.net with SMTP id filter0601p1iad2-15673-5B27B754-3A 2018-06-18 13:44:52.971230448 +0000 UTC Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id QMSdtr-MQ8W2hvccsNwItQ for ; Mon, 18 Jun 2018 13:44:52.929 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id E0F92C041F for ; Mon, 18 Jun 2018 06:44:52 -0700 (PDT) Date: Mon, 18 Jun 2018 13:44:53 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b754df537_54aa2ad119a1af5821091"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0jQ7ez+iZ6cGAVcDEsbZD6Hyf/ZfOWj1cs5d L24FNYFpn0TyUlr4QyeyXg02uwazRnPWCZ9jrhlk5GuM+UETtmZt6xlwp692ZjQ13gWhh3pXJ4YHiW 9Us3+DSLui3Nc7oYlmXkQRA1YduAGLIheYRNXloHQt4JTuWV+/TJlmFmtTCkIVLgG6xO/sF4bwjfnb s= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 13:45:07 -0000 ----==_mimepart_5b27b754df537_54aa2ad119a1af5821091 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mirjak In general, QUIC doesn't process duplicate packets and QUIC doesn't ACK anything it can't process, so ignoring duplicate marked packets matches with this model. I suspect a lot more marked packets will be dropped because they were undecryptable(ie: 0RTT) than because of duplication, since duplication is very rare in my experience, and when it does occur, it'd commonly be better to ignore the second mark anyway, since the marking would occur before the duplication. -- 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/1372#issuecomment-398058825 ----==_mimepart_5b27b754df537_54aa2ad119a1af5821091 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mirjak In general, QUIC doesn't proces= s duplicate packets and QUIC doesn't ACK anything it can't process, so igno= ring duplicate marked packets matches with this model.

I suspect a lot more marked packets will be dropped because they were un= decryptable(ie: 0RTT) than because of duplication, since duplication is ver= y rare in my experience, and when it does occur, it'd commonly be better to= ignore the second mark anyway, since the marking would occur before the du= plication.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b27b754df537_54aa2ad119a1af5821091-- From nobody Mon Jun 18 06:47:29 2018 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 1782D130DE5 for ; Mon, 18 Jun 2018 06:47:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KMHB6wTiHXlv for ; Mon, 18 Jun 2018 06:47:26 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D716124C04 for ; Mon, 18 Jun 2018 06:47:26 -0700 (PDT) Date: Mon, 18 Jun 2018 06:47:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529329645; bh=qZBYElsMEC4tMdPYWONWzjOebfjBi8XaAUo/5nfw5pU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RoSX1PXo/kRVvn2/0PWVAdFZwPl1g99s6ijsVKIffb2Xz500OTUdDav8UQD69qSti HtoGbQs+ox+AXmNDRAMeW5pJhKTUnGf5IokJnW85aFYfgIOe0TWH5DNXsytcXZE4bA cCalItDdTSpD0MSncpOgNYYoag//2s5a6dcPvq44= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27b7edc8159_78102b15fa68cf5093414"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 13:47:29 -0000 ----==_mimepart_5b27b7edc8159_78102b15fa68cf5093414 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FWIW, the QUIC-HTTP draft mandates the use of SNI. Quoting from [section 2.3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.2.3), "The Server Name Indication (SNI) extension [RFC6066] MUST be included in the TLS handshake." Though I wonder if we might want to relax the wording in possibility of having SNI encryption, to something like what we see in [RFC 7540 section 9.2](https://tools.ietf.org/html/rfc7540#section-9.2). -- 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/1456#issuecomment-398059647 ----==_mimepart_5b27b7edc8159_78102b15fa68cf5093414 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

FWIW, the QUIC-HTTP draft mandates the use of SNI. Quoting from section 2.3, "The Server Name Indication (SNI)= extension [RFC6066] MUST be included in the TLS handshake."

Though I wonder if we might want to relax the wording in possibility o= f having SNI encryption, to something like what we see in RFC 7540 se= ction 9.2.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27b7edc8159_78102b15fa68cf5093414-- From nobody Mon Jun 18 07:12:26 2018 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 513F3130DE9 for ; Mon, 18 Jun 2018 07:12:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DggGW_5Zf9Rm for ; Mon, 18 Jun 2018 07:12:21 -0700 (PDT) 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 89300124C04 for ; Mon, 18 Jun 2018 07:12:21 -0700 (PDT) Date: Mon, 18 Jun 2018 07:12:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529331140; bh=EZ1E8FhW1PRem1fn1F48l9cdvnHfLwD7+JWAdD25kOM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cuEa9jfyuu1JtNZw2BIbRxGDcTlyIc8fCbzyFDAuy/65L2N4pJqaJp2gQjNZs1zNT bT6ZBSUuOA692yXDvK8a8ybmDIyn7/urCOSO0SwNe6mEXXrAF8KyWH0EIbXBMKkAJx 918Lqk+WEPHaC85dVNPO1AI5YDSlS/xqwRwUYa9o= From: Marten Seemann Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27bdc46d536_22d62ad2239d8f5823461"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: marten-seemann 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.26 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, 18 Jun 2018 14:12:25 -0000 ----==_mimepart_5b27bdc46d536_22d62ad2239d8f5823461 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In an end-to-end protocol, we generally don't want "helpful" middleboxes to interfere with handshakes by performing a Retry (and thereby introducing latency). Obviously, this statement depends on the definition of "middlebox", which I here use as any node on the path that neither belongs to the server's nor the client's architecture. We should design QUIC's retry mechanism such that a retry can **only** be performed by devices that are under the control of the server operator. Limiting the number of retries on the client side is an insufficient solution here, since under normal conditions, the server won't perform a retry, so the client would accept the any performed by the middlebox, and only fail in the rare case when both the middlebox and the server perform a retry. I agree with @ianswett here, that any architecture that performs multiple retries for a single connection is so suboptimal for performance that you probably wouldn't want to deploy it, and I think QUIC should only support it if we can at the same time prevent retries by "helpful" middleboxes. In fact, if we only allow a single retry, the solution is straightforward: a server (or whatever device is responsible for the DoS projection) would simply reject all Initial packets that contain a token that it didn't issue itself. -- 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/1451#issuecomment-398067827 ----==_mimepart_5b27bdc46d536_22d62ad2239d8f5823461 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In an end-to-end protocol, we generally don't want "helpful" middlebox= es to interfere with handshakes by performing a Retry (and thereby introd= ucing latency). Obviously, this statement depends on the definition of "m= iddlebox", which I here use as any node on the path that neither belongs = to the server's nor the client's architecture.
We should design QUIC's retry mechanism such that a retry can onl= y be performed by devices that are under the control of the serv= er operator.

Limiting the number of retries on the client side is an insufficient s= olution here, since under normal conditions, the server won't perform a r= etry, so the client would accept the any performed by the middlebox, and = only fail in the rare case when both the middlebox and the server perform= a retry.

I agree with @ianswett here, tha= t any architecture that performs multiple retries for a single connection= is so suboptimal for performance that you probably wouldn't want to depl= oy it, and I think QUIC should only support it if we can at the same time= prevent retries by "helpful" middleboxes.
In fact, if we only allow a single retry, the solution is straightforward= : a server (or whatever device is responsible for the DoS projection) wou= ld simply reject all Initial packets that contain a token that it didn't = issue itself.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27bdc46d536_22d62ad2239d8f5823461-- From nobody Mon Jun 18 07:15:14 2018 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 A7A1E130EA6 for ; Mon, 18 Jun 2018 07:14:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Y03TCxN8vf3A for ; Mon, 18 Jun 2018 07:14:57 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE6DE130EC1 for ; Mon, 18 Jun 2018 07:14:56 -0700 (PDT) Date: Mon, 18 Jun 2018 07:14:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529331296; bh=zXfjwDfGer1J9wL4kpLJ4hKzgiVmU0oOn+ouDoQL+9E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iDa2AUH8IHsip1SJ+Ph2CCbkCvI1mpSCCPuZNMPjylGY3Qmjao22lXD5WeqXQ1JsU v6O0jbHT+EzrFgQ9vi6TFvfYWsxGpSX391Yr9l4C6vFQXtHpMF4m0kIi5kPzDjFHwe fxKiz/nNze/IiY6xRTVyLf5+tjTBicxklDWOWz1k= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27be608cb1_636e2ae0f1ac6f5011784"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 18 Jun 2018 14:15:06 -0000 ----==_mimepart_5b27be608cb1_636e2ae0f1ac6f5011784 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 2 commits. 55fa3d6 Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn e06a2a0 Added requirement on ECN marking suppression for packet duplicates. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/4af108c47fd2cbaea42b6b83c8d19f1d52513443..e06a2a0efb1e655ecd1fa4e3a8e182689a50ff54 ----==_mimepart_5b27be608cb1_636e2ae0f1ac6f5011784 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 2 commits.

  • 55fa3d6 Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • e06a2a0 Added requirement on ECN marking suppression for packet duplicates.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b27be608cb1_636e2ae0f1ac6f5011784-- From nobody Mon Jun 18 07:21:18 2018 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 21BE1120049 for ; Mon, 18 Jun 2018 07:21:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 TsUtS2y0y1yd for ; Mon, 18 Jun 2018 07:21:12 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CFFA126DBF for ; Mon, 18 Jun 2018 07:21:12 -0700 (PDT) Date: Mon, 18 Jun 2018 07:21:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529331671; bh=OErHEXBz9XkW8xpX8hEr07RicCkqajondQMlWeKKv7w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qOwIt1IsQimQWhrqukH3o3yv0FXYDOnkKaWD1FIVU5dcIfLGYgs7rjRVGxHPp3Dm3 fjG3g3I8gPfqeYqzB4tLgs/Jqi0h53In4DH0Q8wDPvWzRjriPfOl2QBejQPFadSkKH /PYLm7TLL5avuM1x7mKHfFVnQzO6pd4kL6wlv9M4= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27bfd7812a9_233d2ada7d4eef5811239"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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, 18 Jun 2018 14:21:16 -0000 ----==_mimepart_5b27bfd7812a9_233d2ada7d4eef5811239 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree that we don't want to introduce unnecessary latency but I disagree with your suggestion to only allow the end server to perform the Retry for the reasons I previously stated, and that @jmtilli built upon. I don't think we should necessarily allow an infinite number of Retry packets, but more than 2 does seem necessary to me. -- 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/1451#issuecomment-398070805 ----==_mimepart_5b27bfd7812a9_233d2ada7d4eef5811239 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I agree that we don't want to introduce unnecessary latency but I disa= gree with your suggestion to only allow the end server to perform the Ret= ry for the reasons I previously stated, and that @jmtilli built upon. I don't think we should necessarily allo= w an infinite number of Retry packets, but more than 2 does seem necessar= y to me.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27bfd7812a9_233d2ada7d4eef5811239-- From nobody Mon Jun 18 07:23:02 2018 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 59FCD12F1AC for ; Mon, 18 Jun 2018 07:23:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 81JW0KlWNPHX for ; Mon, 18 Jun 2018 07:22:57 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ED30126DBF for ; Mon, 18 Jun 2018 07:22:57 -0700 (PDT) Date: Mon, 18 Jun 2018 07:22:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529331776; bh=wXaHgSmXq7Cne8U5TiyhmATT9M+v5LZqNBktgzu8TtM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cVUoKYbIPC6sLoVtWSPPL7ef1u/XdXpSZUNtpoCKTRREU/F1SQhBiUaoAiDimphUi j/Q+SZtagRBMZXRL/IMaTG+qBkv2zC9x+ReVNsmPZxS+g4xhLq7QUykdmERqfYxLwt kVAdL6VanL+KDKFz/OWQRSUrOQw4/tStotZGW7DU= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27c04077f6e_ead3fa26f33af80143111"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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, 18 Jun 2018 14:23:01 -0000 ----==_mimepart_5b27c04077f6e_ead3fa26f33af80143111 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Clarification question: considering the use of "SHALL," does this imply that an endpoint MUST detect all duplicates? I understand that it is possible to implement such a scheme; an endpoint will keep track of the cut-off PN (the biggest PN that it would ignore) as well as all the PNs that it have seen above the cut-off PN. But I wonder if the intent here is to require all implementations to have such defense. -- 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/1372#pullrequestreview-129584511 ----==_mimepart_5b27c04077f6e_ead3fa26f33af80143111 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Clarification question: considering the use of "SHALL," does this imply that an endpoint MUST detect all duplicates?

I understand that it is possible to implement such a scheme; an endpoint will keep track of the cut-off PN (the biggest PN that it would ignore) as well as all the PNs that it have seen above the cut-off PN. But I wonder if the intent here is to require all implementations to have such defense.

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

----==_mimepart_5b27c04077f6e_ead3fa26f33af80143111-- From nobody Mon Jun 18 07:40:19 2018 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 5A73112F1A2 for ; Mon, 18 Jun 2018 07:40:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 h3YXnqXAYM6L for ; Mon, 18 Jun 2018 07:40:14 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F802126F72 for ; Mon, 18 Jun 2018 07:40:14 -0700 (PDT) Date: Mon, 18 Jun 2018 07:40:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529332813; bh=fCBwNkZ8nyEZFFjxRPLUzWZlXnYFIDtGQZyxOESvXq4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gv12u7pIGNoseQ4ZXpgLzFoi6ZNiD/apRhfJoWWFCobNr2hjNlt1jBIoLQZkUFyGn 0V5X2yjGHvXt7ilDwvTMD7jgacLyRzjkhhjMnyc3kD+UFFNVcgT1u+dOWQH+kr29Uo KNfkrxBjLxO37nAoMVT5xCOHagEwni4ps1zOsN6o= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27c44dc63a6_630a2ae40c950f547018d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 18 Jun 2018 14:40:18 -0000 ----==_mimepart_5b27c44dc63a6_630a2ae40c950f547018d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Yes, that is the intention, to avoid getting ECN field values for duplicates added to the counters for packets that are included in any ACK. So if a receiver has included it in an ACK, it need to remember that this PN already have an ECN field valued added to the counters. But it doesn't need to detect duplicates for packet that are discarded directly after decryption, i.e. older than the cut-off PN. This is straightforward and fulfills the requirements that appears to currently exist. If #1405 concludes it would be easier to determine if there are other approaches including other ECN field value encodings as discussed in #1439. -- 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/1372#discussion_r196103436 ----==_mimepart_5b27c44dc63a6_630a2ae40c950f547018d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Yes, that is the intention, to avoid getting ECN field values for duplicates added to the counters for packets that are included in any ACK. So if a receiver has included it in an ACK, it need to remember that this PN already have an ECN field valued added to the counters. But it doesn't need to detect duplicates for packet that are discarded directly after decryption, i.e. older than the cut-off PN.

This is straightforward and fulfills the requirements that appears to currently exist. If #1405 concludes it would be easier to determine if there are other approaches including other ECN field value encodings as discussed in #1439.

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

----==_mimepart_5b27c44dc63a6_630a2ae40c950f547018d-- From nobody Mon Jun 18 07:59:47 2018 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 BC264120049 for ; Mon, 18 Jun 2018 07:59:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 IbLLXWmn4v_4 for ; Mon, 18 Jun 2018 07:59:43 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 AA4D6130DE1 for ; Mon, 18 Jun 2018 07:59:42 -0700 (PDT) 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=rTQwkxlBI2puJhdLxV/BnahVctk=; b=Q3o4getQfNPWoWes cPZ3SVFdt1KRpuS84MhGP2pFle8aiPcIOz+ug7nc7v8nVhI0U+sry2wMWXOS5wvT mVRPFNlGF6ZbrgTEmsiIowNXJwCrrSlwDp3zbPk3JTqiMy8Lozo6MEcFU8Ofc103 Y+nl2bAxRBpUwK4Dow47zXQoj8U= Received: by filter0124p1iad2.sendgrid.net with SMTP id filter0124p1iad2-13255-5B27C8DD-14 2018-06-18 14:59:41.338404378 +0000 UTC Received: from github-lowworker-643483b.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id zywohZgmRDCOcLPeicn2XQ for ; Mon, 18 Jun 2018 14:59:41.286 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-643483b.cp1-iad.github.net (Postfix) with ESMTP id 442456C13D5 for ; Mon, 18 Jun 2018 07:59:41 -0700 (PDT) Date: Mon, 18 Jun 2018 14:59:41 +0000 (UTC) From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27c8dd429dc_65ff3ff5d5e64f7852742"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak13QzsgPs8JcjCrfK06uvcW3+5Ay8XFUzd8eF UtGdFhSG1BErd6yCY2ilAzG8WtlJHbDNzIJeplZO2ui3g//NmoX/jkaMl4yN096yv1IzDK84ZH84ss mBSMzsMutzNB0E1f28YMt65KHlYEACWwvvU4GpiEqbqS5I3By7Imv/JkuXVszbiHixzi5FFe6i1ox5 s= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 14:59:46 -0000 ----==_mimepart_5b27c8dd429dc_65ff3ff5d5e64f7852742 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Thank you for the clarification. My two cents go to that this is an unnecessary burden, because IMO while idempotency is required for frame payloads, it is not required for ECN signal that is injected by an on-path device (even though we need some defense against injection attacks). -- 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/1372#discussion_r196110762 ----==_mimepart_5b27c8dd429dc_65ff3ff5d5e64f7852742 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Thank you for the clarification. My two cents go to that this is an unnecessary burden, because IMO while idempotency is required for frame payloads, it is not required for ECN signal that is injected by an on-path device (even though we need some defense against injection attacks).

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

----==_mimepart_5b27c8dd429dc_65ff3ff5d5e64f7852742-- From nobody Mon Jun 18 08:09:50 2018 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 4FF26130DE0 for ; Mon, 18 Jun 2018 08:09:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3S5JlBB17Qs9 for ; Mon, 18 Jun 2018 08:09:46 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 648C312777C for ; Mon, 18 Jun 2018 08:09:46 -0700 (PDT) Date: Mon, 18 Jun 2018 08:09:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529334585; bh=/ZIu7Rkkx8Bq6zFMAiydDZf2XYhmmRlMLmHDA8tHvuU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HZ8UBaLfEloLBDa33ODqH34HUxr6NvjrpgGC7qMdz5Nue2yPhfICYwOw1YYcZOW/m 2sMOfKHsBcfP0ze5DYLWRLdo1V1QLwfAgAnv6HDKcs0kMApneBDslFghEmhusXHA0H fJeeB3sBPlhXB62JIT0UdVgiyD0qbIP0nDyuNR30= From: mirjak Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27cb39600a5_1a6a2ac7ae54af60110930"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mirjak 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.26 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, 18 Jun 2018 15:09:49 -0000 ----==_mimepart_5b27cb39600a5_1a6a2ac7ae54af60110930 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mirjak commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the This is incorrect. The requirements that currently exists in tsv is that ALL CEs must be counted because the network does not know if a packet is a duplicate or not! -- 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/1372#discussion_r196114651 ----==_mimepart_5b27cb39600a5_1a6a2ac7ae54af60110930 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mirjak commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

This is incorrect. The requirements that currently exists in tsv is that ALL CEs must be counted because the network does not know if a packet is a duplicate or not!

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

----==_mimepart_5b27cb39600a5_1a6a2ac7ae54af60110930-- From nobody Mon Jun 18 08:14:05 2018 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 9EC58130DEA for ; Mon, 18 Jun 2018 08:14:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 VYmtB2K1ZU2V for ; Mon, 18 Jun 2018 08:14:01 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 C80AD130DE0 for ; Mon, 18 Jun 2018 08:14:00 -0700 (PDT) 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=fRzLX+uTPD4l8/A3ZjZqF4Qm+U8=; b=N0L1bHfUfABGloSs EzRq1YVbVWug3YrZPWKgPZrlnwOFX8UekSlvzAqpADPNku6Z9FKTSJjl8kCtauz5 M0Xb0+bSsB5a7JmxC0YLZEzRvst0No0uHBGjlurLPKGYgCKyhyMnuq58JdhP7MMV I0BJvza9K0UCnpJK3JhTc69ikMU= Received: by filter0615p1iad2.sendgrid.net with SMTP id filter0615p1iad2-5024-5B27CC37-14 2018-06-18 15:13:59.442573484 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id THNO_gJNSs2xmyK0TE8aPA for ; Mon, 18 Jun 2018 15:13:59.398 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 75E5A3E0FDB for ; Mon, 18 Jun 2018 08:13:59 -0700 (PDT) Date: Mon, 18 Jun 2018 15:13:59 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27cc3772d68_694f2b07f96acf581335a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2hhLWNcuqoRIULzE1+cNltvyHCjvYtjY9cHv IEZs8BznlQ3YCufSh3Q7o/QAZ7w5V4qSeK+BWhFNEqF1fcak1FCnRUxrjGTnp9DmUMN3e/+vz2AaqC PfOmxWlPpsfQ3qnTwjPN/044JzZ6N1AQkgZsV+QEyfHbu5PGhTN5ut409Q== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 15:14:03 -0000 ----==_mimepart_5b27cc3772d68_694f2b07f96acf581335a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the I believe the reason TCP counts all CEs is because TCP retransmits packets, not because of an effort to count packets the network inadvertently duplicated. QUIC does not duplicate packets and instead uses new packet numbes for retransmissions, so I believe this embodies the intent of the requirement. -- 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/1372#discussion_r196116256 ----==_mimepart_5b27cc3772d68_694f2b07f96acf581335a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

I believe the reason TCP counts all CEs is because TCP retransmits packets, not because of an effort to count packets the network inadvertently duplicated. QUIC does not duplicate packets and instead uses new packet numbes for retransmissions, so I believe this embodies the intent of the requirement.

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

----==_mimepart_5b27cc3772d68_694f2b07f96acf581335a6-- From nobody Mon Jun 18 08:21:30 2018 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 5A5F4130DE1 for ; Mon, 18 Jun 2018 08:21:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 2gVbCBVg63tu for ; Mon, 18 Jun 2018 08:21:27 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B32AE12872C for ; Mon, 18 Jun 2018 08:21:27 -0700 (PDT) Date: Mon, 18 Jun 2018 08:21:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529335287; bh=1xDBSLw0JfMiTerRn19ksnFRjpAV0Z64UmA7cRvK5+U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hqLd0w4xHMSEgG51y7PNRdJ7/9ZlmpLJZnv3K4/N1IfkLo1DZW78LqKz8wvmk+RMn SpnqbFs1oPxcJJ1VTq8FDi1U+9MFGQJSjCTbUrQW3vWLg31/h8e9+wRmpLYCUbvM/6 ToAY8eytSpQUSJ8jY9oAnJuXj4K3ac5uIP6H8yf8= From: mirjak Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27cdf790ab_56513fbc9b914f7812458d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mirjak 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.26 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, 18 Jun 2018 15:21:29 -0000 ----==_mimepart_5b27cdf790ab_56513fbc9b914f7812458d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mirjak commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the No, that is not true. The network marks a packet as congested because it is congested and want to signal this to the endpoint. The network does not distinguish between retransmission or duplicates or anything because all these packets need the same amount of network resources and therefore cause congestion. RFC8085 even says "A receiver that enables the use of ECN for a UDP port MUST check the ECN field at the receiver for each UDP datagram that it receives on this port." and "This MUST report the presence of datagrams received with a CE-mark by providing a mechanism to feed this congestion information back to the sending application." You cannot just ignore an CE because it's on a retransmission or a duplicated packet! The problem with duplicates it that a packet could have been duplicated before or after it was CE marked. If it gets duplicated after it was marked, this is not a real congestion indication and if counted overstates the congestion. However, if it gets marked after it was duplicated, it is an indication of congestion. As you don't know when it got marked, you need to be conservative and account for it. -- 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/1372#discussion_r196119153 ----==_mimepart_5b27cdf790ab_56513fbc9b914f7812458d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mirjak commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

No, that is not true. The network marks a packet as congested because it is congested and want to signal this to the endpoint. The network does not distinguish between retransmission or duplicates or anything because all these packets need the same amount of network resources and therefore cause congestion. RFC8085 even says
"A receiver that enables the use of ECN for a UDP port MUST check
the ECN field at the receiver for each UDP datagram that it
receives on this port."
and
"This MUST report the
presence of datagrams received with a CE-mark by providing a
mechanism to feed this congestion information back to the sending
application."
You cannot just ignore an CE because it's on a retransmission or a duplicated packet!

The problem with duplicates it that a packet could have been duplicated before or after it was CE marked. If it gets duplicated after it was marked, this is not a real congestion indication and if counted overstates the congestion. However, if it gets marked after it was duplicated, it is an indication of congestion. As you don't know when it got marked, you need to be conservative and account for it.

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

----==_mimepart_5b27cdf790ab_56513fbc9b914f7812458d-- From nobody Mon Jun 18 08:25:25 2018 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 5CC41130E06 for ; Mon, 18 Jun 2018 08:25:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 LDRruAWY8dxi for ; Mon, 18 Jun 2018 08:25:10 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236C0130ECA for ; Mon, 18 Jun 2018 08:24:57 -0700 (PDT) Date: Mon, 18 Jun 2018 08:24:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529335496; bh=X1DpVMpLB/2QgPQRmYg4gczSnd7c55SZgdPImB7/RmY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BCCRCci0j9ubuJXpSLePKaAzh8HG8e9qL48eCxF8WoXWwYsmNeGAvlB7wKkJIOEKW ULXV/TIknwbu1S7laN6Cw/iY/F6Dk9kr2oAl44+0en6mQTyQ2n1kzYIczfE7fb7pnS WaEnKrY/kCJpMo8xj2Jm6qGOcJFWfdf0p4jmf6pM= From: mirjak Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27cec858c61_2a093fc7beef6f801693a9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mirjak 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.26 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, 18 Jun 2018 15:25:23 -0000 ----==_mimepart_5b27cec858c61_2a093fc7beef6f801693a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mirjak commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Also QUIC does process duplicate packets to the point where it can detect that it is duplicated which probably already gives you some confidence that it is a valid quic packet and therefore you can also check the ECN IP mark at this point of time. -- 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/1372#discussion_r196120477 ----==_mimepart_5b27cec858c61_2a093fc7beef6f801693a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mirjak commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Also QUIC does process duplicate packets to the point where it can detect that it is duplicated which probably already gives you some confidence that it is a valid quic packet and therefore you can also check the ECN IP mark at this point of time.

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

----==_mimepart_5b27cec858c61_2a093fc7beef6f801693a9-- From nobody Mon Jun 18 08:28:27 2018 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 C368F12872C for ; Mon, 18 Jun 2018 08:28:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 g0GKQ0_UT3rZ for ; Mon, 18 Jun 2018 08:28:22 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 78BDB130DE1 for ; Mon, 18 Jun 2018 08:28:22 -0700 (PDT) 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=ofagh5Ah6P44mPIn9DYLpGpXL1g=; b=pd3ARjuFQ+m1PiUI Mr5edZun7u7F/DHP7tMxTxOEkD4Z6UNRXJ+h0JYuj2Hr8nLWoJmy41dHDpH4IRXS 6ieBaQY68HeD1l+i3GR7t6B5GqTH8QZdp6boGIkm1AshHuvFbz9mjC9aeblMPNZa P1kQiegCxOfZrHVrpg0QoNrRWvY= Received: by filter1025p1las1.sendgrid.net with SMTP id filter1025p1las1-14291-5B27CF94-11 2018-06-18 15:28:20.821556186 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0022p1iad2.sendgrid.net (SG) with ESMTP id 25TEb1aeQ9mHTLQGOVS9mQ for ; Mon, 18 Jun 2018 15:28:20.800 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id A9D65C0750 for ; Mon, 18 Jun 2018 08:28:20 -0700 (PDT) Date: Mon, 18 Jun 2018 15:28:20 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27cf94a7b50_3ea13fb5e1830f781563bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak33bkTDN23p4sh74sUkOiaQ/eLH0upW+D7jeu CpdARpQ5BFxBJKOfTiEOFxBLH/1M05Q7xM8OvY4rK6O3TZ/81mu4q+4NYqM+gqURzJxFMPP1ycjmye swUp39w/rs1U2Bb6MRVgG1Mo6dTaIGbUhl6yECAc3fEF6zpZXZSuJL/xYcqFl9knDTgdnzD3AQQoDE A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 15:28:25 -0000 ----==_mimepart_5b27cf94a7b50_3ea13fb5e1830f781563bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Fair enough, then I think that text wasn't written with QUIC in mind. As I mentioned previously, I think this is an edge case that is not a practical problem in real networks. Unnecessary packet duplication is the real problem, not it's implications on ECN. -- 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/1372#discussion_r196121655 ----==_mimepart_5b27cf94a7b50_3ea13fb5e1830f781563bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Fair enough, then I think that text wasn't written with QUIC in mind.

As I mentioned previously, I think this is an edge case that is not a practical problem in real networks. Unnecessary packet duplication is the real problem, not it's implications on ECN.

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

----==_mimepart_5b27cf94a7b50_3ea13fb5e1830f781563bb-- From nobody Mon Jun 18 08:33:41 2018 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 F03F3130DF9 for ; Mon, 18 Jun 2018 08:33:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 c2jFjzUk4X44 for ; Mon, 18 Jun 2018 08:33:37 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E61E0130E01 for ; Mon, 18 Jun 2018 08:33:36 -0700 (PDT) Date: Mon, 18 Jun 2018 08:33:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529336016; bh=hPBDZNqlAum3pFLXYDgqUmeCgCVrfYGL75/03W7XuK8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IlHFT7lRyT+NhwAvUPuQkEb5ELF5fFOlUGyJsLHBA7NTeZXym3C8zQI40m4QrqZbk 5RbtYFMvgQIO6DK6JBro6u1ABYeXDNezfAbwy+cdDmLek3d7A0FeQ/cC08Q+5kVKtr thHmb6uXXVtNP9XpgOzhOrTolD6GdbZXNguHPBUE= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27d0d0e558_313d2af04339af543499ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 18 Jun 2018 15:33:40 -0000 ----==_mimepart_5b27d0d0e558_313d2af04339af543499ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If we're going to allow more than 2, I'm not at all clear on how we're going to guarantee forward progress. I'll point out that if a server is under DoS and thinks a QUIC connection is a potential attack, it can close the connection and force the client to fall back to TCP. This isn't optimal, but it avoids a lot of edge cases involving multiple retries and rollout issues where the server expects to be behind a DoS prevention device, but isn't temporarily. I'll remind everyone that QUIC's requirement of a full-sized INITIAL should make it much less prone to issues than TCP syn attacks, so one layer of defense really should be enough. -- 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/1451#issuecomment-398096042 ----==_mimepart_5b27d0d0e558_313d2af04339af543499ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If we're going to allow more than 2, I'm not at all clear on how we're= going to guarantee forward progress.

I'll point out that if a server is under DoS and thinks a QUIC connect= ion is a potential attack, it can close the connection and force the clie= nt to fall back to TCP. This isn't optimal, but it avoids a lot of edge = cases involving multiple retries and rollout issues where the server expe= cts to be behind a DoS prevention device, but isn't temporarily.

I'll remind everyone that QUIC's requirement of a full-sized INITIAL s= hould make it much less prone to issues than TCP syn attacks, so one laye= r of defense really should be enough.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27d0d0e558_313d2af04339af543499ef-- From nobody Mon Jun 18 08:35:34 2018 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 2F9AE130DF5 for ; Mon, 18 Jun 2018 08:35:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 yZFmEreH7-0g for ; Mon, 18 Jun 2018 08:35:18 -0700 (PDT) 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 E225A130DF9 for ; Mon, 18 Jun 2018 08:35:16 -0700 (PDT) Date: Mon, 18 Jun 2018 08:35:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529336116; bh=sg+VVY9r2f2VDziRGh7Vp0moa77niuDSqaOpplpxLxY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fq2QzyuiLe8bT+QanbJeIBZu5VMABVtnjdk/lI+u3KYKyPJ20uOCbCxLCIIvEoXJe wVwhuxr4UCfQqhp8ivzF/fFqEvDh/GJwGl9aGrmI7am7JS7LQye26oMgdGZgsji2AT cl0sFoXG7qysr1nJI36Z9Om6uiG4+Nhj0eV7Cm3Q= From: mirjak Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27d134b0d3_71dd2aba663aef582188e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mirjak 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.26 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, 18 Jun 2018 15:35:32 -0000 ----==_mimepart_5b27d134b0d3_71dd2aba663aef582188e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mirjak commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the I agree that this is an edge case and should hopefully not be a problem but saying in the spec that duplicated shall be ignored is not the right thing to do. -- 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/1372#discussion_r196124349 ----==_mimepart_5b27d134b0d3_71dd2aba663aef582188e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mirjak commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

I agree that this is an edge case and should hopefully not be a problem but saying in the spec that duplicated shall be ignored is not the right thing to do.

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

----==_mimepart_5b27d134b0d3_71dd2aba663aef582188e5-- From nobody Mon Jun 18 09:04:31 2018 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 EDFB0130DF6 for ; Mon, 18 Jun 2018 09:04:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 iLD_xkgjOach for ; Mon, 18 Jun 2018 09:04:21 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97698130DF5 for ; Mon, 18 Jun 2018 09:04:21 -0700 (PDT) Date: Mon, 18 Jun 2018 09:04:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529337860; bh=N3IVCeCfpb881+IEMCjsM9VurrsSNtsr+gbSA5evCJ4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QwNx7ISjSDzaz45+qQh97tgjDlBVcwhZKPS3EVkILzcWo57Lxk/uGO5PFT3+mvWOl cDYS8z+BpIkSOLfHzM0FDxsmXnbOb2Yxh+Z+6H9gcqNCL6S52pyxYDvIc9d7Z1voFJ QQHvK+qXaLPHu8fT5nnkBqQhlopgYfgp0hd0tiIQ= From: Praveen Balasubramanian Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27d8048c9d0_28a83fd0de42af8811182"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: pravb 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.26 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, 18 Jun 2018 16:04:29 -0000 ----==_mimepart_5b27d8048c9d0_28a83fd0de42af8811182 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit pravb approved this pull request. Looks good since we don't need to handle polarity in this QUIC version. -- 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/1447#pullrequestreview-129630848 ----==_mimepart_5b27d8048c9d0_28a83fd0de42af8811182 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@pravb approved this pull request.

Looks good since we don't need to handle polarity in this QUIC version.

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

----==_mimepart_5b27d8048c9d0_28a83fd0de42af8811182-- From nobody Mon Jun 18 10:51:13 2018 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 CA60F130EC8 for ; Mon, 18 Jun 2018 10:51:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oUl_q2QWztPH for ; Mon, 18 Jun 2018 10:51:03 -0700 (PDT) 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 E3A76130E9A for ; Mon, 18 Jun 2018 10:51:02 -0700 (PDT) Date: Mon, 18 Jun 2018 10:50:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529344259; bh=hcwTDqdOEmVeNByVQoofqJGCy3SpOtuK1c39UIW7z6w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=t5+SpOA1LvwAilFXrGtzEtl/zUXbYTpgaA/TMA5JEYCMD60Zydqpm6agDgmi2+eM0 Wc9awqMwoakofR8GyQrP3E0JJACHby0GM802sxv2hZ0hfTZoMDUly5PJ0CO8TbP5UG 9+iCETAOxxnluKmdnWvTrWzn55pO4a89nPC6ZInY= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f103eb145_56cd2b099956cf5c1060a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 18 Jun 2018 17:51:10 -0000 ----==_mimepart_5b27f103eb145_56cd2b099956cf5c1060a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @igorlord pushed 28 commits. 3cb44ee Set TLS extension codepoint to 0xffa5 8081d70 What if invariants change? 74a0e43 Which witch? 33b7f3a Things, properties 342e647 Fix variable-length fields in picture 93b9900 Add PUSH_PROMISE xref df786b9 Rewrap 9f171d0 Remove sequence number from NEW_CONNECTION_ID b052fa4 Remove Flags (#1398) e7b9cca Coalescing guidance 9ef7802 HTTP/QUIC specific, not HTTP-specific 9c327ec Include decryption failures 5d6ab28 fix typo 984efe0 fix typo (#1434) 1d02e03 Don't cite octet indices any more b421f5b No mixing CIDs 4567f7b Move Draft Version Identification section 1a1fc7f Kazuho's suggestion 8002125 Statement of idempotency d52a00e Say why 9d92555 Remove stream sequencing requirement; obsoleted by implicit-open of streams df94970 Re-"framing" d2756b6 "End Header Block" does not exist 3f4d7f9 Expand Primitives section 49c2b08 exercise editorial discretion 73fb978 Fix sentence: make clear what fails with PROTOCOL_VIOLATION code 05ecc25 Describe QPACK Feedback mechanisms (#1410) de84e82 Updated ICMP PMTU section: incorporating feedback -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1412/files/160afb012b00075d8716df39414edc138029e332..de84e82636bd7ffd6df51eb1caf3cf9670bd62eb ----==_mimepart_5b27f103eb145_56cd2b099956cf5c1060a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord pushed 28 commits.

  • 3cb44ee Set TLS extension codepoint to 0xffa5
  • 8081d70 What if invariants change?
  • 74a0e43 Which witch?
  • 33b7f3a Things, properties
  • 342e647 Fix variable-length fields in picture
  • 93b9900 Add PUSH_PROMISE xref
  • df786b9 Rewrap
  • 9f171d0 Remove sequence number from NEW_CONNECTION_ID
  • b052fa4 Remove Flags (#1398)
  • e7b9cca Coalescing guidance
  • 9ef7802 HTTP/QUIC specific, not HTTP-specific
  • 9c327ec Include decryption failures
  • 5d6ab28 fix typo
  • 984efe0 fix typo (#1434)
  • 1d02e03 Don't cite octet indices any more
  • b421f5b No mixing CIDs
  • 4567f7b Move Draft Version Identification section
  • 1a1fc7f Kazuho's suggestion
  • 8002125 Statement of idempotency
  • d52a00e Say why
  • 9d92555 Remove stream sequencing requirement; obsoleted by implicit-open of streams
  • df94970 Re-"framing"
  • d2756b6 "End Header Block" does not exist
  • 3f4d7f9 Expand Primitives section
  • 49c2b08 exercise editorial discretion
  • 73fb978 Fix sentence: make clear what fails with PROTOCOL_VIOLATION code
  • 05ecc25 Describe QPACK Feedback mechanisms (#1410)
  • de84e82 Updated ICMP PMTU section: incorporating feedback

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b27f103eb145_56cd2b099956cf5c1060a-- From nobody Mon Jun 18 10:55:19 2018 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 65DFC130E13 for ; Mon, 18 Jun 2018 10:55:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bDMobewDnCjC for ; Mon, 18 Jun 2018 10:55:15 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 759DF130DCA for ; Mon, 18 Jun 2018 10:55:15 -0700 (PDT) Date: Mon, 18 Jun 2018 10:55:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529344514; bh=PsjvPtb61yLd6bKe+r8CbLyUrLbxng4l3AiF9JubfHY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uumbU2/pM/qi+Eis5w4fRWhTPnfvNkQGAIQ4DFSf7G9Ft6Qxk4qtZNGN3c9tZ7WUZ tImiZK8joItguAjrpIltwelqoLKDZ8asOQb6KiHl7fvxU4uspXX/MAcDJ4sBTONRuv 9LxarWSChS/iH278R0oJXJzkfrVfdzw4ZB5fIPfw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f202d4065_1c8f3f8a2ec7cf842503f"; 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.26 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, 18 Jun 2018 17:55:17 -0000 ----==_mimepart_5b27f202d4065_1c8f3f8a2ec7cf842503f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Would it make sense to carry a sequence number on the token? The server increments every time it sends a Retry; the client ignores Retries which don't exactly increment the sequence number of its most recent Initial. If the Initial gets duplicated, the client will latch onto whichever Retry it receives first and ignore the subsequent one; if the Retry gets duplicated/delayed, the client will ignore it. -- 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/1451#issuecomment-398140825 ----==_mimepart_5b27f202d4065_1c8f3f8a2ec7cf842503f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Would it make sense to carry a sequence number on the token? The serv= er increments every time it sends a Retry; the client ignores Retries whi= ch don't exactly increment the sequence number of its most recent Initial= . If the Initial gets duplicated, the client will latch onto whichever R= etry it receives first and ignore the subsequent one; if the Retry gets d= uplicated/delayed, the client will ignore it.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27f202d4065_1c8f3f8a2ec7cf842503f-- From nobody Mon Jun 18 11:02:58 2018 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 AE212130F78 for ; Mon, 18 Jun 2018 11:02:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 L2vVX51xBH66 for ; Mon, 18 Jun 2018 11:02:47 -0700 (PDT) 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 981A5130F44 for ; Mon, 18 Jun 2018 11:02:47 -0700 (PDT) Date: Mon, 18 Jun 2018 11:02:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529344966; bh=kPVQdUdKmVrF5g+PbBzGEyQ1lKhNJDC/c/Li2nL6ynk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ke9cG3hv494X+MwOplAgre4k9pBZ4DZND+JpYMmoWx4Iz9ZsREnx6QPNILIibFGOu If7t//kd1gVqjQLGLvRwnFNF6/gx4at0OW3uuaUrYFP/XCwvIJFwTByt/OQ3mpto/U kmzqrOsnR84w0RpJYt4aCv5iSysMrkpesGkbHG2k= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f3c6e38fb_621d2ad7ac9f2f50301086"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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, 18 Jun 2018 18:02:55 -0000 ----==_mimepart_5b27f3c6e38fb_621d2ad7ac9f2f50301086 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop for that to work, the QUIC server would need to read the Retry packet it gets from the client (that it sent in response to the DoS protection device's Retry) and then increment from there. But what happen if there was spurious retransmission? For instance, the DoS protection device ends up sending two Retry packets, and both are eventually responded to by the client and both responses end up getting to the QUIC server. The server would send seq_num=2 for its first Retry, but the client would ignore it. -- 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/1451#issuecomment-398143072 ----==_mimepart_5b27f3c6e38fb_621d2ad7ac9f2f50301086 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@MikeBishop for that to work, t= he QUIC server would need to read the Retry packet it gets from the clien= t (that it sent in response to the DoS protection device's Retry) and the= n increment from there. But what happen if there was spurious retransmiss= ion? For instance, the DoS protection device ends up sending two Retry pa= ckets, and both are eventually responded to by the client and both respon= ses end up getting to the QUIC server. The server would send seq_num=3D2 = for its first Retry, but the client would ignore it.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27f3c6e38fb_621d2ad7ac9f2f50301086-- From nobody Mon Jun 18 11:05:00 2018 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 C61B8130EFF for ; Mon, 18 Jun 2018 11:04:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 Tt19tBZYR0zR for ; Mon, 18 Jun 2018 11:04:48 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 BA902130EE2 for ; Mon, 18 Jun 2018 11:04:47 -0700 (PDT) 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=1cq0x9anVO/ZxZlctnJ36HKRLRo=; b=fNlTQPrdkeSVSJIj eGZpwUYqXzfsyCdcwhirtoIObouhioMtwn5TeSFg5fiQSfzI+6/HjW23yyHHV8ku cURhNwUX6uy8rvkJu5MBsEKkbvAu/ad6fFiRRHZzaCOWBSDaTOzTabbkfC/1bNWl +EJuXhIZrzyrkHbiu3uhelg7VwY= Received: by filter1134p1las1.sendgrid.net with SMTP id filter1134p1las1-6560-5B27F43C-19 2018-06-18 18:04:44.948077882 +0000 UTC Received: from github-lowworker8-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0022p1iad2.sendgrid.net (SG) with ESMTP id KoB81cUHRkKiHHMxhRM9cA for ; Mon, 18 Jun 2018 18:04:44.854 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker8-cp1-prd.iad.github.net (Postfix) with ESMTP id D1D0A6146E for ; Mon, 18 Jun 2018 11:04:44 -0700 (PDT) Date: Mon, 18 Jun 2018 18:04:44 +0000 (UTC) From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f43ccfee8_23983f8431614f781200c0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1J3M79amxRpZDhcCGDbO+kPisCCfK5UXg3cU F7vSvUcPsSC8j2J66jVWyEc/xTaU7Sjq+EPmLTvWnVMaJhyGrEx7w1Qlo30kcJgl0nGyT4i14AKt3l 6WIpPDYONn2P+wtkvQr0aJpmZhd6dacd2+koGhkwaLy1P7hHCO+pu8J1GD+wEHniu69fldZjYvG5fE E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 18:04:52 -0000 ----==_mimepart_5b27f43ccfee8_23983f8431614f781200c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Maybe, instead of the server incrementing the sequence counter, the client does and the server just echoes it back? -- 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/1451#issuecomment-398143629 ----==_mimepart_5b27f43ccfee8_23983f8431614f781200c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Maybe, instead of the server incrementing the sequence counter, the client does and the server just echoes it back?

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

----==_mimepart_5b27f43ccfee8_23983f8431614f781200c0-- From nobody Mon Jun 18 11:06:07 2018 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 D6CA6130F01 for ; Mon, 18 Jun 2018 11:06:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ygUm2ky_SI99 for ; Mon, 18 Jun 2018 11:06:03 -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 15855130EFF for ; Mon, 18 Jun 2018 11:06:03 -0700 (PDT) Date: Mon, 18 Jun 2018 11:06:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529345162; bh=vn6QgcO9BSxQ1awh9IadvaKUXftcd8Jtz40wMkSkMx8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rUVjNn3GSv1LjMjqAb5fScfGcKH2XSbaFAxR2itdL99kgiNz8Xm2y5ZHj/4qtpbL4 wEKP1Y/hgaq2sic/huuoMrefXUvxzzhk38ut9jdKOazgN7OLWcfteSLaTsK70KFj30 Cp3nGEof0xeWVSXpyA3Tc5c6wB8g34XNAdJcwbmc= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f48a3d1fa_15092abc0a4d8f5027145"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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, 18 Jun 2018 18:06:05 -0000 ----==_mimepart_5b27f48a3d1fa_15092abc0a4d8f5027145 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm afraid this could get easily ossified though, and I really don't want to encrypt yet another thing to prevent ossification. -- 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/1451#issuecomment-398143962 ----==_mimepart_5b27f48a3d1fa_15092abc0a4d8f5027145 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm afraid this could get easily ossified though, and I really don't want to encrypt yet another thing to prevent ossification.

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

----==_mimepart_5b27f48a3d1fa_15092abc0a4d8f5027145-- From nobody Mon Jun 18 11:18:40 2018 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 3C868130E24 for ; Mon, 18 Jun 2018 11:18:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bXh8nLGj_cM7 for ; Mon, 18 Jun 2018 11:18:36 -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 6648E130E0D for ; Mon, 18 Jun 2018 11:18:36 -0700 (PDT) Date: Mon, 18 Jun 2018 11:18:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529345915; bh=8I4TrRp5+zkeCkXIFKM/1tAdD7q4HWralNRhRv1VH2o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Viye+cmYIemsiC5kylEmVzzwVPLyL0KCnt5EYm04MF2j6Ubb9j4xYtqCzv9kpyHwb kzbAtzXtMg4Ll9PDpx28W2Zx/FFux9uJ3LvwVhE/7RmV8OAFdQpVbNAFdaJ+nlepzJ kBZo2ubtC8o0DPw4/FMEX7riweXFNplla9mSNDWU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27f77baa467_32003f7ecbbd8f881146a3"; 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.26 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, 18 Jun 2018 18:18:39 -0000 ----==_mimepart_5b27f77baa467_32003f7ecbbd8f881146a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @nibanks, if the DoS device sends two Retry packets, the client would ignore the second: - Client sends Initial, stored token, SN = 0 - DoS device responds Retry, token A, SN = 1 - DoS device spuriously sends Retry, token B, SN = 1 - Client processes either Retry, sends new Initial with SN = 1 and token A or B - Client receives other Retry, ignores because SN != 2. - Server responds to the Initial with SN = 1 with a Retry, SN = 2 - Client processes Retry, sends another Initial with SN = 2, etc. Ossification is definitely a concern; someone could come to expect that this field is always zero on the client's first packet. Encryption would be preferable, but the point of this is to avoid doing decryption work on the server until it's reasonably confident that the client is genuine, so that's problematic. However, GREASE is an option. Nothing requires this to start at 0/1 -- client could randomize the value on the first Initial, simply checking that the server incremented. If we permit wrapping when the server increments, all initial values are acceptable. -- 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/1451#issuecomment-398147736 ----==_mimepart_5b27f77baa467_32003f7ecbbd8f881146a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@nibanks, if the DoS device sends= two Retry packets, the client would ignore the second:

  • Client sends Initial, stored token, SN =3D 0
  • DoS device responds Retry, token A, SN =3D 1
  • DoS device spuriously sends Retry, token B, SN =3D 1
  • Client processes either Retry, sends new Initial with SN =3D 1 and to= ken A or B
  • Client receives other Retry, ignores because SN !=3D 2.
  • Server responds to the Initial with SN =3D 1 with a Retry, SN =3D 2
  • Client processes Retry, sends another Initial with SN =3D 2, etc.

Ossification is definitely a concern; someone could come to expect tha= t this field is always zero on the client's first packet. Encryption wou= ld be preferable, but the point of this is to avoid doing decryption work= on the server until it's reasonably confident that the client is genuine= , so that's problematic.

However, GREASE is an option. Nothing requires this to start at 0/1 -= - client could randomize the value on the first Initial, simply checking = that the server incremented. If we permit wrapping when the server incre= ments, all initial values are acceptable.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b27f77baa467_32003f7ecbbd8f881146a3-- From nobody Mon Jun 18 11:50:53 2018 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 71C16130F01 for ; Mon, 18 Jun 2018 11:50:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 AMa010JjTdCd for ; Mon, 18 Jun 2018 11:50:45 -0700 (PDT) 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 35016130EFE for ; Mon, 18 Jun 2018 11:50:42 -0700 (PDT) Date: Mon, 18 Jun 2018 11:50:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529347841; bh=U0Av8VlA1CXerI9R/1kqnFITjoCFWVrrBU/jwc8LrM4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bJmdKiv5KR7WmJ7SLGVTwFnfwmbOkRNebtqYJQUF+TCWFf7LiA7V0Ns0m/BmXQA/M Qox8tV6xt2XDVIMXngarmSS+W1wACBwGVUNHUD7VEYcBY3d/Sx0StLgGPPFSb2ow6U LctqYRUxZ9zmEfUnuPBHBLILXH6Iy3wEibXZQorA= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27ff011032c_2b3d3fade64f8f8478718"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 18:50:52 -0000 ----==_mimepart_5b27ff011032c_2b3d3fade64f8f8478718 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain application data, aggressive increases in probe size carry fewer consequences. +## Responding to ICMP "Unreachable" messages {#icmp-unreach} + +When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake, +the response SHOULD be identical to receiving an ICMP TPB message that announces +a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}). + +When an ICMP "Unreachable" message is received after the handshake, the QUIC +endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}). Sending +PATH_CHALLENGE frames on the same path due to ICMP "Unreachable" messages should +be rate limited. I'll rewrite this completely. -- 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/1412#discussion_r196186262 ----==_mimepart_5b27ff011032c_2b3d3fade64f8f8478718 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain
 application data, aggressive increases in probe size carry fewer consequences.
 
 
+## Responding to ICMP "Unreachable" messages {#icmp-unreach}
+
+When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake,
+the response SHOULD be identical to receiving an ICMP TPB message that announces
+a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}).
+
+When an ICMP "Unreachable" message is received after the handshake, the QUIC
+endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}).  Sending
+PATH_CHALLENGE frames on the same path due to ICMP "Unreachable" messages should
+be rate limited.

I'll rewrite this completely.

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

----==_mimepart_5b27ff011032c_2b3d3fade64f8f8478718-- From nobody Mon Jun 18 11:54:11 2018 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 CD414130EFE for ; Mon, 18 Jun 2018 11:54:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 F04Q0O4G0JFb for ; Mon, 18 Jun 2018 11:53:58 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721E2130F79 for ; Mon, 18 Jun 2018 11:53:58 -0700 (PDT) Date: Mon, 18 Jun 2018 11:53:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529348037; bh=BwKw75eahspwecFgOWn4TWBY+i+AmGsE6+LRjnOleog=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xWNxxmyH4bHsxUuPP8XpwBJUUMIi0wZxndcEqPr77kbwaC5uedtJyRNeDaPaEMT1D yLWpiwFi1QFSnWAaxiYAtMBlcLYO+X5b1wyJayvAK7lv2cy5gAtrB4KnpaWSi8tNoA b+N3VIqdo4JxQw7H+0vr/TRdoRwXz8z8qwDWpsVY= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b27ffc590f08_2b3d3fbd4257cf80100064"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 18:54:10 -0000 ----==_mimepart_5b27ffc590f08_2b3d3fbd4257cf80100064 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields. All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP fragmentation or packet drops. To optimize bandwidth efficiency, endpoints SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}). Endpoints -MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for -detecting the PMTU, setting the PMTU appropriately, and storing the result of -previous PMTU determinations. +MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) How strongly do you feel against word "classical"? It is used in other RFCs for the purpose I am using it here. See https://tools.ietf.org/html/rfc4821 and https://tools.ietf.org/html/rfc5320. -- 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/1412#discussion_r196187281 ----==_mimepart_5b27ffc590f08_2b3d3fbd4257cf80100064 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields.
 All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP
 fragmentation or packet drops. To optimize bandwidth efficiency, endpoints
 SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}).  Endpoints
-MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for
-detecting the PMTU, setting the PMTU appropriately, and storing the result of
-previous PMTU determinations.
+MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}})

How strongly do you feel against word "classical"? It is used in other RFCs for the purpose I am using it here. See https://tools.ietf.org/html/rfc4821 and https://tools.ietf.org/html/rfc5320.

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

----==_mimepart_5b27ffc590f08_2b3d3fbd4257cf80100064-- From nobody Mon Jun 18 12:00:46 2018 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 D52F5130FCE for ; Mon, 18 Jun 2018 12:00:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4QIwMKWLTftk for ; Mon, 18 Jun 2018 12:00:35 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68F1C130F9F for ; Mon, 18 Jun 2018 12:00:29 -0700 (PDT) Date: Mon, 18 Jun 2018 12:00:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529348428; bh=ADQmwHLccHh7cdkDXoRhPdAWbooC1A82dn0U2CozUrA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ojQp+6Xt68+Rhg7Lbmq4KoEyuC4wCa6nrYiMBXpUaATZZdZpoSzHFp6VQCYHMgroC JNDMI6G0qTHqCXM27CruaCZdBaQp4e0qsJLYkJBRv9sXC0sD3AhHDXMg6W/Nvm/XLp NwyYBAns/9VZRbe/GldvbAn3lIwqx2Tr2cisfOGw= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28014c80c65_7bef3fe07b302f78142514"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 19:00:46 -0000 ----==_mimepart_5b28014c80c65_7bef3fe07b302f78142514 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by this endpoint with at least 1-2^32 +probability and it is still outstanding (not acknowledged and not deemed lost). You are right. This needs revising. -- 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/1412#discussion_r196189355 ----==_mimepart_5b28014c80c65_7bef3fe07b302f78142514 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by this endpoint with at least 1-2^32
+probability and it is still outstanding (not acknowledged and not deemed lost).

You are right. This needs revising.

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

----==_mimepart_5b28014c80c65_7bef3fe07b302f78142514-- From nobody Mon Jun 18 13:25:02 2018 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 873AA130E37 for ; Mon, 18 Jun 2018 13:24:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 e_TMPZW0f3am for ; Mon, 18 Jun 2018 13:24:57 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8148130E22 for ; Mon, 18 Jun 2018 13:24:57 -0700 (PDT) Date: Mon, 18 Jun 2018 13:24:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529353496; bh=ocIZ8VmlC4MSt8LFjYqIgsYSwAJW1pgVkZltWucEN1Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R/zTWLuUh2uhlHpl4rWvPZfbtEshWaGzfOKsj/iePm/kX50Z+NwsBWETfDuRcKKrw slDZEEt+LtPuSYdWZc0lwGbtocjAe8nh3UTVr6NlMClIEro3s8CNw1kis7QmHTZgir Q7SNCxszy8cJkFx+WH1afj7VAb+YQto6gWlW+OLY= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2815189bcf9_36803fc26cf2af801940aa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 18 Jun 2018 20:25:00 -0000 ----==_mimepart_5b2815189bcf9_36803fc26cf2af801940aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett pushed 1 commit. a4ad49b Restore Generating Acknowledgements -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/777114ac355c7a4b15dabd67122ca21c164e2e17..a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835 ----==_mimepart_5b2815189bcf9_36803fc26cf2af801940aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett pushed 1 commit.

  • a4ad49b Restore Generating Acknowledgements

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2815189bcf9_36803fc26cf2af801940aa-- From nobody Mon Jun 18 13:36:02 2018 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 8A1E3130E22 for ; Mon, 18 Jun 2018 13:35:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qM3DLBqJdxmI for ; Mon, 18 Jun 2018 13:35:46 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 159FD130F17 for ; Mon, 18 Jun 2018 13:35:46 -0700 (PDT) Date: Mon, 18 Jun 2018 13:35:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529354145; bh=QD7oBN5tx6KYeDCW89/rBBkfRDO+Qb64mvnWD7oVBcs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CNiU36GEWGhE2gbBtTRJuuGaDR6lWbV9cUUGixxyxDUTG3szsT7wCxSz6wdNdWqMt JmUIrRI0oL3Xk8PGUKbsDOOELNItwymlWYUu7blnty+oOBrOYsZ2umFvqZ5Pfo66V2 Z5h/u30fU9zdkJ+OcusMWwMnbgNLkVlVhdUz2mnE= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2817a135b05_16083f9681f76f7875893"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 20:35:59 -0000 ----==_mimepart_5b2817a135b05_16083f9681f76f7875893 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > + and can therefore be identified as spurious. + +* Store IP ID field of the sent datagrams to validate that ICMP message is + refering to an outstanding packet. + +Any ICMP messages that fail validation MUST be discarded. + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP Packet Too Big (PTB) message during a handshake, +unless then would cause a reduction to a Path MTU value smaller than 1280 +octets. + +If during a handshake a client receives an ICMP TPB message that requests it to +reduce Path MTU to a value smaller than 1280 octets, then: This is specifically done during the handshake. The language here is trying to stay in agreement with the decision that PMTU < 1280 does not support QUIC. Which ones of the statements is the concern: 1. to switch IPs (but stick w/ QUIC), if multiple IPs are available for the server? 2. to switch protocols, if we have an on-path validation of the signal? Would you rather see all PMTU<1280 signals ignored (and not switch to TCP, if available, for example)? -- 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/1412#discussion_r196216169 ----==_mimepart_5b2817a135b05_16083f9681f76f7875893 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

> +  and can therefore be identified as spurious.
+
+* Store IP ID field of the sent datagrams to validate that ICMP message is
+  refering to an outstanding packet.
+
+Any ICMP messages that fail validation MUST be discarded.
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP Packet Too Big (PTB) message during a handshake,
+unless then would cause a reduction to a Path MTU value smaller than 1280
+octets.
+
+If during a handshake a client receives an ICMP TPB message that requests it to
+reduce Path MTU to a value smaller than 1280 octets, then:

This is specifically done during the handshake. The language here is trying to stay in agreement with the decision that PMTU < 1280 does not support QUIC. Which ones of the statements is the concern:

  1. to switch IPs (but stick w/ QUIC), if multiple IPs are available for the server?
  2. to switch protocols, if we have an on-path validation of the signal?

Would you rather see all PMTU<1280 signals ignored (and not switch to TCP, if available, for example)?

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

----==_mimepart_5b2817a135b05_16083f9681f76f7875893-- From nobody Mon Jun 18 13:47:12 2018 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 333AD130F85 for ; Mon, 18 Jun 2018 13:47:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 B0Pl4FrCHMDv for ; Mon, 18 Jun 2018 13:47:01 -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 9F44E1277BB for ; Mon, 18 Jun 2018 13:47:01 -0700 (PDT) Date: Mon, 18 Jun 2018 13:47:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529354821; bh=nxMpInkTi4omKvjQFDCH4YFTU2C24u5C9I8w5YpULJo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LPcds9KNjR3Vi9Rh/BZtobhrLBVmyah+wGbQuAMirewpLDDxPfaQcosH5u2UgZzHK 6KF9z+0vuVsODvsbtpH/JcEJaqr4WV0HvCuBfjb1UpvfnVu++rcqYIs5Lvl3BTIXQ3 6cJf3W51zowrT86vK8Ux/B9Z7d8FKjL1HsVGBCZM= From: martinduke Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b281a44f2c35_7a752aba1d036f54113862"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinduke 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.26 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, 18 Jun 2018 20:47:10 -0000 ----==_mimepart_5b281a44f2c35_7a752aba1d036f54113862 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree with @gorryfair -- this is a generic problem with load balancers and ICMP, and there are several workarounds which are outside the scope of QUIC itself. -- 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/1243#issuecomment-398190157 ----==_mimepart_5b281a44f2c35_7a752aba1d036f54113862 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I agree with @gorryfair -- this is a generic problem with load balancers and ICMP, and there are several workarounds which are outside the scope of QUIC itself.

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

----==_mimepart_5b281a44f2c35_7a752aba1d036f54113862-- From nobody Mon Jun 18 14:02:34 2018 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 78788127148 for ; Mon, 18 Jun 2018 14:02:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 whBOQGZKzQei for ; Mon, 18 Jun 2018 14:02:26 -0700 (PDT) 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 346E2130F97 for ; Mon, 18 Jun 2018 14:02:26 -0700 (PDT) Date: Mon, 18 Jun 2018 14:02:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529355745; bh=8pUnpVpXUVfAvT3eg+5h08i+PcgHv9+rx0B8Vhcaedg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VnwllemnOrEYl0oIuj4gmTLuChFOW4uydEmuifkrk5KMBQ+0Q+8qVD42CounzrFIZ QBfgkD8KrZTfaOvFddqUioSgopo/akQzwkmd3cHyyV9YVudK0BkByBOukOiRKHz4RC s2jsfn1q+vun1AKW4uY647uzgtImNOP+IhIkuYEE= From: martinduke Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b281de12458d_29593f98c4a74f8038029"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinduke 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.26 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, 18 Jun 2018 21:02:33 -0000 ----==_mimepart_5b281de12458d_29593f98c4a74f8038029 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinduke requested changes on this pull request. There a bunch of nits, but I have three higher-level comments: 1) There are no MUSTs in the ICMP stuff because you don't always control that in user space. We reached consensus before that PLPMTUD was a SHOULD and all ICMP stuff was a MAY; we should socialize this in the whole group if we upend that now. You've slipped in some SHOULDs that muddy those waters. 2) The added clarification around handshake/non-handshake, and the explicit call for some validation of QUIC headers, if available, is valuable. 3) A big part of this PR is a rewrite of how to handle it when ICMP gives you only 8 bytes. I found the original text to be more clear and concise than the new text, but perhaps we can discuss what the motivation for this rewrite is. > @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields. All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP fragmentation or packet drops. To optimize bandwidth efficiency, endpoints SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}). Endpoints -MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for -detecting the PMTU, setting the PMTU appropriately, and storing the result of -previous PMTU determinations. +MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) How about "ICMP-based"? This eliminates all ambiguity and saves people the trouble of clicking through references to know what we're talking about. > -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially -vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and -reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this -risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP -message to validate the TCP sequence number as valid for the current -connection. However, as QUIC operates over UDP, in IPv4 the echoed information -could consist only of the IP and UDP headers, which usually has insufficient -entropy to mitigate off-path attacks. +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with I disagree with the statement that some ICMP messages have no proof. The 8-byte trailer is sufficient as a proof for TCP, and even if the QUIC case there is enough entropy if we store the right things. > -* Any reduction in PMTU due to a report contained in an ICMP packet is -provisional until QUIC's loss detection algorithm determines that the packet is -actually lost. +Any ICMP messages that fail validation MUST be discarded. The problem with MUSTs in this section is that some user space implementations may not have any control over ICMP handling logic. > +Any reduction in Path MTU due to a report contained in an ICMP Packet Too Big +message (PTB) provisional until QUIC's loss detection algorithm determines that ... SHOULD be provisional... > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP PTB message during a handshake, unless then would +cause a reduction to a Path MTU value smaller than 1280 octets. + +If a client receives an ICMP PTB message that requests it to reduce Path MTU to +a value smaller than 1280 octets during a handshake, then: + +* If the client has another IP address for the server to try, the client should SHOULD > +* Otherwise, if the client can fail over to another protocol, and the ICMP + packet has on-path validation, the client should retry connecting with another SHOULD > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} I like how you separate the handshake issues here, but these also apply to PLPMTUD, yes? > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path This is a significant change. The spec suggests ("SHOULD") that PLPMTUD be used. ICMP-based PMTUD is strictly a MAY. > -The PADDING frame provides a useful option for PMTU probe packets. PADDING +#### ICMP PTB After Handshake {#icmp-ptb-after-handshake} + +If an ICMP PTB message is received after handshake, and the claimed Path MTU is +at least 1280 octets for messages with on-path validation or 1392 for messages +without on-path validations, the Path MTU SHOULD be set accordingly. Otherwise, Same comment: we're elevating ICMP response from a MAY to a SHOULD. > -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially -vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and -reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this -risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP -message to validate the TCP sequence number as valid for the current -connection. However, as QUIC operates over UDP, in IPv4 the echoed information -could consist only of the IP and UDP headers, which usually has insufficient -entropy to mitigate off-path attacks. +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with Zooming out a bit, I think the original text of this section is a bit clearer about what the real problem is. I do think it could use a paragraph like "endpoints SHOULD use fields from the QUIC header, if provided in the ICMP message, to validate that a QUIC packet in flight might have generated the ICMP message." And leave the rest unchanged. > -* Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that -most invalid ICMP messages arrive when there are no DF packets outstanding, and -can therefore be identified as spurious. I guess you deleted this because it didn't meet your 1/2^32 standard? -- 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/1412#pullrequestreview-129725968 ----==_mimepart_5b281de12458d_29593f98c4a74f8038029 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinduke requested changes on this pull request.

There a bunch of nits, but I have three higher-level comments:

  1. There are no MUSTs in the ICMP stuff because you don't always control that in user space. We reached consensus before that PLPMTUD was a SHOULD and all ICMP stuff was a MAY; we should socialize this in the whole group if we upend that now. You've slipped in some SHOULDs that muddy those waters.

  2. The added clarification around handshake/non-handshake, and the explicit call for some validation of QUIC headers, if available, is valuable.

  3. A big part of this PR is a rewrite of how to handle it when ICMP gives you only 8 bytes. I found the original text to be more clear and concise than the new text, but perhaps we can discuss what the motivation for this rewrite is.

In draft-ietf-quic-transport.md:

> @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields.
 All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP
 fragmentation or packet drops. To optimize bandwidth efficiency, endpoints
 SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}).  Endpoints
-MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for
-detecting the PMTU, setting the PMTU appropriately, and storing the result of
-previous PMTU determinations.
+MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}})

How about "ICMP-based"? This eliminates all ambiguity and saves people the trouble of clicking through references to know what we're talking about.

In draft-ietf-quic-transport.md:

>  
-Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially
-vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and
-reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this
-risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP
-message to validate the TCP sequence number as valid for the current
-connection. However, as QUIC operates over UDP, in IPv4 the echoed information
-could consist only of the IP and UDP headers, which usually has insufficient
-entropy to mitigate off-path attacks.
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with

I disagree with the statement that some ICMP messages have no proof. The 8-byte trailer is sufficient as a proof for TCP, and even if the QUIC case there is enough entropy if we store the right things.

In draft-ietf-quic-transport.md:

>  
-* Any reduction in PMTU due to a report contained in an ICMP packet is
-provisional until QUIC's loss detection algorithm determines that the packet is
-actually lost.
+Any ICMP messages that fail validation MUST be discarded.

The problem with MUSTs in this section is that some user space implementations may not have any control over ICMP handling logic.

In draft-ietf-quic-transport.md:

>  
+Any reduction in Path MTU due to a report contained in an ICMP Packet Too Big
+message (PTB) provisional until QUIC's loss detection algorithm determines that

... SHOULD be provisional...

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP PTB message during a handshake, unless then would
+cause a reduction to a Path MTU value smaller than 1280 octets.
+
+If a client receives an ICMP PTB message that requests it to reduce Path MTU to
+a value smaller than 1280 octets during a handshake, then:
+
+* If the client has another IP address for the server to try, the client should

SHOULD

In draft-ietf-quic-transport.md:

>  
+* Otherwise, if the client can fail over to another protocol, and the ICMP
+  packet has on-path validation, the client should retry connecting with another

SHOULD

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}

I like how you separate the handshake issues here, but these also apply to PLPMTUD, yes?

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path

This is a significant change. The spec suggests ("SHOULD") that PLPMTUD be used. ICMP-based PMTUD is strictly a MAY.

In draft-ietf-quic-transport.md:

>  
-The PADDING frame provides a useful option for PMTU probe packets. PADDING
+#### ICMP PTB After Handshake   {#icmp-ptb-after-handshake}
+
+If an ICMP PTB message is received after handshake, and the claimed Path MTU is
+at least 1280 octets for messages with on-path validation or 1392 for messages
+without on-path validations, the Path MTU SHOULD be set accordingly.  Otherwise,

Same comment: we're elevating ICMP response from a MAY to a SHOULD.

In draft-ietf-quic-transport.md:

>  
-Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially
-vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and
-reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this
-risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP
-message to validate the TCP sequence number as valid for the current
-connection. However, as QUIC operates over UDP, in IPv4 the echoed information
-could consist only of the IP and UDP headers, which usually has insufficient
-entropy to mitigate off-path attacks.
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with

Zooming out a bit, I think the original text of this section is a bit clearer about what the real problem is. I do think it could use a paragraph like "endpoints SHOULD use fields from the QUIC header, if provided in the ICMP message, to validate that a QUIC packet in flight might have generated the ICMP message." And leave the rest unchanged.

In draft-ietf-quic-transport.md:

>  
-* Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that
-most invalid ICMP messages arrive when there are no DF packets outstanding, and
-can therefore be identified as spurious.

I guess you deleted this because it didn't meet your 1/2^32 standard?

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

----==_mimepart_5b281de12458d_29593f98c4a74f8038029-- From nobody Mon Jun 18 14:30:52 2018 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 822F4130E7D for ; Mon, 18 Jun 2018 14:30:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uP5ty-9_5Lut for ; Mon, 18 Jun 2018 14:30:45 -0700 (PDT) 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 44806130E47 for ; Mon, 18 Jun 2018 14:30:45 -0700 (PDT) Date: Mon, 18 Jun 2018 14:30:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529357444; bh=wC1SGMa+JR9r2PExcQObbbJmZsOkQ0wVsXASrxSXNyw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AS0wsV7FunLYWBm6vk6wLTukF1iamwM2bsPQGpIjxIws02SARVWy3iqdsLypYl0co O0czK5zZ0Mbmo+c3wj6EyHuhObmgVd3EY0QduJFTV+OlN2E/JaUdREYCzWck1jrkwc 8sAusDJpl1fJ1jdW6n9I3XM321LL2oDv/g/BiUt0= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28248449234_51532af1dcab0f60229072"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:30:49 -0000 ----==_mimepart_5b28248449234_51532af1dcab0f60229072 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -* Any reduction in PMTU due to a report contained in an ICMP packet is +If an ICMP PTB message is received after handshake, and the claimed Path MTU is +at least 1280 octets for messages with on-path validation or 1392 for messages Somewhat arbitrary, examining various tunneling protocols out there to see what seems like a conservative-enough number that is not too small to be significantly concerned with degraded performance. This number would certainly need a wg consensus. The goal was to make sure that in the common case (no attack), we can switch to a workable PMTU immediately. Of course, if the wg believes that 1280 is "large enough" to use it immediately, this would simplify things. -- 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/1412#discussion_r196232146 ----==_mimepart_5b28248449234_51532af1dcab0f60229072 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-* Any reduction in PMTU due to a report contained in an ICMP packet is
+If an ICMP PTB message is received after handshake, and the claimed Path MTU is
+at least 1280 octets for messages with on-path validation or 1392 for messages

Somewhat arbitrary, examining various tunneling protocols out there to see what seems like a conservative-enough number that is not too small to be significantly concerned with degraded performance. This number would certainly need a wg consensus.

The goal was to make sure that in the common case (no attack), we can switch to a workable PMTU immediately.

Of course, if the wg believes that 1280 is "large enough" to use it immediately, this would simplify things.

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

----==_mimepart_5b28248449234_51532af1dcab0f60229072-- From nobody Mon Jun 18 14:31:16 2018 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 0DF22130F79 for ; Mon, 18 Jun 2018 14:31:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OYIeqztaaOkg for ; Mon, 18 Jun 2018 14:31:10 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8173130E47 for ; Mon, 18 Jun 2018 14:31:09 -0700 (PDT) Date: Mon, 18 Jun 2018 14:31:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529357469; bh=dvoIfvy/A7tDHGccK18j0uyfDT9p15yYb6kBncV6+Ys=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1GvIVT8uoZ4wabxA8nbmDrxCxE6GeqGMtqP2G/a4F8g1zb9BhM81q6YUq/TmC+dGV qK+DMA6ixYwnCQ8BsOgMZj81dx6nnak/8bwYC2x68QqCLebxXWPFd3dIobDVifmFIg vXYf9Bh8fH0nM9P/0creWSsZZGEml290l142HZME= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28249d55340_549b2ad2fa5e6f58373757"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:31:14 -0000 ----==_mimepart_5b28249d55340_549b2ad2fa5e6f58373757 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain application data, aggressive increases in probe size carry fewer consequences. +## Responding to ICMP "Unreachable" messages {#icmp-unreach} + +When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake, +the response SHOULD be identical to receiving an ICMP TPB message that announces +a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}). + +When an ICMP "Unreachable" message is received after the handshake, the QUIC +endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}). Sending Fixing and rewriting this. -- 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/1412#discussion_r196232260 ----==_mimepart_5b28249d55340_549b2ad2fa5e6f58373757 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -3228,6 +3261,18 @@ increases in the size of probe packets. As QUIC probe packets need not contain
 application data, aggressive increases in probe size carry fewer consequences.
 
 
+## Responding to ICMP "Unreachable" messages {#icmp-unreach}
+
+When a QUIC endpoint receives an ICMP "Unreachable" message during a handshake,
+the response SHOULD be identical to receiving an ICMP TPB message that announces
+a Path MTU smaller than 1280 octets (see {{icmp-pmtu}}).
+
+When an ICMP "Unreachable" message is received after the handshake, the QUIC
+endpoint should send a PATH_CHALLENGE frame ({{frame-path-challenge}}).  Sending

Fixing and rewriting this.

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

----==_mimepart_5b28249d55340_549b2ad2fa5e6f58373757-- From nobody Mon Jun 18 14:44:22 2018 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 C0375130FF1 for ; Mon, 18 Jun 2018 14:44:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 GOeJCOKBFkeC for ; Mon, 18 Jun 2018 14:43:56 -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 019A4131027 for ; Mon, 18 Jun 2018 14:43:53 -0700 (PDT) Date: Mon, 18 Jun 2018 14:43:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358232; bh=eSRlwSlzZD4MDxeoVbOdwlppLvhVwtamK3nSbuwj8Io=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CiiQ/WB7SE8dYRDzd+R9jOTGxR8PHHBN1GT76Hs1/kGpSdYU0EzngE1y6wYS91nD8 esuZesqrmUm/gZloX64GaucWCMx4/3f56CgatX2bfdpI2T97ZqvupZd4Y23f7xoX9W OAS/Nl5pOU/jJlay79amDzQyenZ4Gr6zyBDQdgS8= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b282798dede0_66273f9d56caaf84271793"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:44:12 -0000 ----==_mimepart_5b282798dede0_66273f9d56caaf84271793 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially -vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and -reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this -risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP -message to validate the TCP sequence number as valid for the current -connection. However, as QUIC operates over UDP, in IPv4 the echoed information -could consist only of the IP and UDP headers, which usually has insufficient -entropy to mitigate off-path attacks. +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with I'd say that not just the QUIC header but, more importantly, the QUIC encrypted section, since it has more entropy. But, I agree, instead of coming up with metrics, we should just leave the specifics undefined. I like your wording. Will adapt and incorporate. -- 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/1412#discussion_r196235331 ----==_mimepart_5b282798dede0_66273f9d56caaf84271793 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially
-vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and
-reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this
-risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP
-message to validate the TCP sequence number as valid for the current
-connection. However, as QUIC operates over UDP, in IPv4 the echoed information
-could consist only of the IP and UDP headers, which usually has insufficient
-entropy to mitigate off-path attacks.
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with

I'd say that not just the QUIC header but, more importantly, the QUIC encrypted section, since it has more entropy.

But, I agree, instead of coming up with metrics, we should just leave the specifics undefined. I like your wording. Will adapt and incorporate.

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

----==_mimepart_5b282798dede0_66273f9d56caaf84271793-- From nobody Mon Jun 18 14:44:42 2018 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 E579A130E45 for ; Mon, 18 Jun 2018 14:44:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ypgJMYL8GBaR for ; Mon, 18 Jun 2018 14:44:37 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4910E129C6B for ; Mon, 18 Jun 2018 14:44:37 -0700 (PDT) Date: Mon, 18 Jun 2018 14:44:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358276; bh=vo4PToYSEEXSctayoR9feAJ1+Gk36vmOmLvhaOLfAnc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xcpbLqphy5N+tdlDiIWoGZ2BGeDnTieO7WouWqZciK0Mk/odc23/JIeMxhQqTsVLG JJbZLs8v6Q/pGKjJXDNONtMXaZLVbQ80XFq13uUs34h21RTCA8GcH4EYdCDCmklG8h ZlF4LsU5C8Hz3eEky3QD1aSOh5GkWHQVB/ND4U3Y= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2827c492e4f_29593f98c4a74f8019942f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:44:40 -0000 ----==_mimepart_5b2827c492e4f_29593f98c4a74f8019942f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially -vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and -reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this -risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP -message to validate the TCP sequence number as valid for the current -connection. However, as QUIC operates over UDP, in IPv4 the echoed information -could consist only of the IP and UDP headers, which usually has insufficient -entropy to mitigate off-path attacks. +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with (As for an 8-byte proof, it is sufficient for TCP but not QUIC. Hence this entire discussion.) -- 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/1412#discussion_r196235506 ----==_mimepart_5b2827c492e4f_29593f98c4a74f8019942f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-Traditional ICMP-based path MTU discovery in IPv4 {{!PMTUDv4}} is potentially
-vulnerable to off-path attacks that successfully guess the IP/port 4-tuple and
-reduce the MTU to a bandwidth-inefficient value. TCP connections mitigate this
-risk by using the (at minimum) 8 bytes of transport header echoed in the ICMP
-message to validate the TCP sequence number as valid for the current
-connection. However, as QUIC operates over UDP, in IPv4 the echoed information
-could consist only of the IP and UDP headers, which usually has insufficient
-entropy to mitigate off-path attacks.
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with

(As for an 8-byte proof, it is sufficient for TCP but not QUIC. Hence this entire discussion.)

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

----==_mimepart_5b2827c492e4f_29593f98c4a74f8019942f-- From nobody Mon Jun 18 14:47:12 2018 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 77A93130FFC for ; Mon, 18 Jun 2018 14:47:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OXxdczg4rMdk for ; Mon, 18 Jun 2018 14:47:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 749E5130FDF for ; Mon, 18 Jun 2018 14:47:07 -0700 (PDT) Date: Mon, 18 Jun 2018 14:47:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358426; bh=Y/a9A+nqwlgpSE+MWFeu27Pp9u5v1vumdYcDZhITfDI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iAU8PivBybcjf3oQTFdQEAoqbk3+TLZEBPDmZ6uXCKUcady6h9x67GQx9yenlpkaV t2iY8qr7eTqz7TRrgYfbA6W9Y7KlV7CWYXIvqmEfuNeW9nSSnm6q1gdHTeuzqS6Ck0 k2vCfhvbUskn8cYFFlFvqIto1ydU6tflUoZy1nBs= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28285abccc7_5752ab20e3c8f582167ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:47:10 -0000 ----==_mimepart_5b28285abccc7_5752ab20e3c8f582167ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -* Any reduction in PMTU due to a report contained in an ICMP packet is -provisional until QUIC's loss detection algorithm determines that the packet is -actually lost. +Any ICMP messages that fail validation MUST be discarded. The language in this section says that validation is a SHOULD. But if that validation fails, discarding is a MUST. (And if the validation is not done, since it is not mandatory, then the signal SHOULD be treated as a signal without an on-path proof.) Do you still think this is a problem? -- 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/1412#discussion_r196236060 ----==_mimepart_5b28285abccc7_5752ab20e3c8f582167ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-* Any reduction in PMTU due to a report contained in an ICMP packet is
-provisional until QUIC's loss detection algorithm determines that the packet is
-actually lost.
+Any ICMP messages that fail validation MUST be discarded.

The language in this section says that validation is a SHOULD. But if that validation fails, discarding is a MUST. (And if the validation is not done, since it is not mandatory, then the signal SHOULD be treated as a signal without an on-path proof.)

Do you still think this is a problem?

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

----==_mimepart_5b28285abccc7_5752ab20e3c8f582167ac-- From nobody Mon Jun 18 14:49:50 2018 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 5E9C3130EA0 for ; Mon, 18 Jun 2018 14:49:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 y1L3LPteqLEk for ; Mon, 18 Jun 2018 14:49:46 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2BA5129C6B for ; Mon, 18 Jun 2018 14:49:45 -0700 (PDT) Date: Mon, 18 Jun 2018 14:49:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358585; bh=xdzmP++GdR18ZOqjU/1/hOzXzCAH4W8bIg79ezzCGU4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0b9oaXrQ/8GzI4LfGoEZO0A+XtZgA8/oKl/BYVME82sT4K5c4LnWPE+VDaDB9pXeL rhEo90k3POCK0kxPhyXirurixvrPKn9PjyG3V2sAj2qhydVJDNIbu9S7OAdoEo3OQx C1nNYWvD448t5sJMiwJS3qKTQ+5nLSfuLWjjyEB0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2828f93c4e8_289a2aac1d404f54347915"; 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.26 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, 18 Jun 2018 21:49:49 -0000 ----==_mimepart_5b2828f93c4e8_289a2aac1d404f54347915 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Both current and DT output text restricts the server from sending more than three "packets" to the client until address validation has occurred. However, in the presence of coalesced packets, three packets could be contained in a single UDP datagram: Initial, Handshake, 1-RTT with response to the client's 0-RTT requests. Is this text actually intending to limit the transmission to three *datagrams*? -- 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/1458 ----==_mimepart_5b2828f93c4e8_289a2aac1d404f54347915 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Both current and DT output text restricts the server from sending more than three "packets" to the client until address validation has occurred. However, in the presence of coalesced packets, three packets could be contained in a single UDP datagram: Initial, Handshake, 1-RTT with response to the client's 0-RTT requests.

Is this text actually intending to limit the transmission to three datagrams?

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

----==_mimepart_5b2828f93c4e8_289a2aac1d404f54347915-- From nobody Mon Jun 18 14:50:12 2018 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 D4A89130EA0 for ; Mon, 18 Jun 2018 14:50:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 9i-Ehp8RUjND for ; Mon, 18 Jun 2018 14:50:08 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 20D04129C6B for ; Mon, 18 Jun 2018 14:50:08 -0700 (PDT) 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=BckL2rOI+RQJGjwCEtdSo8wBsYY=; b=FtJUX7bmYUO+pDin XwvuOCum6Z4pUJMD+QF8U4YtWeKO0IMe+p4Viyj0kVrX/qtMWXJ/rJEeomqdyCE2 DNYm7NXjeHsBKcNq+htbTL8ldO0R5+Yi2cgaPliq8DdxyXXh6Hma5xw93KFF/3xO IF7xbJQ0af7xH7mS/tne7jy46G8= Received: by filter1546p1mdw1.sendgrid.net with SMTP id filter1546p1mdw1-30587-5B28290F-13 2018-06-18 21:50:07.295626499 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0012p1iad2.sendgrid.net (SG) with ESMTP id smJODCVwSUejCOQTZlonRg for ; Mon, 18 Jun 2018 21:50:07.189 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id 3D51780081 for ; Mon, 18 Jun 2018 14:50:07 -0700 (PDT) Date: Mon, 18 Jun 2018 21:50:07 +0000 (UTC) From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28290f3a29a_4f192b1028c7cf5046148e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1HvaXURhQk46JW0HpSvaYO1hCvfQr/27cnzZ oseDAYeLQgZ8rrlAENoR+QwQmFm/R6ikBGFIspMJ9J+Q/Euz0Ic90uk0z0csBqtZTZExMUQbSVUtvS 9pjwec1OpAUxZz2m+Rpdhi8e8C6iWWSbXCPUfwl7w/YpZpVWYxemTCEepcmPK6+NLcjv7Uyx4jDu8f Q= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 21:50:10 -0000 ----==_mimepart_5b28290f3a29a_4f192b1028c7cf5046148e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} PLPMTUD take time to do its work (it is loss/timeout-based). The purpose of this discussion is to identify conditions, when you can trust ICMP immediately and not have to resort to PLPMTUD (especially during handshake). -- 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/1412#discussion_r196236756 ----==_mimepart_5b28290f3a29a_4f192b1028c7cf5046148e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}

PLPMTUD take time to do its work (it is loss/timeout-based). The purpose of this discussion is to identify conditions, when you can trust ICMP immediately and not have to resort to PLPMTUD (especially during handshake).

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

----==_mimepart_5b28290f3a29a_4f192b1028c7cf5046148e-- From nobody Mon Jun 18 14:53:40 2018 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 49688129C6B for ; Mon, 18 Jun 2018 14:53:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 dimYFqHjF-o5 for ; Mon, 18 Jun 2018 14:53:34 -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 2C1C2130F80 for ; Mon, 18 Jun 2018 14:53:34 -0700 (PDT) Date: Mon, 18 Jun 2018 14:53:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358813; bh=B9QiRNA2kGcCcu8SOzbqmOWCVv0pRjc89Fp/ChUCdE4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DW9t06vOKs4An2mUU9p7M9b15KQfQwv9dHZeTF6yOwJOd/XpBQcTFIrcZqeOp/XPG Hh2CrDTBfcO8VaJzW/+Vk9w+xvjjy706GmAzu+8yW0uNZuaBXX3mV5gIaVwPWn2o9w o/ZwekU93QTGFasTE2RjEBr1nBPyc1IvWMW5z9d0= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2829dd7987b_30292aeea8448f6072413"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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, 18 Jun 2018 21:53:37 -0000 ----==_mimepart_5b2829dd7987b_30292aeea8448f6072413 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I've always assumed it meant three UDP datagrams, and not QUIC packets. I think that makes the most sense. -- 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/1458#issuecomment-398207770 ----==_mimepart_5b2829dd7987b_30292aeea8448f6072413 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I've always assumed it meant three UDP datagrams, and not QUIC packets. I think that makes the most sense.

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

----==_mimepart_5b2829dd7987b_30292aeea8448f6072413-- From nobody Mon Jun 18 14:54:35 2018 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 C1BFD130EC2 for ; Mon, 18 Jun 2018 14:54:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uO320jIEBiWU for ; Mon, 18 Jun 2018 14:54:27 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33E61129C6B for ; Mon, 18 Jun 2018 14:54:27 -0700 (PDT) Date: Mon, 18 Jun 2018 14:54:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529358866; bh=5v+rBdEZqhsPU9/S45eZ/FMs2d2j5T3ZtCjey5e7uS8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=blpRbftR+LX15XChtq35f+MpVHoQ5ZI+Mz52u9aqzEFwzwv5H3qtV80Tu842kL0Fx oeav2267YYg+/ssOAFkcNtg2tfTlpmZJh7DqQUtY6PSDSHwrevb+V2Y6Np7hoTR007 CTqkCRuIFhzxCGbDXlh+BgWA9SsVVTuUCCixPu+Y= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b282a128d818_30202aeea8448f6088586"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:54:29 -0000 ----==_mimepart_5b282a128d818_30202aeea8448f6088586 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path Yes, this would need to be reconfirmed. I do believe that we should encourage implementations to use the best available signal, including ICMP, especially when we have reasons to trust it. Performance is important for QUIC, and it is double-important for handshake, and ICMP works much faster than PLPMTUD. -- 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/1412#discussion_r196237806 ----==_mimepart_5b282a128d818_30202aeea8448f6088586 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path

Yes, this would need to be reconfirmed. I do believe that we should encourage implementations to use the best available signal, including ICMP, especially when we have reasons to trust it. Performance is important for QUIC, and it is double-important for handshake, and ICMP works much faster than PLPMTUD.

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

----==_mimepart_5b282a128d818_30202aeea8448f6088586-- From nobody Mon Jun 18 14:57:51 2018 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 76B7E131021 for ; Mon, 18 Jun 2018 14:57:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7-3k5nwLPuY9 for ; Mon, 18 Jun 2018 14:57:37 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A25130FB8 for ; Mon, 18 Jun 2018 14:57:37 -0700 (PDT) Date: Mon, 18 Jun 2018 14:57:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529359056; bh=n3wW4ANhP/KCiY6fM87+hvSvFJIxA7PoQQD4COfpTgI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=csbitTSLXG6ys2pgvyqTPVQQfVKwaalTYnqqBVxzg/ZLD0XoT8nJ1YV7xEKRDONLs yUltIwz16duF+OkMIS08TpUcF+/X2C3Ud1piq3pZE78g8mPY3ONz0k5dHEDWIAGXaC Gj5aUijWrs+kPb+XqDL3BiSyk8zx55hcg4uDN49g= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b282ad071b5f_216a2b0d51906f58130387"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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, 18 Jun 2018 21:57:48 -0000 ----==_mimepart_5b282ad071b5f_216a2b0d51906f58130387 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -* Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that -most invalid ICMP messages arrive when there are no DF packets outstanding, and -can therefore be identified as spurious. LOL. Mostly because I received comments that we recommend DF to be set on all packets, and this is going against that recommendation. (But being pedantic, that standard was for on-path proof, while this discussion is for validation packets w/o on-path proof.) More importantly, the entire standard thing is gone now. I will further revise it to use your latest feedback as to the wording (ie. "use the data from the packet" instead of prescribing standards or which data to use). -- 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/1412#discussion_r196238564 ----==_mimepart_5b282ad071b5f_216a2b0d51906f58130387 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-* Set the IPv4 Don't Fragment (DF) bit on a small proportion of packets, so that
-most invalid ICMP messages arrive when there are no DF packets outstanding, and
-can therefore be identified as spurious.

LOL. Mostly because I received comments that we recommend DF to be set on all packets, and this is going against that recommendation.

(But being pedantic, that standard was for on-path proof, while this discussion is for validation packets w/o on-path proof.)

More importantly, the entire standard thing is gone now. I will further revise it to use your latest feedback as to the wording (ie. "use the data from the packet" instead of prescribing standards or which data to use).

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

----==_mimepart_5b282ad071b5f_216a2b0d51906f58130387-- From nobody Mon Jun 18 15:09:22 2018 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 68CE6130E35 for ; Mon, 18 Jun 2018 15:09:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 VT4FkfiTbpvk for ; Mon, 18 Jun 2018 15:09:19 -0700 (PDT) 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 CDC25129385 for ; Mon, 18 Jun 2018 15:09:18 -0700 (PDT) Date: Mon, 18 Jun 2018 15:09:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529359758; bh=WVq5Q7w3FrlrXV29SbCuQjx3RHaw6b9Z0E4zCzUGON4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l9GTReqYd6TqLmKB1OBGYlD6rKi6XNKKOpjqytqjVeaHZkabQDXfWJYEIGpKihWbo 07auXODfgNghmQfPdqBqIGYbP9VnnET3pSnTxgPXW3tpkiBeCkQP1QUHBoS7XCElnh p1XCvBqB7Xebl24CTQK28Wpi1Qv9U3G2tGigJWfs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b282d8e1c78_6142b0de3adaf5418798d"; 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.26 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, 18 Jun 2018 22:09:21 -0000 ----==_mimepart_5b282d8e1c78_6142b0de3adaf5418798d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think when we wrote that, we didn't have coalesced packets, so they were equivalent statements. -- 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/1458#issuecomment-398211383 ----==_mimepart_5b282d8e1c78_6142b0de3adaf5418798d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think when we wrote that, we didn't have coalesced packets, so they were equivalent statements.

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

----==_mimepart_5b282d8e1c78_6142b0de3adaf5418798d-- From nobody Mon Jun 18 15:53:07 2018 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 D392A130E4D for ; Mon, 18 Jun 2018 15:53:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bpOlM-Pw0k6t for ; Mon, 18 Jun 2018 15:52:58 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B69C130E36 for ; Mon, 18 Jun 2018 15:52:58 -0700 (PDT) Date: Mon, 18 Jun 2018 15:52:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529362377; bh=a5MGVkl/PO8uQ8mRHc/VIBGK5T2ayHzSvBhRyC/dGtk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CDuvMmnc+JnNFQ0QG/dGJvlveWWbZqXGL+SZFMkI9oKsQ4qGerTMxCs/Av5X8d4/e h8w5KBXSm3HQuvz+RwJEDxgcinRcsRlpIOlZ2Zm5z0ywlpMiPhetIa0I6AMF6VobIl zjGLv7aCRa+ORh7gRvsjxNneTb8SuyIJ7cfrAl9M= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2837c92f384_36672ab146dcef5c816de"; 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.26 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, 18 Jun 2018 22:53:06 -0000 ----==_mimepart_5b2837c92f384_36672ab146dcef5c816de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable MikeBishop commented on this pull request. Lots of editorial comments, but the content looks good. > = +Unlike TLS over TCP, QUIC applications which want to send data do not +send it through TLS "application_data" records. Rather, they send it +as QUIC STREAM frames which are then carried in QUIC packets. + + +# Carrying TLS Messages {#carrying-tls} + +QUIC carries TLS handshake data in CRYPTO_HS frames, each of which Bikeshed: I hate this name. Why not simply CRYPTO frames or HANDSHAKE f= rames? Compounding the two seems unnecessary. > +and encrypted under the current TLS encryption level. +As with TLS over TCP, once TLS handshake data has +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: This statement is confusing, as it precedes a bulleted list of things whi= ch don't exist in TLS over TCP. Perhaps this should be reframed in terms= of the types of data TLS/TCP permits, and the QUIC equivalents that carr= y it? > +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level.= +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. There are so many exceptions, it almost seems more efficient to indicate = what frames *cannot* appear in different levels. STREAM and flow control= frames aren't permitted in Initial or Handshake; *_CLOSE aren't permitte= d in 0-RTT, except maybe APPLICATION_CLOSE. > = ## Interface to TLS = -As shown in {{schematic}}, the interface from QUIC to TLS consists of fo= ur -primary functions: Handshake, Source Address Validation, Key Ready Event= s, and -Secret Export. +As shown in {{schematic}}, the interface from QUIC to TLS consists of th= ree +primary functions: + +- Sending and receiving handshake messages +- Rekeying (both in and out) Perhaps "send and receive" here? Otherwise, it could sound like the key = is both coming from and being supplied to TLS. > = In order to drive the handshake, TLS depends on being able to send and r= eceive -handshake messages on stream 0. There are two basic functions on this +handshake messages. There are two basic functions on this Rewrap. > + +At any given time, an endpoint will have a current sending encryption +level and receiving encryption level. Each encryption level is +associated with a different flow of bytes, which is reliably +transmitted to the peer in CRYPTO_HS frames. When TLS provides handshake= +octets to be sent, they are appended to the current flow and +will eventually be transmitted under the then-current key. + +When an endpoint receives a QUIC packet containing a CRYPTO_HS frame fro= m +the network, it proceeds as follows: + +- If the packet was in the current receiving encryption level, sequence + the data into the input flow as usual. As with STREAM frames, + the offset is used to find the proper location in the data sequence. + If the result of this process is that new data is available, then + it is delivered to TLS. Might be worth mentioning that bytes are always provided in-order to TLS,= since QUIC is otherwise permitted to support out-of-order delivery on st= reams. > -request of QUIC, including the value extracted from the cookie extensi= on. In -response to this request, QUIC cannot ask for client address validation,= it can -only abort or permit the connection attempt to proceed. - -QUIC can provide a new address validation token for use in session resum= ption at -any time after the handshake is complete. Each time a new token is prov= ided TLS -generates a NewSessionTicket message, with the token included in the tic= ket. - -See {{client-address-validation}} for more details on client address val= idation. - - -### Key Ready Events - -TLS provides QUIC with signals when 0-RTT and 1-RTT keys are ready for u= se. +At each change of encryption level in either direction, TLS signals +QUIC, providing the new level and the encryption keys. These events are not asynchronous, they always occur immediately after T= LS is Comma splice; either use a semicolon or divide into separate sentences. = (Though, yes, this line wasn't changed.) > If 0-RTT is possible, it is ready after the client sends a TLS ClientH= ello message or the server receives that message. After providing a QUIC cli= ent with -the first handshake octets, the TLS stack might signal that 0-RTT keys a= re -ready. On the server, after receiving handshake octets that contain a +the first handshake octets, the TLS stack might signal the change to the= +the 0-RTT keys. On the server, after receiving handshake octets that con= tain a ...and I think it reads better without "the" at all. > ClientHello message, a TLS server might signal that 0-RTT keys are ava= ilable. = -1-RTT keys are used for packets in both directions. 0-RTT keys are only= -used to protect packets sent by the client. - - -### Secret Export +Note that although TLS only uses one encryption level at a time, QUIC +may use more than one level. For instance, after sending its Finished May? Will have to, I believe. > = -## QUIC Key Expansion {#key-expansion} +A server rejects 0-RTT by rejecting 0-RTT at the TLS layer. This result= s in +early exporter keys being unavailable, thereby preventing the use of 0-R= TT for +QUIC. Under this model, exporters (early or otherwise) have nothing to do with = the use of a particular encryption level for QUIC, IIUC. > = -QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=3DRFC586= 9}} with -the same hash function negotiated by TLS for key derivation. For exampl= e, if -TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is us= ed. +In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section +4.1.4) can be used to correct a client's incorrect KeyShare extension +as well as for a stateless round trip check. From the perspective of round-trip > = -QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=3DRFC586= 9}} with -the same hash function negotiated by TLS for key derivation. For exampl= e, if -TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is us= ed. +In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section +4.1.4) can be used to correct a client's incorrect KeyShare extension +as well as for a stateless round trip check. From the perspective of +QUIC, this just looks like additional messages carried in the Initial +encryption level. Although it is in principle possible to use this +feature for address verification in QUIC, QUIC implementations SHOULD +instead use the Retry feature ({{QUIC-TRANSPORT}}; Section 4.4.2)). Might be worth explicitly noting that this *is* still used for incorrect = key shares. > = -~~~ -struct { - uint16 length =3D Length; - opaque label<6..255> =3D "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the T= LS +handshake, using the AEAD algorithm negotiated by TLS. Since TCP doesn't actually do the encryption, perhaps this would be more = clearly stated as "As with the TLS record layer used with TCP, QUIC...." > = -For example, assuming a hash function with a 32 octet output, derivation= for a -client packet protection key would use HKDF-Expand with an `info` parame= ter of -0x00200851554943206b6579. +The keys for the Initial encryption level are computed based on +the client's first Destination Connection Id, as described in ID > = -Packets that carry the TLS handshake (Initial, Retry, and Handshake) are= -protected with a secret derived from the Destination Connection ID field= from -the client's Initial packet. Specifically: +Initial packets are protected with +a secret derived from the Destination Connection ID field from the clien= t's +Initial packet. Specifically: First Initial packet, or does the key change with the DCID of each new In= itial the client sends? > ~~~ = The hash function for HKDF when deriving handshake secrets and keys is S= HA-256 -{{!SHA=3DDOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with QHK= DF-Expand -is the connection ID chosen by the client. +{{!SHA=3DDOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with +HKDF-Expand-Label is the connection ID chosen by the client. initial Destination Connection ID > @@ -743,121 +653,11 @@ Note: = : The Destination Connection ID is of arbitrary length, and it could be = zero length if the server sends a Retry packet with a zero-length Source Co= nnection - ID field. In this case, the handshake keys provide no assurance to th= e client + ID field. In this case, the initial keys provide no assurance to the = client Initial > @@ -873,26 +673,20 @@ from the packet number. All QUIC packets other than Version Negotiation and Stateless Reset pack= ets are protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shar= ed secret, packets are protected with AEAD_AES_128_GCM and a key derived fr= om the -client's connection ID (see {{handshake-secrets}}). This provides prote= ction +client's connection ID (see {{initial-secrets}}). This provides protect= ion initial Destination Connection ID > = -### Retransmission and Acknowledgment of Unprotected Packets +: 0-RTT data can be acknowledged by the server as it receives it, but an= y Is this being formatted the way you want it? It's being rendered as a de= finition of the previous line (MUST NOT use 0-RTT keys), which looks a li= ttle weird for prose. It seems like it should just be a straight paragra= ph of text.... > = -A HelloRetryRequest handshake message might be used to reject an initial= -ClientHello. A HelloRetryRequest handshake message is sent in a Retry p= acket; -any second ClientHello that is sent in response uses a Initial packet ty= pe. -These packets are only protected with a predictable key (see -{{handshake-secrets}}). This is natural, because no shared secret will = be -available when these messages need to be sent. Upon receipt of a -HelloRetryRequest, a client SHOULD cease any transmission of 0-RTT data;= 0-RTT -data will only be discarded by any server that sends a HelloRetryRequest= . +Due to reordering and loss, protected packets might be received by an en= dpoint +before the final TLS handshake messages are received. A client will be = unable +to decrypt 1-RTT packets from the server, whereas a server will be able = to +decrypt 1-RTT packets from the client. However, +a server MUST NOT process data from incoming 1-RTT protected packets MUST NOT (BUT WE KNOW YOU WILL). 6919 OUGHT TO have mentioned that one. > = -Once 1-RTT keys are available to an endpoint, it no longer needs the TLS= -handshake messages that are carried in unprotected packets. However, a = server -might need to retransmit its TLS handshake messages in response to recei= ving an -unprotected packet that contains ACK frames. A server MUST process ACK = frames -in unprotected packets until the TLS handshake is reported as complete, = or it -receives an ACK frame in a protected packet that acknowledges all of its= -handshake messages. +Receiving and verifying the TLS Finished message is critical in +ensuring the integrity of the TLS handshake. A server MUST NOT use +1-RTT protected packets from the client prior to verifying the client +Finished message if its response depends on client authentication. But it provides an additional conditional that the previous one doesn't w= hich is interest. MUST NOT ... *if* its response depends on client authe= ntication. So we're willing to tolerate a tampered ClientHello for trans= ferring public data, and just assume decryption will fail on the other si= de? > -server has chosen to use a pre-shared key - the pre-shared key binder = (see -Section 4.2.8 of {{!TLS13}}). Verifying these values provides the serve= r with -an assurance that the ClientHello has not been modified. - -A server could receive packets protected with 0-RTT keys prior to receiv= ing a -TLS ClientHello. The server MAY retain these packets for later decrypti= on in -anticipation of receiving a ClientHello. - -Receiving and verifying the TLS Finished message is critical in ensuring= the -integrity of the TLS handshake. A server MUST NOT use protected packets= from -the client prior to verifying the client Finished message if its respons= e -depends on client authentication. +It is also possible for the attacker to tamper with data that +is carried in Handshake packets, but because that tampering +requires modifying TLS handshake messages, that tampering will be +detected as soon as the TLS handshake completes. "...will cause the TLS handshake to fail."? > @@ -1592,6 +996,11 @@ version of QUIC defined in {{QUIC-TRANSPORT}} is = used. The quic_transport_parameters extension is carried in the ClientHello an= d the EncryptedExtensions messages during the handshake. = +While the transport parameters are technically available prior to the +completion of the handshake, they cannot be fully trusted until the hand= shake +completes, and reliance on them should be minimized. +However, any tampering with the parameters will be detected +when the handshake completes. Same as previous. Also, rewrap. > = All these packets use the long header and contain the current QUIC versi= on in the version field. = -In order to prevent tampering by version-unaware middleboxes, handshake = packets -are protected with a connection- and version-specific key, as described = in -{{QUIC-TLS}}. This protection does not provide confidentiality or integr= ity -against on-path attackers, but provides some level of protection against= -off-path attackers. +In order to prevent tampering by version-unaware middleboxes, Initial +packets are protected with a connection- and version-specific keys "with ~a~... keys" > = = ### Initial Packet {#packet-initial} = The Initial packet uses long headers with a type value of 0x7F. It carr= ies the -first cryptographic handshake message sent by the client. +first CRYPTO_HS frames sent by the client as well as the +cryptographic messages sent by the server to perform key exchange. The I= nitial +packet is protected by Initial keys as described in {{QUIC-TLS}}. Rewrap. > +Token Length: + +: A variable-length integer specifying the length of the Token field, in= bytes. +It may be zero if no token is present. The server MUST send a zero-lengt= h +token. + +Token: + +: An optional token blob previously received in either a Retry packet or= +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that co= ntains +an initial cryptographic handshake message. This includes all cases wher= e a new +packet containing the initial cryptographic message needs to be created,= this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). "This includes..., this includes...." is an awkward construction. Perhap= s "In addition to the first packet(s), this also includes all cases where= a new packet containing the initial cryptographic message needs to be cr= eated, such as...."? > +Token: + +: An optional token blob previously received in either a Retry packet or= +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that co= ntains +an initial cryptographic handshake message. This includes all cases wher= e a new +packet containing the initial cryptographic message needs to be created,= this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial.= A +server may send multiple Initial packets. The cryptographic key exchang= e could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) conveys =3D> includes > +Token: + +: An optional token blob previously received in either a Retry packet or= +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that co= ntains +an initial cryptographic handshake message. This includes all cases wher= e a new +packet containing the initial cryptographic message needs to be created,= this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial.= A +server may send multiple Initial packets. The cryptographic key exchang= e could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) Not necessarily; it could just include ACKs of handshake messages. > +: An optional token blob previously received in either a Retry packet = or +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that co= ntains +an initial cryptographic handshake message. This includes all cases wher= e a new +packet containing the initial cryptographic message needs to be created,= this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial.= A +server may send multiple Initial packets. The cryptographic key exchang= e could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete sent > +The client and server use the Initial packet type for any packet that = contains +an initial cryptographic handshake message. This includes all cases wher= e a new +packet containing the initial cryptographic message needs to be created,= this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial.= A +server may send multiple Initial packets. The cryptographic key exchang= e could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete +first message MUST fit in a single packet (see {{handshake}}). Note that= if +the server sends a HelloRetryRequest, the client will send a second Init= ial +packet with a CRYPTO_HS frame starting immediately after the first one. "starting immediately after" could be misconstrued as packet layout. Per= haps "continuing the sequence of handshake messages"? > + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete +first message MUST fit in a single packet (see {{handshake}}). Note that= if +the server sends a HelloRetryRequest, the client will send a second Init= ial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously r= eceived +a Retry packet from the server, it populates the Destination Connection = ID field +with a randomly selected value. This MUST be at least 8 octets in lengt= h. Until +a packet is received from the server, the client MUST use the same rando= m value +unless it also changes the Source Connection ID (which effectively start= s a new Is there a way in which this is just "effectively"? Maybe "...unless it = abandons the connection attempt and begins a new one. In this case, the = client MUST change the Source Connection ID." > +containing a cryptographic handshake message. The first CRYPTO_HS fram= e +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete +first message MUST fit in a single packet (see {{handshake}}). Note that= if +the server sends a HelloRetryRequest, the client will send a second Init= ial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously r= eceived +a Retry packet from the server, it populates the Destination Connection = ID field +with a randomly selected value. This MUST be at least 8 octets in lengt= h. Until +a packet is received from the server, the client MUST use the same rando= m value +unless it also changes the Source Connection ID (which effectively start= s a new +connection attempt). The randomized Destination Connection ID is used t= o +determine packet protection keys. Initial > = The client populates the Source Connection ID field with a value of its = choosing and sets the SCIL field to match. = -The first Initial packet that is sent by a client contains a packet numb= er of 0. -All subsequent packets contain a packet number that is incremented by at= least -one, see ({{packet-numbers}}). - -The payload of an Initial packet conveys a STREAM frame (or frames) for = stream -0 containing a cryptographic handshake message. The stream in this pack= et -always starts at an offset of 0 (see {{stateless-retry}}) and the comple= te -cryptographic handshake message MUST fit in a single packet (see {{hands= hake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet Perhaps "the" connection ID? > = The client populates the Source Connection ID field with a value of its = choosing and sets the SCIL field to match. = -The first Initial packet that is sent by a client contains a packet numb= er of 0. -All subsequent packets contain a packet number that is incremented by at= least -one, see ({{packet-numbers}}). - -The payload of an Initial packet conveys a STREAM frame (or frames) for = stream -0 containing a cryptographic handshake message. The stream in this pack= et -always starts at an offset of 0 (see {{stateless-retry}}) and the comple= te -cryptographic handshake message MUST fit in a single packet (see {{hands= hake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection This implies the server can have multiple consistent SCIDs during the han= dshake. "...MUST use a consistent SCID during the handshake." > - -The payload of an Initial packet conveys a STREAM frame (or frames) for = stream -0 containing a cryptographic handshake message. The stream in this pack= et -always starts at an offset of 0 (see {{stateless-retry}}) and the comple= te -cryptographic handshake message MUST fit in a single packet (see {{hands= hake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection +IDs during the handshake. + +On first receiving an Initial or Retry packet from the server, the +client uses the Source Connection ID supplied by the server as the +Destination Connection ID for subsequent packets. The client MUST +discard any subsequent packets it receives with different "with a different SCID" probably, since the packet contains only one SCID= . > + +#### Tokens + +If the client has a suitable token available from a previous connection,= +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID t= o +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated Additionally, the token could have been issued by a previous iteration of= the server with a different key / token generation scheme, as described = in the following paragraph. I can see an argument for this being SHOULD,= however -- this isn't a case of becoming incompatible with other impleme= ntations, but a footgun. If you don't do this, you'll break yourself if = you don't retain the ability to parse your old tokens. > = -Continuing the cryptographic handshake is necessary to ensure that an at= tacker -cannot force a downgrade of any cryptographic parameters. In addition t= o -continuing the cryptographic handshake, the client MUST remember the res= ults of -any version negotiation that occurred (see {{version-negotiation}}). Th= e client -MAY also retain any observed RTT or congestion state that it has accumul= ated for -the flow, but other transport state MUST be discarded. +If the Original Destination Connection ID field does not match the +Destination Connection ID from the Initial packet it sent, clients MUST +discard the packet. This prevents an off-path attacker from injecting +a Retry packet with a bogus new Source Connection ID. "...from injecting a fabricated Retry packet." > = -If the server expects to generate more than three Handshake packets in r= esponse -to an Initial packet, it SHOULD include a PATH_CHALLENGE frame in each H= andshake -packet that it sends. After receiving at least one valid PATH_RESPONSE = frame, -the server can send its remaining Handshake packets. Servers can instead= perform -address validation using a Retry packet; this requires less state on the= server, -but could involve additional computational effort depending on implement= ation -choices. +Servers MUST NOT send more than three packets including Initial and Hand= shake See #1458. This should perhaps be three datagrams. > @@ -694,7 +777,7 @@ Packets protected with 0-RTT keys use a type value = of 0x7C. The connection ID fields for a 0-RTT packet MUST match the values used in the Initial pack= et ({{packet-initial}}). = -The client can send 0-RTT packets after receiving a Handshake packet +The client can send 0-RTT packets after receiving an Initial or Handshak= e packet Handshake gets a back-reference; why doesn't Initial? > -least one after sending a packet. +maintains a separate packet number for sending and receiving. + +Packet numbers are divided into 3 spaces in QUIC: + +- Initial space: All Initial packets {{packet-initial}} are in this spac= e. +- Handshake space: All Handshake packets {{packet-handshake}} are in thi= s space. +- Application data space: All 0-RTT and 1-RTT encrypted packets + {{packet-protected}} are in this space. + +As descibed in {{QUIC-TLS}}, each packet type uses different encryption = keys. + +Conceptually, a packet number space is the encryption context in which a= packet +can be processed and ACKed. Initial packets can only be sent with +Initial encryption keys and ACKed in packets which are also Initial pack= ets. +Similarly Handshake packets can only be sent and acked in Handshake pack= ets. "Similarly," and "ACKed" / "acked" =3D> "acknowledged" > = The first client packet of the cryptographic handshake protocol MUST fit= within a 1232 octet QUIC packet payload. This includes overheads that reduce t= he space available to the cryptographic handshake protocol. = -Details of how TLS is integrated with QUIC is provided in more detail in= -{{QUIC-TLS}}. +The CRYPTO_HS frame can be sent in different packet number spaces. +CRYPTO_HS frames in each packet number space carry a separate sequence +of handshake data starting from an offset of 0. + +## Example Handshake Flows + +Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},= +but we provide some examples here. Document typically avoids the first person. "...but some examples are pr= ovided here." > connection state MUST use the Retry packet ({{packet-retry}}). This p= acket -causes a client to reset its transport state and to continue the connect= ion -attempt with new connection state while maintaining the state of the -cryptographic handshake. - -A server MUST NOT send multiple Retry packets in response to a client ha= ndshake -packet. Thus, any cryptographic handshake message that is sent MUST fit= within -a single packet. - -In TLS, the Retry packet type is used to carry the HelloRetryRequest mes= sage. +causes a client to restart the connection attempt and includes the token= in the "include~s~" > @@ -1459,68 +1623,69 @@ To send additional data prior to completing the= cryptographic handshake, the server then needs to validate that the client owns the address that it c= laims. = Source address validation is therefore performed during the establishmen= t of a -connection. TLS provides the tools that support the feature, but basic -validation is performed by the core transport protocol. +connection, by the core transport protocol. "performed by the core transport protocol during the establishment of a c= onnection." > = A server MAY provide clients with an address validation token during one= connection that can be used on a subsequent connection. Address validat= ion is especially important with 0-RTT because a server potentially sends a sig= nificant amount of data to a client in response to 0-RTT data. = -A different type of token is needed when resuming. Unlike the token tha= t is -created during a handshake, there might be some time between when the to= ken is -created and when the token is subsequently used. Thus, a resumption tok= en -SHOULD include an expiration time. It is also unlikely that the client = port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c= lient +with an address validation token that can be used to validate future 0-R= TT +connections. The client may then use this token to validate future 0-RT= T +connections by including it in the Initial packet's header. The client = MUST +NOT use the token provided in a RETRY for future connections. Title case, not all-caps. > = A server MAY provide clients with an address validation token during one= connection that can be used on a subsequent connection. Address validat= ion is especially important with 0-RTT because a server potentially sends a sig= nificant amount of data to a client in response to 0-RTT data. = -A different type of token is needed when resuming. Unlike the token tha= t is -created during a handshake, there might be some time between when the to= ken is -created and when the token is subsequently used. Thus, a resumption tok= en -SHOULD include an expiration time. It is also unlikely that the client = port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c= lient +with an address validation token that can be used to validate future 0-R= TT +connections. The client may then use this token to validate future 0-RT= T +connections by including it in the Initial packet's header. The client = MUST +NOT use the token provided in a RETRY for future connections. + +Unlike the token that is created for a Retry packet, there might be some= time +between when the token is created and when the token is subsequently use= d. +Thus, a resumption token SHOULD include an expiration time. The server = may MAY? Might? Could? > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endp= oint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. = = +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a = token to "A~n~" > +that each encryption level is treated as a separate CRYPTO_HS stream +of data. + +Unlike STREAM frames, which include a Stream ID indicating to which +stream the data belongs, the CRYPTO_HS frame carries data for a single +stream per encryption level. The stream does not have an explicit +end, so CRYPTO_HS frames do not have a FIN bit. + + +## CRYPTO_CLOSE Frame {#frame-crypto-close} + +The CRYPTO_CLOSE frame (type=3D0x20) is used to indicate connection fail= ures +caused by the crypto handshake. It uses the same format as the +CONNECTION_CLOSE frame ({{frame-connection-close}}), except that the +error codes are specific to the crypto protocol in use. For TLS 1.3, +the error code is simply the one-byte TLS alert number. The error code in the other two frames is two bytes long. Is this frame = shorter (in which case the format is not the same), or is the MSB of the = error code always zero? > @@ -3064,6 +3293,10 @@ been lost. In general, information is sent agai= n when a packet containing that information is determined to be lost and sending ceases when a packet containing that information is acknowledged. = +* Data sent in CRYPTO_HS frames are retransmitted according to the rules= in + {{QUIC-RECOVERY}}, until either all data has been ACKed or the crypto = state "acknowledged" > @@ -3299,8 +3532,7 @@ The two type bits from a Stream ID therefore iden= tify streams as summarized in | 0x3 | Server-Initiated, Unidirectional | {: #stream-id-types title=3D"Stream ID Types"} = -Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is us= ed for -the cryptographic handshake. Stream 0 MUST NOT be used for application = data. +The first bi-directional stream opened by the client is stream 0. For people who don't have the Stream 0 legacy (intended audience of this = doc), is this statement even relevant? > @@ -3893,6 +4102,14 @@ errors is not mandatory, but only because requir= ing that an endpoint generate these errors also means that the endpoint needs to maintain the final of= fset state for closed streams, which could mean a significant state commitmen= t. = +## Flow control of CRYPTO_HS data {#flow-control-crypto} + +Data sent in CRYPTO_HS frames is not flow controlled in the same way as = STREAM +frames. QUIC relies on the cryptographic protocol implementation to avo= id +excessive buffering of data, see {{QUIC-TLS}}. The implementation SHOUL= D +provide an interface to QUIC to tell it about its buffering limits so th= at there +is no excessive buffering at multiple layers. no =3D> not > @@ -4313,6 +4531,15 @@ the range from 0xFE00 to 0xFFFF. = Issue and pull request numbers are listed with a leading octothorp. = +## Since draft-ietf-quic-transport-12 + +- Enable server to transition connections to a preferred address (#560,#= 1251). +- No more stream 0. Stream 0 still exists. Maybe "Stream 0 is no longer reserved for the cry= ptographic handshake. Instead, CRYPTO_HS frames are used." > -new packet with a new packet number, removing ambiguity about which pa= cket is -acknowledged when an ACK is received. Consequently, more accurate RTT -measurements can be made, spurious retransmissions are trivially detecte= d, and -mechanisms such as Fast Retransmit can be applied universally, based onl= y on -packet number. +QUIC's packet number is strictly increasing within a packet number +space, and directly encodes transmission order. A higher QUIC packet +number signifies that the packet was sent later, and a lower QUIC +packet number signifies that the packet was sent earlier. When a +packet containing frames is deemed lost, QUIC rebundles the +retransmittable data in a new packet with a new packet number, +removing ambiguity about which packet is acknowledged when an ACK is +received. Consequently, more accurate RTT measurements can be made, +spurious retransmissions are trivially detected, and mechanisms such +as Fast Retransmit can be applied universally, based only on packet +number. The only change here seems to be that it was rewrapped to a smaller width= than the rest of the document. Is this necessary? > = -(TODO: Work this section some more. Add text on client vs. server, and o= n -stateless retry.) +A RETRY packet causes the content of the client's Initial packet to be Packet types are title-cased, not all-caps. Same on line 318. > = -QUIC SHOULD delay sending acknowledgements in response to packets, -but MUST NOT excessively delay acknowledgements of packets containing -non-ack frames. Specifically, implementaions MUST attempt to -enforce a maximum ack delay to avoid causing the peer spurious -timeouts. The default maximum ack delay in QUIC is 25ms. +There are cases where one may be able to gain recovery information from +acknowledgements of packets in another packet number space, but they rel= y +on complex assumptions about the peer=E2=80=99s processing and acknowled= gement +algorithms. Even those are unable to quickly recover from cases such as= +losing the client's Initial, but receiving the 0-RTT packets. Below is +an optimization using coalesced packets and implicit acknowledgements. I don't see the optimization using coalesced packets and implicit acknowl= edgements. If it's not immediately below this statement, perhaps add a f= orward reference? -- = 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/1450#pullrequestreview-1296819= 35= ----==_mimepart_5b2837c92f384_36672ab146dcef5c816de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@MikeBishop commented on this pull request.

Lots of editorial comments, but the content looks good.

In draft-ietf-quic-tls.md:

>  =

+Unlike TLS over TCP, QUIC applications which want to send data do not
+send it through TLS "application_data" records. Rather, they s=
end it
+as QUIC STREAM frames which are then carried in QUIC packets.
+
+
+# Carrying TLS Messages {#carrying-tls}
+
+QUIC carries TLS handshake data in CRYPTO_HS frames, each of which

Bikeshed: I hate this name. Why not simply CRYPTO frames or HANDSHAK= E frames? Compounding the two seems unnecessary.

In draft-ietf-quic-tls.md:

> +and encrypted under the current TLS encry=
ption level.
+As with TLS over TCP, once TLS handshake data has
+been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:

This statement is confusing, as it precedes a bulleted list of things = which don't exist in TLS over TCP. Perhaps this should be reframed in te= rms of the types of data TLS/TCP permits, and the QUIC equivalents that c= arry it?

In draft-ietf-quic-tls.md:

> +same encryption level. For instance, an i=
mplementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.=

+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.

There are so many exceptions, it almost seems more efficient to indica= te what frames cannot appear in different levels. STREAM and fl= ow control frames aren't permitted in Initial or Handshake; *_CLOSE aren'= t permitted in 0-RTT, except maybe APPLICATION_CLOSE.

In draft-ietf-quic-tls.md:

>  =

 ## Interface to TLS
 =

-As shown in {{schematic}}, the interface from QUIC to TLS consists of fo=
ur
-primary functions: Handshake, Source Address Validation, Key Ready Event=
s, and
-Secret Export.
+As shown in {{schematic}}, the interface from QUIC to TLS consists of th=
ree
+primary functions:
+
+- Sending and receiving handshake messages
+- Rekeying (both in and out)

Perhaps "send and receive" here? Otherwise, it could sound like the k= ey is both coming from and being supplied to TLS.

In draft-ietf-quic-tls.md:

>  =

 In order to drive the handshake, TLS depends on being able to send and r=
eceive
-handshake messages on stream 0.  There are two basic functions on this
+handshake messages. There are two basic functions on this

Rewrap.

In draft-ietf-quic-tls.md:

> +
+At any given time, an endpoint will have a current sending encryption
+level and receiving encryption level. Each encryption level is
+associated with a different flow of bytes, which is reliably
+transmitted to the peer in CRYPTO_HS frames. When TLS provides handshake=

+octets to be sent, they are appended to the current flow and
+will eventually be transmitted under the then-current key.
+
+When an endpoint receives a QUIC packet containing a CRYPTO_HS frame fro=
m
+the network, it proceeds as follows:
+
+- If the packet was in the current receiving encryption level, sequence
+  the data into the input flow as usual. As with STREAM frames,
+  the offset is used to find the proper location in the data sequence.
+  If the result of this process is that new data is available, then
+  it is delivered to TLS.

Might be worth mentioning that bytes are always provided in-order to T= LS, since QUIC is otherwise permitted to support out-of-order delivery on= streams.

In draft-ietf-quic-tls.md:

> -request of QUIC, including the value extr=
acted from the cookie extension.  In
-response to this request, QUIC cannot ask for client address validation,=
 it can
-only abort or permit the connection attempt to proceed.
-
-QUIC can provide a new address validation token for use in session resum=
ption at
-any time after the handshake is complete.  Each time a new token is prov=
ided TLS
-generates a NewSessionTicket message, with the token included in the tic=
ket.
-
-See {{client-address-validation}} for more details on client address val=
idation.
-
-
-### Key Ready Events
-
-TLS provides QUIC with signals when 0-RTT and 1-RTT keys are ready for u=
se.
+At each change of encryption level in either direction, TLS signals
+QUIC, providing the new level and the encryption keys.
 These events are not asynchronous, they always occur immediately after T=
LS is

Comma splice; either use a semicolon or divide into separate sentences= . (Though, yes, this line wasn't changed.)

In draft-ietf-quic-tls.md:

>  If 0-RTT is possible, it is ready after t=
he client sends a TLS ClientHello
 message or the server receives that message.  After providing a QUIC cli=
ent with
-the first handshake octets, the TLS stack might signal that 0-RTT keys a=
re
-ready.  On the server, after receiving handshake octets that contain a
+the first handshake octets, the TLS stack might signal the change to the=

+the 0-RTT keys. On the server, after receiving handshake octets that con=
tain a

...and I think it reads better without "the" at all.

In draft-ietf-quic-tls.md:

>  ClientHello message, a TLS server might s=
ignal that 0-RTT keys are available.
 =

-1-RTT keys are used for packets in both directions.  0-RTT keys are only=

-used to protect packets sent by the client.
-
-
-### Secret Export
+Note that although TLS only uses one encryption level at a time, QUIC
+may use more than one level. For instance, after sending its Finished

May? Will have to, I believe.

In draft-ietf-quic-tls.md:

>  =

-## QUIC Key Expansion {#key-expansion}
+A server rejects 0-RTT by rejecting 0-RTT at the TLS layer.  This result=
s in
+early exporter keys being unavailable, thereby preventing the use of 0-R=
TT for
+QUIC.

Under this model, exporters (early or otherwise) have nothing to do wi= th the use of a particular encryption level for QUIC, IIUC.

In draft-ietf-quic-tls.md:

>  =

-QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=3DRFC586=
9}} with
-the same hash function negotiated by TLS for key derivation.  For exampl=
e, if
-TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is us=
ed.
+In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section
+4.1.4) can be used to correct a client's incorrect KeyShare extensio=
n
+as well as for a stateless round trip check. From the perspective of

round-trip

In draft-ietf-quic-tls.md:

>  =

-QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=3DRFC586=
9}} with
-the same hash function negotiated by TLS for key derivation.  For exampl=
e, if
-TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is us=
ed.
+In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section
+4.1.4) can be used to correct a client's incorrect KeyShare extensio=
n
+as well as for a stateless round trip check. From the perspective of
+QUIC, this just looks like additional messages carried in the Initial
+encryption level. Although it is in principle possible to use this
+feature for address verification in QUIC, QUIC implementations SHOULD
+instead use the Retry feature ({{QUIC-TRANSPORT}}; Section 4.4.2)).

Might be worth explicitly noting that this is still used for = incorrect key shares.

In draft-ietf-quic-tls.md:

>  =

-~~~
-struct {
-   uint16 length =3D Length;
-   opaque label<6..255> =3D "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the T=
LS
+handshake, using the AEAD algorithm negotiated by TLS.

Since TCP doesn't actually do the encryption, perhaps this would be mo= re clearly stated as "As with the TLS record layer used with TCP, QUIC...= ."

In draft-ietf-quic-tls.md:

>  =

-For example, assuming a hash function with a 32 octet output, derivation=
 for a
-client packet protection key would use HKDF-Expand with an `info` parame=
ter of
-0x00200851554943206b6579.
+The keys for the Initial encryption level are computed based on
+the client's first Destination Connection Id, as described in

ID

In draft-ietf-quic-tls.md:

>  =

-Packets that carry the TLS handshake (Initial, Retry, and Handshake) are=

-protected with a secret derived from the Destination Connection ID field=
 from
-the client's Initial packet.  Specifically:
+Initial packets are protected with
+a secret derived from the Destination Connection ID field from the clien=
t's
+Initial packet.  Specifically:

First Initial packet, or does the key change with the DCID of each new= Initial the client sends?

In draft-ietf-quic-tls.md:

>  ~~~
 =

 The hash function for HKDF when deriving handshake secrets and keys is S=
HA-256
-{{!SHA=3DDOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with QHK=
DF-Expand
-is the connection ID chosen by the client.
+{{!SHA=3DDOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with
+HKDF-Expand-Label is the connection ID chosen by the client.

initial Destination Connection ID

In draft-ietf-quic-tls.md:

> @@ -743,121 +653,11 @@ Note:
 =

 : The Destination Connection ID is of arbitrary length, and it could be =
zero
   length if the server sends a Retry packet with a zero-length Source Co=
nnection
-  ID field.  In this case, the handshake keys provide no assurance to th=
e client
+  ID field.  In this case, the initial keys provide no assurance to the =
client

Initial

In draft-ietf-quic-tls.md:

> @@ -873,26 +673,20 @@ from the packet numb=
er.
 All QUIC packets other than Version Negotiation and Stateless Reset pack=
ets are
 protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shar=
ed
 secret, packets are protected with AEAD_AES_128_GCM and a key derived fr=
om the
-client's connection ID (see {{handshake-secrets}}).  This provides p=
rotection
+client's connection ID (see {{initial-secrets}}).  This provides pro=
tection

initial Destination Connection ID

In draft-ietf-quic-tls.md:

>  =

-### Retransmission and Acknowledgment of Unprotected Packets
+: 0-RTT data can be acknowledged by the server as it receives it, but an=
y

Is this being formatted the way you want it? It's being rendered as a= definition of the previous line (MUST NOT use 0-RTT keys), which looks a= little weird for prose. It seems like it should just be a straight para= graph of text....

In draft-ietf-quic-tls.md:

>  =

-A HelloRetryRequest handshake message might be used to reject an initial=

-ClientHello.  A HelloRetryRequest handshake message is sent in a Retry p=
acket;
-any second ClientHello that is sent in response uses a Initial packet ty=
pe.
-These packets are only protected with a predictable key (see
-{{handshake-secrets}}).  This is natural, because no shared secret will =
be
-available when these messages need to be sent.  Upon receipt of a
-HelloRetryRequest, a client SHOULD cease any transmission of 0-RTT data;=
 0-RTT
-data will only be discarded by any server that sends a HelloRetryRequest=
.
+Due to reordering and loss, protected packets might be received by an en=
dpoint
+before the final TLS handshake messages are received.  A client will be =
unable
+to decrypt 1-RTT packets from the server, whereas a server will be able =
to
+decrypt 1-RTT packets from the client. However,
+a server MUST NOT process data from incoming 1-RTT protected packets

MUST NOT (BUT WE KNOW YOU WILL). 6919 OUGHT TO have mentioned that on= e.

In draft-ietf-quic-tls.md:

>  =

-Once 1-RTT keys are available to an endpoint, it no longer needs the TLS=

-handshake messages that are carried in unprotected packets.  However, a =
server
-might need to retransmit its TLS handshake messages in response to recei=
ving an
-unprotected packet that contains ACK frames.  A server MUST process ACK =
frames
-in unprotected packets until the TLS handshake is reported as complete, =
or it
-receives an ACK frame in a protected packet that acknowledges all of its=

-handshake messages.
+Receiving and verifying the TLS Finished message is critical in
+ensuring the integrity of the TLS handshake.  A server MUST NOT use
+1-RTT protected packets from the client prior to verifying the client
+Finished message if its response depends on client authentication.

But it provides an additional conditional that the previous one doesn'= t which is interest. MUST NOT ... if its response depends on cl= ient authentication. So we're willing to tolerate a tampered ClientHello= for transferring public data, and just assume decryption will fail on th= e other side?

In draft-ietf-quic-tls.md:

> -server has chosen to use a pre-shared key=
 - the pre-shared key binder (see
-Section 4.2.8 of {{!TLS13}}).  Verifying these values provides the serve=
r with
-an assurance that the ClientHello has not been modified.
-
-A server could receive packets protected with 0-RTT keys prior to receiv=
ing a
-TLS ClientHello.  The server MAY retain these packets for later decrypti=
on in
-anticipation of receiving a ClientHello.
-
-Receiving and verifying the TLS Finished message is critical in ensuring=
 the
-integrity of the TLS handshake.  A server MUST NOT use protected packets=
 from
-the client prior to verifying the client Finished message if its respons=
e
-depends on client authentication.
+It is also possible for the attacker to tamper with data that
+is carried in Handshake packets, but because that tampering
+requires modifying TLS handshake messages, that tampering will be
+detected as soon as the TLS handshake completes.

"...will cause the TLS handshake to fail."?

In draft-ietf-quic-tls.md:

> @@ -1592,6 +996,11 @@ version of QUIC defi=
ned in {{QUIC-TRANSPORT}} is used.
 The quic_transport_parameters extension is carried in the ClientHello an=
d the
 EncryptedExtensions messages during the handshake.
 =

+While the transport parameters are technically available prior to the
+completion of the handshake, they cannot be fully trusted until the hand=
shake
+completes, and reliance on them should be minimized.
+However, any tampering with the parameters will be detected
+when the handshake completes.

Same as previous. Also, rewrap.

In draft-ietf-quic-transport.md:

>  =

 All these packets use the long header and contain the current QUIC versi=
on in
 the version field.
 =

-In order to prevent tampering by version-unaware middleboxes, handshake =
packets
-are protected with a connection- and version-specific key, as described =
in
-{{QUIC-TLS}}. This protection does not provide confidentiality or integr=
ity
-against on-path attackers, but provides some level of protection against=

-off-path attackers.
+In order to prevent tampering by version-unaware middleboxes, Initial
+packets are protected with a connection- and version-specific keys

"with a... keys"

In draft-ietf-quic-transport.md:

>  =

 =

 ### Initial Packet {#packet-initial}
 =

 The Initial packet uses long headers with a type value of 0x7F.  It carr=
ies the
-first cryptographic handshake message sent by the client.
+first CRYPTO_HS frames sent by the client as well as the
+cryptographic messages sent by the server to perform key exchange. The I=
nitial
+packet is protected by Initial keys as described in {{QUIC-TLS}}.

Rewrap.

In draft-ietf-quic-transport.md:

> +Token Length:
+
+: A variable-length integer specifying the length of the Token field, in=
 bytes.
+It may be zero if no token is present. The server MUST send a zero-lengt=
h
+token.
+
+Token:
+
+: An optional token blob previously received in either a Retry packet or=

+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that co=
ntains
+an initial cryptographic handshake message. This includes all cases wher=
e a new
+packet containing the initial cryptographic message needs to be created,=
 this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).

"This includes..., this includes...." is an awkward construction. Per= haps "In addition to the first packet(s), this also includes all cases wh= ere a new packet containing the initial cryptographic message needs to be= created, such as...."?

In draft-ietf-quic-transport.md:

> +Token:
+
+: An optional token blob previously received in either a Retry packet or=

+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that co=
ntains
+an initial cryptographic handshake message. This includes all cases wher=
e a new
+packet containing the initial cryptographic message needs to be created,=
 this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.=
  A
+server may send multiple Initial packets.  The cryptographic key exchang=
e could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)

conveys =3D> includes

In draft-ietf-quic-transport.md:

> +Token:
+
+: An optional token blob previously received in either a Retry packet or=

+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that co=
ntains
+an initial cryptographic handshake message. This includes all cases wher=
e a new
+packet containing the initial cryptographic message needs to be created,=
 this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.=
  A
+server may send multiple Initial packets.  The cryptographic key exchang=
e could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)

Not necessarily; it could just include ACKs of handshake messages.

=

In draft-ietf-quic-transport.md:

> +: An optional token blob previously recei=
ved in either a Retry packet or
+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that co=
ntains
+an initial cryptographic handshake message. This includes all cases wher=
e a new
+packet containing the initial cryptographic message needs to be created,=
 this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.=
  A
+server may send multiple Initial packets.  The cryptographic key exchang=
e could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete

sent

In draft-ietf-quic-transport.md:

> +The client and server use the Initial pac=
ket type for any packet that contains
+an initial cryptographic handshake message. This includes all cases wher=
e a new
+packet containing the initial cryptographic message needs to be created,=
 this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.=
  A
+server may send multiple Initial packets.  The cryptographic key exchang=
e could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete
+first message MUST fit in a single packet (see {{handshake}}). Note that=
 if
+the server sends a HelloRetryRequest, the client will send a second Init=
ial
+packet with a CRYPTO_HS frame starting immediately after the first one.

"starting immediately after" could be misconstrued as packet layout. = Perhaps "continuing the sequence of handshake messages"?

In draft-ietf-quic-transport.md:

> +
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete
+first message MUST fit in a single packet (see {{handshake}}). Note that=
 if
+the server sends a HelloRetryRequest, the client will send a second Init=
ial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously r=
eceived
+a Retry packet from the server, it populates the Destination Connection =
ID field
+with a randomly selected value.  This MUST be at least 8 octets in lengt=
h. Until
+a packet is received from the server, the client MUST use the same rando=
m value
+unless it also changes the Source Connection ID (which effectively start=
s a new

Is there a way in which this is just "effectively"? Maybe "...unless = it abandons the connection attempt and begins a new one. In this case, t= he client MUST change the Source Connection ID."

In draft-ietf-quic-transport.md:

> +containing a cryptographic handshake mess=
age. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete
+first message MUST fit in a single packet (see {{handshake}}). Note that=
 if
+the server sends a HelloRetryRequest, the client will send a second Init=
ial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously r=
eceived
+a Retry packet from the server, it populates the Destination Connection =
ID field
+with a randomly selected value.  This MUST be at least 8 octets in lengt=
h. Until
+a packet is received from the server, the client MUST use the same rando=
m value
+unless it also changes the Source Connection ID (which effectively start=
s a new
+connection attempt).  The randomized Destination Connection ID is used t=
o
+determine packet protection keys.

Initial

In draft-ietf-quic-transport.md:

>  =

 The client populates the Source Connection ID field with a value of its =
choosing
 and sets the SCIL field to match.
 =

-The first Initial packet that is sent by a client contains a packet numb=
er of 0.
-All subsequent packets contain a packet number that is incremented by at=
 least
-one, see ({{packet-numbers}}).
-
-The payload of an Initial packet conveys a STREAM frame (or frames) for =
stream
-0 containing a cryptographic handshake message.  The stream in this pack=
et
-always starts at an offset of 0 (see {{stateless-retry}}) and the comple=
te
-cryptographic handshake message MUST fit in a single packet (see {{hands=
hake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet

Perhaps "the" connection ID?

In draft-ietf-quic-transport.md:

>  =

 The client populates the Source Connection ID field with a value of its =
choosing
 and sets the SCIL field to match.
 =

-The first Initial packet that is sent by a client contains a packet numb=
er of 0.
-All subsequent packets contain a packet number that is incremented by at=
 least
-one, see ({{packet-numbers}}).
-
-The payload of an Initial packet conveys a STREAM frame (or frames) for =
stream
-0 containing a cryptographic handshake message.  The stream in this pack=
et
-always starts at an offset of 0 (see {{stateless-retry}}) and the comple=
te
-cryptographic handshake message MUST fit in a single packet (see {{hands=
hake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection

This implies the server can have multiple consistent SCIDs during the = handshake. "...MUST use a consistent SCID during the handshake."

In draft-ietf-quic-transport.md:

> -
-The payload of an Initial packet conveys a STREAM frame (or frames) for =
stream
-0 containing a cryptographic handshake message.  The stream in this pack=
et
-always starts at an offset of 0 (see {{stateless-retry}}) and the comple=
te
-cryptographic handshake message MUST fit in a single packet (see {{hands=
hake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection
+IDs during the handshake.
+
+On first receiving an Initial or Retry packet from the server, the
+client uses the Source Connection ID supplied by the server as the
+Destination Connection ID for subsequent packets. The client MUST
+discard any subsequent packets it receives with different

"with a different SCID" probably, since the packet contains only one S= CID.

In draft-ietf-quic-transport.md:

> +
+#### Tokens
+
+If the client has a suitable token available from a previous connection,=

+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID t=
o
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated

Additionally, the token could have been issued by a previous iteration= of the server with a different key / token generation scheme, as describ= ed in the following paragraph. I can see an argument for this being SHOU= LD, however -- this isn't a case of becoming incompatible with other impl= ementations, but a footgun. If you don't do this, you'll break yourself = if you don't retain the ability to parse your old tokens.

In draft-ietf-quic-transport.md:

>  =

-Continuing the cryptographic handshake is necessary to ensure that an at=
tacker
-cannot force a downgrade of any cryptographic parameters.  In addition t=
o
-continuing the cryptographic handshake, the client MUST remember the res=
ults of
-any version negotiation that occurred (see {{version-negotiation}}).  Th=
e client
-MAY also retain any observed RTT or congestion state that it has accumul=
ated for
-the flow, but other transport state MUST be discarded.
+If the Original Destination Connection ID field does not match the
+Destination Connection ID from the Initial packet it sent, clients MUST
+discard the packet. This prevents an off-path attacker from injecting
+a Retry packet with a bogus new Source Connection ID.

"...from injecting a fabricated Retry packet."

In draft-ietf-quic-transport.md:

>  =

-If the server expects to generate more than three Handshake packets in r=
esponse
-to an Initial packet, it SHOULD include a PATH_CHALLENGE frame in each H=
andshake
-packet that it sends.  After receiving at least one valid PATH_RESPONSE =
frame,
-the server can send its remaining Handshake packets. Servers can instead=
 perform
-address validation using a Retry packet; this requires less state on the=
 server,
-but could involve additional computational effort depending on implement=
ation
-choices.
+Servers MUST NOT send more than three packets including Initial and Hand=
shake

See #1458. This should perhaps be three datagrams.

In draft-ietf-quic-transport.md:

> @@ -694,7 +777,7 @@ Packets protected with=
 0-RTT keys use a type value of 0x7C.  The connection ID
 fields for a 0-RTT packet MUST match the values used in the Initial pack=
et
 ({{packet-initial}}).
 =

-The client can send 0-RTT packets after receiving a Handshake packet
+The client can send 0-RTT packets after receiving an Initial or Handshak=
e packet

Handshake gets a back-reference; why doesn't Initial?

In draft-ietf-quic-transport.md:

> -least one after sending a packet.
+maintains a separate packet number for sending and receiving.
+
+Packet numbers are divided into 3 spaces in QUIC:
+
+- Initial space: All Initial packets {{packet-initial}} are in this spac=
e.
+- Handshake space: All Handshake packets {{packet-handshake}} are in thi=
s space.
+- Application data space: All 0-RTT and 1-RTT encrypted packets
+  {{packet-protected}} are in this space.
+
+As descibed in {{QUIC-TLS}}, each packet type uses different encryption =
keys.
+
+Conceptually, a packet number space is the encryption context in which a=
 packet
+can be processed and ACKed.  Initial packets can only be sent with
+Initial encryption keys and ACKed in packets which are also Initial pack=
ets.
+Similarly Handshake packets can only be sent and acked in Handshake pack=
ets.

"Similarly," and "ACKed" / "acked" =3D> "acknowledged"

In draft-ietf-quic-transport.md:

>  =

 The first client packet of the cryptographic handshake protocol MUST fit=
 within
 a 1232 octet QUIC packet payload.  This includes overheads that reduce t=
he space
 available to the cryptographic handshake protocol.
 =

-Details of how TLS is integrated with QUIC is provided in more detail in=

-{{QUIC-TLS}}.
+The CRYPTO_HS frame can be sent in different packet number spaces.
+CRYPTO_HS frames in each packet number space carry a separate sequence
+of handshake data starting from an offset of 0.
+
+## Example Handshake Flows
+
+Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},=

+but we provide some examples here.

Document typically avoids the first person. "...but some examples are= provided here."

In draft-ietf-quic-transport.md:

>  connection state MUST use the Retry packe=
t ({{packet-retry}}).  This packet
-causes a client to reset its transport state and to continue the connect=
ion
-attempt with new connection state while maintaining the state of the
-cryptographic handshake.
-
-A server MUST NOT send multiple Retry packets in response to a client ha=
ndshake
-packet.  Thus, any cryptographic handshake message that is sent MUST fit=
 within
-a single packet.
-
-In TLS, the Retry packet type is used to carry the HelloRetryRequest mes=
sage.
+causes a client to restart the connection attempt and includes the token=
 in the

"includes"

In draft-ietf-quic-transport.md:

> @@ -1459,68 +1623,69 @@ To send additional=
 data prior to completing the cryptographic handshake, the
 server then needs to validate that the client owns the address that it c=
laims.
 =

 Source address validation is therefore performed during the establishmen=
t of a
-connection.  TLS provides the tools that support the feature, but basic
-validation is performed by the core transport protocol.
+connection, by the core transport protocol.

"performed by the core transport protocol during the establishment of = a connection."

In draft-ietf-quic-transport.md:

>  =

 A server MAY provide clients with an address validation token during one=

 connection that can be used on a subsequent connection.  Address validat=
ion is
 especially important with 0-RTT because a server potentially sends a sig=
nificant
 amount of data to a client in response to 0-RTT data.
 =

-A different type of token is needed when resuming.  Unlike the token tha=
t is
-created during a handshake, there might be some time between when the to=
ken is
-created and when the token is subsequently used.  Thus, a resumption tok=
en
-SHOULD include an expiration time.  It is also unlikely that the client =
port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c=
lient
+with an address validation token that can be used to validate future 0-R=
TT
+connections.  The client may then use this token to validate future 0-RT=
T
+connections by including it in the Initial packet's header.  The cli=
ent MUST
+NOT use the token provided in a RETRY for future connections.

Title case, not all-caps.

In draft-ietf-quic-transport.md:

>  =

 A server MAY provide clients with an address validation token during one=

 connection that can be used on a subsequent connection.  Address validat=
ion is
 especially important with 0-RTT because a server potentially sends a sig=
nificant
 amount of data to a client in response to 0-RTT data.
 =

-A different type of token is needed when resuming.  Unlike the token tha=
t is
-created during a handshake, there might be some time between when the to=
ken is
-created and when the token is subsequently used.  Thus, a resumption tok=
en
-SHOULD include an expiration time.  It is also unlikely that the client =
port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c=
lient
+with an address validation token that can be used to validate future 0-R=
TT
+connections.  The client may then use this token to validate future 0-RT=
T
+connections by including it in the Initial packet's header.  The cli=
ent MUST
+NOT use the token provided in a RETRY for future connections.
+
+Unlike the token that is created for a Retry packet, there might be some=
 time
+between when the token is created and when the token is subsequently use=
d.
+Thus, a resumption token SHOULD include an expiration time.  The server =
may

MAY? Might? Could?

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE fram=
e previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 =

 =

+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a =
token to

"An"

In draft-ietf-quic-transport.md:

> +that each encryption level is treated as =
a separate CRYPTO_HS stream
+of data.
+
+Unlike STREAM frames, which include a Stream ID indicating to which
+stream the data belongs, the CRYPTO_HS frame carries data for a single
+stream per encryption level. The stream does not have an explicit
+end, so CRYPTO_HS frames do not have a FIN bit.
+
+
+## CRYPTO_CLOSE Frame {#frame-crypto-close}
+
+The CRYPTO_CLOSE frame (type=3D0x20) is used to indicate connection fail=
ures
+caused by the crypto handshake. It uses the same format as the
+CONNECTION_CLOSE frame ({{frame-connection-close}}), except that the
+error codes are specific to the crypto protocol in use. For TLS 1.3,
+the error code is simply the one-byte TLS alert number.

The error code in the other two frames is two bytes long. Is this fra= me shorter (in which case the format is not the same), or is the MSB of t= he error code always zero?

In draft-ietf-quic-transport.md:

> @@ -3064,6 +3293,10 @@ been lost.  In gene=
ral, information is sent again when a packet containing that
 information is determined to be lost and sending ceases when a packet
 containing that information is acknowledged.
 =

+* Data sent in CRYPTO_HS frames are retransmitted according to the rules=
 in
+  {{QUIC-RECOVERY}}, until either all data has been ACKed or the crypto =
state

"acknowledged"

In draft-ietf-quic-transport.md:

> @@ -3299,8 +3532,7 @@ The two type bits fr=
om a Stream ID therefore identify streams as summarized in
 | 0x3      | Server-Initiated, Unidirectional |
 {: #stream-id-types title=3D"Stream ID Types"}
 =

-Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is us=
ed for
-the cryptographic handshake.  Stream 0 MUST NOT be used for application =
data.
+The first bi-directional stream opened by the client is stream 0.

For people who don't have the Stream 0 legacy (intended audience of th= is doc), is this statement even relevant?

In draft-ietf-quic-transport.md:

> @@ -3893,6 +4102,14 @@ errors is not manda=
tory, but only because requiring that an endpoint generate
 these errors also means that the endpoint needs to maintain the final of=
fset
 state for closed streams, which could mean a significant state commitmen=
t.
 =

+## Flow control of CRYPTO_HS data {#flow-control-crypto}
+
+Data sent in CRYPTO_HS frames is not flow controlled in the same way as =
STREAM
+frames.  QUIC relies on the cryptographic protocol implementation to avo=
id
+excessive buffering of data, see {{QUIC-TLS}}.  The implementation SHOUL=
D
+provide an interface to QUIC to tell it about its buffering limits so th=
at there
+is no excessive buffering at multiple layers.

no =3D> not

In draft-ietf-quic-transport.md:

> @@ -4313,6 +4531,15 @@ the range from 0xFE=
00 to 0xFFFF.
 =

 Issue and pull request numbers are listed with a leading octothorp.
 =

+## Since draft-ietf-quic-transport-12
+
+- Enable server to transition connections to a preferred address (#560,#=
1251).
+- No more stream 0.

Stream 0 still exists. Maybe "Stream 0 is no longer reserved for the = cryptographic handshake. Instead, CRYPTO_HS frames are used."

In draft-ietf-quic-recovery.md:

> -new packet with a new packet number, remo=
ving ambiguity about which packet is
-acknowledged when an ACK is received.  Consequently, more accurate RTT
-measurements can be made, spurious retransmissions are trivially detecte=
d, and
-mechanisms such as Fast Retransmit can be applied universally, based onl=
y on
-packet number.
+QUIC's packet number is strictly increasing within a packet number
+space, and directly encodes transmission order.  A higher QUIC packet
+number signifies that the packet was sent later, and a lower QUIC
+packet number signifies that the packet was sent earlier.  When a
+packet containing frames is deemed lost, QUIC rebundles the
+retransmittable data in a new packet with a new packet number,
+removing ambiguity about which packet is acknowledged when an ACK is
+received.  Consequently, more accurate RTT measurements can be made,
+spurious retransmissions are trivially detected, and mechanisms such
+as Fast Retransmit can be applied universally, based only on packet
+number.

The only change here seems to be that it was rewrapped to a smaller wi= dth than the rest of the document. Is this necessary?

In draft-ietf-quic-recovery.md:

>  =

-(TODO: Work this section some more. Add text on client vs. server, and o=
n
-stateless retry.)
+A RETRY packet causes the content of the client's Initial packet to =
be

Packet types are title-cased, not all-caps. Same on line 318.

In draft-ietf-quic-recovery.md:

>  =

-QUIC SHOULD delay sending acknowledgements in response to packets,
-but MUST NOT excessively delay acknowledgements of packets containing
-non-ack frames.  Specifically, implementaions MUST attempt to
-enforce a maximum ack delay to avoid causing the peer spurious
-timeouts.  The default maximum ack delay in QUIC is 25ms.
+There are cases where one may be able to gain recovery information from
+acknowledgements of packets in another packet number space, but they rel=
y
+on complex assumptions about the peer=E2=80=99s processing and acknowled=
gement
+algorithms.  Even those are unable to quickly recover from cases such as=

+losing the client's Initial, but receiving the 0-RTT packets.  Below=
 is
+an optimization using coalesced packets and implicit acknowledgements.

I don't see the optimization using coalesced packets and implicit ackn= owledgements. If it's not immediately below this statement, perhaps add = a forward reference?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

= = ----==_mimepart_5b2837c92f384_36672ab146dcef5c816de-- From nobody Mon Jun 18 16:56:35 2018 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 21170130E36 for ; Mon, 18 Jun 2018 16:56:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 N4ovel6vOJ5k for ; Mon, 18 Jun 2018 16:56:29 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B54AF130DBE for ; Mon, 18 Jun 2018 16:56:29 -0700 (PDT) Date: Mon, 18 Jun 2018 16:56:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529366189; bh=6vP3Xuawsl7r4QRTr/oXcX3vunXzlRbnXQbdK/G+Ozc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dJVMB0IRIR9VWan2BU/EUqvvszpJMetm9KOyOS4MNv3hDrenRrL3DyVmuRGT2w6oD PbMTZPLQk6iQ7BXM7Mzju/cVMBmgTt7ZUyBeXYW+86yAji8Z7/ws3bWbEGDR1eK/Wn BA0XnFJrCL7jlie7d0LWk9AbFwacOGLbuI0xmRRM= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2846ace6520_5f3f2acb24212f54408ca"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 23:56:34 -0000 ----==_mimepart_5b2846ace6520_5f3f2acb24212f54408ca Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. Thanks for getting this going, @igorlord ! A few comments, mostly editorial. > @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields. All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP fragmentation or packet drops. To optimize bandwidth efficiency, endpoints SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}). Endpoints -MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for -detecting the PMTU, setting the PMTU appropriately, and storing the result of -previous PMTU determinations. +MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) I think the context does make it clear, but @martinduke's suggestion seems reasonable. > @@ -3187,40 +3187,76 @@ QUIC packets on the affected path. This could result in termination of the connection if an alternative path cannot be found. -### IPv4 PMTU Discovery {#v4-pmtud} +### Classical ICMP-based path MTU discovery {#icmp-pmtu} ditto. Also, Capitalize This Section Title. > @@ -3187,40 +3187,76 @@ QUIC packets on the affected path. This could result in termination of the connection if an alternative path cannot be found. -### IPv4 PMTU Discovery {#v4-pmtud} +### Classical ICMP-based path MTU discovery {#icmp-pmtu} + +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}}, the messages -> messages > +### Classical ICMP-based path MTU discovery {#icmp-pmtu} + +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}}, +which requires ICMPv6 error messages to contain "as much of invoking packet as +possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and +{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). This sentence is a bit hard to follow. Also, it's possible that the ICMP message was received after the sender deemed it lost, since the sender may have been too earnest in marking it lost. Perhaps remove the requirement that it not be marked as lost yet? How about the following: "To validate an ICMP message containing on-path proof, the proof MUST be from a QUIC packet that is not yet acknowledged." > + +ICMP error messages used in classical Path MTU discovery may be classified into +messages with an on-path proof and without an on-path proof. ICMP messages with +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}}, +which requires ICMPv6 error messages to contain "as much of invoking packet as +possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and +{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 To perform the on-path validation -> To validate a received ICMP message > +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}}, +which requires ICMPv6 error messages to contain "as much of invoking packet as +possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and +{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum the outstanding => outstanding > +which requires ICMPv6 error messages to contain "as much of invoking packet as +possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and +{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum +validation, it SHOULD treat the packet as an ICMP message without an on-path SHOULD -> MUST > +the original datagram as possible without the length of the ICMP datagram +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum +validation, it SHOULD treat the packet as an ICMP message without an on-path +proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes an on-path proof -> on-path proof > +exceeding 576 bytes". ICMPv4 messages without an on-path proof are sent in +accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum +validation, it SHOULD treat the packet as an ICMP message without an on-path +proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. the protocol implementation -> an endpoint > +octets past the IP header (typically only 8 octets). + +The minimum required validation of ICMP messages with an on-path proof invoves +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum +validation, it SHOULD treat the packet as an ICMP message without an on-path +proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. + +ICMP messages without an on-path proof SHOULD undergo as much validation as an on-path proof -> on-path proof > +verifying that the message was sent by a network element that has observed a +QUIC packet that is still outstanding (not acknowledged and not deemed lost). +To perform the on-path validation, the sender would need to remember at least 8 +octets from the encrypted portion of outstanding QUIC packets. Alternatively, +the sender would need to remember a 64-bit hash of the first 64 octets of the +outstanding QUIC packets. If a QUIC endpoint does not perform this minimum +validation, it SHOULD treat the packet as an ICMP message without an on-path +proof. + +As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes +the protocol implementation to off-path attacks and requires mitigations. + +ICMP messages without an on-path proof SHOULD undergo as much validation as +possible. For example, such validation could include storing IP ID fields of +sent datagrams to validate that received ICMP messages are refering to +outstanding packets. This paragraph seems quite redundant. I would replace it with one sentence with recommendation for what state a sender can store to validate proof in ICMP messages. > -As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to -mitigate this risk. For instance, an application could: +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path +MTU in response to an ICMP PTB message during a handshake, unless then would then -> they -- 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/1412#pullrequestreview-129770367 ----==_mimepart_5b2846ace6520_5f3f2acb24212f54408ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

Thanks for getting this going, @igorlord ! A few comments, mostly editorial.

In draft-ietf-quic-transport.md:

> @@ -3157,9 +3157,9 @@ header, protected payload, and any authentication fields.
 All QUIC packets SHOULD be sized to fit within the estimated PMTU to avoid IP
 fragmentation or packet drops. To optimize bandwidth efficiency, endpoints
 SHOULD use Packetization Layer PMTU Discovery ({{!PLPMTUD=RFC4821}}).  Endpoints
-MAY use PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}}) for
-detecting the PMTU, setting the PMTU appropriately, and storing the result of
-previous PMTU determinations.
+MAY use classical PMTU Discovery ({{!PMTUDv4=RFC1191}}, {{!PMTUDv6=RFC8201}})

I think the context does make it clear, but @martinduke's suggestion seems reasonable.

In draft-ietf-quic-transport.md:

> @@ -3187,40 +3187,76 @@ QUIC packets on the affected path.  This could result in termination of the
 connection if an alternative path cannot be found.
 
 
-### IPv4 PMTU Discovery {#v4-pmtud}
+### Classical ICMP-based path MTU discovery {#icmp-pmtu}

ditto. Also, Capitalize This Section Title.

In draft-ietf-quic-transport.md:

> @@ -3187,40 +3187,76 @@ QUIC packets on the affected path.  This could result in termination of the
 connection if an alternative path cannot be found.
 
 
-### IPv4 PMTU Discovery {#v4-pmtud}
+### Classical ICMP-based path MTU discovery {#icmp-pmtu}
+
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with
+an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}},

the messages -> messages

In draft-ietf-quic-transport.md:

> +### Classical ICMP-based path MTU discovery {#icmp-pmtu}
+
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with
+an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}},
+which requires ICMPv6 error messages to contain "as much of invoking packet as
+possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and
+{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of
+the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).

This sentence is a bit hard to follow. Also, it's possible that the ICMP message was received after the sender deemed it lost, since the sender may have been too earnest in marking it lost. Perhaps remove the requirement that it not be marked as lost yet? How about the following: "To validate an ICMP message containing on-path proof, the proof MUST be from a QUIC packet that is not yet acknowledged."

In draft-ietf-quic-transport.md:

> +
+ICMP error messages used in classical Path MTU discovery may be classified into
+messages with an on-path proof and without an on-path proof.  ICMP messages with
+an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}},
+which requires ICMPv6 error messages to contain "as much of invoking packet as
+possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and
+{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of
+the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8

To perform the on-path validation -> To validate a received ICMP message

In draft-ietf-quic-transport.md:

> +an on-path proof are the messages sent in accordance with {{!ICMPv6=RFC4443}},
+which requires ICMPv6 error messages to contain "as much of invoking packet as
+possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and
+{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of
+the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum

the outstanding => outstanding

In draft-ietf-quic-transport.md:

> +which requires ICMPv6 error messages to contain "as much of invoking packet as
+possible without the ICMPv6 packet exceeding the minimum IPv6 MTU", and
+{{!RFC1812}}, which states that ICMPv4 error messages "SHOULD contain as much of
+the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum
+validation, it SHOULD treat the packet as an ICMP message without an on-path

SHOULD -> MUST

In draft-ietf-quic-transport.md:

> +the original datagram as possible without the length of the ICMP datagram
+exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum
+validation, it SHOULD treat the packet as an ICMP message without an on-path
+proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes

an on-path proof -> on-path proof

In draft-ietf-quic-transport.md:

> +exceeding 576 bytes".  ICMPv4 messages without an on-path proof are sent in
+accordance with the minimum requirments of {{!ICMP=RFC0792}} and contain fewer
+octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum
+validation, it SHOULD treat the packet as an ICMP message without an on-path
+proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.

the protocol implementation -> an endpoint

In draft-ietf-quic-transport.md:

> +octets past the IP header (typically only 8 octets).
+
+The minimum required validation of ICMP messages with an on-path proof invoves
+verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum
+validation, it SHOULD treat the packet as an ICMP message without an on-path
+proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.
+
+ICMP messages without an on-path proof SHOULD undergo as much validation as

an on-path proof -> on-path proof

In draft-ietf-quic-transport.md:

> +verifying that the message was sent by a network element that has observed a
+QUIC packet that is still outstanding (not acknowledged and not deemed lost).
+To perform the on-path validation, the sender would need to remember at least 8
+octets from the encrypted portion of outstanding QUIC packets.  Alternatively,
+the sender would need to remember a 64-bit hash of the first 64 octets of the
+outstanding QUIC packets.  If a QUIC endpoint does not perform this minimum
+validation, it SHOULD treat the packet as an ICMP message without an on-path
+proof.
+
+As noted in {{?RFC5927}}, using ICMP messages without an on-path proof exposes
+the protocol implementation to off-path attacks and requires mitigations.
+
+ICMP messages without an on-path proof SHOULD undergo as much validation as
+possible.  For example, such validation could include storing IP ID fields of
+sent datagrams to validate that received ICMP messages are refering to
+outstanding packets.

This paragraph seems quite redundant. I would replace it with one sentence with recommendation for what state a sender can store to validate proof in ICMP messages.

In draft-ietf-quic-transport.md:

>  
-As a result, endpoints that implement PMTUD in IPv4 SHOULD take steps to
-mitigate this risk. For instance, an application could:
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path
+MTU in response to an ICMP PTB message during a handshake, unless then would

then -> they

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

----==_mimepart_5b2846ace6520_5f3f2acb24212f54408ca-- From nobody Mon Jun 18 17:03:04 2018 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 0E22F130E36 for ; Mon, 18 Jun 2018 17:03:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 AS2VBZz9UcVj for ; Mon, 18 Jun 2018 17:02:58 -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 9C20012F18C for ; Mon, 18 Jun 2018 17:02:58 -0700 (PDT) Date: Mon, 18 Jun 2018 17:02:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529366577; bh=w6GH1ohOPzASkUfEm3bhLFbmZdwRMWfSuxfPF28nlps=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ichJbDMfbjs7iAxHPDvdiOHNRxFSErhjgiV79WIaDjbqhV8p1PiO1tuYwOLpMx44+ vLWW/8vYp/iBljn+6xXMyjEVZCplmKDyYsw0XGgsE53MBeM/gZdm/oPCIGOWJN3htl kG5tw99CEKrOUz8YcLITHve+c7+UsChcc/4VvleU= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b284831550f4_12db2aba9b670f54918fe"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 00:03:02 -0000 ----==_mimepart_5b284831550f4_12db2aba9b670f54918fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ekr commented on this pull request. > = -QUIC SHOULD delay sending acknowledgements in response to packets, -but MUST NOT excessively delay acknowledgements of packets containing -non-ack frames. Specifically, implementaions MUST attempt to -enforce a maximum ack delay to avoid causing the peer spurious -timeouts. The default maximum ack delay in QUIC is 25ms. +There are cases where one may be able to gain recovery information from +acknowledgements of packets in another packet number space, but they rel= y +on complex assumptions about the peer=E2=80=99s processing and acknowled= gement +algorithms. Even those are unable to quickly recover from cases such as= +losing the client's Initial, but receiving the 0-RTT packets. Below is +an optimization using coalesced packets and implicit acknowledgements. Oh, I meant to delete this graf too > = +Unlike TLS over TCP, QUIC applications which want to send data do not +send it through TLS "application_data" records. Rather, they send it +as QUIC STREAM frames which are then carried in QUIC packets. + + +# Carrying TLS Messages {#carrying-tls} + +QUIC carries TLS handshake data in CRYPTO_HS frames, each of which We also have CRYPTO_CLOSE. It's also confusing to have HANDSHAKE frames i= n !Handshake packets. I would really prefer not to change this at this time. I'm happy to bikes= hed this later, but it's going to be much easier to s/CRYPTO_HS// than any of the more generic alternatives, and so this doesn't need to= block the PR. > +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level.= +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. I am going to leave this up to MT's discretion. You should open an issue for BLOCKED. > = -## QUIC Key Expansion {#key-expansion} +A server rejects 0-RTT by rejecting 0-RTT at the TLS layer. This result= s in +early exporter keys being unavailable, thereby preventing the use of 0-R= TT for +QUIC. Yes, this just got missed in my edit. I can fix. > = -~~~ -struct { - uint16 length =3D Length; - opaque label<6..255> =3D "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the T= LS +handshake, using the AEAD algorithm negotiated by TLS. I think this is fine as-is. The TLS record layer is never used alone with= TCP. But I'll leave it to MT's discretion. > = -Packets that carry the TLS handshake (Initial, Retry, and Handshake) are= -protected with a secret derived from the Destination Connection ID field= from -the client's Initial packet. Specifically: +Initial packets are protected with +a secret derived from the Destination Connection ID field from the clien= t's +Initial packet. Specifically: Yes, that's correctl > = -### Retransmission and Acknowledgment of Unprotected Packets +: 0-RTT data can be acknowledged by the server as it receives it, but an= y OK -- = 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/1450#discussion_r196259663= ----==_mimepart_5b284831550f4_12db2aba9b670f54918fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ekr commented on this pull request.

In draft-ietf-quic-recovery.md:

>  =

-QUIC SHOULD delay sending acknowledgements in response to packets,
-but MUST NOT excessively delay acknowledgements of packets containing
-non-ack frames.  Specifically, implementaions MUST attempt to
-enforce a maximum ack delay to avoid causing the peer spurious
-timeouts.  The default maximum ack delay in QUIC is 25ms.
+There are cases where one may be able to gain recovery information from
+acknowledgements of packets in another packet number space, but they rel=
y
+on complex assumptions about the peer=E2=80=99s processing and acknowled=
gement
+algorithms.  Even those are unable to quickly recover from cases such as=

+losing the client's Initial, but receiving the 0-RTT packets.  Below=
 is
+an optimization using coalesced packets and implicit acknowledgements.

Oh, I meant to delete this graf too

In draft-ietf-quic-tls.md:

>  =

+Unlike TLS over TCP, QUIC applications which want to send data do not
+send it through TLS "application_data" records. Rather, they s=
end it
+as QUIC STREAM frames which are then carried in QUIC packets.
+
+
+# Carrying TLS Messages {#carrying-tls}
+
+QUIC carries TLS handshake data in CRYPTO_HS frames, each of which

We also have CRYPTO_CLOSE. It's also confusing to have HANDSHAKE frame= s in !Handshake packets.

I would really prefer not to change this at this time. I'm happy to bi= keshed this later, but it's going to be much easier to s/CRYPTO_HS// than= any of the more generic alternatives, and so this doesn't need to block = the PR.

In draft-ietf-quic-tls.md:

> +same encryption level. For instance, an i=
mplementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.=

+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.

I am going to leave this up to MT's discretion.

You should open an issue for BLOCKED.

In draft-ietf-quic-tls.md:

>  =

-## QUIC Key Expansion {#key-expansion}
+A server rejects 0-RTT by rejecting 0-RTT at the TLS layer.  This result=
s in
+early exporter keys being unavailable, thereby preventing the use of 0-R=
TT for
+QUIC.

Yes, this just got missed in my edit. I can fix.

In draft-ietf-quic-tls.md:

>  =

-~~~
-struct {
-   uint16 length =3D Length;
-   opaque label<6..255> =3D "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the T=
LS
+handshake, using the AEAD algorithm negotiated by TLS.

I think this is fine as-is. The TLS record layer is never used alone w= ith TCP. But I'll leave it to MT's discretion.

In draft-ietf-quic-tls.md:

>  =

-Packets that carry the TLS handshake (Initial, Retry, and Handshake) are=

-protected with a secret derived from the Destination Connection ID field=
 from
-the client's Initial packet.  Specifically:
+Initial packets are protected with
+a secret derived from the Destination Connection ID field from the clien=
t's
+Initial packet.  Specifically:

Yes, that's correctl

In draft-ietf-quic-tls.md:

>  =

-### Retransmission and Acknowledgment of Unprotected Packets
+: 0-RTT data can be acknowledged by the server as it receives it, but an=
y

OK

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or= mute the thread.3D""

= ----==_mimepart_5b284831550f4_12db2aba9b670f54918fe-- From nobody Mon Jun 18 17:16:24 2018 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 38F30130E5E for ; Mon, 18 Jun 2018 17:16:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EZZJphoW8H9c for ; Mon, 18 Jun 2018 17:16:20 -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 003C51274D0 for ; Mon, 18 Jun 2018 17:16:19 -0700 (PDT) Date: Mon, 18 Jun 2018 17:16:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529367378; bh=xN7hJnrSzBYpAzOiJmo0T3zfa4T1/oEjE94Xsr8bFLI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2aWo7vDke7exny5pcVVAqeKBJcjnfosX9uS2I/p05bcGSjiMOlbRcThKcdaZ88NAM QUooi4E9d05iDOJWHYtuVgjJljGPYGMTiS9Pod1YhlPJM1QmWXOK5HCU5IEgLNr04j a1bym3wdc7XD9YpFJJOOGuNFT94gVH7TZk/cZH6w= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b284b52d2dc1_39893ff427a00f7c1382be"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 00:16:23 -0000 ----==_mimepart_5b284b52d2dc1_39893ff427a00f7c1382be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson : There's another use case, which I had to think about when getting connection migration out for GQUIC. This is where if you have a CDN server inside of an ISP, you want to explicitly disable migrating connections to other client ISPs, since that would constitute "leakage" at the server. You may still want to hand out new CIDs to allow a client to use it after a long quiescent period, in anticipation of NAT rebinding. An explicit signal from the server is a clear policy indication to the client not to migrate connections across networks. This is admittedly difficult to enforce at the server without being too restrictive (by not handing out new CIDs). As I see it, a TP tells the client to not migrate connections across network changes. I would even suggest that a server MAY detect migrations across networks and close the connection with PROTOCOL_VIOLATION if it finds that a client violated this policy. -- 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/1271#issuecomment-398234657 ----==_mimepart_5b284b52d2dc1_39893ff427a00f7c1382be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson : There's anoth= er use case, which I had to think about when getting connection migration= out for GQUIC. This is where if you have a CDN server inside of an ISP, = you want to explicitly disable migrating connections to other client ISPs= , since that would constitute "leakage" at the server. You may still want= to hand out new CIDs to allow a client to use it after a long quiescent = period, in anticipation of NAT rebinding. An explicit signal from the ser= ver is a clear policy indication to the client not to migrate connections= across networks.

This is admittedly difficult to enforce at the server without being to= o restrictive (by not handing out new CIDs). As I see it, a TP tells the = client to not migrate connections across network changes. I would even su= ggest that a server MAY detect migrations across networks and close the c= onnection with PROTOCOL_VIOLATION if it finds that a client violated this= policy.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b284b52d2dc1_39893ff427a00f7c1382be-- From nobody Mon Jun 18 17:25:06 2018 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 8B160130F67 for ; Mon, 18 Jun 2018 17:25:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2xbSPIZLaVKk for ; Mon, 18 Jun 2018 17:25:02 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CE91130EA1 for ; Mon, 18 Jun 2018 17:25:02 -0700 (PDT) Date: Mon, 18 Jun 2018 17:25:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529367901; bh=5IrQSFHWxpuXTAYhxgbYg7wMuj6D1wbaq49NS4TDBvA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=P6jARyOgWyfB4HMkb3wzC3hOWA8zNyi6lkeu2luP70vm7eqbBsQHrGVOAW0x6zstb 0ItSLbPRwhyez7JaZyrgG86YQMzZAfJ5EQHWQeJjotNgaPjsgARUgbHfM5s01UJViw NZDKxUScK8wt1h1gf0tvuWIbe1DYXaBe9MVyWEXE= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b284d5df1aac_73463f80a4f70f802448fd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 00:25:05 -0000 ----==_mimepart_5b284d5df1aac_73463f80a4f70f802448fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. One comment inline. Also, I would suggest (as I did in my comment on the issue) that: (i) a server should be allowed to detect a client violation of this TP and close the connection with PROTOCOL_VIOLATION (or a new error if this doesn't sit well with folks), (ii) the text should make it clear that a NAT rebinding may still result in path validation. > @@ -1289,6 +1290,13 @@ preferred_address (0x0004): : The server's Preferred Address is used to effect a change in server address at the end of the handshake, as described in {{preferred-address}}. +disable_migration (0x0009): + +: The server does not support connection migration ({{migration}}). Clients MUST It's true that we only support client-driven migrations, but I think there's value in keeping most of the text agnostic to polarity. Is there a reason to disallow this TP in the opposite direction? It'll be a NO-OP, but we don't need to disallow it, I think. -- 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/1447#pullrequestreview-129782442 ----==_mimepart_5b284d5df1aac_73463f80a4f70f802448fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

One comment inline. Also, I would suggest (as I did in my comment on the issue) that: (i) a server should be allowed to detect a client violation of this TP and close the connection with PROTOCOL_VIOLATION (or a new error if this doesn't sit well with folks), (ii) the text should make it clear that a NAT rebinding may still result in path validation.

In draft-ietf-quic-transport.md:

> @@ -1289,6 +1290,13 @@ preferred_address (0x0004):
 : The server's Preferred Address is used to effect a change in server address at
   the end of the handshake, as described in {{preferred-address}}.
 
+disable_migration (0x0009):
+
+: The server does not support connection migration ({{migration}}). Clients MUST

It's true that we only support client-driven migrations, but I think there's value in keeping most of the text agnostic to polarity. Is there a reason to disallow this TP in the opposite direction? It'll be a NO-OP, but we don't need to disallow it, I think.

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

----==_mimepart_5b284d5df1aac_73463f80a4f70f802448fd-- From nobody Mon Jun 18 18:01:47 2018 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 E74A4130FA0 for ; Mon, 18 Jun 2018 18:01:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1A_22PXTBPzz for ; Mon, 18 Jun 2018 18:01:44 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59B59130F97 for ; Mon, 18 Jun 2018 18:01:44 -0700 (PDT) Date: Mon, 18 Jun 2018 18:01:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529370103; bh=/i+a4/iYjdL8RFWjZmo05G00cEux17Qr9WGEzw/J1nY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gDgLEcvcVk3xXl0v0GpuCKOLZAVD3qHtO3IkeiagZh0VHyMcaoK8z/Vs8gBVBUWuM MrgIe7ZxqnI/rfNXc3UQT0d9bbzz+r/DpZYN+mmdelTZGK3OvGLrm8m8Vm/LATOMm7 fRDu8wY62/9MvDx1IBUU7RuKwoN1TJ3fl6NXcxc4= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2855f7b6b20_1e853fc692df2f8096941"; 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.26 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: Tue, 19 Jun 2018 01:01:47 -0000 ----==_mimepart_5b2855f7b6b20_1e853fc692df2f8096941 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > ~~~ The hash function for HKDF when deriving handshake secrets and keys is SHA-256 -{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with QHKDF-Expand -is the connection ID chosen by the client. +{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with +HKDF-Expand-Label is the connection ID chosen by the client. Okay, then this one doesn't apply. -- 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/1450#discussion_r196268757 ----==_mimepart_5b2855f7b6b20_1e853fc692df2f8096941 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-tls.md:

>  ~~~
 
 The hash function for HKDF when deriving handshake secrets and keys is SHA-256
-{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with QHKDF-Expand
-is the connection ID chosen by the client.
+{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with
+HKDF-Expand-Label is the connection ID chosen by the client.

Okay, then this one doesn't apply.

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

----==_mimepart_5b2855f7b6b20_1e853fc692df2f8096941-- From nobody Mon Jun 18 18:14:28 2018 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 15F26130FA0 for ; Mon, 18 Jun 2018 18:14:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7gmkp1FhjEph for ; Mon, 18 Jun 2018 18:14:25 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D99B1130F97 for ; Mon, 18 Jun 2018 18:14:24 -0700 (PDT) Date: Mon, 18 Jun 2018 18:14:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529370863; bh=mGCETVZXIJ4Dg5GSLt2yL2TSEvRfENGzMuGk894XNT8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LYhInn4mwgrqEI+AWckif5AV5TdwKDYAj/P65inJwVrsAqK/zYXrcPlwA2uRIjDAa daugA6I8qPnrmqxEv8Rwzjx+6ZXmpsXJ6PKKsnGNM87vgBArSIywhexSg3RUKS/DoF 9m/vpVsMfnocPCyY+c5RrpNI1H1F71DmDB3lUZE8= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2858efcef08_555d3fde30782f78483451"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 01:14:27 -0000 ----==_mimepart_5b2858efcef08_555d3fde30782f78483451 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the Let's back up just a bit. First, QUIC receivers are far less likely to receive duplicates because as @ianswett pointed out, retransmissions are not duplicates. As @mirjak notes, this doesn't mean that the network won't do stupid things, but that really is the exception, not the rule. Duplicates in QUIC are necessarily network duplication. This is a significant difference in terms of *how much* this problem matters. I think suppression is fine, since the tradeoff is between enabling an on-the-side performance attack vs. an infinitesimally more aggressive response to a CE marked packet. Second, I agree with @kazuho that requiring duplicate detection should not be required, if only because I can cook up conditions under which an endpoint won't be able to do this without infinite state. Consider an endpoint that nacks a packet (sends an ack with this packet in a gap), receives an ack for this nack, and moves its "left edge" past that PN. Now, it receives a packet with that PN. It cannot verify that this packet is a duplicate, since it may never have received the original. I'd like to point out that this is ultimately a performance attack, and as with any other such attacks that use unauthenticated bits (ICMP?), we can provide some guidance to the receiver of a duplicate. I think the text here can changed a bit, with little to no real difference in impact. I'll propose the following text: "The ECN counters that an endpoint reports include values of the ECN field only from packets that are subsequently newly acknowledged. Note that an endpoint may newly acknowledge a duplicate packet if it no longer has state about the first receipt of the same packet. An endpoint may decrypt and drop a duplicate packet if it has state about the first receipt of the same packet, and in this case, the endpoint will not increase the ECN counters based on the duplicate packet." -- 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/1372#discussion_r196270229 ----==_mimepart_5b2858efcef08_555d3fde30782f78483451 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

Let's back up just a bit.

First, QUIC receivers are far less likely to receive duplicates because as @ianswett pointed out, retransmissions are not duplicates. As @mirjak notes, this doesn't mean that the network won't do stupid things, but that really is the exception, not the rule. Duplicates in QUIC are necessarily network duplication. This is a significant difference in terms of how much this problem matters. I think suppression is fine, since the tradeoff is between enabling an on-the-side performance attack vs. an infinitesimally more aggressive response to a CE marked packet.

Second, I agree with @kazuho that requiring duplicate detection should not be required, if only because I can cook up conditions under which an endpoint won't be able to do this without infinite state. Consider an endpoint that nacks a packet (sends an ack with this packet in a gap), receives an ack for this nack, and moves its "left edge" past that PN. Now, it receives a packet with that PN. It cannot verify that this packet is a duplicate, since it may never have received the original.

I'd like to point out that this is ultimately a performance attack, and as with any other such attacks that use unauthenticated bits (ICMP?), we can provide some guidance to the receiver of a duplicate. I think the text here can changed a bit, with little to no real difference in impact.

I'll propose the following text: "The ECN counters that an endpoint reports include values of the ECN field only from packets that are subsequently newly acknowledged. Note that an endpoint may newly acknowledge a duplicate packet if it no longer has state about the first receipt of the same packet. An endpoint may decrypt and drop a duplicate packet if it has state about the first receipt of the same packet, and in this case, the endpoint will not increase the ECN counters based on the duplicate packet."

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

----==_mimepart_5b2858efcef08_555d3fde30782f78483451-- From nobody Mon Jun 18 22:27:24 2018 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 7A6D6130E39 for ; Mon, 18 Jun 2018 22:27:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 WD6qsM0zbGT1 for ; Mon, 18 Jun 2018 22:27:21 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3699E128CF3 for ; Mon, 18 Jun 2018 22:27:21 -0700 (PDT) Date: Mon, 18 Jun 2018 22:27:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529386040; bh=9/fxWkR3BGHRbXLZxrzP/5iMw5xhlBzMQ0M7WCNWeso=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K6n55aA5t/nQKq4FRf/fikmGv7G0G3hZ3nYyIR6RWFZrPTrufuGxySEcL6BWTwwB4 X3tj71YVTuz6W2Ib6A3JaIudPl9ZGmLB69DUpALSjjoJVaeaSkJoH8mFSgkZqKPzQv 7eHyzR0eXxSdZVPkAEcQFlsIRntrUWGj+fS30Ea0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify and strengthen key update requirements (#1457) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28943856f80_771c3fd632612f7c13407a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 05:27:23 -0000 ----==_mimepart_5b28943856f80_771c3fd632612f7c13407a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The current design has limits for each cipher suite, that would be inherited from TLS. If we want to reference those requirements, we can do so. -- 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/1457#issuecomment-398278424 ----==_mimepart_5b28943856f80_771c3fd632612f7c13407a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The current design has limits for each cipher suite, that would be inherited from TLS. If we want to reference those requirements, we can do so.

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

----==_mimepart_5b28943856f80_771c3fd632612f7c13407a-- From nobody Mon Jun 18 22:32:02 2018 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 1330D128CF3 for ; Mon, 18 Jun 2018 22:32:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TjBKpwMDLTjL for ; Mon, 18 Jun 2018 22:31:58 -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 4DD9B128BAC for ; Mon, 18 Jun 2018 22:31:58 -0700 (PDT) Date: Mon, 18 Jun 2018 22:31:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529386317; bh=KFmoSw1o20/xAOvGIJMRSwaIJ8Udt2t3n+S9/LC2Lro=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ILR/KtNWm7YxwcUPMHu9SGe4xcGKoncJHtEtCxviz3ZVeHYNwxP5JfPO7XzB5nr9J 6ZNyMqSzSHwYW+pQmv3b+wHLQvSCS4AkuFZpAAT9XyP2ZEA413IuW/0DRtl4BW3NwS Fj3xDtg78e8DF+ZvWCdesz/WKSsJmlS6bFbgjhmU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28954d67e29_2d2b2adb8ac2ef5811233e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 05:32:00 -0000 ----==_mimepart_5b28954d67e29_2d2b2adb8ac2ef5811233e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As observed, we mandate use of SNI already (though we might want to soften this to allow encrypted SNI as @kazuho points out). TLS doesn't mandate use of SNI, which is entirely appropriate for QUIC-the-transport. -- 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/1456#issuecomment-398279115 ----==_mimepart_5b28954d67e29_2d2b2adb8ac2ef5811233e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

As observed, we mandate use of SNI already (though we might want to soften this to allow encrypted SNI as @kazuho points out). TLS doesn't mandate use of SNI, which is entirely appropriate for QUIC-the-transport.

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

----==_mimepart_5b28954d67e29_2d2b2adb8ac2ef5811233e-- From nobody Mon Jun 18 22:33:36 2018 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 E4261128CF3 for ; Mon, 18 Jun 2018 22:33:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 brrU5hMq5dix for ; Mon, 18 Jun 2018 22:33:33 -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 3CF0C128BAC for ; Mon, 18 Jun 2018 22:33:33 -0700 (PDT) Date: Mon, 18 Jun 2018 22:33:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529386410; bh=7Hu6X49Zb7wwFFAhrrYy0YDiDYKwksDe2uFzxWFIXZw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=mXwwgG/rC4+M0ndubGVXCOqWGntBSS9PB+QVAqQHyuSScayzioCqKk2I03B9cfLd5 dCQ2BAogbJ34VnGCoXWxplb4Fa1ghDYK5DUnFA1o0PIZW3j0qXNPXWmL0gdINF5SAW +zOqFIE10Bj4zki3veGFbyVo6bxyIE94EAFfQT3A= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2895aab60d1_5a5a3fc55a354f80155790"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 05:33:35 -0000 ----==_mimepart_5b2895aab60d1_5a5a3fc55a354f80155790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit hq mandates use of the server_name extension rather too strongly. > The Server Name Indication (SNI) extension [RFC6066] MUST be included in the TLS handshake. RFC 7540 is much weaker on this point. > The TLS implementation MUST support the Server Name Indication (SNI) [TLS-EXT] extension to TLS. HTTP/2 clients MUST indicate the target domain name when negotiating TLS. If we are to allow SNI encryption, then we should adopt similar language. -- 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/1459 ----==_mimepart_5b2895aab60d1_5a5a3fc55a354f80155790 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

hq mandates use of the server_name extension rather too strongly.

The Server Name Indication (SNI) extension [RFC6066] MUST be included in the TLS handshake.

RFC 7540 is much weaker on this point.

The TLS implementation MUST support the Server Name Indication (SNI) [TLS-EXT] extension to TLS. HTTP/2 clients MUST indicate the target domain name when negotiating TLS.

If we are to allow SNI encryption, then we should adopt similar language.

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

----==_mimepart_5b2895aab60d1_5a5a3fc55a354f80155790-- From nobody Mon Jun 18 22:40:28 2018 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 62D57128CF3 for ; Mon, 18 Jun 2018 22:40:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jAM1o1YRCV0t for ; Mon, 18 Jun 2018 22:40:23 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7357E124D68 for ; Mon, 18 Jun 2018 22:40:23 -0700 (PDT) Date: Mon, 18 Jun 2018 22:40:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529386822; bh=3SGO0NVnCCaEnNwqritRFVt+sIkDxxq6ygrXz7Wm+0o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xg/IViua0neskFJis5qriVAM0jead2VDXZEBpIqPcJ5Psg9gemo7pM6ZpXDPWx8tY o/1zBVJTVXhJKL4+oLPp6x1nz0zmgMeklUQwDz2OHf1F8uzf7qB7wtDAtVyrzjSY5B 1n93qRiJD8leVo1sdZq4pzIafqiT8QyR1FwNTApU= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b289746d51de_25a6f3f8f432bef781182d8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Tue, 19 Jun 2018 05:40:26 -0000 ----==_mimepart_5b289746d51de_25a6f3f8f432bef781182d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop by "use the real name from later", I was just thinking that we should use a defined term that we can link to -- if "probing packets" fits the bill, then that's great! -- 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/1271#issuecomment-398280390 ----==_mimepart_5b289746d51de_25a6f3f8f432bef781182d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop by "use the real name from later", I was just thinking that we should use a defined term that we can link to -- if "probing packets" fits the bill, then that's great!

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

----==_mimepart_5b289746d51de_25a6f3f8f432bef781182d8-- From nobody Mon Jun 18 22:44:25 2018 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 5B852128CF3 for ; Mon, 18 Jun 2018 22:44:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 lYm7Umz9iuk6 for ; Mon, 18 Jun 2018 22:44:22 -0700 (PDT) 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 9EF4F124D68 for ; Mon, 18 Jun 2018 22:44:22 -0700 (PDT) Date: Mon, 18 Jun 2018 22:44:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529387061; bh=E1dv8YLQTiOKmH4EHcav+ys0g8UM8I0rQzTMjQzp1K0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QcugNk0UQeuVNUTNFj0Dw9MKurDZjzpb4zFo+nVNMCJhDb14Ug0za+FEumyxQvO4r 68AAu7tUrPHYMha0DBT0VXH4/Iwzs8tr/FBD+MPy1mmVHKcHBW5P5zL2hCnb/yuWPS z6S3agRysi6qVmSKgdRnxmDHOZtpLFp44KZdib+4= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b289835f1c7d_7d4c3fdd75ec4f7c1467be"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Tue, 19 Jun 2018 05:44:25 -0000 ----==_mimepart_5b289835f1c7d_7d4c3fdd75ec4f7c1467be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @janaiyengar Minor clarification of (ii) above: NAT rebinding may result in a full migration, not just path validation, right? (With the current text indicating that servers are free to recognize that it's just a NAT rebinding and behave accordingly.) In other words, I think the operative intent here is that the client not initiate migration, with a note that just because the client isn't sending from a different endpoint that the server may still see NAT rebinding. -- 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/1447#issuecomment-398281005 ----==_mimepart_5b289835f1c7d_7d4c3fdd75ec4f7c1467be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@janaiyengar Minor clarificat= ion of (ii) above: NAT rebinding may result in a full migration, not just= path validation, right? (With the current text indicating that servers a= re free to recognize that it's just a NAT rebinding and behave accordingl= y.)

In other words, I think the operative intent here is that the client n= ot initiate migration, with a note that just because the client isn't sen= ding from a different endpoint that the server may still see NAT rebindin= g.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b289835f1c7d_7d4c3fdd75ec4f7c1467be-- From nobody Mon Jun 18 23:33:36 2018 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 2DBD7128CF3 for ; Mon, 18 Jun 2018 23:33:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yA87DK0bBrXn for ; Mon, 18 Jun 2018 23:33:32 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57E3E124D68 for ; Mon, 18 Jun 2018 23:33:32 -0700 (PDT) Date: Mon, 18 Jun 2018 23:33:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529390011; bh=z3l6AWW301a4/jrKTuGsAcCVdr19u/D9iuK4GGeAAy4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=S/i9y9Mf7AiKIP88J/W9yKL0urCHRLDbHBiAjL/3ffE609VwB1QPNuorM4ZvfpqfT QSKc59OY+AtEcU8Oe8lMRfxU+jx4hNvL//uLVZBL/Nn6uiLpz38h/T1i9JgbNdDSFn rG/AAlg5qdRZz0+svEO6D1JhcqTR57uLvgEb7JWI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28a3bb4370d_f593fc4bffa8f8417686b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 06:33:34 -0000 ----==_mimepart_5b28a3bb4370d_f593fc4bffa8f8417686b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit An alternative is to include the packet number from the Initial in the Retry packet. That makes Retry very-much more version-specific than it was, but it would allow the client to learn which Initial triggered the Retry, so that it can avoid going backwards. -- 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/1451#issuecomment-398289684 ----==_mimepart_5b28a3bb4370d_f593fc4bffa8f8417686b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

An alternative is to include the packet number from the Initial in the Retry packet. That makes Retry very-much more version-specific than it was, but it would allow the client to learn which Initial triggered the Retry, so that it can avoid going backwards.

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

----==_mimepart_5b28a3bb4370d_f593fc4bffa8f8417686b-- From nobody Mon Jun 18 23:39:29 2018 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 6A901130DC1 for ; Mon, 18 Jun 2018 23:39:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 lK9ZNIG-kxJR for ; Mon, 18 Jun 2018 23:39:25 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63CB012E039 for ; Mon, 18 Jun 2018 23:39:25 -0700 (PDT) Date: Mon, 18 Jun 2018 23:39:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529390364; bh=2mYmeMffXZD6+4cipmjDwOfaH3dHCYGwN30diW+FzzI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PW6z9BKb3Q1XA81iPqUZqOr8JCHeTuZMLMR74UcGtmMjvhrIFhiby8re9m4D9YGBi FIn72R/I1JGGKOcmvrhmgGQpLjYmwr6GHmJPFl7DcgS0I3i6FEqfcyItX7dIVrN5eD KACAIS2WILOoq2ots+ahsKRl5MWZY7VUOhOfKpdA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28a51c5db9c_dabf3fc9650caf801310f1"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 06:39:28 -0000 ----==_mimepart_5b28a51c5db9c_dabf3fc9650caf801310f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the The problem with that text is that it assumes something quite dangerous: that a receiver might accept a packet when it isn't sure that it has received it before. And content might be different. What @ianswett suggested before is better: if you move the trailing edge forward, then packets that you believe to be behind that edge are dropped unconditionally. Or, more concisely stated: you only accept packets that you know you haven't accepted before. That errs on the side of dropping rather than accepting, which I believe to be safe. -- 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/1372#discussion_r196308696 ----==_mimepart_5b28a51c5db9c_dabf3fc9650caf801310f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

The problem with that text is that it assumes something quite dangerous: that a receiver might accept a packet when it isn't sure that it has received it before. And content might be different.

What @ianswett suggested before is better: if you move the trailing edge forward, then packets that you believe to be behind that edge are dropped unconditionally. Or, more concisely stated: you only accept packets that you know you haven't accepted before. That errs on the side of dropping rather than accepting, which I believe to be safe.

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

----==_mimepart_5b28a51c5db9c_dabf3fc9650caf801310f1-- From nobody Tue Jun 19 01:09:54 2018 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 528A8130DEB for ; Tue, 19 Jun 2018 01:09:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 58vKwb9KjUHu for ; Tue, 19 Jun 2018 01:09:50 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F23E12D7F8 for ; Tue, 19 Jun 2018 01:09:50 -0700 (PDT) Date: Tue, 19 Jun 2018 01:09:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529395788; bh=QAygtMAJcbC4P8+J66yn2wFiwlWK4Jn1t0JwIoeSJKs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WZcy51CorCwxUuSPqCNaESLs1qgjE6Y1DmAGnZJNh32ssPMApPpf5c5UVmaEp+Pbt csecAH7VBlt5q+czjerhbS3BVHkIgPAPhoOiTiKDd3Scq+2QWKMcJEYmdT/p5SCd0e ncWFxWHNMp2YwtELuFMRlMfrZXkON9vK548YG3Jk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28ba4c272e_7672adf92722f581730bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 19 Jun 2018 08:09:53 -0000 ----==_mimepart_5b28ba4c272e_7672adf92722f581730bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the > The problem with that text is that it assumes something quite dangerous: that a receiver might accept a packet when it isn't sure that it has received it before. And content might be different. I am not sure if the content could be different. I'd assume that the only case in which it could be different is when the sender reuses a packet number. I do not think that we need to detect that (and if we do, it should be a PROTOCOL_VIOLATION rather than a drop). -- 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/1372#discussion_r196330195 ----==_mimepart_5b28ba4c272e_7672adf92722f581730bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

The problem with that text is that it assumes something quite dangerous: that a receiver might accept a packet when it isn't sure that it has received it before. And content might be different.

I am not sure if the content could be different. I'd assume that the only case in which it could be different is when the sender reuses a packet number. I do not think that we need to detect that (and if we do, it should be a PROTOCOL_VIOLATION rather than a drop).

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

----==_mimepart_5b28ba4c272e_7672adf92722f581730bb-- From nobody Tue Jun 19 01:25:16 2018 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 30D861310AF for ; Tue, 19 Jun 2018 01:25:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 CyrSQDsgvuFG for ; Tue, 19 Jun 2018 01:25:12 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1821310AD for ; Tue, 19 Jun 2018 01:25:12 -0700 (PDT) Date: Tue, 19 Jun 2018 01:25:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529396711; bh=FsOQY19y8H9i9MlEP9lBlSzT4bDxlieUwc1zUObue8k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pEBUo7Etqn0ASP4Se49/7u+NUgk6PusajJIGMsssmFl/QCJ0YAN3F0HPui2gDtL29 K9JBBcjdvPdySq0SL8x+5DRh71CibIkA9QcNBSJqba5tWTCmuiGrDCC3P3UnXReE3S y99uaZ1P3TSHVpEgfTzsBje1ZKjwXoNbBoNdBRKw= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28bde7d1d00_14b93fdf76ebef84661e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Tue, 19 Jun 2018 08:25:15 -0000 ----==_mimepart_5b28bde7d1d00_14b93fdf76ebef84661e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @marten-seemann > In an end-to-end protocol, we generally don't want "helpful" middleboxes to interfere with handshakes by performing a Retry (and thereby introducing latency). Obviously, this statement depends on the definition of "middlebox", which I here use as any node on the path that neither belongs to the server's nor the client's architecture. We should design QUIC's retry mechanism such that a retry can **only** be performed by devices that are under the control of the server operator. +1 I agree to what Marten says. Allowing middleboxes that send retries without sharing secrets with the servers has two issues: * the feature can be abused by somebody other than server operator * that in turn may lead to ossification, considering the fact that Retry is not a invariant Considering that, I'd prefer having a retry mechanism that enforces sharing a secret between the middlebox (that sends a retry) and the server. Which in turns would mean that multiple retries are unnecessary. -- 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/1451#issuecomment-398317321 ----==_mimepart_5b28bde7d1d00_14b93fdf76ebef84661e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@marten-seemann

In an end-to-end protocol, we generally don't want "helpful" middlebox= es to interfere with handshakes by performing a Retry (and thereby introd= ucing latency). Obviously, this statement depends on the definition of "m= iddlebox", which I here use as any node on the path that neither belongs = to the server's nor the client's architecture.
We should design QUIC's retry mechanism such that a retry can onl= y be performed by devices that are under the control of the serv= er operator.

+1

I agree to what Marten says.

Allowing middleboxes that send retries without sharing secrets with th= e servers has two issues:

  • the feature can be abused by somebody other than server operator
    • =
  • that in turn may lead to ossification, considering the fact that Retr= y is not a invariant

Considering that, I'd prefer having a retry mechanism that enforces sh= aring a secret between the middlebox (that sends a retry) and the server.= Which in turns would mean that multiple retries are unnecessary.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b28bde7d1d00_14b93fdf76ebef84661e5-- From nobody Tue Jun 19 02:08:59 2018 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 357CD130F00 for ; Tue, 19 Jun 2018 02:08:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 W0-vjlEL4Sm9 for ; Tue, 19 Jun 2018 02:08:52 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEFC6130DD0 for ; Tue, 19 Jun 2018 02:08:49 -0700 (PDT) Date: Tue, 19 Jun 2018 02:08:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529399329; bh=UilQpZYn66Vb4NC7C5MeaNTRZsebFSHZreK8RB2Gy3M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F6GiPUJPWaQDSeM/pPxREEkYA3HHWt15dMlkafGTVWMTA453Id4BlYMHNVL9tajdK 1EB3qdXqrZ50ZhHyhGo1XuiRBji11eJwQOz8gp1fQw0ygykO6PDx7KwTShopPe3+xE mF8r82Ihxgjm6udgc3+/gaT1Fe2vCkQ1LKafJoSQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28c820e9ea7_36512ab53f0f0f5417665e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 09:08:58 -0000 ----==_mimepart_5b28c820e9ea7_36512ab53f0f0f5417665e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. There are a few sections here that seem to be quite verbose. Nothing technically wrong, but I think that fewer words would be OK. > @@ -1042,6 +1080,31 @@ acked_packet from sent_packets. kDefaultMss * acked_packet.bytes / congestion_window ~~~ +### On Packets Marked + +Invoked by an increment in the number of CE marked packets, as +indicated by a newly received ACK_ECN frame when compared to +previous_ecn_ce_ctr. + +~~~ + CongestionEvent(packet_number): This looks like a generic function (it's invoked from OnPacketsLost). It should probably be moved to a common section.. > @@ -1125,21 +1129,22 @@ multiple packets. Reassembling messages requires that a server maintain state prior to establishing a connection, exposing the server to a denial of service risk. -The first client packet of the cryptographic handshake protocol MUST fit within -a 1232 octet QUIC packet payload. This includes overheads that reduce the space -available to the cryptographic handshake protocol. + +The first client packet of the cryptographic handshake protocol MUST fit +within a 1232 octet QUIC packet payload. This includes overheads that +reduce the space available to the cryptographic handshake protocol. Not sure what is going on here. Looks like gratuitous reflow. > @@ -1427,6 +1432,77 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN Capability Check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for +non-destructive congestion notification by a network node. That is, packets are +marked instead of being discarded by routers and other devices along a network +path. QUIC endpoints perform capability verification on connection establishment non-sequitur: this moves from saying what ECN is to capability verification. Suggest: "QUIC endpoints determine whether a path correctly supports ECN marking by verifying paths when connections are established and when migrating the connection to a new path." > @@ -1427,6 +1432,77 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN Capability Check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for +non-destructive congestion notification by a network node. That is, packets are +marked instead of being discarded by routers and other devices along a network +path. QUIC endpoints perform capability verification on connection establishment +as well as connection migration. ECN can be used unidirectionally, +bidirectionally, or disabled depending on endpoint and path capabilities. This is odd, but you might instead say "Each peer independently validates network paths, which leads to ECN being enabled separately for each direction on a path." > @@ -1427,6 +1432,77 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN Capability Check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for +non-destructive congestion notification by a network node. That is, packets are +marked instead of being discarded by routers and other devices along a network +path. QUIC endpoints perform capability verification on connection establishment +as well as connection migration. ECN can be used unidirectionally, +bidirectionally, or disabled depending on endpoint and path capabilities. + +The capability check makes use of the ACK_ECN frame in {{frame-ack-ecn}}. Each +endpoint individually performs an ECN capability check for its send path. The +check is performed by attempting to set the ECN bits in the IP header to either +ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with I'm struggling a little with the length of this sentence, and I think that we could be a little more concise with the remainder of this section: """ ECN is validated by setting the ECT(0) or ECT(1) bit in the IP header, following the guidelines of {{!RFC8311}}. Clients and servers both mark the IP packet containing an Initial packet ({{packet-initial}}). If ECN is supported, the recipient of a marked packet will increase the corresponding counter and send an ACK_ECN frame. An endpoint uses the ACK_ECN frame to verify that the ECT markings were received by its peer. The endpoint counts the number of acknowledged QUIC packets that were sent in marked IP packets. If the counters in the ACK_ECN frame match that number, the path and peer do not remove ECN markings. The endpoint records this path as being ECN capable and continues to mark IP packets that it sends. If an endpoint receives an ACK frame, indicating that no markings were received, or the counter in the ACK_ECN frame do not match the number of QUIC packets that were sent in marked IP packets, then the path or peer remove ECN markings. The endpoint records this path as not being ECN capable and it ceases marking of packets. IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify that the new path supports ECN, see {{ecn-connection-migration}}. """ Note that I've chosen to assume the stream 0 changes here. It simplifies things. I've also made clear the distinction between QUIC packets and IP packets. With coalescing, that distinction is critical. I've opted for counting of QUIC packets in marked IP packets rather than marked IP packets. More on this below... > +This capability check thus has verified that one direction of the path between +the peers is free from issues with ECN bleaching and that the application does +not experience problems with access to the ECN field in the IP header. In this +case the marking of the generated packets with ECT continues. + +If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of +packets that was marked as ECT in the sender, or if the comparision of the +counters with the total of acknolwedged packets indicates that not all packets +arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN +Capable. If the endpoint determine the path as currently not ECN capable it +SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + + +### Continuous Verification of ECN {#ecn-continuous-verification} If an endpoint successfully marks packets, then every IP packet it sends will be marked. That leads to continuously increasing counters, which is a little inefficient. A different design for ACK_ECN might be more efficient: record the number of exceptions. An ACK frame is used if there is no ECN support, or bleaching. ACK_ECN then records two counters: the number of packets with ECT(1) markings, and the number of packets with CE markings. Yes, this optimizes for ECT(0) markings, but that's consistent with advice in 8311. The counters should stay low, or at least increase only as congestion is avoided. This requires that you count QUIC packets carried in marked IP packets, and not count IP packets, as above. The only problem with this is that it breaks down if you have multiple paths and one of those paths bleaches. You could use ACK for the bleaching path and ACK_ECN for the other. Given that we only have to manage migration occasionally, that might be OK. The ACK loss problem described below remains, unfortunately. But it's much less likely to happen. I'm not sure if that's a good thing or not. > @@ -1783,6 +1860,75 @@ Note that receipt of packets with higher packet numbers from the legitimate peer address will trigger another connection migration. This will cause the validation of the address of the spurious migration to be abandoned. +### ECN Capability Check for Migrated Connection {#ecn-connection-migration} + +Connection migration requires that the path's ECN capability is verified +again. The ECN capability as indicated in section {{ecn-capability-check}} +should be repeated when a connection is migrated. This verifies that the +endpoints are ECN-capable and that the ECN field is not bleached along the new +path. This section could probably be more concise. """ Each new path is probed to determine whether it supports ECN. Packets sent on the new path are sent in IP packets with an ECT marking as described in {{previous-section-on-ecn}}. Markings, or absence of markings, on packets sent on multiple paths can make it difficult to correctly attribute counters with markings on specific packets. Recording the packet number when connection migration occurred might help in correlating increases in counters with packets sent on the new path. If an acknowledgment indicates that the markings were retained, the path is marked as ECN capable and subsequent IP packets sent on that path continue to be ECT marked. If an acknowledgment indicates that ECN markings are removed, subsequent packets are sent with Non-ECT. """ > +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN Block ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"} + + +### ECN Block {#ECN-Block} + +The ECN block is described below. The size (i) indicates variable-length +encoding, explained in {{integer-encoding}}. The encoding length for each +counter (1, 2, 4 or 8 bytes) should be selected such that all the +significant bits are represented. This second sentence is unnecessary and potentially misleading. > @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks {#security-ecn} + +An on-path attacker may manipulate the value of the field, affecting the +congestion avoidance behavior of the sender. Removing any ECN-CE marking causes +senders to maintain or increase their sending rate beyond that the path can +sustain, which will eventually result in loss. Adding an ECN-CE marking causes +senders to reduce their sending rate. The later could equally be accomplished by latter > @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks {#security-ecn} + +An on-path attacker may manipulate the value of the field, affecting the +congestion avoidance behavior of the sender. Removing any ECN-CE marking causes +senders to maintain or increase their sending rate beyond that the path can +sustain, which will eventually result in loss. Adding an ECN-CE marking causes +senders to reduce their sending rate. The later could equally be accomplished by +dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} discusses +the effects of undesired manipulation of the ECN field in more details. detail > @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack. However, setting the limit too low could affect performance when applications expect to open large number of streams. +## Explicit Congestion Notification Attacks {#security-ecn} + +An on-path attacker may manipulate the value of the field, affecting the +congestion avoidance behavior of the sender. Removing any ECN-CE marking causes +senders to maintain or increase their sending rate beyond that the path can +sustain, which will eventually result in loss. Adding an ECN-CE marking causes +senders to reduce their sending rate. The later could equally be accomplished by +dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} discusses +the effects of undesired manipulation of the ECN field in more details. + +If a receiver does not discard duplicate packets, an off-path attacker can +retransmit packets with ECN bits set and manipulate the senders congestion +avoidance state. If duplicate packets are dropped, the off-path attacker will s/dropped/discarded -- 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/1372#pullrequestreview-129837319 ----==_mimepart_5b28c820e9ea7_36512ab53f0f0f5417665e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

There are a few sections here that seem to be quite verbose. Nothing technically wrong, but I think that fewer words would be OK.

In draft-ietf-quic-recovery.md:

> @@ -1042,6 +1080,31 @@ acked_packet from sent_packets.
          kDefaultMss * acked_packet.bytes / congestion_window
 ~~~
 
+### On Packets Marked
+
+Invoked by an increment in the number of CE marked packets, as
+indicated by a newly received ACK_ECN frame when compared to
+previous_ecn_ce_ctr.
+
+~~~
+   CongestionEvent(packet_number):

This looks like a generic function (it's invoked from OnPacketsLost). It should probably be moved to a common section..

In draft-ietf-quic-transport.md:

> @@ -1125,21 +1129,22 @@ multiple packets.  Reassembling messages requires that a server maintain state
 prior to establishing a connection, exposing the server to a denial of service
 risk.
 
-The first client packet of the cryptographic handshake protocol MUST fit within
-a 1232 octet QUIC packet payload.  This includes overheads that reduce the space
-available to the cryptographic handshake protocol.
+
+The first client packet of the cryptographic handshake protocol MUST fit
+within a 1232 octet QUIC packet payload. This includes overheads that
+reduce the space available to the cryptographic handshake protocol.

Not sure what is going on here. Looks like gratuitous reflow.

In draft-ietf-quic-transport.md:

> @@ -1427,6 +1432,77 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN Capability Check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for
+non-destructive congestion notification by a network node.  That is, packets are
+marked instead of being discarded by routers and other devices along a network
+path. QUIC endpoints perform capability verification on connection establishment

non-sequitur: this moves from saying what ECN is to capability verification. Suggest: "QUIC endpoints determine whether a path correctly supports ECN marking by verifying paths when connections are established and when migrating the connection to a new path."

In draft-ietf-quic-transport.md:

> @@ -1427,6 +1432,77 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN Capability Check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for
+non-destructive congestion notification by a network node.  That is, packets are
+marked instead of being discarded by routers and other devices along a network
+path. QUIC endpoints perform capability verification on connection establishment
+as well as connection migration. ECN can be used unidirectionally,
+bidirectionally, or disabled depending on endpoint and path capabilities.

This is odd, but you might instead say "Each peer independently validates network paths, which leads to ECN being enabled separately for each direction on a path."

In draft-ietf-quic-transport.md:

> @@ -1427,6 +1432,77 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN Capability Check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for
+non-destructive congestion notification by a network node.  That is, packets are
+marked instead of being discarded by routers and other devices along a network
+path. QUIC endpoints perform capability verification on connection establishment
+as well as connection migration. ECN can be used unidirectionally,
+bidirectionally, or disabled depending on endpoint and path capabilities.
+
+The capability check makes use of the ACK_ECN frame in {{frame-ack-ecn}}. Each
+endpoint individually performs an ECN capability check for its send path. The
+check is performed by attempting to set the ECN bits in the IP header to either
+ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with

I'm struggling a little with the length of this sentence, and I think that we could be a little more concise with the remainder of this section:

"""
ECN is validated by setting the ECT(0) or ECT(1) bit in the IP header, following the guidelines of {{!RFC8311}}. Clients and servers both mark the IP packet containing an Initial packet ({{packet-initial}}). If ECN is supported, the recipient of a marked packet will increase the corresponding counter and send an ACK_ECN frame.

An endpoint uses the ACK_ECN frame to verify that the ECT markings were received by its peer. The endpoint counts the number of acknowledged QUIC packets that were sent in marked IP packets. If the counters in the ACK_ECN frame match that number, the path and peer do not remove ECN markings. The endpoint records this path as being ECN capable and continues to mark IP packets that it sends.

If an endpoint receives an ACK frame, indicating that no markings were received, or the counter in the ACK_ECN frame do not match the number of QUIC packets that were sent in marked IP packets, then the path or peer remove ECN markings. The endpoint records this path as not being ECN capable and it ceases marking of packets.

IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify that the new path supports ECN, see {{ecn-connection-migration}}.
"""

Note that I've chosen to assume the stream 0 changes here. It simplifies things.

I've also made clear the distinction between QUIC packets and IP packets. With coalescing, that distinction is critical. I've opted for counting of QUIC packets in marked IP packets rather than marked IP packets. More on this below...

In draft-ietf-quic-transport.md:

> +This capability check thus has verified that one direction of the path between
+the peers is free from issues with ECN bleaching and that the application does
+not experience problems with access to the ECN field in the IP header. In this
+case the marking of the generated packets with ECT continues.
+
+If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of
+packets that was marked as ECT in the sender, or if the comparision of the
+counters with the total of acknolwedged packets indicates that not all packets
+arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN
+Capable.  If the endpoint determine the path as currently not ECN capable it
+SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the
+connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+
+### Continuous Verification of ECN {#ecn-continuous-verification}

If an endpoint successfully marks packets, then every IP packet it sends will be marked. That leads to continuously increasing counters, which is a little inefficient.

A different design for ACK_ECN might be more efficient: record the number of exceptions. An ACK frame is used if there is no ECN support, or bleaching. ACK_ECN then records two counters: the number of packets with ECT(1) markings, and the number of packets with CE markings.

Yes, this optimizes for ECT(0) markings, but that's consistent with advice in 8311. The counters should stay low, or at least increase only as congestion is avoided.

This requires that you count QUIC packets carried in marked IP packets, and not count IP packets, as above.

The only problem with this is that it breaks down if you have multiple paths and one of those paths bleaches. You could use ACK for the bleaching path and ACK_ECN for the other. Given that we only have to manage migration occasionally, that might be OK.

The ACK loss problem described below remains, unfortunately. But it's much less likely to happen. I'm not sure if that's a good thing or not.

In draft-ietf-quic-transport.md:

> @@ -1783,6 +1860,75 @@ Note that receipt of packets with higher packet numbers from the legitimate peer
 address will trigger another connection migration.  This will cause the
 validation of the address of the spurious migration to be abandoned.
 
+### ECN Capability Check for Migrated Connection {#ecn-connection-migration}
+
+Connection migration requires that the path's ECN capability is verified
+again. The ECN capability as indicated in section {{ecn-capability-check}}
+should be repeated when a connection is migrated. This verifies that the
+endpoints are ECN-capable and that the ECN field is not bleached along the new
+path.

This section could probably be more concise.

"""
Each new path is probed to determine whether it supports ECN. Packets sent on the new path are sent in IP packets with an ECT marking as described in {{previous-section-on-ecn}}.

Markings, or absence of markings, on packets sent on multiple paths can make it difficult to correctly attribute counters with markings on specific packets. Recording the packet number when connection migration occurred might help in correlating increases in counters with packets sent on the new path.

If an acknowledgment indicates that the markings were retained, the path is marked as ECN capable and subsequent IP packets sent on that path continue to be ECT marked. If an acknowledgment indicates that ECN markings are removed, subsequent packets are sent with Non-ECT.
"""

In draft-ietf-quic-transport.md:

> +|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                           ECN Block                         ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"}
+
+
+### ECN Block {#ECN-Block}
+
+The ECN block is described below. The size (i) indicates variable-length
+encoding, explained in {{integer-encoding}}. The encoding length for each
+counter (1, 2, 4 or 8 bytes) should be selected such that all the
+significant bits are represented.

This second sentence is unnecessary and potentially misleading.

In draft-ietf-quic-transport.md:

> @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks {#security-ecn}
+
+An on-path attacker may manipulate the value of the field, affecting the
+congestion avoidance behavior of the sender. Removing any ECN-CE marking causes
+senders to maintain or increase their sending rate beyond that the path can
+sustain, which will eventually result in loss. Adding an ECN-CE marking causes
+senders to reduce their sending rate. The later could equally be accomplished by

latter

In draft-ietf-quic-transport.md:

> @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks {#security-ecn}
+
+An on-path attacker may manipulate the value of the field, affecting the
+congestion avoidance behavior of the sender. Removing any ECN-CE marking causes
+senders to maintain or increase their sending rate beyond that the path can
+sustain, which will eventually result in loss. Adding an ECN-CE marking causes
+senders to reduce their sending rate. The later could equally be accomplished by
+dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} discusses
+the effects of undesired manipulation of the ECN field in more details.

detail

In draft-ietf-quic-transport.md:

> @@ -4200,6 +4434,20 @@ limit mitigates the effect of the stream commitment attack.  However, setting
 the limit too low could affect performance when applications expect to open
 large number of streams.
 
+## Explicit Congestion Notification Attacks {#security-ecn}
+
+An on-path attacker may manipulate the value of the field, affecting the
+congestion avoidance behavior of the sender. Removing any ECN-CE marking causes
+senders to maintain or increase their sending rate beyond that the path can
+sustain, which will eventually result in loss. Adding an ECN-CE marking causes
+senders to reduce their sending rate. The later could equally be accomplished by
+dropping packets for the connection. Section 18 and 19 of {{!RFC3168}} discusses
+the effects of undesired manipulation of the ECN field in more details.
+
+If a receiver does not discard duplicate packets, an off-path attacker can
+retransmit packets with ECN bits set and manipulate the senders congestion
+avoidance state. If duplicate packets are dropped, the off-path attacker will

s/dropped/discarded

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

----==_mimepart_5b28c820e9ea7_36512ab53f0f0f5417665e-- From nobody Tue Jun 19 02:45:31 2018 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 31B0D1310CA for ; Tue, 19 Jun 2018 02:45:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 8GSNgqpBpsHn for ; Tue, 19 Jun 2018 02:45:27 -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 CB02B130DC5 for ; Tue, 19 Jun 2018 02:45:26 -0700 (PDT) Date: Tue, 19 Jun 2018 02:45:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529401525; bh=j2gkDl5Iyg0Flqp9GOnvIgiTIkwrxvon7ZmewoQh1C8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OFt5cXUylrl/aOlNmHkXqVfD2WuGTVMmQc2H+itzVf0y/pujFSDa/ajJQE8ylKolA 6UvmHcdP8/lNnlXVvwnSrsZCLQ+EBAafYn43BnO/4JqNQC7b2fJc9G198jmcnJ1vnG R0mA2xfbpt06Y2odTKfm3YQoeT33Bj6ml3RJnxmk= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28d0b5a41f8_6ce83fdf67160f7c155463"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 19 Jun 2018 09:45:29 -0000 ----==_mimepart_5b28d0b5a41f8_6ce83fdf67160f7c155463 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording +the number of packets that were received with the corresponding ECN +codepoint in the IP header. If the header is not readable from the +application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet +are duplicated by the network then only the value of the ECN field of +the packet copy first received SHALL be included in the counters, the ECN +field value for a duplicate SHALL be ignored. This to prevent the @martinthomson it was not my intention to require infinite state. I will see if I can reformulate to say that for any packet within the window of PNs that you will accept to process at all you need to maintain duplication detection before adding the ECN field values to the counters. @mirjak TSVWG has asked if there was anything from the QUIC ECN work that was of general nature and should be discussed in TSVWG and I think this is one of those things. However, my opinion is that due to ECN's unauthenticated nature, it is reasonable to suppress network duplicates. Otherwise use of ECN makes one more open to attacks to drive down the congestion window for a connection than when not using it. Yes, the connection will be slightly less responsive to the congestion signal, how much is depending on the amount of network duplication that occur. -- 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/1372#discussion_r196358953 ----==_mimepart_5b28d0b5a41f8_6ce83fdf67160f7c155463 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +3033,95 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording
+the number of packets that were received with the corresponding ECN
+codepoint in the IP header. If the header is not readable from the
+application, the codepoint 00 (Not-ECT) MUST be assumed. If any packet
+are duplicated by the network then only the value of the ECN field of
+the packet copy first received SHALL be included in the counters, the ECN
+field value for a duplicate SHALL be ignored. This to prevent the

@martinthomson it was not my intention to require infinite state. I will see if I can reformulate to say that for any packet within the window of PNs that you will accept to process at all you need to maintain duplication detection before adding the ECN field values to the counters.

@mirjak TSVWG has asked if there was anything from the QUIC ECN work that was of general nature and should be discussed in TSVWG and I think this is one of those things. However, my opinion is that due to ECN's unauthenticated nature, it is reasonable to suppress network duplicates. Otherwise use of ECN makes one more open to attacks to drive down the congestion window for a connection than when not using it. Yes, the connection will be slightly less responsive to the congestion signal, how much is depending on the amount of network duplication that occur.

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

----==_mimepart_5b28d0b5a41f8_6ce83fdf67160f7c155463-- From nobody Tue Jun 19 02:57:09 2018 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 E8015130DC5 for ; Tue, 19 Jun 2018 02:57:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cYE7yim2rUTr for ; Tue, 19 Jun 2018 02:57:06 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3E731277D2 for ; Tue, 19 Jun 2018 02:57:05 -0700 (PDT) Date: Tue, 19 Jun 2018 02:57:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529402225; bh=StA/61v+QgGW49ZP6ZZ2TJpN14rlY8VC33FDaDgaJ9w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=afoHxAf5yleVoO233iAijOYQErY4bZc/G94tvOMBk9fSqs8UUeA59F9DRoDTDXy8f dQVaXhlbLZc/R6qpzY4RXnShXJyT0d62XUVx9ExZ8bvSmfXXrzO3XFaiiO0PWr50TL SqtLOXRaqZzkaB08myEfnbi3r5KRz50XKg5k7r7c= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28d37134de5_616f2b0a1ae6ef5c57177"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 19 Jun 2018 09:57:09 -0000 ----==_mimepart_5b28d37134de5_616f2b0a1ae6ef5c57177 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho Yes, now we are getting to proposals that appear to be working from my perspective. I think the one bit proposal is actually quite interesting, but I think there need to be feedback from people who better understand L4S and any other proposals for using ECT(1). Why I say I think it is workable is that if the assumption holds that a packet sender will mark with only one of the ECT codepoints. And the use of ECT(1) and the response function is negotiated, likely in Transport Parameters then we don't usually need to care about which ECT codepoint it was. The only thing that likely should be there is that if a receiver sees a packet being remarked from the assumed ECT(1) to ECT(0) for example then it could report that remarking using the ACK frame, i.e. make it equivalent to a bleaching to Not-ECT to indicate that change and thus likely result in ECN being turned off due to the bleaching occurring. However, I would really prefer if we can get #1372 landed first, then draft a detailed proposal for the change, so that anyone can clearly evaluate the pro and cons of the 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/1439#issuecomment-398344097 ----==_mimepart_5b28d37134de5_616f2b0a1ae6ef5c57177 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho Yes, now we are getting to pr= oposals that appear to be working from my perspective. I think the one bi= t proposal is actually quite interesting, but I think there need to be fe= edback from people who better understand L4S and any other proposals for = using ECT(1).

Why I say I think it is workable is that if the assumption holds that = a packet sender will mark with only one of the ECT codepoints. And the us= e of ECT(1) and the response function is negotiated, likely in Transport = Parameters then we don't usually need to care about which ECT codepoint i= t was. The only thing that likely should be there is that if a receiver s= ees a packet being remarked from the assumed ECT(1) to ECT(0) for example= then it could report that remarking using the ACK frame, i.e. make it eq= uivalent to a bleaching to Not-ECT to indicate that change and thus likel= y result in ECN being turned off due to the bleaching occurring.

However, I would really prefer if we can get #1372 landed first, then draft a detai= led proposal for the change, so that anyone can clearly evaluate the pro = and cons of the change.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b28d37134de5_616f2b0a1ae6ef5c57177-- From nobody Tue Jun 19 04:55:33 2018 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 41253130E5A for ; Tue, 19 Jun 2018 04:55:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 B24LCthrl4Y8 for ; Tue, 19 Jun 2018 04:55:29 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1035F130DDC for ; Tue, 19 Jun 2018 04:55:29 -0700 (PDT) Date: Tue, 19 Jun 2018 04:55:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529409327; bh=WeuwV7jOH8efkxHOkU6yf8EMXUzS/3YW+uIPaloQpxU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=coHLzURtrlda1jyt1ZJ8F2k3kMV3Z8bIAO4MUSYlnvzmyoZ+NgggT94k7DJjjmHWN smBC2btxQkPhl9LxqpsH2BsO6I47FSYRXd1vV52BwPIiCsmRtCeNU4DRvkj2aXAS4B A6laP+iuKYpvt+8f8wmytcQLr4ewKHacfovXKzuI= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28ef2f4c905_1bca3fe1ec04af84119252"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 19 Jun 2018 11:55:32 -0000 ----==_mimepart_5b28ef2f4c905_1bca3fe1ec04af84119252 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 1636ebc Clarifying that idefinite state are not requeired in duplication detection. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/e06a2a0efb1e655ecd1fa4e3a8e182689a50ff54..1636ebc60296c4af708cfd064cf38541eb41f352 ----==_mimepart_5b28ef2f4c905_1bca3fe1ec04af84119252 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • 1636ebc Clarifying that idefinite state are not requeired in duplication detection.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b28ef2f4c905_1bca3fe1ec04af84119252-- From nobody Tue Jun 19 05:12:40 2018 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 C0FA3130E77 for ; Tue, 19 Jun 2018 05:12:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 PECHRf-luEzm for ; Tue, 19 Jun 2018 05:12:36 -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 B2E99130E6A for ; Tue, 19 Jun 2018 05:12:36 -0700 (PDT) Date: Tue, 19 Jun 2018 05:12:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529410356; bh=gVtv6NvkctjSQWiQLpOMUAxUMwJK7dJK79VTkhE/aq0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iKMt/KXZT/g+4JrKfnt0ooBQMbiLMc3PiaSWhJjVv4nQ769EQ/ZVt7hExt/PsCEmh Ekd3WZ2jQLwAF/WVMMIXixMSPPzBnZ8MvAcQAdVXefPhfqAmCOy5w3rqSwCZin1myI EaTIQPN7Xj78ilwc/OvSsfAa2Mf4hRVjuj2SUm2k= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28f3341d99_48193fc1c202ef7c10289e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 19 Jun 2018 12:12:39 -0000 ----==_mimepart_5b28f3341d99_48193fc1c202ef7c10289e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -1427,6 +1432,77 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN Capability Check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for +non-destructive congestion notification by a network node. That is, packets are +marked instead of being discarded by routers and other devices along a network +path. QUIC endpoints perform capability verification on connection establishment +as well as connection migration. ECN can be used unidirectionally, +bidirectionally, or disabled depending on endpoint and path capabilities. + +The capability check makes use of the ACK_ECN frame in {{frame-ack-ecn}}. Each +endpoint individually performs an ECN capability check for its send path. The +check is performed by attempting to set the ECN bits in the IP header to either +ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with I think this proposal is very good, and agree about the IP packet thing and Stream 0 change. The only thing I 100% happy is the explicit mention of ECT(0) being the default. -- 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/1372#discussion_r196397525 ----==_mimepart_5b28f3341d99_48193fc1c202ef7c10289e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1427,6 +1432,77 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN Capability Check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for
+non-destructive congestion notification by a network node.  That is, packets are
+marked instead of being discarded by routers and other devices along a network
+path. QUIC endpoints perform capability verification on connection establishment
+as well as connection migration. ECN can be used unidirectionally,
+bidirectionally, or disabled depending on endpoint and path capabilities.
+
+The capability check makes use of the ACK_ECN frame in {{frame-ack-ecn}}. Each
+endpoint individually performs an ECN capability check for its send path. The
+check is performed by attempting to set the ECN bits in the IP header to either
+ECT(0) or ECT(1) for packets generated by the endpoint, clients starting with

I think this proposal is very good, and agree about the IP packet thing and Stream 0 change. The only thing I 100% happy is the explicit mention of ECT(0) being the default.

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

----==_mimepart_5b28f3341d99_48193fc1c202ef7c10289e-- From nobody Tue Jun 19 05:23:59 2018 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 2027C130E88 for ; Tue, 19 Jun 2018 05:23:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 KLlSLG3qgE_g for ; Tue, 19 Jun 2018 05:23:52 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 992F8130E23 for ; Tue, 19 Jun 2018 05:23:52 -0700 (PDT) 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=6xnKp9olEEcNv0abhjew2pBUAmw=; b=NQk3cmsV81l2G3Ix 1IsKvD86ki8MuX5m7k7wWsWTZjxYTPleoEiqYq7HTDpfhqqTjOSK9tzlGcFq2g9I gh/Z8LYTkVs9ub6QSkvuOPcFXzt/VvCh5yJPOq8U+vYPzyQ4bW7zoIb5lWS+rQB8 EGCp9drS8RJ7vhpb3caoW1zIQIg= Received: by filter0045p1iad2.sendgrid.net with SMTP id filter0045p1iad2-31139-5B28F5D7-D 2018-06-19 12:23:51.35197951 +0000 UTC Received: from github-lowworker14-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id ljcdVhPRTLuRJAW0tlVj0g for ; Tue, 19 Jun 2018 12:23:51.267 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker14-cp1-prd.iad.github.net (Postfix) with ESMTP id 3FCF8E0610 for ; Tue, 19 Jun 2018 05:23:51 -0700 (PDT) Date: Tue, 19 Jun 2018 12:23:51 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28f5d73e23b_6db53fa0dbf7af8843848"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0CxNNHaLlRDDlmA78RZ/877VMhI3CtpnK1nw sLl3sOpe3pSFldAmxwR6LRxdOHCGacdJdS0vgImNOuWFMXOooVLcfVpPypJuzajPGphq1OYBPDC+XY q4a6Ea0NSr9KJXvMeo+RbS2+s4Df9G1Pzzm6cBJ8/sRSI95UnjDfpTspMS+T0dCp2uKprXbKU/zzw6 k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 12:23:58 -0000 ----==_mimepart_5b28f5d73e23b_6db53fa0dbf7af8843848 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > +This capability check thus has verified that one direction of the path between +the peers is free from issues with ECN bleaching and that the application does +not experience problems with access to the ECN field in the IP header. In this +case the marking of the generated packets with ECT continues. + +If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of +packets that was marked as ECT in the sender, or if the comparision of the +counters with the total of acknolwedged packets indicates that not all packets +arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN +Capable. If the endpoint determine the path as currently not ECN capable it +SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + + +### Continuous Verification of ECN {#ecn-continuous-verification} It also requires one to send one ACK_ECN frame for any marked, and one ACK for any Not-ECT marked IP packets. That was not my original intention, but I think works fine. So, yes I think changing the ACK_ECN frame to use this proposal would improve efficiency when it works. When it comes to ACK loss there will be no effect if the lost ACKs only acknowledged ECT(0) pakets. If there was ACKs lost that incremented the CE or ECT(1) counters then it would be in the same situation. The sender can detect the event and record a new comparison point so that it doesn't effect the future bleaching detections. -- 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/1372#discussion_r196400399 ----==_mimepart_5b28f5d73e23b_6db53fa0dbf7af8843848 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +This capability check thus has verified that one direction of the path between
+the peers is free from issues with ECN bleaching and that the application does
+not experience problems with access to the ECN field in the IP header. In this
+case the marking of the generated packets with ECT continues.
+
+If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of
+packets that was marked as ECT in the sender, or if the comparision of the
+counters with the total of acknolwedged packets indicates that not all packets
+arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN
+Capable.  If the endpoint determine the path as currently not ECN capable it
+SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the
+connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+
+### Continuous Verification of ECN {#ecn-continuous-verification}

It also requires one to send one ACK_ECN frame for any marked, and one ACK for any Not-ECT marked IP packets. That was not my original intention, but I think works fine. So, yes I think changing the ACK_ECN frame to use this proposal would improve efficiency when it works.

When it comes to ACK loss there will be no effect if the lost ACKs only acknowledged ECT(0) pakets. If there was ACKs lost that incremented the CE or ECT(1) counters then it would be in the same situation. The sender can detect the event and record a new comparison point so that it doesn't effect the future bleaching detections.

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

----==_mimepart_5b28f5d73e23b_6db53fa0dbf7af8843848-- From nobody Tue Jun 19 05:35:41 2018 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 BD11E130EEC for ; Tue, 19 Jun 2018 05:35:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AwU1nxLQ3FOZ for ; Tue, 19 Jun 2018 05:35:36 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54B8D130ED9 for ; Tue, 19 Jun 2018 05:35:36 -0700 (PDT) Date: Tue, 19 Jun 2018 05:35:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529411735; bh=MbZf8xvmjSTHfDm/Cz9fGY5v9n94wjXUcppiL3GDvpY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cD8pCNbh+EtQjcqIlEUq5fi5py9YO8W2xBkue7P7LmUtIhIgjt/LTQgomeXNQQxqm yzCnlqN3LF7aupBhb/KNfcihmueRVLB0CR4R+Lzf6iOJsR+bOMICeLQwbUiiXG9zts 3+mPuMmOqhVKpuAznxiAUk/pDUPWDXx+53OnYQXY= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28f89752ccd_40772ae8a0a3af58107769"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 19 Jun 2018 12:35:39 -0000 ----==_mimepart_5b28f89752ccd_40772ae8a0a3af58107769 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. 139f1ee Martin Thomson's editorial suggestions. Restructured pseudo code sections. Changed capability check and connection migration text significantly. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/1636ebc60296c4af708cfd064cf38541eb41f352..139f1ee2f508877ad0f8d4cb92170382d4707247 ----==_mimepart_5b28f89752ccd_40772ae8a0a3af58107769 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • 139f1ee Martin Thomson's editorial suggestions. Restructured pseudo code sections. Changed capability check and connection migration text significantly.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b28f89752ccd_40772ae8a0a3af58107769-- From nobody Tue Jun 19 06:02:07 2018 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 E9F011310FD for ; Tue, 19 Jun 2018 06:01:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 bLY2pUUJGYHN for ; Tue, 19 Jun 2018 06:01:53 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A7EE130F1A for ; Tue, 19 Jun 2018 05:54:47 -0700 (PDT) Date: Tue, 19 Jun 2018 05:54:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529412886; bh=6pyZxCJuq56g/YZ0keNDB2fBtZR7yJKKfZEe8jYUqqk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=c8YIZZbiCh63rnTCg+pJJNqHjFtJGriMOQBglSDccJt36TunBv66lCcUr5Dbre7SN IzNrK3s17SnHv0VjAYWwTn++ckCYXJF1q3A8NcLz3R62+0jOZzGydErp4ibyacbb/4 3e4hwpTGrNXcF0MxaeUwJ+P/9gdXZbTXuAQu8IQM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28fd1644d36_65243f952e266f8018112d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 19 Jun 2018 13:02:06 -0000 ----==_mimepart_5b28fd1644d36_65243f952e266f8018112d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ianswett commented on this pull request. > = -QUIC SHOULD delay sending acknowledgements in response to packets, -but MUST NOT excessively delay acknowledgements of packets containing -non-ack frames. Specifically, implementaions MUST attempt to -enforce a maximum ack delay to avoid causing the peer spurious -timeouts. The default maximum ack delay in QUIC is 25ms. +There are cases where one may be able to gain recovery information from +acknowledgements of packets in another packet number space, but they rel= y +on complex assumptions about the peer=E2=80=99s processing and acknowled= gement +algorithms. Even those are unable to quickly recover from cases such as= +losing the client's Initial, but receiving the 0-RTT packets. Below is +an optimization using coalesced packets and implicit acknowledgements. I moved Crypto Handshake Data below under generating acknowledgements. -- = 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/1450#discussion_r196410869= ----==_mimepart_5b28fd1644d36_65243f952e266f8018112d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

>  =

-QUIC SHOULD delay sending acknowledgements in response to packets,
-but MUST NOT excessively delay acknowledgements of packets containing
-non-ack frames.  Specifically, implementaions MUST attempt to
-enforce a maximum ack delay to avoid causing the peer spurious
-timeouts.  The default maximum ack delay in QUIC is 25ms.
+There are cases where one may be able to gain recovery information from
+acknowledgements of packets in another packet number space, but they rel=
y
+on complex assumptions about the peer=E2=80=99s processing and acknowled=
gement
+algorithms.  Even those are unable to quickly recover from cases such as=

+losing the client's Initial, but receiving the 0-RTT packets.  Below=
 is
+an optimization using coalesced packets and implicit acknowledgements.

I moved Crypto Handshake Data below under generating acknowledgements.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or= mute the thread.3D""

= ----==_mimepart_5b28fd1644d36_65243f952e266f8018112d-- From nobody Tue Jun 19 06:02:55 2018 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 3CC3B130EB8 for ; Tue, 19 Jun 2018 06:02:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 GkDJtrfFFCe1 for ; Tue, 19 Jun 2018 06:02:46 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 CF32E130EB5 for ; Tue, 19 Jun 2018 05:57:28 -0700 (PDT) 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=0dxsqEONdHWi/f28w+HjosS/VQ8=; b=YSsxziYYc4y3n2PX fesWTZFYv/LAxPNdj8ysz5GlkyP3iCG1pacriLWd3Xw/jDR/R3alyweA+skXSO1d acgMiDVOGXrNchWyBL8f9CMz0EvenmD7eCMGHOVxURWpHakePh51HWdVHfqYtFpL w02NeNKjKlysDstZBT/uwhnc01Y= Received: by filter0402p1iad2.sendgrid.net with SMTP id filter0402p1iad2-18598-5B28FDB7-23 2018-06-19 12:57:27.900953509 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id JIVOa_4xQHq1QQpnCrUXHg for ; Tue, 19 Jun 2018 12:57:27.791 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id BEAD341006 for ; Tue, 19 Jun 2018 05:57:27 -0700 (PDT) Date: Tue, 19 Jun 2018 12:57:27 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28fdb7bcc52_4f273fcfc5e08f887324b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Q1eiLCkFKD+tRYKC5nrp+yUg8twsya6ciJ8 Kc2yIS/OX7hmvFLxBkhp1CTB9xWfKLhGAex0IC0DG5SlDB7joBXUyuSk22OixJTyonejkm/f9r/eiG OpMJMzxze13NinOF5Moa7foffJmvZA2812/GTqiEQU4Q1FICjIVJFZokNg== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 13:02:54 -0000 ----==_mimepart_5b28fdb7bcc52_4f273fcfc5e08f887324b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ekr pushed 2 commits. 6b36300 Mike's comments 0cfdf67 Merge pull request #34 from ekr/ianswett-mike-comments -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835..0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d ----==_mimepart_5b28fdb7bcc52_4f273fcfc5e08f887324b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr pushed 2 commits.

  • 6b36300 Mike's comments
  • 0cfdf67 Merge pull request #34 from ekr/ianswett-mike-comments

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b28fdb7bcc52_4f273fcfc5e08f887324b-- From nobody Tue Jun 19 06:12:05 2018 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 B740A131144 for ; Tue, 19 Jun 2018 06:11:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TBaJDprSJnJ4 for ; Tue, 19 Jun 2018 06:11:54 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6929A130EF8 for ; Tue, 19 Jun 2018 06:05:20 -0700 (PDT) Date: Tue, 19 Jun 2018 06:05:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529413519; bh=nVpKFweLWLEjh7kL9RFaiE1ZW/VKTWz3qvZK5H3afRg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bk2FxFlw75EeOjdy5MDQ/N/vlA5wJOzgni0BfXu1Q9oQrse8w1Ba/U6l8pNa9n92N rmiwhlYv80J8sBgt2jLvcCInAejXYJzhDP/CgrbmJhcNzPom1RrLTeTuLnum8NBZKX /n9+l9YC8sE+hQovPG1O1u1wOIbc3bpo/hyFBzLw= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b28ff8fc5a0d_511e3ffc95628f784917e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 19 Jun 2018 13:12:02 -0000 ----==_mimepart_5b28ff8fc5a0d_511e3ffc95628f784917e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > An alternative is to include the packet number from the Initial in the Retry packet. That makes Retry very-much more version-specific than it was, but it would allow the client to learn which Initial triggered the Retry, so that it can avoid going backwards. Isn't this always 0? Following retry, a new connection is made, so PN starts over, and we did drop that the random offset at start I suppose. Of course the encrypted PN would vary but not in any secret way, and the initial CID would vary too. -- 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/1451#issuecomment-398391564 ----==_mimepart_5b28ff8fc5a0d_511e3ffc95628f784917e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

An alternative is to include the packet number from the Initial in the= Retry packet. That makes Retry very-much more version-specific than it w= as, but it would allow the client to learn which Initial triggered the Re= try, so that it can avoid going backwards.

Isn't this always 0? Following retry, a new connection is made, so PN = starts over, and we did drop that the random offset at start I suppose. O= f course the encrypted PN would vary but not in any secret way, and the i= nitial CID would vary too.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b28ff8fc5a0d_511e3ffc95628f784917e-- From nobody Tue Jun 19 06:12:26 2018 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 99F7C130F02 for ; Tue, 19 Jun 2018 06:12:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 WBNEHqY7Frak for ; Tue, 19 Jun 2018 06:12:18 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 352BA13101F for ; Tue, 19 Jun 2018 06:09:35 -0700 (PDT) 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=4jCBFCApbnG9+q7YR+ii8Etefso=; b=VEX1Hw3IPdv6PsH5 Wc9KUqHElSzHMd5Mm1YGVWNmr4TczMBf22o5dGFDeA11ZGbOs8ArfmkB8BdtUnQW uH+4ft+KF1E7r4VN6jY4aaE8W9AbguBhGen8OkAjle9M3Mtb/2/9AEMuSkXCllRs wn0PN16Xq63g+9E39SzGc0rBATY= Received: by filter1201p1las1.sendgrid.net with SMTP id filter1201p1las1-23909-5B29008D-37 2018-06-19 13:09:33.913690346 +0000 UTC Received: from github-lowworker-0be93ae.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id Su4krNHAT8CxGEL67zWyBQ for ; Tue, 19 Jun 2018 13:09:33.762 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-0be93ae.cp1-iad.github.net (Postfix) with ESMTP id B94593E087B for ; Tue, 19 Jun 2018 06:09:33 -0700 (PDT) Date: Tue, 19 Jun 2018 13:09:34 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29008db79f8_25d803fcd005d6f802407c3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3/lk3Miuox50MTONpWhdqQEhkpOq9vMDny9p 6qc8dnE27pi0Db6FpOtRPOGYCi745lDz66T383T3H+IFpy/vfcj4/XvhAv0/+cw2W2fQaIvTRKsD16 evRm+xDmX/C3z7oTJNEniWoyTQZrbt/QIU6oa9pB98IboWEF+YIYvmR11Q== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 13:12:23 -0000 ----==_mimepart_5b29008db79f8_25d803fcd005d6f802407c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ekr pushed 2 commits. 4065266 Fix retry and remove optimizations 954c585 Merge pull request #35 from ekr/ianswett-mike2 -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d..954c585e680ca4bf8e2e18af57e5832b716d9fb7 ----==_mimepart_5b29008db79f8_25d803fcd005d6f802407c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr pushed 2 commits.

  • 4065266 Fix retry and remove optimizations
  • 954c585 Merge pull request #35 from ekr/ianswett-mike2

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b29008db79f8_25d803fcd005d6f802407c3-- From nobody Tue Jun 19 06:27:36 2018 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 2B802130F3A for ; Tue, 19 Jun 2018 06:27:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xE3LTU8lcoYW for ; Tue, 19 Jun 2018 06:27:32 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 905D2130EAA for ; Tue, 19 Jun 2018 06:27:32 -0700 (PDT) Date: Tue, 19 Jun 2018 06:27:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529414851; bh=GG4ZwA3rEEM3vnoWnY4d5H55/elxE3yvzHLHI18R5ow=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FgI3QUq8WdM2m8BuJH329F6/BztD9UISESCpwU/JVaWc/f3WzgOmPTznlOAMhcJhV lilipMdU6EgkW4VRrRfz1HFEwCW/QIQCeD9mCug+r76ikiVk8tHAQyJFxic99H4Vfl IbSjggMGa+LxB3BzqA8uoJFndOvDAvkGfS8VyTbw= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2904c3df6b1_3cc22ae016edef6013376b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 19 Jun 2018 13:27:35 -0000 ----==_mimepart_5b2904c3df6b1_3cc22ae016edef6013376b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 3 datagrams is better. It's possibly 3*num_received_bytes makes even more sense, given the goal is to avoid amplification attacks? -- 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/1458#issuecomment-398398426 ----==_mimepart_5b2904c3df6b1_3cc22ae016edef6013376b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

3 datagrams is better.

It's possibly 3*num_received_bytes makes even more sense, given the goal is to avoid amplification attacks?

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

----==_mimepart_5b2904c3df6b1_3cc22ae016edef6013376b-- From nobody Tue Jun 19 06:45:03 2018 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 60F5D130F3A for ; Tue, 19 Jun 2018 06:45:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2yt_hsdvm4QZ for ; Tue, 19 Jun 2018 06:44:59 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61F6A130EAA for ; Tue, 19 Jun 2018 06:44:59 -0700 (PDT) Date: Tue, 19 Jun 2018 06:44:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529415897; bh=tLHQQmktASilGXaVZl9rLX0ccYJLZiCrtyRBJZiyy4c=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Y0WQbAYnR/X5KSn3IKdnW5J1dNpJNQ/Oof6qBlt3Ca7IbyO1ccJ3ZmhFrSrsWQg6w qgixRf8IKUZhi3+Pz05PhaDHfBclvmkzMKpRq4b+8FfXS5won/O7cGu5UX2grIErHv RI0yT0IBikkteC9QssyUC48FnYOWSLjn+dIlp+pA= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] ECN Proposal with only two counters (#1460) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2908d9a1c7c_17962aece03c4f542611cc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 19 Jun 2018 13:45:03 -0000 ----==_mimepart_5b2908d9a1c7c_17962aece03c4f542611cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is an evolution based on #1372 but using @martinthomson proposal of only two counters tracking only the CE and non-default ECT marking. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1460 -- Commit Summary -- * According to text in wiki. Some MD fixes to get right formating. * Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks. * Fixed a typo on anchor creation * According to text in wiki. Some MD fixes to get right formating. * Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks. * Fixed a typo on anchor creation * Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn * Clarified that ACK or ACK_ECN can be used for acknowledgment in handshake. Clarified what the first packets that can be marked as ECT are in a connection. * Added ECN intro paragraph. Various editorial improvements of ECN text. * Fixed bullet list, Added parenthis around section refs. * Fixed indentation and formating * Spelling fixed * Rewrote the ECN check algorithm for connection migration to be robust. * Removed trailing spaces. * Fixed trailing spaces in recovery. * Rewraped text in both recovery and transport. Added a new sub-section on continous verification. * Added textual description of ECN-CE indicating congestion events. * Editorial fixes * Merge pull request #1 from quicwg/ecn * Editing some formulations. Rewraping more text * Fixed trailing spaces and remaining line length issues, I hope. * Reflowing now saved * Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn * Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn * Changed so that additional ECN-CE marks are sent in immediate ACKs to avoid unclarity in regards to CE marks and receovery period. * Fixed lint issues * Adding security consideration around ECN into transport. * Reverting some rewrapping that are not necessary to reduce clutter. * Addressing issues raised by Ian Sweet on 180611. Editorial improvements, new psuedo code function. * Clarifying that both cases are capability checks. Correcting a number of editorial things. * Fixed a too too much * Addressing Martin Thomson's comments. Several editorial changes. The biggest on the ECN block definition. * Added paragraph on dealing with persistent loss of acknowledgement of some sent packets. Removed editorial note that are covered by issue #1402. * Fixing typo in new paragraph. * Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn * Added requirement on ECN marking suppression for packet duplicates. * Clarifying that idefinite state are not requeired in duplication detection. * Martin Thomson's editorial suggestions. Restructured pseudo code sections. Changed capability check and connection migration text significantly. * Rewrote using two counter fields. -- File Changes -- M draft-ietf-quic-recovery.md (112) M draft-ietf-quic-transport.md (203) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1460.patch https://github.com/quicwg/base-drafts/pull/1460.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/1460 ----==_mimepart_5b2908d9a1c7c_17962aece03c4f542611cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is an evolution based on #1372 but using @martinthomson proposal of only two counters tracking only the CE and non-default ECT marking.

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

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

Commit Summary

  • According to text in wiki. Some MD fixes to get right formating.
  • Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks.
  • Fixed a typo on anchor creation
  • According to text in wiki. Some MD fixes to get right formating.
  • Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks.
  • Fixed a typo on anchor creation
  • Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn
  • Clarified that ACK or ACK_ECN can be used for acknowledgment in handshake. Clarified what the first packets that can be marked as ECT are in a connection.
  • Added ECN intro paragraph. Various editorial improvements of ECN text.
  • Fixed bullet list, Added parenthis around section refs.
  • Fixed indentation and formating
  • Spelling fixed
  • Rewrote the ECN check algorithm for connection migration to be robust.
  • Removed trailing spaces.
  • Fixed trailing spaces in recovery.
  • Rewraped text in both recovery and transport. Added a new sub-section on continous verification.
  • Added textual description of ECN-CE indicating congestion events.
  • Editorial fixes
  • Merge pull request #1 from quicwg/ecn
  • Editing some formulations. Rewraping more text
  • Fixed trailing spaces and remaining line length issues, I hope.
  • Reflowing now saved
  • Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • Changed so that additional ECN-CE marks are sent in immediate ACKs to avoid unclarity in regards to CE marks and receovery period.
  • Fixed lint issues
  • Adding security consideration around ECN into transport.
  • Reverting some rewrapping that are not necessary to reduce clutter.
  • Addressing issues raised by Ian Sweet on 180611. Editorial improvements, new psuedo code function.
  • Clarifying that both cases are capability checks. Correcting a number of editorial things.
  • Fixed a too too much
  • Addressing Martin Thomson's comments. Several editorial changes. The biggest on the ECN block definition.
  • Added paragraph on dealing with persistent loss of acknowledgement of some sent packets. Removed editorial note that are covered by issue #1402.
  • Fixing typo in new paragraph.
  • Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn
  • Added requirement on ECN marking suppression for packet duplicates.
  • Clarifying that idefinite state are not requeired in duplication detection.
  • Martin Thomson's editorial suggestions. Restructured pseudo code sections. Changed capability check and connection migration text significantly.
  • Rewrote using two counter fields.

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 mute the thread.

----==_mimepart_5b2908d9a1c7c_17962aece03c4f542611cc-- From nobody Tue Jun 19 06:46:26 2018 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 E8838130F3A for ; Tue, 19 Jun 2018 06:46:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 d-3rtqO_JW5m for ; Tue, 19 Jun 2018 06:46:21 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E721130EAA for ; Tue, 19 Jun 2018 06:46:21 -0700 (PDT) Date: Tue, 19 Jun 2018 06:46:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529415981; bh=S4ZGPSgOEG/XLWvFpW7o4nTNBugZIZs/hxKHa3lrmYE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RxoewEyVNpwe3iz+4TcBDBT2S5GW2uIeYu6hJOfbPv8sVw9UHtudRy32Rc3xBRL0F zo5agAiakLnQuZOCrZtKDZpSaXHCpWRDBVrihH+gDA55B1NbO/S6P4k/HA/hsjcbGa m3ybPXYgNtmI72O3WXK4bKGM9pMRicKLeW5OeHjM= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29092cf279f_4f563f8847890f803290c1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Tue, 19 Jun 2018 13:46:25 -0000 ----==_mimepart_5b29092cf279f_4f563f8847890f803290c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > +This capability check thus has verified that one direction of the path between +the peers is free from issues with ECN bleaching and that the application does +not experience problems with access to the ECN field in the IP header. In this +case the marking of the generated packets with ECT continues. + +If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of +packets that was marked as ECT in the sender, or if the comparision of the +counters with the total of acknolwedged packets indicates that not all packets +arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN +Capable. If the endpoint determine the path as currently not ECN capable it +SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the +connection is migrated then the ECN capability check is rerun as specified in +{{ecn-connection-migration}}. + + +### Continuous Verification of ECN {#ecn-continuous-verification} If one is interested in seeing how this two counter proposal looks, please look at #1460. -- 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/1372#discussion_r196430233 ----==_mimepart_5b29092cf279f_4f563f8847890f803290c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +This capability check thus has verified that one direction of the path between
+the peers is free from issues with ECN bleaching and that the application does
+not experience problems with access to the ECN field in the IP header. In this
+case the marking of the generated packets with ECT continues.
+
+If an ACK frame (not the ACK_ECN frame) is used to acknowledge reception of
+packets that was marked as ECT in the sender, or if the comparision of the
+counters with the total of acknolwedged packets indicates that not all packets
+arrive as ECT(0), ECT(1) or ECN-CE, then the path is determined as not ECN
+Capable.  If the endpoint determine the path as currently not ECN capable it
+SHALL stop marking the packets as ECT, and instead mark them as Not-ECT. If the
+connection is migrated then the ECN capability check is rerun as specified in
+{{ecn-connection-migration}}.
+
+
+### Continuous Verification of ECN {#ecn-continuous-verification}

If one is interested in seeing how this two counter proposal looks, please look at #1460.

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

----==_mimepart_5b29092cf279f_4f563f8847890f803290c1-- From nobody Tue Jun 19 07:09:50 2018 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 B3F23130EFA for ; Tue, 19 Jun 2018 07:09:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 P_X9yETUaEPl for ; Tue, 19 Jun 2018 07:09:46 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F607130EAA for ; Tue, 19 Jun 2018 07:09:46 -0700 (PDT) Date: Tue, 19 Jun 2018 07:09:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529417384; bh=sG3YN/2oXbaxXAB/NeHd9cPolykycTEqsMGS5Of8fmQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=cuBlI0Usq5XdgDhofvvwy43QDyXlsIfDmVfRDiDCiwalSBg1Wd8Ib0eLW8qoGOEOQ eJ8sR3AtxaRnSEaODju+36XGf4GRQYsuyitf60gGGuzhVKH8KS8SKWY8VpgSXzft4S gSfPlXW2he6Iyil7/cDFSoUgdNOP2Oa2rPCPZMyA= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] hq: Are h2 pseudo-header requirements applicable (#1461) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b290ea8b8d03_49ca2ae823ef0f5c211334"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 14:09:49 -0000 ----==_mimepart_5b290ea8b8d03_49ca2ae823ef0f5c211334 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I was reading through [RFC 7540 Section 8.1.2.1](https://tools.ietf.org/html/rfc7540#section-8.1.2.1) and was wondering if these requirements still hold true for HTTP/QUIC. Especially regarding pseudo-headers, from RFC 7540 > All pseudo-header fields MUST appear in the header block before regular header fields. [HTTP/QUIC Section 3.2](https://tools.ietf.org/html/draft-ietf-quic-http-12#section-3.2) states that the message exchange sequence starts with one header block containing RFC 7230 headers. The HEADERS frame description mostly delegates to QPACK, which doesn't seem to mention pseudo-headers. I appreciate a lot of HTTP/2 behaviour is inherited and the tendancy is to document difference. Perhaps we just need a small statement to highlight H2-defined pseudo-headers. PS. the only mention of pseudo-headers is in 3.2.2 in relation to the CONNECT method :) -- 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/1461 ----==_mimepart_5b290ea8b8d03_49ca2ae823ef0f5c211334 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I was reading through RFC 7540 Section 8.1.2.1 and was wondering if these requirements still hold true for HTTP/QUIC. Especially regarding pseudo-headers, from RFC 7540

All pseudo-header fields MUST appear in the header block before regular header fields.

HTTP/QUIC Section 3.2 states that the message exchange sequence starts with one header block containing RFC 7230 headers. The HEADERS frame description mostly delegates to QPACK, which doesn't seem to mention pseudo-headers.

I appreciate a lot of HTTP/2 behaviour is inherited and the tendancy is to document difference. Perhaps we just need a small statement to highlight H2-defined pseudo-headers.

PS. the only mention of pseudo-headers is in 3.2.2 in relation to the CONNECT method :)

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

----==_mimepart_5b290ea8b8d03_49ca2ae823ef0f5c211334-- From nobody Tue Jun 19 07:53:14 2018 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 AE045130E19 for ; Tue, 19 Jun 2018 07:53:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 uta-ht_XGK9B for ; Tue, 19 Jun 2018 07:53:10 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D6FA130DEC for ; Tue, 19 Jun 2018 07:53:10 -0700 (PDT) Date: Tue, 19 Jun 2018 07:53:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529419989; bh=vuZThDIAxA6gyQQmPL6oil2ARORCGXcl2odNTbp5R9c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZVBs/4q6Xu+ZYn3hogtwRS5QlRKGHudWvviCVq94vLRA9zCh9A5B9nR3tGQh6ABeQ akOeKYNj0S5YEN6YxlAup6K30EfHKpAUGUZB4GmB2gQwdPDrJ35GP365IOVI9ZWVUc Ovdw+EqV4K7BQkG9zh2xAGBYOcx2W5eh1j7TI0JY= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2918d595945_4f7f3f993f466f7846192d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Tue, 19 Jun 2018 14:53:13 -0000 ----==_mimepart_5b2918d595945_4f7f3f993f466f7846192d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -### Special Considerations for Packetization Layer PMTU Discovery +#### ICMP PTB During Handshake {#icmp-ptb-during-handshake} + +It is important that any problems are detected quickly during the connection +handshake, because the client may be able to mitigate them by switching to +alternative IP addresses or protocols. Hence, an endpoint SHOULD reduce Path Re-reading PLPMTUD, the draft says explicitly that it is an extension to the classical (ICMP-based) PMTU discovery process and its prescriptions are to be used in cases where ICMP-based PMTU discovery cannot be done. So say that PLPMTUD is a SHOULD is effectively saying that ICMP is a SHOULD (as much as practicable). -- 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/1412#discussion_r196457957 ----==_mimepart_5b2918d595945_4f7f3f993f466f7846192d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-### Special Considerations for Packetization Layer PMTU Discovery
+#### ICMP PTB During Handshake  {#icmp-ptb-during-handshake}
+
+It is important that any problems are detected quickly during the connection
+handshake, because the client may be able to mitigate them by switching to
+alternative IP addresses or protocols.  Hence, an endpoint SHOULD reduce Path

Re-reading PLPMTUD, the draft says explicitly that it is an extension to the classical (ICMP-based) PMTU discovery process and its prescriptions are to be used in cases where ICMP-based PMTU discovery cannot be done. So say that PLPMTUD is a SHOULD is effectively saying that ICMP is a SHOULD (as much as practicable).

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

----==_mimepart_5b2918d595945_4f7f3f993f466f7846192d-- From nobody Tue Jun 19 08:49:04 2018 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 08AEE130F56 for ; Tue, 19 Jun 2018 08:49:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1RebAYg8ieD3 for ; Tue, 19 Jun 2018 08:48:56 -0700 (PDT) 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 8A984130DE8 for ; Tue, 19 Jun 2018 08:48:56 -0700 (PDT) Date: Tue, 19 Jun 2018 08:48:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529423335; bh=1v1Y14WqFN4q5Ehd4jiL9lljsHWmOeW/TAWjq6JoKbE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oFqbrGawG9RokRfqjLcl0jt3628v7V9QzNFHjXYIB1MKfQzB6C+Mqy8Cx4Dvot2x6 QwxEYFDY+QTPN/y9CCv08nUh+ySYvWN50/SxFuQthCRD5vii34g9tOSdlVRRrMYMSC ef6j3x5da1W2N7G9p0zHPvwhI4GHwVTrKxiMpjM4= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2925e75b91f_38d12b0744e4af5412989f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Tue, 19 Jun 2018 15:49:02 -0000 ----==_mimepart_5b2925e75b91f_38d12b0744e4af5412989f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit igorlord commented on this pull request. > -* Any reduction in PMTU due to a report contained in an ICMP packet is -provisional until QUIC's loss detection algorithm determines that the packet is -actually lost. +Any ICMP messages that fail validation MUST be discarded. @janaiyengar is suggesting that not doing (or not being able to do) a validation means it is a ~~SHOULD~~ MUST to treat the signal as not having an on-path proof. It makes sense to me. -- 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/1412#discussion_r196480657 ----==_mimepart_5b2925e75b91f_38d12b0744e4af5412989f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@igorlord commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-* Any reduction in PMTU due to a report contained in an ICMP packet is
-provisional until QUIC's loss detection algorithm determines that the packet is
-actually lost.
+Any ICMP messages that fail validation MUST be discarded.

@janaiyengar is suggesting that not doing (or not being able to do) a validation means it is a SHOULD MUST to treat the signal as not having an on-path proof. It makes sense to me.

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

----==_mimepart_5b2925e75b91f_38d12b0744e4af5412989f-- From nobody Tue Jun 19 11:46:13 2018 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 1DD87130E18 for ; Tue, 19 Jun 2018 11:46:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Is1P9TAH0nuz for ; Tue, 19 Jun 2018 11:46:09 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 3F082130DC2 for ; Tue, 19 Jun 2018 11:46:09 -0700 (PDT) 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=EoSsr41Kunx0wYmegmcLL07eQHM=; b=BmBoCb0Cpcg3RLH2 YZBQ5y7VYyAUa9XuJv9qfLv8yjotoDDgdCjL7olBGj1DFiXm/FM7bes6lFJElUxt mXa1oR/CuNyiLX6kAdk26RsMUKZB7wJrUSkkbqDZQUkoxg/D6Z1y0VyvWiNrKKF6 GY7txvl55rQ/jWL+tUZVyDuivw8= Received: by filter0347p1iad2.sendgrid.net with SMTP id filter0347p1iad2-16914-5B294F6F-E 2018-06-19 18:46:07.228973542 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id kp8DmpfsSLiNOnWTz51dBQ for ; Tue, 19 Jun 2018 18:46:07.175 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 275B43E0C10 for ; Tue, 19 Jun 2018 11:46:07 -0700 (PDT) Date: Tue, 19 Jun 2018 18:46:07 +0000 (UTC) From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b294f6f2513c_c542b0b1af8ef58123740"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ax9aqCbW5ydhyVIpjtQaTXiqLDzES2A363m MmO3I8tDvOxtOZRmZQBeLXyI2D7YMM+P0H8HGuKBYpy4EICBgWtjb0aeJOIRD28O1Ja9R5K27XrcZU 84le20TAfRkpI8kawaIxSVCPrinZ6cmIL5JJh7Q8UU1bOU8V9kwYMwHyjO0Kqev9U1CJCPFI6ph+fz 4= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 18:46:11 -0000 ----==_mimepart_5b294f6f2513c_c542b0b1af8ef58123740 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable As noted already, QUIC inherits TLS's requirements of SNI (the SNI field is= still part of TLS), and QUIC-HTTP inherits HTTP/2's requirements of SNI. @= jmtilli : If you're concerned about encrypted SNI, that conversation ought = to apply to HTTP over TCP as well, so I would take that to the httpbis work= ing group.=C2=A0If you are concerned about other applications using QUIC wi= thout SNI, that'll probably be relevant when considering other applications= mapped on QUIC, which we haven't done yet as a wg. --=20 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/1456#issuecomment-398504617= ----==_mimepart_5b294f6f2513c_c542b0b1af8ef58123740 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As noted already, QUIC inherits TLS's requirements of SNI (the SNI field= is still part of TLS), and QUIC-HTTP inherits HTTP/2's requirements of SNI= . @jmtilli : If you're concerned about en= crypted SNI, that conversation ought to apply to HTTP over TCP as well, so = I would take that to the httpbis working group.=C2=A0If you are concerned a= bout other applications using QUIC without SNI, that'll probably be relevan= t when considering other applications mapped on QUIC, which we haven't done= yet as a wg.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b294f6f2513c_c542b0b1af8ef58123740-- From nobody Tue Jun 19 11:49:32 2018 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 3074E130E13 for ; Tue, 19 Jun 2018 11:49:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 XiNV5WL9r_kM for ; Tue, 19 Jun 2018 11:49:28 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 A6598130DC2 for ; Tue, 19 Jun 2018 11:49:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529434167; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Mx+7Xbe9XvF5RaMC0f0cqGqoWJHUE5Xuwu0AO8NtjCw=; b=ByxsYYGoB5q0Ku9g1TEPkLhHMFeAhG5qNphAqtuoBDRiozvgT0TJCNTCDTsIHPOB+Gqdk5BM ESdLX45iTLqjeQW14kZERh/BGdx2FGA1EDs5Hu8eI3jyNIRqHrfjz0SAcq+Cb2jcXgJymudE XUos6z9pFhbas6uKGdsV2hh8HkM= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b295037.7f591e069e40-smtp-out-n03; Tue, 19 Jun 2018 18:49:27 -0000 (UTC) Date: Tue, 19 Jun 2018 11:49:27 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b295037823c2_131e2b1af5acdc04891ca@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 1d2b00: allow sni encryption Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b29503781eb0_131e2b1af5acdc0489010"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 18:49:31 -0000 ----==_mimepart_5b29503781eb0_131e2b1af5acdc0489010 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 1d2b00255ba6d56bd2e8e9855851c5ab98075ba7 https://github.com/quicwg/base-drafts/commit/1d2b00255ba6d56bd2e8e9855851c5ab98075ba7 Author: Jana Iyengar Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- allow sni encryption **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b29503781eb0_131e2b1af5acdc0489010-- From nobody Tue Jun 19 11:51:17 2018 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 54854130E13 for ; Tue, 19 Jun 2018 11:51:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 O45U2IDuQvT5 for ; Tue, 19 Jun 2018 11:51:14 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 EECE8130DC2 for ; Tue, 19 Jun 2018 11:51:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529434273; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=kjt1TJKcyTi3X3SCrDXq8WEZbXrfWqI7ZacxVwQ8mU4=; b=AAeJwAYrlAWe3yU+u1XFqa0aXmg4bGnpXfbC+9UJDONLQQ8hEjGUD3Ec160LgDEjPaBGPoDX RD1Fe6/qAqvkMZCoH6a2b6jxZpRWRAX6u06lpZ5am3grcJ9FL8PPlzHI/V5VZQS8eQfehjmX jf9OhoCh3JK9RoLVNXs9C9NKL28= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2950a0.7fd483919870-smtp-out-n01; Tue, 19 Jun 2018 18:51:12 -0000 (UTC) Date: Tue, 19 Jun 2018 11:51:11 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b29509fadd15_134b2ab4c4badbfc371b4@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c78556: Revert "allow sni encryption" Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b29509fad99b_134b2ab4c4badbfc37091"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 18:51:16 -0000 ----==_mimepart_5b29509fad99b_134b2ab4c4badbfc37091 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: c785569af10eb5636dbed2d5fe79fac7510b011a https://github.com/quicwg/base-drafts/commit/c785569af10eb5636dbed2d5fe79fac7510b011a Author: Jana Iyengar Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Revert "allow sni encryption" This reverts commit 1d2b00255ba6d56bd2e8e9855851c5ab98075ba7. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b29509fad99b_134b2ab4c4badbfc37091-- From nobody Tue Jun 19 11:53:15 2018 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 6B27D130DED for ; Tue, 19 Jun 2018 11:53:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 17F3SR4Yr3pA for ; Tue, 19 Jun 2018 11:53:11 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 C7B881294D0 for ; Tue, 19 Jun 2018 11:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=VgXmNUEH6MYw0utoHRuWIiSjzNQ=; b=XP7djZLt4u0Zg4XN 5uq8rR84eX2A/c8XIFLMz4LH2iFo2Q3vZ9I0NYdP4v2ILblnktHGHrQmn1xOBjUI WAL7EqQKrfqLqHmlI3+S3dH4tJQf6gIJXCBWXGr3iqCA1GrVqhAVxJxXLdYcqhNp OjhVgxpdryU0Kk7n9dxMOZbjxGc= Received: by filter0864p1las1.sendgrid.net with SMTP id filter0864p1las1-2613-5B295117-C 2018-06-19 18:53:11.354514845 +0000 UTC Received: from github-lowworker18-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id 5YPPxuCdRSOzULeTGjI3zg for ; Tue, 19 Jun 2018 18:53:11.115 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker18-cp1-prd.iad.github.net (Postfix) with ESMTP id 1B00A23C09 for ; Tue, 19 Jun 2018 11:53:11 -0700 (PDT) Date: Tue, 19 Jun 2018 18:53:11 +0000 (UTC) From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Enable SNI encryption (#1462) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29511719794_6be83fa6d9c6ef84920a9"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak104xe1sfVqmKKrd5B4NUvzD5rbQSsqUcifIP u6ojotqpG28GU2gaFcTsrX0Aheyg+5nqDypsjpsD9SbIizNdsCr4uOz42WzN+6PyQXWHhpBjT5Wh9m //bBO0DYXSx3NPUT7V6l1qJQMdTzcUbddbsBpT7MpjBLbDil+22nmDs0EQNBV+8sFVvuhgTEtmxvn2 Q= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 18:53:14 -0000 ----==_mimepart_5b29511719794_6be83fa6d9c6ef84920a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closes #1459. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1462 -- Commit Summary -- * enable sni encryption -- File Changes -- M draft-ietf-quic-http.md (7) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1462.patch https://github.com/quicwg/base-drafts/pull/1462.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/1462 ----==_mimepart_5b29511719794_6be83fa6d9c6ef84920a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closes #1459.

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

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

Commit Summary

  • enable sni encryption

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 mute the thread.

----==_mimepart_5b29511719794_6be83fa6d9c6ef84920a9-- From nobody Tue Jun 19 11:58:54 2018 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 881E0130DC2 for ; Tue, 19 Jun 2018 11:58:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2M1ecXgIUnbM for ; Tue, 19 Jun 2018 11:58:50 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 A47A31294D0 for ; Tue, 19 Jun 2018 11:58:50 -0700 (PDT) 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=yOTKp4OThXwd/PA56f38rS3SB/E=; b=LCAsbnzYgVcDb2bA fv+ID35ezE9q9bdvx3qEkCUSz4vTNTsITjxzHE/fuuXMFSuZaFsi3GUmDCZstKK3 A0RvgOMCxnHxP3zxiF+Dk0sJAjNnsaWM3p9TnN5er+R0r4sf4smdFIOq3h6Vipas pinfFRZ0hbeJvMsZ0F+cjI6biFc= Received: by filter0659p1las1.sendgrid.net with SMTP id filter0659p1las1-12701-5B29526A-C 2018-06-19 18:58:50.321508964 +0000 UTC Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id hzSx5Z8qSsmO0QO4A0_JqA for ; Tue, 19 Jun 2018 18:58:50.212 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id 3214C40D24 for ; Tue, 19 Jun 2018 11:58:50 -0700 (PDT) Date: Tue, 19 Jun 2018 18:58:50 +0000 (UTC) From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29526a30966_d973fda39804f78112073"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0Ja4o0HnjqDAoSLLgF2qFwJwif0YApic7O5i d1v5pDnC5WlRpH53eIz5piI3FNLMkfn/45xQfWwsYboKtUGShoyVWpZJ+gSRrc+pNmldpeVD8UD4Ah c5tfvtthFS46CN1OcZdIXG1R5fB/7WCbOvdWmfgWgqTwSg0j0zxt0qdH0T4/bfJ5lnrzLFVb0WyUGL M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 18:58:53 -0000 ----==_mimepart_5b29526a30966_d973fda39804f78112073 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @erickinnear Yes, though I wouldn't call it a "full migration", because all you have is a server potentially responding to what seems like a migration. Basically [Section 6.8.3](http://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.6.8.3) applies. -- 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/1447#issuecomment-398508475 ----==_mimepart_5b29526a30966_d973fda39804f78112073 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@erickinnear Yes, though I wouldn't call it a "full migration", because all you have is a server potentially responding to what seems like a migration. Basically Section 6.8.3 applies.

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

----==_mimepart_5b29526a30966_d973fda39804f78112073-- From nobody Tue Jun 19 12:15:11 2018 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 6FFD8130F3C for ; Tue, 19 Jun 2018 12:15:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 5RTVZh2rwmWk for ; Tue, 19 Jun 2018 12:14:59 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF6B8130ECB for ; Tue, 19 Jun 2018 12:14:59 -0700 (PDT) Date: Tue, 19 Jun 2018 12:14:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529435697; bh=BternOC3Kz8hmG3A0E3AEqgX4+SQu7UbPj+JXxgY8ns=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hNgBBbgG/ca2jx7Ln7x7Od1F0HTtwCosfM+H9DCU+s/fZ5ez4wT9UM1qKdQvV5RlE UcZuG8lwqTLaHPJXzx8HhTYk4ieX+gvmT0w/XxLCvCxprcENw5GsBkw3fu+3XWp0+B ZAuVwKrep7W2hAlmKYxM5zDX+yChTY3KTacPvYIA= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b295631c64ea_68932adc9c20cf587623d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 19:15:09 -0000 ----==_mimepart_5b295631c64ea_68932adc9c20cf587623d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nice catch. Yes, we definitely meant that for 3 datagrams, and we did not have coalesced packets back then. I suspect 3 datagrams is simpler than 3 * num_bytes_received, so I'm in favor of 3 datagrams. -- 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/1458#issuecomment-398513037 ----==_mimepart_5b295631c64ea_68932adc9c20cf587623d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Nice catch. Yes, we definitely meant that for 3 datagrams, and we did not have coalesced packets back then. I suspect 3 datagrams is simpler than 3 * num_bytes_received, so I'm in favor of 3 datagrams.

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

----==_mimepart_5b295631c64ea_68932adc9c20cf587623d-- From nobody Tue Jun 19 12:17:34 2018 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 9D13D130DED for ; Tue, 19 Jun 2018 12:17:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 M133gEmPSC-W for ; Tue, 19 Jun 2018 12:17:31 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 2AF2A130DCA for ; Tue, 19 Jun 2018 12:17:31 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529435850; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=iN2JJZCrDGXwUcARGbkgvxZW7eFy2SM4nFROlqT2Iw8=; b=AdquRIoXpgTnPtXnwY3z54t/Z2c4XbkeCNYzRpZ+FR+pJD3c8pI0nEXdG1cvw86xERbm4UaF VM0YAygiRcEzQy2jIqIwbwodUmD/dTvlnzAw4pizb/a0l/2FyNSgQyXr/FRgUsrQ/ptoyNbX 9pTtqDzUSKkciABLk0IuhOR3s18= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2950ee.7f4548ed43c0-smtp-out-n02; Tue, 19 Jun 2018 18:52:30 -0000 (UTC) Date: Tue, 19 Jun 2018 11:52:30 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b2950ee62d30_4daf2b20985dbc0c88822@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 3245bf: enable sni encryption Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2950ee628bd_4daf2b20985dbc0c887e0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 19:17:33 -0000 ----==_mimepart_5b2950ee628bd_4daf2b20985dbc0c887e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni Home: https://github.com/quicwg/base-drafts Commit: 3245bf7d8f645dcdfdda6655760806e7b3d2415e https://github.com/quicwg/base-drafts/commit/3245bf7d8f645dcdfdda6655760806e7b3d2415e Author: Jana Iyengar Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- enable sni encryption **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2950ee628bd_4daf2b20985dbc0c887e0-- From nobody Tue Jun 19 12:22:49 2018 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 B2403130F03 for ; Tue, 19 Jun 2018 12:22:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 RZO2NT7_ksHW for ; Tue, 19 Jun 2018 12:22:37 -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 34F18130F58 for ; Tue, 19 Jun 2018 12:22:36 -0700 (PDT) Date: Tue, 19 Jun 2018 12:22:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529436155; bh=lBIqn5iYQ2ts80ZTthB9xuLO987YssyHS0E3urWCrNk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zbHsPE6O1/p5MnQVhkitlORgql2JsOx7+hew5ds1DtnpXXy4Qf4Mnb1v3uSlgyOYv 4ZNsaraV/zJVpwMUt7SqumE3z4a6ccxcPdMCdg16qR2Lx7NfOZAXSg+t4ysPTg4bjF 64izlVJaX2AFi+MdhajnpE4c6A5852RAXtQuxDqk= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Coalesced packets and handshake packet limiting (#1458) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2957fb65cf4_3ce42b20b82a2f5c8187c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 19:22:47 -0000 ----==_mimepart_5b2957fb65cf4_3ce42b20b82a2f5c8187c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 for 3 datagrams On Tue, Jun 19, 2018 at 12:14 PM, janaiyengar wrote: > Nice catch. Yes, we definitely meant that for 3 datagrams, and we did n= ot > have coalesced packets back then. I suspect 3 datagrams is simpler than= 3 * > num_bytes_received, so I'm in favor of 3 datagrams. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = 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/1458#issuecomment-398515158= ----==_mimepart_5b2957fb65cf4_3ce42b20b82a2f5c8187c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 for 3 datagrams

On Tue, Jun 19, 2018 at 12:14 PM, janaiyengar <notifications@github.co= m>
wrote:

> Nice catch. Yes, we definitely meant that for 3 datagrams, and we di= d not
> have coalesced packets back then. I suspect 3 datagrams is simpler t= han 3 *
> num_bytes_received, so I'm in favor of 3 datagrams.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1458#issuecomment-3= 98513037>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1obQt9qXdNz= YnPTBmkJ1Gb_Xcn0PYks5t-U2vgaJpZM4Ush7e>
> .
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2957fb65cf4_3ce42b20b82a2f5c8187c-- From nobody Tue Jun 19 12:43:31 2018 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 18497130E9A for ; Tue, 19 Jun 2018 12:43:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 OzPS2aqIUEpF for ; Tue, 19 Jun 2018 12:43:27 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 373F3130E6E for ; Tue, 19 Jun 2018 12:43:27 -0700 (PDT) Date: Tue, 19 Jun 2018 12:43:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529437406; bh=3VyT+q1dknqQjyYxDMRIt5lQoIihGLp1gna2e0oQ5lI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ey6/xsnyK4X7GU4O5/iA+bjCkg4j430kt5SFWDbGeD4e3cBWHRG5JFGhDjSTmuIrU NsoFQxYdqZFMnKFxf6iOYwwhgPKwwb1LO4wLEA4Rdq960HGnOKTQoq4E7DK+ezsr0d IK2cKUnEyfr838dZMGAWWLnQ5AZHvbXpONo7kVuQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] hq: Are h2 pseudo-header requirements applicable (#1461) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b295cde4dc0f_68562afda245ef502253a8"; 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.26 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: Tue, 19 Jun 2018 19:43:29 -0000 ----==_mimepart_5b295cde4dc0f_68562afda245ef502253a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's intended to. I think this falls in the general category of "Things the draft assumes readers already know from HTTP/2," a category I've been trying to eliminate. I'd rather either explicitly reference the RFC7540 text where it applies (e.g. priorities) or restate it locally. @ianswett said some of his team had feedback in this vein as well; can we get issues filed for those, or just a laundry list sent my way? -- 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/1461#issuecomment-398521271 ----==_mimepart_5b295cde4dc0f_68562afda245ef502253a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's intended to. I think this falls in the general category of "Thin= gs the draft assumes readers already know from HTTP/2," a category I've b= een trying to eliminate. I'd rather either explicitly reference the RFC7= 540 text where it applies (e.g. priorities) or restate it locally.

@ianswett said some of his team = had feedback in this vein as well; can we get issues filed for those, or = just a laundry list sent my way?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b295cde4dc0f_68562afda245ef502253a8-- From nobody Tue Jun 19 12:46:30 2018 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 3CAE0130EC1 for ; Tue, 19 Jun 2018 12:46:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hIC5jYHrqKVh for ; Tue, 19 Jun 2018 12:46:25 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 644C3130E6E for ; Tue, 19 Jun 2018 12:46:25 -0700 (PDT) Date: Tue, 19 Jun 2018 12:46:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529437584; bh=B3NY/jJ3lBi/EvAt8E+qzjYPGZIm4B7DO19tHqkkSEU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OQB8EJotnQA8/0WLOlQfN20wvkGfq9JltkFSPSZqHdSK8R0L1aFLitbFVzPvKSNu6 +0jTXPe2wId5u1QDGvMijzM3W6Qnds6HWYCqOZgXZ573701HSz+k3Bub3emNei8c1x pbVU9xczE8B4YJfpv+W59TEAYz2ssBi1W1loEMrs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b295d907dc37_366f3ff9a8572f88343954"; 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.26 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: Tue, 19 Jun 2018 19:46:28 -0000 ----==_mimepart_5b295d907dc37_366f3ff9a8572f88343954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm fine with that change. It seems a little bit of a stretch to read into that language that an alternative to SNI is acceptable, though. I'm almost inclined to add "...MUST indicate the target domain name when negotiating TLS using SNI or another mechanism." just to highlight that SNI isn't the only compliant option. -- 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/1459#issuecomment-398522087 ----==_mimepart_5b295d907dc37_366f3ff9a8572f88343954 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm fine with that change. It seems a little bit of a stretch to read= into that language that an alternative to SNI is acceptable, though. I'= m almost inclined to add "...MUST indicate the target domain name when ne= gotiating TLS using SNI or another mechanism." just to highlight that SNI= isn't the only compliant option.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b295d907dc37_366f3ff9a8572f88343954-- From nobody Tue Jun 19 12:55:38 2018 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 3D704130EC1 for ; Tue, 19 Jun 2018 12:55:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 azWP0ibGpH1L for ; Tue, 19 Jun 2018 12:55:34 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 8CBA8130E6E for ; Tue, 19 Jun 2018 12:55:34 -0700 (PDT) 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=dT3qGZKP0nv4JaAy1MCQbv5oPaE=; b=ttI5TIE5315jvB7F WTM12nkp60uQAxIylrVGFT4zbkIWdGJvMVv8iqLucd9DSyXpmY0DttXx7yiJsxlz Z6/B9y4OZfJyygxjxhw5dxPtuAngDXMvVj5sRUOXGWRR9BMuJtnJ4F1HKSEJP4yo 26TMMCRTYG5DvG13zByCl0PX9uc= Received: by filter1086p1las1.sendgrid.net with SMTP id filter1086p1las1-26840-5B295FB5-22 2018-06-19 19:55:33.856377712 +0000 UTC Received: from github-lowworker-cbd19a4.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id UJ2O8MD8Svm0-GPfDtwM3w for ; Tue, 19 Jun 2018 19:55:33.669 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cbd19a4.cp1-iad.github.net (Postfix) with ESMTP id A15E65809CC for ; Tue, 19 Jun 2018 12:55:33 -0700 (PDT) Date: Tue, 19 Jun 2018 19:55:34 +0000 (UTC) From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] hq: Are h2 pseudo-header requirements applicable (#1461) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b295fb5a0408_279773fcd8cc46f7811309b"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1QKtts4nFNG09t50RASrkkVyAWJVYjzJ7XEt PjxshfVmOD4v8vcmnztgPPs2lNnHzxibDaHU89yJ65Ts4QZ7qacJusNq4WKvGkOSgwbiDgLBaLtdmE eXzRFWo6nWSLQDQI7Oivd7lWghg0thLKU2rgKhufwlQ/MMHexlRWww1yEPivLopKMd69+3uGLwYfcb 0= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 19:55:37 -0000 ----==_mimepart_5b295fb5a0408_279773fcd8cc46f7811309b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Speaking to our implementation experience, we happened upon the right answer by relying on existing HTTP/2 knowledge and code. I think it would help to do what you've suggested. -- 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/1461#issuecomment-398524716 ----==_mimepart_5b295fb5a0408_279773fcd8cc46f7811309b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Speaking to our implementation experience, we happened upon the right answer by relying on existing HTTP/2 knowledge and code. I think it would help to do what you've suggested.

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

----==_mimepart_5b295fb5a0408_279773fcd8cc46f7811309b-- From nobody Tue Jun 19 13:54:43 2018 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 A727C130F29 for ; Tue, 19 Jun 2018 13:54:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ypmR1aLDszzs for ; Tue, 19 Jun 2018 13:54:40 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32C3130E3E for ; Tue, 19 Jun 2018 13:54:39 -0700 (PDT) Date: Tue, 19 Jun 2018 13:54:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529441678; bh=1FiVPiPRtyJ0INKvHj59N8ulYZzWIM79XArlirPLTD8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nMekg0AaoHjdkNtBZsB3JKGBqwXfUdxulOcU4xjrtj8T2MGeotnqoQiqUj04C12+f eH8zSRgHtSqnb3gKNpehpdzmzGxPAs/1xO9tID018fRu2ifXsb3L/DOF38KPUH5fz+ 6rnfe6r7KgBi8bX9uGZG1gXakgNXN6Z3U1BNBh7I= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow SNI encryption (#1462) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b296d8ec360d_796b2af0f8c5ef546986c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 20:54:42 -0000 ----==_mimepart_5b296d8ec360d_796b2af0f8c5ef546986c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @janaiyengar: The commit message seems wrong here. -- 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/1462#issuecomment-398542279 ----==_mimepart_5b296d8ec360d_796b2af0f8c5ef546986c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar: The commit message seems wrong here.

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

----==_mimepart_5b296d8ec360d_796b2af0f8c5ef546986c-- From nobody Tue Jun 19 15:22:34 2018 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 79A72130F96 for ; Tue, 19 Jun 2018 15:22:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Apcw4Lv14RZP for ; Tue, 19 Jun 2018 15:22:30 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 21038130F26 for ; Tue, 19 Jun 2018 15:22:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529446949; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=jhCptvq3FVlFEkc8kObj/tWbYJv/G1NhYBFNoHmuXdU=; b=VwcyB+NiYOtpZb8KymQUeBRFOX3jwujysmyrIC7KLvqHffZhenRCd0ZRNiOOBv9siffRWW/e kdJ+GWwdm1AAIReT9x4So58amx9JthLOtzcMRSfqvrkZQp6y1LIUBo9EKbtMlHaA0CHWcIYS 3lXWtqO5yJjYp9mA+Hoep9wHMEw= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b298225.7fc593d3b900-smtp-out-n01; Tue, 19 Jun 2018 22:22:29 -0000 (UTC) Date: Tue, 19 Jun 2018 15:22:28 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b2982242ba59_7082b2351bafc1c88724@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 56990a: Expand CID ratchet text Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2982242b54b_7082b2351bafc1c886f0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 22:22:32 -0000 ----==_mimepart_5b2982242b54b_7082b2351bafc1c886f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 56990a07efaa84b592838961544e3211c7d926e5 https://github.com/quicwg/base-drafts/commit/56990a07efaa84b592838961544e3211c7d926e5 Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Expand CID ratchet text Commit: 4d59b1d910884caa08efad0737fdf61bc254360e https://github.com/quicwg/base-drafts/commit/4d59b1d910884caa08efad0737fdf61bc254360e Author: Martin Thomson Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1453 from quicwg/transport/cids_not_ordered Expand CID ratchet text Compare: https://github.com/quicwg/base-drafts/compare/c785569af10e...4d59b1d91088 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2982242b54b_7082b2351bafc1c886f0-- From nobody Tue Jun 19 15:22:42 2018 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 A2416130FA3 for ; Tue, 19 Jun 2018 15:22:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.9 X-Spam-Level: X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 rtG_GjtCF7cv for ; Tue, 19 Jun 2018 15:22:32 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 59D9D130F7E for ; Tue, 19 Jun 2018 15:22:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529446951; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=w1h/3/c+UBMcAOnQ9GtJySw0+l1MM17LDqqH8izgFiA=; b=tTo2WGAUADKVYQbDz2lbI5LBPbml8Z2iBtLlb6Gayfff5luKB4XoN1/V90t1QWmq2VS3SPOc Y++9BYZkN9MAtlSOVoBtHJck8j2vMsaR9CRV1ByMrT4wvullSytJ5WgdmOc7mYhZt0OD+qlE EuGHuRRpbHMXAT72uLgOHU97NvQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b298227.7fe3e48569f0-smtp-out-n03; Tue, 19 Jun 2018 22:22:31 -0000 (UTC) Date: Tue, 19 Jun 2018 15:22:31 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b2982276dba0_34092abe1320fc0011423@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2982276d7e4_34092abe1320fc001137c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 22:22:34 -0000 ----==_mimepart_5b2982276d7e4_34092abe1320fc001137c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/cids_not_ordered Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2982276d7e4_34092abe1320fc001137c-- From nobody Tue Jun 19 15:22:49 2018 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 76C5A130F7E for ; Tue, 19 Jun 2018 15:22:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 dx00c7kmylSI for ; Tue, 19 Jun 2018 15:22:32 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9C61130F26 for ; Tue, 19 Jun 2018 15:22:32 -0700 (PDT) Date: Tue, 19 Jun 2018 15:22:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529446951; bh=Clyl8rlqu3wOPnYeY4MrZlrFHNhOkgNrMMrTNNFVfyw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yql3kHouSoycekwogNIGIc4gWKWCKezHd2CBv+yOKJubKrKu7NvWAAUzfAuvPNfbr 4VGIyHK1FkR5osz0R4zQyHBpQbLp75+nZcFShlxZaEzeyMb2HLgCpN5j0KNd3s+Vkd Yr0BchaYx9KPRiu0CwQsXeuhddY2mtC9QNz+98rs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Expand CID ratchet text (#1453) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b298227a72ed_3e842afce2b4ef6017523d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 22:22:35 -0000 ----==_mimepart_5b298227a72ed_3e842afce2b4ef6017523d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1453. -- 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/1453#event-1689824166 ----==_mimepart_5b298227a72ed_3e842afce2b4ef6017523d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1453.

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

----==_mimepart_5b298227a72ed_3e842afce2b4ef6017523d-- From nobody Tue Jun 19 15:22:54 2018 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 65766130FB5 for ; Tue, 19 Jun 2018 15:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 kVzTMEAlU2uQ for ; Tue, 19 Jun 2018 15:22:33 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF5E6130F96 for ; Tue, 19 Jun 2018 15:22:32 -0700 (PDT) Date: Tue, 19 Jun 2018 15:22:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529446951; bh=osXZF8brtsSfk5pZ+YmSwnvaPKWqD2CiWnE/k+qa8lo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d5e7cMzeCbewUAfxSUqy+HSJVqrsQqA6/b5xomws9GQNPL8EMnFGGeXgjCxaMZkeY llJSLWeJN0q0/TddBJbbaj6MdbA52ElRErE6Y44Kk47IkdzlkdBetvOhGsZUghWKUC NQ6TPHLbdxKV/VLO9oYbA8/8baxbQ3CxM5hpY12g= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Exhausting a supply of connection IDs (#1276) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b298227ad908_22283f872a95ef841589c2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 22:22:37 -0000 ----==_mimepart_5b298227ad908_22283f872a95ef841589c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1276 via #1453. -- 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/1276#event-1689824170 ----==_mimepart_5b298227ad908_22283f872a95ef841589c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1276 via #1453.

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

----==_mimepart_5b298227ad908_22283f872a95ef841589c2-- From nobody Tue Jun 19 15:25:31 2018 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 E2E5E130F83 for ; Tue, 19 Jun 2018 15:25:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 iNCivaUxgEvx for ; Tue, 19 Jun 2018 15:25:27 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 64419130F78 for ; Tue, 19 Jun 2018 15:25:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529447126; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=sOJyL053ILzlRnz8PeRPO7WAuOT6creHNed6WcjkxMw=; b=uttW81guBfPGISxgwTtKbg8LYGbi5bri8xyjeuapud5abWjoplQkbDFfn5SyrDqgqofvfKpe Gngy7zzUIkoiiN5fe/u05ZYRmp3y6JCkuXbFO0eFM2T5MZFd4dDE3Lj5txGFAZ/lf5ES4o7J 4uFpph6oe62zq2HqKZg3QaTGMkk= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2982d6.7f786cfdf1b0-smtp-out-n02; Tue, 19 Jun 2018 22:25:26 -0000 (UTC) Date: Tue, 19 Jun 2018 15:25:25 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b2982d58388c_58272ac069f4fc00745fc@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 881169: Don't forbid sni encryption Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2982d5834dd_58272ac069f4fc0074445"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 22:25:30 -0000 ----==_mimepart_5b2982d5834dd_58272ac069f4fc0074445 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni Home: https://github.com/quicwg/base-drafts Commit: 8811699c929da32b89bb4a058684ab7fffc5ea61 https://github.com/quicwg/base-drafts/commit/8811699c929da32b89bb4a058684ab7fffc5ea61 Author: Jana Iyengar Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Don't forbid sni encryption **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2982d5834dd_58272ac069f4fc0074445-- From nobody Tue Jun 19 15:25:44 2018 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 B54E8130FA3 for ; Tue, 19 Jun 2018 15:25:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 MtqUY3KoGL4F for ; Tue, 19 Jun 2018 15:25:36 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 484A6130F78 for ; Tue, 19 Jun 2018 15:25:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529447136; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nWIlfXP1iINmOtsfw00dKNPwGr1pVRY3vuL0oLswSRw=; b=kNAN3JDgRq8NvwBAA80OUblzuraanILbyJw/j3bZUr1mUGxRE9uguuvVUDrivV4y9wGAm23X 4U9zoUnfO/2n/ghyrLyusdCu3lyVORqI63/I+pQORSqqBejvf0bmmCw83o/YNeYLKxSZQAOM OoS9T5vI3voiWbGbQoe/QrByqeg= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b2982df.7faa7d5ef0f0-smtp-out-n03; Tue, 19 Jun 2018 22:25:35 -0000 (UTC) Date: Tue, 19 Jun 2018 15:25:35 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b2982df69dd0_741d2ac821091c08311d8@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 881169: Don't forbid sni encryption Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2982df697da_741d2ac821091c083105c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 22:25:42 -0000 ----==_mimepart_5b2982df697da_741d2ac821091c083105c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 8811699c929da32b89bb4a058684ab7fffc5ea61 https://github.com/quicwg/base-drafts/commit/8811699c929da32b89bb4a058684ab7fffc5ea61 Author: Jana Iyengar Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Don't forbid sni encryption Commit: 3dd52db0ee472a7ee2085604688c05aaab17c702 https://github.com/quicwg/base-drafts/commit/3dd52db0ee472a7ee2085604688c05aaab17c702 Author: Martin Thomson Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Merge pull request #1462 from quicwg/sni Allow SNI encryption Compare: https://github.com/quicwg/base-drafts/compare/4d59b1d91088...3dd52db0ee47 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2982df697da_741d2ac821091c083105c-- From nobody Tue Jun 19 15:25:52 2018 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 54A8B130F78 for ; Tue, 19 Jun 2018 15:25:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 NgcPsSxH3LLG for ; Tue, 19 Jun 2018 15:25:38 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87235130F7E for ; Tue, 19 Jun 2018 15:25:38 -0700 (PDT) Date: Tue, 19 Jun 2018 15:25:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529447137; bh=wHs8jC0j0Xgsivj+ZZWDOErVyP8eBogrrkIJ8LpP7o8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tksveNLHvw710lG8u0G7YIg01RXZz0O3M1oJ290gU1G3Lgsf+Bf9eoqJVoBXw0yAv IaJLVsnKJUr9KApYoOVrvWRNVxFCYiGD3S6IU4KXiNUjkYYdynZhJs3Gdj4GdcHs6Q rOiEhKXBKn2RHZJQrNBbW+4KKYUto+yaFU3QCWA0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2982e1ce9af_c152b149bfc6f54117344"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 22:25:43 -0000 ----==_mimepart_5b2982e1ce9af_c152b149bfc6f54117344 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1459 via #1462. -- 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/1459#event-1689828850 ----==_mimepart_5b2982e1ce9af_c152b149bfc6f54117344 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1459 via #1462.

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

----==_mimepart_5b2982e1ce9af_c152b149bfc6f54117344-- From nobody Tue Jun 19 15:25:58 2018 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 44899130FB1 for ; Tue, 19 Jun 2018 15:25:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sWjOaBw1TH-a for ; Tue, 19 Jun 2018 15:25:41 -0700 (PDT) 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 7E59A130F26 for ; Tue, 19 Jun 2018 15:25:38 -0700 (PDT) Date: Tue, 19 Jun 2018 15:25:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529447137; bh=sWW09munt4M/XAGEyQ02ReNej3fOZfRQqfd1Dta984Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k2/QiADZfQSsn97V07W6Al9O5nkCNoFP3Zy8hOj4KvONCisAAQN1Hq+hKLCsus/I0 UuB8n/DpKaFUqcOBSN3RVnVjj6JMDOmmBapX3n6BoZtRNeK4fiswqXScOdGVajJPIE StHfEPfLHOeq1VpPo2vmdu0EHlIunyQ/49p4O+N0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow SNI encryption (#1462) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2982e1d214f_222c3f872a95ef841829d4"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 19 Jun 2018 22:25:46 -0000 ----==_mimepart_5b2982e1d214f_222c3f872a95ef841829d4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1462. -- 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/1462#event-1689828849 ----==_mimepart_5b2982e1d214f_222c3f872a95ef841829d4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1462.

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

----==_mimepart_5b2982e1d214f_222c3f872a95ef841829d4-- From nobody Tue Jun 19 15:26:03 2018 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 D3A16130FC4 for ; Tue, 19 Jun 2018 15:25:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.9 X-Spam-Level: X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 y7uy7sM4ple0 for ; Tue, 19 Jun 2018 15:25:43 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 0CC9B130F96 for ; Tue, 19 Jun 2018 15:25:40 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529447140; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9rhQGOeWid+nvZmhGIx1sFLFd5my05O5/h/KlbjcPEo=; b=ZwbQwokJMGJl6KfBwvfLKpEgfpMRHOyES8ShNimGa4r+qMVexzl0/I5mmFQquJl9Drr8XwdW 0MjZXgSr2XtIGHlf5D+0STQ4sqVLCUQ/4JhkJJdndW7mVgP2bWBAMfvQWuNSg6iF1V89pV+m +ooZlywFTLW5OmfiA7zcIaVxj1c= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b2982e3.7f9af5cd46c0-smtp-out-n02; Tue, 19 Jun 2018 22:25:39 -0000 (UTC) Date: Tue, 19 Jun 2018 15:25:38 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b2982e28962d_4072b1989cabc141432@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2982e2892da_4072b1989cabc14142b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 19 Jun 2018 22:25:46 -0000 ----==_mimepart_5b2982e2892da_4072b1989cabc14142b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2982e2892da_4072b1989cabc14142b-- From nobody Tue Jun 19 16:08:02 2018 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 A480C130E40 for ; Tue, 19 Jun 2018 16:07:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4mDnESavuL_X for ; Tue, 19 Jun 2018 16:07:51 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BDCD1311DE for ; Tue, 19 Jun 2018 16:07:51 -0700 (PDT) Date: Tue, 19 Jun 2018 16:07:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529449670; bh=iiiJ7zbtvFe78w7PT4KkZl/+ppc7OVm3+rZwVEt7NvU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eTb0FppFPx2feSxGSFe+PxWNq5AGa6VHym9r5mzuh+1iAOqnrJq7y+aaiZ3QUs3QA kmKzKTMEg4jlsykgvWvfXn+onAEh1LI2PdVqOJxRptnuBvYyE13NodZyHEySUi8TdV T8SCkZ0wA2ja7JRXd+br8KdUcyC84bibS82LuvAc= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b298cc622f88_50a63fdf807d8f8017881f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:07:59 -0000 ----==_mimepart_5b298cc622f88_50a63fdf807d8f8017881f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. I'm not sure where to point this out, but shouldn't we have a restriction saying that a QUIC packet can only have *one* CRYPTO_HS frame? -- 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/1450#pullrequestreview-130191828 ----==_mimepart_5b298cc622f88_50a63fdf807d8f8017881f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

I'm not sure where to point this out, but shouldn't we have a restriction saying that a QUIC packet can only have one CRYPTO_HS frame?

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

----==_mimepart_5b298cc622f88_50a63fdf807d8f8017881f-- From nobody Tue Jun 19 16:13:13 2018 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 8F667130FF5 for ; Tue, 19 Jun 2018 16:13:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gUx9vlBGVlLR for ; Tue, 19 Jun 2018 16:13:08 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEA30130FF7 for ; Tue, 19 Jun 2018 16:13:08 -0700 (PDT) Date: Tue, 19 Jun 2018 16:13:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529449988; bh=ijNzjTqPUGBuL5hEkO0x9Siq1pWvNyp2Xx99TyfKbe4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sXe1hWuUFkrw5MEnt7Cbjf0KQWjwnSvWMMAlJkwj5clI3vOu7wG1HibaBdd7Kd8jR olg4Iy6jZmbBBjs9iLV+hw+RdyP9iG4jtKZlSnMJJXtzUouEVuhx3eNPDocagzkoPA XvuV2mznmbMFZNO1N5G2Ag6s+mQUOUSxqFxhqtwk= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b298e041c6b_650c2afffe556f5870559"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:13:13 -0000 ----==_mimepart_5b298e041c6b_650c2afffe556f5870559 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. I think that, up to this point, we were relying on the fact that typical UDP stacks give us a clear per-packet boundary and this changes that. Do we now see implementations receiving a UDP packet and assuming it might contain more than one QUIC packet? It seems like the only way to implement this is to start parsing the QUIC packet and then, if there are leftover bytes, interpret that as another QUIC packet. It's not too hard but it seems like a significant 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/pull/1450#pullrequestreview-130192833 ----==_mimepart_5b298e041c6b_650c2afffe556f5870559 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

I think that, up to this point, we were relying on the fact that typical UDP stacks give us a clear per-packet boundary and this changes that. Do we now see implementations receiving a UDP packet and assuming it might contain more than one QUIC packet?
It seems like the only way to implement this is to start parsing the QUIC packet and then, if there are leftover bytes, interpret that as another QUIC packet.
It's not too hard but it seems like a significant change.

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

----==_mimepart_5b298e041c6b_650c2afffe556f5870559-- From nobody Tue Jun 19 16:28:42 2018 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 B74E8130E4B for ; Tue, 19 Jun 2018 16:28:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 kkSCHiMaN7-f for ; Tue, 19 Jun 2018 16:28:39 -0700 (PDT) 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 E7183129385 for ; Tue, 19 Jun 2018 16:28:38 -0700 (PDT) Date: Tue, 19 Jun 2018 16:28:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529450918; bh=NwSb89UxxxJDwo6R8R1UHrs6qsDw5iwnb9gAbuuSjpc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=J6EAhYo3UMaF5rPBML90EtYGf/ZTvLNWFGEfunyUai4XsfU7J8bi8+TQWJyBiUFRh MYP6pj4ztI1O+OItl+UTW/7Qy4iW2tp2MWUUX2acDVmi9YpT32qgbLjcNCMsWf85gt ZQTQE2rZSPCoL6cX1oKCYXYZkiH8oSQZy20EPEE4= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2991a61ba0a_53112b18ca66af541592c9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 23:28:41 -0000 ----==_mimepart_5b2991a61ba0a_53112b18ca66af541592c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. Why? That's not, for instance, how Minq works. -- 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/1450#discussion_r196609514 ----==_mimepart_5b2991a61ba0a_53112b18ca66af541592c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

Why? That's not, for instance, how Minq works.

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

----==_mimepart_5b2991a61ba0a_53112b18ca66af541592c9-- From nobody Tue Jun 19 16:29:42 2018 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 DB12F130E4B for ; Tue, 19 Jun 2018 16:29:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 NTJ76_at8MxL for ; Tue, 19 Jun 2018 16:29:39 -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 6BA9E129385 for ; Tue, 19 Jun 2018 16:29:39 -0700 (PDT) Date: Tue, 19 Jun 2018 16:29:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529450978; bh=LvOkAUmQcr+SxsPc4+FkLnO+fpB1bqrEmy4grtSY2rk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0BFBE3vhHopurv9xSY3mcbqQP9Kr8Zyo/T/ZIzfqlnEWvhUGVJiEn6/K2qI40JNGD 7v86lqyNfjn8QLbgShmr7Y3eNke6GkMyGHUUk69aPDDDm8b78ngrvxLbK/O+lCOrBK mpkJMc3PYOa71PwZNabndAMSn2SQOtdFtgWEgA7Y= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2991e2b2cdd_5f6c3fcd050f8f7c69894"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:29:41 -0000 ----==_mimepart_5b2991e2b2cdd_5f6c3fcd050f8f7c69894 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > -The HKDF-Expand function used by QHKDF-Expand uses the PRF hash function -negotiated by TLS, except for handshake secrets and keys derived from them (see -{{handshake-secrets}}). +If TLS experiences an error, it MUST generate an appropriate alert +as defined in {{TLS13}}; Section 6) and then provide it to QUIC, +which sends the alert in a CRYPTO_CLOSE frame. All such alerts are +"fatal". "fatal" is under quotes but its meaning isn't explained. -- 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/1450#pullrequestreview-130196028 ----==_mimepart_5b2991e2b2cdd_5f6c3fcd050f8f7c69894 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

>  
-The HKDF-Expand function used by QHKDF-Expand uses the PRF hash function
-negotiated by TLS, except for handshake secrets and keys derived from them (see
-{{handshake-secrets}}).
+If TLS experiences an error, it MUST generate an appropriate alert
+as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
+which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
+"fatal".

"fatal" is under quotes but its meaning isn't explained.

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

----==_mimepart_5b2991e2b2cdd_5f6c3fcd050f8f7c69894-- From nobody Tue Jun 19 16:30:00 2018 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 12422129385 for ; Tue, 19 Jun 2018 16:29:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 27Ws9LOvrJXP for ; Tue, 19 Jun 2018 16:29:53 -0700 (PDT) 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 A96A0130E4B for ; Tue, 19 Jun 2018 16:29:53 -0700 (PDT) Date: Tue, 19 Jun 2018 16:29:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529450993; bh=XftKz0k5j/DMhvNTsVbYyt1Ubet7/yA38jtedX12KIs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d+8kRj61ZxBZuvn2n7XAgj62e/PzaqRvJcfhP3NTt154em2sT1NdNkbOynj3Oew+I XM9arWKb5Flr0fam6lCXiHwVef81kKAcq6ALcKd4ubixRK+R8kfqyLiSO96GtMF2J9 ntew1uLAOe2OO7Xz7OFsMiNEvbgO/NSCD9ZWDR9k= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2991f154d3_11fc3fab10fc8f781078a5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 23:29:59 -0000 ----==_mimepart_5b2991f154d3_11fc3fab10fc8f781078a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. That's already documented under coalesced packets, I think: https://tools.ietf.org/html/draft-ietf-quic-transport-12#section-4.6 -- 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/1450#discussion_r196609791 ----==_mimepart_5b2991f154d3_11fc3fab10fc8f781078a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

That's already documented under coalesced packets, I think: https://tools.ietf.org/html/draft-ietf-quic-transport-12#section-4.6

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

----==_mimepart_5b2991f154d3_11fc3fab10fc8f781078a5-- From nobody Tue Jun 19 16:32:42 2018 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 9DDBF130FF5 for ; Tue, 19 Jun 2018 16:32:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gZW6O07X_853 for ; Tue, 19 Jun 2018 16:32:39 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8746130E4B for ; Tue, 19 Jun 2018 16:32:38 -0700 (PDT) Date: Tue, 19 Jun 2018 16:32:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529451158; bh=DkpH0GpEzTETDfBga7Y30Elu68/0aKDLFyoAEh+3taU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2CENTpVOAPlcIuGWJFNmR2BmPUWaP6QcArCQFwvl+ZTUa6DuxS7C7RN7bAYTpjNPG E2uWRyh/YmC0uvnBcEGPZ7uBEy1hc9jWMm4dTmXExejQYwMwjOaxi/T+AiQxy+5ajn 5kwmltSmd6xeD14BamzhaQbomIqo3Nij+nTQrdrU= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b299296d5e9_4fc03f8c01a92f782476a7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:32:41 -0000 ----==_mimepart_5b299296d5e9_4fc03f8c01a92f782476a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > against off-path attackers and robustness against QUIC version unaware middleboxes, but not against on-path attackers. All ciphersuites currently defined for TLS 1.3 - and therefore QUIC - have a 16-byte authentication tag and produce an output 16 bytes larger than their input. -Once TLS has provided a key, the contents of regular QUIC packets immediately -after any TLS messages have been sent are protected by the AEAD selected by TLS. - -The key, K, is either the client packet protection key (client_pp_key\) or -the server packet protection key (server_pp_key\), derived as defined in -{{key-expansion}}. - -The nonce, N, is formed by combining the packet protection IV (either -client_pp_iv\ or server_pp_iv\) with the packet number. The 64 bits -of the reconstructed QUIC packet number in network byte order is left-padded -with zeros to the size of the IV. The exclusive OR of the padded packet number -and the IV forms the AEAD nonce. +The key and iv for the packet are computed as described in {{encryption-keys}}. IV -- 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/1450#pullrequestreview-130196646 ----==_mimepart_5b299296d5e9_4fc03f8c01a92f782476a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

>  against off-path attackers and robustness against QUIC version unaware
 middleboxes, but not against on-path attackers.
 
 All ciphersuites currently defined for TLS 1.3 - and therefore QUIC - have a
 16-byte authentication tag and produce an output 16 bytes larger than their
 input.
 
-Once TLS has provided a key, the contents of regular QUIC packets immediately
-after any TLS messages have been sent are protected by the AEAD selected by TLS.
-
-The key, K, is either the client packet protection key (client_pp_key\<i>) or
-the server packet protection key (server_pp_key\<i>), derived as defined in
-{{key-expansion}}.
-
-The nonce, N, is formed by combining the packet protection IV (either
-client_pp_iv\<i\> or server_pp_iv\<i\>) with the packet number.  The 64 bits
-of the reconstructed QUIC packet number in network byte order is left-padded
-with zeros to the size of the IV.  The exclusive OR of the padded packet number
-and the IV forms the AEAD nonce.
+The key and iv for the packet are computed as described in {{encryption-keys}}.

IV

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

----==_mimepart_5b299296d5e9_4fc03f8c01a92f782476a7-- From nobody Tue Jun 19 16:33:18 2018 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 D3428130FF7 for ; Tue, 19 Jun 2018 16:33:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DbFYdggXQaWV for ; Tue, 19 Jun 2018 16:33:13 -0700 (PDT) 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 AB207130FF5 for ; Tue, 19 Jun 2018 16:33:13 -0700 (PDT) Date: Tue, 19 Jun 2018 16:33:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529451193; bh=lWjKcSUjXVEkNywOszkNp7WD0mjr6byk7itXo7gzThE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1CNQ4A3nmYSj1yM29GfY3Q7IkW6Oxp7XJOYWkLF/r4PSUthJy0nJEiQ5jcZ4r+Mao KBubflbAhD4qgBYAw6JxmLSHCJi4F9yu5C6U/HSZ1XueESuc9Z88zpRuZhnNiyyzvr UZmtzJBFseiaCi7XdGBhlXo9MrkBmBZfZxULAylw= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2992b93a9e_52d52b18ca66af5423057b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:33:16 -0000 ----==_mimepart_5b2992b93a9e_52d52b18ca66af5423057b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > -Once TLS has provided a key, the contents of regular QUIC packets immediately -after any TLS messages have been sent are protected by the AEAD selected by TLS. - -The key, K, is either the client packet protection key (client_pp_key\) or -the server packet protection key (server_pp_key\), derived as defined in -{{key-expansion}}. - -The nonce, N, is formed by combining the packet protection IV (either -client_pp_iv\ or server_pp_iv\) with the packet number. The 64 bits -of the reconstructed QUIC packet number in network byte order is left-padded -with zeros to the size of the IV. The exclusive OR of the padded packet number -and the IV forms the AEAD nonce. +The key and iv for the packet are computed as described in {{encryption-keys}}. +The nonce, N, is formed by combining the packet protection IV with the +packet number. The 64 bits of the reconstructed QUIC packet number in +network byte order is left-padded with zeros to the size of the IV. "is left-padded" or "are left-padded"? -- 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/1450#pullrequestreview-130196768 ----==_mimepart_5b2992b93a9e_52d52b18ca66af5423057b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> -Once TLS has provided a key, the contents of regular QUIC packets immediately
-after any TLS messages have been sent are protected by the AEAD selected by TLS.
-
-The key, K, is either the client packet protection key (client_pp_key\<i>) or
-the server packet protection key (server_pp_key\<i>), derived as defined in
-{{key-expansion}}.
-
-The nonce, N, is formed by combining the packet protection IV (either
-client_pp_iv\<i\> or server_pp_iv\<i\>) with the packet number.  The 64 bits
-of the reconstructed QUIC packet number in network byte order is left-padded
-with zeros to the size of the IV.  The exclusive OR of the padded packet number
-and the IV forms the AEAD nonce.
+The key and iv for the packet are computed as described in {{encryption-keys}}.
+The nonce, N, is formed by combining the packet protection IV with the
+packet number.  The 64 bits of the reconstructed QUIC packet number in
+network byte order is left-padded with zeros to the size of the IV.

"is left-padded" or "are left-padded"?

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

----==_mimepart_5b2992b93a9e_52d52b18ca66af5423057b-- From nobody Tue Jun 19 16:45:37 2018 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 3568F130FDE for ; Tue, 19 Jun 2018 16:45:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 bgmh-A5YSm5x for ; Tue, 19 Jun 2018 16:45:33 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2C42130E4F for ; Tue, 19 Jun 2018 16:45:32 -0700 (PDT) Date: Tue, 19 Jun 2018 16:45:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529451931; bh=BwPDHSjynYMN1PyrvafxvAQhmk0ftZ0cB8379siEFYM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PZY5LRdTtgIfpNIpRudLiOVo7PRFW/HpCHWztlx4Ff0G+R50/+jKXDfJFuAHTd2Q/ AK2cYMpbhhaUjq6efqa0nGk/xxIAUFyzTncZv/d96BSaRBR0hTxm1NtnYkmUipCMk6 qZcmm75JRCIjrpYZsXIK0l0jKvov1hkr/yme8ZYk= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29959bc6abf_75202ab8f7148f543245d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:45:36 -0000 ----==_mimepart_5b29959bc6abf_75202ab8f7148f543245d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. Because it's like having two STREAM frames for the same stream ID. -- 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/1450#discussion_r196612421 ----==_mimepart_5b29959bc6abf_75202ab8f7148f543245d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

Because it's like having two STREAM frames for the same stream ID.

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

----==_mimepart_5b29959bc6abf_75202ab8f7148f543245d-- From nobody Tue Jun 19 16:47:05 2018 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 0267D13101E for ; Tue, 19 Jun 2018 16:47:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 CrOk6ZwOqWah for ; Tue, 19 Jun 2018 16:47:01 -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 5C9BB130FDE for ; Tue, 19 Jun 2018 16:47:01 -0700 (PDT) Date: Tue, 19 Jun 2018 16:47:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452020; bh=iRjqIsl3jfQJ7Ksx4isAUoknY0y/n3RfGnKYeK4POi8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ynVB+RSPd3cVaB3iyerHh2xNoDTwOO9uY/zY1WFO4mZL3GqR4lN2/s3MgKvTxwbLZ CSkqFJ+2LM086GfSosr+XgBzZuv8V8Ll25RTIDU7oo43URgdYCpBSivgtNtr/awsLq 3g5bHoE2WdSvY2xMMdM3u2d0uvr4fry243FmlafE= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2995f4aa305_244b2b245f75af5420631b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:47:04 -0000 ----==_mimepart_5b2995f4aa305_244b2b245f75af5420631b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. OK, got it. -- 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/1450#discussion_r196612668 ----==_mimepart_5b2995f4aa305_244b2b245f75af5420631b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

OK, got it.

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

----==_mimepart_5b2995f4aa305_244b2b245f75af5420631b-- From nobody Tue Jun 19 16:49:19 2018 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 AB4661311FF for ; Tue, 19 Jun 2018 16:49:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 I_SUI_a_U7uo for ; Tue, 19 Jun 2018 16:49:04 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E54131206 for ; Tue, 19 Jun 2018 16:49:04 -0700 (PDT) Date: Tue, 19 Jun 2018 16:49:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452143; bh=cQgfmyibLWrsPP36BNC9d6uTSF3Xs36MUntea5J77Bo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0e4bGrqUQl7aaiVL9/pvKdFvn09II28c6ZjgLz9Nt6ImdzHFHXXGsC5kiymdZTQeE E5CoaPiDKuCTBe3aLv434G69DKzgwXax0wTbWhSMvkGbcM2CQKH0g5vL/7prmo2OX9 4Fyb0xHCgYNqWV+MdH/+/fFzMKgmcg4YatTYempY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29966fd9759_1a662b227d5aaf581468fc"; 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.26 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: Tue, 19 Jun 2018 23:49:19 -0000 ----==_mimepart_5b29966fd9759_1a662b227d5aaf581468fc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed on the editors' call, and then a follow-up conversation with @janaiyengar and a whiteboard. When there are multiple retry sources on the path, if the server's CID does not change between Retries, you are highly likely but not guaranteed to make forward progress and eventually get a response from the server. The client gets confused about two things in this scenario: - It doesn't know which Initial-with-token actually made it to the origin and got a server Initial rather than a Retry. However, this doesn't matter, because the token isn't bound into the TLS handshake or protocol state, so if it ever gets a response from the origin the connection will proceed successfully. - It can believe there were more (potentially many more) rounds of Retry than the server infrastructure has layers; if we keep the arbitrary limit of three it's easy to blow right past that. In fact, for *any* finite limit, there are conceivable situations where the client would see more retries with the right chances of packet loss and spurious retransmission. If the server *does* change CIDs on a Retry, however, you ratchet forward at each layer and ignore any extra Retry packets from the previous layer, which fixes both problems. The proposal on the call was to say that not only may each Retry change the CID, each Retry MUST change the CID unless the sender knows for sure that it's the last layer. -- 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/1451#issuecomment-398580384 ----==_mimepart_5b29966fd9759_1a662b227d5aaf581468fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Discussed on the editors' call, and then a follow-up conversation with= @janaiyengar and a whiteboard. = When there are multiple retry sources on the path, if the server's CID d= oes not change between Retries, you are highly likely but not guaranteed = to make forward progress and eventually get a response from the server. = The client gets confused about two things in this scenario:

  • It doesn't know which Initial-with-token actually made it to the orig= in and got a server Initial rather than a Retry. However, this doesn't m= atter, because the token isn't bound into the TLS handshake or protocol s= tate, so if it ever gets a response from the origin the connection will p= roceed successfully.
  • It can believe there were more (potentially many more) rounds of Retr= y than the server infrastructure has layers; if we keep the arbitrary lim= it of three it's easy to blow right past that. In fact, for any= finite limit, there are conceivable situations where the client would se= e more retries with the right chances of packet loss and spurious retrans= mission.

If the server does change CIDs on a Retry, however, you ratch= et forward at each layer and ignore any extra Retry packets from the prev= ious layer, which fixes both problems. The proposal on the call was to s= ay that not only may each Retry change the CID, each Retry MUST change th= e CID unless the sender knows for sure that it's the last layer.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29966fd9759_1a662b227d5aaf581468fc-- From nobody Tue Jun 19 16:50:11 2018 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 CCDD31311D3 for ; Tue, 19 Jun 2018 16:50:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sONmf6m0YRt9 for ; Tue, 19 Jun 2018 16:50:06 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A68131012 for ; Tue, 19 Jun 2018 16:50:05 -0700 (PDT) Date: Tue, 19 Jun 2018 16:50:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452205; bh=cOH7/ObIb5uTPVUdutf8ffE7YBv7xbrukGTcohwFLKs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NBFqgK5gaAm+ITwRSdj3/iL3kSsyO5UNBh+yg4shuS0FccBwDWfSs7AN4BZCUw+Ul nQq75hq334SNxT4SvlLTdxtrI68RR2uOZ7y+AIGf0/R+xoGOLjkKO944tzfY6876p4 ZFgaWoQbglSRAQ0jHrvIBpjDX1hLfdOlqhIxLE34= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2996ad21d6e_6ddb3f9f899b2f7c14314c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 19 Jun 2018 23:50:09 -0000 ----==_mimepart_5b2996ad21d6e_6ddb3f9f899b2f7c14314c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if typo? is padded to? -- 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/1450#pullrequestreview-130199762 ----==_mimepart_5b2996ad21d6e_6ddb3f9f899b2f7c14314c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if

typo? is padded to?

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

----==_mimepart_5b2996ad21d6e_6ddb3f9f899b2f7c14314c-- From nobody Tue Jun 19 16:50:33 2018 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 2873A131012 for ; Tue, 19 Jun 2018 16:50:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 lerccMPkYrXU for ; Tue, 19 Jun 2018 16:50:24 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC0A31311E9 for ; Tue, 19 Jun 2018 16:50:24 -0700 (PDT) Date: Tue, 19 Jun 2018 16:50:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452224; bh=vKQy23ob+YRBwqUdgBPK5GrRMGDZtzOVJ17in9ikBeA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vY4/yNpORgKRZysuBCRFlRVlBT7a38ILKupR0/q8b1tEraz9np3CZazr3Tv6R3VZE 39yKeLD1HcTXZPZUlXB9WCmrzF22sHkgqk7ikQFmc39qWFK4XrTdrwg2uU0bXLsJij 7IJsnjex4pvGrCMu/fVRSCgUbc/+sGI5Cnsjcg+U= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2996c0132cc_55f62aae2750ef6072983"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 19 Jun 2018 23:50:31 -0000 ----==_mimepart_5b2996c0132cc_55f62aae2750ef6072983 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. This also seems to be permitted for STREAM frames: ``` Stream multiplexing is achieved by interleaving STREAM frames from multiple streams into one or more QUIC packets. A single QUIC packet can include multiple STREAM frames from one or more streams. ``` -- 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/1450#discussion_r196613186 ----==_mimepart_5b2996c0132cc_55f62aae2750ef6072983 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

This also seems to be permitted for STREAM frames:

   Stream multiplexing is achieved by interleaving STREAM frames from
   multiple streams into one or more QUIC packets.  A single QUIC packet
   can include multiple STREAM frames from one or more streams.

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

----==_mimepart_5b2996c0132cc_55f62aae2750ef6072983-- From nobody Tue Jun 19 16:52:42 2018 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 E890413102A for ; Tue, 19 Jun 2018 16:52:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 49gH2k43hQwO for ; Tue, 19 Jun 2018 16:52:39 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 503D413101E for ; Tue, 19 Jun 2018 16:52:38 -0700 (PDT) Date: Tue, 19 Jun 2018 16:52:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452357; bh=Ov/5KDC9MTx2xYRKaH/5bqGduJmCjzY2nb402C/wQxk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ls6BSvhkfBACPRqriGUxr5l76DacYEQrqjYQyr9sA4zDXpkc21N5ekbV9hEaFNV4T Q/5KgwAYe6U7FVjjdMmgToG+vJMkqOFJEB2BdKjpXpoI9xlTV+ZMQAvZVHaFaTs2Hq KfqtTspKVNUuXsjDDnEmXkKwDSkA+2tD0Ka1GdJU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b299745aa5dc_787b2b27c44bcf5010874"; 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.26 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: Tue, 19 Jun 2018 23:52:41 -0000 ----==_mimepart_5b299745aa5dc_787b2b27c44bcf5010874 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reopened #1459. -- 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/1459#event-1689934727 ----==_mimepart_5b299745aa5dc_787b2b27c44bcf5010874 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Reopened #1459.

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

----==_mimepart_5b299745aa5dc_787b2b27c44bcf5010874-- From nobody Tue Jun 19 16:52:50 2018 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 E4653131041 for ; Tue, 19 Jun 2018 16:52:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 6g7fvQCnpVhL for ; Tue, 19 Jun 2018 16:52:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C29131012 for ; Tue, 19 Jun 2018 16:52:37 -0700 (PDT) Date: Tue, 19 Jun 2018 16:52:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452357; bh=Uaqa7aOICUdJJxQpypXhaMG+uBvnTiHTJQ0sPlNsqZc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=x3YZIHlshdAbABJzJ1JD1HMipXHryR1usQwrl5hnrO2n2jaActxgoEZy5QBu8EDsH wOO+wR2TiFE2Dl5eFFSpPGnTmJJb94VSlHocYuvqfaZKDSjq3N+LbKiMQ+KgmOMf9q DWYPWd+Z9tfGEY+OSQNqGav+PpDw7Q7IKYkvpuno= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2997452bc74_18f03fd270b3cf7c549f6"; 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.26 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: Tue, 19 Jun 2018 23:52:42 -0000 ----==_mimepart_5b2997452bc74_18f03fd270b3cf7c549f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson, the point of my previous comment was that I don't believe Jana's PR clearly fixes this issue. -- 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/1459#issuecomment-398580927 ----==_mimepart_5b2997452bc74_18f03fd270b3cf7c549f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson, the point of my previous comment was that I don't believe Jana's PR clearly fixes this issue.

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

----==_mimepart_5b2997452bc74_18f03fd270b3cf7c549f6-- From nobody Tue Jun 19 16:58:28 2018 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 252B9131205 for ; Tue, 19 Jun 2018 16:58:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 zVXy-x1WhG6v for ; Tue, 19 Jun 2018 16:58:12 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B5CA1311F9 for ; Tue, 19 Jun 2018 16:58:12 -0700 (PDT) Date: Tue, 19 Jun 2018 16:58:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529452691; bh=/Z28dyHuMGNwB0DT20RCbP1rx2FFyybXRowYCH6UWIQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r4FfTJoo5rxC9Ls3GjMIzHG6mmUqGO/oTfuWrbV4o9egRaKZYchdNDEdTPMx/HDIO 2dZHAuWXLdDnyBHcCpWbLZzSw2nYNsQ8cEoRzH93huxXPuWHMHQfyf5BJGGawXZxFW QO43mNPcIiXMC0y7w3JjRl7ZJFYgFA4o9f/AVsvg= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29989364de0_7af12ab6325c8f6085644"; 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.26 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: Tue, 19 Jun 2018 23:58:25 -0000 ----==_mimepart_5b29989364de0_7af12ab6325c8f6085644 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. There's nothing wrong with having multiple STREAM frames from the same stream, and I don't see anything wrong with having multiple CRYPTO_HS frames for the same reason. Presumably, they contain different regions of the handshake stream generated at different points by the TLS stack. (If they claim to contain the same region of data but differ, that might be a good reason to blow up, of course....) -- 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/1450#discussion_r196614410 ----==_mimepart_5b29989364de0_7af12ab6325c8f6085644 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

There's nothing wrong with having multiple STREAM frames from the same stream, and I don't see anything wrong with having multiple CRYPTO_HS frames for the same reason. Presumably, they contain different regions of the handshake stream generated at different points by the TLS stack.

(If they claim to contain the same region of data but differ, that might be a good reason to blow up, of course....)

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

----==_mimepart_5b29989364de0_7af12ab6325c8f6085644-- From nobody Tue Jun 19 17:13:29 2018 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 8AB8F1311DB for ; Tue, 19 Jun 2018 17:13:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xOYxluw3xNXV for ; Tue, 19 Jun 2018 17:13:25 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FB1A1311D8 for ; Tue, 19 Jun 2018 17:13:25 -0700 (PDT) Date: Tue, 19 Jun 2018 17:13:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529453605; bh=4bPs40aa5McHIrsOQ55/ZSYcHVFLi/sFnB70uyGgACg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=E30KMQxwOAtzICNBLXyTI0tFhS8OgKJBmt2Ir0EEtH8vSnQ6BVMuDUVMrA2jVoYIG duHaZXMdx7bcHx55M8ObYdFhIvBINbTHEbVzpyAugu/dyoNYH7+XbIqv8ojVCMZb2z MYL0DPLguQpoAwkDul+W0/3rBT0WfGA6t0brlvSQ= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b299c24e7535_675a2ab11349cf5c93247"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Wed, 20 Jun 2018 00:13:28 -0000 ----==_mimepart_5b299c24e7535_675a2ab11349cf5c93247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. Right, so I get the case where more than one CRYPTO_HS/STREAM frame is present but at least we should mention what to do if they overlap. -- 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/1450#discussion_r196616553 ----==_mimepart_5b299c24e7535_675a2ab11349cf5c93247 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

Right, so I get the case where more than one CRYPTO_HS/STREAM frame is present but at least we should mention what to do if they overlap.

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

----==_mimepart_5b299c24e7535_675a2ab11349cf5c93247-- From nobody Tue Jun 19 17:51:08 2018 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 07084130E36 for ; Tue, 19 Jun 2018 17:51:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 A-DSk6Odhi8w for ; Tue, 19 Jun 2018 17:51:01 -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 C9FAF130DBE for ; Tue, 19 Jun 2018 17:51:00 -0700 (PDT) Date: Tue, 19 Jun 2018 17:50:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529455859; bh=2NMmv+ReT0kMYwT9zDjWNPowbHoZoOfxh4nJ8JXSa0A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UeXN/cVwPdmJkkS+0yzvy+KEu1A7CG6CDwTdzcnq//BH94wd2eQVa8km/qieIftM0 woudsmp+HXwjQ3rPtpAS+4owHd0MwyqTLtxkzKyHISX8r7nCyqcNg8xgE/DLnvsNIf pVIX/mAypplfaw8aahksjhGg1mfH8RgawuSZugXY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29a4f2f27b3_145ce3f8082e2af8070235"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 00:51:07 -0000 ----==_mimepart_5b29a4f2f27b3_145ce3f8082e2af8070235 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. I think we should, but not limit it to the case where they are in the same packet. The situation is the same if they are in two different packets. -- 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/1450#discussion_r196621214 ----==_mimepart_5b29a4f2f27b3_145ce3f8082e2af8070235 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

I think we should, but not limit it to the case where they are in the same packet. The situation is the same if they are in two different packets.

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

----==_mimepart_5b29a4f2f27b3_145ce3f8082e2af8070235-- From nobody Tue Jun 19 19:17:29 2018 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 D5735130E6F for ; Tue, 19 Jun 2018 19:17:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 9QxOFfmrFeiD for ; Tue, 19 Jun 2018 19:17:26 -0700 (PDT) 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 05160130DF1 for ; Tue, 19 Jun 2018 19:17:26 -0700 (PDT) Date: Tue, 19 Jun 2018 19:17:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529461044; bh=ySBOuNNoaeMep/jKj9NWOpPIXVCm8FR2F9xLuYAFHvk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LeZWpO20o48MqXq+NCnprzRohY7i9IUGEggfSbqwQEUQui+iMN0c2d1h/d/HI3xgf fJ2lDB0SK4Xar/ySiUi02gQm4Gw7JpWsAwSR6ZsEOg+XksZHC/6v/ChtMob4QuBtYf bHIPLTkcH67RWYCmqoYkCpNUxHVg2usdIN5dNSQM= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29b93454dc0_14092afe23fe6f54109072"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Wed, 20 Jun 2018 02:17:28 -0000 ----==_mimepart_5b29b93454dc0_14092afe23fe6f54109072 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. If they are in two different packets then it's just a retransmission ;-) I'm thinking we just need some text saying the receive is supposed to detect and handle overlapping CRYPTO_HS/STREAM frame even if they are in the same packet. Maybe we already have that, but I don't see it. -- 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/1450#discussion_r196631210 ----==_mimepart_5b29b93454dc0_14092afe23fe6f54109072 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

If they are in two different packets then it's just a retransmission ;-)
I'm thinking we just need some text saying the receive is supposed to detect and handle overlapping CRYPTO_HS/STREAM frame even if they are in the same packet. Maybe we already have that, but I don't see it.

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

----==_mimepart_5b29b93454dc0_14092afe23fe6f54109072-- From nobody Tue Jun 19 19:58:26 2018 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 7B2EF130EA1 for ; Tue, 19 Jun 2018 19:58:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8-iboR5Ia0Fd for ; Tue, 19 Jun 2018 19:58:22 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3470A130E71 for ; Tue, 19 Jun 2018 19:58:22 -0700 (PDT) Date: Tue, 19 Jun 2018 19:58:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529463501; bh=INcnP9L2ygb8Q0SySry3REBN0FuawTEiVQiuPfInYoE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2KWmJ87FLNCDD9hGDSk4I5hlJfy5xki5Fu8yxZi7z6YYqx3xdfCcFFBvEp/8YpBoP bSatPU6ePvH9TAhmTotUc2ItfzhcMMzYnDIL5X9O/vDAR6c+9xRQ88eDtSR3qR9frh 3MrYigvIDikgZfhMwDIcZVTml6Md4n3pKDj2cEWo= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29c2cd8d1b_69d02aea2b3b4f58187285"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 02:58:25 -0000 ----==_mimepart_5b29c2cd8d1b_69d02aea2b3b4f58187285 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. Sure. Given that CRYPTO_HS has the same semantics in this respect as STREAM, I suggest a separate PR that adds it to the stream section. -- 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/1450#discussion_r196635694 ----==_mimepart_5b29c2cd8d1b_69d02aea2b3b4f58187285 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

Sure. Given that CRYPTO_HS has the same semantics in this respect as STREAM, I suggest a separate PR that adds it to the stream section.

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

----==_mimepart_5b29c2cd8d1b_69d02aea2b3b4f58187285-- From nobody Tue Jun 19 20:15:20 2018 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 ECD8D130EA1 for ; Tue, 19 Jun 2018 20:15:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vGHGcKQwgz-H for ; Tue, 19 Jun 2018 20:15:16 -0700 (PDT) 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 943B9130DFC for ; Tue, 19 Jun 2018 20:15:16 -0700 (PDT) Date: Tue, 19 Jun 2018 20:15:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529464515; bh=gCn8+hKE88dZcCdu2mhTdgiEebmk2m8IW6/uh6aYiEg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EU5vGAicAU1oY79xiWpMlia9U2sllI/kdsCBRz7f9s62vCzhtolUblzJmT1eeE1fP OLyoRm7y6TLJ5USXx4mwLlTolv8Tn17NEBeKvIadkIt1dAa46hGpzo6XvNRzM9TRHF EvYxVHU9kCwRFZcf1Wn2jFwta/LiH3DcrKvTlcRI= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29c6c3900c7_50553fb0faeaaf846222fe"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 03:15:18 -0000 ----==_mimepart_5b29c6c3900c7_50553fb0faeaaf846222fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Let me see if I understand correctly. Are you saying it looks like this? ``` Initial [SCID=X, DCID=Y] -> <- Retry[SCID=A, DCID=X] Initial [SCID=X, DCID=A] -> <- Retry [SCID=B, DCID=X] Initial [SCID=X, DCID=B] -> ``` Is that what you are proposing? -- 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/1451#issuecomment-398611100 ----==_mimepart_5b29c6c3900c7_50553fb0faeaaf846222fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Let me see if I understand correctly. Are you saying it looks like thi= s?

Initial [SCID=3DX, DCID=3DY] ->
<- Retry[SCID=3DA, DCID=3DX]
Initial [SCID=3DX, DCID=3DA] ->
<- Retry [SCID=3DB, DCID=3DX]
Initial [SCID=3DX, DCID=3DB] ->

Is that what you are proposing?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29c6c3900c7_50553fb0faeaaf846222fe-- From nobody Tue Jun 19 20:34:10 2018 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 5EF84130FF0 for ; Tue, 19 Jun 2018 20:34:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 xfwcI0brZPo5 for ; Tue, 19 Jun 2018 20:34:06 -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 45A77130DFC for ; Tue, 19 Jun 2018 20:34:06 -0700 (PDT) Date: Tue, 19 Jun 2018 20:34:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529465645; bh=nvabPdR1PUPvIFKMNDrIf2WTXJCriXZ56z4SK3jaGVQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=shr0vXqOuqeiMOsZ/2nQKfL9BcKUj9Fusn0v/wtqsA/SJJ2DwQlsI3q50bBFfxJD4 T6uEc+VIJoAGhIKx6dJWho1++YD88znOuI7Imtzsme0FJIA2ldllzEcQTaorEc9lv/ 8zXZp6eweS3mv1fS44QQmvBW9BZugeAEJXQBbrOM= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29cb2d4eeed_12f3f85eaf6cf84323949"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Wed, 20 Jun 2018 03:34:08 -0000 ----==_mimepart_5b29cb2d4eeed_12f3f85eaf6cf84323949 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We should make it clear that implementations must handle overlapping data in all cases: 1) Duplicate STREAM/CRYPTO_HS in two different packets 2) Duplicate STREAM/CRYPTO_HS in the same packet 3) Duplicate STREAM/CRYPTO_HS in two packets but inside one UDP datagram The receiver should discard overlapping data and not close the connection. -- 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/1463 ----==_mimepart_5b29cb2d4eeed_12f3f85eaf6cf84323949 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We should make it clear that implementations must handle overlapping data in all cases:

  1. Duplicate STREAM/CRYPTO_HS in two different packets
  2. Duplicate STREAM/CRYPTO_HS in the same packet
  3. Duplicate STREAM/CRYPTO_HS in two packets but inside one UDP datagram

The receiver should discard overlapping data and not close the connection.

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

----==_mimepart_5b29cb2d4eeed_12f3f85eaf6cf84323949-- From nobody Tue Jun 19 21:46:34 2018 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 4182D131027 for ; Tue, 19 Jun 2018 21:46:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 APfuOw-pJzsx for ; Tue, 19 Jun 2018 21:46:31 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80720130EBA for ; Tue, 19 Jun 2018 21:46:31 -0700 (PDT) Date: Tue, 19 Jun 2018 21:46:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529469990; bh=TqYvBFooq4zbXQOMhUV1NB3VIR3WBlboufeSaLPjG7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QDuH1tqknkShTERudubmLHWm9VwytfrtZOCIda25Vo9DzdDndQ8JfxPZnLQ7HZpV/ uubBxcndYngCALbsk2dFLngYoYLqm0xyJvfxm37zazxCFxMFazRdTayQlbLcUYV35s obQqEoOe6chgF6EB82OlCaHzIshQ2U9GoNx1ikyE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29dc2656d99_413f2b1ca78b8f5031813c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 04:46:34 -0000 ----==_mimepart_5b29dc2656d99_413f2b1ca78b8f5031813c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I pointed this out, but it was lost on transcription. We need to also require that the SCID in a Retry is >N octets (the same restrictions as on the client-generated DCID would work, but it's probably OK to use the 4 octet minimum). -- 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/1451#issuecomment-398622910 ----==_mimepart_5b29dc2656d99_413f2b1ca78b8f5031813c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I pointed this out, but it was lost on transcription. We need to also require that the SCID in a Retry is >N octets (the same restrictions as on the client-generated DCID would work, but it's probably OK to use the 4 octet minimum).

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

----==_mimepart_5b29dc2656d99_413f2b1ca78b8f5031813c-- From nobody Tue Jun 19 21:54:49 2018 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 0BF55130EFC for ; Tue, 19 Jun 2018 21:54:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zK0Fvmhf1tE4 for ; Tue, 19 Jun 2018 21:54:45 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E6BC130EE8 for ; Tue, 19 Jun 2018 21:54:45 -0700 (PDT) Date: Tue, 19 Jun 2018 21:54:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529470484; bh=ZC6xsPCHmqVtbNE+u8A1fbKNVVPeJrs+ickaFkP5DYw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V5Tac8zpVRVQUnJ8LecXKe3b0NgG/qwd77lvZEwzr1K3th8FXABa/ExcrYvnaOrVq A6PQ/XQjJCR63ZX3dMbhfwugUQsZqhq77GEO6gRfJE/395UWxSlYMLbhHBMf38dlfg fuN12tty7jRV+W165ep/YgOE9hydaPXcJo+k55P4= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29de143720e_31252ab8cfdcaf5c804ce"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 04:54:48 -0000 ----==_mimepart_5b29de143720e_31252ab8cfdcaf5c804ce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, I think it would be better to abandon the use of the SCID as a nonce here. instead, I propose we say that Retry has to contain the last 8 octets of the Initial packet it's responding to. That's high entropy by definition (it's a hash of CH), and then we won't need any other rule -- 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/1451#issuecomment-398623929 ----==_mimepart_5b29de143720e_31252ab8cfdcaf5c804ce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Actually, I think it would be better to abandon the use of the SCID as= a nonce here.

instead, I propose we say that Retry has to contain the last 8 octets = of the Initial packet it's responding to. That's high entropy by definiti= on (it's a hash of CH), and then we won't need any other rule

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29de143720e_31252ab8cfdcaf5c804ce-- From nobody Tue Jun 19 22:12:36 2018 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 CE10013102B for ; Tue, 19 Jun 2018 22:12:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_SUMOF=5, 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 0baEkGAJyk4H for ; Tue, 19 Jun 2018 22:12:27 -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 D1C0C13102C for ; Tue, 19 Jun 2018 22:12:26 -0700 (PDT) Date: Tue, 19 Jun 2018 22:12:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529471546; bh=FB1V6W9c8B6MGLtTk+ZZSd/hAxJDJjd2tJ9avfepwFQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V/hoBJkWjnoQUuJQdquzVI1WEEresB4nWwdDZIwXD/Jhu2fzcvczw/70XJ6VHj8dc U6W6tGHB3Sg/BuZdNlQjhNeYxEANG3t8ogUzyuEhfVPBt6RKEKBqhyTVplh3RXWIPA yWVNc6/CZGcqYzlUHmTQxg2QfNfoUt8MFdegTcXU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e239e9c5a_18b02aca1febaf50640976"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 05:12:35 -0000 ----==_mimepart_5b29e239e9c5a_18b02aca1febaf50640976 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable martinthomson approved this pull request. At risk of this turning into a unicorn, here are my comments. I don't th= ink that you need to address all of them, but I would appreciate you taki= ng one pass through this so we don't have too many editorial landmines to= worry about later. Most are nitty, so they should be easy to fix; other= s I'm happy to punt on. On the renaming of frames and the removal of CRYPTO_CLOSE, I think that w= e can easily make that sort of change later. And I plan to do so. An appeal to those commenting on this PR. This is almost at the point th= at GitHub is going to choke on it, if it doesn't start doing that already= . If you have nits, questions, or responses to others comments, please r= efrain from adding to the pile of comments. If you think that there is a= substantive issue that this PR creates, please open an issue. > @@ -107,7 +111,7 @@ important to the loss detection and congestion cont= rol machinery below. * Retransmittable packets are those that contain at least one retransmittable frame. = -* Crypto handshake data is sent on stream 0, and uses the reliability +* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliab= ility s/CRYPTO_HS/CRYPTO/g Yes, I understand that there is a message that carries a TLS alert, but I= don't think that's ideal. If we want to carry alerts, we can pack the r= ange of cryptographic alerts into the CONNECTION_CLOSE space, or recommen= d that the reason phrase start with the alert. > @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones.= Protocol differences between QUIC and TCP however contribute to algorithmic differences. We briefly d= escribe these protocol differences below. = +### Separate Packet Number Spaces + +QUIC uses separate packet number spaces for each encryption level, excep= t that +0-RTT and all generations of 1-RTT keys use the same packet number space= . +Separating the spaces allows the recovery mechanisms to work without spe= cial +cases to avoid spuriously retransmitting un-processable packets. This really doesn't say why. I think that you want to say that separatin= g the spaces ensures that packets from different spaces, which can't be d= ecrypted, could trigger spurious retransmission. > @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones.= Protocol differences between QUIC and TCP however contribute to algorithmic differences. We briefly d= escribe these protocol differences below. = +### Separate Packet Number Spaces + +QUIC uses separate packet number spaces for each encryption level, excep= t that +0-RTT and all generations of 1-RTT keys use the same packet number space= . +Separating the spaces allows the recovery mechanisms to work without spe= cial +cases to avoid spuriously retransmitting un-processable packets. +Separate packet number spaces do not imply separate paths. Consequently,= I don't think that you need to talk about separate paths. It opens more q= uestions than it answers. > = -Handshake packets, which contain STREAM frames for stream 0, are critica= l to -QUIC transport and crypto negotiation, so a separate alarm is used for t= hem. +Data in CRYPTO_HS frames is critical to QUIC transport and crypto negoti= ation, +so a more aggressive timeout is used to retransmit it. Below, the word +handshake packet is used to refer to packets containing CRYPTO_HS frames= , +not packets with the specific long header packet type Handshake. This h/H thing is not ideal, but we don't need to fix it before landing t= his. > = -When the alarm fires, the sender MUST retransmit all unacknowledged hand= shake -data, by calling RetransmitAllUnackedHandshakeData(). On each consecutiv= e -firing of the handshake alarm, the sender SHOULD double the handshake ti= meout -and set an alarm for this period. +When the alarm fires, the sender MUST retransmit all unacknowledged CRYP= TO_HS This needs to be in the same paragraph as the previous. > @@ -422,6 +439,14 @@ sending any ACK frames in response. In this case = they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. = +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +should use a very short ack delay, such as 1ms. ACK frames may be SHOULD? and (later) MAY? is it "ack delay" or "ACK delay"? don't abbreviate crypto (that means cryptocurrency, dinchano?) > @@ -559,6 +584,8 @@ sent_packets: was sent, a boolean indicating whether the packet is ack only, and a b= ytes field indicating the packet's size. sent_packets is ordered by packet= number, and packets remain in sent_packets until acknowledged or lost.= + A sent_packets data structure is maintained per packet number space, a= nd ack ACK > @@ -422,6 +439,14 @@ sending any ACK frames in response. In this case = they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. = +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +should use a very short ack delay, such as 1ms. ACK frames may be +sent immediately when the crypto stack indicates all data for that +encryption level has been received. + The full implications of the change to multiple packet number spaces does= n't seem to be present here. Shouldn't this say something about RTO as w= ell? If I understand the design, packets sent with handshake and initial= keys are retransmitted on this timer only, not RTO. The awkward thing here is that this seems to lead to EndOfEarlyData being= retransmitted on RTO, not the handshake timer. We need an issue for cha= sing that down. > +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level.= +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption not MUST, can > +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level.= +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. The list here is accurate, but we can consider rotating it later. > +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level.= +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet s/may/could/ > +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. + +| Packet Type | Encryption Level | +|:----------------|:-----------------| +| Initial | Initial secrets | +| 0-RTT Protected | 0-RTT | +| Handshake | Handshake | +| Retry | N/A | +| Short Header | 1-RTT | +{: #packet-types-levels title=3D"Encryption Levels by Packet Type"} Any sense extending this to include packet number spaces? > +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. + +| Packet Type | Encryption Level | +|:----------------|:-----------------| +| Initial | Initial secrets | +| 0-RTT Protected | 0-RTT | +| Handshake | Handshake | +| Retry | N/A | +| Short Header | 1-RTT | +{: #packet-types-levels title=3D"Encryption Levels by Packet Type"} + +{{QUIC-TRANSPORT}}; Section 6.3 shows how packets at the various encrypt= ion Section 6.3 of `[...]`, or use a comma > -A QUIC server starts the process by providing TLS with stream 0 octets= . - -Each time that an endpoint receives data on stream 0, it delivers the oc= tets to -TLS if it is able. Each time that TLS is provided with new data, new ha= ndshake -octets are requested from TLS. TLS might not provide any octets if the -handshake messages it has received are incomplete or it has no data to s= end. - -At the server, when TLS provides handshake octets, it also needs to indi= cate -whether the octets contain a HelloRetryRequest. A HelloRetryRequest MUS= T always -be sent in a Retry packet, so the QUIC server needs to know whether the = octets -are a HelloRetryRequest. +A QUIC server starts the process by providing TLS with the client's +handshake octets. + +At any given time, an endpoint will have a current sending encryption +level and receiving encryption level. Each encryption level is I don't think that we need this sentence any more. If you consider that = TLS provides octets that are explicitly destined for a particular epoch a= nd that each epoch is clearly identified by the type of packet, then you = only need to concern yourself with routing to the correct epoch. This do= esn't have to follow the strict linear regime that TLS assumes, which in = any case is detrimental when you consider the potential for reordering. It's fine to mention that later epochs might not be available early on an= d then (separately) saying that epochs can be discarded when they aren't = needed. > +will eventually be transmitted under the then-current key. + +When an endpoint receives a QUIC packet containing a CRYPTO_HS frame fro= m +the network, it proceeds as follows: + +- If the packet was in the current receiving encryption level, sequence + the data into the input flow as usual. As with STREAM frames, + the offset is used to find the proper location in the data sequence. + If the result of this process is that new data is available, then + it is delivered to TLS. + +- If the packet is from a previously installed encryption level, it + MUST not contain data which extends past the end of previously + received data in that flow. Implementations MUST treat any + violations of this requirement as a connection error of type + PROTOCOL_VIOLATION. I don't think that this works. Consider EndOfEarlyData, which could be l= ost, then later repaired. The end of the previously installed encryption= level (aside from being only loosely defined) for CRYPTO is 0, so EOED w= ould extend past that. Also, if you take a looser interpretation, then a= delayed 0-RTT STREAM frame might also extend that stream beyond the poin= t where the server cut over to reading Handshake or 1-RTT. > @@ -440,102 +433,63 @@ Important: STREAM frame that carries the Finished message in multiple packets. T= his enables immediate server processing for those packets. = +### Encryption Level Changes As above, rather than casting these as changes, it might be better to con= centrate on availability of keys and how TLS targets particular keys. For most frames, the notion of current level doesn't matter: you send in = the latest 1-RTT if you can, 0-RTT if you can't otherwise, and don't send= at all otherwise. > Get Handshake - 1-RTT Keys Ready - <--- send/receive --- + <------------ Initial + Rekey rx to 0-RTT keys Consistent with the above, I don't think that we need to "rekey" receptio= n, but rather install those keys and make them available. The same applies to rekeying for transmission really. This diagram is somewhat useful, but we should have text that it is only = indicative, and that keys are selected based on the type of content being= sent, or based on the type of packet that was received. > = -QUIC uses a system of packet protection secrets, keys and IVs that are m= odelled -on the system used in TLS {{!TLS13}}. The secrets that QUIC uses -as the basis of its key schedule are obtained using TLS exporters (see S= ection -7.5 of {{!TLS13}}). +A client that attempts 0-RTT MUST also consider 0-RTT to be rejected if = it +receives a Version Negotiation packet. ... or Retry. > = -~~~ -struct { - uint16 length =3D Length; - opaque label<6..255> =3D "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the T= LS +handshake, using the AEAD algorithm negotiated by TLS. Seems fine to me. > - uint16 length =3D Length; - opaque label<6..255> =3D "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the T= LS +handshake, using the AEAD algorithm negotiated by TLS. + + +## QUIC Packet Encryption Keys {#encryption-keys} + +QUIC derives packet encryption keys in the same way as TLS 1.3: +Each encryption level/direction pair has a secret value, which +is then used to derive the traffic keys using as described +in {{TLS13}}; Section 7.3. Section 7.3 of > = +The keys for the remaining encryption level are computed in the same +fashion as the corresponding TLS keys (see {{TLS13}}; Section 7), +except that the label for HKDF-Expand-Label uses the prefix "quic " +rather than "tls 13". The purpose of this change is to provide key +separation between TLS and QUIC, so that TLS stacks can avoid +exposing TLS record protection keys. I don't think that we need this separation. Isn't the fact that this is = a QUIC connection separation enough? The same TLS connection can't be us= ed to key TLS record protection on a TCP connection. If this remains, then we need to ensure that this is only ever the final = derivation (those with "key" and "iv"). Otherwise, there might be confus= ion about the label provided to Derive-Secret as well. > = -Packets that carry the TLS handshake (Initial, Retry, and Handshake) are= -protected with a secret derived from the Destination Connection ID field= from -the client's Initial packet. Specifically: +Initial packets are protected with +a secret derived from the Destination Connection ID field from the clien= t's +Initial packet. Specifically: Well, not entirely. If the client changes the destination connection ID = in response to Retry, then the packets will be protected with keys derive= d from that value. Where this gets hairy is the Initial packets that the= client needs to send after the server sends ServerHello or HelloRetryReq= uest, the first of which can change the destination connection ID. ACK frames in Initial packets will probably then need to use the updated = connection ID, and keys derived from the first Initial packet sent. That= 's fine. But if this is another ClientHello and we require the same rule= s, then we're preventing the use of a stateless HelloRetryRequest. > @@ -873,26 +673,20 @@ from the packet number. All QUIC packets other than Version Negotiation and Stateless Reset pack= ets are protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shar= ed secret, packets are protected with AEAD_AES_128_GCM and a key derived fr= om the -client's connection ID (see {{handshake-secrets}}). This provides prote= ction +client's connection ID (see {{initial-secrets}}). This provides protect= ion or "from the destination connection ID in the client's first Initial pack= et (see ..." > @@ -1024,144 +795,90 @@ encrypted_pn =3D ChaCha20(pn_key, counter, nonc= e, packet_number) = ## Receiving Protected Packets = -Once an endpoint successfully receives a packet with a given packet numb= er, it -MUST discard all packets with higher packet numbers if they cannot be -successfully unprotected with either the same key, or - if there is a ke= y update -- the next packet protection key (see {{key-update}}). Similarly, a pac= ket that -appears to trigger a key update, but cannot be unprotected successfully = MUST be -discarded. +Once an endpoint successfully receives a packet with a given packet +number, it MUST discard all packets in the same packet number space +with higher packet numbers if they cannot be successfully unprotected +with either the same key, or - if there is a key update - the next +packet protection key (see {{key-update}}). Similarly, a packet that +appears to trigger a key update, but cannot be unprotected +successfully MUST be discarded. Unfortunately this doesn't work with 0-RTT, because we need reliable tran= smission of EndOfEarlyData. That probably just needs a carve-out. > = -A server might choose to retain 0-RTT packets that arrive before a TLS -ClientHello. The server can then use those packets once the ClientHello= -arrives. However, the potential for denial of service from buffering 0-= RTT -packets is significant. These packets cannot be authenticated and so mi= ght be -employed by an attacker to exhaust server resources. Limiting the numbe= r of -packets that are saved might be necessary. +A client MUST only use 0-RTT keys to protect data that is idempotent. A= client +MAY wish to apply additional restrictions on what data it sends prior to= the +completion of the TLS handshake. A client otherwise treats 0-RTT keys a= s +equivalent to 1-RTT keys, except that ACKs for that data MUST only be se= nt with +1-RTT keys. "A server uses 1-RTT keys to protect acknowledgements of 0-RTT packets." > = -### Retransmission and Acknowledgment of Unprotected Packets +: 0-RTT data can be acknowledged by the server as it receives it, but an= y Either that or make it a note. It's a shame we can't just use Handshake keys for those acknowledgments, = but that would require a change in the design. > = -Once 1-RTT keys are available to an endpoint, it no longer needs the TLS= -handshake messages that are carried in unprotected packets. However, a = server -might need to retransmit its TLS handshake messages in response to recei= ving an -unprotected packet that contains ACK frames. A server MUST process ACK = frames -in unprotected packets until the TLS handshake is reported as complete, = or it -receives an ACK frame in a protected packet that acknowledges all of its= -handshake messages. +Receiving and verifying the TLS Finished message is critical in +ensuring the integrity of the TLS handshake. A server MUST NOT use +1-RTT protected packets from the client prior to verifying the client +Finished message if its response depends on client authentication. Let's drop this one. No point in getting into the client authentication = thing. > = -## Key Update {#key-update} +Once the 1-RTT keys are established and the short header is in use, it +is possible to update the keys, for instance because of limits on AEAD +encryption. The KEY_PHASE bit in the short header is used to indicate This "for instance" is a little stilted. I don't have a good suggestion = right now though. > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large blo= ck of handshake messages from a server can be used in packet reflection attacks to amplify the traffic g= enerated by an attacker. = -Certificate caching {{?RFC7924}} can reduce the size of the server's han= dshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a mi= nimum -size. A server is less likely to generate a packet reflection attack if= the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is like= ly to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; We concluded that this wasn't packets, but UDP datagrams. > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large blo= ck of handshake messages from a server can be used in packet reflection attacks to amplify the traffic g= enerated by an attacker. = -Certificate caching {{?RFC7924}} can reduce the size of the server's han= dshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a mi= nimum -size. A server is less likely to generate a packet reflection attack if= the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is like= ly to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; +Section 4.4.3). Finally, because ACKs of Handshake packets s/ACKs/acknowledgments/ (to allow for ACK_ECN) > = = ### Initial Packet {#packet-initial} = The Initial packet uses long headers with a type value of 0x7F. It carr= ies the -first cryptographic handshake message sent by the client. +first CRYPTO_HS frames sent by the client as well as the +cryptographic messages sent by the server to perform key exchange. The I= nitial Any sense mentioning acknowledgments here? > = -If the client received a Retry packet and is sending a second Initial pa= cket, -then it sets the Destination Connection ID to the value from the Source -Connection ID in the Retry packet. Changing Destination Connection ID a= lso -results in a change to the keys used to protect the Initial packet. +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... Check alignment. > -results in a change to the keys used to protect the Initial packet. +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +Token Length: + +: A variable-length integer specifying the length of the Token field, in= bytes. +It may be zero if no token is present. The server MUST send a zero-lengt= h +token. Initial packets sent by the server MUST include a zero-length token. > +| Token Length (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +Token Length: + +: A variable-length integer specifying the length of the Token field, in= bytes. +It may be zero if no token is present. The server MUST send a zero-lengt= h +token. + +Token: + +: An optional token blob previously received in either a Retry packet or= +NEW_TOKEN frame. Is the client required to include a token on every Initial packet that it= sends, including ones that include only ACK frames, or is it only the fi= rst and any that are sent in response to Retry? Interestingly, if you take the first+Retry rule, then that matches neatly= with the rules about which destination connection ID is used to determin= e keys. > + +A server sends its first Initial packet in response to a client Initial.= A +server may send multiple Initial packets. The cryptographic key exchang= e could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete +first message MUST fit in a single packet (see {{handshake}}). Note that= if +the server sends a HelloRetryRequest, the client will send a second Init= ial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously r= eceived an an > +server may send multiple Initial packets. The cryptographic key excha= nge could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's c= omplete +first message MUST fit in a single packet (see {{handshake}}). Note that= if +the server sends a HelloRetryRequest, the client will send a second Init= ial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously r= eceived +a Retry packet from the server, it populates the Destination Connection = ID field +with a randomly selected value. This MUST be at least 8 octets in lengt= h. Until We've agreed to "unpredictable" in other such cases rather than "randomly= ". > = The client populates the Source Connection ID field with a value of its = choosing and sets the SCIL field to match. = -The first Initial packet that is sent by a client contains a packet numb= er of 0. -All subsequent packets contain a packet number that is incremented by at= least -one, see ({{packet-numbers}}). - -The payload of an Initial packet conveys a STREAM frame (or frames) for = stream -0 containing a cryptographic handshake message. The stream in this pack= et -always starts at an offset of 0 (see {{stateless-retry}}) and the comple= te -cryptographic handshake message MUST fit in a single packet (see {{hands= hake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection This consistency requirement seems to be under debate. We're currently g= ravitating toward a requirement to change the value on (almost) every Ret= ry, and then allowing the first Initial packet from the server to set a n= ew value. Only after that can it be consistent. > - -The payload of an Initial packet conveys a STREAM frame (or frames) for = stream -0 containing a cryptographic handshake message. The stream in this pack= et -always starts at an offset of 0 (see {{stateless-retry}}) and the comple= te -cryptographic handshake message MUST fit in a single packet (see {{hands= hake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection +IDs during the handshake. + +On first receiving an Initial or Retry packet from the server, the +client uses the Source Connection ID supplied by the server as the +Destination Connection ID for subsequent packets. The client MUST +discard any subsequent packets it receives with different Perhaps: "Once a client has received an Initial packet from the server, i= t MUST discard any packet it receives with a different Source Connection = ID." > +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection +IDs during the handshake. + +On first receiving an Initial or Retry packet from the server, the +client uses the Source Connection ID supplied by the server as the +Destination Connection ID for subsequent packets. The client MUST +discard any subsequent packets it receives with different +Source Connection IDs. + +#### Tokens + +If the client has a suitable token available from a previous connection,= +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an This paragraph doesn't belong here really. It's part of the description = of Retry. > + +#### Tokens + +If the client has a suitable token available from a previous connection,= +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID t= o +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated We can't assume retention of keys, but we can provide some recommendation= s. If tokens are clearly marked as NEW_TOKEN vs. Retry, then the former = might be old and broken, so treating that as equivalent to an absent toke= n is reasonable. For the latter, Retry might be verifiable. If somethin= g is clearly a Retry token, then dropping the connection seems OK. Needs more text. > + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID t= o +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated +address, including potentially sending a Retry. If the validation +succeeds, the server SHOULD then allow the handshake to proceed (see +{{stateless-retry}}). + +Note: The rationale for treating the client as unvalidated rather Formatting for notes is generally to use a definition list: ``` Note: : The rationale ... ``` > +address, including potentially sending a Retry. If the validation +succeeds, the server SHOULD then allow the handshake to proceed (see +{{stateless-retry}}). + +Note: The rationale for treating the client as unvalidated rather +than discarding the packet is that the client might have received +the token in a previous connection using the NEW_TOKEN message, +and if the server has lost state, it might be unable to validate +the token at all, leading to connection failure if the packet +is discarded. + +#### Starting Packet Numbers + +The first Initial packet contains a packet number of 0. Each packet sent= after +the Initial packet is associated with a packet number space and its pack= et +number increases monotonically in that space (see {{packet-numbers}}). Do you start at zero again if you change the connection ID? I don't thin= k you do, but it might help to be clear on this point. > = ### Retry Packet {#packet-retry} = -A Retry packet uses long headers with a type value of 0x7E. It carries -cryptographic handshake messages and acknowledgments. It is used by a s= erver -that wishes to perform a stateless retry (see {{stateless-retry}}). +A Retry packet uses long headers with a type value of 0x7E. It carries a= n +address validation token created by the server. It is used by a server t= hat +wishes to perform a stateless retry (see {{stateless-retry}}). + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| DCIL(8) | Original Destination Connection ID (*) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Retry Token (*) ... > = ### Retry Packet {#packet-retry} = -A Retry packet uses long headers with a type value of 0x7E. It carries -cryptographic handshake messages and acknowledgments. It is used by a s= erver -that wishes to perform a stateless retry (see {{stateless-retry}}). +A Retry packet uses long headers with a type value of 0x7E. It carries a= n +address validation token created by the server. It is used by a server t= hat +wishes to perform a stateless retry (see {{stateless-retry}}). + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| DCIL(8) | Original Destination Connection ID (*) | ODCIL ? > = -Continuing the cryptographic handshake is necessary to ensure that an at= tacker -cannot force a downgrade of any cryptographic parameters. In addition t= o -continuing the cryptographic handshake, the client MUST remember the res= ults of -any version negotiation that occurred (see {{version-negotiation}}). Th= e client -MAY also retain any observed RTT or congestion state that it has accumul= ated for -the flow, but other transport state MUST be discarded. +If the Original Destination Connection ID field does not match the +Destination Connection ID from the Initial packet it sent, clients MUST "most recent Initial packet" (this will also help with the other problem = we have) > = -After receiving a Retry packet, the client uses a new -Initial packet containing the next cryptographic handshake message. The= client -retains the state of its cryptographic handshake, but discards all trans= port -state. The Initial packet that is generated in response to a Retry pack= et -includes STREAM frames on stream 0 that start again at an offset of 0. +A server MUST only send a Retry in response to a client Initial packet. Do we need to include a minimum size constraint here as well? A Retry th= at is sent in response to an ACK frame is just weird. > = -The payload of the Retry packet contains at least two frames. It MUST in= clude a -STREAM frame on stream 0 with offset 0 containing the server's cryptogra= phic -stateless retry material. It MUST also include an ACK frame to acknowled= ge the -client's Initial packet. It MAY additionally include PADDING frames. The= next -STREAM frame sent by the server will also start at stream offset 0. +Otherwise, the client SHOULD respond with a new Initial +packet with the Token field set to the token received in the Retry packe= t. Following the above thought, I think that we need to prohibit this reacti= on from clients if they have received an Initial packet from the server. > @@ -761,7 +844,7 @@ During the handshake, an endpoint might receive mul= tiple packets with the long header, and thus be given multiple opportunities to update the Destinati= on Connection ID it sends. A client MUST only change the value it sends in= the Destination Connection ID in response to the first packet of each type i= t -receives from the server (Retry or Handshake); a server MUST set its val= ue based +receives from the server (Retry or Initial); a server MUST set its value= based on the Initial packet. Any additional changes are not permitted; if sub= sequent We need more text here, but I think that we can instead say "in response = to a Retry packet or the first Initial packet if receives from the server= ". > @@ -792,15 +875,36 @@ response to connection migration ({{migration}}).= NEW_CONNECTION_ID frames = The packet number is an integer in the range 0 to 2^62-1. The value is u= sed in determining the cryptographic nonce for packet encryption. Each endpoin= t -maintains a separate packet number for sending and receiving. The packe= t number -for sending MUST start at zero for the first packet sent and MUST increa= se by at -least one after sending a packet. +maintains a separate packet number for sending and receiving. + +Packet numbers are divided into 3 spaces in QUIC: + +- Initial space: All Initial packets {{packet-initial}} are in this spac= e. +- Handshake space: All Handshake packets {{packet-handshake}} are in thi= s space. +- Application data space: All 0-RTT and 1-RTT encrypted packets + {{packet-protected}} are in this space. + +As descibed in {{QUIC-TLS}}, each packet type uses different encryption = keys. typo: described > = -A QUIC endpoint MUST NOT reuse a packet number within the same connectio= n (that -is, under the same cryptographic keys). If the packet number for sendin= g -reaches 2^62 - 1, the sender MUST close the connection without sending a= -CONNECTION_CLOSE frame or any further packets; an endpoint MAY send a St= ateless -Reset ({{stateless-reset}}) in response to further packets that it recei= ves. +This enforces cryptographic separation between the data sent in the +different packet sequence number spaces. As a result, each packet numbe= r space s/As a result, // > @@ -1084,14 +1191,16 @@ solicit a list of supported versions from a ser= ver. = ## Cryptographic and Transport Handshake {#handshake} = -QUIC relies on a combined cryptographic and transport handshake to minim= ize -connection establishment latency. QUIC allocates stream 0 for the crypt= ographic -handshake. Version 0x00000001 of QUIC uses TLS 1.3 as described in -{{QUIC-TLS}}; a different QUIC version number could indicate that a diff= erent +QUIC relies on a combined cryptographic and transport handshake to +minimize connection establishment latency. QUIC uses the CRYPTO_HS +frame {frame-crypto} to transmit the cryptographic handshake. Version {{}} > cryptographic handshake protocol is in use. = -QUIC provides this stream with reliable, ordered delivery of data. In r= eturn, -the cryptographic handshake provides QUIC with: +QUIC provides the cryptographic handshake with reliable, ordered +delivery of data via the CRYPTO_HS frame. In return, the QUIC provides reliable, ordered delivery of the cryptographic handshake d= ata. QUIC packet protection ensures confidentiality and integrity protec= tion that meets the requirements of the cryptographic handshake protocol.= > @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with:= client can receive packets that are addressed with the transport addre= ss that is claimed by the client (see {{address-validation}}) = -The initial cryptographic handshake message MUST be sent in a single pac= ket. -Any second attempt that is triggered by address validation MUST also be = sent -within a single packet. This avoids having to reassemble a message from= -multiple packets. Reassembling messages requires that a server maintain= state -prior to establishing a connection, exposing the server to a denial of s= ervice -risk. +The CRYPTO_HS frame provides an offset and a length. QUIC functions +as the record encryption layer for the cryptographic protocol. With the above suggestion, drop this 'graph. > @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with:= client can receive packets that are addressed with the transport addre= ss that is claimed by the client (see {{address-validation}}) = -The initial cryptographic handshake message MUST be sent in a single pac= ket. -Any second attempt that is triggered by address validation MUST also be = sent -within a single packet. This avoids having to reassemble a message from= -multiple packets. Reassembling messages requires that a server maintain= state -prior to establishing a connection, exposing the server to a denial of s= ervice -risk. +The CRYPTO_HS frame provides an offset and a length. QUIC functions +as the record encryption layer for the cryptographic protocol. + +The initial CRYPTO_HS frame MUST be sent in a single packet. Any +second attempt that is triggered by address validation MUST also be +sent within a single packet. This avoids having to reassemble a +message from multiple packets. This duplicates the text from the next paragraph, partly. Maybe combine = them. No need to mention CRYPTO_HS here though. > = The first client packet of the cryptographic handshake protocol MUST fit= within a 1232 octet QUIC packet payload. This includes overheads that reduce t= he space available to the cryptographic handshake protocol. = -Details of how TLS is integrated with QUIC is provided in more detail in= -{{QUIC-TLS}}. +The CRYPTO_HS frame can be sent in different packet number spaces. +CRYPTO_HS frames in each packet number space carry a separate sequence +of handshake data starting from an offset of 0. This best goes with the description of the CRYPTO_HS frame. > + +## Example Handshake Flows + +Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},= +but we provide some examples here. + +{{tls-1rtt-handshake}} provides an overview of the 1-RTT handshake. +Each line shows a QUIC packet with the packet type and packet +number shown first, followed by the contents. So, for instance +the first packet is of type Initial, with packet number 0, and +contains a CRYPTO_HS frame carrying the ClientHello. + +Note that multiple QUIC packets -- even of different encryption levels +-- may be coalesced into a single UDP datagram (see +{{packet-coalesce}}, and so this handshake may consist of anywhere +from 4 to 9 UDP datagrams. For instance, the server's first flight Many more than 9 in the perverse case. Just say "as few as 4 UDP datagra= ms, or any number more". > +to increment from its 0-RTT packets. + +~~~~ +Client Server + +Initial[0]: CRYPTO_HS[CH] +0-RTT[0]: STREAM[0, "..."] -> + + Initial[0]: CRYPTO_HS[SH] ACK[0] + Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN] + <- 1-RTT[0]: STREAM[1, "..."] ACK[0] + +Initial[1]: ACK[0] +0-RTT[1]: CRYPTO_HS[EOED] +Handshake[0]: CRYPTO_HS[FIN], ACK[0] +1-RTT[2]: STREAM[0, "..."], ACK[0] -> Commas here separate frames, but you didn't use them elsewhere. > +to increment from its 0-RTT packets. + +~~~~ +Client Server + +Initial[0]: CRYPTO_HS[CH] +0-RTT[0]: STREAM[0, "..."] -> + + Initial[0]: CRYPTO_HS[SH] ACK[0] + Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN] + <- 1-RTT[0]: STREAM[1, "..."] ACK[0] + +Initial[1]: ACK[0] +0-RTT[1]: CRYPTO_HS[EOED] +Handshake[0]: CRYPTO_HS[FIN], ACK[0] +1-RTT[2]: STREAM[0, "..."], ACK[0] -> This needs to show the entire handshake, even if that means duplicating a= few things. The important things missing are ACKs for 0-RTT[1] and Hand= shake[0] from the client. > -port), a timestamp, and any other supplementary information the server= will need -to validate the token in the future. - -The cryptographic handshake is responsible for enacting validation by se= nding -the address validation token to the client. A legitimate client will in= clude a -copy of the token when it attempts to continue the handshake. The crypt= ographic -handshake extracts the token then asks QUIC a second time whether the to= ken is -acceptable. In response, QUIC can either abort the connection or permit= it to -proceed. +QUIC uses token-based address validation. Any time the server wishes +to validate a client address, it provides the client with a token. As +long as the token's authenticity can be checked (see +{{token-integrity}}) and the client is able to return that token, it +proves to the server that it received the token. + +If QUIC decides to request address validation for the current "During the handshake, a server can request address validation by sending= a Retry packet. The token included in the Retry are consumed by the[...= ]" > +long as the token's authenticity can be checked (see +{{token-integrity}}) and the client is able to return that token, it +proves to the server that it received the token. + +If QUIC decides to request address validation for the current +handshake, it encodes the token in a Retry packet. The contents of +this token are consumed by the server that generates the token, so +there is no need for a single well-defined format. A token could +include information about the claimed client address (IP and port), a +timestamp, and any other supplementary information the server will +need to validate the token in the future. + +The Retry packet is sent to the client and a legitimate client will +respond with an Initial packet containing the token from the Retry packe= t +when it continues the handshake. In response to receiving the token, a +QUIC server can either abort the connection or permit it to proceed. No need to qualify server here. I don't know why we had so much "QUIC" i= n the old text. > = A connection MAY be accepted without address validation - or with only l= imited validation - but a server SHOULD limit the data it sends toward an unval= idated address. Successful completion of the cryptographic handshake implicitl= y provides proof that the client has received packets from the server. = +The client should allow for additional Retry packets being sent in +response to Initial packets sent containing a token. There are several +situations in which the server might not be able to use the previously +generated token to validate the client's address and must send a new +Retry. A reasonable limit to the number of tries the client allows +for, before giving up, is 3. That is, the client SHOULD echo the +address validation token from a new Retry packet up to 3 times. After +that, it MAY give up on the connection attempt. I think that the SHOULD needs to be a MUST. That is, clients need to hav= e a minimum number of times they will pull on the thread before giving up= . No issue if they keep on pulling indefinitely, but servers need to be = able to rely on a certain number of retries working. > = A server MAY provide clients with an address validation token during one= connection that can be used on a subsequent connection. Address validat= ion is especially important with 0-RTT because a server potentially sends a sig= nificant amount of data to a client in response to 0-RTT data. = -A different type of token is needed when resuming. Unlike the token tha= t is -created during a handshake, there might be some time between when the to= ken is -created and when the token is subsequently used. Thus, a resumption tok= en -SHOULD include an expiration time. It is also unlikely that the client = port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c= lient +with an address validation token that can be used to validate future 0-R= TT +connections. The client may then use this token to validate future 0-RT= T drop "0-RTT" here. Of course this is most useful for 0-RTT, but the toke= n might also be used by servers with massive certificates or very large 0= .5 RTT flights in the same way. > @@ -2676,6 +2832,12 @@ QUIC acknowledgements are irrevocable. Once ack= nowledged, a packet remains acknowledged, even if it does not appear in a future ACK frame. This is= unlike TCP SACKs ({{?RFC2018}}). = +It is expected that a sender will reuse the same packet number across di= fferent +packet number spaces. ACK frames only acknowledge the packet numbers th= at were +transmitted by the sender in the same packet number space of the packet = that the +ACK was received in. This is an important property to allow for separat= ion +between the different packet number spaces. Delete the last sentence. There's no alternative to this design so this = needs no further justification. > @@ -2839,6 +3001,9 @@ is only sending ACK frames will only receive ackn= owledgements for its packets if the sender includes them in packets with non-ACK frames. A sender SH= OULD bundle ACK frames with other frames when possible. = +Implementations must be aware of the packet number space of the packet b= eing +transmitted and only acknowledge packets from that space. This is an odd statement. How about: "Endpoints can only acknowledge pac= kets sent in a particular packet number space by sending ACK frames in pa= ckets from the same packet number space." > @@ -2849,43 +3014,19 @@ received packets in preference to packets recei= ved in the past. = ### ACK Frames and Packet Protection = -ACK frames that acknowledge protected packets MUST be carried in a packe= t that -has an equivalent or greater level of packet protection. - -Packets that are protected with 1-RTT keys MUST be acknowledged in packe= ts that -are also protected with 1-RTT keys. - -A packet that is not protected and claims to acknowledge a packet number= that -was sent with packet protection is not valid. An unprotected packet tha= t -carries acknowledgments for protected packets MUST be discarded in its e= ntirety. +ACK frames MUST only be carried in a packet that has the same packet The MUST isn't useful here. It's not an interoperability requirement, be= cause there is no alternative. "ACK frames only acknowledge packets from the same packet number space as= the packet that carries them. For instance, ...." > -messages in the next unprotected packet that it sends, unless it is ab= le to -acknowledge those packets in later packets protected by 1-RTT keys. At = the -completion of the cryptographic handshake, both peers send unprotected p= ackets -containing cryptographic handshake messages followed by packets protecte= d by -1-RTT keys. An endpoint SHOULD acknowledge the unprotected packets that = complete -the cryptographic handshake in a protected packet, because its peer is -guaranteed to have access to 1-RTT packet protection keys. - -For instance, a server acknowledges a TLS ClientHello in the packet that= carries -the TLS ServerHello; similarly, a client can acknowledge a TLS HelloRetr= yRequest -in the packet containing a second TLS ClientHello. The complete set of = server -handshake messages (TLS ServerHello through to Finished) might be acknow= ledged -by a client in protected packets, because it is certain that the server = is able -to decipher the packet. - +Implementations SHOULD aggressively ACK packets containing CRYPTO_HS fra= mes. Endpoints SHOULD send acknowledgments for packets containing CRYPTO_HS fr= ames with a reduced delay; see Section 3.5.1 of {{RECOVERY}}. > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endp= oint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. = = +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a = token to +send in a the header of an Initial packet for a future 0-RTT connection.= ~~0-RTT~~ > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endp= oint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. = = +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a = token to +send in a the header of an Initial packet for a future 0-RTT connection.= + +The NEW_TOKEN frame is as follows: + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... Alignment > + +Offset: + +: A variable-length integer specifying the byte offset in the stream for= the + data in this CRYPTO_HS frame. + +Length: + +: A variable-length integer specifying the length of the Crypto Data fie= ld in + this CRYPTO_HS frame. + +Crypto Data: + +: The cryptographic message data. + +There is a separate flow of cryptographic handshake data in each Missing context: "CRYPTO_HS frames are functionally identical to STREAM f= rames, except that they do not bear a stream identifier; they are not flo= w controlled; and they do not carry markers for optional offset, optional= , length, and the end of the stream." > +: A variable-length integer specifying the length of the Crypto Data f= ield in + this CRYPTO_HS frame. + +Crypto Data: + +: The cryptographic message data. + +There is a separate flow of cryptographic handshake data in each +encryption level, each of which starts at an offset of 0. This implies +that each encryption level is treated as a separate CRYPTO_HS stream +of data. + +Unlike STREAM frames, which include a Stream ID indicating to which +stream the data belongs, the CRYPTO_HS frame carries data for a single +stream per encryption level. The stream does not have an explicit +end, so CRYPTO_HS frames do not have a FIN bit. What do we do about extra Handshake messages on old epochs? Those could = be added to every epoch indefinitely, if it weren't for the fact that TLS= would choke. But I'm not entirely sure that it would choke if the hands= hake message were chosen carefully. > @@ -3299,8 +3532,7 @@ The two type bits from a Stream ID therefore iden= tify streams as summarized in | 0x3 | Server-Initiated, Unidirectional | {: #stream-id-types title=3D"Stream ID Types"} = -Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is us= ed for -the cryptographic handshake. Stream 0 MUST NOT be used for application = data. +The first bi-directional stream opened by the client is stream 0. I'd double down and make this comprehensive. We might have confusion abo= ut whether 0 is allowed if we don't say at least this much. > @@ -3733,9 +3958,9 @@ Stream flow control, which prevents a single stre= am from consuming the entire receive buffer for a connection. = A data receiver sends MAX_STREAM_DATA or MAX_DATA frames to the sender -to advertise additional credit. MAX_STREAM_DATA frames send the maximum -absolute byte offset of a stream, while MAX_DATA sends the maximum sum -of the absolute byte offsets of all streams other than stream 0. +to advertise additional credit. MAX_STREAM_DATA frames send the +maximum absolute byte offset of a stream, while MAX_DATA sends the +maximum of the sum of the absolute byte offsets of all streams. =F0=9F=91=8D = -- = 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/1450#pullrequestreview-1292358= 05= ----==_mimepart_5b29e239e9c5a_18b02aca1febaf50640976 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@martinthomson approved this pull request.

At risk of this turning into a unicorn, here are my comments. I don't= think that you need to address all of them, but I would appreciate you t= aking one pass through this so we don't have too many editorial landmines= to worry about later. Most are nitty, so they should be easy to fix; ot= hers I'm happy to punt on.

On the renaming of frames and the removal of CRYPTO_CLOSE, I think tha= t we can easily make that sort of change later. And I plan to do so.

=

An appeal to those commenting on this PR. This is almost at the point= that GitHub is going to choke on it, if it doesn't start doing that alre= ady. If you have nits, questions, or responses to others comments, pleas= e refrain from adding to the pile of comments. If you think that there i= s a substantive issue that this PR creates, please open an issue.

=

In draft-ietf-quic-recovery.md:

> @@ -107,7 +111,7 @@ important to the loss =
detection and congestion control machinery below.
 * Retransmittable packets are those that contain at least one
   retransmittable frame.
 =

-* Crypto handshake data is sent on stream 0, and uses the reliability
+* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliab=
ility

s/CRYPTO_HS/CRYPTO/g

Yes, I understand that there is a message that carries a TLS alert, bu= t I don't think that's ideal. If we want to carry alerts, we can pack th= e range of cryptographic alerts into the CONNECTION_CLOSE space, or recom= mend that the reason phrase start with the alert.

In draft-ietf-quic-recovery.md:

> @@ -120,6 +124,17 @@ algorithms here that =
parallel well-known TCP ones. Protocol differences between
 QUIC and TCP however contribute to algorithmic differences. We briefly d=
escribe
 these protocol differences below.
 =

+### Separate Packet Number Spaces
+
+QUIC uses separate packet number spaces for each encryption level, excep=
t that
+0-RTT and all generations of 1-RTT keys use the same packet number space=
.
+Separating the spaces allows the recovery mechanisms to work without spe=
cial
+cases to avoid spuriously retransmitting un-processable packets.

This really doesn't say why. I think that you want to say that separa= ting the spaces ensures that packets from different spaces, which can't b= e decrypted, could trigger spurious retransmission.

In draft-ietf-quic-recovery.md:

> @@ -120,6 +124,17 @@ algorithms here that =
parallel well-known TCP ones. Protocol differences between
 QUIC and TCP however contribute to algorithmic differences. We briefly d=
escribe
 these protocol differences below.
 =

+### Separate Packet Number Spaces
+
+QUIC uses separate packet number spaces for each encryption level, excep=
t that
+0-RTT and all generations of 1-RTT keys use the same packet number space=
.
+Separating the spaces allows the recovery mechanisms to work without spe=
cial
+cases to avoid spuriously retransmitting un-processable packets.
+Separate packet number spaces do not imply separate paths. Consequently,=

I don't think that you need to talk about separate paths. It opens mor= e questions than it answers.

In draft-ietf-quic-recovery.md:

>  =

-Handshake packets, which contain STREAM frames for stream 0, are critica=
l to
-QUIC transport and crypto negotiation, so a separate alarm is used for t=
hem.
+Data in CRYPTO_HS frames is critical to QUIC transport and crypto negoti=
ation,
+so a more aggressive timeout is used to retransmit it.  Below, the word
+handshake packet is used to refer to packets containing CRYPTO_HS frames=
,
+not packets with the specific long header packet type Handshake.

This h/H thing is not ideal, but we don't need to fix it before landin= g this.

In draft-ietf-quic-recovery.md:

>  =

-When the alarm fires, the sender MUST retransmit all unacknowledged hand=
shake
-data, by calling RetransmitAllUnackedHandshakeData(). On each consecutiv=
e
-firing of the handshake alarm, the sender SHOULD double the handshake ti=
meout
-and set an alarm for this period.
+When the alarm fires, the sender MUST retransmit all unacknowledged CRYP=
TO_HS

This needs to be in the same paragraph as the previous.

In draft-ietf-quic-recovery.md:

> @@ -422,6 +439,14 @@ sending any ACK frame=
s in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 =

+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+should use a very short ack delay, such as 1ms.  ACK frames may be

SHOULD? and (later) MAY?

is it "ack delay" or "ACK delay"?

don't abbreviate crypto (that means cryptocurrency, dinchano?)

In draft-ietf-quic-recovery.md:

> @@ -559,6 +584,8 @@ sent_packets:
   was sent, a boolean indicating whether the packet is ack only, and a b=
ytes
   field indicating the packet's size.  sent_packets is ordered by pa=
cket
   number, and packets remain in sent_packets until acknowledged or lost.=

+  A sent_packets data structure is maintained per packet number space, a=
nd ack

ACK

In draft-ietf-quic-recovery.md:

> @@ -422,6 +439,14 @@ sending any ACK frame=
s in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 =

+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+should use a very short ack delay, such as 1ms.  ACK frames may be
+sent immediately when the crypto stack indicates all data for that
+encryption level has been received.
+

The full implications of the change to multiple packet number spaces d= oesn't seem to be present here. Shouldn't this say something about RTO a= s well? If I understand the design, packets sent with handshake and init= ial keys are retransmitted on this timer only, not RTO.

The awkward thing here is that this seems to lead to EndOfEarlyData be= ing retransmitted on RTO, not the handshake timer. We need an issue for = chasing that down.

In draft-ietf-quic-tls.md:

> +One important difference between TLS 1.3 =
records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.=

+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption

not MUST, can

In draft-ietf-quic-tls.md:

> +same encryption level. For instance, an i=
mplementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.=

+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.

The list here is accurate, but we can consider rotating it later.

In draft-ietf-quic-tls.md:

> +data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.=

+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet

s/may/could/

In draft-ietf-quic-tls.md:

> +- All other frame types MUST only appear =
at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.
+
+| Packet Type     | Encryption Level |
+|:----------------|:-----------------|
+| Initial         | Initial secrets  |
+| 0-RTT Protected | 0-RTT            |
+| Handshake       | Handshake        |
+| Retry           | N/A              |
+| Short Header    | 1-RTT            |
+{: #packet-types-levels title=3D"Encryption Levels by Packet Type&q=
uot;}

Any sense extending this to include packet number spaces?

In draft-ietf-quic-tls.md:

> +Because packets may be reordered on the w=
ire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.
+
+| Packet Type     | Encryption Level |
+|:----------------|:-----------------|
+| Initial         | Initial secrets  |
+| 0-RTT Protected | 0-RTT            |
+| Handshake       | Handshake        |
+| Retry           | N/A              |
+| Short Header    | 1-RTT            |
+{: #packet-types-levels title=3D"Encryption Levels by Packet Type&q=
uot;}
+
+{{QUIC-TRANSPORT}}; Section 6.3 shows how packets at the various encrypt=
ion

Section 6.3 of [...], or use a comma

In draft-ietf-quic-tls.md:

> -A QUIC server starts the process by provi=
ding TLS with stream 0 octets.
-
-Each time that an endpoint receives data on stream 0, it delivers the oc=
tets to
-TLS if it is able.  Each time that TLS is provided with new data, new ha=
ndshake
-octets are requested from TLS.  TLS might not provide any octets if the
-handshake messages it has received are incomplete or it has no data to s=
end.
-
-At the server, when TLS provides handshake octets, it also needs to indi=
cate
-whether the octets contain a HelloRetryRequest.  A HelloRetryRequest MUS=
T always
-be sent in a Retry packet, so the QUIC server needs to know whether the =
octets
-are a HelloRetryRequest.
+A QUIC server starts the process by providing TLS with the client's
+handshake octets.
+
+At any given time, an endpoint will have a current sending encryption
+level and receiving encryption level. Each encryption level is

I don't think that we need this sentence any more. If you consider th= at TLS provides octets that are explicitly destined for a particular epoc= h and that each epoch is clearly identified by the type of packet, then y= ou only need to concern yourself with routing to the correct epoch. This= doesn't have to follow the strict linear regime that TLS assumes, which = in any case is detrimental when you consider the potential for reordering= .

It's fine to mention that later epochs might not be available early on= and then (separately) saying that epochs can be discarded when they aren= 't needed.

In draft-ietf-quic-tls.md:

> +will eventually be transmitted under the =
then-current key.
+
+When an endpoint receives a QUIC packet containing a CRYPTO_HS frame fro=
m
+the network, it proceeds as follows:
+
+- If the packet was in the current receiving encryption level, sequence
+  the data into the input flow as usual. As with STREAM frames,
+  the offset is used to find the proper location in the data sequence.
+  If the result of this process is that new data is available, then
+  it is delivered to TLS.
+
+- If the packet is from a previously installed encryption level, it
+  MUST not contain data which extends past the end of previously
+  received data in that flow. Implementations MUST treat any
+  violations of this requirement as a connection error of type
+  PROTOCOL_VIOLATION.

I don't think that this works. Consider EndOfEarlyData, which could b= e lost, then later repaired. The end of the previously installed encrypt= ion level (aside from being only loosely defined) for CRYPTO is 0, so EOE= D would extend past that. Also, if you take a looser interpretation, the= n a delayed 0-RTT STREAM frame might also extend that stream beyond the p= oint where the server cut over to reading Handshake or 1-RTT.

In draft-ietf-quic-tls.md:

> @@ -440,102 +433,63 @@ Important:
   STREAM frame that carries the Finished message in multiple packets.  T=
his
   enables immediate server processing for those packets.
 =

+### Encryption Level Changes

As above, rather than casting these as changes, it might be better to = concentrate on availability of keys and how TLS targets particular keys.<= /p>

For most frames, the notion of current level doesn't matter: you send = in the latest 1-RTT if you can, 0-RTT if you can't otherwise, and don't s= end at all otherwise.

In draft-ietf-quic-tls.md:

>                                           =
          Get Handshake
-                                                1-RTT Keys Ready
-                     <--- send/receive ---
+                      <------------ Initial
+                                          Rekey rx to 0-RTT keys

Consistent with the above, I don't think that we need to "rekey" recep= tion, but rather install those keys and make them available.

The same applies to rekeying for transmission really.

This diagram is somewhat useful, but we should have text that it is on= ly indicative, and that keys are selected based on the type of content be= ing sent, or based on the type of packet that was received.

In draft-ietf-quic-tls.md:

>  =

-QUIC uses a system of packet protection secrets, keys and IVs that are m=
odelled
-on the system used in TLS {{!TLS13}}.  The secrets that QUIC uses
-as the basis of its key schedule are obtained using TLS exporters (see S=
ection
-7.5 of {{!TLS13}}).
+A client that attempts 0-RTT MUST also consider 0-RTT to be rejected if =
it
+receives a Version Negotiation packet.

... or Retry.

In draft-ietf-quic-tls.md:

>  =

-~~~
-struct {
-   uint16 length =3D Length;
-   opaque label<6..255> =3D "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the T=
LS
+handshake, using the AEAD algorithm negotiated by TLS.

Seems fine to me.

In draft-ietf-quic-tls.md:

> -   uint16 length =3D Length;
-   opaque label<6..255> =3D "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the T=
LS
+handshake, using the AEAD algorithm negotiated by TLS.
+
+
+## QUIC Packet Encryption Keys {#encryption-keys}
+
+QUIC derives packet encryption keys in the same way as TLS 1.3:
+Each encryption level/direction pair has a secret value, which
+is then used to derive the traffic keys using as described
+in {{TLS13}}; Section 7.3.

Section 7.3 of

In draft-ietf-quic-tls.md:

>  =

+The keys for the remaining encryption level are computed in the same
+fashion as the corresponding TLS keys (see {{TLS13}}; Section 7),
+except that the label for HKDF-Expand-Label uses the prefix "quic &=
quot;
+rather than "tls 13". The purpose of this change is to provide=
 key
+separation between TLS and QUIC, so that TLS stacks can avoid
+exposing TLS record protection keys.

I don't think that we need this separation. Isn't the fact that this = is a QUIC connection separation enough? The same TLS connection can't be= used to key TLS record protection on a TCP connection.

If this remains, then we need to ensure that this is only ever the fin= al derivation (those with "key" and "iv"). Otherwise, there might be con= fusion about the label provided to Derive-Secret as well.

In draft-ietf-quic-tls.md:

>  =

-Packets that carry the TLS handshake (Initial, Retry, and Handshake) are=

-protected with a secret derived from the Destination Connection ID field=
 from
-the client's Initial packet.  Specifically:
+Initial packets are protected with
+a secret derived from the Destination Connection ID field from the clien=
t's
+Initial packet.  Specifically:

Well, not entirely. If the client changes the destination connection = ID in response to Retry, then the packets will be protected with keys der= ived from that value. Where this gets hairy is the Initial packets that = the client needs to send after the server sends ServerHello or HelloRetry= Request, the first of which can change the destination connection ID.

=

ACK frames in Initial packets will probably then need to use the updat= ed connection ID, and keys derived from the first Initial packet sent. T= hat's fine. But if this is another ClientHello and we require the same r= ules, then we're preventing the use of a stateless HelloRetryRequest.

=

In draft-ietf-quic-tls.md:

> @@ -873,26 +673,20 @@ from the packet numb=
er.
 All QUIC packets other than Version Negotiation and Stateless Reset pack=
ets are
 protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shar=
ed
 secret, packets are protected with AEAD_AES_128_GCM and a key derived fr=
om the
-client's connection ID (see {{handshake-secrets}}).  This provides p=
rotection
+client's connection ID (see {{initial-secrets}}).  This provides pro=
tection

or "from the destination connection ID in the client's first Initial p= acket (see ..."

In draft-ietf-quic-tls.md:

> @@ -1024,144 +795,90 @@ encrypted_pn =3D C=
haCha20(pn_key, counter, nonce, packet_number)
 =

 ## Receiving Protected Packets
 =

-Once an endpoint successfully receives a packet with a given packet numb=
er, it
-MUST discard all packets with higher packet numbers if they cannot be
-successfully unprotected with either the same key, or - if there is a ke=
y update
-- the next packet protection key (see {{key-update}}).  Similarly, a pac=
ket that
-appears to trigger a key update, but cannot be unprotected successfully =
MUST be
-discarded.
+Once an endpoint successfully receives a packet with a given packet
+number, it MUST discard all packets in the same packet number space
+with higher packet numbers if they cannot be successfully unprotected
+with either the same key, or - if there is a key update - the next
+packet protection key (see {{key-update}}).  Similarly, a packet that
+appears to trigger a key update, but cannot be unprotected
+successfully MUST be discarded.

Unfortunately this doesn't work with 0-RTT, because we need reliable t= ransmission of EndOfEarlyData. That probably just needs a carve-out.

=

In draft-ietf-quic-tls.md:

>  =

-A server might choose to retain 0-RTT packets that arrive before a TLS
-ClientHello.  The server can then use those packets once the ClientHello=

-arrives.  However, the potential for denial of service from buffering 0-=
RTT
-packets is significant.  These packets cannot be authenticated and so mi=
ght be
-employed by an attacker to exhaust server resources.  Limiting the numbe=
r of
-packets that are saved might be necessary.
+A client MUST only use 0-RTT keys to protect data that is idempotent.  A=
 client
+MAY wish to apply additional restrictions on what data it sends prior to=
 the
+completion of the TLS handshake.  A client otherwise treats 0-RTT keys a=
s
+equivalent to 1-RTT keys, except that ACKs for that data MUST only be se=
nt with
+1-RTT keys.

"A server uses 1-RTT keys to protect acknowledgements of 0-RTT packets= ."

In draft-ietf-quic-tls.md:

>  =

-### Retransmission and Acknowledgment of Unprotected Packets
+: 0-RTT data can be acknowledged by the server as it receives it, but an=
y

Either that or make it a note.

It's a shame we can't just use Handshake keys for those acknowledgment= s, but that would require a change in the design.

In draft-ietf-quic-tls.md:

>  =

-Once 1-RTT keys are available to an endpoint, it no longer needs the TLS=

-handshake messages that are carried in unprotected packets.  However, a =
server
-might need to retransmit its TLS handshake messages in response to recei=
ving an
-unprotected packet that contains ACK frames.  A server MUST process ACK =
frames
-in unprotected packets until the TLS handshake is reported as complete, =
or it
-receives an ACK frame in a protected packet that acknowledges all of its=

-handshake messages.
+Receiving and verifying the TLS Finished message is critical in
+ensuring the integrity of the TLS handshake.  A server MUST NOT use
+1-RTT protected packets from the client prior to verifying the client
+Finished message if its response depends on client authentication.

Let's drop this one. No point in getting into the client authenticati= on thing.

In draft-ietf-quic-tls.md:

>  =

-## Key Update {#key-update}
+Once the 1-RTT keys are established and the short header is in use, it
+is possible to update the keys, for instance because of limits on AEAD
+encryption.  The KEY_PHASE bit in the short header is used to indicate

This "for instance" is a little stilted. I don't have a good suggesti= on right now though.

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHell=
o that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic g=
enerated
 by an attacker.
 =

-Certificate caching {{?RFC7924}} can reduce the size of the server's=
 handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a mi=
nimum
-size.  A server is less likely to generate a packet reflection attack if=
 the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is like=
ly to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};

We concluded that this wasn't packets, but UDP datagrams.

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHell=
o that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic g=
enerated
 by an attacker.
 =

-Certificate caching {{?RFC7924}} can reduce the size of the server's=
 handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a mi=
nimum
-size.  A server is less likely to generate a packet reflection attack if=
 the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is like=
ly to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};
+Section 4.4.3). Finally, because ACKs of Handshake packets

s/ACKs/acknowledgments/ (to allow for ACK_ECN)

In draft-ietf-quic-transport.md:

>  =

 =

 ### Initial Packet {#packet-initial}
 =

 The Initial packet uses long headers with a type value of 0x7F.  It carr=
ies the
-first cryptographic handshake message sent by the client.
+first CRYPTO_HS frames sent by the client as well as the
+cryptographic messages sent by the server to perform key exchange. The I=
nitial

Any sense mentioning acknowledgments here?

In draft-ietf-quic-transport.md:

>  =

-If the client received a Retry packet and is sending a second Initial pa=
cket,
-then it sets the Destination Connection ID to the value from the Source
-Connection ID in the Retry packet.  Changing Destination Connection ID a=
lso
-results in a change to the keys used to protect the Initial packet.
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...

Check alignment.

In draft-ietf-quic-transport.md:

> -results in a change to the keys used to p=
rotect the Initial packet.
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                            Token (*)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+Token Length:
+
+: A variable-length integer specifying the length of the Token field, in=
 bytes.
+It may be zero if no token is present. The server MUST send a zero-lengt=
h
+token.

Initial packets sent by the server MUST include a zero-length token.

In draft-ietf-quic-transport.md:

> +|        Token Length (i)  ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                            Token (*)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+Token Length:
+
+: A variable-length integer specifying the length of the Token field, in=
 bytes.
+It may be zero if no token is present. The server MUST send a zero-lengt=
h
+token.
+
+Token:
+
+: An optional token blob previously received in either a Retry packet or=

+NEW_TOKEN frame.

Is the client required to include a token on every Initial packet that= it sends, including ones that include only ACK frames, or is it only the= first and any that are sent in response to Retry?

Interestingly, if you take the first+Retry rule, then that matches nea= tly with the rules about which destination connection ID is used to deter= mine keys.

In draft-ietf-quic-transport.md:

> +
+A server sends its first Initial packet in response to a client Initial.=
  A
+server may send multiple Initial packets.  The cryptographic key exchang=
e could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete
+first message MUST fit in a single packet (see {{handshake}}). Note that=
 if
+the server sends a HelloRetryRequest, the client will send a second Init=
ial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously r=
eceived

an an

In draft-ietf-quic-transport.md:

> +server may send multiple Initial packets.=
  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client'=
;s complete
+first message MUST fit in a single packet (see {{handshake}}). Note that=
 if
+the server sends a HelloRetryRequest, the client will send a second Init=
ial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously r=
eceived
+a Retry packet from the server, it populates the Destination Connection =
ID field
+with a randomly selected value.  This MUST be at least 8 octets in lengt=
h. Until

We've agreed to "unpredictable" in other such cases rather than "rando= mly".

In draft-ietf-quic-transport.md:

>  =

 The client populates the Source Connection ID field with a value of its =
choosing
 and sets the SCIL field to match.
 =

-The first Initial packet that is sent by a client contains a packet numb=
er of 0.
-All subsequent packets contain a packet number that is incremented by at=
 least
-one, see ({{packet-numbers}}).
-
-The payload of an Initial packet conveys a STREAM frame (or frames) for =
stream
-0 containing a cryptographic handshake message.  The stream in this pack=
et
-always starts at an offset of 0 (see {{stateless-retry}}) and the comple=
te
-cryptographic handshake message MUST fit in a single packet (see {{hands=
hake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection

This consistency requirement seems to be under debate. We're currentl= y gravitating toward a requirement to change the value on (almost) every = Retry, and then allowing the first Initial packet from the server to set = a new value. Only after that can it be consistent.

In draft-ietf-quic-transport.md:

> -
-The payload of an Initial packet conveys a STREAM frame (or frames) for =
stream
-0 containing a cryptographic handshake message.  The stream in this pack=
et
-always starts at an offset of 0 (see {{stateless-retry}}) and the comple=
te
-cryptographic handshake message MUST fit in a single packet (see {{hands=
hake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection
+IDs during the handshake.
+
+On first receiving an Initial or Retry packet from the server, the
+client uses the Source Connection ID supplied by the server as the
+Destination Connection ID for subsequent packets. The client MUST
+discard any subsequent packets it receives with different

Perhaps: "Once a client has received an Initial packet from the server= , it MUST discard any packet it receives with a different Source Connecti= on ID."

In draft-ietf-quic-transport.md:

> +ID that the sender of the packet wishes t=
o use (see
+{{connection-id}}). The server MUST use consistent Source Connection
+IDs during the handshake.
+
+On first receiving an Initial or Retry packet from the server, the
+client uses the Source Connection ID supplied by the server as the
+Destination Connection ID for subsequent packets. The client MUST
+discard any subsequent packets it receives with different
+Source Connection IDs.
+
+#### Tokens
+
+If the client has a suitable token available from a previous connection,=

+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an

This paragraph doesn't belong here really. It's part of the descripti= on of Retry.

In draft-ietf-quic-transport.md:

> +
+#### Tokens
+
+If the client has a suitable token available from a previous connection,=

+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID t=
o
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated

We can't assume retention of keys, but we can provide some recommendat= ions. If tokens are clearly marked as NEW_TOKEN vs. Retry, then the form= er might be old and broken, so treating that as equivalent to an absent t= oken is reasonable. For the latter, Retry might be verifiable. If somet= hing is clearly a Retry token, then dropping the connection seems OK.

=

Needs more text.

In draft-ietf-quic-transport.md:

> +
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID t=
o
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated
+address, including potentially sending a Retry. If the validation
+succeeds, the server SHOULD then allow the handshake to proceed (see
+{{stateless-retry}}).
+
+Note: The rationale for treating the client as unvalidated rather

Formatting for notes is generally to use a definition list:

Note:
: The rationale ...

In draft-ietf-quic-transport.md:

> +address, including potentially sending a =
Retry. If the validation
+succeeds, the server SHOULD then allow the handshake to proceed (see
+{{stateless-retry}}).
+
+Note: The rationale for treating the client as unvalidated rather
+than discarding the packet is that the client might have received
+the token in a previous connection using the NEW_TOKEN message,
+and if the server has lost state, it might be unable to validate
+the token at all, leading to connection failure if the packet
+is discarded.
+
+#### Starting Packet Numbers
+
+The first Initial packet contains a packet number of 0. Each packet sent=
 after
+the Initial packet is associated with a packet number space and its pack=
et
+number increases monotonically in that space (see {{packet-numbers}}).

Do you start at zero again if you change the connection ID? I don't t= hink you do, but it might help to be clear on this point.

In draft-ietf-quic-transport.md:

>  =

 ### Retry Packet {#packet-retry}
 =

-A Retry packet uses long headers with a type value of 0x7E.  It carries
-cryptographic handshake messages and acknowledgments.  It is used by a s=
erver
-that wishes to perform a stateless retry (see {{stateless-retry}}).
+A Retry packet uses long headers with a type value of 0x7E. It carries a=
n
+address validation token created by the server. It is used by a server t=
hat
+wishes to perform a stateless retry (see {{stateless-retry}}).
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|     DCIL(8)   |      Original Destination Connection ID (*)   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        Retry Token (*)

...

In draft-ietf-quic-transport.md:

>  =

 ### Retry Packet {#packet-retry}
 =

-A Retry packet uses long headers with a type value of 0x7E.  It carries
-cryptographic handshake messages and acknowledgments.  It is used by a s=
erver
-that wishes to perform a stateless retry (see {{stateless-retry}}).
+A Retry packet uses long headers with a type value of 0x7E. It carries a=
n
+address validation token created by the server. It is used by a server t=
hat
+wishes to perform a stateless retry (see {{stateless-retry}}).
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|     DCIL(8)   |      Original Destination Connection ID (*)   |

ODCIL ?

In draft-ietf-quic-transport.md:

>  =

-Continuing the cryptographic handshake is necessary to ensure that an at=
tacker
-cannot force a downgrade of any cryptographic parameters.  In addition t=
o
-continuing the cryptographic handshake, the client MUST remember the res=
ults of
-any version negotiation that occurred (see {{version-negotiation}}).  Th=
e client
-MAY also retain any observed RTT or congestion state that it has accumul=
ated for
-the flow, but other transport state MUST be discarded.
+If the Original Destination Connection ID field does not match the
+Destination Connection ID from the Initial packet it sent, clients MUST

"most recent Initial packet" (this will also help with the other probl= em we have)

In draft-ietf-quic-transport.md:

>  =

-After receiving a Retry packet, the client uses a new
-Initial packet containing the next cryptographic handshake message.  The=
 client
-retains the state of its cryptographic handshake, but discards all trans=
port
-state.  The Initial packet that is generated in response to a Retry pack=
et
-includes STREAM frames on stream 0 that start again at an offset of 0.
+A server MUST only send a Retry in response to a client Initial packet.

Do we need to include a minimum size constraint here as well? A Retry= that is sent in response to an ACK frame is just weird.

In draft-ietf-quic-transport.md:

>  =

-The payload of the Retry packet contains at least two frames. It MUST in=
clude a
-STREAM frame on stream 0 with offset 0 containing the server's crypt=
ographic
-stateless retry material. It MUST also include an ACK frame to acknowled=
ge the
-client's Initial packet. It MAY additionally include PADDING frames.=
 The next
-STREAM frame sent by the server will also start at stream offset 0.
+Otherwise, the client SHOULD respond with a new Initial
+packet with the Token field set to the token received in the Retry packe=
t.

Following the above thought, I think that we need to prohibit this rea= ction from clients if they have received an Initial packet from the serve= r.

In draft-ietf-quic-transport.md:

> @@ -761,7 +844,7 @@ During the handshake, =
an endpoint might receive multiple packets with the long
 header, and thus be given multiple opportunities to update the Destinati=
on
 Connection ID it sends.  A client MUST only change the value it sends in=
 the
 Destination Connection ID in response to the first packet of each type i=
t
-receives from the server (Retry or Handshake); a server MUST set its val=
ue based
+receives from the server (Retry or Initial); a server MUST set its value=
 based
 on the Initial packet.  Any additional changes are not permitted; if sub=
sequent

We need more text here, but I think that we can instead say "in respon= se to a Retry packet or the first Initial packet if receives from the ser= ver".

In draft-ietf-quic-transport.md:

> @@ -792,15 +875,36 @@ response to connecti=
on migration ({{migration}}). NEW_CONNECTION_ID frames
 =

 The packet number is an integer in the range 0 to 2^62-1. The value is u=
sed in
 determining the cryptographic nonce for packet encryption.  Each endpoin=
t
-maintains a separate packet number for sending and receiving.  The packe=
t number
-for sending MUST start at zero for the first packet sent and MUST increa=
se by at
-least one after sending a packet.
+maintains a separate packet number for sending and receiving.
+
+Packet numbers are divided into 3 spaces in QUIC:
+
+- Initial space: All Initial packets {{packet-initial}} are in this spac=
e.
+- Handshake space: All Handshake packets {{packet-handshake}} are in thi=
s space.
+- Application data space: All 0-RTT and 1-RTT encrypted packets
+  {{packet-protected}} are in this space.
+
+As descibed in {{QUIC-TLS}}, each packet type uses different encryption =
keys.

typo: described

In draft-ietf-quic-transport.md:

>  =

-A QUIC endpoint MUST NOT reuse a packet number within the same connectio=
n (that
-is, under the same cryptographic keys).  If the packet number for sendin=
g
-reaches 2^62 - 1, the sender MUST close the connection without sending a=

-CONNECTION_CLOSE frame or any further packets; an endpoint MAY send a St=
ateless
-Reset ({{stateless-reset}}) in response to further packets that it recei=
ves.
+This enforces cryptographic separation between the data sent in the
+different packet sequence number spaces.  As a result, each packet numbe=
r space

s/As a result, //

In draft-ietf-quic-transport.md:

> @@ -1084,14 +1191,16 @@ solicit a list of =
supported versions from a server.
 =

 ## Cryptographic and Transport Handshake {#handshake}
 =

-QUIC relies on a combined cryptographic and transport handshake to minim=
ize
-connection establishment latency.  QUIC allocates stream 0 for the crypt=
ographic
-handshake.  Version 0x00000001 of QUIC uses TLS 1.3 as described in
-{{QUIC-TLS}}; a different QUIC version number could indicate that a diff=
erent
+QUIC relies on a combined cryptographic and transport handshake to
+minimize connection establishment latency.  QUIC uses the CRYPTO_HS
+frame {frame-crypto} to transmit the cryptographic handshake.  Version

{{}}

In draft-ietf-quic-transport.md:

>  cryptographic handshake protocol is in us=
e.
 =

-QUIC provides this stream with reliable, ordered delivery of data.  In r=
eturn,
-the cryptographic handshake provides QUIC with:
+QUIC provides the cryptographic handshake with reliable, ordered
+delivery of data via the CRYPTO_HS frame.  In return, the

QUIC provides reliable, ordered delivery of the cryptographic handshak= e data. QUIC packet protection ensures confidentiality and integrity pro= tection that meets the requirements of the cryptographic handshake protoc= ol.

In draft-ietf-quic-transport.md:

> @@ -1118,19 +1227,83 @@ the cryptographic =
handshake provides QUIC with:
   client can receive packets that are addressed with the transport addre=
ss that
   is claimed by the client (see {{address-validation}})
 =

-The initial cryptographic handshake message MUST be sent in a single pac=
ket.
-Any second attempt that is triggered by address validation MUST also be =
sent
-within a single packet.  This avoids having to reassemble a message from=

-multiple packets.  Reassembling messages requires that a server maintain=
 state
-prior to establishing a connection, exposing the server to a denial of s=
ervice
-risk.
+The CRYPTO_HS frame provides an offset and a length.  QUIC functions
+as the record encryption layer for the cryptographic protocol.

With the above suggestion, drop this 'graph.

In draft-ietf-quic-transport.md:

> @@ -1118,19 +1227,83 @@ the cryptographic =
handshake provides QUIC with:
   client can receive packets that are addressed with the transport addre=
ss that
   is claimed by the client (see {{address-validation}})
 =

-The initial cryptographic handshake message MUST be sent in a single pac=
ket.
-Any second attempt that is triggered by address validation MUST also be =
sent
-within a single packet.  This avoids having to reassemble a message from=

-multiple packets.  Reassembling messages requires that a server maintain=
 state
-prior to establishing a connection, exposing the server to a denial of s=
ervice
-risk.
+The CRYPTO_HS frame provides an offset and a length.  QUIC functions
+as the record encryption layer for the cryptographic protocol.
+
+The initial CRYPTO_HS frame MUST be sent in a single packet.  Any
+second attempt that is triggered by address validation MUST also be
+sent within a single packet. This avoids having to reassemble a
+message from multiple packets.

This duplicates the text from the next paragraph, partly. Maybe combi= ne them.

No need to mention CRYPTO_HS here though.

In draft-ietf-quic-transport.md:

>  =

 The first client packet of the cryptographic handshake protocol MUST fit=
 within
 a 1232 octet QUIC packet payload.  This includes overheads that reduce t=
he space
 available to the cryptographic handshake protocol.
 =

-Details of how TLS is integrated with QUIC is provided in more detail in=

-{{QUIC-TLS}}.
+The CRYPTO_HS frame can be sent in different packet number spaces.
+CRYPTO_HS frames in each packet number space carry a separate sequence
+of handshake data starting from an offset of 0.

This best goes with the description of the CRYPTO_HS frame.

In draft-ietf-quic-transport.md:

> +
+## Example Handshake Flows
+
+Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},=

+but we provide some examples here.
+
+{{tls-1rtt-handshake}} provides an overview of the 1-RTT handshake.
+Each line shows a QUIC packet with the packet type and packet
+number shown first, followed by the contents. So, for instance
+the first packet is of type Initial, with packet number 0, and
+contains a CRYPTO_HS frame carrying the ClientHello.
+
+Note that multiple QUIC packets -- even of different encryption levels
+-- may be coalesced into a single UDP datagram (see
+{{packet-coalesce}}, and so this handshake may consist of anywhere
+from 4 to 9 UDP datagrams.  For instance, the server's first flight

Many more than 9 in the perverse case. Just say "as few as 4 UDP data= grams, or any number more".

In draft-ietf-quic-transport.md:

> +to increment from its 0-RTT packets.
+
+~~~~
+Client                                                  Server
+
+Initial[0]: CRYPTO_HS[CH]
+0-RTT[0]: STREAM[0, "..."] ->
+
+                              Initial[0]: CRYPTO_HS[SH] ACK[0]
+                     Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN]
+                          <- 1-RTT[0]: STREAM[1, "..."] ACK=
[0]
+
+Initial[1]: ACK[0]
+0-RTT[1]: CRYPTO_HS[EOED]
+Handshake[0]: CRYPTO_HS[FIN], ACK[0]
+1-RTT[2]: STREAM[0, "..."], ACK[0] ->

Commas here separate frames, but you didn't use them elsewhere.

In draft-ietf-quic-transport.md:

> +to increment from its 0-RTT packets.
+
+~~~~
+Client                                                  Server
+
+Initial[0]: CRYPTO_HS[CH]
+0-RTT[0]: STREAM[0, "..."] ->
+
+                              Initial[0]: CRYPTO_HS[SH] ACK[0]
+                     Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN]
+                          <- 1-RTT[0]: STREAM[1, "..."] ACK=
[0]
+
+Initial[1]: ACK[0]
+0-RTT[1]: CRYPTO_HS[EOED]
+Handshake[0]: CRYPTO_HS[FIN], ACK[0]
+1-RTT[2]: STREAM[0, "..."], ACK[0] ->

This needs to show the entire handshake, even if that means duplicatin= g a few things. The important things missing are ACKs for 0-RTT[1] and H= andshake[0] from the client.

In draft-ietf-quic-transport.md:

> -port), a timestamp, and any other supplem=
entary information the server will need
-to validate the token in the future.
-
-The cryptographic handshake is responsible for enacting validation by se=
nding
-the address validation token to the client.  A legitimate client will in=
clude a
-copy of the token when it attempts to continue the handshake.  The crypt=
ographic
-handshake extracts the token then asks QUIC a second time whether the to=
ken is
-acceptable.  In response, QUIC can either abort the connection or permit=
 it to
-proceed.
+QUIC uses token-based address validation.  Any time the server wishes
+to validate a client address, it provides the client with a token.  As
+long as the token's authenticity can be checked (see
+{{token-integrity}}) and the client is able to return that token, it
+proves to the server that it received the token.
+
+If QUIC decides to request address validation for the current

"During the handshake, a server can request address validation by send= ing a Retry packet. The token included in the Retry are consumed by the[= ...]"

In draft-ietf-quic-transport.md:

> +long as the token's authenticity can =
be checked (see
+{{token-integrity}}) and the client is able to return that token, it
+proves to the server that it received the token.
+
+If QUIC decides to request address validation for the current
+handshake, it encodes the token in a Retry packet. The contents of
+this token are consumed by the server that generates the token, so
+there is no need for a single well-defined format.  A token could
+include information about the claimed client address (IP and port), a
+timestamp, and any other supplementary information the server will
+need to validate the token in the future.
+
+The Retry packet is sent to the client and a legitimate client will
+respond with an Initial packet containing the token from the Retry packe=
t
+when it continues the handshake.  In response to receiving the token, a
+QUIC server can either abort the connection or permit it to proceed.

No need to qualify server here. I don't know why we had so much "QUIC= " in the old text.

In draft-ietf-quic-transport.md:

>  =

 A connection MAY be accepted without address validation - or with only l=
imited
 validation - but a server SHOULD limit the data it sends toward an unval=
idated
 address.  Successful completion of the cryptographic handshake implicitl=
y
 provides proof that the client has received packets from the server.
 =

+The client should allow for additional Retry packets being sent in
+response to Initial packets sent containing a token. There are several
+situations in which the server might not be able to use the previously
+generated token to validate the client's address and must send a new=

+Retry. A reasonable limit to the number of tries the client allows
+for, before giving up, is 3. That is, the client SHOULD echo the
+address validation token from a new Retry packet up to 3 times. After
+that, it MAY give up on the connection attempt.

I think that the SHOULD needs to be a MUST. That is, clients need to = have a minimum number of times they will pull on the thread before giving= up. No issue if they keep on pulling indefinitely, but servers need to = be able to rely on a certain number of retries working.

In draft-ietf-quic-transport.md:

>  =

 A server MAY provide clients with an address validation token during one=

 connection that can be used on a subsequent connection.  Address validat=
ion is
 especially important with 0-RTT because a server potentially sends a sig=
nificant
 amount of data to a client in response to 0-RTT data.
 =

-A different type of token is needed when resuming.  Unlike the token tha=
t is
-created during a handshake, there might be some time between when the to=
ken is
-created and when the token is subsequently used.  Thus, a resumption tok=
en
-SHOULD include an expiration time.  It is also unlikely that the client =
port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the c=
lient
+with an address validation token that can be used to validate future 0-R=
TT
+connections.  The client may then use this token to validate future 0-RT=
T

drop "0-RTT" here. Of course this is most useful for 0-RTT, but the t= oken might also be used by servers with massive certificates or very larg= e 0.5 RTT flights in the same way.

In draft-ietf-quic-transport.md:

> @@ -2676,6 +2832,12 @@ QUIC acknowledgemen=
ts are irrevocable.  Once acknowledged, a packet remains
 acknowledged, even if it does not appear in a future ACK frame.  This is=
 unlike
 TCP SACKs ({{?RFC2018}}).
 =

+It is expected that a sender will reuse the same packet number across di=
fferent
+packet number spaces.  ACK frames only acknowledge the packet numbers th=
at were
+transmitted by the sender in the same packet number space of the packet =
that the
+ACK was received in.  This is an important property to allow for separat=
ion
+between the different packet number spaces.

Delete the last sentence. There's no alternative to this design so th= is needs no further justification.

In draft-ietf-quic-transport.md:

> @@ -2839,6 +3001,9 @@ is only sending ACK =
frames will only receive acknowledgements for its packets
 if the sender includes them in packets with non-ACK frames.  A sender SH=
OULD
 bundle ACK frames with other frames when possible.
 =

+Implementations must be aware of the packet number space of the packet b=
eing
+transmitted and only acknowledge packets from that space.

This is an odd statement. How about: "Endpoints can only acknowledge = packets sent in a particular packet number space by sending ACK frames in= packets from the same packet number space."

In draft-ietf-quic-transport.md:

> @@ -2849,43 +3014,19 @@ received packets i=
n preference to packets received in the past.
 =

 ### ACK Frames and Packet Protection
 =

-ACK frames that acknowledge protected packets MUST be carried in a packe=
t that
-has an equivalent or greater level of packet protection.
-
-Packets that are protected with 1-RTT keys MUST be acknowledged in packe=
ts that
-are also protected with 1-RTT keys.
-
-A packet that is not protected and claims to acknowledge a packet number=
 that
-was sent with packet protection is not valid.  An unprotected packet tha=
t
-carries acknowledgments for protected packets MUST be discarded in its e=
ntirety.
+ACK frames MUST only be carried in a packet that has the same packet

The MUST isn't useful here. It's not an interoperability requirement,= because there is no alternative.

"ACK frames only acknowledge packets from the same packet number space= as the packet that carries them. For instance, ...."

In draft-ietf-quic-transport.md:

> -messages in the next unprotected packet t=
hat it sends, unless it is able to
-acknowledge those packets in later packets protected by 1-RTT keys.  At =
the
-completion of the cryptographic handshake, both peers send unprotected p=
ackets
-containing cryptographic handshake messages followed by packets protecte=
d by
-1-RTT keys. An endpoint SHOULD acknowledge the unprotected packets that =
complete
-the cryptographic handshake in a protected packet, because its peer is
-guaranteed to have access to 1-RTT packet protection keys.
-
-For instance, a server acknowledges a TLS ClientHello in the packet that=
 carries
-the TLS ServerHello; similarly, a client can acknowledge a TLS HelloRetr=
yRequest
-in the packet containing a second TLS ClientHello.  The complete set of =
server
-handshake messages (TLS ServerHello through to Finished) might be acknow=
ledged
-by a client in protected packets, because it is certain that the server =
is able
-to decipher the packet.
-
+Implementations SHOULD aggressively ACK packets containing CRYPTO_HS fra=
mes.

Endpoints SHOULD send acknowledgments for packets containing CRYPTO_HS= frames with a reduced delay; see Section 3.5.1 of {{RECOVERY}}.

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE fram=
e previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 =

 =

+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a =
token to
+send in a the header of an Initial packet for a future 0-RTT connection.=

0-RTT

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE fram=
e previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 =

 =

+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=3D0x21) to provide the client a =
token to
+send in a the header of an Initial packet for a future 0-RTT connection.=

+
+The NEW_TOKEN frame is as follows:
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...

Alignment

In draft-ietf-quic-transport.md:

> +
+Offset:
+
+: A variable-length integer specifying the byte offset in the stream for=
 the
+  data in this CRYPTO_HS frame.
+
+Length:
+
+: A variable-length integer specifying the length of the Crypto Data fie=
ld in
+  this CRYPTO_HS frame.
+
+Crypto Data:
+
+: The cryptographic message data.
+
+There is a separate flow of cryptographic handshake data in each

Missing context: "CRYPTO_HS frames are functionally identical to STREA= M frames, except that they do not bear a stream identifier; they are not = flow controlled; and they do not carry markers for optional offset, optio= nal, length, and the end of the stream."

In draft-ietf-quic-transport.md:

> +: A variable-length integer specifying th=
e length of the Crypto Data field in
+  this CRYPTO_HS frame.
+
+Crypto Data:
+
+: The cryptographic message data.
+
+There is a separate flow of cryptographic handshake data in each
+encryption level, each of which starts at an offset of 0. This implies
+that each encryption level is treated as a separate CRYPTO_HS stream
+of data.
+
+Unlike STREAM frames, which include a Stream ID indicating to which
+stream the data belongs, the CRYPTO_HS frame carries data for a single
+stream per encryption level. The stream does not have an explicit
+end, so CRYPTO_HS frames do not have a FIN bit.

What do we do about extra Handshake messages on old epochs? Those cou= ld be added to every epoch indefinitely, if it weren't for the fact that = TLS would choke. But I'm not entirely sure that it would choke if the ha= ndshake message were chosen carefully.

In draft-ietf-quic-transport.md:

> @@ -3299,8 +3532,7 @@ The two type bits fr=
om a Stream ID therefore identify streams as summarized in
 | 0x3      | Server-Initiated, Unidirectional |
 {: #stream-id-types title=3D"Stream ID Types"}
 =

-Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is us=
ed for
-the cryptographic handshake.  Stream 0 MUST NOT be used for application =
data.
+The first bi-directional stream opened by the client is stream 0.

I'd double down and make this comprehensive. We might have confusion = about whether 0 is allowed if we don't say at least this much.

In draft-ietf-quic-transport.md:

> @@ -3733,9 +3958,9 @@ Stream flow control,=
 which prevents a single stream from consuming the entire
 receive buffer for a connection.
 =

 A data receiver sends MAX_STREAM_DATA or MAX_DATA frames to the sender
-to advertise additional credit. MAX_STREAM_DATA frames send the maximum
-absolute byte offset of a stream, while MAX_DATA sends the maximum sum
-of the absolute byte offsets of all streams other than stream 0.
+to advertise additional credit. MAX_STREAM_DATA frames send the
+maximum absolute byte offset of a stream, while MAX_DATA sends the
+maximum of the sum of the absolute byte offsets of all streams.

=F0=9F=91=8D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.

= = ----==_mimepart_5b29e239e9c5a_18b02aca1febaf50640976-- From nobody Tue Jun 19 22:13:47 2018 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 CE18213102E for ; Tue, 19 Jun 2018 22:13:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3eaJEg_l1H2Q for ; Tue, 19 Jun 2018 22:13:43 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8437E13102B for ; Tue, 19 Jun 2018 22:13:43 -0700 (PDT) Date: Tue, 19 Jun 2018 22:13:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529471622; bh=zCDd1JAzQtGgFiCHTKWON2HMsLmmIxS/lkcpEovWoa0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V67CyH5DnZd9Q43yUZbbLL5tWv9Y2X1+FqjLe4zHVDcyhfSz43KgqN8WqwQXS+9n4 S/xYrhn5pPXRSUFlCxaZ3mUqQsEK7lGRCGybiv1M2x0mcyOcLSjO4GSIBLKj+1mkpl ma2GKcrlkfK8NsVUTCrdFWl9OZTSkTKFkqLKJzNA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e286a73b4_43a42b17822aaf5c350b9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 05:13:45 -0000 ----==_mimepart_5b29e286a73b4_43a42b17822aaf5c350b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That's fine with me. It means that senders of Initial packets need to remember those octets, but it simplifies things (to the point that we don't need a length field even). -- 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/1451#issuecomment-398626480 ----==_mimepart_5b29e286a73b4_43a42b17822aaf5c350b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

That's fine with me. It means that senders of Initial packets need to remember those octets, but it simplifies things (to the point that we don't need a length field even).

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

----==_mimepart_5b29e286a73b4_43a42b17822aaf5c350b9-- From nobody Tue Jun 19 22:19:54 2018 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 1C6AA131032 for ; Tue, 19 Jun 2018 22:19:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ngpQdR3kCjUi for ; Tue, 19 Jun 2018 22:19:51 -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 DAE6513102F for ; Tue, 19 Jun 2018 22:19:51 -0700 (PDT) Date: Tue, 19 Jun 2018 22:19:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529471991; bh=rh7bTbmkqut50d89x8FHGWKi7/EC5QLgwheAAl1VwmU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nEYoVEYbEKKNkLi0xL7fhEy8DfxQQTbsr8dPkW5BlINxPeqj1pvaS+NT16vSkQBy9 wY9ti0q/2xZHjeGw/137PPNq7/5aewOLFvLxxnKX4JT0Ym9OGFHd96m498Dfcttdqg yOH5OmxQpqvoa5mkjyMbfBlZKn0pOY9Ysya9iCkI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e3f75ff0e_2f3ea3f9a2d890f88846bd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 05:19:53 -0000 ----==_mimepart_5b29e3f75ff0e_2f3ea3f9a2d890f88846bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The sender might not have access to the encrypted packet if delegates that part. -- 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/1451#issuecomment-398627329 ----==_mimepart_5b29e3f75ff0e_2f3ea3f9a2d890f88846bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The sender might not have access to the encrypted packet if delegates that part.

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

----==_mimepart_5b29e3f75ff0e_2f3ea3f9a2d890f88846bd-- From nobody Tue Jun 19 22:24:50 2018 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 2E1BF13103F for ; Tue, 19 Jun 2018 22:24:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 5nQIQtN47ruv for ; Tue, 19 Jun 2018 22:24:46 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57225131032 for ; Tue, 19 Jun 2018 22:24:46 -0700 (PDT) Date: Tue, 19 Jun 2018 22:24:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529472285; bh=DOuBwuE2w64Ff0tPCXb++wenZued+p0ehHqGNF3S9gU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F9OGDZgj7Jkkd9UkimfRSs2kEn17szrgATzuwJH8qpfr68GQFRGt5mD/nWA5SID6Y kj6/JvqC23U3Ez4KO0SBoxPThGCqgDjSTP3FJauXdnvdB5u69Cm4pm4v7NxSUg1Mek ycRY6/FVA+byj0DX+E15QwMFI9Zxj3XXf1Jx8Nqc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e51d7d155_43ac2b17822aaf5c44424"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 05:24:49 -0000 ----==_mimepart_5b29e51d7d155_43ac2b17822aaf5c44424 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, but don't do that then. -- 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/1451#issuecomment-398627975 ----==_mimepart_5b29e51d7d155_43ac2b17822aaf5c44424 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, but don't do that then.

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

----==_mimepart_5b29e51d7d155_43ac2b17822aaf5c44424-- From nobody Tue Jun 19 22:25:04 2018 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 2D8C513104A for ; Tue, 19 Jun 2018 22:25:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 9AjSCBty4hai for ; Tue, 19 Jun 2018 22:25:00 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97C03131045 for ; Tue, 19 Jun 2018 22:25:00 -0700 (PDT) Date: Tue, 19 Jun 2018 22:24:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529472299; bh=qPiA7yk7b3FZe7iToe4nzdNlBjDR6kamrFz1bul899I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xvSZHAo/fGr+W3UJEhUFBT8DY5w5g5M8IPtC1iUU8u9mTyTbwfSTrxAZtAFPvQ6Qi w5LiNFEUHGmRW+SHzytGpKQX09UJ5xuli+ghyxNMD2U9Zt9nrMgBHqx7Uux9Dmiz9x DYLdiyhWK7UV34vu+yeSeiQCVBkUNgPyGFQKAbxk= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e52bba9bd_16c02b0523c80f5c1790e9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 05:25:02 -0000 ----==_mimepart_5b29e52bba9bd_16c02b0523c80f5c1790e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Or delegate the processing of the Retry. -- 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/1451#issuecomment-398628006 ----==_mimepart_5b29e52bba9bd_16c02b0523c80f5c1790e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Or delegate the processing of the Retry.

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

----==_mimepart_5b29e52bba9bd_16c02b0523c80f5c1790e9-- From nobody Tue Jun 19 22:29:29 2018 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 7140E131041 for ; Tue, 19 Jun 2018 22:29:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 SrKp3UBb18zj for ; Tue, 19 Jun 2018 22:29:26 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF9DF130EB9 for ; Tue, 19 Jun 2018 22:29:25 -0700 (PDT) Date: Tue, 19 Jun 2018 22:29:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529472565; bh=7mPWXTaUsQT0fRBtm/wbExWC0OGUibIpKw084P03BsI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VKmRb0Y8kyT9FyGzEhTrLrTIMZHigQ2dC64fjcAjScZONq7MH9JjFP1/izDD8TSIN EIotStY9J+kOxAKISD5fpXcv/StGybCyO3QVdSaX8EHewLPgJkjELHf0hehJbsX+Ku phqMg2q4qw7H8l5Bes8/D2F+xhoVmlgY/BHtPZw0= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e6354220b_70d3fed77b7af8058634a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 05:29:28 -0000 ----==_mimepart_5b29e6354220b_70d3fed77b7af8058634a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > At risk of this turning into a unicorn, here are my comments. I don't think that you need to address all of them, but I would appreciate you taking one pass through this so we don't have too many editorial landmines to worry about later. Most are nitty, so they should be easy to fix; others I'm happy to punt on. I will do so directly. ETA tomorrow. -- 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/1450#issuecomment-398628677 ----==_mimepart_5b29e6354220b_70d3fed77b7af8058634a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

At risk of this turning into a unicorn, here are my comments. I don't = think that you need to address all of them, but I would appreciate you ta= king one pass through this so we don't have too many editorial landmines = to worry about later. Most are nitty, so they should be easy to fix; othe= rs I'm happy to punt on.

I will do so directly. ETA tomorrow.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b29e6354220b_70d3fed77b7af8058634a-- From nobody Tue Jun 19 22:31:32 2018 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 9CCF31311EA for ; Tue, 19 Jun 2018 22:31:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rGs0baeOJZRL for ; Tue, 19 Jun 2018 22:31:22 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE49213106B for ; Tue, 19 Jun 2018 22:31:18 -0700 (PDT) Date: Tue, 19 Jun 2018 22:31:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529472678; bh=rSrziszJSWTFbiKMJC5rRrUM/Um1S7KYsGV8hEmI1ks=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rOCCjQTLBxy2yAi5/Qc05RxK4iTclnSX4TECm9tslAYOpg5XKjzCwZ1Oprp3NBMuJ v0PFyfpW8jKqMnu2hONY69u6rtJp8sPQlxvymOLnoq8lA/+W8ujg/xpZakbj7piNtW EX97lZHG+nDqh2V2Eescg4U66DNmXYOLLnf6SMAI= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e6a641b3a_55943f8c2e08cf88655be"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 05:31:30 -0000 ----==_mimepart_5b29e6a641b3a_55943f8c2e08cf88655be Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I appreciate the simplicity, but consider an IoT device with crypto hw radio - or a transputer with many cores and few hw crypto units. -- 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/1451#issuecomment-398628967 ----==_mimepart_5b29e6a641b3a_55943f8c2e08cf88655be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I appreciate the simplicity, but consider an IoT device with crypto hw radio - or a transputer with many cores and few hw crypto units.

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

----==_mimepart_5b29e6a641b3a_55943f8c2e08cf88655be-- From nobody Tue Jun 19 22:41:12 2018 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 04908131048 for ; Tue, 19 Jun 2018 22:41:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 aIytZM8EQg48 for ; Tue, 19 Jun 2018 22:41:09 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BE92130EB9 for ; Tue, 19 Jun 2018 22:41:09 -0700 (PDT) Date: Tue, 19 Jun 2018 22:41:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529473268; bh=84ZhCbOdIsnl+OLGhFvXPigWH4pbb3hHh8JM0cpmOV0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=c5Q4toEu6LzMrsSvg1dr6SWESLd63q6p4kG30wwqhvQG0ANcNVIAwO0sAV+k+Oetl unuuEbAmIEtPr5sp3uy1yz1S3vAkMcYlFYaNVc3pr5oDINaTU5Vil9yB2eVByXXN6p lKy7Uq2bQsvQ3Az3JDJy33CKyV3NxMIt3b/1QZDc= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e8f4a696f_137b3ff8c90eef781140b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 05:41:11 -0000 ----==_mimepart_5b29e8f4a696f_137b3ff8c90eef781140b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Said device can stuff the last bytes somewhere and pass them to the CPU. -- 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/1451#issuecomment-398630424 ----==_mimepart_5b29e8f4a696f_137b3ff8c90eef781140b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Said device can stuff the last bytes somewhere and pass them to the CPU.

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

----==_mimepart_5b29e8f4a696f_137b3ff8c90eef781140b1-- From nobody Tue Jun 19 22:42:43 2018 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 2712F131048 for ; Tue, 19 Jun 2018 22:42:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 GBrl5mTppNWT for ; Tue, 19 Jun 2018 22:42:39 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A899130EB9 for ; Tue, 19 Jun 2018 22:42:39 -0700 (PDT) Date: Tue, 19 Jun 2018 22:42:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529473358; bh=KiFaImCKOp/Z46iZN+y55m36QSaiE2w+grzDDZxl5+I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kOgHdg00fa16mKc+P7f6aZzC8tGeOTBWNy4jj4WtmfPXY3egixS3ExfsCvRIiBS+N DiZdspSC+Wixm9pYXul1fbU6Uza/YBDWhvlyCxT3XF9MfSwKufmrbgyTJsDdeJVOx6 bDyPdKy+95yxcv1AwlS9s4+5LjnPTSRh8I1uuJ5s= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29e94e9d9e5_5e8c2ae6e8d58f50585ba"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 05:42:42 -0000 ----==_mimepart_5b29e94e9d9e5_5e8c2ae6e8d58f50585ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Worst case, you can ask for the packet to be delivered back to yourself so that you can copy the octets and send it out again. -- 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/1451#issuecomment-398630643 ----==_mimepart_5b29e94e9d9e5_5e8c2ae6e8d58f50585ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Worst case, you can ask for the packet to be delivered back to yourself so that you can copy the octets and send it out again.

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

----==_mimepart_5b29e94e9d9e5_5e8c2ae6e8d58f50585ba-- From nobody Tue Jun 19 23:17:21 2018 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 9ADAC12F1AB for ; Tue, 19 Jun 2018 23:17:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BafsuMxK9RSB for ; Tue, 19 Jun 2018 23:17:18 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E2EC1292F1 for ; Tue, 19 Jun 2018 23:17:18 -0700 (PDT) Date: Tue, 19 Jun 2018 23:17:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529475436; bh=ckbhGwxYGuaodsVE7InH1HXrVejDyzidxy4AFBePZvQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0cHVn3GLAcbu0494PwYYcs09zuLlfqyyclAKAm4hTNdnQ8xeVAX3UTg4dQd69cPQt o2684wW+isWLnlCuTm5E8AUCnkKZP1s6no1LRSi/4yXpE1BrOcgzrow4ARb+uwjO2u mP2N76k+4wVFxU0y460t/Wl2MBFyn14p6uO2TOJY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f16c6734b_6a422abb8ef16f5c152610"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 06:17:20 -0000 ----==_mimepart_5b29f16c6734b_6a422abb8ef16f5c152610 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The order in which the receiver apply ranges and discards overlap is arbitrary and does not necessarily happen on any one frame boundary. The sender SHOULD send the same content when introducing overlap (but can't always when relaying on external data sources). The receiver MUST provide consistent view of data. Once a range is visible to the application it will not 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/1463#issuecomment-398636536 ----==_mimepart_5b29f16c6734b_6a422abb8ef16f5c152610 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The order in which the receiver apply ranges and discards overlap is a= rbitrary and does not necessarily happen on any one frame boundary.

The sender SHOULD send the same content when introducing overlap (but = can't always when relaying on external data sources).

The receiver MUST provide consistent view of data. Once a range is vis= ible to the application it will not change.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29f16c6734b_6a422abb8ef16f5c152610-- From nobody Tue Jun 19 23:30:14 2018 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 84DE713104E for ; Tue, 19 Jun 2018 23:30:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OM9eiRNObe6q for ; Tue, 19 Jun 2018 23:30:11 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 012761292F1 for ; Tue, 19 Jun 2018 23:30:10 -0700 (PDT) Date: Tue, 19 Jun 2018 23:30:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529476210; bh=WQkT9L2VK4nuiNd9YzQm8eEZaoHZX3lWoUKVOrcFG68=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TWzPn9YIGpuj/gmgLL3NfM/WpBjX53SwA70qFYi+UmxoPczRTN2Iae5aygMI03HZ6 VaV0tFmmn5dYvB6s1+CZ1kRp0NeQKOUksF8tlo6SP9DBSLEH5jjQ+35XjcSWfdL3Zo 1iBQoLbjowOoV0wuseRiIGAvEbcJ1W6sz+nx56gA= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f47227d85_2a253f9b652c6f885762f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 06:30:13 -0000 ----==_mimepart_5b29f47227d85_2a253f9b652c6f885762f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Worst case, you can ask for the packet to be delivered back to yourself so that you can copy the octets and send it out again. This can profoundly change the architecture of a QUIC deployment. It is far from easy to synchronize and send back data in a distributed pipeline. For the same reason I'm not too keen on PNE in its current form, but as long as the encrypted PNE has no semantic meaning, it is less of an issue as it can be delegated. -- 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/1451#issuecomment-398638958 ----==_mimepart_5b29f47227d85_2a253f9b652c6f885762f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Worst case, you can ask for the packet to be delivered back to yoursel= f so that you can copy the octets and send it out again.

This can profoundly change the architecture of a QUIC deployment. It i= s far from easy to synchronize and send back data in a distributed pipeli= ne. For the same reason I'm not too keen on PNE in its current form, but = as long as the encrypted PNE has no semantic meaning, it is less of an is= sue as it can be delegated.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29f47227d85_2a253f9b652c6f885762f-- From nobody Tue Jun 19 23:32:31 2018 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 B3E34131050 for ; Tue, 19 Jun 2018 23:32:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OI32T06Vuv6N for ; Tue, 19 Jun 2018 23:32:27 -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 AABBB1292F1 for ; Tue, 19 Jun 2018 23:32:26 -0700 (PDT) Date: Tue, 19 Jun 2018 23:32:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529476345; bh=XdBy5d0CiIp5+9zo6iXGC0nWJe3NTy/tGCvkrHGE+Ss=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iKLsk7PyHQLsgXu+vGldHzRjIYWsFrS9pcavVY1srmkbvDLgcrrBjD1HA809P0VJC 8YaD4k1EogAt/wbN8iQLSECtGvSH+OTaUbhBLMVuoaMsYGPH1eWUXUfBE83Xo/IEmM ZhCUy+CwMI+vHXFWke5NOtUC7LugcPBM0nEyswrc= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f4f9d9ae1_6b8d3fe7bfce6f80107335"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 06:32:30 -0000 ----==_mimepart_5b29f4f9d9ae1_6b8d3fe7bfce6f80107335 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > The sender SHOULD send the same content when introducing overlap (but can't always when relaying on external data sources). This is not correct: https://tools.ietf.org/html/draft-ietf-quic-transport-12#section-9.5 says: > An endpoint could receive the same octets multiple times; octets that have already been received can be discarded. The value for a given octet MUST NOT change if it is sent multiple times; an endpoint MAY treat receipt of a changed octet as a connection error of type PROTOCOL_VIOLATION. -- 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/1463#issuecomment-398639359 ----==_mimepart_5b29f4f9d9ae1_6b8d3fe7bfce6f80107335 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The sender SHOULD send the same content when introducing overlap (but = can't always when relaying on external data sources).

This is not correct: https://tools.ietf.org/h= tml/draft-ietf-quic-transport-12#section-9.5 says:

An endpoint could receive the same octets multiple times; octets that<= br> have already been received can be discarded. The value for a given
octet MUST NOT change if it is sent multiple times; an endpoint MAY
treat receipt of a changed octet as a connection error of type
PROTOCOL_VIOLATION.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29f4f9d9ae1_6b8d3fe7bfce6f80107335-- From nobody Tue Jun 19 23:34:00 2018 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 C1045131050 for ; Tue, 19 Jun 2018 23:33:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FllYCAMZnzTL for ; Tue, 19 Jun 2018 23:33:56 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2518A1292F1 for ; Tue, 19 Jun 2018 23:33:56 -0700 (PDT) Date: Tue, 19 Jun 2018 23:33:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529476435; bh=04J3gOTG05jdzBoAKCgyDYT4BerDNmIKVqKD8Fb5Ous=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l7vTZliDWQconAWMRbp5xqu2IYZMWaU4grl99N4XnsBRhgtunpap/eEn4TOZRpaHX nRk0mCWptcqQi4pRg9UK6EqQxZvDvc6Y933j/lIL1TGM1hC/FocJ2D5AxTa5KUJWzQ AjjT8dp8KsDfJLXj19hCc3nZKLXVorNLObiOvMLk= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f5537c651_15c83fbdf185cf84272338"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 06:33:58 -0000 ----==_mimepart_5b29f5537c651_15c83fbdf185cf84272338 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj: I'm not finding this objection particularly compelling, but feel free to propose an alternate 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/issues/1451#issuecomment-398639604 ----==_mimepart_5b29f5537c651_15c83fbdf185cf84272338 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj: I'm not finding this objection particularly compelling, but feel free to propose an alternate design.

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

----==_mimepart_5b29f5537c651_15c83fbdf185cf84272338-- From nobody Tue Jun 19 23:36:32 2018 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 D69A1131054 for ; Tue, 19 Jun 2018 23:36:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7ACgdfj0WMNk for ; Tue, 19 Jun 2018 23:36:28 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A3ED131052 for ; Tue, 19 Jun 2018 23:36:28 -0700 (PDT) Date: Tue, 19 Jun 2018 23:36:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529476587; bh=peKzCFf8kuM9pDyAoZKuxaBjtdvt7xwt3SwJMTsLjTA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xu5woNTvWg8BcLi8MWhk7q7UBaHfn5Wdkozw/Ap9nA1OZR5ENle3ucMMGb0hXB/C0 j8UoSO67NFY2BatBoxLHooerOu+mJTetCPUeahIAKiDJFjM/NUXEZM24bLWsMfqj2w AEk8qxrRFYIN+sho2l0nMwn1IMDNr1XiQ94WmgHQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Improve ACK_ECN frame encoding (e.g., use bit-vector) (#1439) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f5eb73ab5_29f73f9b652c6f88856f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 20 Jun 2018 06:36:30 -0000 ----==_mimepart_5b29f5eb73ab5_29f73f9b652c6f88856f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul Thank you for your comments and your efforts on this issue. Using TP to indicate the use of ECT(1) sounds like a novel approach. > However, I would really prefer if we can get #1372 landed first, then draft a detailed proposal for the change, so that anyone can clearly evaluate the pro and cons of the change. Agreed. -- 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/1439#issuecomment-398640108 ----==_mimepart_5b29f5eb73ab5_29f73f9b652c6f88856f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@gloinul Thank you for your comme= nts and your efforts on this issue. Using TP to indicate the use of ECT(1= ) sounds like a novel approach.

However, I would really prefer if we can get #1372 landed first, then draft a detai= led proposal for the change, so that anyone can clearly evaluate the pro = and cons of the change.

Agreed.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29f5eb73ab5_29f73f9b652c6f88856f6-- From nobody Tue Jun 19 23:46:24 2018 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 96C54131055 for ; Tue, 19 Jun 2018 23:46:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ntNCSZb2jTGH for ; Tue, 19 Jun 2018 23:46:19 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF07131052 for ; Tue, 19 Jun 2018 23:46:19 -0700 (PDT) Date: Tue, 19 Jun 2018 23:46:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529477178; bh=wfHV0UC0mSmySIHcWAdoXhI46UFTGaKDOPQkbx422b4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uokVXrTu0YiCpZ7LfKP6s0fhhOrO05fcTG3klObQCH9HMc8MMS5D0lPvwYIQ0G3x4 iAaYMXaQoP+0++b2fRdpqGCkgzvAn+Lq2AI9AI8XGq3tcK0+azYzFrlJ/xR1gkwlVq 8eM8TgimkZQSjgQaQkBewpzF5SaXzAmv2l87nK2g= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f83acb949_afd3febc6a5cf849752d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 06:46:22 -0000 ----==_mimepart_5b29f83acb949_afd3febc6a5cf849752d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit One could include a retry serial number (or retry TTL) in the long header. That TTL could also be the start packet number (sort of what @martinthomson suggested earlier but in the explicit form: a client initial packet starts with packet number zero. Any retry MUST increase the packer number by one and start a new initial packet with the peer provided destination CID. A retry must reflect the source packet number. The client can choose how many retries it is willing to pursue, but it MUST not respond to a retry of a serial number older than once or to a number older than the latest initial request transmitted. There is still a chance of receiving a valid handshake on an older serial number racing a retry packet. A client may choose to accept that handshake and discard all other connenction attempts on the same line of serial numbers. This to protect against man on side attacks. There is a chance that a client receives multiple retries on the same serial number either through network packet duplication, attacks, or through competing infrastructure. In that case only one retry must be responded to - but this is already covered in the above. The serial number alone is insufficient to distinguish between different connections. The client must therefore issue a SCID that it can associate with each retry or handshake response, but it can be the same, different, or zero length, depending on the clients configuration. (I think this would work, but need more thought). -- 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/1451#issuecomment-398642239 ----==_mimepart_5b29f83acb949_afd3febc6a5cf849752d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One could include a retry serial number (or retry TTL) in the long hea= der. That TTL could also be the start packet number (sort of what @martinthomson suggested earlier but in = the explicit form: a client initial packet starts with packet number zero= . Any retry MUST increase the packer number by one and start a new initia= l packet with the peer provided destination CID. A retry must reflect the= source packet number. The client can choose how many retries it is willi= ng to pursue, but it MUST not respond to a retry of a serial number older= than once or to a number older than the latest initial request transmitt= ed.

There is still a chance of receiving a valid handshake on an older ser= ial number racing a retry packet. A client may choose to accept that hand= shake and discard all other connenction attempts on the same line of seri= al numbers. This to protect against man on side attacks.

There is a chance that a client receives multiple retries on the same = serial number either through network packet duplication, attacks, or thro= ugh competing infrastructure. In that case only one retry must be respond= ed to - but this is already covered in the above.

The serial number alone is insufficient to distinguish between differe= nt connections. The client must therefore issue a SCID that it can associ= ate with each retry or handshake response, but it can be the same, differ= ent, or zero length, depending on the clients configuration. (I think thi= s would work, but need more thought).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29f83acb949_afd3febc6a5cf849752d-- From nobody Tue Jun 19 23:49:11 2018 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 9CBC6131028 for ; Tue, 19 Jun 2018 23:49:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 stBR6dd4YXx0 for ; Tue, 19 Jun 2018 23:49:07 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E41A7131045 for ; Tue, 19 Jun 2018 23:49:07 -0700 (PDT) Date: Tue, 19 Jun 2018 23:49:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529477347; bh=BOhMdefjHyp8kY6p5DGgBqoOdZXP/08qp+MP98pWEEA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k+QDGJ36UnKjw54fT2FRu+gICMvVOkFW1iHO0wOC5id/OrfEHVXC5KD4+aWXOVok0 81zO9aypbTFt99AzDFfYxKNnnRlbc5ZhfZb5ypcryXVoKml4QEb2FVjOaces7B2q8w Q6hTUEUKFVB91irK8UIxCVg8J4Tt0WazoYVYtBko= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f8e37ccfb_16733fb76c5f2f7c107839"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 06:49:10 -0000 ----==_mimepart_5b29f8e37ccfb_16733fb76c5f2f7c107839 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't see how this protects against an off-path attacker injecting a fake Retry with serial number = 1. In order to have that, you need entropy from the client. -- 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/1451#issuecomment-398642853 ----==_mimepart_5b29f8e37ccfb_16733fb76c5f2f7c107839 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I don't see how this protects against an off-path attacker injecting a fake Retry with serial number = 1. In order to have that, you need entropy from the client.

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

----==_mimepart_5b29f8e37ccfb_16733fb76c5f2f7c107839-- From nobody Tue Jun 19 23:53:46 2018 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 40C06131028 for ; Tue, 19 Jun 2018 23:53:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 LygtD-OYqXuG for ; Tue, 19 Jun 2018 23:53:43 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE70F130FBE for ; Tue, 19 Jun 2018 23:53:42 -0700 (PDT) Date: Tue, 19 Jun 2018 23:53:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529477621; bh=S5AygHuv2Wq5l2+vU18ViDNDIAKKWVoRxM/8I/n06GM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ybkI2GwVHRle4d3NSdQppYVEDxqp1SZ4P4+PIS9D2Pur9DFflCHQNwxkw/dxcFWPc pzdu6KmZEAT65BNY6vr+nVQLROqVMhCMcTxuQq3x6bE9WdXbjU3nuqzJ0GW0W1eXM+ MuoAVewk7l2HOEWL1wf6ybt8h3BT4jDyIEuLY9uc= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29f9f5c6fb7_75cb2af0e8498f50133858"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 06:53:44 -0000 ----==_mimepart_5b29f9f5c6fb7_75cb2af0e8498f50133858 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes that is correct. I suppose that problem also exists today with a single retry? -- 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/1451#issuecomment-398643846 ----==_mimepart_5b29f9f5c6fb7_75cb2af0e8498f50133858 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes that is correct. I suppose that problem also exists today with a single retry?

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

----==_mimepart_5b29f9f5c6fb7_75cb2af0e8498f50133858-- From nobody Tue Jun 19 23:54:49 2018 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 489FD130FBE for ; Tue, 19 Jun 2018 23:54:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 dxCYDOnsXl75 for ; Tue, 19 Jun 2018 23:54: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 BD4FB131050 for ; Tue, 19 Jun 2018 23:54:45 -0700 (PDT) Date: Tue, 19 Jun 2018 23:54:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529477684; bh=bUlBQqeuiwsO6/Mqsjd8w0fUTMg2utRksp5zxhwSHGo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2Rp8e0F1ggZXpNnEpTasheyHVsqO6p46JxXvbcn3j98HlgxKcN/kCRLPMlN6mJQB8 zehlLovvPRZyk/cXrUnbsnQdedpbXKwK6YTa1pCiDRSHbvGI7uqbBQMbR2O2Gd9d9E jbOQk3JrA9zTcyt1H80HpeW3NFEx+TXQSWCQLDGU= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29fa34a0b1a_6b963fe7bfce6f80221528"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 06:54:47 -0000 ----==_mimepart_5b29fa34a0b1a_6b963fe7bfce6f80221528 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit No, it doesn't, because the server has to echo the client's original DCID, and that is high entropy. -- 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/1451#issuecomment-398644109 ----==_mimepart_5b29fa34a0b1a_6b963fe7bfce6f80221528 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

No, it doesn't, because the server has to echo the client's original DCID, and that is high entropy.

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

----==_mimepart_5b29fa34a0b1a_6b963fe7bfce6f80221528-- From nobody Tue Jun 19 23:58:22 2018 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 E8EE9131062 for ; Tue, 19 Jun 2018 23:58:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qoY-I_vN7cqx for ; Tue, 19 Jun 2018 23:58:11 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD2FE131096 for ; Tue, 19 Jun 2018 23:58:10 -0700 (PDT) Date: Tue, 19 Jun 2018 23:58:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529477890; bh=c9ljg74Z6AcP4CAk5YhzJIBvUN1hUSq6b5FDE6Jb4bM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K7tAxunHTeqHQcKiSZ54C2Gk9tkaiUzA2ECZ/jLc6N2FXqJP/YsLFKnt7hE73eBfj /mJP7vlprMT2CpdTKakSjQCAVx2m355yoTDtTNNgCps4VvYE+WwJxWanUzdegkXTPg s2fOY+OGnB99syirs2h/C08BlMTx6geMBpaobnFA= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29fb02d26a_6b993fe7bfce6f802012b4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 06:58:20 -0000 ----==_mimepart_5b29fb02d26a_6b993fe7bfce6f802012b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit OK two things then: the original case: if the client has random initial DCID and a SCID the retry must respond with a new CID used for server routing, and the SCID to route to the client (if any), AND and additional copy of the origin random DCID for entropy. That is 3 three CIDS in a retry repsonse if that is to work. If the above works, it also works with retries with serial numbers, but it does require 3 CIDS in a retry packet. -- 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/1451#issuecomment-398644842 ----==_mimepart_5b29fb02d26a_6b993fe7bfce6f802012b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

OK two things then: the original case: if the client has random initia= l DCID and a SCID the retry must respond with a new CID used for server r= outing, and the SCID to route to the client (if any), AND and additional = copy of the origin random DCID for entropy. That is 3 three CIDS in a ret= ry repsonse if that is to work.

If the above works, it also works with retries with serial numbers, bu= t it does require 3 CIDS in a retry packet.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29fb02d26a_6b993fe7bfce6f802012b4-- From nobody Wed Jun 20 00:08:14 2018 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 62810131052 for ; Wed, 20 Jun 2018 00:08:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QScgsKBem_Eb for ; Wed, 20 Jun 2018 00:08:10 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7457712D949 for ; Wed, 20 Jun 2018 00:08:10 -0700 (PDT) Date: Wed, 20 Jun 2018 00:08:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529478489; bh=Ce6Nnfspi2uC2/STYHgdiHKsOmP+fq9gebJ7gHZCvY4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ad9rYyUKXWemIiU0oaOA3OlfIGHBcaFvE07jf7gpR3fL4oGz9iG58oGS0ABuBpC09 VcBDrbVyno4DPtyJHwUgyBPUCW8ZO2Z44iQSCyvST8IIM1jbvHMsNB6cgOvWFgFJpj wMJeqEBUBL5LXWR93Z7WetQ7eLEQQdARZ/+1zGtY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29fd59ac447_10902b1d26ab8f6032147a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 07:08:13 -0000 ----==_mimepart_5b29fd59ac447_10902b1d26ab8f6032147a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The server is stateless and so cannot send the original DCID in the second retry. -- 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/1451#issuecomment-398647021 ----==_mimepart_5b29fd59ac447_10902b1d26ab8f6032147a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The server is stateless and so cannot send the original DCID in the second retry.

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

----==_mimepart_5b29fd59ac447_10902b1d26ab8f6032147a-- From nobody Wed Jun 20 00:12:45 2018 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 8FED3130F3C for ; Wed, 20 Jun 2018 00:12:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 eeCSNZtVhr12 for ; Wed, 20 Jun 2018 00:12:42 -0700 (PDT) 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 46F9C12D949 for ; Wed, 20 Jun 2018 00:12:42 -0700 (PDT) Date: Wed, 20 Jun 2018 00:12:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529478761; bh=leiz/5AFRuCjklbCnTnJvyTcRiGowfYGDFjduTEct0k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a3g22YKO3HH0tA8dyJMEYnagHW6USk7hYD6gczK7c5W3CkmKFf/b6vdKzhhdQo4hy NNUVkmLtQBQAnC5ZNOK1H/o5dYesM4pNeyPm5UXwzZaIqW9zcoH8/Mr4s8PQyOAzea dwgi4ZihLZ3vraKqYlfAyNrnaj5KQcUrs7o/6QE8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29fe699a7d2_7d373fce4b23af884830fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 07:12:44 -0000 ----==_mimepart_5b29fe699a7d2_7d373fce4b23af884830fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes I realized. It is necessary to have an extra nonce field in the intial packet, at least on secondary attempts, unless you derive from the encrypted packet. I see the complexity of adding an extra field here, and also the elegance of using the (non-secret) encrypted packet sample as nonce instead. I still prefer an extra nonce field to allow encryption to be pipelined, but I see your point. -- 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/1451#issuecomment-398648113 ----==_mimepart_5b29fe699a7d2_7d373fce4b23af884830fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes I realized. It is necessary to have an extra nonce field in the in= tial packet, at least on secondary attempts, unless you derive from the e= ncrypted packet. I see the complexity of adding an extra field here, and = also the elegance of using the (non-secret) encrypted packet sample as no= nce instead.
I still prefer an extra nonce field to allow encryption to be pipelined, = but I see your point.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29fe699a7d2_7d373fce4b23af884830fa-- From nobody Wed Jun 20 00:15:10 2018 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 68D18130F73 for ; Wed, 20 Jun 2018 00:15:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HwJZ4Y5cDlyl for ; Wed, 20 Jun 2018 00:15:06 -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 7BA5B12D949 for ; Wed, 20 Jun 2018 00:15:06 -0700 (PDT) Date: Wed, 20 Jun 2018 00:15:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529478905; bh=0//nj85zPmKX1rX8bS8cTRZiTsxJtItDxX4eGHroe38=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NpbQoYlA+2pL7g4lO/pnxGClJb5UD64FVWThWdhUvvA3BZEA/a2yk7JBa2UZLlQ+4 cxyhqdNHbXxeia3WAdm4Jbtq3pDaOYsjcRcrYW0Iep8YBJebbQ023jxZ6q0+SuuGtd ZyTe505D0xiZXfHYxKxlhBhbZ+ST29Q48vGFQbvA= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b29fef9dc027_7d443fce4b23af88190723"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 20 Jun 2018 07:15:09 -0000 ----==_mimepart_5b29fef9dc027_7d443fce4b23af88190723 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > instead, I propose we say that Retry has to contain the last 8 octets of the Initial packet it's responding to. That's high entropy by definition (it's a hash of CH), and then we won't need any other rule > > [OK, not a hash, actually the auth tag...] @ekr Instead, can we require Retry packets to always contain SCID longer than eight octets? I'd assume that the server can switch to the final SCID when it sends an Initial packet. I think that approach might be simpler than requiring the client to remember the last 8 octets of the Initial packet that it has sent. -- 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/1451#issuecomment-398648636 ----==_mimepart_5b29fef9dc027_7d443fce4b23af88190723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

instead, I propose we say that Retry has to contain the last 8 octets = of the Initial packet it's responding to. That's high entropy by definiti= on (it's a hash of CH), and then we won't need any other rule

[OK, not a hash, actually the auth tag...]

@ekr Instead, can we require Retry pac= kets to always contain SCID longer than eight octets? I'd assume that the= server can switch to the final SCID when it sends an Initial packet.

=

I think that approach might be simpler than requiring the client to re= member the last 8 octets of the Initial packet that it has sent.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b29fef9dc027_7d443fce4b23af88190723-- From nobody Wed Jun 20 00:22:48 2018 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 A76A812D949 for ; Wed, 20 Jun 2018 00:22:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bBPgVN3w7vts for ; Wed, 20 Jun 2018 00:22:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 543D3124D68 for ; Wed, 20 Jun 2018 00:22:45 -0700 (PDT) Date: Wed, 20 Jun 2018 00:22:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529479364; bh=bfLYsgKmzFdIbHyQzG0ke0BkbZeYyQuW/NYMWbsKGcI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AEelEvQoLkhic+cbeA/M7bu/Z6yKOZglMGc224sZdbDAalnDfqFN/MxKHsVtIv1IA KWpsYf7KNTUvMp9DPusOKk64iU3b4F1Xqbx1nDmOVpmMowKyRKpgZUR0LTeQ+zJsKg RUcbzbkn/7+Hz8zjMQQkQCdUu0+7q4CJCSvaBweY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a00c4a703e_6bda3fe7bfce6f8021090"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 07:22:47 -0000 ----==_mimepart_5b2a00c4a703e_6bda3fe7bfce6f8021090 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho: I think that might work. yes, but I'd need to noodle on it a bit. -- 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/1451#issuecomment-398650432 ----==_mimepart_5b2a00c4a703e_6bda3fe7bfce6f8021090 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho: I think that might work. yes, but I'd need to noodle on it a bit.

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

----==_mimepart_5b2a00c4a703e_6bda3fe7bfce6f8021090-- From nobody Wed Jun 20 00:26:42 2018 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 93A4812D949 for ; Wed, 20 Jun 2018 00:26:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NnDFgsk3DE8S for ; Wed, 20 Jun 2018 00:26:39 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34BB5124D68 for ; Wed, 20 Jun 2018 00:26:39 -0700 (PDT) Date: Wed, 20 Jun 2018 00:26:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529479598; bh=22rkrF50NNzCFNtNPrIgtXP2rS93IEjdQqlTrQqKTF4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aZem5ukOkG6SraG52yj7Hm5yyxPEhdDEYJwKXtf4WdW373qDVkiX4dRUsdi39qSAf K5vUPQ9VB087tcsg4wWU+KNV5cxBw0+4jr7yQCAKMBQun8kXh5SKLTTgexzqCAuoGF utuxiO/8qrE8F6PfV3ZQOyiLrfD9qOkjQvqgBf6Q= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a01ae4f246_107a2b1d26ab8f60498219"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 07:26:41 -0000 ----==_mimepart_5b2a01ae4f246_107a2b1d26ab8f60498219 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Another observation: When the initial random DCID is used for routing, it can be used to attack a specific subset of infrastructure. If the initial DCID is zero length and a separate nonce is provided. The peers LB is responsible for distribution of traffic and the nonce becomes the same in both cases. Additionally, on secondary attempts the LB can verify the DCID now present from the retry packet. That nonce could be part of the early SCID as @kazuho suggests, but that is a matter of framing. -- 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/1451#issuecomment-398651339 ----==_mimepart_5b2a01ae4f246_107a2b1d26ab8f60498219 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Another observation: When the initial random DCID is used for routing,= it can be used to attack a specific subset of infrastructure. If the ini= tial DCID is zero length and a separate nonce is provided. The peers LB i= s responsible for distribution of traffic and the nonce becomes the same = in both cases. Additionally, on secondary attempts the LB can verify the = DCID now present from the retry packet.

That nonce could be part of the early SCID as @kazuho suggests, but that is a matter of framing.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2a01ae4f246_107a2b1d26ab8f60498219-- From nobody Wed Jun 20 00:30:41 2018 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 A6594130DD8 for ; Wed, 20 Jun 2018 00:30:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mseP74uq8SKi for ; Wed, 20 Jun 2018 00:30:38 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07EE130DC1 for ; Wed, 20 Jun 2018 00:30:37 -0700 (PDT) Date: Wed, 20 Jun 2018 00:30:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529479837; bh=dU/IZez1z1T46xnojGWkIiJLpWxdYDvIFN3dBU3opAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=At0puoakKritjt2Hvh/pLxHCLUsCEsStPbHMq1pnnXf5VWC/MPVCEPYOTCLNXF9b1 z9hmHVOg292oG4H8UdR3fBaMInaOsV97lr5XkXKIyr+UYOdcjidgwm1/GYEAT4Gfax +ZEa0IjK8s3DLHacjNe9kYQsf4W6qUDwESZhgZeU= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a029d2c6ca_4c502b04a7604f60294041"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 07:30:40 -0000 ----==_mimepart_5b2a029d2c6ca_4c502b04a7604f60294041 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, sorry, I am aware that this is the case now. I propose to change it because it is impossible to conform to when using memory mapped files as a source on Linux. -- 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/1463#issuecomment-398652385 ----==_mimepart_5b2a029d2c6ca_4c502b04a7604f60294041 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, sorry, I am aware that this is the case now. I propose to change it because it is impossible to conform to when using memory mapped files as a source on Linux.

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

----==_mimepart_5b2a029d2c6ca_4c502b04a7604f60294041-- From nobody Wed Jun 20 00:32:14 2018 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 807F613108F for ; Wed, 20 Jun 2018 00:32:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BybVVZsNsCyd for ; Wed, 20 Jun 2018 00:32:02 -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 BDA1613107F for ; Wed, 20 Jun 2018 00:32:02 -0700 (PDT) Date: Wed, 20 Jun 2018 00:32:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529479922; bh=iaYILQ9z4d5A1CFNFfkjChmoGkvtDIlA/h+fkxFR6NU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CDIJEDFLqa7z8PP2yGMkgWyqtFpl8tEfAXipRl2Z19YCVy0HjKpcw+/2O7dJZSg37 oKHW0OSGXqS8J0cpZoIULwLRo7Pak5uGd/0zRgGnH3PWuNmObIaZdSRMgDbAv1FI7m E64uaHeP9BNl3/sxoeVNz7FLIvVrcX7sqFec9RDY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a02f2168d6_24ee2b212fed6f54582070"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 07:32:12 -0000 ----==_mimepart_5b2a02f2168d6_24ee2b212fed6f54582070 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ah. I would oppose that 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/1463#issuecomment-398652718 ----==_mimepart_5b2a02f2168d6_24ee2b212fed6f54582070 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Ah. I would oppose that change.

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

----==_mimepart_5b2a02f2168d6_24ee2b212fed6f54582070-- From nobody Wed Jun 20 00:36:08 2018 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 4E03F130DC1 for ; Wed, 20 Jun 2018 00:36:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Ev5bouXLobK3 for ; Wed, 20 Jun 2018 00:36:04 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C76B131052 for ; Wed, 20 Jun 2018 00:36:04 -0700 (PDT) Date: Wed, 20 Jun 2018 00:36:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529480163; bh=gBXssxxYYlp/d7Mbj2ffrz13ZM2RWcif1Xpkq86jjqQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YL6u25JNMatlfr8eksrYLE6DOojZU8se/0ApOuw18gBkZGRwrbAs9YqRv50wFuOTB LsXeyX/7CB7EWQNaBGKADvQejMHE5tpmfDs0dRuWGlMRhpxi9lBJkzdFmpnh11tqen VRkrQkoDNa9VfiaIWsDhixBRDFlMKfJqvTDmkEmk= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a03e367470_1dcc3fda25fb6f78361010"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 20 Jun 2018 07:36:07 -0000 ----==_mimepart_5b2a03e367470_1dcc3fda25fb6f78361010 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 2 commits. dbfe4d8 partial editorial fixes 73bf8cb Merge pull request #2 from janaiyengar/ecn -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/139f1ee2f508877ad0f8d4cb92170382d4707247..73bf8cb46b529bd799a4cf7df370b54aab5b29b8 ----==_mimepart_5b2a03e367470_1dcc3fda25fb6f78361010 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 2 commits.

  • dbfe4d8 partial editorial fixes
  • 73bf8cb Merge pull request #2 from janaiyengar/ecn

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2a03e367470_1dcc3fda25fb6f78361010-- From nobody Wed Jun 20 02:45:57 2018 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 74AC0130D7A for ; Wed, 20 Jun 2018 02:45:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 SK4_j59ewCnv for ; Wed, 20 Jun 2018 02:45:53 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C010912F295 for ; Wed, 20 Jun 2018 02:45:53 -0700 (PDT) Date: Wed, 20 Jun 2018 02:45:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529487952; bh=oQ8QYL9eKhCgbtzkj62qtBviuOk0WCkdM83PA1cnW6A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OLp/Zgfk6w9E5fY8hvjIXMvKGcKFbFaw7IXDrQLl4c4owNAZJt0pEMCJ1PwFoB2Du Z+Ua7F4gJoq1zYDSULv52KsYCI18No99K+TwbnQ6MnTWm3NMrHdWS3bE8yD9QyU+G+ TdVj+0sg6WrNks5utaLGFZpFmll15XacuP7H1pKg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Duplicate STREAM/CRYPTO_HS in the same packet (#1463) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a22507d16_2a912ab24a276f60455f5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 09:45:56 -0000 ----==_mimepart_5b2a22507d16_2a912ab24a276f60455f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We discussed that specific possibility (that bytes can change after invoking sendfile() or equivalent), but I don't think that there was much appetite for allowing that. See #1353. If anyone disagrees with this, they are welcome to take that to the mailing list (or the chairs). -- 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/1463#issuecomment-398690343 ----==_mimepart_5b2a22507d16_2a912ab24a276f60455f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

We discussed that specific possibility (that bytes can change after in= voking sendfile() or equivalent), but I don't think that there was much a= ppetite for allowing that. See #1353. If anyone disagrees with this, they are welcom= e to take that to the mailing list (or the chairs).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2a22507d16_2a912ab24a276f60455f5-- From nobody Wed Jun 20 05:29:34 2018 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 D8996130E3B for ; Wed, 20 Jun 2018 05:29:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 tAKRnfPZHaJ4 for ; Wed, 20 Jun 2018 05:29:31 -0700 (PDT) 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 F2DAC130E2A for ; Wed, 20 Jun 2018 05:29:30 -0700 (PDT) Date: Wed, 20 Jun 2018 05:29:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529497769; bh=41STN6GZV4pls0rXgT4x4FPyN4PxdhGPJIcwd9lVWxs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BbU1NRV6kJe09NEAjT8gs9LWugjn+5Jy7O4ywTt3vEniHMzD1ITH4/7ST7g81pZEV gjumr68Aer8aiT+L1c03OwqkIAbYoVDtb8TdCitW+s70z5MltH/d1uXnSCDXmbQdy6 LciQJT8I83288mo1lli6UT4WG7zuKQr9SWvJgF3A= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a48a9e1c7f_24592b082e6c8f5c18555f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 20 Jun 2018 12:29:33 -0000 ----==_mimepart_5b2a48a9e1c7f_24592b082e6c8f5c18555f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho why longer than 8 octets and not >=8 octets? I would like the simple RETRY case to work as well, which is the server doesn't want to change the CID at all, and it is the terminal node, so I don't want to require senders of RETRY to be required to change CID. Related question: What CID is the client deriving the key for INITIAL packets from? I was thinking all INITIAL packets used the same key, but if the terminal server may not have seen the client's first DCID, that doesn't work unless the original DCID is put somewhere the final server can read in the token. -- 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/1451#issuecomment-398731413 ----==_mimepart_5b2a48a9e1c7f_24592b082e6c8f5c18555f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho why longer than 8 octets and = not >=3D8 octets?

I would like the simple RETRY case to work as well, which is the serve= r doesn't want to change the CID at all, and it is the terminal node, so = I don't want to require senders of RETRY to be required to change CID.

Related question: What CID is the client deriving the key for INITIAL = packets from? I was thinking all INITIAL packets used the same key, but = if the terminal server may not have seen the client's first DCID, that do= esn't work unless the original DCID is put somewhere the final server can= read in the token.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2a48a9e1c7f_24592b082e6c8f5c18555f-- From nobody Wed Jun 20 05:47:08 2018 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 02B361310F3 for ; Wed, 20 Jun 2018 05:46:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 e_qNz15uYqZS for ; Wed, 20 Jun 2018 05:46:57 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D99B131129 for ; Wed, 20 Jun 2018 05:46:57 -0700 (PDT) Date: Wed, 20 Jun 2018 05:46:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529498816; bh=DX9bfSAJFK5bRkwQ3z9eCGmdKcU1yMVrIEv30cJ81k8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gHQt7ZR0neI9oP9qMTBnLo3WNX0qmxAxSPBVPLjFaAW89Pu6bNaOMtHAq46B/HhRM SpibIUiQlWS7TnJxBNrPXsRdWcu4r7AfRohlEyHtMYnTgn6xnSiTT3rd2D78Xb/jcR ZwhSDFGgsavpiX5vCYqVhhkXp/ZB0hAhiyFqrbqM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a4cc026811_3fb53fd346274f807842ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 20 Jun 2018 12:47:07 -0000 ----==_mimepart_5b2a4cc026811_3fb53fd346274f807842ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > +appended at the end. + + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Largest Acknowledged (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Delay (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN Block ... As discussed on the list, I think it makes sense to but the ACK Block Count and ACK blocks at the end of this frame, to make it simpler to truncate the ack blocks if necessary. -- 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/1372#pullrequestreview-130375599 ----==_mimepart_5b2a4cc026811_3fb53fd346274f807842ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> +appended at the end.
+
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                     Largest Acknowledged (i)                ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Delay (i)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                           ECN Block                         ...

As discussed on the list, I think it makes sense to but the ACK Block Count and ACK blocks at the end of this frame, to make it simpler to truncate the ack blocks if necessary.

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

----==_mimepart_5b2a4cc026811_3fb53fd346274f807842ef-- From nobody Wed Jun 20 06:18:12 2018 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 53C7B130E6D for ; Wed, 20 Jun 2018 06:18:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 S0v8Itr3x5w6 for ; Wed, 20 Jun 2018 06:18:09 -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 E146D130E23 for ; Wed, 20 Jun 2018 06:18:08 -0700 (PDT) Date: Wed, 20 Jun 2018 06:18:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529500687; bh=0cjDCgGmODxBYFu6kRoWb3C7AworLR3EAj+z6/dHGu4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0yk5WumqanMjz+ezsrAWVY6JA4SNaRr38KHk3MqFcSI7YgXLE86pY3l7ATHWZOzKb zAuplRSUCkkvvtROFPg3cXCbJF0Zpllwhjbjd2BE3adSb892qNfjbrbzQoLwgA55+c mptZDWUkf4IaDR6HINZoabrw03hPOgLQyQVkWsq0= From: Juha-Matti Tilli Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] SNI encryption (#795) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a540fc2657_697a2b21ae51ef502220fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jmtilli 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.26 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: Wed, 20 Jun 2018 13:18:11 -0000 ----==_mimepart_5b2a540fc2657_697a2b21ae51ef502220fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The full explanation is easy. It's for incoming connections in a use case where multiple HTTP2/QUIC servers are multiplexed behind a single IPv4 server address. For example, IoT adoption might require more than 4 billion HTTP servers all around the world. If the first QUIC packet sent will contain the SNI, the NAT will compare it against a full list of (SNI, internal IP) pairs. For example: * device1.iot.company.com -> 10.0.1.100 * device2.iot.company.com -> 10.0.1.101 * device3.iot.company.com -> 10.0.1.102 * device4.iot.company.com -> 10.0.1.103 If the SNI is unencrypted and required to be always present, this scheme will work all the time. The only problem is configuring the SNI -> internal IP mappings in the NAT box. If it's a carrier grade NAT, presumably the carrier will allow configuring wildcard matches against the domain names the customers own. Outgoing connections will always work with NAT without any SNI matching. -- 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/795#issuecomment-398745019 ----==_mimepart_5b2a540fc2657_697a2b21ae51ef502220fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The full explanation is easy. It's for incoming connections in a use c= ase where multiple HTTP2/QUIC servers are multiplexed behind a single IPv= 4 server address. For example, IoT adoption might require more than 4 bil= lion HTTP servers all around the world.

If the first QUIC packet sent will contain the SNI, the NAT will compa= re it against a full list of (SNI, internal IP) pairs. For example:

  • device1.iot.company.com -> 10.0.1.100
  • device2.iot.company.com -> 10.0.1.101
  • device3.iot.company.com -> 10.0.1.102
  • device4.iot.company.com -> 10.0.1.103

If the SNI is unencrypted and required to be always present, this sche= me will work all the time.

The only problem is configuring the SNI -> internal IP mappings in = the NAT box. If it's a carrier grade NAT, presumably the carrier will all= ow configuring wildcard matches against the domain names the customers ow= n.

Outgoing connections will always work with NAT without any SNI matchin= g.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b2a540fc2657_697a2b21ae51ef502220fa-- From nobody Wed Jun 20 06:20:20 2018 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 770FD130E7C for ; Wed, 20 Jun 2018 06:20:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KO2iMuB8OT0i for ; Wed, 20 Jun 2018 06:20:17 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18E7130E7B for ; Wed, 20 Jun 2018 06:20:16 -0700 (PDT) Date: Wed, 20 Jun 2018 06:20:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529500815; bh=yLyIhoiNR4uRTJCyNdvl/XpzhUZKBxRsyNNR1cp2dHg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ghsGS+GlPekOD8cWmjkogXR+H1756HgxTsCcxXxSfi176cv0zdJH8PdEIBqs7GiyN WftMRAYOHhHo29XGqyOhDhvfDArALldG/d5OA81VjdxSDSJv9uTKYSQRwvbZGTzY9n ZgNqiEc5iVyi3SReRt0tsYkLy2GoWjxhbUrFipxk= From: Juha-Matti Tilli Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a548fecd7c_67353fa2a8048f783821e4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jmtilli 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.26 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: Wed, 20 Jun 2018 13:20:19 -0000 ----==_mimepart_5b2a548fecd7c_67353fa2a8048f783821e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok, perhaps this issue can be closed then, if QUIC inherits the requirement of TLS. I was fearing that QUIC might not adopt all of TLS, as QUIC is very different from TCP and not all of TLS might necessarily apply. -- 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/1456#issuecomment-398745630 ----==_mimepart_5b2a548fecd7c_67353fa2a8048f783821e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Ok, perhaps this issue can be closed then, if QUIC inherits the requirement of TLS. I was fearing that QUIC might not adopt all of TLS, as QUIC is very different from TCP and not all of TLS might necessarily apply.

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

----==_mimepart_5b2a548fecd7c_67353fa2a8048f783821e4-- From nobody Wed Jun 20 06:21:19 2018 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 004C8130E84 for ; Wed, 20 Jun 2018 06:21:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 3zK15eYviHHW for ; Wed, 20 Jun 2018 06:21:16 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FADC130E23 for ; Wed, 20 Jun 2018 06:21:15 -0700 (PDT) Date: Wed, 20 Jun 2018 06:21:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529500874; bh=AhGYN6M/xbh93ftoQ/pjBi2Z5vsjDFbcqXjjs+/l7L0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0yhtYf17rwqzi6ExV/2hQt+vWhMzzx7IekWLEKwMaG5MEwiQ8jgJEGcObJIdeqUGy 25bH8ty4Vsh70GMw/Op+b/7UfYs1nDPHeGTwv2U9Aq55u8kEheTOhYF+rM0URfNA2K HQ/9l7B/J4LDVjfb30g8H+w9LLyGFh+YWtyCUD8Y= From: Lars Eggert Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] SNI encryption (#795) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a54caad134_70383f919d58af84101242"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.26 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: Wed, 20 Jun 2018 13:21:18 -0000 ----==_mimepart_5b2a54caad134_70383f919d58af84101242 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This discussion needs to happen in the TLS WG. -- 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/795#issuecomment-398745956 ----==_mimepart_5b2a54caad134_70383f919d58af84101242 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This discussion needs to happen in the TLS WG.

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

----==_mimepart_5b2a54caad134_70383f919d58af84101242-- From nobody Wed Jun 20 06:52:36 2018 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 EA981130EA2 for ; Wed, 20 Jun 2018 06:52:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ls8VLkpiFGK7 for ; Wed, 20 Jun 2018 06:52:33 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 394AC130E96 for ; Wed, 20 Jun 2018 06:52:33 -0700 (PDT) Date: Wed, 20 Jun 2018 06:52:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529502752; bh=vGsuyeJTGOHaJOkYzCL3koqrniH9OAcb9KYE9TOIYeU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ivAsSwo+yDGw0cicIEVaqig0pR2VMVElnmLsMG+t6klPV+HIBq6obARbTWT7nbHbt 56N2Gb66jfDWMZS+CaCJME4R8ZPEUcw91NLEgD1HD/dKe2GSHKDwnOhXU5vNhweMsp QWUgS6W3mkfdXuk30vcWMyXufXTGT3z9/nMU7gA4= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a5c1feb7c7_2b6e3fde2324ef78143564"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 20 Jun 2018 13:52:35 -0000 ----==_mimepart_5b2a5c1feb7c7_2b6e3fde2324ef78143564 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree with @mikkelfj here that relying on the encrypted packet makes a hw offload solution much more difficult, and I would prefer not to do that. The Initial packet is the one packet that we generally have extra room, so I don't think we should be afraid to add an additional nonce. -- 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/1451#issuecomment-398757226 ----==_mimepart_5b2a5c1feb7c7_2b6e3fde2324ef78143564 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I agree with @mikkelfj here that r= elying on the encrypted packet makes a hw offload solution much more diff= icult, and I would prefer not to do that. The Initial packet is the one p= acket that we generally have extra room, so I don't think we should be af= raid to add an additional nonce.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2a5c1feb7c7_2b6e3fde2324ef78143564-- From nobody Wed Jun 20 07:08:18 2018 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 9D932130EAF for ; Wed, 20 Jun 2018 07:08:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 2_w03D2BTHKC for ; Wed, 20 Jun 2018 07:08:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4B8C130EAE for ; Wed, 20 Jun 2018 07:08:13 -0700 (PDT) Date: Wed, 20 Jun 2018 07:08:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529503693; bh=SF1B4AE6pPkjfe+xNu1h8X1yqXwV1rupclqZXfv36Qo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zPFF6tX/SbQkViriw3ZNj0pYyvqRjSdiIytpMFh60G+Z2EfbJMZgeR1L/Kb+SJ4E2 orcemSKZFTmHm9xhglE8F+M2d01dbyhR4VNUCzMaKK11/DC7+JK17bbRMvElr5NPpE MxYwqmvTqs1n2p/xCldm/xkTFVsa1kLXj2qrnK2Y= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a5fcdfda_dda73ff6095d0f7c2881bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Wed, 20 Jun 2018 14:08:16 -0000 ----==_mimepart_5b2a5fcdfda_dda73ff6095d0f7c2881bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > +appended at the end. + + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Largest Acknowledged (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Delay (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN Block ... Agree, if no ones protests, I will implement that change tomorrow. -- 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/1372#discussion_r196793189 ----==_mimepart_5b2a5fcdfda_dda73ff6095d0f7c2881bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +appended at the end.
+
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                     Largest Acknowledged (i)                ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Delay (i)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                           ECN Block                         ...

Agree, if no ones protests, I will implement that change tomorrow.

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

----==_mimepart_5b2a5fcdfda_dda73ff6095d0f7c2881bf-- From nobody Wed Jun 20 09:51:01 2018 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 432D3130DEE for ; Wed, 20 Jun 2018 09:50:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rWWdtT4LF-Qe for ; Wed, 20 Jun 2018 09:50:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5AF5130DEA for ; Wed, 20 Jun 2018 09:50:56 -0700 (PDT) Date: Wed, 20 Jun 2018 09:50:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529513455; bh=4uRM/mcnLaiuFwNTvlivijuVmWiMZ/VnEsMfVco8SD8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i7aRsrcinvgr6GJucyewb5vIEdbjUBOmWMYTwuQjH64Ah3V8AeNaFBFHL6CTmaOYP D9N9NWuSTVsHaxgpYOg94N4IdaupTlPGOCXjuK08LqEZCBCq7Vf+eIGhcL/mzF/W1D ylSyAIiMsDNLpCF3V1tbrDYwD93jcSuMrhAz2rmE= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] SNI encryption (#795) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a85ef8fb4f_461d2b1f1a280f50236038"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 20 Jun 2018 16:50:59 -0000 ----==_mimepart_5b2a85ef8fb4f_461d2b1f1a280f50236038 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit +1 to @larseggert, but more importantly, every proposed SNI encryption system would require opt-in from the site. With that said, those sites should just give the middlebox the SNI encryption key. -- 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/795#issuecomment-398820402 ----==_mimepart_5b2a85ef8fb4f_461d2b1f1a280f50236038 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

+1 to @larseggert, but more importantly, every proposed SNI encryption system would require opt-in from the site. With that said, those sites should just give the middlebox the SNI encryption key.

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

----==_mimepart_5b2a85ef8fb4f_461d2b1f1a280f50236038-- From nobody Wed Jun 20 10:03:42 2018 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 A663212F1A2 for ; Wed, 20 Jun 2018 10:03:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 isZm6wbNzJ6J for ; Wed, 20 Jun 2018 10:03:36 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 1CA18130DEF for ; Wed, 20 Jun 2018 10:03:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529514215; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=vaO8DiOiH9UNyoTbkjl4XF9i5hsCVnNGhA5XiNV87Uk=; b=tPr9D6g22lhtZBUC+TbsUAiSITV6vyCCCQd0ILjceWqxRiFXHc2Od+Yj3NsVu4JY9DdJGch9 eD3lq6ggwmKy9jKHPV0dYNw3s58bafSpYHQPDDQGq8Yh2QZY/73+D6i2HQAP5v+FoAIcqbqm gZGs+goEmAn0pK7TUgNA/kflP00= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2a88e6.7fd6d74a35a0-smtp-out-n01; Wed, 20 Jun 2018 17:03:34 -0000 (UTC) Date: Wed, 20 Jun 2018 10:03:34 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2a88e65a59b_fef2b0c85113c14240ef@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] f94df3: Bilateral, error Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2a88e659e14_fef2b0c85113c1423962"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 17:03:38 -0000 ----==_mimepart_5b2a88e659e14_fef2b0c85113c1423962 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/disable_migration Home: https://github.com/quicwg/base-drafts Commit: f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b https://github.com/quicwg/base-drafts/commit/f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Bilateral, error **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2a88e659e14_fef2b0c85113c1423962-- From nobody Wed Jun 20 10:03:49 2018 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 CEF7F12F1A2 for ; Wed, 20 Jun 2018 10:03:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 VYHEHjnW_HNN for ; Wed, 20 Jun 2018 10:03:38 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7AEC130DEF for ; Wed, 20 Jun 2018 10:03:38 -0700 (PDT) Date: Wed, 20 Jun 2018 10:03:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529514218; bh=o02N5aldw4SuxbeunX+xWE8wyCjwulz+Tl5GUSlCdqQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Y8bIAqbON2yfDELay/Ghvt1WBaz+BdVw0HLvgK3c3NHRSYXzHad1FxJ/Pit0bsW+k yp9vuPDQOI/RASGZ1tNXBKQ647f4h6+8QLxsPcrPmlIxG9coCmDlxBwSzyGj6vqx3J +JCEmSSquYr9r4DD2kI49Ag0U2b2tnU18mZAKlgA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a88ea1fe3d_70752aaca7a74f58506359"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 20 Jun 2018 17:03:42 -0000 ----==_mimepart_5b2a88ea1fe3d_70752aaca7a74f58506359 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. f94df3a Bilateral, error -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1447/files/b789dd84f3b9dbd0182f8b674411368824afb22b..f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b ----==_mimepart_5b2a88ea1fe3d_70752aaca7a74f58506359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2a88ea1fe3d_70752aaca7a74f58506359-- From nobody Wed Jun 20 10:27:31 2018 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 44AEA130FFE for ; Wed, 20 Jun 2018 10:27:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 4206l71QexwZ for ; Wed, 20 Jun 2018 10:27:28 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 3EE44130E07 for ; Wed, 20 Jun 2018 10:27:28 -0700 (PDT) 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=3DJ/S3Dsjb7iWMpafOxZS+TMSa8=; b=sM+G8dZi3hZJnGOI J+4a9o3F8aqmpoQecXstH6RneAqBKXrTcOycWlkXpt4geeiFzw0Ny1QBg7pQ968V 3ZO0G3/YhVzaOiaM5E6G1tLWweqXovKYvpyu7JPPLppOYOQUXvdQlliXuLRKoDI8 QcvObYiBPK4cg3k+9PG1LxNmPR8= Received: by filter0061p1iad2.sendgrid.net with SMTP id filter0061p1iad2-20029-5B2A8E7E-5A 2018-06-20 17:27:26.991800224 +0000 UTC Received: from github-lowworker-39ccb07.cp1-iad.github.net (unknown [192.30.252.40]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id 2oU1WXNFRYOalh-rAh6txA for ; Wed, 20 Jun 2018 17:27:26.961 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-39ccb07.cp1-iad.github.net (Postfix) with ESMTP id E879540009C for ; Wed, 20 Jun 2018 10:27:26 -0700 (PDT) Date: Wed, 20 Jun 2018 17:27:27 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a8e7ee5df2_1fa52afbb319ef5415514"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2xxXHrOgLvVS5Iw6lcMRXS/XQ7/LSOgXVNaI rxbjXBhPf7/21z+ZiMl4qRM8d7H72pdp9Rmmzhr0F/Y/XuMKLVclakdjFleqHDHYUD1YJiUuUqG9j3 Q3xBN2/aEuqFIYQRM4O1mvOEHsj9so3OjX96Wk5huNfSTqyBKGhfVkmwYVdAA2s5XBgJykgxcftKvV g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 17:27:31 -0000 ----==_mimepart_5b2a8e7ee5df2_1fa52afbb319ef5415514 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm fine with either an explicit nonce or continuing to use ODCID as the PR currently does and including a minimum SCID length along with the "MUST change unless" text. The Initial packet does have extra room, in theory, but coalesced packets means we can use that extra room for 0-RTT data in the common case, so I'd rather not burn *too* many bytes that are only needed in this exceptional path. That makes an explicit nonce less preferred in my view. I'm sympathetic to the offload issue -- this is worse than PNE because it doesn't just take the encrypted bytes as input, it requires remembering them. -- 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/1451#issuecomment-398831433 ----==_mimepart_5b2a8e7ee5df2_1fa52afbb319ef5415514 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'm fine with either an explicit nonce or continuing to use ODCID as the= PR currently does and including a minimum SCID length along with the "MUST= change unless" text. The Initial packet does have extra room, in theory, = but coalesced packets means we can use that extra room for 0-RTT data in th= e common case, so I'd rather not burn too many bytes that are only= needed in this exceptional path. That makes an explicit nonce less prefer= red in my view.

I'm sympathetic to the offload issue -- this is worse than PNE because i= t doesn't just take the encrypted bytes as input, it requires remembering t= hem.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b2a8e7ee5df2_1fa52afbb319ef5415514-- From nobody Wed Jun 20 11:01:28 2018 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 3F60A130E02 for ; Wed, 20 Jun 2018 11:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 npRh0EetZrcd for ; Wed, 20 Jun 2018 11:01:24 -0700 (PDT) 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 6E99A130DFF for ; Wed, 20 Jun 2018 11:01:24 -0700 (PDT) Date: Wed, 20 Jun 2018 11:01:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529517682; bh=bdULaDkqfRx0Ll8X/2JuaFP2k5P205KcJ2Mglj7TphE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OjwZP83e0SH7jx/LuUcJztz9NM8GmvrW5Vi5/OQ7BQrLDY8vnkAipc10cwlvmY4uB kZHqjU93XMIvlBtqjc/fvGMgIeeJjpk/oQtbB3T/LLzS6b0UqlbbpSalZWDKRPtYkQ 4v6Fa+XUS/A4oizQ514DuRblgfW/34/ubHkKQOXA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a967288411_685a3f8b49508f84139263"; 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.26 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: Wed, 20 Jun 2018 18:01:27 -0000 ----==_mimepart_5b2a967288411_685a3f8b49508f84139263 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think the "compatible CID formats" piece of this doesn't matter. The recipient of a short header packet won't be able to identify the CID because the length is unknown. It will guess the length it probably used (assuming the remainder is payload) and generate a Stateless Reset with a random CID/body. But yes, in the absence of loss, this will continue forever. An attacker could start the process with a spoofed source address. Perhaps a suggestion that endpoints SHOULD limit the number of Stateless Resets they will send to a given address? If each side sends back even one fewer SR than it received incoming packets, the attacker doesn't get much return from its spoofed traffic. -- 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/1443#issuecomment-398842429 ----==_mimepart_5b2a967288411_685a3f8b49508f84139263 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think the "compatible CID formats" piece of this doesn't matter. Th= e recipient of a short header packet won't be able to identify the CID be= cause the length is unknown. It will guess the length it probably used (= assuming the remainder is payload) and generate a Stateless Reset with a = random CID/body.

But yes, in the absence of loss, this will continue forever. An attac= ker could start the process with a spoofed source address. Perhaps a sug= gestion that endpoints SHOULD limit the number of Stateless Resets they w= ill send to a given address? If each side sends back even one fewer SR t= han it received incoming packets, the attacker doesn't get much return fr= om its spoofed traffic.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2a967288411_685a3f8b49508f84139263-- From nobody Wed Jun 20 11:03:38 2018 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 2D26B130E02 for ; Wed, 20 Jun 2018 11:03:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 ksCX-RXgESBB for ; Wed, 20 Jun 2018 11:03:34 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 48198130DFF for ; Wed, 20 Jun 2018 11:03:34 -0700 (PDT) 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=Lm9SS2oQgxOcIRFtW80A9eoBeL0=; b=cbqkYI3floR+JHge 4SFXPNxUZideiLeEb9eFiWz1OWwxSSRbaYLx3VEiopaX1qF1p4THGK9VsY2v+MGn 8Mbil3QYrZfrtTrs9EDu1W+3fkYB69Y5efhciaMWsADNjcNWKCXk4vcp/3S6+5zy 6w2HFpa4g09cfMvPhGJSMJeMMmY= Received: by filter0624p1iad2.sendgrid.net with SMTP id filter0624p1iad2-30954-5B2A96F4-3 2018-06-20 18:03:32.063060254 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id EWcFUthWSOyi2zXVwYGPyw for ; Wed, 20 Jun 2018 18:03:31.938 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id E36F1C0740 for ; Wed, 20 Jun 2018 11:03:31 -0700 (PDT) Date: Wed, 20 Jun 2018 18:03:32 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a96f3def6a_39023f96023c8f847589e"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1/oFlc1gDBbOQ4aIcr3vIHpuOxbTPZkWEl46 +a4RD/k8jCudwsJiK9dizbElJTOz+IWU7kXU4F/PNv17Z4T/jGwjG75fhuzJULcVSKFUR9fA7KmmdI xMVtfJDC+dEcoS1kMD/nI/9KchZldcDwyWUvhrJInTfBnjQg8XudE1QTN3dQLtoykSt8DXZecft4Yg Y= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 18:03:37 -0000 ----==_mimepart_5b2a96f3def6a_39023f96023c8f847589e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1456. -- 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/1456#event-1691862761 ----==_mimepart_5b2a96f3def6a_39023f96023c8f847589e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1456.

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

----==_mimepart_5b2a96f3def6a_39023f96023c8f847589e-- From nobody Wed Jun 20 11:30:03 2018 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 58308130E02 for ; Wed, 20 Jun 2018 11:30:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pXpsIGiBc36e for ; Wed, 20 Jun 2018 11:29:59 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3260130DFA for ; Wed, 20 Jun 2018 11:29:58 -0700 (PDT) Date: Wed, 20 Jun 2018 11:29:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529519398; bh=aPUw6/sMPoYCSxVmglU0H6aSZ5lZbMIYTbn7f8NGuzM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=YkB7GeFwiGxp3v2u3ZcmEsK4WnjQ2gREKK68GN5In2aPwtmZo3sewgMR/jPnZ4LpP WGFm2tkKSXg7zdGV5CcrYNBufLZkfVeZa90vcfVZJYjhOLD9NFVKE69pRXvLuUHNpe 56+QtTEskHsPJ5yVeyq2BnPedHQolXbIAB6Sg1vA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2a9d265dfb0_320c2aadc598ef5c26347c"; 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.26 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: Wed, 20 Jun 2018 18:30:02 -0000 ----==_mimepart_5b2a9d265dfb0_320c2aadc598ef5c26347c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Suppose an endpoint is probing an alternate path to keep it available for future migration. (Probing periodically over cellular in case Wi-Fi goes away, for example.) The endpoint has N connection IDs outstanding and chooses to use one of them on a probing packet, which gets lost. When the endpoint retransmits the probe, it uses a different CID because it has been quiescent for a while. This probe gets through. At this point, the endpoint believes it has N-2 remaining CIDs to work with, while its peer believes it has N-1 CIDs still issued. Now the text about making sure your peer has outstanding CIDs becomes pointless, because the peers can't accurately estimate. Repeat this a couple times, and you might find yourself stuck behind "MUST NOT send additional packets until a NEW_CONNECTION_ID frame is received" because you've run out and the peer thinks you haven't. ACK tracking would let the endpoint detect that this has happened (all packets using CID A have been declared lost, so peer doesn't know I burned it), but that doesn't permit the endpoint to *fix* the problem. I think this ultimately leads us to a NEED_MORE_CIDS frame, unless anyone else has an idea. (Not quite CID_BLOCKED, because once you're blocked it's too late.) -- 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/1464 ----==_mimepart_5b2a9d265dfb0_320c2aadc598ef5c26347c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Suppose an endpoint is probing an alternate path to keep it available for future migration. (Probing periodically over cellular in case Wi-Fi goes away, for example.) The endpoint has N connection IDs outstanding and chooses to use one of them on a probing packet, which gets lost. When the endpoint retransmits the probe, it uses a different CID because it has been quiescent for a while. This probe gets through.

At this point, the endpoint believes it has N-2 remaining CIDs to work with, while its peer believes it has N-1 CIDs still issued. Now the text about making sure your peer has outstanding CIDs becomes pointless, because the peers can't accurately estimate. Repeat this a couple times, and you might find yourself stuck behind "MUST NOT send additional packets until a NEW_CONNECTION_ID frame is received" because you've run out and the peer thinks you haven't.

ACK tracking would let the endpoint detect that this has happened (all packets using CID A have been declared lost, so peer doesn't know I burned it), but that doesn't permit the endpoint to fix the problem. I think this ultimately leads us to a NEED_MORE_CIDS frame, unless anyone else has an idea. (Not quite CID_BLOCKED, because once you're blocked it's too late.)

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

----==_mimepart_5b2a9d265dfb0_320c2aadc598ef5c26347c-- From nobody Wed Jun 20 12:08:29 2018 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 15B2412872C for ; Wed, 20 Jun 2018 12:08:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 2l4P_DUSlg9K for ; Wed, 20 Jun 2018 12:08:25 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 6C64212777C for ; Wed, 20 Jun 2018 12:08:25 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529521704; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nPaOIpTsVhsnoCebEnV9YBGJHWoW1N+3GRD1BwQJE5A=; b=lG7aYf1w8D/jHnk1ukMKcr/3dsaV3md0tEUZvCxDiv1kjFnXGPOxb7zZMEYPavmq2/V7+Eji xVpKoutO/u+6NnSp9zZ1TUcngQyhsq517/kBEPklAfgdD6bD1wk0rjRiGwUUdKCxzQvMnq2O 9QmTMO7WOzOr+wIu9tG/owiGwEM= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2aa628.7fe0a43e2600-smtp-out-n01; Wed, 20 Jun 2018 19:08:24 -0000 (UTC) Date: Wed, 20 Jun 2018 12:08:23 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2aa62791e2c_614a2aaca0ae7c0839186@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d677fb: Count connection IDs used Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2aa627919fa_614a2aaca0ae7c083909c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 19:08:27 -0000 ----==_mimepart_5b2aa627919fa_614a2aaca0ae7c083909c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: d677fb1cba7e8ead45335ef4dd8edefd93de3e77 https://github.com/quicwg/base-drafts/commit/d677fb1cba7e8ead45335ef4dd8edefd93de3e77 Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Count connection IDs used **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2aa627919fa_614a2aaca0ae7c083909c-- From nobody Wed Jun 20 12:20:40 2018 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 C8DC5131106 for ; Wed, 20 Jun 2018 12:20:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nOlJmGoKiSh1 for ; Wed, 20 Jun 2018 12:20:29 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A13A113117B for ; Wed, 20 Jun 2018 12:20:29 -0700 (PDT) Date: Wed, 20 Jun 2018 12:20:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529522427; bh=DuMrq8LIHzzuq7sskWS/gp5V2vul9yMPfWU2aGaQeUA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T8ojGoN3sMmCNqeS2PBT3D1y8060e9l541jtaiZVxp3RKdVNc8QorSCXI4PwCCmYH tGJ++2RzrTQdVaFnIKcQKKi4BHWDYFDgyMD+UkTkBkXujzcfylv2QcC8KsM9KvkbNL QvV3FALF3/L3O7QNbQ6nP2KX4socqwojQ4Qw44Ac= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID ratcheting language is imprecise (#1452) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2aa8fba8e7a_286c2af4a6688f60435359"; 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.26 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: Wed, 20 Jun 2018 19:20:37 -0000 ----==_mimepart_5b2aa8fba8e7a_286c2af4a6688f60435359 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Packet loss makes this even harder, similar to the case in #1464. Using the counter approach, if you don't un-count a CID where all packets using it were lost, you'll fail to change CIDs the next time the peer changes. However, if you *do* un-count it, but any of the packets were declared lost in error, then you wind up in the same loop where your delayed packet causes the peer to change, which causes you to change, which causes the peer to change.... I'm starting to think we need the sequence numbers back to make this work, but with some additional text about probing packets on a different path being handled a bit differently. -- 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/1452#issuecomment-398866138 ----==_mimepart_5b2aa8fba8e7a_286c2af4a6688f60435359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Packet loss makes this even harder, similar to the case in #1464. Using the coun= ter approach, if you don't un-count a CID where all packets using it were= lost, you'll fail to change CIDs the next time the peer changes. Howeve= r, if you do un-count it, but any of the packets were declared l= ost in error, then you wind up in the same loop where your delayed packet= causes the peer to change, which causes you to change, which causes the = peer to change....

I'm starting to think we need the sequence numbers back to make this w= ork, but with some additional text about probing packets on a different p= ath being handled a bit differently.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2aa8fba8e7a_286c2af4a6688f60435359-- From nobody Wed Jun 20 12:22:25 2018 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 E4D0D131175 for ; Wed, 20 Jun 2018 12:22:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1nrvlwcOnoAM for ; Wed, 20 Jun 2018 12:22:12 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8E53131181 for ; Wed, 20 Jun 2018 12:22:12 -0700 (PDT) Date: Wed, 20 Jun 2018 12:22:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529522532; bh=YbunkCjhmtsx3zaDsstk71YLy6yLBlrkK8/G8hBgWhM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QDfc1tvQbhuVEHfvawlsKJi578O9lhKNyaXpqqL2wR1UWOvB+oVwfOK0a/1pnTmz1 I9WjeODMf3ZdJw++WczqUUKe/J+1dZhC79ZdB9/EBdMdzbtIHbG4fclMqqoVLv1vX2 2qUeK3O6ucqtrQu8IasflMCE0ktf1qTx54krir2A= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2aa9642cf7f_3b9c2abf33d14f58571893"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 19:22:24 -0000 ----==_mimepart_5b2aa9642cf7f_3b9c2abf33d14f58571893 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think it would be easier to detect resets, but that is apparently not an option. Rembering source address in a stateless context is not ideal. But exponential decay can be used: Whenever an endpoint feels the urge to send a reset, it should ignore that urge it with a probability x, 0 < x <= 1 such that reflected resets will eventually die out. -- 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/1443#issuecomment-398866569 ----==_mimepart_5b2aa9642cf7f_3b9c2abf33d14f58571893 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think it would be easier to detect resets, but that is apparently no= t an option.

Rembering source address in a stateless context is not ideal. But expo= nential decay can be used:

Whenever an endpoint feels the urge to send a reset, it should ignore = that urge it with a probability x, 0 < x <=3D 1 such that reflected= resets will eventually die out.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2aa9642cf7f_3b9c2abf33d14f58571893-- From nobody Wed Jun 20 12:34:07 2018 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 58D38131120 for ; Wed, 20 Jun 2018 12:33:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 62eIydu-eiz5 for ; Wed, 20 Jun 2018 12:33:54 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71D64130E2D for ; Wed, 20 Jun 2018 12:33:54 -0700 (PDT) Date: Wed, 20 Jun 2018 12:33:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529523233; bh=t/PQVcb4fOceRxiZOZHZ5v/XErjeENpmtCgt2Tq+oZM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XoPzMssKS2SnHNhr4u3SBuTEi0C+wUa+GWecDrOcignVbRSQx+KXiBMLl2sdHWP2S sMJSpgqDRs3mN9Uf7tHSNusSutFB/bUfGNkbdEBTmizEjyEYPnEVRiet+aqfS4umRW ioSvxPSEZUc25rGJcyiaEI82BJOaGN69/vvvkXwg= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2aac219fe9d_26303fd1b6f60f78438fa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 20 Jun 2018 19:33:58 -0000 ----==_mimepart_5b2aac219fe9d_26303fd1b6f60f78438fa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Somewhat OT, but it got me thinking - for long should a connection track a given path? Consider an drone traversing a futuristic public mesh wifi network there could be thousands of migrations over the lifetime of the connection. -- 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/1464#issuecomment-398869861 ----==_mimepart_5b2aac219fe9d_26303fd1b6f60f78438fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Somewhat OT, but it got me thinking - for long should a connection track a given path? Consider an drone traversing a futuristic public mesh wifi network there could be thousands of migrations over the lifetime of the connection.

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

----==_mimepart_5b2aac219fe9d_26303fd1b6f60f78438fa-- From nobody Wed Jun 20 13:37:15 2018 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 CE921130E86 for ; Wed, 20 Jun 2018 13:37:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 eW4N1U2SuNJo for ; Wed, 20 Jun 2018 13:37:12 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDC73130E33 for ; Wed, 20 Jun 2018 13:37:11 -0700 (PDT) Date: Wed, 20 Jun 2018 13:37:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529527030; bh=TTlEagvn15ClDofrkwawxvQ9q6DPyPkCvCz2RBrzV50=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mL/x27EUqqbElTo9SpoENQlz7nNd0xbgeyYA6VpRCFb/T8Dnb0jwxF4WOzIdwSwth Xotmilrcjp0s80XHPq6nd0A7xSA4oEj+2Buq+pkLE/pYmSu87MV474glYa4rgYX76S 6o/XJzvIa1adnZLR3IzvZmDOqKDKdS59/7sypoQ4= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2abaf6e5df3_57c72aab1d6ccf581617a4"; 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.26 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: Wed, 20 Jun 2018 20:37:14 -0000 ----==_mimepart_5b2abaf6e5df3_57c72aab1d6ccf581617a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Implementation specific. I'm inclined to say that once you've lost the local address, you can forget all paths associated with it, unless you have some local reason to believe it will come back. -- 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/1464#issuecomment-398888236 ----==_mimepart_5b2abaf6e5df3_57c72aab1d6ccf581617a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Implementation specific. I'm inclined to say that once you've lost the local address, you can forget all paths associated with it, unless you have some local reason to believe it will come back.

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

----==_mimepart_5b2abaf6e5df3_57c72aab1d6ccf581617a4-- From nobody Wed Jun 20 13:46:07 2018 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 0795D130EBF for ; Wed, 20 Jun 2018 13:46:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Zhg8We_49wB4 for ; Wed, 20 Jun 2018 13:46:02 -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 2ECE9130E1B for ; Wed, 20 Jun 2018 13:46:02 -0700 (PDT) Date: Wed, 20 Jun 2018 13:46:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529527560; bh=snPQOhO+5pENBcezOyRjzxdQWMRnh+lLawQ6wBTkQKo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hr9nDZdvwHh1g4hkfAWxHG0FzzZMVtrzmPMZmxrTT6lPLZMxx9Jmf9LPnzX4mpPKu pf8G1ifg4N2po1qFhf0kM4j+VyXOC66slPBrdIvdUhRQt8cIXqz/vH0NvEYAbZ2h+w N7giUpGoK2SxJvTk3UONLAF4L1zodxDJKiCDWJEQ= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2abd0827ce9_5b4b2ae98e0a4f54165e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 20 Jun 2018 20:46:05 -0000 ----==_mimepart_5b2abd0827ce9_5b4b2ae98e0a4f54165e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I do agree that it's implementation specific, but I still think it's something they spec should provide recommendations for. For @mikkelfj's scenario, I'm more worried about the server side. It keeps giving out more CIDs and the client keeps using them. Should we have a way for the client to explicitly tell the server that a particular old CID is no longer in use? Otherwise the best I can see the server doing it having some timer (idle timeout period?) per CID to age it out or just a simple max number of simultaneous CIDs to allow at any one time, and as new CIDs are given out, if there is no more room, the oldest is automatically aged out. -- 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/1464#issuecomment-398890796 ----==_mimepart_5b2abd0827ce9_5b4b2ae98e0a4f54165e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I do agree that it's implementation specific, but I still think it's s= omething they spec should provide recommendations for.

For @mikkelfj's scenario, I'm more= worried about the server side. It keeps giving out more CIDs and the cli= ent keeps using them. Should we have a way for the client to explicitly t= ell the server that a particular old CID is no longer in use? Otherwise t= he best I can see the server doing it having some timer (idle timeout per= iod?) per CID to age it out or just a simple max number of simultaneous C= IDs to allow at any one time, and as new CIDs are given out, if there is = no more room, the oldest is automatically aged out.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2abd0827ce9_5b4b2ae98e0a4f54165e5-- From nobody Wed Jun 20 13:56:57 2018 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 8BD50130EBF for ; Wed, 20 Jun 2018 13:56:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 8MdknAKW2d89 for ; Wed, 20 Jun 2018 13:56:52 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 C7A3E130E1B for ; Wed, 20 Jun 2018 13:56:52 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529528212; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=+sq2zriPgh+VmHsYbyQy7ipIfHpsIcCMQBR5OY9AiOY=; b=GLkgEVgxLUXO7RnRzzK/vB2JGqNZQNM3I8p3/tjtWmxRcRz/vPSrxvBB2ee8TMlhPFwyLtv7 LUFzWJ3DmlO2VHStlawsuOMqGIaj9szpiuZWe8lpdtClZ3UmuLZdSperG7d3l2UDP618c+FC bBdvGAys0XmEy7oa5Arifz9TyLQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b2abf93.7f9127eb2060-smtp-out-n02; Wed, 20 Jun 2018 20:56:51 -0000 (UTC) Date: Wed, 20 Jun 2018 13:56:50 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2abf9271495_34772ad19ec51c10958c6@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] acaced: Revert "Remove sequence number from NEW_CONNECTION... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2abf9270d5f_34772ad19ec51c1095799"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 20:56:55 -0000 ----==_mimepart_5b2abf9270d5f_34772ad19ec51c1095799 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: acaceda49b22560c3eeab3be18a45d79689c33d0 https://github.com/quicwg/base-drafts/commit/acaceda49b22560c3eeab3be18a45d79689c33d0 Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Revert "Remove sequence number from NEW_CONNECTION_ID" This reverts commit 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6. Commit: 4f8705840bad07c1f5a836df36b360631ba2b177 https://github.com/quicwg/base-drafts/commit/4f8705840bad07c1f5a836df36b360631ba2b177 Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Require CID sequence number ratcheting Compare: https://github.com/quicwg/base-drafts/compare/d677fb1cba7e...4f8705840bad **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2abf9270d5f_34772ad19ec51c1095799-- From nobody Wed Jun 20 14:07:58 2018 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 72DE9130E29 for ; Wed, 20 Jun 2018 14:07:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 iJyN2CoxSkRb for ; Wed, 20 Jun 2018 14:07:55 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 40B09130E1B for ; Wed, 20 Jun 2018 14:07:55 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529528874; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=mPz8TukGdCsa2a6GwFjOk02FmE/7aZ5qNrVfkGy3IdI=; b=AAnPtgk/PhMfCqwyh8ZKUv9iKYOgwFxmqI4hpgxCoP7RguR6vtUVFoz59VaLzFBO5e2stwGO VZO+CNjZZMT85vbgyiwcrFmfYkvQR/L4aoJtoRpmGbmNHQyFBTvMNWb2m906R2kSvOI7xjWY 9KfNPYrcBosxE57N6Z98bV/XkPQ= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2ac229.7fd6d737cf30-smtp-out-n01; Wed, 20 Jun 2018 21:07:53 -0000 (UTC) Date: Wed, 20 Jun 2018 14:07:52 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2ac228e955f_616f2b23abe7dc1457664@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] eda401: Prefer equality Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2ac228e91af_616f2b23abe7dc1457532"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 21:07:57 -0000 ----==_mimepart_5b2ac228e91af_616f2b23abe7dc1457532 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: eda401101ae367fc840dc5f38c33aef616f6a99d https://github.com/quicwg/base-drafts/commit/eda401101ae367fc840dc5f38c33aef616f6a99d Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Prefer equality **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2ac228e91af_616f2b23abe7dc1457532-- From nobody Wed Jun 20 14:35:42 2018 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 65B79130E34 for ; Wed, 20 Jun 2018 14:35:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vYtja5WAtTR8 for ; Wed, 20 Jun 2018 14:35:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE24130E18 for ; Wed, 20 Jun 2018 14:35:38 -0700 (PDT) Date: Wed, 20 Jun 2018 14:35:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529530537; bh=1DjEyoCg5BkTCeGAkzooJBnHCMjw14AXANp4dAPvRmY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=AbCjmaAGq/kRVviWwBRw0A3zbqEUsVKmjykscV9Im0I1ab4BSCwVyZUmQNmaUoVW4 osYXmHKanKPnEmo9cf4+ToFF8Tg/mJd5vXurG2WfdEShftdbzDHMnMNuBlbyaDQCL9 gDkHh+8J2sz/5BfJFCwEa9+SRwkPlFn8KMKvKC3c= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ac8a96d96_114c2afdc905ef503393b"; 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.26 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: Wed, 20 Jun 2018 21:35:41 -0000 ----==_mimepart_5b2ac8a96d96_114c2afdc905ef503393b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit After trying to find a better way to manage CID changes, probing, etc. I concluded that what we had before and removed is a superior place to start than anything else I'm coming up with. The result of this PR is that, while we no longer have packet number gaps (so #1280 is no longer an issue), the sequence of CIDs issued by each endpoint is once again ordered. On each path (local address), you know the sequence number of the CID you're currently using, and you can recognize the sequence number of the CID you're currently receiving (because you assigned it). Fixes #1452 by requiring that each CID change on a path move to a CID with a greater sequence number; you move to the CID with the matching sequence number if it's usable, but if it's not, you move to something with a higher sequence number. That will force your peer to meet you on that sequence number instead, and either way you land in equilibrium on each path. This improves, but doesn't totally fix, the two problems discussed on #1464: - You can forget the old CIDs you're allowed to use at any time that's convenient to you -- you just won't use them. Because the CID sequence must advance per path, you can forget old CIDs you've issued once every path has either moved past that sequence number or been abandoned. However, there's a slight possibility that peers will have different concepts of abandoned (particularly for probing on backup paths that are never migrated to), so we might need to mint a `RETIRE_CONNECTION_IDS` frame to tell the receiver that connection IDs with a sequence before X are no longer recognized by the sender. - Once you've moved to the CID with sequence number X, the peer knows you can't use CID X-1 on this path even if you've never used it; if you're on the last / next-to-last CID the peer issued, you need more, even if you have some old ones you could still use on a different path. However, if you have the bad luck to use your last CID for a probe which gets dropped and you're no longer able to send on that path, you can still get stuck if your peer is only giving you one CID at a time. This probably still requires a `REQUEST_CONNECTION_ID` frame. While I think the design is mostly sound, this is too wordy. I'd appreciate help making this more readable. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1465 -- Commit Summary -- * Revert "Remove sequence number from NEW_CONNECTION_ID" * Require CID sequence number ratcheting * Prefer equality -- File Changes -- M draft-ietf-quic-transport.md (46) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1465.patch https://github.com/quicwg/base-drafts/pull/1465.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/1465 ----==_mimepart_5b2ac8a96d96_114c2afdc905ef503393b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

After trying to find a better way to manage CID changes, probing, etc. I concluded that what we had before and removed is a superior place to start than anything else I'm coming up with.

The result of this PR is that, while we no longer have packet number gaps (so #1280 is no longer an issue), the sequence of CIDs issued by each endpoint is once again ordered. On each path (local address), you know the sequence number of the CID you're currently using, and you can recognize the sequence number of the CID you're currently receiving (because you assigned it).

Fixes #1452 by requiring that each CID change on a path move to a CID with a greater sequence number; you move to the CID with the matching sequence number if it's usable, but if it's not, you move to something with a higher sequence number. That will force your peer to meet you on that sequence number instead, and either way you land in equilibrium on each path.

This improves, but doesn't totally fix, the two problems discussed on #1464:

  • You can forget the old CIDs you're allowed to use at any time that's convenient to you -- you just won't use them. Because the CID sequence must advance per path, you can forget old CIDs you've issued once every path has either moved past that sequence number or been abandoned. However, there's a slight possibility that peers will have different concepts of abandoned (particularly for probing on backup paths that are never migrated to), so we might need to mint a RETIRE_CONNECTION_IDS frame to tell the receiver that connection IDs with a sequence before X are no longer recognized by the sender.
  • Once you've moved to the CID with sequence number X, the peer knows you can't use CID X-1 on this path even if you've never used it; if you're on the last / next-to-last CID the peer issued, you need more, even if you have some old ones you could still use on a different path. However, if you have the bad luck to use your last CID for a probe which gets dropped and you're no longer able to send on that path, you can still get stuck if your peer is only giving you one CID at a time. This probably still requires a REQUEST_CONNECTION_ID frame.

While I think the design is mostly sound, this is too wordy. I'd appreciate help making this more readable.

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

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

Commit Summary

  • Revert "Remove sequence number from NEW_CONNECTION_ID"
  • Require CID sequence number ratcheting
  • Prefer equality

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 mute the thread.

----==_mimepart_5b2ac8a96d96_114c2afdc905ef503393b-- From nobody Wed Jun 20 14:48:01 2018 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 0172A130EEF for ; Wed, 20 Jun 2018 14:47:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pWrhI5v-Xm2S for ; Wed, 20 Jun 2018 14:47:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED18D130F04 for ; Wed, 20 Jun 2018 14:47:41 -0700 (PDT) Date: Wed, 20 Jun 2018 14:47:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529531261; bh=IqrlABe1J+yerUs4fSN5tAAVOI54go6JxL9w4MOtBBw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a8EsEG0+caaWLc8xONb1OdaiZvzU8MP7lgSUE07UfJsg+x7pAlKnl6sBn1o5LK6Zi 1jlQIUgkETsbQD7M7BngDFyVDtZplENIHD6Tm3jgjI7rizEqQv7YRypZrWXzeTU17W AjGKefCY8DfbtxyF3OaTupYAgyG7BHmOvTq5OkFk= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acb7d3d3ab_46923fdb66cc8f7c57414"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 20 Jun 2018 21:47:55 -0000 ----==_mimepart_5b2acb7d3d3ab_46923fdb66cc8f7c57414 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -422,6 +439,14 @@ sending any ACK frames in response. In this case they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +should use a very short ack delay, such as 1ms. ACK frames may be It's ack delay everywhere in this doc. -- 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/1450#discussion_r196953259 ----==_mimepart_5b2acb7d3d3ab_46923fdb66cc8f7c57414 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -422,6 +439,14 @@ sending any ACK frames in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 
+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+should use a very short ack delay, such as 1ms.  ACK frames may be

It's ack delay everywhere in this doc.

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

----==_mimepart_5b2acb7d3d3ab_46923fdb66cc8f7c57414-- From nobody Wed Jun 20 14:49:09 2018 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 59DA7130E18 for ; Wed, 20 Jun 2018 14:49:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 prPI_KCMSgIQ for ; Wed, 20 Jun 2018 14:48:59 -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 B6ECA130F36 for ; Wed, 20 Jun 2018 14:48:52 -0700 (PDT) Date: Wed, 20 Jun 2018 14:48:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529531331; bh=2w8wKXCQV3bJGoi242F5/FQcfUdw+aCksMGNl07wQ1Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qBk1qC8Lwz8VqIbFKBRUlJisiq22X4W7PEyveq1g0sGaW9sZl/h1E7UsB9XOwXvZy +zEUB0KP7KMBqgGzLGDP/pou5KQb/XLnESoRwRlqMlEqIUhQ3Ota/Q1zB0sX+RTKrh EiItw2RgISh6Mn6k1yf2xXGCe/zoUfEC1aJ9H2zA= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acbc3e0f87_32513f8e56018f78104092"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 20 Jun 2018 21:49:07 -0000 ----==_mimepart_5b2acbc3e0f87_32513f8e56018f78104092 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -422,6 +439,14 @@ sending any ACK frames in response. In this case they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +should use a very short ack delay, such as 1ms. ACK frames may be +sent immediately when the crypto stack indicates all data for that +encryption level has been received. + This part is only about sending ACKs, but good point on the EndOfEarlyData. As spec'd, that'd be TLP'd before being RTO'd, FYI. -- 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/1450#discussion_r196953517 ----==_mimepart_5b2acbc3e0f87_32513f8e56018f78104092 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -422,6 +439,14 @@ sending any ACK frames in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 
+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+should use a very short ack delay, such as 1ms.  ACK frames may be
+sent immediately when the crypto stack indicates all data for that
+encryption level has been received.
+

This part is only about sending ACKs, but good point on the EndOfEarlyData. As spec'd, that'd be TLP'd before being RTO'd, FYI.

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

----==_mimepart_5b2acbc3e0f87_32513f8e56018f78104092-- From nobody Wed Jun 20 14:52:45 2018 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 7C0B1130E26 for ; Wed, 20 Jun 2018 14:52:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 AQY7FI8KqlWK for ; Wed, 20 Jun 2018 14:52:41 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 06BF7130E18 for ; Wed, 20 Jun 2018 14:52:40 -0700 (PDT) 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=5JATcFoOqTrnRIDUILcvdn5eKQ4=; b=kWLRY0ZkU+HscjvN WfrwnKlgrtj+4g3Y7MqRrGWMifQMub2hII6doKSwij5iXztcUtDt//vISlaoA62/ MN1mB8NDvhbVa5PS0AoeWX/olBlUjEIrXcmG/jMJXP/6XQZuR0DJ9OHunjneCF+b xlbHdGdfQuiolT3M9d9pbApnzSc= Received: by filter1088p1las1.sendgrid.net with SMTP id filter1088p1las1-16833-5B2ACCA8-16 2018-06-20 21:52:40.531763988 +0000 UTC Received: from github-lowworker-c7d2ff2.cp1-iad.github.net (unknown [192.30.252.32]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id aA9mkzJmQgew7vFfStRKBQ for ; Wed, 20 Jun 2018 21:52:40.389 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-c7d2ff2.cp1-iad.github.net (Postfix) with ESMTP id 5C6DA4C0265 for ; Wed, 20 Jun 2018 14:52:40 -0700 (PDT) Date: Wed, 20 Jun 2018 21:52:40 +0000 (UTC) From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acca859fb7_757c2b06c2494f5073298"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak01kJzRCgtMxX2yaM134n/R9g4GtOiLsWZAz2 M+kep9/pGKyT7YWGJguDRM/ngsr6V6dTthi80EKVUOU0fuVDNMWYN/Yc5NQ3wEsvPobzW9fw7QcDVN L9LFJE80AUZR0AAEsVDgoNoZFxxAnfl0nstkrIMLiIvQ3NhuPWWHCmAKfX2nknp8YroQMjwxy9z6cm c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 21:52:44 -0000 ----==_mimepart_5b2acca859fb7_757c2b06c2494f5073298 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks requested changes on this pull request. The text here is really confusing and I don't understand what it supposed to be going on. Perhaps you can explain more in the comments and we can figure out some better text. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection +ID with a later sequence number each time the connection ID changes. Once a +connection ID has been used, connection IDs with an earlier sequence number MUST +NOT be used for packets with a greater packet number from that local address. I'm confused as to how this works with probing a new path (but not moving to it). Assume I am currently on Path A using CID 1, then I probe Path B with CID 2. This text seems to state that I may not use CID 1 on Path A with any packet number greater than I used to probe Path B with CID 2. Is that correct? > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, Is there a real reason we can consider the handshake CID `0` and start from there? I'd rather not have to deal with negative numbers in my code. -- 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/1465#pullrequestreview-130601503 ----==_mimepart_5b2acca859fb7_757c2b06c2494f5073298 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks requested changes on this pull request.

The text here is really confusing and I don't understand what it supposed to be going on. Perhaps you can explain more in the comments and we can figure out some better text.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection
+ID with a later sequence number each time the connection ID changes.  Once a
+connection ID has been used, connection IDs with an earlier sequence number MUST
+NOT be used for packets with a greater packet number from that local address.

I'm confused as to how this works with probing a new path (but not moving to it). Assume I am currently on Path A using CID 1, then I probe Path B with CID 2. This text seems to state that I may not use CID 1 on Path A with any packet number greater than I used to probe Path B with CID 2. Is that correct?

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

Is there a real reason we can consider the handshake CID 0 and start from there? I'd rather not have to deal with negative numbers in my code.

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

----==_mimepart_5b2acca859fb7_757c2b06c2494f5073298-- From nobody Wed Jun 20 14:55:59 2018 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 E470D130E26 for ; Wed, 20 Jun 2018 14:55:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 EI-2IAqS0ceK for ; Wed, 20 Jun 2018 14:55:56 -0700 (PDT) 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 2719E130E48 for ; Wed, 20 Jun 2018 14:55:56 -0700 (PDT) Date: Wed, 20 Jun 2018 14:55:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529531755; bh=tUr4Pro6HbaqDBPihN3md6YSM+C9E7RQrpkDLoXHPb8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=igTxkEQCf2VGl5FdtsY8+81K8/M1QJrn07OmPv5xS1O5RK2yLvCI/WD8YwndP3YlS fJSQoXSaNxu2OXB/37ruU/qBtplmiPpnXv3k+Jl1Ev956QaP0AjP4cQzBIxHUv2nN6 SqSTJ8ZIJGsiGIrRfdw++MIc68Gf8ljriK+DsMc8= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acd6b53190_469a3fdb66cc8f7c27999a"; 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.26 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: Wed, 20 Jun 2018 21:55:58 -0000 ----==_mimepart_5b2acd6b53190_469a3fdb66cc8f7c27999a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection +ID with a later sequence number each time the connection ID changes. Once a +connection ID has been used, connection IDs with an earlier sequence number MUST +NOT be used for packets with a greater packet number from that local address. At that point, you may not use a CID < 1 on path A, and may not use a CID < 2 on path B. You also aren't allowed to use CID = 2 on path A, because it's been used on a different path. -- 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/1465#discussion_r196955161 ----==_mimepart_5b2acd6b53190_469a3fdb66cc8f7c27999a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection
+ID with a later sequence number each time the connection ID changes.  Once a
+connection ID has been used, connection IDs with an earlier sequence number MUST
+NOT be used for packets with a greater packet number from that local address.

At that point, you may not use a CID < 1 on path A, and may not use a CID < 2 on path B. You also aren't allowed to use CID = 2 on path A, because it's been used on a different path.

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

----==_mimepart_5b2acd6b53190_469a3fdb66cc8f7c27999a-- From nobody Wed Jun 20 14:57:08 2018 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 2930D130EC4 for ; Wed, 20 Jun 2018 14:57:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 v_iSWmXgMo13 for ; Wed, 20 Jun 2018 14:57:04 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 CE0A2130EC6 for ; Wed, 20 Jun 2018 14:57:03 -0700 (PDT) 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=1tkwDiERwQg7KvxghERBRgc9I78=; b=tbKa6XALWxkC/uq+ nXAebhDSvVMdM3TG7PwcOhdU+KWIAJfQrHrMjGBMPTLc18jxc9n1w9ssz2EsmquG 85frBMPF4GvdVF8yl2VbYja8qpEf1U0HW5JdeCcxI6B+JFW4ezP8YYthGxJMmkPk COWZ5e6Immq7Gwc8mE/QzxHndRs= Received: by filter0282p1iad2.sendgrid.net with SMTP id filter0282p1iad2-12347-5B2ACDAD-B 2018-06-20 21:57:01.460367368 +0000 UTC Received: from github-lowworker-d2dd71d.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id nBIyTVHPR3WWT33hcHiLCg for ; Wed, 20 Jun 2018 21:57:01.381 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-d2dd71d.cp1-iad.github.net (Postfix) with ESMTP id 5AACA88138D for ; Wed, 20 Jun 2018 14:57:01 -0700 (PDT) Date: Wed, 20 Jun 2018 21:57:01 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acdad58dd6_6bf63f892e9a0f781219d8"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3vZwBp3Y+hnweyMul0Nf8hfEN380I81ZP7Tp IEqURov/FFyhIE5OGW4GskEEyQVs9q8Y8Sr7dG2WXQucBmVNqCyjMH0rOSLu4nwfPy5mf9zIJC7F+D /BeWhIAgJR+bGZRE98twwylfq1MNdMGsk3oKsFKCMD5mzvJEXgEt3ePpY1eYhVW0y8I6UK2ZR4I1R+ s= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 21:57:07 -0000 ----==_mimepart_5b2acdad58dd6_6bf63f892e9a0f781219d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, Probably not. This is just the existing text. It's actually a little worse than that, because the Server's Preferred Address gives the client a CID to use when probing, so there can actually be two CIDs prior to the first one issued by frame. -- 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/1465#discussion_r196955405 ----==_mimepart_5b2acdad58dd6_6bf63f892e9a0f781219d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

Probably not. This is just the existing text. It's actually a little worse than that, because the Server's Preferred Address gives the client a CID to use when probing, so there can actually be two CIDs prior to the first one issued by frame.

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

----==_mimepart_5b2acdad58dd6_6bf63f892e9a0f781219d8-- From nobody Wed Jun 20 15:01:46 2018 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 C4719130EC8 for ; Wed, 20 Jun 2018 15:01:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 anobDwgje00Y for ; Wed, 20 Jun 2018 15:01:35 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 487B5130EC6 for ; Wed, 20 Jun 2018 15:01:35 -0700 (PDT) Date: Wed, 20 Jun 2018 15:01:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532094; bh=0nfQ++43dNa6x4rMYnSqYrAa4QfyRYDoxxq9O3frmaI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1MHQGMHknRmn2tZKpTFAgrWbO/DEQMyTMWC/9n92oyjp/0qi2+Ka8felWUp5oxpIl yYOLWU4DGgpOAFkxe1NCof+LgCgogkAXezE9uZg4n8MfkIVPkRaUFHF1VcEvK7p5bb cICdmwg8iU/oMTW4oDW/+L8BccLzEDkC1A/hWPfA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acebe90def_2e532b0408332f5c65237"; 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.26 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: Wed, 20 Jun 2018 22:01:39 -0000 ----==_mimepart_5b2acebe90def_2e532b0408332f5c65237 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection +ID with a later sequence number each time the connection ID changes. Once a +connection ID has been used, connection IDs with an earlier sequence number MUST +NOT be used for packets with a greater packet number from that local address. Basically: - For each path, the CID sequence number must advance, but the currently-in-use CID for each path is unrelated. You could keep probing forever with CID2 on Path B even while Path A has moved up to CID 39, so long as the path isn't abandoned. - Each CID can only be used on a single path. If you used CID2 on Path B, you have to skip CID2 on Path A. -- 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/1465#discussion_r196956391 ----==_mimepart_5b2acebe90def_2e532b0408332f5c65237 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection
+ID with a later sequence number each time the connection ID changes.  Once a
+connection ID has been used, connection IDs with an earlier sequence number MUST
+NOT be used for packets with a greater packet number from that local address.

Basically:

  • For each path, the CID sequence number must advance, but the currently-in-use CID for each path is unrelated. You could keep probing forever with CID2 on Path B even while Path A has moved up to CID 39, so long as the path isn't abandoned.
  • Each CID can only be used on a single path. If you used CID2 on Path B, you have to skip CID2 on Path A.

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

----==_mimepart_5b2acebe90def_2e532b0408332f5c65237-- From nobody Wed Jun 20 15:01:58 2018 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 30CD2130EC6 for ; Wed, 20 Jun 2018 15:01:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FJ7PpYw5u5wS for ; Wed, 20 Jun 2018 15:01:49 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DCAE130EBF for ; Wed, 20 Jun 2018 15:01:49 -0700 (PDT) Date: Wed, 20 Jun 2018 15:01:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532108; bh=FvCv47gHVNITrrOQ4dW4kFVRzmuZmSE4R0M42s8Ageo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zYKvDDTc9Sp45jZ1cryFlNlxNxaC2Bc2EsnXo+3cv5L1bj+x9+SGdg8i0gIoNEz73 KicwdoddO/9xSmKX1GhVeUTT1s4+BiLzKKi1NIUbitYLQsl8aP9AUiN0GcnOQ852D5 mdvcvL+LPmKuZInxE/L6g94mHadQyFVx66+jfidU= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acecc87daf_4a703fc1cb6e0f88993ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 20 Jun 2018 22:01:52 -0000 ----==_mimepart_5b2acecc87daf_4a703fc1cb6e0f88993ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection +ID with a later sequence number each time the connection ID changes. Once a +connection ID has been used, connection IDs with an earlier sequence number MUST +NOT be used for packets with a greater packet number from that local address. Ok, maybe instead of "Once a connection ID has been used, connection IDs with an earlier sequence number MUST NOT be used for packets with a greater packet number from that local address." something like "Once a new connection ID is used, earlier connection IDs MUST NOT be used for new packets sent from the new local address". -- 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/1465#discussion_r196956451 ----==_mimepart_5b2acecc87daf_4a703fc1cb6e0f88993ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection
+ID with a later sequence number each time the connection ID changes.  Once a
+connection ID has been used, connection IDs with an earlier sequence number MUST
+NOT be used for packets with a greater packet number from that local address.

Ok, maybe instead of "Once a connection ID has been used, connection IDs with an earlier sequence number MUST NOT be used for packets with a greater packet number from that local address." something like "Once a new connection ID is used, earlier connection IDs MUST NOT be used for new packets sent from the new local address".

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

----==_mimepart_5b2acecc87daf_4a703fc1cb6e0f88993ef-- From nobody Wed Jun 20 15:06:24 2018 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 180C0130EC6 for ; Wed, 20 Jun 2018 15:06:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NOEeGeSwTSVu for ; Wed, 20 Jun 2018 15:06:19 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556B3130ED1 for ; Wed, 20 Jun 2018 15:06:12 -0700 (PDT) Date: Wed, 20 Jun 2018 15:06:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532371; bh=MnVjqu/5yhkaK2WB5TnqcMHW2gAW2vrAUPXRZQ3rLeM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hEN26qQvnf6cqzkz30J72kvX8phQgXmIMSMEciZ8c6KBotwfJGU9Z+TYkoJeHduYS JcfM/rGQtjpwsT9V2Lm5CX6QRUG6kU7XyRSYV0UWqfBEq2ol83AbY3sje1xy0oZOW+ R8olLSIBa/9oJ660bvYRTsJ/VscCobY3Mv2G70L8= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acfd3812e2_4f282af1955d0f50535ec"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 20 Jun 2018 22:06:22 -0000 ----==_mimepart_5b2acfd3812e2_4f282af1955d0f50535ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, Then maybe we define handshake as `0`, the server's preferred address as `1` (even if not present) and then new CIDs start from there (i.e. `2`). I don't see any reason to prevent gaps in the CID sequence number space either. -- 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/1465#discussion_r196957444 ----==_mimepart_5b2acfd3812e2_4f282af1955d0f50535ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

Then maybe we define handshake as 0, the server's preferred address as 1 (even if not present) and then new CIDs start from there (i.e. 2). I don't see any reason to prevent gaps in the CID sequence number space either.

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

----==_mimepart_5b2acfd3812e2_4f282af1955d0f50535ec-- From nobody Wed Jun 20 15:07:37 2018 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 40254130EC6 for ; Wed, 20 Jun 2018 15:07:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 BZTndfVHxcRj for ; Wed, 20 Jun 2018 15:07:33 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 DBD6A130EBF for ; Wed, 20 Jun 2018 15:07:32 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529532452; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=aU21px/K+YkBMlyLPXHd8btXHYiwpKJavwpgSNMImVk=; b=vSSNmfLkrutILzegli7r3ZfpPzRmACjtiAqQYOXLzMlFEFvwExx4AL2SwkSQjnRFHIq4jRWN yqGn3HemHfoWUPBllbE4gxQdUuHXanLfD5HPsB9vudPxbpaP9jVyuTAZDJhNyIJXDKqLoZq6 xW6Z6u7A8E/8gvlsqV3f7sL3/ME= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2ad023.7f87d48a3cf0-smtp-out-n03; Wed, 20 Jun 2018 22:07:31 -0000 (UTC) Date: Wed, 20 Jun 2018 15:07:30 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2ad022e1ad5_5c482afe22ff7bfc81461@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 0d6755: Nick's reword Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2ad022e1724_5c482afe22ff7bfc8135c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 22:07:35 -0000 ----==_mimepart_5b2ad022e1724_5c482afe22ff7bfc8135c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: 0d675544aaa5263bbfa2c0a3e1879e18dc71200e https://github.com/quicwg/base-drafts/commit/0d675544aaa5263bbfa2c0a3e1879e18dc71200e Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Nick's reword **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2ad022e1724_5c482afe22ff7bfc8135c-- From nobody Wed Jun 20 15:07:42 2018 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 03977130EC6 for ; Wed, 20 Jun 2018 15:07:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oJpx7EKnPN3t for ; Wed, 20 Jun 2018 15:07:34 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3EA6130EBF for ; Wed, 20 Jun 2018 15:07:34 -0700 (PDT) Date: Wed, 20 Jun 2018 15:07:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532454; bh=+wbROb4piXiOS4/c/5/58nibXC4WUHM4C+oflcKCDN8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dOj4jA+L5OtGcbfyJ2clkcWWsPqEGjKE8KjoJ5vi20TumXAcQU+APhtPLHfz1HvWk 8uIGDszSYc47xNnVX+bYFpjossKjXEg0Fg+5Lxv5MpXTbpbW3Mvj11d6z2krqq3iFC xCnHk3GXfrIlKHpRvkZWCmCNypeZ7sNQEe+RJako= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad026b92d_eb53fc5304c8f8072632"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 20 Jun 2018 22:07:36 -0000 ----==_mimepart_5b2ad026b92d_eb53fc5304c8f8072632 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 0d67554 Nick's reword -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1465/files/eda401101ae367fc840dc5f38c33aef616f6a99d..0d675544aaa5263bbfa2c0a3e1879e18dc71200e ----==_mimepart_5b2ad026b92d_eb53fc5304c8f8072632 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2ad026b92d_eb53fc5304c8f8072632-- From nobody Wed Jun 20 15:12:26 2018 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 499B3130E22 for ; Wed, 20 Jun 2018 15:12:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nCzgYFVXkvET for ; Wed, 20 Jun 2018 15:12:22 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACD87130E51 for ; Wed, 20 Jun 2018 15:12:22 -0700 (PDT) Date: Wed, 20 Jun 2018 15:12:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532742; bh=Ku7MRz4oK6uqmtX066K4MAQ35jIBujK9bgzi21uKdec=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WT1M4ChCJq6hKZDkN++CeheKnLnSi/VbnxxlT8SQU2JJ7waEfpixevN9Vonb44lgR zPO6MmhWsAw83PhxAN5kwUGP9hEweaV++de9HmDOsoGS9tRnsBCn505pywpP4ITej5 /Urth0iBvsXNbXjie8N3OF0PTtFI3oeKk+hLzGds= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad146983f_6f072b1e03410f541433d0"; 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.26 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: Wed, 20 Jun 2018 22:12:25 -0000 ----==_mimepart_5b2ad146983f_6f072b1e03410f541433d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, The alternative being -2, -1, and starting from 0. I think the logic there is the principle that we should try to avoid there being invalid values, and 0/1 would be invalid values still present in the frame. If the frame can carry a 0, then 0 should be the first value value. -- 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/1465#discussion_r196958757 ----==_mimepart_5b2ad146983f_6f072b1e03410f541433d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

The alternative being -2, -1, and starting from 0. I think the logic there is the principle that we should try to avoid there being invalid values, and 0/1 would be invalid values still present in the frame. If the frame can carry a 0, then 0 should be the first value value.

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

----==_mimepart_5b2ad146983f_6f072b1e03410f541433d0-- From nobody Wed Jun 20 15:15:07 2018 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 E1B79130F07 for ; Wed, 20 Jun 2018 15:14:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 lRZZP4kBxE3F for ; Wed, 20 Jun 2018 15:14:58 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12356130ED1 for ; Wed, 20 Jun 2018 15:14:58 -0700 (PDT) Date: Wed, 20 Jun 2018 15:14:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529532897; bh=quXTdgxbnoG2D7YWAHd9Kp0tKbB4zpzZjS2Owsg99WE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SLVNK0hcuDwuoZixqMtNDZOkVLdIX/xOdW5YfEAuldv9sI7+/JIz4ku4rcS8bR8K1 G5tkRIGfa66KboC4+ZVYSIRhmJ8RdGOrgJsD4Es65DugJD+QEwpW42u/IxRu+U4ZPM WsQRb7w3vHuAb0hXhri6f9XN06BE+VaIOo6+KN30= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad1e13723b_6292ab053026f6057288"; 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.26 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: Wed, 20 Jun 2018 22:15:04 -0000 ----==_mimepart_5b2ad1e13723b_6292ab053026f6057288 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, This also creates an odd situation in that SPA prompts the client to probe, but the server won't have a corresponding CID at that sequence number, so it will have to use the first CID the client issued to it -- *if* the client issues one with/before the probe! -- which will force the client to advance again. -- 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/1465#discussion_r196959300 ----==_mimepart_5b2ad1e13723b_6292ab053026f6057288 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

This also creates an odd situation in that SPA prompts the client to probe, but the server won't have a corresponding CID at that sequence number, so it will have to use the first CID the client issued to it -- if the client issues one with/before the probe! -- which will force the client to advance again.

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

----==_mimepart_5b2ad1e13723b_6292ab053026f6057288-- From nobody Wed Jun 20 15:16:02 2018 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 9FB3F130E68 for ; Wed, 20 Jun 2018 15:16:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 f4Ti8BsV6wXQ for ; Wed, 20 Jun 2018 15:15:58 -0700 (PDT) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 AD375130E22 for ; Wed, 20 Jun 2018 15:15:58 -0700 (PDT) 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=H/gkorBOOfTieKJWavTxWbTLKZs=; b=mt6rzFjm030xmp3t wFR1ueGRbx1FkpZ7JFO4VKj0uqkUtBQOD/pRhhLMNCSiuxLyRueyD4TJ6u7ZGziF CTeX51dbEwxY0TmUgApk21L1gh3pRGsorJxSnXOU+hG+O1Tsuwi7EXmvkQ5cHjyt AME5jMVSGMwH9WuMxPMZFDp23NE= Received: by filter1059p1las1.sendgrid.net with SMTP id filter1059p1las1-25281-5B2AD21E-6 2018-06-20 22:15:58.328602614 +0000 UTC Received: from github-lowworker13-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0048p1mdw1.sendgrid.net (SG) with ESMTP id wpDWsEuQTkGaxSiGD8rgdA for ; Wed, 20 Jun 2018 22:15:58.008 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker13-cp1-prd.iad.github.net (Postfix) with ESMTP id E5DAA22374 for ; Wed, 20 Jun 2018 15:15:57 -0700 (PDT) Date: Wed, 20 Jun 2018 22:15:58 +0000 (UTC) From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad21de43f3_61b93f866479cf7812728a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2yAe0TbsWt3jxNYJzMoqmhnZfwcZaYPgEldI uMpaoAD2YSta12tpC8UCPkYmn4HROSE6HE2N2wl/gvGVBMuKhKA7GYq0072ljMP4Kpi87naqFtTTYz wPSai6aTNt+WBJMIAMLlnDFGqnHDm0BwW0yMHcsw13qIJXIbB9tbHgiC8Cy/e1vBLmkt1oBUd1hHnS I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 22:16:01 -0000 ----==_mimepart_5b2ad21de43f3_61b93f866479cf7812728a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit One way of fixing this is to forbid sending a stateless reset unless the size of the stateless reset will be smaller than the packet that has triggered the stateless reset. Note that endpoints are already required to send a large packet after quiescence, if they want to see stateless reset in case the server has lost state. See the following statement in [section 6.10.4](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.6.10.4): > An endpoint SHOULD NOT send a stateless reset that is significantly larger than the packet it receives. -- 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/1443#issuecomment-398915066 ----==_mimepart_5b2ad21de43f3_61b93f866479cf7812728a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One way of fixing this is to forbid sending a stateless reset unless the= size of the stateless reset will be smaller than the packet that has trigg= ered the stateless reset.

Note that endpoints are already required to send a large packet after qu= iescence, if they want to see stateless reset in case the server has lost s= tate. See the following statement in sec= tion 6.10.4:

An endpoint SHOULD NOT send a stateless reset that is significantly larg= er than the packet it receives.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b2ad21de43f3_61b93f866479cf7812728a-- From nobody Wed Jun 20 15:24:51 2018 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 B3E29130F36 for ; Wed, 20 Jun 2018 15:24:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4VxEteANgAqs for ; Wed, 20 Jun 2018 15:24:46 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF3E3130F18 for ; Wed, 20 Jun 2018 15:24:45 -0700 (PDT) Date: Wed, 20 Jun 2018 15:24:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529533485; bh=shrVjdZtUmYISXdsjgDW7XoqVlRR7amxtgSneSBKklo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ldFKbNgoXbPaGedi34FKf8W65HovgrmIRHIkHV9qlHAtgelGr9otnEN1Ig75o0Zls 4LWiqBbE1E9oKltC3geLqnTODmY8G3HAhp+tnI4YUWlG/SrD6f/yAZ8r6e0x09qFpj Z+j6jRnld9NxOA3nTOQqdTszfIdzBkoAgbdi178Y= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad42d1e81_40d83fb1c35f8f8415011b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 20 Jun 2018 22:24:50 -0000 ----==_mimepart_5b2ad42d1e81_40d83fb1c35f8f8415011b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett: > @kazuho why longer than 8 octets and not >=8 octets? > > I would like the simple RETRY case to work as well, which is the server doesn't want to change the CID at all, and it is the terminal node, so I don't want to require senders of RETRY to be required to change CID. I agree. My intent was to say `>= 8`. Sorry for the confusion. > Related question: What CID is the client deriving the key for INITIAL packets from? I was thinking all INITIAL packets used the same key, but if the terminal server may not have seen the client's first DCID, that doesn't work unless the original DCID is put somewhere the final server can read in the token. I agree with your observation, and think it would make sense to state that the DCID field of the Initial packet that carries the first Client Hello (i.e. the one that also gets padded up to 1280 octets) will be used as the key material. -- 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/1451#issuecomment-398917049 ----==_mimepart_5b2ad42d1e81_40d83fb1c35f8f8415011b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett:

@kazuho why longer than 8 octets and = not >=3D8 octets?

I would like the simple RETRY case to work as well, which is the serve= r doesn't want to change the CID at all, and it is the terminal node, so = I don't want to require senders of RETRY to be required to change CID.

I agree. My intent was to say >=3D 8. Sorry for the co= nfusion.

Related question: What CID is the client deriving the key for INITIAL = packets from? I was thinking all INITIAL packets used the same key, but i= f the terminal server may not have seen the client's first DCID, that doe= sn't work unless the original DCID is put somewhere the final server can = read in the token.

I agree with your observation, and think it would make sense to state = that the DCID field of the Initial packet that carries the first Client H= ello (i.e. the one that also gets padded up to 1280 octets) will be used = as the key material.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2ad42d1e81_40d83fb1c35f8f8415011b-- From nobody Wed Jun 20 15:49:32 2018 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 B8A88130E2F for ; Wed, 20 Jun 2018 15:49:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BvUH_UmSlH5a for ; Wed, 20 Jun 2018 15:49:29 -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 EE3C71277BB for ; Wed, 20 Jun 2018 15:49:28 -0700 (PDT) Date: Wed, 20 Jun 2018 15:49:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529534968; bh=kFbMCL86GkDuyId4xKB1jsZYFZNRHiqqVu9z0Z2BSRM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TKuBHnTRSUtHpSCXi0MXFohsemjowWbXREqL3gpCjsWsAEOFnTQvW55dcBdO1NXc1 py0joDFIo6OVdnsKNzN33MCTGKDMAVtzq3yi9Sb6x8D3RhgI99OGnDVALROvunWY1F 7POSBOcmalp0WW/Um8B8WP+d456I1Ni6Ca9LpQs8= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ad9f7f20e7_43202b1c99f3cf6013395b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 20 Jun 2018 22:49:31 -0000 ----==_mimepart_5b2ad9f7f20e7_43202b1c99f3cf6013395b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett: > Related question: What CID is the client deriving the key for INITIAL packets from? I was thinking all INITIAL packets used the same key, but if the terminal server may not have seen the client's first DCID, that doesn't work unless the original DCID is put somewhere the final server can read in the token. This is an interesting question. If we are to permit running DOS mitigation devices that do not share some secrets with the servers, we would be required to state that the Initial keys would match to the DCID field of the Initial packet that carries the first ClientHello. However, I am not sure if that is the right path forward, because defining such behavior would mean that somebody else can setup a middlebox that sets the Initial key to the same value for all connections that it sees (e.g., by sending a Retry with SCID field of `0000000000000000` for all connections), effectively nullifying the merit of having obfuscation. Admittedly, this kind of attack can only be applied to server deployments that does not validate the token field generated by an on-path device (e.g., by sharing the secret between the DoS mitigation device and the server). But my question is: do we want to even allow such server deployments to be set up? -- 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/1451#issuecomment-398921875 ----==_mimepart_5b2ad9f7f20e7_43202b1c99f3cf6013395b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett:

Related question: What CID is the client deriving the key for INITIAL = packets from? I was thinking all INITIAL packets used the same key, but i= f the terminal server may not have seen the client's first DCID, that doe= sn't work unless the original DCID is put somewhere the final server can = read in the token.

This is an interesting question.

If we are to permit running DOS mitigation devices that do not share s= ome secrets with the servers, we would be required to state that the Init= ial keys would match to the DCID field of the Initial packet that carries= the first ClientHello.

However, I am not sure if that is the right path forward, because defi= ning such behavior would mean that somebody else can setup a middlebox th= at sets the Initial key to the same value for all connections that it see= s (e.g., by sending a Retry with SCID field of 0000000000000000 for all connections), effectively nullifying the merit of having obfu= scation.

Admittedly, this kind of attack can only be applied to server deployme= nts that does not validate the token field generated by an on-path device= (e.g., by sharing the secret between the DoS mitigation device and the s= erver).

But my question is: do we want to even allow such server deployments t= o be set up?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2ad9f7f20e7_43202b1c99f3cf6013395b-- From nobody Wed Jun 20 16:11:40 2018 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 BF42F130E72 for ; Wed, 20 Jun 2018 16:11:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.501 X-Spam-Level: X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 5b2ZmFBXejlc for ; Wed, 20 Jun 2018 16:11:36 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 618BE130E45 for ; Wed, 20 Jun 2018 16:11:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529536295; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=IRAAFvDeWHocO5jJNCb2ztoBgp3Su4AUOnwV1gwwI9c=; b=VQ47GO04f77rQmRrPouaKquNv6bcr7cSR9JEChnPiOKDgVbCwMzO1R+/lxIXeWfCQKHpIOfe zJ0VmE1f/qVj0dqJq0H1qmSEODI2/FMPhMaAmpsURzN3XtXpbu8XIiuFu4d3fwY9sWFrCyp0 LatUoYBtVQuD6KHEqPx+Gbyomns= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b2adf26.7fc6b808e930-smtp-out-n01; Wed, 20 Jun 2018 23:11:34 -0000 (UTC) Date: Wed, 20 Jun 2018 16:11:33 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b2adf25c5df8_70bb2b2a32203c08228e0@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e33eb1: Allow non-RFC6066 methods for indicating server do... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2adf25c5726_70bb2b2a32203c082275b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 20 Jun 2018 23:11:38 -0000 ----==_mimepart_5b2adf25c5726_70bb2b2a32203c082275b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni-again Home: https://github.com/quicwg/base-drafts Commit: e33eb1e3d98eada16612ea2eee9c0cb5ce5309dd https://github.com/quicwg/base-drafts/commit/e33eb1e3d98eada16612ea2eee9c0cb5ce5309dd Author: Jana Iyengar Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Allow non-RFC6066 methods for indicating server domain. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2adf25c5726_70bb2b2a32203c082275b-- From nobody Wed Jun 20 16:13:00 2018 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 A4D69130E04 for ; Wed, 20 Jun 2018 16:12:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FNqWU4dKRPeg for ; Wed, 20 Jun 2018 16:12:57 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF235130E35 for ; Wed, 20 Jun 2018 16:12:56 -0700 (PDT) Date: Wed, 20 Jun 2018 16:12:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529536374; bh=PPw6MKeRql8qCewKqzDFkGR+dy4Hon55nUQ/mmhuJ+k=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Im+Tz9XSMwuSoHqKuVxts5WG2rfYev04nZCvIZM7Y8NhmkyRoZd+4DptDDlwV2DoG Or5/zwjxDwKBf6Ugdys4PpXMzoWL0kfaoi0E+9dlVkLEwJtm+Jfo96k2FZXMswrEOq 0C4AzT7UkYMxYLufpgv20cJ22MODgRSUjak58TT0= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Allow non-RFC6066 methods for indicating server domain (#1466) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2adf7643fec_73ee2af650e0cf603765f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 20 Jun 2018 23:12:59 -0000 ----==_mimepart_5b2adf7643fec_73ee2af650e0cf603765f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closes #1459. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1466 -- Commit Summary -- * Allow non-RFC6066 methods for indicating server domain. -- File Changes -- M draft-ietf-quic-http.md (8) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1466.patch https://github.com/quicwg/base-drafts/pull/1466.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/1466 ----==_mimepart_5b2adf7643fec_73ee2af650e0cf603765f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closes #1459.

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

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

Commit Summary

  • Allow non-RFC6066 methods for indicating server domain.

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 mute the thread.

----==_mimepart_5b2adf7643fec_73ee2af650e0cf603765f-- From nobody Wed Jun 20 16:16:53 2018 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 741E5130E72 for ; Wed, 20 Jun 2018 16:16:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 taw79Aayp-by for ; Wed, 20 Jun 2018 16:16:50 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF7A130E35 for ; Wed, 20 Jun 2018 16:16:50 -0700 (PDT) Date: Wed, 20 Jun 2018 16:16:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529536609; bh=cQk9s3ghWVjB8T/bIh19l6ZrkGfRfKTucBl5Cw6hPeE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HSDc005l+v1ZmKW3TldTW5kk7O85waJAeifUlmdELyt3IlLVQUQElqcrDgOlSW56p Uimo98u6uHgb1v7Ee1w03OwhUy9ON2dcRIkqsXzeh4jZaCl/IxaDK52eXFvUqnS8JH i1mfkbLduAufwPYtb4hiB6GiJ42+GvAZYIs2yEWk= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow non-RFC6066 methods for indicating server domain (#1466) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ae06137465_57d92ac4be6caf54129425"; 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.26 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: Wed, 20 Jun 2018 23:16:52 -0000 ----==_mimepart_5b2ae06137465_57d92ac4be6caf54129425 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. -- 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/1466#pullrequestreview-130621022 ----==_mimepart_5b2ae06137465_57d92ac4be6caf54129425 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

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

----==_mimepart_5b2ae06137465_57d92ac4be6caf54129425-- From nobody Wed Jun 20 16:20:30 2018 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 29389130F14 for ; Wed, 20 Jun 2018 16:20:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uqFFOPIfF3Q8 for ; Wed, 20 Jun 2018 16:20:07 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66890130EE0 for ; Wed, 20 Jun 2018 16:20:07 -0700 (PDT) Date: Wed, 20 Jun 2018 16:20:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529536806; bh=QbWRiUNzMBXPibcWETTDFlVKUYDP0pGfzunS0phYxww=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l92VnRCbKNyflCwCLXFkHS1eYufKTB55pzTYomluLbwqB23vI98y7DBXIGtcnkMVa OpFaeWtSGBTtPUvObUAsqSQNv4zYPgE8dV+OUv6F9rghXYUSGeZGS05vxMeQQu+081 WOCaCWRgSD3lojJaE84S/zt5F4g1VFigvnSIeKi4= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ae126b36be_5b363f8721b66f88364d1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 20 Jun 2018 23:20:24 -0000 ----==_mimepart_5b2ae126b36be_5b363f8721b66f88364d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It is our (Microsoft's) goal to use Retry for DDoS mitigation and possibly load balancing. In both cases the middle box operating on behalf of the QUIC server would likely have little or no shared state with the QUIC server. This is a very high priority for our Azure scenarios. In order to support these scenarios, we would need the Retry packet to not rely on some shared secret. -- 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/1451#issuecomment-398927508 ----==_mimepart_5b2ae126b36be_5b363f8721b66f88364d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It is our (Microsoft's) goal to use Retry for DDoS mitigation and poss= ibly load balancing. In both cases the middle box operating on behalf of = the QUIC server would likely have little or no shared state with the QUIC= server. This is a very high priority for our Azure scenarios. In order t= o support these scenarios, we would need the Retry packet to not rely on = some shared secret.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2ae126b36be_5b363f8721b66f88364d1-- From nobody Wed Jun 20 18:56:18 2018 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 52BCC130FE4 for ; Wed, 20 Jun 2018 18:56:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 cvhniJJZeBZ6 for ; Wed, 20 Jun 2018 18:56:11 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 98BC2130FCA for ; Wed, 20 Jun 2018 18:56:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529546164; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Biu7X9TkE3JuEXk+xXz5268Fff7xuFUtCPFnITqom5Q=; b=NQsCPNK0DZPgl2H80pCfnSgGEqtD64OgXXVkJ1PsCYRRRV8tj05qdQ/f2K5hQ3MVE9HSJjUL y3ifq+zUrwu215wEr0BSa+QBxywoj3/8Kh+1esbpgaPfwwtEMWVjBZdxzJ+0z4/67udBWGUq GIMraV2fUQLUaeEBTg8m5V1V1Mk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2b05b4.7effd96a1540-smtp-out-n03; Thu, 21 Jun 2018 01:56:04 -0000 (UTC) Date: Wed, 20 Jun 2018 18:56:03 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b2b05b320d11_4fe52ab73f60dc10128ca@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 2c1ca8: using Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2b05b32096d_4fe52ab73f60dc1012732"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 21 Jun 2018 01:56:14 -0000 ----==_mimepart_5b2b05b32096d_4fe52ab73f60dc1012732 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni-again Home: https://github.com/quicwg/base-drafts Commit: 2c1ca8ad91798a63893233c083f10d6456523d0a https://github.com/quicwg/base-drafts/commit/2c1ca8ad91798a63893233c083f10d6456523d0a Author: Jana Iyengar Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- using **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2b05b32096d_4fe52ab73f60dc1012732-- From nobody Wed Jun 20 18:56:28 2018 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 0E921130FC4 for ; Wed, 20 Jun 2018 18:56:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Q5Ajc-McgXjm for ; Wed, 20 Jun 2018 18:56:15 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57A7E130FE2 for ; Wed, 20 Jun 2018 18:56:08 -0700 (PDT) Date: Wed, 20 Jun 2018 18:56:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529546166; bh=TZkg2Te9yIsf3OmMN/S0vJvbva21W8grzTnaD9PpX00=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w93tHUzc4+zFXxOAIUvImoFomXWjla3kGhtu6aYQOFcMF/zzlAkXx702aeWXUkICc Q7Tvq1iHNrJNT/d+PwyMKILQ3W2eDFCKgSyYFU4700t190bGcs+RIU+UEQ4TazwtDK lCY9upGfkU/HmgCRqBadWmDfJpCJ/wflPcN0kka4= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow non-RFC6066 methods for indicating server domain (#1466) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b05b6c1148_36c73fd866e68f88138291"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: janaiyengar X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 21 Jun 2018 01:56:22 -0000 ----==_mimepart_5b2b05b6c1148_36c73fd866e68f88138291 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @janaiyengar pushed 1 commit. 2c1ca8a using -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1466/files/e33eb1e3d98eada16612ea2eee9c0cb5ce5309dd..2c1ca8ad91798a63893233c083f10d6456523d0a ----==_mimepart_5b2b05b6c1148_36c73fd866e68f88138291 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2b05b6c1148_36c73fd866e68f88138291-- From nobody Wed Jun 20 18:59:19 2018 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 72209130FB1 for ; Wed, 20 Jun 2018 18:59:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 v3vIpTF-22KA for ; Wed, 20 Jun 2018 18:59:17 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 DFEA2130E5D for ; Wed, 20 Jun 2018 18:59:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529546356; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=LQ0N3xunj8QvUZg4R96pmqANv8pOQAM2onok/6m8SFo=; b=c4M3PxvZ7OTAA129kd2de39eVSJlHUjzk2J7m4xmuZ4tQR1TAvFSMVVw5FKhnbqX5Bph1mMa LpfwnuHmW5E6KitPRp47e6SlD0EUshqIk/odDgIeYi911Kp9aEBjrdiW2yCum+wMcxDMYme1 ep32ZgQTXD3TL5invEAporCRRmA= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2b0674.7f8df39b67b0-smtp-out-n02; Thu, 21 Jun 2018 01:59:16 -0000 (UTC) Date: Wed, 20 Jun 2018 18:59:15 -0700 From: janaiyengar Reply-To: janaiyengar To: quic-issues@ietf.org Message-ID: <5b2b0673db08e_6ea92b10161e1c10503fe@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 084178: Allow non-RFC6066 methods for indicating server do... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2b0673daae1_6ea92b10161e1c10502d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 21 Jun 2018 01:59:19 -0000 ----==_mimepart_5b2b0673daae1_6ea92b10161e1c10502d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 084178aab8c1d6148f61e4222f008585043f02b2 https://github.com/quicwg/base-drafts/commit/084178aab8c1d6148f61e4222f008585043f02b2 Author: janaiyengar Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Allow non-RFC6066 methods for indicating server domain (#1466) * Allow non-RFC6066 methods for indicating server domain. * using **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2b0673daae1_6ea92b10161e1c10502d0-- From nobody Wed Jun 20 18:59:29 2018 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 E8DBD130FEA for ; Wed, 20 Jun 2018 18:59:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Y2qkpHT9nIsH for ; Wed, 20 Jun 2018 18:59:20 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E932130E5D for ; Wed, 20 Jun 2018 18:59:20 -0700 (PDT) Date: Wed, 20 Jun 2018 18:59:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529546359; bh=h9Ro/82V4J6aS13aNSfF3PQZjDPR76a/ipIUw4uRdsg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ILuBUzou2H0kGEvyjtai4DbySUTC5qX8ysWDnSobrJRO4sqZGp0JvpUDxEKnjTXGi UI1AddKLLJcjSMN7sCuDRXFS5z82DhR/tMIg9MpK35rvIi7pduBxEo7C0DFBdYk0MB 41xYsC5pwwlL7KRgpFgkuyTdeRO74uT4oheacGII= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Soften SNI requirement (#1459) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b06776f810_23522b1297da4f603026d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 21 Jun 2018 01:59:24 -0000 ----==_mimepart_5b2b06776f810_23522b1297da4f603026d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1459 via #1466. -- 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/1459#event-1692563553 ----==_mimepart_5b2b06776f810_23522b1297da4f603026d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1459 via #1466.

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

----==_mimepart_5b2b06776f810_23522b1297da4f603026d-- From nobody Wed Jun 20 18:59:35 2018 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 55AC0130FF2 for ; Wed, 20 Jun 2018 18:59:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 dKxWcka_xiEX for ; Wed, 20 Jun 2018 18:59:20 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9336B130FB1 for ; Wed, 20 Jun 2018 18:59:20 -0700 (PDT) Date: Wed, 20 Jun 2018 18:59:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529546359; bh=Flygwvd4a/2bKkB8OzZ+4PQuxhTIFlAPryICtAx20gs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=t0K81hKYbr/W9W43zf09W0B41Y5tK7leIBczWv9iyflQu9ld1uuwW3ENqmARyclgc mwQuOzlRFgIWjcbLChKxER8CA0fKYT0t8VjIqucyJKlE2Jb/a5FnPEDtzbUuoI/9MQ EvlC5aZEUtBo7Cht6Rp8XWeb2HWnPYcCS+RFnNC8= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Allow non-RFC6066 methods for indicating server domain (#1466) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b0677b2ec4_46412ab4ec704f6055730"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 21 Jun 2018 01:59:24 -0000 ----==_mimepart_5b2b0677b2ec4_46412ab4ec704f6055730 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1466. -- 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/1466#event-1692563550 ----==_mimepart_5b2b0677b2ec4_46412ab4ec704f6055730 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1466.

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

----==_mimepart_5b2b0677b2ec4_46412ab4ec704f6055730-- From nobody Wed Jun 20 19:58:14 2018 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 81C55130E79 for ; Wed, 20 Jun 2018 19:58:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cLn-4mJyjJW8 for ; Wed, 20 Jun 2018 19:58:10 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 962C0130E27 for ; Wed, 20 Jun 2018 19:58:10 -0700 (PDT) Date: Wed, 20 Jun 2018 19:58:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529549889; bh=6DBUdjVhoKlbddkjALBlRk1ZwaSVoLUnsd9tonskkf4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2eTLaCRSsq0w/k5XyPbg7Md0UzCRjjC2Bu3uEZAb0XjA535NY1TI+efwT9GfQGFhg L3pFviczKWhViPcPtiNbY8XMqIlxlh3Bv/TmMLVh3E5zI0FJUucZKD6x8oGxjIecSr jkdVHlZoDwvD6t2yBYekILGfAaGDbSXsyuWfkljU= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b1441275bf_15a2afa9a8d4f544127a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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.26 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: Thu, 21 Jun 2018 02:58:13 -0000 ----==_mimepart_5b2b1441275bf_15a2afa9a8d4f544127a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit huitema commented on this pull request. Busy implementing this. It would be much easier to work draft-13 than parsing the PR... > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. I am busy implementing this, and I have a small issue with the "MAY appear in packets of any encryption level." How do I verify that the packets are sent as intended? For example, what if I receive a CRYPTO_HS frame with offset 500 in an handshake-protected, and another CRYPTO_HS frame with an overlapping offset in an application-data protected packet? I think there is a subtle interaction there between offset sequencing in CRYPTO_HS and per-stream packet sequence numbers. > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. This changes coalesced packets from an optional performance-oriented feature to an almost mandatory security related feature. We should make clear that sending coalesced packets is optional. -- 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/1450#pullrequestreview-130214629 ----==_mimepart_5b2b1441275bf_15a2afa9a8d4f544127a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@huitema commented on this pull request.

Busy implementing this. It would be much easier to work draft-13 than parsing the PR...

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

I am busy implementing this, and I have a small issue with the "MAY appear in packets of any encryption level." How do I verify that the packets are sent as intended? For example, what if I receive a CRYPTO_HS frame with offset 500 in an handshake-protected, and another CRYPTO_HS frame with an overlapping offset in an application-data protected packet?

I think there is a subtle interaction there between offset sequencing in CRYPTO_HS and per-stream packet sequence numbers.

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

This changes coalesced packets from an optional performance-oriented feature to an almost mandatory security related feature. We should make clear that sending coalesced packets is optional.

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

----==_mimepart_5b2b1441275bf_15a2afa9a8d4f544127a-- From nobody Wed Jun 20 20:07:56 2018 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 783101311B0 for ; Wed, 20 Jun 2018 20:07:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nThayb-L6M-s for ; Wed, 20 Jun 2018 20:07:43 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE5C61311A5 for ; Wed, 20 Jun 2018 20:07:43 -0700 (PDT) Date: Wed, 20 Jun 2018 20:07:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529550462; bh=/A7p6VFUY3HnTilM12ppylk9QhqqvUpu1XDypopXITs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dS9Vzn+MXTZWsbwFW2phIX5NO1uck7SA3SH3/LtapfYZtJ8qsIwYmH54VbeT1clEm FuX6CjjtPRfJEthp4z43Ay+vzyMBUoxKViV5q/q6KuYhKZaMGKcJ9+sKMWLtUKLPrY Jp4uVL5oYZKcBgN9twFqxcGZSWAhEzFQlcAa6KZw= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b167ed7e37_7d7c3fccfd15cf848474b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 21 Jun 2018 03:07:55 -0000 ----==_mimepart_5b2b167ed7e37_7d7c3fccfd15cf848474b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. @huitema: > I am busy implementing this, and I have a small issue with the "MAY appear in packets of any encryption level." How do I verify that the packets are sent as intended? For example, what if I receive a CRYPTO_HS frame with offset 500 in an handshake-protected, and another CRYPTO_HS frame with an overlapping offset in an application-data protected packet? My assumption is that such check will be provided as an API or a guideline by the TLS stack, and that therefore it is unnecessary to clarify in the specification on how that should be done. For example, the `ptls_handle_messages` function of [picotls](https://github.com/h2o/picotls/pull/141) accepts the epoch as the argument, and returns an error if a TLS messages was being received in an incorrect epoch. -- 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/1450#discussion_r196999359 ----==_mimepart_5b2b167ed7e37_7d7c3fccfd15cf848474b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

@huitema:

I am busy implementing this, and I have a small issue with the "MAY appear in packets of any encryption level." How do I verify that the packets are sent as intended? For example, what if I receive a CRYPTO_HS frame with offset 500 in an handshake-protected, and another CRYPTO_HS frame with an overlapping offset in an application-data protected packet?

My assumption is that such check will be provided as an API or a guideline by the TLS stack, and that therefore it is unnecessary to clarify in the specification on how that should be done.

For example, the ptls_handle_messages function of picotls accepts the epoch as the argument, and returns an error if a TLS messages was being received in an incorrect epoch.

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

----==_mimepart_5b2b167ed7e37_7d7c3fccfd15cf848474b-- From nobody Wed Jun 20 22:40:37 2018 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 A46811311FC for ; Wed, 20 Jun 2018 22:40:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 uSu7n-VUtCHq for ; Wed, 20 Jun 2018 22:40:30 -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 B7001131229 for ; Wed, 20 Jun 2018 22:40:30 -0700 (PDT) Date: Wed, 20 Jun 2018 22:40:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529559629; bh=COoLRi2BS2N59b2Q9Foe+9o1A2DDkruvzMcem40atLk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C0SebeBh62ujhMQgRa7Ov2yPv19L6Bojbkqzf1IaSuNXLdcXgtFaCy+lCRtJb1l1l 7jbNH+li44wcqAwGyXVzb/1NDQ6JjWJ9YTSPwTYVqk8jRoCknfyPVnEiD67FvPk536 pKZoflZXDvpt2yjrwrCibFJMatcHcXfQ2SKZ4rIQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b3a4d82cc6_1fc83fc0b9696f7c2094f3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 21 Jun 2018 05:40:35 -0000 ----==_mimepart_5b2b3a4d82cc6_1fc83fc0b9696f7c2094f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > It is our (Microsoft's) goal to use Retry for DDoS mitigation and possibly load balancing. That's understandable. I'd anticipate that others will do the same thing. > In both cases the middle box operating on behalf of the QUIC server would likely have little or no shared state with the QUIC server. May I ask why you think that it is not a good idea to require every one of us to share some small amount of secret (e.g. encryption key) between the middleboxes and the servers than we would be running? As stated in my previous comment, not sharing opens an attack vector. There could be other attack vectors since lack of shared state allows anyone to run the middlebox. Considering that, I think it makes sense to *require* sharing state, under the assumption that doing so is not hard. -- 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/1451#issuecomment-398982420 ----==_mimepart_5b2b3a4d82cc6_1fc83fc0b9696f7c2094f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It is our (Microsoft's) goal to use Retry for DDoS mitigation and poss= ibly load balancing.

That's understandable. I'd anticipate that others will do the same thi= ng.

In both cases the middle box operating on behalf of the QUIC server wo= uld likely have little or no shared state with the QUIC server.

May I ask why you think that it is not a good idea to require every on= e of us to share some small amount of secret (e.g. encryption key) betwee= n the middleboxes and the servers than we would be running?

As stated in my previous comment, not sharing opens an attack vector. = There could be other attack vectors since lack of shared state allows any= one to run the middlebox. Considering that, I think it makes sense to require sharing state, under the assumption that doing so is not ha= rd.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b3a4d82cc6_1fc83fc0b9696f7c2094f3-- From nobody Wed Jun 20 22:49:46 2018 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 C46C913102A for ; Wed, 20 Jun 2018 22:49:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FSECVJfBG6oG for ; Wed, 20 Jun 2018 22:49:42 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28A89130F20 for ; Wed, 20 Jun 2018 22:49:42 -0700 (PDT) Date: Wed, 20 Jun 2018 22:49:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529560181; bh=5INoOnkTdeq/Dq0R76XzwtKowPr4p9VdZGPwqhx0XB0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BbPLs4BSabSFYJ64/Iv782MLstvFj+rHxMwzZ+aud0OOrUTfQM+LoBBFA0L4Nfs00 CBDrYXsSEYhfdOlqlpBRQ36EY3G86esoH5VsgxMgOd5XdU0uQ38S1iEgjJ0kwWIXIN nm7GTC1BTPVTxIL68wSlWt4WyzlKJne/qBh6vuJ8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b3c7541b14_72293fd62d04cf842083d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 21 Jun 2018 05:49:44 -0000 ----==_mimepart_5b2b3c7541b14_72293fd62d04cf842083d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > One way of fixing this is to forbid sending a stateless reset unless the size of the stateless reset will be smaller than the packet that has triggered the stateless reset. This would require a significant size reduction which could be observable (I still don't understand why the reset must be hidden). It would also not address transmissions of many very small messages in separate packets. I think the statistically dropping every N'th packet, say 4'th, would work well because in most cases the reset happen as expected, and when not, it happens on retransmission just as if a packet were lost. -- 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/1443#issuecomment-398983982 ----==_mimepart_5b2b3c7541b14_72293fd62d04cf842083d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One way of fixing this is to forbid sending a stateless reset unless t= he size of the stateless reset will be smaller than the packet that has t= riggered the stateless reset.

This would require a significant size reduction which could be observa= ble (I still don't understand why the reset must be hidden). It would als= o not address transmissions of many very small messages in separate packe= ts.

I think the statistically dropping every N'th packet, say 4'th, would = work well because in most cases the reset happen as expected, and when no= t, it happens on retransmission just as if a packet were lost.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b3c7541b14_72293fd62d04cf842083d5-- From nobody Wed Jun 20 22:58:08 2018 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 7323D13102A for ; Wed, 20 Jun 2018 22:58:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Ss7E_1i8-wT8 for ; Wed, 20 Jun 2018 22:58:03 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3EFF130F20 for ; Wed, 20 Jun 2018 22:58:02 -0700 (PDT) Date: Wed, 20 Jun 2018 22:58:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529560682; bh=OzBFjxunudbRNTi6lYFzZiYAYJhFU0D2fKfeNXC1P6w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sPY1WFW0pzL4+i3TuZtVQ7jqDEfyM38K3MdCOLtWRXuzv+3K+75VQOzWvFMOxwYM7 ZRxHbTA4HeSlR4Mw8O+sEB6mukPkfw+xw5+M3isngVK0yFx5sBAUlvwiIAr8ncMwR6 G6E3/FoH+V2BiqTGkLAP1XQazWYGw22oeTKkoLNk= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b3e6a1ece0_1f7a3fc0b9696f7c23831"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 21 Jun 2018 05:58:06 -0000 ----==_mimepart_5b2b3e6a1ece0_1f7a3fc0b9696f7c23831 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I believe the initial packet should always contain 1280 bytes, also after RETRY, otherwise an attacker might learn how to construct retry SCID's and use a second flight INITIAL as a DDoS vector. The initial key should also be derived based on the NONCE in the current INITIAL packet. So, as I suggested before, it makes sense to carry the NONCE separately and make the initial DCID empty - at cannot be used for safe routing anyway and it simplifies routing logic because LB's don't have to know if the INITIAL DCID is random or not, they just have to take a decision based on emptiness. The source SCID cannot be used as that NONCE without adding complexity to the clients LB infrastructure in a P2P server configuration. So I believe the NONCE should be a separate field. And it will not waste any space if the premise holds that all initial packets must be 1280 to prevent attacks. -- 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/1451#issuecomment-398985376 ----==_mimepart_5b2b3e6a1ece0_1f7a3fc0b9696f7c23831 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I believe the initial packet should always contain 1280 bytes, also af= ter RETRY, otherwise an attacker might learn how to construct retry SCID'= s and use a second flight INITIAL as a DDoS vector.

The initial key should also be derived based on the NONCE in the curre= nt INITIAL packet. So, as I suggested before, it makes sense to carry the= NONCE separately and make the initial DCID empty - at cannot be used for= safe routing anyway and it simplifies routing logic because LB's don't h= ave to know if the INITIAL DCID is random or not, they just have to take = a decision based on emptiness.

The source SCID cannot be used as that NONCE without adding complexity= to the clients LB infrastructure in a P2P server configuration. So I bel= ieve the NONCE should be a separate field. And it will not waste any spac= e if the premise holds that all initial packets must be 1280 to prevent a= ttacks.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b3e6a1ece0_1f7a3fc0b9696f7c23831-- From nobody Wed Jun 20 23:15:04 2018 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 6294713102A for ; Wed, 20 Jun 2018 23:15:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ZupGh1Y2J0h0 for ; Wed, 20 Jun 2018 23:15:00 -0700 (PDT) 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 E6DBD130EE8 for ; Wed, 20 Jun 2018 23:14:59 -0700 (PDT) Date: Wed, 20 Jun 2018 23:14:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529561698; bh=L3noGjl4wiJ70yAndeDpcnefl5sMnsTSkx06J+5P5hs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VWMmPVkaV/j15awnUOqPN59ZmK/mVRY7OLYqYSME6iSi7imqzWE+ShKIpcEt/0It0 xQIcBGP1LNt43pKUhRWQXD2xepP0vPQGIM9G+8yRHOPAGN/yOvHUYZBtMz3u/8gPnL 10ps/LAUjesp7T7TqvoeM3OZMeMzR+c6HF1EwBj8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b4262ee387_21a32b2523054f60295263"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 21 Jun 2018 06:15:02 -0000 ----==_mimepart_5b2b4262ee387_21a32b2523054f60295263 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit With the iteration specific NONCE reflected in RETRY, a client can easily drop secondary retry responses to older iterations of retries. But the NONCE does not have be reflected because the response would use a key derived from that NONCE thus failing verification if it doesn't match. Using packet numbers to count iterations would simplify operations, but are not strictly necessary. I n this form the INITIAL packet must have packet number that identifies the retry attempt number, starting at 0 and the retry response must reflect that packet number. Late handshake responses to older iterations may be preferable to new retry responses due to man-on-side races. This can be detected via trial decryption of older NONCE derived keys, but it is simpler if the first server handshake packet number reflects the clients INITIAL packet number. A NONCE could be generated randomly, or it could be using counter mode encryption such that the INITIAL packet number is an IV encrypting a base NONCE. Using counter mode avoids having to store several NONCE's in case an old handshake is received. -- 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/1451#issuecomment-398988314 ----==_mimepart_5b2b4262ee387_21a32b2523054f60295263 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

With the iteration specific NONCE reflected in RETRY, a client can eas= ily drop secondary retry responses to older iterations of retries. But th= e NONCE does not have be reflected because the response would use a key d= erived from that NONCE thus failing verification if it doesn't match.

=

Using packet numbers to count iterations would simplify operations, bu= t are not strictly necessary. I n this form the INITIAL packet must have = packet number that identifies the retry attempt number, starting at 0 an= d the retry response must reflect that packet number.

Late handshake responses to older iterations may be preferable to new = retry responses due to man-on-side races. This can be detected via trial = decryption of older NONCE derived keys, but it is simpler if the first se= rver handshake packet number reflects the clients INITIAL packet number.<= /p>

A NONCE could be generated randomly, or it could be using counter mode= encryption such that the INITIAL packet number is an IV encrypting a bas= e NONCE. Using counter mode avoids having to store several NONCE's in cas= e an old handshake is received.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b4262ee387_21a32b2523054f60295263-- From nobody Wed Jun 20 23:27:29 2018 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 05301131048 for ; Wed, 20 Jun 2018 23:27:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HXdiGpqpxvrh for ; Wed, 20 Jun 2018 23:27:25 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DDA41311EF for ; Wed, 20 Jun 2018 23:27:17 -0700 (PDT) Date: Wed, 20 Jun 2018 23:27:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529562436; bh=uymTNjkYYNH3AhCGo84Y7Q3rkuvCyc3mdgnf9qQetAE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zWMdjh0WpZ8hbKHWKo+dh6t51scfnnzgFO3ABczdC6kDPbKTEqDlrQXVPLuvitBaV EKdrBlN9MAUjpdmngXWRxuPOUQVSt9l62tznGN17SHONNCZDdv08dHLDouQNPV/Jvz KMnThcnftDiCgEhuuGFCm7ZxZynHyQCNWMEJENTM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b45444a13a_1ffe53f8afecf2f88363813"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 21 Jun 2018 06:27:28 -0000 ----==_mimepart_5b2b45444a13a_1ffe53f8afecf2f88363813 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > May I ask why you think that it is not a good idea to require every one of us to share some small amount of secret (e.g. encryption key) between the middleboxes and the servers than we would be running? If you are in a cloud hosted setup (like Azure or Digital Ocean) the servers are operated by customers while load balancers and DDoS mitigation devices might be operated by the cloud provider. Requiring shared secrets here is messy. Sometimes this is done with TLS termination today, but it is still messy - some moving towards auto-configuration via LetsEncrypt - which of course would be an option for QUIC as well - but there are many moving parts making automation difficult. -- 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/1451#issuecomment-398990515 ----==_mimepart_5b2b45444a13a_1ffe53f8afecf2f88363813 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

May I ask why you think that it is not a good idea to require every on= e of us to share some small amount of secret (e.g. encryption key) betwee= n the middleboxes and the servers than we would be running?

If you are in a cloud hosted setup (like Azure or Digital Ocean) the s= ervers are operated by customers while load balancers and DDoS mitigation= devices might be operated by the cloud provider. Requiring shared secret= s here is messy. Sometimes this is done with TLS termination today, but i= t is still messy - some moving towards auto-configuration via LetsEncrypt= - which of course would be an option for QUIC as well - but there are ma= ny moving parts making automation difficult.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b45444a13a_1ffe53f8afecf2f88363813-- From nobody Thu Jun 21 00:11:09 2018 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 A634B130E39 for ; Thu, 21 Jun 2018 00:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 VeoJBxVAu1Oy for ; Thu, 21 Jun 2018 00:11:06 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E1612F1AB for ; Thu, 21 Jun 2018 00:11:06 -0700 (PDT) Date: Thu, 21 Jun 2018 00:11:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529565065; bh=ccDzRQxgC1hepny8NaNxowXcHDlKNC9uzeZ1XO0HpdM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2AoYO1HljIzdhruHQ+vVIrY++DokGVtgUtKpx910AlrXgdGMa0srpXqi3HusI0FIC L01rxEnTPQPfFNUJBwkr2J6m164vUGde29q/yGv7njSdrbLZ+auuYGU7TJkETXT4Hc GjFqF5kyv6r5hnasN+RBXcdHOYPdj0BNSz1VdLUs= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b4f893398d_304d2af1ab8fcf6071578"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 21 Jun 2018 07:11:08 -0000 ----==_mimepart_5b2b4f893398d_304d2af1ab8fcf6071578 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > I think that statistically dropping every N'th retry packet, say every 4'th, would work well because in most cases the reset happen as expected, and when not, it happens on retransmission just as if a packet were lost. I might argue that statistically ignoring a packet goes against the goal of stateless reset; i.e. provide a signal that the connection has been reset *as early as possible, before timeout happens*. IMO, the method to fix the issue should be either remember the peer address (as has been suggested by @MikeBishop in https://github.com/quicwg/base-drafts/issues/1443#issuecomment-398842429) or to limit the size (as I have suggested in https://github.com/quicwg/base-drafts/issues/1443#issuecomment-398915066). -- 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/1443#issuecomment-398999726 ----==_mimepart_5b2b4f893398d_304d2af1ab8fcf6071578 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think that statistically dropping every N'th retry packet, say every= 4'th, would work well because in most cases the reset happen as expected= , and when not, it happens on retransmission just as if a packet were los= t.

I might argue that statistically ignoring a packet goes against the go= al of stateless reset; i.e. provide a signal that the connection has been= reset as early as possible, before timeout happens.

IMO, the method to fix the issue should be either remember the peer ad= dress (as has been suggested by @MikeB= ishop in #1443 (comment)) or to limit the size (as I have= suggested in #1443 (comment)).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b4f893398d_304d2af1ab8fcf6071578-- From nobody Thu Jun 21 00:14:32 2018 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 887EF130EB9 for ; Thu, 21 Jun 2018 00:14:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 R7KMJNXBEVPk for ; Thu, 21 Jun 2018 00:14:27 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D633D12F1AB for ; Thu, 21 Jun 2018 00:14:27 -0700 (PDT) Date: Thu, 21 Jun 2018 00:14:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529565265; bh=3y2Ko/0XdWCE3MwLKDqSTa3FHtvhk2gsW97LZ33vE6E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=slOxzKUzDquk4jStTN4ob5GtlHogn8JOqLc6AED529+5nt/fhil67peRd6FV3IhYc IYUvfU8BVi+vwZqYlMdN7ikv7Zgb+TlBkt/qvGIShcOCXNiCmspZrjZQPZltkOeEcW 4DChzZQw+/VQDeTmS9Us85fagfDeql1tO7cZgixk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b5051de94_58f12b07480b0f5c1429db"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 21 Jun 2018 07:14:30 -0000 ----==_mimepart_5b2b5051de94_58f12b07480b0f5c1429db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj: > If you are in a cloud hosted setup (like Azure or Digital Ocean) the servers are operated by customers while load balancers and DDoS mitigation devices might be operated by the cloud provider. Requiring shared secrets here is messy. Thank you for pointing out that. I must say that that is a compelling argument. It's the use case where a network operator wants to protect a server administered by a different person / entity. Though I am not sure about the security properties. -- 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/1451#issuecomment-399000486 ----==_mimepart_5b2b5051de94_58f12b07480b0f5c1429db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@mikkelfj:

If you are in a cloud hosted setup (like Azure or Digital Ocean) the s= ervers are operated by customers while load balancers and DDoS mitigation= devices might be operated by the cloud provider. Requiring shared secret= s here is messy.

Thank you for pointing out that. I must say that that is a compelling = argument. It's the use case where a network operator wants to protect a s= erver administered by a different person / entity.

Though I am not sure about the security properties.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2b5051de94_58f12b07480b0f5c1429db-- From nobody Thu Jun 21 00:41:41 2018 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 35CBD131056 for ; Thu, 21 Jun 2018 00:41:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rr3c1jw9a9YC for ; Thu, 21 Jun 2018 00:41:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FD58131054 for ; Thu, 21 Jun 2018 00:41:38 -0700 (PDT) Date: Thu, 21 Jun 2018 00:41:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529566897; bh=HZcKWUBIva9uU7p8MS6fSmLTvf0l/IDZkzFtqmZ7Fh0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DGjDtGyvY0z3BUTezXPjCB+LcMcT6bjeBDDHmHtmfLChDQzJWTLjzfWe/EtaHLQsS D39qx2nF72Tv7wlIHmzSwCWkiDpZhQB3KLlDDaZmhpqKw8pePeeh6/7aBjT6jEPwWK eUKX4FlLQr29hEOYwFiuc6nM74XKvWsIjAg2mCdY= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b56b13af83_47823fc11d4faf883949e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 21 Jun 2018 07:41:40 -0000 ----==_mimepart_5b2b56b13af83_47823fc11d4faf883949e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 2 commits. be91e8f Moved the ECN block in the ACK prior to the ACK blocks themselves. Removed unneeded sentence. f8d3d5c Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/73bf8cb46b529bd799a4cf7df370b54aab5b29b8..f8d3d5c6040ad0da6595cf07019d5c4f755aa0f3 ----==_mimepart_5b2b56b13af83_47823fc11d4faf883949e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 2 commits.

  • be91e8f Moved the ECN block in the ACK prior to the ACK blocks themselves. Removed unneeded sentence.
  • f8d3d5c Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2b56b13af83_47823fc11d4faf883949e7-- From nobody Thu Jun 21 00:41:53 2018 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 849C8131056 for ; Thu, 21 Jun 2018 00:41:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1xXBgFs-B36p for ; Thu, 21 Jun 2018 00:41:47 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F67B131054 for ; Thu, 21 Jun 2018 00:41:47 -0700 (PDT) Date: Thu, 21 Jun 2018 00:41:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529566906; bh=Uz/UWIGvrugEkgnLXEWQSP0tVWVwweuFyMm9J2tWEF8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HiAkJBUiOUMyhmjEYuh/BzLP1pSueQMfI9Lv4OwKN7wPFez/f7ynsA0xvSW1UnXf8 Kl28wqzCNhLxBjFmzLGgwSbBk8WhyQI6+II/BNPRmt6afYlBb33ld3SO1V0xSozLRG mKzxyCyLEHy4ekaYGyAs/+orKH2h5Tl11BGN3i1o= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2b56ba8e3f5_2a453f7f6c7acf80247464"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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: Thu, 21 Jun 2018 07:41:51 -0000 ----==_mimepart_5b2b56ba8e3f5_2a453f7f6c7acf80247464 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > +appended at the end. + + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Largest Acknowledged (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Delay (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN Block ... Now implemented -- 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/1372#discussion_r197037592 ----==_mimepart_5b2b56ba8e3f5_2a453f7f6c7acf80247464 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> +appended at the end.
+
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                     Largest Acknowledged (i)                ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Delay (i)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                           ECN Block                         ...

Now implemented

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

----==_mimepart_5b2b56ba8e3f5_2a453f7f6c7acf80247464-- From nobody Thu Jun 21 06:13:19 2018 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 553CA1310BE for ; Thu, 21 Jun 2018 06:13:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 29z0xE3FDZvw for ; Thu, 21 Jun 2018 06:13:05 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49CB41310A7 for ; Thu, 21 Jun 2018 06:13:05 -0700 (PDT) Date: Thu, 21 Jun 2018 06:13:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529586784; bh=RJBkGpOFS06jD9+YrjqucJDC21RrB8bX0PPyu8YIoiE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DRuXvyNVN4Qa/nKfFqLGYvwYA+Xb7ZRoVl1TzdEkcyDJprFapJ3i6XmWqbLxrEkG1 Z6B1fFnZCJ2go6ZBbOYQKfU15m2FqbYY0nraAeYB95+G6GOoQkIaCcFuucX3W8xxmn fFrOjTtOeIvey2IR8jw4AaLGMyYslZGvx65qiKzg= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ba4604e990_2c12ada7410ef544546a0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Thu, 21 Jun 2018 13:13:17 -0000 ----==_mimepart_5b2ba4604e990_2c12ada7410ef544546a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The case that @mikkelfj points out is exactly the case we are trying to solve for Azure. Azure owns the DDoS mitigation devices and load balancers, while the 3rd party owns the QUIC server, which could be from any implementation. I agree we should look at the security properties and enumerate all the threats/attacks this design could expose. Then it's a matter of weighting the impact of those threats vs the cost/complexity if we decided to fix them. Personally, I haven't seen an attack that would really benefit a middle box any more than any other handshake disruption tactic. -- 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/1451#issuecomment-399098726 ----==_mimepart_5b2ba4604e990_2c12ada7410ef544546a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The case that @mikkelfj points out= is exactly the case we are trying to solve for Azure. Azure owns the DDo= S mitigation devices and load balancers, while the 3rd party owns the QUI= C server, which could be from any implementation.

I agree we should look at the security properties and enumerate all th= e threats/attacks this design could expose. Then it's a matter of weighti= ng the impact of those threats vs the cost/complexity if we decided to fi= x them. Personally, I haven't seen an attack that would really benefit a = middle box any more than any other handshake disruption tactic.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2ba4604e990_2c12ada7410ef544546a0-- From nobody Thu Jun 21 06:27:07 2018 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 55D1B130E3B for ; Thu, 21 Jun 2018 06:27:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 fcPw8er0PTvb for ; Thu, 21 Jun 2018 06:27:03 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6FEF130E2B for ; Thu, 21 Jun 2018 06:27:03 -0700 (PDT) Date: Thu, 21 Jun 2018 06:27:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529587622; bh=VyyF3Ini7ObxTIji9TkOpLY3CtUXChm/7QT+JLxcH9c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C+FudQY53SQDIiWSjZqCDvXP2bcRRJ6c1RmFg4itILIurGx5A+xHzlKMYi0V2Htdq FXfWvs9YrO4QB+K3SKmOE61iv3ZHCdesQYpNv1DmB5JhZFeCbR1MHdCaycX7FLSb8K I/eA84POnDSaA/1vhKp+6TbUthbQA/+2Wk4KUR3o= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2ba7a6c65f6_4d122af318020f54103173"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Thu, 21 Jun 2018 13:27:06 -0000 ----==_mimepart_5b2ba7a6c65f6_4d122af318020f54103173 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, Maybe we have some weird special case, and have handshake and SPA are both considered `0`? I understand and agree that all values should be valid, but I just really don't like the idea of a negative number if we don't absolutely need it. -- 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/1465#discussion_r197131356 ----==_mimepart_5b2ba7a6c65f6_4d122af318020f54103173 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

Maybe we have some weird special case, and have handshake and SPA are both considered 0? I understand and agree that all values should be valid, but I just really don't like the idea of a negative number if we don't absolutely need it.

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

----==_mimepart_5b2ba7a6c65f6_4d122af318020f54103173-- From nobody Thu Jun 21 06:39:55 2018 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 1876B130E3B for ; Thu, 21 Jun 2018 06:39:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7OSTLOan-skU for ; Thu, 21 Jun 2018 06:39:49 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 690EF13108B for ; Thu, 21 Jun 2018 06:39:49 -0700 (PDT) Date: Thu, 21 Jun 2018 06:39:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529588388; bh=MPzB//MTdWbGn9pPsoB8nUU3igqm9OzyOXakdpwYNds=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dOF8e7Csm4L9W20kZjPb9yK0PeZBDlt4UpXEKbPQ9fYc+bp77C2b1nGiohcsBUOQz XCxrp19Y6WbSfTNNJmvpP11x029N1tzSqC77qxsmVJBe1XgV25nTejQg4Cw/ba/ztx BeYQ4TZODyDOjsUrjrQngmcRUvzz9qhlKVwfR2MQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2baaa4c3b88_739f3fadcff62f7c168155"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 21 Jun 2018 13:39:54 -0000 ----==_mimepart_5b2baaa4c3b88_739f3fadcff62f7c168155 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that we need a NEED_MORE_CIDS frame. The issue I see with the approach proposed in #1465 is that it is hard to determine the number of spare CIDs is an endpoint expected to provide to the peer. I'd assume that 1 as the number of spare CIDs is too small, since if an endpoint tries to probe a path using the spare and fails, it would get out of CIDs. -- 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/1464#issuecomment-399106812 ----==_mimepart_5b2baaa4c3b88_739f3fadcff62f7c168155 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think that we need a NEED_MORE_CIDS frame.

The issue I see with the approach proposed in #1465 is that it is hard to determine= the number of spare CIDs is an endpoint expected to provide to the peer.= I'd assume that 1 as the number of spare CIDs is too small, since if an = endpoint tries to probe a path using the spare and fails, it would get ou= t of CIDs.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2baaa4c3b88_739f3fadcff62f7c168155-- From nobody Thu Jun 21 07:17:49 2018 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 4A199130E88 for ; Thu, 21 Jun 2018 07:17:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Uso9NhCG5tBh for ; Thu, 21 Jun 2018 07:17:45 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D7B1130E77 for ; Thu, 21 Jun 2018 07:17:45 -0700 (PDT) Date: Thu, 21 Jun 2018 07:17:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529590663; bh=ljJioyaiG9tLL+AIycUk9d2jw7m+12u9BxxTdY+UvGY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gwI2/aXi0X/EymKKWJv23+rO1bG7/JA2pLTE/Bu0tlVjTCYvIdc3kpP6A7TxahObQ tNrApPm4BbV/8eZQR3QAm1AWZWWt7FdxpPoKINyNm1Ec2zxKUWd2fpjgQkUco8wbrW Py8XS+ioozTD81BXsGlQhG/ITykasjFnmAo7aagY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2bb3876c530_6a672acb09b0af50434b4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Thu, 21 Jun 2018 14:17:47 -0000 ----==_mimepart_5b2bb3876c530_6a672acb09b0af50434b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. @huitema: I don't understand what you are asking here, because those are different data namespaces. So, for instance, SH will be sent with Handshake[Offset=0], and NST will be sent with Application[Offset=0]. They don't interact with each other. The case that is an error is when data comes in at a given encryption level after the TLS state machine has moved on. For instance, if the server sends Handshake: [Offset=X, SFIN], Handshake: [Offset=X + len(SFIN), ]. This isn't valid because the TLS handshake is now reading at Application. As Kazuho says, this should generate an error, and the text requires that: ``` - If the packet is from a previously installed encryption level, it MUST not contain data which extends past the end of previously received data in that flow. Implementations MUST treat any violations of this requirement as a connection error of type PROTOCOL_VIOLATION. ``` -- 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/1450#discussion_r197150080 ----==_mimepart_5b2bb3876c530_6a672acb09b0af50434b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

@huitema: I don't understand what you are asking here, because those are different data namespaces.

So, for instance, SH will be sent with Handshake[Offset=0], and NST will be sent with Application[Offset=0]. They don't interact with each other.

The case that is an error is when data comes in at a given encryption level after the TLS state machine has moved on. For instance, if the server sends Handshake: [Offset=X, SFIN], Handshake: [Offset=X + len(SFIN), ]. This isn't valid because the TLS handshake is now reading at Application. As Kazuho says, this should generate an error, and the text requires that:

- If the packet is from a previously installed encryption level, it
  MUST not contain data which extends past the end of previously
  received data in that flow. Implementations MUST treat any
  violations of this requirement as a connection error of type
  PROTOCOL_VIOLATION.

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

----==_mimepart_5b2bb3876c530_6a672acb09b0af50434b4-- From nobody Thu Jun 21 08:36:42 2018 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 1BC98130ED8 for ; Thu, 21 Jun 2018 08:36:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sxGVBC6yO8KV for ; Thu, 21 Jun 2018 08:36:38 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7813F130ECC for ; Thu, 21 Jun 2018 08:36:38 -0700 (PDT) Date: Thu, 21 Jun 2018 08:36:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529595397; bh=Z/6jBnfHkDmkQnO01hQtiQiITJJvVVMEYgsKYhuw0XE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PIZXwCwQ/4Qf85OGR8Wk9G887BzwhP0cwVAOtbGpckgxMD9bROTIFwrmh1DUdkDqq AmunmAlu8a0gWafPnnXHqW5z1y1g3QIv74UKFStvXACYzB+eu+cL6t7tonVl729oHs mnpSpJ0ufBZTUgl0atyBNPMEJv0PYF7xXC8CVxhY= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2bc605acbe3_7eac3ff9098a0f881817e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Thu, 21 Jun 2018 15:36:41 -0000 ----==_mimepart_5b2bc605acbe3_7eac3ff9098a0f881817e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable CID_BLOCKED! On Thu, Jun 21, 2018 at 6:39 AM, Kazuho Oku wrote: > I think that we need a NEED_MORE_CIDS frame. > > The issue I see with the approach proposed in #1465 > is that it is hard to= > determine the number of spare CIDs is an endpoint expected to provide t= o > the peer. I'd assume that 1 as the number of spare CIDs is too small, s= ince > if an endpoint tries to probe a path using the spare and fails, it woul= d > get out of CIDs. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = 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/1464#issuecomment-399147142= ----==_mimepart_5b2bc605acbe3_7eac3ff9098a0f881817e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable CID_BLOCKED!

On Thu, Jun 21, 2018 at 6:39 AM, Kazuho Oku <notifications@github.com&= gt;
wrote:

> I think that we need a NEED_MORE_CIDS frame.
>
> The issue I see with the approach proposed in #1465
> <https://github.com/quicwg/base-drafts/pull/1465> is that it i= s hard to
> determine the number of spare CIDs is an endpoint expected to provid= e to
> the peer. I'd assume that 1 as the number of spare CIDs is too s= mall, since
> if an endpoint tries to probe a path using the spare and fails, it w= ould
> get out of CIDs.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1464#issuecomment-3= 99106812>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1ocl_rWMJrW= ThFaMJCO6ZAEavXeWKks5t-6IhgaJpZM4UvxS5>
> .
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2bc605acbe3_7eac3ff9098a0f881817e5-- From nobody Thu Jun 21 09:22:59 2018 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 4283B130F08 for ; Thu, 21 Jun 2018 09:22:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 WwPxK8vLgpLb for ; Thu, 21 Jun 2018 09:22:56 -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 95BC7130DCB for ; Thu, 21 Jun 2018 09:22:56 -0700 (PDT) Date: Thu, 21 Jun 2018 09:22:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529598175; bh=CfMoiaiAJ/CeFSx7Lht5c5ru2yzoKgRNyDSbZOJvT10=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Y/+ysz8HrFoOrL86JtjNmcjFFDy70FSu6zSB0W3Ek2sBiWDtF54VIGSPxXqfbJm9W 2qleeiISj04TwJIj2DvwUj2P4Yaenk+RDSqHSWmNk7QZN2qK6EyoOyp+LBbM3lAeRN 4MaNWKbszZVeS8SpL3R4A8g5sbLGr5wuk6h223cM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2bd0df93620_20f02b1b3326af60736bb"; 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.26 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: Thu, 21 Jun 2018 16:22:58 -0000 ----==_mimepart_5b2bd0df93620_20f02b1b3326af60736bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit While I can't claim it's a committed product plan to do exactly this, Akamai has a DDoS mitigation product that I could envision working this way when facing QUIC traffic. I don't know what the token format would look like in this case. -- 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/1451#issuecomment-399162677 ----==_mimepart_5b2bd0df93620_20f02b1b3326af60736bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

While I can't claim it's a committed product plan to do exactly this, Akamai has a DDoS mitigation product that I could envision working this way when facing QUIC traffic. I don't know what the token format would look like in this case.

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

----==_mimepart_5b2bd0df93620_20f02b1b3326af60736bb-- From nobody Thu Jun 21 11:04:32 2018 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 E100E129C6B for ; Thu, 21 Jun 2018 11:04:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Oo28PyGkPAX5 for ; Thu, 21 Jun 2018 11:04:28 -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 4511E124C04 for ; Thu, 21 Jun 2018 11:04:28 -0700 (PDT) Date: Thu, 21 Jun 2018 11:04:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529604267; bh=1BYn5/KVgZF8GFFMg8DekY6XSbc4PxTkxs+ZV6y8ZvY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2DLakixT1jHvpqzfSzvIJhIcBPLDn7ZEvd7+BBKz+sbdbt8/zZlZE0GbyX3qgBy5z 7nOqXXeD4aD/XFxqqMMcynjN/OfTQIkq44RVF2mCciY0AV7APtB4BOQYWvNqIFwRkU iq3wTpgT9KeOga7IvKHElJe4NKSXGz3AGe+e4u/E= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2be8ab37bcb_5d8c3fb1d3e36f883361e9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 21 Jun 2018 18:04:31 -0000 ----==_mimepart_5b2be8ab37bcb_5d8c3fb1d3e36f883361e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ekr pushed 3 commits. d814642 Martin's comments da0d8ec Ensures that 89c45a6 Merge pull request #36 from ekr/ianswett-martin -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/954c585e680ca4bf8e2e18af57e5832b716d9fb7..89c45a658dc9cfe765d1252050f7874fe27bfd2f ----==_mimepart_5b2be8ab37bcb_5d8c3fb1d3e36f883361e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr pushed 3 commits.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2be8ab37bcb_5d8c3fb1d3e36f883361e9-- From nobody Thu Jun 21 12:51:10 2018 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 2BB4A130EC5 for ; Thu, 21 Jun 2018 12:51:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 J7N9x4BHowHo for ; Thu, 21 Jun 2018 12:51:05 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64790130DFA for ; Thu, 21 Jun 2018 12:51:05 -0700 (PDT) Date: Thu, 21 Jun 2018 12:51:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529610664; bh=dkXJwMTsGWx3FzsE/0P56Rmo7PvZLIMqp1VTAbUG85E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p1/KW5dxKL9yZVMQBj0vzjWvnL6tazSR3H4TwXKalDvZCxCSpeu+DF2ZLL0Uo0SI4 qdA5BNE3KNI3M/vOJRxZGA6fGPP7B0mxE1J8X0IPY2neeTscuaG5FlNbNADIT0CBMZ CJjtt6yjTyKlQcPConSE0CJCHLJF41OiWNeTKbis= From: Hristo Venev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK encoding requires two passes (#1138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c01a87907b_2d5a2aca09222f6053649"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: hvenev 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.26 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: Thu, 21 Jun 2018 19:51:10 -0000 ----==_mimepart_5b2c01a87907b_2d5a2aca09222f6053649 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Does it make sense for the base index to be greater than the largest reference? Won't then all post-base references be illegal? -- 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/1138#issuecomment-399222163 ----==_mimepart_5b2c01a87907b_2d5a2aca09222f6053649 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Does it make sense for the base index to be greater than the largest reference? Won't then all post-base references be illegal?

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

----==_mimepart_5b2c01a87907b_2d5a2aca09222f6053649-- From nobody Thu Jun 21 13:51:56 2018 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 9F9C2130DC2 for ; Thu, 21 Jun 2018 13:51:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 p4NXFboWEI9j for ; Thu, 21 Jun 2018 13:51:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD9271294D0 for ; Thu, 21 Jun 2018 13:51:50 -0700 (PDT) Date: Thu, 21 Jun 2018 13:51:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529614309; bh=VOc3j9lZBf4Xfw4pNj7psp/jS8la1Wyn5/jQwBe1D7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XJOWEBKn/tbjEwpI6fZh9Ts/HrFolxeyNgq2cwuwkql87QnJEkaMwffyblSp2Os2U hYMWiM2oKudtO8i5nxGSSc1fX19THUqmrhkUhfLE9+jcs1zuPF9iJgemfFXb7N0Mgo F52f2U+uLylPLT3KCpSSOgl7pBLHCYyB+VDXaAek= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK encoding requires two passes (#1138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c0fe5d21c8_ffa2b17033b0f5c6165a"; 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.26 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: Thu, 21 Jun 2018 20:51:53 -0000 ----==_mimepart_5b2c0fe5d21c8_ffa2b17033b0f5c6165a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, they would be illegal because they would by definition be referring to values greater than the Largest Reference. That doesn't mean it's nonsensical -- a single-pass encoder will pick a Base Index before it knows what references it will make; if it doesn't insert any entries, then it won't need to make post-base references. A two-pass encoder will probably make them always equal and never make post-base references. -- 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/1138#issuecomment-399239646 ----==_mimepart_5b2c0fe5d21c8_ffa2b17033b0f5c6165a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, they would be illegal because they would by definition be referri= ng to values greater than the Largest Reference. That doesn't mean it's = nonsensical -- a single-pass encoder will pick a Base Index before it kno= ws what references it will make; if it doesn't insert any entries, then i= t won't need to make post-base references.

A two-pass encoder will probably make them always equal and never make= post-base references.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2c0fe5d21c8_ffa2b17033b0f5c6165a-- From nobody Thu Jun 21 14:25:55 2018 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 9E64F130E21 for ; Thu, 21 Jun 2018 14:25:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 8fj2GgWeMVPQ for ; Thu, 21 Jun 2018 14:25:41 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3BF5131125 for ; Thu, 21 Jun 2018 14:25:41 -0700 (PDT) Date: Thu, 21 Jun 2018 14:25:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529616340; bh=ROyKcoNwnPWtFvgUqE3WiRTQoA2veRhZ7b7Ik24F9ZY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zNnOFCU93zbEjS1vws0XkKBiyT4/ga8bwRn40PMHGNxSfYP6Ez6dDjiwugdjuTLli o4LGkxsOJSGztyHSAlbV9aAT0wLh8FkJHWRmV+m+etwN9cZlfxJIRlDhY8YSbbJcKb pGFCy1KYBOWE8EpdJe5rQOGLkDAOVHVwz0jihwPo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c17d49385f_1c0c2ade4ce70f5415665a"; 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.26 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: Thu, 21 Jun 2018 21:25:52 -0000 ----==_mimepart_5b2c17d49385f_1c0c2ade4ce70f5415665a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Honestly, I'm inclined toward both/and. @mikkelfj, nothing says it needs to be dramatically smaller. SR currently has to be at least 37 octets long; with a requirement that it also be smaller than the triggering packet, it's guaranteed to die eventually. An implementation can choose the size of SR it sends back based on how concerned it is; if it usually selects a size that's 60-80% the size of the packet that triggered it, the ping-pong will die out after ~6 round trips. Select smaller, and it dies even more quickly. Couple that with permission (not a requirement) for an implementation to keep a little state to short-circuit these and I think it's sufficient. -- 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/1443#issuecomment-399248516 ----==_mimepart_5b2c17d49385f_1c0c2ade4ce70f5415665a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Honestly, I'm inclined toward both/and. @mikkelfj, nothing says it needs to be dramatically smaller. SR c= urrently has to be at least 37 octets long; with a requirement that it al= so be smaller than the triggering packet, it's guaranteed to die eventual= ly.

An implementation can choose the size of SR it sends back based on how= concerned it is; if it usually selects a size that's 60-80% the size of = the packet that triggered it, the ping-pong will die out after ~6 round t= rips. Select smaller, and it dies even more quickly. Couple that with p= ermission (not a requirement) for an implementation to keep a little stat= e to short-circuit these and I think it's sufficient.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2c17d49385f_1c0c2ade4ce70f5415665a-- From nobody Thu Jun 21 16:30:05 2018 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 7ECBF128BAC for ; Thu, 21 Jun 2018 16:30:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 NQKHWfK40vTY for ; Thu, 21 Jun 2018 16:30:01 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 E201F12785F for ; Thu, 21 Jun 2018 16:30:00 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529623800; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=mU0JKx74ot/SepLwbxNjzK9cw3tu+rSGaQQb+VBeziQ=; b=VAG0EnaOtE+LS6bvAXpm/igvPlo6Ex4YdB6CQd2OSmPxrcDK4r50t6l4xG1Aer9TMKEH2xEp 8lJMKcT65F9O97HPSAoAt2q2OzwWPMbROEX/m4FgwFBwzC61UBNPUV0jaQF+fS491tq6miNK Qi2q2lS4v46OGXCYo3bDj8LEnvw= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b2c34f7.7fd84379d4b0-smtp-out-n02; Thu, 21 Jun 2018 23:29:59 -0000 (UTC) Date: Thu, 21 Jun 2018 16:29:58 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2c34f64143a_3f9e2abddfe3fc0c289f8@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b96fc4: Define the contents of QPACK Encoder and Decoder s... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2c34f640ab0_3f9e2abddfe3fc0c288cc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 21 Jun 2018 23:30:03 -0000 ----==_mimepart_5b2c34f640ab0_3f9e2abddfe3fc0c288cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/encoder-framing Home: https://github.com/quicwg/base-drafts Commit: b96fc4aa9443530d1635738b05e261ac6ab9ffd6 https://github.com/quicwg/base-drafts/commit/b96fc4aa9443530d1635738b05e261ac6ab9ffd6 Author: Alan Frindell Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Define the contents of QPACK Encoder and Decoder streams This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2c34f640ab0_3f9e2abddfe3fc0c288cc-- From nobody Thu Jun 21 16:31:06 2018 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 A3DA1127AC2 for ; Thu, 21 Jun 2018 16:31:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 j5bNFPGJbojJ for ; Thu, 21 Jun 2018 16:31:03 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 1128512785F for ; Thu, 21 Jun 2018 16:31:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529623862; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=UJSiCVVrlxd12ZoexGjd5Ncn9SPxMXK5tYESM5RS69o=; b=Kh9dV2j3wSviFnxu28n4g3l7cLSFGIIkAsUk+/9Kuq6fCvILO1tGS78S/6D8TYgT2TJ9tt1n KMjyjF7f6W3TmUvOiaNAGrFXTII0Djy6OvPXFCs/KNOGhhqIQz/xC8qUKRYgkRPzcr7bRd3s K9D+Ur+uRH50PefPhqG2+ZnUEwo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b2c3536.7f87d46cb6c0-smtp-out-n03; Thu, 21 Jun 2018 23:31:02 -0000 (UTC) Date: Thu, 21 Jun 2018 16:31:01 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2c3535d4510_31a02afd68cdbc08216ed@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 4475cc: Define the contents of QPACK Encoder and Decoder s... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2c3535d4052_31a02afd68cdbc08215a3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 21 Jun 2018 23:31:05 -0000 ----==_mimepart_5b2c3535d4052_31a02afd68cdbc08215a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/encoder-framing Home: https://github.com/quicwg/base-drafts Commit: 4475cc42abbc4bcf8df14e37959d61f5a3331edc https://github.com/quicwg/base-drafts/commit/4475cc42abbc4bcf8df14e37959d61f5a3331edc Author: Alan Frindell Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Define the contents of QPACK Encoder and Decoder streams Fixes #1361 This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2c3535d4052_31a02afd68cdbc08215a3-- From nobody Thu Jun 21 16:37:20 2018 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 2E51C130DC7 for ; Thu, 21 Jun 2018 16:37:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 KwNGisJy3xgR for ; Thu, 21 Jun 2018 16:37:06 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9FAC130DC6 for ; Thu, 21 Jun 2018 16:37:05 -0700 (PDT) Date: Thu, 21 Jun 2018 16:37:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529624224; bh=pbZWjwvPMoB+O5Gh2G5QxaXYP7Kg8OKCVkC6K/G9ynA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=pCznbNfkjMiUc3IvWfjZuCUZu2mZg+B7sSZKyS4ctAvLe42OZnKBbqylTa5+hkOPZ 5U/7tPR1odiUbvLhE180vXPuB8NxNlr5lNGx+yjgYpTggQof+nOo+8tO1trdvJjoWM uyB48o4SBudIJfWMCVliH0hy2p6dn8x2DbCep3fw= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Define the contents of QPACK Encoder and Decoder streams (#1467) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c36a0dff3d_5d4e2ae1277e2f60106429"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Thu, 21 Jun 2018 23:37:18 -0000 ----==_mimepart_5b2c36a0dff3d_5d4e2ae1277e2f60106429 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1361 This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1467 -- Commit Summary -- * Define the contents of QPACK Encoder and Decoder streams -- File Changes -- M draft-ietf-quic-qpack.md (18) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1467.patch https://github.com/quicwg/base-drafts/pull/1467.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/1467 ----==_mimepart_5b2c36a0dff3d_5d4e2ae1277e2f60106429 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1361

This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions.

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

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

Commit Summary

  • Define the contents of QPACK Encoder and Decoder streams

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 mute the thread.

----==_mimepart_5b2c36a0dff3d_5d4e2ae1277e2f60106429-- From nobody Thu Jun 21 17:43:45 2018 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 EE30E12F1A5 for ; Thu, 21 Jun 2018 17:43:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 k1fnhyr98Ok3 for ; Thu, 21 Jun 2018 17:43:40 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007061294D0 for ; Thu, 21 Jun 2018 17:43:39 -0700 (PDT) Date: Thu, 21 Jun 2018 17:43:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529628218; bh=xZeEVif9BS3NdonKl9heeIqDjPfY3DWZzcHG3tmbdhU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gV+hc5jyujcEA6QV2tLZnmJirkaFsy54/ojjWtnZOSotkiNCqP/HtUbpu6kZq429I K/KDAnBi3G+tbjZx9aMUNT888bVnapOcliv7UioYrr7UWYhwj9lfGph5oBmm8/S/KZ d5K2f+Asu/RKRF1g9M+sfwE4FZAv1877Yj7R1nUk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c463ad9ff7_9c43fc2502f8f804974e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 00:43:43 -0000 ----==_mimepart_5b2c463ad9ff7_9c43fc2502f8f804974e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Yeah, this is a little tricky. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection Perhaps ... on only one local address. An endpoint MUST use a connection ID with a higher sequence number if it changes to using a different local address or network interface. Once an endpoint has used a connection ID for packets sent from a given local address, they MUST NOT use a connection ID with a lower sequence number with that address. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, There can be very many connection IDs during the handshake with this new Retry packet, so it's all special casing here. Start at 2^16-N if you feel compelled to track things this way. > endpoint MUST NOT send additional packets until a NEW_CONNECTION_ID frame is -received. +received. However, an implementation need not stop sending packets due to a gap +in sequence numbers; it simply advances to the next currently-available +connection ID it has received. Connection IDs with earlier sequence numbers +which arrive later MAY be retained for use on other local addresses or +discarded. OMG wall of text :) When this happens, it's probably cause to create a new section. FWIW, I like the idea that once you use a connection ID on a given interface, you can't use a lower-numbered one. That could extend to responses. Once you see a connection ID on a given tuple, then you can't use a lower-numbered one. That leads to some simple rules: When you use a new interface/address you MUST use of a new connection ID. When you use a new connection ID, you MUST use one with a higher sequence number than you have ever used before. You MUST NOT use a connection ID with a lower sequence number than you have either sent or received on that path. Formulating the text around that is what we need. > @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame. An endpoint might need to send packets on multiple networks without receiving any response from its peer. To ensure that the endpoint is not linkable across each of these changes, a new connection ID is needed for each network. To -support this, multiple NEW_CONNECTION_ID messages are needed. +support this, multiple NEW_CONNECTION_ID messages are needed. Each +NEW_CONNECTION_ID is marked with a sequence number. Connection IDs MUST be used +on only one local address, and each local address MUST advance to a connection Or, create a new section on connection ID use along the lines I describe below and cite that instead. -- 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/1465#pullrequestreview-131035960 ----==_mimepart_5b2c463ad9ff7_9c43fc2502f8f804974e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Yeah, this is a little tricky.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection

Perhaps
... on only one local address. An endpoint MUST use a connection ID with a higher sequence number if it changes to using a different local address or network interface. Once an endpoint has used a connection ID for packets sent from a given local address, they MUST NOT use a connection ID with a lower sequence number with that address.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

There can be very many connection IDs during the handshake with this new Retry packet, so it's all special casing here. Start at 2^16-N if you feel compelled to track things this way.

In draft-ietf-quic-transport.md:

>  endpoint MUST NOT send additional packets until a NEW_CONNECTION_ID frame is
-received.
+received.  However, an implementation need not stop sending packets due to a gap
+in sequence numbers; it simply advances to the next currently-available
+connection ID it has received.  Connection IDs with earlier sequence numbers
+which arrive later MAY be retained for use on other local addresses or
+discarded.

OMG wall of text :)

When this happens, it's probably cause to create a new section.

FWIW, I like the idea that once you use a connection ID on a given interface, you can't use a lower-numbered one. That could extend to responses. Once you see a connection ID on a given tuple, then you can't use a lower-numbered one. That leads to some simple rules:

When you use a new interface/address you MUST use of a new connection ID.
When you use a new connection ID, you MUST use one with a higher sequence number than you have ever used before.
You MUST NOT use a connection ID with a lower sequence number than you have either sent or received on that path.

Formulating the text around that is what we need.

In draft-ietf-quic-transport.md:

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection

Or, create a new section on connection ID use along the lines I describe below and cite that instead.

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

----==_mimepart_5b2c463ad9ff7_9c43fc2502f8f804974e-- From nobody Thu Jun 21 17:46:03 2018 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 7D75412F1A6 for ; Thu, 21 Jun 2018 17:45:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HyidHPgMCrub for ; Thu, 21 Jun 2018 17:45:57 -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 3CF241294D0 for ; Thu, 21 Jun 2018 17:45:57 -0700 (PDT) Date: Thu, 21 Jun 2018 17:45:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529628356; bh=jrfHrwlucACJTHv5Bkqa6kYoLlmR9eE19u8XGuYw4RI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yxCp43OCs7CW9MNIkcA1j9pMtmnaDUkXE7ghLPi1KZ1WRn+paxfEhwUYGRRGlqFUu qFKHRzv4xTNVxFmhnq1RdiicFCU9d1li3eIT9aPJ/YuaPO5q0GQAFzdYRIrZBFb/AX A3PcDlUccd2h5xyJ/ijMl6eU/ulPcer1zqTZdBp8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Confusion about number of outstanding CIDs (#1464) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c46c45a005_114c3fba7e6aaf7c2068fe"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 00:46:00 -0000 ----==_mimepart_5b2c46c45a005_114c3fba7e6aaf7c2068fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Maybe the simplest way to deal with that is to require reciprocation. If you get a NEW_CONNECTION_ID with a sequence number of N, then you have to provide that many connection IDs. New issue inbound. -- 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/1464#issuecomment-399286416 ----==_mimepart_5b2c46c45a005_114c3fba7e6aaf7c2068fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Maybe the simplest way to deal with that is to require reciprocation. If you get a NEW_CONNECTION_ID with a sequence number of N, then you have to provide that many connection IDs. New issue inbound.

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

----==_mimepart_5b2c46c45a005_114c3fba7e6aaf7c2068fe-- From nobody Thu Jun 21 17:50:06 2018 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 F252A12F1A6 for ; Thu, 21 Jun 2018 17:50:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8Kc_Dw27BgOZ for ; Thu, 21 Jun 2018 17:50:00 -0700 (PDT) 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 567271294D0 for ; Thu, 21 Jun 2018 17:50:00 -0700 (PDT) Date: Thu, 21 Jun 2018 17:49:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529628599; bh=CBFoaDcbjqrjLlqrJ5pc9oH3XxwH8SQuD5E7WiJToWM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=FX8x7SkFISv19BNMzYIkni5xnchxuzKYne/0JLs5T+9CgXkph2zArbJ13t17bU7iv H2B5BmIyt+ciXktKsjwqjd0igKgj84oPG3mq/5RXDRg4LKdh/WDzPlVHjXl75AO+Qk qh6t2pIJLCXXW0WUUw5COZnvgr3EdOyFJ74qs05A= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c47b76ee6c_6a032ac5898d4f54834a7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 00:50:04 -0000 ----==_mimepart_5b2c47b76ee6c_6a032ac5898d4f54834a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In #1452, we realized that we need connection ID sequence numbers back, and it seems like the design in #1465 depends on symmetry: if you see connection ID X, then you have to use at least connection ID X (and not X-1). In that case, there will never be a case where an endpoint is going to want to provide significantly more connection IDs than its peer. If any of those are used, it won't be able to send anything in response. So that suggests a simple solution to exhaustion: if you receive NEW_CONNECTION_ID, you are required to provide NEW_CONNECTION_ID frames up to the sequence number you have received. Then, an endpoint that wants to maintain N spare connection IDs can simply issue NEW_CONNECTION_ID frames until it has made that many connection IDs available to its peer. It's peer is then obligated to provide the same number in return. -- 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/1468 ----==_mimepart_5b2c47b76ee6c_6a032ac5898d4f54834a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In #1452, we realized that we need connection ID sequence numbers back, and it seems like the design in #1465 depends on symmetry: if you see connection ID X, then you have to use at least connection ID X (and not X-1).

In that case, there will never be a case where an endpoint is going to want to provide significantly more connection IDs than its peer. If any of those are used, it won't be able to send anything in response. So that suggests a simple solution to exhaustion: if you receive NEW_CONNECTION_ID, you are required to provide NEW_CONNECTION_ID frames up to the sequence number you have received.

Then, an endpoint that wants to maintain N spare connection IDs can simply issue NEW_CONNECTION_ID frames until it has made that many connection IDs available to its peer. It's peer is then obligated to provide the same number in return.

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

----==_mimepart_5b2c47b76ee6c_6a032ac5898d4f54834a7-- From nobody Thu Jun 21 20:03:34 2018 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 BDAC4130DD2 for ; Thu, 21 Jun 2018 20:03:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6j0TXmlKYbuh for ; Thu, 21 Jun 2018 20:03:31 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EACF5130DD1 for ; Thu, 21 Jun 2018 20:03:30 -0700 (PDT) Date: Thu, 21 Jun 2018 20:03:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529636609; bh=rGeykfvNYU1myz+GxSjELjTIDzl7JJ4GDnrSm+0brI0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XD7ls8tUK7pZNqzpSZ6YfoaPWqMwl+Yjfcxkrtk6iXCKh52zsYnALwHgi1UxrqtDs yo3ZLVdiB5gju5BTDzbZ3eCFJaAcA9jDZZoWXC7ucaAokqilZL5bSo49cXOZpOab+D yqVO/+irfpvdV6oNML0VL/R36O1Hy2O573Xa8ra0= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c6701e4865_39802aded2056f50207646"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 22 Jun 2018 03:03:33 -0000 ----==_mimepart_5b2c6701e4865_39802aded2056f50207646 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Am I correct in assuming that we would have a sequence number in this proposed approach? I think that we need it, otherwise an eternal ping-pong might happen. Of course we can prevent eternal ping-pong from happening by having a `is_pong` flag. But I would assume that it would be more straightforward (and descriptive) to have a sequence number. -- 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/1468#issuecomment-399306505 ----==_mimepart_5b2c6701e4865_39802aded2056f50207646 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Am I correct in assuming that we would have a sequence number in this = proposed approach?

I think that we need it, otherwise an eternal ping-pong might happen. = Of course we can prevent eternal ping-pong from happening by having a is_pong flag. But I would assume that it would be more straight= forward (and descriptive) to have a sequence number.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2c6701e4865_39802aded2056f50207646-- From nobody Thu Jun 21 20:26:20 2018 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 72766130DDC for ; Thu, 21 Jun 2018 20:26:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 43ZmXpWv1ur9 for ; Thu, 21 Jun 2018 20:26:17 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24D9B128CF3 for ; Thu, 21 Jun 2018 20:26:17 -0700 (PDT) Date: Thu, 21 Jun 2018 20:26:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529637976; bh=TdTJArLHvIGfbxAwDLzhJvQFMF/wkQMHSJseC47S/O4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=itskmAWKS+BhP78UjYakNrqxg+8AdDWkPoFryoWNTigNSXTowR/qQSIo++TKcw0FU 9D2QfZByIB1bBgEbEI3kvW04bEk3Lb0AE+mB06/VS5G1R5aGb/+zW2ZpZgJ79RajJe pA2Sp5pqQ0kHnaUSrXz+ZXpBWachmNAJDg+rmeus= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c6c584bc1e_477b3fb0e239cf88584bd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 22 Jun 2018 03:26:19 -0000 ----==_mimepart_5b2c6c584bc1e_477b3fb0e239cf88584bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Answering my question by myself: by reading https://github.com/quicwg/base-drafts/issues/1464#issuecomment-399286416 I now understand that the solution proposed here works together with sequence numbers. -- 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/1468#issuecomment-399309663 ----==_mimepart_5b2c6c584bc1e_477b3fb0e239cf88584bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Answering my question by myself: by reading #1464 (comment) I now understand that the solution proposed here works together with sequence numbers.

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

----==_mimepart_5b2c6c584bc1e_477b3fb0e239cf88584bd-- From nobody Thu Jun 21 21:32:21 2018 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 E1EEA130DE3 for ; Thu, 21 Jun 2018 21:32:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 VlbhHrqU569j for ; Thu, 21 Jun 2018 21:32:16 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76268130DDE for ; Thu, 21 Jun 2018 21:32:16 -0700 (PDT) Date: Thu, 21 Jun 2018 21:32:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529641935; bh=S/5NXu5eX9S9DtV6rjgSGijtzXy5IqW6RnBHSqwTlD8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=urjZpdBRgfoKyOvjFdRzU8PhmBRk8Ojs7fru2KO387oneZICDTblqr1SWCLAlRpKM lNaB1zUF4dB4+FlMZU9VxoGtww8Iup+fe6NLoBlid0l0gOzYpClSfhJhyeNbJwyb81 oYkartOOW+aTplY8ioI+vugoN8F6k6nA5VB5iVk4= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2c7bcf9d0d3_553c2b1592e32f6046527"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 22 Jun 2018 04:32:19 -0000 ----==_mimepart_5b2c7bcf9d0d3_553c2b1592e32f6046527 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @nibanks @MikeBishop It's good to know that we have interest in such deployments. Thank you. > I agree we should look at the security properties and enumerate all the threats/attacks this design could expose. Then it's a matter of weighting the impact of those threats vs the cost/complexity if we decided to fix them. Personally, I haven't seen an attack that would really benefit a middle box any more than any other handshake disruption tactic. The issue about simply allowing the existence of an uncoordinated middlebox is that it becomes impossible for _any_ server to detect somebody on-path altering the handshake traffic. For example, a middlebox can alter the server CID by sending a Retry, and the server will not notice the alternation if the middlebox also drops the token field of the 2nd Initial packet sent from the client that traverses through the middlebox to the server. While I understand that you cannot care about the issue in the deployments that you are interested in, I think that others would be worried about the possible impact on security as well as the ossification concern including the one that I have described in https://github.com/quicwg/base-drafts/issues/1451#issuecomment-398982420. Fortunately, there are ways to define a signal for detecting tampering that _can_ be implemented by server operators who will not have uncoordinated DOS detection devices. One way is to add an "Original_DCID" field to Transport Parameters, and state that "a server SHOULD check that the value of the Original_DCID field matches that of the packet that it saw in the first packet that belonged to the connection". Servers running behind an uncoordinated middlebox will turn this check off. Note that having a configuration knob is mandatory for servers running behind such a middlebox, even if we do not introduce the "Original_DCID" field. This is because Retry is version-specific (which means that uncoordinated DOS mitigation devices might need to send a Version Negotiation packet). To support that, the servers need to have a knob that changes how the downgrade protection logic works (FWIW, end-to-end version downgrade protection is currently a MUST; we need to change it as well to allow the existence of uncoordinated DOS mitigation devices). -- 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/1451#issuecomment-399317602 ----==_mimepart_5b2c7bcf9d0d3_553c2b1592e32f6046527 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@nibanks @MikeBishop It's good to know that we have interest in suc= h deployments. Thank you.

I agree we should look at the security properties and enumerate all th= e threats/attacks this design could expose. Then it's a matter of weighti= ng the impact of those threats vs the cost/complexity if we decided to fi= x them. Personally, I haven't seen an attack that would really benefit a = middle box any more than any other handshake disruption tactic.

The issue about simply allowing the existence of an uncoordinated midd= lebox is that it becomes impossible for any server to detect som= ebody on-path altering the handshake traffic.

For example, a middlebox can alter the server CID by sending a Retry, = and the server will not notice the alternation if the middlebox also drop= s the token field of the 2nd Initial packet sent from the client that tra= verses through the middlebox to the server.

While I understand that you cannot care about the issue in the deploym= ents that you are interested in, I think that others would be worried abo= ut the possible impact on security as well as the ossification concern in= cluding the one that I have described in #1451 (comment).

=

Fortunately, there are ways to define a signal for detecting tampering= that can be implemented by server operators who will not have u= ncoordinated DOS detection devices.

One way is to add an "Original_DCID" field to Transport Parameters, an= d state that "a server SHOULD check that the value of the Original_DCID f= ield matches that of the packet that it saw in the first packet that belo= nged to the connection". Servers running behind an uncoordinated middlebo= x will turn this check off.

Note that having a configuration knob is mandatory for servers running= behind such a middlebox, even if we do not introduce the "Original_DCID"= field. This is because Retry is version-specific (which means that uncoo= rdinated DOS mitigation devices might need to send a Version Negotiation = packet). To support that, the servers need to have a knob that changes ho= w the downgrade protection logic works (FWIW, end-to-end version downgrad= e protection is currently a MUST; we need to change it as well to allow t= he existence of uncoordinated DOS mitigation devices).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2c7bcf9d0d3_553c2b1592e32f6046527-- From nobody Fri Jun 22 06:20:46 2018 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 F3EF5130E5E for ; Fri, 22 Jun 2018 06:20:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 5ztLkWuqUlof for ; Fri, 22 Jun 2018 06:20:42 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 7D87F130E52 for ; Fri, 22 Jun 2018 06:20:42 -0700 (PDT) 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=2zbspn0r1FWoEqu+1kZUKXWO+eo=; b=FRHfRFPwcWFytW7m qaml5HW+4mXaLLi76mYvtHtu/ES0jQrmRe1UKUKQ9WSXLzg/2CO9ORA0EPS0xfGZ XlIVIwrRYeS2SxaRfDlKuz92q9l7QSwmq4qc/sKNswo6vc3WttOPafTBzM4sMVbs ALlic9H49ZZ4Vsm813ArBQrTIV4= Received: by filter0290p1iad2.sendgrid.net with SMTP id filter0290p1iad2-8173-5B2CF7A9-D 2018-06-22 13:20:41.229586495 +0000 UTC Received: from github-lowworker17-cp1-prd.iad.github.net (unknown [192.30.252.44]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 0FzLveowS1OFwCDY14YeBQ for ; Fri, 22 Jun 2018 13:20:41.110 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker17-cp1-prd.iad.github.net (Postfix) with ESMTP id 196C0C0C89 for ; Fri, 22 Jun 2018 06:20:41 -0700 (PDT) Date: Fri, 22 Jun 2018 13:20:41 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2cf7a917ef9_17bc3fa6a6280f7822419f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1btXjHdxXPLDp7wMeGc631bBgjVIDo8o26Za ckm5pmICEXHsuC6AjgmkcMNklqEdYRrF5re0lt+pu6cj3Ovs2CcuGkQ5F9uwWUGx7AM5XFZaC/PUCa uJGy5qrjo35G8u5aekJD5Iqb/FKRKNp5PX3mIxqeTqZr29m2QUI5xfCRcA== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 13:20:44 -0000 ----==_mimepart_5b2cf7a917ef9_17bc3fa6a6280f7822419f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ekr pushed 4 commits. daea861 Address MT's comments on TLS 3aea50d MT/Bishop comments on transport bd5f9ff Ian's comments e2ed4db Merge pull request #37 from ekr/martins_comments -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/89c45a658dc9cfe765d1252050f7874fe27bfd2f..e2ed4db7df7d72a08fe13b8da8d17f6fca601c26 ----==_mimepart_5b2cf7a917ef9_17bc3fa6a6280f7822419f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr pushed 4 commits.

  • daea861 Address MT's comments on TLS
  • 3aea50d MT/Bishop comments on transport
  • bd5f9ff Ian's comments
  • e2ed4db Merge pull request #37 from ekr/martins_comments

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2cf7a917ef9_17bc3fa6a6280f7822419f-- From nobody Fri Jun 22 06:24:52 2018 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 86C51130E59 for ; Fri, 22 Jun 2018 06:24:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FKDMoaa4VzIZ for ; Fri, 22 Jun 2018 06:24:41 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C3C3130E58 for ; Fri, 22 Jun 2018 06:24:40 -0700 (PDT) Date: Fri, 22 Jun 2018 06:24:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529673879; bh=N2WLWuMJOzC7TWgSOq514e6cmT+bioUzvHsyXfLqFIE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XYV4R/ut2c7LlJUeAywDZv0ZWuuKBQAtpbZ44WfZ9DA8wCfNEjOyR8azFNwSbdRda 8boWLyuBQLaSwKpUFQRjUBj+ppzJovMfJyEc7x58cfy0s0ni3lXkygagZqpnoMOrpn PLWeFpfE5NnfdlNudpMiW3tESCWGgAVMhNoYRqAo= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2cf8979905f_24772aed49cc6f58898a8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Fri, 22 Jun 2018 13:24:51 -0000 ----==_mimepart_5b2cf8979905f_24772aed49cc6f58898a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. @martinthomson this addresses the comments on the PR. There are two points to call out: 1. There is some substantive back and forth about the model for how to describe the state of the TLS stack and the current encryption level it is reading from. I left some comments describing my view, but it might be easier to discuss live. I don't believe it actually affects bytes on the wire, except for a few points where I think you may have misunderstood, noted in my comments. I didn't change that text. 2. In a number of places, I opted not to update the Retry text because it seems we are still working through the details on the list. > @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones. Protocol differences between QUIC and TCP however contribute to algorithmic differences. We briefly describe these protocol differences below. +### Separate Packet Number Spaces + +QUIC uses separate packet number spaces for each encryption level, except that +0-RTT and all generations of 1-RTT keys use the same packet number space. +Separating the spaces allows the recovery mechanisms to work without special +cases to avoid spuriously retransmitting un-processable packets. Done > @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones. Protocol differences between QUIC and TCP however contribute to algorithmic differences. We briefly describe these protocol differences below. +### Separate Packet Number Spaces + +QUIC uses separate packet number spaces for each encryption level, except that +0-RTT and all generations of 1-RTT keys use the same packet number space. +Separating the spaces allows the recovery mechanisms to work without special +cases to avoid spuriously retransmitting un-processable packets. +Separate packet number spaces do not imply separate paths. Consequently, Done > @@ -107,7 +111,7 @@ important to the loss detection and congestion control machinery below. * Retransmittable packets are those that contain at least one retransmittable frame. -* Crypto handshake data is sent on stream 0, and uses the reliability +* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliability I am going to hold this for now. It's a simple sed script once we decide what this should say and CRYPTO_HS is easier to sed. I disagree with you about the alerts, so let's pick that up on-list. > -Handshake packets, which contain STREAM frames for stream 0, are critical to -QUIC transport and crypto negotiation, so a separate alarm is used for them. +Data in CRYPTO_HS frames is critical to QUIC transport and crypto negotiation, +so a more aggressive timeout is used to retransmit it. Below, the word +handshake packet is used to refer to packets containing CRYPTO_HS frames, +not packets with the specific long header packet type Handshake. Leaving as-is > +Unlike TLS over TCP, QUIC applications which want to send data do not +send it through TLS "application_data" records. Rather, they send it +as QUIC STREAM frames which are then carried in QUIC packets. + + +# Carrying TLS Messages {#carrying-tls} + +QUIC carries TLS handshake data in CRYPTO_HS frames, each of which Leaving as-is. > +and encrypted under the current TLS encryption level. +As with TLS over TCP, once TLS handshake data has +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: Rewritten a bit. > +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use +the same keys even if TLS has already updated to newer keys. + +One important difference between TLS 1.3 records (used with TCP) +and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear +in the same QUIC packet as long as they are associated with the +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. Nothing needed at this time. > +same encryption level. For instance, an implementation might +bundle a Handshake message and an ACK for some Handshake +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. Doing nothing. > +data into the same packet. + +In general, the rules for which data can appear in packets of which +encryption level are the same in QUIC as in TLS over TCP: + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet Done > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. Done. > +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. + +| Packet Type | Encryption Level | +|:----------------|:-----------------| +| Initial | Initial secrets | +| 0-RTT Protected | 0-RTT | +| Handshake | Handshake | +| Retry | N/A | +| Short Header | 1-RTT | +{: #packet-types-levels title="Encryption Levels by Packet Type"} Done. > +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. + +| Packet Type | Encryption Level | +|:----------------|:-----------------| +| Initial | Initial secrets | +| 0-RTT Protected | 0-RTT | +| Handshake | Handshake | +| Retry | N/A | +| Short Header | 1-RTT | +{: #packet-types-levels title="Encryption Levels by Packet Type"} + +{{QUIC-TRANSPORT}}; Section 6.3 shows how packets at the various encryption Done > ## Interface to TLS -As shown in {{schematic}}, the interface from QUIC to TLS consists of four -primary functions: Handshake, Source Address Validation, Key Ready Events, and -Secret Export. +As shown in {{schematic}}, the interface from QUIC to TLS consists of three +primary functions: + +- Sending and receiving handshake messages +- Rekeying (both in and out) Changed to "transmit and receive" > In order to drive the handshake, TLS depends on being able to send and receive -handshake messages on stream 0. There are two basic functions on this +handshake messages. There are two basic functions on this Done > -A QUIC server starts the process by providing TLS with stream 0 octets. - -Each time that an endpoint receives data on stream 0, it delivers the octets to -TLS if it is able. Each time that TLS is provided with new data, new handshake -octets are requested from TLS. TLS might not provide any octets if the -handshake messages it has received are incomplete or it has no data to send. - -At the server, when TLS provides handshake octets, it also needs to indicate -whether the octets contain a HelloRetryRequest. A HelloRetryRequest MUST always -be sent in a Retry packet, so the QUIC server needs to know whether the octets -are a HelloRetryRequest. +A QUIC server starts the process by providing TLS with the client's +handshake octets. + +At any given time, an endpoint will have a current sending encryption +level and receiving encryption level. Each encryption level is I don't think that I agree with this. Let's take send and receive separately. At any given time, the TLS stack is always sending with a given encryption level. That's just a fact of TLS, whether that's done by doing Rekey(); Send() or Send(Keys). In either case, the data is associated with that level when its sent to QUIC and QUIC needs to maintain that level upon transmission or retransmission. Receive is more complicated: At any given time, the TLS stack is only prepared to receive packets at a given level. This is also a fact of TLS [0]. As you say, when a packet comes in, it is tagged with an encryption level and there are three cases: - It's from a prior level, in which case it needs to be consistent with the existing data - It's from the current level, in which case you process it - It's from a future level, in which case you (probably) buffer it [I'm ignoring cases in which you packet that's impossibly from the future, like CFIN before you send SH. Now, you can do this sorting/buffering operation at the TLS layer (like I think picoTLS does) or at the QUIC layer (like Minq does), but I think it's still true that there's one active level [0] The only case in which this is confusing is 0-RTT rejection where the client is sending with Epoch 1 and the server is trying to receive with Epoch 0 or 2 (depending on how it was rejected). However, neither of these cases applies to QUIC, because you just don't enable the 0-RTT encryption level and so the packets are dropped prior to TLS. > + +At any given time, an endpoint will have a current sending encryption +level and receiving encryption level. Each encryption level is +associated with a different flow of bytes, which is reliably +transmitted to the peer in CRYPTO_HS frames. When TLS provides handshake +octets to be sent, they are appended to the current flow and +will eventually be transmitted under the then-current key. + +When an endpoint receives a QUIC packet containing a CRYPTO_HS frame from +the network, it proceeds as follows: + +- If the packet was in the current receiving encryption level, sequence + the data into the input flow as usual. As with STREAM frames, + the offset is used to find the proper location in the data sequence. + If the result of this process is that new data is available, then + it is delivered to TLS. Done > +will eventually be transmitted under the then-current key. + +When an endpoint receives a QUIC packet containing a CRYPTO_HS frame from +the network, it proceeds as follows: + +- If the packet was in the current receiving encryption level, sequence + the data into the input flow as usual. As with STREAM frames, + the offset is used to find the proper location in the data sequence. + If the result of this process is that new data is available, then + it is delivered to TLS. + +- If the packet is from a previously installed encryption level, it + MUST not contain data which extends past the end of previously + received data in that flow. Implementations MUST treat any + violations of this requirement as a connection error of type + PROTOCOL_VIOLATION. This doesn't seem right to me. First, the 0-RTT STREAM frame isn't relevant, because this is just about CRYPTO_HS. As for EOED, here's what happens ordinarily (no loss) - Recv CH; Rekey current RX to epoch 1 - Receive EOED: Rekey current RX to epoch 2 - Receive CFIN: Rekey current RX to epoch 3 If instead you get CH, CFIN, EOED, here's what happens: - Recv CH; Rekey current RX to epoch 1 - Receive CFIN: it's in the future, so buffer - Receive EOED: Rekey current RX to epoch 2 - Process CFIN; Rekey current RX to epoch 3 > Get Handshake - 1-RTT Keys Ready - <--- send/receive --- + <------------ Initial + Rekey rx to 0-RTT keys Leaving this pending the "current" discussion above. > -## QUIC Key Expansion {#key-expansion} +A server rejects 0-RTT by rejecting 0-RTT at the TLS layer. This results in +early exporter keys being unavailable, thereby preventing the use of 0-RTT for +QUIC. Done. > -QUIC uses a system of packet protection secrets, keys and IVs that are modelled -on the system used in TLS {{!TLS13}}. The secrets that QUIC uses -as the basis of its key schedule are obtained using TLS exporters (see Section -7.5 of {{!TLS13}}). +A client that attempts 0-RTT MUST also consider 0-RTT to be rejected if it +receives a Version Negotiation packet. Why? It seems like you could just start sending 0-RTT right then > -QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=RFC5869}} with -the same hash function negotiated by TLS for key derivation. For example, if -TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is used. +In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section +4.1.4) can be used to correct a client's incorrect KeyShare extension +as well as for a stateless round trip check. From the perspective of Done. > -QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=RFC5869}} with -the same hash function negotiated by TLS for key derivation. For example, if -TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is used. +In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section +4.1.4) can be used to correct a client's incorrect KeyShare extension +as well as for a stateless round trip check. From the perspective of +QUIC, this just looks like additional messages carried in the Initial +encryption level. Although it is in principle possible to use this +feature for address verification in QUIC, QUIC implementations SHOULD +instead use the Retry feature ({{QUIC-TRANSPORT}}; Section 4.4.2)). Done > -The HKDF-Expand function used by QHKDF-Expand uses the PRF hash function -negotiated by TLS, except for handshake secrets and keys derived from them (see -{{handshake-secrets}}). +If TLS experiences an error, it MUST generate an appropriate alert +as defined in {{TLS13}}; Section 6) and then provide it to QUIC, +which sends the alert in a CRYPTO_CLOSE frame. All such alerts are +"fatal". Added a reference to TLS 13. > -~~~ -struct { - uint16 length = Length; - opaque label<6..255> = "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the TLS +handshake, using the AEAD algorithm negotiated by TLS. Left. > - uint16 length = Length; - opaque label<6..255> = "QUIC " + Label; -} QhkdfExpandInfo; -~~~ +# QUIC Packet Protection {#packet-protection} + +As with TLS over TCP, QUIC encrypts packets with keys derived from the TLS +handshake, using the AEAD algorithm negotiated by TLS. + + +## QUIC Packet Encryption Keys {#encryption-keys} + +QUIC derives packet encryption keys in the same way as TLS 1.3: +Each encryption level/direction pair has a secret value, which +is then used to derive the traffic keys using as described +in {{TLS13}}; Section 7.3. replaced with comma. > -For example, assuming a hash function with a 32 octet output, derivation for a -client packet protection key would use HKDF-Expand with an `info` parameter of -0x00200851554943206b6579. +The keys for the Initial encryption level are computed based on +the client's first Destination Connection Id, as described in Done. > +The keys for the remaining encryption level are computed in the same +fashion as the corresponding TLS keys (see {{TLS13}}; Section 7), +except that the label for HKDF-Expand-Label uses the prefix "quic " +rather than "tls 13". The purpose of this change is to provide key Done > +The keys for the remaining encryption level are computed in the same +fashion as the corresponding TLS keys (see {{TLS13}}; Section 7), +except that the label for HKDF-Expand-Label uses the prefix "quic " +rather than "tls 13". The purpose of this change is to provide key +separation between TLS and QUIC, so that TLS stacks can avoid +exposing TLS record protection keys. My intention was that this be completely separate, actually. With that said, I think there are a number of options here. I have the action item to talk to the cryptographers. > -Packets that carry the TLS handshake (Initial, Retry, and Handshake) are -protected with a secret derived from the Destination Connection ID field from -the client's Initial packet. Specifically: +Initial packets are protected with +a secret derived from the Destination Connection ID field from the client's +Initial packet. Specifically: Rewritten a bit. The Retry thing is still in flux. > ~~~ The hash function for HKDF when deriving handshake secrets and keys is SHA-256 -{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with QHKDF-Expand -is the connection ID chosen by the client. +{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}. The connection ID used with +HKDF-Expand-Label is the connection ID chosen by the client. changed. > @@ -743,121 +653,11 @@ Note: : The Destination Connection ID is of arbitrary length, and it could be zero length if the server sends a Retry packet with a zero-length Source Connection - ID field. In this case, the handshake keys provide no assurance to the client + ID field. In this case, the initial keys provide no assurance to the client Done. > @@ -873,26 +673,20 @@ from the packet number. All QUIC packets other than Version Negotiation and Stateless Reset packets are protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shared secret, packets are protected with AEAD_AES_128_GCM and a key derived from the -client's connection ID (see {{handshake-secrets}}). This provides protection +client's connection ID (see {{initial-secrets}}). This provides protection Done. > against off-path attackers and robustness against QUIC version unaware middleboxes, but not against on-path attackers. All ciphersuites currently defined for TLS 1.3 - and therefore QUIC - have a 16-byte authentication tag and produce an output 16 bytes larger than their input. -Once TLS has provided a key, the contents of regular QUIC packets immediately -after any TLS messages have been sent are protected by the AEAD selected by TLS. - -The key, K, is either the client packet protection key (client_pp_key\) or -the server packet protection key (server_pp_key\), derived as defined in -{{key-expansion}}. - -The nonce, N, is formed by combining the packet protection IV (either -client_pp_iv\ or server_pp_iv\) with the packet number. The 64 bits -of the reconstructed QUIC packet number in network byte order is left-padded -with zeros to the size of the IV. The exclusive OR of the padded packet number -and the IV forms the AEAD nonce. +The key and iv for the packet are computed as described in {{encryption-keys}}. Done > -Once TLS has provided a key, the contents of regular QUIC packets immediately -after any TLS messages have been sent are protected by the AEAD selected by TLS. - -The key, K, is either the client packet protection key (client_pp_key\) or -the server packet protection key (server_pp_key\), derived as defined in -{{key-expansion}}. - -The nonce, N, is formed by combining the packet protection IV (either -client_pp_iv\ or server_pp_iv\) with the packet number. The 64 bits -of the reconstructed QUIC packet number in network byte order is left-padded -with zeros to the size of the IV. The exclusive OR of the padded packet number -and the IV forms the AEAD nonce. +The key and iv for the packet are computed as described in {{encryption-keys}}. +The nonce, N, is formed by combining the packet protection IV with the +packet number. The 64 bits of the reconstructed QUIC packet number in +network byte order is left-padded with zeros to the size of the IV. are > @@ -1024,144 +795,90 @@ encrypted_pn = ChaCha20(pn_key, counter, nonce, packet_number) ## Receiving Protected Packets -Once an endpoint successfully receives a packet with a given packet number, it -MUST discard all packets with higher packet numbers if they cannot be -successfully unprotected with either the same key, or - if there is a key update -- the next packet protection key (see {{key-update}}). Similarly, a packet that -appears to trigger a key update, but cannot be unprotected successfully MUST be -discarded. +Once an endpoint successfully receives a packet with a given packet +number, it MUST discard all packets in the same packet number space +with higher packet numbers if they cannot be successfully unprotected +with either the same key, or - if there is a key update - the next +packet protection key (see {{key-update}}). Similarly, a packet that +appears to trigger a key update, but cannot be unprotected +successfully MUST be discarded. I don't see what this has to do with EOED. Can you show me the packet flow you think has a problem here. > -A server might choose to retain 0-RTT packets that arrive before a TLS -ClientHello. The server can then use those packets once the ClientHello -arrives. However, the potential for denial of service from buffering 0-RTT -packets is significant. These packets cannot be authenticated and so might be -employed by an attacker to exhaust server resources. Limiting the number of -packets that are saved might be necessary. +A client MUST only use 0-RTT keys to protect data that is idempotent. A client +MAY wish to apply additional restrictions on what data it sends prior to the +completion of the TLS handshake. A client otherwise treats 0-RTT keys as +equivalent to 1-RTT keys, except that ACKs for that data MUST only be sent with +1-RTT keys. Done. > -### Retransmission and Acknowledgment of Unprotected Packets +: 0-RTT data can be acknowledged by the server as it receives it, but any It's a Note. > -Once 1-RTT keys are available to an endpoint, it no longer needs the TLS -handshake messages that are carried in unprotected packets. However, a server -might need to retransmit its TLS handshake messages in response to receiving an -unprotected packet that contains ACK frames. A server MUST process ACK frames -in unprotected packets until the TLS handshake is reported as complete, or it -receives an ACK frame in a protected packet that acknowledges all of its -handshake messages. +Receiving and verifying the TLS Finished message is critical in +ensuring the integrity of the TLS handshake. A server MUST NOT use +1-RTT protected packets from the client prior to verifying the client +Finished message if its response depends on client authentication. Removed. I think this is old text, though. > -## Key Update {#key-update} +Once the 1-RTT keys are established and the short header is in use, it +is possible to update the keys, for instance because of limits on AEAD +encryption. The KEY_PHASE bit in the short header is used to indicate I just removed it. > -server has chosen to use a pre-shared key - the pre-shared key binder (see -Section 4.2.8 of {{!TLS13}}). Verifying these values provides the server with -an assurance that the ClientHello has not been modified. - -A server could receive packets protected with 0-RTT keys prior to receiving a -TLS ClientHello. The server MAY retain these packets for later decryption in -anticipation of receiving a ClientHello. - -Receiving and verifying the TLS Finished message is critical in ensuring the -integrity of the TLS handshake. A server MUST NOT use protected packets from -the client prior to verifying the client Finished message if its response -depends on client authentication. +It is also possible for the attacker to tamper with data that +is carried in Handshake packets, but because that tampering +requires modifying TLS handshake messages, that tampering will be +detected as soon as the TLS handshake completes. Done. > @@ -1592,6 +996,11 @@ version of QUIC defined in {{QUIC-TRANSPORT}} is used. The quic_transport_parameters extension is carried in the ClientHello and the EncryptedExtensions messages during the handshake. +While the transport parameters are technically available prior to the +completion of the handshake, they cannot be fully trusted until the handshake +completes, and reliance on them should be minimized. +However, any tampering with the parameters will be detected +when the handshake completes. Done > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if Done > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; Done. > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; +Section 4.4.3). Finally, because ACKs of Handshake packets Done > @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a server can be used in packet reflection attacks to amplify the traffic generated by an attacker. -Certificate caching {{?RFC7924}} can reduce the size of the server's handshake -messages significantly. - -QUIC requires that the packet containing a ClientHello be padded to a minimum -size. A server is less likely to generate a packet reflection attack if the -data it sends is a small multiple of this size. A server SHOULD use a -HelloRetryRequest if the size of the handshake messages it sends is likely to -significantly exceed the size of the packet containing the ClientHello. +QUIC includes three defenses against this attack. First, the packet +containing a ClientHello be padded to a minimum size. Second, if +responding to an unverified source address, the server is forbidden to +send more than three packets in its first flight ({{QUIC-TRANSPORT}}; +Section 4.4.3). Finally, because ACKs of Handshake packets +are authenticated, a blind attacker cannot forge them Done > All these packets use the long header and contain the current QUIC version in the version field. -In order to prevent tampering by version-unaware middleboxes, handshake packets -are protected with a connection- and version-specific key, as described in -{{QUIC-TLS}}. This protection does not provide confidentiality or integrity -against on-path attackers, but provides some level of protection against -off-path attackers. +In order to prevent tampering by version-unaware middleboxes, Initial +packets are protected with a connection- and version-specific keys Done > ### Initial Packet {#packet-initial} The Initial packet uses long headers with a type value of 0x7F. It carries the -first cryptographic handshake message sent by the client. +first CRYPTO_HS frames sent by the client as well as the +cryptographic messages sent by the server to perform key exchange. The Initial Done > ### Initial Packet {#packet-initial} The Initial packet uses long headers with a type value of 0x7F. It carries the -first cryptographic handshake message sent by the client. +first CRYPTO_HS frames sent by the client as well as the +cryptographic messages sent by the server to perform key exchange. The Initial +packet is protected by Initial keys as described in {{QUIC-TLS}}. Done > -If the client received a Retry packet and is sending a second Initial packet, -then it sets the Destination Connection ID to the value from the Source -Connection ID in the Retry packet. Changing Destination Connection ID also -results in a change to the keys used to protect the Initial packet. +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... I mostly-centered this. Is that what you wanted. > -results in a change to the keys used to protect the Initial packet. +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +Token Length: + +: A variable-length integer specifying the length of the Token field, in bytes. +It may be zero if no token is present. The server MUST send a zero-length +token. Done. > +| Token Length (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +Token Length: + +: A variable-length integer specifying the length of the Token field, in bytes. +It may be zero if no token is present. The server MUST send a zero-length +token. + +Token: + +: An optional token blob previously received in either a Retry packet or +NEW_TOKEN frame. I would expect it only on the first one, but leaving the text as-is, as this whole design seems a bit in flux. > +Token Length: + +: A variable-length integer specifying the length of the Token field, in bytes. +It may be zero if no token is present. The server MUST send a zero-length +token. + +Token: + +: An optional token blob previously received in either a Retry packet or +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that contains +an initial cryptographic handshake message. This includes all cases where a new +packet containing the initial cryptographic message needs to be created, this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). Done. > +Token: + +: An optional token blob previously received in either a Retry packet or +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that contains +an initial cryptographic handshake message. This includes all cases where a new +packet containing the initial cryptographic message needs to be created, this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial. A +server may send multiple Initial packets. The cryptographic key exchange could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) Done. > +: An optional token blob previously received in either a Retry packet or +NEW_TOKEN frame. + +The client and server use the Initial packet type for any packet that contains +an initial cryptographic handshake message. This includes all cases where a new +packet containing the initial cryptographic message needs to be created, this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial. A +server may send multiple Initial packets. The cryptographic key exchange could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete Done > +The client and server use the Initial packet type for any packet that contains +an initial cryptographic handshake message. This includes all cases where a new +packet containing the initial cryptographic message needs to be created, this +includes the packets sent after receiving a Version Negotiation +({{packet-version}}) or Retry packet ({{packet-retry}}). + +A server sends its first Initial packet in response to a client Initial. A +server may send multiple Initial packets. The cryptographic key exchange could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete +first message MUST fit in a single packet (see {{handshake}}). Note that if +the server sends a HelloRetryRequest, the client will send a second Initial +packet with a CRYPTO_HS frame starting immediately after the first one. Did something here. > + +A server sends its first Initial packet in response to a client Initial. A +server may send multiple Initial packets. The cryptographic key exchange could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete +first message MUST fit in a single packet (see {{handshake}}). Note that if +the server sends a HelloRetryRequest, the client will send a second Initial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously received Done. > +server may send multiple Initial packets. The cryptographic key exchange could +require multiple round trips or retransmissions of this data. + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete +first message MUST fit in a single packet (see {{handshake}}). Note that if +the server sends a HelloRetryRequest, the client will send a second Initial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously received +a Retry packet from the server, it populates the Destination Connection ID field +with a randomly selected value. This MUST be at least 8 octets in length. Until OK, though I see a lot of "random" in this document. > + +The payload of an Initial packet conveys a CRYPTO_HS frame (or frames) +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete +first message MUST fit in a single packet (see {{handshake}}). Note that if +the server sends a HelloRetryRequest, the client will send a second Initial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously received +a Retry packet from the server, it populates the Destination Connection ID field +with a randomly selected value. This MUST be at least 8 octets in length. Until +a packet is received from the server, the client MUST use the same random value +unless it also changes the Source Connection ID (which effectively starts a new That's not actually correct, because you can use SCID="" > +containing a cryptographic handshake message. The first CRYPTO_HS frame +send always begins at an offset of 0 (see {{handshake}}). The client's complete +first message MUST fit in a single packet (see {{handshake}}). Note that if +the server sends a HelloRetryRequest, the client will send a second Initial +packet with a CRYPTO_HS frame starting immediately after the first one. + + +#### Connection IDs + +When an an Initial packet is sent by a client which has not previously received +a Retry packet from the server, it populates the Destination Connection ID field +with a randomly selected value. This MUST be at least 8 octets in length. Until +a packet is received from the server, the client MUST use the same random value +unless it also changes the Source Connection ID (which effectively starts a new +connection attempt). The randomized Destination Connection ID is used to +determine packet protection keys. Done. > The client populates the Source Connection ID field with a value of its choosing and sets the SCIL field to match. -The first Initial packet that is sent by a client contains a packet number of 0. -All subsequent packets contain a packet number that is incremented by at least -one, see ({{packet-numbers}}). - -The payload of an Initial packet conveys a STREAM frame (or frames) for stream -0 containing a cryptographic handshake message. The stream in this packet -always starts at an offset of 0 (see {{stateless-retry}}) and the complete -cryptographic handshake message MUST fit in a single packet (see {{handshake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet I think "a" is fine here. > The client populates the Source Connection ID field with a value of its choosing and sets the SCIL field to match. -The first Initial packet that is sent by a client contains a packet number of 0. -All subsequent packets contain a packet number that is incremented by at least -one, see ({{packet-numbers}}). - -The payload of an Initial packet conveys a STREAM frame (or frames) for stream -0 containing a cryptographic handshake message. The stream in this packet -always starts at an offset of 0 (see {{stateless-retry}}) and the complete -cryptographic handshake message MUST fit in a single packet (see {{handshake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection Leaving as-is because in flux. > - -The payload of an Initial packet conveys a STREAM frame (or frames) for stream -0 containing a cryptographic handshake message. The stream in this packet -always starts at an offset of 0 (see {{stateless-retry}}) and the complete -cryptographic handshake message MUST fit in a single packet (see {{handshake}}). +The Destination Connection ID field in the server's Initial packet +contains a connection ID that is chosen by the recipient of the packet +(i.e., the client); the Source Connection ID includes the connection +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection +IDs during the handshake. + +On first receiving an Initial or Retry packet from the server, the +client uses the Source Connection ID supplied by the server as the +Destination Connection ID for subsequent packets. The client MUST +discard any subsequent packets it receives with different Done. > +ID that the sender of the packet wishes to use (see +{{connection-id}}). The server MUST use consistent Source Connection +IDs during the handshake. + +On first receiving an Initial or Retry packet from the server, the +client uses the Source Connection ID supplied by the server as the +Destination Connection ID for subsequent packets. The client MUST +discard any subsequent packets it receives with different +Source Connection IDs. + +#### Tokens + +If the client has a suitable token available from a previous connection, +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an I'm going to leave it as-is for now. > + +#### Tokens + +If the client has a suitable token available from a previous connection, +it SHOULD populate the Token field. + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID to +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated Leaving b/c this design is in flux. > + +If the client received a Retry packet from the server and sends an +Initial packet in response, then it sets the Destination Connection ID to +the value from the Source Connection ID in the Retry packet. Changing +Destination Connection ID also results in a change to the keys used to +protect the Initial packet. It also sets the Token field to the +token provided in the Retry. + +When a server receives an Initial packet with an address validation +token, it SHOULD attempt to validate it. If the token is invalid then +the server SHOULD proceed as if the client did not have a validated +address, including potentially sending a Retry. If the validation +succeeds, the server SHOULD then allow the handshake to proceed (see +{{stateless-retry}}). + +Note: The rationale for treating the client as unvalidated rather Done. > +address, including potentially sending a Retry. If the validation +succeeds, the server SHOULD then allow the handshake to proceed (see +{{stateless-retry}}). + +Note: The rationale for treating the client as unvalidated rather +than discarding the packet is that the client might have received +the token in a previous connection using the NEW_TOKEN message, +and if the server has lost state, it might be unable to validate +the token at all, leading to connection failure if the packet +is discarded. + +#### Starting Packet Numbers + +The first Initial packet contains a packet number of 0. Each packet sent after +the Initial packet is associated with a packet number space and its packet +number increases monotonically in that space (see {{packet-numbers}}). Good question. Seems like an open issue. > ### Retry Packet {#packet-retry} -A Retry packet uses long headers with a type value of 0x7E. It carries -cryptographic handshake messages and acknowledgments. It is used by a server -that wishes to perform a stateless retry (see {{stateless-retry}}). +A Retry packet uses long headers with a type value of 0x7E. It carries an +address validation token created by the server. It is used by a server that +wishes to perform a stateless retry (see {{stateless-retry}}). + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| DCIL(8) | Original Destination Connection ID (*) | Done. > ### Retry Packet {#packet-retry} -A Retry packet uses long headers with a type value of 0x7E. It carries -cryptographic handshake messages and acknowledgments. It is used by a server -that wishes to perform a stateless retry (see {{stateless-retry}}). +A Retry packet uses long headers with a type value of 0x7E. It carries an +address validation token created by the server. It is used by a server that +wishes to perform a stateless retry (see {{stateless-retry}}). + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| DCIL(8) | Original Destination Connection ID (*) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Retry Token (*) Done. > -After receiving a Retry packet, the client uses a new -Initial packet containing the next cryptographic handshake message. The client -retains the state of its cryptographic handshake, but discards all transport -state. The Initial packet that is generated in response to a Retry packet -includes STREAM frames on stream 0 that start again at an offset of 0. +A server MUST only send a Retry in response to a client Initial packet. Leaving because in flux. > -Continuing the cryptographic handshake is necessary to ensure that an attacker -cannot force a downgrade of any cryptographic parameters. In addition to -continuing the cryptographic handshake, the client MUST remember the results of -any version negotiation that occurred (see {{version-negotiation}}). The client -MAY also retain any observed RTT or congestion state that it has accumulated for -the flow, but other transport state MUST be discarded. +If the Original Destination Connection ID field does not match the +Destination Connection ID from the Initial packet it sent, clients MUST +discard the packet. This prevents an off-path attacker from injecting +a Retry packet with a bogus new Source Connection ID. I prefer the current text. > -Continuing the cryptographic handshake is necessary to ensure that an attacker -cannot force a downgrade of any cryptographic parameters. In addition to -continuing the cryptographic handshake, the client MUST remember the results of -any version negotiation that occurred (see {{version-negotiation}}). The client -MAY also retain any observed RTT or congestion state that it has accumulated for -the flow, but other transport state MUST be discarded. +If the Original Destination Connection ID field does not match the +Destination Connection ID from the Initial packet it sent, clients MUST Done. > -The payload of the Retry packet contains at least two frames. It MUST include a -STREAM frame on stream 0 with offset 0 containing the server's cryptographic -stateless retry material. It MUST also include an ACK frame to acknowledge the -client's Initial packet. It MAY additionally include PADDING frames. The next -STREAM frame sent by the server will also start at stream offset 0. +Otherwise, the client SHOULD respond with a new Initial +packet with the Token field set to the token received in the Retry packet. I agree, but leaving because the design is in flux. > -If the server expects to generate more than three Handshake packets in response -to an Initial packet, it SHOULD include a PATH_CHALLENGE frame in each Handshake -packet that it sends. After receiving at least one valid PATH_RESPONSE frame, -the server can send its remaining Handshake packets. Servers can instead perform -address validation using a Retry packet; this requires less state on the server, -but could involve additional computational effort depending on implementation -choices. +Servers MUST NOT send more than three packets including Initial and Handshake Done. > @@ -694,7 +777,7 @@ Packets protected with 0-RTT keys use a type value of 0x7C. The connection ID fields for a 0-RTT packet MUST match the values used in the Initial packet ({{packet-initial}}). -The client can send 0-RTT packets after receiving a Handshake packet +The client can send 0-RTT packets after receiving an Initial or Handshake packet Done > @@ -761,7 +844,7 @@ During the handshake, an endpoint might receive multiple packets with the long header, and thus be given multiple opportunities to update the Destination Connection ID it sends. A client MUST only change the value it sends in the Destination Connection ID in response to the first packet of each type it -receives from the server (Retry or Handshake); a server MUST set its value based +receives from the server (Retry or Initial); a server MUST set its value based on the Initial packet. Any additional changes are not permitted; if subsequent Leaving, in flux. > @@ -792,15 +875,36 @@ response to connection migration ({{migration}}). NEW_CONNECTION_ID frames The packet number is an integer in the range 0 to 2^62-1. The value is used in determining the cryptographic nonce for packet encryption. Each endpoint -maintains a separate packet number for sending and receiving. The packet number -for sending MUST start at zero for the first packet sent and MUST increase by at -least one after sending a packet. +maintains a separate packet number for sending and receiving. + +Packet numbers are divided into 3 spaces in QUIC: + +- Initial space: All Initial packets {{packet-initial}} are in this space. +- Handshake space: All Handshake packets {{packet-handshake}} are in this space. +- Application data space: All 0-RTT and 1-RTT encrypted packets + {{packet-protected}} are in this space. + +As descibed in {{QUIC-TLS}}, each packet type uses different encryption keys. Done. > -least one after sending a packet. +maintains a separate packet number for sending and receiving. + +Packet numbers are divided into 3 spaces in QUIC: + +- Initial space: All Initial packets {{packet-initial}} are in this space. +- Handshake space: All Handshake packets {{packet-handshake}} are in this space. +- Application data space: All 0-RTT and 1-RTT encrypted packets + {{packet-protected}} are in this space. + +As descibed in {{QUIC-TLS}}, each packet type uses different encryption keys. + +Conceptually, a packet number space is the encryption context in which a packet +can be processed and ACKed. Initial packets can only be sent with +Initial encryption keys and ACKed in packets which are also Initial packets. +Similarly Handshake packets can only be sent and acked in Handshake packets. Done. > -A QUIC endpoint MUST NOT reuse a packet number within the same connection (that -is, under the same cryptographic keys). If the packet number for sending -reaches 2^62 - 1, the sender MUST close the connection without sending a -CONNECTION_CLOSE frame or any further packets; an endpoint MAY send a Stateless -Reset ({{stateless-reset}}) in response to further packets that it receives. +This enforces cryptographic separation between the data sent in the +different packet sequence number spaces. As a result, each packet number space Done. > cryptographic handshake protocol is in use. -QUIC provides this stream with reliable, ordered delivery of data. In return, -the cryptographic handshake provides QUIC with: +QUIC provides the cryptographic handshake with reliable, ordered +delivery of data via the CRYPTO_HS frame. In return, the Done. > @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with: client can receive packets that are addressed with the transport address that is claimed by the client (see {{address-validation}}) -The initial cryptographic handshake message MUST be sent in a single packet. -Any second attempt that is triggered by address validation MUST also be sent -within a single packet. This avoids having to reassemble a message from -multiple packets. Reassembling messages requires that a server maintain state -prior to establishing a connection, exposing the server to a denial of service -risk. +The CRYPTO_HS frame provides an offset and a length. QUIC functions +as the record encryption layer for the cryptographic protocol. Done, > @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with: client can receive packets that are addressed with the transport address that is claimed by the client (see {{address-validation}}) -The initial cryptographic handshake message MUST be sent in a single packet. -Any second attempt that is triggered by address validation MUST also be sent -within a single packet. This avoids having to reassemble a message from -multiple packets. Reassembling messages requires that a server maintain state -prior to establishing a connection, exposing the server to a denial of service -risk. +The CRYPTO_HS frame provides an offset and a length. QUIC functions +as the record encryption layer for the cryptographic protocol. + +The initial CRYPTO_HS frame MUST be sent in a single packet. Any +second attempt that is triggered by address validation MUST also be +sent within a single packet. This avoids having to reassemble a +message from multiple packets. I'm not following, so leaving. > The first client packet of the cryptographic handshake protocol MUST fit within a 1232 octet QUIC packet payload. This includes overheads that reduce the space available to the cryptographic handshake protocol. -Details of how TLS is integrated with QUIC is provided in more detail in -{{QUIC-TLS}}. +The CRYPTO_HS frame can be sent in different packet number spaces. +CRYPTO_HS frames in each packet number space carry a separate sequence +of handshake data starting from an offset of 0. I think I'm happier where it is, so I'm going to leave as-is and let you realize your vision when you want ti. > The first client packet of the cryptographic handshake protocol MUST fit within a 1232 octet QUIC packet payload. This includes overheads that reduce the space available to the cryptographic handshake protocol. -Details of how TLS is integrated with QUIC is provided in more detail in -{{QUIC-TLS}}. +The CRYPTO_HS frame can be sent in different packet number spaces. +CRYPTO_HS frames in each packet number space carry a separate sequence +of handshake data starting from an offset of 0. + +## Example Handshake Flows + +Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}}, +but we provide some examples here. Done > + +## Example Handshake Flows + +Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}}, +but we provide some examples here. + +{{tls-1rtt-handshake}} provides an overview of the 1-RTT handshake. +Each line shows a QUIC packet with the packet type and packet +number shown first, followed by the contents. So, for instance +the first packet is of type Initial, with packet number 0, and +contains a CRYPTO_HS frame carrying the ClientHello. + +Note that multiple QUIC packets -- even of different encryption levels +-- may be coalesced into a single UDP datagram (see +{{packet-coalesce}}, and so this handshake may consist of anywhere +from 4 to 9 UDP datagrams. For instance, the server's first flight Done. > +to increment from its 0-RTT packets. + +~~~~ +Client Server + +Initial[0]: CRYPTO_HS[CH] +0-RTT[0]: STREAM[0, "..."] -> + + Initial[0]: CRYPTO_HS[SH] ACK[0] + Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN] + <- 1-RTT[0]: STREAM[1, "..."] ACK[0] + +Initial[1]: ACK[0] +0-RTT[1]: CRYPTO_HS[EOED] +Handshake[0]: CRYPTO_HS[FIN], ACK[0] +1-RTT[2]: STREAM[0, "..."], ACK[0] -> Thanks. This was just a cut and paste error. > connection state MUST use the Retry packet ({{packet-retry}}). This packet -causes a client to reset its transport state and to continue the connection -attempt with new connection state while maintaining the state of the -cryptographic handshake. - -A server MUST NOT send multiple Retry packets in response to a client handshake -packet. Thus, any cryptographic handshake message that is sent MUST fit within -a single packet. - -In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +causes a client to restart the connection attempt and includes the token in the I don't know what you mean here. > @@ -1459,68 +1623,69 @@ To send additional data prior to completing the cryptographic handshake, the server then needs to validate that the client owns the address that it claims. Source address validation is therefore performed during the establishment of a -connection. TLS provides the tools that support the feature, but basic -validation is performed by the core transport protocol. +connection, by the core transport protocol. Done. > -port), a timestamp, and any other supplementary information the server will need -to validate the token in the future. - -The cryptographic handshake is responsible for enacting validation by sending -the address validation token to the client. A legitimate client will include a -copy of the token when it attempts to continue the handshake. The cryptographic -handshake extracts the token then asks QUIC a second time whether the token is -acceptable. In response, QUIC can either abort the connection or permit it to -proceed. +QUIC uses token-based address validation. Any time the server wishes +to validate a client address, it provides the client with a token. As +long as the token's authenticity can be checked (see +{{token-integrity}}) and the client is able to return that token, it +proves to the server that it received the token. + +If QUIC decides to request address validation for the current Did a slightly more aggressive rewrite. > +long as the token's authenticity can be checked (see +{{token-integrity}}) and the client is able to return that token, it +proves to the server that it received the token. + +If QUIC decides to request address validation for the current +handshake, it encodes the token in a Retry packet. The contents of +this token are consumed by the server that generates the token, so +there is no need for a single well-defined format. A token could +include information about the claimed client address (IP and port), a +timestamp, and any other supplementary information the server will +need to validate the token in the future. + +The Retry packet is sent to the client and a legitimate client will +respond with an Initial packet containing the token from the Retry packet +when it continues the handshake. In response to receiving the token, a +QUIC server can either abort the connection or permit it to proceed. Done. > A connection MAY be accepted without address validation - or with only limited validation - but a server SHOULD limit the data it sends toward an unvalidated address. Successful completion of the cryptographic handshake implicitly provides proof that the client has received packets from the server. +The client should allow for additional Retry packets being sent in +response to Initial packets sent containing a token. There are several +situations in which the server might not be able to use the previously +generated token to validate the client's address and must send a new +Retry. A reasonable limit to the number of tries the client allows +for, before giving up, is 3. That is, the client SHOULD echo the +address validation token from a new Retry packet up to 3 times. After +that, it MAY give up on the connection attempt. Done, but we need to work out the bigger design. > A server MAY provide clients with an address validation token during one connection that can be used on a subsequent connection. Address validation is especially important with 0-RTT because a server potentially sends a significant amount of data to a client in response to 0-RTT data. -A different type of token is needed when resuming. Unlike the token that is -created during a handshake, there might be some time between when the token is -created and when the token is subsequently used. Thus, a resumption token -SHOULD include an expiration time. It is also unlikely that the client port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client +with an address validation token that can be used to validate future 0-RTT +connections. The client may then use this token to validate future 0-RTT Done. > A server MAY provide clients with an address validation token during one connection that can be used on a subsequent connection. Address validation is especially important with 0-RTT because a server potentially sends a significant amount of data to a client in response to 0-RTT data. -A different type of token is needed when resuming. Unlike the token that is -created during a handshake, there might be some time between when the token is -created and when the token is subsequently used. Thus, a resumption token -SHOULD include an expiration time. It is also unlikely that the client port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client +with an address validation token that can be used to validate future 0-RTT +connections. The client may then use this token to validate future 0-RTT +connections by including it in the Initial packet's header. The client MUST +NOT use the token provided in a RETRY for future connections. Done. > A server MAY provide clients with an address validation token during one connection that can be used on a subsequent connection. Address validation is especially important with 0-RTT because a server potentially sends a significant amount of data to a client in response to 0-RTT data. -A different type of token is needed when resuming. Unlike the token that is -created during a handshake, there might be some time between when the token is -created and when the token is subsequently used. Thus, a resumption token -SHOULD include an expiration time. It is also unlikely that the client port -number is the same on two different connections; validating the port is +The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client +with an address validation token that can be used to validate future 0-RTT +connections. The client may then use this token to validate future 0-RTT +connections by including it in the Initial packet's header. The client MUST +NOT use the token provided in a RETRY for future connections. + +Unlike the token that is created for a Retry packet, there might be some time +between when the token is created and when the token is subsequently used. +Thus, a resumption token SHOULD include an expiration time. The server may MAY > @@ -2676,6 +2832,12 @@ QUIC acknowledgements are irrevocable. Once acknowledged, a packet remains acknowledged, even if it does not appear in a future ACK frame. This is unlike TCP SACKs ({{?RFC2018}}). +It is expected that a sender will reuse the same packet number across different +packet number spaces. ACK frames only acknowledge the packet numbers that were +transmitted by the sender in the same packet number space of the packet that the +ACK was received in. This is an important property to allow for separation +between the different packet number spaces. Done, > @@ -2839,6 +3001,9 @@ is only sending ACK frames will only receive acknowledgements for its packets if the sender includes them in packets with non-ACK frames. A sender SHOULD bundle ACK frames with other frames when possible. +Implementations must be aware of the packet number space of the packet being +transmitted and only acknowledge packets from that space. Done. > @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past. ### ACK Frames and Packet Protection -ACK frames that acknowledge protected packets MUST be carried in a packet that -has an equivalent or greater level of packet protection. - -Packets that are protected with 1-RTT keys MUST be acknowledged in packets that -are also protected with 1-RTT keys. - -A packet that is not protected and claims to acknowledge a packet number that -was sent with packet protection is not valid. An unprotected packet that -carries acknowledgments for protected packets MUST be discarded in its entirety. +ACK frames MUST only be carried in a packet that has the same packet It actually is an interoperability requirement, because if you inadvertantly cross-ACK, you will have failures. > -messages in the next unprotected packet that it sends, unless it is able to -acknowledge those packets in later packets protected by 1-RTT keys. At the -completion of the cryptographic handshake, both peers send unprotected packets -containing cryptographic handshake messages followed by packets protected by -1-RTT keys. An endpoint SHOULD acknowledge the unprotected packets that complete -the cryptographic handshake in a protected packet, because its peer is -guaranteed to have access to 1-RTT packet protection keys. - -For instance, a server acknowledges a TLS ClientHello in the packet that carries -the TLS ServerHello; similarly, a client can acknowledge a TLS HelloRetryRequest -in the packet containing a second TLS ClientHello. The complete set of server -handshake messages (TLS ServerHello through to Finished) might be acknowledged -by a client in protected packets, because it is certain that the server is able -to decipher the packet. - +Implementations SHOULD aggressively ACK packets containing CRYPTO_HS frames. Done. > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to Done. > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to +send in a the header of an Initial packet for a future 0-RTT connection. Done. > @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate a connection error of type UNSOLICITED_PATH_RESPONSE. +## NEW_TOKEN frame {#frame-new-token} + +An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to +send in a the header of an Initial packet for a future 0-RTT connection. + +The NEW_TOKEN frame is as follows: + +~~~ + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Token Length (i) ... Done. > + +Offset: + +: A variable-length integer specifying the byte offset in the stream for the + data in this CRYPTO_HS frame. + +Length: + +: A variable-length integer specifying the length of the Crypto Data field in + this CRYPTO_HS frame. + +Crypto Data: + +: The cryptographic message data. + +There is a separate flow of cryptographic handshake data in each Added above. > +: A variable-length integer specifying the length of the Crypto Data field in + this CRYPTO_HS frame. + +Crypto Data: + +: The cryptographic message data. + +There is a separate flow of cryptographic handshake data in each +encryption level, each of which starts at an offset of 0. This implies +that each encryption level is treated as a separate CRYPTO_HS stream +of data. + +Unlike STREAM frames, which include a Stream ID indicating to which +stream the data belongs, the CRYPTO_HS frame carries data for a single +stream per encryption level. The stream does not have an explicit +end, so CRYPTO_HS frames do not have a FIN bit. Hence the text above that forbids stuff extending past the end. > +that each encryption level is treated as a separate CRYPTO_HS stream +of data. + +Unlike STREAM frames, which include a Stream ID indicating to which +stream the data belongs, the CRYPTO_HS frame carries data for a single +stream per encryption level. The stream does not have an explicit +end, so CRYPTO_HS frames do not have a FIN bit. + + +## CRYPTO_CLOSE Frame {#frame-crypto-close} + +The CRYPTO_CLOSE frame (type=0x20) is used to indicate connection failures +caused by the crypto handshake. It uses the same format as the +CONNECTION_CLOSE frame ({{frame-connection-close}}), except that the +error codes are specific to the crypto protocol in use. For TLS 1.3, +the error code is simply the one-byte TLS alert number. Sent as left-padded for now. I know MT wants to argue about this whole structure. > @@ -3064,6 +3293,10 @@ been lost. In general, information is sent again when a packet containing that information is determined to be lost and sending ceases when a packet containing that information is acknowledged. +* Data sent in CRYPTO_HS frames are retransmitted according to the rules in + {{QUIC-RECOVERY}}, until either all data has been ACKed or the crypto state Done. > @@ -3299,8 +3532,7 @@ The two type bits from a Stream ID therefore identify streams as summarized in | 0x3 | Server-Initiated, Unidirectional | {: #stream-id-types title="Stream ID Types"} -Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is used for -the cryptographic handshake. Stream 0 MUST NOT be used for application data. +The first bi-directional stream opened by the client is stream 0. Left as-is. > @@ -3893,6 +4102,14 @@ errors is not mandatory, but only because requiring that an endpoint generate these errors also means that the endpoint needs to maintain the final offset state for closed streams, which could mean a significant state commitment. +## Flow control of CRYPTO_HS data {#flow-control-crypto} + +Data sent in CRYPTO_HS frames is not flow controlled in the same way as STREAM +frames. QUIC relies on the cryptographic protocol implementation to avoid +excessive buffering of data, see {{QUIC-TLS}}. The implementation SHOULD +provide an interface to QUIC to tell it about its buffering limits so that there +is no excessive buffering at multiple layers. Done. > @@ -4313,6 +4531,15 @@ the range from 0xFE00 to 0xFFFF. Issue and pull request numbers are listed with a leading octothorp. +## Since draft-ietf-quic-transport-12 + +- Enable server to transition connections to a preferred address (#560,#1251). +- No more stream 0. Done, -- 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/1450#pullrequestreview-130932728 ----==_mimepart_5b2cf8979905f_24772aed49cc6f58898a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

@martinthomson this addresses the comments on the PR. There are two points to call out:

  1. There is some substantive back and forth about the model for how to describe the state of the TLS stack and the current encryption level it is reading from. I left some comments describing my view, but it might be easier to discuss live. I don't believe it actually affects bytes on the wire, except for a few points where I think you may have misunderstood, noted in my comments.
    I didn't change that text.

  2. In a number of places, I opted not to update the Retry text because it seems we are still working through the details on the list.

In draft-ietf-quic-recovery.md:

> @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones. Protocol differences between
 QUIC and TCP however contribute to algorithmic differences. We briefly describe
 these protocol differences below.
 
+### Separate Packet Number Spaces
+
+QUIC uses separate packet number spaces for each encryption level, except that
+0-RTT and all generations of 1-RTT keys use the same packet number space.
+Separating the spaces allows the recovery mechanisms to work without special
+cases to avoid spuriously retransmitting un-processable packets.

Done

In draft-ietf-quic-recovery.md:

> @@ -120,6 +124,17 @@ algorithms here that parallel well-known TCP ones. Protocol differences between
 QUIC and TCP however contribute to algorithmic differences. We briefly describe
 these protocol differences below.
 
+### Separate Packet Number Spaces
+
+QUIC uses separate packet number spaces for each encryption level, except that
+0-RTT and all generations of 1-RTT keys use the same packet number space.
+Separating the spaces allows the recovery mechanisms to work without special
+cases to avoid spuriously retransmitting un-processable packets.
+Separate packet number spaces do not imply separate paths. Consequently,

Done

In draft-ietf-quic-recovery.md:

> @@ -107,7 +111,7 @@ important to the loss detection and congestion control machinery below.
 * Retransmittable packets are those that contain at least one
   retransmittable frame.
 
-* Crypto handshake data is sent on stream 0, and uses the reliability
+* Crypto handshake data is sent in CRYPTO_HS frames, and uses the reliability

I am going to hold this for now. It's a simple sed script once we decide what this should say and CRYPTO_HS is easier to sed.

I disagree with you about the alerts, so let's pick that up on-list.

In draft-ietf-quic-recovery.md:

>  
-Handshake packets, which contain STREAM frames for stream 0, are critical to
-QUIC transport and crypto negotiation, so a separate alarm is used for them.
+Data in CRYPTO_HS frames is critical to QUIC transport and crypto negotiation,
+so a more aggressive timeout is used to retransmit it.  Below, the word
+handshake packet is used to refer to packets containing CRYPTO_HS frames,
+not packets with the specific long header packet type Handshake.

Leaving as-is

In draft-ietf-quic-tls.md:

>  
+Unlike TLS over TCP, QUIC applications which want to send data do not
+send it through TLS "application_data" records. Rather, they send it
+as QUIC STREAM frames which are then carried in QUIC packets.
+
+
+# Carrying TLS Messages {#carrying-tls}
+
+QUIC carries TLS handshake data in CRYPTO_HS frames, each of which

Leaving as-is.

In draft-ietf-quic-tls.md:

> +and encrypted under the current TLS encryption level.
+As with TLS over TCP, once TLS handshake data has
+been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:

Rewritten a bit.

In draft-ietf-quic-tls.md:

> +been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use
+the same keys even if TLS has already updated to newer keys.
+
+One important difference between TLS 1.3 records (used with TCP)
+and QUIC CRYPTO_HS frames is that in QUIC multiple frames may appear
+in the same QUIC packet as long as they are associated with the
+same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.

Nothing needed at this time.

In draft-ietf-quic-tls.md:

> +same encryption level. For instance, an implementation might
+bundle a Handshake message and an ACK for some Handshake
+data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.

Doing nothing.

In draft-ietf-quic-tls.md:

> +data into the same packet.
+
+In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet

Done

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

Done.

In draft-ietf-quic-tls.md:

> +- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.
+
+| Packet Type     | Encryption Level |
+|:----------------|:-----------------|
+| Initial         | Initial secrets  |
+| 0-RTT Protected | 0-RTT            |
+| Handshake       | Handshake        |
+| Retry           | N/A              |
+| Short Header    | 1-RTT            |
+{: #packet-types-levels title="Encryption Levels by Packet Type"}

Done.

In draft-ietf-quic-tls.md:

> +Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.
+
+| Packet Type     | Encryption Level |
+|:----------------|:-----------------|
+| Initial         | Initial secrets  |
+| 0-RTT Protected | 0-RTT            |
+| Handshake       | Handshake        |
+| Retry           | N/A              |
+| Short Header    | 1-RTT            |
+{: #packet-types-levels title="Encryption Levels by Packet Type"}
+
+{{QUIC-TRANSPORT}}; Section 6.3 shows how packets at the various encryption

Done

In draft-ietf-quic-tls.md:

>  
 ## Interface to TLS
 
-As shown in {{schematic}}, the interface from QUIC to TLS consists of four
-primary functions: Handshake, Source Address Validation, Key Ready Events, and
-Secret Export.
+As shown in {{schematic}}, the interface from QUIC to TLS consists of three
+primary functions:
+
+- Sending and receiving handshake messages
+- Rekeying (both in and out)

Changed to "transmit and receive"

In draft-ietf-quic-tls.md:

>  
 In order to drive the handshake, TLS depends on being able to send and receive
-handshake messages on stream 0.  There are two basic functions on this
+handshake messages. There are two basic functions on this

Done

In draft-ietf-quic-tls.md:

> -A QUIC server starts the process by providing TLS with stream 0 octets.
-
-Each time that an endpoint receives data on stream 0, it delivers the octets to
-TLS if it is able.  Each time that TLS is provided with new data, new handshake
-octets are requested from TLS.  TLS might not provide any octets if the
-handshake messages it has received are incomplete or it has no data to send.
-
-At the server, when TLS provides handshake octets, it also needs to indicate
-whether the octets contain a HelloRetryRequest.  A HelloRetryRequest MUST always
-be sent in a Retry packet, so the QUIC server needs to know whether the octets
-are a HelloRetryRequest.
+A QUIC server starts the process by providing TLS with the client's
+handshake octets.
+
+At any given time, an endpoint will have a current sending encryption
+level and receiving encryption level. Each encryption level is

I don't think that I agree with this.

Let's take send and receive separately. At any given time, the TLS stack is always sending with a given encryption level. That's just a fact of TLS, whether that's done by doing Rekey(); Send() or Send(Keys). In either case, the data is associated with that level when its sent to QUIC and QUIC needs to maintain that level upon transmission or retransmission.

Receive is more complicated: At any given time, the TLS stack is only prepared to receive packets at a given level. This is also a fact of TLS [0]. As you say, when a packet comes in, it is tagged with an encryption level and there are three cases:

  • It's from a prior level, in which case it needs to be consistent with the existing data
  • It's from the current level, in which case you process it
  • It's from a future level, in which case you (probably) buffer it [I'm ignoring cases in which you packet that's impossibly from the future, like CFIN before you send SH.

Now, you can do this sorting/buffering operation at the TLS layer (like I think picoTLS does) or at the QUIC layer (like Minq does), but I think it's still true that there's one active level

[0] The only case in which this is confusing is 0-RTT rejection where the client is sending with Epoch 1 and the server is trying to receive with Epoch 0 or 2 (depending on how it was rejected). However, neither of these cases applies to QUIC, because you just don't enable the 0-RTT encryption level and so the packets are dropped prior to TLS.

In draft-ietf-quic-tls.md:

> +
+At any given time, an endpoint will have a current sending encryption
+level and receiving encryption level. Each encryption level is
+associated with a different flow of bytes, which is reliably
+transmitted to the peer in CRYPTO_HS frames. When TLS provides handshake
+octets to be sent, they are appended to the current flow and
+will eventually be transmitted under the then-current key.
+
+When an endpoint receives a QUIC packet containing a CRYPTO_HS frame from
+the network, it proceeds as follows:
+
+- If the packet was in the current receiving encryption level, sequence
+  the data into the input flow as usual. As with STREAM frames,
+  the offset is used to find the proper location in the data sequence.
+  If the result of this process is that new data is available, then
+  it is delivered to TLS.

Done

In draft-ietf-quic-tls.md:

> +will eventually be transmitted under the then-current key.
+
+When an endpoint receives a QUIC packet containing a CRYPTO_HS frame from
+the network, it proceeds as follows:
+
+- If the packet was in the current receiving encryption level, sequence
+  the data into the input flow as usual. As with STREAM frames,
+  the offset is used to find the proper location in the data sequence.
+  If the result of this process is that new data is available, then
+  it is delivered to TLS.
+
+- If the packet is from a previously installed encryption level, it
+  MUST not contain data which extends past the end of previously
+  received data in that flow. Implementations MUST treat any
+  violations of this requirement as a connection error of type
+  PROTOCOL_VIOLATION.

This doesn't seem right to me. First, the 0-RTT STREAM frame isn't relevant, because this is just about CRYPTO_HS.

As for EOED, here's what happens ordinarily (no loss)

  • Recv CH; Rekey current RX to epoch 1
  • Receive EOED: Rekey current RX to epoch 2
  • Receive CFIN: Rekey current RX to epoch 3

If instead you get CH, CFIN, EOED, here's what happens:

  • Recv CH; Rekey current RX to epoch 1
  • Receive CFIN: it's in the future, so buffer
  • Receive EOED: Rekey current RX to epoch 2
  • Process CFIN; Rekey current RX to epoch 3

In draft-ietf-quic-tls.md:

>                                                     Get Handshake
-                                                1-RTT Keys Ready
-                     <--- send/receive ---
+                      <------------ Initial
+                                          Rekey rx to 0-RTT keys

Leaving this pending the "current" discussion above.

In draft-ietf-quic-tls.md:

>  
-## QUIC Key Expansion {#key-expansion}
+A server rejects 0-RTT by rejecting 0-RTT at the TLS layer.  This results in
+early exporter keys being unavailable, thereby preventing the use of 0-RTT for
+QUIC.

Done.

In draft-ietf-quic-tls.md:

>  
-QUIC uses a system of packet protection secrets, keys and IVs that are modelled
-on the system used in TLS {{!TLS13}}.  The secrets that QUIC uses
-as the basis of its key schedule are obtained using TLS exporters (see Section
-7.5 of {{!TLS13}}).
+A client that attempts 0-RTT MUST also consider 0-RTT to be rejected if it
+receives a Version Negotiation packet.

Why? It seems like you could just start sending 0-RTT right then

In draft-ietf-quic-tls.md:

>  
-QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=RFC5869}} with
-the same hash function negotiated by TLS for key derivation.  For example, if
-TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is used.
+In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section
+4.1.4) can be used to correct a client's incorrect KeyShare extension
+as well as for a stateless round trip check. From the perspective of

Done.

In draft-ietf-quic-tls.md:

>  
-QUIC uses the Hash-based Key Derivation Function (HKDF) {{!HKDF=RFC5869}} with
-the same hash function negotiated by TLS for key derivation.  For example, if
-TLS is using the TLS_AES_128_GCM_SHA256, the SHA-256 hash function is used.
+In TLS over TCP, the HelloRetryRequest feature ({{TLS13}; Section
+4.1.4) can be used to correct a client's incorrect KeyShare extension
+as well as for a stateless round trip check. From the perspective of
+QUIC, this just looks like additional messages carried in the Initial
+encryption level. Although it is in principle possible to use this
+feature for address verification in QUIC, QUIC implementations SHOULD
+instead use the Retry feature ({{QUIC-TRANSPORT}}; Section 4.4.2)).

Done

In draft-ietf-quic-tls.md:

>  
-The HKDF-Expand function used by QHKDF-Expand uses the PRF hash function
-negotiated by TLS, except for handshake secrets and keys derived from them (see
-{{handshake-secrets}}).
+If TLS experiences an error, it MUST generate an appropriate alert
+as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
+which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
+"fatal".

Added a reference to TLS 13.

In draft-ietf-quic-tls.md:

>  
-~~~
-struct {
-   uint16 length = Length;
-   opaque label<6..255> = "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the TLS
+handshake, using the AEAD algorithm negotiated by TLS.

Left.

In draft-ietf-quic-tls.md:

> -   uint16 length = Length;
-   opaque label<6..255> = "QUIC " + Label;
-} QhkdfExpandInfo;
-~~~
+# QUIC Packet Protection {#packet-protection}
+
+As with TLS over TCP, QUIC encrypts packets with keys derived from the TLS
+handshake, using the AEAD algorithm negotiated by TLS.
+
+
+## QUIC Packet Encryption Keys {#encryption-keys}
+
+QUIC derives packet encryption keys in the same way as TLS 1.3:
+Each encryption level/direction pair has a secret value, which
+is then used to derive the traffic keys using as described
+in {{TLS13}}; Section 7.3.

replaced with comma.

In draft-ietf-quic-tls.md:

>  
-For example, assuming a hash function with a 32 octet output, derivation for a
-client packet protection key would use HKDF-Expand with an `info` parameter of
-0x00200851554943206b6579.
+The keys for the Initial encryption level are computed based on
+the client's first Destination Connection Id, as described in

Done.

In draft-ietf-quic-tls.md:

>  
+The keys for the remaining encryption level are computed in the same
+fashion as the corresponding TLS keys (see {{TLS13}}; Section 7),
+except that the label for HKDF-Expand-Label uses the prefix "quic "
+rather than "tls 13". The purpose of this change is to provide key

Done

In draft-ietf-quic-tls.md:

>  
+The keys for the remaining encryption level are computed in the same
+fashion as the corresponding TLS keys (see {{TLS13}}; Section 7),
+except that the label for HKDF-Expand-Label uses the prefix "quic "
+rather than "tls 13". The purpose of this change is to provide key
+separation between TLS and QUIC, so that TLS stacks can avoid
+exposing TLS record protection keys.

My intention was that this be completely separate, actually.

With that said, I think there are a number of options here. I have the action item to talk to the cryptographers.

In draft-ietf-quic-tls.md:

>  
-Packets that carry the TLS handshake (Initial, Retry, and Handshake) are
-protected with a secret derived from the Destination Connection ID field from
-the client's Initial packet.  Specifically:
+Initial packets are protected with
+a secret derived from the Destination Connection ID field from the client's
+Initial packet.  Specifically:

Rewritten a bit. The Retry thing is still in flux.

In draft-ietf-quic-tls.md:

>  ~~~
 
 The hash function for HKDF when deriving handshake secrets and keys is SHA-256
-{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with QHKDF-Expand
-is the connection ID chosen by the client.
+{{!SHA=DOI.10.6028/NIST.FIPS.180-4}}.  The connection ID used with
+HKDF-Expand-Label is the connection ID chosen by the client.

changed.

In draft-ietf-quic-tls.md:

> @@ -743,121 +653,11 @@ Note:
 
 : The Destination Connection ID is of arbitrary length, and it could be zero
   length if the server sends a Retry packet with a zero-length Source Connection
-  ID field.  In this case, the handshake keys provide no assurance to the client
+  ID field.  In this case, the initial keys provide no assurance to the client

Done.

In draft-ietf-quic-tls.md:

> @@ -873,26 +673,20 @@ from the packet number.
 All QUIC packets other than Version Negotiation and Stateless Reset packets are
 protected with an AEAD algorithm {{!AEAD}}. Prior to establishing a shared
 secret, packets are protected with AEAD_AES_128_GCM and a key derived from the
-client's connection ID (see {{handshake-secrets}}).  This provides protection
+client's connection ID (see {{initial-secrets}}).  This provides protection

Done.

In draft-ietf-quic-tls.md:

>  against off-path attackers and robustness against QUIC version unaware
 middleboxes, but not against on-path attackers.
 
 All ciphersuites currently defined for TLS 1.3 - and therefore QUIC - have a
 16-byte authentication tag and produce an output 16 bytes larger than their
 input.
 
-Once TLS has provided a key, the contents of regular QUIC packets immediately
-after any TLS messages have been sent are protected by the AEAD selected by TLS.
-
-The key, K, is either the client packet protection key (client_pp_key\<i>) or
-the server packet protection key (server_pp_key\<i>), derived as defined in
-{{key-expansion}}.
-
-The nonce, N, is formed by combining the packet protection IV (either
-client_pp_iv\<i\> or server_pp_iv\<i\>) with the packet number.  The 64 bits
-of the reconstructed QUIC packet number in network byte order is left-padded
-with zeros to the size of the IV.  The exclusive OR of the padded packet number
-and the IV forms the AEAD nonce.
+The key and iv for the packet are computed as described in {{encryption-keys}}.

Done

In draft-ietf-quic-tls.md:

> -Once TLS has provided a key, the contents of regular QUIC packets immediately
-after any TLS messages have been sent are protected by the AEAD selected by TLS.
-
-The key, K, is either the client packet protection key (client_pp_key\<i>) or
-the server packet protection key (server_pp_key\<i>), derived as defined in
-{{key-expansion}}.
-
-The nonce, N, is formed by combining the packet protection IV (either
-client_pp_iv\<i\> or server_pp_iv\<i\>) with the packet number.  The 64 bits
-of the reconstructed QUIC packet number in network byte order is left-padded
-with zeros to the size of the IV.  The exclusive OR of the padded packet number
-and the IV forms the AEAD nonce.
+The key and iv for the packet are computed as described in {{encryption-keys}}.
+The nonce, N, is formed by combining the packet protection IV with the
+packet number.  The 64 bits of the reconstructed QUIC packet number in
+network byte order is left-padded with zeros to the size of the IV.

are

In draft-ietf-quic-tls.md:

> @@ -1024,144 +795,90 @@ encrypted_pn = ChaCha20(pn_key, counter, nonce, packet_number)
 
 ## Receiving Protected Packets
 
-Once an endpoint successfully receives a packet with a given packet number, it
-MUST discard all packets with higher packet numbers if they cannot be
-successfully unprotected with either the same key, or - if there is a key update
-- the next packet protection key (see {{key-update}}).  Similarly, a packet that
-appears to trigger a key update, but cannot be unprotected successfully MUST be
-discarded.
+Once an endpoint successfully receives a packet with a given packet
+number, it MUST discard all packets in the same packet number space
+with higher packet numbers if they cannot be successfully unprotected
+with either the same key, or - if there is a key update - the next
+packet protection key (see {{key-update}}).  Similarly, a packet that
+appears to trigger a key update, but cannot be unprotected
+successfully MUST be discarded.

I don't see what this has to do with EOED. Can you show me the packet flow you think has a problem here.

In draft-ietf-quic-tls.md:

>  
-A server might choose to retain 0-RTT packets that arrive before a TLS
-ClientHello.  The server can then use those packets once the ClientHello
-arrives.  However, the potential for denial of service from buffering 0-RTT
-packets is significant.  These packets cannot be authenticated and so might be
-employed by an attacker to exhaust server resources.  Limiting the number of
-packets that are saved might be necessary.
+A client MUST only use 0-RTT keys to protect data that is idempotent.  A client
+MAY wish to apply additional restrictions on what data it sends prior to the
+completion of the TLS handshake.  A client otherwise treats 0-RTT keys as
+equivalent to 1-RTT keys, except that ACKs for that data MUST only be sent with
+1-RTT keys.

Done.

In draft-ietf-quic-tls.md:

>  
-### Retransmission and Acknowledgment of Unprotected Packets
+: 0-RTT data can be acknowledged by the server as it receives it, but any

It's a Note.

In draft-ietf-quic-tls.md:

>  
-Once 1-RTT keys are available to an endpoint, it no longer needs the TLS
-handshake messages that are carried in unprotected packets.  However, a server
-might need to retransmit its TLS handshake messages in response to receiving an
-unprotected packet that contains ACK frames.  A server MUST process ACK frames
-in unprotected packets until the TLS handshake is reported as complete, or it
-receives an ACK frame in a protected packet that acknowledges all of its
-handshake messages.
+Receiving and verifying the TLS Finished message is critical in
+ensuring the integrity of the TLS handshake.  A server MUST NOT use
+1-RTT protected packets from the client prior to verifying the client
+Finished message if its response depends on client authentication.

Removed. I think this is old text, though.

In draft-ietf-quic-tls.md:

>  
-## Key Update {#key-update}
+Once the 1-RTT keys are established and the short header is in use, it
+is possible to update the keys, for instance because of limits on AEAD
+encryption.  The KEY_PHASE bit in the short header is used to indicate

I just removed it.

In draft-ietf-quic-tls.md:

> -server has chosen to use a pre-shared key - the pre-shared key binder (see
-Section 4.2.8 of {{!TLS13}}).  Verifying these values provides the server with
-an assurance that the ClientHello has not been modified.
-
-A server could receive packets protected with 0-RTT keys prior to receiving a
-TLS ClientHello.  The server MAY retain these packets for later decryption in
-anticipation of receiving a ClientHello.
-
-Receiving and verifying the TLS Finished message is critical in ensuring the
-integrity of the TLS handshake.  A server MUST NOT use protected packets from
-the client prior to verifying the client Finished message if its response
-depends on client authentication.
+It is also possible for the attacker to tamper with data that
+is carried in Handshake packets, but because that tampering
+requires modifying TLS handshake messages, that tampering will be
+detected as soon as the TLS handshake completes.

Done.

In draft-ietf-quic-tls.md:

> @@ -1592,6 +996,11 @@ version of QUIC defined in {{QUIC-TRANSPORT}} is used.
 The quic_transport_parameters extension is carried in the ClientHello and the
 EncryptedExtensions messages during the handshake.
 
+While the transport parameters are technically available prior to the
+completion of the handshake, they cannot be fully trusted until the handshake
+completes, and reliance on them should be minimized.
+However, any tampering with the parameters will be detected
+when the handshake completes.

Done

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if

Done

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};

Done.

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};
+Section 4.4.3). Finally, because ACKs of Handshake packets

Done

In draft-ietf-quic-tls.md:

> @@ -1608,14 +1017,13 @@ A small ClientHello that results in a large block of handshake messages from a
 server can be used in packet reflection attacks to amplify the traffic generated
 by an attacker.
 
-Certificate caching {{?RFC7924}} can reduce the size of the server's handshake
-messages significantly.
-
-QUIC requires that the packet containing a ClientHello be padded to a minimum
-size.  A server is less likely to generate a packet reflection attack if the
-data it sends is a small multiple of this size.  A server SHOULD use a
-HelloRetryRequest if the size of the handshake messages it sends is likely to
-significantly exceed the size of the packet containing the ClientHello.
+QUIC includes three defenses against this attack. First, the packet
+containing a ClientHello be padded to a minimum size. Second, if
+responding to an unverified source address, the server is forbidden to
+send more than three packets in its first flight ({{QUIC-TRANSPORT}};
+Section 4.4.3). Finally, because ACKs of Handshake packets
+are authenticated, a blind attacker cannot forge them

Done

In draft-ietf-quic-transport.md:

>  
 All these packets use the long header and contain the current QUIC version in
 the version field.
 
-In order to prevent tampering by version-unaware middleboxes, handshake packets
-are protected with a connection- and version-specific key, as described in
-{{QUIC-TLS}}. This protection does not provide confidentiality or integrity
-against on-path attackers, but provides some level of protection against
-off-path attackers.
+In order to prevent tampering by version-unaware middleboxes, Initial
+packets are protected with a connection- and version-specific keys

Done

In draft-ietf-quic-transport.md:

>  
 
 ### Initial Packet {#packet-initial}
 
 The Initial packet uses long headers with a type value of 0x7F.  It carries the
-first cryptographic handshake message sent by the client.
+first CRYPTO_HS frames sent by the client as well as the
+cryptographic messages sent by the server to perform key exchange. The Initial

Done

In draft-ietf-quic-transport.md:

>  
 
 ### Initial Packet {#packet-initial}
 
 The Initial packet uses long headers with a type value of 0x7F.  It carries the
-first cryptographic handshake message sent by the client.
+first CRYPTO_HS frames sent by the client as well as the
+cryptographic messages sent by the server to perform key exchange. The Initial
+packet is protected by Initial keys as described in {{QUIC-TLS}}.

Done

In draft-ietf-quic-transport.md:

>  
-If the client received a Retry packet and is sending a second Initial packet,
-then it sets the Destination Connection ID to the value from the Source
-Connection ID in the Retry packet.  Changing Destination Connection ID also
-results in a change to the keys used to protect the Initial packet.
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...

I mostly-centered this. Is that what you wanted.

In draft-ietf-quic-transport.md:

> -results in a change to the keys used to protect the Initial packet.
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                            Token (*)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+Token Length:
+
+: A variable-length integer specifying the length of the Token field, in bytes.
+It may be zero if no token is present. The server MUST send a zero-length
+token.

Done.

In draft-ietf-quic-transport.md:

> +|        Token Length (i)  ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                            Token (*)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+Token Length:
+
+: A variable-length integer specifying the length of the Token field, in bytes.
+It may be zero if no token is present. The server MUST send a zero-length
+token.
+
+Token:
+
+: An optional token blob previously received in either a Retry packet or
+NEW_TOKEN frame.

I would expect it only on the first one, but leaving the text as-is, as this whole design seems a bit in flux.

In draft-ietf-quic-transport.md:

> +Token Length:
+
+: A variable-length integer specifying the length of the Token field, in bytes.
+It may be zero if no token is present. The server MUST send a zero-length
+token.
+
+Token:
+
+: An optional token blob previously received in either a Retry packet or
+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that contains
+an initial cryptographic handshake message. This includes all cases where a new
+packet containing the initial cryptographic message needs to be created, this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).

Done.

In draft-ietf-quic-transport.md:

> +Token:
+
+: An optional token blob previously received in either a Retry packet or
+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that contains
+an initial cryptographic handshake message. This includes all cases where a new
+packet containing the initial cryptographic message needs to be created, this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.  A
+server may send multiple Initial packets.  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)

Done.

In draft-ietf-quic-transport.md:

> +: An optional token blob previously received in either a Retry packet or
+NEW_TOKEN frame.
+
+The client and server use the Initial packet type for any packet that contains
+an initial cryptographic handshake message. This includes all cases where a new
+packet containing the initial cryptographic message needs to be created, this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.  A
+server may send multiple Initial packets.  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete

Done

In draft-ietf-quic-transport.md:

> +The client and server use the Initial packet type for any packet that contains
+an initial cryptographic handshake message. This includes all cases where a new
+packet containing the initial cryptographic message needs to be created, this
+includes the packets sent after receiving a Version Negotiation
+({{packet-version}}) or Retry packet ({{packet-retry}}).
+
+A server sends its first Initial packet in response to a client Initial.  A
+server may send multiple Initial packets.  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete
+first message MUST fit in a single packet (see {{handshake}}). Note that if
+the server sends a HelloRetryRequest, the client will send a second Initial
+packet with a CRYPTO_HS frame starting immediately after the first one.

Did something here.

In draft-ietf-quic-transport.md:

> +
+A server sends its first Initial packet in response to a client Initial.  A
+server may send multiple Initial packets.  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete
+first message MUST fit in a single packet (see {{handshake}}). Note that if
+the server sends a HelloRetryRequest, the client will send a second Initial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously received

Done.

In draft-ietf-quic-transport.md:

> +server may send multiple Initial packets.  The cryptographic key exchange could
+require multiple round trips or retransmissions of this data.
+
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete
+first message MUST fit in a single packet (see {{handshake}}). Note that if
+the server sends a HelloRetryRequest, the client will send a second Initial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously received
+a Retry packet from the server, it populates the Destination Connection ID field
+with a randomly selected value.  This MUST be at least 8 octets in length. Until

OK, though I see a lot of "random" in this document.

In draft-ietf-quic-transport.md:

> +
+The payload of an Initial packet conveys a CRYPTO_HS frame (or frames)
+containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete
+first message MUST fit in a single packet (see {{handshake}}). Note that if
+the server sends a HelloRetryRequest, the client will send a second Initial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously received
+a Retry packet from the server, it populates the Destination Connection ID field
+with a randomly selected value.  This MUST be at least 8 octets in length. Until
+a packet is received from the server, the client MUST use the same random value
+unless it also changes the Source Connection ID (which effectively starts a new

That's not actually correct, because you can use SCID=""

In draft-ietf-quic-transport.md:

> +containing a cryptographic handshake message. The first CRYPTO_HS frame
+send always begins at an offset of 0 (see {{handshake}}). The client's complete
+first message MUST fit in a single packet (see {{handshake}}). Note that if
+the server sends a HelloRetryRequest, the client will send a second Initial
+packet with a CRYPTO_HS frame starting immediately after the first one.
+
+
+#### Connection IDs
+
+When an an Initial packet is sent by a client which has not previously received
+a Retry packet from the server, it populates the Destination Connection ID field
+with a randomly selected value.  This MUST be at least 8 octets in length. Until
+a packet is received from the server, the client MUST use the same random value
+unless it also changes the Source Connection ID (which effectively starts a new
+connection attempt).  The randomized Destination Connection ID is used to
+determine packet protection keys.

Done.

In draft-ietf-quic-transport.md:

>  
 The client populates the Source Connection ID field with a value of its choosing
 and sets the SCIL field to match.
 
-The first Initial packet that is sent by a client contains a packet number of 0.
-All subsequent packets contain a packet number that is incremented by at least
-one, see ({{packet-numbers}}).
-
-The payload of an Initial packet conveys a STREAM frame (or frames) for stream
-0 containing a cryptographic handshake message.  The stream in this packet
-always starts at an offset of 0 (see {{stateless-retry}}) and the complete
-cryptographic handshake message MUST fit in a single packet (see {{handshake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet

I think "a" is fine here.

In draft-ietf-quic-transport.md:

>  
 The client populates the Source Connection ID field with a value of its choosing
 and sets the SCIL field to match.
 
-The first Initial packet that is sent by a client contains a packet number of 0.
-All subsequent packets contain a packet number that is incremented by at least
-one, see ({{packet-numbers}}).
-
-The payload of an Initial packet conveys a STREAM frame (or frames) for stream
-0 containing a cryptographic handshake message.  The stream in this packet
-always starts at an offset of 0 (see {{stateless-retry}}) and the complete
-cryptographic handshake message MUST fit in a single packet (see {{handshake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection

Leaving as-is because in flux.

In draft-ietf-quic-transport.md:

> -
-The payload of an Initial packet conveys a STREAM frame (or frames) for stream
-0 containing a cryptographic handshake message.  The stream in this packet
-always starts at an offset of 0 (see {{stateless-retry}}) and the complete
-cryptographic handshake message MUST fit in a single packet (see {{handshake}}).
+The Destination Connection ID field in the server's Initial packet
+contains a connection ID that is chosen by the recipient of the packet
+(i.e., the client); the Source Connection ID includes the connection
+ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection
+IDs during the handshake.
+
+On first receiving an Initial or Retry packet from the server, the
+client uses the Source Connection ID supplied by the server as the
+Destination Connection ID for subsequent packets. The client MUST
+discard any subsequent packets it receives with different

Done.

In draft-ietf-quic-transport.md:

> +ID that the sender of the packet wishes to use (see
+{{connection-id}}). The server MUST use consistent Source Connection
+IDs during the handshake.
+
+On first receiving an Initial or Retry packet from the server, the
+client uses the Source Connection ID supplied by the server as the
+Destination Connection ID for subsequent packets. The client MUST
+discard any subsequent packets it receives with different
+Source Connection IDs.
+
+#### Tokens
+
+If the client has a suitable token available from a previous connection,
+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an

I'm going to leave it as-is for now.

In draft-ietf-quic-transport.md:

> +
+#### Tokens
+
+If the client has a suitable token available from a previous connection,
+it SHOULD populate the Token field.
+
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID to
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated

Leaving b/c this design is in flux.

In draft-ietf-quic-transport.md:

> +
+If the client received a Retry packet from the server and sends an
+Initial packet in response, then it sets the Destination Connection ID to
+the value from the Source Connection ID in the Retry packet. Changing
+Destination Connection ID also results in a change to the keys used to
+protect the Initial packet. It also sets the Token field to the
+token provided in the Retry.
+
+When a server receives an Initial packet with an address validation
+token, it SHOULD attempt to validate it.  If the token is invalid then
+the server SHOULD proceed as if the client did not have a validated
+address, including potentially sending a Retry. If the validation
+succeeds, the server SHOULD then allow the handshake to proceed (see
+{{stateless-retry}}).
+
+Note: The rationale for treating the client as unvalidated rather

Done.

In draft-ietf-quic-transport.md:

> +address, including potentially sending a Retry. If the validation
+succeeds, the server SHOULD then allow the handshake to proceed (see
+{{stateless-retry}}).
+
+Note: The rationale for treating the client as unvalidated rather
+than discarding the packet is that the client might have received
+the token in a previous connection using the NEW_TOKEN message,
+and if the server has lost state, it might be unable to validate
+the token at all, leading to connection failure if the packet
+is discarded.
+
+#### Starting Packet Numbers
+
+The first Initial packet contains a packet number of 0. Each packet sent after
+the Initial packet is associated with a packet number space and its packet
+number increases monotonically in that space (see {{packet-numbers}}).

Good question. Seems like an open issue.

In draft-ietf-quic-transport.md:

>  
 ### Retry Packet {#packet-retry}
 
-A Retry packet uses long headers with a type value of 0x7E.  It carries
-cryptographic handshake messages and acknowledgments.  It is used by a server
-that wishes to perform a stateless retry (see {{stateless-retry}}).
+A Retry packet uses long headers with a type value of 0x7E. It carries an
+address validation token created by the server. It is used by a server that
+wishes to perform a stateless retry (see {{stateless-retry}}).
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|     DCIL(8)   |      Original Destination Connection ID (*)   |

Done.

In draft-ietf-quic-transport.md:

>  
 ### Retry Packet {#packet-retry}
 
-A Retry packet uses long headers with a type value of 0x7E.  It carries
-cryptographic handshake messages and acknowledgments.  It is used by a server
-that wishes to perform a stateless retry (see {{stateless-retry}}).
+A Retry packet uses long headers with a type value of 0x7E. It carries an
+address validation token created by the server. It is used by a server that
+wishes to perform a stateless retry (see {{stateless-retry}}).
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|     DCIL(8)   |      Original Destination Connection ID (*)   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        Retry Token (*)

Done.

In draft-ietf-quic-transport.md:

>  
-After receiving a Retry packet, the client uses a new
-Initial packet containing the next cryptographic handshake message.  The client
-retains the state of its cryptographic handshake, but discards all transport
-state.  The Initial packet that is generated in response to a Retry packet
-includes STREAM frames on stream 0 that start again at an offset of 0.
+A server MUST only send a Retry in response to a client Initial packet.

Leaving because in flux.

In draft-ietf-quic-transport.md:

>  
-Continuing the cryptographic handshake is necessary to ensure that an attacker
-cannot force a downgrade of any cryptographic parameters.  In addition to
-continuing the cryptographic handshake, the client MUST remember the results of
-any version negotiation that occurred (see {{version-negotiation}}).  The client
-MAY also retain any observed RTT or congestion state that it has accumulated for
-the flow, but other transport state MUST be discarded.
+If the Original Destination Connection ID field does not match the
+Destination Connection ID from the Initial packet it sent, clients MUST
+discard the packet. This prevents an off-path attacker from injecting
+a Retry packet with a bogus new Source Connection ID.

I prefer the current text.

In draft-ietf-quic-transport.md:

>  
-Continuing the cryptographic handshake is necessary to ensure that an attacker
-cannot force a downgrade of any cryptographic parameters.  In addition to
-continuing the cryptographic handshake, the client MUST remember the results of
-any version negotiation that occurred (see {{version-negotiation}}).  The client
-MAY also retain any observed RTT or congestion state that it has accumulated for
-the flow, but other transport state MUST be discarded.
+If the Original Destination Connection ID field does not match the
+Destination Connection ID from the Initial packet it sent, clients MUST

Done.

In draft-ietf-quic-transport.md:

>  
-The payload of the Retry packet contains at least two frames. It MUST include a
-STREAM frame on stream 0 with offset 0 containing the server's cryptographic
-stateless retry material. It MUST also include an ACK frame to acknowledge the
-client's Initial packet. It MAY additionally include PADDING frames. The next
-STREAM frame sent by the server will also start at stream offset 0.
+Otherwise, the client SHOULD respond with a new Initial
+packet with the Token field set to the token received in the Retry packet.

I agree, but leaving because the design is in flux.

In draft-ietf-quic-transport.md:

>  
-If the server expects to generate more than three Handshake packets in response
-to an Initial packet, it SHOULD include a PATH_CHALLENGE frame in each Handshake
-packet that it sends.  After receiving at least one valid PATH_RESPONSE frame,
-the server can send its remaining Handshake packets. Servers can instead perform
-address validation using a Retry packet; this requires less state on the server,
-but could involve additional computational effort depending on implementation
-choices.
+Servers MUST NOT send more than three packets including Initial and Handshake

Done.

In draft-ietf-quic-transport.md:

> @@ -694,7 +777,7 @@ Packets protected with 0-RTT keys use a type value of 0x7C.  The connection ID
 fields for a 0-RTT packet MUST match the values used in the Initial packet
 ({{packet-initial}}).
 
-The client can send 0-RTT packets after receiving a Handshake packet
+The client can send 0-RTT packets after receiving an Initial or Handshake packet

Done

In draft-ietf-quic-transport.md:

> @@ -761,7 +844,7 @@ During the handshake, an endpoint might receive multiple packets with the long
 header, and thus be given multiple opportunities to update the Destination
 Connection ID it sends.  A client MUST only change the value it sends in the
 Destination Connection ID in response to the first packet of each type it
-receives from the server (Retry or Handshake); a server MUST set its value based
+receives from the server (Retry or Initial); a server MUST set its value based
 on the Initial packet.  Any additional changes are not permitted; if subsequent

Leaving, in flux.

In draft-ietf-quic-transport.md:

> @@ -792,15 +875,36 @@ response to connection migration ({{migration}}). NEW_CONNECTION_ID frames
 
 The packet number is an integer in the range 0 to 2^62-1. The value is used in
 determining the cryptographic nonce for packet encryption.  Each endpoint
-maintains a separate packet number for sending and receiving.  The packet number
-for sending MUST start at zero for the first packet sent and MUST increase by at
-least one after sending a packet.
+maintains a separate packet number for sending and receiving.
+
+Packet numbers are divided into 3 spaces in QUIC:
+
+- Initial space: All Initial packets {{packet-initial}} are in this space.
+- Handshake space: All Handshake packets {{packet-handshake}} are in this space.
+- Application data space: All 0-RTT and 1-RTT encrypted packets
+  {{packet-protected}} are in this space.
+
+As descibed in {{QUIC-TLS}}, each packet type uses different encryption keys.

Done.

In draft-ietf-quic-transport.md:

> -least one after sending a packet.
+maintains a separate packet number for sending and receiving.
+
+Packet numbers are divided into 3 spaces in QUIC:
+
+- Initial space: All Initial packets {{packet-initial}} are in this space.
+- Handshake space: All Handshake packets {{packet-handshake}} are in this space.
+- Application data space: All 0-RTT and 1-RTT encrypted packets
+  {{packet-protected}} are in this space.
+
+As descibed in {{QUIC-TLS}}, each packet type uses different encryption keys.
+
+Conceptually, a packet number space is the encryption context in which a packet
+can be processed and ACKed.  Initial packets can only be sent with
+Initial encryption keys and ACKed in packets which are also Initial packets.
+Similarly Handshake packets can only be sent and acked in Handshake packets.

Done.

In draft-ietf-quic-transport.md:

>  
-A QUIC endpoint MUST NOT reuse a packet number within the same connection (that
-is, under the same cryptographic keys).  If the packet number for sending
-reaches 2^62 - 1, the sender MUST close the connection without sending a
-CONNECTION_CLOSE frame or any further packets; an endpoint MAY send a Stateless
-Reset ({{stateless-reset}}) in response to further packets that it receives.
+This enforces cryptographic separation between the data sent in the
+different packet sequence number spaces.  As a result, each packet number space

Done.

In draft-ietf-quic-transport.md:

>  cryptographic handshake protocol is in use.
 
-QUIC provides this stream with reliable, ordered delivery of data.  In return,
-the cryptographic handshake provides QUIC with:
+QUIC provides the cryptographic handshake with reliable, ordered
+delivery of data via the CRYPTO_HS frame.  In return, the

Done.

In draft-ietf-quic-transport.md:

> @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with:
   client can receive packets that are addressed with the transport address that
   is claimed by the client (see {{address-validation}})
 
-The initial cryptographic handshake message MUST be sent in a single packet.
-Any second attempt that is triggered by address validation MUST also be sent
-within a single packet.  This avoids having to reassemble a message from
-multiple packets.  Reassembling messages requires that a server maintain state
-prior to establishing a connection, exposing the server to a denial of service
-risk.
+The CRYPTO_HS frame provides an offset and a length.  QUIC functions
+as the record encryption layer for the cryptographic protocol.

Done,

In draft-ietf-quic-transport.md:

> @@ -1118,19 +1227,83 @@ the cryptographic handshake provides QUIC with:
   client can receive packets that are addressed with the transport address that
   is claimed by the client (see {{address-validation}})
 
-The initial cryptographic handshake message MUST be sent in a single packet.
-Any second attempt that is triggered by address validation MUST also be sent
-within a single packet.  This avoids having to reassemble a message from
-multiple packets.  Reassembling messages requires that a server maintain state
-prior to establishing a connection, exposing the server to a denial of service
-risk.
+The CRYPTO_HS frame provides an offset and a length.  QUIC functions
+as the record encryption layer for the cryptographic protocol.
+
+The initial CRYPTO_HS frame MUST be sent in a single packet.  Any
+second attempt that is triggered by address validation MUST also be
+sent within a single packet. This avoids having to reassemble a
+message from multiple packets.

I'm not following, so leaving.

In draft-ietf-quic-transport.md:

>  
 The first client packet of the cryptographic handshake protocol MUST fit within
 a 1232 octet QUIC packet payload.  This includes overheads that reduce the space
 available to the cryptographic handshake protocol.
 
-Details of how TLS is integrated with QUIC is provided in more detail in
-{{QUIC-TLS}}.
+The CRYPTO_HS frame can be sent in different packet number spaces.
+CRYPTO_HS frames in each packet number space carry a separate sequence
+of handshake data starting from an offset of 0.

I think I'm happier where it is, so I'm going to leave as-is and let you realize your vision when you want ti.

In draft-ietf-quic-transport.md:

>  
 The first client packet of the cryptographic handshake protocol MUST fit within
 a 1232 octet QUIC packet payload.  This includes overheads that reduce the space
 available to the cryptographic handshake protocol.
 
-Details of how TLS is integrated with QUIC is provided in more detail in
-{{QUIC-TLS}}.
+The CRYPTO_HS frame can be sent in different packet number spaces.
+CRYPTO_HS frames in each packet number space carry a separate sequence
+of handshake data starting from an offset of 0.
+
+## Example Handshake Flows
+
+Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},
+but we provide some examples here.

Done

In draft-ietf-quic-transport.md:

> +
+## Example Handshake Flows
+
+Details of how TLS is integrated with QUIC are provided in {{QUIC-TLS}},
+but we provide some examples here.
+
+{{tls-1rtt-handshake}} provides an overview of the 1-RTT handshake.
+Each line shows a QUIC packet with the packet type and packet
+number shown first, followed by the contents. So, for instance
+the first packet is of type Initial, with packet number 0, and
+contains a CRYPTO_HS frame carrying the ClientHello.
+
+Note that multiple QUIC packets -- even of different encryption levels
+-- may be coalesced into a single UDP datagram (see
+{{packet-coalesce}}, and so this handshake may consist of anywhere
+from 4 to 9 UDP datagrams.  For instance, the server's first flight

Done.

In draft-ietf-quic-transport.md:

> +to increment from its 0-RTT packets.
+
+~~~~
+Client                                                  Server
+
+Initial[0]: CRYPTO_HS[CH]
+0-RTT[0]: STREAM[0, "..."] ->
+
+                              Initial[0]: CRYPTO_HS[SH] ACK[0]
+                     Handshake[0] CRYPTO_HS[EE, CERT, CV, FIN]
+                          <- 1-RTT[0]: STREAM[1, "..."] ACK[0]
+
+Initial[1]: ACK[0]
+0-RTT[1]: CRYPTO_HS[EOED]
+Handshake[0]: CRYPTO_HS[FIN], ACK[0]
+1-RTT[2]: STREAM[0, "..."], ACK[0] ->

Thanks. This was just a cut and paste error.

In draft-ietf-quic-transport.md:

>  connection state MUST use the Retry packet ({{packet-retry}}).  This packet
-causes a client to reset its transport state and to continue the connection
-attempt with new connection state while maintaining the state of the
-cryptographic handshake.
-
-A server MUST NOT send multiple Retry packets in response to a client handshake
-packet.  Thus, any cryptographic handshake message that is sent MUST fit within
-a single packet.
-
-In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
+causes a client to restart the connection attempt and includes the token in the

I don't know what you mean here.

In draft-ietf-quic-transport.md:

> @@ -1459,68 +1623,69 @@ To send additional data prior to completing the cryptographic handshake, the
 server then needs to validate that the client owns the address that it claims.
 
 Source address validation is therefore performed during the establishment of a
-connection.  TLS provides the tools that support the feature, but basic
-validation is performed by the core transport protocol.
+connection, by the core transport protocol.

Done.

In draft-ietf-quic-transport.md:

> -port), a timestamp, and any other supplementary information the server will need
-to validate the token in the future.
-
-The cryptographic handshake is responsible for enacting validation by sending
-the address validation token to the client.  A legitimate client will include a
-copy of the token when it attempts to continue the handshake.  The cryptographic
-handshake extracts the token then asks QUIC a second time whether the token is
-acceptable.  In response, QUIC can either abort the connection or permit it to
-proceed.
+QUIC uses token-based address validation.  Any time the server wishes
+to validate a client address, it provides the client with a token.  As
+long as the token's authenticity can be checked (see
+{{token-integrity}}) and the client is able to return that token, it
+proves to the server that it received the token.
+
+If QUIC decides to request address validation for the current

Did a slightly more aggressive rewrite.

In draft-ietf-quic-transport.md:

> +long as the token's authenticity can be checked (see
+{{token-integrity}}) and the client is able to return that token, it
+proves to the server that it received the token.
+
+If QUIC decides to request address validation for the current
+handshake, it encodes the token in a Retry packet. The contents of
+this token are consumed by the server that generates the token, so
+there is no need for a single well-defined format.  A token could
+include information about the claimed client address (IP and port), a
+timestamp, and any other supplementary information the server will
+need to validate the token in the future.
+
+The Retry packet is sent to the client and a legitimate client will
+respond with an Initial packet containing the token from the Retry packet
+when it continues the handshake.  In response to receiving the token, a
+QUIC server can either abort the connection or permit it to proceed.

Done.

In draft-ietf-quic-transport.md:

>  
 A connection MAY be accepted without address validation - or with only limited
 validation - but a server SHOULD limit the data it sends toward an unvalidated
 address.  Successful completion of the cryptographic handshake implicitly
 provides proof that the client has received packets from the server.
 
+The client should allow for additional Retry packets being sent in
+response to Initial packets sent containing a token. There are several
+situations in which the server might not be able to use the previously
+generated token to validate the client's address and must send a new
+Retry. A reasonable limit to the number of tries the client allows
+for, before giving up, is 3. That is, the client SHOULD echo the
+address validation token from a new Retry packet up to 3 times. After
+that, it MAY give up on the connection attempt.

Done, but we need to work out the bigger design.

In draft-ietf-quic-transport.md:

>  
 A server MAY provide clients with an address validation token during one
 connection that can be used on a subsequent connection.  Address validation is
 especially important with 0-RTT because a server potentially sends a significant
 amount of data to a client in response to 0-RTT data.
 
-A different type of token is needed when resuming.  Unlike the token that is
-created during a handshake, there might be some time between when the token is
-created and when the token is subsequently used.  Thus, a resumption token
-SHOULD include an expiration time.  It is also unlikely that the client port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client
+with an address validation token that can be used to validate future 0-RTT
+connections.  The client may then use this token to validate future 0-RTT

Done.

In draft-ietf-quic-transport.md:

>  
 A server MAY provide clients with an address validation token during one
 connection that can be used on a subsequent connection.  Address validation is
 especially important with 0-RTT because a server potentially sends a significant
 amount of data to a client in response to 0-RTT data.
 
-A different type of token is needed when resuming.  Unlike the token that is
-created during a handshake, there might be some time between when the token is
-created and when the token is subsequently used.  Thus, a resumption token
-SHOULD include an expiration time.  It is also unlikely that the client port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client
+with an address validation token that can be used to validate future 0-RTT
+connections.  The client may then use this token to validate future 0-RTT
+connections by including it in the Initial packet's header.  The client MUST
+NOT use the token provided in a RETRY for future connections.

Done.

In draft-ietf-quic-transport.md:

>  
 A server MAY provide clients with an address validation token during one
 connection that can be used on a subsequent connection.  Address validation is
 especially important with 0-RTT because a server potentially sends a significant
 amount of data to a client in response to 0-RTT data.
 
-A different type of token is needed when resuming.  Unlike the token that is
-created during a handshake, there might be some time between when the token is
-created and when the token is subsequently used.  Thus, a resumption token
-SHOULD include an expiration time.  It is also unlikely that the client port
-number is the same on two different connections; validating the port is
+The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client
+with an address validation token that can be used to validate future 0-RTT
+connections.  The client may then use this token to validate future 0-RTT
+connections by including it in the Initial packet's header.  The client MUST
+NOT use the token provided in a RETRY for future connections.
+
+Unlike the token that is created for a Retry packet, there might be some time
+between when the token is created and when the token is subsequently used.
+Thus, a resumption token SHOULD include an expiration time.  The server may

MAY

In draft-ietf-quic-transport.md:

> @@ -2676,6 +2832,12 @@ QUIC acknowledgements are irrevocable.  Once acknowledged, a packet remains
 acknowledged, even if it does not appear in a future ACK frame.  This is unlike
 TCP SACKs ({{?RFC2018}}).
 
+It is expected that a sender will reuse the same packet number across different
+packet number spaces.  ACK frames only acknowledge the packet numbers that were
+transmitted by the sender in the same packet number space of the packet that the
+ACK was received in.  This is an important property to allow for separation
+between the different packet number spaces.

Done,

In draft-ietf-quic-transport.md:

> @@ -2839,6 +3001,9 @@ is only sending ACK frames will only receive acknowledgements for its packets
 if the sender includes them in packets with non-ACK frames.  A sender SHOULD
 bundle ACK frames with other frames when possible.
 
+Implementations must be aware of the packet number space of the packet being
+transmitted and only acknowledge packets from that space.

Done.

In draft-ietf-quic-transport.md:

> @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past.
 
 ### ACK Frames and Packet Protection
 
-ACK frames that acknowledge protected packets MUST be carried in a packet that
-has an equivalent or greater level of packet protection.
-
-Packets that are protected with 1-RTT keys MUST be acknowledged in packets that
-are also protected with 1-RTT keys.
-
-A packet that is not protected and claims to acknowledge a packet number that
-was sent with packet protection is not valid.  An unprotected packet that
-carries acknowledgments for protected packets MUST be discarded in its entirety.
+ACK frames MUST only be carried in a packet that has the same packet

It actually is an interoperability requirement, because if you inadvertantly cross-ACK, you will have failures.

In draft-ietf-quic-transport.md:

> -messages in the next unprotected packet that it sends, unless it is able to
-acknowledge those packets in later packets protected by 1-RTT keys.  At the
-completion of the cryptographic handshake, both peers send unprotected packets
-containing cryptographic handshake messages followed by packets protected by
-1-RTT keys. An endpoint SHOULD acknowledge the unprotected packets that complete
-the cryptographic handshake in a protected packet, because its peer is
-guaranteed to have access to 1-RTT packet protection keys.
-
-For instance, a server acknowledges a TLS ClientHello in the packet that carries
-the TLS ServerHello; similarly, a client can acknowledge a TLS HelloRetryRequest
-in the packet containing a second TLS ClientHello.  The complete set of server
-handshake messages (TLS ServerHello through to Finished) might be acknowledged
-by a client in protected packets, because it is certain that the server is able
-to decipher the packet.
-
+Implementations SHOULD aggressively ACK packets containing CRYPTO_HS frames.

Done.

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 
 
+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to

Done.

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 
 
+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to
+send in a the header of an Initial packet for a future 0-RTT connection.

Done.

In draft-ietf-quic-transport.md:

> @@ -2929,6 +3070,34 @@ PATH_CHALLENGE frame previously sent by the endpoint, the endpoint MAY generate
 a connection error of type UNSOLICITED_PATH_RESPONSE.
 
 
+## NEW_TOKEN frame {#frame-new-token}
+
+An server sends a NEW_TOKEN frame (type=0x21) to provide the client a token to
+send in a the header of an Initial packet for a future 0-RTT connection.
+
+The NEW_TOKEN frame is as follows:
+
+~~~
+ 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|        Token Length (i)  ...

Done.

In draft-ietf-quic-transport.md:

> +
+Offset:
+
+: A variable-length integer specifying the byte offset in the stream for the
+  data in this CRYPTO_HS frame.
+
+Length:
+
+: A variable-length integer specifying the length of the Crypto Data field in
+  this CRYPTO_HS frame.
+
+Crypto Data:
+
+: The cryptographic message data.
+
+There is a separate flow of cryptographic handshake data in each

Added above.

In draft-ietf-quic-transport.md:

> +: A variable-length integer specifying the length of the Crypto Data field in
+  this CRYPTO_HS frame.
+
+Crypto Data:
+
+: The cryptographic message data.
+
+There is a separate flow of cryptographic handshake data in each
+encryption level, each of which starts at an offset of 0. This implies
+that each encryption level is treated as a separate CRYPTO_HS stream
+of data.
+
+Unlike STREAM frames, which include a Stream ID indicating to which
+stream the data belongs, the CRYPTO_HS frame carries data for a single
+stream per encryption level. The stream does not have an explicit
+end, so CRYPTO_HS frames do not have a FIN bit.

Hence the text above that forbids stuff extending past the end.

In draft-ietf-quic-transport.md:

> +that each encryption level is treated as a separate CRYPTO_HS stream
+of data.
+
+Unlike STREAM frames, which include a Stream ID indicating to which
+stream the data belongs, the CRYPTO_HS frame carries data for a single
+stream per encryption level. The stream does not have an explicit
+end, so CRYPTO_HS frames do not have a FIN bit.
+
+
+## CRYPTO_CLOSE Frame {#frame-crypto-close}
+
+The CRYPTO_CLOSE frame (type=0x20) is used to indicate connection failures
+caused by the crypto handshake. It uses the same format as the
+CONNECTION_CLOSE frame ({{frame-connection-close}}), except that the
+error codes are specific to the crypto protocol in use. For TLS 1.3,
+the error code is simply the one-byte TLS alert number.

Sent as left-padded for now. I know MT wants to argue about this whole structure.

In draft-ietf-quic-transport.md:

> @@ -3064,6 +3293,10 @@ been lost.  In general, information is sent again when a packet containing that
 information is determined to be lost and sending ceases when a packet
 containing that information is acknowledged.
 
+* Data sent in CRYPTO_HS frames are retransmitted according to the rules in
+  {{QUIC-RECOVERY}}, until either all data has been ACKed or the crypto state

Done.

In draft-ietf-quic-transport.md:

> @@ -3299,8 +3532,7 @@ The two type bits from a Stream ID therefore identify streams as summarized in
 | 0x3      | Server-Initiated, Unidirectional |
 {: #stream-id-types title="Stream ID Types"}
 
-Stream ID 0 (0x0) is a client-initiated, bidirectional stream that is used for
-the cryptographic handshake.  Stream 0 MUST NOT be used for application data.
+The first bi-directional stream opened by the client is stream 0.

Left as-is.

In draft-ietf-quic-transport.md:

> @@ -3893,6 +4102,14 @@ errors is not mandatory, but only because requiring that an endpoint generate
 these errors also means that the endpoint needs to maintain the final offset
 state for closed streams, which could mean a significant state commitment.
 
+## Flow control of CRYPTO_HS data {#flow-control-crypto}
+
+Data sent in CRYPTO_HS frames is not flow controlled in the same way as STREAM
+frames.  QUIC relies on the cryptographic protocol implementation to avoid
+excessive buffering of data, see {{QUIC-TLS}}.  The implementation SHOULD
+provide an interface to QUIC to tell it about its buffering limits so that there
+is no excessive buffering at multiple layers.

Done.

In draft-ietf-quic-transport.md:

> @@ -4313,6 +4531,15 @@ the range from 0xFE00 to 0xFFFF.
 
 Issue and pull request numbers are listed with a leading octothorp.
 
+## Since draft-ietf-quic-transport-12
+
+- Enable server to transition connections to a preferred address (#560,#1251).
+- No more stream 0.

Done,

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

----==_mimepart_5b2cf8979905f_24772aed49cc6f58898a8-- From nobody Fri Jun 22 08:25:15 2018 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 63A94130EC6 for ; Fri, 22 Jun 2018 08:25:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 72wNVy3DTqvs for ; Fri, 22 Jun 2018 08:25:06 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E4617130E9B for ; Fri, 22 Jun 2018 08:25:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529681105; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=8G1KSEttafJcwqxCjDP2VCinGRwad3qmktG/V0do580=; b=h/McZX2xOscEyupegM2NkKWdmKhaWuK4mL8UC4j2W0WknTDLVfXxfu4ICrED5bGt+O25wAcb lGIDU2KwH7cCu7aT/ET8Do0BnE0fMT3NB/Su1aEFi+v2TlrcW6r//TL5b5YbixmzbwvOsGTD w7WePnxV7LBvPx+KVoTgQ2HseQs= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b2d14d0.7ff0581fe180-smtp-out-n02; Fri, 22 Jun 2018 15:25:04 -0000 (UTC) Date: Fri, 22 Jun 2018 08:25:03 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2d14cf8cf5f_57382ace87667c10689ce@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] bf0401: Decoder MAY error on an incorrect largest referenc... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d14cf8cb42_57382ace87667c1068890"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 15:25:12 -0000 ----==_mimepart_5b2d14cf8cb42_57382ace87667c1068890 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/lr-too-big Home: https://github.com/quicwg/base-drafts Commit: bf04010d3b1320fb19af571b649231d58e9e84bf https://github.com/quicwg/base-drafts/commit/bf04010d3b1320fb19af571b649231d58e9e84bf Author: Alan Frindell Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Decoder MAY error on an incorrect largest reference Fixes #1404 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d14cf8cb42_57382ace87667c1068890-- From nobody Fri Jun 22 08:26:18 2018 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 34C4F130E9A for ; Fri, 22 Jun 2018 08:26:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 S-ddWY832_w8 for ; Fri, 22 Jun 2018 08:26:14 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 EDD6B130E99 for ; Fri, 22 Jun 2018 08:26:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529681173; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=a1/bal5TCFk+F4MwGit9vSo2vEpiCvihsax1sohyBW8=; b=ajyZRhvk1ee4amnen9a79HnRsQSaLfBqjEQquiwh2URVI8plqzXveEVvLuma+OunG3oP194A uvyCCCeCm3156lGaeKT+lrVrRjkrFy8cuL6iNClnUlt1h44RSDqQx5wYlNE6AtLCEtVLQ5iQ 4kGjp8EVDP4rgZVe3y7Tv9AtyZc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2d1515.7f583d0970f0-smtp-out-n02; Fri, 22 Jun 2018 15:26:13 -0000 (UTC) Date: Fri, 22 Jun 2018 08:26:12 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2d15142a820_de72ac9dcf75c08161fd@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] a191ec: Fix bug in QPACK sample code Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d15142a33e_de72ac9dcf75c081601a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 15:26:16 -0000 ----==_mimepart_5b2d15142a33e_de72ac9dcf75c081601a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sample-bug Home: https://github.com/quicwg/base-drafts Commit: a191ec431cdd8b045bc7e248c165a854b7a64fe1 https://github.com/quicwg/base-drafts/commit/a191ec431cdd8b045bc7e248c165a854b7a64fe1 Author: Alan Frindell Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix bug in QPACK sample code Fixes #1455 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d15142a33e_de72ac9dcf75c081601a-- From nobody Fri Jun 22 08:27:00 2018 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 EF660130E99 for ; Fri, 22 Jun 2018 08:26:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qx4yFYPn7PeN for ; Fri, 22 Jun 2018 08:26:57 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3567130E96 for ; Fri, 22 Jun 2018 08:26:56 -0700 (PDT) Date: Fri, 22 Jun 2018 08:26:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529681215; bh=K7LaL77vQiMTkTNGP9PxmKhvvxLPd9UXVR6D1LwbW20=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=NGj3D2iulmhqOCnT0XV+0O3LtcgiQH0h1LFurNEGlqULgirDHnxmsQt06MZxTPwUG LC8g/GNHfJAh7LwkFL7msxHiVLkSBmd4qPZan5H0ecgHwHV6KDKp9Wchj2kd4h5GGm +CINcYpt1NrLOnp8+syYzPvtiPQjpPSCQp4DcWb8= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Decoder MAY error on an incorrect largest reference (#1469) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d153fe9ddd_57f3fe5864acf8014965c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 15:26:59 -0000 ----==_mimepart_5b2d153fe9ddd_57f3fe5864acf8014965c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1404 You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1469 -- Commit Summary -- * Decoder MAY error on an incorrect largest reference -- File Changes -- M draft-ietf-quic-qpack.md (3) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1469.patch https://github.com/quicwg/base-drafts/pull/1469.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/1469 ----==_mimepart_5b2d153fe9ddd_57f3fe5864acf8014965c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1404

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

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

Commit Summary

  • Decoder MAY error on an incorrect largest reference

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 mute the thread.

----==_mimepart_5b2d153fe9ddd_57f3fe5864acf8014965c-- From nobody Fri Jun 22 08:27:46 2018 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 836FE130E98 for ; Fri, 22 Jun 2018 08:27:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 kmlmn8TZ5Cf8 for ; Fri, 22 Jun 2018 08:27:32 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 4C0F8130EC1 for ; Fri, 22 Jun 2018 08:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=CwCdLeGPey6tD/qiS2anMhW+1+E=; b=dV/HAbjSmEfHW3rr cRg/xhKVGWmhRhTBcOZecEPixuiBAHI1Exc3aeCQKQm+vA+Eb1sVSbJ9EcFzwzMl +Fcd+3tmbIBOFPbO6N+J/wJ0OwCcZ/xNh3byMvz5pYorebiF6DKYvMDKsbVOiC4s a4mrQXfAKmAzPttSX+tvQiZZTD8= Received: by filter0432p1iad2.sendgrid.net with SMTP id filter0432p1iad2-20136-5B2D1563-5 2018-06-22 15:27:31.068510973 +0000 UTC Received: from github-lowworker-baaab27.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id EI5RtcDTRJGZFNK8yqaOzQ for ; Fri, 22 Jun 2018 15:27:31.005 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-baaab27.cp1-iad.github.net (Postfix) with ESMTP id F2F19802FD for ; Fri, 22 Jun 2018 08:27:30 -0700 (PDT) Date: Fri, 22 Jun 2018 15:27:31 +0000 (UTC) From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Fix bug in QPACK sample code (#1470) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d1562f0ae9_19bc2aac002c2f50142028"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3AZpIQ3VnR6sHyVHYVZbggwBVQ68Ecjuf4I0 gQzDRyNZVCVDA0TG/+y30waTo1/ofHXh485i+fWc4W9Pxx83dacV8HfiECO6O9F533re/DDiDE5b5/ BL7V3CJptykGUwLnbi4GChkVn6lqh0x3Nrly1e+0St5OfzU5Tr6s/vw4Pw== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 15:27:41 -0000 ----==_mimepart_5b2d1562f0ae9_19bc2aac002c2f50142028 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1455 You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1470 -- Commit Summary -- * Fix bug in QPACK sample code -- File Changes -- M draft-ietf-quic-qpack.md (8) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1470.patch https://github.com/quicwg/base-drafts/pull/1470.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/1470 ----==_mimepart_5b2d1562f0ae9_19bc2aac002c2f50142028 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1455

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

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

Commit Summary

  • Fix bug in QPACK sample code

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 mute the thread.

----==_mimepart_5b2d1562f0ae9_19bc2aac002c2f50142028-- From nobody Fri Jun 22 08:43:38 2018 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 B9BF0130EA2 for ; Fri, 22 Jun 2018 08:43:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 SYBMQ-1yhxMu for ; Fri, 22 Jun 2018 08:43:34 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2504130E96 for ; Fri, 22 Jun 2018 08:43:33 -0700 (PDT) Date: Fri, 22 Jun 2018 08:43:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529682213; bh=cU4hsLKPWEMXu3OX81a87ksK0hIdwuNpEHi/jWIeiaM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0GATn2KbPLls6csYF80443diXJXaoSbx12PCwLZ34usQ+rAo2dfRj0zi9V+4USapE GpcUFDnbo4yrdXkomNwZpnD/XmhXR8uaYnsd2D5VmvhG8bTSKyjUjZlRHWjGqFB9T2 hxT7ZJSYa52PFuFCoKGXaOKTgysVm8nQ58SFZ7RQ= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] QPACK instruction code points are inconsistent (#1471) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d19254e147_6db22af130238f6018012b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 15:43:36 -0000 ----==_mimepart_5b2d19254e147_6db22af130238f6018012b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit HPACK/QPACK can encode N different instructions in N-1 bits. Both HPACK and the QPACK encoder stream use the same style fore code points - each instruction has either one or zero '1' bits (eg: 1, 01, 001, 0001, 0000). The QPACK decoder stream and request/push streams however use (0, 10, 11) and (1, 00, 011, 0100, 0101), each of which have instructions with more than one '1'. The logic to decode the instruction is slightly simpler when using the HPACK form, eg: ``` if byte & shortest_instruction: ... else if byte & next_shortest_instruction: ... else: # it's the all-zero instruction ... ``` This logic doesn't work on the other two streams right now, you need to mask and check for equality. -- 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/1471 ----==_mimepart_5b2d19254e147_6db22af130238f6018012b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

HPACK/QPACK can encode N different instructions in N-1 bits. Both HPACK and the QPACK encoder stream use the same style fore code points - each instruction has either one or zero '1' bits (eg: 1, 01, 001, 0001, 0000). The QPACK decoder stream and request/push streams however use (0, 10, 11) and (1, 00, 011, 0100, 0101), each of which have instructions with more than one '1'. The logic to decode the instruction is slightly simpler when using the HPACK form, eg:

if byte & shortest_instruction:
  ...
else if byte & next_shortest_instruction:
  ...
else:  # it's the all-zero instruction
  ...

This logic doesn't work on the other two streams right now, you need to mask and check for equality.

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

----==_mimepart_5b2d19254e147_6db22af130238f6018012b-- From nobody Fri Jun 22 10:05:49 2018 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 72912130EB0 for ; Fri, 22 Jun 2018 10:05:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 WJBcoM-qlfKx for ; Fri, 22 Jun 2018 10:05:46 -0700 (PDT) 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 37D74130EAF for ; Fri, 22 Jun 2018 10:05:46 -0700 (PDT) Date: Fri, 22 Jun 2018 10:05:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529687145; bh=Gc+VGudyarLYvyySmIoRkmH0vKi/eZoJ5f3cXVpxypU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oPceHnIZ467quYFeFN6wmhX3WnamAMmSSsj9W1s0KtnhlxrOHH5/kdJ2TqqDRFZMP lCE5/bIjjF+S142AaqEOJY8lPUmK5kvSvBc8YnaA8vR6QvnHUahLiz7rdjlTkmyxv8 qc+2NBufDkmebKeMSz4YFlLOYRtK4UokqMj2mVaE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d2c694fa51_1b8fd3fb4c8bb0f7810296a"; 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.26 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: Fri, 22 Jun 2018 17:05:48 -0000 ----==_mimepart_5b2d2c694fa51_1b8fd3fb4c8bb0f7810296a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This doesn't solve the case where one side is using zero-length connection IDs, though. Unless we permit sending NEW_CONNECTION_ID with sequence numbers and zero length, I suppose. I'm not sure I prefer that to a new frame type. -- 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/1468#issuecomment-399512932 ----==_mimepart_5b2d2c694fa51_1b8fd3fb4c8bb0f7810296a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This doesn't solve the case where one side is using zero-length connection IDs, though. Unless we permit sending NEW_CONNECTION_ID with sequence numbers and zero length, I suppose. I'm not sure I prefer that to a new frame type.

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

----==_mimepart_5b2d2c694fa51_1b8fd3fb4c8bb0f7810296a-- From nobody Fri Jun 22 10:27:00 2018 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 AE3BB130EB3 for ; Fri, 22 Jun 2018 10:26:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1hBpK_5_QQ9a for ; Fri, 22 Jun 2018 10:26:57 -0700 (PDT) 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 074C8130E10 for ; Fri, 22 Jun 2018 10:26:57 -0700 (PDT) Date: Fri, 22 Jun 2018 10:26:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529688416; bh=enOCHeAihGjU4h6CRzwnCqHNR0WiQk7KLFA7NZkned4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VUQe58Qfl1xZjyeNr9SBV/UjPF5W7VO+kcFgIcJYchJe1/ZC55sX1nyfm3GiA35X1 MGKubsNOkGLnofk6xhznkyIPTLI1N0ppKkSZCVT1iiffJCg8m3SIaJqVaTP31lxULY 3fLsXI0iYZXy+6MXRgO1cngYdoIhjfCO0PQyb7xY= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d316022b15_67802aed6f96cf5821898"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Fri, 22 Jun 2018 17:26:59 -0000 ----==_mimepart_5b2d316022b15_67802aed6f96cf5821898 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > @@ -1656,7 +1664,12 @@ network. This section describes the process by which an endpoint migrates to a new address. An endpoint MUST NOT initiate connection migration before the handshake is -finished and the endpoint has 1-RTT keys. +finished and the endpoint has 1-RTT keys. An endpoint also MUST NOT initiate +connection migration if the peer sent the `disable_migration` transport +parameter during the handshake. An endpoint which has sent this transport +parameter, but detects that a peer has nonetheless migrated to a different +network MAY treat this as a connection error of type INVALID_MIGRATION. +However, note that not all changes of peer address are intentional migrations. I really think we should mention NAT rebinding here and how `disable_migration` doesn't mean the endpoint doesn't need to handle NAT rebinding. -- 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/1447#pullrequestreview-131279954 ----==_mimepart_5b2d316022b15_67802aed6f96cf5821898 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1656,7 +1664,12 @@ network.  This section describes the process by which an endpoint migrates to a
 new address.
 
 An endpoint MUST NOT initiate connection migration before the handshake is
-finished and the endpoint has 1-RTT keys.
+finished and the endpoint has 1-RTT keys.  An endpoint also MUST NOT initiate
+connection migration if the peer sent the `disable_migration` transport
+parameter during the handshake.  An endpoint which has sent this transport
+parameter, but detects that a peer has nonetheless migrated to a different
+network MAY treat this as a connection error of type INVALID_MIGRATION.
+However, note that not all changes of peer address are intentional migrations.

I really think we should mention NAT rebinding here and how disable_migration doesn't mean the endpoint doesn't need to handle NAT rebinding.

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

----==_mimepart_5b2d316022b15_67802aed6f96cf5821898-- From nobody Fri Jun 22 10:44:55 2018 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 94922130EB0 for ; Fri, 22 Jun 2018 10:44:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Rpj0rQ8xsZgL for ; Fri, 22 Jun 2018 10:44:49 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBA18130E10 for ; Fri, 22 Jun 2018 10:44:48 -0700 (PDT) Date: Fri, 22 Jun 2018 10:44:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529689488; bh=9cmaUam5c8o9crBFTjsliRk+ZdS6v+sYQOqfX1tvZa4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dJfZU5kEbxoxAyhjmb95JUJ5tiF+vp3pw3rxHaok+eyZI1v2MqIy37phpaay95RJZ YKOxv2sf+bikbDMNczFfAX4ZjJIpz9SBecZCYibKqM2hk83rs8RF29yxlqQVfR2C+H tUL0gzj50W95SapEalWIEjlvRd3VBP3YlOx6rw5g= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d358ff3a71_249d2af91c92af503282e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 22 Jun 2018 17:44:53 -0000 ----==_mimepart_5b2d358ff3a71_249d2af91c92af503282e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit erickinnear commented on this pull request. > @@ -1656,7 +1664,12 @@ network. This section describes the process by which an endpoint migrates to a new address. An endpoint MUST NOT initiate connection migration before the handshake is -finished and the endpoint has 1-RTT keys. +finished and the endpoint has 1-RTT keys. An endpoint also MUST NOT initiate +connection migration if the peer sent the `disable_migration` transport +parameter during the handshake. An endpoint which has sent this transport +parameter, but detects that a peer has nonetheless migrated to a different +network MAY treat this as a connection error of type INVALID_MIGRATION. +However, note that not all changes of peer address are intentional migrations. Good point! If you send the parameter, you still need to implement a response to path challenge frames, for example. I'll comment on the issue with more thoughts, but the text should at least mention that you still need to be prepared for that to happen. -- 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/1447#discussion_r197520017 ----==_mimepart_5b2d358ff3a71_249d2af91c92af503282e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@erickinnear commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -1656,7 +1664,12 @@ network.  This section describes the process by which an endpoint migrates to a
 new address.
 
 An endpoint MUST NOT initiate connection migration before the handshake is
-finished and the endpoint has 1-RTT keys.
+finished and the endpoint has 1-RTT keys.  An endpoint also MUST NOT initiate
+connection migration if the peer sent the `disable_migration` transport
+parameter during the handshake.  An endpoint which has sent this transport
+parameter, but detects that a peer has nonetheless migrated to a different
+network MAY treat this as a connection error of type INVALID_MIGRATION.
+However, note that not all changes of peer address are intentional migrations.

Good point! If you send the parameter, you still need to implement a response to path challenge frames, for example. I'll comment on the issue with more thoughts, but the text should at least mention that you still need to be prepared for that to happen.

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

----==_mimepart_5b2d358ff3a71_249d2af91c92af503282e7-- From nobody Fri Jun 22 10:51:09 2018 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 61435130EBA for ; Fri, 22 Jun 2018 10:51:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bLy2dKg-QOf2 for ; Fri, 22 Jun 2018 10:51:05 -0700 (PDT) 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 B0A16130EB9 for ; Fri, 22 Jun 2018 10:51:05 -0700 (PDT) Date: Fri, 22 Jun 2018 10:51:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529689864; bh=ihFwqoyBFISh6v6jGjCG3afI90aKAQKRNQgObP06m7E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R+2uYLvKH1d36Oz+3dnU3nTK0l7ceNZrVzyoADIJaB1NymMggxEA9SKhucqQfcvoQ L3WZKrAhE063tr1GxCVBCRmA0u+XagZozBgFRhogVO2lTGzYEPMRgziHlHuub5jugb 4y8pqTfUr0cEkmG9GETevtA5VLIcU/Pt8Ooy6z2Q= From: erickinnear Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d3708da547_3bac2aad9bc3af501270dd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: erickinnear 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.26 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: Fri, 22 Jun 2018 17:51:08 -0000 ----==_mimepart_5b2d3708da547_3bac2aad9bc3af501270dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Another thought, spurred by Rui's comment on the PR: Sending this TP means that the other end doesn't get to *knowingly* initiate migration. However, both sides (or the client since we're currently not direction-agnostic) still need to handle path challenge frames and generate path response frames. If this is just for use in datacenter environments, then there isn't really anything gained by having a TP, just don't do migration. However, I do still see the value for cases, especially until load balancers can cope with connection IDs, where you'd want to indicate that a client on the public internet shouldn't perform migration. Of course, even in that case, you still have to implement all the code on the server itself to deal with the observed client endpoint changing. -- 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/1271#issuecomment-399524870 ----==_mimepart_5b2d3708da547_3bac2aad9bc3af501270dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Another thought, spurred by Rui's comment on the PR:

Sending this TP means that the other end doesn't get to knowingly<= /em> initiate migration. However, both sides (or the client since we're c= urrently not direction-agnostic) still need to handle path challenge fram= es and generate path response frames.

If this is just for use in datacenter environments, then there isn't r= eally anything gained by having a TP, just don't do migration.
However, I do still see the value for cases, especially until load balanc= ers can cope with connection IDs, where you'd want to indicate that a cli= ent on the public internet shouldn't perform migration.

Of course, even in that case, you still have to implement all the code= on the server itself to deal with the observed client endpoint changing.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b2d3708da547_3bac2aad9bc3af501270dd-- From nobody Fri Jun 22 10:56:05 2018 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 8E027130EBD for ; Fri, 22 Jun 2018 10:56:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 ZjLwKXIvJRHE for ; Fri, 22 Jun 2018 10:56:00 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 61C89130EBB for ; Fri, 22 Jun 2018 10:55:54 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529690153; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=xpyKdR1eq0c223ORTUW5yW9zW6QoNqzkDEPNFffg+Rk=; b=N3hytXkBhnH/eQM37LH5zaycQ9FMFpm6FfPDlRr0e030uuWLymtnp22B0GXCbas34wTGlWlk p8gnxnHEnAZQzvIg82t3Hu7wdQ4l0FiEOHWhs3lu8OcxDTUejmih3iD+ENIINwPDxDQm5oNd hfij/MUqy5SkyOQEB3EVg7hQif8= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b2d3829.7fa286daac60-smtp-out-n02; Fri, 22 Jun 2018 17:55:53 -0000 (UTC) Date: Fri, 22 Jun 2018 10:55:53 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2d382989750_dfd2ae2cd5f9c10796d8@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ef8abf: New CID section Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d382989362_dfd2ae2cd5f9c107953"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 17:56:02 -0000 ----==_mimepart_5b2d382989362_dfd2ae2cd5f9c107953 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: ef8abfb7393adb6a050d46e26ed23c48da12e083 https://github.com/quicwg/base-drafts/commit/ef8abfb7393adb6a050d46e26ed23c48da12e083 Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- New CID section **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d382989362_dfd2ae2cd5f9c107953-- From nobody Fri Jun 22 10:56:10 2018 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 21871130EBB for ; Fri, 22 Jun 2018 10:56:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OcLsnGbL-PXs for ; Fri, 22 Jun 2018 10:56:00 -0700 (PDT) Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CFFA130EBC for ; Fri, 22 Jun 2018 10:55:58 -0700 (PDT) Date: Fri, 22 Jun 2018 10:55:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529690157; bh=0pHorYGcpucrCmYrl+tPvkbRCmfvTtng4hTCarT7h80=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=peBfjsUh9cl49J2eEYDeJK4BghJgcZgbqfmODb0hL+ZJ1Y8AhZa3Tk8ZDlE8Y+UAT 6HutFZAVZQLWR1pKC+WZbcrPTVgMSZNuLxkigLkRGbW11CqCyVavBAXczK/lISnwzx a9SjO8E6I738pl6lJ62ncJlyK5e2PpgzQm2IehPQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d382db3bc1_4dcb2aad3bd46f581894e8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 22 Jun 2018 17:56:02 -0000 ----==_mimepart_5b2d382db3bc1_4dcb2aad3bd46f581894e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. ef8abfb New CID section -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1465/files/0d675544aaa5263bbfa2c0a3e1879e18dc71200e..ef8abfb7393adb6a050d46e26ed23c48da12e083 ----==_mimepart_5b2d382db3bc1_4dcb2aad3bd46f581894e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2d382db3bc1_4dcb2aad3bd46f581894e8-- From nobody Fri Jun 22 10:56:33 2018 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 302E8130EB9 for ; Fri, 22 Jun 2018 10:56:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HWIyuDSF02CB for ; Fri, 22 Jun 2018 10:56:29 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D8C0130E10 for ; Fri, 22 Jun 2018 10:56:29 -0700 (PDT) Date: Fri, 22 Jun 2018 10:56:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529690188; bh=iJ8fNBSgYvT+gim7ykgvgsAlU4pnwevzgrVdKYkh2HQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GU7zffYNN6YmMY68h/n4xk64oS010R0UdRl2L/g5qVUHpaW9RhzZzV+c0+JxTLME3 1A/g423jrVill5K6D7iIwomH37co8+Swj3xsZNevOwaxlOo7D13NvxOL74QhWsxhm1 r0+mKuy0rSZEKhdnc/fpvOQt6VglPxiOPhmhleN0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d384ca1687_1efb3fef97686f842335c0"; 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.26 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: Fri, 22 Jun 2018 17:56:32 -0000 ----==_mimepart_5b2d384ca1687_1efb3fef97686f842335c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Moved to a separate section. Doesn't actually change the line count any, but hopefully it's clearer. -- 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/1465#issuecomment-399526404 ----==_mimepart_5b2d384ca1687_1efb3fef97686f842335c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Moved to a separate section. Doesn't actually change the line count any, but hopefully it's clearer.

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

----==_mimepart_5b2d384ca1687_1efb3fef97686f842335c0-- From nobody Fri Jun 22 11:03:33 2018 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 72F5D130EDD for ; Fri, 22 Jun 2018 11:03:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 CqlkOCv1z_Ss for ; Fri, 22 Jun 2018 11:03:18 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A943F130EF0 for ; Fri, 22 Jun 2018 11:03:18 -0700 (PDT) Date: Fri, 22 Jun 2018 11:03:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529690597; bh=phuBNy+oVd+O773+KrbpmdXHkt6pQGy4JQNcqytg6pM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dLzJoOxQDK01/L2sTtVbI06ciF7kgBlg5ViGlP0B7VlDLUqywcWXxig2gJUcLOrpw ejOCWw+ZBvbuw+Lj+Bu0ayCwBO5vOqGlopmyUw4fFetJOx1Ij/pO0UUVQofsjky0LG 2L9X0ZLA0TPU5Scp96F7uvhcbS6WN9hWTpB3UFsk= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d39e5e8a4f_47602b0a39140f501372e7"; 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.26 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: Fri, 22 Jun 2018 18:03:32 -0000 ----==_mimepart_5b2d39e5e8a4f_47602b0a39140f501372e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, What if we just eliminate this statement and let it be implementation-local? The new text I added to the CID section says that "The series of connection IDs issued by an endpoint is ordered, with the final connection ID selected during the handshake coming first." We could also fix this by removing the CID from SPA and simply saying that the server needs to send the client a CID it can use for the probe pretty promptly if it wants the client to do so. -- 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/1465#discussion_r197525078 ----==_mimepart_5b2d39e5e8a4f_47602b0a39140f501372e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

What if we just eliminate this statement and let it be implementation-local? The new text I added to the CID section says that "The series of
connection IDs issued by an endpoint is ordered, with the final connection ID
selected during the handshake coming first."

We could also fix this by removing the CID from SPA and simply saying that the server needs to send the client a CID it can use for the probe pretty promptly if it wants the client to do so.

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

----==_mimepart_5b2d39e5e8a4f_47602b0a39140f501372e7-- From nobody Fri Jun 22 11:21:16 2018 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 92F5B130EC6 for ; Fri, 22 Jun 2018 11:21:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 GSpE6cLrVVcw for ; Fri, 22 Jun 2018 11:21:10 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 CFCA3130ECC for ; Fri, 22 Jun 2018 11:21:09 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529691669; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=D7qnAWw11GYG30z3zKUvlXrmxmGsjLb2Lbt7P7TqPfA=; b=W3T23JrM/yxJb07qazDSgTyM9+lo2OOLY3qCDmCN0/cT0KFVB1BesbQgRl0EFybCRmYacrRa QgkKxLKA0w/EmodvQ3XoUDxQB1I1BlKJ4o7jmkEfvDEHhupmN9pGjj3yP1tfHOXzlvj2Vmb0 hxNsjbppGHXvQz52dcaVS3zngM4= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2d3e15.7f273becc570-smtp-out-n01; Fri, 22 Jun 2018 18:21:09 -0000 (UTC) Date: Fri, 22 Jun 2018 11:21:08 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2d3e141c5df_6e2c2ac85ed37c0491931@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b221b7: Fix bug in QPACK sample code Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d3e141c2a9_6e2c2ac85ed37c049184c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 18:21:13 -0000 ----==_mimepart_5b2d3e141c2a9_6e2c2ac85ed37c049184c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: b221b796fd016315f74c9aa22e8dc87754b375e2 https://github.com/quicwg/base-drafts/commit/b221b796fd016315f74c9aa22e8dc87754b375e2 Author: Alan Frindell Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix bug in QPACK sample code Fixes #1455 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d3e141c2a9_6e2c2ac85ed37c049184c-- From nobody Fri Jun 22 11:21:26 2018 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 E8836130EC1 for ; Fri, 22 Jun 2018 11:21:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 k6ULs8kB9qEc for ; Fri, 22 Jun 2018 11:21:15 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41FF1130ED7 for ; Fri, 22 Jun 2018 11:21:12 -0700 (PDT) Date: Fri, 22 Jun 2018 11:21:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529691671; bh=C1BZrG2uNeFKAyA20GsaCF6UdzeRAGKtqpepMyfv/KA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=e6a/WK+D4YTV/C5ezB+9lYoUCYqqDG3ljX8Wfze5C9Vu0Mrb14bbYhd+jTjDRYTss OHvNhQt6yvaJELtavnrEq+Vr3cr6YLaGjysu1Dq+SkCGnKcyo9ueZ0QtLmib84yFD1 Qq0p11qdoOH0Lmpbiw+Yg1THp/4+jXggyRLcWGjs= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fix bug in QPACK sample code (#1470) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d3e1763412_51002ae9fe616f58151082"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 18:21:20 -0000 ----==_mimepart_5b2d3e1763412_51002ae9fe616f58151082 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1470. -- 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/1470#event-1696539579 ----==_mimepart_5b2d3e1763412_51002ae9fe616f58151082 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1470.

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

----==_mimepart_5b2d3e1763412_51002ae9fe616f58151082-- From nobody Fri Jun 22 11:21:32 2018 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 975F9130EC0 for ; Fri, 22 Jun 2018 11:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 ExYUffEUIzKC for ; Fri, 22 Jun 2018 11:21:18 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 11C9E130EF6 for ; Fri, 22 Jun 2018 11:21:12 -0700 (PDT) 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=qs7bG0TilJn+hmH/7r+MNP524XY=; b=MHtJo93CIcqEkq7M mWZrxExJ4xM9cQiJe5sxrGeSorFc62YrA20s+qIa3HaIXKUYnXI+yq/wl7sQntXL TDMJvNnu0R1Swa+t2jzYKST+AvLncImVvEqqdgY7tx5fxBZQKIfoBG2pJV8DePw5 aKKW4wMvELMqSuMcztxnZkz8B7U= Received: by filter0276p1iad2.sendgrid.net with SMTP id filter0276p1iad2-23608-5B2D3E17-14 2018-06-22 18:21:11.718266154 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id JqWN_ZdgRkKSl-0LgKQung for ; Fri, 22 Jun 2018 18:21:11.694 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id A6CEB80036 for ; Fri, 22 Jun 2018 11:21:11 -0700 (PDT) Date: Fri, 22 Jun 2018 18:21:11 +0000 (UTC) From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK sample encoder bug (#1455) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d3e17a4f2a_50c02ac4b021ef5497766"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2JyegMHU5E2FKXJIK1gLp9FRvDPThIDgJCdv wJLD5fnCnhuypKUbOr+YS15IzYvtB5M9tWwnJvoMoRMPwYPaQzuBXdgJiZ6oFvdU72gD5xxsrWBi2V AB04J2SGx5c04e9ch0IW+1lF2Pu78uEcLpdlBuzBHzZmNvzS6CitKriDzg== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 18:21:26 -0000 ----==_mimepart_5b2d3e17a4f2a_50c02ac4b021ef5497766 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1455 via #1470. -- 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/1455#event-1696539581 ----==_mimepart_5b2d3e17a4f2a_50c02ac4b021ef5497766 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1455 via #1470.

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

----==_mimepart_5b2d3e17a4f2a_50c02ac4b021ef5497766-- From nobody Fri Jun 22 11:33:26 2018 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 F002A130EC1 for ; Fri, 22 Jun 2018 11:33:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 Weq3goSraiV5 for ; Fri, 22 Jun 2018 11:33:22 -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 43166130EAF for ; Fri, 22 Jun 2018 11:33:22 -0700 (PDT) Date: Fri, 22 Jun 2018 11:33:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529692401; bh=8hGoGXLa/c0YT+tfKshCHggY5OCFKSUO+wA5xJmTfDM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fw7o/gbRhxLuGO2viJ+aeHpP99FcaAuwXPXK6g8bC6rCJ0swUk5yC+6mKLLSWQkHj XaNdmJB8sIEDmVdbaUKtfwoNXm4YCTyoogFkKquwUGHhgwTrXWMGVoJzfKD7LUwVmn WSf4+O+JTlKWMXrKN3KqpaJS47n+dQrOL+PSOOtE= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Decoder MAY error on an incorrect largest reference (#1469) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d40f132550_68852b1975166f5c35332e"; 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.26 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: Fri, 22 Jun 2018 18:33:24 -0000 ----==_mimepart_5b2d40f132550_68852b1975166f5c35332e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. -- 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/1469#pullrequestreview-131302421 ----==_mimepart_5b2d40f132550_68852b1975166f5c35332e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

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

----==_mimepart_5b2d40f132550_68852b1975166f5c35332e-- From nobody Fri Jun 22 11:35:34 2018 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 5D42C130EC1 for ; Fri, 22 Jun 2018 11:35:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 BoJXrXifVnvX for ; Fri, 22 Jun 2018 11:35:28 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 99A77130EAF for ; Fri, 22 Jun 2018 11:35:28 -0700 (PDT) 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=iREm+UIy33ovl0F3tc6dPU6Kw2k=; b=BKS3Z0A2ir7FDSnE ge/zkbEkOG6LdnSMQA1xyrpdgn2QK2Oip5iJ8OvinVZhUOx7sWfkRqIuGhnslZcZ z4Es7i32rjZZMBFjvHou1XrALfXvWVdxufkH8akpKrE6pmCwCVAL0H5do60AEpg3 G8mt360yemYc3lBor3pXsjzYlAk= Received: by filter0608p1iad2.sendgrid.net with SMTP id filter0608p1iad2-24364-5B2D416E-3B 2018-06-22 18:35:26.800847948 +0000 UTC Received: from github-lowworker11-cp1-prd.iad.github.net (unknown [192.30.252.35]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id nE6YtDhJSc2R7VsLVpKqYg for ; Fri, 22 Jun 2018 18:35:26.816 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker11-cp1-prd.iad.github.net (Postfix) with ESMTP id C489FDF970 for ; Fri, 22 Jun 2018 11:35:26 -0700 (PDT) Date: Fri, 22 Jun 2018 18:35:27 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK instruction code points are inconsistent (#1471) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d416ec21df_4be53fcc3df52f781930c2"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1wi9yF5//hRFUVPWhP4O/Ccg6+BvmYOcxAxL oQHcZAqIWNCxDgvonKHK/UScn6hwE+/xsxxbHQU48WM7NYQu+4To05q+EpN2hxKSrbpECiM1+LwgSh p4588kWG4ULfLhNsdX/vlNFjA1KzICVSiaMSakGWzWVBUUXn9n8IC6cA+daErmsPBNwdZ+hmH1KqBD w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 18:35:31 -0000 ----==_mimepart_5b2d416ec21df_4be53fcc3df52f781930c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As discussed in Slack, this would involve changing the request stream code pretty substantially and flipping all the instruction bits on the decoder stream. However, I think the length of the prefix matters more than what bits are set and not set, so I'm indifferent. If it makes implementation easier, that's fine. -- 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/1471#issuecomment-399539336 ----==_mimepart_5b2d416ec21df_4be53fcc3df52f781930c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As discussed in Slack, this would involve changing the request stream co= de pretty substantially and flipping all the instruction bits on the decode= r stream. However, I think the length of the prefix matters more than what= bits are set and not set, so I'm indifferent. If it makes implementation = easier, that's fine.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b2d416ec21df_4be53fcc3df52f781930c2-- From nobody Fri Jun 22 11:39:11 2018 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 94573130EC8 for ; Fri, 22 Jun 2018 11:39:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 fPraWeRdqGT6 for ; Fri, 22 Jun 2018 11:39:08 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 E40BD130EAF for ; Fri, 22 Jun 2018 11:39:07 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529692747; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=NSvKSsG17TKoMbSubKQLEcwq5Ra/Heveg7QoC1PQoxQ=; b=L3QHAgjFQwx75C7sF1PiiO7b6wtKIidoYcosrIEi15Sss9CD1FFEHjr0olSJITi/hbQX+ZuY F40fSeDKZYUUhdVr8S7rbFT3bLG7lnATguuuKre1O+soYHd3iHb7L7SVUsyhfleW0sIbn9zS pl7MRRXfJTNNPCitsNEsvlKz2Po= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b2d424b.7f294478e750-smtp-out-n02; Fri, 22 Jun 2018 18:39:07 -0000 (UTC) Date: Fri, 22 Jun 2018 11:39:06 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b2d424a60096_6f142b08a41bdc1c293ef@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 9cb100: Discuss rebinding briefly Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d424a5fc98_6f142b08a41bdc1c29211"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 18:39:10 -0000 ----==_mimepart_5b2d424a5fc98_6f142b08a41bdc1c29211 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/disable_migration Home: https://github.com/quicwg/base-drafts Commit: 9cb100067a0c892b68a8ca5156fadc22f5365932 https://github.com/quicwg/base-drafts/commit/9cb100067a0c892b68a8ca5156fadc22f5365932 Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Discuss rebinding briefly **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d424a5fc98_6f142b08a41bdc1c29211-- From nobody Fri Jun 22 11:39:19 2018 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 A972F130EDA for ; Fri, 22 Jun 2018 11:39:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mlb2CQUPygWB for ; Fri, 22 Jun 2018 11:39:11 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19F72130EC2 for ; Fri, 22 Jun 2018 11:39:11 -0700 (PDT) Date: Fri, 22 Jun 2018 11:39:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529692750; bh=eBsJGEW7M1vubfJuOVs6cZ55E6dsFw2rBXiCJ2VN2LE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kMh8vZg4PXJQGNByR5cy7Jh0lY8sG7Xu054wL/eNItHxKwZJ2sa/DrSSRCbrQccwb YZvVqSL3RtmxhRCBfiOB5kUZj/8TOLAQs9z1rdFV1NVYBLEo8fiMHgFFUYEBU8VtP0 oXAizw/irG6giAOAjf7gBcNn118FUk833VL2ZlFw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d424e13dd7_7fa42ac6c80ecf54228f4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 22 Jun 2018 18:39:14 -0000 ----==_mimepart_5b2d424e13dd7_7fa42ac6c80ecf54228f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 9cb1000 Discuss rebinding briefly -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1447/files/f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b..9cb100067a0c892b68a8ca5156fadc22f5365932 ----==_mimepart_5b2d424e13dd7_7fa42ac6c80ecf54228f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

  • 9cb1000 Discuss rebinding briefly

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2d424e13dd7_7fa42ac6c80ecf54228f4-- From nobody Fri Jun 22 11:39:28 2018 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 20150130EC6 for ; Fri, 22 Jun 2018 11:39:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 6cD4Vr3b5uXQ for ; Fri, 22 Jun 2018 11:39:17 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 A13E8130EAF for ; Fri, 22 Jun 2018 11:39:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529692756; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=bOBbHrLwyfQ0qz77BmLUOt7UtVflkNfOBe4L5sOjXdk=; b=PRqebMx1ryYL1GlwQFELF/8ERBApkqwabUouIg9Y+hgXaLjc1BJYs1lqunXyeN3xOHnfX8vA v6tBtBBNTL9pLOc9NnKFZwskYNDK16T9CUDF7EEHp56PgSATrGIykGrWFQXXFPQ8al5t4qU5 67kw3TvJJnY+S2kbJHQonnqvFB4= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b2d4254.7fb8ea2c94e0-smtp-out-n01; Fri, 22 Jun 2018 18:39:16 -0000 (UTC) Date: Fri, 22 Jun 2018 11:39:16 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2d425497a20_da52b25d1d5fc10453f@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] eedc1d: Modify codepoints on decoder and request/push stre... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d425497672_da52b25d1d5fc1045250"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 18:39:21 -0000 ----==_mimepart_5b2d425497672_da52b25d1d5fc1045250 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-codepoints Home: https://github.com/quicwg/base-drafts Commit: eedc1d3ff8f1991272b4e59614294129c5f50e9d https://github.com/quicwg/base-drafts/commit/eedc1d3ff8f1991272b4e59614294129c5f50e9d Author: Alan Frindell Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Modify codepoints on decoder and request/push streams for consistency The prefix lengths remain the same but the instruction bits now follow the rule that each instruction has at most one '1' bit. Fixes #1471 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d425497672_da52b25d1d5fc1045250-- From nobody Fri Jun 22 11:40:55 2018 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 011B4130EAF for ; Fri, 22 Jun 2018 11:40:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 WtUlhn6Hj7zC for ; Fri, 22 Jun 2018 11:40:52 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B95F130EC6 for ; Fri, 22 Jun 2018 11:40:52 -0700 (PDT) Date: Fri, 22 Jun 2018 11:40:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529692851; bh=k6vNAqn2p/zTWkbfeQZvcmfht8FuZJLvSq3b2veRLDU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=tbIkAukTlJszKimbVgcab43Tgh79X+Oyk2BQRrPCZ6/5sbYSFZNYeAuAHH54OAbdt scbX590TfnJpSEVzCOyE8sStgeLie5/AN6bm9dwAmIuofOp5E3ScwjV0jfKuo0QFIU Eqv8yGKuSiQIhQ5ipK1PQClfgRa4WybckDwuQFdw= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d42b385cdc_7bf62b2159144f60894c9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 18:40:55 -0000 ----==_mimepart_5b2d42b385cdc_7bf62b2159144f60894c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The prefix lengths remain the same but the instruction bits now follow the rule that each instruction has at most one '1' bit. Fixes #1471 You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1472 -- Commit Summary -- * Modify codepoints on decoder and request/push streams for consistency -- File Changes -- M draft-ietf-quic-qpack.md (28) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1472.patch https://github.com/quicwg/base-drafts/pull/1472.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/1472 ----==_mimepart_5b2d42b385cdc_7bf62b2159144f60894c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The prefix lengths remain the same but the instruction bits now follow the rule that each instruction has at most one '1' bit.

Fixes #1471

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

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

Commit Summary

  • Modify codepoints on decoder and request/push streams for consistency

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 mute the thread.

----==_mimepart_5b2d42b385cdc_7bf62b2159144f60894c9-- From nobody Fri Jun 22 11:50:30 2018 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 67F34130EED for ; Fri, 22 Jun 2018 11:50:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 bxnS8vra2m8g for ; Fri, 22 Jun 2018 11:50:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BABDE130EC1 for ; Fri, 22 Jun 2018 11:50:18 -0700 (PDT) Date: Fri, 22 Jun 2018 11:50:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529693418; bh=qL1yFgAUG8NyBaa2QQPcOYPeA6LHSQI3g4gLSuDeES0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yFkjrm1aO4zhRQ2d39KeoR8IAO7DktVH7LubIYtc5Tq84TBj6Kh+ffF9iYG3ffb9w 2QgXIw9NNs+6kOa6NSi0EEYYbMVISiDvv+MDyloIjJTbESgWhXAmLlWhKVXIl0SEb/ sAYm9u90NL6hGwBUXBtJMVs9j3XIpT2KFJZBCPS4= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d44ea29f26_4e573fd5d3eeef88110462"; 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.26 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: Fri, 22 Jun 2018 18:50:27 -0000 ----==_mimepart_5b2d44ea29f26_4e573fd5d3eeef88110462 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. > two-bit pattern. If the entry is in the dynamic table with an absolute index -greater than Base Index, the representation starts with the '0101' four-bit +greater than Base Index, the representation starts with the '0000' four-bit pattern. This change is fine, but didn't we separate out the Post-Base things to their own headers? Did we miss one? -- 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/1472#pullrequestreview-131307888 ----==_mimepart_5b2d44ea29f26_4e573fd5d3eeef88110462 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

In draft-ietf-quic-qpack.md:

>  two-bit pattern.  If the entry is in the dynamic table with an absolute index
-greater than Base Index, the representation starts with the '0101' four-bit
+greater than Base Index, the representation starts with the '0000' four-bit
 pattern.

This change is fine, but didn't we separate out the Post-Base things to their own headers? Did we miss one?

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

----==_mimepart_5b2d44ea29f26_4e573fd5d3eeef88110462-- From nobody Fri Jun 22 12:10:04 2018 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 68EAE130EC6 for ; Fri, 22 Jun 2018 12:10:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 mVUTrUshSabW for ; Fri, 22 Jun 2018 12:10:00 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 68514130EC0 for ; Fri, 22 Jun 2018 12:09:59 -0700 (PDT) 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=t9Qz1i8/lZMwGX2YUXY2A/g8X8k=; b=B1NR/IuYirwcCMg7 q/Ie6AFtKxgY7RSg2KlUxPrpp6IK2Vy2T0n6fpx9D43kGyIpNyO+Q4VFSWw97drq amW4S16uWMGquNOzImT8EM4lY1EMYYlWbqzCvVHKUXOtiPKzEch7Tdn7JfIixdIU X23oA/Ew+Eih8ap5D61STPcVlX8= Received: by filter0271p1iad2.sendgrid.net with SMTP id filter0271p1iad2-17875-5B2D4980-48 2018-06-22 19:09:52.655416349 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id NHZeDSjqRh23u_2QKpqpZA for ; Fri, 22 Jun 2018 19:09:52.674 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id A2B503E1973 for ; Fri, 22 Jun 2018 12:09:52 -0700 (PDT) Date: Fri, 22 Jun 2018 19:09:52 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d4980a0c22_3b842b119c6c4f5c784b0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0obxHix9I6MADgCZlT1d4ZPmVkV2/WtUqS+W oD12HZPuuP/OldmhvGpm0d2DSgzExUMQ/uxsUClbETfgLYjuchOGAtvulRZ9N/mJ4LtJoZ13Uh7fk7 4r8GYkQ1cWdzmaZHRC+J729IA7biQTfzvP0Y3ZdjvGl4KQCOE4XS057P3JziRQvgwx3QqmYj7FHumW E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 22 Jun 2018 19:10:03 -0000 ----==_mimepart_5b2d4980a0c22_3b842b119c6c4f5c784b0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. Two comments on the frame diagram. > @@ -2999,10 +2999,10 @@ appended at the end. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACK Block Count (i) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Can you move the ACK Block Count down as well. It's odd to have that up here. > @@ -2999,10 +2999,10 @@ appended at the end. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACK Block Count (i) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Also, how about putting the ECN info in this diagram, rather than having it in a separate diagram? -- 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/1372#pullrequestreview-131313634 ----==_mimepart_5b2d4980a0c22_3b842b119c6c4f5c784b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

Two comments on the frame diagram.

In draft-ietf-quic-transport.md:

> @@ -2999,10 +2999,10 @@ appended at the end.
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                       ACK Block Count (i)                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Can you move the ACK Block Count down as well. It's odd to have that up here.

In draft-ietf-quic-transport.md:

> @@ -2999,10 +2999,10 @@ appended at the end.
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                       ACK Block Count (i)                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Also, how about putting the ECN info in this diagram, rather than having it in a separate diagram?

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

----==_mimepart_5b2d4980a0c22_3b842b119c6c4f5c784b0-- From nobody Fri Jun 22 12:24:54 2018 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 25F3E130ED6 for ; Fri, 22 Jun 2018 12:24:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 jpCWMKOHAczZ for ; Fri, 22 Jun 2018 12:24:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4E72130EC0 for ; Fri, 22 Jun 2018 12:24:51 -0700 (PDT) Date: Fri, 22 Jun 2018 12:24:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529695490; bh=LxjnHgXgszQhwCXrTYVJ8dMz39mH54w9p4/0WN/EQxA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V6ag+7tYDrUz+qJY6yl3yWgGoY9fNU9878Y0kDuiJBj+2VY7bOyHTbiJXDuDPINPB rQZM5EQ1HsoToBUA1F3ScE+1BFFup3b0OeFovMexgbCQMeDRxmKZgZJRp7Ifxp4W2T 204HVUV/VMLpxiZie0HH2cLOuKrzLBZnuEJTlnAM= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d4d02bc60a_19592abf2b734f5013424b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 19:24:54 -0000 ----==_mimepart_5b2d4d02bc60a_19592abf2b734f5013424b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit afrind commented on this pull request. > two-bit pattern. If the entry is in the dynamic table with an absolute index -greater than Base Index, the representation starts with the '0101' four-bit +greater than Base Index, the representation starts with the '0000' four-bit pattern. It has its own section but the normative text is in this section. -- 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/1472#discussion_r197546038 ----==_mimepart_5b2d4d02bc60a_19592abf2b734f5013424b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind commented on this pull request.

In draft-ietf-quic-qpack.md:

>  two-bit pattern.  If the entry is in the dynamic table with an absolute index
-greater than Base Index, the representation starts with the '0101' four-bit
+greater than Base Index, the representation starts with the '0000' four-bit
 pattern.

It has its own section but the normative text is in this section.

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

----==_mimepart_5b2d4d02bc60a_19592abf2b734f5013424b-- From nobody Fri Jun 22 13:06:21 2018 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 9F732130EE3 for ; Fri, 22 Jun 2018 13:06:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 tUD0M9MTRY6d for ; Fri, 22 Jun 2018 13:06:18 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0C4B3130DF5 for ; Fri, 22 Jun 2018 13:06:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529697977; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=VIRzbtvwvUbYZ+SOwdMB1fOlecK/0ATbcR09J2cCbbo=; b=AKzrijgoET6tgWsppk43TLTrjzwCM/bzQHo9kBUFFg9LXBLGcelJu64cqdrgKMMUcdiWTG96 PvZ4mYCW66UYUJAUUNKaFckayBjvhja9f5uwGOingBndlAH/YDe7vYF81izBPS8mvMWQs9bA vBN5rJ7lNrKkjFkJUPDL7/HLKbE= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b2d56b8.7fbd126e8db0-smtp-out-n01; Fri, 22 Jun 2018 20:06:16 -0000 (UTC) Date: Fri, 22 Jun 2018 13:06:15 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b2d56b74f12a_3ef72b08fb9a7c1497589@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 710b19: Decoder MAY error on an incorrect largest referenc... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b2d56b74ed3a_3ef72b08fb9a7c149741f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 22 Jun 2018 20:06:20 -0000 ----==_mimepart_5b2d56b74ed3a_3ef72b08fb9a7c149741f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 710b199b45342fe2efd49294427f29eafc10a911 https://github.com/quicwg/base-drafts/commit/710b199b45342fe2efd49294427f29eafc10a911 Author: Alan Frindell Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Decoder MAY error on an incorrect largest reference Fixes #1404 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b2d56b74ed3a_3ef72b08fb9a7c149741f-- From nobody Fri Jun 22 13:06:28 2018 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 957AD130DF5 for ; Fri, 22 Jun 2018 13:06:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 CSeq0zkjPUUS for ; Fri, 22 Jun 2018 13:06:19 -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 D9E8D130EDF for ; Fri, 22 Jun 2018 13:06:18 -0700 (PDT) Date: Fri, 22 Jun 2018 13:06:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529697977; bh=VKvWI8WbnynSbBmKumUcKFQL4a4lnK70o/XqFXf9Mog=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K4t2XOi6eM6JAD3tJTGt17Inj5xmQKcmDhBVS08oOlkT61RHImD8xEL47yiesXmOq ppwsbGt/zdar9VBEMaU156XaQyHw41/Q0+h7MsY6dS0h/aGtb+puAkLjQ4BG6pqoBL Yy6AIvBqAMnea7F4Ljv8o1/W26Km9uDOR/5aWXdQ= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Decoder MAY error on an incorrect largest reference (#1469) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d56b9e45a3_4c982ab6b1818f5c12665b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 20:06:21 -0000 ----==_mimepart_5b2d56b9e45a3_4c982ab6b1818f5c12665b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1469. -- 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/1469#event-1696720253 ----==_mimepart_5b2d56b9e45a3_4c982ab6b1818f5c12665b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1469.

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

----==_mimepart_5b2d56b9e45a3_4c982ab6b1818f5c12665b-- From nobody Fri Jun 22 13:06:34 2018 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 31553130EDF for ; Fri, 22 Jun 2018 13:06:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 6l-DTmvfHhPf for ; Fri, 22 Jun 2018 13:06:19 -0700 (PDT) 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 5E4EC130EE1 for ; Fri, 22 Jun 2018 13:06:19 -0700 (PDT) Date: Fri, 22 Jun 2018 13:06:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529697978; bh=HnosmgsUf8ZnvMXw1/9pxddEEaQAzPPzt+elZWWr4gA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=URcj6SBz5VefoTcBKIuQAfNI0kHJB53iJVe3cEG119iiJRdeNh6jDWghoQMDnCidN 05hNDYodgeEmdfg8WqabpkRu7dYtdDHfzcBtl47u6eZdBUAuMNQSpnN0SqroI82i3N 6WBskKj0YMTbawj0GMFonJyH+KVW8CxygHEptMEU= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Largest Reference too big (#1404) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d56ba4263d_38252ad9aa7b0f58127641"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Fri, 22 Jun 2018 20:06:22 -0000 ----==_mimepart_5b2d56ba4263d_38252ad9aa7b0f58127641 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1404 via #1469. -- 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/1404#event-1696720256 ----==_mimepart_5b2d56ba4263d_38252ad9aa7b0f58127641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1404 via #1469.

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

----==_mimepart_5b2d56ba4263d_38252ad9aa7b0f58127641-- From nobody Fri Jun 22 15:37:26 2018 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 30F60130F0B for ; Fri, 22 Jun 2018 15:37:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 p8xGS3Y_q7lw for ; Fri, 22 Jun 2018 15:37:22 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74494130F08 for ; Fri, 22 Jun 2018 15:37:22 -0700 (PDT) Date: Fri, 22 Jun 2018 15:37:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529707040; bh=Ce8x6qCeZgfPhrVFmRwPD6b0H0zmfGn9iK1J2dGjPRI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=L3qSARP2HPrEtAp1mZj3IJTWEUGXMDnamkXlFj7dO6Nr2Ef4KgieBGL7khXatc4oA lYEpr7kxTtwtS5MzCJHFiJicFbnEJy5c4TZ3zFC3bY+WDRRNhxfJLL0O2BTIMHyMS3 Qtvm1X5u1/GWGcXJAGbxwEaIQuqpEmg1vCYAFPec= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d7a206955d_5c792ab285552f501528b0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 22 Jun 2018 22:37:25 -0000 ----==_mimepart_5b2d7a206955d_5c792ab285552f501528b0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 7a780db Fix build breaks -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/e2ed4db7df7d72a08fe13b8da8d17f6fca601c26..7a780dbed8eed8ed9584db89215bd752dbf86c7a ----==_mimepart_5b2d7a206955d_5c792ab285552f501528b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2d7a206955d_5c792ab285552f501528b0-- From nobody Fri Jun 22 15:54:22 2018 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 9E6E4130F0D for ; Fri, 22 Jun 2018 15:54:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 SLYw-3p54xWh for ; Fri, 22 Jun 2018 15:54:19 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03DED130F08 for ; Fri, 22 Jun 2018 15:54:19 -0700 (PDT) Date: Fri, 22 Jun 2018 15:54:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529708058; bh=iSUPEPFjKZ2IRkuDLA0X5Pby6RVPT/LwavTzfHPV5MI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=loFKHsZKWVv5k3AXCCHYWenaGzqwhNJDJLIhVc1rX9riS2tmDI6l9BCPBWTtUtIjJ lpTfaFO85NHiFfz4OQEAP0MQnK//7OPiwQv87aLXAYy/ItRwz6zT2oTgTgm06o4Pm8 3NLeDDVQQO6P+WfefGRIKqW6n90di/vlPMkm5wLk= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2d7e1a44a95_1c463f82eb03ef7815575a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 22 Jun 2018 22:54:21 -0000 ----==_mimepart_5b2d7e1a44a95_1c463f82eb03ef7815575a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 4db5568 Extra word -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/7a780dbed8eed8ed9584db89215bd752dbf86c7a..4db556887313b51de0139bb7c6c7be33614c4ddb ----==_mimepart_5b2d7e1a44a95_1c463f82eb03ef7815575a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b2d7e1a44a95_1c463f82eb03ef7815575a-- From nobody Fri Jun 22 18:30:23 2018 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 E3E2612F1A5 for ; Fri, 22 Jun 2018 18:30:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oks6en7vrmmz for ; Fri, 22 Jun 2018 18:30:19 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D6A71271FF for ; Fri, 22 Jun 2018 18:30:19 -0700 (PDT) Date: Fri, 22 Jun 2018 18:30:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529717417; bh=8Dydk+593gEwh5NObALV03HQ2qkNqvLmJYiw9eoM730=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ts/bBkvElKUmo9d30nwDZIabF5OMHXMOhx5CmoI9nxXC81kejOqEWBNsSh3aqQgVA eKstbDyBJ7avNEN98onYu5n5LN5lyC1xvXXH9+15Fkaiuti0wxF4ghvlXbUiiqMl3E rW9d/yxfX7aag3GmYeyryOkTkCChYkX7PkwXZwus= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b2da2a9e9de8_7c7b2acabf626f60720ad"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Sat, 23 Jun 2018 01:30:22 -0000 ----==_mimepart_5b2da2a9e9de8_7c7b2acabf626f60720ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The latest addition looks good to me, thanks! -- 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/1447#issuecomment-399620647 ----==_mimepart_5b2da2a9e9de8_7c7b2acabf626f60720ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The latest addition looks good to me, thanks!

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

----==_mimepart_5b2da2a9e9de8_7c7b2acabf626f60720ad-- From nobody Sun Jun 24 16:37:30 2018 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 61E83130E79 for ; Sun, 24 Jun 2018 16:37:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 YaWzKS4IOLjJ for ; Sun, 24 Jun 2018 16:37:27 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7A79130E72 for ; Sun, 24 Jun 2018 16:37:26 -0700 (PDT) Date: Sun, 24 Jun 2018 16:37:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529883445; bh=EYXgk37zVzIkRuo7PApEac/ZiqorS286+/h7+Xt8VbA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BEV6Mm+Jaf6Xzba8yPmhv/bVtRcKwryx3u7W0XFrxZj1nKL3DgEHQAs+lXg8Xz0sI PPvLfwDuWlXtHcfrGlcwLS6hRcgOEKOnkezIyPepLE4D+i5hkQwxXcaDzVrg7Xz8Lg Yue2nTb33O7m6cLMk48k6ZSB1ZAe5RAKQ7sRG/ls= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b302b3598729_4c572b0b52a12f6012317a9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 24 Jun 2018 23:37:29 -0000 ----==_mimepart_5b302b3598729_4c572b0b52a12f6012317a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can't switch between requesting a connection ID and not, so if zero length is chosen, then you might assume that that peer has every connection ID it will ever need and they are always on the right connection ID. -- 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/1468#issuecomment-399798066 ----==_mimepart_5b302b3598729_4c572b0b52a12f6012317a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You can't switch between requesting a connection ID and not, so if zero length is chosen, then you might assume that that peer has every connection ID it will ever need and they are always on the right connection ID.

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

----==_mimepart_5b302b3598729_4c572b0b52a12f6012317a9-- From nobody Sun Jun 24 16:41:00 2018 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 1B6A0130E78 for ; Sun, 24 Jun 2018 16:40:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 eGN62ztEMhse for ; Sun, 24 Jun 2018 16:40:57 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56A04130E72 for ; Sun, 24 Jun 2018 16:40:57 -0700 (PDT) Date: Sun, 24 Jun 2018 16:40:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529883656; bh=jxjvaoCiXV7Koc8HLvkZk9TmdDWnODtUtMZVpwxN2Ys=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xDFcHEYR784K0cnH072BRyLNi7FE2WRRZaBo4sgv+Y+Uu2tgdFvryg+dC+h3+TY6z EqZsas7rP7ZB1SAy3igvsenXVwcBkH+bpZdUu/YBGpZHWEYObRyF1udG7ZF0TpY9IX p3P7LVBbC8EBGbMS0MReOLKm3St02Qp3g7uMCX6Y= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b302c08a9f2b_dda2acba61f2f6053710"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 24 Jun 2018 23:40:59 -0000 ----==_mimepart_5b302c08a9f2b_dda2acba61f2f6053710 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, I don't think that would help with the suggestion in #1468. Insisting on a fixed starting point ensures that you can do things like matching. Removing the connection ID from the preferred address would make it harder to get that right because you then need to wait for a NEW_CONNECTION_ID frame before migrating. -- 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/1465#discussion_r197656872 ----==_mimepart_5b302c08a9f2b_dda2acba61f2f6053710 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

I don't think that would help with the suggestion in #1468. Insisting on a fixed starting point ensures that you can do things like matching.

Removing the connection ID from the preferred address would make it harder to get that right because you then need to wait for a NEW_CONNECTION_ID frame before migrating.

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

----==_mimepart_5b302c08a9f2b_dda2acba61f2f6053710-- From nobody Sun Jun 24 17:27:14 2018 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 AC1DE130E81 for ; Sun, 24 Jun 2018 17:27:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 JtLZu9vh50BH for ; Sun, 24 Jun 2018 17:27:09 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A285130E7A for ; Sun, 24 Jun 2018 17:27:09 -0700 (PDT) Date: Sun, 24 Jun 2018 17:27:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529886428; bh=+sP2makhDTqjKgiTFperpBmIwO00uILLdzcx2haqK5w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wTxDoyr99bSgdiYQLjSlYOdb5bXIdOLNU431st7x+5TvyDXrexeKz9lLY4vxC8P6E AWckjKFQkO5tyihBDd+6rl7l2MDAaDjl+1nTRjvUM2hcgJoIwMB/B6iTrfaYgrnpW0 eG22e4NWrpYmE3RCuVm4C5Lpj504MKd6LIgZCXt4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3036dc7585a_7d522ab7a1ab8f5016953dd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 00:27:12 -0000 ----==_mimepart_5b3036dc7585a_7d522ab7a1ab8f5016953dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Not 100% sure about the organization here, but the text is definitely worth having. We definitely need to do some reorganizing of the document real soon now, so I'm not going to stress about where text goes. > +selected during the handshake coming first. Additional connection IDs are +provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each +with a specified sequence number. The series of connection IDs issued SHOULD be +contiguous, but might not appear to be upon receipt due to reordering or loss. + +Each connection ID MUST be used on only one local address. When packets are sent +for the first time on a new local address, a new connection ID MUST be used with +a higher sequence number than any connection ID previously used on any local +address. At any time, an endpoint MAY change to a new connection ID on a local +address already in use. + +An endpoint MUST NOT send packets with a connection ID which has a lower +sequence number than the highest sequence number of any connection ID ever sent +or received on that local address. + +Implementations SHOULD ensure that peers have a connection ID with a matching If this isn't MUST, then the above MUST NOT will just result in broken connections. > +series of connection IDs over the lifetime of a connection. The series of +connection IDs issued by an endpoint is ordered, with the final connection ID +selected during the handshake coming first. Additional connection IDs are +provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each +with a specified sequence number. The series of connection IDs issued SHOULD be +contiguous, but might not appear to be upon receipt due to reordering or loss. + +Each connection ID MUST be used on only one local address. When packets are sent +for the first time on a new local address, a new connection ID MUST be used with +a higher sequence number than any connection ID previously used on any local +address. At any time, an endpoint MAY change to a new connection ID on a local +address already in use. + +An endpoint MUST NOT send packets with a connection ID which has a lower +sequence number than the highest sequence number of any connection ID ever sent +or received on that local address. This is going to be hard to understand. It's precise, but I think that we might provide a little more help. Something like "This guarantees that when an endpoint migrates to a new path the packets sent on that path use new connection IDs in both directions." I don't know how to say this, but it seems like it might be worth adding: "Note: A connection ID MUST NOT include an unprotected encoding of the associated sequence number. Endpoints need to be able to recover the sequence number associated with each connection ID they provide without relying on information available to the recipient of the connection ID. A connection ID that encodes an unencrypted sequence number could be used to correlate connection IDs across network paths." -- 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/1465#pullrequestreview-131442400 ----==_mimepart_5b3036dc7585a_7d522ab7a1ab8f5016953dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Not 100% sure about the organization here, but the text is definitely worth having. We definitely need to do some reorganizing of the document real soon now, so I'm not going to stress about where text goes.

In draft-ietf-quic-transport.md:

> +selected during the handshake coming first.  Additional connection IDs are
+provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each
+with a specified sequence number.  The series of connection IDs issued SHOULD be
+contiguous, but might not appear to be upon receipt due to reordering or loss.
+
+Each connection ID MUST be used on only one local address. When packets are sent
+for the first time on a new local address, a new connection ID MUST be used with
+a higher sequence number than any connection ID previously used on any local
+address.  At any time, an endpoint MAY change to a new connection ID on a local
+address already in use.
+
+An endpoint MUST NOT send packets with a connection ID which has a lower
+sequence number than the highest sequence number of any connection ID ever sent
+or received on that local address.
+
+Implementations SHOULD ensure that peers have a connection ID with a matching

If this isn't MUST, then the above MUST NOT will just result in broken connections.

In draft-ietf-quic-transport.md:

> +series of connection IDs over the lifetime of a connection. The series of
+connection IDs issued by an endpoint is ordered, with the final connection ID
+selected during the handshake coming first.  Additional connection IDs are
+provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each
+with a specified sequence number.  The series of connection IDs issued SHOULD be
+contiguous, but might not appear to be upon receipt due to reordering or loss.
+
+Each connection ID MUST be used on only one local address. When packets are sent
+for the first time on a new local address, a new connection ID MUST be used with
+a higher sequence number than any connection ID previously used on any local
+address.  At any time, an endpoint MAY change to a new connection ID on a local
+address already in use.
+
+An endpoint MUST NOT send packets with a connection ID which has a lower
+sequence number than the highest sequence number of any connection ID ever sent
+or received on that local address.

This is going to be hard to understand. It's precise, but I think that we might provide a little more help. Something like "This guarantees that when an endpoint migrates to a new path the packets sent on that path use new connection IDs in both directions."

I don't know how to say this, but it seems like it might be worth adding: "Note: A connection ID MUST NOT include an unprotected encoding of the associated sequence number. Endpoints need to be able to recover the sequence number associated with each connection ID they provide without relying on information available to the recipient of the connection ID. A connection ID that encodes an unencrypted sequence number could be used to correlate connection IDs across network paths."

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

----==_mimepart_5b3036dc7585a_7d522ab7a1ab8f5016953dd-- From nobody Sun Jun 24 17:48:11 2018 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 E7FF5130E7A for ; Sun, 24 Jun 2018 17:48:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4Qjzop9PPLei for ; Sun, 24 Jun 2018 17:48:06 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EA8D130E10 for ; Sun, 24 Jun 2018 17:48:06 -0700 (PDT) Date: Sun, 24 Jun 2018 17:48:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529887685; bh=GmHBHayxyEGOfsKmHJGgCmw3aRdNXY4T2rd61qI3IFg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jNpEwv/33icx0zfBytXKPeoY0D9HOgLom/oda5Xjoj+zXMaF+a+9Mixtp941obbyy 2Qzb/wXYXT/XLXHKFd870kZpNOvuv+vVzEaViccnu/BMz3wohwSxR1JetXXrEyBzfG xdTXnUXHU4a9H9OH128f/QVqDS774sdIe/6teoA8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b303bc58d59a_14c62ae49be98f54381598"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 00:48:09 -0000 ----==_mimepart_5b303bc58d59a_14c62ae49be98f54381598 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson approved this pull request. 24h warning. There are a number of things that this text leaves open, and in some cases things are broken (see esp. Retry), but we can't afford to leave this open any longer. If you have new issues; this isn't the place to discuss them. It's OK to open a new issue with the assumption that this PR will be merged, because it will be. (I'll take some of the open comments here and make issues. It looks like we already have issues for the Retry problems.) > -When the alarm fires, the sender MUST retransmit all unacknowledged handshake -data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive -firing of the handshake alarm, the sender SHOULD double the handshake timeout -and set an alarm for this period. +When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active +unless the CRYPTO_HS frames were sent at 1RTT encryption. Is this encryption level or packet number space? Also, the first SHOULD in the previous paragraph needs at least one caveat for this case. > @@ -422,6 +441,14 @@ sending any ACK frames in response. In this case they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +SHOULD use a very short ack delay, such as 1ms. ACK frames MAY be The MAY is weird. ACK can always be sent immediately. > +Unlike TLS over TCP, QUIC applications which want to send data do not +send it through TLS "application_data" records. Rather, they send it +as QUIC STREAM frames which are then carried in QUIC packets. + + +# Carrying TLS Messages {#carrying-tls} + +QUIC carries TLS handshake data in CRYPTO_HS frames, each of which +consists of a contiguous block of handshake data identified by an +offset and length. Those frames are packaged into QUIC packets +and encrypted under the current TLS encryption level. +As with TLS over TCP, once TLS handshake data has +been delivered to QUIC, it is QUIC's responsibility to deliver it +reliably. Each chunk of data is associated with the then-current TLS +sending keys, and if QUIC needs to retransmit that data, it MUST use We use "encryption level" rather than sending keys, but I don't think that either works very well for this; TLS has a strict notion of what should be used to protect every octet, but there are multiple of these contexts in flight at the same time. Needs work. > + +- CRYPTO_HS frames MAY appear in packets of any encryption level. +- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any + encryption level other than 0-RTT. +- PADDING and PING frames MAY appear in packets of any encryption level. +- ACK frames MAY appear in packets of any encryption level, but + MUST only acknowledge packets which appeared in that encryption + level. +- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels. +- All other frame types MUST only appear at the 1-RTT levels. + +Because packets may be reordered on the wire, QUIC uses the packet +type to indicate which level a given packet was encrypted +under, as shown in {{packet-types-levels}}. When multiple packets of +different encryption levels need to be sent, endpoints SHOULD use +coalesced packets to send them in the same UDP datagram. I agree with Christian here. Nothing says that sending together is necessary, no matter how good it might be for performance. > -A QUIC server starts the process by providing TLS with stream 0 octets. - -Each time that an endpoint receives data on stream 0, it delivers the octets to -TLS if it is able. Each time that TLS is provided with new data, new handshake -octets are requested from TLS. TLS might not provide any octets if the -handshake messages it has received are incomplete or it has no data to send. - -At the server, when TLS provides handshake octets, it also needs to indicate -whether the octets contain a HelloRetryRequest. A HelloRetryRequest MUST always -be sent in a Retry packet, so the QUIC server needs to know whether the octets -are a HelloRetryRequest. +A QUIC server starts the process by providing TLS with the client's +handshake octets. + +At any given time, an endpoint will have a current sending encryption +level and receiving encryption level. Each encryption level is I see. The problem here is that I was thinking QUIC, and this really applies to TLS. TLS assumes ordering, but QUIC doesn't. That's something that needs to be improved here, but I don't think that we need to do that here. > @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past. ### ACK Frames and Packet Protection -ACK frames that acknowledge protected packets MUST be carried in a packet that -has an equivalent or greater level of packet protection. - -Packets that are protected with 1-RTT keys MUST be acknowledged in packets that -are also protected with 1-RTT keys. - -A packet that is not protected and claims to acknowledge a packet number that -was sent with packet protection is not valid. An unprotected packet that -carries acknowledgments for protected packets MUST be discarded in its entirety. +ACK frames MUST only be carried in a packet that has the same packet My point is that you can't cross-ACK because you aren't capable of acknowledging something in a different packet number space. -- 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/1450#pullrequestreview-131038370 ----==_mimepart_5b303bc58d59a_14c62ae49be98f54381598 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

24h warning.

There are a number of things that this text leaves open, and in some cases things are broken (see esp. Retry), but we can't afford to leave this open any longer. If you have new issues; this isn't the place to discuss them. It's OK to open a new issue with the assumption that this PR will be merged, because it will be. (I'll take some of the open comments here and make issues. It looks like we already have issues for the Retry problems.)

In draft-ietf-quic-recovery.md:

>  
-When the alarm fires, the sender MUST retransmit all unacknowledged handshake
-data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive
-firing of the handshake alarm, the sender SHOULD double the handshake timeout
-and set an alarm for this period.
+When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active
+unless the CRYPTO_HS frames were sent at 1RTT encryption.

Is this encryption level or packet number space?

Also, the first SHOULD in the previous paragraph needs at least one caveat for this case.

In draft-ietf-quic-recovery.md:

> @@ -422,6 +441,14 @@ sending any ACK frames in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 
+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+SHOULD use a very short ack delay, such as 1ms.  ACK frames MAY be

The MAY is weird. ACK can always be sent immediately.

In draft-ietf-quic-tls.md:

>  
+Unlike TLS over TCP, QUIC applications which want to send data do not
+send it through TLS "application_data" records. Rather, they send it
+as QUIC STREAM frames which are then carried in QUIC packets.
+
+
+# Carrying TLS Messages {#carrying-tls}
+
+QUIC carries TLS handshake data in CRYPTO_HS frames, each of which
+consists of a contiguous block of handshake data identified by an
+offset and length. Those frames are packaged into QUIC packets
+and encrypted under the current TLS encryption level.
+As with TLS over TCP, once TLS handshake data has
+been delivered to QUIC, it is QUIC's responsibility to deliver it
+reliably. Each chunk of data is associated with the then-current TLS
+sending keys, and if QUIC needs to retransmit that data, it MUST use

We use "encryption level" rather than sending keys, but I don't think that either works very well for this; TLS has a strict notion of what should be used to protect every octet, but there are multiple of these contexts in flight at the same time. Needs work.

In draft-ietf-quic-tls.md:

> +
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under, as shown in {{packet-types-levels}}. When multiple packets of
+different encryption levels need to be sent, endpoints SHOULD use
+coalesced packets to send them in the same UDP datagram.

I agree with Christian here. Nothing says that sending together is necessary, no matter how good it might be for performance.

In draft-ietf-quic-tls.md:

> -A QUIC server starts the process by providing TLS with stream 0 octets.
-
-Each time that an endpoint receives data on stream 0, it delivers the octets to
-TLS if it is able.  Each time that TLS is provided with new data, new handshake
-octets are requested from TLS.  TLS might not provide any octets if the
-handshake messages it has received are incomplete or it has no data to send.
-
-At the server, when TLS provides handshake octets, it also needs to indicate
-whether the octets contain a HelloRetryRequest.  A HelloRetryRequest MUST always
-be sent in a Retry packet, so the QUIC server needs to know whether the octets
-are a HelloRetryRequest.
+A QUIC server starts the process by providing TLS with the client's
+handshake octets.
+
+At any given time, an endpoint will have a current sending encryption
+level and receiving encryption level. Each encryption level is

I see. The problem here is that I was thinking QUIC, and this really applies to TLS. TLS assumes ordering, but QUIC doesn't. That's something that needs to be improved here, but I don't think that we need to do that here.

In draft-ietf-quic-transport.md:

> @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past.
 
 ### ACK Frames and Packet Protection
 
-ACK frames that acknowledge protected packets MUST be carried in a packet that
-has an equivalent or greater level of packet protection.
-
-Packets that are protected with 1-RTT keys MUST be acknowledged in packets that
-are also protected with 1-RTT keys.
-
-A packet that is not protected and claims to acknowledge a packet number that
-was sent with packet protection is not valid.  An unprotected packet that
-carries acknowledgments for protected packets MUST be discarded in its entirety.
+ACK frames MUST only be carried in a packet that has the same packet

My point is that you can't cross-ACK because you aren't capable of acknowledging something in a different packet number space.

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

----==_mimepart_5b303bc58d59a_14c62ae49be98f54381598-- From nobody Sun Jun 24 18:45:29 2018 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 06B94130E10 for ; Sun, 24 Jun 2018 18:45:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mEQ0_PjQAnsv for ; Sun, 24 Jun 2018 18:45:25 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79758130E80 for ; Sun, 24 Jun 2018 18:45:25 -0700 (PDT) Date: Sun, 24 Jun 2018 18:45:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529891124; bh=AwiAcvbs5mFc/z8s9cgZf4N+7aXrsTk7EP6P1qNL9Cc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JW3t70s1/CeW1R0Dzu6a92R2cXnr4oQ1hhAn5TRlvDkXyBdmveez8s1cbkdlPQ/V4 RPMxdM5fjogafsZO2UOV32XyuYCi3/LPmkvLSAFTIsIr02pqeExAa3HigwtkLQRhqf rLl9nmCk0018xQ4LUd8koxPb8XbPvKOHtS23Hjzc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3049348e728_77f73f7fbe08af8453682d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 25 Jun 2018 01:45:27 -0000 ----==_mimepart_5b3049348e728_77f73f7fbe08af8453682d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 8d57711 remove "the the" -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/4db556887313b51de0139bb7c6c7be33614c4ddb..8d57711c819307c44cec8db2964a2a80c8f87ab9 ----==_mimepart_5b3049348e728_77f73f7fbe08af8453682d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3049348e728_77f73f7fbe08af8453682d-- From nobody Sun Jun 24 18:58:22 2018 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 214AA130E83 for ; Sun, 24 Jun 2018 18:58:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 C9CrKY9-VUjx for ; Sun, 24 Jun 2018 18:58:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B98D130E80 for ; Sun, 24 Jun 2018 18:58:18 -0700 (PDT) Date: Sun, 24 Jun 2018 18:58:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529891897; bh=SREnQeY5/sqH5WFGaLNlOOw+YNJdmPwF+R6v5K/7luw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BPmyVVq4bqxo6cdOyRnj/JFNssfZSlYuQ6Ksd5CHcNptJd+i92qr+6AzgIAHONEyQ 6jebhEEcST3M5QCyduXpnTFyHfyWtad+8bLOI9rjTgYAcMKQqy9heXP/E7EskTDA2C QnlkCgRz4l5nAMCFaRL1dQ6k+TlUL/d5Q057gDd4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b304c399bad8_6f672afacc04cf584679a8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 25 Jun 2018 01:58:21 -0000 ----==_mimepart_5b304c399bad8_6f672afacc04cf584679a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. a2aabfe More errors around delivering to TLS out of order -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/8d57711c819307c44cec8db2964a2a80c8f87ab9..a2aabfe9e6feec0eaab59af0f4a0c212190b4474 ----==_mimepart_5b304c399bad8_6f672afacc04cf584679a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • a2aabfe More errors around delivering to TLS out of order

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b304c399bad8_6f672afacc04cf584679a8-- From nobody Sun Jun 24 19:02:14 2018 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 7D0DD12785F for ; Sun, 24 Jun 2018 19:02:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 g8zMRnhvPKDv for ; Sun, 24 Jun 2018 19:02:11 -0700 (PDT) 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 AEF6B124BE5 for ; Sun, 24 Jun 2018 19:02:11 -0700 (PDT) Date: Sun, 24 Jun 2018 19:02:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529892131; bh=0apeDTaPRoT+dsKtUQsYVGPquYNsJk2y6QLlVPVTgw8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z5B+mJ8vzJ8LJnFr4g+qh9Zzj1HhkQRiiVmQDP5tbRKPXcBD6oR73Stry5XExnrtS O1HmpCcTdFuP9ivotA5ordn8jmP7Td2ydP+VWquFGvSDyZSdOWnrK3ZYxBHkm3nQco AfLubp0/MF+yBYWuc7vvFEmQBCUxQUMDsq4AfygA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b304d23dfc6_7e683fce7c0e4f7c371764"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 25 Jun 2018 02:02:14 -0000 ----==_mimepart_5b304d23dfc6_7e683fce7c0e4f7c371764 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 2473966 The online editor is terrible -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1450/files/a2aabfe9e6feec0eaab59af0f4a0c212190b4474..2473966033d8f2d75a37113e723d05be42b20f38 ----==_mimepart_5b304d23dfc6_7e683fce7c0e4f7c371764 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 2473966 The online editor is terrible

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b304d23dfc6_7e683fce7c0e4f7c371764-- From nobody Sun Jun 24 19:26:30 2018 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 6AE73130E87 for ; Sun, 24 Jun 2018 19:26:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Ety7vK0PS5OH for ; Sun, 24 Jun 2018 19:26:27 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 771181277BB for ; Sun, 24 Jun 2018 19:26:27 -0700 (PDT) Date: Sun, 24 Jun 2018 19:26:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529893586; bh=K9boEzwmyaLmAsjv2xmUbOox661akf93GKJuopncCKQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PhJZkJJ6z61D1i7FAhw7VzXpnM89byiKq/qMwsbAEyXhT4WvidJFW5pLCHCHlLx97 smMWeTy/IQJ9QFaLt7BxpXnFfbx9ZdFKIoACCd81h0G8lcI4B6Agn86DjQBZ+W/1vO e4ZdSMDUYYPWN3n0KHM2Z+w2AGU+oIxqcO1WpSxk= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3052d271cba_26092adf41b54f502343"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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, 25 Jun 2018 02:26:30 -0000 ----==_mimepart_5b3052d271cba_26092adf41b54f502343 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > -When the alarm fires, the sender MUST retransmit all unacknowledged handshake -data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive -firing of the handshake alarm, the sender SHOULD double the handshake timeout -and set an alarm for this period. +When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active +unless the CRYPTO_HS frames were sent at 1RTT encryption. @ianswett: ^^? -- 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/1450#discussion_r197666160 ----==_mimepart_5b3052d271cba_26092adf41b54f502343 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-recovery.md:

>  
-When the alarm fires, the sender MUST retransmit all unacknowledged handshake
-data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive
-firing of the handshake alarm, the sender SHOULD double the handshake timeout
-and set an alarm for this period.
+When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active
+unless the CRYPTO_HS frames were sent at 1RTT encryption.

@ianswett: ^^?

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

----==_mimepart_5b3052d271cba_26092adf41b54f502343-- From nobody Sun Jun 24 19:26:43 2018 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 65E7B130E89 for ; Sun, 24 Jun 2018 19:26:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jBb0qu9TPEP3 for ; Sun, 24 Jun 2018 19:26:38 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 778D51277BB for ; Sun, 24 Jun 2018 19:26:38 -0700 (PDT) Date: Sun, 24 Jun 2018 19:26:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529893597; bh=4rEt3zYHd0nVTK+g3dcemyx3rNOy5Od2FUnLM+VEEOc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FDfesMa12cD25f5zBjHSJQDtWRuUrn+ZAocOIOu/3Fp8TsLTaIwQForD5JkNEMd8N B+PzEc8e9iDaUlfGvau0x16LGMrs1BcG/6cP3dI/RWWkhrTI/7oIOk7r0TBJ2G8qce lS0q/xUK+xzCrsc72fWNsgfWxeSIxz+yilDp2xsU= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3052ddc8ff8_13292af4df7aef505155e3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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, 25 Jun 2018 02:26:42 -0000 ----==_mimepart_5b3052ddc8ff8_13292af4df7aef505155e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > @@ -422,6 +441,14 @@ sending any ACK frames in response. In this case they can determine whether an immediate or delayed acknowledgement should be generated after processing incoming packets. +### Crypto Handshake Data + +In order to quickly complete the handshake and avoid spurious +retransmissions due to handshake alarm timeouts, handshake packets +SHOULD use a very short ack delay, such as 1ms. ACK frames MAY be It does seem like this should be a SHOULD -- 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/1450#discussion_r197666178 ----==_mimepart_5b3052ddc8ff8_13292af4df7aef505155e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -422,6 +441,14 @@ sending any ACK frames in response.  In this case they can determine
 whether an immediate or delayed acknowledgement should be generated
 after processing incoming packets.
 
+### Crypto Handshake Data
+
+In order to quickly complete the handshake and avoid spurious
+retransmissions due to handshake alarm timeouts, handshake packets
+SHOULD use a very short ack delay, such as 1ms.  ACK frames MAY be

It does seem like this should be a SHOULD

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

----==_mimepart_5b3052ddc8ff8_13292af4df7aef505155e3-- From nobody Sun Jun 24 19:31:27 2018 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 A0944130E97 for ; Sun, 24 Jun 2018 19:31:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0HHETcW3go_Y for ; Sun, 24 Jun 2018 19:31:16 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 363CF130ECC for ; Sun, 24 Jun 2018 19:31:11 -0700 (PDT) Date: Sun, 24 Jun 2018 19:31:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529893870; bh=vRrb+LoEk5N9uTamU5H8eA3ChuxFofYW3zAg5PSXxk0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CJNXx/HXBe9MgsVzxpHATEbSOUu4UqKj7nFS9xzsG7ZtGQXWToTAQ1czNAa/ivz8z vnzK7XlB6J4JTl3MsadE1loclSoabBcXvYEpg5PTVXkeU4aaSwMurlBMfDyGeEf6+Y BlGma0tEAaxZuwgmK5c4OTTjiSgnSsUklZKR0qoM= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3053ee6e08b_442e2ae49be98f544680a2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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, 25 Jun 2018 02:31:25 -0000 ----==_mimepart_5b3053ee6e08b_442e2ae49be98f544680a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past. ### ACK Frames and Packet Protection -ACK frames that acknowledge protected packets MUST be carried in a packet that -has an equivalent or greater level of packet protection. - -Packets that are protected with 1-RTT keys MUST be acknowledged in packets that -are also protected with 1-RTT keys. - -A packet that is not protected and claims to acknowledge a packet number that -was sent with packet protection is not valid. An unprotected packet that -carries acknowledgments for protected packets MUST be discarded in its entirety. +ACK frames MUST only be carried in a packet that has the same packet I guess this may be a terminology issue. Let me try to explain what I am saying again. Say I receive the following packets 2:1, 2:2, 3:1, 3:3 where X:Y means "epoch X, PN Y". And then I screw up and ACK PN space 3 in epoch 2, so I send epoch=2: ACK[3, 1]. Technically, this means "Acknowledge PNs 3 and 1 in epoch 2", so it's not a cross-ACK from the receiver's perspective, but it *is* an ACK of an unsent packet, which at least at some times we have thought was grounds for tearing down a connection. -- 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/1450#discussion_r197666543 ----==_mimepart_5b3053ee6e08b_442e2ae49be98f544680a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past.
 
 ### ACK Frames and Packet Protection
 
-ACK frames that acknowledge protected packets MUST be carried in a packet that
-has an equivalent or greater level of packet protection.
-
-Packets that are protected with 1-RTT keys MUST be acknowledged in packets that
-are also protected with 1-RTT keys.
-
-A packet that is not protected and claims to acknowledge a packet number that
-was sent with packet protection is not valid.  An unprotected packet that
-carries acknowledgments for protected packets MUST be discarded in its entirety.
+ACK frames MUST only be carried in a packet that has the same packet

I guess this may be a terminology issue. Let me try to explain what I am saying again.

Say I receive the following packets 2:1, 2:2, 3:1, 3:3 where X:Y means "epoch X, PN Y". And then I screw up and ACK PN space 3 in epoch 2, so I send epoch=2: ACK[3, 1]. Technically, this means "Acknowledge PNs 3 and 1 in epoch 2", so it's not a cross-ACK from the receiver's perspective, but it is an ACK of an unsent packet, which at least at some times we have thought was grounds for tearing down a connection.

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

----==_mimepart_5b3053ee6e08b_442e2ae49be98f544680a2-- From nobody Sun Jun 24 20:58:32 2018 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 A31121277C8 for ; Sun, 24 Jun 2018 20:58:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 h_xEDdnnU7IC for ; Sun, 24 Jun 2018 20:58:28 -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 CE75B127598 for ; Sun, 24 Jun 2018 20:58:28 -0700 (PDT) Date: Sun, 24 Jun 2018 20:58:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529899107; bh=TT69zv//VczBSR9EtCdXBWPd8O18JQoxHQyo4/77GOo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KFfKzG9ycqU7zJnrtdMH5Tzrq/XRZm/3AcUep8RSI5XlEVj4Rs/xllycE5MJWXXDc 00BaM/j+aYVdBh0EfIuAQWx5iZcsKovPSRHRj0AjjFM58mKXQ4eEzlWlp3nzbueOoN jTefJ3wpqbqevOkIJyJL+9/b114HlbV2FnpuSm3I= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3068635e189_6dc23f92ffea6f88116405a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 03:58:31 -0000 ----==_mimepart_5b3068635e189_6dc23f92ffea6f88116405a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past. ### ACK Frames and Packet Protection -ACK frames that acknowledge protected packets MUST be carried in a packet that -has an equivalent or greater level of packet protection. - -Packets that are protected with 1-RTT keys MUST be acknowledged in packets that -are also protected with 1-RTT keys. - -A packet that is not protected and claims to acknowledge a packet number that -was sent with packet protection is not valid. An unprotected packet that -carries acknowledgments for protected packets MUST be discarded in its entirety. +ACK frames MUST only be carried in a packet that has the same packet Yeah, I think that there are two statements to make, each of which differs from the one you chose. 1. An endpoint MUST NOT acknowledge packets you haven't received (and processed). 2. An ACK frame can only acknowledges packets from the same packet number space. The conjunction of these two things is what you are getting at: if you receive a packet in one packet number space, you cannot acknowledge it in a different space because that would be acknowledging a different packet, one you might not have received. -- 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/1450#discussion_r197674413 ----==_mimepart_5b3068635e189_6dc23f92ffea6f88116405a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2849,43 +3014,19 @@ received packets in preference to packets received in the past.
 
 ### ACK Frames and Packet Protection
 
-ACK frames that acknowledge protected packets MUST be carried in a packet that
-has an equivalent or greater level of packet protection.
-
-Packets that are protected with 1-RTT keys MUST be acknowledged in packets that
-are also protected with 1-RTT keys.
-
-A packet that is not protected and claims to acknowledge a packet number that
-was sent with packet protection is not valid.  An unprotected packet that
-carries acknowledgments for protected packets MUST be discarded in its entirety.
+ACK frames MUST only be carried in a packet that has the same packet

Yeah, I think that there are two statements to make, each of which differs from the one you chose.

  1. An endpoint MUST NOT acknowledge packets you haven't received (and processed).
  2. An ACK frame can only acknowledges packets from the same packet number space.

The conjunction of these two things is what you are getting at: if you receive a packet in one packet number space, you cannot acknowledge it in a different space because that would be acknowledging a different packet, one you might not have received.

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

----==_mimepart_5b3068635e189_6dc23f92ffea6f88116405a-- From nobody Mon Jun 25 00:12:31 2018 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 515201292F1 for ; Mon, 25 Jun 2018 00:12:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 dy60BUM-_XmR for ; Mon, 25 Jun 2018 00:12:28 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 95614127598 for ; Mon, 25 Jun 2018 00:12:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529910747; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=IdyRDGVXwqbYJ7fcxX0YB6rRiB7FjsXqncx5T7WbsMI=; b=Qjq7VLR6JhHeYNFWonxTMW7oNNiJsyCdcPktcn4fszsBLkTY2DEL3vhoq/J7S/UMjGqzy5Sn aZZzrlQpFH/WmrdFncEahmXIewOKdgzkZGUC9kXjhUISsWbgQfd50fbx+mrQJ3h6Rjn6hf0/ +5P6k55xUv7dk1hhGtA/FZGVk/g= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3095da.7f7dbe5b2720-smtp-out-n03; Mon, 25 Jun 2018 07:12:26 -0000 (UTC) Date: Mon, 25 Jun 2018 00:12:26 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3095dad9de9_2c712b28240dbc1417176@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e4725a: Extension frames Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3095dad9a99_2c712b28240dbc1417092"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 25 Jun 2018 07:12:31 -0000 ----==_mimepart_5b3095dad9a99_2c712b28240dbc1417092 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts Commit: e4725aca6943b04e1ef7f347a0fea5ade6313741 https://github.com/quicwg/base-drafts/commit/e4725aca6943b04e1ef7f347a0fea5ade6313741 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Extension frames Closes #58, #1072, #1068. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3095dad9a99_2c712b28240dbc1417092-- From nobody Mon Jun 25 00:17:50 2018 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 B6B69127598 for ; Mon, 25 Jun 2018 00:17:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HACzeWUTxN3N for ; Mon, 25 Jun 2018 00:17:47 -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 1C165124D68 for ; Mon, 25 Jun 2018 00:17:47 -0700 (PDT) Date: Mon, 25 Jun 2018 00:17:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529911066; bh=jbZlkgE6Thg6TOCpWYTGFrkk3OXuiBrh+nutXjhRXrA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=hyOUb+JVeq0EjUdM/xPa/RtkMtd2Y/ZQyzLWSYOWMXeJCORA5bXVpj4+V71BLHqjJ cVg842mfn3FBBRGtHEoVDFpFOUggZVKBeBi+vfK2gvDvqnj8A4NQlKnFnq9mZda5He wceNsqL1HRPrO27uUXmSkTqFUcDTYo3B1tGaI5do= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30971a38aa6_37123faf7a2c6f784622f3"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 07:17:49 -0000 ----==_mimepart_5b30971a38aa6_37123faf7a2c6f784622f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is the outcome we discussed in Kista. One tweak here is to avoid allowing variant variable-length integer encodings. The definition of variable-length integers would allow for four different encodings of the core set of frame types, which would require recipients to modify their code to look at more than one octet. For instance, ping is 0x07, 0x4007, 0x80000007, and 0xc000000000000007. I think that it's easier for all involved not to have to worry about long encodings until they want to experiment. I'm flexible on that point, as I am with respect to registration policies. Closes #58, #1072, #1068. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1473 -- Commit Summary -- * Extension frames -- File Changes -- M draft-ietf-quic-transport.md (85) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1473.patch https://github.com/quicwg/base-drafts/pull/1473.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/1473 ----==_mimepart_5b30971a38aa6_37123faf7a2c6f784622f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is the outcome we discussed in Kista.

One tweak here is to avoid allowing variant variable-length integer encodings. The definition of variable-length integers would allow for four different encodings of the core set of frame types, which would require recipients to modify their code to look at more than one octet. For instance, ping is 0x07, 0x4007, 0x80000007, and 0xc000000000000007. I think that it's easier for all involved not to have to worry about long encodings until they want to experiment.

I'm flexible on that point, as I am with respect to registration policies.

Closes #58, #1072, #1068.

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

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

Commit Summary

  • Extension frames

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 mute the thread.

----==_mimepart_5b30971a38aa6_37123faf7a2c6f784622f3-- From nobody Mon Jun 25 01:27:51 2018 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 A67731292F1 for ; Mon, 25 Jun 2018 01:27:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 zOrGeSg56lm3 for ; Mon, 25 Jun 2018 01:27:48 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03B5A1277C8 for ; Mon, 25 Jun 2018 01:27:48 -0700 (PDT) Date: Mon, 25 Jun 2018 01:27:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529915266; bh=zWE52wtgYxXzxWg6cRU07+5F7pa5Se6wSVV+t4q+LXI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=K0DJe/IBA25jKL2+ThTKiljX7AUUzDPy4ZNMnoJ8f1yMkVj0wSmRnL+4L7dvrIF9M oa4XqiV1+oaUt2k5BRj7KIUrlMR5ZObz+cZnEA3teF0oGz/vnpDijlVfZ8Mr/S/O20 +Cn/L5ICIv89YgomtiY+d+76WyVdp84rXFrBro4k= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30a782a988b_4653fec1ce28f7c6821a1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 25 Jun 2018 08:27:50 -0000 ----==_mimepart_5b30a782a988b_4653fec1ce28f7c6821a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @gloinul pushed 1 commit. cf312f9 Merged ECN counters into single ACK frame section and move them before the ACK Block Count. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1372/files/f8d3d5c6040ad0da6595cf07019d5c4f755aa0f3..cf312f90a6d844953e35a095d411e20965724124 ----==_mimepart_5b30a782a988b_4653fec1ce28f7c6821a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul pushed 1 commit.

  • cf312f9 Merged ECN counters into single ACK frame section and move them before the ACK Block Count.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b30a782a988b_4653fec1ce28f7c6821a1-- From nobody Mon Jun 25 01:30:50 2018 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 0649C1292F1 for ; Mon, 25 Jun 2018 01:30:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1Gp_Xybdnj7k for ; Mon, 25 Jun 2018 01:30:46 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459921277C8 for ; Mon, 25 Jun 2018 01:30:46 -0700 (PDT) Date: Mon, 25 Jun 2018 01:30:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529915445; bh=lD/saCPkr5lDNlq5vasTFb5IoC9CAg5lUyjQZjqGlsw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zfOcngR0cPAxz4z/zVJHMB029FSJv0sGHa+5BiPYsciiz89jOVU0SE/RNYBm7GCk7 iiyxgrGuRYFMJ9tfXZMQv1IR837yyedDFl9z9CRct3auNX/3wr5vVFHJ9hYalVGs9H aPQQqcAja70fKrq6Yrl31sVz6tTbmsZrVSE/WhS0= From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30a8357361e_3b662b0fe4032f545340bc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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.26 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, 25 Jun 2018 08:30:49 -0000 ----==_mimepart_5b30a8357361e_3b662b0fe4032f545340bc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit gloinul commented on this pull request. > @@ -2999,10 +2999,10 @@ appended at the end. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACK Block Count (i) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Yes, I merged the ECN counters and text into a single section for the ACK_ECN frame. I think that is very reasonable. So please check this latest 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/pull/1372#discussion_r197715962 ----==_mimepart_5b30a8357361e_3b662b0fe4032f545340bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@gloinul commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2999,10 +2999,10 @@ appended at the end.
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                       ACK Block Count (i)                   ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Yes, I merged the ECN counters and text into a single section for the ACK_ECN frame. I think that is very reasonable. So please check this latest change.

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

----==_mimepart_5b30a8357361e_3b662b0fe4032f545340bc-- From nobody Mon Jun 25 02:11:30 2018 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 38965130D7A for ; Mon, 25 Jun 2018 02:11:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qcfsWJW8LFfU for ; Mon, 25 Jun 2018 02:11:27 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDD6A1277C8 for ; Mon, 25 Jun 2018 02:11:26 -0700 (PDT) Date: Mon, 25 Jun 2018 02:11:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529917885; bh=/EZPH/kwl63E4irIj9GBJFcSGMVMiNWvn7BQhnFO5cg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ibBEg9CmPhH4Y0cBH+TDgDcvR47xyT5Q5HgoGjiwJ3XImeJyqSk3xrsD+nciHXcnJ 47qiawYg1/7iQTND4VWvuolo5lml2Y0ZzzGECN4P3MZgDvcuU5EMSoaNQ5ZVxEOv6f Rfhl9bbmgg0DbUJSogV2w/crL/oovIQX873H4SWw= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30b1bdeab84_b1d3fed0739ef8410350d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 25 Jun 2018 09:11:28 -0000 ----==_mimepart_5b30b1bdeab84_b1d3fed0739ef8410350d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'd definitely prefer a few code points for var length for example 0xfd for a single octet following. 0xfe for two octest following, and 0xff for a varint following. This will use much less space in the average case. -- 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/1473#issuecomment-399884958 ----==_mimepart_5b30b1bdeab84_b1d3fed0739ef8410350d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'd definitely prefer a few code points for var length for example 0xfd for a single octet following. 0xfe for two octest following, and 0xff for a varint following. This will use much less space in the average case.

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

----==_mimepart_5b30b1bdeab84_b1d3fed0739ef8410350d0-- From nobody Mon Jun 25 02:27:03 2018 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 7E7311277C8 for ; Mon, 25 Jun 2018 02:27:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Yo3L97TEsmAC for ; Mon, 25 Jun 2018 02:26:59 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CDC6130DC0 for ; Mon, 25 Jun 2018 02:26:59 -0700 (PDT) Date: Mon, 25 Jun 2018 02:26:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529918818; bh=9rzxbwliCM+kKPv0zNHI+ExWg1SuvTXJ4vxaBR1hVNY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=frWYksajK4pE/YAzZB2Z2SIOwtYDvC/g6ZRnlpCjofTU+QbhdYdVuXRy4OEUqBoIM PzE58bJ6s680YtYTIbohUJO+MFGOpSLyYFUgYphiXGCJ1YYXGff7a4kss3W1E9ULHd 8v9Ab7WNhLEdqz2klZHKTFJWOAB8rO6kaskwmAhE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30b5625e664_15d93fc9ab69cf80964e7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 09:27:01 -0000 ----==_mimepart_5b30b5625e664_15d93fc9ab69cf80964e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @mikkelfj, I didn't want to invent another encoding here. That's fun and all, but the encoding we have has ample space. The cost here is that the number of one-octet encodings is limited to 64. -- 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/1473#issuecomment-399889457 ----==_mimepart_5b30b5625e664_15d93fc9ab69cf80964e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj, I didn't want to invent another encoding here. That's fun and all, but the encoding we have has ample space. The cost here is that the number of one-octet encodings is limited to 64.

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

----==_mimepart_5b30b5625e664_15d93fc9ab69cf80964e7-- From nobody Mon Jun 25 02:43:39 2018 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 5FC01130DC0 for ; Mon, 25 Jun 2018 02:43:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ZKvtbFXRsqnE for ; Mon, 25 Jun 2018 02:43:36 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6E1812F1AB for ; Mon, 25 Jun 2018 02:43:35 -0700 (PDT) Date: Mon, 25 Jun 2018 02:43:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529919814; bh=HhY101QvRK8BGKHcehK8nefhAUb1ewR0o/GXz2RJwUE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WRFO3zaHh3+t9fQHG3Ske2JgwRlMSh/Hzih5fZiTSr1Sj9WGF2uiy7QJ/SCRFmmuS 8V9zoHukqzoPwmMK8IFwnJuAAHervMRywoKDw7RrEJBRu6+CfQCBcnwS1CTfxmh3Fp KorV376wxahLSxMMNP6126Tr4UGhIiaWvmrarcCs= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30b94694045_60242ac461ecef50149855"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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, 25 Jun 2018 09:43:38 -0000 ----==_mimepart_5b30b94694045_60242ac461ecef50149855 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fair point. Each length could be explicitly placed in its own namespace by mapping all frames to 64-bit including the length encoding. This makes PING unique and other values easy to index. Another fun encoding would be an FNV1a-64 hash of the reverse org name to use as a base for extensions where the upper two bits clamped to 1. Each such name reserving 100 sequential values. -- 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/1473#issuecomment-399894115 ----==_mimepart_5b30b94694045_60242ac461ecef50149855 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Fair point.

Each length could be explicitly placed in its own namespace by mapping= all frames to 64-bit including the length encoding. This makes PING uniq= ue and other values easy to index.

Another fun encoding would be an FNV1a-64 hash of the reverse org name= to use as a base for extensions where the upper two bits clamped to 1. E= ach such name reserving 100 sequential values.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b30b94694045_60242ac461ecef50149855-- From nobody Mon Jun 25 02:47:59 2018 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 61A3B12F1A5 for ; Mon, 25 Jun 2018 02:47:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 SJPKrk4Jo-rc for ; Mon, 25 Jun 2018 02:47:55 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B84851277C8 for ; Mon, 25 Jun 2018 02:47:55 -0700 (PDT) Date: Mon, 25 Jun 2018 02:47:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529920075; bh=HAUTZ5kQFwekYa0zAnu+dJIsjuvTl7rd/3DQa1PIYf0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hqaj020Kza41SEoIJqkB92owFlRvvAzeV0Bc5Rcyk94BIRDepvwdk7j8WJ4Z/9CIV YHXeijzv4dMn9RI0mCXb+Yuh12LkRv6QxyOAG1w+ABUxlrRcDwOa6xCAZx/H0iQ624 uc0J657EyQuznJdpKQ9DSa1xQoMrEq87LalWlu7o= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30ba4b1c7ff_60092ac461ecef50171723"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 09:47:58 -0000 ----==_mimepart_5b30ba4b1c7ff_60092ac461ecef50171723 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson approved this pull request. More changes. Interop gets that much further away. -- 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/1472#pullrequestreview-131537303 ----==_mimepart_5b30ba4b1c7ff_60092ac461ecef50171723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson approved this pull request.

More changes. Interop gets that much further away.

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

----==_mimepart_5b30ba4b1c7ff_60092ac461ecef50171723-- From nobody Mon Jun 25 06:31:30 2018 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 EC3CD130DF0 for ; Mon, 25 Jun 2018 06:31:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FOIumWWBIBJO for ; Mon, 25 Jun 2018 06:31:27 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98FE4130DED for ; Mon, 25 Jun 2018 06:31:27 -0700 (PDT) Date: Mon, 25 Jun 2018 06:31:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529933486; bh=NUS5/7xkqmbd/L7+LfaAGePQJh3LTVEUxsgIyAPgdKQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=KCh9o9CTDna0CWM2UwSF8fVbZr53Ne8lLXFumA/TD3mSH9cY+agFCgGJk/J0zk8OO TYbXC7lZc6672eCwfzbTWfhlhB7MPE5RjI8IMzlrZSGYnNPGiIyYXFs68MiWs4zf6D i140vE7Q2He22Q4eEzbFMby7je1tL8nCHGM+DPN0= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Retry Token Makeup (#1474) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30eeae96bf0_58462ac61bdacf588644f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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, 25 Jun 2018 13:31:29 -0000 ----==_mimepart_5b30eeae96bf0_58462ac61bdacf588644f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This issue is related to the new Stream 0 dt PR (#1450). Is a client allowed to change its connection ID in response to a Retry packet from a server? The reason I ask is that it is possible to conceive of a server generating a token for a stateless Retry that encodes the client's original CID (among other things) in it for validation purposes. If the client is allowed to change its CID, then that obviously would break. So I feel we should have text either explicitly saying the client may (which I don't see how we could prevent) change its CID, and that a server shouldn't try to use the CID for stateless Retry validation or that a client must not change its CID so the server can use it for validation in stateless Retry. -- 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/1474 ----==_mimepart_5b30eeae96bf0_58462ac61bdacf588644f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This issue is related to the new Stream 0 dt PR (#1450).

Is a client allowed to change its connection ID in response to a Retry packet from a server?

The reason I ask is that it is possible to conceive of a server generating a token for a stateless Retry that encodes the client's original CID (among other things) in it for validation purposes. If the client is allowed to change its CID, then that obviously would break. So I feel we should have text either explicitly saying the client may (which I don't see how we could prevent) change its CID, and that a server shouldn't try to use the CID for stateless Retry validation or that a client must not change its CID so the server can use it for validation in stateless Retry.

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

----==_mimepart_5b30eeae96bf0_58462ac61bdacf588644f-- From nobody Mon Jun 25 07:19:32 2018 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 18644130EEA for ; Mon, 25 Jun 2018 07:19:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 9Znf3n5ZOCEn for ; Mon, 25 Jun 2018 07:19:20 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995E2130EDF for ; Mon, 25 Jun 2018 07:19:18 -0700 (PDT) Date: Mon, 25 Jun 2018 07:19:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529936357; bh=F+3nD2rfq2kB/oaTAa05Mj7tDDTzPzvSMnBQvHdvm0M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uKaHYWETj3VKM1hl1f9Q2H6zmQJIILeGLYwvJGJR7QWEcCyo0QSAlasj66GLWD/Hn 8VXAw6aD72wem3zCec5vciGWdu+OyLWmwYay4HlLfKqX8IhnE5yiMRFKjMqTpWdf8Z ayq8BGzW/2XfD6BB/EVQxy9knIL/0TP8rIHhWXro= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b30f9e5b1a50_457f3fe170e1cf80235433"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 25 Jun 2018 14:19:30 -0000 ----==_mimepart_5b30f9e5b1a50_457f3fe170e1cf80235433 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. Thanks for the update, looks good. -- 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/1372#pullrequestreview-131629374 ----==_mimepart_5b30f9e5b1a50_457f3fe170e1cf80235433 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

Thanks for the update, looks good.

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

----==_mimepart_5b30f9e5b1a50_457f3fe170e1cf80235433-- From nobody Mon Jun 25 08:24:00 2018 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 137C8130E04 for ; Mon, 25 Jun 2018 08:23:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 5IM0FeiV5Yjy for ; Mon, 25 Jun 2018 08:23:57 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1CC130E01 for ; Mon, 25 Jun 2018 08:23:57 -0700 (PDT) Date: Mon, 25 Jun 2018 08:23:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529940236; bh=fFYI5IAqnSA4vCk4xFPSq4TbGN1NbZqG2zU28KvptVE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SQAOj8oe4rhDro3urc9XRfreXmijsb3rg6og1OIUIntKvU0OOoKMI2UrEuQw+5Ew8 lDVSi6/pOWamsxKatef0XDXmz1tN3eHCz6Qh+ejTKzm2LZ8ToyKeKjteHjbUk7ya9Q kOIJojIknSbR+e5k8AQ++4WusHgZhfk/Hz3xLl3I= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31090c3c92_3e113fbb0cacaf8883226"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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, 25 Jun 2018 15:24:00 -0000 ----==_mimepart_5b31090c3c92_3e113fbb0cacaf8883226 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > -When the alarm fires, the sender MUST retransmit all unacknowledged handshake -data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive -firing of the handshake alarm, the sender SHOULD double the handshake timeout -and set an alarm for this period. +When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active +unless the CRYPTO_HS frames were sent at 1RTT encryption. I was intending it to be encryption level, since I thought it was necessary to send end of early data in a timely manner? But maybe it doesn't matter that much? It's possible a signal that the handshake is complete would be preferable to monitoring what encryption level CRYPTO_HS is sent at, but I'll just make it consistent for now. -- 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/1450#discussion_r197837633 ----==_mimepart_5b31090c3c92_3e113fbb0cacaf8883226 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

>  
-When the alarm fires, the sender MUST retransmit all unacknowledged handshake
-data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive
-firing of the handshake alarm, the sender SHOULD double the handshake timeout
-and set an alarm for this period.
+When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active
+unless the CRYPTO_HS frames were sent at 1RTT encryption.

I was intending it to be encryption level, since I thought it was necessary to send end of early data in a timely manner? But maybe it doesn't matter that much?

It's possible a signal that the handshake is complete would be preferable to monitoring what encryption level CRYPTO_HS is sent at, but I'll just make it consistent for now.

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

----==_mimepart_5b31090c3c92_3e113fbb0cacaf8883226-- From nobody Mon Jun 25 09:58:28 2018 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 0E899130EF4 for ; Mon, 25 Jun 2018 09:58:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 e1MpADRbFc5B for ; Mon, 25 Jun 2018 09:58:15 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F154F130EDB for ; Mon, 25 Jun 2018 09:58:14 -0700 (PDT) Date: Mon, 25 Jun 2018 09:58:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529945894; bh=V+eW+V4rhTZMs3u036wuVekZRr/gXZMfVkelVsZKyAs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=J3NT1pTIw3nxdcjmsdJdENbpYCLzjET0o1tq44Uu8QjGlZMMu1bGB/5tU2IujXeOb gXLP7dDK4CHK6Chbyro+q9NGjkX4iIPekFM75Qzcmy54qrnFbv2E7aF1h4tQJ3DORo EY4mzPX6eCdV6WcUZ3Fw0ltu1Z7l/gNitrNWV9q4= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b311f2625003_7d3b3fbca6262f80542840"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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, 25 Jun 2018 16:58:27 -0000 ----==_mimepart_5b311f2625003_7d3b3fbca6262f80542840 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm not concerned about this change delaying interop dramatically. Implicit acks landed last week and was a bigger 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/pull/1472#issuecomment-400022519 ----==_mimepart_5b311f2625003_7d3b3fbca6262f80542840 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm not concerned about this change delaying interop dramatically. Implicit acks landed last week and was a bigger change.

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

----==_mimepart_5b311f2625003_7d3b3fbca6262f80542840-- From nobody Mon Jun 25 12:59:13 2018 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 8A7E7130E5D for ; Mon, 25 Jun 2018 12:59:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 iLAGqrIbWA6t for ; Mon, 25 Jun 2018 12:59:09 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 18C84130E33 for ; Mon, 25 Jun 2018 12:59:09 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529956748; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=3rbCPZHM4K4OP+G5gnuG5Sp6le5Gwz+spaOTy32N4ms=; b=SiX66X7y/6T8jwmS8im8K0KmAdN8/EfHbbyU0N3d5YehCn1ELljbmQebDh9rxo7K1exF88QG icirWJJztVAd5Xva4oxu+GMfmXFDkawCB2OxNanELET8uSfecGnW+nbshjO3eL03AIdAaAV3 J40MHcJxO453DOuuDxfvt0sVbps= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=fb.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b31498c.7f38fc8b1e10-smtp-out-n02; Mon, 25 Jun 2018 19:59:08 -0000 (UTC) Date: Mon, 25 Jun 2018 12:59:07 -0700 From: Alan Frindell Reply-To: Alan Frindell To: quic-issues@ietf.org Message-ID: <5b31498be7a95_18922b1735a39c0c62444@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 5a38c9: Swap TSS and Stream Cancellation codepoints Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b31498be7621_18922b1735a39c0c6236d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 25 Jun 2018 19:59:11 -0000 ----==_mimepart_5b31498be7621_18922b1735a39c0c6236d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-codepoints Home: https://github.com/quicwg/base-drafts Commit: 5a38c97d2c208743bdb916d6af0d3b33b7afc2a8 https://github.com/quicwg/base-drafts/commit/5a38c97d2c208743bdb916d6af0d3b33b7afc2a8 Author: Alan Frindell Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Swap TSS and Stream Cancellation codepoints This is somewhat superficial, but we're changing it anyways so bear with me. HEADER_ACK and STREAM_CANCEL are almost identical, so code processing them should be next to each other. By swapping TSS and Stream Cancel codepoints, the processing code might be more readable. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b31498be7621_18922b1735a39c0c6236d-- From nobody Mon Jun 25 12:59:19 2018 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 20F07130EDD for ; Mon, 25 Jun 2018 12:59:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pKLt2MhM7W2S for ; Mon, 25 Jun 2018 12:59:13 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39E9C130E3E for ; Mon, 25 Jun 2018 12:59:13 -0700 (PDT) Date: Mon, 25 Jun 2018 12:59:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529956751; bh=C/H1hLRvZBJwydcxuyCcarKuRN3z6PU/Ib8nhCi8b/g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mm4ysr2JBWxZx9hjw3HFOQavNzUsVIAm6w5EUaQhD+cnamwem1VPEhgXKqI+Ex5J9 1FfEwyxT1tVeWepQX2AW8eHUbt2fmgxKvCNOigbbD9w3IWfCR3xr1AN9QDwvS3mxv0 8A/px2BPhf+HT4z6WH/KqIiSaAluJadPYabFriHY= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31498fcdd3b_ca42abbfbd0cf50136218"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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, 25 Jun 2018 19:59:16 -0000 ----==_mimepart_5b31498fcdd3b_ca42abbfbd0cf50136218 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @afrind pushed 1 commit. 5a38c97 Swap TSS and Stream Cancellation codepoints -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1472/files/eedc1d3ff8f1991272b4e59614294129c5f50e9d..5a38c97d2c208743bdb916d6af0d3b33b7afc2a8 ----==_mimepart_5b31498fcdd3b_ca42abbfbd0cf50136218 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@afrind pushed 1 commit.

  • 5a38c97 Swap TSS and Stream Cancellation codepoints

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b31498fcdd3b_ca42abbfbd0cf50136218-- From nobody Mon Jun 25 16:35:04 2018 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 4951F130E5C for ; Mon, 25 Jun 2018 16:35:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jTuIBz3srgST for ; Mon, 25 Jun 2018 16:35:00 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC54E130DFA for ; Mon, 25 Jun 2018 16:35:00 -0700 (PDT) Date: Mon, 25 Jun 2018 16:34:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529969699; bh=pcc4yRw4K3fAq/1Ah3yiuy4hWrtPbpH9QOId/ZH33/I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l8mm1ZjYwz4F+YqvER1GiUuVfMa6aN+UGw9PwMPQquE4jJDnxQrE3Q7AKfjyPa2HH vKS+fRD5NgRdkEXX2aQHzUTHveZ3P5Ozxpf14W4tAv7jT/os57TNW/zQVmO9f1JvK0 6IxWuChFS4B77BaveYlvE043q6co932U2V0XcKEs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b317c238c195_5c9d2b17f689cf541204c6"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 23:35:02 -0000 ----==_mimepart_5b317c238c195_5c9d2b17f689cf541204c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > -When the alarm fires, the sender MUST retransmit all unacknowledged handshake -data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive -firing of the handshake alarm, the sender SHOULD double the handshake timeout -and set an alarm for this period. +When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active +unless the CRYPTO_HS frames were sent at 1RTT encryption. Sounds reasonable. I just wanted to check. And yeah, we probably need to send EndOfEarlyData quickly. It blocks access to 1-RTT data just like Finished. -- 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/1450#discussion_r197973976 ----==_mimepart_5b317c238c195_5c9d2b17f689cf541204c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-recovery.md:

>  
-When the alarm fires, the sender MUST retransmit all unacknowledged handshake
-data, by calling RetransmitAllUnackedHandshakeData(). On each consecutive
-firing of the handshake alarm, the sender SHOULD double the handshake timeout
-and set an alarm for this period.
+When CRYPTO_HS frames are outstanding, the TLP and RTO timers are not active
+unless the CRYPTO_HS frames were sent at 1RTT encryption.

Sounds reasonable. I just wanted to check. And yeah, we probably need to send EndOfEarlyData quickly. It blocks access to 1-RTT data just like Finished.

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

----==_mimepart_5b317c238c195_5c9d2b17f689cf541204c6-- From nobody Mon Jun 25 16:52:32 2018 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 86A49130E5C for ; Mon, 25 Jun 2018 16:52:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 RmdNmgOpK2Mq for ; Mon, 25 Jun 2018 16:52:27 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 BD48D130F04 for ; Mon, 25 Jun 2018 16:52:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529970747; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=T9QKm7zu7VTvLvN62u1SNnhv2UvSyK7iycgUELEFPR4=; b=cGEc50oHNC3mEWJ8OBXutm4AZTzLafctc3jg0fu5sdnWZa3ty3Xg4N+uX7qLnKI7HFb1Rrn6 Mk/uwQFmwMNSKCKPtTDK7VJT4s1N3Isk2JyCn9Fk2e9V6MkL+J6mp98tOHiljsp2e19Rf2kV 52xytX2xhUdVVixb0v/kuTy/oR4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b31803a.7f7b23369e70-smtp-out-n02; Mon, 25 Jun 2018 23:52:26 -0000 (UTC) Date: Mon, 25 Jun 2018 16:52:25 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3180399c7a8_39f92aca2f729c0410304e@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 42f55d: Output of Stream 0 Design Team. Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3180399c24a_39f92aca2f729c04102962"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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, 25 Jun 2018 23:52:31 -0000 ----==_mimepart_5b3180399c24a_39f92aca2f729c04102962 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 42f55df78007dab2d02faf837eebed5e864d17ee https://github.com/quicwg/base-drafts/commit/42f55df78007dab2d02faf837eebed5e864d17ee Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Output of Stream 0 Design Team. See: https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit for design rationale. Commit: cab82952ab67bd994da0da4160af42f2e95a9850 https://github.com/quicwg/base-drafts/commit/cab82952ab67bd994da0da4160af42f2e95a9850 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fix changelog Commit: 984ecc86d259d76d8498f3b4990bb5cfdc10c448 https://github.com/quicwg/base-drafts/commit/984ecc86d259d76d8498f3b4990bb5cfdc10c448 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fix whitespace Commit: 36899e50d963d6d7aa427168d45311f444014bdf https://github.com/quicwg/base-drafts/commit/36899e50d963d6d7aa427168d45311f444014bdf Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Offset and length fields in CRYPTO_HS are not optional Commit: f8f172f52889036ddbc697165393194a28073b0d https://github.com/quicwg/base-drafts/commit/f8f172f52889036ddbc697165393194a28073b0d Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Remove EMPTY_ACK Commit: 70b26e8c3ae6b30acbcb9b915eac98e6757d2a5d https://github.com/quicwg/base-drafts/commit/70b26e8c3ae6b30acbcb9b915eac98e6757d2a5d Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md Log Message: ----------- Incorporate the comments from PR#1377 Commit: af70f236548b53a9a7ff69b4e52f850d1a350a57 https://github.com/quicwg/base-drafts/commit/af70f236548b53a9a7ff69b4e52f850d1a350a57 Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove EMPTY_ACK Commit: aa1b6834af8b327ef0ef761b9daede3447504deb https://github.com/quicwg/base-drafts/commit/aa1b6834af8b327ef0ef761b9daede3447504deb Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Update draft-ietf-quic-transport.md Commit: 927cf128a760708657f3d7ea76ba0495ed60af49 https://github.com/quicwg/base-drafts/commit/927cf128a760708657f3d7ea76ba0495ed60af49 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Add the TLS diagrams Commit: 74300a1be6e84f5deec8dcb513bc370433e1dca3 https://github.com/quicwg/base-drafts/commit/74300a1be6e84f5deec8dcb513bc370433e1dca3 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Redact diagram from the TLS doc Commit: 04fd3213c3873c7f8593a16115b36061421251a3 https://github.com/quicwg/base-drafts/commit/04fd3213c3873c7f8593a16115b36061421251a3 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Ian Swett's comments Commit: bf9c62cb42534d90efc7aae65e16c31b793a75b6 https://github.com/quicwg/base-drafts/commit/bf9c62cb42534d90efc7aae65e16c31b793a75b6 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- server-initiated streams start from 1 Commit: 77155f9f535fddf86c88bd18db0cce32edb66555 https://github.com/quicwg/base-drafts/commit/77155f9f535fddf86c88bd18db0cce32edb66555 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Remove last TODO Commit: 779b3a007bae19afeed9bd32d8f3bc58640f67d2 https://github.com/quicwg/base-drafts/commit/779b3a007bae19afeed9bd32d8f3bc58640f67d2 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Minor editorial Commit: d3b055a6e9afc403a9b0cb2862f09880938b5eb7 https://github.com/quicwg/base-drafts/commit/d3b055a6e9afc403a9b0cb2862f09880938b5eb7 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Remove the advice on how to use coalesced packets for recovery. This may be re-added in a future PR, but isn't part of the minimal set for the stream 0 DT. Commit: 48c9b9fde954d6a8b3a52e5ee7006fffd0c8a6ca https://github.com/quicwg/base-drafts/commit/48c9b9fde954d6a8b3a52e5ee7006fffd0c8a6ca Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Self-review, ready to submit Commit: 396c318dabd73952ee44b4bf1826aa28ebd19d8b https://github.com/quicwg/base-drafts/commit/396c318dabd73952ee44b4bf1826aa28ebd19d8b Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Some more cleanup Commit: 777114ac355c7a4b15dabd67122ca21c164e2e17 https://github.com/quicwg/base-drafts/commit/777114ac355c7a4b15dabd67122ca21c164e2e17 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Fix compile errors Commit: a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835 https://github.com/quicwg/base-drafts/commit/a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835 Author: ianswett Date: 2018-06-18 (Mon, 18 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Restore Generating Acknowledgements Commit: 6b363007d1875ffb02cf6f0c9006696c72a2cd0b https://github.com/quicwg/base-drafts/commit/6b363007d1875ffb02cf6f0c9006696c72a2cd0b Author: ianswett Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Mike's comments Commit: 0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d https://github.com/quicwg/base-drafts/commit/0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d Author: ekr Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #34 from ekr/ianswett-mike-comments Mike's comments Commit: 4065266b5a01d982ec01050305247d342e8cdff7 https://github.com/quicwg/base-drafts/commit/4065266b5a01d982ec01050305247d342e8cdff7 Author: ianswett Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fix retry and remove optimizations Commit: 954c585e680ca4bf8e2e18af57e5832b716d9fb7 https://github.com/quicwg/base-drafts/commit/954c585e680ca4bf8e2e18af57e5832b716d9fb7 Author: ekr Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #35 from ekr/ianswett-mike2 Fix retry and remove optimizations Commit: d814642dec0176287f81ac2b0391aa7d541850c8 https://github.com/quicwg/base-drafts/commit/d814642dec0176287f81ac2b0391aa7d541850c8 Author: ianswett Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Martin's comments Commit: da0d8ecff5905d4321db902c2df6a51846791fec https://github.com/quicwg/base-drafts/commit/da0d8ecff5905d4321db902c2df6a51846791fec Author: ianswett Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Ensures that Commit: 89c45a658dc9cfe765d1252050f7874fe27bfd2f https://github.com/quicwg/base-drafts/commit/89c45a658dc9cfe765d1252050f7874fe27bfd2f Author: ekr Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #36 from ekr/ianswett-martin Martin's comments Commit: daea8615f43545e42fda486d92b5ac6c4218e760 https://github.com/quicwg/base-drafts/commit/daea8615f43545e42fda486d92b5ac6c4218e760 Author: EKR Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Address MT's comments on TLS Commit: 3aea50db51a14f2b42ed8aea7dbeeea72c6321b4 https://github.com/quicwg/base-drafts/commit/3aea50db51a14f2b42ed8aea7dbeeea72c6321b4 Author: EKR Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- MT/Bishop comments on transport Commit: bd5f9ff36dd1fc11a14f8fccd7ff144482ed356f https://github.com/quicwg/base-drafts/commit/bd5f9ff36dd1fc11a14f8fccd7ff144482ed356f Author: EKR Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Ian's comments Commit: e2ed4db7df7d72a08fe13b8da8d17f6fca601c26 https://github.com/quicwg/base-drafts/commit/e2ed4db7df7d72a08fe13b8da8d17f6fca601c26 Author: ekr Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #37 from ekr/martins_comments Martins comments Commit: 7a780dbed8eed8ed9584db89215bd752dbf86c7a https://github.com/quicwg/base-drafts/commit/7a780dbed8eed8ed9584db89215bd752dbf86c7a Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Fix build breaks Commit: 4db556887313b51de0139bb7c6c7be33614c4ddb https://github.com/quicwg/base-drafts/commit/4db556887313b51de0139bb7c6c7be33614c4ddb Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Extra word Commit: 8d57711c819307c44cec8db2964a2a80c8f87ab9 https://github.com/quicwg/base-drafts/commit/8d57711c819307c44cec8db2964a2a80c8f87ab9 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- remove "the the" Commit: a2aabfe9e6feec0eaab59af0f4a0c212190b4474 https://github.com/quicwg/base-drafts/commit/a2aabfe9e6feec0eaab59af0f4a0c212190b4474 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- More errors around delivering to TLS out of order Commit: 2473966033d8f2d75a37113e723d05be42b20f38 https://github.com/quicwg/base-drafts/commit/2473966033d8f2d75a37113e723d05be42b20f38 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- The online editor is terrible Commit: ba809b106bac23ecf8b83e080c0e17f6814907f4 https://github.com/quicwg/base-drafts/commit/ba809b106bac23ecf8b83e080c0e17f6814907f4 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1450 from ekr/stream0_dt_output_for_merge Stream0 dt output for merge Compare: https://github.com/quicwg/base-drafts/compare/710b199b4534...ba809b106bac **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3180399c24a_39f92aca2f729c04102962-- From nobody Mon Jun 25 16:52:38 2018 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 EDEAC130E5C for ; Mon, 25 Jun 2018 16:52:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 5AAhAFhdb9Mk for ; Mon, 25 Jun 2018 16:52:30 -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 3630E130F07 for ; Mon, 25 Jun 2018 16:52:29 -0700 (PDT) Date: Mon, 25 Jun 2018 16:52:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529970748; bh=nWo4JIGEHkLXCZego+KNLmlXYEar0tkZ8otQ5t5207U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tK8UuNAPY0dHsLjiQ2Q3hUFQQYajRQHWRwUjgiau0HJMVTnJP1TeVkSlBnHUqi31y 5k84TOm4B81cSM4flvc97NaJK9YWdEtL3jbh1KlpzpfJqk7bXBfwyxkC+OaCFiMWrZ +SUehVP3PnnnE8dnYBoMK/jAnjtqRHI6tpXqOVXI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output for merge (#1450) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31803c66501_3f5b3fd51364af78349041"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 23:52:33 -0000 ----==_mimepart_5b31803c66501_3f5b3fd51364af78349041 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1450. -- 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/1450#event-1700170756 ----==_mimepart_5b31803c66501_3f5b3fd51364af78349041 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1450.

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

----==_mimepart_5b31803c66501_3f5b3fd51364af78349041-- From nobody Mon Jun 25 17:42:29 2018 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 5795A130F35 for ; Mon, 25 Jun 2018 17:42:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Q_NNPBzsv2ht for ; Mon, 25 Jun 2018 17:42:25 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 0024A130F05 for ; Mon, 25 Jun 2018 17:42:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529973744; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=xKfoiCuByRMX+L7UFkoehnj1agz6wtl8opZb83Aw68c=; b=K/HILnHbw13wjzXhAPx4CDPmzFP0nXiwda/l/WqZGDXKVbz7jtj3vCYqRugmYcw6u7xglb6h P8Jxiy+LVcWQRPLNRLnqQSIuPaeY4D4ydK+rm9DX6wlGk6TQwhB4z8VufwBQAvBWzKKBpi0A PfgES99iWQ8+Wcm2OcIzXToMZOQ= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b318bef.7f0a403dcf90-smtp-out-n02; Tue, 26 Jun 2018 00:42:23 -0000 (UTC) Date: Mon, 25 Jun 2018 17:42:22 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b318bee8ddfa_3f432ad1236f9c0c63537@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 5f438a: Defer artifact saving Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b318bee8d8e1_3f432ad1236f9c0c6343"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 00:42:26 -0000 ----==_mimepart_5b318bee8d8e1_3f432ad1236f9c0c6343 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 5f438af3c17cbd1f908f1806d33d58c340287cfa https://github.com/quicwg/base-drafts/commit/5f438af3c17cbd1f908f1806d33d58c340287cfa Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M .circleci/config.yml Log Message: ----------- Defer artifact saving **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b318bee8d8e1_3f432ad1236f9c0c6343-- From nobody Mon Jun 25 18:10:39 2018 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 E1EC5130E7D for ; Mon, 25 Jun 2018 18:10:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rtXxRH8doEsj for ; Mon, 25 Jun 2018 18:10:35 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60012130F43 for ; Mon, 25 Jun 2018 18:10:35 -0700 (PDT) Date: Mon, 25 Jun 2018 18:10:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529975434; bh=nSziFLtPJponUkpdw/fxK2a/7WizZHHbbE7WZD9VQAQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=04a2Jn943q6BrrgrpdO2+NdwMHc6PTg14GPBqqnc6IG1rt+xLevslmImGQceAlaxH EBuImKKNAa8dV5uqoSA3XuF05e8HgJPNtthFlyPHKxbFnQH8MoJOpY2bRW0NfBj85K yEiUyocsiwa+4/VZcG7yXUgFUez1NAP9RncdZNl8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] "Default" max ack delay (#1475) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31928a767d2_4c0d3ff4b104ef804919a9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 01:10:37 -0000 ----==_mimepart_5b31928a767d2_4c0d3ff4b104ef804919a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > The default maximum ack delay in QUIC is 25ms. We can't set defaults in a spec. We can recommend this as a sensible value though. -- 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/1475 ----==_mimepart_5b31928a767d2_4c0d3ff4b104ef804919a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The default maximum ack delay in QUIC is 25ms.

We can't set defaults in a spec. We can recommend this as a sensible value though.

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

----==_mimepart_5b31928a767d2_4c0d3ff4b104ef804919a9-- From nobody Mon Jun 25 18:11:28 2018 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 29267130F43 for ; Mon, 25 Jun 2018 18:11:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 NlbA0cW34_Uc for ; Mon, 25 Jun 2018 18:11:24 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 B1BB8130E7D for ; Mon, 25 Jun 2018 18:11:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529975484; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zTyTHcoPmAthLXsQ3gREfurqWHht4tTW7sS5VxTOLKc=; b=F4A+7erOAjOnJY6URPNmS5spWIFlF/AJp239iw8FTViK0z3fY5B3S+3Lez5gKoCLNFQoPwqR XHcBDLSt9QTA4LOIJUelVbRR+vx46BIkJpR6L19Er8TkyrEw/BoXazlgcTpR1PLyN4/DW00d SCuw0qefjR6uCOqDxRNZNzniXR4= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b3192bb.7f723618d630-smtp-out-n03; Tue, 26 Jun 2018 01:11:23 -0000 (UTC) Date: Mon, 25 Jun 2018 18:11:23 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3192bbdefa4_4f582abc65b11c18104174@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 3d1f00: Rename CRYPTO_HS to CRYPTO Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3192bbde9db_4f582abc65b11c1810407f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 01:11:26 -0000 ----==_mimepart_5b3192bbde9db_4f582abc65b11c1810407f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/crypto-cleanup Home: https://github.com/quicwg/base-drafts Commit: 3d1f0031440864bc1f48526be2a3379f6fe4aab6 https://github.com/quicwg/base-drafts/commit/3d1f0031440864bc1f48526be2a3379f6fe4aab6 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Rename CRYPTO_HS to CRYPTO Commit: 2378dc70f15dfd0c9b16aafb80912285bcfd579d https://github.com/quicwg/base-drafts/commit/2378dc70f15dfd0c9b16aafb80912285bcfd579d Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Reflow paragraphs Compare: https://github.com/quicwg/base-drafts/compare/3d1f00314408^...2378dc70f15d **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3192bbde9db_4f582abc65b11c1810407f-- From nobody Mon Jun 25 18:13:00 2018 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 2B844130F43 for ; Mon, 25 Jun 2018 18:12:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ceqIe11uNhFB for ; Mon, 25 Jun 2018 18:12:57 -0700 (PDT) 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 B8BDD130E7D for ; Mon, 25 Jun 2018 18:12:57 -0700 (PDT) Date: Mon, 25 Jun 2018 18:12:57 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529975577; bh=PCOgANBJQZO4XicVDhEQCwNyHyRGaDnhh8jXA1f3zu0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=pY3B1TqmAIKKS3PFpYIKvapk06EMSL4qlusIAq43lCPXJ2FgaIviPbduYZrUnZqvG uln4a8etBlSTwTtrsbbyN3kmh5V2BiH48RUeZAM5bbkzGTAhiiAu/OGbRKRhmhz/Zu WgZXt8ppiU6NWoPUFl9rl8Wk8oQdS8RW9ApmCJ6I= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31931915c04_5c812b17f689cf5447656b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 01:12:59 -0000 ----==_mimepart_5b31931915c04_5c812b17f689cf5447656b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is two changes: a mechanical renaming of CRYPTO_HS to CRYPTO. Then it's a reflowing of a bunch of paragraphs. Both are mechanical in nature, though I did notice and correct a couple of typos in the process (which I'll have to dig out if we decide this is a bad idea). You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1476 -- Commit Summary -- * Rename CRYPTO_HS to CRYPTO * Reflow paragraphs -- File Changes -- M draft-ietf-quic-recovery.md (220) M draft-ietf-quic-tls.md (438) M draft-ietf-quic-transport.md (363) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1476.patch https://github.com/quicwg/base-drafts/pull/1476.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/1476 ----==_mimepart_5b31931915c04_5c812b17f689cf5447656b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is two changes: a mechanical renaming of CRYPTO_HS to CRYPTO. Then it's a reflowing of a bunch of paragraphs. Both are mechanical in nature, though I did notice and correct a couple of typos in the process (which I'll have to dig out if we decide this is a bad idea).

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

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

Commit Summary

  • Rename CRYPTO_HS to CRYPTO
  • Reflow paragraphs

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 mute the thread.

----==_mimepart_5b31931915c04_5c812b17f689cf5447656b-- From nobody Mon Jun 25 18:30:47 2018 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 CC10B130F49 for ; Mon, 25 Jun 2018 18:30:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 P2a_VHwPdoJ6 for ; Mon, 25 Jun 2018 18:30:44 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 4FED6130E7F for ; Mon, 25 Jun 2018 18:30:44 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529976643; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=yvFxuOwKPuvweuXVCn+Oq6lI9wfuhshiwCNTkV/RO+I=; b=Ax8Vb6Py4zZFP41k47PJo8Lz7oC/buzhNRWETMqxcVA3xhypR1aiUPdFaOIe2R+vs+Y17abU OFZofq7PfnIYt6CYCntalnrM1uBqpB0vJHf9Y+3JKqfbcEbjR4VEqnpCV2tzvPPMZh8Fc1EP rdPmCLeRIN4rpYULk2HPG+j+akI= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b319742.7f41ba3ad600-smtp-out-n03; Tue, 26 Jun 2018 01:30:42 -0000 (UTC) Date: Mon, 25 Jun 2018 18:30:42 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b319742c0d68_56382ad67d8fdc10873c2@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] cadc2c: Didn't save some of the recovery tweaks Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b319742c08c6_56382ad67d8fdc108729"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 01:30:46 -0000 ----==_mimepart_5b319742c08c6_56382ad67d8fdc108729 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/crypto-cleanup Home: https://github.com/quicwg/base-drafts Commit: cadc2c9ac74f46fc637dc3ce755e53ffb3e4e452 https://github.com/quicwg/base-drafts/commit/cadc2c9ac74f46fc637dc3ce755e53ffb3e4e452 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Didn't save some of the recovery tweaks **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b319742c08c6_56382ad67d8fdc108729-- From nobody Mon Jun 25 18:30:56 2018 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 45C03130F50 for ; Mon, 25 Jun 2018 18:30:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 XaP_9PyTllPp for ; Mon, 25 Jun 2018 18:30:46 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C23A5130E7F for ; Mon, 25 Jun 2018 18:30:46 -0700 (PDT) Date: Mon, 25 Jun 2018 18:30:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529976646; bh=eQwVcC4HVSnRSF8HLibY9U2nQ7RElhP+B+NUt0QCZek=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MzyjEjs1Rn45adMAM1xD+/47bOWtq/ONGb8zVTDfy0+AxeHtooPjkRy/+/ETdvDeY H1uih8fSvHwENmlf0O1kZqGskeHOFFt/X9lEncuS8aNaerZ+ZIFy/eVdYEE/NKIEXJ ULgXZadlll9VMi2j2W71UHLTa7hZyNrf7FfhQhwU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b319745f2a9a_41243fc622098f80347941"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 01:30:50 -0000 ----==_mimepart_5b319745f2a9a_41243fc622098f80347941 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. cadc2c9 Didn't save some of the recovery tweaks -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1476/files/2378dc70f15dfd0c9b16aafb80912285bcfd579d..cadc2c9ac74f46fc637dc3ce755e53ffb3e4e452 ----==_mimepart_5b319745f2a9a_41243fc622098f80347941 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • cadc2c9 Didn't save some of the recovery tweaks

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b319745f2a9a_41243fc622098f80347941-- From nobody Mon Jun 25 18:40:54 2018 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 978AA130E7F for ; Mon, 25 Jun 2018 18:40:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 NyYc8pzjaPDs for ; Mon, 25 Jun 2018 18:40:52 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 090DC130E7A for ; Mon, 25 Jun 2018 18:40:51 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529977251; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=j97JUgyr3Kjc80+Xjup30BJS/pIyUW0xQjdtzkH3Vt0=; b=G3FPkqc2dp4BO+JBtFbjnC6DCg3yvQoLIE4fGr4quGCuo7yfEztvSQo2oXNDX5iIg6o1jWx6 rvLQiBgGt/GleAswP5RXm/m5oXwA1YdUr2vibB+eBNBucmC0hzCrsUzzSwvK9OJTOm+zQSnh wp1PWkWaG9zJSt+ykmMBMRpycb8= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b3199a3.7f5b320bf390-smtp-out-n01; Tue, 26 Jun 2018 01:40:51 -0000 (UTC) Date: Mon, 25 Jun 2018 18:40:50 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3199a22de8a_35ab2b22d2a6dc0c107349@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 0acc8f: Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3199a22daa2_35ab2b22d2a6dc0c107224"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 01:40:54 -0000 ----==_mimepart_5b3199a22daa2_35ab2b22d2a6dc0c107224 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts Commit: 0acc8f8b945ffc6199492f12fa6d0c5059101175 https://github.com/quicwg/base-drafts/commit/0acc8f8b945ffc6199492f12fa6d0c5059101175 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Use CONNECTION_CLOSE rather than CRYPTO_CLOSE **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3199a22daa2_35ab2b22d2a6dc0c107224-- From nobody Mon Jun 25 18:42:11 2018 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 A6CF9130F3F for ; Mon, 25 Jun 2018 18:42:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ieAErexdIIaI for ; Mon, 25 Jun 2018 18:42:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1EC130E7A for ; Mon, 25 Jun 2018 18:42:07 -0700 (PDT) Date: Mon, 25 Jun 2018 18:42:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529977327; bh=hJ7X+JPOX+tXRAF+0IHTrQLNOw1w76+2UwNtaRkGt6U=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=x5VqFMkudTpjxaA0tNo1AujRW1oa8eQHkv/OGdSil9ZPKu8amfOfED8UZnEx+YCfb E3sugNEujEvKryLdhbBbLO+DQhAFu7dqMy+jQDxRkbAzDi0Es29QGwsOeO/i8EgdMk Ph8yib16PuVEQFjcVUqu3RJQK1P6OmbTf1D9yIWY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3199ef8c2a_67463fe68cf16f78481367"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 01:42:10 -0000 ----==_mimepart_5b3199ef8c2a_67463fe68cf16f78481367 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit More frame types aren't really necessary here. (This will conflict with the rename of CRYPTO_HS, but I can manage that.) You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1477 -- Commit Summary -- * Use CONNECTION_CLOSE rather than CRYPTO_CLOSE -- File Changes -- M draft-ietf-quic-tls.md (18) M draft-ietf-quic-transport.md (94) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1477.patch https://github.com/quicwg/base-drafts/pull/1477.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/1477 ----==_mimepart_5b3199ef8c2a_67463fe68cf16f78481367 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

More frame types aren't really necessary here.

(This will conflict with the rename of CRYPTO_HS, but I can manage that.)

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

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

Commit Summary

  • Use CONNECTION_CLOSE rather than CRYPTO_CLOSE

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 mute the thread.

----==_mimepart_5b3199ef8c2a_67463fe68cf16f78481367-- From nobody Mon Jun 25 20:49:16 2018 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 11516130F55 for ; Mon, 25 Jun 2018 20:49:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 m-XUhiqlfts9 for ; Mon, 25 Jun 2018 20:49:12 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63B4C130F3B for ; Mon, 25 Jun 2018 20:49:12 -0700 (PDT) Date: Mon, 25 Jun 2018 20:49:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529984951; bh=AGmZw6WT2x65E/eNpUMnGAMxJ08t7ya2GplM9hIJow8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZDM0UjqkM8r5v/ASPMuwdJwTskaK8a6cvalDEfzoQA8e14SMVKtGHFHUnO5NrNljP I+6bKOwk1vQZWY8GLQzMhZhKSFKthyygfgZrDaTAkNUFOBWM+d1gbDIpBnBzzac2fx YPhNGs8SSsppG7rw+tcWYNMfX1uyA1ziNMLaszwQ= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31b7b76598b_717a3f8a10e68f78232220"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Tue, 26 Jun 2018 03:49:14 -0000 ----==_mimepart_5b31b7b76598b_717a3f8a10e68f78232220 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. Not sure how I feel about this, but noticed some glitches you should probably correct pre-landing > @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares. ## TLS Errors -If TLS experiences an error, it MUST generate an appropriate alert -as defined in {{TLS13}}; Section 6) and then provide it to QUIC, -which sends the alert in a CRYPTO_CLOSE frame. All such alerts are -"fatal" (see {{TLS13}}, Section 6.2. +If TLS experiences an error, it generates an appropriate alert as defined in +Section 6 of {{TLS13}}. + +A TLS alert is turned into a QUIC connection error by converting the alert +description into a QUIC error code. The alert description is added to 0x200 to Probably worth observing that this is a one-byte field. > @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares. ## TLS Errors -If TLS experiences an error, it MUST generate an appropriate alert -as defined in {{TLS13}}; Section 6) and then provide it to QUIC, -which sends the alert in a CRYPTO_CLOSE frame. All such alerts are -"fatal" (see {{TLS13}}, Section 6.2. +If TLS experiences an error, it generates an appropriate alert as defined in +Section 6 of {{TLS13}}. + +A TLS alert is turned into a QUIC connection error by converting the alert +description into a QUIC error code. The alert description is added to 0x200 to +produce a QUIC error code from the range reserved for CRYPTO_ERROR. The +resulting value is sent in a QUIC CONNECTION_CLOSE frame. + +The alert level of all TLS alerts is "fatal", a TLS stack does not generate +alerts at the "warning" level. This is a bit confusing because stacks can in fact do that. Maybe MUST NOT? -- 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/1477#pullrequestreview-131856622 ----==_mimepart_5b31b7b76598b_717a3f8a10e68f78232220 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

Not sure how I feel about this, but noticed some glitches you should probably correct pre-landing

In draft-ietf-quic-tls.md:

> @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares.
 
 ## TLS Errors
 
-If TLS experiences an error, it MUST generate an appropriate alert
-as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
-which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
-"fatal" (see {{TLS13}}, Section 6.2.
+If TLS experiences an error, it generates an appropriate alert as defined in
+Section 6 of {{TLS13}}.
+
+A TLS alert is turned into a QUIC connection error by converting the alert
+description into a QUIC error code.  The alert description is added to 0x200 to

Probably worth observing that this is a one-byte field.

In draft-ietf-quic-tls.md:

> @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares.
 
 ## TLS Errors
 
-If TLS experiences an error, it MUST generate an appropriate alert
-as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
-which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
-"fatal" (see {{TLS13}}, Section 6.2.
+If TLS experiences an error, it generates an appropriate alert as defined in
+Section 6 of {{TLS13}}.
+
+A TLS alert is turned into a QUIC connection error by converting the alert
+description into a QUIC error code.  The alert description is added to 0x200 to
+produce a QUIC error code from the range reserved for CRYPTO_ERROR.  The
+resulting value is sent in a QUIC CONNECTION_CLOSE frame.
+
+The alert level of all TLS alerts is "fatal", a TLS stack does not generate
+alerts at the "warning" level.

This is a bit confusing because stacks can in fact do that. Maybe MUST NOT?

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

----==_mimepart_5b31b7b76598b_717a3f8a10e68f78232220-- From nobody Mon Jun 25 21:25:28 2018 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 8159A130F61 for ; Mon, 25 Jun 2018 21:25:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 38Esjg78r7ip for ; Mon, 25 Jun 2018 21:25:26 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F33471277BB for ; Mon, 25 Jun 2018 21:25:25 -0700 (PDT) Date: Mon, 25 Jun 2018 21:25:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529987125; bh=Vo+qsSJt8HyEYDIzdh2DdUtjV147e52kgwxv7ad84po=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=W3gQ4gxnEEAajHU+aaoi8Nm22mjilyf3Iizm86ec+rRHtZXlUmffaUZHQ67o8QLVz ezNKltN4XBkrCn1dc+oym+icglcrXFMkEv4v7iLUHG/Q97Jn89O6+zU4dbK1wKGsLN xLjV2bXBmtB9Ll4OaEQVM2YSYg5RkLJz2oUUn+E4= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Updated ICMP PMTU section (#1412) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31c034f2449_1c2323f890d8e6f7c6735a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Tue, 26 Jun 2018 04:25:28 -0000 ----==_mimepart_5b31c034f2449_1c2323f890d8e6f7c6735a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I've made updates per feedback received. There are two points of discussion left (that I know of): 1. This is promoting ICMP processing to a SHOULD. I think this is a correct thing to do, since PLPMTUD claims itself to be an extension of ICMP-based PMTUD process. Of course, implementations w/o access to ICMP would not be able to implement this SHOULD, but this is ok albeit unfortunate -- the very definition of a SHOULD (skipping on MAY is not "unfortunate"). 2. I am using a mostly made up number (1392) as "conservative enough to be believed w/o on-path proof". It was a compromise between "small enough for most Internet tunnels" and "not that small that someone would go into troubles of maliciously reducing PMTU of the victim to that number". This may need a discussion. -- 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/1412#issuecomment-400174137 ----==_mimepart_5b31c034f2449_1c2323f890d8e6f7c6735a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I've made updates per feedback received. There are two points of disc= ussion left (that I know of):

  1. This is promoting ICMP processing to a SHOULD. I think this is a corr= ect thing to do, since PLPMTUD claims itself to be an extension of ICMP-b= ased PMTUD process. Of course, implementations w/o access to ICMP would = not be able to implement this SHOULD, but this is ok albeit unfortunate -= - the very definition of a SHOULD (skipping on MAY is not "unfortunate").=

  2. I am using a mostly made up number (1392) as "conservative enough to b= e believed w/o on-path proof". It was a compromise between "small enough= for most Internet tunnels" and "not that small that someone would go int= o troubles of maliciously reducing PMTU of the victim to that number". T= his may need a discussion.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b31c034f2449_1c2323f890d8e6f7c6735a-- From nobody Mon Jun 25 22:03:16 2018 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 703C0130E9B for ; Mon, 25 Jun 2018 22:03:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 PqI-MiGocdph for ; Mon, 25 Jun 2018 22:03:12 -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 4BA4D130EBA for ; Mon, 25 Jun 2018 22:03:12 -0700 (PDT) Date: Mon, 25 Jun 2018 22:03:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529989391; bh=70KEUtjgY17wWKrnri6yNqLTSba+lS/clYxT3CnsCsI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DjfDCJDs/R4syQ8DPmNLvnsfRzRfbyEcZeYqh0gT3ozzUQ1PyJRyhqI4BW8LjvUTz /ksZmRuGNRf86pBPbodBQ/wucke6dFc03qd78P+Fwwd6TR6R/AWxgjsmM55J9YNwIs XL8HAXKpSaePe1AnsexwGJ4GJmCWzX3w0m1TOhBU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31c90f8ccc8_7e6b2abbd7776f6027993"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 05:03:15 -0000 ----==_mimepart_5b31c90f8ccc8_7e6b2abbd7776f6027993 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares. ## TLS Errors -If TLS experiences an error, it MUST generate an appropriate alert -as defined in {{TLS13}}; Section 6) and then provide it to QUIC, -which sends the alert in a CRYPTO_CLOSE frame. All such alerts are -"fatal" (see {{TLS13}}, Section 6.2. +If TLS experiences an error, it generates an appropriate alert as defined in +Section 6 of {{TLS13}}. + +A TLS alert is turned into a QUIC connection error by converting the alert +description into a QUIC error code. The alert description is added to 0x200 to +produce a QUIC error code from the range reserved for CRYPTO_ERROR. The +resulting value is sent in a QUIC CONNECTION_CLOSE frame. + +The alert level of all TLS alerts is "fatal", a TLS stack does not generate +alerts at the "warning" level. I thought that this was OK. TLS 1.3 prohibits use of warning for anything but close_notify, and we don't allow TLS to close. I guess that MUST NOT isn't a problem though. -- 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/1477#discussion_r198014372 ----==_mimepart_5b31c90f8ccc8_7e6b2abbd7776f6027993 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-tls.md:

> @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares.
 
 ## TLS Errors
 
-If TLS experiences an error, it MUST generate an appropriate alert
-as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
-which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
-"fatal" (see {{TLS13}}, Section 6.2.
+If TLS experiences an error, it generates an appropriate alert as defined in
+Section 6 of {{TLS13}}.
+
+A TLS alert is turned into a QUIC connection error by converting the alert
+description into a QUIC error code.  The alert description is added to 0x200 to
+produce a QUIC error code from the range reserved for CRYPTO_ERROR.  The
+resulting value is sent in a QUIC CONNECTION_CLOSE frame.
+
+The alert level of all TLS alerts is "fatal", a TLS stack does not generate
+alerts at the "warning" level.

I thought that this was OK. TLS 1.3 prohibits use of warning for anything but close_notify, and we don't allow TLS to close. I guess that MUST NOT isn't a problem though.

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

----==_mimepart_5b31c90f8ccc8_7e6b2abbd7776f6027993-- From nobody Mon Jun 25 22:03:44 2018 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 4F5DC130F55 for ; Mon, 25 Jun 2018 22:03:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 rKCSWSuKPYrj for ; Mon, 25 Jun 2018 22:03:40 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C2D42130E9B for ; Mon, 25 Jun 2018 22:03:40 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1529989420; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=4FRDHqaaQjXN7yzSPA+i5d+1pmvoPseso+vVSyp8Ky8=; b=fK6GDy1rKOKEX2Rm5B1Rm1Ip2lHEHy6fVhvOXr1VWE+hpsEho48yw5uUwJdiAroxUEOdPtG/ jCX0N0gZH2AsPfEVUatHbFxPsnZE8qraw+qXbs7w9nTHnVA1LnoP4td+lg027bKtr+FufhrZ 77CLbcDJyQkoNEkDWRf0yszDFBc= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b31c92b.7fd4b0a65e70-smtp-out-n01; Tue, 26 Jun 2018 05:03:39 -0000 (UTC) Date: Mon, 25 Jun 2018 22:03:38 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b31c92a90897_3dc92af5d97bfc104021b@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 9b80c4: one-octet description; MUST NOT warning alert Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b31c92a904b1_3dc92af5d97bfc10401ce"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 05:03:43 -0000 ----==_mimepart_5b31c92a904b1_3dc92af5d97bfc10401ce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts Commit: 9b80c45f58b43ede57b9876e21df30dfa963f49b https://github.com/quicwg/base-drafts/commit/9b80c45f58b43ede57b9876e21df30dfa963f49b Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- one-octet description; MUST NOT warning alert **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b31c92a904b1_3dc92af5d97bfc10401ce-- From nobody Mon Jun 25 22:03:52 2018 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 AE2E3130E9B for ; Mon, 25 Jun 2018 22:03:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Nttwonh0vhOP for ; Mon, 25 Jun 2018 22:03:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06666130EBA for ; Mon, 25 Jun 2018 22:03:42 -0700 (PDT) Date: Mon, 25 Jun 2018 22:03:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529989421; bh=VhCm6zB144Kn8HfUbVzqRLBfIuTV9XzEi7XIyZMn6LA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eE614q1/PB62Dh57oZtqFikjDGvBnCcADBpYIzJJLi046Uw8+4CH+vdUccSjqV4no Fa6P0DP+yKtoQEYg+hv9hCH5BxBrX+zFFqVqUHD0U8Z27QUuWnLF75NfkAndlkC4Vg +IRuP6/izbh5s6CxtikYQA0U37BKHwmgx8iVRB80= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31c92d12b49_71653f8a10e68f7825767b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 05:03:44 -0000 ----==_mimepart_5b31c92d12b49_71653f8a10e68f7825767b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 9b80c45 one-octet description; MUST NOT warning alert -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1477/files/0acc8f8b945ffc6199492f12fa6d0c5059101175..9b80c45f58b43ede57b9876e21df30dfa963f49b ----==_mimepart_5b31c92d12b49_71653f8a10e68f7825767b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 9b80c45 one-octet description; MUST NOT warning alert

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b31c92d12b49_71653f8a10e68f7825767b-- From nobody Mon Jun 25 23:35:58 2018 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 D0E6B130F7F for ; Mon, 25 Jun 2018 23:35:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 3_gVJcgBB1FC for ; Mon, 25 Jun 2018 23:35:55 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28418130F78 for ; Mon, 25 Jun 2018 23:35:55 -0700 (PDT) Date: Mon, 25 Jun 2018 23:35:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529994953; bh=awUb+MMRh+2mQriiYtmZ+g+wDlTGUosoqVmTPs4IxDc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ubijWKS5B0JWhSoH/As2udzGkAACwk0qtbXpcWRUHg4zRLcbtzM98/qTkA8gypnsI LvrLkygrDYHw0A49M59B4eDuZwIqWVx1Ep5V2g0JpMzH4ZOPsF/9leEc9AN8bG8OEI fRr5rWmMhO9b4jvC8ndm7XdT2Dj383KC7AgYtk/s= From: Julian Reschke Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] tls: fix citation format (#1478) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31dec9eceff_56ca3fe2744eef80416838"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: reschke 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.26 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: Tue, 26 Jun 2018 06:35:57 -0000 ----==_mimepart_5b31dec9eceff_56ca3fe2744eef80416838 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1478 -- Commit Summary -- * tls: fix citation format -- File Changes -- M draft-ietf-quic-tls.md (12) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1478.patch https://github.com/quicwg/base-drafts/pull/1478.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/1478 ----==_mimepart_5b31dec9eceff_56ca3fe2744eef80416838 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • tls: fix citation format

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 mute the thread.

----==_mimepart_5b31dec9eceff_56ca3fe2744eef80416838-- From nobody Tue Jun 26 00:13:23 2018 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 27CC8130DE6 for ; Tue, 26 Jun 2018 00:13:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 eVi5AYvQyNjH for ; Tue, 26 Jun 2018 00:13:20 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E2D12872C for ; Tue, 26 Jun 2018 00:13:20 -0700 (PDT) Date: Tue, 26 Jun 2018 00:13:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529997200; bh=izzu2ZTmFpl3xnysP/JRoK9RLuA5+IE56a7GodquzeY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z/393v2+qizR75WoL1nh6KkIz83m26v0vE+HOEGbnFByK+nXxPmmPWOvAQK0aPoFF miapmEIX9cLswY0FuHLRbg5pP4dwOPZBYVh3E7ElehWo6iAhZeOJXwwOiewghgQoR+ /AzE8RjASALvjzgedmH8hER0zEpYesT90mwRYizU= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31e78fd9538_76a73f9858204f889743b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Tue, 26 Jun 2018 07:13:22 -0000 ----==_mimepart_5b31e78fd9538_76a73f9858204f889743b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I really like this simplification. -- 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/1477#issuecomment-400204210 ----==_mimepart_5b31e78fd9538_76a73f9858204f889743b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I really like this simplification.

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

----==_mimepart_5b31e78fd9538_76a73f9858204f889743b-- From nobody Tue Jun 26 01:17:16 2018 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 67888130F7B for ; Tue, 26 Jun 2018 01:17:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 CKFTLMhFr-xM for ; Tue, 26 Jun 2018 01:17:13 -0700 (PDT) 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 92FF91274D0 for ; Tue, 26 Jun 2018 01:17:13 -0700 (PDT) Date: Tue, 26 Jun 2018 01:17:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530001032; bh=qGjvhMOn9vvsBsXtSVms56K1dHIlxpoTjqFkAkwm6Pw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m7VsfaqVPyscXE82Iu4MGNikv7K7vj53RgbMQXp1C9Xd9W27mUBCB+8ntmhIB5xuI lXTGH3eEQy5csKjRLlwbq8BDgURkQQLVHqlJ/DmaUCj3MqczxxRvxus9rZ+V4xB9UO vCZeOoGOjQ93GBCeAkOVv2sMd908KAWHoguOQ5Mc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] tls: fix citation format (#1478) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31f6889e8b7_5b483fc9d5054f7c1567e8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 08:17:15 -0000 ----==_mimepart_5b31f6889e8b7_5b483fc9d5054f7c1567e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I've been switching these to "Section x.y of {{...}}" as I go. I will do that instead. I'll hold this PR open until that's done though (this would be better than not doing that so I'll merge this if I don't get time before we cut -13). -- 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/1478#issuecomment-400221699 ----==_mimepart_5b31f6889e8b7_5b483fc9d5054f7c1567e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I've been switching these to "Section x.y of {{...}}" as I go. I will do that instead. I'll hold this PR open until that's done though (this would be better than not doing that so I'll merge this if I don't get time before we cut -13).

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

----==_mimepart_5b31f6889e8b7_5b483fc9d5054f7c1567e8-- From nobody Tue Jun 26 01:36:19 2018 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 9E21B130EC0 for ; Tue, 26 Jun 2018 01:36:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1mZxhKF34Tib for ; Tue, 26 Jun 2018 01:36:13 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6309D130F4A for ; Tue, 26 Jun 2018 01:36:13 -0700 (PDT) Date: Tue, 26 Jun 2018 01:36:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530002172; bh=Cs44DlSsU6ftrSItMYCsgwHUlKqYKdP+lB5CLZZed1I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kCsg2u6z9uGvSf3O2hzaobBzVU+vYuIqdS3jDz1LtqyByAdVI/v69lZPBQ+UnbLbJ tNd9DQhyy2nIqa8t/UqGIbgImvAyYR1HbXdQGzc5XPxT5cosCelU1JR9HanJzHikO7 VjXnul9ZLg1vtVxgVqEh3R20e8YQXqYnsRi/V7OE= From: Lars Eggert Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b31fafca6117_4852adb6dc62f50141152"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: larseggert 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.26 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: Tue, 26 Jun 2018 08:36:18 -0000 ----==_mimepart_5b31fafca6117_4852adb6dc62f50141152 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit larseggert commented on this pull request. > @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in the +IP header. If the header is not readable from the application, the codepoint 00 +(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only s/packet/packets/ > @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in the +IP header. If the header is not readable from the application, the codepoint 00 +(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only s/by the network/by the network,/ > @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in the +IP header. If the header is not readable from the application, the codepoint 00 +(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only +the value of the ECN field of the packet copy first received SHALL be included +in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and +ensure that ACK_ECN frames becomes idempotent in the event of packet s/becomes/are/ > @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in the +IP header. If the header is not readable from the application, the codepoint 00 +(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only +the value of the ECN field of the packet copy first received SHALL be included +in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and +ensure that ACK_ECN frames becomes idempotent in the event of packet +duplication. Note, a receiver is not required to maintain indefinite state for +which packet numbers have been received far into the history. Packets discarded +for this reason, their ECN values are also not counted. These sentences read awkwardly. Maybe "when information about old packets is discarded at a receiver, any ECN information associated with them is also discarded" or something like that? > @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able to decipher the packet. +## ACK_ECN Frame {#frame-ack-ecn} + +A QUIC connection MUST keep counters for each ECN codepoint, recording the +number of packets that were received with the corresponding ECN codepoint in the +IP header. If the header is not readable from the application, the codepoint 00 +(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only +the value of the ECN field of the packet copy first received SHALL be included +in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and +ensure that ACK_ECN frames becomes idempotent in the event of packet +duplication. Note, a receiver is not required to maintain indefinite state for +which packet numbers have been received far into the history. Packets discarded +for this reason, their ECN values are also not counted. + +ACK_ECN Frame MUST be used when when an endpoint is acknowledging a packet were s/ACK_ECN Frame/An ACK_ECN frame/ There are other instances where "Frame" is capitalized; they should also be lowercased IMO for consistency with the rest of the docs. > @@ -1427,6 +1431,63 @@ a single packet. In TLS, the Retry packet type is used to carry the HelloRetryRequest message. +## ECN Capability Check {#ecn-capability-check} + +Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for s/allows for/enables/ > +number, the path and peer do not remove ECN markings. The endpoint records this +path as being ECN capable and continues to mark IP packets that it sends. + +If an endpoint receives an ACK frame, indicating that no markings were received, +or the counter in the ACK_ECN frame do not match the number of QUIC packets that +were sent in marked IP packets, then the path or peer remove ECN markings. The +endpoint records this path as not being ECN capable and it ceases marking of +packets. + +IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify +that the new path supports ECN, see {{ecn-connection-migration}}. + +### Continuous Verification of ECN {#ecn-continuous-verification} + +If the ECN capability check was successful and the endpoint continues to send +ECT marked packets then continuous verification is applied. This is to detect s/packets then/packets, then/ > +path as being ECN capable and continues to mark IP packets that it sends. + +If an endpoint receives an ACK frame, indicating that no markings were received, +or the counter in the ACK_ECN frame do not match the number of QUIC packets that +were sent in marked IP packets, then the path or peer remove ECN markings. The +endpoint records this path as not being ECN capable and it ceases marking of +packets. + +IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify +that the new path supports ECN, see {{ecn-connection-migration}}. + +### Continuous Verification of ECN {#ecn-continuous-verification} + +If the ECN capability check was successful and the endpoint continues to send +ECT marked packets then continuous verification is applied. This is to detect +any cases when ECN field is bleached, that is, zeroed out by a network node, Above, the text used the term "remove markings". We should pick one term - zeroed, bleached, removed - consistently. > +endpoint records this path as not being ECN capable and it ceases marking of +packets. + +IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify +that the new path supports ECN, see {{ecn-connection-migration}}. + +### Continuous Verification of ECN {#ecn-continuous-verification} + +If the ECN capability check was successful and the endpoint continues to send +ECT marked packets then continuous verification is applied. This is to detect +any cases when ECN field is bleached, that is, zeroed out by a network node, +likely as the result of a routing changes since the ECN capability check. + +For each received ACK_ECN frame, the total number of newly acknowledged packets +can be compared to the total increase in ECN counters. If the increase in ECN +counters is less, then an ECN failure has occurred and ECN should be disabled. less than what? > +that the new path supports ECN, see {{ecn-connection-migration}}. + +### Continuous Verification of ECN {#ecn-continuous-verification} + +If the ECN capability check was successful and the endpoint continues to send +ECT marked packets then continuous verification is applied. This is to detect +any cases when ECN field is bleached, that is, zeroed out by a network node, +likely as the result of a routing changes since the ECN capability check. + +For each received ACK_ECN frame, the total number of newly acknowledged packets +can be compared to the total increase in ECN counters. If the increase in ECN +counters is less, then an ECN failure has occurred and ECN should be disabled. +ECN is also disabled in case an ACK frame is received acknowledging any ECT sent +packet. + +If the acknowledgements from the receiver are lost such that one or more packet s/packet/packets/ > + +If the ECN capability check was successful and the endpoint continues to send +ECT marked packets then continuous verification is applied. This is to detect +any cases when ECN field is bleached, that is, zeroed out by a network node, +likely as the result of a routing changes since the ECN capability check. + +For each received ACK_ECN frame, the total number of newly acknowledged packets +can be compared to the total increase in ECN counters. If the increase in ECN +counters is less, then an ECN failure has occurred and ECN should be disabled. +ECN is also disabled in case an ACK frame is received acknowledging any ECT sent +packet. + +If the acknowledgements from the receiver are lost such that one or more packet +are received by the receiver, but never acknowledged to the sender an +insensitivity to bleaching will be created. In this situation the ECN counters +reported will have increase, but the sender side total for acknowledged packets s/increase/increased/ > +ECN is also disabled in case an ACK frame is received acknowledging any ECT sent +packet. + +If the acknowledgements from the receiver are lost such that one or more packet +are received by the receiver, but never acknowledged to the sender an +insensitivity to bleaching will be created. In this situation the ECN counters +reported will have increase, but the sender side total for acknowledged packets +will not have increased. Thus, a number of bleached packets equal to the number +of packets that failed to be acknowledged can be received before triggering the +continuous verification. To address this issue the sender detect the case when +the ECN counters grows more than number of acknowledged packets when a ACK_ECN +frame is received. In such cases a new comparison point is created by storing +the current number of totally acknowledged packets and latest ECN counters. Then +comparison are done by subtracting these stored values from the respective +counters prior to the comparison. Note that any out-of-order ACK_ECN frames +can't be used for determining any loss of acknowledgements. This whole paragraph is really difficult to understand. "Comparison points" are not mentioned anywhere else, for starters. > @@ -1783,6 +1845,21 @@ Note that receipt of packets with higher packet numbers from the legitimate peer address will trigger another connection migration. This will cause the validation of the address of the spurious migration to be abandoned. +### ECN Capability Check for Migrated Connection {#ecn-connection-migration} + +Each new path is probed to determine whether it supports ECN. Packets sent on +the new path are sent in IP packets with an ECT marking as described in +{{ecn-capability-check}}. + +Markings, or absence of markings, on packets sent on multiple paths can make it +difficult to correctly attribute counters with markings on specific packets. +Recording the packet number when connection migration occurred might help in +correlating increases in counters with packets sent on the new path. Might help how? > +| ACK Delay (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECT(0) Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECT(1) Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN-CE Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"} + +The receiver side report three ECN counters in the ACK_ECN frame. These counters s/side // > ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECT(0) Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECT(1) Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ECN-CE Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Block Count (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ACK Blocks (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"} + +The receiver side report three ECN counters in the ACK_ECN frame. These counters +counts the number of packets marked with this codepoint since the start of the s/counts/count/ -- 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/1372#pullrequestreview-131908133 ----==_mimepart_5b31fafca6117_4852adb6dc62f50141152 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@larseggert commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in the
+IP header. If the header is not readable from the application, the codepoint 00
+(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only

s/packet/packets/

In draft-ietf-quic-transport.md:

> @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in the
+IP header. If the header is not readable from the application, the codepoint 00
+(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only

s/by the network/by the network,/

In draft-ietf-quic-transport.md:

> @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in the
+IP header. If the header is not readable from the application, the codepoint 00
+(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only
+the value of the ECN field of the packet copy first received SHALL be included
+in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and
+ensure that ACK_ECN frames becomes idempotent in the event of packet

s/becomes/are/

In draft-ietf-quic-transport.md:

> @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in the
+IP header. If the header is not readable from the application, the codepoint 00
+(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only
+the value of the ECN field of the packet copy first received SHALL be included
+in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and
+ensure that ACK_ECN frames becomes idempotent in the event of packet
+duplication. Note, a receiver is not required to maintain indefinite state for
+which packet numbers have been received far into the history. Packets discarded
+for this reason, their ECN values are also not counted.

These sentences read awkwardly. Maybe "when information about old packets is discarded at a receiver, any ECN information associated with them is also discarded" or something like that?

In draft-ietf-quic-transport.md:

> @@ -2887,6 +2964,73 @@ by a client in protected packets, because it is certain that the server is able
 to decipher the packet.
 
 
+## ACK_ECN Frame {#frame-ack-ecn}
+
+A QUIC connection MUST keep counters for each ECN codepoint, recording the
+number of packets that were received with the corresponding ECN codepoint in the
+IP header. If the header is not readable from the application, the codepoint 00
+(Not-ECT) MUST be assumed. If any packet are duplicated by the network then only
+the value of the ECN field of the packet copy first received SHALL be included
+in the counters. This to prevent the on-the-side attack ({{security-ecn}}) and
+ensure that ACK_ECN frames becomes idempotent in the event of packet
+duplication. Note, a receiver is not required to maintain indefinite state for
+which packet numbers have been received far into the history. Packets discarded
+for this reason, their ECN values are also not counted.
+
+ACK_ECN Frame MUST be used when when an endpoint is acknowledging a packet were

s/ACK_ECN Frame/An ACK_ECN frame/

There are other instances where "Frame" is capitalized; they should also be lowercased IMO for consistency with the rest of the docs.

In draft-ietf-quic-transport.md:

> @@ -1427,6 +1431,63 @@ a single packet.
 
 In TLS, the Retry packet type is used to carry the HelloRetryRequest message.
 
+## ECN Capability Check {#ecn-capability-check}
+
+Explicit Congestion Notification (ECN) {{!RFC3168}} is feature that allows for

s/allows for/enables/

In draft-ietf-quic-transport.md:

> +number, the path and peer do not remove ECN markings. The endpoint records this
+path as being ECN capable and continues to mark IP packets that it sends.
+
+If an endpoint receives an ACK frame, indicating that no markings were received,
+or the counter in the ACK_ECN frame do not match the number of QUIC packets that
+were sent in marked IP packets, then the path or peer remove ECN markings. The
+endpoint records this path as not being ECN capable and it ceases marking of
+packets.
+
+IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify
+that the new path supports ECN, see {{ecn-connection-migration}}.
+
+### Continuous Verification of ECN {#ecn-continuous-verification}
+
+If the ECN capability check was successful and the endpoint continues to send
+ECT marked packets then continuous verification is applied. This is to detect

s/packets then/packets, then/

In draft-ietf-quic-transport.md:

> +path as being ECN capable and continues to mark IP packets that it sends.
+
+If an endpoint receives an ACK frame, indicating that no markings were received,
+or the counter in the ACK_ECN frame do not match the number of QUIC packets that
+were sent in marked IP packets, then the path or peer remove ECN markings. The
+endpoint records this path as not being ECN capable and it ceases marking of
+packets.
+
+IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify
+that the new path supports ECN, see {{ecn-connection-migration}}.
+
+### Continuous Verification of ECN {#ecn-continuous-verification}
+
+If the ECN capability check was successful and the endpoint continues to send
+ECT marked packets then continuous verification is applied. This is to detect
+any cases when ECN field is bleached, that is, zeroed out by a network node,

Above, the text used the term "remove markings". We should pick one term - zeroed, bleached, removed - consistently.

In draft-ietf-quic-transport.md:

> +endpoint records this path as not being ECN capable and it ceases marking of
+packets.
+
+IP packets sent on a new path SHOULD be marked with ECT(0) or ECT(1) to verify
+that the new path supports ECN, see {{ecn-connection-migration}}.
+
+### Continuous Verification of ECN {#ecn-continuous-verification}
+
+If the ECN capability check was successful and the endpoint continues to send
+ECT marked packets then continuous verification is applied. This is to detect
+any cases when ECN field is bleached, that is, zeroed out by a network node,
+likely as the result of a routing changes since the ECN capability check.
+
+For each received ACK_ECN frame, the total number of newly acknowledged packets
+can be compared to the total increase in ECN counters. If the increase in ECN
+counters is less, then an ECN failure has occurred and ECN should be disabled.

less than what?

In draft-ietf-quic-transport.md:

> +that the new path supports ECN, see {{ecn-connection-migration}}.
+
+### Continuous Verification of ECN {#ecn-continuous-verification}
+
+If the ECN capability check was successful and the endpoint continues to send
+ECT marked packets then continuous verification is applied. This is to detect
+any cases when ECN field is bleached, that is, zeroed out by a network node,
+likely as the result of a routing changes since the ECN capability check.
+
+For each received ACK_ECN frame, the total number of newly acknowledged packets
+can be compared to the total increase in ECN counters. If the increase in ECN
+counters is less, then an ECN failure has occurred and ECN should be disabled.
+ECN is also disabled in case an ACK frame is received acknowledging any ECT sent
+packet.
+
+If the acknowledgements from the receiver are lost such that one or more packet

s/packet/packets/

In draft-ietf-quic-transport.md:

> +
+If the ECN capability check was successful and the endpoint continues to send
+ECT marked packets then continuous verification is applied. This is to detect
+any cases when ECN field is bleached, that is, zeroed out by a network node,
+likely as the result of a routing changes since the ECN capability check.
+
+For each received ACK_ECN frame, the total number of newly acknowledged packets
+can be compared to the total increase in ECN counters. If the increase in ECN
+counters is less, then an ECN failure has occurred and ECN should be disabled.
+ECN is also disabled in case an ACK frame is received acknowledging any ECT sent
+packet.
+
+If the acknowledgements from the receiver are lost such that one or more packet
+are received by the receiver, but never acknowledged to the sender an
+insensitivity to bleaching will be created. In this situation the ECN counters
+reported will have increase, but the sender side total for acknowledged packets

s/increase/increased/

In draft-ietf-quic-transport.md:

> +ECN is also disabled in case an ACK frame is received acknowledging any ECT sent
+packet.
+
+If the acknowledgements from the receiver are lost such that one or more packet
+are received by the receiver, but never acknowledged to the sender an
+insensitivity to bleaching will be created. In this situation the ECN counters
+reported will have increase, but the sender side total for acknowledged packets
+will not have increased. Thus, a number of bleached packets equal to the number
+of packets that failed to be acknowledged can be received before triggering the
+continuous verification. To address this issue the sender detect the case when
+the ECN counters grows more than number of acknowledged packets when a ACK_ECN
+frame is received. In such cases a new comparison point is created by storing
+the current number of totally acknowledged packets and latest ECN counters. Then
+comparison are done by subtracting these stored values from the respective
+counters prior to the comparison. Note that any out-of-order ACK_ECN frames
+can't be used for determining any loss of acknowledgements.

This whole paragraph is really difficult to understand. "Comparison points" are not mentioned anywhere else, for starters.

In draft-ietf-quic-transport.md:

> @@ -1783,6 +1845,21 @@ Note that receipt of packets with higher packet numbers from the legitimate peer
 address will trigger another connection migration.  This will cause the
 validation of the address of the spurious migration to be abandoned.
 
+### ECN Capability Check for Migrated Connection {#ecn-connection-migration}
+
+Each new path is probed to determine whether it supports ECN. Packets sent on
+the new path are sent in IP packets with an ECT marking as described in
+{{ecn-capability-check}}.
+
+Markings, or absence of markings, on packets sent on multiple paths can make it
+difficult to correctly attribute counters with markings on specific packets.
+Recording the packet number when connection migration occurred might help in
+correlating increases in counters with packets sent on the new path.

Might help how?

In draft-ietf-quic-transport.md:

> +|                          ACK Delay (i)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECT(0) Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECT(1) Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECN-CE Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"}
+
+The receiver side report three ECN counters in the ACK_ECN frame. These counters

s/side //

In draft-ietf-quic-transport.md:

> ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECT(0) Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECT(1) Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        ECN-CE Count (i)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                       ACK Block Count (i)                   ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          ACK Blocks (*)                     ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #ACN_ECN_FRAME_FORMAT title="ACK_ECN Frame Format"}
+
+The receiver side report three ECN counters in the ACK_ECN frame. These counters
+counts the number of packets marked with this codepoint since the start of the

s/counts/count/

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

----==_mimepart_5b31fafca6117_4852adb6dc62f50141152-- From nobody Tue Jun 26 05:16:06 2018 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 5D79A131016 for ; Tue, 26 Jun 2018 05:15:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DvdUG1NyEqoz for ; Tue, 26 Jun 2018 05:15:57 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 19CBE131051 for ; Tue, 26 Jun 2018 05:15:57 -0700 (PDT) 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=vRRtMCfz1vcncaMFBvg86ip08bk=; b=fobA5gGNC26VhL+j 327602Cn6LZwevJ9e//E9pb2Femcz01TcTn6M4d8SuXJQFe+yPzaMJ756yHtOLee Ab+eYB28d5k27NqA2TunZpzuCMM9p8gecrH0H76TmeNiCBU0CNZc8MERVeBOiYsD xPBcuYM+6h84RkwJ4asjZf8mqsw= Received: by filter0382p1iad2.sendgrid.net with SMTP id filter0382p1iad2-12824-5B322E73-1E 2018-06-26 12:15:47.411481233 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id A-vnjTW6Q0KtBT3KwSl8qg for ; Tue, 26 Jun 2018 12:15:47.352 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id 53A2B3FFCF for ; Tue, 26 Jun 2018 05:15:47 -0700 (PDT) Date: Tue, 26 Jun 2018 12:15:47 +0000 (UTC) From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b322e7351ee3_75f93fc3cb61cf78140913"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3M2tHm5qnqb1/tBmxEe/XAD4nyaFHFwh+alt iISahd5XL7uL3WEXcrFhe+CIaH9qgBMtOFvShZQanNXlH2CDs9x4Cm5iGvoTnrVrBnkfLwC+0s61GS rDnsvE6zTbmfThh9akhMAseMOLXSugX/Q+c8zJbBGtLXB2t9Cl6mUtCdEZSjt0JVfe8VrQpY/7HXca c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 12:16:05 -0000 ----==_mimepart_5b322e7351ee3_75f93fc3cb61cf78140913 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My $0.02: I'm not a fan of CRYPTO_HS or CRYPTO. I'd much prefer them to be named HANDSHAKE. Pushback to that stemmed from the collision with packet type names, which I'm not convinced is confusing. (I'd expect handshake packets to carry handshake frames after all.) -- 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/1476#issuecomment-400285915 ----==_mimepart_5b322e7351ee3_75f93fc3cb61cf78140913 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

My $0.02: I'm not a fan of CRYPTO_HS or CRYPTO. I'd much prefer them to be named HANDSHAKE. Pushback to that stemmed from the collision with packet type names, which I'm not convinced is confusing. (I'd expect handshake packets to carry handshake frames after all.)

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

----==_mimepart_5b322e7351ee3_75f93fc3cb61cf78140913-- From nobody Tue Jun 26 05:18:50 2018 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 851BD130DCD for ; Tue, 26 Jun 2018 05:18:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 6PRkj2Af5J1T for ; Tue, 26 Jun 2018 05:18:45 -0700 (PDT) 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 B4598130DC2 for ; Tue, 26 Jun 2018 05:18:45 -0700 (PDT) Date: Tue, 26 Jun 2018 05:18:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530015523; bh=qAKrT4lSp1WlE2b5RTSVpDFNaF2Ls8VAY2pXSZyAJF8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WmD1/wccF9IgTY9eCMJe6rqAqk85IYi/D3VKWfyBs7oqcjEN7VQWBTBmP7+OEf00p v8XSUNusg+pvOR85pTJZ8jQxvVblMhucN/wU6qjIiBAepDYPsRYCb8U0ZOCbs6eepg C8MGVVHbo/YYPI4qAGzeESvT4BhwXt3KeRJbePwc= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b322f23d77ec_47052af470598f50156970"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 26 Jun 2018 12:18:48 -0000 ----==_mimepart_5b322f23d77ec_47052af470598f50156970 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > I'd much prefer them to be named HANDSHAKE. But some communication happens post handshake, such as rekeying. -- 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/1476#issuecomment-400286741 ----==_mimepart_5b322f23d77ec_47052af470598f50156970 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'd much prefer them to be named HANDSHAKE.

But some communication happens post handshake, such as rekeying.

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

----==_mimepart_5b322f23d77ec_47052af470598f50156970-- From nobody Tue Jun 26 05:35:50 2018 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 71F4513101E for ; Tue, 26 Jun 2018 05:35:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 WNzTjGZ07wpx for ; Tue, 26 Jun 2018 05:35:46 -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 B270F131017 for ; Tue, 26 Jun 2018 05:35:46 -0700 (PDT) Date: Tue, 26 Jun 2018 05:35:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530016545; bh=vkVD6qwdl+pCsnvjar+RCDTULTShI0i3Iy5QtxFNROU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZuU7K8iA95JIfxJ5JjXcJ3ualiNdmeKFuWVgxJDLeN2PAhvP1yGCuLDNszZ9ISUY8 mwY4MsLwWYTsld4/nnN3kP6OvJKZfDMdNV5ofy99bm3PqQV+FMlimEUD9fzz5vM6Ca e95X8LDjs0/bE9N2swiPcOtIc1lxPPTlTvHTDtw4= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323321b92e1_47e73fa1119f8f841792ae"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Tue, 26 Jun 2018 12:35:49 -0000 ----==_mimepart_5b323321b92e1_47e73fa1119f8f841792ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If I'm reading the latest drafts correctly, the client's chosen source CID, used as destination CID by the server, is unauthenticated. If this is unintentional, perhaps we could address it by shoving the client's initial source and destination CID into the transport parameters? -- 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/1479 ----==_mimepart_5b323321b92e1_47e73fa1119f8f841792ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If I'm reading the latest drafts correctly, the client's chosen source CID, used as destination CID by the server, is unauthenticated. If this is unintentional, perhaps we could address it by shoving the client's initial source and destination CID into the transport parameters?

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

----==_mimepart_5b323321b92e1_47e73fa1119f8f841792ae-- From nobody Tue Jun 26 05:45:31 2018 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 A10B4131024 for ; Tue, 26 Jun 2018 05:45:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xsgsVp3EVNQu for ; Tue, 26 Jun 2018 05:45:27 -0700 (PDT) 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 26E27131021 for ; Tue, 26 Jun 2018 05:45:27 -0700 (PDT) Date: Tue, 26 Jun 2018 05:45:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530017126; bh=kZSnqpxY4D64vqEQnzxqTLXdg95mn+4DUdHmIDmJ+kM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F4KdHFnvx7zPKvYxn6jNfRoUgXzKn/QCa6Fb2KToaiQxleqTurefYsJcOdX4sU9NY sLXqvoGzPp0mbw7bkdeWeSGLp5wgCbJw6b8ZbFbIIaI2uriizZHLxSAYxE3af08EVA EMLvQjJ55ThlE33/M/k0r7jTywsaRuJV9otyoMhw= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3235666571d_53293fb9a4206f78206732"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Tue, 26 Jun 2018 12:45:30 -0000 ----==_mimepart_5b3235666571d_53293fb9a4206f78206732 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It somewhat relates to: https://github.com/quicwg/base-drafts/issues/1451 I suggest the intial CID become empty an a separate nonce is sent instead. This nonce should be verified by retry. But a normal handshake ought to also reflect it back to the client. I don't have the full overview of how the initial CID is validated today. There is path validation and TP validation, but in principle someone could race a handshake if the initial CID is not verified. That is what the long loop discussion is all about, except here it is race to win a retry. -- 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/1479#issuecomment-400294172 ----==_mimepart_5b3235666571d_53293fb9a4206f78206732 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It somewhat relates to: #1451

I suggest the intial CID become empty an a separate nonce is sent inst= ead. This nonce should be verified by retry. But a normal handshake ought= to also reflect it back to the client.

I don't have the full overview of how the initial CID is validated tod= ay. There is path validation and TP validation, but in principle someone = could race a handshake if the initial CID is not verified. That is what t= he long loop discussion is all about, except here it is race to win a ret= ry.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3235666571d_53293fb9a4206f78206732-- From nobody Tue Jun 26 06:04:13 2018 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 9DC1E130DDF for ; Tue, 26 Jun 2018 06:04:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 yBggzVAGExN3 for ; Tue, 26 Jun 2018 06:04:08 -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 471B01294D7 for ; Tue, 26 Jun 2018 06:04:08 -0700 (PDT) Date: Tue, 26 Jun 2018 06:04:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530018247; bh=ClCkuxc9t0Hxdyt8S5qKJhEk4H6R1t+TJuwi8zb0x14=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZyVT7cmxrQHQ8MwS/osHGAzwn/wWHPDYl6WRcSoLDdijbowXHFZQBpBaJLBDwkWMD k9NAKqQcucg/mEMK8XM/IJIq+iQfMKJtGCLbw83NWSjEw7xLfyrfujx1g93e7OECTq LbBseauwnQFUbBxGVtW+HH3dfKbCWwoeWRIKLhNM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3239c74a384_46e32af470598f5030788e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 13:04:11 -0000 ----==_mimepart_5b3239c74a384_46e32af470598f5030788e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. Some small nits, but mostly looks good to me. > @@ -1032,7 +1032,6 @@ explained in more detail as they are referenced later in the document. | 0x0f | PATH_RESPONSE | {{frame-path-response}} | | 0x10 - 0x17 | STREAM | {{frame-stream}} | | 0x18 | CRYPTO_HS | {{frame-crypto}} | -| 0x19 | CRYPTO_CLOSE | {{frame-crypto-close}} | | 0x20 | NEW_TOKEN | {{frame-new-token}} | Renumber NEW_TOKEN to 0x19 > Application protocols can signal application-specific protocol errors using the APPLICATION_CLOSE frame. Errors that are specific to the transport, including all those described in this document, are carried in a CONNECTION_CLOSE frame. Other than the type of error code they carry, these frames are identical in format and semantics. -A CONNECTION_CLOSE, CRYPTO_CLOSE, or APPLICATION_CLOSE frame could be -sent in a packet that is lost. An endpoint SHOULD be prepared to -retransmit a packet containing either frame type if it receives more -packets on a terminated connection. Limiting the number of -retransmissions and the time over which this final packet is sent +A CONNECTION_CLOSE, or APPLICATION_CLOSE frame could be sent in a packet that is "," unnecessary -- 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/1477#pullrequestreview-131980571 ----==_mimepart_5b3239c74a384_46e32af470598f5030788e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

Some small nits, but mostly looks good to me.

In draft-ietf-quic-transport.md:

> @@ -1032,7 +1032,6 @@ explained in more detail as they are referenced later in the document.
 | 0x0f        | PATH_RESPONSE     | {{frame-path-response}}     |
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 | 0x18        | CRYPTO_HS         | {{frame-crypto}}            |
-| 0x19        | CRYPTO_CLOSE      | {{frame-crypto-close}}      |
 | 0x20        | NEW_TOKEN         | {{frame-new-token}}         |

Renumber NEW_TOKEN to 0x19

In draft-ietf-quic-transport.md:

>  
 Application protocols can signal application-specific protocol errors
 using the APPLICATION_CLOSE frame.  Errors that are specific to the
 transport, including all those described in this document, are carried
 in a CONNECTION_CLOSE frame.  Other than the type of error code they
 carry, these frames are identical in format and semantics.
 
-A CONNECTION_CLOSE, CRYPTO_CLOSE, or APPLICATION_CLOSE frame could be
-sent in a packet that is lost.  An endpoint SHOULD be prepared to
-retransmit a packet containing either frame type if it receives more
-packets on a terminated connection.  Limiting the number of
-retransmissions and the time over which this final packet is sent
+A CONNECTION_CLOSE, or APPLICATION_CLOSE frame could be sent in a packet that is

"," unnecessary

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

----==_mimepart_5b3239c74a384_46e32af470598f5030788e-- From nobody Tue Jun 26 06:09:31 2018 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 3CA2613104C for ; Tue, 26 Jun 2018 06:09:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 d8119UEgiQXi for ; Tue, 26 Jun 2018 06:09:23 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 601F113102C for ; Tue, 26 Jun 2018 06:09:23 -0700 (PDT) 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=v8NQkTGN7YywUsmYLGVnhH3uzhw=; b=ipXmAnnoGUPOP4FV 5M8xEdlrQY0tkTyssmTtpXijBj50m+pLgIxMoNKWeLA8CKHnsoqCH0HwToZ9+X52 JFf+x08vhGxcZte6QN0TwJOrao6pslrB2PHjltByAmINrCnYJ/eZGUm2dYaErQiW 1krrQ3dBRvPzRJjj4JYejpXULi0= Received: by filter0152p1iad2.sendgrid.net with SMTP id filter0152p1iad2-1855-5B323AF9-57 2018-06-26 13:09:13.989402165 +0000 UTC Received: from github-lowworker13-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id nh3aIBfoRoGw5oGOnSlexw for ; Tue, 26 Jun 2018 13:09:13.839 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker13-cp1-prd.iad.github.net (Postfix) with ESMTP id BEEBB20CE0 for ; Tue, 26 Jun 2018 06:09:13 -0700 (PDT) Date: Tue, 26 Jun 2018 13:09:14 +0000 (UTC) From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323af9bd854_48213fa335f8cf88417881"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2I1HGVlHj6fCbRgCKqqMRc+sSAs0MlXw8wXg lwafJvg6HzTUOjBrGz+xcMFlC1ARzXPXapkIHxPMict+tNsofdJ6NP6AMFN7oemr4RFdjQ3Lg3w6MC 7/EU0j0K+/baGH4StQPL/aaRreUAiOgRg+1v+piYlUWZ+HB1xtsb6pOc9g== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 13:09:29 -0000 ----==_mimepart_5b323af9bd854_48213fa335f8cf88417881 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I also prefer HANDSHAKE. -- 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/1476#issuecomment-400301512 ----==_mimepart_5b323af9bd854_48213fa335f8cf88417881 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I also prefer HANDSHAKE.

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

----==_mimepart_5b323af9bd854_48213fa335f8cf88417881-- From nobody Tue Jun 26 06:18:46 2018 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 33CDD130DEA for ; Tue, 26 Jun 2018 06:18:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 gvI_taaZgbi9 for ; Tue, 26 Jun 2018 06:18:42 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE5BF130DE1 for ; Tue, 26 Jun 2018 06:18:42 -0700 (PDT) Date: Tue, 26 Jun 2018 06:18:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530019122; bh=tw4qy5uVipRT0QzuYuM7tyq11Xmy/MtzLdgByc9OqFQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KQWZWFTJj+0gJ2SecgzlcpBJHf5UUsJP9NBXwmzOz3a9WzLNxgmjDNHmwok9oEScP oexmlhtNlEoZ/k2NtQXEjlkJcBoNJCgW9WAllE2azV7SOcxXcR2LbEAjhP5yGJ+gOR FfLpfoH443UeXb2INzvKWR6i1Kfh65361V3mW2og= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323d327a27_5ba33fbe66acaf80590840"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 13:18:45 -0000 ----==_mimepart_5b323d327a27_5ba33fbe66acaf80590840 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. The reflow makes this more difficult to review, but otherwise looks good. -- 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/1476#pullrequestreview-132013419 ----==_mimepart_5b323d327a27_5ba33fbe66acaf80590840 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

The reflow makes this more difficult to review, but otherwise looks good.

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

----==_mimepart_5b323d327a27_5ba33fbe66acaf80590840-- From nobody Tue Jun 26 06:21:52 2018 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 E9B34131054 for ; Tue, 26 Jun 2018 06:21:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 LYZSYre8c7V1 for ; Tue, 26 Jun 2018 06:21:36 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78599131072 for ; Tue, 26 Jun 2018 06:21:36 -0700 (PDT) Date: Tue, 26 Jun 2018 06:21:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530019295; bh=fn0LAt5d7nyOqEcrUCqQfjCtkBciK7iWEb/GU+U7l1I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dKKrIZXj6d8lREsYIEeWyu0Dzatw7fkg8TbPG9oy2gfyLmhwtPrz1Cb3ZFQoT7c8p wBg+Nt4wEqc/ArwLiibP8h9aDWuGsZeCnX7RMSIyNyH6d3qeCs5hgrXCESGayPX9ce QH8lVuvVARFCtgrU02fUQ0zzf0OH+KOWpzrpJVwg= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323ddfa8947_78302b1bf7e4af50755079"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Tue, 26 Jun 2018 13:21:50 -0000 ----==_mimepart_5b323ddfa8947_78302b1bf7e4af50755079 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks approved this pull request. Looks good to me. -- 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/1477#pullrequestreview-132014704 ----==_mimepart_5b323ddfa8947_78302b1bf7e4af50755079 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks approved this pull request.

Looks good to me.

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

----==_mimepart_5b323ddfa8947_78302b1bf7e4af50755079-- From nobody Tue Jun 26 06:25:01 2018 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 AD9DA130DE1 for ; Tue, 26 Jun 2018 06:24:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4kxXDPQSDriJ for ; Tue, 26 Jun 2018 06:24:52 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57CA7130DDE for ; Tue, 26 Jun 2018 06:24:52 -0700 (PDT) Date: Tue, 26 Jun 2018 06:24:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530019491; bh=LKsFYUdW2PNjSuOhS4eiEfe+HEcErLg0pY9MvjILUGc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ke6AqPv2PfDNIB5ewZ+nEKDotqSSJWkhFsbVLgUIicbN9rFRKVhQ76KADmikhtpmJ 4gtCENLFXzbw4DtfZ837sXP48cOhqZk0jA5IaSn95CDDSXzMNN71tAQOg1us2XBzRp rYnckG8gubPqT3RJH6GfivPssuvht2SD9KkXwtLk= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323ea3a02d5_72e82aeaf322ef58392495"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Tue, 26 Jun 2018 13:24:59 -0000 ----==_mimepart_5b323ea3a02d5_72e82aeaf322ef58392495 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I prefer CRYPTO over HANDSHAKE personally, for the same reason @mikkelfj indicated. It is used post handshake. There are other names similar to CRYTPO that work too; something like SECURITY or SEC_STREAM work too. -- 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/1476#issuecomment-400306763 ----==_mimepart_5b323ea3a02d5_72e82aeaf322ef58392495 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I prefer CRYPTO over HANDSHAKE personally, for the same reason @mikkelfj indicated. It is used post handshake. There are other names similar to CRYTPO that work too; something like SECURITY or SEC_STREAM work too.

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

----==_mimepart_5b323ea3a02d5_72e82aeaf322ef58392495-- From nobody Tue Jun 26 06:25:13 2018 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 70ECB131026 for ; Tue, 26 Jun 2018 06:25:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 ytSjgAEMJVmh for ; Tue, 26 Jun 2018 06:25:07 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 05434130DDE for ; Tue, 26 Jun 2018 06:25:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530019506; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=iT3zu4wx7/o8mdNbRbMZs/5IhqAgnuaPxngmkG5BuD0=; b=vPbAzj+thcSsxOUaE5f/2WxxY26oFtz07JYB0FDBc+txtpq8cOqoEOsCOrbBJ1EZpvHnM1b3 jXBs8WFe/wiUUVlc9WNP/CvaiWRuFohH3sK5ws59QWuoXYrkI+y+Fr7qDEPYC8Ik6IILodHk hec6y0AklLBBwW/8C3Lpqfx+rJ0= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: ianswett=users.noreply.github.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b323eb1.7f15cb642420-smtp-out-n01; Tue, 26 Jun 2018 13:25:05 -0000 (UTC) Date: Tue, 26 Jun 2018 06:25:04 -0700 From: ianswett Reply-To: ianswett To: quic-issues@ietf.org Message-ID: <5b323eb0b30c7_3d5c2b092df7dbfc111239@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d7fcd1: Replace default with recommended Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b323eb0b2aea_3d5c2b092df7dbfc111161"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 13:25:12 -0000 ----==_mimepart_5b323eb0b2aea_3d5c2b092df7dbfc111161 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-default Home: https://github.com/quicwg/base-drafts Commit: d7fcd1ab6ca99f2354897fea579b194600e2c8eb https://github.com/quicwg/base-drafts/commit/d7fcd1ab6ca99f2354897fea579b194600e2c8eb Author: ianswett Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Replace default with recommended Fixes #1475 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b323eb0b2aea_3d5c2b092df7dbfc111161-- From nobody Tue Jun 26 06:25:28 2018 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 B9794131026 for ; Tue, 26 Jun 2018 06:25:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4IIbGKz0Q6aK for ; Tue, 26 Jun 2018 06:25:25 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 47D40130DE1 for ; Tue, 26 Jun 2018 06:25:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=9mYP5jgNV8CX1OMzGYGQqSyzZpY=; b=mPXk6Js4YCuPQY99 eTL+ylCflmmSKm+CO247AL0xUW1rgY5QiGssrZJG3iXT6gh8+1sMrgsVlKd6h6BF wGsusbHaFTkwh9T+f448ol2DIWMxLM3AMB9xyvcrPttACfBU2xcoOwa1Tm8LDi/c SYNol6UBNwbOR8st8Neq2BQlOP8= Received: by filter0292p1iad2.sendgrid.net with SMTP id filter0292p1iad2-5934-5B323EC4-1 2018-06-26 13:25:24.225012551 +0000 UTC Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id fOyOTXfGTUKhXGYHu-Z1Zg for ; Tue, 26 Jun 2018 13:25:24.089 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 15A45C1A8A for ; Tue, 26 Jun 2018 06:25:24 -0700 (PDT) Date: Tue, 26 Jun 2018 13:25:24 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323ec4136db_5b952b2a32494f584978a1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0DK8zl6+UFrBA3Dy6ZeFo1UOuL93MJJeHP9Y fg2sCJiDNMH+PSedYiHjj1Faa3ae/w8suIUV16Cj5YidCETXL4OYi4TaSncZ0ZA8rDfqtAuU8JrpHK D/D7Ssx6O/xVbGy6w4nyv0t4Dsfn2r7gGuJ09ENCPQ/mTqQdUSnMXRB3TQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 13:25:27 -0000 ----==_mimepart_5b323ec4136db_5b952b2a32494f584978a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1475 You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1480 -- Commit Summary -- * Replace default with recommended -- File Changes -- M draft-ietf-quic-recovery.md (40) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1480.patch https://github.com/quicwg/base-drafts/pull/1480.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/1480 ----==_mimepart_5b323ec4136db_5b952b2a32494f584978a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1475

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

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

Commit Summary

  • Replace default with recommended

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 mute the thread.

----==_mimepart_5b323ec4136db_5b952b2a32494f584978a1-- From nobody Tue Jun 26 06:25:59 2018 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 AF937131026 for ; Tue, 26 Jun 2018 06:25:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 qQhNX5a20xfA for ; Tue, 26 Jun 2018 06:25:56 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2442E130DE1 for ; Tue, 26 Jun 2018 06:25:56 -0700 (PDT) Date: Tue, 26 Jun 2018 06:25:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530019555; bh=5YnrOdYaGYoIQ4+rXUb5NXnME1IfcOWVNBlSIjsWIu8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HVVt7dCYt+iwKvtSNztkbLSQmMYFH8Ks9XT/VMgGeUM3SqoreL25WpLccIUESzI3T NGnY7Ffp2w9upOY3unD3qKgKXtONGZ/Avjx0ebGgkAvh3J2K/zZcmEmWJgUNPdpRUG 25yTYI1XVbEEjpCwnPHnReZoruPhjgt8IFAuS1oY= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] "Default" max ack delay (#1475) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b323ee3766f2_46dd2af470598f50466785"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 13:25:58 -0000 ----==_mimepart_5b323ee3766f2_46dd2af470598f50466785 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good point, I sent out a PR to remove all uses of the word default and use recommended instead. -- 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/1475#issuecomment-400307181 ----==_mimepart_5b323ee3766f2_46dd2af470598f50466785 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Good point, I sent out a PR to remove all uses of the word default and use recommended instead.

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

----==_mimepart_5b323ee3766f2_46dd2af470598f50466785-- From nobody Tue Jun 26 06:33:42 2018 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 66959131072 for ; Tue, 26 Jun 2018 06:33:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 Ubyj7v0ymIt8 for ; Tue, 26 Jun 2018 06:33:28 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33508131055 for ; Tue, 26 Jun 2018 06:33:28 -0700 (PDT) Date: Tue, 26 Jun 2018 06:33:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530020007; bh=DlopExuLvnzNq6ws9cDr3cLPDs2d6n1ywRtyepztoUw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nFa9DljPYGsTqXxvOy+OUKbaq791C6E63N8Wbk9xTL9+kezauF7VIxreEe/u7GzZC Tlj5hpf6/FcxAcVJZh/S6shapr90zNFura5xe6f2ex/CjFYBf53F4iR2KJaI/hvkQO Smk++EWUL4u2UVJDruLVcR6SRn7Em1BmB/+IFI20= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3240a762497_e743fdaec05cf8899848"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Tue, 26 Jun 2018 13:33:41 -0000 ----==_mimepart_5b3240a762497_e743fdaec05cf8899848 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks approved this pull request. LGTM -- 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/1480#pullrequestreview-132020007 ----==_mimepart_5b3240a762497_e743fdaec05cf8899848 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks approved this pull request.

LGTM

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

----==_mimepart_5b3240a762497_e743fdaec05cf8899848-- From nobody Tue Jun 26 06:59:11 2018 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 7A35C130DE0 for ; Tue, 26 Jun 2018 06:59:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2WFVYpBQKZaH for ; Tue, 26 Jun 2018 06:59:06 -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 82B7C130DDD for ; Tue, 26 Jun 2018 06:59:05 -0700 (PDT) Date: Tue, 26 Jun 2018 06:59:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530021544; bh=P+/4uUuh7XMBfhdiZFmlvPVc07j7xPapQviIrs2l60Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WP3LHHlqg9PGQyqpC7TRM5GW3MOqHdwUFBcTRxZ3fBVJHqdnoFlerI1OEj9YBg+pU GiBKNeCROkbEEf5PsnbZFKxJRn11UreTQKptVihMW09U6SseOk7Pm8DFq3i/uHKRkL GIIhbjDSyhv05myf8tLm8mU69balXkXMOQ9Mcd1Y= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3246a87a042_4b1a2ab6561b0f581298df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 13:59:10 -0000 ----==_mimepart_5b3246a87a042_4b1a2ab6561b0f581298df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I also prefer CRYPTO over HANDSHAKE FWIW -- 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/1476#issuecomment-400318912 ----==_mimepart_5b3246a87a042_4b1a2ab6561b0f581298df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I also prefer CRYPTO over HANDSHAKE FWIW

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

----==_mimepart_5b3246a87a042_4b1a2ab6561b0f581298df-- From nobody Tue Jun 26 07:40:08 2018 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 1016D130DF6 for ; Tue, 26 Jun 2018 07:40:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 uwcQ_oFmmH_4 for ; Tue, 26 Jun 2018 07:40:05 -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 45C4B130DF2 for ; Tue, 26 Jun 2018 07:40:05 -0700 (PDT) Date: Tue, 26 Jun 2018 07:40:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530024004; bh=NEFgIJsxDOhSge8X3NKtkD9WzLqCq0VV5/MHdrGovXk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=z19MfVukocR4yBq8tJSg34dY7IqgJX6FCEhIsJmYitLETVQDzkJnjOoUCeSEZ84/0 jOOGKgxHtv+VOt/LAcSVYiQJSLUybItrjkzhLsdKlvlZL6xizLcvMS34jxfA9kgIfZ LXnNTI7S+ZA1f9p004jQg1qcOceOL/cNf4OFgpqA= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32504457b0d_3e0f3fc5cfd9cf7c180925"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Tue, 26 Jun 2018 14:40:08 -0000 ----==_mimepart_5b32504457b0d_3e0f3fc5cfd9cf7c180925 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Regarding post-handshake events -- I consider these part of the handshake path. They simply occur later in time. This really is a minor detail. I just don't like the name CRYPTO. I'm also not fond of SECURITY or SEC_STREAM. -- 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/1476#issuecomment-400333619 ----==_mimepart_5b32504457b0d_3e0f3fc5cfd9cf7c180925 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Regarding post-handshake events -- I consider these part of the handshake path. They simply occur later in time. This really is a minor detail. I just don't like the name CRYPTO. I'm also not fond of SECURITY or SEC_STREAM.

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

----==_mimepart_5b32504457b0d_3e0f3fc5cfd9cf7c180925-- From nobody Tue Jun 26 08:22:37 2018 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 5BBE713103C for ; Tue, 26 Jun 2018 08:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 zKHjgHiHAZyv for ; Tue, 26 Jun 2018 08:22:34 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 2476613102E for ; Tue, 26 Jun 2018 08:22:34 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530026553; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=bClR/FRrbjqcBQ0/OEtmUwPR6jjwqyMCuNc/TE2645o=; b=IedrUCiuahAQRk9NBXHmotP5ZOEFRBTIFsD8xTKqnNrUbGwVE5TZllGigbk2ySyUbcN2VXbu rhfI4v7JWDsqjUHir7RV9jIypzswxdcoF6E9MbXg4hAeb31tTXtAMKsS0qfPjjPbKQfhHWCT 3Aa9yzo0pAKJY+xp+MT38G5Vok0= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=users.noreply.github.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b325a39.7fb5b070e900-smtp-out-n02; Tue, 26 Jun 2018 15:22:33 -0000 (UTC) Date: Tue, 26 Jun 2018 08:22:33 -0700 From: afrind Reply-To: afrind To: quic-issues@ietf.org Message-ID: <5b325a3940c2b_e192b0862849c0811717@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 758310: Modify codepoints on decoder and request/push stre... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b325a39407e5_e192b0862849c08116d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 15:22:36 -0000 ----==_mimepart_5b325a39407e5_e192b0862849c08116d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 7583103bc5070b5e02a29b8546eaee06f5524277 https://github.com/quicwg/base-drafts/commit/7583103bc5070b5e02a29b8546eaee06f5524277 Author: afrind Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Modify codepoints on decoder and request/push streams for consistency (#1472) * Modify codepoints on decoder and request/push streams for consistency The prefix lengths remain the same but the instruction bits now follow the rule that each instruction has at most one '1' bit. Fixes #1471 * Swap TSS and Stream Cancellation codepoints This is somewhat superficial, but we're changing it anyways so bear with me. HEADER_ACK and STREAM_CANCEL are almost identical, so code processing them should be next to each other. By swapping TSS and Stream Cancel codepoints, the processing code might be more readable. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b325a39407e5_e192b0862849c08116d0-- From nobody Tue Jun 26 08:22:49 2018 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 07647131038 for ; Tue, 26 Jun 2018 08:22:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 3BbIs0QLbQdH for ; Tue, 26 Jun 2018 08:22:42 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E23DF13102E for ; Tue, 26 Jun 2018 08:22:42 -0700 (PDT) Date: Tue, 26 Jun 2018 08:22:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530026562; bh=QWNvuC1VkOowUPadLv6+flZE3lVB8eEOVbdLC6vuWcs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=avX39gqn9ZCXqGa8qMofAcwo0Y+QAFFIOxiVR4Bt1PyH4AepjKIxcKeZBJxMQxsCU 9smuozUGSsHUiaafgbKxwdHuKQC3S/UCTVcVSJqao+VpGIbBG/tHL04SDyJ9kr0TJ/ qW2k/KxLtEcC5uUzAkM0uVNKkGtDXhe3jV5N//+8= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QPACK instruction code points are inconsistent (#1471) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b325a422ac06_3c082af77ea7ef54287947"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Tue, 26 Jun 2018 15:22:47 -0000 ----==_mimepart_5b325a422ac06_3c082af77ea7ef54287947 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1471 via #1472. -- 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/1471#event-1701724204 ----==_mimepart_5b325a422ac06_3c082af77ea7ef54287947 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1471 via #1472.

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

----==_mimepart_5b325a422ac06_3c082af77ea7ef54287947-- From nobody Tue Jun 26 08:22:55 2018 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 1774C13102E for ; Tue, 26 Jun 2018 08:22:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 aOFGz8MgaSCd for ; Tue, 26 Jun 2018 08:22:45 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 BB4A013103C for ; Tue, 26 Jun 2018 08:22:44 -0700 (PDT) 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=Zcdq7dhZqCdBaaIlpw/VF8ZX5y8=; b=d8EXfEBZwdboCh/8 +wC3wf8MkdQ5s0Ajznql404j4hiVyvOUAB/KJvgggSHcGkuuT8MQQhsPCDFxioMo lpKzukc2jb4IUNYnz/JB3/+azd1fCXlq8OT6jDpU7s1XtbGjomq4QW3+UpZlC0tk qa5AAehwhvxHKo3NXUU6Qe43wRQ= Received: by filter1625p1mdw1.sendgrid.net with SMTP id filter1625p1mdw1-13356-5B325A43-C 2018-06-26 15:22:43.3033572 +0000 UTC Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id KNYmVaSXSqaEKt4PI8-jsg for ; Tue, 26 Jun 2018 15:22:43.211 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id 30109A8028C for ; Tue, 26 Jun 2018 08:22:43 -0700 (PDT) Date: Tue, 26 Jun 2018 15:22:43 +0000 (UTC) From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b325a432cdf0_62ff2b0c6d802f6027337e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak26K3LvtEx5wMXeu8P54Tw1HLiSSaeuMwvVbc i1UCIIqBwAFm2TG1AQ8/vqMeOyXOov6SBFID9YAxgRPm1F4ddWFtpD18a4cbj8CljTTykW1F8Rm8Zv +w7gtAvjg1vOFXqpp/PRva2JZamqYuzT6T1L1iXOLOvGE0RKaPoOGIRXUQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 15:22:49 -0000 ----==_mimepart_5b325a432cdf0_62ff2b0c6d802f6027337e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1472. -- 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/1472#event-1701724198 ----==_mimepart_5b325a432cdf0_62ff2b0c6d802f6027337e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1472.

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

----==_mimepart_5b325a432cdf0_62ff2b0c6d802f6027337e-- From nobody Tue Jun 26 10:51:24 2018 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 77DCB1310E8 for ; Tue, 26 Jun 2018 10:51:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Rq9IanePPIWv for ; Tue, 26 Jun 2018 10:51:16 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 83C091310E1 for ; Tue, 26 Jun 2018 10:51:16 -0700 (PDT) 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=B1+zso8dCBWRi1RF45h2zXvIQQY=; b=oI3Bd5KOYFSpKajp VGUq4tLr7MDn5Pg6DDrndMlThYijVOq7ZNBrgIYXI701y5FqEGWsci0gptNUWuqa Vqj1XVt723Z69GFSjl7sWt/2jk52C8uW5SNaDRT5xh8g50FK0y5owOZPLach75mz Sytjn+yqs2dE6XFBLSWQuLtgQ+Y= Received: by filter1785p1mdw1.sendgrid.net with SMTP id filter1785p1mdw1-8917-5B327CD8-19 2018-06-26 17:50:16.338212385 +0000 UTC Received: from github-lowworker7-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0037p1mdw1.sendgrid.net (SG) with ESMTP id 0SMG01wsSI6N2cNW799l1A for ; Tue, 26 Jun 2018 17:50:15.949 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker7-cp1-prd.iad.github.net (Postfix) with ESMTP id A8EC59FB04 for ; Tue, 26 Jun 2018 10:50:15 -0700 (PDT) Date: Tue, 26 Jun 2018 17:50:16 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Prevent connection ID exhaustion (#1468) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b327cd7a7027_1a0b3fd9d01c8f8887444"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1v7QkZo8yNIiXkcuXo//AGwm7aJ8ye0EoLi3 aM6XCsff2k5f84b6vgErxYyepRGirbBcmuo8n3SwVckPcQD0LrE2RVHCZPMNn1T0QaM/ZB3uxxJh2q obDtsTX3yd9C4HXz5y2T0T9NHwbXUZxSu1KpEKF0AqBTDHu/hieBEu/pF/TQKeyaYXVJuTbXP5WXBg c= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 17:51:23 -0000 ----==_mimepart_5b327cd7a7027_1a0b3fd9d01c8f8887444 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Right, but say I've chosen to receive a zero-length connection ID and you choose an eight-byte connection ID. Because you're always going to send me a zero-length connection ID, you'll never need more -- you'll never change, and so I'm prohibited from sending you a NEW_CONNECTION_ID frame. So how do *I* prompt *you* to send me more? -- 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/1468#issuecomment-400404919 ----==_mimepart_5b327cd7a7027_1a0b3fd9d01c8f8887444 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Right, but say I've chosen to receive a zero-length connection ID and yo= u choose an eight-byte connection ID. Because you're always going to send = me a zero-length connection ID, you'll never need more -- you'll never chan= ge, and so I'm prohibited from sending you a NEW_CONNECTION_ID frame.

So how do I prompt you to send me more?

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b327cd7a7027_1a0b3fd9d01c8f8887444-- From nobody Tue Jun 26 11:03:52 2018 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 6F60F13112B for ; Tue, 26 Jun 2018 11:03:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 t-g9aGbFZnV3 for ; Tue, 26 Jun 2018 11:03:46 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 0DA7013111E for ; Tue, 26 Jun 2018 11:03:45 -0700 (PDT) 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=h036Ury8DLV2ASS0NfjnP1no9kk=; b=qW5QnocfF/SGsF6q GRpWm9QyPT1l7VAStAKgx9TjkaDQUDfexCCNMQt2+UqSxwbInqeJf9DVnwveuvfl O8Ynp1aK7Vvq4rKCOMCnHkqX6aNBpB9oiqCL877AoPQxpo3H+c3SgN+MjrYCHjPn KUeD1Sk2b7Pt4NR5cebE20ToWhY= Received: by filter1325p1mdw1.sendgrid.net with SMTP id filter1325p1mdw1-10775-5B327FFE-7 2018-06-26 18:03:42.079710862 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id RCAH-Pa2RUiknLFrsJySuQ for ; Tue, 26 Jun 2018 18:03:41.932 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id E0F743FFCF for ; Tue, 26 Jun 2018 11:03:41 -0700 (PDT) Date: Tue, 26 Jun 2018 18:03:42 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b327ffddf2c9_29a13fc4f7d08f802558f1"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2PjSULZ4EkbwYoBiWOeo9J8xb0cSl3vZMDp2 Dob92ZE4FQrU07AULCyUI44HQ+eKJrMuaVOzDwlq3q8Gt9oMRA4kkZ7FVGMxYN/sY/vl2zUPo2x1Zz 7IlOfAcAICclGPDVbmPKpB3jQXpZa8GLOENP/UFk0q4ZY5TgT7jPlXMoa8lQ84AnzHOGBZwRhL4DJp g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 18:03:50 -0000 ----==_mimepart_5b327ffddf2c9_29a13fc4f7d08f802558f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > +selected during the handshake coming first. Additional connection IDs are +provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each +with a specified sequence number. The series of connection IDs issued SHOULD be +contiguous, but might not appear to be upon receipt due to reordering or loss. + +Each connection ID MUST be used on only one local address. When packets are sent +for the first time on a new local address, a new connection ID MUST be used with +a higher sequence number than any connection ID previously used on any local +address. At any time, an endpoint MAY change to a new connection ID on a local +address already in use. + +An endpoint MUST NOT send packets with a connection ID which has a lower +sequence number than the highest sequence number of any connection ID ever sent +or received on that local address. + +Implementations SHOULD ensure that peers have a connection ID with a matching But the trade-off is that lost packets can cause a peer to appear to violate this temporarily, so it's not realistically enforceable by a peer. You can't "MUST ensure" something has arrived on the other side, only detect whether it has or not. And the connection doesn't actually break; the peer will have to advance to a higher-order CID, which will force the endpoint to move off of the one that doesn't have a match (assuming it still hasn't arrived). Actually, what a smart implementation could do is to bundle the NEW_CONNECTION_ID frame with the corresponding CID in every packet between when it changes to a new CID until *something* gets ACK'd. -- 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/1465#discussion_r198244528 ----==_mimepart_5b327ffddf2c9_29a13fc4f7d08f802558f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> +selected during the handshake coming first.  Additional connection IDs are
+provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each
+with a specified sequence number.  The series of connection IDs issued SHOULD be
+contiguous, but might not appear to be upon receipt due to reordering or loss.
+
+Each connection ID MUST be used on only one local address. When packets are sent
+for the first time on a new local address, a new connection ID MUST be used with
+a higher sequence number than any connection ID previously used on any local
+address.  At any time, an endpoint MAY change to a new connection ID on a local
+address already in use.
+
+An endpoint MUST NOT send packets with a connection ID which has a lower
+sequence number than the highest sequence number of any connection ID ever sent
+or received on that local address.
+
+Implementations SHOULD ensure that peers have a connection ID with a matching

But the trade-off is that lost packets can cause a peer to appear to violate this temporarily, so it's not realistically enforceable by a peer. You can't "MUST ensure" something has arrived on the other side, only detect whether it has or not. And the connection doesn't actually break; the peer will have to advance to a higher-order CID, which will force the endpoint to move off of the one that doesn't have a match (assuming it still hasn't arrived).

Actually, what a smart implementation could do is to bundle the NEW_CONNECTION_ID frame with the corresponding CID in every packet between when it changes to a new CID until something gets ACK'd.

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

----==_mimepart_5b327ffddf2c9_29a13fc4f7d08f802558f1-- From nobody Tue Jun 26 11:10:50 2018 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 D522A131134 for ; Tue, 26 Jun 2018 11:10:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nJSwlZ97ph01 for ; Tue, 26 Jun 2018 11:10:32 -0700 (PDT) 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 DE1A71310FF for ; Tue, 26 Jun 2018 11:10:31 -0700 (PDT) Date: Tue, 26 Jun 2018 11:10:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530036630; bh=CXqwMHDZIg1KYIUMptRsiYNxkAL+Xg4iQyVLExuKIMk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PfQG/MEVJDKl4GMBmWwG+JBgOsZ369v+lzK1cxnkVV8vevinrY0+XCZofpGK1wdXT et80Vy6/OINjAtzFh/d+sYMc16xZZHpHfeUwljfrxmuh8RRESr5cZb4QFDiChCBcrq rKEp4hc6wA7g9YoHVCL7SH0nCVWAk3sP7Pca39BM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b328196bbd48_1ee63fbdb060ef84710f4"; 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.26 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: Tue, 26 Jun 2018 18:10:47 -0000 ----==_mimepart_5b328196bbd48_1ee63fbdb060ef84710f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > +series of connection IDs over the lifetime of a connection. The series of +connection IDs issued by an endpoint is ordered, with the final connection ID +selected during the handshake coming first. Additional connection IDs are +provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each +with a specified sequence number. The series of connection IDs issued SHOULD be +contiguous, but might not appear to be upon receipt due to reordering or loss. + +Each connection ID MUST be used on only one local address. When packets are sent +for the first time on a new local address, a new connection ID MUST be used with +a higher sequence number than any connection ID previously used on any local +address. At any time, an endpoint MAY change to a new connection ID on a local +address already in use. + +An endpoint MUST NOT send packets with a connection ID which has a lower +sequence number than the highest sequence number of any connection ID ever sent +or received on that local address. Good point. I tried to put it mid-discussion, but it didn't flow, so right now it's tucked at the end. Editorial discretion welcome. -- 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/1465#discussion_r198246753 ----==_mimepart_5b328196bbd48_1ee63fbdb060ef84710f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> +series of connection IDs over the lifetime of a connection. The series of
+connection IDs issued by an endpoint is ordered, with the final connection ID
+selected during the handshake coming first.  Additional connection IDs are
+provided using the NEW_CONNECTION_ID frame ({{frame-new-connection-id}}), each
+with a specified sequence number.  The series of connection IDs issued SHOULD be
+contiguous, but might not appear to be upon receipt due to reordering or loss.
+
+Each connection ID MUST be used on only one local address. When packets are sent
+for the first time on a new local address, a new connection ID MUST be used with
+a higher sequence number than any connection ID previously used on any local
+address.  At any time, an endpoint MAY change to a new connection ID on a local
+address already in use.
+
+An endpoint MUST NOT send packets with a connection ID which has a lower
+sequence number than the highest sequence number of any connection ID ever sent
+or received on that local address.

Good point. I tried to put it mid-discussion, but it didn't flow, so right now it's tucked at the end. Editorial discretion welcome.

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

----==_mimepart_5b328196bbd48_1ee63fbdb060ef84710f4-- From nobody Tue Jun 26 11:12:37 2018 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 B9FAD1310EB for ; Tue, 26 Jun 2018 11:12:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 mKv6yaXNd-rw for ; Tue, 26 Jun 2018 11:12:33 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 1443D130F08 for ; Tue, 26 Jun 2018 11:12:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530036752; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=4pN8OVQisAp/L6ec7KIboFE250J1jybYv3yZKeuEo3g=; b=yaVfsvKRh2Lw/yatJYlj3j+SEftS7m5KDkWQzzuF/7WvjihwbjRS5R3KaNPioyBs4ApkevZ+ O6CfFUxg2rC7I4LG+1rdbTad1cmtTrgJwRYYMlOTa8KjwzLABhzFhdVyPqpxZjbaA/7amVbb VTy6rfBnjo++2JYlSHCTYqKif3I= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b328210.7f6a2d492c00-smtp-out-n03; Tue, 26 Jun 2018 18:12:32 -0000 (UTC) Date: Tue, 26 Jun 2018 11:12:32 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b3282101f01f_49952adcfc773c0c3291d@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e1aa62: Revert "Remove sequence number from NEW_CONNECTION... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3282101ec15_49952adcfc773c0c328d0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 18:12:35 -0000 ----==_mimepart_5b3282101ec15_49952adcfc773c0c328d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts Commit: e1aa62531825699ae815534096dda6d99a9bf9ae https://github.com/quicwg/base-drafts/commit/e1aa62531825699ae815534096dda6d99a9bf9ae Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Revert "Remove sequence number from NEW_CONNECTION_ID" This reverts commit 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6. Commit: 7d7850061e3d7fe01b1b31551f1689cce5f2464a https://github.com/quicwg/base-drafts/commit/7d7850061e3d7fe01b1b31551f1689cce5f2464a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Require CID sequence number ratcheting Commit: fdc9651e19cdd1ed794f66a44c01f800651d3a1a https://github.com/quicwg/base-drafts/commit/fdc9651e19cdd1ed794f66a44c01f800651d3a1a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Prefer equality Commit: 26a3a1f06d21b858814b5f71f8c96d457edce61f https://github.com/quicwg/base-drafts/commit/26a3a1f06d21b858814b5f71f8c96d457edce61f Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Nick's reword Commit: c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 https://github.com/quicwg/base-drafts/commit/c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- New CID section Commit: 32c8bc1477966608fd5e7015317cd2887e8553ab https://github.com/quicwg/base-drafts/commit/32c8bc1477966608fd5e7015317cd2887e8553ab Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Additional recommendations Compare: https://github.com/quicwg/base-drafts/compare/ef8abfb7393a...32c8bc147796 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3282101ec15_49952adcfc773c0c328d0-- From nobody Tue Jun 26 11:21:19 2018 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 E116A1310F6 for ; Tue, 26 Jun 2018 11:21:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 39mepllMV9Ti for ; Tue, 26 Jun 2018 11:21:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FD4F1310F4 for ; Tue, 26 Jun 2018 11:21:14 -0700 (PDT) Date: Tue, 26 Jun 2018 11:21:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530037273; bh=M9ZOLX/mskuHUsM26m0MDuQEM9+jfBoXUQkeRJiWhAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ICHQcBVEQMtemvTCBM9ffHUzcw/janf6VsbowXfdGtc0dheZhlwU5zrjySdszN3Q7 0svDXlraDO7inurO3fhVcxJSFd3PL+2qIF10Vf6g4QZpzIcnMwoMtjHCFbEMWXto/N gNhLeb4rOz4enYQJ3EwluBbONBysIGBMnl0fzNPI= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b328419c2cc7_16613f95c1100f7c107064"; 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.26 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: Tue, 26 Jun 2018 18:21:17 -0000 ----==_mimepart_5b328419c2cc7_16613f95c1100f7c107064 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. > @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document. All QUIC frames are idempotent. That is, a valid frame does not cause undesirable side effects or errors when received more than once. +The Frame Type field uses a variable length integer encoding (see +{{integer-encoding}}) with one exception. To ensure simple and efficient +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. And what am I required to do if I encounter a 2+ byte encoding of 7? > @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document. All QUIC frames are idempotent. That is, a valid frame does not cause undesirable side effects or errors when received more than once. +The Frame Type field uses a variable length integer encoding (see +{{integer-encoding}}) with one exception. To ensure simple and efficient +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. + +## Extension Frames + +QUIC frames do not use a self-describing encoding. An endpoint therefore needs +to understand the syntax of all frame before it can successfully process a all frames / each frame > +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. + +## Extension Frames + +QUIC frames do not use a self-describing encoding. An endpoint therefore needs +to understand the syntax of all frame before it can successfully process a +packet. This allows for efficient encoding of frames, but it means that an +endpoint cannot send a frame of a type that is unknown to its peer. + +An extension to QUIC that wishes to use a new type of frame MUST first ensure +that a peer is able to understand the frame. An endpoint can use a transport +parameter to signal its willingness to receive a new type of frame, or even +multiple types of frame with the one transport parameter. ...receive one or more extension frame types. -- 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/1473#pullrequestreview-132145266 ----==_mimepart_5b328419c2cc7_16613f95c1100f7c107064 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

In draft-ietf-quic-transport.md:

> @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document.
 All QUIC frames are idempotent.  That is, a valid frame does not cause
 undesirable side effects or errors when received more than once.
 
+The Frame Type field uses a variable length integer encoding (see
+{{integer-encoding}}) with one exception.  To ensure simple and efficient
+implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.

And what am I required to do if I encounter a 2+ byte encoding of 7?

In draft-ietf-quic-transport.md:

> @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document.
 All QUIC frames are idempotent.  That is, a valid frame does not cause
 undesirable side effects or errors when received more than once.
 
+The Frame Type field uses a variable length integer encoding (see
+{{integer-encoding}}) with one exception.  To ensure simple and efficient
+implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.
+
+## Extension Frames
+
+QUIC frames do not use a self-describing encoding.  An endpoint therefore needs
+to understand the syntax of all frame before it can successfully process a

all frames / each frame

In draft-ietf-quic-transport.md:

> +defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.
+
+## Extension Frames
+
+QUIC frames do not use a self-describing encoding.  An endpoint therefore needs
+to understand the syntax of all frame before it can successfully process a
+packet.  This allows for efficient encoding of frames, but it means that an
+endpoint cannot send a frame of a type that is unknown to its peer.
+
+An extension to QUIC that wishes to use a new type of frame MUST first ensure
+that a peer is able to understand the frame.  An endpoint can use a transport
+parameter to signal its willingness to receive a new type of frame, or even
+multiple types of frame with the one transport parameter.

...receive one or more extension frame types.

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

----==_mimepart_5b328419c2cc7_16613f95c1100f7c107064-- From nobody Tue Jun 26 11:45:15 2018 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 113271310FC for ; Tue, 26 Jun 2018 11:45:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 up9JB_hDb7aQ for ; Tue, 26 Jun 2018 11:45:09 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250EE1310F8 for ; Tue, 26 Jun 2018 11:45:08 -0700 (PDT) Date: Tue, 26 Jun 2018 11:45:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530038707; bh=+uCU3c80bV8xecL+Jo100kknVkFDDQz80YvyxzLHZ4M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cJ/5yW/J8PaclsG/8cSII+HeOJ3R4CPeWHKO6tTLHOLJuayzB+SU6ICUqHPzvW+zv KYmUT5b556NpPyaO8y3+mNNV7TLiSSYtMyiy3m92BAbfBTyc8/dBx7Z+oHCHryyHRJ iCwRaKsd5s89faxlPybw8sIJjy4ezgwtBkQoCwvs= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3289b3adf25_b193fd0d58e6f808278c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 18:45:13 -0000 ----==_mimepart_5b3289b3adf25_b193fd0d58e6f808278c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. Looking good. > @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document. All QUIC frames are idempotent. That is, a valid frame does not cause undesirable side effects or errors when received more than once. +The Frame Type field uses a variable length integer encoding (see +{{integer-encoding}}) with one exception. To ensure simple and efficient +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. Agreed, I think we either need to say you MAY close the connection or this is a SHOULD not a MUST > +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. + +## Extension Frames + +QUIC frames do not use a self-describing encoding. An endpoint therefore needs +to understand the syntax of all frame before it can successfully process a +packet. This allows for efficient encoding of frames, but it means that an +endpoint cannot send a frame of a type that is unknown to its peer. + +An extension to QUIC that wishes to use a new type of frame MUST first ensure +that a peer is able to understand the frame. An endpoint can use a transport It would be nice to have an example here at some point, but since we don't have any extension frames, I guess that's for the future? -- 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/1473#pullrequestreview-132154963 ----==_mimepart_5b3289b3adf25_b193fd0d58e6f808278c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

Looking good.

In draft-ietf-quic-transport.md:

> @@ -921,6 +924,30 @@ explained in more detail as they are referenced later in the document.
 All QUIC frames are idempotent.  That is, a valid frame does not cause
 undesirable side effects or errors when received more than once.
 
+The Frame Type field uses a variable length integer encoding (see
+{{integer-encoding}}) with one exception.  To ensure simple and efficient
+implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.

Agreed, I think we either need to say you MAY close the connection or this is a SHOULD not a MUST

In draft-ietf-quic-transport.md:

> +implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.
+
+## Extension Frames
+
+QUIC frames do not use a self-describing encoding.  An endpoint therefore needs
+to understand the syntax of all frame before it can successfully process a
+packet.  This allows for efficient encoding of frames, but it means that an
+endpoint cannot send a frame of a type that is unknown to its peer.
+
+An extension to QUIC that wishes to use a new type of frame MUST first ensure
+that a peer is able to understand the frame.  An endpoint can use a transport

It would be nice to have an example here at some point, but since we don't have any extension frames, I guess that's for the future?

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

----==_mimepart_5b3289b3adf25_b193fd0d58e6f808278c-- From nobody Tue Jun 26 11:57:49 2018 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 8A952131101 for ; Tue, 26 Jun 2018 11:57:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Sz7CZt2vEKWF for ; Tue, 26 Jun 2018 11:57:44 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4A11310F8 for ; Tue, 26 Jun 2018 11:57:44 -0700 (PDT) Date: Tue, 26 Jun 2018 11:57:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530039463; bh=OD+2TnTf6KXaDSyNlvtAeFlpRGhwywlOHcIc9+DioeY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sbz9trPNr0BsbmI1oQhgyp3w3zdAkfnHpyEYi3RsWGrff+wCdoQi9hMWwxN9fiyvc 29hCGFzBE7YOJawKzoSBhQnipw0vbnrXrObILfZaDJ9ekDKfVR2lWVK6cCNAWFRaN5 c2Xa2S2f3a/0qe0e0EhNgGDM5tBD4Kx7b0LlwMTk= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b328ca7d26c0_71a62ae1d99a2f501258e0"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 18:57:47 -0000 ----==_mimepart_5b328ca7d26c0_71a62ae1d99a2f501258e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Such reflow. Wow. I prefer CRYPTO. But either is better than the current CRYPTO_HS. All this reflow is going to rot rapidly, so if you want to keep discussing this name, I'd at least submit the reflow/typo changes and discuss the name separately. -- 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/1476#issuecomment-400425564 ----==_mimepart_5b328ca7d26c0_71a62ae1d99a2f501258e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Such reflow. Wow.

I prefer CRYPTO. But either is better than the current CRYPTO_HS.

All this reflow is going to rot rapidly, so if you want to keep discussing this name, I'd at least submit the reflow/typo changes and discuss the name separately.

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

----==_mimepart_5b328ca7d26c0_71a62ae1d99a2f501258e0-- From nobody Tue Jun 26 11:57:57 2018 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 EAC15131104 for ; Tue, 26 Jun 2018 11:57:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 BW_R1BMvP08D for ; Tue, 26 Jun 2018 11:57:51 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B525F131101 for ; Tue, 26 Jun 2018 11:57:51 -0700 (PDT) Date: Tue, 26 Jun 2018 11:57:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530039470; bh=UukdSZMJgYAOtcgF0qjCtyBDus4+h0dPjCA96KnyV5M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cM1IG/st/TquDgV4REYAFbRnOVgVFaaLjiJDR0K2VvGlgILwOhqmvONk4qXNcCaGd Vn9B5dKITnEEqbldEC1A2q3ft19uf/8egolHtHm4aZ/a+kftNfL+AvMhDHaBhb9PDv bru/CtRhqh9DSP5CtKs5KZU0bnzgHg+QHvgn3rdU= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b328caea04f7_58932ab335e40f582549e6"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 18:57:54 -0000 ----==_mimepart_5b328caea04f7_58932ab335e40f582549e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar approved this pull request. -- 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/1476#pullrequestreview-132160665 ----==_mimepart_5b328caea04f7_58932ab335e40f582549e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar approved this pull request.

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

----==_mimepart_5b328caea04f7_58932ab335e40f582549e6-- From nobody Tue Jun 26 12:16:55 2018 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 ADC8113112E for ; Tue, 26 Jun 2018 12:16:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 q3Y15XW3LdAs for ; Tue, 26 Jun 2018 12:16:43 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14190131126 for ; Tue, 26 Jun 2018 12:16:43 -0700 (PDT) Date: Tue, 26 Jun 2018 12:16:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530040602; bh=tvAR6plkCN4XVTrUBl7Z4vH6gA4MsVsPmK/oN/CSkV4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aG6z47GMxysTrYWtxjts7DP+TOzGYgGi8k1rd4CQflo5sj95Pdh6hNdlIhPbEyyAg tbyvXqfblZxMGgFwzrDQsblRIvTXytPymyKosTuQ8HD+1Z8rTFOC+/tP8IAj9xodlH JaB243IM686/xlUJ1HXAI4XyDokHAkzS0IOFkyys= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32911a737dc_41943f871b58cf78193472"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 19:16:55 -0000 ----==_mimepart_5b32911a737dc_41943f871b58cf78193472 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar approved this pull request. Yes, definitely. -- 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/1477#pullrequestreview-132167155 ----==_mimepart_5b32911a737dc_41943f871b58cf78193472 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar approved this pull request.

Yes, definitely.

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

----==_mimepart_5b32911a737dc_41943f871b58cf78193472-- From nobody Tue Jun 26 12:21:58 2018 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 81181131110 for ; Tue, 26 Jun 2018 12:21:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Sc4ahqnxRLLJ for ; Tue, 26 Jun 2018 12:21:53 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCE3E13110D for ; Tue, 26 Jun 2018 12:21:52 -0700 (PDT) Date: Tue, 26 Jun 2018 12:21:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530040911; bh=U6kD6Un1PH+sA+tit4TM2r/CjBc9iOBtdrb+PmA29Gg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1jFjd5XWMYAoQcxPYd9UWqFqh9NhKxttllm8M/n0MIgRPoijNp+yrVIJV/h1E7Vdl PCI4EhGqI2bf+2pEbrALe8k3voHT1ES2xTXusZbTdPPxWwf1xpPvDD1UWVTrkgl9sO ADjVaZdySvPw2EoihIm2HdSj7YD8SguWZ5SmCRkA= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32924ff1018_34f03f9f7b7fcf8819024"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 19:21:55 -0000 ----==_mimepart_5b32924ff1018_34f03f9f7b7fcf8819024 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar commented on this pull request. > @@ -423,7 +423,7 @@ QUIC SHOULD delay sending acknowledgements in response to packets, but MUST NOT excessively delay acknowledgements of packets containing non-ack frames. Specifically, implementaions MUST attempt to enforce a maximum ack delay to avoid causing the peer spurious -timeouts. The default maximum ack delay in QUIC is 25ms. +timeouts. The RECOMMENDED maximum ack delay in QUIC is 25ms. Why is only this recommendation capitalized? I think we should use capitalized RECOMMEND everywhere below -- 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/1480#pullrequestreview-132168775 ----==_mimepart_5b32924ff1018_34f03f9f7b7fcf8819024 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -423,7 +423,7 @@ QUIC SHOULD delay sending acknowledgements in response to packets,
 but MUST NOT excessively delay acknowledgements of packets containing
 non-ack frames.  Specifically, implementaions MUST attempt to
 enforce a maximum ack delay to avoid causing the peer spurious
-timeouts.  The default maximum ack delay in QUIC is 25ms.
+timeouts.  The RECOMMENDED maximum ack delay in QUIC is 25ms.

Why is only this recommendation capitalized? I think we should use capitalized RECOMMEND everywhere below

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

----==_mimepart_5b32924ff1018_34f03f9f7b7fcf8819024-- From nobody Tue Jun 26 12:40:43 2018 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 56AF6130E23 for ; Tue, 26 Jun 2018 12:40:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 TQzzXjeuPswv for ; Tue, 26 Jun 2018 12:40:38 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 B4E81128CF3 for ; Tue, 26 Jun 2018 12:40:38 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530042038; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=fwNaztVixD5eURfETCRYvXoGMQdvovI52bqK+E0g4pM=; b=Vl+rWfPZP2U0CjqCtdgq1SwMF9q1pF0ig4or8bkKxDgcLRoCueh+Ntpk+vl/fpiy6mDBpxw2 M4EWET94dhk8ZHbZd1i19pFqbMq9F+aMAMPIMFFe2jVnKsRPSMmU0F+sX8X7s2z/S7ex5o5N WS3U75shzMq06QjFK6M6q4DW63k= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: ianswett=users.noreply.github.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b3296b5.7f49f81d71e0-smtp-out-n01; Tue, 26 Jun 2018 19:40:37 -0000 (UTC) Date: Tue, 26 Jun 2018 12:40:36 -0700 From: ianswett Reply-To: ianswett To: quic-issues@ietf.org Message-ID: <5b3296b4545bc_4e9b2b2072495c1064267@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ff8aae: RECOMMENDED Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3296b453f67_4e9b2b2072495c106417"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 19:40:41 -0000 ----==_mimepart_5b3296b453f67_4e9b2b2072495c106417 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-default Home: https://github.com/quicwg/base-drafts Commit: ff8aae88251ae1fbf1a85b09d0cfbd6208c5878b https://github.com/quicwg/base-drafts/commit/ff8aae88251ae1fbf1a85b09d0cfbd6208c5878b Author: ianswett Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- RECOMMENDED **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3296b453f67_4e9b2b2072495c106417-- From nobody Tue Jun 26 12:40:49 2018 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 5EB61128CF3 for ; Tue, 26 Jun 2018 12:40:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 H7PTL1sbHZco for ; Tue, 26 Jun 2018 12:40:39 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DEA4130E1F for ; Tue, 26 Jun 2018 12:40:39 -0700 (PDT) Date: Tue, 26 Jun 2018 12:40:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530042038; bh=kxFWSDBIW145EYF7epbUQ/r7VK3rMbXkrCdtQnt83Ko=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cTO63tDmInB+VGO1s151dXG8NL1J49KYO4DyIM+clFokbk7tXHUyfNXQLppphliUm INz1KhhlNJETvG2P9FyP/rx9MNhvHr2oAzUCxGR3UgKYffw5qV+T0kVo89TFYq+Wq+ /kf7rjeWDu+MJybGNz59SrQA3+WrMg5w5EP5kUGM= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3296b6c3283_66483fd82cf7cf8080132"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 19:40:42 -0000 ----==_mimepart_5b3296b6c3283_66483fd82cf7cf8080132 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett pushed 1 commit. ff8aae8 RECOMMENDED -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1480/files/d7fcd1ab6ca99f2354897fea579b194600e2c8eb..ff8aae88251ae1fbf1a85b09d0cfbd6208c5878b ----==_mimepart_5b3296b6c3283_66483fd82cf7cf8080132 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3296b6c3283_66483fd82cf7cf8080132-- From nobody Tue Jun 26 12:40:59 2018 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 4F126130E1F for ; Tue, 26 Jun 2018 12:40:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ZFahYI2Cz5AX for ; Tue, 26 Jun 2018 12:40:47 -0700 (PDT) Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB82C128CF3 for ; Tue, 26 Jun 2018 12:40:47 -0700 (PDT) Date: Tue, 26 Jun 2018 12:40:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530042047; bh=Dklnna1HIOc5pwYSnWLDCdvvXvKHZo/JU+i/u5PmS94=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AYZT2jbzgbc2hFCvM4BqthrAo/3KcAsQnQ71zEwkH3IcU3RApbEW+VdbMiAHeVzTR 3fyxyXlZzAhHpUL+otxs/LdfkLqLYtpR0ulw+tOCFEn6WhuoVzbkNMP6xrrBUVAbht GF0vxLWZMWKX9nrfP2z84vAasl2Db1P28oD/8apo= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3296bf5339e_31f43fef3b9f0f78858e9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 19:40:52 -0000 ----==_mimepart_5b3296bf5339e_31f43fef3b9f0f78858e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > @@ -423,7 +423,7 @@ QUIC SHOULD delay sending acknowledgements in response to packets, but MUST NOT excessively delay acknowledgements of packets containing non-ack frames. Specifically, implementaions MUST attempt to enforce a maximum ack delay to avoid causing the peer spurious -timeouts. The default maximum ack delay in QUIC is 25ms. +timeouts. The RECOMMENDED maximum ack delay in QUIC is 25ms. Done. -- 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/1480#discussion_r198272807 ----==_mimepart_5b3296bf5339e_31f43fef3b9f0f78858e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -423,7 +423,7 @@ QUIC SHOULD delay sending acknowledgements in response to packets,
 but MUST NOT excessively delay acknowledgements of packets containing
 non-ack frames.  Specifically, implementaions MUST attempt to
 enforce a maximum ack delay to avoid causing the peer spurious
-timeouts.  The default maximum ack delay in QUIC is 25ms.
+timeouts.  The RECOMMENDED maximum ack delay in QUIC is 25ms.

Done.

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

----==_mimepart_5b3296bf5339e_31f43fef3b9f0f78858e9-- From nobody Tue Jun 26 12:47:39 2018 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 69B27131133 for ; Tue, 26 Jun 2018 12:47:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 f9XDKlxXCe8E for ; Tue, 26 Jun 2018 12:47:27 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1965A13112B for ; Tue, 26 Jun 2018 12:47:27 -0700 (PDT) Date: Tue, 26 Jun 2018 12:47:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530042446; bh=yEHU88y/LleZETI6h2Wus8OPLMPSCYvmUCe/Amn2Gfw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XrUNj4zggpm54SQiHXb8TWk5C0khnieJ1f1J4r9pjgcuX9og93oGwQaiXf7dyYLhZ oqNULzNRTwObvRyD3EzptUaZeiAO/EkYTVU/3rHUBozRifPHgu0DN4sna7I6s1Y1Yg OZdLrSK5KP5uPB+HRDaPCmYgm9c6AUuX/chxliJ8= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32984e119c8_31cd3fef3b9f0f7810362"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 19:47:38 -0000 ----==_mimepart_5b32984e119c8_31cd3fef3b9f0f7810362 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar approved this pull request. Thanks! -- 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/1480#pullrequestreview-132176821 ----==_mimepart_5b32984e119c8_31cd3fef3b9f0f7810362 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar approved this pull request.

Thanks!

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

----==_mimepart_5b32984e119c8_31cd3fef3b9f0f7810362-- From nobody Tue Jun 26 12:52:05 2018 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 532A3130E2C for ; Tue, 26 Jun 2018 12:52:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 fXGfDidG3ExQ for ; Tue, 26 Jun 2018 12:52:02 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2FC96130DBE for ; Tue, 26 Jun 2018 12:52:02 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530042721; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=HWCtIq6OcYX4hlI44X5IIGi6fTDERt8nj/r9iSSjM+U=; b=xcxV6qUddX0DbwRgs4LOQ6G+/sxYHnwobo2yoCzKIEnKiNdD7CZnha2nnX+iCxaxhUcdczLj rtYwFOEiMt93xfTpDxx+zrKxqsoEslcOD/xkaUB/muSNsgBU+c5ZHd6jhs7+2cSwXb6bRTo9 1U/VKn7lTQYpYEiav8V3qZqpqa0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: ianswett=users.noreply.github.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b329961.7f26ee76d8a0-smtp-out-n01; Tue, 26 Jun 2018 19:52:01 -0000 (UTC) Date: Tue, 26 Jun 2018 12:51:59 -0700 From: ianswett Reply-To: ianswett To: quic-issues@ietf.org Message-ID: <5b32995f8ea97_221c2b03fa82bc1096334@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 61e932: Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32995f8e6b5_221c2b03fa82bc10962aa"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 19:52:04 -0000 ----==_mimepart_5b32995f8e6b5_221c2b03fa82bc10962aa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 61e932dbeac2e70d603010d9596552a5f057b253 https://github.com/quicwg/base-drafts/commit/61e932dbeac2e70d603010d9596552a5f057b253 Author: ianswett Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Replace default with recommended (#1480) * Replace default with recommended Fixes #1475 * RECOMMENDED **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32995f8e6b5_221c2b03fa82bc10962aa-- From nobody Tue Jun 26 12:52:14 2018 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 EDCF2130E2A for ; Tue, 26 Jun 2018 12:52:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 MoQOOcpTUd7I for ; Tue, 26 Jun 2018 12:52:03 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22CD8130E2B for ; Tue, 26 Jun 2018 12:52:03 -0700 (PDT) Date: Tue, 26 Jun 2018 12:52:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530042722; bh=4tir4Lr0DHTx3Hdae/eizr3PSd4zqmUG08sFTnAWCTA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zs+urHl4CWNEd+fwT+KgraH0UoUcqAgDRyVXu34iJdSf+7MPxS2gugaxC91C5rajG 8G12gg8T4xQ38B0QHEQEem/Oorj5rpcT2o22yLfnjMZ3r70JDQrQgrJnPnrkn/OTYI Yw3b88sl0NpAnvxoOl+b3+Jp+pK7a6f1MPNux7rI= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] "Default" max ack delay (#1475) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3299624ec14_43003fac3eeb8f781256d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 19:52:06 -0000 ----==_mimepart_5b3299624ec14_43003fac3eeb8f781256d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1475 via #1480. -- 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/1475#event-1702333489 ----==_mimepart_5b3299624ec14_43003fac3eeb8f781256d5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1475 via #1480.

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

----==_mimepart_5b3299624ec14_43003fac3eeb8f781256d5-- From nobody Tue Jun 26 12:52:20 2018 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 8B867130EF3 for ; Tue, 26 Jun 2018 12:52:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 MGlNoVVNHukB for ; Tue, 26 Jun 2018 12:52:04 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 428C1130DBE for ; Tue, 26 Jun 2018 12:52:04 -0700 (PDT) Date: Tue, 26 Jun 2018 12:52:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530042723; bh=fJrzXrDUOv3PLbPbaZfE8YAQGmVpRdC7Ips6+aE3fsE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=B1Ndj1wrriD+APjfGnHBn/LtBdwMcEUKqfiD6jZEDGk18QkV5JxsNHTs0Xo4LHGn1 nMfgIq6c1SHa7WioTfeSJIkkxNtmnZ5r+b+CJit+YOahU3s1j4jcRJ7npTRb23kE8t oCkkMMRE49CNV3YMTgCE66ZEkOJnOuFNwI3bfkRc= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Replace default with recommended (#1480) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32996398892_48e82aac57fdef5c5026e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 19:52:08 -0000 ----==_mimepart_5b32996398892_48e82aac57fdef5c5026e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1480. -- 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/1480#event-1702333488 ----==_mimepart_5b32996398892_48e82aac57fdef5c5026e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1480.

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

----==_mimepart_5b32996398892_48e82aac57fdef5c5026e-- From nobody Tue Jun 26 13:29:05 2018 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 44D2B130E3A for ; Tue, 26 Jun 2018 13:29:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 dnMvcpgaPs5v for ; Tue, 26 Jun 2018 13:29:02 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7E9C130E2C for ; Tue, 26 Jun 2018 13:29:01 -0700 (PDT) Date: Tue, 26 Jun 2018 13:29:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530044940; bh=7XxNJ4sNlCKOMbSgwT4WpEP+teCSQRFtkLcgQaeX2Ko=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Fa4hjZfdhqnzOknNObf+g33hFuKKPnP2Nun1NugetS8qQq15iGT2p/xm/BRnSjTb/ mk6NGWroJOxru2wq3OmhEavs6EtGE0jL6FbkAKUkXk4PkpeJ7ee1TjGlWQhCcNBesT Oqb2AJV26PS15yr11uOfa+/4CyiLAlXuNh/+hYfs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define the contents of QPACK Encoder and Decoder streams (#1467) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a20ced257_457a3fba7fab4f7c1669f7"; 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.26 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: Tue, 26 Jun 2018 20:29:04 -0000 ----==_mimepart_5b32a20ced257_457a3fba7fab4f7c1669f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. -- 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/1467#pullrequestreview-132191425 ----==_mimepart_5b32a20ced257_457a3fba7fab4f7c1669f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

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

----==_mimepart_5b32a20ced257_457a3fba7fab4f7c1669f7-- From nobody Tue Jun 26 13:31:46 2018 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 79CAB130E3A for ; Tue, 26 Jun 2018 13:31:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 M76UewJYWzd6 for ; Tue, 26 Jun 2018 13:31:42 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDE1A130E2C for ; Tue, 26 Jun 2018 13:31:41 -0700 (PDT) Date: Tue, 26 Jun 2018 13:31:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530045100; bh=LcdYri+i4X9oPIHN8bPBeys+PqD0mx+qtaUxiEGMR9o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lbwn4aRxSRw2nggpGca5S+FV+bsWhSZwz3D4KT/RpE8EREGGEy1hW/M903eP6dtaY AW0cwwIQk3LHAI9JEy39CPA5jFbEI5Pq7cwsYpZc71AlYy80XOQQKAMdujor2PXHLt so3uc+Dtb2z+qctEzOpCwAhcN9BvqL2tFgFqcRlA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Modify codepoints on decoder and request/push streams for consistency (#1472) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a2acdbcb0_34863fc50f4bcf80113857"; 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.26 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: Tue, 26 Jun 2018 20:31:44 -0000 ----==_mimepart_5b32a2acdbcb0_34863fc50f4bcf80113857 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson, that's perhaps technically true, but I don't think this pushes out interop noticeably. The bit sequences are the same length they previously were, and were always arbitrary bit sequences. This should be a trivial change to incorporate. -- 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/1472#issuecomment-400451844 ----==_mimepart_5b32a2acdbcb0_34863fc50f4bcf80113857 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson, that's perhaps technically true, but I don't think this pushes out interop noticeably. The bit sequences are the same length they previously were, and were always arbitrary bit sequences. This should be a trivial change to incorporate.

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

----==_mimepart_5b32a2acdbcb0_34863fc50f4bcf80113857-- From nobody Tue Jun 26 13:35:14 2018 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 27BEB130E3A for ; Tue, 26 Jun 2018 13:35:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 lF7xqIxJHquJ for ; Tue, 26 Jun 2018 13:35:10 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 27A5E130E2C for ; Tue, 26 Jun 2018 13:35:10 -0700 (PDT) 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=hs3JHDHSdTOIAEeh8K5GZOuCm0E=; b=EHxDUjJmCGJ/3BZV aSuPbdQvbFmafEPW40H8mh44lDTNpo1R9xHCnQDXN+AnDVUfwdAuxgjVwYsFXGgu 1CxptkxzbYXnYNtC9Ma2ACnNhdeRSB85BzfOpfaAhBlj9Yg9BY79xsaJkek2DK5x 2XIWnh6mXPua7Y6vUa1zMxOguvk= Received: by filter0440p1iad2.sendgrid.net with SMTP id filter0440p1iad2-10529-5B32A37B-8 2018-06-26 20:35:07.128663356 +0000 UTC Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id 7Ut6bsEOR3e0m0dsp1DJ5Q for ; Tue, 26 Jun 2018 20:35:07.062 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id 0CC1EAE02E7 for ; Tue, 26 Jun 2018 13:35:07 -0700 (PDT) Date: Tue, 26 Jun 2018 20:35:07 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a37ba7db_f2e2b0faaffef58786a1"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak33/qMTsDoUgSw9Mcjs7Z4qwD6DjWP2XB+KxK cQn65B/0YF7mtaFtPvx624LEMScSrRd1sFdyyPBaTz/Xt83f2vD3cueuGyib5vMIWacsbptbQci1b9 y5Eqa6n6/kxdNNGes62Ry0Ytqze+MMwUKt1S7daMzkNaLwRfYAZc6a1PyZrBrTV3CJdWH6+Coy5h1H 8= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 20:35:13 -0000 ----==_mimepart_5b32a37ba7db_f2e2b0faaffef58786a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. + +## Extension Frames + +QUIC frames do not use a self-describing encoding. An endpoint therefore needs +to understand the syntax of all frame before it can successfully process a +packet. This allows for efficient encoding of frames, but it means that an +endpoint cannot send a frame of a type that is unknown to its peer. + +An extension to QUIC that wishes to use a new type of frame MUST first ensure +that a peer is able to understand the frame. An endpoint can use a transport There's always @larseggert's suggestion that BLOCKED et al. should be extensions. That's been on hold while we wait for an extension mechanism to be defined, but it's a perfectly reasonable one. Define a transport parameter `inform_if_blocked` and if that's set, the various BLOCKED frames are understood. -- 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/1473#discussion_r198288379 ----==_mimepart_5b32a37ba7db_f2e2b0faaffef58786a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> +implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.
+
+## Extension Frames
+
+QUIC frames do not use a self-describing encoding.  An endpoint therefore needs
+to understand the syntax of all frame before it can successfully process a
+packet.  This allows for efficient encoding of frames, but it means that an
+endpoint cannot send a frame of a type that is unknown to its peer.
+
+An extension to QUIC that wishes to use a new type of frame MUST first ensure
+that a peer is able to understand the frame.  An endpoint can use a transport

There's always @larseggert's suggestion that BLOCKED et al. should be extensions. That's been on hold while we wait for an extension mechanism to be defined, but it's a perfectly reasonable one. Define a transport parameter inform_if_blocked and if that's set, the various BLOCKED frames are understood.

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

----==_mimepart_5b32a37ba7db_f2e2b0faaffef58786a1-- From nobody Tue Jun 26 13:38:37 2018 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 94772130EDE for ; Tue, 26 Jun 2018 13:38:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 xwgte_kCug66 for ; Tue, 26 Jun 2018 13:38:32 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 93D27130ECF for ; Tue, 26 Jun 2018 13:38:31 -0700 (PDT) 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=1yeA3KuZ3E7NLPBYdZN5nY2NXpE=; b=DMViJ42QaU8llh7N ywUrVCbRxfIydi4ZXUyrCkkJyfd9qqA1L3TH5IRN2gXMibsiRv6uIUlsLadsw9jy zRdsqACXbFHtFeS/N4QzzCHjLuLs207Jsd6cU8qRatea+/zd1BqQVqBK4bbWqP7w Z3PfPG7SlFmbqGJtzugmOER4k/Q= Received: by filter0280p1iad2.sendgrid.net with SMTP id filter0280p1iad2-27625-5B32A446-9 2018-06-26 20:38:30.238899023 +0000 UTC Received: from github-lowworker-5909e27.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id Q6zcIwXKR9KNhhukrLULiQ for ; Tue, 26 Jun 2018 20:38:30.185 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-5909e27.cp1-iad.github.net (Postfix) with ESMTP id 2AE2E3E13B4 for ; Tue, 26 Jun 2018 13:38:30 -0700 (PDT) Date: Tue, 26 Jun 2018 20:38:30 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a446292cc_22e2b1db6d3cf581865c0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1iG7RWcE3h02vIkiSk1Tx59JXHcjT1KLk5WP X8LjoSshmmoCT0htLMshZH7NE76u46enyLT31jxWJiez/TejaZKqlgfixAfBm+X7wQeizXkRXTvDEx z9thfHkiL3DugAZ9rDLaPGzE0ixuEY7X333SL4QUcMLF/KolxoThgtCFpw== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 20:38:35 -0000 ----==_mimepart_5b32a446292cc_22e2b1db6d3cf581865c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > +implementations of frame parsing, a frame type MUST use the shortest possible +encoding. Though a two-, four- or eight-octet encoding of the frame types +defined in this document is possible, the Frame Type field for these frames are +encoded on a single octet. For instance, though 0x4007 is a legitimate +two-octet encoding for a variable-length integer with a value of 7, PING frames +are always encoded as a single octet with the value 0x07. + +## Extension Frames + +QUIC frames do not use a self-describing encoding. An endpoint therefore needs +to understand the syntax of all frame before it can successfully process a +packet. This allows for efficient encoding of frames, but it means that an +endpoint cannot send a frame of a type that is unknown to its peer. + +An extension to QUIC that wishes to use a new type of frame MUST first ensure +that a peer is able to understand the frame. An endpoint can use a transport That sounds like a reasonable suggestion to me. -- 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/1473#discussion_r198289383 ----==_mimepart_5b32a446292cc_22e2b1db6d3cf581865c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> +implementations of frame parsing, a frame type MUST use the shortest possible
+encoding.  Though a two-, four- or eight-octet encoding of the frame types
+defined in this document is possible, the Frame Type field for these frames are
+encoded on a single octet.  For instance, though 0x4007 is a legitimate
+two-octet encoding for a variable-length integer with a value of 7, PING frames
+are always encoded as a single octet with the value 0x07.
+
+## Extension Frames
+
+QUIC frames do not use a self-describing encoding.  An endpoint therefore needs
+to understand the syntax of all frame before it can successfully process a
+packet.  This allows for efficient encoding of frames, but it means that an
+endpoint cannot send a frame of a type that is unknown to its peer.
+
+An extension to QUIC that wishes to use a new type of frame MUST first ensure
+that a peer is able to understand the frame.  An endpoint can use a transport

That sounds like a reasonable suggestion to me.

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

----==_mimepart_5b32a446292cc_22e2b1db6d3cf581865c0-- From nobody Tue Jun 26 13:44:51 2018 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 BA91B130ED2 for ; Tue, 26 Jun 2018 13:44:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 VQLkh1PULl5g for ; Tue, 26 Jun 2018 13:44:47 -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 CBF50130ECB for ; Tue, 26 Jun 2018 13:44:46 -0700 (PDT) Date: Tue, 26 Jun 2018 13:44:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530045886; bh=5UU8cEI7m/XHqtF0dzqZP4lZ+4F2/gp2I3yLBbwYPwo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VSmkmD8qFK4HmQrFuMCoPPJf8pva5pH53qahLsj7O++GRU5pf78WoannkufnFwTZr dXY6WhGSOndCVu9JHIFAzrAQz3se1CcUN2Vb/53JK8I4riUuOECUCdmZu3iH1LH8U7 4KOad7zqltkPMjmpQVFPz0iQGTAEWo/Nk9uBWCcM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a5be2c6d5_4a392ad01e36ef5c306816"; 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.26 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: Tue, 26 Jun 2018 20:44:49 -0000 ----==_mimepart_5b32a5be2c6d5_4a392ad01e36ef5c306816 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. +1 to Jana's suggestion to merge this quickly. A reflow without any text changes, I would probably just have committed directly to master. It will break any open PRs that aren't already bitrotten, so do it quickly before there are any. > @@ -255,11 +252,11 @@ than 1.25 * max(SRTT, latest_RTT) since when it was sent. Using max(SRTT, latest_RTT) protects from the two following cases: * the latest RTT sample is lower than the SRTT, perhaps due to reordering where -packet whose ack triggered the Early Retransit process encountered a shorter -path; + packet whose ack triggered the Early Retransit process encountered a shorter **the** packet > ### Crypto Handshake Timeout -Data in CRYPTO_HS frames is critical to QUIC transport and crypto negotiation, -so a more aggressive timeout is used to retransmit it. Below, the word -handshake packet is used to refer to packets containing CRYPTO_HS frames, -not packets with the specific long header packet type Handshake. +Data in CRYPTO frames is critical to QUIC transport and crypto negotiation, so a +more aggressive timeout is used to retransmit it. Below, the word handshake +packet is used to refer to packets containing CRYPTO frames, not packets with (Unmodified text, but you touch it, you own it.) "handshake packet" isn't actually *a* word. Perhaps "the term," and put "handshake packet" in quotes to designate it as the term you're discussing for clarity? -- 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/1476#pullrequestreview-132194801 ----==_mimepart_5b32a5be2c6d5_4a392ad01e36ef5c306816 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

+1 to Jana's suggestion to merge this quickly. A reflow without any text changes, I would probably just have committed directly to master.

It will break any open PRs that aren't already bitrotten, so do it quickly before there are any.

In draft-ietf-quic-recovery.md:

> @@ -255,11 +252,11 @@ than 1.25 * max(SRTT, latest_RTT) since when it was sent.
 Using max(SRTT, latest_RTT) protects from the two following cases:
 
 * the latest RTT sample is lower than the SRTT, perhaps due to reordering where
-packet whose ack triggered the Early Retransit process encountered a shorter
-path;
+  packet whose ack triggered the Early Retransit process encountered a shorter

the packet

In draft-ietf-quic-recovery.md:

>  
 ### Crypto Handshake Timeout
 
-Data in CRYPTO_HS frames is critical to QUIC transport and crypto negotiation,
-so a more aggressive timeout is used to retransmit it.  Below, the word
-handshake packet is used to refer to packets containing CRYPTO_HS frames,
-not packets with the specific long header packet type Handshake.
+Data in CRYPTO frames is critical to QUIC transport and crypto negotiation, so a
+more aggressive timeout is used to retransmit it.  Below, the word handshake
+packet is used to refer to packets containing CRYPTO frames, not packets with

(Unmodified text, but you touch it, you own it.) "handshake packet" isn't actually a word. Perhaps "the term," and put "handshake packet" in quotes to designate it as the term you're discussing for clarity?

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

----==_mimepart_5b32a5be2c6d5_4a392ad01e36ef5c306816-- From nobody Tue Jun 26 13:53:23 2018 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 E168C130ED2 for ; Tue, 26 Jun 2018 13:53:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sBU3rljcC62V for ; Tue, 26 Jun 2018 13:53:19 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D13DC130E5D for ; Tue, 26 Jun 2018 13:53:18 -0700 (PDT) Date: Tue, 26 Jun 2018 13:53:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530046398; bh=5B0/HnZSLSbZMEc33eskZkNwb5IP4BSwwVPHG1ZziMw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SUYiRvQQNrsHP32ViL9XoaPP7F4lSBRvBd7suPE4R3pOrIh4vNjJcBi2+J03eWyYL tw/Hru1Ds6zsYOH5KOussVTXorB/I0cLAV9GWd6cYhcxb06xF+bKyZgHl1MG0IKhG8 9FXhsXnLGGwBpjdAsxYLFUTWUsvJz6AeDXFlnrQI= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a7be341d4_7e393fdf2e618f8079342"; 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.26 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: Tue, 26 Jun 2018 20:53:21 -0000 ----==_mimepart_5b32a7be341d4_7e393fdf2e618f8079342 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. Yes please. > @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares. ## TLS Errors -If TLS experiences an error, it MUST generate an appropriate alert -as defined in {{TLS13}}; Section 6) and then provide it to QUIC, -which sends the alert in a CRYPTO_CLOSE frame. All such alerts are -"fatal" (see {{TLS13}}, Section 6.2. +If TLS experiences an error, it generates an appropriate alert as defined in +Section 6 of {{TLS13}}. + +A TLS alert is turned into a QUIC connection error by converting the one-octet +alert description into a QUIC error code. The alert description is added to +0x200 to produce a QUIC error code from the range reserved for CRYPTO_ERROR. +The resulting value is sent in a QUIC CONNECTION_CLOSE frame. + +The alert level of all TLS alerts is "fatal", a TLS stack MUST NOT generate Comma splice. Separate sentences or `;`. > @@ -1032,7 +1032,6 @@ explained in more detail as they are referenced later in the document. | 0x0f | PATH_RESPONSE | {{frame-path-response}} | | 0x10 - 0x17 | STREAM | {{frame-stream}} | | 0x18 | CRYPTO_HS | {{frame-crypto}} | -| 0x19 | CRYPTO_CLOSE | {{frame-crypto-close}} | | 0x20 | NEW_TOKEN | {{frame-new-token}} | No objection, but also seems unnecessary. Leave 0x19 for the next frame to be defined, and if there are gaps in the space we'll defrag before we ship. > @@ -2200,10 +2199,9 @@ before the packet is received. ### Immediate Close -An endpoint sends a closing frame, (CONNECTION_CLOSE, CRYPTO_CLOSE or -APPLICATION_CLOSE) to terminate the connection immediately. Any -closing frame causes all streams to immediately become closed; open -streams can be assumed to be implicitly reset. +An endpoint sends a closing frame, (CONNECTION_CLOSE or APPLICATION_CLOSE) to Unnecessary comma -- 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/1477#pullrequestreview-132199013 ----==_mimepart_5b32a7be341d4_7e393fdf2e618f8079342 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

Yes please.

In draft-ietf-quic-tls.md:

> @@ -602,10 +602,16 @@ HelloRetryRequest is still used for incorrect key shares.
 
 ## TLS Errors
 
-If TLS experiences an error, it MUST generate an appropriate alert
-as defined in {{TLS13}}; Section 6) and then provide it to QUIC,
-which sends the alert in a CRYPTO_CLOSE frame. All such alerts are
-"fatal" (see {{TLS13}}, Section 6.2.
+If TLS experiences an error, it generates an appropriate alert as defined in
+Section 6 of {{TLS13}}.
+
+A TLS alert is turned into a QUIC connection error by converting the one-octet
+alert description into a QUIC error code.  The alert description is added to
+0x200 to produce a QUIC error code from the range reserved for CRYPTO_ERROR.
+The resulting value is sent in a QUIC CONNECTION_CLOSE frame.
+
+The alert level of all TLS alerts is "fatal", a TLS stack MUST NOT generate

Comma splice. Separate sentences or ;.

In draft-ietf-quic-transport.md:

> @@ -1032,7 +1032,6 @@ explained in more detail as they are referenced later in the document.
 | 0x0f        | PATH_RESPONSE     | {{frame-path-response}}     |
 | 0x10 - 0x17 | STREAM            | {{frame-stream}}            |
 | 0x18        | CRYPTO_HS         | {{frame-crypto}}            |
-| 0x19        | CRYPTO_CLOSE      | {{frame-crypto-close}}      |
 | 0x20        | NEW_TOKEN         | {{frame-new-token}}         |

No objection, but also seems unnecessary. Leave 0x19 for the next frame to be defined, and if there are gaps in the space we'll defrag before we ship.

In draft-ietf-quic-transport.md:

> @@ -2200,10 +2199,9 @@ before the packet is received.
 
 ### Immediate Close
 
-An endpoint sends a closing frame, (CONNECTION_CLOSE, CRYPTO_CLOSE or
-APPLICATION_CLOSE) to terminate the connection immediately.  Any
-closing frame causes all streams to immediately become closed; open
-streams can be assumed to be implicitly reset.
+An endpoint sends a closing frame, (CONNECTION_CLOSE or APPLICATION_CLOSE) to

Unnecessary comma

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

----==_mimepart_5b32a7be341d4_7e393fdf2e618f8079342-- From nobody Tue Jun 26 14:01:18 2018 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 49F19130E41 for ; Tue, 26 Jun 2018 14:01:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 B682m9rRjlmH for ; Tue, 26 Jun 2018 14:01:11 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB40130EF3 for ; Tue, 26 Jun 2018 14:01:11 -0700 (PDT) Date: Tue, 26 Jun 2018 14:01:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530046870; bh=nwgayb/WwByFrGqZUsWQSEm1kATazsZuauXv80dgMos=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=RnR86vIsUBYpMMrwvvLOaSAJOyGMxDVYtlIIIxy3E3ecxvA8Zrtimn+Mcabp1NH4h mciEpK1fBb0w6zAasyIArkc59tKkbzTnVUsMk2szO6ACXQKGpA0YWy8OEiQulEA9h9 O3RNYb9kZSsRORSRHXrvOGqoDomOmt4OOU/Xch+M= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Fragility in ECN counters with lost acks (#1481) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32a9965d911_1a892ab18565af5c167442"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 21:01:16 -0000 ----==_mimepart_5b32a9965d911_1a892ab18565af5c167442 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The proposed text for ECN (in https://github.com/gloinul/base-drafts/pull/3) says: "The increase in ECT(0) and ECT(1) counters MUST be no greater than the number of packets newly acknowledged that were sent with the corresponding codepoint." As @gloinul observed in his PR and @martinthomson noted in his review, this can cause ECN to be disabled when acks are lost. A sender may never receive an ack for a packet that was in fact acknowledged, and might see an increase in ECN counters without a corresponding packet being newly acked. This should be addressed. @martinthomson writes: "Say a marked packet gets through and gets acknowledged, but the acknowledgment is lost. And the recipient abandons the ACK. The counters will increase, but the number of newly acknowledged packets will be lower than the increase to the counters. That suggests a tweak, though it complicates things a little: If the acknowledgments cover a range of packet numbers that extend past (or adjacent to) the largest acknowledged packet number that was previously acknowledged, then the counters must match precisely. If the acknowledgments do not extend to the largest previously acknowledged packet number, then the numbers MAY increase by the number of unacknowledged packets between the previously largest acknowledged and the newly lowest acknowledged. That is, if an endpoint has seen an ACK_ECN for packet 10, then receives a new ACK_ECN for packet 20-30, it needs to allow for an increase in the counters for packets 11 through 19 (inclusive). It can then reset both the largest acknowledged and the values it tracks for each counter." -- 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/1481 ----==_mimepart_5b32a9965d911_1a892ab18565af5c167442 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The proposed text for ECN (in gloinul#3) says: "The increase in ECT(0) and ECT(1) counters MUST be no greater than the number of packets newly acknowledged that were sent with the corresponding codepoint."

As @gloinul observed in his PR and @martinthomson noted in his review, this can cause ECN to be disabled when acks are lost. A sender may never receive an ack for a packet that was in fact acknowledged, and might see an increase in ECN counters without a corresponding packet being newly acked. This should be addressed.

@martinthomson writes: "Say a marked packet gets through and gets acknowledged, but the acknowledgment is lost. And the recipient abandons the ACK. The counters will increase, but the number of newly acknowledged packets will be lower than the increase to the counters. That suggests a tweak, though it complicates things a little:

If the acknowledgments cover a range of packet numbers that extend past (or adjacent to) the largest acknowledged packet number that was previously acknowledged, then the counters must match precisely. If the acknowledgments do not extend to the largest previously acknowledged packet number, then the numbers MAY increase by the number of unacknowledged packets between the previously largest acknowledged and the newly lowest acknowledged.

That is, if an endpoint has seen an ACK_ECN for packet 10, then receives a new ACK_ECN for packet 20-30, it needs to allow for an increase in the counters for packets 11 through 19 (inclusive). It can then reset both the largest acknowledged and the values it tracks for each counter."

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

----==_mimepart_5b32a9965d911_1a892ab18565af5c167442-- From nobody Tue Jun 26 15:06:36 2018 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 00A6F131134 for ; Tue, 26 Jun 2018 15:06:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 akqgRvQGWL0c for ; Tue, 26 Jun 2018 15:06:33 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 9B2D0130EE9 for ; Tue, 26 Jun 2018 15:06:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530050792; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=dmrF34nGOmFqAUAkr9Wm8n/1XLVn1blwbfDX6JS5DYs=; b=q9NArKolDIYvDtOdr59bByFAGK4hiex2xjs5mvg+Qic7jjZj685HpVtn7sKtBpIQopCcEmLY y6WHufIIvoa5s6rnZj2aN7W4BnVuW9TwAZdNCD6Nejk3NurLs5AKB8ep7RiAwyx8m/KrNjrA bIe2jJXZo/LzRCzxkSxd0kkSQEM= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32b8e8.7fdff54792a0-smtp-out-n01; Tue, 26 Jun 2018 22:06:32 -0000 (UTC) Date: Tue, 26 Jun 2018 15:06:31 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b32b8e755321_55c12af38f853c04219b5@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e2ec18: Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32b8e754c67_55c12af38f853c042184"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:06:36 -0000 ----==_mimepart_5b32b8e754c67_55c12af38f853c042184 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: e2ec1807626a1b62e8494e82971083f3248dcc2c https://github.com/quicwg/base-drafts/commit/e2ec1807626a1b62e8494e82971083f3248dcc2c Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Grease values in HTTP/QUIC (#1446) * Import grease recommendations * HTTP/QUIC doesn't give settings initial values * Martin's feedback * Grease section header **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32b8e754c67_55c12af38f853c042184-- From nobody Tue Jun 26 15:06:44 2018 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 39BA4131134 for ; Tue, 26 Jun 2018 15:06:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 YFqGs-ZRnDS2 for ; Tue, 26 Jun 2018 15:06:35 -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 6C365130EE9 for ; Tue, 26 Jun 2018 15:06:35 -0700 (PDT) Date: Tue, 26 Jun 2018 15:06:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530050793; bh=DWbeDK4FtccAf13cjXrS2nS/OOrAC0felsWBB2xDPA8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Mu1iGGb3JK5THyRmACV15gzf9MED9eUyDANf1hF13RbEjjYi96K+h1WIYORz/3OtW ahlFOhpNW5x8GPykri6BrlQ/WbR+guWrEG0aOCs0Am1ftMZQWzf7M/AzI9zOqhoOOh XGQvIlYUJSawRmyN67JFL/YBEEGJ0KxLpDoBDO4Q= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Grease values in HTTP/QUIC (#1446) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32b8e98dd6c_58063fe6b9a72f80101698"; 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.26 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: Tue, 26 Jun 2018 22:06:38 -0000 ----==_mimepart_5b32b8e98dd6c_58063fe6b9a72f80101698 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1446. -- 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/1446#event-1702584174 ----==_mimepart_5b32b8e98dd6c_58063fe6b9a72f80101698 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1446.

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

----==_mimepart_5b32b8e98dd6c_58063fe6b9a72f80101698-- From nobody Tue Jun 26 15:06:50 2018 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 87EC3131146 for ; Tue, 26 Jun 2018 15:06:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 4mAAl2qGqGb8 for ; Tue, 26 Jun 2018 15:06:37 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70D8613113A for ; Tue, 26 Jun 2018 15:06:35 -0700 (PDT) Date: Tue, 26 Jun 2018 15:06:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530050793; bh=URJ9c+ZQa6KJBTnemEcAP+8lcyN6XHnCYsGK47Rr/+k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hGGrJrjWc4MVNawvA4G1QCBBcaqp/RRxCcEVhnURz6KM/0EZ6VXao2PqxjF/2ijze HUqoh2Yj1i8HSLV+G/PBNWHTXMX0AJmtbSLbTkChRyKb8OL9Bgo7SGfL65djYl2CaY oK2yhmUpd8E6uERUkvXj8yKuljdRrAmAm1t+/Dvg= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] hq: extensibility greasing (#1333) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32b8e98c2e4_601f3fbb99b92f781141a2"; 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.26 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: Tue, 26 Jun 2018 22:06:40 -0000 ----==_mimepart_5b32b8e98c2e4_601f3fbb99b92f781141a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1333 via #1446. -- 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/1333#event-1702584175 ----==_mimepart_5b32b8e98c2e4_601f3fbb99b92f781141a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1333 via #1446.

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

----==_mimepart_5b32b8e98c2e4_601f3fbb99b92f781141a2-- From nobody Tue Jun 26 15:12:27 2018 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 CB460130EE9 for ; Tue, 26 Jun 2018 15:12:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 W52vDtqtf4ZC for ; Tue, 26 Jun 2018 15:12:24 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 B9C73130DF1 for ; Tue, 26 Jun 2018 15:12:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051144; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rhpWhqLPOdXABcwFJ60Eze5EO9asIgHqRGgQBGZp1ew=; b=B2L5qzQxwpXNZ1P1G5yuoAVV8Z2NYOStRjz85PLo7dtomr3XFefXNn7NEcapXtKaYRrcccjU Ql+WHdL8IYk6esfdHfNELUzvr1kMa+n7OqbXkQ33R044N4YFU/6WkIybZLZ+dHO53LzCbNx2 i6DTl+3Qg7QSOwnqHBbr5VTWGZc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32ba47.7f349f7653f0-smtp-out-n01; Tue, 26 Jun 2018 22:12:23 -0000 (UTC) Date: Tue, 26 Jun 2018 15:12:23 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32ba4744575_3c2b2ad4cde61c085554b@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e1aa62: Revert "Remove sequence number from NEW_CONNECTION... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32ba4743e98_3c2b2ad4cde61c08554dc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:12:26 -0000 ----==_mimepart_5b32ba4743e98_3c2b2ad4cde61c08554dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: e1aa62531825699ae815534096dda6d99a9bf9ae https://github.com/quicwg/base-drafts/commit/e1aa62531825699ae815534096dda6d99a9bf9ae Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Revert "Remove sequence number from NEW_CONNECTION_ID" This reverts commit 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6. Commit: 7d7850061e3d7fe01b1b31551f1689cce5f2464a https://github.com/quicwg/base-drafts/commit/7d7850061e3d7fe01b1b31551f1689cce5f2464a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Require CID sequence number ratcheting Commit: fdc9651e19cdd1ed794f66a44c01f800651d3a1a https://github.com/quicwg/base-drafts/commit/fdc9651e19cdd1ed794f66a44c01f800651d3a1a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Prefer equality Commit: 26a3a1f06d21b858814b5f71f8c96d457edce61f https://github.com/quicwg/base-drafts/commit/26a3a1f06d21b858814b5f71f8c96d457edce61f Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Nick's reword Commit: c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 https://github.com/quicwg/base-drafts/commit/c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- New CID section Commit: 32c8bc1477966608fd5e7015317cd2887e8553ab https://github.com/quicwg/base-drafts/commit/32c8bc1477966608fd5e7015317cd2887e8553ab Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Additional recommendations Commit: e08e13e564939c3ed9621a695dcd3b2ddd4b3bb1 https://github.com/quicwg/base-drafts/commit/e08e13e564939c3ed9621a695dcd3b2ddd4b3bb1 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1465 from quicwg/transport/ratchet_precision Restore CID sequence numbers Compare: https://github.com/quicwg/base-drafts/compare/e2ec1807626a...e08e13e56493 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32ba4743e98_3c2b2ad4cde61c08554dc-- From nobody Tue Jun 26 15:12:32 2018 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 86F50131147 for ; Tue, 26 Jun 2018 15:12:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Si9onQHsX5lx for ; Tue, 26 Jun 2018 15:12:27 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 288F7130DF1 for ; Tue, 26 Jun 2018 15:12:27 -0700 (PDT) Date: Tue, 26 Jun 2018 15:12:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051146; bh=2G4Sylzrmuy2pv183RRu+u1waB1w2Vb8JnCnRFZpZt4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=auxWNo5iSOKV2Xy8338IudN9Eti0OGI0kj3WigSjyeNML2bUCjSAw/zxU4NwFVDc0 apJhRLJ1G9KrchHhIsb8bepR96o/E7oIP+z0mpDFew3ub5Z+IdHfzJzk66kW1a4wQN Se7t/mt7kfTy9KiDfb+BA4PvlclT6zIX+C/hdRxA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ba4a756ac_6f022adce69daf60534c6"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:12:30 -0000 ----==_mimepart_5b32ba4a756ac_6f022adce69daf60534c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1465. -- 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/1465#event-1702592712 ----==_mimepart_5b32ba4a756ac_6f022adce69daf60534c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1465.

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

----==_mimepart_5b32ba4a756ac_6f022adce69daf60534c6-- From nobody Tue Jun 26 15:12:39 2018 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 82336131149 for ; Tue, 26 Jun 2018 15:12:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hFqtc8hzKn3Z for ; Tue, 26 Jun 2018 15:12:27 -0700 (PDT) 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 C5A6813113F for ; Tue, 26 Jun 2018 15:12:27 -0700 (PDT) Date: Tue, 26 Jun 2018 15:12:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051147; bh=BcbvJ2IqjDWgZ1vh8aW9HHDS0BgaCeEYSbU6lPac4/g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NYquLy8VLHlVQM/7UJFVF8dWpaNqOiCCU4OVyFB88GQ0fV/nJE6btDSwosqFHVdzX lQtt05fBXjE7LLb1cdCNxtYsBYlfT5vtzDZypSZRTSv7Grpt8BfWOETk0D76huXm7J pkCSINZgqNBdY0sV/xzvqa9tpHAkZmdfmYBclGo0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID ratcheting language is imprecise (#1452) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ba4b27bfa_3e6a2acb74668f54103d9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:12:30 -0000 ----==_mimepart_5b32ba4b27bfa_3e6a2acb74668f54103d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1452 via #1465. -- 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/1452#event-1702592718 ----==_mimepart_5b32ba4b27bfa_3e6a2acb74668f54103d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1452 via #1465.

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

----==_mimepart_5b32ba4b27bfa_3e6a2acb74668f54103d9-- From nobody Tue Jun 26 15:12:48 2018 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 B4E4A130EE9 for ; Tue, 26 Jun 2018 15:12:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 orlS0w3ZNd13 for ; Tue, 26 Jun 2018 15:12:39 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 81DD113113E for ; Tue, 26 Jun 2018 15:12:39 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051159; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=q9TIO/W//JiKqv7eCl1+3yoz8JGDcob8Zl04jjrdDMA=; b=gkAKEvQ+FkAEK1/Fi05j0mOAybYV3NSuZnyHAIGLeKN5AKlxEKbtrLlCC5Vz+2yTqCfoxRVe HG+XYOkf6AYQNM3zWJvrNmAJ7FDN7l5oJXDD10b84Hnz/pTfiIYsSwn5xbIHORtA0c4wqEdF YhZgITe/RGi6tmv6QZV3/C7UYjo= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: afrind=users.noreply.github.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b32ba56.7f584620a930-smtp-out-n03; Tue, 26 Jun 2018 22:12:38 -0000 (UTC) Date: Tue, 26 Jun 2018 15:12:38 -0700 From: afrind Reply-To: afrind To: quic-issues@ietf.org Message-ID: <5b32ba56676ab_19012b13034fdc105363f@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ac5aad: Define the contents of QPACK Encoder and Decoder s... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32ba5666e5b_19012b13034fdc1053514"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:12:41 -0000 ----==_mimepart_5b32ba5666e5b_19012b13034fdc1053514 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: ac5aadba7f3e85375229e11867af504dfc868807 https://github.com/quicwg/base-drafts/commit/ac5aadba7f3e85375229e11867af504dfc868807 Author: afrind Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Define the contents of QPACK Encoder and Decoder streams (#1467) Fixes #1361 This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32ba5666e5b_19012b13034fdc1053514-- From nobody Tue Jun 26 15:12:53 2018 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 947E8130EE9 for ; Tue, 26 Jun 2018 15:12:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AnkHAG0vju5u for ; Tue, 26 Jun 2018 15:12:41 -0700 (PDT) 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 170B9131138 for ; Tue, 26 Jun 2018 15:12:41 -0700 (PDT) Date: Tue, 26 Jun 2018 15:12:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051160; bh=w1ki0ja1wU1ZQ7NFNL1Bj7JdUoH3QShPszHN5r5d0x0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pT/sgNka/AkRAj1oyofGx9sFtRDmMkicCUf6M9CCFUzgI15JnMiKTZ/Z4PAPEOteu fvS1J8f9tuWs90x3lITulpuAvDwKSZu5PUXkKHzJbLsew3ouuu4ZBOwKYAuFhszHNN YTKuZYCaoeKeghEkoN45fD34Y9eM26dHf95ieUq8= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define the contents of QPACK Encoder and Decoder streams (#1361) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ba58669fd_23c953fe94f398f7890516"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Tue, 26 Jun 2018 22:12:44 -0000 ----==_mimepart_5b32ba58669fd_23c953fe94f398f7890516 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1361 via #1467. -- 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/1361#event-1702593088 ----==_mimepart_5b32ba58669fd_23c953fe94f398f7890516 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1361 via #1467.

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

----==_mimepart_5b32ba58669fd_23c953fe94f398f7890516-- From nobody Tue Jun 26 15:12:58 2018 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 68494131138 for ; Tue, 26 Jun 2018 15:12:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 5aZx_qTuJ1Bf for ; Tue, 26 Jun 2018 15:12:41 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D33513113E for ; Tue, 26 Jun 2018 15:12:41 -0700 (PDT) Date: Tue, 26 Jun 2018 15:12:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051160; bh=CTHi2PAgFAPvnai0qgxUpx6GD6uaWO4GcBfDIqBeAdo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CpDsJxpzNUWEEnzAnHnzw/oZB5jAAWoh+N25rRFkwB4hHY00DZywWrrrUmRKgaRa3 YxyfHltnERg8pT1YU36ugQipGc3rpPJAK8hArMR9RjblgNz33WuYG4z45Dmv+3Z2bg 6w2cI9Ahw8aI4L9H4P5GGqvxD05L9DmWhvSZliDA= From: afrind Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define the contents of QPACK Encoder and Decoder streams (#1467) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ba5891aa2_19c773f83bd20ef881084"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: afrind 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.26 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: Tue, 26 Jun 2018 22:12:45 -0000 ----==_mimepart_5b32ba5891aa2_19c773f83bd20ef881084 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1467. -- 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/1467#event-1702593086 ----==_mimepart_5b32ba5891aa2_19c773f83bd20ef881084 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1467.

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

----==_mimepart_5b32ba5891aa2_19c773f83bd20ef881084-- From nobody Tue Jun 26 15:13:50 2018 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 CE08C130DF1 for ; Tue, 26 Jun 2018 15:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 tgpq0uwQW4zn for ; Tue, 26 Jun 2018 15:13:47 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A66B130E15 for ; Tue, 26 Jun 2018 15:13:47 -0700 (PDT) Date: Tue, 26 Jun 2018 15:13:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051226; bh=JNcjzlOBPBRwCm8kr0IqZNWdNkbWNB0ILh1xc7C7uGE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uY3eNaGZPbJHHlVwZCxDrmdj52mK5mT5yiMuHAyoW6DGZy2+PWoIddxHzFsRtkzaR fy7E5XeXrhAhzBdivEFDecPWC6Ucg19wHBcDYo49caOhAnXK9d5ZR/qk+gOHUAGCsy ZyQpU3vTvUTKYLKXJ+o5Kn8EwszWY/JFn/cidQWc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ba9a1a8e9_25453ff412ac8f78802c8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:13:49 -0000 ----==_mimepart_5b32ba9a1a8e9_25453ff412ac8f78802c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows: The fields are: +Sequence: + +: A variable-length integer. This value starts at 0 and increases by 1 for each + connection ID that is provided by the server. The connection ID that is + assigned during the handshake is assumed to have a sequence of -1. That is, I've merged this, so let's open an issue to close this out. -- 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/1465#discussion_r198314183 ----==_mimepart_5b32ba9a1a8e9_25453ff412ac8f78802c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

I've merged this, so let's open an issue to close this out.

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

----==_mimepart_5b32ba9a1a8e9_25453ff412ac8f78802c8-- From nobody Tue Jun 26 15:14:52 2018 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 7EA37130E15 for ; Tue, 26 Jun 2018 15:14:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 bJg_E1Lfq2ti for ; Tue, 26 Jun 2018 15:14:48 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 1F67D130DF1 for ; Tue, 26 Jun 2018 15:14:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051287; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nyL3ydEsu6LLLXPupV+jQkAgX3yd1Kj8t+BYz8Zup+0=; b=MJ5rib2SMeoIt7/niRVEtG3MQ9O3UXCpxSqWs9ubLKix3bG6VRB1lSzc9kSkTontOLj2OxLC QjPjvR0DyoUxbsW8IRmaq0Aeppfv4Jbzm2uTdswJ/Rhd4OmvbcowFOynsPHxp1+0o/+7dL4x HnMFJsFSQSx0hSiGUD0F5z+ly8M= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: jri.ietf=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32bad7.7f4629984240-smtp-out-n02; Tue, 26 Jun 2018 22:14:47 -0000 (UTC) Date: Tue, 26 Jun 2018 15:14:46 -0700 From: Jana Iyengar Reply-To: Jana Iyengar To: quic-issues@ietf.org Message-ID: <5b32bad62589f_2561c2b138576fc14717e3@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 1d6b6f: typo Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32bad6253a3_2561c2b138576fc1471646"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:14:50 -0000 ----==_mimepart_5b32bad6253a3_2561c2b138576fc1471646 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 1d6b6f1dd76829b9010b8599383f0e2c6312d5c8 https://github.com/quicwg/base-drafts/commit/1d6b6f1dd76829b9010b8599383f0e2c6312d5c8 Author: Jana Iyengar Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- typo **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32bad6253a3_2561c2b138576fc1471646-- From nobody Tue Jun 26 15:19:04 2018 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 00959130EFF for ; Tue, 26 Jun 2018 15:19:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 46wNh8b6shtw for ; Tue, 26 Jun 2018 15:19:00 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 030C2131144 for ; Tue, 26 Jun 2018 15:19:00 -0700 (PDT) Date: Tue, 26 Jun 2018 15:18:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051539; bh=nq16LT0/Kc2mT94uTOGN9uLmPq98Mw5buJFqM8mu458=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=S26mG20X+EchXI7YobI9JyXfIc0aA6V3aUC2otoCSqXwbKBahfI1SMEZqU2IUfvAw dtScIBxSm0OTN5ihXqmV8fEnqxB6KXUyNQSU4Jfz+RSQyTtAtnTfVImwyVJbue64o6 ST5EejP66m6+mvR6To7WozGUfEGw2svKwLhoCNfg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32bbd366c8a_6403f9159f46f8085251"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 22:19:02 -0000 ----==_mimepart_5b32bbd366c8a_6403f9159f46f8085251 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. a77b066 Typos, renumber -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1477/files/9b80c45f58b43ede57b9876e21df30dfa963f49b..a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf ----==_mimepart_5b32bbd366c8a_6403f9159f46f8085251 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32bbd366c8a_6403f9159f46f8085251-- From nobody Tue Jun 26 15:19:51 2018 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 B3225131149 for ; Tue, 26 Jun 2018 15:19:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 v8chX8i2-WGW for ; Tue, 26 Jun 2018 15:19:48 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 85964131143 for ; Tue, 26 Jun 2018 15:19:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051588; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=mnq8XkHxjSEfd4oQ3Ta2qrB3GXdSm+ACXbPKHp9s6+E=; b=wskE/TLkMF8pR7hmmSat61Glj3Dh2P7+Qk8BRK2spdEnl1b5c7w2f7Rscsr8pcnz8C8UGZ4e w+j2ij1HKeQfjTVHAkcGyiFd5NpeUVmIby/FRBTKU1r7gpuODBC0m7p7rZTwPR3g701nqI1E XvWlxQkm3UC6hpzfZuWBKRuCRG0= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32bc03.7fac4086d990-smtp-out-n03; Tue, 26 Jun 2018 22:19:47 -0000 (UTC) Date: Tue, 26 Jun 2018 15:19:46 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32bc02e6838_2e2f2afb6b0e5c0447587@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d76834: commas Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32bc02e64db_2e2f2afb6b0e5c04474ce"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:19:50 -0000 ----==_mimepart_5b32bc02e64db_2e2f2afb6b0e5c04474ce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts Commit: d7683479e2bdde11a8763e1964916937e2f33063 https://github.com/quicwg/base-drafts/commit/d7683479e2bdde11a8763e1964916937e2f33063 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- commas **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32bc02e64db_2e2f2afb6b0e5c04474ce-- From nobody Tue Jun 26 15:19:58 2018 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 C969C131147 for ; Tue, 26 Jun 2018 15:19:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vaSZpZxzaifM for ; Tue, 26 Jun 2018 15:19:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CAAE131143 for ; Tue, 26 Jun 2018 15:19:50 -0700 (PDT) Date: Tue, 26 Jun 2018 15:19:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051589; bh=RSnv0zDm9skJCzVsEkybUnxYGDTMtmfQDl1mY+X29iI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PiyiX1SJBE8Ur69O8i9ZVb4n/9Qmyq5PERJW8yH39KjsFGm9cmVdbnZOTQbQnDYRn aH38mNmgEC5BlED9IZtbm5TozUAWbAnPJJcJaB8KdpWXun4HFmWAusi2gqnDBL2GDI sEQX/NSORrIVWpKQeWjf6EudM2pdtSvaamgRldiU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32bc05ca5ae_73403fa1935eaf7833196"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 22:19:55 -0000 ----==_mimepart_5b32bc05ca5ae_73403fa1935eaf7833196 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. d768347 commas -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1477/files/a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf..d7683479e2bdde11a8763e1964916937e2f33063 ----==_mimepart_5b32bc05ca5ae_73403fa1935eaf7833196 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32bc05ca5ae_73403fa1935eaf7833196-- From nobody Tue Jun 26 15:22:44 2018 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 43A1F13114B for ; Tue, 26 Jun 2018 15:22:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 SBnMbpM_AuAK for ; Tue, 26 Jun 2018 15:22:42 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 11FA4131149 for ; Tue, 26 Jun 2018 15:22:42 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051761; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=g8b6Gxu2ZPR+upMiOyp7UzQ1h1cGiiPF1TZR4mndj3k=; b=d/EyMfmAmpvnMLWIFdE7tb7n64PFbB783ue1Ng+mp/VSkaHFNRfMdspNLLHllvlpgM0dG1Po u+EvLgaGGPTHRXl8MTvu/FJeHCa3PMQNCftuUrplMX5buy8gx5RPljN6AqTziKCm0pURaxbP ouf8OJHKQJPANXl8tDICIMzXgQY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b32ba58.7f820a87e7e0-smtp-out-n03; Tue, 26 Jun 2018 22:12:40 -0000 (UTC) Date: Tue, 26 Jun 2018 15:12:39 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32ba5740c7a_26c62b155e35bc105301a@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32ba57407f9_26c62b155e35bc1052974"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:22:43 -0000 ----==_mimepart_5b32ba57407f9_26c62b155e35bc1052974 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/ratchet_precision Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32ba57407f9_26c62b155e35bc1052974-- From nobody Tue Jun 26 15:23:18 2018 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 5FAB1131143 for ; Tue, 26 Jun 2018 15:23:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 VlMw1joM1Vot for ; Tue, 26 Jun 2018 15:23:15 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 DD1B6130EFF for ; Tue, 26 Jun 2018 15:23:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530051794; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=LJ4XDL5gcCbMhCJCTmHw2wJlYAiUfWRvbv+5N+O4Fm4=; b=hTuJ37Dg6+1xrrwh/maMq/H4CjV0gBb969XOaJoH5kb4dk2mwe4r1bPbETzh1mBRwLtXfz3k b33XYF+T6eANzTdKIMrwvb7WSXmZVjmkbxNzeHp23cJp2vXVXlxUOs6IeGP2fRA+GKCRw+++ q589YMn34p0TtsnvP/1/+ShaYz0= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32bcd1.7f7dd6fe5240-smtp-out-n03; Tue, 26 Jun 2018 22:23:13 -0000 (UTC) Date: Tue, 26 Jun 2018 15:23:13 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32bcd1b0959_32a92af076289c0410239d@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32bcd1b060a_32a92af076289c0410225e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:23:17 -0000 ----==_mimepart_5b32bcd1b060a_32a92af076289c0410225e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ext-frame Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32bcd1b060a_32a92af076289c0410225e-- From nobody Tue Jun 26 15:23:26 2018 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 362DB13114B for ; Tue, 26 Jun 2018 15:23:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 czl5K3Gqqsrq for ; Tue, 26 Jun 2018 15:23:17 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B32C7130EFF for ; Tue, 26 Jun 2018 15:23:17 -0700 (PDT) Date: Tue, 26 Jun 2018 15:23:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530051797; bh=2ntkCHIck8OL+wHTpBf21vttFBsp7vp/yoAjKefXxNc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bxV4l4mNf/O8MnqRhBrCX/dk5gM8gy7+yvMLECNVl7JXrMiWQOsfYy13ikYrDEuDr BSb7lc3y3sj7d0fhO7h+1JdLQprDmYgnbCcA/F8KnnOp6y5qAx3q9G+J59y3KL3Ch1 j5nNxSEP5W3oz2Y3tbGgwvF2sLsEzsZ3zp3uxxfI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1068) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32bcd5f4ed_6773f9159f46f80803a4"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:23:22 -0000 ----==_mimepart_5b32bcd5f4ed_6773f9159f46f80803a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1068. -- 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/1068#event-1702608176 ----==_mimepart_5b32bcd5f4ed_6773f9159f46f80803a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1068.

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

----==_mimepart_5b32bcd5f4ed_6773f9159f46f80803a4-- From nobody Tue Jun 26 15:29:02 2018 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 EC92C130E42 for ; Tue, 26 Jun 2018 15:28:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 hRQ7yjZng9-n for ; Tue, 26 Jun 2018 15:28:59 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 DC7E2129C6A for ; Tue, 26 Jun 2018 15:28:58 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530052138; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=20g/sSdhY7WKH7aRKExO8BwryPQ1Ckmnxf+NtksY15I=; b=VT9baK5qb+qO8SpfVySXeobJWCrDe3/9TuIv3+++plkxKJSOt4Q+6oVJuU8NK6wEZu540ePc aD6238TGYGudTe8w3kSEl0nqx9T4NIay1+B4AC9xsXbUbKK9S7gHjjEzGAu1u3RPk2qW5Mp+ UP3UXR2ml8MOdGaTl2e/0tCc1K8= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32bbd1.7f4022d63ab0-smtp-out-n02; Tue, 26 Jun 2018 22:18:57 -0000 (UTC) Date: Tue, 26 Jun 2018 15:18:56 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32bbd092b80_3ba62abb02329c084907f@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] a77b06: Typos, renumber Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32bbd092818_3ba62abb02329c0848925"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:29:01 -0000 ----==_mimepart_5b32bbd092818_3ba62abb02329c0848925 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts Commit: a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf https://github.com/quicwg/base-drafts/commit/a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Typos, renumber **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32bbd092818_3ba62abb02329c0848925-- From nobody Tue Jun 26 15:38:58 2018 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 07E8913116A for ; Tue, 26 Jun 2018 15:38:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 nRDDHZXrCPQt for ; Tue, 26 Jun 2018 15:38:39 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F9B613113A for ; Tue, 26 Jun 2018 15:38:39 -0700 (PDT) Date: Tue, 26 Jun 2018 15:38:38 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530052718; bh=0onUQqacu1sdDHY/YNj/5n5OLbii37fWmRbF+mf5sqk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=A/wD899W6/x6V9yjK7nfzn4vqqpRK6svIpuPSpMhePDjEO0bveBscF8JlEvuPGiSs noKhIIDOlviB8JmQUbjQzzgA8kglQbeTjbB623iYXmt9lVONbNBmFRYtVRsqoiYXHv unNBXBvQ3cenbXY/umvi4X/gCM4PMBqtGecgkGX8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream0 dt output ready (#1377) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c06e91a79_399f2b21d261af5c2847d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:38:56 -0000 ----==_mimepart_5b32c06e91a79_399f2b21d261af5c2847d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1377. -- 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/1377#event-1702628621 ----==_mimepart_5b32c06e91a79_399f2b21d261af5c2847d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1377.

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

----==_mimepart_5b32c06e91a79_399f2b21d261af5c2847d-- From nobody Tue Jun 26 15:42:19 2018 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 B6C4B129C6A for ; Tue, 26 Jun 2018 15:42:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 9Zl1YohyVMao for ; Tue, 26 Jun 2018 15:42:15 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 47210131141 for ; Tue, 26 Jun 2018 15:42:15 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530052934; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=TH37yTSZ5XWTQFOCFw9GHhETQN3BZAs/osKhfS1zyYc=; b=qp7G6cDxx1y/W90bAKPAkBtCfut45nUdYbT+1ENB2xGpOuLDAtFCpz5OJY//1F/xO0XMCHCD FLXxtA0cPwOPnVbOrpfRCLJ+GJedMszzgYKR+fDFvBHP30p7cuIWjylpplTUq5O+XgTfLfYo O8uu5G5qTw5puwzLUzxPo0Gy4ww= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32c146.7fe13c0c77e0-smtp-out-n03; Tue, 26 Jun 2018 22:42:14 -0000 (UTC) Date: Tue, 26 Jun 2018 15:42:14 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c1468cdeb_5a292b2508db9c0c72065@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 81e10c: PROTOCOL_VIOLATION for bad frame type Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c1468c416_5a292b2508db9c0c71996"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:42:17 -0000 ----==_mimepart_5b32c1468c416_5a292b2508db9c0c71996 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts Commit: 81e10cc2c71804fdd8945244381510c63df3c257 https://github.com/quicwg/base-drafts/commit/81e10cc2c71804fdd8945244381510c63df3c257 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- PROTOCOL_VIOLATION for bad frame type Commit: 89c0aefc2371a872e8de519346c225c1e0fc17e0 https://github.com/quicwg/base-drafts/commit/89c0aefc2371a872e8de519346c225c1e0fc17e0 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- WIP Compare: https://github.com/quicwg/base-drafts/compare/e4725aca6943...89c0aefc2371 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c1468c416_5a292b2508db9c0c71996-- From nobody Tue Jun 26 15:42:25 2018 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 58BEA130EFF for ; Tue, 26 Jun 2018 15:42:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vbLCaWW3mzSb for ; Tue, 26 Jun 2018 15:42:18 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93B25129C6A for ; Tue, 26 Jun 2018 15:42:18 -0700 (PDT) Date: Tue, 26 Jun 2018 15:42:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530052937; bh=jJ791+XV2MdlfE+z6ftWIB4KUezgJhEWQmSotj12t4Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IvgihJAFQqYrMZp5EUqLdmJq2Z/sUnWJ/XhN6oYbWnmPD7d3V5+Fmx6pQSl6nFR+d Vbqdas0cvm/WsKtouFh0it8AuSgUGifB/Hz/tVvIdpU6KSetteDX122cZjO8UORyBc TjK3TRG5sMhfHqLr0J5Px10mXGxpdgn9raAQJcKk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c149ebdc8_77672adda5a7ef6070413"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 22:42:23 -0000 ----==_mimepart_5b32c149ebdc8_77672adda5a7ef6070413 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 2 commits. 81e10cc PROTOCOL_VIOLATION for bad frame type 89c0aef WIP -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1473/files/e4725aca6943b04e1ef7f347a0fea5ade6313741..89c0aefc2371a872e8de519346c225c1e0fc17e0 ----==_mimepart_5b32c149ebdc8_77672adda5a7ef6070413 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 2 commits.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32c149ebdc8_77672adda5a7ef6070413-- From nobody Tue Jun 26 15:49:09 2018 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 52E7A13114B for ; Tue, 26 Jun 2018 15:49:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 mAWKEyRZ5fPy for ; Tue, 26 Jun 2018 15:49:05 -0700 (PDT) Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B61A7129C6A for ; Tue, 26 Jun 2018 15:49:05 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=ybldn6SZ4tqONmyI+XzuAyHt60hkrSg0NHhw5IjtcV0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=D5cSClpPnbjyvl5rcHoEhsL0W19u0q4jaCLZv7afCXIwLRF5rORowE8N8N+P0XX2m If2K1qMRoHknf8Q8oegWRE/4OTApSPh1ic79XJ4CbI36c86cIihrlLmwcwSQDkIj8u tcLKv+0ijqEqd6JwKM14O8Hr732iBoWbgE9AhQ7s= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Implicit acknowledgment during handshake (#627) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e124e5c_14fd2afdfb754f58440f7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:08 -0000 ----==_mimepart_5b32c2e124e5c_14fd2afdfb754f58440f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #627. -- 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/627#event-1702641489 ----==_mimepart_5b32c2e124e5c_14fd2afdfb754f58440f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #627.

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

----==_mimepart_5b32c2e124e5c_14fd2afdfb754f58440f7-- From nobody Tue Jun 26 15:49:21 2018 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 9256313114B for ; Tue, 26 Jun 2018 15:49:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TNplK90S_lsz for ; Tue, 26 Jun 2018 15:49:05 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93E3130E5F for ; Tue, 26 Jun 2018 15:49:05 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053344; bh=wDZLULwECV1vwYs1UDIjdgXYVZ6oG37C41aohskuaRQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JrLM9LMpz+/R2IhTUUyIeyTF9+MqDFvuCbyIdsAg/Y0SxoBCsH7SOseTfx7SY777N WzYk1XA6Cm6F28BjFnFgO4yNIONQgO0JewCks7S1dfFQRrGY0qTxhv4iYRUtNprPrL URagfFeYjHjtvOACnX8SppJ+rcaWLQ+dTySb7xW8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Second flight DOS Attack with Client Clear Text packets. (#1018) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e0e9d4d_277c2ab10a374f5c8649f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:09 -0000 ----==_mimepart_5b32c2e0e9d4d_277c2ab10a374f5c8649f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1018. -- 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/1018#event-1702641494 ----==_mimepart_5b32c2e0e9d4d_277c2ab10a374f5c8649f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1018.

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

----==_mimepart_5b32c2e0e9d4d_277c2ab10a374f5c8649f-- From nobody Tue Jun 26 15:49:28 2018 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 5DC58131154 for ; Tue, 26 Jun 2018 15:49:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1P7yCHZbxwv0 for ; Tue, 26 Jun 2018 15:49:08 -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 062E1130E8A for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=S44/MCAwwDMJDrZ3S8xAmUl6szMvImFCQvaTY+YspbI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a5GPrrHD7yqaViS5rx8hBAskrgUHoCKyxqIUNZnlbDC0+O4Brxv9pldsd62we2LV4 LxGN1FyScuwOCS2aqbqFVM9Er2UCZwBaFNWb/ok6rCcaDNtCtklvObktYc7QXIQrrT tA/PRbS7xCVm0bpvurPPMD5VaR36Yr+WXHt2O6Z0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Pathological loss recovery case with Finished (#1190) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e145f8c_1c453f963fc02f781834f2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:12 -0000 ----==_mimepart_5b32c2e145f8c_1c453f963fc02f781834f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1190. -- 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/1190#event-1702641507 ----==_mimepart_5b32c2e145f8c_1c453f963fc02f781834f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1190.

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

----==_mimepart_5b32c2e145f8c_1c453f963fc02f781834f2-- From nobody Tue Jun 26 15:49:35 2018 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 E256413115D for ; Tue, 26 Jun 2018 15:49:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jLFfYjXONzLz for ; Tue, 26 Jun 2018 15:49:07 -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 07CB413113E for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=BxiTAxQCiqa5nJ/KN4yUvdSLdAm90o7WTQrFMpBZxW0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KyoBeqvm2fIKVGMzbMVcCvTPGhY50t2oZAXYCx2dXBzc9WB4dFKePIeamBo3V04AB xzvE3f6oBcNBZGHDLm9wcSIKv9Gx7+2zXx6iFQYmZ/wa6Y2qOZTQy8Ch5iqUrD6ReR YrSEMXClYEdV12Hl6G6UrXHgLi/1Tlb2/zbtwldg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Do we still need Retry packets? (#1233) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e15f03d_6e033fac6856af787771d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:12 -0000 ----==_mimepart_5b32c2e15f03d_6e033fac6856af787771d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1233. -- 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/1233#event-1702641510 ----==_mimepart_5b32c2e15f03d_6e033fac6856af787771d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1233.

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

----==_mimepart_5b32c2e15f03d_6e033fac6856af787771d-- From nobody Tue Jun 26 15:49:40 2018 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 01BFC131158 for ; Tue, 26 Jun 2018 15:49:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 is_5zg4MBzaU for ; Tue, 26 Jun 2018 15:49:10 -0700 (PDT) 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 29F27131141 for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=RjSG4yox23exyjAerirRPU9c/aROABam8OjmoFgqZXo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KUERiISeANQN+xpnujjdq4wm5p5qKJd5yF4LKbbUbnML4kQ59OekCm6q2LA0zUx8Y +zPBcgl/atjDwL1u070HPB5DI0SbB8UHqqsU6duO8DUlMThAB9OdCsfwydk0FOs966 Op2/6d+op0qVbcB8cN4tKirwkh15AEuugjS7mgE0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Can a server use a Handshake packet for ACK of the last client Handshake packet (#829) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e15e6ef_13792afdfb754f58561ad"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:14 -0000 ----==_mimepart_5b32c2e15e6ef_13792afdfb754f58561ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #829. -- 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/829#event-1702641492 ----==_mimepart_5b32c2e15e6ef_13792afdfb754f58561ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #829.

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

----==_mimepart_5b32c2e15e6ef_13792afdfb754f58561ad-- From nobody Tue Jun 26 15:49:47 2018 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 8949313114C for ; Tue, 26 Jun 2018 15:49:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FrYxRCaYRAnb for ; Tue, 26 Jun 2018 15:49:10 -0700 (PDT) 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 3F51E130F25 for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=Kq50/ZVCyLnTk/JO/5Tati3gW0UzrAR5lFfWKVUKNdk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xaDbA2GSnIiAMBFpZt4TLXxsrPCTVDhnKyItc7XoFh4nM3hefCcIdnUVFCdvTeyRn zBk69h2/9tMfjTSws5tutCV4hJp/+arJRwV2t0p56EgxkEKJRUHnRSoDPGFuEGFbfy GeVaSPykhdOHIqO524gt9Bb2IzVHTCmM/p+m+bL0= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] QUIC over DTLS (#1165) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e18c1b3_7fcb2ab742928f501633ed"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:14 -0000 ----==_mimepart_5b32c2e18c1b3_7fcb2ab742928f501633ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1165. -- 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/1165#event-1702641502 ----==_mimepart_5b32c2e18c1b3_7fcb2ab742928f501633ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1165.

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

----==_mimepart_5b32c2e18c1b3_7fcb2ab742928f501633ed-- From nobody Tue Jun 26 15:49:52 2018 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 638A6130E5F for ; Tue, 26 Jun 2018 15:49:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 RjMqy4kwV0zU for ; Tue, 26 Jun 2018 15:49:12 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F9C131144 for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053345; bh=vbePxRXD+g5PpN64JQh99Bwju/vR8xPhKeOUxe4BjsY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=o3FJisSRSFBbTb7EXSOr9B611Z2pttpI2FT/IType/VS1wAyb14KcewE7FAPK5qyL 9uLs5IGK0DJWtyQ9i6FXJGe9+V6ZelCy2P9HiFCmy4cWLtnZe0WFuaKTvUuTrs7TiC UNFR3C9emrVHbcvu/6Fuh7v/vWCqkSXUsZmyocHE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CFIN only recoverable with timeout (#1242) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e19574d_b013fe2f70c2f7818797f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:15 -0000 ----==_mimepart_5b32c2e19574d_b013fe2f70c2f7818797f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1242. -- 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/1242#event-1702641515 ----==_mimepart_5b32c2e19574d_b013fe2f70c2f7818797f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1242.

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

----==_mimepart_5b32c2e19574d_b013fe2f70c2f7818797f-- From nobody Tue Jun 26 15:49:57 2018 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 DDC61130F25 for ; Tue, 26 Jun 2018 15:49:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 L5eu4wNikZV1 for ; Tue, 26 Jun 2018 15:49:12 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A204E131148 for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053346; bh=aL5NUq0n6P458Vi+/dHS8Y7YdZEAsC96rshgJKF17kA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u2CbK+XdrX8ivKiV8GA7tAcQCxxPEefASvf88w+JOFGSyPJLeu4rRVDL7LfZgCBnW 83HswAfR4W+zhHB0xXBg+34jyvEV6jJSjnDY+toa2YEc4J04J54OntUzBM8j623otN bo/xYtW7AoIxSnWers7/xDJlWQS948SBzvnBKhyE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Signals of Initial Packet (#1188) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e22d005_5892abd336d8f601067ee"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:15 -0000 ----==_mimepart_5b32c2e22d005_5892abd336d8f601067ee Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1188. -- 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/1188#event-1702641504 ----==_mimepart_5b32c2e22d005_5892abd336d8f601067ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1188.

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

----==_mimepart_5b32c2e22d005_5892abd336d8f601067ee-- From nobody Tue Jun 26 15:50:02 2018 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 1A2E4130E8A for ; Tue, 26 Jun 2018 15:49:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cDwOt_Q9pB76 for ; Tue, 26 Jun 2018 15:49:13 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7AA4131142 for ; Tue, 26 Jun 2018 15:49:06 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053346; bh=HQnYqypMPSaTQhVSZJx5/DVN9fh3MjOw2DZe23BmXBk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NIV+t3fJYU2at38H89fqIG1VIcN7oVdfuE7Kc2wvxI1tn3k3nBKKQ+FxkXmLldfE/ bF1jzLbv6NQ4TtXd/a4Kz8GA0RxKs0zMD6PTHIM90PilQgWn3iGXT3NSyNc+Irt80W 3UjjtEIGwh2XMEtKMIvKOn8NVlqAmpgAJGjKAnAU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream Flow Control on Stream 0 (#1252) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e23a84d_7fbf2ab742928f50146819"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:16 -0000 ----==_mimepart_5b32c2e23a84d_7fbf2ab742928f50146819 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1252. -- 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/1252#event-1702641520 ----==_mimepart_5b32c2e23a84d_7fbf2ab742928f50146819 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1252.

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

----==_mimepart_5b32c2e23a84d_7fbf2ab742928f50146819-- From nobody Tue Jun 26 15:50:06 2018 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 904BC130E5F for ; Tue, 26 Jun 2018 15:49:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 8LVjyWK7jwXh for ; Tue, 26 Jun 2018 15:49:13 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D95131149 for ; Tue, 26 Jun 2018 15:49:07 -0700 (PDT) Date: Tue, 26 Jun 2018 15:49:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053346; bh=1yaQGVU4F3jEHxzkufMiH/zembg/0r0Gm0Oe/pkhnMs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bPxr2ft6MoEr2nZf9TJaZAQwGTcmPP3vfayIJhxP4ze4PGst4OCeCkNRoWZG9KSvH jSlUsQ/dDgpEH/BPt/TFOj9gc3SkEyjNHXuyRFkvz1u9acgRaqSmPBgBgylQyJsqvu M8NJdlu5TU//Uoyi3xfmkDOy+KoBFRJ2bSI/B7MM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Recovery incorrectly declares packets lost at higher encryption levels (#1413) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e2ab3e8_5b82abd336d8f601270fc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:16 -0000 ----==_mimepart_5b32c2e2ab3e8_5b82abd336d8f601270fc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1413. -- 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/1413#event-1702641526 ----==_mimepart_5b32c2e2ab3e8_5b82abd336d8f601270fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1413.

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

----==_mimepart_5b32c2e2ab3e8_5b82abd336d8f601270fc-- From nobody Tue Jun 26 15:50:14 2018 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 0748A130E5F for ; Tue, 26 Jun 2018 15:49:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JOYUzg0HN68Q for ; Tue, 26 Jun 2018 15:49:15 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 DC410129C6A for ; Tue, 26 Jun 2018 15:49:07 -0700 (PDT) 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=i+nYJ2BqcT3QxgkgIWtZN5MX3wU=; b=SvQRkeI2+ZW5W2XO O/+e0ltkpjAu9hPjYwJuEetsNIq3MdP2l3kkymmGo7sj0RgqEce2feMo0zxQDCTO HkkmkS59ddPowZuXODDoa9Ir/o8wJJ0/eU+/LQHUJcuJCjKtg9abxZV7TPpkHheM KBabwwr/1z9buy+D+t7R0vOzwGU= Received: by filter0611p1iad2.sendgrid.net with SMTP id filter0611p1iad2-11282-5B32C2E2-19 2018-06-26 22:49:06.523088085 +0000 UTC Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) by ismtpd0045p1mdw1.sendgrid.net (SG) with ESMTP id e9M01nGITBa0yY6rRz4GOA for ; Tue, 26 Jun 2018 22:49:06.163 +0000 (UTC) Date: Tue, 26 Jun 2018 22:49:06 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarification: HRR which does not perform address validation (#1094) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c2e16cc97_7fb92ab742928f501273b"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2qhtfLIX9TrY7O6+mEs43FUtdROdfYFgPr8x L1J+REDufTiswCpYUR9j5ZBqup3UhJryTk20xEViU8m1CEep2DmYaPg4A6LCMVfIZvTVrapWO1g+Jv zrCN/neWgPSkqa1S6P9s5s6mRXQliiWlG0q7i2jMrCLmZe4MNPwGa0wLAIpvifZG6Zg4ucfDt5d2Zg k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:49:20 -0000 ----==_mimepart_5b32c2e16cc97_7fb92ab742928f501273b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1094. -- 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/1094#event-1702641498 ----==_mimepart_5b32c2e16cc97_7fb92ab742928f501273b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1094.

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

----==_mimepart_5b32c2e16cc97_7fb92ab742928f501273b-- From nobody Tue Jun 26 15:51:07 2018 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 5BDB1131140 for ; Tue, 26 Jun 2018 15:50:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 MPlFeEf3vhOZ for ; Tue, 26 Jun 2018 15:50:46 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 0A796131161 for ; Tue, 26 Jun 2018 15:50:43 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530053443; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=NHjiMuqIRXOde9PcTwm7NoE9Egr7z5jfec9esljpCX8=; b=CrzH0Fp4OEO89jf6L9y71pYQzx7Z0XbfAs+bye0nIjWdrBnASQgrLaVXHYmjYVlNkddxASHD ggSLm65JZ8j9uTuM388u7xytzobjOxGltMX8YeRz8uUko2cfcgZwnVWwmBGgUkfulKjR/O65 33ynZa7Jvww2/fZ5cQsKJQ+2+1s= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32c343.7fe035e80180-smtp-out-n01; Tue, 26 Jun 2018 22:50:43 -0000 (UTC) Date: Tue, 26 Jun 2018 15:50:42 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c34251276_3ab42aba52d55c141075b2@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 6fa28c: reflow Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c34250ea3_3ab42aba52d55c14107491"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:50:59 -0000 ----==_mimepart_5b32c34250ea3_3ab42aba52d55c14107491 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts Commit: 6fa28c2172d549f036ca97ab6cf981c7162f2660 https://github.com/quicwg/base-drafts/commit/6fa28c2172d549f036ca97ab6cf981c7162f2660 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- reflow **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c34250ea3_3ab42aba52d55c14107491-- From nobody Tue Jun 26 15:51:15 2018 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 C1AA9130E8A for ; Tue, 26 Jun 2018 15:50:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oKcJFYMDnu0F for ; Tue, 26 Jun 2018 15:50:47 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 132E3131166 for ; Tue, 26 Jun 2018 15:50:46 -0700 (PDT) Date: Tue, 26 Jun 2018 15:50:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053445; bh=uGt4h1Ahy0KiIjyMrtShZnke9Jh5rRFW8wGTWjMQX9g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vjjrckUyVw99w482Au/jdfBiIc8di+M01GVxgDLUkpXudCdEi2hYBjHfG0YJoyj+f 2S4AJqd7DuIVSPp0vfyv04xetPWLaud7SErsrdeAZG8EgfnTxLw0Ik/b1H87IDNm4g QJX4M+7b5aKw0WFInJCWgBx4DSH6cYc7l/9hjazM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c3456c20c_52e32ab89a4f2f5458584"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 22:51:07 -0000 ----==_mimepart_5b32c3456c20c_52e32ab89a4f2f5458584 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 6fa28c2 reflow -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1473/files/89c0aefc2371a872e8de519346c225c1e0fc17e0..6fa28c2172d549f036ca97ab6cf981c7162f2660 ----==_mimepart_5b32c3456c20c_52e32ab89a4f2f5458584 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32c3456c20c_52e32ab89a4f2f5458584-- From nobody Tue Jun 26 15:52:18 2018 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 E1B30130E8A for ; Tue, 26 Jun 2018 15:52:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 D9C__MMQBvx5 for ; Tue, 26 Jun 2018 15:52:03 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 8198E131158 for ; Tue, 26 Jun 2018 15:52:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530053522; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nhVdp9ukubCckUXOeqYCxgkQv6Efui+kD7lsHzpw02A=; b=NB7V+hx3x9YIB5AKCgEXl75YGdJFysaZ3065dzLJhGhqTeIB7+nlDiTnJlwO+0P+WyAhPC2U hnaWw2ki+8QpM31WcbrpFs0n/gXeLmNgemdAz80ia/Dc0kZsJBSSPQ1FFoY3VAgL9ekyI6Wq 7ULjDvuyH/8GFNc7Nsy/oZ3skCA= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b32c392.7f3554425ae0-smtp-out-n01; Tue, 26 Jun 2018 22:52:02 -0000 (UTC) Date: Tue, 26 Jun 2018 15:52:02 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c392954d4_40512b22e934fc1044012@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 09b7e9: Simplify Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c392950a9_40512b22e934fc10439e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:52:17 -0000 ----==_mimepart_5b32c392950a9_40512b22e934fc10439e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts Commit: 09b7e945e7aaa909144651f9c7411a5f8dd774e7 https://github.com/quicwg/base-drafts/commit/09b7e945e7aaa909144651f9c7411a5f8dd774e7 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Simplify **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c392950a9_40512b22e934fc10439e2-- From nobody Tue Jun 26 15:52:30 2018 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 8FDB313113E for ; Tue, 26 Jun 2018 15:52:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2Gdm6UJVKC87 for ; Tue, 26 Jun 2018 15:52:13 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C024513115E for ; Tue, 26 Jun 2018 15:52:05 -0700 (PDT) Date: Tue, 26 Jun 2018 15:52:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053525; bh=PE6Q5/Xo23kZjKXZWD7tpJNCVIXutgvlpA3EmxquWPk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aRKY59jPgAP4s5phKGsVkmw5gS08rSv1r95jxmxauUQ4XH+e/BuVmjU3sOpDT1ckq A1+MrTafY44z9NYDd68lBQKjMHjsaGpDFk1yZsutk0TpBi+SB770S+J0AKBEmeD8P0 xpqK0xzXwPSehje8AbxNQoz1Tcj+bgT4PRL2g0EY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c395276ac_4a9f3f8a87e18f881563cc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 22:52:27 -0000 ----==_mimepart_5b32c395276ac_4a9f3f8a87e18f881563cc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 09b7e94 Simplify -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1473/files/6fa28c2172d549f036ca97ab6cf981c7162f2660..09b7e945e7aaa909144651f9c7411a5f8dd774e7 ----==_mimepart_5b32c395276ac_4a9f3f8a87e18f881563cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32c395276ac_4a9f3f8a87e18f881563cc-- From nobody Tue Jun 26 15:53:48 2018 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 43E25130E5F for ; Tue, 26 Jun 2018 15:53:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ZBf7kNMh4E2l for ; Tue, 26 Jun 2018 15:53:44 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9308E129C6A for ; Tue, 26 Jun 2018 15:53:44 -0700 (PDT) Date: Tue, 26 Jun 2018 15:53:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053623; bh=mdY4yvaGvW1vasnQyfKGwiVs0uw2eBRYa7Tvn5KjWbQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=p/zc14Vz4bIyaaVbVd33+h483zAoc4m/kN4nafE0gqkuvC7zHh8IWcMCriu/HtU7f RGjG2cxKbkIBEawvmFStRC9sGmusIS/O7j0kVaNXAYotg1FnyLnEW5GpY7IPeFgdix rlwZyG0n3ho6e2r7SOzw/XjUduW2SmTpPBBbZU9Y= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Extension poster-child (#1482) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c3f7eba40_59992ae6ebdf2f5814597"; 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.26 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: Tue, 26 Jun 2018 22:53:47 -0000 ----==_mimepart_5b32c3f7eba40_59992ae6ebdf2f5814597 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Lars had suggested a while back that BLOCKED and friends are unnecessary = to the core protocol. These frames are NOT REQUIRED, but since you=E2=80= =99re allowed to send them, every implementation must be able to receive = and skip them even if they=E2=80=99re ignored. In HTTP/2, we decided to = remove BLOCKED from the main spec and let that be reintroduced as an exte= nsion if anyone wanted. (It turned out no one did.) As part of the review on the new Extension mechanism, Ian had suggested t= hat we should consider actually publishing an extension to demonstrate ho= w the extension mechanism would work. It has also proved useful in HTTP/= 2 to have some extensions we can point authors to and say =E2=80=9Cdo it = like that.=E2=80=9D Now that the extension mechanism is landing/landed, does the working grou= p want to consider pulling BLOCKED and kin out to a separate document and= letting it be our recommended demo extension? -- = 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/1482= ----==_mimepart_5b32c3f7eba40_59992ae6ebdf2f5814597 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Lars had suggested a while back that BLOCKED and friends are unnecessa= ry to the core protocol. These frames are NOT REQUIRED, but since you=E2= =80=99re allowed to send them, every implementation must be able to recei= ve and skip them even if they=E2=80=99re ignored. In HTTP/2, we decided = to remove BLOCKED from the main spec and let that be reintroduced as an e= xtension if anyone wanted. (It turned out no one did.)

As part of the review on the new Extension mechanism, Ian had suggeste= d that we should consider actually publishing an extension to demonstrate= how the extension mechanism would work. It has also proved useful in HT= TP/2 to have some extensions we can point authors to and say =E2=80=9Cdo = it like that.=E2=80=9D

Now that the extension mechanism is landing/landed, does the working g= roup want to consider pulling BLOCKED and kin out to a separate document = and letting it be our recommended demo extension?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b32c3f7eba40_59992ae6ebdf2f5814597-- From nobody Tue Jun 26 15:54:06 2018 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 33ADD129C6A for ; Tue, 26 Jun 2018 15:54:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1EUadlYozM0D for ; Tue, 26 Jun 2018 15:54:00 -0700 (PDT) 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 99FEF130E5F for ; Tue, 26 Jun 2018 15:54:00 -0700 (PDT) Date: Tue, 26 Jun 2018 15:53:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053639; bh=rmC7n8j+Sjv39OCd5KC4q6SuEjQZTh1zgEdMDNin190=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WAnA26EwjesiiL771wkR5Rn44yulualw1/tZXXl8Ws7evXAJEHY3cTsUop91/okeo cL8Z/qlUgITOkqTdkdcmVvZuGHsVcSr2AlqlkfljTfVVI2FCjxE43zD69xIpJ4qPZ9 kXXblwuzPvjKhdNpC3lCCEU8qnQMtsnloHOu7Ae8= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add a MESSAGE frame optimized for sub-MTU payloads (#814) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c407dacf3_67c3f84b94aaf88682de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Tue, 26 Jun 2018 22:54:04 -0000 ----==_mimepart_5b32c407dacf3_67c3f84b94aaf88682de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Now that we have an extension mechanism, this is an excellent candidate. -- 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/814#issuecomment-400488500 ----==_mimepart_5b32c407dacf3_67c3f84b94aaf88682de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Now that we have an extension mechanism, this is an excellent candidate.

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

----==_mimepart_5b32c407dacf3_67c3f84b94aaf88682de-- From nobody Tue Jun 26 15:55:42 2018 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 3723C130EF1 for ; Tue, 26 Jun 2018 15:55:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 iEC85T5W3tIb for ; Tue, 26 Jun 2018 15:55:38 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 916BF130E8A for ; Tue, 26 Jun 2018 15:55:38 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530053738; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=oD4Y/qGbk7bNaRODKuY8ezYDbGc0WFoLHZFxE8cT+zA=; b=tgDl0rxa3OzpR29LZrlygR+7ns0AyJ9YxFBWbLhMb734nw4HybUzGdbMaSGOTD6eeVZcvKj/ aFW1ctVkl8vrz6NtZn6KLNGCHvV5o18DauOJEBeF2+lkRDs5wjsk7ipHlNUo9dUfQSgmVH/z aIRkMDQ01VPyEDjqw9moBHphjQc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b32c469.7fa432613d20-smtp-out-n02; Tue, 26 Jun 2018 22:55:37 -0000 (UTC) Date: Tue, 26 Jun 2018 15:55:37 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c46921a32_3df22b1266135c1039571@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ec94b6: TP to disable migration Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c469213cf_3df22b1266135c1039469"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:55:41 -0000 ----==_mimepart_5b32c469213cf_3df22b1266135c1039469 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: ec94b63b140ea2d92417a6c9c674d10cb1d6f001 https://github.com/quicwg/base-drafts/commit/ec94b63b140ea2d92417a6c9c674d10cb1d6f001 Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- TP to disable migration Commit: b789dd84f3b9dbd0182f8b674411368824afb22b https://github.com/quicwg/base-drafts/commit/b789dd84f3b9dbd0182f8b674411368824afb22b Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- local address Commit: f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b https://github.com/quicwg/base-drafts/commit/f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Bilateral, error Commit: 9cb100067a0c892b68a8ca5156fadc22f5365932 https://github.com/quicwg/base-drafts/commit/9cb100067a0c892b68a8ca5156fadc22f5365932 Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Discuss rebinding briefly Commit: aca29a5b84be32cd672a1871254812357c4ff9fd https://github.com/quicwg/base-drafts/commit/aca29a5b84be32cd672a1871254812357c4ff9fd Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1447 from quicwg/transport/disable_migration TP to disable migration Compare: https://github.com/quicwg/base-drafts/compare/1d6b6f1dd768...aca29a5b84be **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c469213cf_3df22b1266135c1039469-- From nobody Tue Jun 26 15:55:52 2018 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 6F8B1130E5F for ; Tue, 26 Jun 2018 15:55:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 0P-kZCJJenZF for ; Tue, 26 Jun 2018 15:55:41 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 C17F913113F for ; Tue, 26 Jun 2018 15:55:40 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530053740; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=F931iWHt+rScytXIZTgGMJh2Q9CR4gbI/SpDO0upPIc=; b=C4h59AIX31TZ4ff1V623hdcI4rpveFHOnqe3uNSr4STOzPq0FkttZVldsdEsqgAjpsMqbLcH sXSItv8tcsKApIxRMXfKOb2A+2h1Q1i4n07e87VNuuwrcm45Zx+fwl5BjB6swzDp6dwGtnAk 0jAdvwLg1y+b4otFXTf5RnTzx24= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32c46c.7fa9474f8810-smtp-out-n03; Tue, 26 Jun 2018 22:55:40 -0000 (UTC) Date: Tue, 26 Jun 2018 15:55:40 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32c46c51b89_3ad22ad175a95c10451b1@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c46c517b8_3ad22ad175a95c10450fd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 22:55:43 -0000 ----==_mimepart_5b32c46c517b8_3ad22ad175a95c10450fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/disable_migration Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c46c517b8_3ad22ad175a95c10450fd-- From nobody Tue Jun 26 15:55:58 2018 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 A85B2130EF1 for ; Tue, 26 Jun 2018 15:55:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1l97jnx7Rs1c for ; Tue, 26 Jun 2018 15:55:40 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42199130E8A for ; Tue, 26 Jun 2018 15:55:40 -0700 (PDT) Date: Tue, 26 Jun 2018 15:55:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053739; bh=Vkm3KfDdx4MCOOmQoMNCMltdwpHq/rUKIVTAGo73ZrI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a230OX+x5nlB2TUUd/ZGix+mN0oAneePojchuI/vL3e3C7nVECk6+CmdbIvL2SRM2 TOZ8teiiYYHTNr96hHDZWwrOySxwhmHwuLl/Wc+EiEviQTrqfZ2//kZg3Ln2CVMpzs VaXNMIGeMi0khruu4wWqVyVjEGxQo1NbgkST4bKA= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection migration optional? (#1271) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c46b90c76_39d02b21d261af5c735d2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:55:43 -0000 ----==_mimepart_5b32c46b90c76_39d02b21d261af5c735d2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1271 via #1447. -- 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/1271#event-1702649374 ----==_mimepart_5b32c46b90c76_39d02b21d261af5c735d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1271 via #1447.

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

----==_mimepart_5b32c46b90c76_39d02b21d261af5c735d2-- From nobody Tue Jun 26 15:56:07 2018 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 EBF88130EF1 for ; Tue, 26 Jun 2018 15:55:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 u07YuaizZPTu for ; Tue, 26 Jun 2018 15:55:42 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3BA3130F53 for ; Tue, 26 Jun 2018 15:55:40 -0700 (PDT) Date: Tue, 26 Jun 2018 15:55:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053740; bh=Ah9ryCl5NNKh+MmR8ZiBLbfuiEsQQIpnid98qzZ5Txo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Wo7k12xV/cbhTboX1lgwWW7GvlS53uVQVvqI8+azyoeu9ngH+fVKerJsntmwNVuK6 +LLT583haLZmmjN3cE7fpwhJn/8IgX4Vyq4jhPikE8NNCzKPlqkHzDYPMubfA9pAJ9 LGXSMxsXWd7oBzIEG6bsc16Qrb6ymXGv2FsO3ZOQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c46c76e2_27383fe73163cf88174365"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:55:45 -0000 ----==_mimepart_5b32c46c76e2_27383fe73163cf88174365 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1447. -- 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/1447#event-1702649372 ----==_mimepart_5b32c46c76e2_27383fe73163cf88174365 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1447.

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

----==_mimepart_5b32c46c76e2_27383fe73163cf88174365-- From nobody Tue Jun 26 15:56:19 2018 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 4BD01130E8A for ; Tue, 26 Jun 2018 15:56:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Que-617e4wWc for ; Tue, 26 Jun 2018 15:56:13 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B1B2130E5F for ; Tue, 26 Jun 2018 15:56:13 -0700 (PDT) Date: Tue, 26 Jun 2018 15:56:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530053772; bh=4PVoHklYsmYNZi0Z8QpSVE+cwZcV1YM5YbFLibE82lo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JUmo0jOfpqtEp5ca4FNteREeIOnFUQPj9r6lyRNugT26eAHuWGXwLk3bvvCDHvSkM nxJUpi3PLkUsEH8bnyo7uO5CNhCcpLXMhSN26yBUDLFZ+ZcEQgOmzt25r4bJhvamGT 3A1umGLsA2OBltVC+o2FF+8d7QDujvAekiYGppCM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN Proposal with only two counters (#1460) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c48cea67c_776d2adda5a7ef601353f5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:56:17 -0000 ----==_mimepart_5b32c48cea67c_776d2adda5a7ef601353f5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit we're making progress on the other, so let's close this -- 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/1460#issuecomment-400488884 ----==_mimepart_5b32c48cea67c_776d2adda5a7ef601353f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

we're making progress on the other, so let's close this

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

----==_mimepart_5b32c48cea67c_776d2adda5a7ef601353f5-- From nobody Tue Jun 26 15:56:28 2018 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 D866213114B for ; Tue, 26 Jun 2018 15:56:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AzhfK-tGHMba for ; Tue, 26 Jun 2018 15:56:16 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 A4CA2130E5F for ; Tue, 26 Jun 2018 15:56:16 -0700 (PDT) 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=nuFvq0sjvF4WXCMF/vRo/pJoDdo=; b=DReQm7Lm5vjMOPkp pdyo2mC42wZa18AUgps57/TBfufpiVsjNnRp6RfTsWeFFxTC5reD5yJxpZ40dGg7 3knNYnzfiV78v1PtkZnJxRmH9L+eISv33ViTgKlZMWQtqfQj4OWlqvT7vV/CxhCv dnEGEuMBYN7ProHMsMTsCJsFvPg= Received: by filter1127p1las1.sendgrid.net with SMTP id filter1127p1las1-32176-5B32C48F-2B 2018-06-26 22:56:15.860928159 +0000 UTC Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) by ismtpd0036p1mdw1.sendgrid.net (SG) with ESMTP id urqjW5-iQQStvFtktQq5gw for ; Tue, 26 Jun 2018 22:56:15.563 +0000 (UTC) Date: Tue, 26 Jun 2018 22:56:16 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN Proposal with only two counters (#1460) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c48eb954b_c0a2ad551394f589918"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0INU3DxWjnFO3w1KkmPaLvES0aysf142deNx cTheOwy6GKclu9cw2dtFSo+EEyAAYHUGK1Iu8fy2xHRkhoKXno0G0lpVDvGhj4Ko63c1X61LXMIFUu OO2QCncNKpPZW2qTMhtQJCeTFnqlKjp2+I3CfQhyIkt0loGFQw8hzsH4ycpbOHD5phaN5x3Xj06nUt w= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 22:56:21 -0000 ----==_mimepart_5b32c48eb954b_c0a2ad551394f589918 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1460. -- 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/1460#event-1702650051 ----==_mimepart_5b32c48eb954b_c0a2ad551394f589918 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1460.

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

----==_mimepart_5b32c48eb954b_c0a2ad551394f589918-- From nobody Tue Jun 26 16:00:37 2018 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 0BFE6130E65 for ; Tue, 26 Jun 2018 16:00:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 sqNrdLr9mWkG for ; Tue, 26 Jun 2018 16:00:33 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D416130E5F for ; Tue, 26 Jun 2018 16:00:33 -0700 (PDT) Date: Tue, 26 Jun 2018 16:00:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054032; bh=7/d8r+EdRKEVcfvo9K/h79FiJ9//J9u1CGkjhI9PRxg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VNP69GRBwkAVwXEX4i2dqDeOIar//a+ysg7XFp+M9aCPuhDnzeGkbQ+TnKDn5FBbW R0rU9mwQXuRsZgAsCfrtxivGiO+UoKMtTp7DUmBJjDyhumEYqOZZoZA0xfqz8M0yhV h5H4ILI/xPRoXzwH2nJnccS0zbeIJ/jASABh1Iko= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retry Token Makeup (#1474) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c590b9a08_5c73fe6d9fe0f8821652b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:00:36 -0000 ----==_mimepart_5b32c590b9a08_5c73fe6d9fe0f8821652b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My thought would be a token that is carried in a Retry would be bound strongly to the connection ID. It's very different to NEW_TOKEN in that way. -- 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/1474#issuecomment-400489654 ----==_mimepart_5b32c590b9a08_5c73fe6d9fe0f8821652b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

My thought would be a token that is carried in a Retry would be bound strongly to the connection ID. It's very different to NEW_TOKEN in that way.

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

----==_mimepart_5b32c590b9a08_5c73fe6d9fe0f8821652b-- From nobody Tue Jun 26 16:01:40 2018 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 7E351130F0F for ; Tue, 26 Jun 2018 16:01:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 6ViOYcY6WGep for ; Tue, 26 Jun 2018 16:01:37 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15EBF130E5F for ; Tue, 26 Jun 2018 16:01:37 -0700 (PDT) Date: Tue, 26 Jun 2018 16:01:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054096; bh=9zs8K+Sif6+a9qtYc8yjX59WhqB9lba/Uh3Q1P1GszQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=goGmoXgo8gq/qorEXjcS8uF5vW5r/82LoW3DBL6teZtJXWah4+J9tKjfmH0ODmbi3 8Mds8CBQZy0FF+8A/pabQUNogqTewTbpfx4PHmP3g37GpS/z/AJGDLIOH/s/gknq97 IRu9WqVCd25Ex6Fr80ELLusJCmMrSRqdaiVzn2L4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c5d077533_2a993fbb4ace0f78570e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:01:39 -0000 ----==_mimepart_5b32c5d077533_2a993fbb4ace0f78570e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's in the AAD. What else are you concerned about? -- 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/1479#issuecomment-400489814 ----==_mimepart_5b32c5d077533_2a993fbb4ace0f78570e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It's in the AAD. What else are you concerned about?

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

----==_mimepart_5b32c5d077533_2a993fbb4ace0f78570e-- From nobody Tue Jun 26 16:06:10 2018 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 8D526130EF1 for ; Tue, 26 Jun 2018 16:06:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 wp8BBDMlcQZK for ; Tue, 26 Jun 2018 16:06:08 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11434130E5A for ; Tue, 26 Jun 2018 16:06:08 -0700 (PDT) Date: Tue, 26 Jun 2018 16:06:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054367; bh=yCHRdK02IAhTtBYdwMp4YS55k4GTG3KJND5KirxpG2Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Y3qEvyU1JiTzhiawW4E+BJg2QWtxAkyUhy4sWY3J8H/3kfnE9aZDqX3xOi4ofttKX eYik5mNIeWfhyQ69DsaEwGtIrCoZthjrHHo9WOGbDRhJ/xTEj3pNLMfJycojg1jv9b iE4m7XAcARosnDIo4zYJuM0MNP82HgFeDa3P9jZ8= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c6df685e9_2c62ad551394f5824475e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:06:10 -0000 ----==_mimepart_5b32c6df685e9_2c62ad551394f5824475e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit janaiyengar approved this pull request. -- 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/1473#pullrequestreview-132236004 ----==_mimepart_5b32c6df685e9_2c62ad551394f5824475e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@janaiyengar approved this pull request.

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

----==_mimepart_5b32c6df685e9_2c62ad551394f5824475e-- From nobody Tue Jun 26 16:07:32 2018 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 3CBF5130EF1 for ; Tue, 26 Jun 2018 16:07:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 aSArHarQjg9l for ; Tue, 26 Jun 2018 16:07:28 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 CB75C130E5A for ; Tue, 26 Jun 2018 16:07:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530054447; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9m9mKYhdLllBZLkt0l7jzzK7z990FHqsmoJz8/AtiqU=; b=NMgAixwuUhtqkCRQzCwIyPktA5NbWJCKRJ1A7ounxZyHAprldfVbpWnkrNVBuBhSGmB3Z/+Z NcPIx7HzI2yfdk7z8qXkCDWnNJIXAaLoBVuzmZoBkvSYOOCuob2JVBmUCS1oAAodgGNniw7B s8jrNt5OPQPyNev/KN6mcdf/Fto= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b32c72f.7ffb24f53f00-smtp-out-n02; Tue, 26 Jun 2018 23:07:27 -0000 (UTC) Date: Tue, 26 Jun 2018 16:07:26 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c72e201ea_358f2ad815f75c0c376f@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d4ec8a: comma splice Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c72e1fb64_358f2ad815f75c0c375c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:07:30 -0000 ----==_mimepart_5b32c72e1fb64_358f2ad815f75c0c375c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts Commit: d4ec8a52378b5b2862bb9fca3e48a7305749e06e https://github.com/quicwg/base-drafts/commit/d4ec8a52378b5b2862bb9fca3e48a7305749e06e Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- comma splice **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c72e1fb64_358f2ad815f75c0c375c5-- From nobody Tue Jun 26 16:07:38 2018 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 4AC04130E5A for ; Tue, 26 Jun 2018 16:07:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Juz2xaX_AysH for ; Tue, 26 Jun 2018 16:07:30 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2D20130E5F for ; Tue, 26 Jun 2018 16:07:29 -0700 (PDT) Date: Tue, 26 Jun 2018 16:07:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054449; bh=WJqLk9dE20OcRr5DGhfq3ZShzOd3lI91Qz83s3EOtXI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XxwILD7+C61DM3+vR+ug8Fn3l0Kulz8R+qfT8dtJhUuGaEnxKQbNGvetDdwVgKMqG iGMgwznhKJZimvhJI12ovYdva4WwFHDlbO2Eg5P3MCa//Ml0AjR8NxwBzRzfsQBWVk jJFyczaNOC5/ruJeesnUn4WG4G0jFCmtwQMKRraQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c7315d667_2f0c2b14bfa18f5c1532dc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 23:07:31 -0000 ----==_mimepart_5b32c7315d667_2f0c2b14bfa18f5c1532dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. d4ec8a5 comma splice -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1477/files/d7683479e2bdde11a8763e1964916937e2f33063..d4ec8a52378b5b2862bb9fca3e48a7305749e06e ----==_mimepart_5b32c7315d667_2f0c2b14bfa18f5c1532dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32c7315d667_2f0c2b14bfa18f5c1532dc-- From nobody Tue Jun 26 16:09:16 2018 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 3A7DA130E17 for ; Tue, 26 Jun 2018 16:09:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4GxZMEdytSfE for ; Tue, 26 Jun 2018 16:09:13 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 C6832130E5A for ; Tue, 26 Jun 2018 16:09:12 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530054552; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ZTUtBUasIz5Ev0xWH80S7RwGM/5D7Gr5gb0s/oIWLUI=; b=fB59n1I44xLuDkRzJSy6M4QNSD1s663ZFo7y1saAR6CLux+0HI0R8ex4aZO42jahkC4Kk6vb xa3c9BIggTz+KINotPHxKKmociw3CkSyKgdPOxGcLUc5cgH3iQ3mdGiMTJqlExNLMYCYDwsR Gtv3EeATNptuvD5Dit6AWv8RvOY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b32c797.7f034f15e120-smtp-out-n02; Tue, 26 Jun 2018 23:09:11 -0000 (UTC) Date: Tue, 26 Jun 2018 16:09:11 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c7971d0e2_768d2aabcd553c0c634cb@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 0acc8f: Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c7971c90f_768d2aabcd553c0c633a2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:09:15 -0000 ----==_mimepart_5b32c7971c90f_768d2aabcd553c0c633a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 0acc8f8b945ffc6199492f12fa6d0c5059101175 https://github.com/quicwg/base-drafts/commit/0acc8f8b945ffc6199492f12fa6d0c5059101175 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Commit: 9b80c45f58b43ede57b9876e21df30dfa963f49b https://github.com/quicwg/base-drafts/commit/9b80c45f58b43ede57b9876e21df30dfa963f49b Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- one-octet description; MUST NOT warning alert Commit: a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf https://github.com/quicwg/base-drafts/commit/a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Typos, renumber Commit: d7683479e2bdde11a8763e1964916937e2f33063 https://github.com/quicwg/base-drafts/commit/d7683479e2bdde11a8763e1964916937e2f33063 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- commas Commit: d4ec8a52378b5b2862bb9fca3e48a7305749e06e https://github.com/quicwg/base-drafts/commit/d4ec8a52378b5b2862bb9fca3e48a7305749e06e Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- comma splice Commit: ec383d67809209ec4da40c5f0526df00f5677535 https://github.com/quicwg/base-drafts/commit/ec383d67809209ec4da40c5f0526df00f5677535 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1477 from quicwg/remove-crypto_close Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Compare: https://github.com/quicwg/base-drafts/compare/aca29a5b84be...ec383d678092 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c7971c90f_768d2aabcd553c0c633a2-- From nobody Tue Jun 26 16:09:22 2018 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 EDB46130E17 for ; Tue, 26 Jun 2018 16:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 U-CKxXFT7Wsa for ; Tue, 26 Jun 2018 16:09:14 -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 4707E130E5A for ; Tue, 26 Jun 2018 16:09:14 -0700 (PDT) Date: Tue, 26 Jun 2018 16:09:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054553; bh=el/9Oi4qFKNwW3XQdie8Fp+S1djiTXmLsvsoeFYrd74=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fU028jMqU5IUUQ332kvH9PPCL4sGqvgpEIhdPGVuIYIeVQalSF2huIGb2zUe0ov/f +czoEASUnPSE5WT4+7Z0Li/7NDB00cnwGBSxCjvM9/Xo4S5B044hUCR+6y86PGgBaI uTvxtEsld9L4lv4x0iEogkff7KwQcoBOO9+VEMoU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Use CONNECTION_CLOSE rather than CRYPTO_CLOSE (#1477) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c7999c2f2_52e62ab89a4f2f541411d1"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:09:16 -0000 ----==_mimepart_5b32c7999c2f2_52e62ab89a4f2f541411d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1477. -- 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/1477#event-1702665298 ----==_mimepart_5b32c7999c2f2_52e62ab89a4f2f541411d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1477.

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

----==_mimepart_5b32c7999c2f2_52e62ab89a4f2f541411d1-- From nobody Tue Jun 26 16:10:52 2018 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 57E2E130E5A for ; Tue, 26 Jun 2018 16:10:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 O3QC9XVxc5mH for ; Tue, 26 Jun 2018 16:10:46 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 9D652130E17 for ; Tue, 26 Jun 2018 16:10:46 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530054645; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=tp/hUYmJAoQCmg58QoXk8qYImb2SZlMU2r06N7OmkzE=; b=DIhPnRm8l6Hd1aVUJ/GgxH3kZVGgXUV2Z8OXSn9IXo/NLVxoQ7+HlFi0IITdBxUaJD9vtLzl 7N30ZKXnrtCqAcMhaJgA4fOAAh6nPw0+dFpSnLlzMHIrgIDf2pXgRYG54a599xxDCbDG1WuB 4YC+i6KQa7vO26OmLVw4nsSCsmY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b32c7f4.7fbd0b8faf00-smtp-out-n01; Tue, 26 Jun 2018 23:10:44 -0000 (UTC) Date: Tue, 26 Jun 2018 16:10:43 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c7f3d6c84_26102af679e4bc1457198@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ec94b6: TP to disable migration Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c7f3d623e_26102af679e4bc14570e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:10:50 -0000 ----==_mimepart_5b32c7f3d623e_26102af679e4bc14570e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts Commit: ec94b63b140ea2d92417a6c9c674d10cb1d6f001 https://github.com/quicwg/base-drafts/commit/ec94b63b140ea2d92417a6c9c674d10cb1d6f001 Author: Mike Bishop Date: 2018-06-14 (Thu, 14 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- TP to disable migration Commit: 42f55df78007dab2d02faf837eebed5e864d17ee https://github.com/quicwg/base-drafts/commit/42f55df78007dab2d02faf837eebed5e864d17ee Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Output of Stream 0 Design Team. See: https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit for design rationale. Commit: cab82952ab67bd994da0da4160af42f2e95a9850 https://github.com/quicwg/base-drafts/commit/cab82952ab67bd994da0da4160af42f2e95a9850 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fix changelog Commit: 984ecc86d259d76d8498f3b4990bb5cfdc10c448 https://github.com/quicwg/base-drafts/commit/984ecc86d259d76d8498f3b4990bb5cfdc10c448 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fix whitespace Commit: 36899e50d963d6d7aa427168d45311f444014bdf https://github.com/quicwg/base-drafts/commit/36899e50d963d6d7aa427168d45311f444014bdf Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Offset and length fields in CRYPTO_HS are not optional Commit: f8f172f52889036ddbc697165393194a28073b0d https://github.com/quicwg/base-drafts/commit/f8f172f52889036ddbc697165393194a28073b0d Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Remove EMPTY_ACK Commit: 70b26e8c3ae6b30acbcb9b915eac98e6757d2a5d https://github.com/quicwg/base-drafts/commit/70b26e8c3ae6b30acbcb9b915eac98e6757d2a5d Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md Log Message: ----------- Incorporate the comments from PR#1377 Commit: af70f236548b53a9a7ff69b4e52f850d1a350a57 https://github.com/quicwg/base-drafts/commit/af70f236548b53a9a7ff69b4e52f850d1a350a57 Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove EMPTY_ACK Commit: aa1b6834af8b327ef0ef761b9daede3447504deb https://github.com/quicwg/base-drafts/commit/aa1b6834af8b327ef0ef761b9daede3447504deb Author: ianswett Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Update draft-ietf-quic-transport.md Commit: 927cf128a760708657f3d7ea76ba0495ed60af49 https://github.com/quicwg/base-drafts/commit/927cf128a760708657f3d7ea76ba0495ed60af49 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Add the TLS diagrams Commit: 74300a1be6e84f5deec8dcb513bc370433e1dca3 https://github.com/quicwg/base-drafts/commit/74300a1be6e84f5deec8dcb513bc370433e1dca3 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Redact diagram from the TLS doc Commit: 04fd3213c3873c7f8593a16115b36061421251a3 https://github.com/quicwg/base-drafts/commit/04fd3213c3873c7f8593a16115b36061421251a3 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Ian Swett's comments Commit: bf9c62cb42534d90efc7aae65e16c31b793a75b6 https://github.com/quicwg/base-drafts/commit/bf9c62cb42534d90efc7aae65e16c31b793a75b6 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- server-initiated streams start from 1 Commit: 77155f9f535fddf86c88bd18db0cce32edb66555 https://github.com/quicwg/base-drafts/commit/77155f9f535fddf86c88bd18db0cce32edb66555 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Remove last TODO Commit: 779b3a007bae19afeed9bd32d8f3bc58640f67d2 https://github.com/quicwg/base-drafts/commit/779b3a007bae19afeed9bd32d8f3bc58640f67d2 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Minor editorial Commit: d3b055a6e9afc403a9b0cb2862f09880938b5eb7 https://github.com/quicwg/base-drafts/commit/d3b055a6e9afc403a9b0cb2862f09880938b5eb7 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Remove the advice on how to use coalesced packets for recovery. This may be re-added in a future PR, but isn't part of the minimal set for the stream 0 DT. Commit: 48c9b9fde954d6a8b3a52e5ee7006fffd0c8a6ca https://github.com/quicwg/base-drafts/commit/48c9b9fde954d6a8b3a52e5ee7006fffd0c8a6ca Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Self-review, ready to submit Commit: 396c318dabd73952ee44b4bf1826aa28ebd19d8b https://github.com/quicwg/base-drafts/commit/396c318dabd73952ee44b4bf1826aa28ebd19d8b Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Some more cleanup Commit: 777114ac355c7a4b15dabd67122ca21c164e2e17 https://github.com/quicwg/base-drafts/commit/777114ac355c7a4b15dabd67122ca21c164e2e17 Author: EKR Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Fix compile errors Commit: b789dd84f3b9dbd0182f8b674411368824afb22b https://github.com/quicwg/base-drafts/commit/b789dd84f3b9dbd0182f8b674411368824afb22b Author: Mike Bishop Date: 2018-06-15 (Fri, 15 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- local address Commit: a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835 https://github.com/quicwg/base-drafts/commit/a4ad49b42d9c6e7f86b1127cc4291f70d5fbe835 Author: ianswett Date: 2018-06-18 (Mon, 18 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Restore Generating Acknowledgements Commit: 6b363007d1875ffb02cf6f0c9006696c72a2cd0b https://github.com/quicwg/base-drafts/commit/6b363007d1875ffb02cf6f0c9006696c72a2cd0b Author: ianswett Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Mike's comments Commit: 0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d https://github.com/quicwg/base-drafts/commit/0cfdf67b77f7f52a0fd3cec28064f4c87d9cde7d Author: ekr Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #34 from ekr/ianswett-mike-comments Mike's comments Commit: 4065266b5a01d982ec01050305247d342e8cdff7 https://github.com/quicwg/base-drafts/commit/4065266b5a01d982ec01050305247d342e8cdff7 Author: ianswett Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fix retry and remove optimizations Commit: 954c585e680ca4bf8e2e18af57e5832b716d9fb7 https://github.com/quicwg/base-drafts/commit/954c585e680ca4bf8e2e18af57e5832b716d9fb7 Author: ekr Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #35 from ekr/ianswett-mike2 Fix retry and remove optimizations Commit: f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b https://github.com/quicwg/base-drafts/commit/f94df3aed2d9ebe2a41dfd7d0f1fe354be103b5b Author: Mike Bishop Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Bilateral, error Commit: d814642dec0176287f81ac2b0391aa7d541850c8 https://github.com/quicwg/base-drafts/commit/d814642dec0176287f81ac2b0391aa7d541850c8 Author: ianswett Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Martin's comments Commit: da0d8ecff5905d4321db902c2df6a51846791fec https://github.com/quicwg/base-drafts/commit/da0d8ecff5905d4321db902c2df6a51846791fec Author: ianswett Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Ensures that Commit: 89c45a658dc9cfe765d1252050f7874fe27bfd2f https://github.com/quicwg/base-drafts/commit/89c45a658dc9cfe765d1252050f7874fe27bfd2f Author: ekr Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #36 from ekr/ianswett-martin Martin's comments Commit: daea8615f43545e42fda486d92b5ac6c4218e760 https://github.com/quicwg/base-drafts/commit/daea8615f43545e42fda486d92b5ac6c4218e760 Author: EKR Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Address MT's comments on TLS Commit: 3aea50db51a14f2b42ed8aea7dbeeea72c6321b4 https://github.com/quicwg/base-drafts/commit/3aea50db51a14f2b42ed8aea7dbeeea72c6321b4 Author: EKR Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- MT/Bishop comments on transport Commit: bd5f9ff36dd1fc11a14f8fccd7ff144482ed356f https://github.com/quicwg/base-drafts/commit/bd5f9ff36dd1fc11a14f8fccd7ff144482ed356f Author: EKR Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Ian's comments Commit: e2ed4db7df7d72a08fe13b8da8d17f6fca601c26 https://github.com/quicwg/base-drafts/commit/e2ed4db7df7d72a08fe13b8da8d17f6fca601c26 Author: ekr Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #37 from ekr/martins_comments Martins comments Commit: 9cb100067a0c892b68a8ca5156fadc22f5365932 https://github.com/quicwg/base-drafts/commit/9cb100067a0c892b68a8ca5156fadc22f5365932 Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Discuss rebinding briefly Commit: 7a780dbed8eed8ed9584db89215bd752dbf86c7a https://github.com/quicwg/base-drafts/commit/7a780dbed8eed8ed9584db89215bd752dbf86c7a Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Fix build breaks Commit: 4db556887313b51de0139bb7c6c7be33614c4ddb https://github.com/quicwg/base-drafts/commit/4db556887313b51de0139bb7c6c7be33614c4ddb Author: Mike Bishop Date: 2018-06-22 (Fri, 22 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Extra word Commit: 8d57711c819307c44cec8db2964a2a80c8f87ab9 https://github.com/quicwg/base-drafts/commit/8d57711c819307c44cec8db2964a2a80c8f87ab9 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- remove "the the" Commit: a2aabfe9e6feec0eaab59af0f4a0c212190b4474 https://github.com/quicwg/base-drafts/commit/a2aabfe9e6feec0eaab59af0f4a0c212190b4474 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- More errors around delivering to TLS out of order Commit: 2473966033d8f2d75a37113e723d05be42b20f38 https://github.com/quicwg/base-drafts/commit/2473966033d8f2d75a37113e723d05be42b20f38 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- The online editor is terrible Commit: ba809b106bac23ecf8b83e080c0e17f6814907f4 https://github.com/quicwg/base-drafts/commit/ba809b106bac23ecf8b83e080c0e17f6814907f4 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1450 from ekr/stream0_dt_output_for_merge Stream0 dt output for merge Commit: 5f438af3c17cbd1f908f1806d33d58c340287cfa https://github.com/quicwg/base-drafts/commit/5f438af3c17cbd1f908f1806d33d58c340287cfa Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M .circleci/config.yml Log Message: ----------- Defer artifact saving Commit: 0acc8f8b945ffc6199492f12fa6d0c5059101175 https://github.com/quicwg/base-drafts/commit/0acc8f8b945ffc6199492f12fa6d0c5059101175 Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Commit: 9b80c45f58b43ede57b9876e21df30dfa963f49b https://github.com/quicwg/base-drafts/commit/9b80c45f58b43ede57b9876e21df30dfa963f49b Author: Martin Thomson Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- one-octet description; MUST NOT warning alert Commit: 7583103bc5070b5e02a29b8546eaee06f5524277 https://github.com/quicwg/base-drafts/commit/7583103bc5070b5e02a29b8546eaee06f5524277 Author: afrind Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Modify codepoints on decoder and request/push streams for consistency (#1472) * Modify codepoints on decoder and request/push streams for consistency The prefix lengths remain the same but the instruction bits now follow the rule that each instruction has at most one '1' bit. Fixes #1471 * Swap TSS and Stream Cancellation codepoints This is somewhat superficial, but we're changing it anyways so bear with me. HEADER_ACK and STREAM_CANCEL are almost identical, so code processing them should be next to each other. By swapping TSS and Stream Cancel codepoints, the processing code might be more readable. Commit: e1aa62531825699ae815534096dda6d99a9bf9ae https://github.com/quicwg/base-drafts/commit/e1aa62531825699ae815534096dda6d99a9bf9ae Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Revert "Remove sequence number from NEW_CONNECTION_ID" This reverts commit 2eee0d82ee9557a79a888dcf4097ce0c8e70ece6. Commit: 7d7850061e3d7fe01b1b31551f1689cce5f2464a https://github.com/quicwg/base-drafts/commit/7d7850061e3d7fe01b1b31551f1689cce5f2464a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Require CID sequence number ratcheting Commit: fdc9651e19cdd1ed794f66a44c01f800651d3a1a https://github.com/quicwg/base-drafts/commit/fdc9651e19cdd1ed794f66a44c01f800651d3a1a Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Prefer equality Commit: 26a3a1f06d21b858814b5f71f8c96d457edce61f https://github.com/quicwg/base-drafts/commit/26a3a1f06d21b858814b5f71f8c96d457edce61f Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Nick's reword Commit: c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 https://github.com/quicwg/base-drafts/commit/c8f0c8c438d080b4a3d2e21b7cdf1e82eb0ea7d4 Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- New CID section Commit: 32c8bc1477966608fd5e7015317cd2887e8553ab https://github.com/quicwg/base-drafts/commit/32c8bc1477966608fd5e7015317cd2887e8553ab Author: Mike Bishop Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Additional recommendations Commit: 61e932dbeac2e70d603010d9596552a5f057b253 https://github.com/quicwg/base-drafts/commit/61e932dbeac2e70d603010d9596552a5f057b253 Author: ianswett Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Replace default with recommended (#1480) * Replace default with recommended Fixes #1475 * RECOMMENDED Commit: e2ec1807626a1b62e8494e82971083f3248dcc2c https://github.com/quicwg/base-drafts/commit/e2ec1807626a1b62e8494e82971083f3248dcc2c Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Grease values in HTTP/QUIC (#1446) * Import grease recommendations * HTTP/QUIC doesn't give settings initial values * Martin's feedback * Grease section header Commit: e08e13e564939c3ed9621a695dcd3b2ddd4b3bb1 https://github.com/quicwg/base-drafts/commit/e08e13e564939c3ed9621a695dcd3b2ddd4b3bb1 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1465 from quicwg/transport/ratchet_precision Restore CID sequence numbers Commit: ac5aadba7f3e85375229e11867af504dfc868807 https://github.com/quicwg/base-drafts/commit/ac5aadba7f3e85375229e11867af504dfc868807 Author: afrind Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Define the contents of QPACK Encoder and Decoder streams (#1467) Fixes #1361 This removes the length prefixed instruction blocks on the encoder stream and replaces them with an unframed sequence of instructions. Commit: 1d6b6f1dd76829b9010b8599383f0e2c6312d5c8 https://github.com/quicwg/base-drafts/commit/1d6b6f1dd76829b9010b8599383f0e2c6312d5c8 Author: Jana Iyengar Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- typo Commit: a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf https://github.com/quicwg/base-drafts/commit/a77b0669f52aaa155dc6fb15f97d3aaf0237a8bf Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Typos, renumber Commit: d7683479e2bdde11a8763e1964916937e2f33063 https://github.com/quicwg/base-drafts/commit/d7683479e2bdde11a8763e1964916937e2f33063 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- commas Commit: aca29a5b84be32cd672a1871254812357c4ff9fd https://github.com/quicwg/base-drafts/commit/aca29a5b84be32cd672a1871254812357c4ff9fd Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1447 from quicwg/transport/disable_migration TP to disable migration Commit: d4ec8a52378b5b2862bb9fca3e48a7305749e06e https://github.com/quicwg/base-drafts/commit/d4ec8a52378b5b2862bb9fca3e48a7305749e06e Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- comma splice Commit: ec383d67809209ec4da40c5f0526df00f5677535 https://github.com/quicwg/base-drafts/commit/ec383d67809209ec4da40c5f0526df00f5677535 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1477 from quicwg/remove-crypto_close Use CONNECTION_CLOSE rather than CRYPTO_CLOSE Commit: fdcc44c610cdd2897774718cc0af2532800157e7 https://github.com/quicwg/base-drafts/commit/fdcc44c610cdd2897774718cc0af2532800157e7 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M .circleci/config.yml M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'master' into extend-frames Compare: https://github.com/quicwg/base-drafts/compare/09b7e945e7aa...fdcc44c610cd **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c7f3d623e_26102af679e4bc14570e6-- From nobody Tue Jun 26 16:10:58 2018 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 0686B130E5A for ; Tue, 26 Jun 2018 16:10:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 h9P6oPQtV9rI for ; Tue, 26 Jun 2018 16:10:50 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A46B130E17 for ; Tue, 26 Jun 2018 16:10:50 -0700 (PDT) Date: Tue, 26 Jun 2018 16:10:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054649; bh=v8K9O3Tr2EIMwWDyJA1UwIafsqvsFofn4Rzp684znCk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bpP6aQFmkzVIN09t3XHF6ddqsy+q2gAaQTwPuJNbKK6TBHde5KO+Aub2vZMFG2erY YcdsW6M/sWZ9amMH+s1v85IKg23LNatfGctDXGi5rKSYQCcuRE5KKFWe9+UJosORXN Mp9tYHpTrOU7/U/TRYWlk9+LfQHFXzOb/r09qO7Q= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c7f9cc897_4e8a3fcf68218f782873f1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Tue, 26 Jun 2018 23:10:53 -0000 ----==_mimepart_5b32c7f9cc897_4e8a3fcf68218f782873f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. fdcc44c Merge branch 'master' into extend-frames -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1473/files/09b7e945e7aaa909144651f9c7411a5f8dd774e7..fdcc44c610cdd2897774718cc0af2532800157e7 ----==_mimepart_5b32c7f9cc897_4e8a3fcf68218f782873f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • fdcc44c Merge branch 'master' into extend-frames

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32c7f9cc897_4e8a3fcf68218f782873f1-- From nobody Tue Jun 26 16:11:04 2018 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 25C75130E17 for ; Tue, 26 Jun 2018 16:10:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 GnroPR_s_QmS for ; Tue, 26 Jun 2018 16:10:54 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 A1C5D130E61 for ; Tue, 26 Jun 2018 16:10:54 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530054654; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=VtyBWP4evBh5OYTRFIprbd8SqfvzPf3tNiaKVecBL54=; b=I92G6H3ANuQ4BGWz2D7aVNfgFi1CD6Pecnakn1FPItIOXpKdL8RNMDFcLGvO+iqw+tDhvZGE rJeDucPKMyIEZXkFYybm56DIBZRh4IQ8EWeGDdw5+I/+MhYiL3Bfj53uxW/Gats8n+pTZ7gy jJNZmTx7LZNqzDu5VbdGeoU5KSE= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b32c7fd.7f20d64cdd80-smtp-out-n02; Tue, 26 Jun 2018 23:10:53 -0000 (UTC) Date: Tue, 26 Jun 2018 16:10:53 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32c7fdd068c_b032ac3f336fc1896329@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e4725a: Extension frames Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c7fdd00d7_b032ac3f336fc189625"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:10:56 -0000 ----==_mimepart_5b32c7fdd00d7_b032ac3f336fc189625 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: e4725aca6943b04e1ef7f347a0fea5ade6313741 https://github.com/quicwg/base-drafts/commit/e4725aca6943b04e1ef7f347a0fea5ade6313741 Author: Martin Thomson Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Extension frames Closes #58, #1072, #1068. Commit: 81e10cc2c71804fdd8945244381510c63df3c257 https://github.com/quicwg/base-drafts/commit/81e10cc2c71804fdd8945244381510c63df3c257 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- PROTOCOL_VIOLATION for bad frame type Commit: 89c0aefc2371a872e8de519346c225c1e0fc17e0 https://github.com/quicwg/base-drafts/commit/89c0aefc2371a872e8de519346c225c1e0fc17e0 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- WIP Commit: 6fa28c2172d549f036ca97ab6cf981c7162f2660 https://github.com/quicwg/base-drafts/commit/6fa28c2172d549f036ca97ab6cf981c7162f2660 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- reflow Commit: 09b7e945e7aaa909144651f9c7411a5f8dd774e7 https://github.com/quicwg/base-drafts/commit/09b7e945e7aaa909144651f9c7411a5f8dd774e7 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Simplify Commit: fdcc44c610cdd2897774718cc0af2532800157e7 https://github.com/quicwg/base-drafts/commit/fdcc44c610cdd2897774718cc0af2532800157e7 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M .circleci/config.yml M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'master' into extend-frames Commit: 4b3735c83221a043b27317f2d2de7c322bb3c396 https://github.com/quicwg/base-drafts/commit/4b3735c83221a043b27317f2d2de7c322bb3c396 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1473 from quicwg/extend-frames Extension frames Compare: https://github.com/quicwg/base-drafts/compare/ec383d678092...4b3735c83221 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c7fdd00d7_b032ac3f336fc189625-- From nobody Tue Jun 26 16:11:15 2018 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 3F0D2130E17 for ; Tue, 26 Jun 2018 16:11:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 wWh7-OCGJsKN for ; Tue, 26 Jun 2018 16:10:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC04B130E5A for ; Tue, 26 Jun 2018 16:10:56 -0700 (PDT) Date: Tue, 26 Jun 2018 16:10:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054656; bh=OsgQ+4n1dSM08oj6rYQVIAd31EoFPi9dczRRApu+tCo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kWt2EOVeB7Wh3vIf9IS38d4t3Rcv2r2FX5BjIHp96CH4aMGyFvThB59ysRTIC4aRh 6LN88DEf28Of3jRTyqqbCBhPVaMBxgZznACCHxAl90/b27QctyscVqf1jMWG6w+49Q wvzpQkNs5rr9TNLDS5G4HPttUe2mci8+RB4RMcHE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Frame type extensions (#58) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c8007b58_227d3f8a87e18f88202790"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:11:08 -0000 ----==_mimepart_5b32c8007b58_227d3f8a87e18f88202790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #58 via #1473. -- 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/58#event-1702667309 ----==_mimepart_5b32c8007b58_227d3f8a87e18f88202790 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #58 via #1473.

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

----==_mimepart_5b32c8007b58_227d3f8a87e18f88202790-- From nobody Tue Jun 26 16:11:20 2018 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 13933130E68 for ; Tue, 26 Jun 2018 16:11:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 LCkH7C9C_k4h for ; Tue, 26 Jun 2018 16:10:57 -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 BF8AF130E61 for ; Tue, 26 Jun 2018 16:10:56 -0700 (PDT) Date: Tue, 26 Jun 2018 16:10:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054656; bh=j9udeVcfgrJXqx9coopwY52G0Y9IMr60+s7UPaVL4Hs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JfUi3M4BPiAG63L/Gl7jcacY33HR4Xer49kg0NXJE2oOO/n5M8NKnTxNaBN/+Wdtq 1//uog3I8UWPPZTrqPaQvLQ97D3klN2Wq+3ZBMu/aPBwIVCbdrwmeUKTzkPLdApiAb E7SQRZppasV0VbVfIWrVPjAzcXoKShrGoYivKtTc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Extension frames (#1473) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c8001bc76_afd3fe2f70c2f782868ae"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:11:09 -0000 ----==_mimepart_5b32c8001bc76_afd3fe2f70c2f782868ae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1473. -- 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/1473#event-1702667304 ----==_mimepart_5b32c8001bc76_afd3fe2f70c2f782868ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1473.

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

----==_mimepart_5b32c8001bc76_afd3fe2f70c2f782868ae-- From nobody Tue Jun 26 16:14:18 2018 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 B77A9130E61 for ; Tue, 26 Jun 2018 16:14:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hjJHBsQhsiPO for ; Tue, 26 Jun 2018 16:14:14 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BCC1130E17 for ; Tue, 26 Jun 2018 16:14:14 -0700 (PDT) Date: Tue, 26 Jun 2018 16:14:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530054853; bh=GpnOhtAfWBVlwkkU/HGxgTUhWnBTYxdnjUlSl9cU+mo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dfI8ECljzUNL0W85hjL2nqcvtNNhQyDVt58+4VJ5mMldkhF8IqU+ULR//mOa91WOk VMPilnsqObkN4+yJZ+JvZ2S42gzYg3IwFPwO19TbVXrzZX3Bippv/szAz6YxDh8wPV TEEN7P/np3YIWiEW8hu4wtZCAUXyw9izvqlFT+A8= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32c8c5b3566_1c993f963fc02f78421195"; 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.26 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: Tue, 26 Jun 2018 23:14:16 -0000 ----==_mimepart_5b32c8c5b3566_1c993f963fc02f78421195 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The AAD encrypted with a key that anyone who knows the version of QUIC can derive. I think the suggestion is that, like VN, the initial DCID should be included in the transport parameters so it can be validated at the end of the handshake to confirm there was no tampering. -- 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/1479#issuecomment-400492023 ----==_mimepart_5b32c8c5b3566_1c993f963fc02f78421195 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The AAD encrypted with a key that anyone who knows the version of QUIC can derive. I think the suggestion is that, like VN, the initial DCID should be included in the transport parameters so it can be validated at the end of the handshake to confirm there was no tampering.

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

----==_mimepart_5b32c8c5b3566_1c993f963fc02f78421195-- From nobody Tue Jun 26 16:19:30 2018 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 3D6B8131167 for ; Tue, 26 Jun 2018 16:19:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 fDmXYJoBs1E2 for ; Tue, 26 Jun 2018 16:19:14 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 C1C53131162 for ; Tue, 26 Jun 2018 16:19:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530055154; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=b0R+pdOCmWMP/U06Rqm+xEoWTvOxE8Nf1/JmhEjmlts=; b=mD3vALcbe7Rk57vAgciHqf6eBudVZ9p/joAtPW+qNZWBjuukADpZ0X9mIjeJn9sciDDo+aj6 Ypai0b9rc8WMZeAOxmRxLHfqha7b4fAhMOzPgPnAgQQM3wf1t7tHV36VjEeLeouAvxkmg3gx adULJAui/QgjSBhc+mg8w/jm2+U= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b32c79a.7f722f743d20-smtp-out-n03; Tue, 26 Jun 2018 23:09:14 -0000 (UTC) Date: Tue, 26 Jun 2018 16:09:13 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32c799ef215_e6a2abce6891c1474b5@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32c799eee94_e6a2abce6891c147382"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:19:30 -0000 ----==_mimepart_5b32c799eee94_e6a2abce6891c147382 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/remove-crypto_close Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32c799eee94_e6a2abce6891c147382-- From nobody Tue Jun 26 16:24:36 2018 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 2D90E13113A for ; Tue, 26 Jun 2018 16:24:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 t_EiyoCIJRZP for ; Tue, 26 Jun 2018 16:24:21 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B9B5131140 for ; Tue, 26 Jun 2018 16:24:21 -0700 (PDT) Date: Tue, 26 Jun 2018 16:24:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530055460; bh=ZGJ4GIMLf1JZ2X4WsZCG6txO4ANdKo5yMxeSnmiUbdw=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=w1nCAXFjxD5DYySCvBw07guMcu9CCqeQw07jbhWqi+czadIKBPdY7bZ+h8Fx3okPu t1dOvdcylDKpy5sejsT/ECrtu6EkXffIHtNEBIHViBkUPP1xrOKmXieuoT7av9JcJG JUSswTpdHa6Js6JygdLt4J2zEix9UWpMF9l6uusw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Connection ID Sequence Number and Server's Preferred Address (#1483) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cb24c4dac_3b8c2b274d418f5811525"; 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.26 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: Tue, 26 Jun 2018 23:24:34 -0000 ----==_mimepart_5b32cb24c4dac_3b8c2b274d418f5811525 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Follow-on issue from #1465. The existing text (restored but not changed by the PR) defines the CID selected during the handshake to be Sequence -1, and the CIDs issued via NCID frame to begin at zero. However, the CID issued by the server as part of the Server's Preferred Address doesn't have a suggested sequence number. If we follow a similar convention and assign it an implicit negative number (e.g. handshake becomes -2, SPA gets -1), that introduces another quirk: With the existing language, the server will answer with a new connection ID (say, 0) which will immediately force the client into a connection ID rotation anyway. Possible solutions include: - Not including a CID with the SPA parameter; client needs to wait for (and server needs to send) a NCID frame before the probe/transition has happened. - Server includes a sequence number in the SPA parameter and treats it like any other sequence number it has issued (but then why should the client be required to use that particular CID?) - SPA is implicitly sequence number zero, and server can use the client's sequence number zero in response -- 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/1483 ----==_mimepart_5b32cb24c4dac_3b8c2b274d418f5811525 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Follow-on issue from #1465. The existing text (restored but not changed by the PR) defines the CID selected during the handshake to be Sequence -1, and the CIDs issued via NCID frame to begin at zero.

However, the CID issued by the server as part of the Server's Preferred Address doesn't have a suggested sequence number. If we follow a similar convention and assign it an implicit negative number (e.g. handshake becomes -2, SPA gets -1), that introduces another quirk: With the existing language, the server will answer with a new connection ID (say, 0) which will immediately force the client into a connection ID rotation anyway.

Possible solutions include:

  • Not including a CID with the SPA parameter; client needs to wait for (and server needs to send) a NCID frame before the probe/transition has happened.
  • Server includes a sequence number in the SPA parameter and treats it like any other sequence number it has issued (but then why should the client be required to use that particular CID?)
  • SPA is implicitly sequence number zero, and server can use the client's sequence number zero in response

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

----==_mimepart_5b32cb24c4dac_3b8c2b274d418f5811525-- From nobody Tue Jun 26 16:24:41 2018 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 2D62F131148 for ; Tue, 26 Jun 2018 16:24:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 qq-nQrpFBjFC for ; Tue, 26 Jun 2018 16:24:21 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67A18130F1D for ; Tue, 26 Jun 2018 16:24:21 -0700 (PDT) Date: Tue, 26 Jun 2018 16:24:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530055460; bh=ft4jgqbMAcObRWUzsNtGL1zQ6WXK9Gu/JZDIgpdVEaQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eJPrFpizseR9QFRLJaEXwRL49/Oqdtb+RUKu+rRC0l+qNNTMatMdPujSqShRIE117 GKRsuZuRygm5DcQLsCK+KfCm0rdJXsg9hnfdxfeWQUZbn9/9wDC6WtgO7ZKyuVv0sk 2NrsAY9ijxiKhU4FsPGH1e9ZCuwhG4gFLwlKKkcc= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cb24b8999_18013fe812d3ef8479647"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Tue, 26 Jun 2018 23:24:34 -0000 ----==_mimepart_5b32cb24b8999_18013fe812d3ef8479647 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What is the harm in a middle box (maybe a load balancer?) changing the CID? -- 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/1479#issuecomment-400493832 ----==_mimepart_5b32cb24b8999_18013fe812d3ef8479647 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

What is the harm in a middle box (maybe a load balancer?) changing the CID?

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

----==_mimepart_5b32cb24b8999_18013fe812d3ef8479647-- From nobody Tue Jun 26 16:24:59 2018 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 A7036130E69 for ; Tue, 26 Jun 2018 16:24:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Q90Zn1ldIeuy for ; Tue, 26 Jun 2018 16:24:56 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B18D130E5E for ; Tue, 26 Jun 2018 16:24:56 -0700 (PDT) Date: Tue, 26 Jun 2018 16:24:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530055495; bh=c+o6pmLXGPXShjXCFDwn9ecbEsok2IuqJXMVzQIwLak=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d6X2I9aQKwbTtk/ugsueN9IxieUtpt7IFPrliKYNAq3/QBP6S2RIUVcran4B2FdGb +HOyZfGK0bUwRCNIVr+kJsrmvwkQAz3LC5bUeT1hdjZYsB29zAv2/Et7/LGOwRVe2x ek4lrGq70NiC8Q6bLRodcShVQuO5Akoki4nV29AA= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add a MESSAGE frame optimized for sub-MTU payloads (#814) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cb4794c58_59d13f9953f7ef7885438"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:24:58 -0000 ----==_mimepart_5b32cb4794c58_59d13f9953f7ef7885438 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'd like to see this to support something I've been cooking up. However, = it would be good to understand if it is still classed as v2. (version doesn'= t affect my interest, more my timeline) On Tue, Jun 26, 2018 at 11:53 PM ianswett wrot= e: > Now that we have an extension mechanism, this is an excellent candidate= . > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = 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/814#issuecomment-400493934= ----==_mimepart_5b32cb4794c58_59d13f9953f7ef7885438 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'd like to see this to support something I've been cooking up. H= owever, it
would be good to understand if it is still classed as v2. (version doesn&= #39;t
affect my interest, more my timeline)

On Tue, Jun 26, 2018 at 11:53 PM ianswett <notifications@github.com>= ; wrote:

> Now that we have an extension mechanism, this is an excellent candid= ate.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/814#issuecomment-40= 0488500>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGRFtfSHAsvmUw= X8iQvqJf4nOQ-sGH3rks5uAruHgaJpZM4PqF_2>
> .
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, = or mute the thread.3D""

= ----==_mimepart_5b32cb4794c58_59d13f9953f7ef7885438-- From nobody Tue Jun 26 16:26:20 2018 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 95F56130E69 for ; Tue, 26 Jun 2018 16:26:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 33NH2L20ZyzB for ; Tue, 26 Jun 2018 16:26:17 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 123A7130E5E for ; Tue, 26 Jun 2018 16:26:17 -0700 (PDT) Date: Tue, 26 Jun 2018 16:26:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530055576; bh=/I/p8fIPeaza5SV0cZT/L8OpdXjuh7xmrhjvJIpnIDk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=V3+0h8VrSwSg5fdNQ6hSON/4oMdVJptSG0+pEnlswW44eCcPST+zz4VXIuE0Ipv5h rQlxSbNNUO1ccKNSwR7MukN1RA8XZ/ESNyeSlytUHmJK35zv2nBGRJ3YZDETJ3IK2b X8lCapv/QjbmQtYUHYihM+C4CdIjB2ueedFlwEDQ= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cb97f157a_5dc02b27f1e2af60191ac"; 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.26 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: Tue, 26 Jun 2018 23:26:19 -0000 ----==_mimepart_5b32cb97f157a_5dc02b27f1e2af60191ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Follow-on issue from #1465. The existing text (restored but not changed by the PR) defines the CID selected during the handshake to be Sequence -1, and the CIDs issued via NCID frame to begin at zero. @nibanks objects to having negative sequence numbers. We could, of course, make the handshake-negotiated CID be number zero, but then NCID with a sequence of zero would either be invalid or pointless. Arguments for/against, or alternative solutions? -- 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/1484 ----==_mimepart_5b32cb97f157a_5dc02b27f1e2af60191ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Follow-on issue from #1465. The existing text (restored but not changed by the PR) defines the CID selected during the handshake to be Sequence -1, and the CIDs issued via NCID frame to begin at zero.

@nibanks objects to having negative sequence numbers. We could, of course, make the handshake-negotiated CID be number zero, but then NCID with a sequence of zero would either be invalid or pointless.

Arguments for/against, or alternative solutions?

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

----==_mimepart_5b32cb97f157a_5dc02b27f1e2af60191ac-- From nobody Tue Jun 26 16:28:16 2018 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 CA5D7130E6C for ; Tue, 26 Jun 2018 16:28:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 2T-BjacTijvg for ; Tue, 26 Jun 2018 16:28:13 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 372FC130E69 for ; Tue, 26 Jun 2018 16:28:13 -0700 (PDT) Date: Tue, 26 Jun 2018 16:28:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530055692; bh=LwgEV2txKsNgL7jn1xmDh5k5WKNjflA5MmxGLzA8tr0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wpl4e0uLl1IG13TZB6gdHuuJys0goUwDCzmvhZZat+iKecZJV7vQg/zooT48qnN9g p9B0RmOGu0TS0taEulEHybHKCcnPbV9bUuAjh8CrTTQ7mnouvKTTYRfYnm43KfKf7I frG3WB9tagENvLooQUSbVUPokdVvDm8IkiZb1n44= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add a MESSAGE frame optimized for sub-MTU payloads (#814) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cc0c6661b_33e52ad12f4def6061127"; 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.26 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: Tue, 26 Jun 2018 23:28:15 -0000 ----==_mimepart_5b32cc0c6661b_33e52ad12f4def6061127 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Work with @ianswett and write a draft? -- 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/814#issuecomment-400494478 ----==_mimepart_5b32cc0c6661b_33e52ad12f4def6061127 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Work with @ianswett and write a draft?

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

----==_mimepart_5b32cc0c6661b_33e52ad12f4def6061127-- From nobody Tue Jun 26 16:38:05 2018 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 9D58C130E6D for ; Tue, 26 Jun 2018 16:38:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 5My1PDM7dMTl for ; Tue, 26 Jun 2018 16:38:01 -0700 (PDT) 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 68D7E130E6B for ; Tue, 26 Jun 2018 16:38:01 -0700 (PDT) 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=sDagZltsj9A+nqa9v+bC2vOrQrk=; b=sXBaNDcUZE0n4rtm i5vpmSjU5BoFfAc2LJvr6HicJQovUFJbQZQUF0AIlgMfj6vBdzVuCJd0IWid6Ctq +DcsTdyyoCy8sPAkaRZXv7a4ERDRrC1D5aQw0sWvYruPv8OJiDfwxog614e+aXR5 K8vAIswSRDqalrTvVKv3sKLg9JI= Received: by filter0403p1iad2.sendgrid.net with SMTP id filter0403p1iad2-15133-5B32CE58-9 2018-06-26 23:38:00.306176759 +0000 UTC Received: from github-lowworker-643483b.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id lD9QkWToRs26JyR7cIrPrg for ; Tue, 26 Jun 2018 23:38:00.235 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-643483b.cp1-iad.github.net (Postfix) with ESMTP id 36C426C13EA for ; Tue, 26 Jun 2018 16:38:00 -0700 (PDT) Date: Tue, 26 Jun 2018 23:38:00 +0000 (UTC) From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32ce58359e7_28d33ff7cb0bef8481927"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2srdK7XHESQd6+v4zNukFxi3UKYEM3z7UORt 7k9NvqPwCXN9EtaDQ+NDUlM9de/2Yh4z1u3XRf5HGcXEYZEiQiK6VNp3ign9txrRYcID7bA8WdX6AS Rzc+UEhf+5D7Llo36tE59q4f79Zcbm5uO1LK68lvLW/qhNhk5bv/vXqhWnmL/XPrZI/0wysZsaQZya A= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:38:04 -0000 ----==_mimepart_5b32ce58359e7_28d33ff7cb0bef8481927 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It's going to be painful to have a variable in memory that can represent both a variable length integer (UINT64) and a negative number. There is no precedent for it already. I'd **really** like to only use positive numbers. -- 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/1484#issuecomment-400496168 ----==_mimepart_5b32ce58359e7_28d33ff7cb0bef8481927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It's going to be painful to have a variable in memory that can represent both a variable length integer (UINT64) and a negative number. There is no precedent for it already. I'd really like to only use positive numbers.

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

----==_mimepart_5b32ce58359e7_28d33ff7cb0bef8481927-- From nobody Tue Jun 26 16:43:24 2018 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 A15F8130E6E for ; Tue, 26 Jun 2018 16:43:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cMPHr6St0CwZ for ; Tue, 26 Jun 2018 16:43:19 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43557130E6C for ; Tue, 26 Jun 2018 16:43:19 -0700 (PDT) Date: Tue, 26 Jun 2018 16:43:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530056598; bh=5hQxM0Io1Qa4/FASzW5Ik3SliI7JucDtdMgS1LfSTJA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=x3rNgZBCOERBmuWaJqe+u4YBZSM2Kpdeq53+0ISciuPf4JhMROGKgX81z/R3sjIoo sH+0ko0pWr0tgRXEnApvwRwm4r/PVD7sARTq12/4meIeJYPfwsRkdGlSSVxStBPgxp g9T2S+/IwnzcMnZML04t+kvpHCAJqHKqnZqfPHEU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32cf965c98d_201c3f7f9a414f845775f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 26 Jun 2018 23:43:22 -0000 ----==_mimepart_5b32cf965c98d_201c3f7f9a414f845775f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Conveniently, varints can use int64_t because they only use the lower 62 bits. Also, uint64_t(0)-1 underflows reliably to UINT64_MAX if you want to keep your variables unsigned. However, I think that the -1 recommendation is wrong, particularly in light of the changes to Retry and the server's preferred address transport parameter. We should rephrase and avoid making any recommendation about how to handle these. Those same things makes me very reluctant to recommend starting at 1 or 2, but if we don't require a contiguous sequence of connection IDs, then maybe some implementations can skip a few without consequence. We probably shouldn't require contiguous sequence numbers anyway because of the potential for some endpoints to consume values that aren't seen and then they might decide not to provision their peer with matching connection IDs. The frame isn't that small, after all. -- 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/1484#issuecomment-400497080 ----==_mimepart_5b32cf965c98d_201c3f7f9a414f845775f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Conveniently, varints can use int64_t because they only use the lower = 62 bits. Also, uint64_t(0)-1 underflows reliably to UINT64_MAX if you wa= nt to keep your variables unsigned.

However, I think that the -1 recommendation is wrong, particularly in = light of the changes to Retry and the server's preferred address transpor= t parameter. We should rephrase and avoid making any recommendation abou= t how to handle these.

Those same things makes me very reluctant to recommend starting at 1 o= r 2, but if we don't require a contiguous sequence of connection IDs, the= n maybe some implementations can skip a few without consequence. We prob= ably shouldn't require contiguous sequence numbers anyway because of the = potential for some endpoints to consume values that aren't seen and then = they might decide not to provision their peer with matching connection ID= s. The frame isn't that small, after all.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b32cf965c98d_201c3f7f9a414f845775f-- From nobody Tue Jun 26 16:46:23 2018 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 5C9CB130E6A for ; Tue, 26 Jun 2018 16:46:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 gBzEkC8tmjhL for ; Tue, 26 Jun 2018 16:46:20 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 DAA6B130E61 for ; Tue, 26 Jun 2018 16:46:19 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530056779; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=e67VBdLHAJ5vV3Fm0ToR1UzpfzrIZ2znFMafcnF8V2c=; b=uCKvHAnMd6hgQLRt/MW5q7HTkHrZmS98mp6aSisXZqsz6hg/HHhhzwEM0q3AjcNpRX/6Vc0Z assA9kAnIAZC1XYj4+kPKaEsdEzxevmYk91B7tYpduqDa2Qg85P/1wq1CyKUQ/zUaR96QZTJ TF1Br8oUeieVQaJ8jVl7qc8jZCU= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b32cdf2.7f03fdfadc30-smtp-out-n03; Tue, 26 Jun 2018 23:36:18 -0000 (UTC) Date: Tue, 26 Jun 2018 16:36:17 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32cdf1ab502_19e62ab7c8b2dc0c27266@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32cdf1ab0c5_19e62ab7c8b2dc0c2716c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Tue, 26 Jun 2018 23:46:22 -0000 ----==_mimepart_5b32cdf1ab0c5_19e62ab7c8b2dc0c2716c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/extend-frames Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32cdf1ab0c5_19e62ab7c8b2dc0c2716c-- From nobody Tue Jun 26 17:04:23 2018 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 4F87E130E6E for ; Tue, 26 Jun 2018 17:04:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 j-SaMg4jJuVQ for ; Tue, 26 Jun 2018 17:04:18 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 847BB130E6A for ; Tue, 26 Jun 2018 17:04:18 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530057857; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=IfwfUvcvj0l8V/5Hg584D+aEMzy0Os8ShnBBT3TWgv8=; b=aqBNgXOSUr/ydHgAt3A1g/le6ec5mZcpvPopQ2V3uYYy8jLQPlXOkRSCMb2Jybia6gCO7bz3 eR1d5SpgB2snjvK8M4cwKGylOVzijGjmt9Dqk45KDkziM6TeSS4NzXM+8j+g98FY8Rs9fJ9I O9KgdF4RcVKy3qX5jZMHgitepl8= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32d481.7f3804a9c390-smtp-out-n02; Wed, 27 Jun 2018 00:04:17 -0000 (UTC) Date: Tue, 26 Jun 2018 17:04:17 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32d48171a0f_59572b11dcad7c081373b@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 961d5d: According to text in wiki. Some MD fixes to get ri... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32d4817144d_59572b11dcad7c08136e0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 00:04:22 -0000 ----==_mimepart_5b32d4817144d_59572b11dcad7c08136e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 961d5d997271f0ee623b26cc51234e2108c84b31 https://github.com/quicwg/base-drafts/commit/961d5d997271f0ee623b26cc51234e2108c84b31 Author: gloinul Date: 2018-05-18 (Fri, 18 May 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- According to text in wiki. Some MD fixes to get right formating. Commit: b50fe189950d125616fbf047423c9d7c6cdd1840 https://github.com/quicwg/base-drafts/commit/b50fe189950d125616fbf047423c9d7c6cdd1840 Author: gloinul Date: 2018-05-18 (Fri, 18 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks. Commit: 57278fefca27545c0f1e0131da9b76f45847e4e4 https://github.com/quicwg/base-drafts/commit/57278fefca27545c0f1e0131da9b76f45847e4e4 Author: gloinul Date: 2018-05-21 (Mon, 21 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixed a typo on anchor creation Commit: 44a70f83faba4c0f82e404ed94397aa9f40c24a7 https://github.com/quicwg/base-drafts/commit/44a70f83faba4c0f82e404ed94397aa9f40c24a7 Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- According to text in wiki. Some MD fixes to get right formating. Commit: afd15f2900259dc63adfa639d3205e4a2b0740ce https://github.com/quicwg/base-drafts/commit/afd15f2900259dc63adfa639d3205e4a2b0740ce Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Modified proposed text to integrate better and take care of issues around connection migration, ensure more straightforward checks. Commit: da6812728424cc31a1c20dfd8e7a7278531b081b https://github.com/quicwg/base-drafts/commit/da6812728424cc31a1c20dfd8e7a7278531b081b Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixed a typo on anchor creation Commit: a9755ce6b9d12d20dea492cf53311396620678af https://github.com/quicwg/base-drafts/commit/a9755ce6b9d12d20dea492cf53311396620678af Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Log Message: ----------- Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn Commit: 3a95c40006b42f2982dd0614133c1df976c58cdc https://github.com/quicwg/base-drafts/commit/3a95c40006b42f2982dd0614133c1df976c58cdc Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Clarified that ACK or ACK_ECN can be used for acknowledgment in handshake. Clarified what the first packets that can be marked as ECT are in a connection. Commit: 12b1054783a4472aa9ec49eea889c087b1286d7c https://github.com/quicwg/base-drafts/commit/12b1054783a4472aa9ec49eea889c087b1286d7c Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Added ECN intro paragraph. Various editorial improvements of ECN text. Commit: bfe80d5d05622f3c2fc13a890ce67256e7693183 https://github.com/quicwg/base-drafts/commit/bfe80d5d05622f3c2fc13a890ce67256e7693183 Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixed bullet list, Added parenthis around section refs. Commit: 88f76dc5db467f42addaae270548c19a86e4f2d4 https://github.com/quicwg/base-drafts/commit/88f76dc5db467f42addaae270548c19a86e4f2d4 Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fixed indentation and formating Commit: f14134fff1963dfe2660b446cad1bab53922e02e https://github.com/quicwg/base-drafts/commit/f14134fff1963dfe2660b446cad1bab53922e02e Author: gloinul Date: 2018-05-22 (Tue, 22 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Spelling fixed Commit: 71c2794fcb6427d72678f7b6604fd32cbf7247e9 https://github.com/quicwg/base-drafts/commit/71c2794fcb6427d72678f7b6604fd32cbf7247e9 Author: gloinul Date: 2018-05-24 (Thu, 24 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Rewrote the ECN check algorithm for connection migration to be robust. Commit: 2ff5ac9aacbe0e62408b21290da73849675693c9 https://github.com/quicwg/base-drafts/commit/2ff5ac9aacbe0e62408b21290da73849675693c9 Author: gloinul Date: 2018-05-24 (Thu, 24 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Removed trailing spaces. Commit: 19d3b53be3d3729bee1f7ec296f51e8ad64d35db https://github.com/quicwg/base-drafts/commit/19d3b53be3d3729bee1f7ec296f51e8ad64d35db Author: gloinul Date: 2018-05-24 (Thu, 24 May 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fixed trailing spaces in recovery. Commit: f71e93395c552cf4a2b2b6c4a4be050d5cd0e3ee https://github.com/quicwg/base-drafts/commit/f71e93395c552cf4a2b2b6c4a4be050d5cd0e3ee Author: gloinul Date: 2018-05-24 (Thu, 24 May 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Rewraped text in both recovery and transport. Added a new sub-section on continous verification. Commit: fc945461c759b99307ca848a13523ce384adf508 https://github.com/quicwg/base-drafts/commit/fc945461c759b99307ca848a13523ce384adf508 Author: gloinul Date: 2018-05-28 (Mon, 28 May 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Added textual description of ECN-CE indicating congestion events. Commit: 66505a3259ef89acf65f88618358fb9568de255f https://github.com/quicwg/base-drafts/commit/66505a3259ef89acf65f88618358fb9568de255f Author: Martin Thomson Date: 2018-05-29 (Tue, 29 May 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Editorial fixes Commit: d5250461b6ddb815fd8fd2422d80a2df8ed670a3 https://github.com/quicwg/base-drafts/commit/d5250461b6ddb815fd8fd2422d80a2df8ed670a3 Author: Magnus Westerlund Date: 2018-05-29 (Tue, 29 May 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1 from quicwg/ecn Editorial fixes Commit: 28ef4c144069f807f468912e5f62ef529398d2da https://github.com/quicwg/base-drafts/commit/28ef4c144069f807f468912e5f62ef529398d2da Author: gloinul Date: 2018-05-29 (Tue, 29 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Editing some formulations. Rewraping more text Commit: 6dd9237e1a1988ce26349d7b306fe3821fbf18a0 https://github.com/quicwg/base-drafts/commit/6dd9237e1a1988ce26349d7b306fe3821fbf18a0 Author: gloinul Date: 2018-05-30 (Wed, 30 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixed trailing spaces and remaining line length issues, I hope. Commit: 0bb5bad97e1d13094463938fcefaa8917f23ffb6 https://github.com/quicwg/base-drafts/commit/0bb5bad97e1d13094463938fcefaa8917f23ffb6 Author: gloinul Date: 2018-05-30 (Wed, 30 May 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Reflowing now saved Commit: 0f9484765fed14f0c8afd9c4fc889fa1a60f2b33 https://github.com/quicwg/base-drafts/commit/0f9484765fed14f0c8afd9c4fc889fa1a60f2b33 Author: gloinul Date: 2018-06-04 (Mon, 04 Jun 2018) Changed paths: M .circleci/config.yml M .lint.py M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-spin-exp.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn Commit: 0e7d43b0d9175ae3f9f61893008c99d8ad865187 https://github.com/quicwg/base-drafts/commit/0e7d43b0d9175ae3f9f61893008c99d8ad865187 Author: gloinul Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-tls.md Log Message: ----------- Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn Commit: 822aded3768e1a1a49a8e9632fe9cc96cbd8fe00 https://github.com/quicwg/base-drafts/commit/822aded3768e1a1a49a8e9632fe9cc96cbd8fe00 Author: gloinul Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Changed so that additional ECN-CE marks are sent in immediate ACKs to avoid unclarity in regards to CE marks and receovery period. Commit: 345f593a92e4455989ada8ff7029e3935f5696d8 https://github.com/quicwg/base-drafts/commit/345f593a92e4455989ada8ff7029e3935f5696d8 Author: gloinul Date: 2018-06-07 (Thu, 07 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Fixed lint issues Commit: e60cc8fed8dc5b1d5d819b3ae3013715fcbbda5f https://github.com/quicwg/base-drafts/commit/e60cc8fed8dc5b1d5d819b3ae3013715fcbbda5f Author: gloinul Date: 2018-06-08 (Fri, 08 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Adding security consideration around ECN into transport. Commit: fdf9df7f91ea314d4e42e246150e2341001d84f8 https://github.com/quicwg/base-drafts/commit/fdf9df7f91ea314d4e42e246150e2341001d84f8 Author: gloinul Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Reverting some rewrapping that are not necessary to reduce clutter. Commit: ec97fd81158d29261e3ea4bb6e80a64efc0aa7a2 https://github.com/quicwg/base-drafts/commit/ec97fd81158d29261e3ea4bb6e80a64efc0aa7a2 Author: gloinul Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Addressing issues raised by Ian Sweet on 180611. Editorial improvements, new psuedo code function. Commit: bf30190128543f0349d8d0b8391b1213c7ebeb3f https://github.com/quicwg/base-drafts/commit/bf30190128543f0349d8d0b8391b1213c7ebeb3f Author: gloinul Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Clarifying that both cases are capability checks. Correcting a number of editorial things. Commit: 60468a79507a1d36a07825b80222da03773e571b https://github.com/quicwg/base-drafts/commit/60468a79507a1d36a07825b80222da03773e571b Author: gloinul Date: 2018-06-12 (Tue, 12 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixed a too too much Commit: f577c8e94d32848feb5cd1582b3ad4b2cc32999c https://github.com/quicwg/base-drafts/commit/f577c8e94d32848feb5cd1582b3ad4b2cc32999c Author: gloinul Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Addressing Martin Thomson's comments. Several editorial changes. The biggest on the ECN block definition. Commit: 2d76935cb8b2f96c4378e86852ae7376cbbb5f91 https://github.com/quicwg/base-drafts/commit/2d76935cb8b2f96c4378e86852ae7376cbbb5f91 Author: gloinul Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Added paragraph on dealing with persistent loss of acknowledgement of some sent packets. Removed editorial note that are covered by issue #1402. Commit: 4af108c47fd2cbaea42b6b83c8d19f1d52513443 https://github.com/quicwg/base-drafts/commit/4af108c47fd2cbaea42b6b83c8d19f1d52513443 Author: gloinul Date: 2018-06-13 (Wed, 13 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixing typo in new paragraph. Commit: 55fa3d65e69355e973e5efcf9daae6e1088a4854 https://github.com/quicwg/base-drafts/commit/55fa3d65e69355e973e5efcf9daae6e1088a4854 Author: gloinul Date: 2018-06-18 (Mon, 18 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-invariants.md M draft-ietf-quic-qpack.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'master' of https://github.com/quicwg/base-drafts into ecn Commit: e06a2a0efb1e655ecd1fa4e3a8e182689a50ff54 https://github.com/quicwg/base-drafts/commit/e06a2a0efb1e655ecd1fa4e3a8e182689a50ff54 Author: gloinul Date: 2018-06-18 (Mon, 18 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Added requirement on ECN marking suppression for packet duplicates. Commit: 1636ebc60296c4af708cfd064cf38541eb41f352 https://github.com/quicwg/base-drafts/commit/1636ebc60296c4af708cfd064cf38541eb41f352 Author: gloinul Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Clarifying that idefinite state are not requeired in duplication detection. Commit: 139f1ee2f508877ad0f8d4cb92170382d4707247 https://github.com/quicwg/base-drafts/commit/139f1ee2f508877ad0f8d4cb92170382d4707247 Author: gloinul Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Martin Thomson's editorial suggestions. Restructured pseudo code sections. Changed capability check and connection migration text significantly. Commit: dbfe4d8a4b22ed8ea779a8bf7fd58d1be0793ddc https://github.com/quicwg/base-drafts/commit/dbfe4d8a4b22ed8ea779a8bf7fd58d1be0793ddc Author: Jana Iyengar Date: 2018-06-19 (Tue, 19 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- partial editorial fixes Commit: 73bf8cb46b529bd799a4cf7df370b54aab5b29b8 https://github.com/quicwg/base-drafts/commit/73bf8cb46b529bd799a4cf7df370b54aab5b29b8 Author: Magnus Westerlund Date: 2018-06-20 (Wed, 20 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge pull request #2 from janaiyengar/ecn Editorial fixes Commit: be91e8f51af527514f9edea18d01a3ca46e20ab4 https://github.com/quicwg/base-drafts/commit/be91e8f51af527514f9edea18d01a3ca46e20ab4 Author: gloinul Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Moved the ECN block in the ACK prior to the ACK blocks themselves. Removed unneeded sentence. Commit: f8d3d5c6040ad0da6595cf07019d5c4f755aa0f3 https://github.com/quicwg/base-drafts/commit/f8d3d5c6040ad0da6595cf07019d5c4f755aa0f3 Author: gloinul Date: 2018-06-21 (Thu, 21 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Merge branch 'ecn' of https://github.com/gloinul/base-drafts into ecn Commit: cf312f90a6d844953e35a095d411e20965724124 https://github.com/quicwg/base-drafts/commit/cf312f90a6d844953e35a095d411e20965724124 Author: gloinul Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merged ECN counters into single ACK frame section and move them before the ACK Block Count. Commit: c37afbbaf89674009a980519edc932c402fa384a https://github.com/quicwg/base-drafts/commit/c37afbbaf89674009a980519edc932c402fa384a Author: Jana Iyengar Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- a few changes Commit: f40dc9d6762888cc178c509979a4f598e3e1e090 https://github.com/quicwg/base-drafts/commit/f40dc9d6762888cc178c509979a4f598e3e1e090 Author: janaiyengar Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'ecn' into ecn Commit: 490dc4f38161ff7a9509a84c439c5280707fb3ee https://github.com/quicwg/base-drafts/commit/490dc4f38161ff7a9509a84c439c5280707fb3ee Author: Jana Iyengar Date: 2018-06-25 (Mon, 25 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- remove ecn block Commit: 9acabc9eeb8a5fe5d722eb40ea7ed89adba67a5c https://github.com/quicwg/base-drafts/commit/9acabc9eeb8a5fe5d722eb40ea7ed89adba67a5c Author: Jana Iyengar Date: 2018-06-26 (Tue, 26 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- mt's and magnus's comments Commit: ec2238b3f7d0e35aece442dbbcedc57fa847addd https://github.com/quicwg/base-drafts/commit/ec2238b3f7d0e35aece442dbbcedc57fa847addd Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'ecn' of https://github.com/janaiyengar/base-drafts into ecn Commit: 8eed0d078d632737bc5afb22e8eb6bf26ff8905d https://github.com/quicwg/base-drafts/commit/8eed0d078d632737bc5afb22e8eb6bf26ff8905d Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fixups for ECN changes Renumber ACK_ECN to 0x20, fix merge conflicts, bad xref Commit: 61ab31e09b98b31cc5dfa358f650d7629d75a426 https://github.com/quicwg/base-drafts/commit/61ab31e09b98b31cc5dfa358f650d7629d75a426 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Line length issues Compare: https://github.com/quicwg/base-drafts/compare/4b3735c83221...61ab31e09b98 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32d4817144d_59572b11dcad7c08136e0-- From nobody Tue Jun 26 17:07:44 2018 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 4F30D130EFD for ; Tue, 26 Jun 2018 17:07:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.008 X-Spam-Level: X-Spam-Status: No, score=-3.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hPCkMlGUvXSF for ; Tue, 26 Jun 2018 17:07:39 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 963D8130F24 for ; Tue, 26 Jun 2018 17:07:38 -0700 (PDT) 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=pbGXPbHmkhBIZtPv18XAUpTiBsc=; b=KIa1ATIiuzvSqBZt jFY/ZnW01hFbXmCsAFLVwVGKk5b7JGNRPHY5kE3Wo9ck6jGaLeKh8JYI7fYAwuKC kMftvWDhNXoYhmwcCU0CKYTjVO7NxRCUKXwJF3HW+iMeF8nKtGVhlimYZlZgiu24 xqmEjGvrg0FfjGbFbX4lHfyCCJ8= Received: by filter0620p1iad2.sendgrid.net with SMTP id filter0620p1iad2-4256-5B32D549-1 2018-06-27 00:07:37.027100721 +0000 UTC Received: from github-lowworker14-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0050p1mdw1.sendgrid.net (SG) with ESMTP id FZ5rgG0ZQGKkhTpp5Rq2Vg for ; Wed, 27 Jun 2018 00:07:36.813 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker14-cp1-prd.iad.github.net (Postfix) with ESMTP id A6796E18A6 for ; Tue, 26 Jun 2018 17:07:36 -0700 (PDT) Date: Wed, 27 Jun 2018 00:07:37 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d548a4c51_509e3fe854a52f7c49194"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3zWAOJGzMfNWIcW7zi/aJhyI7eMAsvP9Rsyx siQu8BvIT5od63Iew5IXNzLPXGfgyc0uOn8Jqr2ifmb08zrxommM5e0r0WcWuFZVWhH/iKYVQgIwqp TKIZut2qlnK6qGO4cY0OR50OzAbMrXxw+rbuTdxpTNq2myUrKYY7KKvoUTKDwhJVFOwWU+g8N+DA0/ k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:07:43 -0000 ----==_mimepart_5b32d548a4c51_509e3fe854a52f7c49194 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1372. -- 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/1372#event-1702723512 ----==_mimepart_5b32d548a4c51_509e3fe854a52f7c49194 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1372.

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

----==_mimepart_5b32d548a4c51_509e3fe854a52f7c49194-- From nobody Tue Jun 26 17:08:48 2018 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 2F6EF130E75 for ; Tue, 26 Jun 2018 17:08:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 osxs3qujVJkj for ; Tue, 26 Jun 2018 17:08:46 -0700 (PDT) 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 BE20A130E5C for ; Tue, 26 Jun 2018 17:08:45 -0700 (PDT) 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=0rPLVE7Nh+9vHrqXxPXm8R8zwgA=; b=vYmuhMCbKGyojNLT f89O9svt6lCqgNLUk3JI+vxEEQfo0XiwmA8NwUbq0ZsRXfTLdH2NRKyMwjYjXoxT kBzx75ok2kLg81q1s+H6Cy7EqM6NvzEJZm2JwtGr9k4siH/mDdmv4tsKWNUrIrNW 4EDdbuAx/ttF3aMg3KZejhxBSeI= Received: by filter0581p1iad2.sendgrid.net with SMTP id filter0581p1iad2-28743-5B32D58B-22 2018-06-27 00:08:43.585145406 +0000 UTC Received: from github-lowworker-0be93ae.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id zJMzR3XiSy2P1SHJQ_aTKg for ; Wed, 27 Jun 2018 00:08:43.581 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-0be93ae.cp1-iad.github.net (Postfix) with ESMTP id 8CBFE3E0774 for ; Tue, 26 Jun 2018 17:08:43 -0700 (PDT) Date: Wed, 27 Jun 2018 00:08:43 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d58b8ac1a_b5063fb2f3ba8f847319a"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak25QHKVk3EW9qWDEfFq9NnCZVE5QX35p+umsd hXHXO6nPGPzdMXWCE/RCO4tp/vGskfRSbQrgklj7FqAgus/DYXq5enyrriwBDmI+LBAZbuopz8w2ZQ V6edx/n3xg9DUUnA7+TWc2tZ8lxTg44yZchDSNBAov6RdDzQQxl+Ugr/SXwWLgjzpAuzCQasjavCOF U= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:08:48 -0000 ----==_mimepart_5b32d58b8ac1a_b5063fb2f3ba8f847319a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop are we resolved on this? (I don't have the code I wrote, sadly). -- 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/1431#issuecomment-400500835 ----==_mimepart_5b32d58b8ac1a_b5063fb2f3ba8f847319a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop are we resolved on this? (I don't have the code I wrote, sadly).

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

----==_mimepart_5b32d58b8ac1a_b5063fb2f3ba8f847319a-- From nobody Tue Jun 26 17:09:13 2018 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 5DF71130E5C for ; Tue, 26 Jun 2018 17:09:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ucq0n3g-73wa for ; Tue, 26 Jun 2018 17:09:09 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B09AA130E75 for ; Tue, 26 Jun 2018 17:09:09 -0700 (PDT) Date: Tue, 26 Jun 2018 17:09:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530058148; bh=FvmSjpLiXx4VWaH2wivlrRMWyhscbEOK8bHTc7nPiQo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mrSAMW72M75eAlMAD5MJgP70fm5tQvx+B0XPob+m9WUh4KNuPQFWr8DZYDKUjSERs vuIE/O/2iv/sMcet7IbzATRk9epI3I7B+1rrEsVmO1ElUi3PrcaQF0OCpd/hmM6nL/ pLS+qM99wxaM0AhqmWYf3Q883xEzMysJdaJvSjBc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d5a4e6ec1_65972b2257278f546435f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:09:12 -0000 ----==_mimepart_5b32d5a4e6ec1_65972b2257278f546435f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop, if you want to get this in for -13, you have a little bit of time left. -- 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/1422#issuecomment-400500953 ----==_mimepart_5b32d5a4e6ec1_65972b2257278f546435f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop, if you want to get this in for -13, you have a little bit of time left.

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

----==_mimepart_5b32d5a4e6ec1_65972b2257278f546435f-- From nobody Tue Jun 26 17:09:37 2018 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 A0E0E130EFA for ; Tue, 26 Jun 2018 17:09:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 TpcFX43NmjsE for ; Tue, 26 Jun 2018 17:09:33 -0700 (PDT) Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 178A4130EE2 for ; Tue, 26 Jun 2018 17:09:31 -0700 (PDT) Date: Tue, 26 Jun 2018 17:09:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530058170; bh=VH9z0sRCqcEdA47surwebbQCHMNPywvJXM7yPcsQyII=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q3+MqCDtZ3xplCUTXNM77FXekhrwDEDTXKGpidPxOTNUbdNMqvaHraZWYp6onoutY C8RKHRcFFL8mw5evnSrBvtxxpXvufn8v6RaYEyn0t7y38fFy1mj4Gk/ghA6+j/AsLD cNe03S85hPSNZFRSZP8vR5HohApulcs5gVC7p+wI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d5ba8c9b0_30f63f9f9b6caf78283583"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:09:35 -0000 ----==_mimepart_5b32d5ba8c9b0_30f63f9f9b6caf78283583 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Did we resolve this on the list? It seemed like the objections were addressed, but I'm biased on this one. -- 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/1359#issuecomment-400501075 ----==_mimepart_5b32d5ba8c9b0_30f63f9f9b6caf78283583 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Did we resolve this on the list? It seemed like the objections were addressed, but I'm biased on this one.

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

----==_mimepart_5b32d5ba8c9b0_30f63f9f9b6caf78283583-- From nobody Tue Jun 26 17:09:43 2018 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 16057130EFA for ; Tue, 26 Jun 2018 17:09:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DI_HoNcDM_AF for ; Tue, 26 Jun 2018 17:09:34 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94B30130EF1 for ; Tue, 26 Jun 2018 17:09:31 -0700 (PDT) Date: Tue, 26 Jun 2018 17:09:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530058170; bh=c1Z4armSAo6mczAnGqvMqWeqon1n5GGVKhYyBdzAKx4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jjWV+LMzZZFRHW//vWg8XmAmA+3qiWGEDAU0cZ3RU4b7zMj0WfRYGNfUxkbtXzvRx BA6QkZghw8QHzAJVzPHmcYmsucV8NKAZiJz9pZF+oNBHufTBJOpqSG27DvIi6gsp70 hSFQn2iKaSybMCMfFpr4A4KwjHi2fH/AOhOuSKdE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify QPACK eviction races (#1237) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d5bac9a61_22483fe12f26cf781489f0"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:09:37 -0000 ----==_mimepart_5b32d5bac9a61_22483fe12f26cf781489f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop, ping. -- 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/1237#issuecomment-400501184 ----==_mimepart_5b32d5bac9a61_22483fe12f26cf781489f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop, ping.

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

----==_mimepart_5b32d5bac9a61_22483fe12f26cf781489f0-- From nobody Tue Jun 26 17:20:12 2018 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 0294C131182 for ; Tue, 26 Jun 2018 17:20:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 XbfboPpoJ6k4 for ; Tue, 26 Jun 2018 17:20:02 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2A87313116E for ; Tue, 26 Jun 2018 17:20:02 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530058801; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=bVZVO7qBFzQOURfubmL0oefMQHyDCzh20lKEWlF+pj4=; b=NL8wlRYY85a78cK1RqHoMmbAy5+TgXqzkK8nWGmapqc0cBI53fSrt/r1drevCFEO0L2hBt+4 IwlhU2sGbpbLrtCE7UPhz0OY/StQMjxmfFr86s1f+IjDt/QqUX08ew1L/HfNvCUd0MnkirD6 B+0DZPPEgsUqNQevjalCag1g4IA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32d831.7fb1b3396120-smtp-out-n01; Wed, 27 Jun 2018 00:20:01 -0000 (UTC) Date: Tue, 26 Jun 2018 17:20:01 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32d83131d56_3fb12af73071bc0c60748@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d42a44: Rename CRYPTO_HS to CRYPTO Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32d831319ac_3fb12af73071bc0c60676"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 00:20:11 -0000 ----==_mimepart_5b32d831319ac_3fb12af73071bc0c60676 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/crypto-cleanup Home: https://github.com/quicwg/base-drafts Commit: d42a4408756da8d18ffbf7c20756c74b95c4c4be https://github.com/quicwg/base-drafts/commit/d42a4408756da8d18ffbf7c20756c74b95c4c4be Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Rename CRYPTO_HS to CRYPTO Commit: 460e6602bb9672c907508b892591847305ee4bb3 https://github.com/quicwg/base-drafts/commit/460e6602bb9672c907508b892591847305ee4bb3 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Reflow paragraphs Commit: 35513e0a6e6527e699401e9cfc4c8891498aec65 https://github.com/quicwg/base-drafts/commit/35513e0a6e6527e699401e9cfc4c8891498aec65 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Didn't save some of the recovery tweaks Commit: 5a4a9906b6cf982cb897043c988d61c85c47db3f https://github.com/quicwg/base-drafts/commit/5a4a9906b6cf982cb897043c988d61c85c47db3f Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Fixup reference format Compare: https://github.com/quicwg/base-drafts/compare/cadc2c9ac74f...5a4a9906b6cf **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32d831319ac_3fb12af73071bc0c60676-- From nobody Tue Jun 26 17:23:17 2018 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 AA504130F26 for ; Tue, 26 Jun 2018 17:23:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gf0UwiJm1XpP for ; Tue, 26 Jun 2018 17:23:14 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 EA9D4130EE7 for ; Tue, 26 Jun 2018 17:23:13 -0700 (PDT) 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=ypl9/Ji6W7E8fpdlEttgAM5gXtk=; b=aS0jR7YP+QQj8IJb 4qi3E6NGb/BS6eChHXxGDGYU0LSGkFm+14EukPzgFPudpx0hqWzcO9pMHpp0KPV+ hB9LPuGlltL6Mvtca6WihSopPFoWpezXdiO5naIMd52NW7ymjhRzttsJ/BUsRQQH 0kt4yPnBJGkscL9Ozhb/ljrXq2I= Received: by filter0385p1iad2.sendgrid.net with SMTP id filter0385p1iad2-24360-5B32D88E-4 2018-06-27 00:21:34.204451078 +0000 UTC Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) by ismtpd0024p1mdw1.sendgrid.net (SG) with ESMTP id 4NbfsvXPTxS5TYwVnh1C5A for ; Wed, 27 Jun 2018 00:21:33.984 +0000 (UTC) Date: Wed, 27 Jun 2018 00:21:34 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d88da8ac_4ef2b01cea6af54137419"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1D7UuuQ0vEE+HSFKe8B04YZhyHQx005sYTF9 jKUuOtAXS3GrifkMsx2dA/EOoOxEbDJ2x2grtNzbGJ44ZsWWfjMBDoIEWJxuDI4CB/ZWlHquTSJt0T lbS5qMaGZ77ONmIQ0qk11hy6vV/U3XgOHUemTN0+KrSKIeruATyUB/ya70qPpT5s8Ei9IIAYLDPe9M E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:23:16 -0000 ----==_mimepart_5b32d88da8ac_4ef2b01cea6af54137419 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. ec1e39f This text is ugly -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1476/files/5a4a9906b6cf982cb897043c988d61c85c47db3f..ec1e39fe2309ac2108fd8752d1136babfceec026 ----==_mimepart_5b32d88da8ac_4ef2b01cea6af54137419 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b32d88da8ac_4ef2b01cea6af54137419-- From nobody Tue Jun 26 17:23:26 2018 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 0CFC1130F26 for ; Tue, 26 Jun 2018 17:23:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 ulRdYfcr4qCk for ; Tue, 26 Jun 2018 17:23:23 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 90D9B131140 for ; Tue, 26 Jun 2018 17:23:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530059003; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Jr2AeIZh7csFxjR4/MH41sNBBslmxxSdJ0/Tj9CZBq0=; b=nKqqyKKYvDzzEm+OUJw/SCEpvoirti1PNqLn6ejznPL28jb6i+dOmgC934rhs2o59yfxrCqx AortgEK2OcIugmDZlkuYTebI0DTavea3gQg+ZQ/e96k715jqf/BtYuDH2/VdtR7P352IHzf2 q7fZq1dN+6yzllYebDEZA0NqhMY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32d8fa.7f26f66e1990-smtp-out-n01; Wed, 27 Jun 2018 00:23:22 -0000 (UTC) Date: Tue, 26 Jun 2018 17:23:22 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32d8fa3ef10_56e22aaf63781bfc609a@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d42a44: Rename CRYPTO_HS to CRYPTO Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32d8fa3e8db_56e22aaf63781bfc60858"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 00:23:25 -0000 ----==_mimepart_5b32d8fa3e8db_56e22aaf63781bfc60858 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: d42a4408756da8d18ffbf7c20756c74b95c4c4be https://github.com/quicwg/base-drafts/commit/d42a4408756da8d18ffbf7c20756c74b95c4c4be Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Rename CRYPTO_HS to CRYPTO Commit: 460e6602bb9672c907508b892591847305ee4bb3 https://github.com/quicwg/base-drafts/commit/460e6602bb9672c907508b892591847305ee4bb3 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Reflow paragraphs Commit: 35513e0a6e6527e699401e9cfc4c8891498aec65 https://github.com/quicwg/base-drafts/commit/35513e0a6e6527e699401e9cfc4c8891498aec65 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- Didn't save some of the recovery tweaks Commit: 5a4a9906b6cf982cb897043c988d61c85c47db3f https://github.com/quicwg/base-drafts/commit/5a4a9906b6cf982cb897043c988d61c85c47db3f Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Fixup reference format Commit: ec1e39fe2309ac2108fd8752d1136babfceec026 https://github.com/quicwg/base-drafts/commit/ec1e39fe2309ac2108fd8752d1136babfceec026 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- This text is ugly Commit: 49eec24e4398ff34e72ff8bef169bb21cbaefda9 https://github.com/quicwg/base-drafts/commit/49eec24e4398ff34e72ff8bef169bb21cbaefda9 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1476 from quicwg/crypto-cleanup Crypto cleanup Compare: https://github.com/quicwg/base-drafts/compare/61ab31e09b98...49eec24e4398 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32d8fa3e8db_56e22aaf63781bfc60858-- From nobody Tue Jun 26 17:23:33 2018 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 82773130F26 for ; Tue, 26 Jun 2018 17:23:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 MuQ-bgJkE5b4 for ; Tue, 26 Jun 2018 17:23:25 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80E69130EE7 for ; Tue, 26 Jun 2018 17:23:25 -0700 (PDT) Date: Tue, 26 Jun 2018 17:23:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530059004; bh=VGzCxmskPrlhsyo09VEgE0hT/oYiZTbhb5siBj7vvh8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2OrQS924dRplbGweol0mMtLGsCAX1VA/8DIMXZZDfRe/1RpHnPV8YyCI1d5inXlNA 8sPRKcXt7zpUWWtxzd5uML/v5XJZ3nuKmNNW/v+Y/h1f+5TwS/kctTkwX+6GoudIz4 EPn1O9b0WAOHvQgutC9wUotoQBy7yJjXq0gH37hY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d8fcb8fcd_47fa3fafed974f781363f9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:23:29 -0000 ----==_mimepart_5b32d8fcb8fcd_47fa3fafed974f781363f9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1476. -- 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/1476#event-1702742231 ----==_mimepart_5b32d8fcb8fcd_47fa3fafed974f781363f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1476.

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

----==_mimepart_5b32d8fcb8fcd_47fa3fafed974f781363f9-- From nobody Tue Jun 26 17:24:33 2018 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 40D95131141 for ; Tue, 26 Jun 2018 17:24:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Ydcyah_V6KFT for ; Tue, 26 Jun 2018 17:24:29 -0700 (PDT) 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 D2F07130F26 for ; Tue, 26 Jun 2018 17:24:28 -0700 (PDT) Date: Tue, 26 Jun 2018 17:24:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530059068; bh=PABk2aIEnbbvzQ4bNFIQf3z5AmYFtRWibYXM2BRN83g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CDGUz+CBmkxKB0gm/tZ0Opj3O4MMhmw1wOn/1jvKZi5hhMFpLy/wVjQFB5nA+eHHJ UYN+QAxLjruh1FB0KaWJb/ikZQNdybwNED8rOO+eYW+MswJyGHTFadp4CgChEThBc7 mtIbOUyfZy1mrEIj3Gr5/ydjmrk/8OHOueBedgPY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Crypto cleanup (#1476) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32d93c33994_ea03f821be4af849394c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:24:31 -0000 ----==_mimepart_5b32d93c33994_ea03f821be4af849394c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Discussed with editors; CRYPTO is fine. Naming is an area where editors have some discretion, but we will continue to accept suggestions for new names for things. -- 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/1476#issuecomment-400503987 ----==_mimepart_5b32d93c33994_ea03f821be4af849394c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Discussed with editors; CRYPTO is fine. Naming is an area where editors have some discretion, but we will continue to accept suggestions for new names for things.

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

----==_mimepart_5b32d93c33994_ea03f821be4af849394c-- From nobody Tue Jun 26 17:34:20 2018 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 E7AED131119 for ; Tue, 26 Jun 2018 17:34:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 smFjCeCVZ0jl for ; Tue, 26 Jun 2018 17:34:16 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 748A6130E70 for ; Tue, 26 Jun 2018 17:34:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530059655; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=N2ijul4f/Lqvnj8YkPq1H36n478C2Bty77GAKa9NR5M=; b=Fbs8FNNdb/H3X4wRK3lrXy6rBjBrETRm1e3XBetGthpzRefpOIsb+UssuYf/+AF4UO0ZgmZg l3F3EmJh16z6CFt2V1soe18Yu6JwVooSU32UD5EHm52vU6FuZ6TdsUTTYHQnYoz9MiGeQXP+ 0PBoHCIOtLYBR9SQb6Qkkz3eCAI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b32d92f.7f453e74ec90-smtp-out-n02; Wed, 27 Jun 2018 00:24:15 -0000 (UTC) Date: Tue, 26 Jun 2018 17:24:14 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32d92e3296_4fc42b1ea7d5fc14657d3@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32d92e2ce1_4fc42b1ea7d5fc146564e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 00:34:18 -0000 ----==_mimepart_5b32d92e2ce1_4fc42b1ea7d5fc146564e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/crypto-cleanup Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32d92e2ce1_4fc42b1ea7d5fc146564e-- From nobody Tue Jun 26 17:46:36 2018 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 83635130E70 for ; Tue, 26 Jun 2018 17:46:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 Sugwvq31_gFe for ; Tue, 26 Jun 2018 17:46:33 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 2904A130EF2 for ; Tue, 26 Jun 2018 17:46:33 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530060392; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Fq+67533yHqVGXTA1gYo+KyT9ItuimBejWUYah5rvio=; b=KJPqadC4b/CGDoAHa8QUWgb0zoWCwcODcbdBLnp7TV8pWwIG3J41EY/iAYJrqbs5NMLPDjbu vd92rYmwew6PvflFdBm6BuLRUipBuWL4aDpTPRsmapzRhWsNLSJVbDjvQA2qfZod2xE2MRsA aINfPu17/EuWbG+lwQq4oaBv0oI= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b32d88b.7ff1535f31b0-smtp-out-n02; Wed, 27 Jun 2018 00:21:31 -0000 (UTC) Date: Tue, 26 Jun 2018 17:21:30 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32d88a1e11e_71f22afb797ebc0c88812@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ec1e39: This text is ugly Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32d88a1dd11_71f22afb797ebc0c887e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 00:46:35 -0000 ----==_mimepart_5b32d88a1dd11_71f22afb797ebc0c887e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/crypto-cleanup Home: https://github.com/quicwg/base-drafts Commit: ec1e39fe2309ac2108fd8752d1136babfceec026 https://github.com/quicwg/base-drafts/commit/ec1e39fe2309ac2108fd8752d1136babfceec026 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-recovery.md Log Message: ----------- This text is ugly **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32d88a1dd11_71f22afb797ebc0c887e2-- From nobody Tue Jun 26 17:59:19 2018 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 79646130E70 for ; Tue, 26 Jun 2018 17:59:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6dLlqO8L2oCJ for ; Tue, 26 Jun 2018 17:59:16 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFB96130DD0 for ; Tue, 26 Jun 2018 17:59:15 -0700 (PDT) Date: Tue, 26 Jun 2018 17:59:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530061153; bh=qWeYNbcw94eifYjmQ5JGDVvRFn8KIsnUTTvoV/li3qM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RNgYq7e+sLBRnezNbhKBijINNG6qDjSCTOwSY7Q6Zu9hFmO7WxB029+0iP0J1Mxaa nxcYOwV6iOcGChUhsSUdqyvOGRKITW6HeLebfcgGw3daeHoCbyNfljkTtHjov4jncH y0R3hZaoQdf7vML7f7YMofZIWmBjzOaPb3mBm/z4= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32e1611d450_69773feb77618f80104954"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 00:59:18 -0000 ----==_mimepart_5b32e1611d450_69773feb77618f80104954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm fine with closing this. -- 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/1431#issuecomment-400509453 ----==_mimepart_5b32e1611d450_69773feb77618f80104954 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm fine with closing this.

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

----==_mimepart_5b32e1611d450_69773feb77618f80104954-- From nobody Tue Jun 26 18:01:01 2018 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 E1138130EF2 for ; Tue, 26 Jun 2018 18:00:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 PUgYv9wZdudU for ; Tue, 26 Jun 2018 18:00:57 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49BCC130DD0 for ; Tue, 26 Jun 2018 18:00:57 -0700 (PDT) Date: Tue, 26 Jun 2018 18:00:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530061256; bh=f7/v4Na908/6hJe67K5C49OULQiM5G0DGyNNcd8zoIM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m8K1wpmC6m07HdI0amQlBwm2p6U1LQM/k1E9cNfiBmNjrX2YfsUSWUMZhi6zmC7MI UlQiFTwEJ/1kGIrEl4n/yvDX2bqVQ2xaIbJbLDyzkkJ+6EA86nBzaWIdIzUEuiF/v6 SSFYhy36N8mjTE62fB725t4dDojNGfAtHAsRctXw= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32e1c8c5169_29e53f873c290f88695c7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 01:01:00 -0000 ----==_mimepart_5b32e1c8c5169_29e53f873c290f88695c7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson : I assume you're planning to merge my PR on top of this? -- 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/1372#issuecomment-400509679 ----==_mimepart_5b32e1c8c5169_29e53f873c290f88695c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson : I assume you're planning to merge my PR on top of this?

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

----==_mimepart_5b32e1c8c5169_29e53f873c290f88695c7-- From nobody Tue Jun 26 18:27:45 2018 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 48688130F04 for ; Tue, 26 Jun 2018 18:27:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 lKHaDs7s9R-x for ; Tue, 26 Jun 2018 18:27:41 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 D4A8B130E7B for ; Tue, 26 Jun 2018 18:27:41 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530062860; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=tXyp5fnyduZ2oXc2s+Ba4QM5Zj5aDjNooe1hB/t53U8=; b=Ms9MuBZ4DBdb9CfutXCoHxHxPH8eLzXBovenpRzzhv1caf3xnH6c7kZTE1sldT4u+BF5v/Y7 3d7DId+CcfewFjAhFlpejqSpdJx+B7C7ocgitrMdWkpRa7UyZFqGw+7kpOB7s6l3MHnWOQ9d YSSDrDrnIN3m1dqtZfJp/IEg7is= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b32e80c.7f886165d990-smtp-out-n01; Wed, 27 Jun 2018 01:27:40 -0000 (UTC) Date: Tue, 26 Jun 2018 18:27:39 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32e80b37b50_2c8b2adda020dc00634a4@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] e2638d: Let's see what the issues file contains Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32e80b37616_2c8b2adda020dc00633b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 01:27:44 -0000 ----==_mimepart_5b32e80b37616_2c8b2adda020dc00633b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/test-issues Home: https://github.com/quicwg/base-drafts Commit: e2638da96507e76b16343647cde1365144f83465 https://github.com/quicwg/base-drafts/commit/e2638da96507e76b16343647cde1365144f83465 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M .circleci/config.yml Log Message: ----------- Let's see what the issues file contains **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32e80b37616_2c8b2adda020dc00633b1-- From nobody Tue Jun 26 18:28:48 2018 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 3DE39130DD0 for ; Tue, 26 Jun 2018 18:28:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BSME6u4T0n-K for ; Tue, 26 Jun 2018 18:28:44 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCA1F130E72 for ; Tue, 26 Jun 2018 18:28:43 -0700 (PDT) Date: Tue, 26 Jun 2018 18:28:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530062922; bh=9nk6Ys+WPaSqajh+PYSOLgeFxZkBEq7aiS2Rr9j8Ih8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0H7OslHE2W6UFqk9zgkd/p0L4aJKDKgNyDMOjyM04m9rZBUCQ7n+svcvqmXzbhh1k pMPT1tMDdsw5AsU1S+CINXMJZIVNlKGDXSfMKya7qYRv6dn01CJ3X2mWs+Pk5gRA8N 0+/ddn/+sGNgHFPJM9+oL8y0fd8GT4y7E9q9UZh4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Proposal for adding ECN support to QUIC. (#1372) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32e84a2f877_1d592b0061c88f5c1348cb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 01:28:47 -0000 ----==_mimepart_5b32e84a2f877_1d592b0061c88f5c1348cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Your PR went into master at the same time. This closed when I merged your changes in. -- 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/1372#issuecomment-400513796 ----==_mimepart_5b32e84a2f877_1d592b0061c88f5c1348cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Your PR went into master at the same time. This closed when I merged your changes in.

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

----==_mimepart_5b32e84a2f877_1d592b0061c88f5c1348cb-- From nobody Tue Jun 26 18:43:25 2018 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 B740B130E78 for ; Tue, 26 Jun 2018 18:43:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 wluwgzo1IJ1q for ; Tue, 26 Jun 2018 18:43:21 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 638D0126DBF for ; Tue, 26 Jun 2018 18:43:21 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530063800; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=U3rz6zqp45IjKi3j2cxUBGiMUDgae3dQvLNmqDKUmdw=; b=WYe69309V8baAWgyB+LhNyFVWqEyLYQlaouM90w08yhrlQmpwDRybbL6qgpDV3e/uv1hZ75w JAStljXD0apiiDks3SnlXJ4D9kfONR9GJLjo5h6VsfQ3LalvyzxUpgPoL7RTuvc3aSUH6CUS P3Gr5BXPSIgwAbZJbmC03speTzs= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b32ebb8.7f87c1c21960-smtp-out-n03; Wed, 27 Jun 2018 01:43:20 -0000 (UTC) Date: Tue, 26 Jun 2018 18:43:20 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32ebb8a193c_5b052ad2b8769c002038c@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 682ebf: OK, this might work Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32ebb8a1356_5b052ad2b8769c00202b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 01:43:23 -0000 ----==_mimepart_5b32ebb8a1356_5b052ad2b8769c00202b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/test-issues Home: https://github.com/quicwg/base-drafts Commit: 682ebff2e2697ff858c4695e48aff40dc53d40fb https://github.com/quicwg/base-drafts/commit/682ebff2e2697ff858c4695e48aff40dc53d40fb Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M .circleci/config.yml Log Message: ----------- OK, this might work **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32ebb8a1356_5b052ad2b8769c00202b-- From nobody Tue Jun 26 18:55:20 2018 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 11199130E78 for ; Tue, 26 Jun 2018 18:55:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 Es8fprZSzmCb for ; Tue, 26 Jun 2018 18:55:17 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 13A8C130E72 for ; Tue, 26 Jun 2018 18:55:17 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530064516; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rpOBtQ9Tu6PfLAXCFv1WqZbOWcFKIcJ3/sBWQt/lnVE=; b=EKG4eRj/uvNOTCn+ycgfaF/QRQUwS7/vvM5Y1Ho4j9ZS77b1GjoDV4kfQJ/yw3YB81nwIIyc VLe1cumi4izilwh4U5rS4vN6w+306OipDBVBvNouuv63nRCROXLDxpeJTyrL22sOFM/fmB9A N/0AQqL4mBUAB4AUSwiHRIhMJ24= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b32ec2c.7f8075940ed0-smtp-out-n03; Wed, 27 Jun 2018 01:45:16 -0000 (UTC) Date: Tue, 26 Jun 2018 18:45:16 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32ec2c35acc_29b22ae5f4eebc04719f9@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 62ef33: try again Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32ec2c35678_29b22ae5f4eebc0471899"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 01:55:20 -0000 ----==_mimepart_5b32ec2c35678_29b22ae5f4eebc0471899 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/test-issues Home: https://github.com/quicwg/base-drafts Commit: 62ef33712c1705c4eb14d92bf1083310ce351bd8 https://github.com/quicwg/base-drafts/commit/62ef33712c1705c4eb14d92bf1083310ce351bd8 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M .circleci/config.yml Log Message: ----------- try again **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32ec2c35678_29b22ae5f4eebc0471899-- From nobody Tue Jun 26 18:56:21 2018 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 C4577130E72 for ; Tue, 26 Jun 2018 18:56:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 M2ebQU_54eUL for ; Tue, 26 Jun 2018 18:56:17 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76683126DBF for ; Tue, 26 Jun 2018 18:56:17 -0700 (PDT) Date: Tue, 26 Jun 2018 18:56:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530064576; bh=fC5Usrn0RxgG7C1I/FZC/LBrZLaqFNJU+cFao7lesvE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=o/XlUrIc74czxTHorfTC5/PPbzzMNlqZbiIk3aiAH6GrC14Pxr0cvrC9ENSfBlWme GNtd/kR/v5Hb+3+QWLBbv0EgqCApuIGGYiK9FxyeWMgKshjSKpEtRtIoHXod9OWfi2 4xX/wO3KmSiasxLEUB9hQofdsfGt6q2VwSUrKS/Q= From: Marten Seemann Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32eec07d3cc_5e762abe6de02f587026b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: marten-seemann 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.26 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: Wed, 27 Jun 2018 01:56:19 -0000 ----==_mimepart_5b32eec07d3cc_5e762abe6de02f587026b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree that we should put it in the transport parameters. There shouldn=E2= =80=99t be any way for middleboxes to tamper with packets, even if that t= ampering might seem harmless now. = -- = 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/1479#issuecomment-400517843= ----==_mimepart_5b32eec07d3cc_5e762abe6de02f587026b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I agree that we should put it in the transport parameters. There shoul= dn=E2=80=99t be any way for middleboxes to tamper with packets, even if t= hat tampering might seem harmless now.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b32eec07d3cc_5e762abe6de02f587026b-- From nobody Tue Jun 26 19:00:10 2018 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 7E3AB130E72 for ; Tue, 26 Jun 2018 19:00:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8PJZZqJZnkqX for ; Tue, 26 Jun 2018 19:00:06 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4D9E126DBF for ; Tue, 26 Jun 2018 19:00:06 -0700 (PDT) Date: Tue, 26 Jun 2018 19:00:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530064805; bh=pLfWf2FmliheBA+reS7To0OdUFGCi/d5eUuA2eWmL4M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C+cnyoD9cKxBY48zBAxZQEt5FE077erBu9z1cGe1CKPLGD+8PsRkyUjda55rMUTz/ jmxpzcxNvj4eg7UGgFN9VIosd975Zf1c4cUGSydN9hzesUetrLpHwODFIvQ9xQhlIR dILONDA5jXmmzUXf1z74/nmWtP+/PNEimJQgm11s= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32efa5be8c0_675f3fa05a1c4f7813201"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Wed, 27 Jun 2018 02:00:09 -0000 ----==_mimepart_5b32efa5be8c0_675f3fa05a1c4f7813201 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit +1 to what @MikeBishop said. It'd be nice to confirm there was no tampering, even if we think it's harmless as of now. -- 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/1479#issuecomment-400518415 ----==_mimepart_5b32efa5be8c0_675f3fa05a1c4f7813201 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

+1 to what @MikeBishop said. It'd be nice to confirm there was no tampering, even if we think it's harmless as of now.

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

----==_mimepart_5b32efa5be8c0_675f3fa05a1c4f7813201-- From nobody Tue Jun 26 19:04:24 2018 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 41609130E72 for ; Tue, 26 Jun 2018 19:04:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ycSTYJIxOsna for ; Tue, 26 Jun 2018 19:04:19 -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 744D7126DBF for ; Tue, 26 Jun 2018 19:04:19 -0700 (PDT) Date: Tue, 26 Jun 2018 19:04:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530065057; bh=jEGHabhV38Karmw0U7s5neaIzU+3SURWZr2tS3cC/Po=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Sbl3iEmxsWsQFhOYVmk22id2lSXrCkXCNwib4fTWZwlae8OSEHQSuQwtCutA3OBcz /WiwS2LhS7YIAN2pPUjMiwirY2ezqnEZqjowjCJTPIorsljMogMRKgSu1v3Apuxg2O fwvIOtn6Kj7qt2NCJIaZ8DkeER18urgUoy7vgSKM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32f0a1e4e04_758f3f9df18c4f7863266"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 02:04:23 -0000 ----==_mimepart_5b32f0a1e4e04_758f3f9df18c4f7863266 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If we were going to include the client source connection ID, then we also need to the server connection ID - that isn't authenticated by the handshake either. Then there are all the connection IDs that the server might have the client cycle through with Retry. We don't authenticate the IP address in the same way. -- 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/1479#issuecomment-400519057 ----==_mimepart_5b32f0a1e4e04_758f3f9df18c4f7863266 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If we were going to include the client source connection ID, then we a= lso need to the server connection ID - that isn't authenticated by the ha= ndshake either. Then there are all the connection IDs that the server mi= ght have the client cycle through with Retry.

We don't authenticate the IP address in the same way.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b32f0a1e4e04_758f3f9df18c4f7863266-- From nobody Tue Jun 26 19:10:49 2018 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 E8339130E72 for ; Tue, 26 Jun 2018 19:10:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 rIpITjCryN-e for ; Tue, 26 Jun 2018 19:10:45 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 A3358126DBF for ; Tue, 26 Jun 2018 19:10:45 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065445; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=ikinqsRde+tpohE10+wW+Ey/4tnEnVUSeXfZmMPXJsQ=; b=YvoDD3E/aWD7oSNsDbZlaKZZDS3PrgwpP2gAUSI7dr0qSLolnKklJvrABuntKQWzeJJsk+JL 3ekiJhKO6GTpnqV+ow5ItMgoC2Hx9Ez5BXDAdc1KS7O4jk8DgemXhdWtpF8yy8dCUwVfTXth D4v1MhvkTT8D6XuCXko9KrOWyeY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b32f224.7fe047f68c30-smtp-out-n01; Wed, 27 Jun 2018 02:10:44 -0000 (UTC) Date: Tue, 26 Jun 2018 19:10:42 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f222efbd7_37282b13d6af7c14926dd@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f222ef704_37282b13d6af7c1492595"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:10:47 -0000 ----==_mimepart_5b32f222ef704_37282b13d6af7c1492595 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/test-issues Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f222ef704_37282b13d6af7c1492595-- From nobody Tue Jun 26 19:10:57 2018 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 DAB69130E78 for ; Tue, 26 Jun 2018 19:10:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 F3yDA-2OwTcL for ; Tue, 26 Jun 2018 19:10:50 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 74D0C130F34 for ; Tue, 26 Jun 2018 19:10:50 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065449; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=kffqzeFasjw/F1kvlladqayIi4UqR7ksNv/7jyFoQQ4=; b=yAenVlIGTZ0jHHbbqnLSTVgedCLlHWdcEvTCkauU7imN1GKRYj2VbL09HC9OiidG30CTo2c4 pP65j3uBF0b0RWtXGamB9ELvL+UcSAREX7Hqc7ssLCnA5iot/VkVw6oJgNBmm5TnZ1HMAEdU Z/RNe65sRGjtKn7y8t51PQ0Oyyc= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b32f228.7fbd10d213f0-smtp-out-n01; Wed, 27 Jun 2018 02:10:48 -0000 (UTC) Date: Tue, 26 Jun 2018 19:10:47 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f227e43fb_42232b0ce160dc1839069@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f227e3f6e_42232b0ce160dc18389f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:10:52 -0000 ----==_mimepart_5b32f227e3f6e_42232b0ce160dc18389f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ianswett-default Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f227e3f6e_42232b0ce160dc18389f6-- From nobody Tue Jun 26 19:11:02 2018 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 30412130E72 for ; Tue, 26 Jun 2018 19:10:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 359GD-SjDzJV for ; Tue, 26 Jun 2018 19:10:50 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 BCF9B130F39 for ; Tue, 26 Jun 2018 19:10:50 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065450; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rPOT2QMVubogY81HLMsFBEieOf8XOmKUqv/Od215aHU=; b=oSAsj0CRQlDbue1pz2V34UcCz5s648tUWlooBasHbnf9Nmy953KEoWD0Va82RW3eFKJkiwj8 XuPVA56z+6puY0NPmc85SmhdIW5VMn245ul6GdVqdZgxChb48GhmoUBwQI+xl3l80faFmrhN uEYEp6RFMvnZ8ybQZ4KsvfuEC3U= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b32f22a.7f7dbc049d50-smtp-out-n03; Wed, 27 Jun 2018 02:10:50 -0000 (UTC) Date: Tue, 26 Jun 2018 19:10:49 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f229878cf_1b462b2153f5dc1096c3@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f2298753d_1b462b2153f5dc109543"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:10:52 -0000 ----==_mimepart_5b32f2298753d_1b462b2153f5dc109543 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/lr-too-big Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f2298753d_1b462b2153f5dc109543-- From nobody Tue Jun 26 19:11:06 2018 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 DAF75130E72 for ; Tue, 26 Jun 2018 19:10:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 FEaw3TDrR7cn for ; Tue, 26 Jun 2018 19:10:51 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 0C107130F30 for ; Tue, 26 Jun 2018 19:10:50 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065450; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=QO8Grz8OSNrkKdi9rfTqngiC6p2oSCLJs01WijWbPG4=; b=mIcGGojjANA/oLcqYqL9LEU6B5XmNW5Jb4+ckt62ZFwgMlmpf7gJZp+GGosNe+QaOJ2xpdOB k6mSvzUzFsz6xoeLMczkHymSNFZVr/TE8q3EhKr8C+qiZttelEwurGqv4OClOcq9XDmj0o2P 76CcLzyudEz/+ZHOLc7CNbbfvWU= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32f22a.7f17038eddb0-smtp-out-n01; Wed, 27 Jun 2018 02:10:50 -0000 (UTC) Date: Tue, 26 Jun 2018 19:10:49 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f22934a35_8bf2aca8809bc08337fd@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f2293459c_8bf2aca8809bc083366f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:10:53 -0000 ----==_mimepart_5b32f2293459c_8bf2aca8809bc083366f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-codepoints Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f2293459c_8bf2aca8809bc083366f-- From nobody Tue Jun 26 19:11:16 2018 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 D96AB130F49 for ; Tue, 26 Jun 2018 19:10:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 A6Q2QSmeh3Fq for ; Tue, 26 Jun 2018 19:10:57 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 543C5130F33 for ; Tue, 26 Jun 2018 19:10:57 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065457; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=9bvAlOcU/TckZAJ6o3tdVLirwXns/VzpEU4e45WQcxo=; b=HKNRSRdYwoccYlRVSOtMYxmGtuEN8CgNxeBW6OcvnSKpf4y73JXi1quksy6eZ/3EVVfwOF0X MhfUkbPxWhTAGEF+jYYMdmQ13WGlOPVMkrBUdYCpp5jhmJdz4ddnddT0fsMc5qvkeLrYzFJ8 5saMghKydQnnbt9Xi6Op7jhAy9E= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32f230.7fe138196c00-smtp-out-n01; Wed, 27 Jun 2018 02:10:56 -0000 (UTC) Date: Tue, 26 Jun 2018 19:10:56 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f2308c059_51832ae428cbbc042552a@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f2308bc03_51832ae428cbbc042543a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:04 -0000 ----==_mimepart_5b32f2308bc03_51832ae428cbbc042543a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/gh-issues Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f2308bc03_51832ae428cbbc042543a-- From nobody Tue Jun 26 19:11:21 2018 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 58337130E72 for ; Tue, 26 Jun 2018 19:11:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 xzp5NrbWtbLE for ; Tue, 26 Jun 2018 19:11:04 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 0CA8D130E78 for ; Tue, 26 Jun 2018 19:11:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065463; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=gZd70g9JJcXDOxGkrTURExRixskSPNXbYKTRilSSXiY=; b=V8NPZlRmLS1zdPGyZRU4rCW79jN7JwAnjrhuq8FM+xFaaE0EtxKgbSRM5NB4DLcjGvc+NIlx AMuLA/YWW12D0yZ2INNlubClHGZjskvIhMSeg5XTGoWBPta/IWYQB66+8MBcalMeoGTUmxXM kSvjnZ04VahdgdnvGKSHk970l+s= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b32f237.7fea11446600-smtp-out-n01; Wed, 27 Jun 2018 02:11:03 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:02 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f236dd3bc_6afa2b0ef5a73c10150a6@hookshot-fe-32b5f5b.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f236dcf07_6afa2b0ef5a73c10149c1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:06 -0000 ----==_mimepart_5b32f236dcf07_6afa2b0ef5a73c10149c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sample-bug Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f236dcf07_6afa2b0ef5a73c10149c1-- From nobody Tue Jun 26 19:11:28 2018 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 C0A34130E72 for ; Tue, 26 Jun 2018 19:11:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 5J5AQrE4DMjV for ; Tue, 26 Jun 2018 19:11:05 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C02E7126DBF for ; Tue, 26 Jun 2018 19:11:05 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065465; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=1xWCUEwSG+HntB8vKnYxiGUySOaa/ajrL5TVXhWFUac=; b=Wbrtq5nkJ1j0KTu42L6fJjTXHZseKcXLqSUXWPhDU/uquJtacObbMPy2TG7QIuP4dGt30M1L B0PZsJvh1/z47XCEWxeiz+aO/p1zwtCcTqMe7sunHpqoGWGQbbRthjbA/Qla6nOk4tT3OAMB O4RHaf/KfOxemyacTXv+y1ePp4A= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.253.29]) by mxa.mailgun.org with ESMTP id 5b32f238.7fd483b15810-smtp-out-n01; Wed, 27 Jun 2018 02:11:04 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:03 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f237deb3e_11a22ab8aee4fc1412955@hookshot-fe-b0febf1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f237de7a1_11a22ab8aee4fc1412894"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:07 -0000 ----==_mimepart_5b32f237de7a1_11a22ab8aee4fc1412894 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/encoder-framing Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f237de7a1_11a22ab8aee4fc1412894-- From nobody Tue Jun 26 19:11:34 2018 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 C93E5126DBF for ; Tue, 26 Jun 2018 19:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 Xk8M45mncCur for ; Tue, 26 Jun 2018 19:11:06 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 9FB48130E78 for ; Tue, 26 Jun 2018 19:11:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065466; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=HFSCwYz2HCtZV1rAiND8GEH0wLA+ibF2Dxkat8TkM/o=; b=GCouz9kDs6MT0/VDmxIj/6zT/yJ6tIidbHByNT/ItJ8wWfkvkElGm0Ps+HkwCPkyCDLchU5/ GDmEfdHePBp2IrJoAC91Ptvv/OiidWgMnRtoNVqjLCNIMpfdwwlZ4CEQbLlY51VgQyqt2OXt u6hJsMfgPf4CjUjrfXAlqmijHpA= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b32f23a.7fdfc51005a0-smtp-out-n01; Wed, 27 Jun 2018 02:11:06 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:05 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f239effe_4d292ac3db7c7c1036995@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f239ebcf_4d292ac3db7c7c103682c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:08 -0000 ----==_mimepart_5b32f239ebcf_4d292ac3db7c7c103682c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack_feedback Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f239ebcf_4d292ac3db7c7c103682c-- From nobody Tue Jun 26 19:11:42 2018 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 5DB62130F32 for ; Tue, 26 Jun 2018 19:11:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 dhsX5S70qFMt for ; Tue, 26 Jun 2018 19:11:24 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 E1E90130F3E for ; Tue, 26 Jun 2018 19:11:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065470; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=X6r/hZBAbdE9FIXU1i0X/a+6NYy/w6Tzlw+GgdTcBpM=; b=Jk/0AFArm6P+7n8Sdu9756oSZNfrdh4UbDdvRuX3AjvV1hrEksqwXKwZXsDMr/VPrWb8OnQc Beb8sEbGF9BjmwElLF4AibDwHBI4KAzIV+oYIKdaSQc0KHe5fNV9GCQM3c8VxwtgfvMTrtVy 5EcKp5fvNJhmhC963ikMtcE0TPU= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b32f23d.7f77be2641b0-smtp-out-n01; Wed, 27 Jun 2018 02:11:09 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:09 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f23dafcd8_50e52ac284347c1074096@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f23daf6cf_50e52ac284347c1073936"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:26 -0000 ----==_mimepart_5b32f23daf6cf_50e52ac284347c1073936 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ecn Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f23daf6cf_50e52ac284347c1073936-- From nobody Tue Jun 26 19:11:48 2018 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 67CE5131119 for ; Tue, 26 Jun 2018 19:11:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 IAvJM0VdntFn for ; Tue, 26 Jun 2018 19:11:23 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 AE3CD13115D for ; Tue, 26 Jun 2018 19:11:14 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065467; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5BFRJPa4WNIi4ykj9pY5d9Ru58jiH8ch5tU9PLeze84=; b=VggFqLMAMmbIkbBbD+0MXmnDsvos2OO0q4RBPvAqDt8qd096ikyMgPy2bYLBr+PX7v6IC82+ Cp7tgdZ+7oZoYM1LUllJ9F7o/qvBFzIh+JK35kuuHmJSw8CfWzqwIGv470v8iX+Qz0CaSrsN XsYr5t8fNi6R+JC6Jcr/NhA5CT4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32f23a.7fa1504b2540-smtp-out-n02; Wed, 27 Jun 2018 02:11:06 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:05 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f239f2e99_151d2ac482e2dc10415cf@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f239f293d_151d2ac482e2dc104146c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:26 -0000 ----==_mimepart_5b32f239f293d_151d2ac482e2dc104146c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/ack-reset-stream Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f239f293d_151d2ac482e2dc104146c-- From nobody Tue Jun 26 19:11:54 2018 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 D9D41130E72 for ; Tue, 26 Jun 2018 19:11:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 igX62Hx49gif for ; Tue, 26 Jun 2018 19:11:24 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 44F3E130E78 for ; Tue, 26 Jun 2018 19:11:24 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530065478; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=1lrJrT7iXuYZRx1O87EhQ71k3IkdkI3VfL0UuxwAZ/A=; b=KYtNKVxMOA0acsrGxDhODQjGkM6wMBpKOJAeRiMtgbJuz++/TQP+HUeqNNZYt3NrUjZ31knE KZnMY8G8hrDKCdKhBfcloW8QsgxpfeHbfxhdXIB3cFUIGsoI1iQ5+exsFlQZ2FBmPU1dIIcM TM0rRplEIiSZ6mbwZxlVrkpAnA8= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32f246.7ff06cd53720-smtp-out-n02; Wed, 27 Jun 2018 02:11:18 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:17 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f245461c2_63d32ac8c7d5dc101044f@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f24545d18_63d32ac8c7d5dc10104322"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:11:27 -0000 ----==_mimepart_5b32f24545d18_63d32ac8c7d5dc10104322 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http/grease Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f24545d18_63d32ac8c7d5dc10104322-- From nobody Tue Jun 26 19:21:23 2018 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 F2633130E72 for ; Tue, 26 Jun 2018 19:21:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 MeBMfcWSGMRH for ; Tue, 26 Jun 2018 19:21:20 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 783A6126F72 for ; Tue, 26 Jun 2018 19:21:20 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530066079; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=68bwAl4/8sg1AXaOeY0fsL2rU68NUGFWyIA/3uajUf4=; b=K2hW3dA3CgtbEX3TLyTPToTY00Kh3lFOBe2P2Xxr1OZtmpl2L2tRzGUeookrpk4yRbL6dSUE EgjPxF1A9hkv9WaJkNWvdEpHLdE8xHegZljvK2w9m5oEUviWln/vPBqBT7z7NKPC6WcgpM00 6a7TEQ9/UMYHNK2KGPx3S98Y9FY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b32f239.7f4537674120-smtp-out-n02; Wed, 27 Jun 2018 02:11:05 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:04 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f23889fc1_3c2b2ad4cde61c0856196@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f238897b8_3c2b2ad4cde61c08560dc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:21:22 -0000 ----==_mimepart_5b32f238897b8_3c2b2ad4cde61c08560dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/sni-again Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f238897b8_3c2b2ad4cde61c08560dc-- From nobody Tue Jun 26 19:21:31 2018 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 493AC130F49 for ; Tue, 26 Jun 2018 19:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 oOZfMPCRm6Qt for ; Tue, 26 Jun 2018 19:21:23 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 CAE2A130E7E for ; Tue, 26 Jun 2018 19:21:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530066083; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Fhou9/xt8M/COffJqPdc/jKJ54xwtUhxEX0bThsZda4=; b=iToBiAz+8SfEh0RMfWmQu2yAGUFno78rUgq48BXTV2a9VI8KTrplK9b2w0nuIDKs3GhXPtbm wIJc0bO6zTdHdw2YQs8jC/yu9fhPJt80SdYFlZ0YaaGKQ62cl1Hf+6JvoFvpoQDqn0Lnwu8p AnJaXIsfVBxyG464bmIwH3gPdVo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b32f23e.7fc99da32cc0-smtp-out-n01; Wed, 27 Jun 2018 02:11:10 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:10 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f23e5bbb3_41f22acaba1c7c0841771@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f23e5b77f_41f22acaba1c7c0841634"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:21:26 -0000 ----==_mimepart_5b32f23e5b77f_41f22acaba1c7c0841634 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/stream0 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f23e5b77f_41f22acaba1c7c0841634-- From nobody Tue Jun 26 19:21:38 2018 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 43DB9130F32 for ; Tue, 26 Jun 2018 19:21:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 l7heabG2h0Xa for ; Tue, 26 Jun 2018 19:21:23 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 CA84E130E7D for ; Tue, 26 Jun 2018 19:21:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530066083; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=mD2XKN13MoSl5UXIBIcEVHYLn2ZVevVbxuXZKAXKJtI=; b=Y5KvDc/MEE7nU8Z6urthviEVyr0uoUEyMZvWcLEKexZWml+paRx/bN8dU5yTAI+ZliSVecYs tc9Tp977kJf80PGqscehPNmwLLNyDytc3BBpLtHQok6BtwfS2fUKvGZN/q8rcKKKEzceeVLG 2E2pgZ4cBEliKCsxVwG5DSWzw4o= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b32f23b.7f9ccbf20e70-smtp-out-n03; Wed, 27 Jun 2018 02:11:07 -0000 (UTC) Date: Tue, 26 Jun 2018 19:11:06 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b32f23abfc29_17ba2ae032df5c1824353@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f23abf842_17ba2ae032df5c1824268"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:21:26 -0000 ----==_mimepart_5b32f23abf842_17ba2ae032df5c1824268 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/implicit-ack-header-block Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f23abf842_17ba2ae032df5c1824268-- From nobody Tue Jun 26 19:25:31 2018 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 33080130E7E for ; Tue, 26 Jun 2018 19:25:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 auxXH7XX2PF6 for ; Tue, 26 Jun 2018 19:25:28 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 9779B130E72 for ; Tue, 26 Jun 2018 19:25:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530066327; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=PWX1WPl5bkw3txNAZCB4GsXkWIjLtUigupR1n5a77IU=; b=pwt94ErTl9rEWjmLnjliVVWjpCneRZasO6SulLyS+9pkhbb3chCJF6gRY6Wop7AoVVGWdSMI VYYUbYO7pv5P7ZH+hkFhQQfUxCX33orPNQ4SvQ+qIJq5FpQ/zy17rhnNF1LlOMc4nvUNAUWi kslw9kF/Oyy4vf4FIjfWlkITJwM= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b32f597.7fab98aba600-smtp-out-n03; Wed, 27 Jun 2018 02:25:27 -0000 (UTC) Date: Tue, 26 Jun 2018 19:25:26 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b32f5969481e_38282acad6533c046914@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 113a2c: Rewrite Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b32f59694426_38282acad6533c0469035"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 02:25:31 -0000 ----==_mimepart_5b32f59694426_38282acad6533c0469035 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/hs-error Home: https://github.com/quicwg/base-drafts Commit: 113a2c448b9cc30dc217ffbe7dbabc84d1bc3508 https://github.com/quicwg/base-drafts/commit/113a2c448b9cc30dc217ffbe7dbabc84d1bc3508 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Rewrite **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b32f59694426_38282acad6533c0469035-- From nobody Tue Jun 26 19:26:29 2018 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 CAC44130F04 for ; Tue, 26 Jun 2018 19:26:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jvJclly3XuYT for ; Tue, 26 Jun 2018 19:26:25 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDCC8130E72 for ; Tue, 26 Jun 2018 19:26:24 -0700 (PDT) Date: Tue, 26 Jun 2018 19:26:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530066384; bh=qkeBvZw0sfgX+PXNcKBy7XH2cZe62e+4L57fiKVVjnk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=GbodZNh4lR41rjue3fZ0E7uvaqw/EWFk9cDr+ah5RZRAITucHlVapH6ZryCR92HyV sDL0BazQksDYymNVHMKsjTcAuTT7r4ejGMyeKUoj7QZy1nUUWCxGbosc7BOBUc1Yzx HiiB+KdX9VeeXdA0X0WUY/cc+s4mOK7ho9eRIs3o= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Rescue PR 930 (#1485) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32f5d057d7_4f3d3fe8f799af78793b9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 02:26:27 -0000 ----==_mimepart_5b32f5d057d7_4f3d3fe8f799af78793b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit When doing a branch cleanup, I found this. PR#930 was merged to another branch that never merged. That's unfortunate, moreso because the stream 0 changes some, but not all of the changes. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1485 -- Commit Summary -- * Rewrite -- File Changes -- M draft-ietf-quic-tls.md (19) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1485.patch https://github.com/quicwg/base-drafts/pull/1485.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/1485 ----==_mimepart_5b32f5d057d7_4f3d3fe8f799af78793b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

When doing a branch cleanup, I found this. PR#930 was merged to another branch that never merged. That's unfortunate, moreso because the stream 0 changes some, but not all of the changes.

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

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

Commit Summary

  • Rewrite

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 mute the thread.

----==_mimepart_5b32f5d057d7_4f3d3fe8f799af78793b9-- From nobody Tue Jun 26 19:49:22 2018 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 8178A126F72 for ; Tue, 26 Jun 2018 19:49:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DkjvgSWn6xxh for ; Tue, 26 Jun 2018 19:49:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A87E130E7F for ; Tue, 26 Jun 2018 19:49:17 -0700 (PDT) Date: Tue, 26 Jun 2018 19:49:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530067756; bh=662L11CjHLWyl/ZBXgOHcxdoBpaG5PH5kZyXX8XGxDI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2HThwUwwh+wRZfZwuwVMstTqY1sZ7pnW2xr58fBpuPj4xqz4N3WFRzAXXJg0EMHZi 0tx3Iqc8x9yhtmNf2ghcAPSbM25AOcZTmdtSDeDShor4EivHA3UKUaP8bKFXvDnm2D jdlhIxoVIPdmc+D6Uz8IR9OUgDfr9FxhHCfapPFA= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32fb2c9effd_68fc2adc60614f602748"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 02:49:21 -0000 ----==_mimepart_5b32fb2c9effd_68fc2adc60614f602748 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As I have commented on https://github.com/quicwg/base-drafts/issues/1451#issuecomment-399317602, I agree with @MikeBishop that the initial DCID should be included in TP so that it would be validated when possible. The reason is because without validation, a handshake might succeed without noticing tampering by a middlebox. OTOH, I do not see a reason to protect client's source CID, because client's CID is never allowed to change during the handshake. If the middlebox changes the value, the handshake never ends. -- 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/1479#issuecomment-400526048 ----==_mimepart_5b32fb2c9effd_68fc2adc60614f602748 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As I have commented on #1451 (comment), I agree with @MikeBishop that the initial DCID should= be included in TP so that it would be validated when possible. The reaso= n is because without validation, a handshake might succeed without notici= ng tampering by a middlebox.

OTOH, I do not see a reason to protect client's source CID, because cl= ient's CID is never allowed to change during the handshake. If the middle= box changes the value, the handshake never ends.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b32fb2c9effd_68fc2adc60614f602748-- From nobody Tue Jun 26 20:02:14 2018 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 EFD70130E7D for ; Tue, 26 Jun 2018 20:02:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 kehYf1t2MpL6 for ; Tue, 26 Jun 2018 20:02:10 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A316126F72 for ; Tue, 26 Jun 2018 20:02:10 -0700 (PDT) Date: Tue, 26 Jun 2018 20:02:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530068529; bh=KPdX3QsV/ncbZkf2Mgv0B+0RFGouwyTPM3z1gucpzTU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ETzsHTytVFWaDQDiCGud7RgNt266vztXf5uj5KIcD7xQY/6qYFSX24LsNStf7DOUc X/qSlgz90rIjmt9nWx4ffg131a134HDFFrsFtgSebjQ5T10lMlyAvTFyVDRLpjl79Q KO7+eJEeCXT2IrYQzGn3MzIhL/s7rOgX6m2I3/4o= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b32fe317d8d6_530a3f91c9138f7c127644"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Wed, 27 Jun 2018 03:02:12 -0000 ----==_mimepart_5b32fe317d8d6_530a3f91c9138f7c127644 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > ... client's CID is never allowed to change during the handshake. Can you please point me to where this is written? If the assumption is that changing the source CID means the handshake continues indefinitely, then putting it in the TP seems to actually enforce that requirement. In general, I'd like the TP to authenticate as many things in initial packets as possible. -- 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/1479#issuecomment-400527950 ----==_mimepart_5b32fe317d8d6_530a3f91c9138f7c127644 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

... client's CID is never allowed to change during the handshake.

Can you please point me to where this is written? If the assumption is= that changing the source CID means the handshake continues indefinitely,= then putting it in the TP seems to actually enforce that requirement. In= general, I'd like the TP to authenticate as many things in initial packe= ts as possible.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b32fe317d8d6_530a3f91c9138f7c127644-- From nobody Tue Jun 26 20:49:00 2018 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 A233E130F35 for ; Tue, 26 Jun 2018 20:48:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 XQKCOCR1M4Uq for ; Tue, 26 Jun 2018 20:48:57 -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 C3364130F32 for ; Tue, 26 Jun 2018 20:48:56 -0700 (PDT) Date: Tue, 26 Jun 2018 20:48:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530071335; bh=ePAi/WnHO9gy+l+ZyHKK9eNmEGs0Ivdhu4oOpQHVGK8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Jjya3e1ePIFDi1TQQl47UP1QoU0gtsW4esTzVGDqtEZ6+J2POW9mE9nzgvhA9MqiN iTrqm91WTjTIRgJUeqesYKyJAbgrs1kZk6NxpuqhnaGUgWYBX9qzLr+bBly5O8cmnc elWRGMsUdLF62B3RmNjgcWftKCPhAWZkd7n5NH2U= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rescue PR 930 (#1485) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b330927e071e_131f2ac5ea0d4f5017522"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 27 Jun 2018 03:48:59 -0000 ----==_mimepart_5b330927e071e_131f2ac5ea0d4f5017522 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr approved this pull request. LGTM -- 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/1485#pullrequestreview-132276673 ----==_mimepart_5b330927e071e_131f2ac5ea0d4f5017522 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr approved this pull request.

LGTM

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

----==_mimepart_5b330927e071e_131f2ac5ea0d4f5017522-- From nobody Tue Jun 26 20:50:05 2018 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 7BA56130E10 for ; Tue, 26 Jun 2018 20:50:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6pxppjzkWmF6 for ; Tue, 26 Jun 2018 20:50:00 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A58212785F for ; Tue, 26 Jun 2018 20:50:00 -0700 (PDT) Date: Tue, 26 Jun 2018 20:49:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530071399; bh=1Z+g/KmJMbNlRLMC4Q2vBnlEvGc9U5iOguLp7g1Uiec=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iLB6kgmKV6aFT/ymEd/1IC9MbQZDC3rPwDkBYPnvbotpcaTdZrA2ivhevafdAxOAJ y7Hv9S5nMtPQP9wVwA42BEvVMS22qsSs2KcCnv7nAHTrX0yAPJ2c6YnxS0n1yzqKMf +kT+gUu/bgzJTPhFiUN9ol/bmI9U/m4hkt5Prbt0= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3309675a8ed_252f2b17a827af5c95e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 03:50:03 -0000 ----==_mimepart_5b3309675a8ed_252f2b17a827af5c95e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @chris-wood >> ... client's CID is never allowed to change during the handshake. > > Can you please point me to where this is written? My understanding is that the following paragraphs effectively requires that. > During the handshake, an endpoint might receive multiple packets with the long header, and thus be given multiple opportunities to update the Destination Connection ID it sends. A client MUST only change the value it sends in the Destination Connection ID in response to the first packet of each type it receives from the server (Retry or Initial); a server MUST set its value based on the Initial packet. Any additional changes are not permitted; if subsequent packets of those types include a different Source Connection ID, they MUST be discarded. This avoids problems that might arise from stateless processing of multiple Initial packets producing different connection IDs. > [4.7. Connection ID Encoding](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#connection-id-encoding) > If the assumption is that changing the source CID means the handshake continues indefinitely, then putting it in the TP seems to actually enforce that requirement. To be precise, having client's initial source CID in the TP allows the server to check if the value was consistent during the handshake. Clients naturally check that, by comparing the DCID field of the Initial / Handshake packets that they receive. That's what is different from having client's initial destination CID in TP; without that, neither the client nor the server can check if the field was tampered by a middlebox. > In general, I'd like the TP to authenticate as many things in initial packets as possible. That's a fair point. Though I might argue that we do not necessarily need to include something that is a constant during the handshake. As @martinthomson points out, we do not authenticate IP addresses. To me it seems that the security properties of client's source CID is equivalent to that. -- 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/1479#issuecomment-400534297 ----==_mimepart_5b3309675a8ed_252f2b17a827af5c95e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@chris-wood

... client's CID is never allowed to change during the handshake.

Can you please point me to where this is written?

My understanding is that the following paragraphs effectively requires= that.

During the handshake, an endpoint might receive multiple packets with = the long header, and thus be given multiple opportunities to update the D= estination Connection ID it sends. A client MUST only change the value it= sends in the Destination Connection ID in response to the first packet o= f each type it receives from the server (Retry or Initial); a server MUST= set its value based on the Initial packet. Any additional changes are no= t permitted; if subsequent packets of those types include a different Sou= rce Connection ID, they MUST be discarded. This avoids problems that migh= t arise from stateless processing of multiple Initial packets producing d= ifferent connection IDs.
4.7. Connection ID Encoding<= /p>

If the assumption is that changing the source CID means the handshake = continues indefinitely, then putting it in the TP seems to actually enfor= ce that requirement.

To be precise, having client's initial source CID in the TP allows the= server to check if the value was consistent during the handshake. Client= s naturally check that, by comparing the DCID field of the Initial / Hand= shake packets that they receive.

That's what is different from having client's initial destination CID = in TP; without that, neither the client nor the server can check if the f= ield was tampered by a middlebox.

In general, I'd like the TP to authenticate as many things in initial = packets as possible.

That's a fair point. Though I might argue that we do not necessarily n= eed to include something that is a constant during the handshake. As @martinthomson points out, we do not = authenticate IP addresses. To me it seems that the security properties of= client's source CID is equivalent to that.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3309675a8ed_252f2b17a827af5c95e-- From nobody Tue Jun 26 20:56:22 2018 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 A9605130E24 for ; Tue, 26 Jun 2018 20:56:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7SA2aEL0Sfus for ; Tue, 26 Jun 2018 20:56:19 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC5E6130E10 for ; Tue, 26 Jun 2018 20:56:18 -0700 (PDT) Date: Tue, 26 Jun 2018 20:56:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530071777; bh=yp5y96zWP88VkrCtSEktvcPmvZa6Tug+JfLlmedNtPU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=W8dz9Bh41WIrO/hixPvX9SOpNW6yeKzC7Y+rTE1OWQMqQhQTWEdDaX4YGObF9FgHw m6zwrlAEW0AgPV+yqO58/3uVoJwjUZajq3+yWVJ+vV+FqtqlRDBtfCOJCd16Yxtv1Z s4YzhtZBjO8nZVo2w1dKaUPQsh10EUjX3pwRp7Ec= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b330ae1c7d9a_281cd3fcfc31cef80374bb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Wed, 27 Jun 2018 03:56:21 -0000 ----==_mimepart_5b330ae1c7d9a_281cd3fcfc31cef80374bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Aha -- thanks! I overlooked the last part of that paragraph requiring endpoints to discard packets with a different source CID. In that case, I'm fine omitting the client initial source CID from TP. Regarding the IP address authentication, is that statement true considering Retry packets and tokens? Isn't one point of the Retry packet to validate the client source address? -- 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/1479#issuecomment-400535132 ----==_mimepart_5b330ae1c7d9a_281cd3fcfc31cef80374bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Aha -- thanks! I overlooked the last part of that paragraph requiring = endpoints to discard packets with a different source CID. In that case, I= 'm fine omitting the client initial source CID from TP.

Regarding the IP address authentication, is that statement true consid= ering Retry packets and tokens? Isn't one point of the Retry packet to va= lidate the client source address?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b330ae1c7d9a_281cd3fcfc31cef80374bb-- From nobody Tue Jun 26 20:58:58 2018 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 263DE130E7A for ; Tue, 26 Jun 2018 20:58:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fi4dzVNXmk75 for ; Tue, 26 Jun 2018 20:58:53 -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 A2C1212785F for ; Tue, 26 Jun 2018 20:58:53 -0700 (PDT) Date: Tue, 26 Jun 2018 20:58:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530071932; bh=FZxsUuZAFizDhFp/DohwhNHI8OnMWIJZcehU2KUSxVs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZhtHUhOJ0vg2V3wuJIQvIGl+5+Izm1u1CitigK/8gaFXYsgZweCM0grI6Iwvp5Q8w iVLqA3euFEjfAZXYw1Bcu8obWBZWM0faXdwiZvZxC8lpyI7WdFu1kErVe3D9nI4OFc ZcQ1IaSoPB5I9SuWDLNoBo7kW3cswVQgsK+Xq66Y= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b330b7cf0fb4_29f32b179b836f5c894a4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 03:58:57 -0000 ----==_mimepart_5b330b7cf0fb4_29f32b179b836f5c894a4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit With the merger of stream 0 DT proposal, we now allow uncoordinated middleboxes to change the server's CID. While I understand that it is beneficial to allow the existence of such middleboxes on certain deployments, I think that we should require (or provide a way for) other deployments to check that the client's initially chosen DCID field has not been tampered by a middlebox. Below is a copy of https://github.com/quicwg/base-drafts/issues/1451#issuecomment-399317602 discussing the possible security and ossification concerns behind the issue. > The issue about simply allowing the existence of an uncoordinated middlebox is that it becomes impossible for any server to detect somebody on-path altering the handshake traffic. > > For example, a middlebox can alter the server CID by sending a Retry, and the server will not notice the alternation if the middlebox also drops the token field of the 2nd Initial packet sent from the client that traverses through the middlebox to the server. > > While I understand that you cannot care about the issue in the deployments that you are interested in, I think that others would be worried about the possible impact on security as well as the ossification concern including the one that I have described in #1451 (comment). > > Fortunately, there are ways to define a signal for detecting tampering that can be implemented by server operators who will not have uncoordinated DOS detection devices. > > One way is to add an "Original_DCID" field to Transport Parameters, and state that "a server SHOULD check that the value of the Original_DCID field matches that of the packet that it saw in the first packet that belonged to the connection". Servers running behind an uncoordinated middlebox will turn this check off. > > Note that having a configuration knob is mandatory for servers running behind such a middlebox, even if we do not introduce the "Original_DCID" field. This is because Retry is version-specific (which means that uncoordinated DOS mitigation devices might need to send a Version Negotiation packet). To support that, the servers need to have a knob that changes how the downgrade protection logic works (FWIW, end-to-end version downgrade protection is currently a MUST; we need to change it as well to allow the existence of uncoordinated DOS mitigation devices). -- 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/1486 ----==_mimepart_5b330b7cf0fb4_29f32b179b836f5c894a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

With the merger of stream 0 DT proposal, we now allow uncoordinated middleboxes to change the server's CID.

While I understand that it is beneficial to allow the existence of such middleboxes on certain deployments, I think that we should require (or provide a way for) other deployments to check that the client's initially chosen DCID field has not been tampered by a middlebox.

Below is a copy of #1451 (comment) discussing the possible security and ossification concerns behind the issue.

The issue about simply allowing the existence of an uncoordinated middlebox is that it becomes impossible for any server to detect somebody on-path altering the handshake traffic.

For example, a middlebox can alter the server CID by sending a Retry, and the server will not notice the alternation if the middlebox also drops the token field of the 2nd Initial packet sent from the client that traverses through the middlebox to the server.

While I understand that you cannot care about the issue in the deployments that you are interested in, I think that others would be worried about the possible impact on security as well as the ossification concern including the one that I have described in #1451 (comment).

Fortunately, there are ways to define a signal for detecting tampering that can be implemented by server operators who will not have uncoordinated DOS detection devices.

One way is to add an "Original_DCID" field to Transport Parameters, and state that "a server SHOULD check that the value of the Original_DCID field matches that of the packet that it saw in the first packet that belonged to the connection". Servers running behind an uncoordinated middlebox will turn this check off.

Note that having a configuration knob is mandatory for servers running behind such a middlebox, even if we do not introduce the "Original_DCID" field. This is because Retry is version-specific (which means that uncoordinated DOS mitigation devices might need to send a Version Negotiation packet). To support that, the servers need to have a knob that changes how the downgrade protection logic works (FWIW, end-to-end version downgrade protection is currently a MUST; we need to change it as well to allow the existence of uncoordinated DOS mitigation devices).

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

----==_mimepart_5b330b7cf0fb4_29f32b179b836f5c894a4-- From nobody Tue Jun 26 21:00:50 2018 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 64AD9130E98 for ; Tue, 26 Jun 2018 21:00:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 h5dnX6zk2-5h for ; Tue, 26 Jun 2018 21:00:46 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C377E130E7A for ; Tue, 26 Jun 2018 21:00:46 -0700 (PDT) Date: Tue, 26 Jun 2018 21:00:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530072046; bh=D3B1yAdMIPQTkZtMfgg/0jvvNK17weyfJo3IyT/uOpM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PUuSe5df+PUAmhKuFvwTK3m8TCau+R60gegt0FD6ph6HGeazUL6lwp878zgR7i91p uEQEGnNiwJDM9qV4EOGeRvLoSVdabKiu30fsD50VfQWDld6wMgkv0cW5ib64QWhepW ri479RFlbv+QP3YNOiLj5DnnCMAxOSZFLqFePUvs= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b330bee3121d_54b83fa6377aef7893497"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 04:00:49 -0000 ----==_mimepart_5b330bee3121d_54b83fa6377aef7893497 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit relates to: #1479 -- 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/1486#issuecomment-400535685 ----==_mimepart_5b330bee3121d_54b83fa6377aef7893497 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

relates to: #1479

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

----==_mimepart_5b330bee3121d_54b83fa6377aef7893497-- From nobody Tue Jun 26 21:21:30 2018 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 5771A130E10 for ; Tue, 26 Jun 2018 21:21:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Ux-0CCDYd11k for ; Tue, 26 Jun 2018 21:21:28 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9F56126F72 for ; Tue, 26 Jun 2018 21:21:27 -0700 (PDT) Date: Tue, 26 Jun 2018 21:21:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073286; bh=2vBYcbWc52jXY6wb0uBJELnxFv+OlLg9HSG5ecJ3VP0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0jucWxEXJp1tOjDWp9ivpYw1dCO5ovHHPto06TO9WhldSWM75vWTsDb18ljtUA/T+ JOLVMtvMRnraWYzL0ZN3hXIsMX3zdPU7SIZ9+1lzvbr5KxJNmUKLLUWZwKocNbC/eJ FqDcVXvE+X8nFzdIXz4Pl2nfG0IKKif0I66o6JP4= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Guidance for flow control and ACK of extension frames (#1487) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3310c6ea386_19682adc95aaaf54510a7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 27 Jun 2018 04:21:29 -0000 ----==_mimepart_5b3310c6ea386_19682adc95aaaf54510a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Given the past history, it is easy to overlook the complixity of ACK and flow control when adding new frames, so some guidance could be useful. One option could be to define a few classes of behavior such as now flow no ACK, etc. and use an existing frame such as PING, PAD, etc. as example. -- 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/1487 ----==_mimepart_5b3310c6ea386_19682adc95aaaf54510a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Given the past history, it is easy to overlook the complixity of ACK and flow control when adding new frames, so some guidance could be useful.

One option could be to define a few classes of behavior such as now flow no ACK, etc. and use an existing frame such as PING, PAD, etc. as example.

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

----==_mimepart_5b3310c6ea386_19682adc95aaaf54510a7-- From nobody Tue Jun 26 21:21:58 2018 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 37585130E10 for ; Tue, 26 Jun 2018 21:21:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 xY9HM49tCjhL for ; Tue, 26 Jun 2018 21:21:54 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83840126F72 for ; Tue, 26 Jun 2018 21:21:54 -0700 (PDT) Date: Tue, 26 Jun 2018 21:21:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073313; bh=yMAgabe4u1A+iaIClXP22OTUbZwdmkHKX5QmDBPbotA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iK4Apt76Sc/iT8VMSv+/1wVsYC27bAU6o7yvnqcuQoa+uGLqHu4D7W3WyZxUrNgCl jt7A1jt0Q5JEFwHoTmOJ2nmHQwxqxsO1pZszdvtzVkT//FYWHzq6aaZoP1ZP8/RLO2 Fb0FrruNMucwr0aQp+WBUZJpQ8q26cJgTR1D+38U= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3310e1ab85e_5e493fc6c88b8f8440786"; 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.26 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: Wed, 27 Jun 2018 04:21:57 -0000 ----==_mimepart_5b3310e1ab85e_5e493fc6c88b8f8440786 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Since I'd been asked to present about the issue in Montreal, I was planning to hold it for that discussion. I don't expect it to change, though, so... why not? -- 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/1422#issuecomment-400538272 ----==_mimepart_5b3310e1ab85e_5e493fc6c88b8f8440786 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Since I'd been asked to present about the issue in Montreal, I was planning to hold it for that discussion. I don't expect it to change, though, so... why not?

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

----==_mimepart_5b3310e1ab85e_5e493fc6c88b8f8440786-- From nobody Tue Jun 26 21:22:08 2018 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 A0712130E10 for ; Tue, 26 Jun 2018 21:22:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 DQ19OBAfbR83 for ; Tue, 26 Jun 2018 21:22:05 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 F2E09126F72 for ; Tue, 26 Jun 2018 21:22:04 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530073324; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=hCO8qm7F9R8aN/KeyOgmnlH7+eY4L1UqqzZPXo8KxxY=; b=eHSwsPcFPJdrlI3we6v/vLUpil33TUlqZOX/xP9SnoT8MfzcrBBNSgwTwyyFsy904lK0kErx FNOK5rzi0rj8atPWX47yU0kF2Fq+zAPgI+CyM+LTUe0fGQH10F8WmnlwMts276BZ5t1vPrEy kFsVzxfEf99aPYH4E2f27C4siSI= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3310ec.7fc67be93c90-smtp-out-n03; Wed, 27 Jun 2018 04:22:04 -0000 (UTC) Date: Tue, 26 Jun 2018 21:22:04 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b3310ec31b96_4b9b2acc86693c145097d@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 947bb2: Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3310ec316b1_4b9b2acc86693c145088d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 04:22:07 -0000 ----==_mimepart_5b3310ec316b1_4b9b2acc86693c145088d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 947bb2b992291199389504ce32e4fe208d8eb443 https://github.com/quicwg/base-drafts/commit/947bb2b992291199389504ce32e4fe208d8eb443 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Placeholders for PRIORITY (#1422) * Placeholder, first pass * Clean up types * 0 is a stream now * Word order * Multiple settings **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3310ec316b1_4b9b2acc86693c145088d-- From nobody Tue Jun 26 21:22:17 2018 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 4723C130E98 for ; Tue, 26 Jun 2018 21:22:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 8O_QvaCr0yCq for ; Tue, 26 Jun 2018 21:22:07 -0700 (PDT) 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 E8E58130E7A for ; Tue, 26 Jun 2018 21:22:06 -0700 (PDT) Date: Tue, 26 Jun 2018 21:22:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073326; bh=AFFrWUIMqqrK9ytp/Dnnl+t4SJ3N8VoA2BuPVh4n9DU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cjKclxXPNJWb5Q7TfvhKqFuutKkzHg/Rg28eqHnFT3f6bnxLHLEOECH2PU/SnDak8 6j7KOFkx+qrz/gVxI69P8Eda28bER7lcPWqtkX8pP80NyaHa9z/UttKJzbqD6QlW2k /7sB+5lfujxxxtWM8wU36iPY9UmutJ7MWYmL8G44= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Priority grouping node ambiguity (#441) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3310ee4c8d1_20b23f7edbd70f8443224f"; 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.26 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: Wed, 27 Jun 2018 04:22:09 -0000 ----==_mimepart_5b3310ee4c8d1_20b23f7edbd70f8443224f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #441 via #1422. -- 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/441#event-1702952630 ----==_mimepart_5b3310ee4c8d1_20b23f7edbd70f8443224f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #441 via #1422.

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

----==_mimepart_5b3310ee4c8d1_20b23f7edbd70f8443224f-- From nobody Tue Jun 26 21:22:23 2018 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 63659130F3F for ; Tue, 26 Jun 2018 21:22:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Fc-VHFtiW4X7 for ; Tue, 26 Jun 2018 21:22:07 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBE20126F72 for ; Tue, 26 Jun 2018 21:22:06 -0700 (PDT) Date: Tue, 26 Jun 2018 21:22:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073326; bh=xbKCIoHnFUt8Emvro19kMxxo4iOm2VkJrKzNGJZCIqE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n+51Edg5rQgUUNE9JfhWCbWg2LJKIE1f6FvTxdX2YIxOMalTlxsLputhxYKAsmNx6 CRJUdVSc/wFkpcVF/maGjJa6d3lrWMPSk/H9ogj/fnh5mMRzNVh+NPlOd3JmN2sZ6H yrFggI+8p0eGJzTjM/2bNF+E3OchuAKZaC7DLfLU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Placeholders for PRIORITY (#1422) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3310ee1f6d4_652f3fef47482f80120881"; 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.26 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: Wed, 27 Jun 2018 04:22:11 -0000 ----==_mimepart_5b3310ee1f6d4_652f3fef47482f80120881 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1422. -- 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/1422#event-1702952628 ----==_mimepart_5b3310ee1f6d4_652f3fef47482f80120881 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1422.

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

----==_mimepart_5b3310ee1f6d4_652f3fef47482f80120881-- From nobody Tue Jun 26 21:22:26 2018 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 1F524126F72 for ; Tue, 26 Jun 2018 21:22:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Lwhj0v1xjzuK for ; Tue, 26 Jun 2018 21:22:08 -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 94775130E10 for ; Tue, 26 Jun 2018 21:22:07 -0700 (PDT) Date: Tue, 26 Jun 2018 21:22:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073326; bh=+PjnGRG4Zjt1id3zZ6B9pYoJ3ZdxzRrOhb2BWYkkTIM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ex8UQjN5Bf90djJTrPtLdsgLV4cx145SRk4TqD3/6Fwrb9XNqnn/Gdxz/O028dJVv lUraggBUE49rpBsroN/oHwp7O0vOHmP5qa12mqGWWa2MyYJzcWvVWf0ZvIofrSik77 iLIl4KDJ6i9yNQttVy7X/foAoHFbAmoX/fvUH+Yw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stream 0 DT proposal conflicts with PRIORITY (#1421) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3310ee9b857_10072ace8ac90f5812906c"; 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.26 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: Wed, 27 Jun 2018 04:22:11 -0000 ----==_mimepart_5b3310ee9b857_10072ace8ac90f5812906c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1421 via #1422. -- 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/1421#event-1702952631 ----==_mimepart_5b3310ee9b857_10072ace8ac90f5812906c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1421 via #1422.

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

----==_mimepart_5b3310ee9b857_10072ace8ac90f5812906c-- From nobody Tue Jun 26 21:23:58 2018 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 B0748130E7A for ; Tue, 26 Jun 2018 21:23:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 hhv1xoizXDMP for ; Tue, 26 Jun 2018 21:23:55 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40402130E98 for ; Tue, 26 Jun 2018 21:23:55 -0700 (PDT) Date: Tue, 26 Jun 2018 21:23:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073434; bh=LBE21JqVU86pXsOWHrMf9EUP0xq2Pbi9+/o0zdtFP9c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zitxcqRj8ehnMJrN+NnEurMxMVK4VPBY1u5BfzLwDry/sv06ClJHP9KyB+xJdBC4n c+WIuziHVBWZQAn+nDTntfD28hV/ZC/T656ptdV69xMtYzm45pxPmYFdh1PqtmPb64 ASuBZq/7xt1k/xXzBiO/4MbN8f7J/WHSt7IVRDKM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Clarify QPACK eviction races (#1237) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33115a9ad59_31ce2b033d21af501189bf"; 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.26 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: Wed, 27 Jun 2018 04:23:57 -0000 ----==_mimepart_5b33115a9ad59_31ce2b033d21af501189bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My opinion is no. But as I'm neither the author of the PR nor the editor for this doc, let's redirect that ping to @afrind. Want to rebase and merge this? -- 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/1237#issuecomment-400538512 ----==_mimepart_5b33115a9ad59_31ce2b033d21af501189bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

My opinion is no. But as I'm neither the author of the PR nor the editor for this doc, let's redirect that ping to @afrind. Want to rebase and merge this?

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

----==_mimepart_5b33115a9ad59_31ce2b033d21af501189bf-- From nobody Tue Jun 26 21:25:16 2018 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 E8A22130E98 for ; Tue, 26 Jun 2018 21:25:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fbTKkqDX7vMq for ; Tue, 26 Jun 2018 21:25:12 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05485126F72 for ; Tue, 26 Jun 2018 21:25:12 -0700 (PDT) Date: Tue, 26 Jun 2018 21:25:11 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073511; bh=EO8w/EyWvgKPd7SMe8FUeSCukTwGXJw0p0Pf3mdTxzE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r0qswGXAIiZMXBRVaV4ohuoRguYXALTlZXEQ3wnYTIoEyQfDlj4Zbzt1mjiy92k2e UA0d2YV3gwCzGd4u4G6OZLS1+l2h9XpDlJsd7nACJhtO02POPJuIJqzBPNBECcDZiA 0nwAGbwSspKM/phGacc4/P1RqJdoMc6lNIwlmC04= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3311a754deb_6e3c2b23f374af581805a6"; 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.26 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: Wed, 27 Jun 2018 04:25:14 -0000 ----==_mimepart_5b3311a754deb_6e3c2b23f374af581805a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm inclined to say we move forward with this, based on the list discussion. However, it's bitrotten, and I promised to update this if #1446 landed first, which it did. So that'll be tomorrow. If that means it's in -14 instead of -13, that's okay. -- 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/1359#issuecomment-400538678 ----==_mimepart_5b3311a754deb_6e3c2b23f374af581805a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm inclined to say we move forward with this, based on the list discussion. However, it's bitrotten, and I promised to update this if #1446 landed first, which it did. So that'll be tomorrow. If that means it's in -14 instead of -13, that's okay.

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

----==_mimepart_5b3311a754deb_6e3c2b23f374af581805a6-- From nobody Tue Jun 26 21:26:50 2018 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 51AA9130E7A for ; Tue, 26 Jun 2018 21:26:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 7ZF3oVtOLBsJ for ; Tue, 26 Jun 2018 21:26:48 -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 CED12126F72 for ; Tue, 26 Jun 2018 21:26:47 -0700 (PDT) Date: Tue, 26 Jun 2018 21:26:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073607; bh=8g3KPYbxEexJnyGysvKuGrpTsFXEJfkPuzAKCG93iIY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pVSzr3p6FJfQYTUjooygFlI9Iun0IkGXkt5XQMpFd1FMAZSFedWn4p42aL4T1Xnpz EnwPR7/n8B8Nqx7E7+l17GNWit9SkNJVtp/7He4Qi+Rlm9ZDxIslLLUwFBD8v7Qbr5 uFZ1LtbvOn75sfs4svgsbDfPVoFhOq9e/dAx0Tok= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3312072d3b5_37372aae943c8f5817354b"; 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.26 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: Wed, 27 Jun 2018 04:26:50 -0000 ----==_mimepart_5b3312072d3b5_37372aae943c8f5817354b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit While I continue to prefer this model conceptually, it doesn't sound like there's consensus to do this for v1. I'm trying to insulate HTTP from the specifics of Stream ID layout so that nothing breaks if we adopt something like this in a future version. -- 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/1431#issuecomment-400538853 ----==_mimepart_5b3312072d3b5_37372aae943c8f5817354b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

While I continue to prefer this model conceptually, it doesn't sound like there's consensus to do this for v1. I'm trying to insulate HTTP from the specifics of Stream ID layout so that nothing breaks if we adopt something like this in a future version.

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

----==_mimepart_5b3312072d3b5_37372aae943c8f5817354b-- From nobody Tue Jun 26 21:26:57 2018 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 79B09126F72 for ; Tue, 26 Jun 2018 21:26:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 NDBIlYfso6Ve for ; Tue, 26 Jun 2018 21:26:51 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97786130F24 for ; Tue, 26 Jun 2018 21:26:51 -0700 (PDT) Date: Tue, 26 Jun 2018 21:26:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073610; bh=TDwkxUADe/eQh2I0Y8C4AuyNZklZUBKmG6MKBapLhEE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QCCSShhRypQee86K+EAQ8n6ooVAKXjNUMcrc56WLS7bXBzs/QzDo8gPJYfVOTuKS6 y0DSvs79PhnAfnKeYe3L+nlTt13+BF10WNP6iplJkcUEIznvhOxmX7IRH5YeTJIRCb pbhmhW2Km8zqGi3lJnzPC0mpR+DRB7ZrjyzWlcHY= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Move stream type into frame type (#1431) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33120ac9956_661b3fc051a8ef8417671c"; 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.26 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: Wed, 27 Jun 2018 04:26:54 -0000 ----==_mimepart_5b33120ac9956_661b3fc051a8ef8417671c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1431. -- 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/1431#event-1702956328 ----==_mimepart_5b33120ac9956_661b3fc051a8ef8417671c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1431.

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

----==_mimepart_5b33120ac9956_661b3fc051a8ef8417671c-- From nobody Tue Jun 26 21:30:11 2018 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 6EFD913116C for ; Tue, 26 Jun 2018 21:30:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ZzzPwA4sFKHz for ; Tue, 26 Jun 2018 21:30:02 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 780D5130F2D for ; Tue, 26 Jun 2018 21:30:02 -0700 (PDT) Date: Tue, 26 Jun 2018 21:30:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073801; bh=JGM3ViMSNzXs4N7t2JSlC0Q4yjZkrvBcf9R1d+zresg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FxaKiwXimGUqE0pyq92o/rd3LMA+zJJ3jluogQwPJw+InACqaL92tytksf9hFLQNu gTnFV3cgqZJS6AhVaywKUl4JpvXCYwwygS8tVt1cGGScJ1dN0BpkTCwqqjf/kgcWzA FujDHT1u5ukRVAbWOXTdqLn5c7YGS4y3Oom5Nh9s= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3312c9d18c4_65753fef47482f80113570"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 04:30:10 -0000 ----==_mimepart_5b3312c9d18c4_65753fef47482f80113570 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Regarding the IP address authentication, is that statement true considering Retry packets and tokens? Isn't one point of the Retry packet to validate the client source address? Yeah I'd say that the server "validates" the path, but it doesn't "authenticate" the path by asking the client prove that it has selected that IP address (which is impossible for a client to prove when NAT is involved). -- 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/1479#issuecomment-400539297 ----==_mimepart_5b3312c9d18c4_65753fef47482f80113570 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Regarding the IP address authentication, is that statement true consid= ering Retry packets and tokens? Isn't one point of the Retry packet to va= lidate the client source address?

Yeah I'd say that the server "validates" the path, but it doesn't "aut= henticate" the path by asking the client prove that it has selected that = IP address (which is impossible for a client to prove when NAT is involve= d).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3312c9d18c4_65753fef47482f80113570-- From nobody Tue Jun 26 21:33:21 2018 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 540F7130E98 for ; Tue, 26 Jun 2018 21:33:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oWLFJli6lnM1 for ; Tue, 26 Jun 2018 21:33:17 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67D50126F72 for ; Tue, 26 Jun 2018 21:33:17 -0700 (PDT) Date: Tue, 26 Jun 2018 21:33:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530073996; bh=bmmpSIx4be/JpaWnTcrQdnkIhVrnE/wtA7lFIlJrhFk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xx9ZNp0QHq+mlxWvGjGFbh/hWuTNAUavhkITmK1EuGNwnN2lzriXY3eAw7dUCTIAz Ovob5s5IGGYAa/nYBXi9xzc14aZwROu4sC3OWnc7KBWPtf12FEyES1KUDmxJALkKx+ 1LS9Vm6ek8stS/+FIgZqxs+DHSCuoPrijkxSNMOs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33138cc14b3_25652b17a827af5c2305e6"; 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.26 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: Wed, 27 Jun 2018 04:33:19 -0000 ----==_mimepart_5b33138cc14b3_25652b17a827af5c2305e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The text currently says they SHOULD be contiguous. The advantage to contiguity is that you can speculatively issue batches and assume with some accuracy that the sequence numbers you pick will match the sequence numbers your peer picks. Loosening that to simply ordered seems touchy, since one since effectively becomes dominant in picking which sequence numbers will actually become useful. (Only the intersection of the sequence numbers chosen by each peer can be stably used.) -- 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/1484#issuecomment-400539712 ----==_mimepart_5b33138cc14b3_25652b17a827af5c2305e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The text currently says they SHOULD be contiguous. The advantage to c= ontiguity is that you can speculatively issue batches and assume with som= e accuracy that the sequence numbers you pick will match the sequence num= bers your peer picks.

Loosening that to simply ordered seems touchy, since one since effecti= vely becomes dominant in picking which sequence numbers will actually bec= ome useful. (Only the intersection of the sequence numbers chosen by each= peer can be stably used.)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b33138cc14b3_25652b17a827af5c2305e6-- From nobody Tue Jun 26 21:36:10 2018 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 2C38C130E7A for ; Tue, 26 Jun 2018 21:36:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 qrJdtXywq52l for ; Tue, 26 Jun 2018 21:36:07 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 97009126F72 for ; Tue, 26 Jun 2018 21:36:07 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530074167; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=OacrRsJ1B2xSYHOe9AG9j4fqFOnzuDP4/FCJacqTOZI=; b=KHDoYUg++nWvbC0iOilsPf5t4kv72dJjQw8MvWaPqfSzKnm9obJdLuyWOwQ724m1G+jT5vD4 HZkRggTluCDJ5exKwzl415Yornbp7v9Owijf0h7w31UkAgLMWhWcxSsPgYfNHP01wuLEdZaW 5wWVqohyt1aUeJCVVbfTWLf+CCI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b331436.7f711eafe690-smtp-out-n03; Wed, 27 Jun 2018 04:36:06 -0000 (UTC) Date: Tue, 26 Jun 2018 21:36:05 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b331435914ba_27112aeef0f9fc04319e@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 113a2c: Rewrite Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33143591038_27112aeef0f9fc0431810"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 04:36:10 -0000 ----==_mimepart_5b33143591038_27112aeef0f9fc0431810 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 113a2c448b9cc30dc217ffbe7dbabc84d1bc3508 https://github.com/quicwg/base-drafts/commit/113a2c448b9cc30dc217ffbe7dbabc84d1bc3508 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Rewrite Commit: 5c511676b267d85a211db66512f27e64a6566daf https://github.com/quicwg/base-drafts/commit/5c511676b267d85a211db66512f27e64a6566daf Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Merge pull request #1485 from quicwg/hs-error Rescue PR 930 Compare: https://github.com/quicwg/base-drafts/compare/947bb2b99229...5c511676b267 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33143591038_27112aeef0f9fc0431810-- From nobody Tue Jun 26 21:36:17 2018 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 3EA80130F39 for ; Tue, 26 Jun 2018 21:36:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 I8UjYH1poH5a for ; Tue, 26 Jun 2018 21:36:10 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69387130E7A for ; Tue, 26 Jun 2018 21:36:10 -0700 (PDT) Date: Tue, 26 Jun 2018 21:36:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530074169; bh=z9cY4ZQrfpojWA8w9yUQN3w1b8NT2DSG5hpMNETrKe4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j9DFNdI+5aGhXSMmg8DziqXmOFEUKu/lgrRxdfvNnOcH2eyNaASKMViN6m4dCl2Ie B78/3eqlJqb5FCebm/4IrEBQAhUU5abiBhsVLNhFGg3h7n/cpNQGervzl3apJ4xLre BKWN37nsFT5AFna5MitDF9roT5gBeGe9aVlu2R/A= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rescue PR 930 (#1485) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b331439ca2bb_255c2b17a827af5c8921b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 04:36:13 -0000 ----==_mimepart_5b331439ca2bb_255c2b17a827af5c8921b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1485. -- 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/1485#event-1702963363 ----==_mimepart_5b331439ca2bb_255c2b17a827af5c8921b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1485.

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

----==_mimepart_5b331439ca2bb_255c2b17a827af5c8921b-- From nobody Tue Jun 26 21:46:58 2018 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 0D5AF130E7A for ; Tue, 26 Jun 2018 21:46:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 m_aTSaAhJpyX for ; Tue, 26 Jun 2018 21:46:55 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD19B126F72 for ; Tue, 26 Jun 2018 21:46:54 -0700 (PDT) Date: Tue, 26 Jun 2018 21:46:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530074814; bh=zsxvDf9q+sEe3ibbTxDebNYLkfjLBTnjXYJG6faDUDw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q0aMQgLGME3jD0WBnjIaYOKrH0BhwHy448rmhoOlm3nbLVJlpZCNFN159htIuOsbU D18gPgms0yFR1IPq+qYzXbwEDr9HyYCEWPor0FARQ+DEoRrHm8PeYANcACRYyINn/S WgvuwHYqHyhBqineNb2tshBvfE6/cLfiT/GjS4wM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3316be3a548_548a3fa6377aef781880c1"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 04:46:57 -0000 ----==_mimepart_5b3316be3a548_548a3fa6377aef781880c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The current design allows for considerable flexibility in routing up until the point that the first Handshake packet commits to a set of connection IDs. Part of that flexibility allows for changing the connection ID. A server could decide to validate changes using the token it passes to clients in Retry packets, if it chose to do so. This could validate the entire sequence of changes, at a modest cost in bytes. The only protection a client has is that packets from Handshake on are authenticated with end-to-end keys. An attacker can't modify these packets. If the client doesn't change its opinion about its connection ID - and it has no reason to do so that I'm aware of - then an attacker can't change the client connection ID value without causing packets to be dropped eventually. The server has the same protection available, though our design allows multiple options for a server to change connection IDs. So the only value that is authenticated is the final value, which might not have been reached honestly if - for example - an attacker has used spoofed Retry packets to route the client to a sub-optimal server instance. If the goal here is to authenticate the chain of connection IDs that are used, starting from the randomized value selected by the client, then it needs to cover more than a single value. -- 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/1486#issuecomment-400541391 ----==_mimepart_5b3316be3a548_548a3fa6377aef781880c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The current design allows for considerable flexibility in routing up u= ntil the point that the first Handshake packet commits to a set of connec= tion IDs. Part of that flexibility allows for changing the connection ID= .

A server could decide to validate changes using the token it passes to= clients in Retry packets, if it chose to do so. This could validate the= entire sequence of changes, at a modest cost in bytes.

The only protection a client has is that packets from Handshake on are= authenticated with end-to-end keys. An attacker can't modify these pack= ets. If the client doesn't change its opinion about its connection ID - = and it has no reason to do so that I'm aware of - then an attacker can't = change the client connection ID value without causing packets to be dropp= ed eventually.

The server has the same protection available, though our design allows= multiple options for a server to change connection IDs. So the only val= ue that is authenticated is the final value, which might not have been re= ached honestly if - for example - an attacker has used spoofed Retry pack= ets to route the client to a sub-optimal server instance.

If the goal here is to authenticate the chain of connection IDs that a= re used, starting from the randomized value selected by the client, then = it needs to cover more than a single value.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3316be3a548_548a3fa6377aef781880c1-- From nobody Tue Jun 26 21:47:57 2018 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 35697128BAC for ; Tue, 26 Jun 2018 21:47:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 yq3FJDgMczf3 for ; Tue, 26 Jun 2018 21:47:53 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A317126F72 for ; Tue, 26 Jun 2018 21:47:53 -0700 (PDT) Date: Tue, 26 Jun 2018 21:47:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530074872; bh=phVSH5fl6a117ZDUH4aXHpWPVyB6Tmu2PqgYxOWMQ5k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i+XHfo8X4qy9UN8QxDneRrdXxPqrSb6ZHmM/Ck/e52rMbw5YLd8yE9NLKUHn3rkSz syYzhCpM97z4yY7YDoX9zgs079V9OSuiQ+2E1lYsnvOVVLeCgcwuOo0NFUl8t3FV+5 RtuAlyAMn3AevCvxUzQi17Hdyt+XgOisR7pRkFVM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Guidance for flow control and ACK of extension frames (#1487) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3316f8e44c5_69dd2af429122f5839326a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 04:47:55 -0000 ----==_mimepart_5b3316f8e44c5_69dd2af429122f5839326a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good idea. We should document what an extension needs to consider in defining a new frame type. -- 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/1487#issuecomment-400541509 ----==_mimepart_5b3316f8e44c5_69dd2af429122f5839326a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Good idea. We should document what an extension needs to consider in defining a new frame type.

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

----==_mimepart_5b3316f8e44c5_69dd2af429122f5839326a-- From nobody Tue Jun 26 21:49:39 2018 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 0C212128BAC for ; Tue, 26 Jun 2018 21:49:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 eloDk3spsAI4 for ; Tue, 26 Jun 2018 21:49:36 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C6D90126F72 for ; Tue, 26 Jun 2018 21:49:36 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530074976; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=wjaGCp0nKZ1hbIbgbdmQnoPUhpw3mngFH8sqnUzK+FU=; b=vZKTwz3nE8TLbgJXC9LNNreyy0StDO8DHDUetS8zMv/zD+UzwtkYTtECpOmHyAVvupLD8B// lL7YVXbCmKkhXNqOKq+gmpaYUqbbx+wA6VHIEhY70utAH7xcI8RBdMBcnuFdxhp4zBIrirSW 06J+JTfqslvuGGeOtNtYht+myms= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b33175f.7fbcd80bc2a0-smtp-out-n03; Wed, 27 Jun 2018 04:49:35 -0000 (UTC) Date: Tue, 26 Jun 2018 21:49:34 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b33175e5b2fd_43d72ac58cd9fc0c985f9@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 65b392: start 102 agenda Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33175e5ad8a_43d72ac58cd9fc0c984d5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 04:49:38 -0000 ----==_mimepart_5b33175e5ad8a_43d72ac58cd9fc0c984d5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 65b3925c3916d89dd5d86e1862949e0591b12456 https://github.com/quicwg/wg-materials/commit/65b3925c3916d89dd5d86e1862949e0591b12456 Author: Mark Nottingham Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: A ietf102/agenda.md Log Message: ----------- start 102 agenda **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33175e5ad8a_43d72ac58cd9fc0c984d5-- From nobody Tue Jun 26 21:51:34 2018 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 21E01128BAC for ; Tue, 26 Jun 2018 21:51:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 UvlKQ0ir_p0v for ; Tue, 26 Jun 2018 21:51:31 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99A40126F72 for ; Tue, 26 Jun 2018 21:51:31 -0700 (PDT) Date: Tue, 26 Jun 2018 21:51:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530075091; bh=MtYjuQo96VoTogJmzZzjPo06zodDjiCJwwpzeBKmOd0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gYNUkFRB16dLIP3M3G3L/1UFY7XGVyJl55pwCk/AkR3dcQe2PiE46o8taAfmoiBY/ w2H9ALO5WXMO/KrIezHGwWoEO5yxhI2lD9hJIMTiGpBLmDqVqYb2EA4kLEyMXsEpK/ 0rp/8KO9Un5IDAtrOy28wEd1ohFPLShf9asmqAEM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3317d2f270d_5e493fc6c88b8f8493638"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 04:51:34 -0000 ----==_mimepart_5b3317d2f270d_5e493fc6c88b8f8493638 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah, I think that we'd want to retain the "SHOULD", but we might expand this to mention that gaps are generally only OK in the case where the corresponding sequence number was used on a dead path (or because you don't want to count backwards from zero to account for the handshake and server preferred address). -- 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/1484#issuecomment-400541961 ----==_mimepart_5b3317d2f270d_5e493fc6c88b8f8493638 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yeah, I think that we'd want to retain the "SHOULD", but we might expa= nd this to mention that gaps are generally only OK in the case where the = corresponding sequence number was used on a dead path (or because you don= 't want to count backwards from zero to account for the handshake and ser= ver preferred address).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3317d2f270d_5e493fc6c88b8f8493638-- From nobody Tue Jun 26 22:00:59 2018 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 5F18B130DC4 for ; Tue, 26 Jun 2018 22:00:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 baxRVbB_HDzm for ; Tue, 26 Jun 2018 22:00:56 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 118ED126F72 for ; Tue, 26 Jun 2018 22:00:55 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530075655; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=uwV5i+bOwux5+F+0BxdYbxKaU3Oc/RSdGNz5GBhnKJw=; b=g9oy7PHOGSn0SDqk9crP8eoOSDVjjMAAo6opdmRtRE8T4vABjUX5fGEx77ZJV6pcUfZMxneq gVqJNxbTLEc0ZLGSKGsqXxqGhfY2bqYvQA3zcTx9PKX0sXH+1kg7FwZw7G3QakI+6TzC0YGC K2WwMJtWIdWa5Mo5YWoIcc80gLY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b331a06.7f5d1e97b330-smtp-out-n03; Wed, 27 Jun 2018 05:00:54 -0000 (UTC) Date: Tue, 26 Jun 2018 22:00:54 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b331a069d0ea_163e2acc0c7c3c083647a@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b331a069c9ff_163e2acc0c7c3c083631d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 05:00:58 -0000 ----==_mimepart_5b331a069c9ff_163e2acc0c7c3c083631d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/hs-error Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b331a069c9ff_163e2acc0c7c3c083631d-- From nobody Tue Jun 26 22:06:18 2018 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 6EB13130DC4 for ; Tue, 26 Jun 2018 22:06:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mArXbFAUOHWB for ; Tue, 26 Jun 2018 22:06:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40DB1126F72 for ; Tue, 26 Jun 2018 22:06:14 -0700 (PDT) Date: Tue, 26 Jun 2018 22:06:12 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530075972; bh=OtNE3Z0VexTXGIRJe2MWtHdazJ+ijs9TN/5v6yJdakc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eQWd+XNVogZyIM2wT2px6vosXI3Rt0c/kZ0hamBRuu2u9177C6a2I7bDaQhEBbZtg VKO9/MdeTBMYj4YT2vPWJsMG2NDEG3fa/X9diDLTn6oYLAusxQc66gucPCDd4y+tN0 xQdvCRwseE3ZEPi/47+h8YmOxG4BInVSYMFdkbbU= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b331b443472a_13152ac5ea0d4f5064783"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 05:06:17 -0000 ----==_mimepart_5b331b443472a_13152ac5ea0d4f5064783 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > The current design allows for considerable flexibility in routing up until the point that the first Handshake packet commits to a set of connection IDs. Part of that flexibility allows for changing the connection ID. > > A server could decide to validate changes using the token it passes to clients in Retry packets, if it chose to do so. My point is that it cannot. Consider the following case: * a middlebox intercepts the 1st Initial, drops it, and sends back a Retry that contains a 8-octet SCID field that has the value that the middlebox wants * client sends an Initial packet with the updated server CID and token found in the Retry * the middlebox trims the Retry field, re-obfuscates the Initial packet and forwards it to the server The initial packet being altered by a middlebox will look as if it was a Initial packet without a token sent from a client. A server cannot tell if the Destination CID field of the Initial packet was generated by the client or by a middlebox. -- 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/1486#issuecomment-400543918 ----==_mimepart_5b331b443472a_13152ac5ea0d4f5064783 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The current design allows for considerable flexibility in routing up u= ntil the point that the first Handshake packet commits to a set of connec= tion IDs. Part of that flexibility allows for changing the connection ID.=

A server could decide to validate changes using the token it passes to= clients in Retry packets, if it chose to do so.

My point is that it cannot.

Consider the following case:

  • a middlebox intercepts the 1st Initial, drops it, and sends back a Re= try that contains a 8-octet SCID field that has the value that the middle= box wants
  • client sends an Initial packet with the updated server CID and token = found in the Retry
  • the middlebox trims the Retry field, re-obfuscates the Initial packet= and forwards it to the server

The initial packet being altered by a middlebox will look as if it was= a Initial packet without a token sent from a client. A server cannot tel= l if the Destination CID field of the Initial packet was generated by the= client or by a middlebox.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b331b443472a_13152ac5ea0d4f5064783-- From nobody Tue Jun 26 22:32:46 2018 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 1776F130F0D for ; Tue, 26 Jun 2018 22:32:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 jOB--63Zammz for ; Tue, 26 Jun 2018 22:32:43 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B81F130E85 for ; Tue, 26 Jun 2018 22:32:43 -0700 (PDT) Date: Tue, 26 Jun 2018 22:32:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530077562; bh=tkiIlOBHw2rK4+2YgWp/t6h42fVQxDoXQK6/RpFDRZE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j5r36ND2Xjf7t24kNTGu27r3Adwz+PPdJQmguVtEcKI/dAVKsLYuEHn6DoPCxK2kT JDPZ2hNNiS7kdQGjhv2AXCUesGwAuUTSxyEoV4uB1mzRjTO9CN8t4Zo4qBZvaE5T/o 6rmHEzz4SHDrhR4zeASBAW/7XOKlWvPOwukDAkQs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN echo in ACK frame or as separate frame (#804) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33217a91483_72cc3fafc68f6f782340b0"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:32:46 -0000 ----==_mimepart_5b33217a91483_72cc3fafc68f6f782340b0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #804. -- 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/804#event-1703010669 ----==_mimepart_5b33217a91483_72cc3fafc68f6f782340b0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #804.

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

----==_mimepart_5b33217a91483_72cc3fafc68f6f782340b0-- From nobody Tue Jun 26 22:32:52 2018 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 AA50D130EC5 for ; Tue, 26 Jun 2018 22:32:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6OGUx86oZ7Ep for ; Tue, 26 Jun 2018 22:32:45 -0700 (PDT) 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 12572130EF3 for ; Tue, 26 Jun 2018 22:32:44 -0700 (PDT) Date: Tue, 26 Jun 2018 22:32:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530077563; bh=fpZDXe3f3iDc7ryytt6r8u9G6M2R1F3CbbWtB1L/ano=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2F0NkV+fjwBbQdlwfF8yRWOLwxS7gUVI4qai5yJjYdq0D5hXSdJD9bqd51Ki5Dn1s PU7Sswhwosc+V1wxg7au6uJrVUv1KV/xqo0LKqYTg86Il9npvA784h2nO+hguzErC8 NClo4Ea9m7S8SpdLZDFecWZlkB6yoZ9FkgMTmt4Y= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN echo in ACK frame or as separate frame (#804) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33217b3eb7f_67212b23f374af581542f3"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:32:47 -0000 ----==_mimepart_5b33217b3eb7f_67212b23f374af581542f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed by #1372. -- 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/804#issuecomment-400547817 ----==_mimepart_5b33217b3eb7f_67212b23f374af581542f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed by #1372.

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

----==_mimepart_5b33217b3eb7f_67212b23f374af581542f3-- From nobody Tue Jun 26 22:32:59 2018 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 8A8D4130E85 for ; Tue, 26 Jun 2018 22:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mTKUR2BRKk_j for ; Tue, 26 Jun 2018 22:32:56 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467F4130EC5 for ; Tue, 26 Jun 2018 22:32:56 -0700 (PDT) Date: Tue, 26 Jun 2018 22:32:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530077575; bh=wKAm2Km3wlsUeXAhpgqGOvNoFKTy/hg2QY4YVf9IXbM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uwu2kQ3rNkhDbYh92r6VefD7R2MzE78kW2/O1FVlBSyVASMWfFMr5FSOEVJuxSgT2 gIjz+6EECUzVNutRMNav4aWlhJ2f+lqC73PAbeAYWPSvas/HfWXOYgYH9RVmd2aPSh hoIy800bHPMQgwm2G/E+48vIwHda/xGiCcMnJepU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN echo encoding, detailed packet level or ECN marked bytes (#805) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332187a9f67_661a3fe475c40f8893764"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:32:58 -0000 ----==_mimepart_5b332187a9f67_661a3fe475c40f8893764 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed by #1372. -- 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/805#issuecomment-400547856 ----==_mimepart_5b332187a9f67_661a3fe475c40f8893764 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed by #1372.

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

----==_mimepart_5b332187a9f67_661a3fe475c40f8893764-- From nobody Tue Jun 26 22:33:10 2018 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 AE707130F39 for ; Tue, 26 Jun 2018 22:33:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 jUsYP6FDHkJA for ; Tue, 26 Jun 2018 22:32:57 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A86BB130EC5 for ; Tue, 26 Jun 2018 22:32:57 -0700 (PDT) Date: Tue, 26 Jun 2018 22:32:56 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530077576; bh=Uocj7cVhdpg/rP4RjuA2giV0ohyjKEZoSKM837a3clk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2WWZJwFP1vHL/IjqgK+bv5K8qBK5+h7d7lFK8pd4YN73V4yLzzi5vH3oiTEvgJ+Sf /iNCDFw+REhfn/RSNOiOOXCpciRhxSGgGEXZlau7eBpCUizbvVxf+fvyPt4N+pYcXF 5XUszOZh03qADT5Zmop3JpDuyAXSVIXEZybOlAeM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ECN echo encoding, detailed packet level or ECN marked bytes (#805) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332188d9043_18123f7e83018f88290825"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:33:02 -0000 ----==_mimepart_5b332188d9043_18123f7e83018f88290825 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #805. -- 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/805#event-1703010923 ----==_mimepart_5b332188d9043_18123f7e83018f88290825 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #805.

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

----==_mimepart_5b332188d9043_18123f7e83018f88290825-- From nobody Tue Jun 26 22:59:46 2018 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 08FC6130F32 for ; Tue, 26 Jun 2018 22:59:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 vdNRYU-8g_yh for ; Tue, 26 Jun 2018 22:59:42 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 619CC130E85 for ; Tue, 26 Jun 2018 22:59:42 -0700 (PDT) Date: Tue, 26 Jun 2018 22:59:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530079181; bh=Xi+FXw1PLJ0Zn3lzWQhC9CI2GEaUDfaUYs4pjhN02EI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q5Vwv7ZsyjQWYAoLwptiLCXAAl2m6DQWmjIzR196HksFH6gVv4OWerUyhS30BgHvX 9HW83p2yI1YKqR8Umyq9ck/3DOP/ubFRbic/jjf2IruNb//4P3KpSAVI7XetEtqCYU UzLn/47KO9OaHoeHIsm6BN7EAM+tgOG/9/8o4g3o= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] tls: fix citation format (#1478) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3327cd77a2e_19683fb75f254f805825bc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:59:44 -0000 ----==_mimepart_5b3327cd77a2e_19683fb75f254f805825bc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixed as part of other changes. -- 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/1478#issuecomment-400552176 ----==_mimepart_5b3327cd77a2e_19683fb75f254f805825bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixed as part of other changes.

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

----==_mimepart_5b3327cd77a2e_19683fb75f254f805825bc-- From nobody Tue Jun 26 22:59:54 2018 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 3EE83130E85 for ; Tue, 26 Jun 2018 22:59:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 pizoNE9NFweX for ; Tue, 26 Jun 2018 22:59:43 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 746E3130F23 for ; Tue, 26 Jun 2018 22:59:43 -0700 (PDT) Date: Tue, 26 Jun 2018 22:59:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530079182; bh=oTfI6pEKqM1WmVU72VsZZoYXGJdeRFBbG+yQ2vLOoPs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d1NnccHrQBvV5hpKhPrBdVMLA91pFMtTykYiZnDLbwFG4YlZhqz5K1+bqCoMtiNLW jRs5S7xQapVuJk0A9p0ddV1tI2vqI0hT6L182mek31uZEZcD9Q1l4gcazpIzVw3uwy gdYt4v2qfqC+LdvrxLy+E4zjeZcVcCwJWn8bQNEQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] tls: fix citation format (#1478) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3327ce5421b_65373fef47482f802953c6"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 05:59:45 -0000 ----==_mimepart_5b3327ce5421b_65373fef47482f802953c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1478. -- 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/1478#event-1703039381 ----==_mimepart_5b3327ce5421b_65373fef47482f802953c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1478.

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

----==_mimepart_5b3327ce5421b_65373fef47482f802953c6-- From nobody Tue Jun 26 23:01:31 2018 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 9AB7C130F32 for ; Tue, 26 Jun 2018 23:01:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 N1L6zfcHQ1JF for ; Tue, 26 Jun 2018 23:01:26 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 6B997130E85 for ; Tue, 26 Jun 2018 23:01:26 -0700 (PDT) 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=HkoUQJEV/M7BqN+soqyMpLOUv9k=; b=eS7LUQJK9u6zEfct uk0HEsZLvq0z8zARpu2jGDKs+aPx7ckl3lqY+jcxezad7edh/oXA6Pb3FWUYyXRy scMas/iuiEKR8S5G4vz58koAquZYuYZYjx7Y/aslH4hLhSvBuFES8yeYHtlb1op/ 23uAGSblf7sgDRjjz6d7Pg7gIKc= Received: by filter0364p1iad2.sendgrid.net with SMTP id filter0364p1iad2-29116-5B332835-13 2018-06-27 06:01:25.519122227 +0000 UTC Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id TydVwWEpSbi-xRgmbREZMQ for ; Wed, 27 Jun 2018 06:01:25.459 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id 6EFF240E6A for ; Tue, 26 Jun 2018 23:01:25 -0700 (PDT) Date: Wed, 27 Jun 2018 06:01:25 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3328356dc4b_19373fb75f254f8032512d"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3QDr99UwhAVW/FOQCRRq4+itwQSkMgDjSSnI IOUiMcaBSWsjoDTXoE3KtOPLC3GxRRz5J0sGaZFYE69Z6c5uXLyc1d73Xbh5z7eS79vN4XETaczqYj pLtt/hBRO1jnbV7somRVHkRUWmmtKModiZF58BZX2pGRhG7XcUHht2/JTabXPnke1NqngDysCzdQNy E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:01:29 -0000 ----==_mimepart_5b3328356dc4b_19373fb75f254f8032512d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ahh, though it's only the first one, that might be enough. Not sure how much this matters, but we should do something, even if that is only write this down. -- 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/1486#issuecomment-400552508 ----==_mimepart_5b3328356dc4b_19373fb75f254f8032512d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Ahh, though it's only the first one, that might be enough. Not sure how much this matters, but we should do something, even if that is only write this down.

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

----==_mimepart_5b3328356dc4b_19373fb75f254f8032512d-- From nobody Tue Jun 26 23:04:33 2018 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 8A226130F32 for ; Tue, 26 Jun 2018 23:04:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 Lz1eNC7Eco8k for ; Tue, 26 Jun 2018 23:04:30 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 19753130F23 for ; Tue, 26 Jun 2018 23:04:29 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530079469; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=E6Zb56Flklqm++aCIyzo4Dx+U6fTXcL2Duw5zXdGVbE=; b=iiTm7Em/bEBAvY8kiwwEZfctcOEPuhny1q/dE1UHrZbxpibbwAwY4qTq7wHCKWXNkxO5iSRS GIWURI7u7rHR/GpxXis2T3PyGedOblmBSMHeFhxWWO4NOEUQyp8hDZIvl3pLZz4pTIFaA0fl MlmsxKP4j/Rsd7d03gMLa0WySrI= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b3328ed.7f86d7baade0-smtp-out-n03; Wed, 27 Jun 2018 06:04:29 -0000 (UTC) Date: Tue, 26 Jun 2018 23:04:29 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3328ed1a971_11a62b0acc6cfc084765d@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 89a889: Added change logs Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3328ed1a407_11a62b0acc6cfc08475d1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:04:32 -0000 ----==_mimepart_5b3328ed1a407_11a62b0acc6cfc08475d1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/changelog-13 Home: https://github.com/quicwg/base-drafts Commit: 89a889049d2f78bdcdf4f0beb745b91d4c79c770 https://github.com/quicwg/base-drafts/commit/89a889049d2f78bdcdf4f0beb745b91d4c79c770 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Added change logs **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3328ed1a407_11a62b0acc6cfc08475d1-- From nobody Tue Jun 26 23:06:00 2018 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 769CA130F23 for ; Tue, 26 Jun 2018 23:05:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1cVCqa7cwRIZ for ; Tue, 26 Jun 2018 23:05:56 -0700 (PDT) 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 A5988130E85 for ; Tue, 26 Jun 2018 23:05:56 -0700 (PDT) Date: Tue, 26 Jun 2018 23:05:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530079555; bh=unxQ+hRVBCPGaOpnj8FZ0qcmjAmd75qyTZ0DK+xK3+E=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=fsNGrbDMX8QYAWGwWljANrKIRxd7S/eKoT5+3LGJb+OFqNY15f8oU62Kps/RumvJR R3zt6mT3Xv5gMZ1iBw1FYd8TlYprjGo5nPi2yYDwtEaBteECLAeuOkUCs8eMDN3Y2C DYa7s8WHNn7KYlIFHuo6nQLCfBHGHHvsitw/B9FY= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332943ec79f_11dac3fc48b78cf7824548a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:05:59 -0000 ----==_mimepart_5b332943ec79f_11dac3fc48b78cf7824548a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit These are big, so I would appreciate a second pair of eyes. That gives @MikeBishop a chance to fixup #1359, which I would like to see in -13 (let's concentrate all the large changes on the one version). You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1488 -- Commit Summary -- * Added change logs -- File Changes -- M draft-ietf-quic-http.md (9) M draft-ietf-quic-qpack.md (8) M draft-ietf-quic-recovery.md (7) M draft-ietf-quic-tls.md (10) M draft-ietf-quic-transport.md (32) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1488.patch https://github.com/quicwg/base-drafts/pull/1488.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/1488 ----==_mimepart_5b332943ec79f_11dac3fc48b78cf7824548a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

These are big, so I would appreciate a second pair of eyes. That gives @MikeBishop a chance to fixup #1359, which I would like to see in -13 (let's concentrate all the large changes on the one version).

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

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

Commit Summary

  • Added change logs

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 mute the thread.

----==_mimepart_5b332943ec79f_11dac3fc48b78cf7824548a-- From nobody Tue Jun 26 23:12:15 2018 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 95A02130F35 for ; Tue, 26 Jun 2018 23:12:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 FPD3PCwgjLom for ; Tue, 26 Jun 2018 23:12:11 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 672CE130E85 for ; Tue, 26 Jun 2018 23:12:11 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530079930; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=MRC5lUX0hbpizlWvyUIiVojT9u83d7IFIqBVAW6iJXk=; b=dBTk2+pL81Uzcv8HlTrtCCUR5dNBwTvMrp763E5xArRaR5RDqEST4veinwk8rk/f9Ix4gyFo Wu0GhEo2hQxHMDgCg5z/eRcHWb0ZfCM8f6SMqBvRUdbF0W7aOm4a/FSzu/D8/vcrPt0spWsA FW95BqlrSfk2RHzxtRbkQRUq+sA= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b332ab9.7f0b6c669e70-smtp-out-n02; Wed, 27 Jun 2018 06:12:09 -0000 (UTC) Date: Tue, 26 Jun 2018 23:12:08 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b332ab8cebcb_44e82ad7592f9bfc741f9@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 42b394: Correct packet number example Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b332ab8ce47b_44e82ad7592f9bfc74010"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:12:13 -0000 ----==_mimepart_5b332ab8ce47b_44e82ad7592f9bfc74010 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/pn-example Home: https://github.com/quicwg/base-drafts Commit: 42b394e7ba93753ee6d08d682ad87f1bf49f961b https://github.com/quicwg/base-drafts/commit/42b394e7ba93753ee6d08d682ad87f1bf49f961b Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Correct packet number example Thanks to Masakazu Kitajo for catching the error. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b332ab8ce47b_44e82ad7592f9bfc74010-- From nobody Tue Jun 26 23:12:26 2018 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 548AC130E85 for ; Tue, 26 Jun 2018 23:12:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4R8V7A0nHAkD for ; Tue, 26 Jun 2018 23:12:23 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B2A7130E80 for ; Tue, 26 Jun 2018 23:12:23 -0700 (PDT) Date: Tue, 26 Jun 2018 23:12:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530079942; bh=GMKu9hj6el1LmS2LWL4Ub4SUHVYpSNBqfhAAxKOr3tI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=t49uca0pL/a0TUzPIu7kHodaNYs1beX1PKgGvJIqx9JfP+NUM/zh4EV+C/A2EUbtY tMnRskCdgW99iG8+5hxBoz2gnhRLJx63jppLwWCwMDmaeDhF1nJbvrlFlg+eI8QVHo oeuOilQ57f3nHWvKFxXYDqibJl8EbDlRauy5SFjQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Correct packet number example (#1489) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332ac67567a_39fa2af097840f502474e9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:12:26 -0000 ----==_mimepart_5b332ac67567a_39fa2af097840f502474e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks to Masakazu Kitajo for catching the error. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1489 -- Commit Summary -- * Correct packet number example -- File Changes -- M draft-ietf-quic-transport.md (4) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1489.patch https://github.com/quicwg/base-drafts/pull/1489.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/1489 ----==_mimepart_5b332ac67567a_39fa2af097840f502474e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks to Masakazu Kitajo for catching the error.

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

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

Commit Summary

  • Correct packet number example

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 mute the thread.

----==_mimepart_5b332ac67567a_39fa2af097840f502474e9-- From nobody Tue Jun 26 23:14:22 2018 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 EAE0C130E85 for ; Tue, 26 Jun 2018 23:14:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 j75NA3lNPTVq for ; Tue, 26 Jun 2018 23:14:18 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 949E1130E80 for ; Tue, 26 Jun 2018 23:14:18 -0700 (PDT) Date: Tue, 26 Jun 2018 23:14:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530080057; bh=ZME2eJ00r6il3jOqezeP+hmvSL8VUjxH11eFw5X55A8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C8Vc8s0t2IbMjgVtG6nNGA9R6PcCvH8zTX+owVsnQ17TM1mvmjHCHInP42/WVZwpb 9HmK6uw67C90E6CxpJXZHbjR6LHt5vxZKiYEPJPm01s1Q07LEt3oIHjOLGeDEWNeS7 Isnae0tbJjIssdD2FjBq++GOnkOo0T5tuSunYuL4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define a mechanism for negotiating extensions (#1072) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332b39c7aad_11daf3fc48b78cf7825952e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:14:21 -0000 ----==_mimepart_5b332b39c7aad_11daf3fc48b78cf7825952e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have a mechanism for frame extensions now. -- 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/1072#issuecomment-400554761 ----==_mimepart_5b332b39c7aad_11daf3fc48b78cf7825952e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have a mechanism for frame extensions now.

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

----==_mimepart_5b332b39c7aad_11daf3fc48b78cf7825952e-- From nobody Tue Jun 26 23:14:29 2018 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 3E0DC130E85 for ; Tue, 26 Jun 2018 23:14:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 yDwd7yO-v7rl for ; Tue, 26 Jun 2018 23:14:20 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E750130E80 for ; Tue, 26 Jun 2018 23:14:20 -0700 (PDT) Date: Tue, 26 Jun 2018 23:14:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530080060; bh=yPwCuNj1iiZ6TBWoKF0af8l1Wu3Btc73KdZAB90vvR4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U7NpMRZaS6PrANzQL+c+/3PI2NWDkSt0SvcaorHGmjx5RoalVl+ZEpmJGG1mQxNax +WoJ+Z3b4G3jahlISzmMTwbNywzudmVeiwz5XT7qZUeN8ZYNdUNtQxwVwrzsOs9JM8 ygvS5l3OuR2J6iDR31lJ4xv/nlCDCr7sTp76lDCE= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define a mechanism for negotiating extensions (#1072) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332b3bf168e_2ef52af0a2112f5c25958a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:14:23 -0000 ----==_mimepart_5b332b3bf168e_2ef52af0a2112f5c25958a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1072. -- 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/1072#event-1703056651 ----==_mimepart_5b332b3bf168e_2ef52af0a2112f5c25958a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1072.

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

----==_mimepart_5b332b3bf168e_2ef52af0a2112f5c25958a-- From nobody Tue Jun 26 23:14:43 2018 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 C95D9130F36 for ; Tue, 26 Jun 2018 23:14:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jaeThFV9v8Pw for ; Tue, 26 Jun 2018 23:14:40 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2816D130E85 for ; Tue, 26 Jun 2018 23:14:40 -0700 (PDT) Date: Tue, 26 Jun 2018 23:14:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530080079; bh=9Pp/dxI240DJ8uWHKzMTf2t8iicNvmHgPMmsEC0JupE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oTtblWtF8ayeB9uKfJfFQqbrwiP3JR4cPlKpQ0+Fpcc3DE+gJwSAJ8ekjSusbgrLR gTiPxYRtnMCEENdxSs/fn4jBLluPboFAfe5gLo9itD5MGiGepJqo9x6DTCaZPbTh+S 8Ou3XvBQcpY3pAon1UmDcQZggiFX06NQWQqLHO2A= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Troubleshooting flags in public header (#418) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332b4f7e7aa_38062aba76a7af5c15118b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:14:42 -0000 ----==_mimepart_5b332b4f7e7aa_38062aba76a7af5c15118b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is so badly bitrotten, that I think we need to start over if we get back to this. -- 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/418#issuecomment-400554870 ----==_mimepart_5b332b4f7e7aa_38062aba76a7af5c15118b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is so badly bitrotten, that I think we need to start over if we get back to this.

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

----==_mimepart_5b332b4f7e7aa_38062aba76a7af5c15118b-- From nobody Tue Jun 26 23:14:51 2018 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 AFCDB130E85 for ; Tue, 26 Jun 2018 23:14:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 DqPw9BBIA56X for ; Tue, 26 Jun 2018 23:14:40 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28BF7130F35 for ; Tue, 26 Jun 2018 23:14:40 -0700 (PDT) Date: Tue, 26 Jun 2018 23:14:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530080079; bh=fMrNQN+TOLeyjgDlo74CFQKT6D6N+uNKqzvOBE3+FIo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=potdgnJeEGS4nC1r4LcHadDrJhNWDY7uhmOlNIBqnsbzZm5/2gsSLXPvMm+WurCeq TA8izVOa18kw2Gtn4tZlnyE++CKmhyS+ZcIKIHYHcbeBJF/DNyfM3Yv4dEaxSFnOAN lW6gXyDUdHM+ubTNXOYx+ayPr/evfnqEC55bysDM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Troubleshooting flags in public header (#418) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b332b4f8493e_59fb3f8c4fcbef88438311"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:14:44 -0000 ----==_mimepart_5b332b4f8493e_59fb3f8c4fcbef88438311 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #418. -- 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/418#event-1703057586 ----==_mimepart_5b332b4f8493e_59fb3f8c4fcbef88438311 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #418.

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

----==_mimepart_5b332b4f8493e_59fb3f8c4fcbef88438311-- From nobody Tue Jun 26 23:37:52 2018 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 3D432130F36 for ; Tue, 26 Jun 2018 23:37:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 O1teuO7RRK5R for ; Tue, 26 Jun 2018 23:37:49 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 DB7DE130E80 for ; Tue, 26 Jun 2018 23:37:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530081468; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=l2d7k0b4zNBsB7Qhn891LVNyKAWQqZZrYYRJAviQY9o=; b=IEryIgYT1wjK0ZWRiO5QKvnirTp6tyX5dgd3ibX70++5Q6/MXcjAAZ1LtXm2LW4EGhvuLeG0 JEHknakp5tutpg2fhR2tShv1hgjQ0f/2cECTXeybt+5YXACJiGDq0sx/OW+BpdP0YFLqOOFk fUg8zBmeHDnSvZvblVIlQGdd/m8= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b3330bb.7f8e1157bf00-smtp-out-n02; Wed, 27 Jun 2018 06:37:47 -0000 (UTC) Date: Tue, 26 Jun 2018 23:37:47 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3330bbb1eea_63f92b16e4af3c0c88928@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] d7d2d3: Fix example Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3330bbb173c_63f92b16e4af3c0c8883f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:37:51 -0000 ----==_mimepart_5b3330bbb173c_63f92b16e4af3c0c8883f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/pn-example Home: https://github.com/quicwg/base-drafts Commit: d7d2d3f0340bfb6d96c9ddf01046b1c5ad317a74 https://github.com/quicwg/base-drafts/commit/d7d2d3f0340bfb6d96c9ddf01046b1c5ad317a74 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Fix example **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3330bbb173c_63f92b16e4af3c0c8883f-- From nobody Tue Jun 26 23:37:59 2018 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 66B38130F4C for ; Tue, 26 Jun 2018 23:37:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 oDWMxicVKMxc for ; Tue, 26 Jun 2018 23:37:51 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13719130E80 for ; Tue, 26 Jun 2018 23:37:51 -0700 (PDT) Date: Tue, 26 Jun 2018 23:37:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530081470; bh=/WDobGOBKgpLJIggelgSylRtvSF0GCFD14gftzZIJyo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OVOqhb8Sek7E9DDTaAHmTLjaSsTz56IfGUun9z3OZvUrwbTxdtYPD44hNGqPfnxJT hQ7xoTvrDVL0TU+I/DxosQCV4TS9B5vRX/Q3ITKMvgjRdElEzGlCPr4V8DlVEZbkpA 1NJnet9HohJQIffgKPvWmBlj2ZX+YFnqYWBD7pdU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Correct packet number example (#1489) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3330be570d3_37202aae943c8f586122e4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 06:37:54 -0000 ----==_mimepart_5b3330be570d3_37202aae943c8f586122e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. d7d2d3f Fix example -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1489/files/42b394e7ba93753ee6d08d682ad87f1bf49f961b..d7d2d3f0340bfb6d96c9ddf01046b1c5ad317a74 ----==_mimepart_5b3330be570d3_37202aae943c8f586122e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3330be570d3_37202aae943c8f586122e4-- From nobody Tue Jun 26 23:39:20 2018 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 8D208130E80 for ; Tue, 26 Jun 2018 23:39:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 8nzKZN4-Fn5M for ; Tue, 26 Jun 2018 23:39:15 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 906C7129385 for ; Tue, 26 Jun 2018 23:39:15 -0700 (PDT) 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=ZY3vIznloY/0eSKnRMgBzhT2yVM=; b=txrwyHm+D3pcan7A T/rf/lB/ckZGgytGoeNPDcRZST/d8/80CVL6KUY+2Hmi7H7PBLzhVGzBDwo5sIgm OncpC3Uyf+LAnHwTRMNluQB79STAuD2z0d2Sn7vwmX7kbXdrRALC24cCo4pnEO4N Wp/PkZL2KhYyAHlBGRfyRVSJoQs= Received: by filter0307p1iad2.sendgrid.net with SMTP id filter0307p1iad2-24862-5B333112-5 2018-06-27 06:39:14.282969582 +0000 UTC Received: from github-lowworker-5909e27.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 1nsnHD93TyOh8xkNz5eoNw for ; Wed, 27 Jun 2018 06:39:14.277 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-5909e27.cp1-iad.github.net (Postfix) with ESMTP id 41F9F3E0083 for ; Tue, 26 Jun 2018 23:39:14 -0700 (PDT) Date: Wed, 27 Jun 2018 06:39:14 +0000 (UTC) From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b333112404f0_399c2af097840f5027636"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1eXU6+A/2TcLKj4NrL2VAFfSL7XRIbwsIStv w9/K6KmvStiJSX9GzFZMwKTWgrEPidLNUqKqUwoB2V9OFURMiWTPwTDrKtFqAKX9Scaht54qjS9M0i w5WTe7gL/lZ5cR9AUxIwMR/WmhctN49dh1CimWJ81S7R7BfNgtcqbT/EZmQCWTHS5zvltH1u26cXGI k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:39:18 -0000 ----==_mimepart_5b333112404f0_399c2af097840f5027636 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 6802896 Dirty edit buffer had a few more things in it -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1488/files/89a889049d2f78bdcdf4f0beb745b91d4c79c770..6802896796a2114977c4215a47160eb1efffd351 ----==_mimepart_5b333112404f0_399c2af097840f5027636 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

  • 6802896 Dirty edit buffer had a few more things in it

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b333112404f0_399c2af097840f5027636-- From nobody Tue Jun 26 23:42:31 2018 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 0587A12F1AC for ; Tue, 26 Jun 2018 23:42:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 35z0VxC8LVT5 for ; Tue, 26 Jun 2018 23:42:29 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 D5BF2129385 for ; Tue, 26 Jun 2018 23:42:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530081748; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=xZeHQHqooHkqBpmlJFHYeYUWWKJKXBtXma3HAsxTVzo=; b=c4A1KDVKE3xL8fWiSRCy2ipdGJuVVK1ap/AeL/GgsVxBhoMlCjSaej3orsuy171Zbsbl4hBN BjBVrtRd2+nTTaMp5EtSKl9P8l7Rb5D8VZcp+UzhX4zwFOOGdERsdntY6gSoW7nucTZMYSRV TbuZUiW1WSJ60tDmy22cyZ+Xb8c= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3331d3.7f8cb8062210-smtp-out-n01; Wed, 27 Jun 2018 06:42:27 -0000 (UTC) Date: Tue, 26 Jun 2018 23:42:26 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b3331d29d278_63d32ac8c7d5dc10105227@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3331d29cea9_63d32ac8c7d5dc10105175"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:42:30 -0000 ----==_mimepart_5b3331d29cea9_63d32ac8c7d5dc10105175 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/pn-example Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3331d29cea9_63d32ac8c7d5dc10105175-- From nobody Tue Jun 26 23:48:59 2018 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 D312B130F30 for ; Tue, 26 Jun 2018 23:48:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 zJqhF-DC2tlt for ; Tue, 26 Jun 2018 23:48:56 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 5394A129385 for ; Tue, 26 Jun 2018 23:48:56 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530082135; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=N2UDoG94Kn4drwhCBUze38MuiFOHyBv/FfM4VFrHqqw=; b=NE5lOBZ5l2ftpGMfuI9B/i35U2wE4waHwWr80d+ppBD0peGvQEps47X9Y7SfP3J6C22X4Lpg 8DGvlyloTigUsh5szn07a6rvMSLMXSXdqOf4DYmULqNlIIWwPm3fnh6GHpdxlZS9vOHsDpZ1 minaF4UlcOfKxM0oN07mlR+KlSY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3330fe.7f82c03bf990-smtp-out-n03; Wed, 27 Jun 2018 06:38:54 -0000 (UTC) Date: Tue, 26 Jun 2018 23:38:53 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3330fdc3130_142b2af9f0b97c14193fb@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 680289: Dirty edit buffer had a few more things in it Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3330fdc2d37_142b2af9f0b97c1419229"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:48:58 -0000 ----==_mimepart_5b3330fdc2d37_142b2af9f0b97c1419229 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/changelog-13 Home: https://github.com/quicwg/base-drafts Commit: 6802896796a2114977c4215a47160eb1efffd351 https://github.com/quicwg/base-drafts/commit/6802896796a2114977c4215a47160eb1efffd351 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Dirty edit buffer had a few more things in it **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3330fdc2d37_142b2af9f0b97c1419229-- From nobody Tue Jun 26 23:53:31 2018 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 E3180130F36 for ; Tue, 26 Jun 2018 23:53:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 4OEaArdkeDWd for ; Tue, 26 Jun 2018 23:53:27 -0700 (PDT) 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 86DA2129385 for ; Tue, 26 Jun 2018 23:53:27 -0700 (PDT) Date: Tue, 26 Jun 2018 23:53:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530082406; bh=kIiP1aykN8V1Tw1ZqtV2TXmM4QLSynnujERytT95ZPo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WgpWvpyl5DV91JZpMwGhP9MTZGmb9fesW2hF8//M0gPrTsNr4UIma2ON68dkf21yO rrt9NxF9C7UzzQLyZ46nxnNY4AyFMK7OI8sygpj8SbkD2bXWJp6w0SkT4ByXzREFr/ xYBKEW7U+V7PWmdzC/T9Y3We4erEvz6KaURcPE2s= From: Masakazu Kitajo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Correct packet number example (#1489) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b333466a3cd2_1b8b3fe0f261cf847373a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: maskit 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.26 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: Wed, 27 Jun 2018 06:53:29 -0000 ----==_mimepart_5b333466a3cd2_1b8b3fe0f261cf847373a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit maskit approved this pull request. The new example values looks correct to me. -- 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/1489#pullrequestreview-132303803 ----==_mimepart_5b333466a3cd2_1b8b3fe0f261cf847373a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@maskit approved this pull request.

The new example values looks correct to me.

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

----==_mimepart_5b333466a3cd2_1b8b3fe0f261cf847373a-- From nobody Tue Jun 26 23:57:02 2018 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 4FA4A129385 for ; Tue, 26 Jun 2018 23:56:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 fTdSHYMVO0kg for ; Tue, 26 Jun 2018 23:56:44 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 B73D4130F36 for ; Tue, 26 Jun 2018 23:56:44 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530082604; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Be9g8ieU3fdHyeZIdUmNOuN0fKnSpFujS87GnduuJkg=; b=CW0xoTmdKtNjvls0j8Cq6qCfPnXDS3B6EpNc1GF1CBmEmbrrSxSmeaVrh96xWmnIJlA9O4bj QETWZooS1QG66uzDF+lRugNu0e4ihv6J9pzy+i7dyhMCT6Rtsy4cr4qLF49F8IfxIFhGuPn3 hyYIYJ8DNAveCK+oUm2/BURQj9I= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b33352b.7f1689581ed0-smtp-out-n01; Wed, 27 Jun 2018 06:56:43 -0000 (UTC) Date: Tue, 26 Jun 2018 23:56:42 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b33352abef2b_41b42adefcfb5bfc10186e@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 42b394: Correct packet number example Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33352abeba5_41b42adefcfb5bfc1017f2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:56:47 -0000 ----==_mimepart_5b33352abeba5_41b42adefcfb5bfc1017f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 42b394e7ba93753ee6d08d682ad87f1bf49f961b https://github.com/quicwg/base-drafts/commit/42b394e7ba93753ee6d08d682ad87f1bf49f961b Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Correct packet number example Thanks to Masakazu Kitajo for catching the error. Commit: 793b7d11031b8073b0209bb9fa7aa210fc377fdf https://github.com/quicwg/base-drafts/commit/793b7d11031b8073b0209bb9fa7aa210fc377fdf Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1489 from quicwg/pn-example Correct packet number example Compare: https://github.com/quicwg/base-drafts/compare/5c511676b267...793b7d11031b **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33352abeba5_41b42adefcfb5bfc1017f2-- From nobody Tue Jun 26 23:57:09 2018 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 C3831129385 for ; Tue, 26 Jun 2018 23:56:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 vE5vE3gveKtr for ; Tue, 26 Jun 2018 23:56:48 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 4CF80130F4D for ; Tue, 26 Jun 2018 23:56:48 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530082607; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=69+yJSjSE/RZWmnHDBW2vMpSTpHjLptTQMfFcci9UZI=; b=kdi9X72KG6APdcAtJ+5KRxU+TFtSO2yTpFrc0YTZtCQFZMbyfQ+LbXCOz1KCr+c6DReEDw3S aCAvPCBvpC8NmIOxVkJfYC2nq6ZTueqfaKlBVbTt8UAMbTKhxFKVtLl/THY2Z3iNwWTTDtd+ cbj8UW5vMjDQaZnsjbfaV0eMiZA= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b33352f.7f8ff17912d0-smtp-out-n02; Wed, 27 Jun 2018 06:56:47 -0000 (UTC) Date: Tue, 26 Jun 2018 23:56:46 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b33352e78d09_5a822b28d7c73c1c77049@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33352e780b9_5a822b28d7c73c1c769b2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 06:56:56 -0000 ----==_mimepart_5b33352e780b9_5a822b28d7c73c1c769b2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/pn-example Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33352e780b9_5a822b28d7c73c1c769b2-- From nobody Tue Jun 26 23:57:13 2018 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 11A0F130F49 for ; Tue, 26 Jun 2018 23:56:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 2GsakdtxtVMq for ; Tue, 26 Jun 2018 23:56:50 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5119213116A for ; Tue, 26 Jun 2018 23:56:50 -0700 (PDT) Date: Tue, 26 Jun 2018 23:56:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530082609; bh=YSBhCwS0wvgPBL5RXAozVJPc05mKZZJIUqJ69aQt6cE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Uo9RpTDOl/Ojef3KhfpqqtIti8vpCm+7wEBZjWTBKA2Ia3nv6y2z4p+v7+GSPfjdS nIYk1VnpsNkdnNfoMiKjxSZwz9rPHql5EINPMjSJ3VzgOd1ra0KwEghXP4AM00M/DB mbzroPF1AuoERemo48hiLV0OIgTuQekikvSRqsXs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Correct packet number example (#1489) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b333531b164d_117b3fc5f0e86f845888f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 06:56:58 -0000 ----==_mimepart_5b333531b164d_117b3fc5f0e86f845888f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1489. -- 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/1489#event-1703113513 ----==_mimepart_5b333531b164d_117b3fc5f0e86f845888f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1489.

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

----==_mimepart_5b333531b164d_117b3fc5f0e86f845888f-- From nobody Wed Jun 27 00:19:23 2018 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 CBFB2130E47 for ; Wed, 27 Jun 2018 00:19:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nudxiOkur57j for ; Wed, 27 Jun 2018 00:19:19 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FD7E130E8D for ; Wed, 27 Jun 2018 00:19:19 -0700 (PDT) Date: Wed, 27 Jun 2018 00:19:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530083958; bh=L2HU5HG5wRqhkqLSrup2DrLNAKYrfGbHsQVsl08zLMc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AhaGpqzZNvImb4iKusGa7rALzV26tpPK0n5e2uH8xkhLKO4H1x5syN9BjQqeHtOM/ hA5HyiSU0NyHt6YI4sP4641IQi/ns79dQQQgMm0Juu+zSD4Yh6dQ8JG/pc7WJfkXv6 ujMRdglnWwipdv738sMVLQqDoHwlmJx7vlhAuynw= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial destination CID is unauthenticated (#1486) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b333a76703ec_c6a2ad40345cf5c176998"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 07:19:21 -0000 ----==_mimepart_5b333a76703ec_c6a2ad40345cf5c176998 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Ahh, though it's only the first one, that might be enough. Not sure how much this matters, but we should do something, even if that is only write this down. Yes. Consider you want to build a middlebox that verifies Client Hello. What you might do is: * precompute AES-CTR for a special 8-octet CID (e.g., 0000000000000000) * send a Retry packet that contains the special CID in the source CID field and a zero-length token for every Initial packet that does not contain the special CID in the destination CID field By doing these, a middlebox can skip the cost of AES for decrypting the Initial packet, because the every Initial packet that it forwards will be encrypted using the same bitstream. I think we should permit the use of zero-length token, because it would be useful for *stateful* path validation. OTOH, I would like to prevent seeing these kind of hacks being applied by middleboxes (since it is an ossification concern), if the cost of preventing it is marginal. IMO, including initial DCID in TP and requiring the servers to validate the value when possible meets that goal. -- 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/1486#issuecomment-400568727 ----==_mimepart_5b333a76703ec_c6a2ad40345cf5c176998 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ahh, though it's only the first one, that might be enough. Not sure ho= w much this matters, but we should do something, even if that is only wri= te this down.

Yes.

Consider you want to build a middlebox that verifies Client Hello. Wha= t you might do is:

  • precompute AES-CTR for a special 8-octet CID (e.g., 0000000000000000)=
  • send a Retry packet that contains the special CID in the source CID f= ield and a zero-length token for every Initial packet that does not conta= in the special CID in the destination CID field

By doing these, a middlebox can skip the cost of AES for decrypting th= e Initial packet, because the every Initial packet that it forwards will = be encrypted using the same bitstream.

I think we should permit the use of zero-length token, because it woul= d be useful for stateful path validation.

OTOH, I would like to prevent seeing these kind of hacks being applied= by middleboxes (since it is an ossification concern), if the cost of pre= venting it is marginal. IMO, including initial DCID in TP and requiring t= he servers to validate the value when possible meets that goal.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b333a76703ec_c6a2ad40345cf5c176998-- From nobody Wed Jun 27 04:31:45 2018 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 138711277C8 for ; Wed, 27 Jun 2018 04:31:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 lAL7vs-1PjJc for ; Wed, 27 Jun 2018 04:31:39 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 6E82612777C for ; Wed, 27 Jun 2018 04:31:39 -0700 (PDT) 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=Sd4GtvzoK7eJj+wnjOlPgwv9kHw=; b=VOIw8vpAuBko+Kku gwsPmcI2MwgpX9gvTDWq8bafVlN59hHLHluuNZEDoK2s/lE7VKWxDgUiMdHSLjgC q23L7lKK0a9SCbCw/owY7nQYsiNhaFjJDyZjxIelM2uqAKz3KnTwm9o+KFHnSvlx mh/lbPZv7Qn21FtbQp30QskAnAU= Received: by filter0683p1las1.sendgrid.net with SMTP id filter0683p1las1-862-5B337599-1B 2018-06-27 11:31:37.803208681 +0000 UTC Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id rvCJ0EIuRjOtfv4f6pDIpw for ; Wed, 27 Jun 2018 11:31:37.631 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id 98C943E0287 for ; Wed, 27 Jun 2018 04:31:37 -0700 (PDT) Date: Wed, 27 Jun 2018 11:31:38 +0000 (UTC) From: Magnus Westerlund Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fragility in ECN counters with lost acks (#1481) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b337599969cb_42372ab905a7cf542045dd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gloinul 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0wb4/tm6RAU9kQ+v7TxkpLb7cqd5F59S6LsC YeLF82JHSzif31SRqef2W9LCko/m3Pfi+WNyX3E0IdWXFljDlBX8SDJtb1Gc5ADbsESvnpKHm4LUs2 2UENP+dLGHHv+kqOSbvDM8A6c1ojCkwkpcAmrk/3Odb2PW9PDt1C+arT3CcloCgUq0/bHCjh88BXeY g= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 11:31:44 -0000 ----==_mimepart_5b337599969cb_42372ab905a7cf542045dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think the general approach of handling this is correct. I don't think the MAY in the fourth paragraph is appropriate. The counters can increase due to their markings, not something that is specified by a RFC 2119 MAY. "It can then reset both the largest acknowledged and the values it tracks for each counter." I don't think reset is the appropriate word for something that is in practice baseline offsets to the comparison. -- 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/1481#issuecomment-400640246 ----==_mimepart_5b337599969cb_42372ab905a7cf542045dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think the general approach of handling this is correct. I don't think = the MAY in the fourth paragraph is appropriate. The counters can increase d= ue to their markings, not something that is specified by a RFC 2119 MAY.

"It can then reset both the largest acknowledged and the values it track= s for each counter." I don't think reset is the appropriate word for someth= ing that is in practice baseline offsets to the comparison.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b337599969cb_42372ab905a7cf542045dd-- From nobody Wed Jun 27 05:11:36 2018 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 67D9E127148 for ; Wed, 27 Jun 2018 05:11:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bHfQQsCyOsrY for ; Wed, 27 Jun 2018 05:11:32 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 749701277C8 for ; Wed, 27 Jun 2018 05:11:32 -0700 (PDT) Date: Wed, 27 Jun 2018 05:11:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530101491; bh=wY0VSl0XUMSgHk9tnyMDbSwM+Da2DT1Tis9Dt6/P1+I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rcFqBxwAjBrmvMW9W5DWPu3hXWrRIrqJy9yJgj808JA/yPiDtzrscrKYz/Duawe03 qoUz+n6IevGTiswJg7aT1aLwL39OVMChVMGFr7geSzx0vJ7h61dptupXAu5sdqtk9d /OJ5vp2TV4sN4gAEBJBGW+Ex8Xjt/7ipZejnhEC0= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b337ef33544c_4f043fd7a6a82f88300658"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Wed, 27 Jun 2018 12:11:35 -0000 ----==_mimepart_5b337ef33544c_4f043fd7a6a82f88300658 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr approved this pull request. LGTM > @@ -4786,17 +4786,35 @@ Issue and pull request numbers are listed with a leading octothorp. ## Since draft-ietf-quic-transport-12 -- Enable server to transition connections to a preferred address (#560, #1251). -- Moved the cryptographic handshake off stream 0 and into CRYPTO frames. -- Move stateless retry to the QUIC layer. -- Added token fields to Initial packet header. -- Added NEW_TOKEN frame. +- Enable server to transition connections to a preferred address (#560, #1251, + #1373) +- Added ECN feedback mechanisms and handling; new ACK_ECN frame (#804, #805, + #1372) +- Changes to integration of the TLS handshake (#829, #1018, #1094, #1165, #1190, + #1233, #1242, #1252, #1450) + - The cryptographic handshake uses CRYPTO frames, not stream 0 + - QUIC packet protection is used in place of TLS record protection + - Separate QUIC packet number spaces are used for the handshake + - Changed Retry to be independent of the cryptographic handshake I would promote this -- 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/1488#pullrequestreview-132402703 ----==_mimepart_5b337ef33544c_4f043fd7a6a82f88300658 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr approved this pull request.

LGTM

In draft-ietf-quic-transport.md:

> @@ -4786,17 +4786,35 @@ Issue and pull request numbers are listed with a leading octothorp.
 
 ## Since draft-ietf-quic-transport-12
 
-- Enable server to transition connections to a preferred address (#560, #1251).
-- Moved the cryptographic handshake off stream 0 and into CRYPTO frames.
-- Move stateless retry to the QUIC layer.
-- Added token fields to Initial packet header.
-- Added NEW_TOKEN frame.
+- Enable server to transition connections to a preferred address (#560, #1251,
+  #1373)
+- Added ECN feedback mechanisms and handling; new ACK_ECN frame (#804, #805,
+  #1372)
+- Changes to integration of the TLS handshake (#829, #1018, #1094, #1165, #1190,
+  #1233, #1242, #1252, #1450)
+  - The cryptographic handshake uses CRYPTO frames, not stream 0
+  - QUIC packet protection is used in place of TLS record protection
+  - Separate QUIC packet number spaces are used for the handshake
+  - Changed Retry to be independent of the cryptographic handshake

I would promote this

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

----==_mimepart_5b337ef33544c_4f043fd7a6a82f88300658-- From nobody Wed Jun 27 05:49:22 2018 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 ED9F6127598 for ; Wed, 27 Jun 2018 05:49:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.606 X-Spam-Level: X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_NONE=-0.0001, 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 93EgrptuDAog for ; Wed, 27 Jun 2018 05:49:19 -0700 (PDT) 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 2C52B126CC7 for ; Wed, 27 Jun 2018 05:49:19 -0700 (PDT) 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=HSt58ENYJ5gRmAWaLm7C+Kiy/28=; b=ApCGjMWHI4wF5G46 H/p9JjouhY5aMCAwcAcABdGXEZrPLJ5QjryqkzEwR71kd8a16w4Vg/1RoV2ut+t7 rZk55CqjgUb0e2cMwYINmt6hC/06w7I39DeMq4VDvmqRAvkOoRNYaUao75oAsc34 +ygR70iOklYBXGT9z125fHTBOuM= Received: by filter0313p1iad2.sendgrid.net with SMTP id filter0313p1iad2-9486-5B3387CD-44 2018-06-27 12:49:17.96570829 +0000 UTC Received: from github-lowworker-e51511d.cp1-iad.github.net (unknown [192.30.252.34]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id DNC003IZTV6MNhX7j6OroA for ; Wed, 27 Jun 2018 12:49:17.850 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e51511d.cp1-iad.github.net (Postfix) with ESMTP id CC77C80D1F for ; Wed, 27 Jun 2018 05:49:17 -0700 (PDT) Date: Wed, 27 Jun 2018 12:49:18 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3387cdca8c5_40182abb7f42cf607548a9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0ES1VxQNr1pVDcDWlIUC9Rey0yBE2YsioMG7 QRsB8LArk/HhGoqYPm0WmH4bv6bDRKLn4ZL5zbIyN2FoeSbTDrS33ICNLx7MFaIoqMr8tsJPxbtobc q59MxNpu274qFNM022YxJl/MQAIvTGQm3STDyO51b10i4asfVyiZ5UQaWQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 12:49:22 -0000 ----==_mimepart_5b3387cdca8c5_40182abb7f42cf607548a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. I can't find anything you missed in recovery or transport. -- 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/1488#pullrequestreview-132417528 ----==_mimepart_5b3387cdca8c5_40182abb7f42cf607548a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

I can't find anything you missed in recovery or transport.

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

----==_mimepart_5b3387cdca8c5_40182abb7f42cf607548a9-- From nobody Wed Jun 27 06:17:15 2018 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 7C5A8130DD7 for ; Wed, 27 Jun 2018 06:17:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 2Frzi4td7YKd for ; Wed, 27 Jun 2018 06:16:57 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8D5D130DC7 for ; Wed, 27 Jun 2018 06:16:50 -0700 (PDT) Date: Wed, 27 Jun 2018 06:16:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530105409; bh=+CwpKYRrnaUpfPx5OqcLGLsN5iSwSrImb1j1RWgpDdQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rMPDv0HIbqnl3dflpv4PflW9aQyxkHQGEFx4Z4kQwK4obiaoyABYUKNpDYF+Ysi/G obvI4hBUNuDiR0BgzgpsjwyVCqt8B526mWyvsyrdYK9af0/YY42X8ZhhwtT91tKvpc SY1HlZs//otnVnzjDgKnGUruzsWZnmt0BNmBAPTI= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b338e41d2a17_52f12b2892d10f5c6024ac"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Wed, 27 Jun 2018 13:17:14 -0000 ----==_mimepart_5b338e41d2a17_52f12b2892d10f5c6024ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sure, sure. That said, if we had a feasible way to authenticate the source address, I'm sure we'd pursue it. -- 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/1479#issuecomment-400667571 ----==_mimepart_5b338e41d2a17_52f12b2892d10f5c6024ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Sure, sure. That said, if we had a feasible way to authenticate the source address, I'm sure we'd pursue it.

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

----==_mimepart_5b338e41d2a17_52f12b2892d10f5c6024ac-- From nobody Wed Jun 27 06:17:32 2018 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 05A5C130EE8 for ; Wed, 27 Jun 2018 06:17:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 7_fJnnl-LdUt for ; Wed, 27 Jun 2018 06:17:11 -0700 (PDT) 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 5882F130DC0 for ; Wed, 27 Jun 2018 06:17:11 -0700 (PDT) Date: Wed, 27 Jun 2018 06:17:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530105430; bh=7XmY0icySBxQBNOZRVkbzfPhmhUL+sWQc+UpweKDW5w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CWd7ZxW5kCNqMO/6gJdJbqzoxFS/DZylKW6uqiuT9C4PsUkJAm7eUOqZu5E1ZausG +7CMWMWUUc4w1lKq2wTloq5APTZrmt8uko9HgDOxVFFACHFiiXF0iOUHzfHvn6g2mU fzscM6hIYU43qNsVkEdZfqKwBZUrYpoholWpwQg0= From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b338e569848a_d393fc39e138f84956448"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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.26 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: Wed, 27 Jun 2018 13:17:23 -0000 ----==_mimepart_5b338e569848a_d393fc39e138f84956448 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1479. -- 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/1479#event-1703870717 ----==_mimepart_5b338e569848a_d393fc39e138f84956448 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1479.

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

----==_mimepart_5b338e569848a_d393fc39e138f84956448-- From nobody Wed Jun 27 06:17:41 2018 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 7EDE5130FA5 for ; Wed, 27 Jun 2018 06:17:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 2iQGLwQZ3psv for ; Wed, 27 Jun 2018 06:17:21 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 703CF130EA5 for ; Wed, 27 Jun 2018 06:17:17 -0700 (PDT) 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=Fq6W1ZCFnXUyQjxhTMKWjCVcXms=; b=E3h36cVFJxufEXy1 En4cSU8XT/EPJLu1WFed9z9NfN5hJl7CL3CsP02ByErXGKOsAzDl2pbXsOh263HN xYaRWtvHkdNTKos6zxtn1GPDp8ZAQIJkGgRl6XI5MjmZ22ck8P0wSAd0XLFOs4vr Rk00/q0HZD+wWyue+XPCPghvWlU= Received: by filter0514p1iad2.sendgrid.net with SMTP id filter0514p1iad2-31305-5B338E57-7 2018-06-27 13:17:11.060502478 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id YK6ERSR7S4mEPx4JiUmSnA for ; Wed, 27 Jun 2018 13:17:11.015 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 020B13E0085 for ; Wed, 27 Jun 2018 06:17:11 -0700 (PDT) Date: Wed, 27 Jun 2018 13:17:11 +0000 (UTC) From: Christopher Wood Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Client's initial source CID is unauthenticated (#1479) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b338e57900_5e352b1969690f5c9911de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: chris-wood 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2YZAmb5/PRh8iNbvwAfJ7gaN4Ea/iXZt5H9u HijdzzkaHF446MoKg4JVGtwK/RKzaWgMx3IgYYbXxMogZbNtaB+n6S8hk3AF+frwEALQTCUg8+GNku aSFIuifwVFm9SFLSZfHmZwm7h2cr8WgLWm6C63/biSLWSTd7qbx/1DiMZtBSqcASv/qHqDKgD+OOuv M= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 13:17:39 -0000 ----==_mimepart_5b338e57900_5e352b1969690f5c9911de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closing in favor of #1486. -- 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/1479#issuecomment-400667674 ----==_mimepart_5b338e57900_5e352b1969690f5c9911de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closing in favor of #1486.

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

----==_mimepart_5b338e57900_5e352b1969690f5c9911de-- From nobody Wed Jun 27 09:23:10 2018 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 1372D130E1E for ; Wed, 27 Jun 2018 09:23:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NMjRA2u_Hyqs for ; Wed, 27 Jun 2018 09:23:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30092130E19 for ; Wed, 27 Jun 2018 09:23:07 -0700 (PDT) Date: Wed, 27 Jun 2018 09:23:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530116586; bh=Tkd+mLs5AEQlt5H+/59VAix9UbfhWCk6bDfPlb+HWBQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uWyYLcBvsYe+wz5NzUI9fHQFncANSr5xgDsXtMsdsRGOGV+0Sjb79H7nHNh50ziAi zDiBPftmFsj3u10Wh0UiHKEOSBlWxE4L1K4RixCI3/695ydSjoDsJEwZRoLotU/B4h KeiLgrWxWSfNvWM7nSqKEGwnVrbA7ern9TuW+x4Y= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retry Token Makeup (#1474) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33b9ea3a231_169f2ab88ceccf6084158"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 27 Jun 2018 16:23:09 -0000 ----==_mimepart_5b33b9ea3a231_169f2ab88ceccf6084158 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Should we add text to say that the client SHOULD NOT change their source CID in response to a Retry packet? If so, I can send a PR to that effect. -- 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/1474#issuecomment-400739456 ----==_mimepart_5b33b9ea3a231_169f2ab88ceccf6084158 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Should we add text to say that the client SHOULD NOT change their source CID in response to a Retry packet? If so, I can send a PR to that effect.

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

----==_mimepart_5b33b9ea3a231_169f2ab88ceccf6084158-- From nobody Wed Jun 27 09:39:24 2018 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 A0506130E04 for ; Wed, 27 Jun 2018 09:39:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 sOvskpRGtDMx for ; Wed, 27 Jun 2018 09:39:19 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 A2880130DFE for ; Wed, 27 Jun 2018 09:39:19 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530117558; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Cv6z6XTo5C3SOcvwdP1jvlA997RpMFzhiODyLtpQBqw=; b=rAHlRVtRDLLoga0dZjQRq0r75Y96dQju0zXi3xSmDBxV7VzifgbH35RbDWeG2pDnSJPGvokA 2h9duGdZLCXPokWMfz5TR9xoGP5v/vI1dhoqJkeiVLTa2SGG4Wbf2q+VcD+r4ePIUMH3ipCK ubJzdCAfTOQilaSmFl2/S2A+ebo= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b33bdb6.7f93d07404b0-smtp-out-n03; Wed, 27 Jun 2018 16:39:18 -0000 (UTC) Date: Wed, 27 Jun 2018 09:39:17 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33bdb599cfe_76e72ade22429c141219e0@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 6efd03: WIP: Unidirectional stream headers Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33bdb599824_76e72ade22429c14121876"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 16:39:22 -0000 ----==_mimepart_5b33bdb599824_76e72ade22429c14121876 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http_unidirectional Home: https://github.com/quicwg/base-drafts Commit: 6efd03871f0632101eb3e524a952739f6c2fae65 https://github.com/quicwg/base-drafts/commit/6efd03871f0632101eb3e524a952739f6c2fae65 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- WIP: Unidirectional stream headers Commit: a08643de537260b83d68f662470b30fa13969fc7 https://github.com/quicwg/base-drafts/commit/a08643de537260b83d68f662470b30fa13969fc7 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Fixups Commit: 183164a52d4a33c4c213ad370a4c55a76ede31d3 https://github.com/quicwg/base-drafts/commit/183164a52d4a33c4c213ad370a4c55a76ede31d3 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Critical streams Commit: eb3b9806c0e2e3bdb8174461d8eda5d51e7fc705 https://github.com/quicwg/base-drafts/commit/eb3b9806c0e2e3bdb8174461d8eda5d51e7fc705 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- QPACK control streams Commit: ba8c13add3061d08c2863c676c22c8159a09c888 https://github.com/quicwg/base-drafts/commit/ba8c13add3061d08c2863c676c22c8159a09c888 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- IANA registration Commit: b7b6ed47862b33eef235f9bd2107fca8611d9647 https://github.com/quicwg/base-drafts/commit/b7b6ed47862b33eef235f9bd2107fca8611d9647 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Review feedback Commit: 1ee0bc5bf7c396ebd6dfe663f42aa9cb5028cb3f https://github.com/quicwg/base-drafts/commit/1ee0bc5bf7c396ebd6dfe663f42aa9cb5028cb3f Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Introduce stream terms Commit: 8cae410fb2a86462365d4dc464e332f33cb78db0 https://github.com/quicwg/base-drafts/commit/8cae410fb2a86462365d4dc464e332f33cb78db0 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- ASCII codes Commit: 405cd8434eb8eea2eb11a50f40a76be7ebe20601 https://github.com/quicwg/base-drafts/commit/405cd8434eb8eea2eb11a50f40a76be7ebe20601 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Martin's comments Commit: e8dec988645b844cb0f7ccfe468643b79e6ab313 https://github.com/quicwg/base-drafts/commit/e8dec988645b844cb0f7ccfe468643b79e6ab313 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix ref breakage, again Commit: db5ddb7ea872f776a22e762d98cdd7f4b4d3000b https://github.com/quicwg/base-drafts/commit/db5ddb7ea872f776a22e762d98cdd7f4b4d3000b Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Stray assumptions of control stream ID Compare: https://github.com/quicwg/base-drafts/compare/e425c3e9cee9...db5ddb7ea872 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33bdb599824_76e72ade22429c14121876-- From nobody Wed Jun 27 09:43:18 2018 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 53EE7130DFE for ; Wed, 27 Jun 2018 09:43:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KPtyP-hNHOd1 for ; Wed, 27 Jun 2018 09:43:15 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2A6E130DEE for ; Wed, 27 Jun 2018 09:43:15 -0700 (PDT) Date: Wed, 27 Jun 2018 09:43:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530117794; bh=PM5EPBEGx3ObrK6wmp/ou3Oe/EMu1wylpDXskHUECtQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uhx0pr+oCP0CoyFFmjEyBbtnCP2I16B5ujgePwhz0ee5BJAiCHYItZeS0Y/iVT1lg yAHYfjYxTJOKp1ue3bHNsY5SP2MXt86DYSAFYOVtK3hlJ9+zP5TaaGHVuNIsJOtJOF 7FcK8zGjWdPDDmOeVdLhvDnEVgUceIOG1wqD/hvs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33bea2e3296_3dd32af2eebd6f58225265"; 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.26 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: Wed, 27 Jun 2018 16:43:18 -0000 ----==_mimepart_5b33bea2e3296_3dd32af2eebd6f58225265 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue, I had said I would come back to this and add greasing values here too. However, given that an unknown stream type is defined to be an error (and implementations are cautioned that peers can promote these errors to connection errors), sending grease values and mandating that receivers not treat them any differently will be a bit fragile. I think to do that, we'd need to either prohibit unknown unidirectional streams being promoted, which seems an unfortunate exception case, or special-case the grease types, which rather defeats the purpose. As a result, I'm merging this without grease and will open an issue to consider greasing later. -- 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/1359#issuecomment-400748238 ----==_mimepart_5b33bea2e3296_3dd32af2eebd6f58225265 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@LPardue, I had said I would come = back to this and add greasing values here too. However, given that an un= known stream type is defined to be an error (and implementations are caut= ioned that peers can promote these errors to connection errors), sending = grease values and mandating that receivers not treat them any differently= will be a bit fragile.

I think to do that, we'd need to either prohibit unknown unidirectiona= l streams being promoted, which seems an unfortunate exception case, or s= pecial-case the grease types, which rather defeats the purpose.

As a result, I'm merging this without grease and will open an issue to= consider greasing later.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b33bea2e3296_3dd32af2eebd6f58225265-- From nobody Wed Jun 27 09:45:11 2018 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 4D528130E60 for ; Wed, 27 Jun 2018 09:45:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 kklvE1F4v8Bv for ; Wed, 27 Jun 2018 09:45:07 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 BFB15130DEE for ; Wed, 27 Jun 2018 09:45:07 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530117907; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=SOzz7UXIj+flHai8xIY4CBOzikClY4NP83s5QXZC2pg=; b=BJ97o1d9tB2vZCHh0arP5F+dQBR9wriptdWtqBdAB43XvMTC94iUnSmE0VCmjROW19sEIInQ EnddaiGqZHeJujjzxansarPZBO3HFAivbkag9IbJC+4e5vXYK7H8gymd9Kk7ffjPIurcB+Rc bCCC+Ak4RMy2diO4n3t8QRWaAbo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b33bf12.7fa39c661120-smtp-out-n02; Wed, 27 Jun 2018 16:45:06 -0000 (UTC) Date: Wed, 27 Jun 2018 09:45:05 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33bf11e05d9_667d2ad4a2543c147241@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 98fad9: Track stream 0 changes Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33bf11e022f_667d2ad4a2543c1472332"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 16:45:10 -0000 ----==_mimepart_5b33bf11e022f_667d2ad4a2543c1472332 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http_unidirectional Home: https://github.com/quicwg/base-drafts Commit: 98fad9e96bc6958a065e73da76b92d6f77e04d50 https://github.com/quicwg/base-drafts/commit/98fad9e96bc6958a065e73da76b92d6f77e04d50 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Track stream 0 changes **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33bf11e022f_667d2ad4a2543c1472332-- From nobody Wed Jun 27 09:45:19 2018 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 D213F130E60 for ; Wed, 27 Jun 2018 09:45:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4AQhudy_CgaO for ; Wed, 27 Jun 2018 09:45:10 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30774130DEE for ; Wed, 27 Jun 2018 09:45:10 -0700 (PDT) Date: Wed, 27 Jun 2018 09:45:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530117909; bh=9vAiqJbnNtGA9oJPu2aVreyztU2ZS2gaYOBMGfH7ngc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YKH5TfpTwoiN+R3SnFKSbMUWNQy25++rsOHLvKVLI+Wtp53fERJYl6W+Ey7AHzVRm z4kyuzuZZsSMZfRTVcoRuzSF5VbRwgHrSgh9BPaiH+5Q6Fd7hagdAgON9qe2KlKJom PNf/awAtSD2VBqYDNkRsTEH6guvgkS/cskRp6vmI= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33bf157b90d_1c402aae4be0ef60216048"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 16:45:12 -0000 ----==_mimepart_5b33bf157b90d_1c402aae4be0ef60216048 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. 98fad9e Track stream 0 changes -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1359/files/db5ddb7ea872f776a22e762d98cdd7f4b4d3000b..98fad9e96bc6958a065e73da76b92d6f77e04d50 ----==_mimepart_5b33bf157b90d_1c402aae4be0ef60216048 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b33bf157b90d_1c402aae4be0ef60216048-- From nobody Wed Jun 27 09:55:04 2018 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 0ED03130DFF for ; Wed, 27 Jun 2018 09:55:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 0V-z5pbX4Ge6 for ; Wed, 27 Jun 2018 09:55:00 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 6EAD0130DFE for ; Wed, 27 Jun 2018 09:55:00 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530118499; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=uLcG9PDF6aDBx/0LjuizbRDGH9ASAnyLmpGUbev/wkI=; b=myTMbKAFCxIbQmP+rd1nLdIgWRNzh5LwVrQynRPoac+GO0eaXpw1mA+YBPD82IB6Nfj7ajx8 zif/sH3JarbQRKQT5mSZ/mR0T4bJvuWFPgVTgpBKEUB6ajzzQaqkqeG8SdoXEv8UQdM8DbN+ 8UhJ051kMq7zKyCATVOG6so9pQs= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b33c163.7f3efed9a7b0-smtp-out-n02; Wed, 27 Jun 2018 16:54:59 -0000 (UTC) Date: Wed, 27 Jun 2018 09:54:58 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33c1622acf3_63f92b16e4af3c0c943e5@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c0e7a6: Not that controlling Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33c1622a8cf_63f92b16e4af3c0c94212"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 16:55:03 -0000 ----==_mimepart_5b33c1622a8cf_63f92b16e4af3c0c94212 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http_unidirectional Home: https://github.com/quicwg/base-drafts Commit: c0e7a6ddfaabc2e9f966e44421e77cf50846faab https://github.com/quicwg/base-drafts/commit/c0e7a6ddfaabc2e9f966e44421e77cf50846faab Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Not that controlling **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33c1622a8cf_63f92b16e4af3c0c94212-- From nobody Wed Jun 27 09:55:10 2018 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 86F33130DFF for ; Wed, 27 Jun 2018 09:55:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 Duy0W3weqYp2 for ; Wed, 27 Jun 2018 09:55:03 -0700 (PDT) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 19C8A130DFE for ; Wed, 27 Jun 2018 09:55:03 -0700 (PDT) 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=wwI1MjUPqRe5GzhEpJB1PFa9Xqs=; b=IyQA4X0nO4hZ7f4E Q1NldTFnFHk3/kZIe77FQUcUprOQ6kBOb5gWXGzXpY/ZK9MAeUa1Ly9ln5AYip0k 43CgWMYCIVzQble7oSRCwR1HK5aMp4akOWk3/cI0wWEcB5C6RCKClYiWkEJQrO6g sn2F5qTdzDtHHbGEVDJwSRmQtdQ= Received: by filter0736p1las1.sendgrid.net with SMTP id filter0736p1las1-7607-5B33C165-15 2018-06-27 16:55:01.869732731 +0000 UTC Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id mBb0k2INSaqswFAN09aarg for ; Wed, 27 Jun 2018 16:55:01.742 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id B33A7AE0279 for ; Wed, 27 Jun 2018 09:55:01 -0700 (PDT) Date: Wed, 27 Jun 2018 16:55:02 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c165b148e_50202ab5e4100f58205090"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3KgI7IfUxelrBG5BYsGZ6L72o6fhNGtgdYmN B5N5Xi3RUSUp6dEVmiL5PlkYi+8WtdJNFZj1lmOKHI01MIsuNpYHG/HqvpUxRcKxcq2wges+s/htrx Yg9dhv4em9GJMntsB1CQWZrdCyyqJdXlAkyZzGbqeaBta6w3BR8v8bk1jNvzeicd77gvE+H0qpHrJs o= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 16:55:05 -0000 ----==_mimepart_5b33c165b148e_50202ab5e4100f58205090 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. c0e7a6d Not that controlling -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1359/files/ba3952371e711cdac70f062fc27a69daa66856e4..c0e7a6ddfaabc2e9f966e44421e77cf50846faab ----==_mimepart_5b33c165b148e_50202ab5e4100f58205090 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b33c165b148e_50202ab5e4100f58205090-- From nobody Wed Jun 27 09:57:06 2018 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 BF87C130EA1 for ; Wed, 27 Jun 2018 09:56:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 NhqS6NUWLfWZ for ; Wed, 27 Jun 2018 09:56:54 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA27A130EAC for ; Wed, 27 Jun 2018 09:56:53 -0700 (PDT) Date: Wed, 27 Jun 2018 09:56:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530118612; bh=DNBVqjbZSUaM/krDJGrZDZsa8sth83qShiB0I+wtIiE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MLhZgNI492OWU/NpYDLSRcNO9758mCHv73RJfDSG/1d9L67KHf8tj3HPzT7ZiqHRh fyJ9U8OfNCXUWDHRellTnPA2aCzBR6ZaIbP857L9JnwornWgpsQJPLRRbMWgDcEA+/ 8GEwP76DobTWXEAzhWQoK0lo/DT8Vs37ErbMghos= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c1d4ec879_23c22af2eebd6f582807e8"; 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.26 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: Wed, 27 Jun 2018 16:57:05 -0000 ----==_mimepart_5b33c1d4ec879_23c22af2eebd6f582807e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1359. -- 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/1359#event-1704432732 ----==_mimepart_5b33c1d4ec879_23c22af2eebd6f582807e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1359.

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

----==_mimepart_5b33c1d4ec879_23c22af2eebd6f582807e8-- From nobody Wed Jun 27 09:57:15 2018 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 0D400130E99 for ; Wed, 27 Jun 2018 09:56:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 kSsUOMYnNqWt for ; Wed, 27 Jun 2018 09:56:54 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 580C8130E94 for ; Wed, 27 Jun 2018 09:56:54 -0700 (PDT) Date: Wed, 27 Jun 2018 09:56:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530118613; bh=q1Up+6SLX2J2Ou30Tjtu0qUJjhF3Z9e6FIFZEUfNR5w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XNo6P3z1EowJl2L/g0D1adrTSbWxiurzh3fuXF68aDhS/V7ie28BT17VZ9m4iWy6p i+GH7MKY6fo/qfo5ipxkOr7A0ASLcccdnx+WNJiYP8WvSLbFx1NPJM5NV7Uv+LTsU0 COLUlieSOO/0i9ytBKvuhRgiCtXjq50IdexTEW48= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Applications and Stream IDs (#910) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c1d54f476_c433fc7c9800f7c26627d"; 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.26 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: Wed, 27 Jun 2018 16:57:05 -0000 ----==_mimepart_5b33c1d54f476_c433fc7c9800f7c26627d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #910 via #1359. -- 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/910#event-1704432750 ----==_mimepart_5b33c1d54f476_c433fc7c9800f7c26627d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #910 via #1359.

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

----==_mimepart_5b33c1d54f476_c433fc7c9800f7c26627d-- From nobody Wed Jun 27 10:04:03 2018 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 883D7130DD9 for ; Wed, 27 Jun 2018 10:04:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 whvsvxez1XMV for ; Wed, 27 Jun 2018 10:03:57 -0700 (PDT) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 2CE7C124D68 for ; Wed, 27 Jun 2018 10:03:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=XsxXIHGrq9gAyBxJcWIwQX7Yono=; b=Kf6g7IIdY2gKUXm/ bAfNqwiqYkb+NXKAI5oLWhy1TJeNNFgsL6eOGU2TCWRYiQJwffi62TvhcgTizt7/ SYuu/NE4j3XY+JoYaemnN3iKsC71xdFD0+mcnEck2CvhfMIQzm56BJNLVoNoTbpE 6xAVYOwNqCjaX8aqqg1xoss90M0= Received: by filter0177p1iad2.sendgrid.net with SMTP id filter0177p1iad2-15216-5B33C37B-19 2018-06-27 17:03:55.65646037 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0033p1mdw1.sendgrid.net (SG) with ESMTP id FwbnemCyQKm0FIHSnw0VgA for ; Wed, 27 Jun 2018 17:03:55.347 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id DF62F41011 for ; Wed, 27 Jun 2018 10:03:54 -0700 (PDT) Date: Wed, 27 Jun 2018 17:03:55 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c37ade1be_e023ff7299b4f784331fe"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0s5ktijkFZRXE35qsjNXHnycCSD/pul03DPX ZvIK1hRGXUE2Bncjp4CdYXZ5kGnV/jjn67er3q5dUGBP7VzG3Rn48UdQvyE7O8stAhLCca5j99hdh/ wWWYFHnlUaOdQW+nlP/tPwzddLpxApY2Kiyx0TAK9Yc9RzQc+nvFNlI9oEx0CeEPdXBH/7slCiXqZc 8= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 17:04:01 -0000 ----==_mimepart_5b33c37ade1be_e023ff7299b4f784331fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit #1446 added greasing values for various elements in HTTP/QUIC (settings, frame types, etc.) where the peer is required to ignore unknown values. #1359 added unidirectional stream types, and there was a suggestion from @LPardue to grease those as well. However, given that an unknown stream type is defined to be an error (and implementations are cautioned that peers can promote these errors to connection errors), sending grease values and mandating that receivers not treat them any differently will be a bit fragile. Options I see: - Prohibit unknown unidirectional streams from being treated as an error at all; ignore them. Unfortunate for wasted data transfer; you really want a STOP_SENDING here. This is also an attack vector. And if you expect some valid unidirectional streams, you can't just clamp down on the number of allowed unidirectional streams using MAX_STREAM_ID. - Prohibit unknown unidirectional streams from being treated as a connection error. This seems an unfortunate exception case, especially since it opens the same attack vector as the previous. - Special-case the grease types on the receiver, which rather defeats the purpose of having grease at all. - Don't grease these. Unless someone has a bright idea, I'm currently inclined toward the last option. -- 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/1490 ----==_mimepart_5b33c37ade1be_e023ff7299b4f784331fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

#1446 added greasing values for various elements in HTTP/QUIC (settings, frame types, etc.) where the peer is required to ignore unknown values. #1359 added unidirectional stream types, and there was a suggestion from @LPardue to grease those as well.

However, given that an unknown stream type is defined to be an error (and implementations are cautioned that peers can promote these errors to connection errors), sending grease values and mandating that receivers not treat them any differently will be a bit fragile.

Options I see:

  • Prohibit unknown unidirectional streams from being treated as an error at all; ignore them. Unfortunate for wasted data transfer; you really want a STOP_SENDING here. This is also an attack vector. And if you expect some valid unidirectional streams, you can't just clamp down on the number of allowed unidirectional streams using MAX_STREAM_ID.
  • Prohibit unknown unidirectional streams from being treated as a connection error. This seems an unfortunate exception case, especially since it opens the same attack vector as the previous.
  • Special-case the grease types on the receiver, which rather defeats the purpose of having grease at all.
  • Don't grease these.

Unless someone has a bright idea, I'm currently inclined toward the last option.

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

----==_mimepart_5b33c37ade1be_e023ff7299b4f784331fe-- From nobody Wed Jun 27 10:04:10 2018 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 5A629130E01 for ; Wed, 27 Jun 2018 10:04:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 cFFpDl60vwXH for ; Wed, 27 Jun 2018 10:04:07 -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 35D9F130DD9 for ; Wed, 27 Jun 2018 10:04:07 -0700 (PDT) Date: Wed, 27 Jun 2018 10:04:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530119046; bh=UUvmkWs5v7Otl++uJEWnWIpT0K+t8t5J3ldHECWXDZ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u5bS2ZWKdEMn0VE9/wbX+taz3ot0vQidmX1GoNRxAz3rFHA7DQTgmiKAgz+EeJ93Y 4HUFNpJSbpfURPPt13iFYT/VRu6pqJbj6CeH61dMXu455j+DtnbixxP/AzpwVIHuBd CvXHVlzuXDJkANyVehQ5rf0JXk9hGp6TkV7ygg2A= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Unidirectional Stream Headers in HTTP (#1359) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c386b0bc1_16ba3ff7299b4f7833351d"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 17:04:09 -0000 ----==_mimepart_5b33c386b0bc1_16ba3ff7299b4f7833351d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop I agree with the dilemma. Now that this change has landed, let me update my unbound server push extension specification and implementation so we can have something tangible for any new ticket. Many thanks! -- 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/1359#issuecomment-400757715 ----==_mimepart_5b33c386b0bc1_16ba3ff7299b4f7833351d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop I agree with the dilemma. Now that this change has landed, let me update my unbound server push extension specification and implementation so we can have something tangible for any new ticket.

Many thanks!

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

----==_mimepart_5b33c386b0bc1_16ba3ff7299b4f7833351d-- From nobody Wed Jun 27 10:06:54 2018 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 45C2B130DFF for ; Wed, 27 Jun 2018 10:06:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 fv8j-rZ2QXVo for ; Wed, 27 Jun 2018 10:06:50 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 A611B124D68 for ; Wed, 27 Jun 2018 10:06:50 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530119210; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5UF/EdO+tS5qRrDQu/V3f8nebYcYzFDJnR1/GP6xjAQ=; b=G9wiKWpGasscNYz1w3q031IFuQokv2+AURutyZ7akeDXSzIbFUpROiBhIgWEOnOMLiIygBMK FLuUfGzOBVpFmtDIrfctGqTm/loCctPsAT7bnVlVdX0QMdYhQSzkbR/hKov9hS7U7FVWLR6b zblhmffhiqSP3rJ+l66slz5MUjg= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b33c1d2.7f8ce8f730c0-smtp-out-n01; Wed, 27 Jun 2018 16:56:50 -0000 (UTC) Date: Wed, 27 Jun 2018 09:56:49 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33c1d19863b_481c2ac3ee73fc0874338@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 6efd03: WIP: Unidirectional stream headers Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33c1d198218_481c2ac3ee73fc087422d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 17:06:53 -0000 ----==_mimepart_5b33c1d198218_481c2ac3ee73fc087422d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 6efd03871f0632101eb3e524a952739f6c2fae65 https://github.com/quicwg/base-drafts/commit/6efd03871f0632101eb3e524a952739f6c2fae65 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- WIP: Unidirectional stream headers Commit: a08643de537260b83d68f662470b30fa13969fc7 https://github.com/quicwg/base-drafts/commit/a08643de537260b83d68f662470b30fa13969fc7 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Fixups Commit: 183164a52d4a33c4c213ad370a4c55a76ede31d3 https://github.com/quicwg/base-drafts/commit/183164a52d4a33c4c213ad370a4c55a76ede31d3 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Critical streams Commit: eb3b9806c0e2e3bdb8174461d8eda5d51e7fc705 https://github.com/quicwg/base-drafts/commit/eb3b9806c0e2e3bdb8174461d8eda5d51e7fc705 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- QPACK control streams Commit: ba8c13add3061d08c2863c676c22c8159a09c888 https://github.com/quicwg/base-drafts/commit/ba8c13add3061d08c2863c676c22c8159a09c888 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- IANA registration Commit: b7b6ed47862b33eef235f9bd2107fca8611d9647 https://github.com/quicwg/base-drafts/commit/b7b6ed47862b33eef235f9bd2107fca8611d9647 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Review feedback Commit: 1ee0bc5bf7c396ebd6dfe663f42aa9cb5028cb3f https://github.com/quicwg/base-drafts/commit/1ee0bc5bf7c396ebd6dfe663f42aa9cb5028cb3f Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Introduce stream terms Commit: 8cae410fb2a86462365d4dc464e332f33cb78db0 https://github.com/quicwg/base-drafts/commit/8cae410fb2a86462365d4dc464e332f33cb78db0 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- ASCII codes Commit: 405cd8434eb8eea2eb11a50f40a76be7ebe20601 https://github.com/quicwg/base-drafts/commit/405cd8434eb8eea2eb11a50f40a76be7ebe20601 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Martin's comments Commit: e8dec988645b844cb0f7ccfe468643b79e6ab313 https://github.com/quicwg/base-drafts/commit/e8dec988645b844cb0f7ccfe468643b79e6ab313 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix ref breakage, again Commit: db5ddb7ea872f776a22e762d98cdd7f4b4d3000b https://github.com/quicwg/base-drafts/commit/db5ddb7ea872f776a22e762d98cdd7f4b4d3000b Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Stray assumptions of control stream ID Commit: ba3952371e711cdac70f062fc27a69daa66856e4 https://github.com/quicwg/base-drafts/commit/ba3952371e711cdac70f062fc27a69daa66856e4 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Track stream 0 changes Commit: c0e7a6ddfaabc2e9f966e44421e77cf50846faab https://github.com/quicwg/base-drafts/commit/c0e7a6ddfaabc2e9f966e44421e77cf50846faab Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Not that controlling Commit: 86660ea4a201df76fa75ea8971ba896c6e6187af https://github.com/quicwg/base-drafts/commit/86660ea4a201df76fa75ea8971ba896c6e6187af Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- Merge pull request #1359 from quicwg/http_unidirectional Unidirectional Stream Headers in HTTP Compare: https://github.com/quicwg/base-drafts/compare/793b7d11031b...86660ea4a201 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33c1d198218_481c2ac3ee73fc087422d-- From nobody Wed Jun 27 10:11:39 2018 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 E4098130E01 for ; Wed, 27 Jun 2018 10:11:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 OESv8N16Ykt7 for ; Wed, 27 Jun 2018 10:11:35 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 4C206130DFF for ; Wed, 27 Jun 2018 10:11:35 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530119494; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=fA8bgF/5RNZUV13FfP3R6lKGwUtf108bfM6WBAqAk30=; b=wwXacMH1rJzaIYTfIT4L06UhxkqD2huji+HL28I+fpHvEcFDCSVsYgyW7Cxntg1GMCrueIHx 2uXo3gxbvGjt+PjjFozWN8L114j8/U2zjiCuTUSKTG8YvPKhaxXLKPIyntjfsEXC1Zrke5ha 0pbKZFoRl5s/6+HovquL7+hyLX4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b33bf6a.7f77be26ddb0-smtp-out-n01; Wed, 27 Jun 2018 16:46:34 -0000 (UTC) Date: Wed, 27 Jun 2018 09:46:34 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33bf6a73a15_41f22acaba1c7c08467e0@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ba3952: Track stream 0 changes Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33bf6a7344c_41f22acaba1c7c08466df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 17:11:37 -0000 ----==_mimepart_5b33bf6a7344c_41f22acaba1c7c08466df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/http_unidirectional Home: https://github.com/quicwg/base-drafts Commit: ba3952371e711cdac70f062fc27a69daa66856e4 https://github.com/quicwg/base-drafts/commit/ba3952371e711cdac70f062fc27a69daa66856e4 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Track stream 0 changes **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33bf6a7344c_41f22acaba1c7c08466df-- From nobody Wed Jun 27 10:12:37 2018 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 18B6C130E01 for ; Wed, 27 Jun 2018 10:12:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 A-NmfP27Tn2O for ; Wed, 27 Jun 2018 10:12:33 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93D44124D68 for ; Wed, 27 Jun 2018 10:12:33 -0700 (PDT) Date: Wed, 27 Jun 2018 10:12:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530119553; bh=zwsbl65ivL3K88VqxaECD3IYXX6+7EV97PDGXWzNDDI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Bsh2kFfLD5XDGFrmXK9PK8H94Wg+42+C9l8sI6s9bQi8St9k/InReiMHGP6mELpvW 6zc8CnfOPg/iVUzr0VA+jHUHn0HgX+jY6GMC5hfK4Sk+1mKuNJLJgVnAwI1MALWTWt PMaAN0/ibfXobhK6SnCbeSGbDN0ppvfvKZXQebNI= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c5811e51_34933ff036ebcf8835474"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 27 Jun 2018 17:12:35 -0000 ----==_mimepart_5b33c5811e51_34933ff036ebcf8835474 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Resolves #1474. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1491 -- Commit Summary -- * Don't Change Source CID After Retry -- File Changes -- M draft-ietf-quic-transport.md (6) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1491.patch https://github.com/quicwg/base-drafts/pull/1491.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/1491 ----==_mimepart_5b33c5811e51_34933ff036ebcf8835474 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Resolves #1474.

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

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

Commit Summary

  • Don't Change Source CID After Retry

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 mute the thread.

----==_mimepart_5b33c5811e51_34933ff036ebcf8835474-- From nobody Wed Jun 27 10:16:24 2018 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 46A0E130DFF for ; Wed, 27 Jun 2018 10:16:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 K89-CgZ29oGb for ; Wed, 27 Jun 2018 10:16:20 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DE90124D68 for ; Wed, 27 Jun 2018 10:16:20 -0700 (PDT) Date: Wed, 27 Jun 2018 10:16:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530119779; bh=vS9OA6H9lvWH7bQMlOLOtkHvfCJiDzeh0osbJK01jIk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ecLNl53Ujmdf55a7sIqYeDXcu89JDajDWBZUzxdX3PGvKDpU66nc8o+nqN31oSK6M sLHWmMarW0zaHkuPmNFelPfbRLw41cQU+AjlK6lzR1toKlK64U83WXC/hSrW8px1D6 e+D0HfrTfTVQOqpr+HfZDsu64JCqOL8/AVmVn6Uc= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33c663ea481_54a52b0cf2410f58277755"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 17:16:23 -0000 ----==_mimepart_5b33c663ea481_54a52b0cf2410f58277755 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To ask a silly question: ow is receiving and unknown frame type on a push promise stream any different to receiving a push promise frame on an unknown stream type? -- 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/1490#issuecomment-400762114 ----==_mimepart_5b33c663ea481_54a52b0cf2410f58277755 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

To ask a silly question: ow is receiving and unknown frame type on a push promise stream any different to receiving a push promise frame on an unknown stream type?

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

----==_mimepart_5b33c663ea481_54a52b0cf2410f58277755-- From nobody Wed Jun 27 10:38:55 2018 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 B3C97130E03 for ; Wed, 27 Jun 2018 10:38:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 fSpw0or0OBqU for ; Wed, 27 Jun 2018 10:38:51 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041AC130E02 for ; Wed, 27 Jun 2018 10:38:51 -0700 (PDT) Date: Wed, 27 Jun 2018 10:38:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530121130; bh=Y52NeBe8yHX+l6OByQ7AJSbK+0DK4Bp9g7/MNS72Ld8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qsxRElthIfG3PK9zzf9//cqLo/sUfN4+ikvbqwY0WQbd8yGLuJd8IM0v30lFKZcRu kXUQqJysT86TzI2jEc+6+svyK9QgYs/Mvx89nskasXWlJ60TLR5WnFT6woeiVPwuD0 jaOxu/caDTStwuariIfMYvAEhNKtejwrHv6R/rDs= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33cbaa39a56_35cf3fe924c76f803764bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 27 Jun 2018 17:38:53 -0000 ----==_mimepart_5b33cbaa39a56_35cf3fe924c76f803764bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit But doesn't this work against fixing loops in retry? Though that hasn't been worked out yet. -- 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/1491#issuecomment-400769114 ----==_mimepart_5b33cbaa39a56_35cf3fe924c76f803764bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

But doesn't this work against fixing loops in retry? Though that hasn't been worked out yet.

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

----==_mimepart_5b33cbaa39a56_35cf3fe924c76f803764bf-- From nobody Wed Jun 27 10:40:17 2018 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 52ED0130E02 for ; Wed, 27 Jun 2018 10:40:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 UIVUoUEQ7KIF for ; Wed, 27 Jun 2018 10:40:13 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 784AF130E01 for ; Wed, 27 Jun 2018 10:40:13 -0700 (PDT) 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=Z94I/hoycWxgBIT7Ww7ECOpPwkQ=; b=WoWvytShLH1JsNMu MMI0ZuTiuA/J8I9OJUH+5x1EIOF9/W44/QTsTHLwhQlsPV3KBpp6na7emEtRKa+3 nCeISEAthK9V//BufEriIPnoa/EnMQ12vAbLv9o1vLxIo0CongTBQ93EMjzzFSF4 D1xWKT/qpDBt/+qobW0RvzGkaiM= Received: by filter0915p1las1.sendgrid.net with SMTP id filter0915p1las1-5957-5B33CBFC-1C 2018-06-27 17:40:12.824771245 +0000 UTC Received: from github-lowworker10-cp1-prd.iad.github.net (unknown [192.30.252.38]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id p55Ve19KR2q7PRxU-dIoZg for ; Wed, 27 Jun 2018 17:40:12.721 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker10-cp1-prd.iad.github.net (Postfix) with ESMTP id AF4914100E for ; Wed, 27 Jun 2018 10:40:12 -0700 (PDT) Date: Wed, 27 Jun 2018 17:40:12 +0000 (UTC) From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33cbfcad25c_5d0e3f9772050f841042f2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak27z8mx9z6RDjDXdBSAj/OXQ2aUAuNU1/kSIC 1ygr+YOjfOfPKi18iYOHxcCZICaEKfQnADqo+eXsyPQLdhVbnAoOhppftOCB2KYU5j7PQKdkI7tY6B 0/ua6bRHbsf9xylNfHqttLOr1EjvCaoueS+vgecp3dM+JgFrPTvVFqeTqQNv2Ls+YHU4JVvxi2P7Id E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 17:40:16 -0000 ----==_mimepart_5b33cbfcad25c_5d0e3f9772050f841042f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I thought he retry loop issue was related changing **destination** connection ID, not source. -- 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/1491#issuecomment-400769514 ----==_mimepart_5b33cbfcad25c_5d0e3f9772050f841042f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I thought he retry loop issue was related changing destination connection ID, not source.

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

----==_mimepart_5b33cbfcad25c_5d0e3f9772050f841042f2-- From nobody Wed Jun 27 10:43:08 2018 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 122FE130E04 for ; Wed, 27 Jun 2018 10:43:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Lrfozzv_-xSA for ; Wed, 27 Jun 2018 10:43:05 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A589E130E01 for ; Wed, 27 Jun 2018 10:43:05 -0700 (PDT) Date: Wed, 27 Jun 2018 10:43:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530121384; bh=n56rAKeJKuJLgcS+fe0D2XRDHZWQjD2qiXSZuSxIabI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ke91HyDqSdjxBqQLLCCpSgIiwKvXyWxi6OBLG1zO/aEwdsO13TJV1pvGcFU8dpjMR WwmGMEPKQpCzjFRgJeaz+Os+bGhkSbruFdLxPQTYrfelD/KcnbfvbR9rG7nDpiX1go 255ZvkQnzHEmMyLX1zQ0Gq0bG+Vh61WXc/DOFkeU= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33cca8b01ae_53762b0c54bfef6040368a"; 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.26 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: Wed, 27 Jun 2018 17:43:07 -0000 ----==_mimepart_5b33cca8b01ae_53762b0c54bfef6040368a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Because with an unknown stream type, you don't even know that it's using frames -- it's just a bytestream about which you have no context. -- 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/1490#issuecomment-400770394 ----==_mimepart_5b33cca8b01ae_53762b0c54bfef6040368a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Because with an unknown stream type, you don't even know that it's using frames -- it's just a bytestream about which you have no context.

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

----==_mimepart_5b33cca8b01ae_53762b0c54bfef6040368a-- From nobody Wed Jun 27 10:49:18 2018 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 A24AC130E03 for ; Wed, 27 Jun 2018 10:49:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Bj0DLx4siHkP for ; Wed, 27 Jun 2018 10:49:14 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DD30129C6B for ; Wed, 27 Jun 2018 10:49:14 -0700 (PDT) Date: Wed, 27 Jun 2018 10:49:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530121753; bh=gNbx2TCcRLFBbm5IJmeOCQ1MCe91+gixHOA74+8MDG0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WL2Te66rLF6l2C5ix27b6LgwyVMWZJoxC0TdvMkeOHk0D42ir4l3U0fTnSZOBgvqX 9TWfskyT74olPcLG+9UO0BHeeT8eebClr1RN+3NNzmVBe4e+EevayM1pYDzr1Cnfnl vw0uNUNOPW3eq3rhWB2aTMS0e2ql3zD7qZizcDlA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33ce193c9fd_30e03f8a476faf84220778"; 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.26 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: Wed, 27 Jun 2018 17:49:16 -0000 ----==_mimepart_5b33ce193c9fd_30e03f8a476faf84220778 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed. I thought there was text to the effect that changing the SCID during the handshake was effectively starting a fresh connection attempt, but I don't see it in the draft. Maybe still in one of the PRs, or maybe that text got lost at some point. -- 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/1491#issuecomment-400772158 ----==_mimepart_5b33ce193c9fd_30e03f8a476faf84220778 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Agreed. I thought there was text to the effect that changing the SCID during the handshake was effectively starting a fresh connection attempt, but I don't see it in the draft. Maybe still in one of the PRs, or maybe that text got lost at some point.

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

----==_mimepart_5b33ce193c9fd_30e03f8a476faf84220778-- From nobody Wed Jun 27 10:49:27 2018 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 14809130E01 for ; Wed, 27 Jun 2018 10:49:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 gulYSkxolz1u for ; Wed, 27 Jun 2018 10:49:22 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C76A129C6B for ; Wed, 27 Jun 2018 10:49:22 -0700 (PDT) Date: Wed, 27 Jun 2018 10:49:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530121762; bh=795eZsf5SAf+Q+il3BHleqF8OW/MMgCahZ4mBkn9zIY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vt/uo6QETnwVwi/VFoVaVxc3bXknBui9MHsEPMnD/mtSmp9w58wgpR8aYbWipv9t5 osJlxG8hh7jNZb8OSrZ24Aq3t6iM2+ucf6quUQAjaOcKcJWo3njF5i/xJ3ss8py+oh QJsniA8PlYUBRbRNkrKL0gLfQIQvjmZcmvlow5Iw= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33ce21ed0c3_1fb113f9f3d424f84538623"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Wed, 27 Jun 2018 17:49:26 -0000 ----==_mimepart_5b33ce21ed0c3_1fb113f9f3d424f84538623 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Not all in fresh memory but goes like: Clients sends original random DCID to server. Server sends retry back to client with a servers SCID Client uses retry SCID as its new DCID towards the server. Client uses whatever SCID it happens to prefer, 0 lenght or otherwise, call this Client-SCID. If the Client-SCID does not change an new random retries happen, the client might be confused. If the server changes Client-SCID it can distinguish responses. But there is a long dicussion that never got fully resolved. Changing Client-SCID is just one option. Reflecting a separate NONCE per retry is probably either better or also needed. https://github.com/quicwg/base-drafts/issues/1451 -- 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/1491#issuecomment-400772206 ----==_mimepart_5b33ce21ed0c3_1fb113f9f3d424f84538623 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Not all in fresh memory but goes like:
Clients sends original random DCID to server.
Server sends retry back to client with a servers SCID
Client uses retry SCID as its new DCID towards the server.
Client uses whatever SCID it happens to prefer, 0 lenght or otherwise, ca= ll this Client-SCID.

If the Client-SCID does not change an new random retries happen, the c= lient might be confused. If the server changes Client-SCID it can disting= uish responses. But there is a long dicussion that never got fully resolv= ed. Changing Client-SCID is just one option. Reflecting a separate NONCE = per retry is probably either better or also needed.

#1451

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b33ce21ed0c3_1fb113f9f3d424f84538623-- From nobody Wed Jun 27 10:49:35 2018 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 860A9130E01 for ; Wed, 27 Jun 2018 10:49:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0m8JLPWUDQZF for ; Wed, 27 Jun 2018 10:49:25 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17BFC130E03 for ; Wed, 27 Jun 2018 10:49:25 -0700 (PDT) Date: Wed, 27 Jun 2018 10:49:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530121764; bh=yWhGE8JLF2KTBYjC9aALYxRKN2/7CfuHnd24uW8vQV8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EB4TrQPiWxwfSe2Z/N6FPToEpol4vM13JBi6ILQslJrMySS8Ye/OIN+KvIhtmRISI dyx8nc8mpoxLJ4cEoWeHrb0To2zK0ucD1TethLdefN7QYNexrEh2Or7+zpPtb1q2Oj sEk8TXiDpKIBpDTOwS0Rv4TWT77bkD8vHQ6epaOo= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33ce247262b_5b162ac0c3260f583232ac"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 17:49:28 -0000 ----==_mimepart_5b33ce247262b_5b162ac0c3260f583232ac Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Understood. So isn't the point of greasing to make it impractical to write code for the special cases while ignoring true extension? Greased streams would not be expected to deliver any subsequent data. Could you specify for greased stream types to be reset by the sender? -- 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/1490#issuecomment-400772215 ----==_mimepart_5b33ce247262b_5b162ac0c3260f583232ac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Understood.

So isn't the point of greasing to make it impractical to write code fo= r the special cases while ignoring true extension?

Greased streams would not be expected to deliver any subsequent data. = Could you specify for greased stream types to be reset by the sender?

=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b33ce247262b_5b162ac0c3260f583232ac-- From nobody Wed Jun 27 10:54:59 2018 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 50F2E130E01 for ; Wed, 27 Jun 2018 10:54:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 x11LcKsH-NpQ for ; Wed, 27 Jun 2018 10:54:56 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFEE129C6B for ; Wed, 27 Jun 2018 10:54:55 -0700 (PDT) Date: Wed, 27 Jun 2018 10:54:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530122095; bh=gPoaojyUkFIVR55EbVcOT6n7RKwQ/SSjBZNSHB3bd+g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OtDu+d+GcBe28Yf2BhFBguR74kSsQC5bPOUrupsVJKFAvAknIs+mhOIVQ1HvTFEBd VeF3QfPg+deHl5CjA7zloDgyHMapQVe0v7yLmc2B399QyDZw1P4TCpiela/s2Wn72p IQc1JrlWAuF2n0y8PMuk9RAhyBveOnLbgabDD64M= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33cf6f5031e_5ad52ac0c3260f583413dc"; 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.26 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: Wed, 27 Jun 2018 17:54:58 -0000 ----==_mimepart_5b33cf6f5031e_5ad52ac0c3260f583413dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The point is to make it impractical to be intolerant of unknown values when the specified behavior is to ignore them and move on (frame types, settings, TLS extensions, etc.). But here, we've specified intolerance of unknown values as the correct behavior. -- 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/1490#issuecomment-400773933 ----==_mimepart_5b33cf6f5031e_5ad52ac0c3260f583413dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The point is to make it impractical to be intolerant of unknown values when the specified behavior is to ignore them and move on (frame types, settings, TLS extensions, etc.). But here, we've specified intolerance of unknown values as the correct behavior.

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

----==_mimepart_5b33cf6f5031e_5ad52ac0c3260f583413dc-- From nobody Wed Jun 27 11:08:47 2018 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 5FB15130E09 for ; Wed, 27 Jun 2018 11:08:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 E6ID2A3wAp0s for ; Wed, 27 Jun 2018 11:08:43 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 E31B6130E07 for ; Wed, 27 Jun 2018 11:08:42 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530122922; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=DdxdRAG++emXDmts5OcmJtgBOFD/nn5gEU3pLZHcA3E=; b=p4o7Y2uigTf784zsEoq9brpI9YKz0ilEEMidNW3SlHhuKv4LW+6hgLHvVYLsNH0VCbpnTArC GmpC0VznFTPpK8uRt3trePbTcUEfeciO4t64xQIxDb73dmItIcirvKzEx7EDoJ8kFP238Qiq g00/t+Z3BYv9HOxRRb5H9OjmuoY= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b33d2a9.7f3f2e399c90-smtp-out-n02; Wed, 27 Jun 2018 18:08:41 -0000 (UTC) Date: Wed, 27 Jun 2018 11:08:40 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b33d2a8d9aef_50e72b0cb6f6dc0c91497@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] be0047: A couple more Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b33d2a8d9757_50e72b0cb6f6dc0c91335"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 18:08:45 -0000 ----==_mimepart_5b33d2a8d9757_50e72b0cb6f6dc0c91335 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/changelog-13 Home: https://github.com/quicwg/base-drafts Commit: be00478a5e4c5eb2f5350e7d0db0494cc3834c54 https://github.com/quicwg/base-drafts/commit/be00478a5e4c5eb2f5350e7d0db0494cc3834c54 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- A couple more **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b33d2a8d9757_50e72b0cb6f6dc0c91335-- From nobody Wed Jun 27 11:08:54 2018 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 120D1130DCB for ; Wed, 27 Jun 2018 11:08:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Qn9QX_uFuzmL for ; Wed, 27 Jun 2018 11:08:44 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5A1130E08 for ; Wed, 27 Jun 2018 11:08:44 -0700 (PDT) Date: Wed, 27 Jun 2018 11:08:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530122923; bh=U0v179VUiAbSddKf89zjMii2p4kwZHuXasy4VMgJ9E0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p+7xERFhnl/gr/bqUPVDDhrcrJaigbcKWSPelH/DVZSUHJEpNo2CVYDCPkvvgzpYb XX06k0vE5UzX64Fn3ICnQd3naYoFk1LM8/YNAGDNo1CBvRCXfRQSqlzKeTClRIZgak Cp1GMQhHoLlxt0gt1tyJtcoTGDn+UZbl6K0B4/8I= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33d2abbd5ab_61273fafe973cf84484299"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: MikeBishop X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 18:08:46 -0000 ----==_mimepart_5b33d2abbd5ab_61273fafe973cf84484299 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop pushed 1 commit. be00478 A couple more -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1488/files/6802896796a2114977c4215a47160eb1efffd351..be00478a5e4c5eb2f5350e7d0db0494cc3834c54 ----==_mimepart_5b33d2abbd5ab_61273fafe973cf84484299 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b33d2abbd5ab_61273fafe973cf84484299-- From nobody Wed Jun 27 11:13:48 2018 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 9E784130E95 for ; Wed, 27 Jun 2018 11:13:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 5yXJxpwQ6SAU for ; Wed, 27 Jun 2018 11:13:35 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF894130EB7 for ; Wed, 27 Jun 2018 11:13:35 -0700 (PDT) Date: Wed, 27 Jun 2018 11:13:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530123214; bh=SV8Icnbzap0kB5JsL8PCCys4OuA9wq4HaZqowLZZFhQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=D01MOiG9K8OBknnsrEG/4feCSNfx9KzKtLBH/3usBrqCphrRwG1Q8MQ38Tvk+GYh8 zO1ExWd435V2GUdTHNE7vkmFQ7awEhjri4J38oGF3jwtPSWKd2OLQnRzAgT/Jpoman AlhZyFDNIkwHix/ZYlHwDnsLhmw+5BiVUNrhJ/Bo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33d3cedff4b_7432af6c27a0f608537f"; 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.26 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: Wed, 27 Jun 2018 18:13:47 -0000 ----==_mimepart_5b33d3cedff4b_7432af6c27a0f608537f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. Added a couple things directly. Ship it! -- 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/1488#pullrequestreview-132549411 ----==_mimepart_5b33d3cedff4b_7432af6c27a0f608537f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

Added a couple things directly. Ship it!

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

----==_mimepart_5b33d3cedff4b_7432af6c27a0f608537f-- From nobody Wed Jun 27 11:38:19 2018 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 B73A6130E74 for ; Wed, 27 Jun 2018 11:38:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 WRq38EjxiMTG for ; Wed, 27 Jun 2018 11:38:16 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39EF0130E97 for ; Wed, 27 Jun 2018 11:38:16 -0700 (PDT) Date: Wed, 27 Jun 2018 11:38:15 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530124695; bh=DwK2L9XQK53P1fivAUYcyk8HZq70eZL/PlGyuTBnLlo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F7/REF18jRP0JuT2wiKseZg1s2ptVUk8tXSXFAtPIfD9ayQIKzGyeTAfdL9f/Er0e kJPBdu4AezgatL2W3TzAWYK0EGGcIqV812gpuL2H2+T73LToBGJkTr9Psw0LRG0d9u yk9PVvXPUMVuKo1bH2QbjQ7OWEgc4KY4SY4IZFYg= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection ID Sequence Number and Server's Preferred Address (#1483) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33d997824ad_770b2acc68086f609114e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 18:38:18 -0000 ----==_mimepart_5b33d997824ad_770b2acc68086f609114e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Do you remember why we needed a CID in the SPA? I can't seem to come up with a good reason for it. -- 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/1483#issuecomment-400787252 ----==_mimepart_5b33d997824ad_770b2acc68086f609114e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Do you remember why we needed a CID in the SPA? I can't seem to come up with a good reason for it.

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

----==_mimepart_5b33d997824ad_770b2acc68086f609114e-- From nobody Wed Jun 27 12:40:23 2018 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 B1FB6130E14 for ; Wed, 27 Jun 2018 12:40:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bbmWb6dbPPhJ for ; Wed, 27 Jun 2018 12:40:17 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A69481292F1 for ; Wed, 27 Jun 2018 12:40:17 -0700 (PDT) Date: Wed, 27 Jun 2018 12:40:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530128416; bh=EeqH3wV9+2B4LgQiZrW/5oWZtAZHQjBfdxlXZZGnFpM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QRIvy9G9oAnwRt5vS+5FVSoJsvUYwtVlOqHNXoPU4CbfYxQ5TTcdWHKBPp00zD9UT baQnNQePOUR6Zwa7l4BCUbWlyvwxeXFlHCR8q+vjyV6Z2BodzF+HoZFZhhq+jZsD/I NqsHVOMGePgiSFoxu3rPx/AVRZbvIroK1xqvswqo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection ID Sequence Number and Server's Preferred Address (#1483) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33e82091782_1a31d3fdd2037cf84801e3"; 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.26 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: Wed, 27 Jun 2018 19:40:20 -0000 ----==_mimepart_5b33e82091782_1a31d3fdd2037cf84801e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit So the client has a CID to probe with as soon as it finishes the handshake. Otherwise, the client has to delay until it receives a NEW_CONNECTION_ID frame. Hopefully that will be in the server's first 1-RTT packet, but it's still an additional wait the client has to introduce. (Or the client probes without changing CID, which is probably okay for a public web server but might not be universally.) -- 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/1483#issuecomment-400804736 ----==_mimepart_5b33e82091782_1a31d3fdd2037cf84801e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So the client has a CID to probe with as soon as it finishes the hands= hake. Otherwise, the client has to delay until it receives a NEW_CONNECT= ION_ID frame. Hopefully that will be in the server's first 1-RTT packet, = but it's still an additional wait the client has to introduce. (Or the c= lient probes without changing CID, which is probably okay for a public we= b server but might not be universally.)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b33e82091782_1a31d3fdd2037cf84801e3-- From nobody Wed Jun 27 13:37:47 2018 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 11F3A130E29 for ; Wed, 27 Jun 2018 13:37:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Xkk6CrQh518u for ; Wed, 27 Jun 2018 13:37:43 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 529DC130E25 for ; Wed, 27 Jun 2018 13:37:43 -0700 (PDT) Date: Wed, 27 Jun 2018 13:37:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530131862; bh=ZenJ3Do3FCtc0m7YhmdsnXtpnwtePcvCHjG6DrJvrDA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=u6xII1bOfL/UOlHHc56IY6dRmcoSYxPBwrH1c1of2I4mcaLpp0voY+SWP3ll+HfFn ecDwz4u96kk0p9yNAZuQ1rODcZZteo6QwSE72p8YN/bo/8re31bGQzchtm0jE+at9A jJ7uZb358ADZMPrAipdKQbd2UM7MoSqpxu/VIpIw= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33f5964047b_5e622ae69c860f5841972"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 27 Jun 2018 20:37:46 -0000 ----==_mimepart_5b33f5964047b_5e622ae69c860f5841972 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Because the Initial packet's token is after the rest of the long header, the packet number must be decrypted first to determine the starting offset of the Token Length field and then the Token field. This adds a requirement for DDoS Mitigation Devices, that would simple read the token field to validate address ownership before passing the packet along or sending a Retry packet of its own, to have crypto support. If the packet number followed the token, this would no longer be a requirement on the hardware. -- 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/1492 ----==_mimepart_5b33f5964047b_5e622ae69c860f5841972 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Because the Initial packet's token is after the rest of the long header, the packet number must be decrypted first to determine the starting offset of the Token Length field and then the Token field. This adds a requirement for DDoS Mitigation Devices, that would simple read the token field to validate address ownership before passing the packet along or sending a Retry packet of its own, to have crypto support. If the packet number followed the token, this would no longer be a requirement on the hardware.

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

----==_mimepart_5b33f5964047b_5e622ae69c860f5841972-- From nobody Wed Jun 27 13:41:05 2018 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 0B534130F96 for ; Wed, 27 Jun 2018 13:40:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 ZUGoZo-YczsM for ; Wed, 27 Jun 2018 13:40:53 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F39D130F7E for ; Wed, 27 Jun 2018 13:40:53 -0700 (PDT) Date: Wed, 27 Jun 2018 13:40:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530132052; bh=ied8yXfJRECbtjvDnIUErRXf9slitLkcll1d1HOww7c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OcQxNMLRnD7zWYlPuRgYkC4PbgLKqZQZCfxzSzXSPgtjvKyqvPSIod/C7mqywMU6D Men8IgxTKSs63P2TgdgqXprIhdZdgaQU6DpcGa2TABFOQ56DJpW6Msv5xlUrU+yoLh jWexr8K/lOQR9TB6OIplaGarpVTJI6puodADEpuo= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33f65445b28_3f443f8eeb0faf787680"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 27 Jun 2018 20:41:05 -0000 ----==_mimepart_5b33f65445b28_3f443f8eeb0faf787680 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Does the Token need a packet number? It already echos the DCID. -- 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/1492#issuecomment-400821852 ----==_mimepart_5b33f65445b28_3f443f8eeb0faf787680 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Does the Token need a packet number? It already echos the DCID.

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

----==_mimepart_5b33f65445b28_3f443f8eeb0faf787680-- From nobody Wed Jun 27 14:16:40 2018 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 64D2C130E2A for ; Wed, 27 Jun 2018 14:16:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vb0zQURj4l0a for ; Wed, 27 Jun 2018 14:16:36 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1C24124BE5 for ; Wed, 27 Jun 2018 14:16:36 -0700 (PDT) Date: Wed, 27 Jun 2018 14:16:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530134195; bh=d8/ITq6i4+2iSv/zik8PL10vYjb1fsUbyUGhOXdRuOE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DJ/mXgkJj1mDW2+zsUAsCgTIP87Tfw8zojeyj8LLDpHp2Zuu7BrRMVuegOuBDnDip XQBES2ZHvBQUulCblIkpPboTAPGA6SVHIvWrp+eQuer8o0mM4KmKDMH2w09+uLwqVq NMrfIhGeqmQVZOaIqCzVGhEZ7Ov8HJX0PO+E4z1U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33feb3a9c6e_3be53fb18e3a6f7c130453"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 21:16:39 -0000 ----==_mimepart_5b33feb3a9c6e_3be53fb18e3a6f7c130453 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that we need MUST NOT here. Tokens provided in Retry can be validated strictly, and allowing a client to change its source connection ID would make that harder. -- 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/1491#issuecomment-400831760 ----==_mimepart_5b33feb3a9c6e_3be53fb18e3a6f7c130453 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think that we need MUST NOT here. Tokens provided in Retry can be validated strictly, and allowing a client to change its source connection ID would make that harder.

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

----==_mimepart_5b33feb3a9c6e_3be53fb18e3a6f7c130453-- From nobody Wed Jun 27 14:19:45 2018 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 788D4124BE5 for ; Wed, 27 Jun 2018 14:19:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 dWa9JoGAff8O for ; Wed, 27 Jun 2018 14:19:41 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F885130E2A for ; Wed, 27 Jun 2018 14:19:41 -0700 (PDT) Date: Wed, 27 Jun 2018 14:19:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530134380; bh=y0u1rvXWddlbEhTg4mclL6iDBQOPXkt6wMHRZevm/UI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=g42Kll3qxJvhbdqPyCcEiAmmI9qOpDP3dBIY+KIVUmSzcWJAPlvQfAjOLqh9hxWDY KqXJ6o+3lk+xwyOxK5acZPUjYakYOaBGugIpkdf0viJNpySKRONv8ideBe4DHJtofm eNYF+DL5FVkNNOVBzOqumpjO2Ze1THbL3Iszs/R8= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b33ff6c44c15_12913f928a7fef843327"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Wed, 27 Jun 2018 21:19:44 -0000 ----==_mimepart_5b33ff6c44c15_12913f928a7fef843327 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. Agreed, MUST NOT > @@ -633,7 +633,11 @@ If the client received a Retry packet from the server and sends an Initial packet in response, then it sets the Destination Connection ID to the value from the Source Connection ID in the Retry packet. Changing Destination Connection ID also results in a change to the keys used to protect the Initial packet. It also -sets the Token field to the token provided in the Retry. +sets the Token field to the token provided in the Retry. Additionally, the +client SHOULD NOT change the Source Connection ID because the server may include +the connection ID as part of its token validation logic. If the client changes +the Source Connection ID in this case, it would likely trigger a new Retry to be nit: would likely -> could > @@ -633,7 +633,11 @@ If the client received a Retry packet from the server and sends an Initial packet in response, then it sets the Destination Connection ID to the value from the Source Connection ID in the Retry packet. Changing Destination Connection ID also results in a change to the keys used to protect the Initial packet. It also -sets the Token field to the token provided in the Retry. +sets the Token field to the token provided in the Retry. Additionally, the +client SHOULD NOT change the Source Connection ID because the server may include MUST NOT -- 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/1491#pullrequestreview-132613045 ----==_mimepart_5b33ff6c44c15_12913f928a7fef843327 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

Agreed, MUST NOT

In draft-ietf-quic-transport.md:

> @@ -633,7 +633,11 @@ If the client received a Retry packet from the server and sends an Initial
 packet in response, then it sets the Destination Connection ID to the value from
 the Source Connection ID in the Retry packet. Changing Destination Connection ID
 also results in a change to the keys used to protect the Initial packet. It also
-sets the Token field to the token provided in the Retry.
+sets the Token field to the token provided in the Retry. Additionally, the
+client SHOULD NOT change the Source Connection ID because the server may include
+the connection ID as part of its token validation logic. If the client changes
+the Source Connection ID in this case, it would likely trigger a new Retry to be

nit: would likely -> could

In draft-ietf-quic-transport.md:

> @@ -633,7 +633,11 @@ If the client received a Retry packet from the server and sends an Initial
 packet in response, then it sets the Destination Connection ID to the value from
 the Source Connection ID in the Retry packet. Changing Destination Connection ID
 also results in a change to the keys used to protect the Initial packet. It also
-sets the Token field to the token provided in the Retry.
+sets the Token field to the token provided in the Retry. Additionally, the
+client SHOULD NOT change the Source Connection ID because the server may include

MUST NOT

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

----==_mimepart_5b33ff6c44c15_12913f928a7fef843327-- From nobody Wed Jun 27 14:48:05 2018 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 0C300130E2A for ; Wed, 27 Jun 2018 14:48:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 6FuV3MmlsJD0 for ; Wed, 27 Jun 2018 14:48:00 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8DAF124BE5 for ; Wed, 27 Jun 2018 14:48:00 -0700 (PDT) Date: Wed, 27 Jun 2018 14:47:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136079; bh=TDVawyhm+URA3fHHFZnJpUOsSGrD7u/Lf7f+K5PgEfQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1JFJh2tXkTrqRfocUFwiEYUdaPm1UvYvhFECryd67dtDWQBV9mPULs1ofE3WBPApA KToBhjW0qsfwmds0OBuD/GIleFG/CQXiIb36WrlorhuijIppi8tV2hLss1QGiChS1m aAJsXvHBWGsbjLjqGrtCemGLg0NqPl5VDtzgPwT8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34060feb1fa_35843fc5d8f5cf8411774a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 21:48:04 -0000 ----==_mimepart_5b34060feb1fa_35843fc5d8f5cf8411774a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If we say that unknown stream types cause the stream to be ignored in total (w/ STOP_SENDING ideally), then frames and unknown stream types are equivalent. -- 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/1490#issuecomment-400839895 ----==_mimepart_5b34060feb1fa_35843fc5d8f5cf8411774a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If we say that unknown stream types cause the stream to be ignored in total (w/ STOP_SENDING ideally), then frames and unknown stream types are equivalent.

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

----==_mimepart_5b34060feb1fa_35843fc5d8f5cf8411774a-- From nobody Wed Jun 27 14:50:02 2018 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 DC2F0130E2A for ; Wed, 27 Jun 2018 14:50:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QZ6rE4vpEL0L for ; Wed, 27 Jun 2018 14:49:59 -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 68736124BE5 for ; Wed, 27 Jun 2018 14:49:59 -0700 (PDT) Date: Wed, 27 Jun 2018 14:49:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136198; bh=UOgYja2yTtcmv6XfmYczP+iLeFAruYLzcidLLjZoOVQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iOp0BvahlOUo6U0b5DUx2FrX7pmtjWXckDHsPCZOxvmaTZRNFjpak01DQ4Yj/qRPy /uHKslmgAZKicvN7iJix7hPbInfcBokWrw6gOH8WO5dvJ87g5WYaGNrZv+RK/Z9FV1 Gwa1FRZwWK1v3yHgh4y0zPZ0syGwhFLSOqIqAojo= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Connection ID Sequence Number and Server's Preferred Address (#1483) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b340686902de_354d3fc5d8f5cf841139dd"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 21:50:02 -0000 ----==_mimepart_5b340686902de_354d3fc5d8f5cf841139dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Also, routing to the new address may be contingent on the corresponding connection ID. -- 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/1483#issuecomment-400840386 ----==_mimepart_5b340686902de_354d3fc5d8f5cf841139dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Also, routing to the new address may be contingent on the corresponding connection ID.

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

----==_mimepart_5b340686902de_354d3fc5d8f5cf841139dd-- From nobody Wed Jun 27 14:51:34 2018 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 B93B5124BE5 for ; Wed, 27 Jun 2018 14:51:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 oLl6H5K_NUdd for ; Wed, 27 Jun 2018 14:51:30 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 437DE130E2A for ; Wed, 27 Jun 2018 14:51:30 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530136289; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=nR2rVnIit58Z37Jbr+uvsi6NZK+yR9fKRype+9r5ReM=; b=glIxemBGDpe7pc9XvFqeRoiqBhYyzzE/V3byoYOagJwgM2UU+QrDjwpskcDnqmXINvmOg+48 0Sq33QvU0rZhuJxEHYrygMZ03njyZqs+BakqCu31mJItjk6I/50pbJ1M+LLMm57HxAE167vu sjX+vXoPGDN4vKaGYnKZG87lPWs= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b3406e1.7f3efd1b2d20-smtp-out-n02; Wed, 27 Jun 2018 21:51:29 -0000 (UTC) Date: Wed, 27 Jun 2018 14:51:28 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b3406e0e74_36c02b22bd22dc1441889@hookshot-fe-31feec6.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ee2d80: Promote TLS changes Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3406e0b10_36c02b22bd22dc1441733"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 21:51:32 -0000 ----==_mimepart_5b3406e0b10_36c02b22bd22dc1441733 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/changelog-13 Home: https://github.com/quicwg/base-drafts Commit: ee2d80d54b68f12433cc53c4e10ac7bb809edc96 https://github.com/quicwg/base-drafts/commit/ee2d80d54b68f12433cc53c4e10ac7bb809edc96 Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Promote TLS changes **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3406e0b10_36c02b22bd22dc1441733-- From nobody Wed Jun 27 14:51:43 2018 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 2CF86124BE5 for ; Wed, 27 Jun 2018 14:51:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 sHOHXplQeM7Y for ; Wed, 27 Jun 2018 14:51:32 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A27E7130E2A for ; Wed, 27 Jun 2018 14:51:32 -0700 (PDT) Date: Wed, 27 Jun 2018 14:51:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136291; bh=ntM89tg6COyGPga0cMYemmHFWemzK6G6dkRjlmjhV4I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DeVa6toDoO+h8hzqxDZShzO4GQuqffEgQt4iT+FPuevFe6uMSexqp8TJGv6QcNCVC yYJNbaCNaOm45cab9ZD24RBwM6YJ/L8gWzQrvTLkutn7NWdJsMMYGcxLZpWnEkblPR ye9mQvr+Qs7gPPT0uMXADujrom1H43hTNWYNrjJQ= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3406e32c2fd_35ca2ab3e30bef5c22154c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 21:51:35 -0000 ----==_mimepart_5b3406e32c2fd_35ca2ab3e30bef5c22154c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. ee2d80d Promote TLS changes -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1488/files/be00478a5e4c5eb2f5350e7d0db0494cc3834c54..ee2d80d54b68f12433cc53c4e10ac7bb809edc96 ----==_mimepart_5b3406e32c2fd_35ca2ab3e30bef5c22154c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3406e32c2fd_35ca2ab3e30bef5c22154c-- From nobody Wed Jun 27 14:52:27 2018 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 59758130E2A for ; Wed, 27 Jun 2018 14:52:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 97l2jnPdanxN for ; Wed, 27 Jun 2018 14:52:23 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 97D06124BE5 for ; Wed, 27 Jun 2018 14:52:23 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530136342; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=AY/5EM3r6RcfFx+lnguFQ+fF7zx9DVsRRjQCFbNYCUE=; b=T6+ZVwCQq/q1EmwyKR49tfQ5RrAXtjn52Drme1+NK8gSEYtfh5e7NrlB66TyMp8grWAueHak x3x7rlkE66WuZKke5nKuM1Pwztc/vdHEICQsodHzNMhluiQyI4k3PU6xaLcja8wOWDonCaXL /dulGNU9dY2xYpNwI8so5SVb/O4= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b340715.7f583d0bdab0-smtp-out-n02; Wed, 27 Jun 2018 21:52:21 -0000 (UTC) Date: Wed, 27 Jun 2018 14:52:20 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b340714e047c_309f2ae963ed3c18508a4@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 89a889: Added change logs Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b340714e0087_309f2ae963ed3c185072c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 21:52:26 -0000 ----==_mimepart_5b340714e0087_309f2ae963ed3c185072c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 89a889049d2f78bdcdf4f0beb745b91d4c79c770 https://github.com/quicwg/base-drafts/commit/89a889049d2f78bdcdf4f0beb745b91d4c79c770 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Added change logs Commit: 6802896796a2114977c4215a47160eb1efffd351 https://github.com/quicwg/base-drafts/commit/6802896796a2114977c4215a47160eb1efffd351 Author: Martin Thomson Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Dirty edit buffer had a few more things in it Commit: be00478a5e4c5eb2f5350e7d0db0494cc3834c54 https://github.com/quicwg/base-drafts/commit/be00478a5e4c5eb2f5350e7d0db0494cc3834c54 Author: Mike Bishop Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md Log Message: ----------- A couple more Commit: ee2d80d54b68f12433cc53c4e10ac7bb809edc96 https://github.com/quicwg/base-drafts/commit/ee2d80d54b68f12433cc53c4e10ac7bb809edc96 Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Promote TLS changes Commit: 921c954b8bee07ced692a64c41cef44a55817d8e https://github.com/quicwg/base-drafts/commit/921c954b8bee07ced692a64c41cef44a55817d8e Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-http.md M draft-ietf-quic-qpack.md M draft-ietf-quic-recovery.md M draft-ietf-quic-tls.md M draft-ietf-quic-transport.md Log Message: ----------- Merge branch 'changelog-13' Commit: e48425a7ad60d306f1971cfe1f6b1f562f2e30ff https://github.com/quicwg/base-drafts/commit/e48425a7ad60d306f1971cfe1f6b1f562f2e30ff Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove merge trash Compare: https://github.com/quicwg/base-drafts/compare/86660ea4a201...e48425a7ad60 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b340714e0087_309f2ae963ed3c185072c-- From nobody Wed Jun 27 14:52:36 2018 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 B622E130E34 for ; Wed, 27 Jun 2018 14:52:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 5NYluAt03JW3 for ; Wed, 27 Jun 2018 14:52:26 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23731124BE5 for ; Wed, 27 Jun 2018 14:52:26 -0700 (PDT) Date: Wed, 27 Jun 2018 14:52:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136345; bh=1dm1t+A/JYYAL4+NNkHaBvts/g+OjXoiDixW/SBx7z0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tmLUEKy6r0ydNFCzQ/5XbWTtyMhCXQJQTf69LjJxmldS13tY/s/wMeryqbG4AquDb 02CWdpAc/x+3ExbHaQSk5ap/iYvrOVJDX90pl5oKw/05UKkppNXVHIDpJ2Tp+5ladc OCcCapMQw7VYGUTpQQVV6YxOSDUEJ9iZmqrmKYPM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Added change logs for -13 (#1488) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34071918eee_36c73fc5d8f5cf841336bc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 21:52:30 -0000 ----==_mimepart_5b34071918eee_36c73fc5d8f5cf841336bc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1488. -- 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/1488#event-1705001635 ----==_mimepart_5b34071918eee_36c73fc5d8f5cf841336bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1488.

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

----==_mimepart_5b34071918eee_36c73fc5d8f5cf841336bc-- From nobody Wed Jun 27 14:54:56 2018 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 3F3DF130E2A for ; Wed, 27 Jun 2018 14:54:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 dUF3LHoUEYrR for ; Wed, 27 Jun 2018 14:54:52 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797FD124BE5 for ; Wed, 27 Jun 2018 14:54:52 -0700 (PDT) Date: Wed, 27 Jun 2018 14:54:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136491; bh=qK/UpmkWbL/aI8gdy8eAr53RFddDgxtSbgzwN24PS34=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qCc2c50mEsOpbdY/JGY6VQamGYEzUhcN+0CnHSx3Td84gRGRSKtoUwVqzzlYqjwOa kjuPXayCkJHI1mp+yd8V6HMvrL8EcYQCwwRekNQwc9qaBKFYcK5PhyV8Ei2VuVJc1X qHLPTQP4yPS1LhidOlCZWWZ2Vb3FwouLgoR60Ndk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3407abc3113_780d3f96fcfd0f842652e2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 21:54:55 -0000 ----==_mimepart_5b3407abc3113_780d3f96fcfd0f842652e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It seems like @ianswett has the answer. It means that Retry will be specified like Version Negotiation, which is clumsy, but it's probably better that way. I have to ask, were people assuming that Retry used packet protection? I had not expected it to be, but I look and it seems like it does. -- 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/1492#issuecomment-400841528 ----==_mimepart_5b3407abc3113_780d3f96fcfd0f842652e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It seems like @ianswett has the = answer. It means that Retry will be specified like Version Negotiation, = which is clumsy, but it's probably better that way.

I have to ask, were people assuming that Retry used packet protection?= I had not expected it to be, but I look and it seems like it does.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3407abc3113_780d3f96fcfd0f842652e2-- From nobody Wed Jun 27 14:57:25 2018 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 C22F7130E34 for ; Wed, 27 Jun 2018 14:57:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 kdmop2HyIsmG for ; Wed, 27 Jun 2018 14:57:21 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93DC2124BE5 for ; Wed, 27 Jun 2018 14:57:21 -0700 (PDT) Date: Wed, 27 Jun 2018 14:57:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530136640; bh=YgqJ6brLsi+ITVCtLBaadfw0fVoUjFaaSksXx2T8XYk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uCAMKIKahKylcntCdKIMS0BqmMcLR6bE1XG+iWWeVQKt08mRnJfo/+x0aOj+5q//T QPm6MsZwqu1UshW/6aMzVOictnHOQpDjBpESOlzPmr4glt4ZB+T+kmuT7LSHYyQhCN Kv+CuGZ4+68eLok3bpwYUfnEsJIMHdsc0F6R+BJc= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b340840c8111_3dd63faf17cb4f84884bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 21:57:24 -0000 ----==_mimepart_5b340840c8111_3dd63faf17cb4f84884bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop > I thought there was text to the effect that changing the SCID during the handshake was effectively starting a fresh connection attempt, but I don't see it in the draft. FWIW, my understanding is that the existing text is (emphasis mine): > During the handshake, an endpoint might receive multiple packets with the long header, and thus be given multiple opportunities to update the Destination Connection ID it sends. A client MUST only change the value it sends in the Destination Connection ID in response to the first packet of each type it receives from the server (Retry or Initial); **a server MUST set its value based on the Initial packet. Any additional changes are not permitted; if subsequent packets of those types include a different Source Connection ID, they MUST be discarded.** This avoids problems that might arise from stateless processing of multiple Initial packets producing different connection IDs. > [4.7 Connection ID Encoding](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#connection-id-encoding) Anyways I agree that this is written from server's viewpoint, and I agree that we should have a "MUST NOT" for the client. -- 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/1491#issuecomment-400842078 ----==_mimepart_5b340840c8111_3dd63faf17cb4f84884bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@MikeBishop

I thought there was text to the effect that changing the SCID during t= he handshake was effectively starting a fresh connection attempt, but I d= on't see it in the draft.

FWIW, my understanding is that the existing text is (emphasis mine):

During the handshake, an endpoint might receive multiple packets with = the long header, and thus be given multiple opportunities to update the D= estination Connection ID it sends. A client MUST only change the value it= sends in the Destination Connection ID in response to the first packet o= f each type it receives from the server (Retry or Initial); a ser= ver MUST set its value based on the Initial packet. Any additional change= s are not permitted; if subsequent packets of those types include a diffe= rent Source Connection ID, they MUST be discarded. This avoids p= roblems that might arise from stateless processing of multiple Initial pa= ckets producing different connection IDs.
4.7 Connection ID Encoding

Anyways I agree that this is written from server's viewpoint, and I ag= ree that we should have a "MUST NOT" for the client.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b340840c8111_3dd63faf17cb4f84884bf-- From nobody Wed Jun 27 15:07:52 2018 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 CA9C8130E2C for ; Wed, 27 Jun 2018 15:07:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 A-9oAJuJ8fao for ; Wed, 27 Jun 2018 15:07:48 -0700 (PDT) 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 C2480124BE5 for ; Wed, 27 Jun 2018 15:07:48 -0700 (PDT) Date: Wed, 27 Jun 2018 15:07:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530137268; bh=nva7y9QTD+4w+jOBgatplFAEnnPfHIA2dGEa2kNYZgQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=av7yzIng4ibsrjhZEQ9/l97Inc/PUNPRBDf1biohQoZBZPuaYqXtDzvlfICW5xZe3 /1dCQ/4bZIsqokHZzVebFrVMupkUeMJ7a1lr7bVoWUYTBGdE4h38aV1Ko+IQHMG9I9 mZ0OP5ZqwlBqndkGKfjgFr6eZ6YbDOFphk/Qi3tk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b340ab3f276e_4d913fd915848f7c5834f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 22:07:51 -0000 ----==_mimepart_5b340ab3f276e_4d913fd915848f7c5834f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett @martinthomson Isn't the issue about the format of the *Initial* packet, not about *Retry*? I agree with @nibanks that the current format of the Initial packet that places token after packet number is incorrect, for two reasons: * token is not a good source of randomness for PNE * token should be accessible by middleboxes that do not want to deal with PNE -- 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/1492#issuecomment-400844693 ----==_mimepart_5b340ab3f276e_4d913fd915848f7c5834f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@ianswett @martinthomson Isn't the issue about the format of the = Initial packet, not about Retry?

I agree with @nibanks that the cu= rrent format of the Initial packet that places token after packet number = is incorrect, for two reasons:

  • token is not a good source of randomness for PNE
  • token should be accessible by middleboxes that do not want to deal wi= th PNE

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b340ab3f276e_4d913fd915848f7c5834f-- From nobody Wed Jun 27 15:08:55 2018 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 2C73E130E2C for ; Wed, 27 Jun 2018 15:08:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 YgTTLTWYT4Tq for ; Wed, 27 Jun 2018 15:08:51 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64855124BE5 for ; Wed, 27 Jun 2018 15:08:51 -0700 (PDT) Date: Wed, 27 Jun 2018 15:08:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530137330; bh=3EoZ+hFy5hlZV4SiIQLis3CW/jFo188/Bhj8WChHJZA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EpNbtBK2ROovrpRnEHqq5yxDrzDlRqyvzeFh610EnraIZK+leRTEfGZijTtBSHi76 kGETyfN1KjFZox2ZsXJmaGJorXog82gELpoK11BT6YUZ4smRuMMPDX7paXgB4LGItj h/NIuKun/EASujBuHk8kmTLpMONKh7ixoYYbWzho= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b340af2bd463_544f2ac534c14f5c522b7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Wed, 27 Jun 2018 22:08:54 -0000 ----==_mimepart_5b340af2bd463_544f2ac534c14f5c522b7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson > I have to ask, were people assuming that Retry used packet protection? I had not expected it to be, but I look and it seems like it does. My understanding is that the outcome of stream 0 DT was to have it _outside_ of packet protection. -- 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/1492#issuecomment-400844948 ----==_mimepart_5b340af2bd463_544f2ac534c14f5c522b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson

I have to ask, were people assuming that Retry used packet protection? I had not expected it to be, but I look and it seems like it does.

My understanding is that the outcome of stream 0 DT was to have it outside of packet protection.

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

----==_mimepart_5b340af2bd463_544f2ac534c14f5c522b7-- From nobody Wed Jun 27 15:33:58 2018 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 E148E130E2C for ; Wed, 27 Jun 2018 15:33:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 1ox-6GPWLt7s for ; Wed, 27 Jun 2018 15:33:47 -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 46AA2130E2E for ; Wed, 27 Jun 2018 15:33:47 -0700 (PDT) Date: Wed, 27 Jun 2018 15:33:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530138826; bh=PuhD9HzzX/xnfBACsv1nLwnzJXxYCNUBSKyG6bbr9xs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EoAJPST5qo5xODT/amBxuUNfLNGuXd8iIoz43LdbjWelYAlqpOLdGnBVj4bIrcY9K /7iqnvJTb02cudyL1IbkVPasrkuauGlihcyFXLxYP6JEnoMdCLuvVNGlI2d9t7bHUD DClyFfDElK0lmlOs+malJicaF5WhV3B6tno/LAiA= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3410ca6e5a8_6bc92af2c287af5c68772"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 22:33:50 -0000 ----==_mimepart_5b3410ca6e5a8_6bc92af2c287af5c68772 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @nibanks pushed 1 commit. 6d48169 should -> must -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1491/files/93b705e92da517221c50d4e4ee4a7d128c9e5faa..6d48169b404bd0ab239c82f9f735ec8faf2d9ebf ----==_mimepart_5b3410ca6e5a8_6bc92af2c287af5c68772 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3410ca6e5a8_6bc92af2c287af5c68772-- From nobody Wed Jun 27 15:34:23 2018 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 09986130E3B for ; Wed, 27 Jun 2018 15:34:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 uXA5J-gC3j4p for ; Wed, 27 Jun 2018 15:34:18 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37261130E2C for ; Wed, 27 Jun 2018 15:34:18 -0700 (PDT) Date: Wed, 27 Jun 2018 15:34:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530138857; bh=gSPu/+5VH0OMXs15Ebc6+BgKWqBy67dnWJz9RVBuqWw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ve70eY9aPDJacb2o9GY0EICRbIE5pS72Lnum07Zv77jlVWRrRQFGZgdgO1hHfWrX7 Bo4kA4LzECJtyPiPXCUVJ29th2INFsYJGdEbdFFqlJoykNterxxyzqq6rC3/DbHdzE Mx/ew586CyjutBSQFasjDpCstnX2j5A1+2UE20iU= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3410e9989b5_71f82af5b1beef5c662bc"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 22:34:22 -0000 ----==_mimepart_5b3410e9989b5_71f82af5b1beef5c662bc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit So taking Martin's point in mind, what about something like: _Implementations SHOULD NOT send stream types that the peer is not already known to support. Recipients of unknown stream types MUST send a STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE. Greased stream types are always classed as unknown and unsupported._ This requires a receiver to only parse the first 8 bytes of a stream. It would help to provide some guidance for HTTP/QUIC extension authors to make it clear that a mechanism (e.g. SETTINGS) for negotiating extension stream types is required, and that failure to do this will invoke the ignorant behaviour. -- 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/1490#issuecomment-400850963 ----==_mimepart_5b3410e9989b5_71f82af5b1beef5c662bc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

So taking Martin's point in mind, what about something like:

Implementations SHOULD NOT send stream types that the peer is not = already known to support. Recipients of unknown stream types MUST send a = STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE. Grease= d stream types are always classed as unknown and unsupported.

This requires a receiver to only parse the first 8 bytes of a stream.<= /p>

It would help to provide some guidance for HTTP/QUIC extension authors= to make it clear that a mechanism (e.g. SETTINGS) for negotiating extens= ion stream types is required, and that failure to do this will invoke the= ignorant behaviour.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3410e9989b5_71f82af5b1beef5c662bc-- From nobody Wed Jun 27 15:35:05 2018 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 18DF4130E2C for ; Wed, 27 Jun 2018 15:35:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 QCx7NnjrE1qu for ; Wed, 27 Jun 2018 15:35:00 -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 0E98A130E2E for ; Wed, 27 Jun 2018 15:35:00 -0700 (PDT) Date: Wed, 27 Jun 2018 15:34:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530138898; bh=zb192PKE5BgoM0TOtMCASmYiq9Zby6uO1nbOqE96yAw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=meFqSVG8a78P+QkYOopVlWITOt0cMugXjJD9UtsVHQNDyN4FLkd46wWYG8jfksoZn 4/LR1BgbU9RLvctfORFeSe2mX6RYzFAkgPf3BMJOuboJiIQ1badMMOsQwEXpOb5cBM ZKcCUTX8G0pkzPa3g3yHOBiZbUmT2B3O3DpWGY14= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34111254e2d_68e33f8d09116f7c86954"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Wed, 27 Jun 2018 22:35:03 -0000 ----==_mimepart_5b34111254e2d_68e33f8d09116f7c86954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, the issue here is the client **Initial** packet and we did agree to keep it **outside** of packet protection to reduce the complexity for DDoS mitigation. -- 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/1492#issuecomment-400851113 ----==_mimepart_5b34111254e2d_68e33f8d09116f7c86954 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, the issue here is the client Initial packet and we did agree to keep it outside of packet protection to reduce the complexity for DDoS mitigation.

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

----==_mimepart_5b34111254e2d_68e33f8d09116f7c86954-- From nobody Wed Jun 27 16:34:19 2018 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 0F539130E3F for ; Wed, 27 Jun 2018 16:34:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Ei1YKeqNjE7m for ; Wed, 27 Jun 2018 16:34:16 -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 7058F130E39 for ; Wed, 27 Jun 2018 16:34:16 -0700 (PDT) Date: Wed, 27 Jun 2018 16:34:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530142454; bh=vlRjdB4BEv+M3fzRXSFORn8GwmzE2xxVUTVEU5cE8Zk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QfLW2j3Hikjf0ihxpp3x3F41oUiu9FMNj6KtIBC3HMVQAXMGvZhIFY/mqceb1qM8E 8KeAZIVEAOgK8sM2Evv+k8Ru7jUw/5sNy5u6etF6xX1I+1oyI0WvsdsPAfjYSsWLuE gYOTwYhB+gp8gxC+fY0GDAxMmuCRjZ97KN8aJi50= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b341ef6b0c5d_20e02b1ebedb0f5896760"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Wed, 27 Jun 2018 23:34:18 -0000 ----==_mimepart_5b341ef6b0c5d_20e02b1ebedb0f5896760 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 6a68e07 Removing extra text -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1491/files/6d48169b404bd0ab239c82f9f735ec8faf2d9ebf..6a68e074e84f04e70a186294a3e468c3c98cef5b ----==_mimepart_5b341ef6b0c5d_20e02b1ebedb0f5896760 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b341ef6b0c5d_20e02b1ebedb0f5896760-- From nobody Wed Jun 27 16:35:31 2018 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 DB271130E40 for ; Wed, 27 Jun 2018 16:35:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 xWSHpHqM4uby for ; Wed, 27 Jun 2018 16:35:27 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 341CB130E39 for ; Wed, 27 Jun 2018 16:35:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530142526; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=8NLsiQ9zQfj9E0K7Cfn9psqhSCJYIpjnwi0YzVb9QYU=; b=z6liUlNC8Gl90o7Yw2Y2Q4ie0uosj+cBlGVkTizK4HhiAveub/qjBdfYA6Nj4hWnzcK1O87u tAWUuxBqwRWHvRdIjS96omHxuRAzTCDeB9AMSQyujjOO19mLsSTsTYCuu+CSTzhvv4WcOK2Z pLuwOtNyQVlxl727eGDAeIDBv2A= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b341f3d.7fea131f3870-smtp-out-n01; Wed, 27 Jun 2018 23:35:25 -0000 (UTC) Date: Wed, 27 Jun 2018 16:35:24 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b341f3cc15c3_1bd2b2422fd1c103016@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 93b705: Don't Change Source CID After Retry Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b341f3cc11f1_1bd2b2422fd1c10300c9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Wed, 27 Jun 2018 23:35:29 -0000 ----==_mimepart_5b341f3cc11f1_1bd2b2422fd1c10300c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 93b705e92da517221c50d4e4ee4a7d128c9e5faa https://github.com/quicwg/base-drafts/commit/93b705e92da517221c50d4e4ee4a7d128c9e5faa Author: Nick Banks Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Don't Change Source CID After Retry Commit: 6d48169b404bd0ab239c82f9f735ec8faf2d9ebf https://github.com/quicwg/base-drafts/commit/6d48169b404bd0ab239c82f9f735ec8faf2d9ebf Author: Nick Banks Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- should -> must Commit: 6a68e074e84f04e70a186294a3e468c3c98cef5b https://github.com/quicwg/base-drafts/commit/6a68e074e84f04e70a186294a3e468c3c98cef5b Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Removing extra text Commit: 2991507bc0a635c4324762f51c558328603e79f6 https://github.com/quicwg/base-drafts/commit/2991507bc0a635c4324762f51c558328603e79f6 Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1491 from nibanks/pr/no-cid-change-after-retry Don't Change Source CID After Retry Compare: https://github.com/quicwg/base-drafts/compare/e48425a7ad60...2991507bc0a6 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b341f3cc11f1_1bd2b2422fd1c10300c9-- From nobody Wed Jun 27 16:35:40 2018 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 3C0C4130E40 for ; Wed, 27 Jun 2018 16:35:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 H32W9zAAE6QL for ; Wed, 27 Jun 2018 16:35:28 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7350B130E3F for ; Wed, 27 Jun 2018 16:35:28 -0700 (PDT) Date: Wed, 27 Jun 2018 16:35:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530142527; bh=aDPdqrsru9di5okfmx5t0dww5pfnOad53QxZaz/X2CM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=b4uF4Oxd2HvI5PUN/+RC2apQMJ7P7iI2+r4+2TlK+4OcIM3hNFcEo/WGKSP/QXqk2 owG16P9uT3q45DDfqtNWmzCL3vritPvTVrm7y97Lss8yYjeYqhHv5ryEFAIDbadmTy 46jDxnR9tvmi43SJ1g9G40fofjwq0Q2/SwfK1ovk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b341f3f7f77c_90b2aeb84462f5466154"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 23:35:31 -0000 ----==_mimepart_5b341f3f7f77c_90b2aeb84462f5466154 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1491. -- 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/1491#event-1705140302 ----==_mimepart_5b341f3f7f77c_90b2aeb84462f5466154 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1491.

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

----==_mimepart_5b341f3f7f77c_90b2aeb84462f5466154-- From nobody Wed Jun 27 16:35:47 2018 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 BDDB1130E3F for ; Wed, 27 Jun 2018 16:35:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 JLyqmnF8dSxK for ; Wed, 27 Jun 2018 16:35:29 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18045130E39 for ; Wed, 27 Jun 2018 16:35:29 -0700 (PDT) Date: Wed, 27 Jun 2018 16:35:27 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530142527; bh=j6j73MM2SYKUob1fUsKn37IbIGBzGparQpMVP5c4d2A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EZc7plWaZq7HSnwWkYCTM5sxmSSskZfyJ2suFK/iYfgJw0qrZtpiwMH0uZ5jMehsD 96GEKzCVnZcTFWMjYR+JLfK+4NLPv0KNbh/7asl/yPBfld6fLBTBDTFocWJotabkl9 ywrhJAsaGE2hI8HZu7nTavOQ7BsmfmuMxDclNTOo= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Retry Token Makeup (#1474) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b341f3f6621c_260a2ac6a1d86f5c4395c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 23:35:31 -0000 ----==_mimepart_5b341f3f6621c_260a2ac6a1d86f5c4395c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #1474 via #1491. -- 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/1474#event-1705140305 ----==_mimepart_5b341f3f6621c_260a2ac6a1d86f5c4395c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #1474 via #1491.

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

----==_mimepart_5b341f3f6621c_260a2ac6a1d86f5c4395c-- From nobody Wed Jun 27 16:35:52 2018 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 4884F130E41 for ; Wed, 27 Jun 2018 16:35:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 kB4ilsGAW0iw for ; Wed, 27 Jun 2018 16:35:31 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900F8130E40 for ; Wed, 27 Jun 2018 16:35:31 -0700 (PDT) Date: Wed, 27 Jun 2018 16:35:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530142531; bh=wUZ51qy3ZCAyG8mHC5V8wuPly9vjz1HCB8W/2y9VwO0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FDUBYCc6MJKfsQcSnHN7zTd7tSR+VOhqMqSb7Wll9Q3ZTOQGrNxj3jCxX9vZvi5do uq9BKVvUbsyBNDzr+rKDlQQ2LgARpNtPvvmTPwzEQW0PmxrtdtIBBSWY0+sF9UDbFo GMJc3CfPkYEmfmaM9Stn1W1+y71mpW6CErb3k3bc= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b341f42f2850_7c212ad982054f5c7793b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 27 Jun 2018 23:35:34 -0000 ----==_mimepart_5b341f42f2850_7c212ad982054f5c7793b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks Nick. This will make -13. I consider it editorial (based on the text @kazuho cites, which should have been generic.) There are a bunch more changes we need to consider with Retry, but this at least clears one of those up. -- 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/1491#issuecomment-400863237 ----==_mimepart_5b341f42f2850_7c212ad982054f5c7793b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Thanks Nick. This will make -13. I consider it editorial (based on the text @kazuho cites, which should have been generic.) There are a bunch more changes we need to consider with Retry, but this at least clears one of those up.

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

----==_mimepart_5b341f42f2850_7c212ad982054f5c7793b-- From nobody Wed Jun 27 17:13:10 2018 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 858C7130E45 for ; Wed, 27 Jun 2018 17:13:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 kRQ2BU7r8gty for ; Wed, 27 Jun 2018 17:13:05 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68653130E46 for ; Wed, 27 Jun 2018 17:13:05 -0700 (PDT) Date: Wed, 27 Jun 2018 17:13:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530144784; bh=1KpEYW1GxSd3DAXgRyFG+OLx98By0SKqELWVDosIj1U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xj9FRov+NKsUwdNT2WZMPATHqepmibe8rsMIcJCGDvRjn9O7N9bjYBDCBDVBSl1w+ xmAA+BJ6JvBOOj0qCT+mnmOw6bbkO/6oKGX0Uxqdn7/RbKjRk/hB3lr+r0S2kJVdok VjMPmoXw1A9NOL+5PZEYHh69SfmCELQLwMvLrhNg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34281082dd1_72e03f993a280f8896767"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 00:13:09 -0000 ----==_mimepart_5b34281082dd1_72e03f993a280f8896767 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Then let's put it before the Length field, outside encryption. -- 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/1492#issuecomment-400869648 ----==_mimepart_5b34281082dd1_72e03f993a280f8896767 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Then let's put it before the Length field, outside encryption.

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

----==_mimepart_5b34281082dd1_72e03f993a280f8896767-- From nobody Wed Jun 27 17:13:59 2018 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 D738D130E46 for ; Wed, 27 Jun 2018 17:13:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 7PrKT0sLC6Be for ; Wed, 27 Jun 2018 17:13:56 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16DB1130E45 for ; Wed, 27 Jun 2018 17:13:56 -0700 (PDT) Date: Wed, 27 Jun 2018 17:13:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530144835; bh=Gv98E59RWRDblSFcoknwt3kRFMQrZF4Pk5MMTaL2gUg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ftxyMoYPINS6Yp1V9tS1wB4Ed+xW6VjZjF4GCgkI0vJcZUg0r+UwRSM62fptw3HlD YF2OmFgNQ2+WgkSuxIDozzvSdFjk1CA3vxg7XY0TE7j1O9CkY0lAD8UP759yebsGSS mfefT8e7Dn32CPCbXsgnaDiWb5gHz7fwlAH+/Kzs= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3428436fc7c_11643ffde613af7812226f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 28 Jun 2018 00:13:58 -0000 ----==_mimepart_5b3428436fc7c_11643ffde613af7812226f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue > So taking Martin's point in mind, what about something like: > > _Implementations SHOULD NOT send stream types that the peer is not already known to support. Recipients of unknown stream types MUST send a STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE. Greased stream types are always classed as unknown and unsupported._ Sounds good to me. Though I might prefer using "MAY" instead of "MUST" for if STOP_SENDING should be sent. For example, if the entire flow of the unidirectional stream (i.e. from the beginning of the stream to EOS) fits in a single packet, I do not think that there is a strong reason to require the peer to send STOP_SENDING. > It would help to provide some guidance for HTTP/QUIC extension authors to make it clear that a mechanism (e.g. SETTINGS) for negotiating extension stream types is required, I am not sure if such requirement is necessary. In fact, I would argue that it would be beneficial allow extended stream types to be sent without negotiation. For example, a server might send additional certificates before receiving the client's SETTINGS frame (i.e. by using in it's 0.5 RTT window, which would be idle time). Or, a client might send a cache digest before observing the server's SETTINGS frame. To generalize the concept, I would argue that both frames and streams defined as extensions should be allowed to be sent without negotiation. The only differences are that streams can be reset by peer (by using STOP_SENDING), and that they would not suffer from HoLB (therefore it is sensible to use unidirectional streams with extended types for sending information that would have been exchanged using stream 0 of HTTP/2). -- 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/1490#issuecomment-400869779 ----==_mimepart_5b3428436fc7c_11643ffde613af7812226f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@LPardue

So taking Martin's point in mind, what about something like:

Implementations SHOULD NOT send stream types that the peer is not = already known to support. Recipients of unknown stream types MUST send a = STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE. Grease= d stream types are always classed as unknown and unsupported.

Sounds good to me. Though I might prefer using "MAY" instead of "MUST"= for if STOP_SENDING should be sent. For example, if the entire flow of t= he unidirectional stream (i.e. from the beginning of the stream to EOS) f= its in a single packet, I do not think that there is a strong reason to r= equire the peer to send STOP_SENDING.

It would help to provide some guidance for HTTP/QUIC extension authors= to make it clear that a mechanism (e.g. SETTINGS) for negotiating extens= ion stream types is required,

I am not sure if such requirement is necessary. In fact, I would argue= that it would be beneficial allow extended stream types to be sent witho= ut negotiation.

For example, a server might send additional certificates before receiv= ing the client's SETTINGS frame (i.e. by using in it's 0.5 RTT window, wh= ich would be idle time). Or, a client might send a cache digest before ob= serving the server's SETTINGS frame.

To generalize the concept, I would argue that both frames and streams = defined as extensions should be allowed to be sent without negotiation. T= he only differences are that streams can be reset by peer (by using STOP_= SENDING), and that they would not suffer from HoLB (therefore it is sensi= ble to use unidirectional streams with extended types for sending informa= tion that would have been exchanged using stream 0 of HTTP/2).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3428436fc7c_11643ffde613af7812226f-- From nobody Wed Jun 27 17:17:22 2018 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 84E95130E45 for ; Wed, 27 Jun 2018 17:17:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 c3ApIlQP0Icu for ; Wed, 27 Jun 2018 17:17:19 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1A69130E4C for ; Wed, 27 Jun 2018 17:17:18 -0700 (PDT) Date: Wed, 27 Jun 2018 17:17:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530145037; bh=RltM+xJjY62VFK5wabunFz0egaEP9MAMxEHQ8KTsnXw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jcAs8+XVodIk9tZEuKhSNPbjuMopr0x2BeZIwOjXHXol/7lJhj6q89f4nIN/gdlC+ TNx2nZfGXMG6Mbo1Z1s5J3uT5LSAQ7nmvB5e9fBe8NBVSreOg81yHFp754CSybP6mX M7785DU1cj3GcvZoKvaKUipnFXwlqolhksRIh/YA= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34290dda1db_2bcd3fd78cb62f805111a"; 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.26 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: Thu, 28 Jun 2018 00:17:21 -0000 ----==_mimepart_5b34290dda1db_2bcd3fd78cb62f805111a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that's reasonable. Another point where I wish we had an API / interface specification for the transport: I need a verb that clearly means "STOP_SENDING if the stream hasn't yet closed, but do nothing if it has." Stating in the HTTP document that a particular QUIC frame needs to be generated is not good encapsulation. -- 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/1490#issuecomment-400870272 ----==_mimepart_5b34290dda1db_2bcd3fd78cb62f805111a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think that's reasonable. Another point where I wish we had an API /= interface specification for the transport: I need a verb that clearly m= eans "STOP_SENDING if the stream hasn't yet closed, but do nothing if it = has." Stating in the HTTP document that a particular QUIC frame needs to= be generated is not good encapsulation.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b34290dda1db_2bcd3fd78cb62f805111a-- From nobody Wed Jun 27 17:26:08 2018 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 9636E130E54 for ; Wed, 27 Jun 2018 17:26:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 EmX5oEe0qi1r for ; Wed, 27 Jun 2018 17:26:04 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD8EE130E53 for ; Wed, 27 Jun 2018 17:26:04 -0700 (PDT) Date: Wed, 27 Jun 2018 17:26:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530145564; bh=rk1EGzunXOtiZbTqQKMB4nxHtZ87SMzSMr0RkPrY4pA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rJmytPOOZSKWtBUtjmZ83HpiVoArJsQji9ZGSJTmHIYQRYrNu88D1yWo4Y/IViqPJ pWl41zd12bYSq1Nmi/ckC5nE2l2dfg6arMqncwTr2+b4sdUp4w4RyI7VaFEO4CSUai zqGHeCJutCLvnbP5tvviAipvJ3Ee1g9zVD038v8E= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b342b1c4ea97_76b73f8cccbd2f8417164"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 28 Jun 2018 00:26:07 -0000 ----==_mimepart_5b342b1c4ea97_76b73f8cccbd2f8417164 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My preference goes to numbering each Connection ID *the endpoint provides* contiguously, starting from zero. To be precise: * SCID of the Initial packet is "zero" * CID of SPA is "one", if exists * CID being exchanged using NEW_CONNECTION_ID frames will start from "one" (if a CID is not provided by the endpoint using SPA), or "two" (if SPA was used) I believe that the definition is clear, and that it is also easy to implement. An implementation is required to have a structure that drops duplicate NEW_CONNECTION_ID frames. Having non-negative sequence numbers for SCID of the Initial packet and CID in SPA is only a matter of how we setup the structure. -- 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/1484#issuecomment-400871736 ----==_mimepart_5b342b1c4ea97_76b73f8cccbd2f8417164 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

My preference goes to numbering each Connection ID the endpoint pr= ovides contiguously, starting from zero.

To be precise:

  • SCID of the Initial packet is "zero"
  • CID of SPA is "one", if exists
  • CID being exchanged using NEW_CONNECTION_ID frames will start from "o= ne" (if a CID is not provided by the endpoint using SPA), or "two" (if SP= A was used)

I believe that the definition is clear, and that it is also easy to im= plement.

An implementation is required to have a structure that drops duplicate= NEW_CONNECTION_ID frames. Having non-negative sequence numbers for SCID = of the Initial packet and CID in SPA is only a matter of how we setup the= structure.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b342b1c4ea97_76b73f8cccbd2f8417164-- From nobody Wed Jun 27 17:37:53 2018 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 F1B5D130E5F for ; Wed, 27 Jun 2018 17:37:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 rgYE_nC9FYll for ; Wed, 27 Jun 2018 17:37:49 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46526130E5A for ; Wed, 27 Jun 2018 17:37:49 -0700 (PDT) Date: Wed, 27 Jun 2018 17:37:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530146268; bh=v+RObbutX8QEdj6F0zJnC2H42IrnlhvHUsWj8rHHZ3A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HitgQ+7zPQchueIgxFM3ZsuRHBtwDgNg7L1ZzkE5IFY+zrp2RScMrUr7YahkfLRGP lstL5jIzNwPY0KcGHa6ojCs4XhN91IFaBs9q9Gr7eFlY+Xad9lq689nCIolXul+VZA pvtzzvhgYPamJBmVWRs8ryjrrKan3ZaYC1tCdRhA= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b342ddc7a01c_2213fb4a761af80109397"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 00:37:51 -0000 ----==_mimepart_5b342ddc7a01c_2213fb4a761af80109397 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit "ignore unicast stream reception"? It could be argued that encapsulation is ready broken by in the document by the text that refers to generating RST_STREAM frames. -- 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/1490#issuecomment-400873827 ----==_mimepart_5b342ddc7a01c_2213fb4a761af80109397 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

"ignore unicast stream reception"?

It could be argued that encapsulation is ready broken by in the document by the text that refers to generating RST_STREAM frames.

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

----==_mimepart_5b342ddc7a01c_2213fb4a761af80109397-- From nobody Wed Jun 27 17:38:12 2018 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 053AC130E5F for ; Wed, 27 Jun 2018 17:38:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 5qdIvpbUDF5O for ; Wed, 27 Jun 2018 17:38:06 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 AC9EE130E5A for ; Wed, 27 Jun 2018 17:38:06 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530146286; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=pYFzLOYQSUbjW9ZVD1rX/KAJWJ3FFuUjsMsbIoMtlhQ=; b=PyhjWKFcGSK956RlxI+YqloPeLQjv4Vq+hB8QrcgVZxnU73XSSpub+/EYptUY50XT5+CjAPR esFp+RuY7a6oDhHbAhUpI0QHFrldqPhnf4xPce4/26YUdxd/I5TktUDp+ikQzNO9R63PzMZP L8OpUyYRMMZQvIwiicI8rsBS+74= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b342ded.7fdff60849c0-smtp-out-n01; Thu, 28 Jun 2018 00:38:05 -0000 (UTC) Date: Wed, 27 Jun 2018 17:38:04 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b342dec66c7f_db82ae1a2143c108171@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b342dec668a1_db82ae1a2143c108162c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 00:38:11 -0000 ----==_mimepart_5b342dec668a1_db82ae1a2143c108162c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/tags/draft-ietf-quic-http-13 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b342dec668a1_db82ae1a2143c108162c-- From nobody Wed Jun 27 17:38:18 2018 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 C0373130E5A for ; Wed, 27 Jun 2018 17:38:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 GuYg4QMIFQrC for ; Wed, 27 Jun 2018 17:38:11 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 9501A130E58 for ; Wed, 27 Jun 2018 17:38:11 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530146290; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=vPiOEQ73y3IldnLEMIJ3xyIds2+aOI1RZ77ZIR4FwMA=; b=VFe3NzNN5SoQpZPIQQW3ggfTxGb0vnll/IaXMZQz7ngbh0NB/Q6dkVs5Gul8auK9ok7nmX2A CBwd5G+JIW6t9SuvSvK0kz7BrC/zc6gRZG6wLCF5TE0TRpSX8I7aQXXeKMrOVVgRjRVB3aYp awLL4pNSfpka7a7rnWvwFDjv9a0= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b342df2.7f77be1e1d50-smtp-out-n01; Thu, 28 Jun 2018 00:38:10 -0000 (UTC) Date: Wed, 27 Jun 2018 17:38:10 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b342df2774c1_6a882b15f08b9c1057674@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b342df2764be_6a882b15f08b9c105757f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 00:38:13 -0000 ----==_mimepart_5b342df2764be_6a882b15f08b9c105757f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/tags/draft-ietf-quic-qpack-01 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b342df2764be_6a882b15f08b9c105757f-- From nobody Wed Jun 27 17:38:27 2018 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 E1FDE130E5F for ; Wed, 27 Jun 2018 17:38:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 34AdVCh0_LEp for ; Wed, 27 Jun 2018 17:38:16 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 A079A130E5A for ; Wed, 27 Jun 2018 17:38:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530146296; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=wTfbMRjLylxZRVZyujLLFn8YDzKmd5JrNkrBJDCrdZI=; b=MoEUGLWqVDZnJkhQAkwowpR3PJzcqi5fPFQr30qWte7GyKEmICTx66Ur+GJ9crftw4/YDcaq /9WZer6H2EwnBIot0PAxLsxqzqJQXPQs/dQ4jUEmO/1pnjB38Qcf0LaxAkBi2kUm6H1viXqZ f9kBBeN0Y4M32KzFlcAzYW+0lYc= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b342df8.7fbc2ac9cd50-smtp-out-n03; Thu, 28 Jun 2018 00:38:16 -0000 (UTC) Date: Wed, 27 Jun 2018 17:38:15 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b342df75a35a_579d2b22397c5c1425fa@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b342df759e06_579d2b22397c5c14249e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 00:38:18 -0000 ----==_mimepart_5b342df759e06_579d2b22397c5c14249e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/tags/draft-ietf-quic-recovery-13 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b342df759e06_579d2b22397c5c14249e-- From nobody Wed Jun 27 17:38:33 2018 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 764A5130E5F for ; Wed, 27 Jun 2018 17:38:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 WLV1d8zMpXHE for ; Wed, 27 Jun 2018 17:38:22 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 4ED15130E5A for ; Wed, 27 Jun 2018 17:38:22 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530146302; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=gLR3LY8sv17Ksa8vARTgVpEvYg63YRJVJImniKoOD5k=; b=Bk+Ay6p7R1zYnFTfHoXt6h6BS+y5mIc5YVJjJcoFlRTx4qEvZ5NWpw25BMdQDRCMuW540u4n d0U7uAjHDoo4hBq9hSROOTco/mjebe6s23jgMFql/fn2GHRvEEBmR+G48jcoQbQ0wi73C6r4 vaOIiYXz6rFxlE+zgfTACHsw+hs= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b342dfd.7f7856147ae0-smtp-out-n02; Thu, 28 Jun 2018 00:38:21 -0000 (UTC) Date: Wed, 27 Jun 2018 17:38:20 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b342dfc7c141_6c3b2b08de8afc0c199fe@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b342dfc7bd8e_6c3b2b08de8afc0c19889"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 00:38:24 -0000 ----==_mimepart_5b342dfc7bd8e_6c3b2b08de8afc0c19889 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/tags/draft-ietf-quic-tls-13 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b342dfc7bd8e_6c3b2b08de8afc0c19889-- From nobody Wed Jun 27 17:38:41 2018 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 26CA3130EAF for ; Wed, 27 Jun 2018 17:38:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 T_gcRtFW32V9 for ; Wed, 27 Jun 2018 17:38:27 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 A376E130E8A for ; Wed, 27 Jun 2018 17:38:27 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530146307; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=+qR1/xsT0yXFrnGNRqlfO8UJR2tvPTWLUfUcHq6uQ9A=; b=LjToegmRGeQ+EoFn8vrLzDNvkLkULEWr1PBfM1Aw5myFN3b5VgbngvjX36DUpAyueYcyxeID uGnT1Wf3xUtqUSob+A8yC0x8I//KYqBy+IWRZddTkC0Ifi1nvizKf9R5aJyPxyj6hjzPRWL7 7wAzjlToDQD4uTb/46jG7l+uWEo= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5b342e02.7f453e7aee10-smtp-out-n02; Thu, 28 Jun 2018 00:38:26 -0000 (UTC) Date: Wed, 27 Jun 2018 17:38:25 -0700 From: martinthomson Reply-To: martinthomson To: quic-issues@ietf.org Message-ID: <5b342e01a17f3_5a2d2b0513c63c002458f@hookshot-fe-d252ca1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b342e01a1100_5a2d2b0513c63c0024428"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 00:38:31 -0000 ----==_mimepart_5b342e01a1100_5a2d2b0513c63c0024428 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/tags/draft-ietf-quic-transport-13 Home: https://github.com/quicwg/base-drafts **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b342e01a1100_5a2d2b0513c63c0024428-- From nobody Wed Jun 27 17:45:16 2018 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 5C327130E63 for ; Wed, 27 Jun 2018 17:45:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Dfuipa6iPjO2 for ; Wed, 27 Jun 2018 17:45:11 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 535F3130E57 for ; Wed, 27 Jun 2018 17:45:11 -0700 (PDT) Date: Wed, 27 Jun 2018 17:45:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530146710; bh=PX1bAst03ZnLr0pHvvfTvTehD9kmU5pysaOm2EkPDsI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=QYv9l9fFCzM2VD2sxDKgNvKFRfcZAaWhbNrF/rZ2+Jrz2RRWa/zrvtyFMllSAuOgL Ha42gvrTwbb15aOtfpiGQKoyV/MtjsyuhDWP6vgaLDCCC1sc9QTgPD0XBXVdcLDzEW BB6jE+k5jfbbosusYEG70+5g2ele66O06y4xBkvw= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b342f966153b_5f683fc769f2cf7c6503a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Thu, 28 Jun 2018 00:45:15 -0000 ----==_mimepart_5b342f966153b_5f683fc769f2cf7c6503a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This PR adds an appendix with some pseudo code that show how to decode packet numbers. The explanation in the draft was a bit terse so I think some example code might help. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1493 -- Commit Summary -- * Add an appendix related to packet number decoding. -- File Changes -- M draft-ietf-quic-transport.md (32) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1493.patch https://github.com/quicwg/base-drafts/pull/1493.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/1493 ----==_mimepart_5b342f966153b_5f683fc769f2cf7c6503a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This PR adds an appendix with some pseudo code that show how to decode packet numbers.
The explanation in the draft was a bit terse so I think some example code might help.

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

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

Commit Summary

  • Add an appendix related to packet number decoding.

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 mute the thread.

----==_mimepart_5b342f966153b_5f683fc769f2cf7c6503a-- From nobody Wed Jun 27 17:48:17 2018 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 D3DFE130E53 for ; Wed, 27 Jun 2018 17:48:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cONK8u7joQZv for ; Wed, 27 Jun 2018 17:48:12 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74B2D130EF4 for ; Wed, 27 Jun 2018 17:48:10 -0700 (PDT) Date: Wed, 27 Jun 2018 17:48:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530146889; bh=qg1DCpGYzyFfwtw0ZLlunQLnzUaM2KvjrdjTt0ZSQfU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uBtDUKzXztM4iy+gSCo3COi2LIAsEafHVHBcT7BTdhgGyDw32zfjUC8ThnLrbAke+ CMOOeJov0JTmN1G0Y2mgN53MhSyIGVgd70dOpl/2o2ttsZeHMRR83OduhgnBvV9KVM HLwHKXUhjjSnkoVvxvHg+J0DnSSfauaiTM6yWgZ4= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b343049a5110_62752b0625592f5852598"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Thu, 28 Jun 2018 00:48:16 -0000 ----==_mimepart_5b343049a5110_62752b0625592f5852598 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @rpaulo pushed 1 commit. e52c8f9 Remove whitespace -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1493/files/ba4d1a8cb381f511ec1864b1bc69dedadb1ff621..e52c8f947d9edee689aebed3546059ddf5b44759 ----==_mimepart_5b343049a5110_62752b0625592f5852598 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b343049a5110_62752b0625592f5852598-- From nobody Wed Jun 27 17:53:22 2018 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 EBF40130E5C for ; Wed, 27 Jun 2018 17:53:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 AQc3ks20Mcg2 for ; Wed, 27 Jun 2018 17:53:18 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97200130E57 for ; Wed, 27 Jun 2018 17:53:18 -0700 (PDT) Date: Wed, 27 Jun 2018 17:53:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530147197; bh=zAkbuKFGmcbI9qQ+b3rkleYq4mXbx6XhSjNZTM9/fdA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C7uCpyZjL2R/ipp18KXChz3TO9y9qOONKkZfspW1o3Be6mrzM7wBcX9dOF0venHIs 2O3YFulnuJY5bZDem50dOKWrkzyIsqRP8Lwr/R2g85gQtAUjCvSGxGNiiW+aLi8b1Q qIT9Xfw5Ygqm93j0paKFpmX/XsHk0OMlmrmK/nHY= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34317db8148_62782b0625592f587913f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 00:53:20 -0000 ----==_mimepart_5b34317db8148_62782b0625592f587913f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @kazuho thanks for your thoughts. I tend to agree about being less strict on negotiation but I think we are retreading some ground on SETTINGS HoL. A middle ground might say that stream extensions should be aware of the trade off in committing resource to data that could be ignored by the peer vs. negotiating at the cost of latency. -- 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/1490#issuecomment-400876342 ----==_mimepart_5b34317db8148_62782b0625592f587913f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@kazuho thanks for your thoughts.

=

I tend to agree about being less strict on negotiation but I think we = are retreading some ground on SETTINGS HoL.

A middle ground might say that stream extensions should be aware of th= e trade off in committing resource to data that could be ignored by the p= eer vs. negotiating at the cost of latency.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b34317db8148_62782b0625592f587913f-- From nobody Wed Jun 27 17:57:39 2018 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 8E79C130E65 for ; Wed, 27 Jun 2018 17:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 iKCmVSoz85cO for ; Wed, 27 Jun 2018 17:57:36 -0700 (PDT) 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 4DB42130E63 for ; Wed, 27 Jun 2018 17:57:36 -0700 (PDT) Date: Wed, 27 Jun 2018 17:57:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530147455; bh=8eqhvmOY6LoEFLTYdUyO0cktioyeOIwgFqXkEaLRxIY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k/P/B1+zbLdighggA1lT6fSeuX+NUsKi6lbv8vOtVX6VJkJpTEqbQA8+inkmHPfrN jeMJKvoLw37fmSGKx/yuLn6uQ0by5Dl0Evw2xU36VacGqPebwobS7IIq9K9ThsFJPE awRrTC6Xt1XhJEzt+VO0z4qorXJHcr+BpBK8uBl4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34327f9c4d1_3fdd3f9692fa8f8010163b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 00:57:39 -0000 ----==_mimepart_5b34327f9c4d1_3fdd3f9692fa8f8010163b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. Thanks! We've been meaning to do this for a while now. > @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}. --- back +# Sample code for packet number decoding {#sample-packet-number-decoding} + +The following pseudo-code shows how an implementation can decode packet +numbers after packet protection has been removed. + +~~~ +rcv_nxt = 0xaa82f30e + 1 +pktn = 0x9b3 +pktn_nbits = 14 +pktn_len = 1 << pktn_nbits +pktn_win = pktn_len / 2 // 0x2000 + +// The incoming packet number is between: +// [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[ I would instead say the incoming packet number is greater than (rcv_next - pktn_win) and less than or equal to (rcv_next + pktn_win). The use of '[' here implies a different interpretation, and it's not so obvious. > @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}. --- back +# Sample code for packet number decoding {#sample-packet-number-decoding} + +The following pseudo-code shows how an implementation can decode packet +numbers after packet protection has been removed. + +~~~ +rcv_nxt = 0xaa82f30e + 1 Maybe start with a function declaration: InterpretPacketNumber(largest_received_pn, truncated_pn, truncated_pn_bits): then you can include comments on each line that show the result of the step, as you do for pktn_win. > +# Sample code for packet number decoding {#sample-packet-number-decoding} + +The following pseudo-code shows how an implementation can decode packet +numbers after packet protection has been removed. + +~~~ +rcv_nxt = 0xaa82f30e + 1 +pktn = 0x9b3 +pktn_nbits = 14 +pktn_len = 1 << pktn_nbits +pktn_win = pktn_len / 2 // 0x2000 + +// The incoming packet number is between: +// [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[ +// +// However, we can't just perform the exclusive-or of rcv_nxt Exclusive-or might be misleading. Also, we're concerned about being outside the window on both sides. Maybe, "However, we can't just remove the trailing bits from rcv_nxt and add the truncated packet number because that might be outside the window." > +rcv_nxt = 0xaa82f30e + 1 +pktn = 0x9b3 +pktn_nbits = 14 +pktn_len = 1 << pktn_nbits +pktn_win = pktn_len / 2 // 0x2000 + +// The incoming packet number is between: +// [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[ +// +// However, we can't just perform the exclusive-or of rcv_nxt +// (with the appropriate bits removed) with pktn because that +// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win. +// +// We need to find a packet number that fits the window, +// so we add the window to the expected packet number and check +// for overflow. Here we find the top of the window and use that as the basis for calculating the value. Then, the value can only be too large. > +pktn = 0x9b3 +pktn_nbits = 14 +pktn_len = 1 << pktn_nbits +pktn_win = pktn_len / 2 // 0x2000 + +// The incoming packet number is between: +// [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[ +// +// However, we can't just perform the exclusive-or of rcv_nxt +// (with the appropriate bits removed) with pktn because that +// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win. +// +// We need to find a packet number that fits the window, +// so we add the window to the expected packet number and check +// for overflow. +rcv_nxt_masked = (rcv_nxt + pktn_win) & ~(pktn_len - 1) I would add a temporary for rcv_max = rcv_nxt + pktn_win so that you can a) explain it better, and b) use it in two places. > +pktn_win = pktn_len / 2 // 0x2000 + +// The incoming packet number is between: +// [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[ +// +// However, we can't just perform the exclusive-or of rcv_nxt +// (with the appropriate bits removed) with pktn because that +// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win. +// +// We need to find a packet number that fits the window, +// so we add the window to the expected packet number and check +// for overflow. +rcv_nxt_masked = (rcv_nxt + pktn_win) & ~(pktn_len - 1) +decoded_pktn = rcv_nxt_masked + pktn + +// Note that we also check for underflow. "Note the extra check for underflow when the next packet number is near zero." -- 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/1493#pullrequestreview-132656969 ----==_mimepart_5b34327f9c4d1_3fdd3f9692fa8f8010163b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

Thanks! We've been meaning to do this for a while now.

In draft-ietf-quic-transport.md:

> @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}.
 
 --- back
 
+# Sample code for packet number decoding {#sample-packet-number-decoding}
+
+The following pseudo-code shows how an implementation can decode packet
+numbers after packet protection has been removed.
+
+~~~
+rcv_nxt        = 0xaa82f30e + 1
+pktn           = 0x9b3
+pktn_nbits     = 14
+pktn_len       = 1 << pktn_nbits
+pktn_win       = pktn_len / 2          // 0x2000
+
+// The incoming packet number is between:
+//     [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[

I would instead say the incoming packet number is greater than (rcv_next - pktn_win) and less than or equal to (rcv_next + pktn_win). The use of '[' here implies a different interpretation, and it's not so obvious.

In draft-ietf-quic-transport.md:

> @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}.
 
 --- back
 
+# Sample code for packet number decoding {#sample-packet-number-decoding}
+
+The following pseudo-code shows how an implementation can decode packet
+numbers after packet protection has been removed.
+
+~~~
+rcv_nxt        = 0xaa82f30e + 1

Maybe start with a function declaration:
InterpretPacketNumber(largest_received_pn, truncated_pn, truncated_pn_bits):

then you can include comments on each line that show the result of the step, as you do for pktn_win.

In draft-ietf-quic-transport.md:

> +# Sample code for packet number decoding {#sample-packet-number-decoding}
+
+The following pseudo-code shows how an implementation can decode packet
+numbers after packet protection has been removed.
+
+~~~
+rcv_nxt        = 0xaa82f30e + 1
+pktn           = 0x9b3
+pktn_nbits     = 14
+pktn_len       = 1 << pktn_nbits
+pktn_win       = pktn_len / 2          // 0x2000
+
+// The incoming packet number is between:
+//     [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[
+//
+// However, we can't just perform the exclusive-or of rcv_nxt

Exclusive-or might be misleading. Also, we're concerned about being outside the window on both sides.

Maybe, "However, we can't just remove the trailing bits from rcv_nxt and add the truncated packet number because that might be outside the window."

In draft-ietf-quic-transport.md:

> +rcv_nxt        = 0xaa82f30e + 1
+pktn           = 0x9b3
+pktn_nbits     = 14
+pktn_len       = 1 << pktn_nbits
+pktn_win       = pktn_len / 2          // 0x2000
+
+// The incoming packet number is between:
+//     [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[
+//
+// However, we can't just perform the exclusive-or of rcv_nxt
+// (with the appropriate bits removed)  with pktn because that
+// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win.
+//
+// We need to find a packet number that fits the window,
+// so we add the window to the expected packet number and check
+// for overflow.

Here we find the top of the window and use that as the basis for calculating the value. Then, the value can only be too large.

In draft-ietf-quic-transport.md:

> +pktn           = 0x9b3
+pktn_nbits     = 14
+pktn_len       = 1 << pktn_nbits
+pktn_win       = pktn_len / 2          // 0x2000
+
+// The incoming packet number is between:
+//     [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[
+//
+// However, we can't just perform the exclusive-or of rcv_nxt
+// (with the appropriate bits removed)  with pktn because that
+// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win.
+//
+// We need to find a packet number that fits the window,
+// so we add the window to the expected packet number and check
+// for overflow.
+rcv_nxt_masked  = (rcv_nxt + pktn_win) & ~(pktn_len - 1)

I would add a temporary for rcv_max = rcv_nxt + pktn_win so that you can a) explain it better, and b) use it in two places.

In draft-ietf-quic-transport.md:

> +pktn_win       = pktn_len / 2          // 0x2000
+
+// The incoming packet number is between:
+//     [rcv_nxt - pktn_win ; rcv_nxt + pktn_win[
+//
+// However, we can't just perform the exclusive-or of rcv_nxt
+// (with the appropriate bits removed)  with pktn because that
+// would yield 0xaa82c9b3 which is lower than rcv_nxt - pktn_win.
+//
+// We need to find a packet number that fits the window,
+// so we add the window to the expected packet number and check
+// for overflow.
+rcv_nxt_masked  = (rcv_nxt + pktn_win) & ~(pktn_len - 1)
+decoded_pktn    = rcv_nxt_masked + pktn
+
+// Note that we also check for underflow.

"Note the extra check for underflow when the next packet number is near zero."

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

----==_mimepart_5b34327f9c4d1_3fdd3f9692fa8f8010163b-- From nobody Wed Jun 27 18:00:48 2018 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 7819B130E69 for ; Wed, 27 Jun 2018 18:00:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DRnGc02PXc1X for ; Wed, 27 Jun 2018 18:00:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A33A130E63 for ; Wed, 27 Jun 2018 18:00:45 -0700 (PDT) Date: Wed, 27 Jun 2018 18:00:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530147644; bh=XLuWHXJArKp+dLx2h4kXjgpS+s/xah1zbvR6rke5JWY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V0z2LVKolfr1PozYnygP9XArHQ4PPeZDzkDQBgfFamV4gt/4W2kgfpgd84Ap/p3jv qJOlGJg4MVKo4/AnTkWFMZ090Mc9TURKD1F25X3eXGobvhIK2F3lG1DBh8L1al1yLH gI/ODTV8PEbOy2e0bvkHR3VyfJ4sf7PladcJdyE8= From: Masakazu Kitajo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34333c8e380_2ccf3fe767c82f88798d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: maskit 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.26 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: Thu, 28 Jun 2018 01:00:47 -0000 ----==_mimepart_5b34333c8e380_2ccf3fe767c82f88798d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Although I'm +1 on adding some pseudo code and this code seems nice as an implementation, I'm not sure this is also nice as a pseudo code to help understanding. Maybe comparing two candidate packet numbers and choosing one from them (like `candidate1 - expected < candidate2 - expected`) is more straightforward approach. -- 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/1493#issuecomment-400877448 ----==_mimepart_5b34333c8e380_2ccf3fe767c82f88798d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Although I'm +1 on adding some pseudo code and this code seems nice as= an implementation, I'm not sure this is also nice as a pseudo code to he= lp understanding.

Maybe comparing two candidate packet numbers and choosing one from the= m (like candidate1 - expected < candidate2 - expected) is= more straightforward approach.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b34333c8e380_2ccf3fe767c82f88798d-- From nobody Wed Jun 27 18:04:40 2018 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 4F515130E6A for ; Wed, 27 Jun 2018 18:04:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 JDVwjIv1-2bY for ; Wed, 27 Jun 2018 18:04:37 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E56DB130E63 for ; Wed, 27 Jun 2018 18:04:36 -0700 (PDT) Date: Wed, 27 Jun 2018 18:04:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530147876; bh=sYhGxYv5l+TVhDtP5AsipgUMXgATWcwaOVCnvHbiPSs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uqdeIXsQSe2QJ5+k1zx1qRzz3KQ4wAVaCnWeZCYQG38HR20s25i0SY5Jfl03sdknJ 2gUAIsYaR43W+rRbFzeIDjh1UniO/r2ZxZJd7wXIDD7n0+P1wVJaNAj57SMXR4oe9Q tAFqBt5I+19H45mjG/IerXCFJsjebI159eQjHL/M= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3434244dde9_33382ac3b3508f60324c2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 01:04:39 -0000 ----==_mimepart_5b3434244dde9_33382ac3b3508f60324c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Note that you can avoid one if statement with: decoded_pktn -= ((rcv_nxt + pktn_win) & (pktn_len - 1) + pktn) & (pktn_len - 1) But no one wants to see that in a spec. @maskit, are you suggesting the simpler code: ```python expected = next + 1 range = 1 << nbits mask = range - 1 candidate = (expected & mask) | truncated if candidate <= expected - range/2: return candidate + range if candidate > expected + range/2 and candidate > range: return candidate - range return candidate ``` That might be better, I agree. -- 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/1493#issuecomment-400878018 ----==_mimepart_5b3434244dde9_33382ac3b3508f60324c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Note that you can avoid one if statement with:

decoded_pktn -=3D ((rcv_nxt + pktn_win) & (pktn_len - 1) + pktn) &= amp; (pktn_len - 1)

But no one wants to see that in a spec.

@maskit, are you suggesting the simp= ler code:

expected =3D next + 1
range =3D 1 << nbits
mask =3D range <=
span class=3D"pl-k">- 1
candidate =3D (expected =
& mask) | truncated
if candidate <=3D expected - range/2:
  return candidate + range
if candidate >=
 expected + range/2 and candidate > range:
  return candidate - range
return candidate

That might be better, I agree.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b3434244dde9_33382ac3b3508f60324c2-- From nobody Wed Jun 27 18:06:04 2018 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 51D3D130E6A for ; Wed, 27 Jun 2018 18:06:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 E36qPyKdPVXg for ; Wed, 27 Jun 2018 18:06:01 -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 CE1A4130E63 for ; Wed, 27 Jun 2018 18:06:00 -0700 (PDT) Date: Wed, 27 Jun 2018 18:06:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530147960; bh=GaxABelx285pQQOiPYuRpXrD5q3GtX9nuf+VS7uY33o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vHcApovk73ao5X+mUxGUwr7/+YoiAjhlaMQB00gVZzqwou/wbw4T30awySc0norJF CJ0ikdqyd2ylQbe/0F99pXwbQ2ECyzhvcoXSDsuFPdpPu/kc+z5BmyZzIs5Rmkm5gW ojs8PHEJA0QpTjY0CDj2yEMToCvcOISXrJz9u27U= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34347812f86_161b3fa36a43ef8494562"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 01:06:03 -0000 ----==_mimepart_5b34347812f86_161b3fa36a43ef8494562 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Just to be clear, the challenge with assembling candidates is that you end up with 3, not 2. -- 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/1493#issuecomment-400878197 ----==_mimepart_5b34347812f86_161b3fa36a43ef8494562 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Just to be clear, the challenge with assembling candidates is that you end up with 3, not 2.

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

----==_mimepart_5b34347812f86_161b3fa36a43ef8494562-- From nobody Wed Jun 27 18:16:38 2018 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 F1380130E75 for ; Wed, 27 Jun 2018 18:16:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 gKK-Ws5S1KRx for ; Wed, 27 Jun 2018 18:16:34 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F912130E63 for ; Wed, 27 Jun 2018 18:16:34 -0700 (PDT) Date: Wed, 27 Jun 2018 18:16:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530148593; bh=1qJF5RSdVSHu4fRC77qsFhSmiI8N/AMuznIXouWyLqI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=npvPKNDcyd5CCtV0oWaMYUE9+N6CTHgLZAX+z5PdvA7CTUmSv05FYmSKpkf7EsUmc pynzwNvVVbZJiFJVmHVkjlHHmxU/bWbo25N2+kHtLKcbRY+MU0WLbYsukah200wPop QLD4G1pbqyQ8cBcFXoNQsEeeHYj6v8AgWbMBFVkw= From: Masakazu Kitajo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3436f1833f5_52fc3faf394a4f84352ce"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: maskit 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.26 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: Thu, 28 Jun 2018 01:16:37 -0000 ----==_mimepart_5b3436f1833f5_52fc3faf394a4f84352ce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson Yeah, something like that. It probably make the code redundant and longer, but we shouldn't be too clever. The point is straightforwardness. -- 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/1493#issuecomment-400879637 ----==_mimepart_5b3436f1833f5_52fc3faf394a4f84352ce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson Yeah, something like that. It probably make the code redundant and longer, but we shouldn't be too clever. The point is straightforwardness.

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

----==_mimepart_5b3436f1833f5_52fc3faf394a4f84352ce-- From nobody Wed Jun 27 18:16:44 2018 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 4167C130E75 for ; Wed, 27 Jun 2018 18:16:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 GMCjq87Rhom1 for ; Wed, 27 Jun 2018 18:16:40 -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 53648130E8A for ; Wed, 27 Jun 2018 18:16:40 -0700 (PDT) Date: Wed, 27 Jun 2018 18:16:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530148599; bh=Ny+6eDtlOR5M59EITrAqwtkqEyPBO5bRLiovAlHVEDc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fc9nTUki4ISLNvHzcEgM32B/x/NetP0TW7Qf9PdheJNybnXmvvLoSLLXBZq4HJMRT VbOZKwl1KTVOwoT3g/raehP/tgViw8xtYlDalQUVkLuE8r6cdIMAEIZTMgz6z4BpeG icjp8//tIhoiWqANNm1NQY6qn9aor/WlSfGamJWI= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3436f74da53_27e02b0226616f54628cd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 28 Jun 2018 01:16:43 -0000 ----==_mimepart_5b3436f74da53_27e02b0226616f54628cd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > A middle ground might say that stream extensions should be aware of the trade off in committing resource to data that could be ignored by the peer vs. negotiating at the cost of latency. Yes. IMO, having a statement that suggests extensions to consider using SETTINGS for negotiation is a good idea, and that is what we have in https://httpwg.org/specs/rfc7540.html#extensibility for frames. My point is that there is no need to switch to a different approach for frames *and unidirectional streams* to be defined in hq. -- 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/1490#issuecomment-400879652 ----==_mimepart_5b3436f74da53_27e02b0226616f54628cd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A middle ground might say that stream extensions should be aware of th= e trade off in committing resource to data that could be ignored by the p= eer vs. negotiating at the cost of latency.

Yes. IMO, having a statement that suggests extensions to consider usin= g SETTINGS for negotiation is a good idea, and that is what we have in https://httpwg.org/specs/rfc7540.html#extensibility for frames.= My point is that there is no need to switch to a different approach for = frames and unidirectional streams to be defined in hq.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3436f74da53_27e02b0226616f54628cd-- From nobody Wed Jun 27 18:38:57 2018 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 8727E130EE0 for ; Wed, 27 Jun 2018 18:38:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 hPw4wxQgJMst for ; Wed, 27 Jun 2018 18:38:54 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C920C130E70 for ; Wed, 27 Jun 2018 18:38:54 -0700 (PDT) Date: Wed, 27 Jun 2018 18:38:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530149934; bh=OmyhlvoVy+hsRaGOm9oC7ut5h1tg2uiser/CbOHhhCo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xk4YkQ57CevbzxA+Xx8CxinORAioP0lwhfXZS7iDRFE73WvrD9zsIoUKlL+BZFC2m Z0YQeslxb8XKoBJKav0LLq7WkX39kIRFMnDt3Xyv7ATBkaNKsjydSDKrmWZcmuTTJM 0s8wiNjBXHoFl6zrOhH/WVDaT74vjjn6aG2wwnEY= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b343c2df1f5c_44ea2aee3c55cf5814696a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 01:38:57 -0000 ----==_mimepart_5b343c2df1f5c_44ea2aee3c55cf5814696a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed. On a tangent, on reading that H2 section, it strikes me that we may want some text that accommodates connection migration (or at least clarifies rules). Are SETTINGS transferable or do they need to be renegotiated? What about QPACK? -- 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/1490#issuecomment-400883364 ----==_mimepart_5b343c2df1f5c_44ea2aee3c55cf5814696a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Agreed.

On a tangent, on reading that H2 section, it strikes me that we may want some text that accommodates connection migration (or at least clarifies rules). Are SETTINGS transferable or do they need to be renegotiated? What about QPACK?

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

----==_mimepart_5b343c2df1f5c_44ea2aee3c55cf5814696a-- From nobody Wed Jun 27 18:57:29 2018 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 D0C08130EE6 for ; Wed, 27 Jun 2018 18:57:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 90YZLja5Z1LS for ; Wed, 27 Jun 2018 18:57:25 -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 02090130E79 for ; Wed, 27 Jun 2018 18:57:24 -0700 (PDT) Date: Wed, 27 Jun 2018 18:57:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530151044; bh=FgvU8EROUGALiJGWZSEo6hbLQZwefRTCZKXB7bPWiWI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BXwb0NYCJit3DeV7xJGSS14WPMNgRK8QJzP3cKVXaH1Z5Hfuo3xjvgzkcZrLYiwZN Qr5TXtYkJMzRQtdu2Hq6CCSQcFCMo6UBUqb3s0cynVejfJdP4jEm4CvLuCd5IQ8zDn QsdHZJqE9J5PnAynDn+C+NKx8QVb/0DSb/8TAH1Q= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b344084a157_27e32b0226616f5421386e"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 01:57:27 -0000 ----==_mimepart_5b344084a157_27e32b0226616f5421386e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit After realizing that you need to consume a sequence number if you intend to implement the preferred address, I think that this is the best approach. At that point, we might as well concede that there will be a gap at the start in a lot of cases. What @kazuho proposes here seems OK. I don't think that the Initial packet needs a slot reserved, but the difference between one unused value and two isn't worth worrying about. This does nothing for connection IDs provided with Retry, but the handling of Retry is reactive and can probably overwrite the zero index as it goes. -- 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/1484#issuecomment-400886188 ----==_mimepart_5b344084a157_27e32b0226616f5421386e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

After realizing that you need to consume a sequence number if you inte= nd to implement the preferred address, I think that this is the best appr= oach.

At that point, we might as well concede that there will be a gap at th= e start in a lot of cases. What @kazuho= proposes here seems OK. I don't think that the Initial packet needs a s= lot reserved, but the difference between one unused value and two isn't w= orth worrying about.

This does nothing for connection IDs provided with Retry, but the hand= ling of Retry is reactive and can probably overwrite the zero index as it= goes.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b344084a157_27e32b0226616f5421386e-- From nobody Wed Jun 27 19:02:27 2018 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 3CA64130E79 for ; Wed, 27 Jun 2018 19:02:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 IJzIylbFIxnz for ; Wed, 27 Jun 2018 19:02:22 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65991130E17 for ; Wed, 27 Jun 2018 19:02:22 -0700 (PDT) Date: Wed, 27 Jun 2018 19:02:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530151341; bh=DjAoHJddVLJdk35Py7XeIbq6kYAiUo/2U7/CrCkykP0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KkNE21/scJ7sgucfQaUeHK/Mx9opkrdsgEG1HP0/p4e5ODQq43Kxuo/UZ6uIv+QeL Wzfxv/b5EXIFXsxn+GFZKlMuhsHEB1Pbkf/uxDOcyRjoEGIRRuCYNtIorObgNxeNmK s05P3Km+Wi+TRDDaI8ycrvjuOCXG6Y4UwpHHdA5Q= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3441adacf0a_488a2b1fedc54f582117e9"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 02:02:25 -0000 ----==_mimepart_5b3441adacf0a_488a2b1fedc54f582117e9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue, settings are protocol-specific. That there is some apparent similarity is to ease the conceptual transition for people reading the spec, nothing more. You shouldn't be able to take h2 settings from a server and expect the hq endpoint to respect them. That is one reason why priming 0-RTT cross protocol is fraught. -- 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/1490#issuecomment-400886964 ----==_mimepart_5b3441adacf0a_488a2b1fedc54f582117e9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@LPardue, settings are protocol-sp= ecific. That there is some apparent similarity is to ease the conceptual= transition for people reading the spec, nothing more. You shouldn't be = able to take h2 settings from a server and expect the hq endpoint to resp= ect them. That is one reason why priming 0-RTT cross protocol is fraught= .

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3441adacf0a_488a2b1fedc54f582117e9-- From nobody Wed Jun 27 19:04:10 2018 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 5E5EA130EE4 for ; Wed, 27 Jun 2018 19:04:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 jx1LbIuneWX2 for ; Wed, 27 Jun 2018 19:04:07 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F47D130E17 for ; Wed, 27 Jun 2018 19:04:07 -0700 (PDT) Date: Wed, 27 Jun 2018 19:04:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530151446; bh=QIiFiJpYeMBx8mwk/dIOodLrBLL2QPtsswoyhbfbNgA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wqqMfK0JiANpjSTJVb5OU6VeQrgdD1RzPiArLtD97VhF3Y71AwWJx9VHOITSaC3oA XekpfMCcqTSY0/mmDeod654n2LrcSX//Zsj7nu4aDNqKPyM/l8PL4sS2TWR/H0X1qi e8oUCNIqbAa1WQfdjvPyVuHtNqcUbA8/mZ/Wo9yQ= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b344216d0727_50d82ab82b88ef603382a0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Thu, 28 Jun 2018 02:04:10 -0000 ----==_mimepart_5b344216d0727_50d82ab82b88ef603382a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > On a tangent, on reading that H2 section, it strikes me that we may want some text that accommodates connection migration (or at least clarifies rules). Are SETTINGS transferable or do they need to be renegotiated? What about QPACK? Migration is something that happens mid-connection, and there is no need to renegotiate. If you are concerned about connection reestablishment, I think the required behavior is stated clearly in [section 4.2.6.3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.4.2.6.3). -- 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/1490#issuecomment-400887249 ----==_mimepart_5b344216d0727_50d82ab82b88ef603382a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On a tangent, on reading that H2 section, it strikes me that we may wa= nt some text that accommodates connection migration (or at least clarifie= s rules). Are SETTINGS transferable or do they need to be renegotiated? W= hat about QPACK?

Migration is something that happens mid-connection, and there is no ne= ed to renegotiate.

If you are concerned about connection reestablishment, I think the req= uired behavior is stated clearly in sect= ion 4.2.6.3.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b344216d0727_50d82ab82b88ef603382a0-- From nobody Wed Jun 27 20:36:51 2018 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 4F5D7130F21 for ; Wed, 27 Jun 2018 20:36:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oEY2jfj062-A for ; Wed, 27 Jun 2018 20:36:48 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8064F130E72 for ; Wed, 27 Jun 2018 20:36:48 -0700 (PDT) Date: Wed, 27 Jun 2018 20:36:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530157007; bh=5mQ6djAPIRoM/z2TKNXrgtwCu6/nspswpIa3eMdEHHs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C0lk9HN4ynGveDrZar7zLUI5GIWhyxrZU0EI2kvFDQL5Zpg8Gq+qfvoNHFLrimhlY Hyxh/r7s7dVzwWpL1gM9YhN6VhaDeLROroqgZiUnCE7dEClnCSrEheb62uA+lqPDzw kuDLG/Q4Z9CR/tobToQLUPw/83HCpFNq3a0EzO4Q= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3457cf79ecc_2bc62b132b49cf5021615f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Thu, 28 Jun 2018 03:36:50 -0000 ----==_mimepart_5b3457cf79ecc_2bc62b132b49cf5021615f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit rpaulo commented on this pull request. > @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}. --- back +# Sample code for packet number decoding {#sample-packet-number-decoding} + +The following pseudo-code shows how an implementation can decode packet +numbers after packet protection has been removed. + +~~~ +rcv_nxt = 0xaa82f30e + 1 I wanted to use this appendix as the basis for the example above but I agree we can follow the status quo -- 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/1493#discussion_r198699834 ----==_mimepart_5b3457cf79ecc_2bc62b132b49cf5021615f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo commented on this pull request.

In draft-ietf-quic-transport.md:

> @@ -4778,6 +4780,36 @@ from 0xFF00 to 0xFFFF are reserved for Private Use {{!RFC8126}}.
 
 --- back
 
+# Sample code for packet number decoding {#sample-packet-number-decoding}
+
+The following pseudo-code shows how an implementation can decode packet
+numbers after packet protection has been removed.
+
+~~~
+rcv_nxt        = 0xaa82f30e + 1

I wanted to use this appendix as the basis for the example above but I agree we can follow the status quo

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

----==_mimepart_5b3457cf79ecc_2bc62b132b49cf5021615f-- From nobody Thu Jun 28 04:24:45 2018 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 C4D43130F62 for ; Thu, 28 Jun 2018 04:24:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 u8bySS0l26y7 for ; Thu, 28 Jun 2018 04:24:40 -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 C0032130F5F for ; Thu, 28 Jun 2018 04:24:40 -0700 (PDT) Date: Thu, 28 Jun 2018 04:24:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530185079; bh=mtfv4GNB3z7QHyKVxWOsyPpvvzcKHLK1hFEzDtUxbo8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bPfw0yOX4NGFLr0gXAWKl2SOhXX1+EsZvxUBFvZMAsdbCCAMvm/xVRrLcLu4vW4oT FZ2i3vmhmI5xmr9ORUvNP1+jpl6c/jLlhFhtmB7zBJgAC8bvhd7gijD55QZ9jbYKuI k/GXwnhNa7OSDS6EaDBgEEdQVYfQ3IrGiYSVX7ic= From: Julian Reschke Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] qpack: section reference is broken (#1494) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34c57755b7b_3463fdc84f3af841040e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: reschke 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.26 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: Thu, 28 Jun 2018 11:24:43 -0000 ----==_mimepart_5b34c57755b7b_3463fdc84f3af841040e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit (that's what you get for using MarkDown :-) You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1494 -- Commit Summary -- * qpack: section reference is broken -- File Changes -- M draft-ietf-quic-qpack.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1494.patch https://github.com/quicwg/base-drafts/pull/1494.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/1494 ----==_mimepart_5b34c57755b7b_3463fdc84f3af841040e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

(that's what you get for using MarkDown :-)

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

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

Commit Summary

  • qpack: section reference is broken

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 mute the thread.

----==_mimepart_5b34c57755b7b_3463fdc84f3af841040e5-- From nobody Thu Jun 28 05:01:48 2018 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 358B5130FF2 for ; Thu, 28 Jun 2018 05:01:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 XSNfHiG3DbTY for ; Thu, 28 Jun 2018 05:01:43 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 7281C130EFC for ; Thu, 28 Jun 2018 05:01:43 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530187300; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=tHfRHmLJJl4Dgm1B3n5NyCHOLo8Pq1iy3bRSgpR86Yk=; b=rcXGGFA2nOq8hWik1ExAsN4tJy1PHPpzoyy5Hs13xDNeEsrKjm+Bl4r74CrfGHfvSE8Iy8Ll r3ruHlWoohcDWB683e2MBbB7eF+HYzZ4QexAlFZBXqv1mQXvKMld/PKrIf1jveA+qKbXHOZw xevSiFXcc+b5DmdWV4+C1QzTwZo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b34ce24.7fe802aeed50-smtp-out-n03; Thu, 28 Jun 2018 12:01:40 -0000 (UTC) Date: Thu, 28 Jun 2018 05:01:39 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b34ce23720cd_26f2ad22a89bc10281b@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 5d6e8a: qpack: section reference is broken Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b34ce23719d3_26f2ad22a89bc1028060"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 12:01:47 -0000 ----==_mimepart_5b34ce23719d3_26f2ad22a89bc1028060 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 5d6e8a98d611a9cde16a3c86f667c86023ee776d https://github.com/quicwg/base-drafts/commit/5d6e8a98d611a9cde16a3c86f667c86023ee776d Author: Julian Reschke Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- qpack: section reference is broken (that's what you get for using MarkDown :-) Commit: 19d713dec417d1aebebc912bf00d4a2a302d6b9b https://github.com/quicwg/base-drafts/commit/19d713dec417d1aebebc912bf00d4a2a302d6b9b Author: Martin Thomson Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Merge pull request #1494 from reschke/patch-21 qpack: section reference is broken Compare: https://github.com/quicwg/base-drafts/compare/2991507bc0a6...19d713dec417 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b34ce23719d3_26f2ad22a89bc1028060-- From nobody Thu Jun 28 05:01:56 2018 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 00B90130EFC for ; Thu, 28 Jun 2018 05:01:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 In5jjnYRtcq8 for ; Thu, 28 Jun 2018 05:01:46 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 263B0130F93 for ; Thu, 28 Jun 2018 05:01:45 -0700 (PDT) Date: Thu, 28 Jun 2018 05:01:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530187304; bh=gi8TxW/C09vm22X50PKN4NgxIklh78mUNla/bDG62i8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gYTr6V0u8e+yrvWu5n2RDsP1FxH4IwTSkZWFKyMgcsXAffW6/JKN7uob73z4jyBgH D3r8oAY4pQzrQzaBZfhUDqHVqy8h/HnXiKgaGQCqvLMBAAxj7E3Cqaj7gLBjTrRy15 wz04ATbDBQjJonsMYB33fqT1TYh1QuZpz/q/Gq6A= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] qpack: section reference is broken (#1494) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34ce281daa2_75d72aee54652f58117094"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 12:01:49 -0000 ----==_mimepart_5b34ce281daa2_75d72aee54652f58117094 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1494. -- 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/1494#event-1706153063 ----==_mimepart_5b34ce281daa2_75d72aee54652f58117094 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1494.

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

----==_mimepart_5b34ce281daa2_75d72aee54652f58117094-- From nobody Thu Jun 28 06:36:20 2018 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 AF225130FED for ; Thu, 28 Jun 2018 06:36:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 b4P_u7buyrsf for ; Thu, 28 Jun 2018 06:36:16 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEC96130FEA for ; Thu, 28 Jun 2018 06:36:15 -0700 (PDT) Date: Thu, 28 Jun 2018 06:36:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530192974; bh=XoUP7Gwmw/v2QmGlKE9rWpcUnfwM605VeiT38iiqZaQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=c0CmqsWKejF6YPO1bcPIMo2Hm2dFitQSfWsx8KBL+T7ngxIJKuS41qsfbCxPPJGsC MZLnmI3+1bVdIvDSUK+Lx7blOM8l6xCFBmIexKROGfQqXYeHtnhC2ynI57591yOGag s37/wjKNUfPqBC89jDccyjLfsBR2Oa/BXXeEhWeo= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Packet Number Must Be Decrypted to Read Initial Token Field (#1492) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b34e44eea668_69f12ab6ffeb8f582769b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 28 Jun 2018 13:36:18 -0000 ----==_mimepart_5b34e44eea668_69f12ab6ffeb8f582769b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, the intent was for Retry not to use packet protection and to put the token outside of packet protection. Given all the open issues with Retry, should we declare it out of scope for the Montreal interop? -- 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/1492#issuecomment-401036991 ----==_mimepart_5b34e44eea668_69f12ab6ffeb8f582769b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yes, the intent was for Retry not to use packet protection and to put the token outside of packet protection.

Given all the open issues with Retry, should we declare it out of scope for the Montreal interop?

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

----==_mimepart_5b34e44eea668_69f12ab6ffeb8f582769b1-- From nobody Thu Jun 28 08:51:45 2018 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 58FDC130DCC for ; Thu, 28 Jun 2018 08:51:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 wxrZW_MhMX7Y for ; Thu, 28 Jun 2018 08:51:41 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 BE33B130DC7 for ; Thu, 28 Jun 2018 08:51:41 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530201100; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=95ulOeXG2sQR1vj/6/j82etPsKn05kdqD7/d3YSGceE=; b=Ysf/dlUOiO2gKfDE3Defc418dd/G57qaUlkYu+8S2oBn8XyIhhj7M3SF40mMMvfY+VTW7A97 8QX0g4BsCPoqVwlSQWgz3nc0RjJZiHYLc0a739YInR7FEdLNSjGsV5bYTX0EbIxqOTWKa0ci 6XlvMgdXtUTeP6T/llRrzeOGKmE= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b35040b.7f0fcc754480-smtp-out-n01; Thu, 28 Jun 2018 15:51:39 -0000 (UTC) Date: Thu, 28 Jun 2018 08:51:38 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b35040ade010_488f2b13e375bc1084575@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 708e9a: Actually fix reference Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35040addc80_488f2b13e375bc10844e0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 15:51:44 -0000 ----==_mimepart_5b35040addc80_488f2b13e375bc10844e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 708e9ad2c4685b8e0357174e3803724846001d79 https://github.com/quicwg/base-drafts/commit/708e9ad2c4685b8e0357174e3803724846001d79 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Actually fix reference **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35040addc80_488f2b13e375bc10844e0-- From nobody Thu Jun 28 09:00:55 2018 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 E8DFE130DE8 for ; Thu, 28 Jun 2018 09:00:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 k2olbzDLe9Ei for ; Thu, 28 Jun 2018 09:00:39 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4172C130DEA for ; Thu, 28 Jun 2018 09:00:39 -0700 (PDT) Date: Thu, 28 Jun 2018 09:00:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530201637; bh=Vzx+/R+SZBm8CG1m+bVFiWCeL7dfWS53LbcJpmoeYqI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C5Jz+cjEj5lePg5I9eQvm/HRxd/Gn/Rv8ImTt+feogKTyr495/xfO40T9bXYYnF+F 0TkGXQ1W5rlaG7nofb+AJ3zlpZvxAd7KwWbjX4Wj8u9pZVCQUJsqvZ4CfUUkRTo683 XWh+MRozLpY/PlZiTUW/Mr8QUyn/rSCk/gnSSNl4= From: Baptiste Jonglez Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b350625571b3_14373fa973f3cf8022753"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: jonglezb 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.26 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: Thu, 28 Jun 2018 16:00:49 -0000 ----==_mimepart_5b350625571b3_14373fa973f3cf8022753 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Resending old ACKs seems like a valid use-case. We have ongoing work that estimates the one-way-delay on a path (within the current Multipath QUIC setting). It relies on bundling a copy of the latest ACK for each path in the same return packet. So, some of these ACKs may potentially be quite old. With the current draft, this will cause `max_ack_delay` to increase a lot at the sender, making the RTO value too large to be useful. I get the impression that `max_ack_delay` is there to compensate delayed ACKs at the sender. We can expect the sender to have a bound on how long it delays ACKs (e.g. TCP on Linux has a max ACK delay of 200 ms), so why not explicitly communicate this bound from sender to receiver? -- 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/1438#issuecomment-401085671 ----==_mimepart_5b350625571b3_14373fa973f3cf8022753 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Resending old ACKs seems like a valid use-case. We have ongoing work = that estimates the one-way-delay on a path (within the current Multipath = QUIC setting). It relies on bundling a copy of the latest ACK for each p= ath in the same return packet. So, some of these ACKs may potentially be= quite old.

With the current draft, this will cause max_ack_delay to = increase a lot at the sender, making the RTO value too large to be useful= .

I get the impression that max_ack_delay is there to compe= nsate delayed ACKs at the sender. We can expect the sender to have a bou= nd on how long it delays ACKs (e.g. TCP on Linux has a max ACK delay of 2= 00 ms), so why not explicitly communicate this bound from sender to recei= ver?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b350625571b3_14373fa973f3cf8022753-- From nobody Thu Jun 28 10:02:11 2018 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 35177130E9D for ; Thu, 28 Jun 2018 10:02:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ujeOyFV1hm3k for ; Thu, 28 Jun 2018 10:02:07 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9FB6130F93 for ; Thu, 28 Jun 2018 10:02:05 -0700 (PDT) Date: Thu, 28 Jun 2018 10:02:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530205323; bh=hkTr72o3RvsEdDTCGOLYmANYgRJ6ezSC+JF6fbrnJkI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rWFFYHAw6/YWMluyFp7JDmGVtT1o31M56ja/VmeKVegs0afoi2lUKc/AfK4ZTTbz6 IR7O7srwkvPOvE+/glKSEcgGAzHdFDYBUEd9UwwwG9myL1A+sxgyQf7Ep34gFiCX3M slid81f7NIC80HxCPH7AyRouf2L2aryLnStmb+2w= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35148bd46f9_8fc3fdc645fef80124158"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Thu, 28 Jun 2018 17:02:10 -0000 ----==_mimepart_5b35148bd46f9_8fc3fdc645fef80124158 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You only increase max_ack_delay if there's a newly acknowledged largest acked packet. So sending old acks by itself doesn't increase max_ack_delay. Explicit communication is a way to bound this, and in theory it seems unnecessary, but I suspect adding it could mitigate some very weird edge cases. -- 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/1438#issuecomment-401104787 ----==_mimepart_5b35148bd46f9_8fc3fdc645fef80124158 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

You only increase max_ack_delay if there's a newly acknowledged larges= t acked packet. So sending old acks by itself doesn't increase max_ack_d= elay.

Explicit communication is a way to bound this, and in theory it seems = unnecessary, but I suspect adding it could mitigate some very weird edge = cases.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b35148bd46f9_8fc3fdc645fef80124158-- From nobody Thu Jun 28 11:44:54 2018 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 5152C13103D for ; Thu, 28 Jun 2018 11:44:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 wCV9jS4MYzQB for ; Thu, 28 Jun 2018 11:44:50 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79FC7130E01 for ; Thu, 28 Jun 2018 11:44:50 -0700 (PDT) Date: Thu, 28 Jun 2018 11:44:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530211489; bh=8YXUOMhT9zYUHWvzYl6ffbce1njlZEYM/TviVUVdvyE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q5PYlPLx42/TIAm7VbImxmWZhzh36IvSDtW7rBxoSDTEyviqch6+B1rYVnR1Xga7P h0FNedrP+oeTamcCqXHHW0EfJCFzcA+hQRdryAHhEeelM5ChcXoJo848JqWNUdnRUd SUkOAUy5hD4WZK6a8p/zaNR7EXpLF64aGl13oL4g= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b352ca158dd2_7a032ac5f4b82f6012915d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 28 Jun 2018 18:44:53 -0000 ----==_mimepart_5b352ca158dd2_7a032ac5f4b82f6012915d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Just a comment from the sideline - I'm not really keep track of NEW CID atm, but I'm worried that a peer can force feed new CID's so the state for an idle connection grows large. Any protection / guidance on this? Ideally a passive QUIC connection should only need to store a few ID's and counters. -- 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/1484#issuecomment-401134683 ----==_mimepart_5b352ca158dd2_7a032ac5f4b82f6012915d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Just a comment from the sideline - I'm not really keep track of NEW CI= D atm, but I'm worried that a peer can force feed new CID's so the state = for an idle connection grows large. Any protection / guidance on this? Id= eally a passive QUIC connection should only need to store a few ID's and = counters.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b352ca158dd2_7a032ac5f4b82f6012915d-- From nobody Thu Jun 28 13:53:04 2018 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 E0F6C130E5E for ; Thu, 28 Jun 2018 13:53:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 FtQC4ZHqZGlL for ; Thu, 28 Jun 2018 13:53:00 -0700 (PDT) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 D17B7130E1D for ; Thu, 28 Jun 2018 13:52:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xGSiimyiKJAEdFOfavcXWhlLSh8=; b=INMTn/StKgiyHjFG D1b+Z/IF3x2Gs7i+9S+Bc7v8FyoSt2pXU0LVNeewMj6uuwsR9BhhC4C1atSHQFbq 8ZLZkxUMfVvhwaVRS4vEa5ylpBcR/mZyaCOUfgh3ULla+u0seDN1fKx6QeOq/PPU umJIG0B7/okeHmc362xqFu5nmf8= Received: by filter0557p1iad2.sendgrid.net with SMTP id filter0557p1iad2-12941-5B354AA9-4E 2018-06-28 20:52:58.008543234 +0000 UTC Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0050p1mdw1.sendgrid.net (SG) with ESMTP id BpPOB5ltSk6KV1v4DIcjtw for ; Thu, 28 Jun 2018 20:52:57.634 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id 4874F40D2E for ; Thu, 28 Jun 2018 13:52:57 -0700 (PDT) Date: Thu, 28 Jun 2018 20:52:58 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Disagreement about Path Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b354aa94719b_79a93fd023006f808531d"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1jfOuYkXyFPrcJE2Ntpu7//rpoyfXE+QyiwK 0ymE5i2WK3pWJpafkEiyYzCvwdnkLGPBcXWUSuvMGD0IOHa3ep0Daw8KLrvpP7Hq3+ux8mTMBvWXFK ML5MLBY9xt8S2VOs6IrElsPDaSTsEtNzXMw2p0NtgL1ONCDsmC+CBG4AJaMtro8gnyy2nPYPbfjsjM U= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 20:53:02 -0000 ----==_mimepart_5b354aa94719b_79a93fd023006f808531d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Follow-on issue from #1465 and #1484. The existing text says that for the first transmission on a new path, you have to use a higher-order CID (greater sequence number) than you've ever used before; once a path exists, you can't use a lower-order CID than you've ever sent or received on the network. Two scenarios: > A client has probed an alternate path, but not migrated, and then sends no traffic on that path for a prolonged period of time. The client considers the path to be idle; the server considers the path to have timed out. After some time, the client decides to re-probe. It's permitted to use the same CID that it had previously used. However, if the server has considered the path closed, it might not remember the old CID that had been bound to a path. > > This will provoke a Stateless Reset from the server in response to the probe, even though the server considers the connection itself to be valid, and would accept the probe if a fresh CID were used. ------------- > An endpoint has advanced to a new CID; the peer, seeing the new CID, now considers older CIDs invalid after a certain period. A packet with an old CID is severely delayed. The peer, upon receipt of the delayed packet, considers it to belong to an unknown connection and generates a Stateless Reset. Possible solution: We might need to have the side forgetting CIDs explicitly inform the peer that it will no longer use or accept CIDs older than a certain cutoff. You have to remember old CIDs you've issued until this frame is acknowledged; upon receipt of this frame, you no longer consider the stateless reset tokens valid. -- 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/1495 ----==_mimepart_5b354aa94719b_79a93fd023006f808531d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Follow-on issue from #1465 and #1484. The existing text says that for the first transmission on a new path, you have to use a higher-order CID (greater sequence number) than you've ever used before; once a path exists, you can't use a lower-order CID than you've ever sent or received on the network.

Two scenarios:

A client has probed an alternate path, but not migrated, and then sends no traffic on that path for a prolonged period of time. The client considers the path to be idle; the server considers the path to have timed out. After some time, the client decides to re-probe. It's permitted to use the same CID that it had previously used. However, if the server has considered the path closed, it might not remember the old CID that had been bound to a path.

This will provoke a Stateless Reset from the server in response to the probe, even though the server considers the connection itself to be valid, and would accept the probe if a fresh CID were used.

An endpoint has advanced to a new CID; the peer, seeing the new CID, now considers older CIDs invalid after a certain period. A packet with an old CID is severely delayed. The peer, upon receipt of the delayed packet, considers it to belong to an unknown connection and generates a Stateless Reset.

Possible solution: We might need to have the side forgetting CIDs explicitly inform the peer that it will no longer use or accept CIDs older than a certain cutoff. You have to remember old CIDs you've issued until this frame is acknowledged; upon receipt of this frame, you no longer consider the stateless reset tokens valid.

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

----==_mimepart_5b354aa94719b_79a93fd023006f808531d-- From nobody Thu Jun 28 13:54:13 2018 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 656BC130E5E for ; Thu, 28 Jun 2018 13:54:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HElX44ow0k-F for ; Thu, 28 Jun 2018 13:54:10 -0700 (PDT) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 B51E9130E1D for ; Thu, 28 Jun 2018 13:54:09 -0700 (PDT) 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=MZUw9zfA26iFS5GXHAq3HDiT4Mw=; b=lMuLUvr+wY1tir0Q /lEbIP0GzLk9uxkHLlDRj3EqE4R2AuPsq18CYHmXoeGYWScHEFTjZQSUVkabH5yn 0zcf72TS6tzJnW1wExUai2Gngaq7QcVmcQmAedYEBK/tG3yOMOO7f3GIvOm2yjR1 a/GYitVIXzQHn9ybYq5z4R3WeAc= Received: by filter0620p1iad2.sendgrid.net with SMTP id filter0620p1iad2-4256-5B354AEE-A0 2018-06-28 20:54:07.018092347 +0000 UTC Received: from github-lowworker9-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id 51s8GHCGRImsMtC2WSUhmA for ; Thu, 28 Jun 2018 20:54:06.970 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker9-cp1-prd.iad.github.net (Postfix) with ESMTP id EA4CDA1677 for ; Thu, 28 Jun 2018 13:54:06 -0700 (PDT) Date: Thu, 28 Jun 2018 20:54:07 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b354aeee8be1_52a73fd5f5d70f7c1546d8"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2/zk+5gMJGTXPEWey0IokyHZBRVUwkWh16Sq 7jv13/g/w/6urCBdrwuTG5z7vBAp0FTjbVYs9i8QfJku4mZUddPcWag2NbmaN6PhBhGytr0mdkOPxP rSFm5qY4Egj6Hig3OFA/AKDy8abWCVmV6BSBvZAahglAzZMBl2ca6DUXg0gvOu6I35UcMvRHMzwcto E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 20:54:12 -0000 ----==_mimepart_5b354aeee8be1_52a73fd5f5d70f7c1546d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I had been playing with adding a RETIRE_CONNECTION_ID frame for that purpose. As I start digging into when you can forget an old CID, you run into situations where the peers don't agree, such as #1495. -- 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/1484#issuecomment-401170074 ----==_mimepart_5b354aeee8be1_52a73fd5f5d70f7c1546d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I had been playing with adding a RETIRE_CONNECTION_ID frame for that purpose. As I start digging into when you can forget an old CID, you run into situations where the peers don't agree, such as #1495.

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

----==_mimepart_5b354aeee8be1_52a73fd5f5d70f7c1546d8-- From nobody Thu Jun 28 14:12:28 2018 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 96C631310DA for ; Thu, 28 Jun 2018 14:12:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 xWxZpdFZYg8w for ; Thu, 28 Jun 2018 14:12:16 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 C43471310C9 for ; Thu, 28 Jun 2018 14:12:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530220336; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=aMCEQMJF7sNWCCnh1NZ+RVYjWM+1aLuhf2avQd3fbts=; b=jV/dZKZ1hTkVfOnw/cJRoEGaSAlcWei+nZk8b2prFdbJ4ccEyygNbigZGrUnOMDPcQOWJuUN CCABs4m4Y7EHqGaVRxkcqclVhwhhLuLI5GpZ50kqWiW5X807kSv+yX0EzQaBlkkjnYhH718x R8ivrGcg6jHOlAxewqJgYitvfoQ= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b354f2f.7f8528c65c60-smtp-out-n01; Thu, 28 Jun 2018 21:12:15 -0000 (UTC) Date: Thu, 28 Jun 2018 14:12:15 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b354f2f79248_21b12af84190dbfc4913@hookshot-fe-cace476.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 6127d5: Multi-CID in NCID frame Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b354f2f78ecc_21b12af84190dbfc490ec"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 21:12:26 -0000 ----==_mimepart_5b354f2f78ecc_21b12af84190dbfc490ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/cid_frames Home: https://github.com/quicwg/base-drafts Commit: 6127d5acc0cab033b5ee54a5cf5e85047cfc7f87 https://github.com/quicwg/base-drafts/commit/6127d5acc0cab033b5ee54a5cf5e85047cfc7f87 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Multi-CID in NCID frame Commit: eb54e0f9e48a3a80da890a13ecd7446f88097733 https://github.com/quicwg/base-drafts/commit/eb54e0f9e48a3a80da890a13ecd7446f88097733 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- CID lifetime frames Commit: 0b233fe12e56c8a85602095f7bb2990c508693bc https://github.com/quicwg/base-drafts/commit/0b233fe12e56c8a85602095f7bb2990c508693bc Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Include in table Compare: https://github.com/quicwg/base-drafts/compare/6127d5acc0ca^...0b233fe12e56 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b354f2f78ecc_21b12af84190dbfc490ec-- From nobody Thu Jun 28 14:27:55 2018 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 B69F5131038 for ; Thu, 28 Jun 2018 14:27:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 XlrNJG0XxOms for ; Thu, 28 Jun 2018 14:27:51 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 6C979128CF3 for ; Thu, 28 Jun 2018 14:27:51 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530221270; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=RMoElVnrnYOFBUe1O//a6pPTDIkE3pc2wBx8Ln541Js=; b=QSFsgj+eqR2YK/gR5fggOWHeVs7toSzcmGHAMMajkWK5Bw6DcuSAJyehBnTJ1PsrH7z260LI y8rZ2/DPtOAk11FT0makcmAEogKThRemmYquvoebW8iuEXVwUJ85oF8QBjsp8TZ9NHkKpLqF vRM9WHwFkcK0VyejtNs+8bhTuZk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.45]) by mxa.mailgun.org with ESMTP id 5b3552d6.7ffb27d0c6f0-smtp-out-n02; Thu, 28 Jun 2018 21:27:50 -0000 (UTC) Date: Thu, 28 Jun 2018 14:27:49 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b3552d56ab0b_28fd2b2960537c08101469@hookshot-fe-5a11256.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b0dc5b: SRT, too Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3552d56a7c7_28fd2b2960537c081013f4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 21:27:53 -0000 ----==_mimepart_5b3552d56a7c7_28fd2b2960537c081013f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/cid_frames Home: https://github.com/quicwg/base-drafts Commit: b0dc5b005a3c9e16eb705bb11e060d71ee0c2ee1 https://github.com/quicwg/base-drafts/commit/b0dc5b005a3c9e16eb705bb11e060d71ee0c2ee1 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- SRT, too **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3552d56a7c7_28fd2b2960537c081013f4-- From nobody Thu Jun 28 14:44:43 2018 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 AE6F4130FAC for ; Thu, 28 Jun 2018 14:44:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 zZ0YlrSV36TZ for ; Thu, 28 Jun 2018 14:44:39 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 2B696130E16 for ; Thu, 28 Jun 2018 14:44:39 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530222278; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=zsvIiVYJNR99n9K2rBfKrmSq81+3mSR6QWoWjX7QK+M=; b=X5xgLF5T4j7Y8SKfy+GQ2zXXx85BYphXMo0Wl+rbP6N5YQBs+8mq/x849ZOQGc64WaP1AfwS MraaoXd7/2JB/Qw1ze/SNRsceSjaGUAeiw69TjZt8I1/D+cx1jd21zGSHz0+6PTFadF47M4G Oz/FI26W/I80phqPtU5UntoPMyI= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mbishop=evequefou.be@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b3556c6.7f3ceb65b870-smtp-out-n01; Thu, 28 Jun 2018 21:44:38 -0000 (UTC) Date: Thu, 28 Jun 2018 14:44:38 -0700 From: Mike Bishop Reply-To: Mike Bishop To: quic-issues@ietf.org Message-ID: <5b3556c617af5_7ea82aee15343c0c6266@hookshot-fe-88eb02d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] c38ecf: CID lifetime frames Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b3556c61771d_7ea82aee15343c0c62527"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Thu, 28 Jun 2018 21:44:41 -0000 ----==_mimepart_5b3556c61771d_7ea82aee15343c0c62527 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/transport/cid_frames Home: https://github.com/quicwg/base-drafts Commit: c38ecfc5fc9c0558f5463076e089a3199099a65d https://github.com/quicwg/base-drafts/commit/c38ecfc5fc9c0558f5463076e089a3199099a65d Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- CID lifetime frames Commit: 8e1f24f8e42346c7b0cabdfbf16c180f38864c08 https://github.com/quicwg/base-drafts/commit/8e1f24f8e42346c7b0cabdfbf16c180f38864c08 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Include in table Commit: fd3c76ac5ab0d172cbec53f8f6194f569303cf15 https://github.com/quicwg/base-drafts/commit/fd3c76ac5ab0d172cbec53f8f6194f569303cf15 Author: Mike Bishop Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- SRT, too Compare: https://github.com/quicwg/base-drafts/compare/b0dc5b005a3c...fd3c76ac5ab0 **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b3556c61771d_7ea82aee15343c0c62527-- From nobody Thu Jun 28 14:47:09 2018 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 B45111310FF for ; Thu, 28 Jun 2018 14:46:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 cQ-K1WzikvnU for ; Thu, 28 Jun 2018 14:46:51 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3B44131104 for ; Thu, 28 Jun 2018 14:46:51 -0700 (PDT) Date: Thu, 28 Jun 2018 14:46:50 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530222411; bh=4M/dhFZoYTYqXdYzPzxDZMnYZAezojMy54tOhUeyzaA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=b0EHLIbE7xocdhvvIRXxZDmBMONz8uRl3NdM8POQJA9riPDy2YayyS9zrPI5Ska4j ybabGVWhhN6ePcJ3rV3uIu8zFLty8LUWzAYbgTh7FGRcTvV7jwTq//r/sc+Sr2GSvl qnNMaByPRSRgPPNfC0M1Pd9B+V685SOmtAkr+SdM= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35574ad7499_80d3f89da6b0f78104062"; 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.26 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: Thu, 28 Jun 2018 21:47:08 -0000 ----==_mimepart_5b35574ad7499_80d3f89da6b0f78104062 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fixes #1495 by adding an explicit `RETIRE_CONNECTION_ID` frame. Fixes #1464 by adding an explicit `REQUEST_CONNECTION_ID` frame. (A previous version also changed `NEW_CONNECTION_ID` to contain a series of CIDs, but that's entirely separable if we decide we want that.) You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1496 -- Commit Summary -- * CID lifetime frames * Include in table * SRT, too -- File Changes -- M draft-ietf-quic-transport.md (117) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1496.patch https://github.com/quicwg/base-drafts/pull/1496.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/1496 ----==_mimepart_5b35574ad7499_80d3f89da6b0f78104062 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fixes #1495 by adding an explicit RETIRE_CONNECTION_ID frame.

Fixes #1464 by adding an explicit REQUEST_CONNECTION_ID frame.

(A previous version also changed NEW_CONNECTION_ID to contain a series of CIDs, but that's entirely separable if we decide we want that.)

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

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

Commit Summary

  • CID lifetime frames
  • Include in table
  • SRT, too

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 mute the thread.

----==_mimepart_5b35574ad7499_80d3f89da6b0f78104062-- From nobody Thu Jun 28 15:20:41 2018 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 ACBD6130FCB for ; Thu, 28 Jun 2018 15:20:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 OlGItHnaJy-W for ; Thu, 28 Jun 2018 15:20:36 -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 C4116130ECE for ; Thu, 28 Jun 2018 15:20:36 -0700 (PDT) Date: Thu, 28 Jun 2018 15:20:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530224435; bh=zIU9F3wesoRGbQUduq+YXFwmPTZuhOtK71pVKXLlAQ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Qjq2USs6W1LsqoifoRD+HiamNhF1lfq4eDbCJf8bUVPQ0+w7tjRQ19CP6UZuOLgoh VFkQp4ODz23PYa2E0ldz7Q9/aLQt9JNJOI90/YcCUiT0pTrtjxxfjlt72YKzcFq2qh uvxOc3I4u/MOuphGEXJbrdeqrJsSU/1dRQY1j3B8= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b355f3396eff_24512ae058a70f54974d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Thu, 28 Jun 2018 22:20:39 -0000 ----==_mimepart_5b355f3396eff_24512ae058a70f54974d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The ACK requirement does not handle malicous intent to drain resources. Could there be a negotiated limit that relates to how many migrations are being excercised that both sides can influence? -- 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/1495#issuecomment-401190673 ----==_mimepart_5b355f3396eff_24512ae058a70f54974d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The ACK requirement does not handle malicous intent to drain resources. Could there be a negotiated limit that relates to how many migrations are being excercised that both sides can influence?

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

----==_mimepart_5b355f3396eff_24512ae058a70f54974d-- From nobody Thu Jun 28 15:35:44 2018 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 555E613112E for ; Thu, 28 Jun 2018 15:35:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 HH4nFZbsidgq for ; Thu, 28 Jun 2018 15:35:26 -0700 (PDT) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 61991131104 for ; Thu, 28 Jun 2018 15:35:26 -0700 (PDT) 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=TVQ0PlT8DfVuIG4iaer80BF1Ils=; b=oLayY/1YwU9ZmoVs MJ/KqQEWetEFOCBYbrVufuobsnTrPiVbbsmHDS7QOL7d6cwF7ojzw+EWYyXhu2sG zppAxd8W4reGv7GRy+oVpcEPvuD5HpyPM0Db0w1YDnhuhQwl8NKanAPeQjrJnJHC XjlToq4WjxB1MB5MaEm2xc1rEpk= Received: by filter0165p1iad2.sendgrid.net with SMTP id filter0165p1iad2-11332-5B3562AC-60 2018-06-28 22:35:25.012712168 +0000 UTC Received: from github-lowworker-e8fa9ff.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 2vDj4kWmSvKPf516yI4kNg for ; Thu, 28 Jun 2018 22:35:25.012 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e8fa9ff.cp1-iad.github.net (Postfix) with ESMTP id 0033842038B for ; Thu, 28 Jun 2018 15:35:25 -0700 (PDT) Date: Thu, 28 Jun 2018 22:35:25 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3562acf2eed_6e32ad4f1df2f509966a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak04hodoEDKxF2gt0aF2nEwbVtTcm4eX7F1jAU pU1EPb2FxSgvpFaSNSDkRlljFMg8nTvNZompTaHUA3LbxNFXtBRbWVeAlwjDzSEq77g2sLiWl0lure 4baMhZEcCl24qq/mTZihFV3zi04SzjqAAwSG+nqNbDcF3izO5mffbFIIj2Ud6tmWeC3WiWqRsUN7Zj I= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 22:35:43 -0000 ----==_mimepart_5b3562acf2eed_6e32ad4f1df2f509966a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Given your recent PR and the 3 open issues, I think it makes sense to talk about CIDs in Montreal. Mike, would you be willing the present on the relevant issues there? -- 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/1495#issuecomment-401193547 ----==_mimepart_5b3562acf2eed_6e32ad4f1df2f509966a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Given your recent PR and the 3 open issues, I think it makes sense to talk about CIDs in Montreal. Mike, would you be willing the present on the relevant issues there?

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

----==_mimepart_5b3562acf2eed_6e32ad4f1df2f509966a-- From nobody Thu Jun 28 15:35:53 2018 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 050C6131104 for ; Thu, 28 Jun 2018 15:35:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 YMpCbRPQnX0O for ; Thu, 28 Jun 2018 15:35:43 -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 49F1A1310FF for ; Thu, 28 Jun 2018 15:35:43 -0700 (PDT) Date: Thu, 28 Jun 2018 15:35:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530225342; bh=2JyWW43rdrpntmtf5pZ4ck9SbhY3MODBylmHxEDDi9c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JJJYIiUHDIHQcRSPwUUXvtTnp1wtjST18n3HPKdVsnJ830zHGnj7kyqtakZOn+B+9 sFjS7a6BqWDFCkCYLncQYmgEUr1aSqCdXKg88HVwOa8rsBjxqqV1CXXE/F58Q3mGKZ 1CWSxi8xpMKDLJSQf4pqboH5yrcEjH/Ium014gRo= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3562bdd78c9_701d3fee54924f78754ec"; 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.26 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: Thu, 28 Jun 2018 22:35:48 -0000 ----==_mimepart_5b3562bdd78c9_701d3fee54924f78754ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Maybe I should amend it to SHOULD accept the packets and MUST NOT Stateless Reset them, because that's really the limitation. You can't respond to old CIDs with a Stateless Reset until you're sure the other side has gotten the retirement packet, but there's nothing seriously wrong with dropping them. If you just keep sending `RETIRE_CID` and start dropping packets with old CIDs, you'll either reach a stable state again or eventually the connection will time out and die because no packets are getting acknowledged. -- 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/1495#issuecomment-401193605 ----==_mimepart_5b3562bdd78c9_701d3fee54924f78754ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Maybe I should amend it to SHOULD accept the packets and MUST NOT Stat= eless Reset them, because that's really the limitation. You can't respon= d to old CIDs with a Stateless Reset until you're sure the other side has= gotten the retirement packet, but there's nothing seriously wrong with d= ropping them.

If you just keep sending RETIRE_CID and start dropping pa= ckets with old CIDs, you'll either reach a stable state again or eventual= ly the connection will time out and die because no packets are getting ac= knowledged.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3562bdd78c9_701d3fee54924f78754ec-- From nobody Thu Jun 28 15:36:07 2018 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 2A0A2130FDE for ; Thu, 28 Jun 2018 15:36:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 6E6HcdnJ-SGg for ; Thu, 28 Jun 2018 15:36:01 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 69DE41310EF for ; Thu, 28 Jun 2018 15:36:01 -0700 (PDT) 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=kcPwEd9B7Om/grQZjNNvmZXbMtk=; b=awpDamFoztdqqGQk XU1fBURWzbdW3sGRTfVZ8xNccxX1N3f8GeqmCI1jO+rNEKmWYpm5PCI8i6gpsm0g 9ddNObvHlQve6RUkZGGxLSrysd0UxN+vcu8tkVD6D31Xjnh2MbTZrQ0p8GqyfPom dvKWTe8VdicQBOM1vzyHjZRpZEw= Received: by filter0228p1iad2.sendgrid.net with SMTP id filter0228p1iad2-27875-5B3562CF-78 2018-06-28 22:35:59.982039091 +0000 UTC Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0033p1mdw1.sendgrid.net (SG) with ESMTP id lWFWWndCRpK-Hpe4D-TGYA for ; Thu, 28 Jun 2018 22:35:59.725 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id 64614422F1 for ; Thu, 28 Jun 2018 15:35:59 -0700 (PDT) Date: Thu, 28 Jun 2018 22:36:00 +0000 (UTC) From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3562cf632aa_17a83f9b0cc7ef84109997"; 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 X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1As2EacqbTu6dYciRZr/2YMPHjNA8JfFDt6o 28/6rdN3A2NVNGHXr6ELD9oqSv7vjgyQeF9v9Mb8zKcg5dYZfdbE3cINGjy5q3gD0bXKPzBqiVsbhe 7CPeY5ukJZzBxDTpqthrsr/NJjcEO0ySoJqKRYDfuonXbU2SThpCvS0PRibnDnWURsXf46XX5AgCYl k= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 22:36:05 -0000 ----==_mimepart_5b3562cf632aa_17a83f9b0cc7ef84109997 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @ianswett, sure. -- 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/1495#issuecomment-401193672 ----==_mimepart_5b3562cf632aa_17a83f9b0cc7ef84109997 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett, sure.

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

----==_mimepart_5b3562cf632aa_17a83f9b0cc7ef84109997-- From nobody Thu Jun 28 16:16:59 2018 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 292101310AF for ; Thu, 28 Jun 2018 16:16:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 SQS2gP630ydX for ; Thu, 28 Jun 2018 16:16:55 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96AD3130E2E for ; Thu, 28 Jun 2018 16:16:55 -0700 (PDT) Date: Thu, 28 Jun 2018 16:16:54 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530227814; bh=6mv3YsA2k2IVZMi5FYQALr4p0RrkYA9ck0Ys/ea2ViQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=reS/5CJNMT4F3YIjL+if5x0PPBbJIyGR+k9CYO7qCyXaGhmpWxYNupnO+P5KGuZct t9x/uxhxQDB9/7WAoMPnglqsOzaubREhjZfd4JTJyAFsnGn5fBhdP170y4Qn6YG05F qZVh1tSr7loHHzBMc2mRqyjegC9TVDeaiex+c06w= From: janaiyengar Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fragility in ECN counters with lost acks (#1481) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b356c66a3144_6613fea0ef50f7c564e8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Thu, 28 Jun 2018 23:16:58 -0000 ----==_mimepart_5b356c66a3144_6613fea0ef50f7c564e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't think this is adequate. @ianswett pointed out that a sender may choose to not retain state about a packet that is not yet acknowledged because, for example, the contents were retransmitted in a new packet. When an ack for such a "forgotten" packet arrives, the endpoint won't know it to be an as yet unacknowledged packet, since there's no state for the packet. At the same time, the ECN counters would have increased. -- 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/1481#issuecomment-401200988 ----==_mimepart_5b356c66a3144_6613fea0ef50f7c564e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I don't think this is adequate. @ian= swett pointed out that a sender may choose to not retain state about = a packet that is not yet acknowledged because, for example, the contents = were retransmitted in a new packet. When an ack for such a "forgotten" pa= cket arrives, the endpoint won't know it to be an as yet unacknowledged p= acket, since there's no state for the packet. At the same time, the ECN c= ounters would have increased.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b356c66a3144_6613fea0ef50f7c564e8-- From nobody Thu Jun 28 17:02:41 2018 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 0C908130DF1 for ; Thu, 28 Jun 2018 17:02:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 wEerxxePqka7 for ; Thu, 28 Jun 2018 17:02:37 -0700 (PDT) Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82C41130E3F for ; Thu, 28 Jun 2018 17:02:37 -0700 (PDT) Date: Thu, 28 Jun 2018 17:02:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530230556; bh=3+nBWISz3dprojAvqf8P+fSyg2UEtwsjXOq3jTbb+0k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=klWFF8L9PRvmpfZMfWHHFEVl9KlUGT7tK0tPQff8PTNUnSrQZQtLWtCVuyODePIeZ eALC4y7uDMYcEn6IWHVD0UXrr+A7gf+pO36xQS60kNArGZPQk8TsfBn+s1z3Pguhk+ 52YVZ6C3A7jKVHqDV7qLHN40r0Na8MsDmz+K42jk= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35771bd3781_274a3fbc14568f78582e1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 00:02:39 -0000 ----==_mimepart_5b35771bd3781_274a3fbc14568f78582e1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @rpaulo pushed 1 commit. 6d2376b Use an alternative approach to decoding the packet number. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1493/files/e52c8f947d9edee689aebed3546059ddf5b44759..6d2376ba3cb035ae30d6cb6a725bea096cf84f29 ----==_mimepart_5b35771bd3781_274a3fbc14568f78582e1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo pushed 1 commit.

  • 6d2376b Use an alternative approach to decoding the packet number.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b35771bd3781_274a3fbc14568f78582e1-- From nobody Thu Jun 28 17:04:33 2018 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 E7A7E130DF1 for ; Thu, 28 Jun 2018 17:04:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ZZ4NmzhjcoJB for ; Thu, 28 Jun 2018 17:04:29 -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 19D4E130E37 for ; Thu, 28 Jun 2018 17:04:29 -0700 (PDT) Date: Thu, 28 Jun 2018 17:04:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530230668; bh=nSsjrQUUHi3egscYH5apYAIAiLVmCChG7d0PXWvmPJk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eTsIAuG1zquaTpbsALu7+QpwSrkVM297hUwupv09CbRet3n+e2BcP/F0TdBw9TNkq L81fMARc5xNE6V7WUQwuCmLA9yZZejDztSZ+EvQDroey65L11er7ABEJqZxISxmdlU cEhUkNmCmDE4LIm8sL1pIiLS46eRw8nQI4jn8snc= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35778c23bb7_12d62adf8040af5838787"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 00:04:31 -0000 ----==_mimepart_5b35778c23bb7_12d62adf8040af5838787 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @rpaulo pushed 1 commit. d42c1f1 Wrap at 65 -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1493/files/6d2376ba3cb035ae30d6cb6a725bea096cf84f29..d42c1f1ad56bc5fd3045fc0fed2fe93192282451 ----==_mimepart_5b35778c23bb7_12d62adf8040af5838787 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b35778c23bb7_12d62adf8040af5838787-- From nobody Thu Jun 28 17:06:16 2018 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 3EAA4130E37 for ; Thu, 28 Jun 2018 17:06:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 5LLWg7pMdE00 for ; Thu, 28 Jun 2018 17:06:12 -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 50EA9130DF1 for ; Thu, 28 Jun 2018 17:06:12 -0700 (PDT) Date: Thu, 28 Jun 2018 17:06:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530230770; bh=zg40VYfut6UpeB5DbmNxjoiL3WHnK8EW43zXx0wCJvI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ujb5JgjeV7GLfhcEqYo3ZochLatpmDd12/ODgQ9CKULRWJ892yplYUb0mbRZjOZ8p X24jujugLar4/UJzG7boWt5OEzcSin6T/7rbZ60/HkbvZ+V1KLm1Lq3DRbJYRASFhG QPg2Ni1c+QWbZkLvnS2wIhKDcTFGdEQKRRI31IaM= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3577f24f909_6e0a3fa9a68fef78104014"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 00:06:15 -0000 ----==_mimepart_5b3577f24f909_6e0a3fa9a68fef78104014 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @rpaulo pushed 1 commit. e607539 Whitespace lint -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1493/files/d42c1f1ad56bc5fd3045fc0fed2fe93192282451..e607539abcf41f7cd57b6de8869dddb7b01de361 ----==_mimepart_5b3577f24f909_6e0a3fa9a68fef78104014 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@rpaulo pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3577f24f909_6e0a3fa9a68fef78104014-- From nobody Thu Jun 28 17:19:13 2018 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 774B8130DEF for ; Thu, 28 Jun 2018 17:19:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 65cX_GV0TpFv for ; Thu, 28 Jun 2018 17:19:07 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13CA3130E37 for ; Thu, 28 Jun 2018 17:19:07 -0700 (PDT) Date: Thu, 28 Jun 2018 17:19:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530231546; bh=Aa5YSW7ZAQy6Jle3hd4XXJcUqTpsr3BI937+yWdQrDw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nYDOKoCBSoaDAMFjmhaTAWeRiAaiKlrplburUR440244uhK0rDVezT9MbbxnjjIyf KQhp4LEh5sCUvm3+dog5CDt/pQ10LQ5+WQ4qcJtu5wCRXGFShhTyZhSMkBs8YLCRjF E6l5aYr6g1lnsnQCufcQHOrhlz7qlJNr+SnNFMSU= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b357afa77614_12e82adf8040af58718fd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 00:19:11 -0000 ----==_mimepart_5b357afa77614_12e82adf8040af58718fd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. 52ba67e Small editorial tweaks -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1493/files/e607539abcf41f7cd57b6de8869dddb7b01de361..52ba67e4eb75b1b71e613073a86fbfeca296f70c ----==_mimepart_5b357afa77614_12e82adf8040af58718fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b357afa77614_12e82adf8040af58718fd-- From nobody Thu Jun 28 17:21:06 2018 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 5E3B3130E3F for ; Thu, 28 Jun 2018 17:21:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 gwEUscTQPKoR for ; Thu, 28 Jun 2018 17:21:01 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 1C7B1130DEF for ; Thu, 28 Jun 2018 17:21:01 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530231660; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=4h2jQA4bnHf32Bj0Zcc39f5MDmlkx+Z+IV7F0gz6NQc=; b=JWVwPaVKtzEW8HfeDRbvke7tyH7a/mnO9PDMFfsuIN7FqC3hIzsfvIoz/ias6iqEUq/RugqA kKBmTV0siMCTPbPKxeTFxueJAZ66rkvMWx+HGRNCQfqDWvLlnnD7vdpfl0C9Wa94Z9FiKyzX JNrLgTqR3Ow7yAqoJplRPRjyWkk= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b357b6c.7f6dd0371ba0-smtp-out-n02; Fri, 29 Jun 2018 00:21:00 -0000 (UTC) Date: Thu, 28 Jun 2018 17:20:59 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b357b6b2fae2_1f7f92abea6231c18369f6@hookshot-fe-dfcc362.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] ba4d1a: Add an appendix related to packet number decoding. Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b357b6b2f48d_1f7f92abea6231c18368d7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 00:21:04 -0000 ----==_mimepart_5b357b6b2f48d_1f7f92abea6231c18368d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: ba4d1a8cb381f511ec1864b1bc69dedadb1ff621 https://github.com/quicwg/base-drafts/commit/ba4d1a8cb381f511ec1864b1bc69dedadb1ff621 Author: Rui Paulo Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Add an appendix related to packet number decoding. Commit: e52c8f947d9edee689aebed3546059ddf5b44759 https://github.com/quicwg/base-drafts/commit/e52c8f947d9edee689aebed3546059ddf5b44759 Author: Rui Paulo Date: 2018-06-27 (Wed, 27 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove whitespace Commit: 6d2376ba3cb035ae30d6cb6a725bea096cf84f29 https://github.com/quicwg/base-drafts/commit/6d2376ba3cb035ae30d6cb6a725bea096cf84f29 Author: Rui Paulo Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Use an alternative approach to decoding the packet number. Commit: d42c1f1ad56bc5fd3045fc0fed2fe93192282451 https://github.com/quicwg/base-drafts/commit/d42c1f1ad56bc5fd3045fc0fed2fe93192282451 Author: Rui Paulo Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Wrap at 65 Commit: e607539abcf41f7cd57b6de8869dddb7b01de361 https://github.com/quicwg/base-drafts/commit/e607539abcf41f7cd57b6de8869dddb7b01de361 Author: Rui Paulo Date: 2018-06-28 (Thu, 28 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Whitespace lint Commit: 52ba67e4eb75b1b71e613073a86fbfeca296f70c https://github.com/quicwg/base-drafts/commit/52ba67e4eb75b1b71e613073a86fbfeca296f70c Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Small editorial tweaks Capitalize and shorten title Rename some variables Indent a little more Commit: 80b08852feebdfc7ecc761170ef03ec3933ae63e https://github.com/quicwg/base-drafts/commit/80b08852feebdfc7ecc761170ef03ec3933ae63e Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Merge pull request #1493 from rpaulo/master Add an appendix related to packet number decoding. Compare: https://github.com/quicwg/base-drafts/compare/708e9ad2c468...80b08852feeb **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b357b6b2f48d_1f7f92abea6231c18368d7-- From nobody Thu Jun 28 17:21:12 2018 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 6FFE5130DEF for ; Thu, 28 Jun 2018 17:21:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.008 X-Spam-Level: X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oWjLhEDPwpPR for ; Thu, 28 Jun 2018 17:21:02 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6385130E37 for ; Thu, 28 Jun 2018 17:21:02 -0700 (PDT) Date: Thu, 28 Jun 2018 17:21:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530231661; bh=hH9oexAAQZ0lQtWjHSsvTcK1cmauXT5y4lAaGSXQN6E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qcA+8g5W7SYMLnf8xclwGHvwRvb63Xo6uIC270omyUs6kp+DMYcssKrzzwNp/+gNt mUtIUkSzy79X0vRALa5qW7WF07V0u0aCXw5jodAY9VfWi3cDg8u+UId5W1bBFxmg0E INtgYOvJUFsk6yVM+vo5JG5YLKUldDCKXe097aoM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add an appendix related to packet number decoding. (#1493) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b357b6ddf0fa_7d372b1ab746af589054c"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 00:21:05 -0000 ----==_mimepart_5b357b6ddf0fa_7d372b1ab746af589054c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1493. -- 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/1493#event-1707602158 ----==_mimepart_5b357b6ddf0fa_7d372b1ab746af589054c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1493.

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

----==_mimepart_5b357b6ddf0fa_7d372b1ab746af589054c-- From nobody Thu Jun 28 17:24:20 2018 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 01644130DEF for ; Thu, 28 Jun 2018 17:24:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 A87if5Az80KL for ; Thu, 28 Jun 2018 17:24:16 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 90FE5130E37 for ; Thu, 28 Jun 2018 17:24:16 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530231855; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=5OVCzzF3i8Ok/I5ydTPNqkllwwZfgS6ZPBZOvC+MFEY=; b=XxXMAWW2saCKAbUgYGdGl8bJjsnjwYIiI3748Hw1aSu4P+fHMthp/X8D8jok5AZe6XfKygjK xinJLdqfmITYW/z73STEYYOK/PcRt3we4CkP8i7W7+duS6ogSKC2lQ5JtA35+OG+fRI8LKRP IBYOHthgmzja5qcZacuH8Ed4ijg= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b357c2f.7f431a097120-smtp-out-n03; Fri, 29 Jun 2018 00:24:15 -0000 (UTC) Date: Thu, 28 Jun 2018 17:24:15 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b357c2fb8368_37532b2a22295c0861183@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] a290ab: Fix references Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b357c2fb7eca_37532b2a22295c08610dc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 00:24:19 -0000 ----==_mimepart_5b357c2fb7eca_37532b2a22295c08610dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/qpack-transport-ref Home: https://github.com/quicwg/base-drafts Commit: a290ab8bc884fd817fe6c17ff27ce8f3253acf3d https://github.com/quicwg/base-drafts/commit/a290ab8bc884fd817fe6c17ff27ce8f3253acf3d Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-qpack.md Log Message: ----------- Fix references **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b357c2fb7eca_37532b2a22295c08610dc-- From nobody Thu Jun 28 17:26:08 2018 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 C7624130DEF for ; Thu, 28 Jun 2018 17:26:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 i8_BiWoquTaD for ; Thu, 28 Jun 2018 17:26:04 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D302130E3F for ; Thu, 28 Jun 2018 17:26:04 -0700 (PDT) Date: Thu, 28 Jun 2018 17:26:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530231963; bh=ODChy9OKI46Aws59vITB99NqpUpVFEWr5/JCOZezv48=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=tglQ9fvAmMaKXHDnKAPjv4DvfJ1IBG4XzJaON6iLV8diYA/j1QoBRbc9rLDZ+11NC Y1ocfnz8hPd+tZUY1jjtkjhy9YvBmDmcZbYC9QTGtNVuQUYiwNRdgWl+vR7/yNetkM zUrJoAXXqKmU2Duxaf2tLdO5jjEaf45u+v44WkSk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Fix references (#1497) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b357c9b3e1b1_55393fe105dc2f78169fb"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 00:26:06 -0000 ----==_mimepart_5b357c9b3e1b1_55393fe105dc2f78169fb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The transport reference was wrong. The reference to Section 1.3 of RFC 7541 was going to be badly linked in tools. It turns out to be unnecessary at this point anyway. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1497 -- Commit Summary -- * Fix references -- File Changes -- M draft-ietf-quic-qpack.md (24) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1497.patch https://github.com/quicwg/base-drafts/pull/1497.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/1497 ----==_mimepart_5b357c9b3e1b1_55393fe105dc2f78169fb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The transport reference was wrong.

The reference to Section 1.3 of RFC 7541 was going to be badly linked in tools. It turns out to be unnecessary at this point anyway.

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

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

Commit Summary

  • Fix references

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 mute the thread.

----==_mimepart_5b357c9b3e1b1_55393fe105dc2f78169fb-- From nobody Thu Jun 28 17:26:59 2018 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 B79A8130E37 for ; Thu, 28 Jun 2018 17:26:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 yvzx7oIolQHR for ; Thu, 28 Jun 2018 17:26:56 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 5F9D2130DEF for ; Thu, 28 Jun 2018 17:26:56 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530232015; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=WIuEZja4H1ZzpO26w8pOBm8gufJJDak3/5lp+AipUQk=; b=ntfznMxSxCC3zHIzFXomEP87RF0ZIyWuNlRqgkjLpvNqL8caz3fNJumdPVDaWHkAFb4L8aT8 iaPicQ/kd5E/D/+tjwrKYaQlZRBj5Lb7Qd52ttrznI8UAen2h43zxCtO+/7zAeVWZcU5IItC F5p3EMnWWK5eZuUAJjUA+mSlUgE= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.37]) by mxa.mailgun.org with ESMTP id 5b357ccf.7fc8b9d4b630-smtp-out-n03; Fri, 29 Jun 2018 00:26:55 -0000 (UTC) Date: Thu, 28 Jun 2018 17:26:54 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b357cce31d99_65602ad156607c0872831@hookshot-fe-2cc8887.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 69f364: Remove HTAB Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b357cce3177a_65602ad156607c087273d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 00:26:59 -0000 ----==_mimepart_5b357cce3177a_65602ad156607c087273d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: 69f364940b67f61f52def13a4dca4ad937fdeb65 https://github.com/quicwg/base-drafts/commit/69f364940b67f61f52def13a4dca4ad937fdeb65 Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Remove HTAB **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b357cce3177a_65602ad156607c087273d-- From nobody Thu Jun 28 17:28:38 2018 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 42071131120 for ; Thu, 28 Jun 2018 17:28:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.66 X-Spam-Level: X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 qpWcZEoiJbDZ for ; Thu, 28 Jun 2018 17:28:14 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 DD957131131 for ; Thu, 28 Jun 2018 17:28:13 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530232093; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=kiWB54PHnitefACeBLCzrpGPDAHpa5J+hsLZydAZMss=; b=Jn/QyZqnSEksKH1Os5wzqtpRJPUg7eKrkDgnKw42cTnNuMT6607Rtvkg1HW7c5ukkGGinkZC E/N7U+eeO8Q4Z83gGclCynieq+RD7hGplA7dB1CVXqyPcZBTipe4CCylbTt5/TF3GzSEdpje YAQqlfrnbKo2hviU7C6leQ/rrw8= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: mnot=mnot.net@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b357d1c.7f9bb2eecf90-smtp-out-n03; Fri, 29 Jun 2018 00:28:12 -0000 (UTC) Date: Thu, 28 Jun 2018 17:28:12 -0700 From: Mark Nottingham Reply-To: Mark Nottingham To: quic-issues@ietf.org Message-ID: <5b357d1cd19b9_232b2b21af161c0484b1@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/wg-materials] 1ea51e: add cid liveness Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b357d1cd15ac_232b2b21af161c0483dd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 00:28:29 -0000 ----==_mimepart_5b357d1cd15ac_232b2b21af161c0483dd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/wg-materials Commit: 1ea51ee42dceeef1ee031e49351fd11f28d6a996 https://github.com/quicwg/wg-materials/commit/1ea51ee42dceeef1ee031e49351fd11f28d6a996 Author: Mark Nottingham Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M ietf102/agenda.md Log Message: ----------- add cid liveness **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b357d1cd15ac_232b2b21af161c0483dd-- From nobody Thu Jun 28 17:37:51 2018 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 51ED8130E40 for ; Thu, 28 Jun 2018 17:37:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 DVzG7r40ZRre for ; Thu, 28 Jun 2018 17:37:47 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 BBEF4130DEF for ; Thu, 28 Jun 2018 17:37:47 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530232667; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=UTSZrchGaXmz1AxCXbrO80or+cqwwnV5SX4+YbDVOPM=; b=hqpCOv8o7fCkljLBg66tU12BIDO9XSUqID957Fvzgl+nI+koIxtghpX+cLr+x40A9kBCMWms M9nJjA0+84HgknVvBWNjJQF3gLOuOa+sJL90oP366DreaZ99UyEEeXYO0rdtWZ5yATXtfuQb J4M698gJR6D/OhWw3LaO2G7CySw= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.38]) by mxa.mailgun.org with ESMTP id 5b357f5b.7f3857c23f00-smtp-out-n02; Fri, 29 Jun 2018 00:37:47 -0000 (UTC) Date: Thu, 28 Jun 2018 17:37:46 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b357f5a2265a_1bb92ae4d43e3bfc315d3@hookshot-fe-265448d.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b37554: Rework Retry packet Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b357f5a21f76_1bb92ae4d43e3bfc31446"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 00:37:50 -0000 ----==_mimepart_5b357f5a21f76_1bb92ae4d43e3bfc31446 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/move-retry Home: https://github.com/quicwg/base-drafts Commit: b3755446d985d542105628c0a6509328976e89da https://github.com/quicwg/base-drafts/commit/b3755446d985d542105628c0a6509328976e89da Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Rework Retry packet This includes several changes: * I moved the Retry packet description. It is more like Version Negotiation than Handshake or Initial, so it made sense to move it up. * Retry doesn't include a packet number or payload. Like Version Negotiation, it includes a complete definition. * As discussed in #1451, this requires a server that might send another Retry to provide a connection ID of at least 8 octets. * I clarified the description of fields, expanded the pictures, and made some other editorial tweaks. Open Question: would it make sense to normalize the encoding of Retry and Initial? The former includes a token without a length (because it's the last piece of the packet), whereas the latter includes a length-prefixed token. It might be easier to invert the ODCID and token on Retry. That would make the token processing more consistent. I'm not sure if we want to consider adding a token to 0-RTT and Handshake packets, but that would fully normalize things. Closes #1492, #1451. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b357f5a21f76_1bb92ae4d43e3bfc31446-- From nobody Thu Jun 28 17:40:27 2018 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 4D9C8130E3E for ; Thu, 28 Jun 2018 17:40:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 mHuT4CqDcWiP for ; Thu, 28 Jun 2018 17:40:23 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237B4130DEF for ; Thu, 28 Jun 2018 17:40:23 -0700 (PDT) Date: Thu, 28 Jun 2018 17:40:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530232822; bh=qBufpV9Mgn0vfNQ7Du9gqE+Hyn1v5kYfxkAHhJ9rgxc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=QYkKabEp2bxCpqZJ6oQCZqnykBuJaVQLSGjf7vUtUpBbrKttZnhSWlffc0FvSveoh gWWZlO3XsECQQkucV5maBlZT9021k/AdNzSahoWozEmt3pJr5THCZ4rrIiU//LtV+q iplSN4NCqoedUItyezp6gnt04+l10iPSK8zXFeSg= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b357ff629395_7c372aee865acf54708a8"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 00:40:26 -0000 ----==_mimepart_5b357ff629395_7c372aee865acf54708a8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This includes several changes: * I moved the Retry packet description. It is more like Version Negotiation than Handshake or Initial, so it made sense to move it up. * Retry doesn't include a packet number or payload. Like Version Negotiation, it includes a complete definition. * As discussed in #1451, this requires a server that might send another Retry to provide a connection ID of at least 8 octets. * I clarified the description of fields, expanded the pictures, and made some other editorial tweaks. Open Question: would it make sense to normalize the encoding of Retry and Initial? The former includes a token without a length (because it's the last piece of the packet), whereas the latter includes a length-prefixed token. It might be easier to invert the ODCID and token on Retry. That would make the token processing more consistent. I'm not sure if we want to consider adding a token to 0-RTT and Handshake packets, but that would fully normalize things. Other open question (editorial): The variety of long header formats is now a little unwieldy. Should we reduce the long header back to what is in invariants and describe the packet number encoding part as being specific to Initial, Handshake, and 0-RTT? Something for editors to consider. Closes #1492, #1451. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1498 -- Commit Summary -- * Rework Retry packet -- File Changes -- M draft-ietf-quic-transport.md (221) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1498.patch https://github.com/quicwg/base-drafts/pull/1498.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/1498 ----==_mimepart_5b357ff629395_7c372aee865acf54708a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This includes several changes:

  • I moved the Retry packet description. It is more like Version Negotiation than Handshake or Initial, so it made sense to move it up.

  • Retry doesn't include a packet number or payload. Like Version Negotiation, it includes a complete definition.

  • As discussed in #1451, this requires a server that might send another Retry to provide a connection ID of at least 8 octets.

  • I clarified the description of fields, expanded the pictures, and made some other editorial tweaks.

Open Question: would it make sense to normalize the encoding of Retry and Initial? The former includes a token without a length (because it's the last piece of the packet), whereas the latter includes a length-prefixed token. It might be easier to invert the ODCID and token on Retry. That would make the token processing more consistent. I'm not sure if we want to consider adding a token to 0-RTT and Handshake packets, but that would fully normalize things.

Other open question (editorial): The variety of long header formats is now a little unwieldy. Should we reduce the long header back to what is in invariants and describe the packet number encoding part as being specific to Initial, Handshake, and 0-RTT? Something for editors to consider.

Closes #1492, #1451.

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

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

Commit Summary

  • Rework Retry packet

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 mute the thread.

----==_mimepart_5b357ff629395_7c372aee865acf54708a8-- From nobody Thu Jun 28 17:52:24 2018 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 1741C130E40 for ; Thu, 28 Jun 2018 17:52:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 o7VYzc2GvzTs for ; Thu, 28 Jun 2018 17:52:18 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6C3130DEF for ; Thu, 28 Jun 2018 17:52:18 -0700 (PDT) Date: Thu, 28 Jun 2018 17:52:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530233537; bh=nmHVJcHM5UZzY/nkAa5zyGnSBABHvsZmbIAVOqIS98c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BT8l/y19LLbJqZ+BVMBTPIU1BMdbamg2Yi3jmAQeo6TF7/jAjNwB9wRA1wU7z9eqi Riw30gblRme52Rn0gBD5NZVE83VDHgMtkKkaJSUA+gRnynhhZE9EwYk5fYqgeUGa+H zFv6rhxqVdm9Y3dsXikcLhn2r5UcY2Fx11kCyiVo= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3582c1b00a9_50562abb5cbacf60138666"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Fri, 29 Jun 2018 00:52:22 -0000 ----==_mimepart_5b3582c1b00a9_50562abb5cbacf60138666 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr requested changes on this pull request. IIRC, there was some resistance to having a token length, though I can't recall why. > @@ -532,6 +532,82 @@ See {{version-negotiation}} for a description of the version negotiation process. +## Retry Packet {#packet-retry} + +A Retry packet uses long headers with a type value of 0x7E. It carries an The comment suggests that we shouldn't say it uses long headers. > ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +|DCIL(4)|SCIL(4)| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Destination Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Source Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ODCIL(8) | Original Destination Connection ID (*) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Retry Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #retry-format title="Retry Packet"} + +A Retry packet (shown in {{retry-format}}) only uses part of the long packet +header. The contents of the Retry packet are not protected. Like Version I would say "The first X fields of a Retry packet are the same as the long header" > +: An opaque token that the server can use to validate the client's address. + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard the most recent > + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard +the packet. This prevents an off-path attacker from injecting a Retry packet +with a bogus new Source Connection ID. + +The client responds to a Retry packet with Initial packet that includes the +provided Retry Token to continue connection establishment. + +A server that might send another Retry packet in response to a subsequent +Initial packet MUST set the Source Connection ID to new value of at least 8 +octets in length. This allows clients to distinguish between Retry packets when +the server sends multiple rounds of Retry packets. A server that will not send +additional Retry packets can set the Source Connection ID to any value. I think you need to add that a client MUST reject a retry that contains an ODCID of less than 8 bytes. > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Token (*) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Length (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Packet Number (8/16/32) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Payload (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I am assuming these haven't changed. > -If the client has a suitable token available from a previous connection, it -SHOULD populate the Token field. +If the client has an unused token that it received in a NEW_TOKEN frame on a +previous connection to what it believes to be the same server, it includes that +value in the Token field of its Initial packet. This seems oddly non-normative. Also, I notice you have removed "suitable" but if you think you changed your IP then you probably shouldn;t. -- 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/1498#pullrequestreview-133068343 ----==_mimepart_5b3582c1b00a9_50562abb5cbacf60138666 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr requested changes on this pull request.

IIRC, there was some resistance to having a token length, though I can't recall why.

In draft-ietf-quic-transport.md:

> @@ -532,6 +532,82 @@ See {{version-negotiation}} for a description of the version negotiation
 process.
 
 
+## Retry Packet {#packet-retry}
+
+A Retry packet uses long headers with a type value of 0x7E. It carries an

The comment suggests that we shouldn't say it uses long headers.

In draft-ietf-quic-transport.md:

> ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|DCIL(4)|SCIL(4)|
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|               Destination Connection ID (0/32..144)         ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                 Source Connection ID (0/32..144)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|    ODCIL(8)   |      Original Destination Connection ID (*)   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        Retry Token (*)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #retry-format title="Retry Packet"}
+
+A Retry packet (shown in {{retry-format}}) only uses part of the long packet
+header.  The contents of the Retry packet are not protected.  Like Version

I would say "The first X fields of a Retry packet are the same as the long header"

In draft-ietf-quic-transport.md:

> +: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard

the most recent

In draft-ietf-quic-transport.md:

> +
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard
+the packet.  This prevents an off-path attacker from injecting a Retry packet
+with a bogus new Source Connection ID.
+
+The client responds to a Retry packet with Initial packet that includes the
+provided Retry Token to continue connection establishment.
+
+A server that might send another Retry packet in response to a subsequent
+Initial packet MUST set the Source Connection ID to new value of at least 8
+octets in length.  This allows clients to distinguish between Retry packets when
+the server sends multiple rounds of Retry packets.  A server that will not send
+additional Retry packets can set the Source Connection ID to any value.

I think you need to add that a client MUST reject a retry that contains an ODCID of less than 8 bytes.

In draft-ietf-quic-transport.md:

>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                            Token (*)                        ...
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                           Length (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                     Packet Number (8/16/32)                   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                          Payload (*)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

I am assuming these haven't changed.

In draft-ietf-quic-transport.md:

>  
-If the client has a suitable token available from a previous connection, it
-SHOULD populate the Token field.
+If the client has an unused token that it received in a NEW_TOKEN frame on a
+previous connection to what it believes to be the same server, it includes that
+value in the Token field of its Initial packet.

This seems oddly non-normative.

Also, I notice you have removed "suitable" but if you think you changed your IP then you probably shouldn;t.

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

----==_mimepart_5b3582c1b00a9_50562abb5cbacf60138666-- From nobody Thu Jun 28 18:56:57 2018 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 97A53130E2F for ; Thu, 28 Jun 2018 18:56:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 UOfs7ZMeLHBj for ; Thu, 28 Jun 2018 18:56:53 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9CD4120049 for ; Thu, 28 Jun 2018 18:56:52 -0700 (PDT) Date: Thu, 28 Jun 2018 18:56:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530237411; bh=mcgFbnvMmrMrqMGJS6+TlsdjBTUlhSXh0u0VIdzxAzw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RWkDk4EMN/L90eH6+E1cBiXnAOvkPCNQRDYMJqDXVVSXX/PcgsTOMkyEgjuUl+jHg blBTfyjlr7mYb1buwp/U5dIJrlNbGlzcdgjZXgonEkYVTqKJYsiVn3PjTVO6UDWBmn HzZDsKe/dqlB9jczk8581jJh7k8rHFthcYHaL7oo= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3591e37edbd_36522af29f29af6085079"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 29 Jun 2018 01:56:56 -0000 ----==_mimepart_5b3591e37edbd_36522af29f29af6085079 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > Open Question: would it make sense to normalize the encoding of Retry and Initial? The former includes a token without a length (because it's the last piece of the packet), whereas the latter includes a length-prefixed token. It might be easier to invert the ODCID and token on Retry. That would make the token processing more consistent. My preference goes to keeping the current format as-is, because IMO it is better to have fields that identify the connection at the top. Having ODCID above token allows implementations to bail out before dealing with the token, if ODCID does not match the expected value. > I'm not sure if we want to consider adding a token to 0-RTT and Handshake packets, but that would fully normalize things. I think that we should limit the existence of the token field to Initial packets. Having the field in Handshake packet does not make sense at all, because it is sent by the client after the path is validated using the token. Note also that we are trying hard to cram the certificate chain into the Handshake packets that can be sent in the first flight. Having an unnecessary field (even if it is empty) goes against that. Having the field in 0-RTT packet _might_ make some sense, but I oppose, because it allows two ways of implementing buffering of potentially reordered 0-RTT packets on the server side. One way (the only way which is possible now) is to buffer such packets without validating the paths. The other way that will be opened up by having the field is to buffer such packets after validating the paths. This flexibility will incentivize the clients to include token for every 0-RTT packets even though it reduces the space that can be used to carry application data. And that in turn disincentivises the server to buffer potentially reordered 0-RTT packets. To summarize, having a token field in 0-RTT packet will force us to end up in an suboptimal implementation, even though 0-RTT is about optimization. I do not think that we want to see such an outcome. -- 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/1498#issuecomment-401224459 ----==_mimepart_5b3591e37edbd_36522af29f29af6085079 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Open Question: would it make sense to normalize the encoding of Retry = and Initial? The former includes a token without a length (because it's t= he last piece of the packet), whereas the latter includes a length-prefix= ed token. It might be easier to invert the ODCID and token on Retry. That= would make the token processing more consistent.

My preference goes to keeping the current format as-is, because IMO it= is better to have fields that identify the connection at the top. Having= ODCID above token allows implementations to bail out before dealing with= the token, if ODCID does not match the expected value.

I'm not sure if we want to consider adding a token to 0-RTT and Handsh= ake packets, but that would fully normalize things.

I think that we should limit the existence of the token field to Initi= al packets.

Having the field in Handshake packet does not make sense at all, becau= se it is sent by the client after the path is validated using the token. = Note also that we are trying hard to cram the certificate chain into the = Handshake packets that can be sent in the first flight. Having an unneces= sary field (even if it is empty) goes against that.

Having the field in 0-RTT packet might make some sense, but I= oppose, because it allows two ways of implementing buffering of potentia= lly reordered 0-RTT packets on the server side. One way (the only way whi= ch is possible now) is to buffer such packets without validating the path= s. The other way that will be opened up by having the field is to buffer = such packets after validating the paths.

This flexibility will incentivize the clients to include token for eve= ry 0-RTT packets even though it reduces the space that can be used to car= ry application data. And that in turn disincentivises the server to buffe= r potentially reordered 0-RTT packets.

To summarize, having a token field in 0-RTT packet will force us to en= d up in an suboptimal implementation, even though 0-RTT is about optimiza= tion. I do not think that we want to see such an outcome.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, o= r mute the thread.3D""

= ----==_mimepart_5b3591e37edbd_36522af29f29af6085079-- From nobody Thu Jun 28 19:06:05 2018 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 BB0A8130E46 for ; Thu, 28 Jun 2018 19:06:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 E4PPixk586F6 for ; Thu, 28 Jun 2018 19:06:00 -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 88649130E45 for ; Thu, 28 Jun 2018 19:06:00 -0700 (PDT) Date: Thu, 28 Jun 2018 19:05:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530237959; bh=iMWgePI/+KBpDbDm/3+r/9svowsqYDg3MKjIACBf+5U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gL+xNOfqHgwzr/s63qsXtEb+H6WzdBgTddnBqLuVWqGVSvrw/TvVQvptV0ImyRilH I+OlIvj+Kr1Ci3Rgj+b28HyeddEwbUl/Q34WrmeMiQdxuLGGqyUpXQYntjSs8iAy7u apwzVSNDLocVjldKm7eFUtP+VoO2DqVut4NcmQ0w= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3594077ec31_40883f9215142f8089140"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 02:06:04 -0000 ----==_mimepart_5b3594077ec31_40883f9215142f8089140 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. Generally looks good. Just a few comments. > + +Retry Token: + +: An opaque token that the server can use to validate the client's address. + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. Could a server not send a Retry in response to a 0-RTT packet? Say the Initial was lost/reordered, and the 0-RTT arrived first. > + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard +the packet. This prevents an off-path attacker from injecting a Retry packet +with a bogus new Source Connection ID. + +The client responds to a Retry packet with Initial packet that includes the +provided Retry Token to continue connection establishment. + +A server that might send another Retry packet in response to a subsequent +Initial packet MUST set the Source Connection ID to new value of at least 8 Two things. One, if multiple in-path devices send a Retry, how do other devices later in the path know they are sending 'another Retry packet'? Two, why 8 bytes? Why not 4 or 6 or any other number for that matter? Why not just specify that a CID (of any length) must be sent in response? -- 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/1498#pullrequestreview-133076842 ----==_mimepart_5b3594077ec31_40883f9215142f8089140 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

Generally looks good. Just a few comments.

In draft-ietf-quic-transport.md:

> +
+Retry Token:
+
+: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.

Could a server not send a Retry in response to a 0-RTT packet? Say the Initial was lost/reordered, and the 0-RTT arrived first.

In draft-ietf-quic-transport.md:

> +
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard
+the packet.  This prevents an off-path attacker from injecting a Retry packet
+with a bogus new Source Connection ID.
+
+The client responds to a Retry packet with Initial packet that includes the
+provided Retry Token to continue connection establishment.
+
+A server that might send another Retry packet in response to a subsequent
+Initial packet MUST set the Source Connection ID to new value of at least 8

Two things. One, if multiple in-path devices send a Retry, how do other devices later in the path know they are sending 'another Retry packet'? Two, why 8 bytes? Why not 4 or 6 or any other number for that matter? Why not just specify that a CID (of any length) must be sent in response?

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

----==_mimepart_5b3594077ec31_40883f9215142f8089140-- From nobody Thu Jun 28 19:09:30 2018 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 B8CEB130E4B for ; Thu, 28 Jun 2018 19:09:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 JISJ9GtEFf2X for ; Thu, 28 Jun 2018 19:09:25 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3AEF130E46 for ; Thu, 28 Jun 2018 19:09:25 -0700 (PDT) Date: Thu, 28 Jun 2018 19:09:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530238165; bh=0v4ipG/8PTucvWucNlJdA3LAv/V+ytPeb6F5bveSi3c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jdFMB5duNtu37A3IpIx5L3o7OYl249ztwzjh1H8KRnpQ9kc3aSIwpxoFIFf8QAanx lWtwuVSdDwhj+fBCYv6y2N+8tjKdpEt3sPtTjfxrUii9th0iFWo1JI4feY3hyEuHtO OFrVUvhHmDgarDZgiZh9cC2wmdTs/rQtN3Sk1y/E= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3594d4ef3b2_15fc3fce06a9ef84918db"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Fri, 29 Jun 2018 02:09:29 -0000 ----==_mimepart_5b3594d4ef3b2_15fc3fce06a9ef84918db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @MikeBishop > Possible solution: We might need to have the side forgetting CIDs explicitly inform the peer that it will no longer use or accept CIDs older than a certain cutoff. You have to remember old CIDs you've issued until this frame is acknowledged; upon receipt of this frame, you no longer consider the stateless reset tokens valid. FWIW, an alternative approach will be to let each endpoint declare the maximum number of spare CIDs that the endpoint is going to keep. An endpoint can request new connection IDs when the number of spares goes below the threshold that has been advertised by the peer, either by sending a `REQUEST_CONNECTION_ID` frame (which is proposed in #1496) or defining offering of CID as a reciprocal action (i.e. a client who wants more CID requests that by sending a new connection ID to the server; IIRC @martinthomson suggested that approach somewhere). -- 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/1495#issuecomment-401226177 ----==_mimepart_5b3594d4ef3b2_15fc3fce06a9ef84918db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

@MikeBishop

Possible solution: We might need to have the side forgetting CIDs expl= icitly inform the peer that it will no longer use or accept CIDs older th= an a certain cutoff. You have to remember old CIDs you've issued until th= is frame is acknowledged; upon receipt of this frame, you no longer consi= der the stateless reset tokens valid.

FWIW, an alternative approach will be to let each endpoint declare the= maximum number of spare CIDs that the endpoint is going to keep.

An endpoint can request new connection IDs when the number of spares g= oes below the threshold that has been advertised by the peer, either by s= ending a REQUEST_CONNECTION_ID frame (which is proposed in <= a class=3D"issue-link js-issue-link" data-error-text=3D"Failed to load is= sue title" data-id=3D"336791523" data-permission-text=3D"Issue title is p= rivate" data-url=3D"https://github.com/quicwg/base-drafts/issues/1496" hr= ef=3D"https://github.com/quicwg/base-drafts/pull/1496">#1496) or defi= ning offering of CID as a reciprocal action (i.e. a client who wants more= CID requests that by sending a new connection ID to the server; IIRC @martinthomson suggested that approac= h somewhere).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3594d4ef3b2_15fc3fce06a9ef84918db-- From nobody Thu Jun 28 19:50:57 2018 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 19216130E40 for ; Thu, 28 Jun 2018 19:50:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 bzfDeAywdUYo for ; Thu, 28 Jun 2018 19:50:53 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22F4B130DD0 for ; Thu, 28 Jun 2018 19:50:53 -0700 (PDT) Date: Thu, 28 Jun 2018 19:50:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530240652; bh=i8lSVmv4N9qyrTSk6nzv/r44zrALb2t7jTcALh+r6FU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=S4XrPqgovbMHXin3PB2tskgs/DAdNOxj25sdUF51ymwjjWb/7ZXUzDUAj2Zt5as4u G1pSrUueRc5WtETH9aKFJG0lpmosHE5czisld3niK9aH3GMJEnKewCIf7rQGfwnMOu AlMATZEyVB4Ab8ZCQX7upxrAAt1dn/gXI2dS+Y50= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b359e8c2664e_7fc02aacd7cd8f5813553"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 02:50:56 -0000 ----==_mimepart_5b359e8c2664e_7fc02aacd7cd8f5813553 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older I don't think older CIDs should be considered unusable. I can imagine a use for this to retire a CID that you used to try to probe a path that didn't work. In that case, you might still be using the older CID for your main path, and you just want to throw away the new one. -- 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/1496#pullrequestreview-133083900 ----==_mimepart_5b359e8c2664e_7fc02aacd7cd8f5813553 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

I don't think older CIDs should be considered unusable. I can imagine a use for this to retire a CID that you used to try to probe a path that didn't work. In that case, you might still be using the older CID for your main path, and you just want to throw away the new one.

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

----==_mimepart_5b359e8c2664e_7fc02aacd7cd8f5813553-- From nobody Thu Jun 28 22:14:22 2018 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 D7F7C130E24 for ; Thu, 28 Jun 2018 22:14:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 io1HWgWKaV-c for ; Thu, 28 Jun 2018 22:14:19 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E19312785F for ; Thu, 28 Jun 2018 22:14:19 -0700 (PDT) Date: Thu, 28 Jun 2018 22:14:18 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530249258; bh=Bea000hi2vnUWohSvJhxTV3QrmDBS8r/XR7Gwl+t1Fg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aruAFW9SHNXgAmkqq7gjwp6qY/sUEKuqB7AED7E27am6q3uBySGsg+8hheUHGAvAN N71LaWUHvG3K0RGrDOto5AIVpL2xXW+Msdc1g0FDR6TB8EBAlT5TOGSOvQ6Qlh8jME slxxPVIF3dZ+BDG3gHgD9VobcMrt+CcdIa6lsaYw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35c02a34661_e703fb46c51af802851f7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 05:14:21 -0000 ----==_mimepart_5b35c02a34661_e703fb46c51af802851f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit FWIW, I agree with @kazuho's rationale. Thanks for the careful analysis there. I wanted to make sure that the question was asked and hadn't thought it through that fully. -- 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/1498#issuecomment-401249606 ----==_mimepart_5b35c02a34661_e703fb46c51af802851f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

FWIW, I agree with @kazuho's rationale. Thanks for the careful analysis there. I wanted to make sure that the question was asked and hadn't thought it through that fully.

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

----==_mimepart_5b35c02a34661_e703fb46c51af802851f7-- From nobody Thu Jun 28 22:15:51 2018 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 E444A130E55 for ; Thu, 28 Jun 2018 22:15:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 AtzKWEkwopes for ; Thu, 28 Jun 2018 22:15:48 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A03A129C6A for ; Thu, 28 Jun 2018 22:15:48 -0700 (PDT) Date: Thu, 28 Jun 2018 22:15:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530249347; bh=pJmjExWo3e4CqhoxZMlqItjFmbf4UeVmtnBAIXkyhuA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EwBAsCXaMsqhjEXwEVxwBvgvpkHOpzzjDNhUyTywWgmKoE6TWfZQEyTkjAzek2B1x 6J8aI9yo+jRwuMj9+Y+8i7khUiZTJ7Gl5h2NKnUrOcM6eCcV6MaQn2xzmDPZIZafs5 SNyvhC9QDfRZXDl957qr5c7wjGDj/DsiOEnK9dSs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35c083b45aa_c6323fe907a98f781324e6"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 05:15:50 -0000 ----==_mimepart_5b35c083b45aa_c6323fe907a98f781324e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > + +Retry Token: + +: An opaque token that the server can use to validate the client's address. + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. I don't think so. The server cannot decrypt 0-RTT, so it's only option is to 1. buffer it in the hopes that it might complete the handshake when it is done, or 2. discard it, which seems the most likely choice if the server is predisposed to send a Retry. -- 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/1498#discussion_r199054856 ----==_mimepart_5b35c083b45aa_c6323fe907a98f781324e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+Retry Token:
+
+: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.

I don't think so. The server cannot decrypt 0-RTT, so it's only option is to

  1. buffer it in the hopes that it might complete the handshake when it is done, or

  2. discard it, which seems the most likely choice if the server is predisposed to send a Retry.

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

----==_mimepart_5b35c083b45aa_c6323fe907a98f781324e6-- From nobody Thu Jun 28 22:19:25 2018 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 EAE60130E55 for ; Thu, 28 Jun 2018 22:19:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DdFh4MIhOgOU for ; Thu, 28 Jun 2018 22:19:21 -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 E996A129C6A for ; Thu, 28 Jun 2018 22:19:20 -0700 (PDT) Date: Thu, 28 Jun 2018 22:19:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530249560; bh=GpdBCqCJXO6uxI4GwcCJg3E2e9pOkESVcyyDwrYgcko=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oyXQ/0dK6dxgYprnmAKi8FuiUB1/vQ1vXH8oH7viFJvJ3zwFIFLZzTdCUZPNp6Qr5 m/W6wDjB+EATQSuCxVSZuGL8s9BPbIWiVycwg+GeB188U0UI37C5KmWUO09DILuewf UttE5D4ehg10hNf+TnMt+Zh3QV7Docs6Vz58PeBw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35c1581e8f8_47ce3ff384d4af784533e7"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 05:19:24 -0000 ----==_mimepart_5b35c1581e8f8_47ce3ff384d4af784533e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard +the packet. This prevents an off-path attacker from injecting a Retry packet +with a bogus new Source Connection ID. + +The client responds to a Retry packet with Initial packet that includes the +provided Retry Token to continue connection establishment. + +A server that might send another Retry packet in response to a subsequent +Initial packet MUST set the Source Connection ID to new value of at least 8 If things on the path aren't planning to terminate the connection (presumably they know this), then they can never send a token with <8. 8 is the number we picked for Initial. It seemed best to align with that. That's all. It's probably the case that 4 would give us equivalent defense against off-path attacks to the TCP handshake, but there is value in consistency here. -- 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/1498#discussion_r199055162 ----==_mimepart_5b35c1581e8f8_47ce3ff384d4af784533e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard
+the packet.  This prevents an off-path attacker from injecting a Retry packet
+with a bogus new Source Connection ID.
+
+The client responds to a Retry packet with Initial packet that includes the
+provided Retry Token to continue connection establishment.
+
+A server that might send another Retry packet in response to a subsequent
+Initial packet MUST set the Source Connection ID to new value of at least 8

If things on the path aren't planning to terminate the connection (presumably they know this), then they can never send a token with <8.

8 is the number we picked for Initial. It seemed best to align with that. That's all. It's probably the case that 4 would give us equivalent defense against off-path attacks to the TCP handshake, but there is value in consistency here.

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

----==_mimepart_5b35c1581e8f8_47ce3ff384d4af784533e7-- From nobody Thu Jun 28 22:22:00 2018 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 4C9DD130E61 for ; Thu, 28 Jun 2018 22:21:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vZzSIpUlvdKC for ; Thu, 28 Jun 2018 22:21:56 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89FD129C6A for ; Thu, 28 Jun 2018 22:21:56 -0700 (PDT) Date: Thu, 28 Jun 2018 22:21:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530249715; bh=MRsQ7sTvq6trRgSuo32t3W18Fbh/Xo/ntmOCME89sfI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TM+6BGrUAHlq2RQtZV9/nimCHKuS118nI/j7bTyAwuTWtTvDCanq7qiv5vBgPN7kA EaCYUTfZZbOHVk6+/eoAN8d9rIAGDO3dsfG8noWK+kga6BQMlSXAF7gEA8V2JpNyre NE253ENQaC4+0H6ccXDhk2AuH1UORaGe4TxwbdX8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35c1f3c4ba5_56482b0fba38ef60254580"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 05:21:59 -0000 ----==_mimepart_5b35c1f3c4ba5_56482b0fba38ef60254580 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit martinthomson commented on this pull request. > -If the client has a suitable token available from a previous connection, it -SHOULD populate the Token field. +If the client has an unused token that it received in a NEW_TOKEN frame on a +previous connection to what it believes to be the same server, it includes that +value in the Token field of its Initial packet. The point is that it can't really be normative. You can't say MUST for sure, and frankly the whole normative thing is not valuable here: there is no interoperability end served by including a token. "suitable" wasn't defined, but I think that it just highlighted a deficiency, so I've add text on linkability. -- 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/1498#discussion_r199055423 ----==_mimepart_5b35c1f3c4ba5_56482b0fba38ef60254580 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-If the client has a suitable token available from a previous connection, it
-SHOULD populate the Token field.
+If the client has an unused token that it received in a NEW_TOKEN frame on a
+previous connection to what it believes to be the same server, it includes that
+value in the Token field of its Initial packet.

The point is that it can't really be normative. You can't say MUST for sure, and frankly the whole normative thing is not valuable here: there is no interoperability end served by including a token.

"suitable" wasn't defined, but I think that it just highlighted a deficiency, so I've add text on linkability.

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

----==_mimepart_5b35c1f3c4ba5_56482b0fba38ef60254580-- From nobody Thu Jun 28 22:22:31 2018 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 39E68130E63 for ; Thu, 28 Jun 2018 22:22:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 RGC8vWP-_Qd9 for ; Thu, 28 Jun 2018 22:22:28 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 2EE1E129C6A for ; Thu, 28 Jun 2018 22:22:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530249747; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=1RJwhZ1I0V/K8rFr8pfy24YFsoDmw0jfGS2vnPr9MMo=; b=A/DhirvnPwUgP+i/uQswmUaRgTr3t06qMzXitJGUR9lMdKLgsh0jPv6rUGIX8GCjBfdtRG9s Vz9wItYKz99Oc5ea3fMwOOIQ8TLsPqxRKQcXWF3zS8t8sQygOswiixVBCi2nlcbBfMiJTrMA 4tGBRYSZDOZqixgIqnuqCY81RsY= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.44]) by mxa.mailgun.org with ESMTP id 5b35c212.7f2b678ee0c0-smtp-out-n03; Fri, 29 Jun 2018 05:22:26 -0000 (UTC) Date: Thu, 28 Jun 2018 22:22:26 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b35c2122ca2_629f2ab6553cdc107366b@hookshot-fe-6e9b612.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] bf3f67: Review comments Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35c21224a9_629f2ab6553cdc1073575"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 05:22:29 -0000 ----==_mimepart_5b35c21224a9_629f2ab6553cdc1073575 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/move-retry Home: https://github.com/quicwg/base-drafts Commit: bf3f67597f3315018d348bfcf638d8fb9379ff0f https://github.com/quicwg/base-drafts/commit/bf3f67597f3315018d348bfcf638d8fb9379ff0f Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Review comments **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35c21224a9_629f2ab6553cdc1073575-- From nobody Thu Jun 28 22:22:37 2018 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 216D9129C6A for ; Thu, 28 Jun 2018 22:22:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 rCsAznt3Ln-a for ; Thu, 28 Jun 2018 22:22:28 -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 BBE19130E55 for ; Thu, 28 Jun 2018 22:22:28 -0700 (PDT) Date: Thu, 28 Jun 2018 22:22:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530249748; bh=OrBv6TiJ5fYaRpZnFHdwWNaHUOrmeibbyXZxV3rTqf8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oWGP1D07DNcK12h3Zgjf+gkWSqXLJtX/t0FpcNVkN3xgWf0VtFBGat//d+aIsrMAL Leaq8ZXMPAclmNZCptaDRX+ulV5Nc4EBlnmcp7SzaW4g3dND99cnr6oh1+fNuwO/im hCAYEMGn3ZBJCl5Pg9nr4tZ2BSjdZDiITWJok0Bk= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35c2145d3a2_1adb3fdea960ef883220b4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinthomson X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 05:22:31 -0000 ----==_mimepart_5b35c2145d3a2_1adb3fdea960ef883220b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @martinthomson pushed 1 commit. bf3f675 Review comments -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1498/files/b3755446d985d542105628c0a6509328976e89da..bf3f67597f3315018d348bfcf638d8fb9379ff0f ----==_mimepart_5b35c2145d3a2_1adb3fdea960ef883220b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@martinthomson pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b35c2145d3a2_1adb3fdea960ef883220b4-- From nobody Thu Jun 28 23:12:11 2018 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 61D0A130E36 for ; Thu, 28 Jun 2018 23:12:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 54Il63SCsJZo for ; Thu, 28 Jun 2018 23:12:06 -0700 (PDT) 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 E4F53130DC4 for ; Thu, 28 Jun 2018 23:12:05 -0700 (PDT) Date: Thu, 28 Jun 2018 23:12:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530252724; bh=tODknbJ93EChZnzU0qOpjfEZxtwO/qX440FcOQUNxFE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ch65jjEG9I1KKXFfamwxUnMgFRExw6MkVp+zsyK1NJGFPpEicIDU3h8Zh5XhuDtYU zwSdlVAPCmFK9OuDjO8eisNWOLfXh72Dt2ZHtsi89Ut1L0T7vY9Bvsxb2dQtMaNLV1 0ZgwVMWv95LhT/Zvp+nM63n3YAh3GiwQCGCFZQlU= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35cdb4e42c1_7aed2b0f4b7b6f5815503b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 29 Jun 2018 06:12:09 -0000 ----==_mimepart_5b35cdb4e42c1_7aed2b0f4b7b6f5815503b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A limit was also what I was trying to suggest in the above. But a limit must somehow be sensitive to the rate of migrations - or future multi-path. -- 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/1495#issuecomment-401257925 ----==_mimepart_5b35cdb4e42c1_7aed2b0f4b7b6f5815503b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

A limit was also what I was trying to suggest in the above. But a limit must somehow be sensitive to the rate of migrations - or future multi-path.

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

----==_mimepart_5b35cdb4e42c1_7aed2b0f4b7b6f5815503b-- From nobody Thu Jun 28 23:41:29 2018 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 F3483130E06 for ; Thu, 28 Jun 2018 23:41:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 rZsRAMqdzFoF for ; Thu, 28 Jun 2018 23:41:25 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 88BB5130DC4 for ; Thu, 28 Jun 2018 23:41:25 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530254484; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Y/1JK5L/lDfyEGkGv9XcxkGxk7v6fEiHLIYRBKg1nKE=; b=JzLP/eyIarH9oTQhW8W5gdYx5vH3PJFqY8+hAjzdlY/UvU/m39OHEdsZHzUCVl6vgDvsEGMG 1lG//mp6QpTfOwSM5b5yhxPl0vfzoGFYC7n4thDNEbi9xPqHLq6XnXsfIMc+erFd3lb+X/zB GUBCH3D84dWM0WbJdHtPj052sF8= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b35d494.7f3d7b0468a0-smtp-out-n01; Fri, 29 Jun 2018 06:41:24 -0000 (UTC) Date: Thu, 28 Jun 2018 23:41:24 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b35d4941e26b_1fc92ad7168f1c1438157@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b5a7ad: Correct a contradiction Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35d4941dd57_1fc92ad7168f1c1438044"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 06:41:28 -0000 ----==_mimepart_5b35d4941dd57_1fc92ad7168f1c1438044 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/invariant-vn-any-endpoint Home: https://github.com/quicwg/base-drafts Commit: b5a7adc11ede00f07b4254b71e7d616b12b07dbe https://github.com/quicwg/base-drafts/commit/b5a7adc11ede00f07b4254b71e7d616b12b07dbe Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Correct a contradiction **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35d4941dd57_1fc92ad7168f1c1438044-- From nobody Thu Jun 28 23:41:59 2018 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 9A57D130E06 for ; Thu, 28 Jun 2018 23:41:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 h8D0uRZT6kVB for ; Thu, 28 Jun 2018 23:41:56 -0700 (PDT) Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (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 49D1E130DC4 for ; Thu, 28 Jun 2018 23:41:56 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530254515; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=vV0fTosBzX7WGjqhfXvB2cO6HZ2Ll0LoemowQWYInbM=; b=bNy/sl0T2YiYy86D6LoSIsi2yQyRIOQZATqc4QhKVyGgK955KrRANHDU5KLTlbz9EtPDY3J7 FRg1e/Dn6ihqY/pKzEQMyIIpBAvbirehBi/RLwAT7HVOcb3xKJIw/B5KOhBuwH+FtMPIwHLa u2UfyVQj5jM3z/4UucXPg5IFa0o= X-Mailgun-Sending-Ip: 166.78.71.131 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.36]) by mxa.mailgun.org with ESMTP id 5b35d4b3.7feafed90ab0-smtp-out-n01; Fri, 29 Jun 2018 06:41:55 -0000 (UTC) Date: Thu, 28 Jun 2018 23:41:55 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b35d4b363539_73f42b1fc4f95c18938c5@hookshot-fe-6b2eebc.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] cf9d80: Correct a contradiction Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35d4b362c8d_73f42b1fc4f95c18937cb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 06:41:58 -0000 ----==_mimepart_5b35d4b362c8d_73f42b1fc4f95c18937cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/invariant-vn-any-endpoint Home: https://github.com/quicwg/base-drafts Commit: cf9d80e152ee805dc6a5b52c12a98cfa335eca68 https://github.com/quicwg/base-drafts/commit/cf9d80e152ee805dc6a5b52c12a98cfa335eca68 Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Correct a contradiction **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35d4b362c8d_73f42b1fc4f95c18937cb-- From nobody Thu Jun 28 23:42:46 2018 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 6D7E5130EEE for ; Thu, 28 Jun 2018 23:42:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Cf6-_HYBqRn2 for ; Thu, 28 Jun 2018 23:42:33 -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 D9BA7130E70 for ; Thu, 28 Jun 2018 23:42:32 -0700 (PDT) Date: Thu, 28 Jun 2018 23:42:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530254551; bh=NAiyq00MG3VHpa+gnX3N0xItNdud0aWS6KRgIOGlRRM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=z4ACMZhfpGuV4Ewqa6qBj/Je1bikM7Xqj4PeZQn0EZ0Lf5G0fGWmXvnoIQ40+EGBy Pf8j5vlfy5KJaLMFHEeTKQD74wMZiAvq0iC3Cp6X9l3SmBE+mD1fsPsWbuE4jEWo3Y 9UThwhnORTiXxbQn4kpm92MFSVdCPZ/OMpRCkNoo= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Correct a contradiction (#1499) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35d4d7caf00_68243fca10306f784595a"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 06:42:45 -0000 ----==_mimepart_5b35d4d7caf00_68243fca10306f784595a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The text says "server", but the appendix says that either endpoint might send VN. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1499 -- Commit Summary -- * Correct a contradiction -- File Changes -- M draft-ietf-quic-invariants.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1499.patch https://github.com/quicwg/base-drafts/pull/1499.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/1499 ----==_mimepart_5b35d4d7caf00_68243fca10306f784595a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The text says "server", but the appendix says that either endpoint might send VN.

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

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

Commit Summary

  • Correct a contradiction

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 mute the thread.

----==_mimepart_5b35d4d7caf00_68243fca10306f784595a-- From nobody Thu Jun 28 23:43:38 2018 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 4BD64130E06 for ; Thu, 28 Jun 2018 23:43:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 vp3mx6XYGODm for ; Thu, 28 Jun 2018 23:43:34 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 35772130DE5 for ; Thu, 28 Jun 2018 23:43:34 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530254613; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=rdXW8+gosYOfDbOv4RP5sUP98uGIbU5uHweIv2+6FR4=; b=V78MgnnrvKgp4dnIgGk02RVKgDZlIlmjZx02Vnt43y+mibrWe7rPJ9eSwEco/+DSrgIh9pUb l47/s2cfPLVm+G9REELx6AwTftcDufB7FRdYfK1C1CwsH25TeufxEpxkx89DnxtTC3q+y1uu 9cXaUjyZhYc+EHzwghYD+uHj450= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.39]) by mxa.mailgun.org with ESMTP id 5b35d514.7f919ca6a840-smtp-out-n03; Fri, 29 Jun 2018 06:43:32 -0000 (UTC) Date: Thu, 28 Jun 2018 23:43:31 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b35d513c1c3b_36282acd75b85c1459534@hookshot-fe-da92815.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 700ba1: Comment about notational conventions Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35d513c1825_36282acd75b85c145940"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 06:43:37 -0000 ----==_mimepart_5b35d513c1825_36282acd75b85c145940 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/invariants-convenstions Home: https://github.com/quicwg/base-drafts Commit: 700ba1c0de47465034676e40a58ced71c8694428 https://github.com/quicwg/base-drafts/commit/700ba1c0de47465034676e40a58ced71c8694428 Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-invariants.md Log Message: ----------- Comment about notational conventions **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35d513c1825_36282acd75b85c145940-- From nobody Thu Jun 28 23:44:12 2018 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 BCE21130E06 for ; Thu, 28 Jun 2018 23:44:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 hADE096dO0ob for ; Thu, 28 Jun 2018 23:44:09 -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 E62AF130DE5 for ; Thu, 28 Jun 2018 23:44:08 -0700 (PDT) Date: Thu, 28 Jun 2018 23:44:08 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530254648; bh=3tqwznjyTZUgOVjiQuqdyJpdgirKQu4krxYsH54jNmA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XX/bl+lZcGemGoDP3WneyqkuJor87O6ZZmwFPL/xZEZYS/74a64G/lCtbtqeKt29J Bb5pAcFHytFMa35gSwNeB4VlEeLMm3xerjNAsL8ZTe1PwCtg/6aide5TbtT/JiLKDb YvBGQjr9VmgMO+FMwZeP/1rlhAE1DzSuTIzeZNz8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Comment about notational conventions (#1500) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35d5382070e_64703fd0c6b76f849117"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 06:44:11 -0000 ----==_mimepart_5b35d5382070e_64703fd0c6b76f849117 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Someone commented that we don't really explain what (i) means in diagrams, for instance. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1500 -- Commit Summary -- * Comment about notational conventions -- File Changes -- M draft-ietf-quic-invariants.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1500.patch https://github.com/quicwg/base-drafts/pull/1500.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/1500 ----==_mimepart_5b35d5382070e_64703fd0c6b76f849117 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Someone commented that we don't really explain what (i) means in diagrams, for instance.

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

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

Commit Summary

  • Comment about notational conventions

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 mute the thread.

----==_mimepart_5b35d5382070e_64703fd0c6b76f849117-- From nobody Fri Jun 29 00:03:06 2018 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 6FD1D130E06 for ; Fri, 29 Jun 2018 00:03:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 FgxY6-3Wx870 for ; Fri, 29 Jun 2018 00:03:01 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC353130DE5 for ; Fri, 29 Jun 2018 00:03:01 -0700 (PDT) Date: Fri, 29 Jun 2018 00:03:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530255780; bh=EGAgGgNtLlXoBuJ17Be2Xn0r7AiEO3fxD4eYcdoWjTo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZXaqOMJYF9eI2rJTz07Nx87jjrGhHAObkQkd0lczR3/CcjGcKuXsedW4+E/yAROlz Y6/KfFlvKfbOBnzR4mXcxpwpJ/yeHDDBtwTi8bPgRRhkNEMIc0c6gJ2Wbz9FBGTd0e WfqmAackcG4Xg2ZCpwZUOBvfhIdM6tmngCpXJLhI= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Border cases in packet number decoding (#674) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35d9a4cf782_7f982b0492beaf5c7304f"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:03:05 -0000 ----==_mimepart_5b35d9a4cf782_7f982b0492beaf5c7304f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed by #1493. -- 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/674#issuecomment-401266998 ----==_mimepart_5b35d9a4cf782_7f982b0492beaf5c7304f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed by #1493.

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

----==_mimepart_5b35d9a4cf782_7f982b0492beaf5c7304f-- From nobody Fri Jun 29 00:03:14 2018 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 06AC9130DE5 for ; Fri, 29 Jun 2018 00:03:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 1Pfeh3PR8quI for ; Fri, 29 Jun 2018 00:03:01 -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 A4D31128BAC for ; Fri, 29 Jun 2018 00:03:01 -0700 (PDT) Date: Fri, 29 Jun 2018 00:03:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530255780; bh=BUjY9SkhWjSWclGdEfXySHxClV2/KKN9OSTjeDyUrSI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tVi10iPEADdmEUOvm4hmelMoA1fjw7M9rJgU3NJw2NX00GOItwWcH4afvMwVBmMyk QcpqmACQMrdZ14Jc2cHdO+6I6H99OJSWciBooGLFTVXpVwW6dHuu4HZmEDWE6a6Oxv dQInfe+lC0HQo1ZVTKy26l6E28fqiAIKz7jqFdU4= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Border cases in packet number decoding (#674) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35d9a4e3f5e_1bc83f92b6e3cf781243b5"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:03:06 -0000 ----==_mimepart_5b35d9a4e3f5e_1bc83f92b6e3cf781243b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #674. -- 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/674#event-1707977503 ----==_mimepart_5b35d9a4e3f5e_1bc83f92b6e3cf781243b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #674.

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

----==_mimepart_5b35d9a4e3f5e_1bc83f92b6e3cf781243b5-- From nobody Fri Jun 29 00:13:06 2018 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 E2B29130E65 for ; Fri, 29 Jun 2018 00:13:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 JtNRQp2cXP9Z for ; Fri, 29 Jun 2018 00:13:03 -0700 (PDT) Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 93E7C130E10 for ; Fri, 29 Jun 2018 00:13:03 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530256382; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=1wi7YOTlR1txv1qPU4a8rKqxvDQEtVD46ADRgjXkHzo=; b=w1/PM4IaRVeAmxhaaOS/gfyY6eSc9umdE07nyQsP35HoGUGIAj2TyhjaUugHNoFZi3KgbkKO yrACuEGe1OOMM+LJxnDsWjFt5/B7BduWeixaFgoi8dIyvEVIh8g3jLMJ40O3SzdzMV6mABDE MYLkuMkzh0tZFSO4xOxy+EgmHE8= X-Mailgun-Sending-Ip: 166.78.69.169 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: martin.thomson=gmail.com@github.com Received: from github.com (Unknown [192.30.252.34]) by mxa.mailgun.org with ESMTP id 5b35dbfe.7f6e8ff94450-smtp-out-n01; Fri, 29 Jun 2018 07:13:02 -0000 (UTC) Date: Fri, 29 Jun 2018 00:13:01 -0700 From: Martin Thomson Reply-To: Martin Thomson To: quic-issues@ietf.org Message-ID: <5b35dbfdf147b_6ad52b251dd4dc1854889@hookshot-fe-7191cb1.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] 6fb525: Define NAT rebinding better Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b35dbfdf10a8_6ad52b251dd4dc18547bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 07:13:05 -0000 ----==_mimepart_5b35dbfdf10a8_6ad52b251dd4dc18547bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/define-rebinding Home: https://github.com/quicwg/base-drafts Commit: 6fb52501a58cc1ae93f3f7d3815270eab788b07e https://github.com/quicwg/base-drafts/commit/6fb52501a58cc1ae93f3f7d3815270eab788b07e Author: Martin Thomson Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- Define NAT rebinding better The change to add a means of disabling migration also mostly fixed #594, so close that too. Closes #952, #594. **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b35dbfdf10a8_6ad52b251dd4dc18547bf-- From nobody Fri Jun 29 00:13:26 2018 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 C477C130E68 for ; Fri, 29 Jun 2018 00:13:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 pXB3et2YqJMg for ; Fri, 29 Jun 2018 00:13:23 -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 260D4130E10 for ; Fri, 29 Jun 2018 00:13:23 -0700 (PDT) Date: Fri, 29 Jun 2018 00:13:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530256402; bh=XZTUd3uXlQxjJvNEdivBp6ugWNYTF9cv+L2H7RDa+pY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bwtkut/PKgXxSf560gc+giMMu4TTpR+/0pXgqvVLi8pFhaPGE+a739FPPcVe66BSW X34Dhk12xYRXirj4M9MKi5yun9y86LuxTNtnlCL4/ELcu3Q0mygvKs2D6T84ocafVZ FbhHpYTumjQDJi37pDJr4MD3EvNnz4Y+E3UUVlpM= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Define NAT rebinding better (#1501) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35dc122837d_23312b14cce8ef5c9052b"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:13:25 -0000 ----==_mimepart_5b35dc122837d_23312b14cce8ef5c9052b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The change to add a means of disabling migration also mostly fixed #594, so close that too. Closes #952, #594. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1501 -- Commit Summary -- * Define NAT rebinding better -- File Changes -- M draft-ietf-quic-transport.md (23) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1501.patch https://github.com/quicwg/base-drafts/pull/1501.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/1501 ----==_mimepart_5b35dc122837d_23312b14cce8ef5c9052b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The change to add a means of disabling migration also mostly fixed #594,
so close that too.

Closes #952, #594.

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

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

Commit Summary

  • Define NAT rebinding better

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 mute the thread.

----==_mimepart_5b35dc122837d_23312b14cce8ef5c9052b-- From nobody Fri Jun 29 00:23:36 2018 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 CD3ED130E25 for ; Fri, 29 Jun 2018 00:23:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 47TRkCS_fnim for ; Fri, 29 Jun 2018 00:23:32 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84201130E10 for ; Fri, 29 Jun 2018 00:23:32 -0700 (PDT) Date: Fri, 29 Jun 2018 00:23:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530257011; bh=+6yXC0aSeMmXjeXV1ndd+hjjQ+VznoKVZee49f9Ze5c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RVGvBSbH+/LkLVh6MqCBlqod5UMXnqtmyngPbFPXxZCCKZ9zvgEHaMdnRCoMaDKFZ sPz2G1rqcNuyKf7twVqTHQyI+sy8Gb7yYnHDC5kMmygdEvcxLhmjoQo2XzPe0Q9Z+R JbgeVk5BNjZu5Sn0HFgmj89M59FF1tVUKI8dOPXw= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] What if the packet number of a retry packet is not zero? (#1448) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35de73da0eb_69193ffc8783cf841927df"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:23:35 -0000 ----==_mimepart_5b35de73da0eb_69193ffc8783cf841927df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This should go away with #1498 - Retry won't have a packet number. -- 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/1448#issuecomment-401271184 ----==_mimepart_5b35de73da0eb_69193ffc8783cf841927df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This should go away with #1498 - Retry won't have a packet number.

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

----==_mimepart_5b35de73da0eb_69193ffc8783cf841927df-- From nobody Fri Jun 29 00:26:50 2018 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 04E5F130E25 for ; Fri, 29 Jun 2018 00:26:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nsuQQzxJmceX for ; Fri, 29 Jun 2018 00:26:46 -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 4AF45130E10 for ; Fri, 29 Jun 2018 00:26:46 -0700 (PDT) Date: Fri, 29 Jun 2018 00:26:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530257205; bh=ed41MA/SLCRUbtPRFTcP5sa8/deZ2phWrb2Sn72zLMQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GNaXdUt8o0cPdTw9dj3wpB7Rsr+TpU7xJMrnn7jsjXAuTRB+xmFuey98OrwhxbuQl 0uhyv1X8s4SeYgV1lebd53exifCoWhxuCAQRr/HH+7p7feQkiJcqEaQfQt61PtOuPI vmrCjaZqn6EJbd/VSA1bo9l7RKEKESeFQxjtjgr8= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Fragility in ECN counters with lost acks (#1481) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35df356f01b_9ad2ac51046af5092632"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:26:48 -0000 ----==_mimepart_5b35df356f01b_9ad2ac51046af5092632 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Right now the text requires an exact match - the number of markings on newly acknowledged packets need to exactly match the increase in counters. If you forgot a packet (and so don't know if it's newly acknowledged), then add one to the upper limit of the number. If there is a gap between the lowest acknowledged packet number in this ACK and the largest packet number previously acknowledged, increase the upper limit by the same amount. -- 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/1481#issuecomment-401271903 ----==_mimepart_5b35df356f01b_9ad2ac51046af5092632 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Right now the text requires an exact match - the number of markings on= newly acknowledged packets need to exactly match the increase in counter= s. If you forgot a packet (and so don't know if it's newly acknowledged)= , then add one to the upper limit of the number. If there is a gap betwe= en the lowest acknowledged packet number in this ACK and the largest pack= et number previously acknowledged, increase the upper limit by the same a= mount.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b35df356f01b_9ad2ac51046af5092632-- From nobody Fri Jun 29 00:36:24 2018 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 EBCAE130E09 for ; Fri, 29 Jun 2018 00:36:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 CuCShtO-KwMR for ; Fri, 29 Jun 2018 00:36:21 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CCFF127AC2 for ; Fri, 29 Jun 2018 00:36:21 -0700 (PDT) Date: Fri, 29 Jun 2018 00:36:20 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530257780; bh=erBgTFWPEQoTPUL2F91gBjGPppk9r1qBd+ObDaIQt7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pZjKSvw/5W6+hmNU22GQQeLBWtZDfHOrjwq0Wgc0gqrFUOpXBW4nv235t+sLNjrkA cdP07Zo7Q/FeU3in8QZoq0YKqAvu5j5x8n6hTW+vN0CrK38VDinjaDbhpBdWoJFvy8 +Txgtj3SR4ziuyYHXx3kv1S0rMjzdlGBsVWE4nNs= From: Martin Thomson Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35e17427d6c_48872b1fe4d8ef58698a2"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 07:36:23 -0000 ----==_mimepart_5b35e17427d6c_48872b1fe4d8ef58698a2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that I'm with @MikeBishop here. 37 octets is quite a bit bigger than the smallest packet that might be sent, and if there is at least a chance of getting a reset back, then connections will die more quickly, though it might only be in the aggregate. Advising reduced probability when the reset is not smaller than the packet it responds to seems right. If you consider that we want to have resets of varying size, that's probably good, because you don't end up clamping resets to the size of the incoming packet. I'm sure that you can devise a simple scheme that randomizes probability as a function of the increase in packet length over the incoming packet. -- 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/1443#issuecomment-401273965 ----==_mimepart_5b35e17427d6c_48872b1fe4d8ef58698a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I think that I'm with @MikeBishop here. 37 octets is quite a bit bigger than the smallest packet that m= ight be sent, and if there is at least a chance of getting a reset back, = then connections will die more quickly, though it might only be in the ag= gregate. Advising reduced probability when the reset is not smaller than= the packet it responds to seems right.

If you consider that we want to have resets of varying size, that's pr= obably good, because you don't end up clamping resets to the size of the = incoming packet. I'm sure that you can devise a simple scheme that rando= mizes probability as a function of the increase in packet length over the= incoming packet.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b35e17427d6c_48872b1fe4d8ef58698a2-- From nobody Fri Jun 29 01:52:58 2018 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 0FC72130DC2 for ; Fri, 29 Jun 2018 01:52:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vl4FF-FiYEMA for ; Fri, 29 Jun 2018 01:52:54 -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 AD89B12F295 for ; Fri, 29 Jun 2018 01:52:54 -0700 (PDT) Date: Fri, 29 Jun 2018 01:52:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530262373; bh=u3PBvJLtNfV2KHvyAl5NtNH62OMgb7e16f43/cJvCfM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=m0U3P05ZSaqHPS3laKdtUe7Ad5x+/1XTGR/TQwfhiYtBovOCBV4xFk8UuPyQn5ko8 hT6L42hmGphTfzsPx91eSbRUVysaouycu0sllbtjz4igA5AeKYRGA3DZ8IWvwDU3A1 tgV2Eg5NFtNHTD23CCSo6DBW1f5gj6IxPjZFb8aM= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35f365a005d_36393f7f68e48f786310b1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 29 Jun 2018 08:52:58 -0000 ----==_mimepart_5b35f365a005d_36393f7f68e48f786310b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm all for reducing reset size, but it can't stand alone as @martinthomson also summarized. Probability is needed for small packets. -- 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/1443#issuecomment-401292527 ----==_mimepart_5b35f365a005d_36393f7f68e48f786310b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm all for reducing reset size, but it can't stand alone as @martinthomson also summarized. Probability is needed for small packets.

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

----==_mimepart_5b35f365a005d_36393f7f68e48f786310b1-- From nobody Fri Jun 29 02:11:27 2018 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 AA138130DC2 for ; Fri, 29 Jun 2018 02:11:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NBRHsZmIegNa for ; Fri, 29 Jun 2018 02:11:23 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07083128BAC for ; Fri, 29 Jun 2018 02:11:23 -0700 (PDT) Date: Fri, 29 Jun 2018 02:11:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530263481; bh=YRtPXyw+FgGB6pcIIRqPgxtsudqlhMR/2vAaicjcmqo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aIG8wNqAm97+uqmKSXiKwkB4phsJPIAhDFB6v58eyKDURk+zluMvId6dzhJnkp3f1 5ycKaROs5d188WwZ33SrhkWZjlzcrVdkfj/2DgoyYWPSoNDAsYGDIV5TWvQtU4YWpW ydapSdWC0p68i6w+8jg7B8OrIIg2ssNxAxgEv8zA= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35f7b986956_54b03feacfb4af8852113c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 29 Jun 2018 09:11:25 -0000 ----==_mimepart_5b35f7b986956_54b03feacfb4af8852113c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from the most recent the Initial packet it sent, clients MUST +discard the packet. This prevents an off-path attacker from injecting a Retry grammar: Connection ID from the most recent the Initial packet it sent, -- 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/1498#pullrequestreview-133152891 ----==_mimepart_5b35f7b986956_54b03feacfb4af8852113c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from the most recent the Initial packet it sent, clients MUST
+discard the packet.  This prevents an off-path attacker from injecting a Retry

grammar: Connection ID from the most recent the Initial packet it sent,

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

----==_mimepart_5b35f7b986956_54b03feacfb4af8852113c-- From nobody Fri Jun 29 02:25:34 2018 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 74B7A128BAC for ; Fri, 29 Jun 2018 02:25:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8_4RtdhglCKn for ; Fri, 29 Jun 2018 02:25:31 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E814130E2E for ; Fri, 29 Jun 2018 02:25:31 -0700 (PDT) Date: Fri, 29 Jun 2018 02:25:30 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530264330; bh=wpAHgcvuWPJAtS9Fl7KVNHRXlfVLiJa0XEB4FKEcZJE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fEVPoTARwMZ1qom1dFRfeAOMb2XMfSS8qoSiMrwkCgCaXh8sjsg6yRpBh/wSzY3vV TVk66mS7gx5/5IzXOXpsJstJ3RnBfU5aRggKuAci96eJFUyQER7C/yRRO4dwxLQN/Q bEPQX1oWmE8JRfWSut0YAXs3PYurbbYy11b81bP4= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Comment about notational conventions (#1500) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35fb0a17e35_7fd92ace1f9c2f58185f1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 29 Jun 2018 09:25:33 -0000 ----==_mimepart_5b35fb0a17e35_7fd92ace1f9c2f58185f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > @@ -106,6 +106,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", document are to be interpreted as described in BCP 14 {{!RFC2119}} {{!RFC8174}} when, and only when, they appear in all capitals, as shown here. +This document uses terms and notational conventions from {{QUIC-TRANSPORT}}. + Shouldn't it be the other way around? Given that invariants are less likely 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/pull/1500#pullrequestreview-133157297 ----==_mimepart_5b35fb0a17e35_7fd92ace1f9c2f58185f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-invariants.md:

> @@ -106,6 +106,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
 document are to be interpreted as described in BCP 14 {{!RFC2119}} {{!RFC8174}}
 when, and only when, they appear in all capitals, as shown here.
 
+This document uses terms and notational conventions from {{QUIC-TRANSPORT}}.
+

Shouldn't it be the other way around? Given that invariants are less likely to change.

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

----==_mimepart_5b35fb0a17e35_7fd92ace1f9c2f58185f1-- From nobody Fri Jun 29 02:27:32 2018 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 BED78130E09 for ; Fri, 29 Jun 2018 02:27:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 O6tzS9gmcfUA for ; Fri, 29 Jun 2018 02:27:29 -0700 (PDT) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 C9A70128BAC for ; Fri, 29 Jun 2018 02:27:28 -0700 (PDT) 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=L8uOY7fOQvMj9PQ83wX03x0yilE=; b=HIpqTkSbWL3l+VaF dCLgL1eAWJFOgdbLLV0I/mfqKcYaFo3uEaoTf6SE3wEty9EdpvvG1ZfnyF30TI7B K8B1zG3c/rQQbGgoJP0XbKHLTQUjHA0SV2mDO1iZ/h0fAvncI0HVvv1ETYDRykcM S0UvI91yicQ+1hnLXKeA5kiX760= Received: by filter0226p1iad2.sendgrid.net with SMTP id filter0226p1iad2-2626-5B35FB7F-4 2018-06-29 09:27:27.612502003 +0000 UTC Received: from github-lowworker7-cp1-prd.iad.github.net (unknown [192.30.252.47]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id oKxNQlSlRpiKDaR4DB3mYw for ; Fri, 29 Jun 2018 09:27:27.647 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker7-cp1-prd.iad.github.net (Postfix) with ESMTP id 82979A6B5F for ; Fri, 29 Jun 2018 02:27:27 -0700 (PDT) Date: Fri, 29 Jun 2018 09:27:27 +0000 (UTC) From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define NAT rebinding better (#1501) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b35fb7f8115b_612d3f9dd3d5ef8424976f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1f6RkF1xTkg/hn9VW7LXN10H5Li2e0G0stVt Gh124jqTzjLS2Zx6bsAb8pdzIJf80U/G01wQHMdZumXC7BkJXVKX8EuhwhOYZ3876Hfi4l+29UeSVE YEVftOHCtMzycGOq6kq+vqumA4hX3oPThiuTsms4osTZvUD7txvoPwpgZQ== Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 09:27:31 -0000 ----==_mimepart_5b35fb7f8115b_612d3f9dd3d5ef8424976f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > -network MAY treat this as a connection error of type INVALID_MIGRATION. However, -note that not all changes of peer address are intentional migrations. The peer -could experience an unintended change of address due to NAT rebinding; endpoints -SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not -cause the connection to fail. +finished and the endpoint has 1-RTT keys. The design of QUIC relies on +endpoints retaining a stable address for the duration of the handshake. + +An endpoint also MUST NOT initiate connection migration if the peer sent the +`disable_migration` transport parameter during the handshake. An endpoint which +has sent this transport parameter, but detects that a peer has nonetheless +migrated to a different network MAY treat this as a connection error of type +INVALID_MIGRATION. + +Not all changes of peer address are intentional migrations. The peer could +experience NAT rebinding: a change of address due a middlebox, usually a NAT, grammar: due a middlebox -- 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/1501#pullrequestreview-133157946 ----==_mimepart_5b35fb7f8115b_612d3f9dd3d5ef8424976f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

> -network MAY treat this as a connection error of type INVALID_MIGRATION. However,
-note that not all changes of peer address are intentional migrations. The peer
-could experience an unintended change of address due to NAT rebinding; endpoints
-SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not
-cause the connection to fail.
+finished and the endpoint has 1-RTT keys.  The design of QUIC relies on
+endpoints retaining a stable address for the duration of the handshake.
+
+An endpoint also MUST NOT initiate connection migration if the peer sent the
+`disable_migration` transport parameter during the handshake.  An endpoint which
+has sent this transport parameter, but detects that a peer has nonetheless
+migrated to a different network MAY treat this as a connection error of type
+INVALID_MIGRATION.
+
+Not all changes of peer address are intentional migrations. The peer could
+experience NAT rebinding: a change of address due a middlebox, usually a NAT,

grammar: due a middlebox

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

----==_mimepart_5b35fb7f8115b_612d3f9dd3d5ef8424976f-- From nobody Fri Jun 29 06:30:20 2018 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 35B7C130E90 for ; Fri, 29 Jun 2018 06:30:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 Nu7MYR1m-_cr for ; Fri, 29 Jun 2018 06:30:17 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53476130E5B for ; Fri, 29 Jun 2018 06:30:17 -0700 (PDT) Date: Fri, 29 Jun 2018 06:30:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530279016; bh=knJD2/qcumAPK5wfdla98RcaSYdKNB+sB/qvL7ErSN8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eD2b5dRerlrhe/bJyXSW37wqrP3fXyMNbd4TBuzgVDOzbzxVsto6RNQ3IAb1cRUOM JGYH5lphBosoyOtALSNyGZjdmjCJ9CRZb/5v5h1xpiC3TjKsrX9dcZCIIIy0eS0LPS AHKdmDebE66HB6Yk4KSkPTch4zgxnf3JR2xhnRTo= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b363467f3ed3_101f2ae04cd10f5421807d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 13:30:20 -0000 ----==_mimepart_5b363467f3ed3_101f2ae04cd10f5421807d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard +the packet. This prevents an off-path attacker from injecting a Retry packet +with a bogus new Source Connection ID. + +The client responds to a Retry packet with Initial packet that includes the +provided Retry Token to continue connection establishment. + +A server that might send another Retry packet in response to a subsequent +Initial packet MUST set the Source Connection ID to new value of at least 8 They way I read this sentence is that only for additional Retry packets (after the first one) do you need to change the Source CID. But if the server doesn't know that some other middle box (DDoS Mitigation device) has already sent a Retry packet once, then it would likely assume it is the first once to send a Retry packet. Then it might not change the Source CID. -- 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/1498#discussion_r199158920 ----==_mimepart_5b363467f3ed3_101f2ae04cd10f5421807d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard
+the packet.  This prevents an off-path attacker from injecting a Retry packet
+with a bogus new Source Connection ID.
+
+The client responds to a Retry packet with Initial packet that includes the
+provided Retry Token to continue connection establishment.
+
+A server that might send another Retry packet in response to a subsequent
+Initial packet MUST set the Source Connection ID to new value of at least 8

They way I read this sentence is that only for additional Retry packets (after the first one) do you need to change the Source CID. But if the server doesn't know that some other middle box (DDoS Mitigation device) has already sent a Retry packet once, then it would likely assume it is the first once to send a Retry packet. Then it might not change the Source CID.

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

----==_mimepart_5b363467f3ed3_101f2ae04cd10f5421807d-- From nobody Fri Jun 29 06:33:04 2018 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 B7CA6130E98 for ; Fri, 29 Jun 2018 06:33:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 GCV5Mjltafk0 for ; Fri, 29 Jun 2018 06:33:01 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C924D130E5B for ; Fri, 29 Jun 2018 06:33:00 -0700 (PDT) Date: Fri, 29 Jun 2018 06:33:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530279180; bh=jP+Rj1FwItiL/CQcIg97kY/uQtfDCP6T/3xUu40iAjc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xcy+642Rul1pCfMp00nzZS23ZZz/dFx2qYg079MS57sCCj84p3M6eV1PVYqNLuo16 MRsQn3Iel1efpJuh3PynBjZ7dWH+ubZCRZE/v7N08u3oHc4SQlgmIWpoA5qcb6CUOx dd3LmHXib92z9JcC7U9VpBMC2K01StN3+fFLDMT0= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36350bf3f9c_3ca92b15bcabef5828676"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 13:33:03 -0000 ----==_mimepart_5b36350bf3f9c_3ca92b15bcabef5828676 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + +Retry Token: + +: An opaque token that the server can use to validate the client's address. + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. So, for a DDoS mitigation device that just sees a 0-RTT packet (assuming the Initial was lost/reordered) it should just drop it instead of sending a Retry? That works, but I just wonder why not use that extra info to do the Retry immediately. Otherwise, the client will eventually retransmit the Initial, and then have to pay an additional RTT for the retry. -- 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/1498#discussion_r199159742 ----==_mimepart_5b36350bf3f9c_3ca92b15bcabef5828676 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+Retry Token:
+
+: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.

So, for a DDoS mitigation device that just sees a 0-RTT packet (assuming the Initial was lost/reordered) it should just drop it instead of sending a Retry? That works, but I just wonder why not use that extra info to do the Retry immediately. Otherwise, the client will eventually retransmit the Initial, and then have to pay an additional RTT for the retry.

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

----==_mimepart_5b36350bf3f9c_3ca92b15bcabef5828676-- From nobody Fri Jun 29 06:42:41 2018 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 79426130EF5 for ; Fri, 29 Jun 2018 06:42:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 qCSEbXInvePa for ; Fri, 29 Jun 2018 06:42:29 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 639BB130EC0 for ; Fri, 29 Jun 2018 06:42:29 -0700 (PDT) Date: Fri, 29 Jun 2018 06:42:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530279748; bh=VdK/VIG0ReSYHrrCP0UQCqgVzDe3/5Io8q1AegkHxdQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qg7gZq/ysw35IeOLplGemg8LgeD7XKo8GecaVg4iyZ9yPpG/be09lx+cvEW+9ylAc cY8RqLD77hsaBVyBI0Nyw3bXlxZbY7AlW5UYdWI9+F6m8Ruak07O8YSRW9l8CJNCcQ CvsBpYxAGomEmzjyRKokJzh/IK2ZNVTSB14IgXOY= From: MikkelFJ Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3637448546b_19a93fa029688f7c4129a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mikkelfj 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.26 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: Fri, 29 Jun 2018 13:42:41 -0000 ----==_mimepart_5b3637448546b_19a93fa029688f7c4129a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit mikkelfj commented on this pull request. > + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from most recent the Initial packet it sent, clients MUST discard +the packet. This prevents an off-path attacker from injecting a Retry packet +with a bogus new Source Connection ID. + +The client responds to a Retry packet with Initial packet that includes the +provided Retry Token to continue connection establishment. + +A server that might send another Retry packet in response to a subsequent +Initial packet MUST set the Source Connection ID to new value of at least 8 @nibanks the way I read it, the reset is stateless so each source is semi-randomly generated, consequently a second retry will stastically differ from the first. Also across servers. This could be made clearer. -- 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/1498#discussion_r199162469 ----==_mimepart_5b3637448546b_19a93fa029688f7c4129a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@mikkelfj commented on this pull request.

In draft-ietf-quic-transport.md:

> +
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from most recent the Initial packet it sent, clients MUST discard
+the packet.  This prevents an off-path attacker from injecting a Retry packet
+with a bogus new Source Connection ID.
+
+The client responds to a Retry packet with Initial packet that includes the
+provided Retry Token to continue connection establishment.
+
+A server that might send another Retry packet in response to a subsequent
+Initial packet MUST set the Source Connection ID to new value of at least 8

@nibanks the way I read it, the reset is stateless so each source is semi-randomly generated, consequently a second retry will stastically differ from the first. Also across servers. This could be made clearer.

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

----==_mimepart_5b3637448546b_19a93fa029688f7c4129a-- From nobody Fri Jun 29 06:49:49 2018 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 E7DEF130EC0 for ; Fri, 29 Jun 2018 06:49:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.606 X-Spam-Level: X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 f-sX0nWWUaTA for ; Fri, 29 Jun 2018 06:49:46 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7AEE130E0E for ; Fri, 29 Jun 2018 06:49:44 -0700 (PDT) Date: Fri, 29 Jun 2018 06:49:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530280184; bh=F6T/NPlH00fClbp/Cdy0+aiCKu799OhU2pubG0GpVTs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nJPSP9n7VDrY7jzazmHOFMNB/LpiDDFBseHVQIFoXdULu+Uu0RGsk3Tex62nGydjj x0JL+PiNMbTsX3ZUJ4fqcqvuCQwfG/L0EJh8AKW+ZQBTy24v4jczIg/EzKts2gKPez p3f267Q8sEsdoveFWpIxtM5Kv2UdR6djZoToO094= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Correct a contradiction (#1499) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3638f83064b_18463fd7ed012f8417033d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Fri, 29 Jun 2018 13:49:49 -0000 ----==_mimepart_5b3638f83064b_18463fd7ed012f8417033d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett approved this pull request. -- 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/1499#pullrequestreview-133233523 ----==_mimepart_5b3638f83064b_18463fd7ed012f8417033d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett approved this pull request.

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

----==_mimepart_5b3638f83064b_18463fd7ed012f8417033d-- From nobody Fri Jun 29 07:10:02 2018 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 4CA2F130F00 for ; Fri, 29 Jun 2018 07:09:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 KkfIYKLgBssM for ; Fri, 29 Jun 2018 07:09:53 -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 50134130F01 for ; Fri, 29 Jun 2018 07:09:53 -0700 (PDT) Date: Fri, 29 Jun 2018 07:09:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530281392; bh=2aRD5X9ORLyB7+a6dQOq60k2at8OzozwmmLere7rW/k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ei/pLlx54LlI0hBrvt5tmFw1Gkk2vxl+TfXEyXU1KSdw+vf1JmGAITa+/gJLallFT zzyaw8fa4zYY3ZyMFATrf3C/Q3x+eSnr7oTA31XjSn5Z7FgCQk5CDT8vSZWUnUam1+ YgfVxwxwQLw0FJCILLyV7RiKrs/GHOemTS9j34eA= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b363db053a50_1e02ac6f9946f5c8764d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Fri, 29 Jun 2018 14:10:00 -0000 ----==_mimepart_5b363db053a50_1e02ac6f9946f5c8764d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ekr commented on this pull request. > -If the client has a suitable token available from a previous connection, it -SHOULD populate the Token field. +If the client has an unused token that it received in a NEW_TOKEN frame on a +previous connection to what it believes to be the same server, it includes that +value in the Token field of its Initial packet. We have plenty of MUST requirements that don't serve interop. But SHOULD would be fine as well. Writing it as "it will" is just confusing. -- 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/1498#discussion_r199171273 ----==_mimepart_5b363db053a50_1e02ac6f9946f5c8764d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ekr commented on this pull request.

In draft-ietf-quic-transport.md:

>  
-If the client has a suitable token available from a previous connection, it
-SHOULD populate the Token field.
+If the client has an unused token that it received in a NEW_TOKEN frame on a
+previous connection to what it believes to be the same server, it includes that
+value in the Token field of its Initial packet.

We have plenty of MUST requirements that don't serve interop. But SHOULD would be fine as well. Writing it as "it will" is just confusing.

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

----==_mimepart_5b363db053a50_1e02ac6f9946f5c8764d-- From nobody Fri Jun 29 08:56:23 2018 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 83D92130DC1 for ; Fri, 29 Jun 2018 08:56:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 yMLvjnhrz-xS for ; Fri, 29 Jun 2018 08:56:20 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D993126CC7 for ; Fri, 29 Jun 2018 08:56:20 -0700 (PDT) Date: Fri, 29 Jun 2018 08:56:19 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530287779; bh=k55wYTZrAP+pZbYixwFqTpIpH3pnDfXQN4FAbhipni0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=h0DpM7F8+nW8JJ1KnQ+NndtgJDG+ereb8rRxXLxLTFbg8XhcqB5daf1qE8rOYzUGP gq4z72DeYvBFYdMslqSVdhc4GUAtmHd72d59mXH7+jGY1Jr7mqoMGrdfmQ1v0gHe8q 8BVzIUFP5KiEcI9hZ8wRWQkxnNWamTxrhA31M3A8= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3656a384bfb_5ed42aedf03e0f5417780"; 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.26 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: Fri, 29 Jun 2018 15:56:23 -0000 ----==_mimepart_5b3656a384bfb_5ed42aedf03e0f5417780 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older Perhaps, but then you'd need to individually retire old CIDs one at a time. I'm envisioning this as more of a sliding window -- an implementation is moving the end of the window. Is there a reason you wouldn't just roll forward to another CID when you send this frame, in that situation? -- 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/1496#discussion_r199205706 ----==_mimepart_5b3656a384bfb_5ed42aedf03e0f5417780 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

Perhaps, but then you'd need to individually retire old CIDs one at a time. I'm envisioning this as more of a sliding window -- an implementation is moving the end of the window. Is there a reason you wouldn't just roll forward to another CID when you send this frame, in that situation?

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

----==_mimepart_5b3656a384bfb_5ed42aedf03e0f5417780-- From nobody Fri Jun 29 08:59:08 2018 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 BF121130DD1 for ; Fri, 29 Jun 2018 08:59:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 o6mltLWte01k for ; Fri, 29 Jun 2018 08:59:05 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5708D130DC1 for ; Fri, 29 Jun 2018 08:59:05 -0700 (PDT) Date: Fri, 29 Jun 2018 08:59:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530287944; bh=6r8zVC/zddqHjjlkZJIKUITzkf/1q1DwJQFxnFxNLQM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kC/xkT0koYCnwKVv8DNKwwTkHVV5/qaj6EsFEb1KGtL8x9uJQy3wItwGUyDIzNyza HK41Eeo5IYqlagoQgs74R+c4aja7X1Nm0ZjsEUELZC4/tY51EH8VRmA3NVuG0bMKoT lxxQUsBAQHTTSEQGeoOm3MYOyHbuTeq6hcjBx+98= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36574877bee_34413fb1a1032f7c133567"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 15:59:07 -0000 ----==_mimepart_5b36574877bee_34413fb1a1032f7c133567 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older We should be dealing is so few numbers of simultaneous CIDs that it should be just fine to be explicit. I think a sliding window puts to much of a restriction that you are constantly moving the primary path to these new CIDs. I must prefer being explicit, per CID. -- 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/1496#discussion_r199206490 ----==_mimepart_5b36574877bee_34413fb1a1032f7c133567 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

We should be dealing is so few numbers of simultaneous CIDs that it should be just fine to be explicit. I think a sliding window puts to much of a restriction that you are constantly moving the primary path to these new CIDs. I must prefer being explicit, per CID.

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

----==_mimepart_5b36574877bee_34413fb1a1032f7c133567-- From nobody Fri Jun 29 09:01:18 2018 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 69DC1130DD1 for ; Fri, 29 Jun 2018 09:01:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 y8Ytk_JSkQIE for ; Fri, 29 Jun 2018 09:01:14 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DCA6130DD8 for ; Fri, 29 Jun 2018 09:01:14 -0700 (PDT) Date: Fri, 29 Jun 2018 09:01:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530288073; bh=M5bfIEurnat4elPbr0rgZgI5+EmxaCcQ3l9wPd4bXNQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yEy/wC3Suvf6+AtjmGC7Zg5DGsC+nclfif5K5Tca8sTSNU2r7HfQcCt7vG16j25lm e+MaPBawHplWJE/lYRC6995ZCtuMZ9zWhzHmKc0q1H+6Hz3sAOyUU+DdOl3UVvk4iR D5DJiK8dd47WSV4g7vu/34AtTH+YN6NuhiZrSo84= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define NAT rebinding better (#1501) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3657c9bb7c7_5eb72aedf03e0f5421352f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Fri, 29 Jun 2018 16:01:17 -0000 ----==_mimepart_5b3657c9bb7c7_5eb72aedf03e0f5421352f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. > -note that not all changes of peer address are intentional migrations. The peer -could experience an unintended change of address due to NAT rebinding; endpoints -SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not -cause the connection to fail. +finished and the endpoint has 1-RTT keys. The design of QUIC relies on +endpoints retaining a stable address for the duration of the handshake. + +An endpoint also MUST NOT initiate connection migration if the peer sent the +`disable_migration` transport parameter during the handshake. An endpoint which +has sent this transport parameter, but detects that a peer has nonetheless +migrated to a different network MAY treat this as a connection error of type +INVALID_MIGRATION. + +Not all changes of peer address are intentional migrations. The peer could +experience NAT rebinding: a change of address due a middlebox, usually a NAT, +allocating a new outgoing IP address and port for a flow. Endpoints SHOULD IP address and/or port? Typically NAT rebinds are only port 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/pull/1501#pullrequestreview-133285426 ----==_mimepart_5b3657c9bb7c7_5eb72aedf03e0f5421352f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

In draft-ietf-quic-transport.md:

> -note that not all changes of peer address are intentional migrations. The peer
-could experience an unintended change of address due to NAT rebinding; endpoints
-SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not
-cause the connection to fail.
+finished and the endpoint has 1-RTT keys.  The design of QUIC relies on
+endpoints retaining a stable address for the duration of the handshake.
+
+An endpoint also MUST NOT initiate connection migration if the peer sent the
+`disable_migration` transport parameter during the handshake.  An endpoint which
+has sent this transport parameter, but detects that a peer has nonetheless
+migrated to a different network MAY treat this as a connection error of type
+INVALID_MIGRATION.
+
+Not all changes of peer address are intentional migrations. The peer could
+experience NAT rebinding: a change of address due a middlebox, usually a NAT,
+allocating a new outgoing IP address and port for a flow.  Endpoints SHOULD

IP address and/or port? Typically NAT rebinds are only port change.

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

----==_mimepart_5b3657c9bb7c7_5eb72aedf03e0f5421352f-- From nobody Fri Jun 29 09:07:55 2018 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 DDA2A130DD4 for ; Fri, 29 Jun 2018 09:07:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 NI2vyIGBGmtm for ; Fri, 29 Jun 2018 09:07:52 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3EBD130DC1 for ; Fri, 29 Jun 2018 09:07:51 -0700 (PDT) Date: Fri, 29 Jun 2018 09:07:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530288471; bh=k9eAm5oasLjCsSFXjLbcp6TyrDz7dVVAFFAhJT9Rgx4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=tMb0tJcJSKKaQA1kb4In/aj5mNfNMwYa39VB3n1sP4tmh9v7AIyZQeLCJNsS9VjJs MPznnfievYLDU6aDlzNgtio8Zlm3Nqp/MXN2xJ3bRoxS6gYX9fYG7fzAT+MuOMaG0s VOZE8Dnc6Ej3BCnvGzU95DUGHABtoQHheeQCF9h0= From: martinduke Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Make Packet Number a standard varint, with no inference (#1502) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3659571b57d_69f43fdd52f24f8077184"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: martinduke 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.26 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: Fri, 29 Jun 2018 16:07:54 -0000 ----==_mimepart_5b3659571b57d_69f43fdd52f24f8077184 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Now that packet numbers start at 0, I am not sure there is a ton of value in truncating these numbers. There are some advantages to making it a standard 1 to 8 byte-varint: - Reuse existing varint code instead of implementing something special that can be screwed up. - Eliminate the need to infer the most significant bits of the PN, which is another thing to screw up that has pretty bad consequences for connection integrity (e.g. acking packets that weren't actually received) - Eliminating the inference also makes it easier for debugging tools like Wireshark to correctly display the PN. I assert that the fraction of connections that will need 64-bit packet numbers will be exceedingly small. There are probably very minor bit-efficiency issues (connections with 255-64K packets sent at a relatively low rate, etc), but these pale in comparison to the bytes we've put into variable length CIDs, etc. We already encoding the PN this way in the Largest_acked field of the ACK frame, so I believe the same principles should apply. If people agree with this assessment, I'll drop a PR. -- 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/1502 ----==_mimepart_5b3659571b57d_69f43fdd52f24f8077184 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Now that packet numbers start at 0, I am not sure there is a ton of value in truncating these numbers. There are some advantages to making it a standard 1 to 8 byte-varint:

  • Reuse existing varint code instead of implementing something special that can be screwed up.
  • Eliminate the need to infer the most significant bits of the PN, which is another thing to screw up that has pretty bad consequences for connection integrity (e.g. acking packets that weren't actually received)
  • Eliminating the inference also makes it easier for debugging tools like Wireshark to correctly display the PN.

I assert that the fraction of connections that will need 64-bit packet numbers will be exceedingly small. There are probably very minor bit-efficiency issues (connections with 255-64K packets sent at a relatively low rate, etc), but these pale in comparison to the bytes we've put into variable length CIDs, etc.

We already encoding the PN this way in the Largest_acked field of the ACK frame, so I believe the same principles should apply.

If people agree with this assessment, I'll drop a PR.

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

----==_mimepart_5b3659571b57d_69f43fdd52f24f8077184-- From nobody Fri Jun 29 09:14:00 2018 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 D5EBC130DDC for ; Fri, 29 Jun 2018 09:13:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 hCTFd4ykH_g9 for ; Fri, 29 Jun 2018 09:13:56 -0700 (PDT) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 C7B0C130DD4 for ; Fri, 29 Jun 2018 09:13:55 -0700 (PDT) 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=Of0otPtLae/WqwtxfyzIC2rvjVI=; b=E3OF3Qmt4JgptI9O JdCheQRwDuDpiG0VMSZid2XQVlRaaLy2YXa1c9sDwKYc5Z6Gd8VQzD7bpb8dx5+3 LCxkqdqGbiQDPZC+8Q1JpQGPZ/DTj3ddA27ydw6XVRcuy0ZOTTs54NtY3E/wxU6f qZKUAyWbvZkuwZPHbn8evXpyKCY= Received: by filter0061p1iad2.sendgrid.net with SMTP id filter0061p1iad2-20029-5B365ABF-3A 2018-06-29 16:13:51.730642549 +0000 UTC Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id Im_4sXA9R1G3P0bkbiV2zw for ; Fri, 29 Jun 2018 16:13:51.828 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id C808A3E00B0 for ; Fri, 29 Jun 2018 09:13:51 -0700 (PDT) Date: Fri, 29 Jun 2018 16:13:51 +0000 (UTC) From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Make Packet Number a standard varint, with no inference (#1502) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b365abfc5f31_4fbf2aaf35620f5c77314"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2IHALaAD1s8U3SuTs/0o/vm46Zf0XzVu9gCH 7ySp024hUJ7GGfn55MJ8/v6J7kxZ+Wt0+zcr6/ME8c4j1kv58GhJKqut958xyZWZLd7uxLrwM6O4uA CZ4RV5DO2W8t6NsQGgmxlAB6qm8ifyVXpUn8pMhFBCDQpLZr4s05zAnTNIXHBGjQ7bxO9ORDLBrr/5 E= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 16:13:58 -0000 ----==_mimepart_5b365abfc5f31_4fbf2aaf35620f5c77314 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This will make users of long-lived bandwidth sensitive apps unhappy. WebRTC audio-only connections are a good example of this. Today they can commonly use a single byte packet number, and with this they'd commonly be using 4 byte PNs. -- 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/1502#issuecomment-401402267 ----==_mimepart_5b365abfc5f31_4fbf2aaf35620f5c77314 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This will make users of long-lived bandwidth sensitive apps unhappy. WebRTC audio-only connections are a good example of this. Today they can commonly use a single byte packet number, and with this they'd commonly be using 4 byte PNs.

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

----==_mimepart_5b365abfc5f31_4fbf2aaf35620f5c77314-- From nobody Fri Jun 29 10:16:48 2018 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 0E3C5130DFB for ; Fri, 29 Jun 2018 10:16:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 BnsJGbjLBYTP for ; Fri, 29 Jun 2018 10:16:41 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED7F1130DE8 for ; Fri, 29 Jun 2018 10:16:40 -0700 (PDT) Date: Fri, 29 Jun 2018 10:16:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530292599; bh=F9N84jP9NLUYVQ8xam0olrKEtXw8PENLr2SDthUYPqM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u+SmZ8iWiady2KXfXQi6ALc0Qkg9EfR6x8Nbq9KoXCEmeRCpjRPHEx7TrqRI4JUht B9I0cBxuLi966W1IYn7HFPyRkanwwyD73FII3xMkrQ0v5Fz5M4/3UV7YyV+ciO2lO0 /8sIc/g92XEHIfjkWTofsYnQUR+W0AeMDZ+1gRBw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Define NAT rebinding better (#1501) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36697718d65_28912b1d4d0a2f5413718b"; 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.26 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: Fri, 29 Jun 2018 17:16:46 -0000 ----==_mimepart_5b36697718d65_28912b1d4d0a2f5413718b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop approved this pull request. > -note that not all changes of peer address are intentional migrations. The peer -could experience an unintended change of address due to NAT rebinding; endpoints -SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not -cause the connection to fail. +finished and the endpoint has 1-RTT keys. The design of QUIC relies on +endpoints retaining a stable address for the duration of the handshake. + +An endpoint also MUST NOT initiate connection migration if the peer sent the +`disable_migration` transport parameter during the handshake. An endpoint which +has sent this transport parameter, but detects that a peer has nonetheless +migrated to a different network MAY treat this as a connection error of type +INVALID_MIGRATION. + +Not all changes of peer address are intentional migrations. The peer could +experience NAT rebinding: a change of address due a middlebox, usually a NAT, +allocating a new outgoing IP address and port for a flow. Endpoints SHOULD Typically, but not universally. I agree with "and/or", or perhaps even making the levels differ more -- "allocating a new port or even a new outgoing IP address for a flow." -- 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/1501#pullrequestreview-133308729 ----==_mimepart_5b36697718d65_28912b1d4d0a2f5413718b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop approved this pull request.

In draft-ietf-quic-transport.md:

> -note that not all changes of peer address are intentional migrations. The peer
-could experience an unintended change of address due to NAT rebinding; endpoints
-SHOULD perform path validation ({{migrate-validate}}) if the rebinding does not
-cause the connection to fail.
+finished and the endpoint has 1-RTT keys.  The design of QUIC relies on
+endpoints retaining a stable address for the duration of the handshake.
+
+An endpoint also MUST NOT initiate connection migration if the peer sent the
+`disable_migration` transport parameter during the handshake.  An endpoint which
+has sent this transport parameter, but detects that a peer has nonetheless
+migrated to a different network MAY treat this as a connection error of type
+INVALID_MIGRATION.
+
+Not all changes of peer address are intentional migrations. The peer could
+experience NAT rebinding: a change of address due a middlebox, usually a NAT,
+allocating a new outgoing IP address and port for a flow.  Endpoints SHOULD

Typically, but not universally. I agree with "and/or", or perhaps even making the levels differ more -- "allocating a new port or even a new outgoing IP address for a flow."

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

----==_mimepart_5b36697718d65_28912b1d4d0a2f5413718b-- From nobody Fri Jun 29 10:21:22 2018 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 A1EE5130DDD for ; Fri, 29 Jun 2018 10:21:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 cxUkvAvol6MG for ; Fri, 29 Jun 2018 10:21:14 -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 492D2130E7E for ; Fri, 29 Jun 2018 10:20:38 -0700 (PDT) Date: Fri, 29 Jun 2018 10:20:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530292837; bh=tqIV2fz8kVnb15nb2NJZH77c633ktQZ3L9IP8xJVXSE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=h5T1bAOPmbUpyn9WkQeJMttErBxsrPZiXG2Wnj5tRkDskCVhUJ0EAEu+e9Xegb0Hg RboJL5DonuKvtXMm/CYEPXx5L2IqMMeNpZNsank7r3Z5IBEMtCQ4d8DvqStnJ1BMCW 1wjMcZAYKyjUeucdGN+r0qZQYiux1zMHL/b4u5k0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b366a657f876_39cf3fcfee064f845651f"; 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.26 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: Fri, 29 Jun 2018 17:21:21 -0000 ----==_mimepart_5b366a657f876_39cf3fcfee064f845651f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older I'm inclined to think that if you're dealing in small numbers of CIDs, it's fine to just remember all of them. If you reach the point where you need to abandon old CIDs because you have too many outstanding, then we're already in a scenario where you're using a lot of them. -- 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/1496#discussion_r199226914 ----==_mimepart_5b366a657f876_39cf3fcfee064f845651f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

I'm inclined to think that if you're dealing in small numbers of CIDs, it's fine to just remember all of them. If you reach the point where you need to abandon old CIDs because you have too many outstanding, then we're already in a scenario where you're using a lot of them.

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

----==_mimepart_5b366a657f876_39cf3fcfee064f845651f-- From nobody Fri Jun 29 10:23:45 2018 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 521F6130DDD for ; Fri, 29 Jun 2018 10:23:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vuuCDvVvhDee for ; Fri, 29 Jun 2018 10:23:33 -0700 (PDT) Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AA88130DCC for ; Fri, 29 Jun 2018 10:23:33 -0700 (PDT) Date: Fri, 29 Jun 2018 10:23:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530293012; bh=Uyv8kMiUME455MtBZEkFo+oQZQzr3CO2OiaF5Lv4sos=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mUvdeM0DFYivFVX0TN3Kew3oZKnH2D8bD32jWxhnEx+8IIwN44n92qzpHvpCK5J67 WsjNS6F2vouv0hposZCPagCp5TITDG70I8nZERGFgMeypJK31didF6Xv8KAtNTAYh3 oQi2MykW6Ie+NPJmuWPWmLdzLoo6dzT5sA+rklk0= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Disagreement about CID Liveness (#1495) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b366b142d038_13d53fdc118a0f8465852"; 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.26 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: Fri, 29 Jun 2018 17:23:40 -0000 ----==_mimepart_5b366b142d038_13d53fdc118a0f8465852 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit One more scenario is load balancer key rotation. We've already sketched the possible scheme where the CID includes a key phase indicator and the CID itself is some encrypted payload. At whatever point the key identifier wraps (every key change, if it's a single bit), you need to bulk purge all CIDs issued under the soon-to-be-removed key. Probably largely irrelevant for short-lived connections, but long-lived connections could easily run afoul of this. -- 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/1495#issuecomment-401420026 ----==_mimepart_5b366b142d038_13d53fdc118a0f8465852 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

One more scenario is load balancer key rotation. We've already sketch= ed the possible scheme where the CID includes a key phase indicator and t= he CID itself is some encrypted payload. At whatever point the key ident= ifier wraps (every key change, if it's a single bit), you need to bulk pu= rge all CIDs issued under the soon-to-be-removed key.

Probably largely irrelevant for short-lived connections, but long-live= d connections could easily run afoul of this.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b366b142d038_13d53fdc118a0f8465852-- From nobody Fri Jun 29 10:27:36 2018 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 B1613130DE2 for ; Fri, 29 Jun 2018 10:27:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 M4fBoNDXvD2o for ; Fri, 29 Jun 2018 10:27:25 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE28130DCC for ; Fri, 29 Jun 2018 10:27:25 -0700 (PDT) Date: Fri, 29 Jun 2018 10:27:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530293244; bh=x1L3yF/xpTiZMGyKi4uhC2w++Mme6kpB2eoKKRoE2ws=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vkogEDIih7ze0rFcV0Ze7MlfJLIu6EbJDmbUiXeJyj8WQuTBnMfmtGatmKhY+ZvUW 3Z1Y6J33hdoDbwn5eK43hYKxg4JF0YL51Y1yeCooNzkO7ld1uP9eWmAyO7HDexWsrd mAwE4MKW7fGfV02FNBQyw4vBlgwVzqkR3mx5nzSc= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b366bfc9f39e_2ca22ae1e1eacf5c818e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 17:27:34 -0000 ----==_mimepart_5b366bfc9f39e_2ca22ae1e1eacf5c818e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older While, we haven't implemented migration yet in WinQuic, the following is the design we'd have been considering: - Have a hard coded limit on the number of CIDs to give to the peer, X (probably 3 or 4) - Have a hard coded limit on the number of valid paths to maintain, Y (probably 2 or 3) - Whenever we need to give a new CID out, if we are at our limit, we throw away the oldest, non-primary path, CID in our cache. If that CID was for a validated path, throw the path away. - Trickier logic is around new paths being created. Not quite worked through the details on that one. But bottom line, with this design, we don't expect to age out more than one at a time. And additionally, the peer could indicate they have to throw a CID away because they tried and failed to use it for a new path validation. -- 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/1496#discussion_r199228603 ----==_mimepart_5b366bfc9f39e_2ca22ae1e1eacf5c818e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

While, we haven't implemented migration yet in WinQuic, the following is the design we'd have been considering:

  • Have a hard coded limit on the number of CIDs to give to the peer, X (probably 3 or 4)
  • Have a hard coded limit on the number of valid paths to maintain, Y (probably 2 or 3)
  • Whenever we need to give a new CID out, if we are at our limit, we throw away the oldest, non-primary path, CID in our cache. If that CID was for a validated path, throw the path away.
  • Trickier logic is around new paths being created. Not quite worked through the details on that one.

But bottom line, with this design, we don't expect to age out more than one at a time. And additionally, the peer could indicate they have to throw a CID away because they tried and failed to use it for a new path validation.

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

----==_mimepart_5b366bfc9f39e_2ca22ae1e1eacf5c818e6-- From nobody Fri Jun 29 12:06:54 2018 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 A8414130E27 for ; Fri, 29 Jun 2018 12:06:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 0R5uGrrArnXi for ; Fri, 29 Jun 2018 12:06:50 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ED83130E26 for ; Fri, 29 Jun 2018 12:06:50 -0700 (PDT) Date: Fri, 29 Jun 2018 12:06:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530299210; bh=/RkDGj+jab4J7wmCHP3taLUn7zuK+otj729AZzbXw48=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oSEqAq+J+VSZZt1bLsDhoCqOXxm3MwI4wXPDND0em1lOr/c0bUm2MWOnKjtDaWLI+ SSHYdqkarzseNQ/H19qb3z1mXqLH6W6B7cgeExM6ZoZ0wiVuSoBmdraXnrj1PuZJ7P ZeKIVVRxYDH+inCQwAW9sRdBXVfoQZ4434B4iHOY= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Rework Retry packet (#1498) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b368349a9ff1_1b1d3fd945ab2f80125596"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Fri, 29 Jun 2018 19:06:53 -0000 ----==_mimepart_5b368349a9ff1_1b1d3fd945ab2f80125596 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. This looks like an improvement overall and clarifies some points. > +| Version (32) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +|DCIL(4)|SCIL(4)| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Destination Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Source Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ODCIL(8) | Original Destination Connection ID (*) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Retry Token (*) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ +{: #retry-format title="Retry Packet"} + +A Retry packet (shown in {{retry-format}}) only the invariant portion of the "A Retry packet only" uses? > + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+ +|1| 0x7e | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Version (32) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +|DCIL(4)|SCIL(4)| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Destination Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Source Connection ID (0/32..144) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| ODCIL(8) | Original Destination Connection ID (*) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Retry Token (*) ... I'm realizing the lack of length means one can't 'coalesce' a RETRY and another packet type in a single datagram. I can't think why this is a practical issue, but it wouldn't surprise me if there was a use for it at some point, so I think it makes sense to add a length. > + +Retry Token: + +: An opaque token that the server can use to validate the client's address. + +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. I think what Martin has is good, but I can imagine a DDoS device doing what you said, especially if it kept a small amount of state to ensure it didn't sent too many RETRY packets to a given IP/port. So this could be a SHOULD instead of a MUST. > +The server populates the Destination Connection ID with the connection ID that +the client included in the Source Connection ID of the Initial packet. + +The server includes a connection ID of its choice in the Source Connection ID +field. The client MUST use this connection ID in the Destination Connection ID +of subsequent packets that it sends. + +A Retry packet does not include a packet number and cannot be explictly +acknowledged by a client. + +A server MUST only send a Retry in response to a client Initial packet. + +If the Original Destination Connection ID field does not match the Destination +Connection ID from the most recent the Initial packet it sent, clients MUST +discard the packet. This prevents an off-path attacker from injecting a Retry +packet with a bogus new Source Connection ID. I think "with a bogus new Source Connection ID." is unnecessary here, since any off-path injection is bad. > Token Length: : A variable-length integer specifying the length of the Token field, in bytes. - It may be zero if no token is present. Initial packets sent by the server + This value is zero if no token is present. Initial packets sent by the server MUST include a zero-length token. I think this would be clearer as "Initial packets sent by the server must specify a zero token length." > +Note that if the server sends a HelloRetryRequest, the client will send a second +Initial packet with a CRYPTO frame with an offset starting at the end of the +CRYPTO stream in the first Initial. "end of the CRYPTO stream" makes it sound like it's after the stream has ended, ie: been FIN'd. Possibly "with an offset starting after the CRYPTO data in the first Initial." > @@ -624,10 +724,18 @@ server, it MUST discard any packet it receives with a different Source Connection ID. -#### Tokens +### Tokens + +If the client has an unused token that it received in a NEW_TOKEN frame on a nit: Unnecessary "that" > @@ -624,10 +724,18 @@ server, it MUST discard any packet it receives with a different Source Connection ID. -#### Tokens +### Tokens + +If the client has an unused token that it received in a NEW_TOKEN frame on a +previous connection to what it believes to be the same server, it includes that it SHOULD include that? > -If the client has a suitable token available from a previous connection, it -SHOULD populate the Token field. +A client MUST NOT reuse a token if it believes that its point of network By saying unused in the previous paragraph, you imply tokens should never be used more than once. But this paragraph seems to imply it's ok if you haven't changed IP. Which do you intend? > @@ -649,85 +757,27 @@ Note: the packet is that the client might have received the token in a previous connection using the NEW_TOKEN frame, and if the server has lost state, it might be unable to validate the token at all, leading to connection failure if - the packet is discarded. + the packet is discarded. A server might encode tokens that it provides with might -> MAY? And I'd suggest "that it provides" -> "provided" > -The first Initial packet contains a packet number of 0. Each packet sent after -the Initial packet is associated with a packet number space and its packet -number increases monotonically in that space (see {{packet-numbers}}). +The first Initial packet sent by either endpoint contains a packet number of SHOULD contain? > -The first Initial packet contains a packet number of 0. Each packet sent after -the Initial packet is associated with a packet number space and its packet -number increases monotonically in that space (see {{packet-numbers}}). +The first Initial packet sent by either endpoint contains a packet number of +0. The packet number increases monotonically thereafter. Initial packets are in MUST increase -- 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/1498#pullrequestreview-133337121 ----==_mimepart_5b368349a9ff1_1b1d3fd945ab2f80125596 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

This looks like an improvement overall and clarifies some points.

In draft-ietf-quic-transport.md:

> +|                         Version (32)                          |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|DCIL(4)|SCIL(4)|
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|               Destination Connection ID (0/32..144)         ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                 Source Connection ID (0/32..144)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|    ODCIL(8)   |      Original Destination Connection ID (*)   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        Retry Token (*)                      ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+{: #retry-format title="Retry Packet"}
+
+A Retry packet (shown in {{retry-format}}) only the invariant portion of the

"A Retry packet only" uses?

In draft-ietf-quic-transport.md:

> + 0                   1                   2                   3
+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+
+|1|    0x7e     |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Version (32)                          |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|DCIL(4)|SCIL(4)|
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|               Destination Connection ID (0/32..144)         ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                 Source Connection ID (0/32..144)            ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|    ODCIL(8)   |      Original Destination Connection ID (*)   |
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                        Retry Token (*)                      ...

I'm realizing the lack of length means one can't 'coalesce' a RETRY and another packet type in a single datagram. I can't think why this is a practical issue, but it wouldn't surprise me if there was a use for it at some point, so I think it makes sense to add a length.

In draft-ietf-quic-transport.md:

> +
+Retry Token:
+
+: An opaque token that the server can use to validate the client's address.
+
+The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.

I think what Martin has is good, but I can imagine a DDoS device doing what you said, especially if it kept a small amount of state to ensure it didn't sent too many RETRY packets to a given IP/port. So this could be a SHOULD instead of a MUST.

In draft-ietf-quic-transport.md:

> +The server populates the Destination Connection ID with the connection ID that
+the client included in the Source Connection ID of the Initial packet.
+
+The server includes a connection ID of its choice in the Source Connection ID
+field.  The client MUST use this connection ID in the Destination Connection ID
+of subsequent packets that it sends.
+
+A Retry packet does not include a packet number and cannot be explictly
+acknowledged by a client.
+
+A server MUST only send a Retry in response to a client Initial packet.
+
+If the Original Destination Connection ID field does not match the Destination
+Connection ID from the most recent the Initial packet it sent, clients MUST
+discard the packet.  This prevents an off-path attacker from injecting a Retry
+packet with a bogus new Source Connection ID.

I think "with a bogus new Source Connection ID." is unnecessary here, since any off-path injection is bad.

In draft-ietf-quic-transport.md:

>  
 Token Length:
 
 : A variable-length integer specifying the length of the Token field, in bytes.
-  It may be zero if no token is present. Initial packets sent by the server
+  This value is zero if no token is present.  Initial packets sent by the server
   MUST include a zero-length token.

I think this would be clearer as "Initial packets sent by the server must specify a zero token length."

In draft-ietf-quic-transport.md:

>  
+Note that if the server sends a HelloRetryRequest, the client will send a second
+Initial packet with a CRYPTO frame with an offset starting at the end of the
+CRYPTO stream in the first Initial.

"end of the CRYPTO stream" makes it sound like it's after the stream has ended, ie: been FIN'd.

Possibly "with an offset starting after the CRYPTO data in the first Initial."

In draft-ietf-quic-transport.md:

> @@ -624,10 +724,18 @@ server, it MUST discard any packet it receives with a different Source
 Connection ID.
 
 
-#### Tokens
+### Tokens
+
+If the client has an unused token that it received in a NEW_TOKEN frame on a

nit: Unnecessary "that"

In draft-ietf-quic-transport.md:

> @@ -624,10 +724,18 @@ server, it MUST discard any packet it receives with a different Source
 Connection ID.
 
 
-#### Tokens
+### Tokens
+
+If the client has an unused token that it received in a NEW_TOKEN frame on a
+previous connection to what it believes to be the same server, it includes that

it SHOULD include that?

In draft-ietf-quic-transport.md:

>  
-If the client has a suitable token available from a previous connection, it
-SHOULD populate the Token field.
+A client MUST NOT reuse a token if it believes that its point of network

By saying unused in the previous paragraph, you imply tokens should never be used more than once. But this paragraph seems to imply it's ok if you haven't changed IP. Which do you intend?

In draft-ietf-quic-transport.md:

> @@ -649,85 +757,27 @@ Note:
   the packet is that the client might have received the token in a previous
   connection using the NEW_TOKEN frame, and if the server has lost state, it
   might be unable to validate the token at all, leading to connection failure if
-  the packet is discarded.
+  the packet is discarded.  A server might encode tokens that it provides with

might -> MAY?
And I'd suggest "that it provides" -> "provided"

In draft-ietf-quic-transport.md:

>  
-The first Initial packet contains a packet number of 0. Each packet sent after
-the Initial packet is associated with a packet number space and its packet
-number increases monotonically in that space (see {{packet-numbers}}).
+The first Initial packet sent by either endpoint contains a packet number of

SHOULD contain?

In draft-ietf-quic-transport.md:

>  
-The first Initial packet contains a packet number of 0. Each packet sent after
-the Initial packet is associated with a packet number space and its packet
-number increases monotonically in that space (see {{packet-numbers}}).
+The first Initial packet sent by either endpoint contains a packet number of
+0. The packet number increases monotonically thereafter.  Initial packets are in

MUST increase

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

----==_mimepart_5b368349a9ff1_1b1d3fd945ab2f80125596-- From nobody Fri Jun 29 13:15:54 2018 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 8D986130E00 for ; Fri, 29 Jun 2018 13:15:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 4lx1g27bLsX0 for ; Fri, 29 Jun 2018 13:15:50 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E700F124C04 for ; Fri, 29 Jun 2018 13:15:49 -0700 (PDT) Date: Fri, 29 Jun 2018 13:15:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530303349; bh=8zVhlRjRV8nEJMvCh/OAXweCcQLTGiQ4veJmKhERYIk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CrPDPL47Q9GXIXQQkINreQTo4o1+6bg5qPxCokhUHw/wxq7uOpXrhRLTXp4Uz7DvN IlI9I8RY2sZ2AznHxwd8TwJvcrPY6tsfrNr146zfW1rxx99M0qyCFTUevRZTQFYzc4 me2Q/buEUjilecLDpqhffmOF9lc/ojCPggJWHh50= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3693756327_57cf3fe0430f0f88293e0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Fri, 29 Jun 2018 20:15:52 -0000 ----==_mimepart_5b3693756327_57cf3fe0430f0f88293e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ICMP and Load Balancers is a generic problem, but QUIC has some protocol elements specifically designed to help load balancers (Server CID). It stands to reason that enable those protocol elements to help with ICMP processing in QUIC context. @martinduke, which workarounds do you have in mind (unless it is PLPMTUD)? PLPMTUD, for example, specifically states that it works most efficiently with ICMP. So this issue is about enabling ICMP to for for PMTU in the presence of load balancers. -- 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/1243#issuecomment-401462472 ----==_mimepart_5b3693756327_57cf3fe0430f0f88293e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

ICMP and Load Balancers is a generic problem, but QUIC has some protoc= ol elements specifically designed to help load balancers (Server CID). I= t stands to reason that enable those protocol elements to help with ICMP = processing in QUIC context.

@martinduke, which workarounds= do you have in mind (unless it is PLPMTUD)? PLPMTUD, for example, speci= fically states that it works most efficiently with ICMP. So this issue i= s about enabling ICMP to for for PMTU in the presence of load balancers.<= /p>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3693756327_57cf3fe0430f0f88293e0-- From nobody Fri Jun 29 13:24:09 2018 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 476B6130F40 for ; Fri, 29 Jun 2018 13:23:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 8ye1DXTmqZ-h for ; Fri, 29 Jun 2018 13:23:56 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48F09130F49 for ; Fri, 29 Jun 2018 13:23:56 -0700 (PDT) Date: Fri, 29 Jun 2018 13:23:55 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530303835; bh=wMLyUupnTkBzYJh4V94Hgp6qIwIrmVlBfnTkMJkDRV0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Xonkkv9+zDpCAkYDy/r7orgE2pk2dZi6icBtW7q1T95QUSuzb+vZ5i40w6Q7jtJt8 Gux2nCBY2oWRjttQ136MnTPCfVSLGvGtRh0Va+j3ENiD8oqDocoiQze6S8GidRCqXN O/D9ojheqWSRaVHfYCt4qXJY48+2czh/9Uj7WOgk= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36955b2105d_23cb2af6bdc5cf54129420"; 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: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 20:24:08 -0000 ----==_mimepart_5b36955b2105d_23cb2af6bdc5cf54129420 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Now that unidirectional streams have landed, its easier to spot where this section could be tightened up. I've removed a bit of duplication and reordered text to match ordering of server push (PUSH_PROMISE and then push stream). You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1503 -- Commit Summary -- * Server push tidy up -- File Changes -- M draft-ietf-quic-http.md (77) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1503.patch https://github.com/quicwg/base-drafts/pull/1503.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/1503 ----==_mimepart_5b36955b2105d_23cb2af6bdc5cf54129420 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Now that unidirectional streams have landed, its easier to spot where this section could be tightened up. I've removed a bit of duplication and reordered text to match ordering of server push (PUSH_PROMISE and then push stream).

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

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

Commit Summary

  • Server push tidy up

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 mute the thread.

----==_mimepart_5b36955b2105d_23cb2af6bdc5cf54129420-- From nobody Fri Jun 29 13:28:14 2018 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 71B46130E0C for ; Fri, 29 Jun 2018 13:28:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vsLQZMreG9v0 for ; Fri, 29 Jun 2018 13:28:11 -0700 (PDT) Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E955A130E8E for ; Fri, 29 Jun 2018 13:28:10 -0700 (PDT) Date: Fri, 29 Jun 2018 13:28:10 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530304090; bh=s+NeieNogl1hlwtJ1U0VhcqvFCBwEHSjZP6h0bFmXzk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kEPDlNQpwqHuIfDfR1enMQ2ckZ43tJShRTGIZeImNikVwy1jr9bspbYGnyoTzr1nh bEZf5RF30y777D0T8/CMaTTVf5lSpDulBH/6ds1JafU9BI+h1NMWEijcUWPcHjOwyP vzittavuACBL2TE/d0F2+ZZHexBYVVCOM1OP1WHs= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36965a4458e_496b2b1aca178f5814857c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: LPardue X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 20:28:13 -0000 ----==_mimepart_5b36965a4458e_496b2b1aca178f5814857c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue pushed 1 commit. c4dba3b My kingdom for an -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1503/files/665cb782f3c6f9abdeb9bd8323a1a83c0140da9a..c4dba3b4419b8fbc0b35be626cd0b2aeb0d0934e ----==_mimepart_5b36965a4458e_496b2b1aca178f5814857c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b36965a4458e_496b2b1aca178f5814857c-- From nobody Fri Jun 29 13:30:47 2018 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 A06FB130E60 for ; Fri, 29 Jun 2018 13:30:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 vABD0SzpiOWs for ; Fri, 29 Jun 2018 13:30: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 2EC2B130E00 for ; Fri, 29 Jun 2018 13:30:45 -0700 (PDT) Date: Fri, 29 Jun 2018 13:30:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530304244; bh=gTJInhrpL0q86b0/sYUOeEqhaEfjxhjfN24ZrQdVTMM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0WO5Wk5MKEeMhW46op53T/8gFcu2NIyYuAWdjt0g8bAwN5vyNJ4vTDjdKK/nQrYl/ IEorFMo9EYNTmt9k3XenftzD9y2z9BK6tlJkp055jfBtKpFQbvBjIiC1X5i/9C3giF xfP94eTgCAFPE2BE48NbnMXagX4qX0wp7YmRvNuE= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3696f45bd95_58033fe0430f0f881164e3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: LPardue X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 20:30:47 -0000 ----==_mimepart_5b3696f45bd95_58033fe0430f0f881164e3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue pushed 1 commit. c4bc704 an online editor that doesn't suck -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1503/files/c4dba3b4419b8fbc0b35be626cd0b2aeb0d0934e..c4bc704a01e99870e06ddda222540a409a460604 ----==_mimepart_5b3696f45bd95_58033fe0430f0f881164e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue pushed 1 commit.

  • c4bc704 an online editor that doesn't suck

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3696f45bd95_58033fe0430f0f881164e3-- From nobody Fri Jun 29 13:36:04 2018 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 CB2F4130EC9 for ; Fri, 29 Jun 2018 13:35:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 jqPoO5E0TlzS for ; Fri, 29 Jun 2018 13:35:50 -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 3F1FA130E94 for ; Fri, 29 Jun 2018 13:35:50 -0700 (PDT) Date: Fri, 29 Jun 2018 13:35:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530304549; bh=4lByH6IqQjiEpLzQxhU8NKRCNaFR+3iMgCkQURXbzOw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yca0b4XBJWpjA/69hlIQsOzOFIvd3eSlb8xoaoUTZ2pIJ1g/D6R+T+17uZRjg8Ran CoYBDbFEpIbQpxwQsHp8YvKzUtT0ZnjScO+UC8WO+A+wXV7Z+eXzedJgUFLm5TP4p7 eWfTiiBN7iKusE3iLVVPZWJe58oXCxBQEi1NSwAg= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36982590632_b313fc7a733af78264537"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: LPardue X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 20:35:55 -0000 ----==_mimepart_5b36982590632_b313fc7a733af78264537 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue pushed 1 commit. 59a9421 80 wasn't enough for me -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1503/files/c4bc704a01e99870e06ddda222540a409a460604..59a94215be8d02cb8f378a0286132a10d281329f ----==_mimepart_5b36982590632_b313fc7a733af78264537 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b36982590632_b313fc7a733af78264537-- From nobody Fri Jun 29 13:38:20 2018 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 95B52130F3B for ; Fri, 29 Jun 2018 13:38:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 OY2BmAHSL4HB for ; Fri, 29 Jun 2018 13:38:04 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F23EF130F0D for ; Fri, 29 Jun 2018 13:38:03 -0700 (PDT) Date: Fri, 29 Jun 2018 13:38:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530304683; bh=0NH15Dj19u6KBKkICJtWziIcLNo731ZH0+xCXjNuB8w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=spRWrJQ1tF8nerrx0+ib5fV3A98y1I59wImYz7ShOUaxUzRzfaC947kXb5RFMyjX1 519ndJ/sn/cZriTS76CDVtacYXuyuF8xkTYUuArtlvam8a/xwNv6HpdlvFTiNFdqcQ SjZ6Rwr8YUxBSdRA9/xl4u1Ny+XwqahU/SPE9T3U= From: Lucas Pardue Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Push Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3698ab4b705_496b2b1aca178f581852b4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: LPardue X-GitHub-Recipient: quic-issues X-GitHub-Reason: push 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.26 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: Fri, 29 Jun 2018 20:38:19 -0000 ----==_mimepart_5b3698ab4b705_496b2b1aca178f581852b4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @LPardue pushed 1 commit. 61c5c55 trailing trash -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/quicwg/base-drafts/pull/1503/files/59a94215be8d02cb8f378a0286132a10d281329f..61c5c55aa5bccb1c617c4ed28f2897941bcd19a6 ----==_mimepart_5b3698ab4b705_496b2b1aca178f581852b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@LPardue pushed 1 commit.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5b3698ab4b705_496b2b1aca178f581852b4-- From nobody Fri Jun 29 14:17:43 2018 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 E97831294D7 for ; Fri, 29 Jun 2018 14:17:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.01 X-Spam-Level: X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 KM-tCrnWTQrB for ; Fri, 29 Jun 2018 14:17:39 -0700 (PDT) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 532FA1292F1 for ; Fri, 29 Jun 2018 14:17:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=HoFqL6yKMUrfrLVdXegQU50ED5A=; b=c/MCQas5iwpuy7tu 3mJ7dffajliQhuiL1sbqeDvfybKXGvO86lZpWnMckdCXfFDNlp/u8ErIsFcqmKyW j7Q0f+sazCWbo4Nbfma+8issQfK+Emlv0J0keFujMJy2D4Hv0CYU31DinNJgvqbY 1dWEpzSq/Vd81NBk83XDF/XjbTQ= Received: by filter0161p1iad2.sendgrid.net with SMTP id filter0161p1iad2-16931-5B36A1F1-25 2018-06-29 21:17:37.389324851 +0000 UTC Received: from github-lowworker18-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id V1QIhayXQgSjFjpTbPbYVw for ; Fri, 29 Jun 2018 21:17:37.202 +0000 (UTC) Received: from github.com (localhost [127.0.0.1]) by github-lowworker18-cp1-prd.iad.github.net (Postfix) with ESMTP id 2F01B23CA6 for ; Fri, 29 Jun 2018 14:17:37 -0700 (PDT) Date: Fri, 29 Jun 2018 21:17:37 +0000 (UTC) From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Editorial: initial offsets -> initial limits (#1504) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36a1f12dbb7_2ffb3f9288ddcf84655f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak351+uL8uvoAMrIUciJ1V2S/qo0J9sP95eU4n cVAoENPZ2Nppen1zbuR/03bJ8OUiwES2y7H49txDhuYFy9nhJwKO9hfxsBEVFSQp5Xq97cpER1+UGK kk+nGjUYCnJNZ1CWc1zL3foLTl3HoMCLZ9f/3IuYNFjqlKRnbajzMh7MVIr31RiHu/X4Gb798ngpg+ 0= Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 21:17:41 -0000 ----==_mimepart_5b36a1f12dbb7_2ffb3f9288ddcf84655f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/1504 -- Commit Summary -- * Editorial: initial offsets -> initial limits -- File Changes -- M draft-ietf-quic-transport.md (2) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/1504.patch https://github.com/quicwg/base-drafts/pull/1504.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/1504 ----==_mimepart_5b36a1f12dbb7_2ffb3f9288ddcf84655f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

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

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

Commit Summary

  • Editorial: initial offsets -> initial limits

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 mute the thread.

----==_mimepart_5b36a1f12dbb7_2ffb3f9288ddcf84655f6-- From nobody Fri Jun 29 14:35:37 2018 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 3CFB8130F28 for ; Fri, 29 Jun 2018 14:35:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.249 X-Spam-Level: X-Spam-Status: No, score=-0.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 rpvX0C6DixPl for ; Fri, 29 Jun 2018 14:35:30 -0700 (PDT) Received: from m69-170.mailgun.net (m69-170.mailgun.net [166.78.69.170]) (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 A7119130F04 for ; Fri, 29 Jun 2018 14:35:28 -0700 (PDT) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1530308127; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=exq4JbgTUAu+c+aBijwhpqoAjkIjfuV0cq9E+VGjXUc=; b=GJsoO8xPl8/V9UO+wKk+kJBgf0B6shU7xM1iZLpwqYI9Tnfkk/kykft7gaFu64oiGQh/uDcM ukP+B83+8NwS7RnBf4wABbzIiKyFC2bnknJxKK9POkvTSAXwlojgDMqWtywwwAHI+FJQxDtf OS5g4Cdvomw/hY/WJ+nNgBFqNPo= X-Mailgun-Sending-Ip: 166.78.69.170 X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ== Sender: lucaspardue.24.7=gmail.com@github.com Received: from github.com (Unknown [192.30.252.40]) by mxa.mailgun.org with ESMTP id 5b36a61f.7f5a2a992480-smtp-out-n03; Fri, 29 Jun 2018 21:35:27 -0000 (UTC) Date: Fri, 29 Jun 2018 14:35:26 -0700 From: Lucas Pardue Reply-To: Lucas Pardue To: quic-issues@ietf.org Message-ID: <5b36a61eeb6ad_20692ac8dc8c3c0810459@hookshot-fe-d2afb11.cp1-iad.github.net.mail> Subject: [quicwg/base-drafts] b97ea1: Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="--==_mimepart_5b36a61eeb02f_20692ac8dc8c3c081044c6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 Precedence: list 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: Fri, 29 Jun 2018 21:35:35 -0000 ----==_mimepart_5b36a61eeb02f_20692ac8dc8c3c081044c6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Branch: refs/heads/master Home: https://github.com/quicwg/base-drafts Commit: b97ea1d1884247622623519d5edc50d0665ba2cc https://github.com/quicwg/base-drafts/commit/b97ea1d1884247622623519d5edc50d0665ba2cc Author: Lucas Pardue Date: 2018-06-29 (Fri, 29 Jun 2018) Changed paths: M draft-ietf-quic-http.md Log Message: ----------- Server push tidy up (#1503) * Server push tidy up Removed a bit of duplication. Reordered text to match ordering of server push (PUSH_PROMISE and then push stream). * My kingdom for an * an online editor that doesn't suck * 80 wasn't enough for me * trailing trash **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. ----==_mimepart_5b36a61eeb02f_20692ac8dc8c3c081044c6-- From nobody Fri Jun 29 14:35:43 2018 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 B6557130F26 for ; Fri, 29 Jun 2018 14:35:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 B48qA_269t0d for ; Fri, 29 Jun 2018 14:35:32 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2622130EA8 for ; Fri, 29 Jun 2018 14:35:30 -0700 (PDT) Date: Fri, 29 Jun 2018 14:35:29 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530308129; bh=tm762attqZb74eCzrYgNqB6+NxK0R1ZkYsjLCfSMTzM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZLysituGNP05OXVg4YPvlnQq8J1ftPXQQPvwkmaYyz12HkauN8M+Ygkyx0keNvHTA HDqiLGKJWLN02c526dRDOEM1iuSLfHp8e2wV+lTRHsfFQuCAGt5G6IaxTyZ0NnlqV8 Kkr+wrosJkX3RC1J4jcAPO6oMzzEQBuQcPuEks80= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Server push tidy up (#1503) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36a621775d5_4acc3fec5ff22f8416907b"; 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.26 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: Fri, 29 Jun 2018 21:35:35 -0000 ----==_mimepart_5b36a621775d5_4acc3fec5ff22f8416907b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Merged #1503. -- 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/1503#event-1709575022 ----==_mimepart_5b36a621775d5_4acc3fec5ff22f8416907b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Merged #1503.

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

----==_mimepart_5b36a621775d5_4acc3fec5ff22f8416907b-- From nobody Fri Jun 29 15:06:18 2018 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 B81AB130E28 for ; Fri, 29 Jun 2018 15:06:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 manHvqqy2zn5 for ; Fri, 29 Jun 2018 15:06:14 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5709130E1B for ; Fri, 29 Jun 2018 15:06:14 -0700 (PDT) Date: Fri, 29 Jun 2018 15:06:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530309973; bh=9syT5ae+3GdQv/SBB7iJvkXiLr4l7RINfrx5ixG9FNU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y/uAHgch5nHqlytHNJSQDewVkoDuitXBJj8SuEF3xtx2gSZa7tD9WcCnp5QNMI9cR 3et6P4F5K39u1RGlyOFXjiQYemwEuA+YlkO72Q1/SazwFKVPBXkriXBKrUC2/AaZGj XhgefmPFWM+mBsdA9DdQbUmw3NjGoZav93WUobLc= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36ad55670db_51bf2af68b410f581770d2"; 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.26 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: Fri, 29 Jun 2018 22:06:17 -0000 ----==_mimepart_5b36ad55670db_51bf2af68b410f581770d2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit MikeBishop commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older I'm surprised at throwing the path away. I'd think there are separate criteria to throw away a path, independent of needing new CIDs. Still, I can see where a reasonable implementation might get into a state where it's always discarding a single CID at a time and perhaps wanting to discard CIDs non-contiguously. Perhaps this is a question to discuss on-list, rather than in a PR comment? -- 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/1496#discussion_r199291098 ----==_mimepart_5b36ad55670db_51bf2af68b410f581770d2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@MikeBishop commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

I'm surprised at throwing the path away. I'd think there are separate criteria to throw away a path, independent of needing new CIDs. Still, I can see where a reasonable implementation might get into a state where it's always discarding a single CID at a time and perhaps wanting to discard CIDs non-contiguously.

Perhaps this is a question to discuss on-list, rather than in a PR comment?

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

----==_mimepart_5b36ad55670db_51bf2af68b410f581770d2-- From nobody Fri Jun 29 15:09:24 2018 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 79059130F41 for ; Fri, 29 Jun 2018 15:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 nUzvUelxkEw1 for ; Fri, 29 Jun 2018 15:09:13 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCB82130ED1 for ; Fri, 29 Jun 2018 15:09:13 -0700 (PDT) Date: Fri, 29 Jun 2018 15:09:13 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530310153; bh=uZ3dQCfOAKO3SN/fUBcLCAL4hpnnmH4r96utVnx1FUk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oBi62fD3r9Py2Ggmq7ZPlYBN2vQgL7R01CfOnj+FLXPFFPf1fbHekCyd2KMc9jbGU m4/NGiNTKgpCxs/qJreMFyfK4VhGSuCRgBMZB2PEfWfKMFkhkPceZje8cYISGJAny5 FXl3/GUGNlJUlUfGDzUuqUfuU6aIYU5EKmwR6Rws= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] CID Lifetime Management (#1496) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36ae094fdb3_4aae2b2388500f60615a5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Fri, 29 Jun 2018 22:09:21 -0000 ----==_mimepart_5b36ae094fdb3_4aae2b2388500f60615a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit nibanks commented on this pull request. > + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| Sequence (i) ... ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +~~~ + +The fields in the RETIRE_CONNECTION_ID frame are as follows: + +Sequence: +: Sequence number of the oldest connection ID issued by the sender which the + sender will still recognize as associated with the current connection. The + sequence number is formatted as a variable-length integer. + +Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider +connection IDs older than the specified sequence number as unusable and MUST NOT +consider the associated stateless reset tokens to be valid. If an older I agree that we can follow up on the migration logic separate from this discussion. For this PR though, I don't think we should use a window style for CIDs. I think it restricts implementations from doing other things. -- 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/1496#discussion_r199291549 ----==_mimepart_5b36ae094fdb3_4aae2b2388500f60615a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@nibanks commented on this pull request.

In draft-ietf-quic-transport.md:

> + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+|                         Sequence (i)                        ...
++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+~~~
+
+The fields in the RETIRE_CONNECTION_ID frame are as follows:
+
+Sequence:
+: Sequence number of the oldest connection ID issued by the sender which the
+  sender will still recognize as associated with the current connection. The
+  sequence number is formatted as a variable-length integer.
+
+Upon receipt of a RETIRE_CONNECTION_ID frame, an endpoint MUST consider
+connection IDs older than the specified sequence number as unusable and MUST NOT
+consider the associated stateless reset tokens to be valid. If an older

I agree that we can follow up on the migration logic separate from this discussion. For this PR though, I don't think we should use a window style for CIDs. I think it restricts implementations from doing other things.

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

----==_mimepart_5b36ae094fdb3_4aae2b2388500f60615a5-- From nobody Fri Jun 29 15:13:07 2018 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 D224E130F56 for ; Fri, 29 Jun 2018 15:12:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 O0GDY587ei4v for ; Fri, 29 Jun 2018 15:12:44 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A37EE130E31 for ; Fri, 29 Jun 2018 15:12:44 -0700 (PDT) Date: Fri, 29 Jun 2018 15:12:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530310362; bh=yI0CHrJ22jYk4+loI2qnYF+vZBamMSugzOQBpcIw6+I=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=07zfC0bHOmeXLMPRDIlPj9zt8em+ZdbUgiSNJlDuPDFuD7kkREqZDWoLCAiXcPT1z ZbfK/RbuWeYtr3WjCBiCeeHkRfDSy50xsQ1V/uWPxK2IQQM5C5hhlfOR+PBU5fe8+m 9LZxrYD+iuJWixl2VgluzmAI6H/dyEroeofKU/kw= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Stateless Reset from clients, bis (#1505) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36aedae4573_401d3fbbb4c5af8010382e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Fri, 29 Jun 2018 22:13:05 -0000 ----==_mimepart_5b36aedae4573_401d3fbbb4c5af8010382e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In #466, we left it as the client cannot use Stateless Reset, until the server starts to use to a CID provided by the client's NEW_CONNECTION_ID. (Something that is actually not stated explicitly in the draft.) This is certainly not great, hence this issue. To fix this, I can think of a few alternatives: 1. A new frame that provides the initial Stateless Reset Token from the client. It only applies to the initial CID (important to note, since you do not want it to override the token from a subsequent NEW_CONNECTION_ID in case of reordering). 2. If NEW_CONNECTION_ID frame is received from the client with Seq=0 and Length=0, it provides the initial Stateless Reset Token (and is considered to be Seq=-1, so the next NEW_CONNECTION_ID would actually be Seq=0). I do not love this and would prefer just a new frame. -- 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/1505 ----==_mimepart_5b36aedae4573_401d3fbbb4c5af8010382e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In #466, we left it as the client cannot use Stateless Reset, until the server starts to use to a CID provided by the client's NEW_CONNECTION_ID. (Something that is actually not stated explicitly in the draft.)

This is certainly not great, hence this issue.

To fix this, I can think of a few alternatives:

  1. A new frame that provides the initial Stateless Reset Token from the client. It only applies to the initial CID (important to note, since you do not want it to override the token from a subsequent NEW_CONNECTION_ID in case of reordering).
  2. If NEW_CONNECTION_ID frame is received from the client with Seq=0 and Length=0, it provides the initial Stateless Reset Token (and is considered to be Seq=-1, so the next NEW_CONNECTION_ID would actually be Seq=0). I do not love this and would prefer just a new frame.

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

----==_mimepart_5b36aedae4573_401d3fbbb4c5af8010382e-- From nobody Fri Jun 29 15:22:20 2018 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 040A9130E29 for ; Fri, 29 Jun 2018 15:22:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 DwBST5vWoc5F for ; Fri, 29 Jun 2018 15:22:17 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C90C9130E5E for ; Fri, 29 Jun 2018 15:22:17 -0700 (PDT) Date: Fri, 29 Jun 2018 15:22:17 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530310937; bh=ZihrpXXNCNnNEdO5yiBt2Vjs1hplwOgA1OLslpzOvJo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VjjmNQMJbW0QE7MI7FtBbQ0sAL8bPqdcP663qBJRkYt4TSeIpTszBUn2jws4iBaW3 Zs/gD0b6hYEYj4kYFKD3gDG25rWTi3qQdm3XPkKJBNcka2FLgXY+Y4LhUPaO2rwKXd jhGT4KFLuyYb+5rD1xKXqxVyE6Cl8AbJJIUzTd64= From: hardie Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#1505) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36b119ac8a_2a72b0640dd2f541275dc"; 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 Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 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: Fri, 29 Jun 2018 22:22:20 -0000 ----==_mimepart_5b36b119ac8a_2a72b0640dd2f541275dc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Igor, I think I'm a little confused. Some questions in-line. On Fri, Jun 29, 2018 at 3:12 PM, Igor Lubashev = wrote: > In #466 , we left it = as > the client cannot use Stateless Reset, until the server starts to use t= o a > CID provided by the client's NEW_CONNECTION_ID. (Something that is actu= ally > not stated explicitly in the draft.) > > This is certainly not great, hence this issue. > > To fix this, I can think of a few alternatives: > > 1. A new frame that provides the initial Stateless Reset Token from > the client. It only applies to the initial CID (important to note, s= ince > you do not want it to override the token from a subsequent > NEW_CONNECTION_ID in case of reordering). > > If the purpose of Stateless Reset is to abruptly tear down a connection= , I'm not sure what the re-ordering issue is. Sending a Stateless Reset an= d then sending more traffic on that connection seems odd. Similarly, if th= e client needs to know whether data already sent has been received, it seem= s like it either has to wait until that data is acknowledged and/or use a graceful shutdown. I don't seen how a reset matches this--what am I missing? > > 1. If NEW_CONNECTION_ID frame is received from the client with Seq=3D= 0 > and Length=3D0, it provides the initial Stateless Reset Token (and i= s > considered to be Seq=3D-1, so the next NEW_CONNECTION_ID would actua= lly be > Seq=3D0). I do not love this and would prefer just a new frame. > > =E2=80=94 > I agree that this is not very lovable. Ted > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , or mute the thread= > > . > -- = 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/1505#issuecomment-401488385= ----==_mimepart_5b36b119ac8a_2a72b0640dd2f541275dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Igor,

I think I'm a little confused. Some questions in-line.


On Fri, Jun 29, 2018 at 3:12 PM, Igor Lubashev <notifications@github.c= om>
wrote:

> In #466 <https://github.com/quicwg/base-drafts/issues/466>, we= left it as
> the client cannot use Stateless Reset, until the server starts to us= e to a
> CID provided by the client's NEW_CONNECTION_ID. (Something that = is actually
> not stated explicitly in the draft.)
>
> This is certainly not great, hence this issue.
>
> To fix this, I can think of a few alternatives:
>
> 1. A new frame that provides the initial Stateless Reset Token fr= om
> the client. It only applies to the initial CID (important to note= , since
> you do not want it to override the token from a subsequent
> NEW_CONNECTION_ID in case of reordering).
>
> If the purpose of Stateless Reset is to abruptly tear down a connect= ion,
I'm not sure what the re-ordering issue is. Sending a Stateless Rese= t and
then sending more traffic on that connection seems odd. Similarly, if th= e
client needs to know whether data already sent has been received, it seem= s
like it either has to wait until that data is acknowledged and/or use a graceful shutdown. I don't seen how a reset matches this--what am I<= br> missing?


>
> 1. If NEW_CONNECTION_ID frame is received from the client with Se= q=3D0
> and Length=3D0, it provides the initial Stateless Reset Token (an= d is
> considered to be Seq=3D-1, so the next NEW_CONNECTION_ID would ac= tually be
> Seq=3D0). I do not love this and would prefer just a new frame. >
> =E2=80=94
>
I agree that this is not very lovable.

Ted


> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1505>, or mute t= he thread
> <https://github.com/notifications/unsubscribe-auth/ABVb5BUeQGYOCQ= 9iZVNLKtp0Y_w-WFZNks5uBqZZgaJpZM4U9sIC>
> .
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b36b119ac8a_2a72b0640dd2f541275dc-- From nobody Fri Jun 29 15:32:49 2018 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 22403130E9F for ; Fri, 29 Jun 2018 15:32:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 VXXYlkVNcKgF for ; Fri, 29 Jun 2018 15:32:45 -0700 (PDT) Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F954130E9E for ; Fri, 29 Jun 2018 15:32:45 -0700 (PDT) Date: Fri, 29 Jun 2018 15:32:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530311565; bh=euTUQb9b+tWpdXO9crRz67NiKZY6YaP1HGkf6afjRNw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VDvgnEZymeDqa/Ji8cAwSYdAnazpeBxVdi027iJ7Kz+4sufReMxLsCjMgAUZUzDmm S+W1B7TzvcYnoZLhNKuGqMOMN+tTW4gotEDw7MFjfISnQhqfXY8Uu8XvLY+Ft0XJ0I JIQPOjD5En1hBBvafW3zwf4A3YUIBbPaFCdh/vuA= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#1505) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36b38ce3a87_1f952b08ccae0f60132633"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Fri, 29 Jun 2018 22:32:47 -0000 ----==_mimepart_5b36b38ce3a87_1f952b08ccae0f60132633 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ted, take a look at #466 (closer to the end of the thread). The problem we have right now is that client cannot supply a stateless reset token during handshake, because client's part of the handshake (unlike the server's) is not protected. So the situation we have right now is that clients _cannot_ send a Stateless Reset any time later, until the server has switched to using a new CID from the client, provided by the client in NEW_CONNECTION_ID. (And switching CIDs may never happen.) So the "idea" I am proposing is very simple -- since the client cannot not send its stateless reset token associated with its CID during handshake, let it send that token later (as soon as it starts to send protected packets). -- 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/1505#issuecomment-401490090 ----==_mimepart_5b36b38ce3a87_1f952b08ccae0f60132633 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ted, take a look at #466 (closer to the end of the thread).

The problem we have right now is that client cannot supply a stateless= reset token during handshake, because client's part of the handshake (un= like the server's) is not protected. So the situation we have right now = is that clients cannot send a Stateless Reset any time later, un= til the server has switched to using a new CID from the client, provided = by the client in NEW_CONNECTION_ID. (And switching CIDs may never happen= .)

So the "idea" I am proposing is very simple -- since the client cannot= not send its stateless reset token associated with its CID during handsh= ake, let it send that token later (as soon as it starts to send protected= packets).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b36b38ce3a87_1f952b08ccae0f60132633-- From nobody Fri Jun 29 16:16:07 2018 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 D664C130E16 for ; Fri, 29 Jun 2018 16:16:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 H7X0b2LDxlU4 for ; Fri, 29 Jun 2018 16:16:03 -0700 (PDT) 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 37AFD130E2A for ; Fri, 29 Jun 2018 16:16:03 -0700 (PDT) Date: Fri, 29 Jun 2018 16:16:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530314162; bh=RDA440N16192HA1h28sB/1vrOZtEERy8pNWMLPQdaJ8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sHggcz/qcMUtXJx2erU3IwJH7hqoKh5dnWHSR+QUWPkz6k/bDlNuuHdKERbI5dbbz Z0UW9zbuhq+2Uqjv+HLxO4Pi6IueIpyx/SvS+kXjzbawiFqoFlNjCWvB/Q6Eiqw+zs Oid3Ucjl+l5s47PdHEWnN6YOso2xLmvTf4Uc9qDs= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#1505) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36bdb264a7d_2bbf3f9496b22f7c118826"; 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.26 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: Fri, 29 Jun 2018 23:16:06 -0000 ----==_mimepart_5b36bdb264a7d_2bbf3f9496b22f7c118826 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The reordering isn=E2=80=99t with the Stateless Reset itself. The server= doesn=E2=80=99t know, during the handshake, what SRT goes with the clien= t=E2=80=99s chosen CID. Igor is looking for a way the server could acqui= re this information, so that a Stateless Reset subsequently sent by the c= lient can be recognized. The first option is a separate frame type that supplies the SRT for a CID= that the server already has. But due to reordering, that might no longe= r be the CID in use when the server receives it, so the server needs to b= e careful not to overwrite the SRT it already possesses for the new CID. = Frankly, this just seems like a bug on the server implementer=E2=80=99s = part, albeit one it might be worth cautioning them against. The second becomes more palatable if the outcome of #1484 is that you can= express the sequence number of the initial handshake CID in a NEW_CONNEC= TION_ID frame; the client could simply re-send that CID as if it were new= , but including the SRT this time. From: hardie [mailto:notifications@github.com] Sent: Friday, June 29, 2018 3:22 PM To: quicwg/base-drafts Cc: Subscribed Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#150= 5) Hi Igor, I think I'm a little confused. Some questions in-line. On Fri, Jun 29, 2018 at 3:12 PM, Igor Lubashev = wrote: > In #466 , we left it = as > the client cannot use Stateless Reset, until the server starts to use t= o a > CID provided by the client's NEW_CONNECTION_ID. (Something that is actu= ally > not stated explicitly in the draft.) > > This is certainly not great, hence this issue. > > To fix this, I can think of a few alternatives: > > 1. A new frame that provides the initial Stateless Reset Token from > the client. It only applies to the initial CID (important to note, sinc= e > you do not want it to override the token from a subsequent > NEW_CONNECTION_ID in case of reordering). > > If the purpose of Stateless Reset is to abruptly tear down a connection= , I'm not sure what the re-ordering issue is. Sending a Stateless Reset and= then sending more traffic on that connection seems odd. Similarly, if the= client needs to know whether data already sent has been received, it seem= s like it either has to wait until that data is acknowledged and/or use a graceful shutdown. I don't seen how a reset matches this--what am I missing? > > 1. If NEW_CONNECTION_ID frame is received from the client with Seq=3D0 > and Length=3D0, it provides the initial Stateless Reset Token (and is > considered to be Seq=3D-1, so the next NEW_CONNECTION_ID would actually= be > Seq=3D0). I do not love this and would prefer just a new frame. > > =E2=80=94 > I agree that this is not very lovable. Ted > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , or mute the thread= > > . > =E2=80=94 You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. -- = 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/1505#issuecomment-401496309= ----==_mimepart_5b36bdb264a7d_2bbf3f9496b22f7c118826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The reordering isn=E2=80=99t with the Stateless Reset itself. The server= doesn=E2=80=99t know, during the handshake, what SRT goes with the clien= t=E2=80=99s chosen CID. Igor is looking for a way the server could acqui= re this information, so that a Stateless Reset subsequently sent by the c= lient can be recognized.

The first option is a separate frame type that supplies the SRT for a CID= that the server already has. But due to reordering, that might no longe= r be the CID in use when the server receives it, so the server needs to b= e careful not to overwrite the SRT it already possesses for the new CID. = Frankly, this just seems like a bug on the server implementer=E2=80=99s = part, albeit one it might be worth cautioning them against.

The second becomes more palatable if the outcome of #1484 is that you can= express the sequence number of the initial handshake CID in a NEW_CONNEC= TION_ID frame; the client could simply re-send that CID as if it were new= , but including the SRT this time.

From: hardie [mailto:notifications@github.com]
Sent: Friday, June 29, 2018 3:22 PM
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#150= 5)

Hi Igor,

I think I'm a little confused. Some questions in-line.


On Fri, Jun 29, 2018 at 3:12 PM, Igor Lubashev <notifications@github.c= om>
wrote:

> In #466 <https://github.com/quicwg/base-drafts/issues/466>, we= left it as
> the client cannot use Stateless Reset, until the server starts to us= e to a
> CID provided by the client's NEW_CONNECTION_ID. (Something that = is actually
> not stated explicitly in the draft.)
>
> This is certainly not great, hence this issue.
>
> To fix this, I can think of a few alternatives:
>
> 1. A new frame that provides the initial Stateless Reset Token from
> the client. It only applies to the initial CID (important to note, s= ince
> you do not want it to override the token from a subsequent
> NEW_CONNECTION_ID in case of reordering).
>
> If the purpose of Stateless Reset is to abruptly tear down a connect= ion,
I'm not sure what the re-ordering issue is. Sending a Stateless Reset= and
then sending more traffic on that connection seems odd. Similarly, if the=
client needs to know whether data already sent has been received, it seem= s
like it either has to wait until that data is acknowledged and/or use a
graceful shutdown. I don't seen how a reset matches this--what am I
missing?


>
> 1. If NEW_CONNECTION_ID frame is received from the client with Seq=3D= 0
> and Length=3D0, it provides the initial Stateless Reset Token (and i= s
> considered to be Seq=3D-1, so the next NEW_CONNECTION_ID would actua= lly be
> Seq=3D0). I do not love this and would prefer just a new frame.
>
> =E2=80=94
>
I agree that this is not very lovable.

Ted


> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1505>, or mute t= he thread
> <https://github.com/notifications/unsubscribe-auth/ABVb5BUeQGYOCQ= 9iZVNLKtp0Y_w-WFZNks5uBqZZgaJpZM4U9sIC>
> .
>


=E2=80=94
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/qui= cwg/base-drafts/issues/1505#issuecomment-401488385>, or mute the threa= d<https://github.com/notifications/unsubscribe-auth/AEE2hSnrCgDe_HW-qY= 5pKgf5D6dc4T3qks5uBqiYgaJpZM4U9sIC>.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b36bdb264a7d_2bbf3f9496b22f7c118826-- From nobody Fri Jun 29 16:28:49 2018 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 71D10130EB8 for ; Fri, 29 Jun 2018 16:28:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 HKavhxrJsj9r for ; Fri, 29 Jun 2018 16:28:45 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2FE3130E9F for ; Fri, 29 Jun 2018 16:28:45 -0700 (PDT) Date: Fri, 29 Jun 2018 16:28:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530314924; bh=Khoe3pKuGGgqW8vN+2M22FyxR6auHif1hhNJN7+6jVY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j0zrNWl4zy5IwG3h7+W6Cb1e7hM1HNIXBnFaj59gM/vTy1OawNKudduE7Y1z5cmla uuJOTHl5tTo8+rgEKvl37PsK6vPJL/ebkaTX4+8tzEP0aYo/ZpN76unx7/US6IR7uE Jt5QeYGzLlP3bgA22CWdR7RaS94qRHxjWpwltNXI= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Stateless Reset from clients, bis (#1505) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36c0accca37_261c63f8706476f7c733f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Fri, 29 Jun 2018 23:28:48 -0000 ----==_mimepart_5b36c0accca37_261c63f8706476f7c733f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, if #1484 assigns number 0 to the client's initial CID, then the simplest way to implement this is to just repeat CID 0 in NEW_CONNECTION_ID frame. Some care would be needed to decide whether CID 0 in NEW_CONNECTION_ID can be different from the client's initial CID, or that's an error. (Len=0 there could be an optimization or be considered an unnecessary complication). -- 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/1505#issuecomment-401497887 ----==_mimepart_5b36c0accca37_261c63f8706476f7c733f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, if #148= 4 assigns number 0 to the client's initial CID, then the simplest way= to implement this is to just repeat CID 0 in NEW_CONNECTION_ID frame. S= ome care would be needed to decide whether CID 0 in NEW_CONNECTION_ID can= be different from the client's initial CID, or that's an error. (Len=3D= 0 there could be an optimization or be considered an unnecessary complica= tion).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b36c0accca37_261c63f8706476f7c733f8-- From nobody Fri Jun 29 17:12:39 2018 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 EA6A4130F04 for ; Fri, 29 Jun 2018 17:12:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 DtYHzWGvVtn9 for ; Fri, 29 Jun 2018 17:12:36 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1A83130E2C for ; Fri, 29 Jun 2018 17:12:36 -0700 (PDT) Date: Fri, 29 Jun 2018 17:12:35 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530317555; bh=y3oQnJCdk04fcQd3Sy+5ksNNU2xMU21rr6yKA5HEKBc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=SuODu8NNvFycR8mRC836elu6Y9LplI1huWFIVOQkhbFGJeXU8oOvK/f6aLu1O2vfy yoNkWU5zejFsVhWBzEto1nbEEvCA+gQ+i8nCfTgg2vj5PAE72gMOII6smCJswsDT7o 71xaradTKuKNO2xWJw8PE1Ru/rhhDa8Rlj80FNU0= From: Rui Paulo Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] HTTP Security Considerations (#1506) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36caf3b13ee_7e562ae94e378f5430349"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: rpaulo 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.26 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: Sat, 30 Jun 2018 00:12:39 -0000 ----==_mimepart_5b36caf3b13ee_7e562ae94e378f5430349 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think the HTTP draft should refer to RFC 7838's Security Considerations, specifically section 2.1 and the attack described in section 9.2. -- 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/1506 ----==_mimepart_5b36caf3b13ee_7e562ae94e378f5430349 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think the HTTP draft should refer to RFC 7838's Security Considerations, specifically section 2.1 and the attack described in section 9.2.

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

----==_mimepart_5b36caf3b13ee_7e562ae94e378f5430349-- From nobody Fri Jun 29 17:26:53 2018 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 D8098130E3A for ; Fri, 29 Jun 2018 17:26:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oqRq8eRwXgZ2 for ; Fri, 29 Jun 2018 17:26:50 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF9C130E2C for ; Fri, 29 Jun 2018 17:26:50 -0700 (PDT) Date: Fri, 29 Jun 2018 17:26:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530318408; bh=/gbeNGJ3Ha9PF+x+BOxsebaXjevRHtQUgTNXbXVBOf0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=V9dcx8fjf4eDWJ9WWss34iAFwJ7wFXvfBHGVrSIR9E5haL/HEDUPvJw3fe07tWss7 ImkP7RrDipuLsc0zZfUyfeJBkASkrRaYGjRYaDX5CpVQf1d5dFheyf1gTns5WscdY5 mMr9nuSPVkjwDbLapMlXYbnyVJYX0F0Cg/uP6XDk= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36ce486362e_2d302ad557cdcf608794c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho 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.26 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: Sat, 30 Jun 2018 00:26:53 -0000 ----==_mimepart_5b36ce486362e_2d302ad557cdcf608794c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In previous drafts (up to -12), use of 0-RTT was forbidden when the server sends a Retry (due to the restriction of TLS 1.3). The restriction no longer exists in -13, most likely due to the fact that retry no longer involves a TLS handshake that had that restriction. Hence the question: is a client allowed to send 0-RTT data when receiving a Retry? My view is that, while there is no need to prohibit that, we should state that: * servers might want to reject 0-RTT when under attack, because it is an useful tool for an attacker to consume server CPU / memory (one example of such an attack is to send a copy of ClientHello and 0-RTT data containing idempotent HTTP requests) * clients are recommended to NOT send 0-RTT data after seeing a Retry packet because it is a sign of server being under an attack, though such a server _might_ still accept 0-RTT data that has been sent relates to: #1498 -- 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/1507 ----==_mimepart_5b36ce486362e_2d302ad557cdcf608794c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In previous drafts (up to -12), use of 0-RTT was forbidden when the server sends a Retry (due to the restriction of TLS 1.3). The restriction no longer exists in -13, most likely due to the fact that retry no longer involves a TLS handshake that had that restriction.

Hence the question: is a client allowed to send 0-RTT data when receiving a Retry?

My view is that, while there is no need to prohibit that, we should state that:

  • servers might want to reject 0-RTT when under attack, because it is an useful tool for an attacker to consume server CPU / memory (one example of such an attack is to send a copy of ClientHello and 0-RTT data containing idempotent HTTP requests)
  • clients are recommended to NOT send 0-RTT data after seeing a Retry packet because it is a sign of server being under an attack, though such a server might still accept 0-RTT data that has been sent

relates to: #1498

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

----==_mimepart_5b36ce486362e_2d302ad557cdcf608794c-- From nobody Fri Jun 29 18:11:07 2018 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 206CA130F93 for ; Fri, 29 Jun 2018 18:11:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 8qfeLk_TYA3O for ; Fri, 29 Jun 2018 18:11:02 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC16130F88 for ; Fri, 29 Jun 2018 18:11:01 -0700 (PDT) Date: Fri, 29 Jun 2018 18:11:00 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530321060; bh=i/mTkxM3XKcJvZFyGZklrVwYJurr5DFfpVDrLfY4yBk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WexARJ4Pa/7h7nzY9Ql+6NALPI+E9Oh+wpsvosrsRkX0cCRI//alIEr/fiFg/l+7S pB1sbAmLMoa9ElfTQa9G7hpYTv1xp3dp2XgXDxBeL8PVG3L1Dyifi3afWQbTxhDqsb 8u7dJN17PVSnfVLbgcAm0u8ciVhxC2T6HJmSvKVg= From: Nick Banks Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b36d8a4b403f_253003fa78fde8f8426264"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: nibanks 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.26 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: Sat, 30 Jun 2018 01:11:06 -0000 ----==_mimepart_5b36d8a4b403f_253003fa78fde8f8426264 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think that 0-RTT should be allowed. Generally, DDoS mitigation is just trying to prove source address ownership and then everything should continue as normal, including 0-RTT. I don't think we should have a MUST for the server to support it, but I think we should allow it. -- 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/1507#issuecomment-401507288 ----==_mimepart_5b36d8a4b403f_253003fa78fde8f8426264 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think that 0-RTT should be allowed. Generally, DDoS mitigation is just trying to prove source address ownership and then everything should continue as normal, including 0-RTT. I don't think we should have a MUST for the server to support it, but I think we should allow it.

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

----==_mimepart_5b36d8a4b403f_253003fa78fde8f8426264-- From nobody Fri Jun 29 21:09:39 2018 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 2401B130EE5 for ; Fri, 29 Jun 2018 21:09:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ofVAtU_WVbC6 for ; Fri, 29 Jun 2018 21:09:34 -0700 (PDT) Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5408E130EC2 for ; Fri, 29 Jun 2018 21:09:34 -0700 (PDT) Date: Fri, 29 Jun 2018 21:09:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530331773; bh=YeCuDOOkg3mCaxVw8eTLU9Ch2kPS5ZZ36DXSTBojQA4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HcFFdN3Ngqtjy6X3qcz5uygONmcnVHUiGwtJn7qCLKyPPKbHf4e7+ulbqqsmiLj6n B/NAumCSfkOHRDg5djZBneeAHbiGGbK4T5jG5hEOLIBoWU/wg9d3KQ87UmvxP65D7e RLNls6PW2J0RlSFPHeROfIpM1JgcB/e8U3sQFUP8= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Can a client send 0-RTT data when receiving Retry? (#1507) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b37027d58cdb_417f2b19c9e90f5871255"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr 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.26 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: Sat, 30 Jun 2018 04:09:37 -0000 ----==_mimepart_5b37027d58cdb_417f2b19c9e90f5871255 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think the client should be allowed to send 0-RTT. I wonder if we should have a field in the Retry that says "don't send 0-RTT". Of course, you'd want to somehow protect that, which would be a pain -- 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/1507#issuecomment-401515661 ----==_mimepart_5b37027d58cdb_417f2b19c9e90f5871255 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I think the client should be allowed to send 0-RTT.

I wonder if we should have a field in the Retry that says "don't send 0-RTT". Of course, you'd want to somehow protect that, which would be a pain

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

----==_mimepart_5b37027d58cdb_417f2b19c9e90f5871255-- From nobody Fri Jun 29 21:46:57 2018 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 99BA2130E58 for ; Fri, 29 Jun 2018 21:46:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 M5WiP93vgFIt for ; Fri, 29 Jun 2018 21:46:53 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 113BB130E53 for ; Fri, 29 Jun 2018 21:46:53 -0700 (PDT) Date: Fri, 29 Jun 2018 21:46:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530334011; bh=5hdi33toUD8CQV227ZoeKID0C4775mak+77HuB5eQi4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Ag0nLhATmm/E2jtFzsSo51Wp3E8xF70aAfG5IWjrZirVhn6jfrzv10u49Y86Qlsyy dH9lOE331UJunxAkDDGhsRzaKX51Yj16IBQBVotD4zdUgeZaLxE/D4CvcYDsXgLQUg li0cga5cX5pMiTO0NNLzvSrfUyBWHrHzuG6o/S5I= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Frame type field in APPLICATION_CLOSE (#1508) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b370b3bd30ae_47003fbd642f6f781036c8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Sat, 30 Jun 2018 04:46:56 -0000 ----==_mimepart_5b370b3bd30ae_47003fbd642f6f781036c8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I would like to see some guidance on how to set Frame Type in APPLICATION_CLOSE. If this field should always be set to "unknown", it probably should not exist in APPLICATION_CLOSE. -- 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/1508 ----==_mimepart_5b370b3bd30ae_47003fbd642f6f781036c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I would like to see some guidance on how to set Frame Type in APPLICATION_CLOSE. If this field should always be set to "unknown", it probably should not exist in APPLICATION_CLOSE.

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

----==_mimepart_5b370b3bd30ae_47003fbd642f6f781036c8-- From nobody Sat Jun 30 01:10:33 2018 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 0FF1F130EF0 for ; Sat, 30 Jun 2018 01:10:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 wkPtOZ1mVrWl for ; Sat, 30 Jun 2018 01:10:30 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52A9D130EE3 for ; Sat, 30 Jun 2018 01:10:30 -0700 (PDT) Date: Sat, 30 Jun 2018 01:10:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530346228; bh=Wqi632bXzRKcrCiDfJT5YzuhXHhNFWl2y+rSN5tKpSg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tCrXZLa8opJPMj2Bv7nozlNMOJuMbuMjglQ4vtggvE5Ghde2pz8PtjaEcZbK1j78D l5FAzR/kEQR+BMnoywQUTnZdwOPI0ZjfLhPe6bsF+SAppcgS/bcOCDOKyfi6RCW4jd tGoS1zsNoCLOpO2ewOqPvgo+pT4H2HehXlrI/FU8= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b373af46a43c_241e3faaa7a4af8811432"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair 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.26 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: Sat, 30 Jun 2018 08:10:32 -0000 ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just to be sure myself .. how does that help a QUIC sender to process a = PTB ICMP message? Gorry = > On 29 Jun 2018, at 21:15, Igor Lubashev wrot= e: > = > ICMP and Load Balancers is a generic problem, but QUIC has some protoco= l elements specifically designed to help load balancers (Server CID). It = stands to reason that enable those protocol elements to help with ICMP pr= ocessing in QUIC context. > = > @martinduke, which workarounds do you have in mind (unless it is PLPMTU= D)? PLPMTUD, for example, specifically states that it works most efficien= tly with ICMP. So this issue is about enabling ICMP to for for PMTU in th= e presence of load balancers. > = > =E2=80=94 > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. -- = 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/1243#issuecomment-401525861= ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just to be sure myself .. how does that help a QUIC sender to process a = PTB ICMP message?

Gorry

> On 29 Jun 2018, at 21:15, Igor Lubashev <notifications@github.com= > wrote:
>
> ICMP and Load Balancers is a generic problem, but QUIC has some prot= ocol elements specifically designed to help load balancers (Server CID). = It stands to reason that enable those protocol elements to help with ICMP= processing in QUIC context.
>
> @martinduke, which workarounds do you have in mind (unless it is PLP= MTUD)? PLPMTUD, for example, specifically states that it works most effic= iently with ICMP. So this issue is about enabling ICMP to for for PMTU in= the presence of load balancers.
>
> =E2=80=94
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432-- From nobody Sat Jun 30 04:41:58 2018 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 234DC13109F for ; Sat, 30 Jun 2018 04:41:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 dPP81BRBlCsq for ; Sat, 30 Jun 2018 04:41:54 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54E6D131094 for ; Sat, 30 Jun 2018 04:41:54 -0700 (PDT) Date: Sat, 30 Jun 2018 04:41:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530358913; bh=sXIe1O8e3bXPyP7Q+Sl/CTkraKoK9VCsBF9IhtMGRhU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HZxV2vvzc+lFbFAFh4hdSYW27fEzCfqc9A+xShzF+/CHFi8q85lYQsFvldayacr/v 35rh9EClmYfw6R1VrEpD3NFVleV3tkvUgmgE2Z+/CM2JBDS3NB24DX967oxJ0Qo7s9 7jxCF5qNOmGIqRYYtg5QaO+p4RUfmQOpGM6Lrk2U= From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Frame type field in APPLICATION_CLOSE (#1508) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b376c8174683_4ce82aabe3b10f5877032"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ianswett 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.26 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: Sat, 30 Jun 2018 11:41:57 -0000 ----==_mimepart_5b376c8174683_4ce82aabe3b10f5877032 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit My intuition is this doesn't belong in APPLICATION_CLOSE, only CONNECTION_CLOSE. -- 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/1508#issuecomment-401535802 ----==_mimepart_5b376c8174683_4ce82aabe3b10f5877032 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

My intuition is this doesn't belong in APPLICATION_CLOSE, only CONNECTION_CLOSE.

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

----==_mimepart_5b376c8174683_4ce82aabe3b10f5877032-- From nobody Sat Jun 30 05:49:09 2018 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 875911310A9 for ; Sat, 30 Jun 2018 05:49:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 UY9vBcdcswuF for ; Sat, 30 Jun 2018 05:49:06 -0700 (PDT) Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4965F130DFA for ; Sat, 30 Jun 2018 05:49:06 -0700 (PDT) Date: Sat, 30 Jun 2018 05:49:05 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530362945; bh=DXa4hsQKlykxmEBlWvDSeAJqP1XxCqwxXVEsK/qKwpQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1udtF3dX9OZKKpNb4QXODABI7xgREZT9sMdn80CRimCmMnzcLf3GN/V16fglpcG5W A2m4PbGFWwDqjGzk2oaSV20m1g0KinPziQeSsh/3jjUWR2koQmiVPfFhnW00T0NNVo l1EBDPUCnEBRzlKyXAO/yVks+rdPLPgQBPZR/dy8= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b377c417db54_6feb2b26b247ef60357687"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Sat, 30 Jun 2018 12:49:09 -0000 ----==_mimepart_5b377c417db54_6feb2b26b247ef60357687 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit All ICMPv6 and a growing number of ICMPv4 packets include a few hundred octets of the packet that triggered that ICMP. A QUIC sender can be behind a load balancer that requires a Server CID to route packets to that server (this is what we designed Server CID for). However, short header packets do not contain Server CID. Hence, when doing a PMTUD probe, such servers may need to use something that would ensure the presence of Server CID in the UDP datagram. (I.e. they may want to use this method when sending packets larger than any packet for which they had received an ACK from this path before.) -- 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/1243#issuecomment-401539218 ----==_mimepart_5b377c417db54_6feb2b26b247ef60357687 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

All ICMPv6 and a growing number of ICMPv4 packets include a few hundre= d octets of the packet that triggered that ICMP.

A QUIC sender can be behind a load balancer that requires a Server CID= to route packets to that server (this is what we designed Server CID for= ). However, short header packets do not contain Server CID. Hence, when d= oing a PMTUD probe, such servers may need to use something that would ens= ure the presence of Server CID in the UDP datagram. (I.e. they may want t= o use this method when sending packets larger than any packet for which t= hey had received an ACK from this path before.)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b377c417db54_6feb2b26b247ef60357687-- From nobody Sat Jun 30 06:26:07 2018 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 3187E130E6B for ; Sat, 30 Jun 2018 06:26:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 3Gd-mql2itGM for ; Sat, 30 Jun 2018 06:26:03 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D9C112777C for ; Sat, 30 Jun 2018 06:26:03 -0700 (PDT) Date: Sat, 30 Jun 2018 06:26:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530365162; bh=W7lOC2Q4eFx5n+sPZqqXXbVaUT1z+/g5PdLuNYyLxiw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hsnPxgrfngJAGlmjp4ja3jeb/kJvNd6yiLRZqKQY91V1zNUIe8XHo/i+RGuBCL970 1jerNENjdJHt7cysOi/+jg+CGDybxpf6gQJ570DtZsK8Jvo/0l8hfze6RjS450UkQB CQeZR0Gtn5fGmbTEe2ehp1VVtQnveeY36OWBN02o= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3784eaab997_24d23f9658e98f805899d9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair 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.26 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: Sat, 30 Jun 2018 13:26:06 -0000 ----==_mimepart_5b3784eaab997_24d23f9658e98f805899d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I see, I think this use of the Server CID seems to provide what is = described as the "protocol information in the quoted payload" in 4.3 = (Verification and Use of PTB Messages) of the dplpmtud draft. Gorry On 30/06/2018, 13:49, Igor Lubashev wrote: > > All ICMPv6 and a growing number of ICMPv4 packets include a few = > hundred octets of the packet that triggered that ICMP. > > A QUIC sender can be behind a load balancer that requires a Server CID = > to route packets to that server (this is what we designed Server CID = > for). However, short header packets do not contain Server CID. Hence, = > when doing a PMTUD probe, such servers may need to use something that = > would ensure the presence of Server CID in the UDP datagram. (I.e. = > they may want to use this method when sending packets larger than any = > packet for which they had received an ACK from this path before.) > > =E2=80=94 > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub = > , = > or mute the thread = > . > -- = 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/1243#issuecomment-401541163= ----==_mimepart_5b3784eaab997_24d23f9658e98f805899d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I see, I think this use of the Server CID seems to provide what is
described as the "protocol information in the quoted payload" = in 4.3
(Verification and Use of PTB Messages) of the dplpmtud draft.

Gorry

On 30/06/2018, 13:49, Igor Lubashev wrote:
>
> All ICMPv6 and a growing number of ICMPv4 packets include a few
= > hundred octets of the packet that triggered that ICMP.
>
> A QUIC sender can be behind a load balancer that requires a Server C= ID
> to route packets to that server (this is what we designed Server CID=
> for). However, short header packets do not contain Server CID. Hence= ,
> when doing a PMTUD probe, such servers may need to use something tha= t
> would ensure the presence of Server CID in the UDP datagram. (I.e. <= br> > they may want to use this method when sending packets larger than an= y
> packet for which they had received an ACK from this path before.) >
> =E2=80=94
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1243#issuecomment-4= 01539218>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHC1kp4A2Lo6lj= q1l6k7sYZ7szsMwP0Hks5uB3PBgaJpZM4Sw_fz>.
>

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b3784eaab997_24d23f9658e98f805899d9-- From nobody Sat Jun 30 20:15:37 2018 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 7B4A8130E4A for ; Sat, 30 Jun 2018 20:15:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 2lukee49b7dz for ; Sat, 30 Jun 2018 20:15:34 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEB9C130E42 for ; Sat, 30 Jun 2018 20:15:33 -0700 (PDT) Date: Sat, 30 Jun 2018 20:15:32 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530414932; bh=2Ln64WZoxebQwET0GZpmQlSQv9BOFWz/0qiuDWCj6lo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gozM1E1bO89yRFDbthLPTwG8FbVNapt5jNj4kxl7Tod75Vt9GlzNNnitBsIKdIz4u UR38ucLDAAClGGq/1ftd7K+4GoTJ6rrqP66Btl6XyTAKV3t6o+oFTaf8tzCWaUO0h8 N17uJHK8kCZPrx/UaQ6+sjk/HKE54U6PnJP++qWw= From: Mike Bishop Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Frame type field in APPLICATION_CLOSE (#1508) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b384754beb00_55df3f9a2a3f6f846536b"; 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.26 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: Sun, 01 Jul 2018 03:15:36 -0000 ----==_mimepart_5b384754beb00_55df3f9a2a3f6f846536b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is probably accidental -- the field was added to CONNECTION_CLOSE without consideration that APPLICATION_CLOSE is defined to have an identical payload. Either the payloads have now diverged, or the APPLICATION_CLOSE section should recommend a value. (Probably STREAM or unknown, given that the error is being provoked at the application layer.) -- 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/1508#issuecomment-401580144 ----==_mimepart_5b384754beb00_55df3f9a2a3f6f846536b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This is probably accidental -- the field was added to CONNECTION_CLOSE= without consideration that APPLICATION_CLOSE is defined to have an ident= ical payload. Either the payloads have now diverged, or the APPLICATION_= CLOSE section should recommend a value. (Probably STREAM or unknown, giv= en that the error is being provoked at the application layer.)

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b384754beb00_55df3f9a2a3f6f846536b-- From nobody Sat Jun 30 21:14:53 2018 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 172EE130E0C for ; Sat, 30 Jun 2018 21:14:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.01 X-Spam-Level: X-Spam-Status: No, score=-8.01 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, 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 r-2xGP2BuD93 for ; Sat, 30 Jun 2018 21:14:50 -0700 (PDT) Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71468130E40 for ; Sat, 30 Jun 2018 21:14:50 -0700 (PDT) Date: Sat, 30 Jun 2018 21:14:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530418489; bh=P0VLTSBX0hQz82kruHC4BCSNOrUl+NmexMAkIChgZrM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pxuY/N6d0ohA98COmGC9FdNVGZURCmZJeqTbaEzwMrNpRQ5D6wP3+rncxIuO3gXNZ lZ9BGkPc+CtyMgfVv1KzZLrBM+smcu0mERZImaeW77JhzTnE8fRJEejeVeYLN16gnm B5VmKAWI+D4DPoJLs50eFFdzhQ/MOude4vQExH7E= From: Igor Lubashev Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Frame type field in APPLICATION_CLOSE (#1508) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b38553988772_749f2aee7a7a4f5c121193c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: igorlord 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.26 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: Sun, 01 Jul 2018 04:14:52 -0000 ----==_mimepart_5b38553988772_749f2aee7a7a4f5c121193c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If there is always one value (STREAM or Unknown), this provides no information. (And STREAM could be misleading -- it could be due to RST_STREAM or nothing to do with any stream at all.) -- 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/1508#issuecomment-401581809 ----==_mimepart_5b38553988772_749f2aee7a7a4f5c121193c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

If there is always one value (STREAM or Unknown), this provides no information. (And STREAM could be misleading -- it could be due to RST_STREAM or nothing to do with any stream at all.)

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

----==_mimepart_5b38553988772_749f2aee7a7a4f5c121193c--