Re: [quicwg/base-drafts] Clarify Connection ID and Version number endianness (#786)
janaiyengar <notifications@github.com> Thu, 21 September 2017 21:42 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 5F1C0133221 for <quic-issues@ietfa.amsl.com>; Thu, 21 Sep 2017 14:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.381
X-Spam-Level:
X-Spam-Status: No, score=-5.381 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCJeJIIe9Is4 for <quic-issues@ietfa.amsl.com>; Thu, 21 Sep 2017 14:42:21 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [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 E1C091331FF for <quic-issues@ietf.org>; Thu, 21 Sep 2017 14:42:20 -0700 (PDT)
Date: Thu, 21 Sep 2017 14:42:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506030140; bh=z7Tg5DzmflXih0IegKSnsFKBkwXXMkTh2dpkRwvecOY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rmQ9yuYcKQAZZCVJTNBpjq/un6rnOgyJ9hdizE0wILzNXEop7cu9OhXvlF4OsbaZf rqu8ycdZzLETY4wRhket6wk7doUvHf3Wh2S7c4NPTyQB6r7JQmalZnZ5vvoEnNtq2p lSPwauUJe6XD1UDN8GYxdyTEOBJFMAchNdFzVqBA=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab846c3bea80cc07baa574184e803ad772401e560d92cf0000000115dbf43c92a169ce0f78bdb5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/786/331290226@github.com>
In-Reply-To: <quicwg/base-drafts/issues/786@github.com>
References: <quicwg/base-drafts/issues/786@github.com>
Subject: Re: [quicwg/base-drafts] Clarify Connection ID and Version number endianness (#786)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c4323c3da11_63433feff6084f7894681"; 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: <https://mailarchive.ietf.org/arch/msg/quic-issues/OS8OKvzHq3Q1OHoelMIDskZHyhA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 21 Sep 2017 21:42:22 -0000
Yes, thanks for correcting, I meant 64-bit connection ID and 32-bit Version. The most important thing here is that we agree on and explicitly specify an endianness to use (I've changed the title of this bug to reflect that). Your point is fair, and I'm fine with treating connection ID as a uint. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/786#issuecomment-331290226
- [quicwg/base-drafts] Connection ID should be trea… janaiyengar
- Re: [quicwg/base-drafts] Connection ID should be … Ryan Hamilton
- Re: [quicwg/base-drafts] Clarify Connection ID an… janaiyengar
- Re: [quicwg/base-drafts] Clarify Connection ID an… janaiyengar
- Re: [quicwg/base-drafts] Clarify Connection ID an… Subodh Iyengar
- Re: [quicwg/base-drafts] Clarify Connection ID an… Martin Thomson