IETF Logo Mail Archive

Connection IDs

Martin Thomson <martin.thomson@gmail.com> Mon, 05 March 2018 01:54 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D4A124D6C for <quic@ietfa.amsl.com>; Sun, 4 Mar 2018 17:54:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rt4MP5kk2eU8 for <quic@ietfa.amsl.com>; Sun, 4 Mar 2018 17:54:35 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B387F124C27 for <quic@ietf.org>; Sun, 4 Mar 2018 17:54:35 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 108so13550972otv.3 for <quic@ietf.org>; Sun, 04 Mar 2018 17:54:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ecVj2GhNqysjtw7UjaPg64BBj0XnICYU8kiayQvLtRo=; b=TMdS27ANqmNbJwdHkHDS9GVMuxcuwlwQifX1CPXttAh4Q/vmf6cqGo8y8koiTqg4ki po3XWgaMgtZURVcOY1thXcKGR0V2QhOQHSh1qDCPoG4uGFEfKRBWgMqjWMo4bzqyzENp LbYT3QYq3ZcoQnKaSXDgK6xAQ8Tb6Sla3+5jYYc+7Nx7V6G4Xjvto2E7wIF2k9NBIACL U5S3zgl370TEysMVlZBhKzrqckGkwaBngD/mBIbN6OMQsKWOtZSVGhmwnqX7FH1ob7it lr70rwtdrAjajyLY7et/Mhmk4viqEACF4fAUrwzZa8OAxdDxgsfw1hJLJjqJGC7ayYxJ qhMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ecVj2GhNqysjtw7UjaPg64BBj0XnICYU8kiayQvLtRo=; b=jcS2/FTIjnJznVCTZHLoMG34f2bLl5nAXPCOSv5Bi+X/PdiW9gSjaDkgjehUvakf2M dJhM9C0KSk0QyacGInCQmLYOD/70J3dL4AUFYuROARzNbeat/HXRGZBSjiHKan90iCWF jeoxRgc7wm+0TSXwPEeYUS5XB0NQqFl4jZGWX5uWVu5Fu5xBSnARsKquFhLG2BHeCgn4 Ko86eMhzGbqLDuXFMcdIW5uqgPZTStclJKP3Yj3CqENudUgIbiYYBwQ7pQDUl8BbpkxK l9j3KGKY9MVxO+VY25pQV9olSFNPKBkgjZNO1wP5SbW+r6mhLQuDqhls+TgoZ9s6uM4B GObw==
X-Gm-Message-State: AElRT7FST3tTFNhtI9mCmAmVmiC64pPh4s3LzES8MmAek5enIu4sLWEQ BAjsaKNBGqsvKeWRuOp0qjBdJs1TSHap0coxgfCsJ9YJ
X-Google-Smtp-Source: AG47ELsnwy3Iwj3nKYGkLzaDv+rGLi7xaHljgG5mbqD8f5zAy4j1i3awijsNmQhwTsKsABmiT/yv9PmVs+7wEyKuu/M=
X-Received: by 10.157.12.229 with SMTP id o34mr9715740otd.352.1520214874684; Sun, 04 Mar 2018 17:54:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.16.85 with HTTP; Sun, 4 Mar 2018 17:54:34 -0800 (PST)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 05 Mar 2018 12:54:34 +1100
Message-ID: <CABkgnnVSCnmzjWOZwQM+ctTxFXVzsVYe6Q3Zzk4yj3LNTYUtHw@mail.gmail.com>
Subject: Connection IDs
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ghDt4kE7TBuYZHKQxL5gzL0WeVk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 01:54:37 -0000

I've written up a PR that enacts the changes suggested by the design team [1].

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

This adds two connection IDs to the long header.  An explicit length
is added for each.

The short header includes the raw connection ID without any C bit or length.

I've tried to explain the limitations of the design where they apply.
That includes stateless reset.

This PR necessarily includes some choices about less critical aspects,
such as how connection ID lengths are encoded.  I ask that you try to
separate objections about minor issues like this from more serious
structural concerns.  I'm happy to discuss details, but I'm most
interested in whether this is broadly the right direction first.

Cheers,
Martin

p.s., happy draft submission deadline day

[1] https://mailarchive.ietf.org/arch/msg/quic/l_b1NnBmQpQGCxCfQteOMkft-lE

v2.23.0 | Report a Bug | By Email