Re: [quicwg/base-drafts] Editorial fix for #2479 (#2877)
Martin Thomson <notifications@github.com> Tue, 09 July 2019 02:14 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F361912008A for <quic-issues@ietfa.amsl.com>; Mon, 8 Jul 2019 19:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzuKqi2wqegb for <quic-issues@ietfa.amsl.com>; Mon, 8 Jul 2019 19:14: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 2F960120091 for <quic-issues@ietf.org>; Mon, 8 Jul 2019 19:14:39 -0700 (PDT)
Date: Mon, 08 Jul 2019 19:14:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1562638477; bh=UvIHEANZ4VtAETCQcAMkqn/eY2moT3G4hr3R+yI4qTg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xj+Xx/SBduacPB46x0JTzwy2UmwQm1VwvGgA/y7NVPwFOQHfRuJSwNHzduozcTFfB I12bfSsOGKW4i6qB9m92JaRmhqcsku4yU//8fZhGnRlpupqQAas3tTPhKENi/ox+f9 oZExa8U5WqMbDxZOyBxETS1jX+nMFbBDm5TdVU+s=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7RQUPGLT67IYA5EHN3GEVQ3EVBNHHBXP3RNI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2877/review/259239188@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2877@github.com>
References: <quicwg/base-drafts/pull/2877@github.com>
Subject: Re: [quicwg/base-drafts] Editorial fix for #2479 (#2877)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d23f88d7667d_192b3fa06e6cd95c868256"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/w54Tcc_YNIzc_dACk3WoML_wTwo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 02:14:42 -0000
martinthomson approved this pull request. Suggestions, but this is definitely cleaner. > -integer. The length of the Destination Connection ID (DCIL) occupies the high -bits of the byte and the length of the Source Connection ID (SCIL) occupies the -low bits of the byte. An encoded length of 0 indicates that the connection ID -is also 0 bytes in length. Non-zero encoded lengths are increased by 3 to get -the full length of the connection ID; the final value is therefore either 0 or -between 4 and 18 bytes in length (inclusive). For example, a byte with the -value 0xe0 describes a 17 byte Destination Connection ID and a zero byte Source -Connection ID. - -The connection ID lengths are followed by two connection IDs. The connection -ID associated with the recipient of the packet (the Destination Connection ID) -is followed by the connection ID associated with the sender of the packet (the -Source Connection ID). +The byte contains the length in bytes of the Destination Connection ID (see +{{connection-id}}) field that follows it. This length is encoded as an 8-bit +unsigned integer. The Destination Connection ID field follows the DCI Len ```suggestion unsigned integer. The Destination Connection ID field follows the DCID Len ``` > -bits of the byte and the length of the Source Connection ID (SCIL) occupies the -low bits of the byte. An encoded length of 0 indicates that the connection ID -is also 0 bytes in length. Non-zero encoded lengths are increased by 3 to get -the full length of the connection ID; the final value is therefore either 0 or -between 4 and 18 bytes in length (inclusive). For example, a byte with the -value 0xe0 describes a 17 byte Destination Connection ID and a zero byte Source -Connection ID. - -The connection ID lengths are followed by two connection IDs. The connection -ID associated with the recipient of the packet (the Destination Connection ID) -is followed by the connection ID associated with the sender of the packet (the -Source Connection ID). +The byte contains the length in bytes of the Destination Connection ID (see +{{connection-id}}) field that follows it. This length is encoded as an 8-bit +unsigned integer. The Destination Connection ID field follows the DCI Len +and is between 0 and 255 bytes in length. ```suggestion field and is between 0 and 255 bytes in length. ``` > -value 0xe0 describes a 17 byte Destination Connection ID and a zero byte Source -Connection ID. - -The connection ID lengths are followed by two connection IDs. The connection -ID associated with the recipient of the packet (the Destination Connection ID) -is followed by the connection ID associated with the sender of the packet (the -Source Connection ID). +The byte contains the length in bytes of the Destination Connection ID (see +{{connection-id}}) field that follows it. This length is encoded as an 8-bit +unsigned integer. The Destination Connection ID field follows the DCI Len +and is between 0 and 255 bytes in length. + +The byte following the Source Connection ID contains the length in bytes +of the Source Connection ID field that follows it. This length is encoded as +a 8-bit unsigned integer. The Source Connection ID field follows the SCID Len +and is between 0 and 255 bytes in length. ```suggestion field and is between 0 and 255 bytes in length. ``` > @@ -3503,16 +3503,13 @@ Version: DCID Len: -: The byte following the version contains the lengths of the two connection ID - fields that follow it. These lengths are encoded as two 4-bit unsigned - integers. The Destination Connection ID Length (DCIL) field occupies the 4 - high bits of the byte and the Source Connection ID Length (SCIL) field - occupies the 4 low bits of the byte. An encoded length of 0 indicates that - the connection ID is also 0 bytes in length. Non-zero encoded lengths are - increased by 3 to get the full length of the connection ID, producing a length - between 4 and 18 bytes inclusive. For example, a byte with the value 0x50 - describes an 8-byte Destination Connection ID and a zero-length Source - Connection ID. +: The byte following the version contains the length in bytes of the Destination + Connection ID field that follows it. This length is encoded as an 8-bit + unsigned integer. In QUIC version 1, this value MUST NOT exceed 20 bytes. ```suggestion unsigned integer. In QUIC version 1, this value MUST NOT exceed 20. ``` Using "bytes" here, while correct, implies that the length of this field is what is being limited. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/pull/2877#pullrequestreview-259239188
- [quicwg/base-drafts] Editorial fix for #2479 (#28… ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … Martin Thomson
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … Martin Thomson
- Re: [quicwg/base-drafts] Editorial fix for #2479 … ianswett
- Re: [quicwg/base-drafts] Editorial fix for #2479 … Jana Iyengar
- Re: [quicwg/base-drafts] Editorial fix for #2479 … Martin Thomson
- Re: [quicwg/base-drafts] Editorial fix for #2479 … Martin Thomson