IETF Logo Mail Archive

[quicwg/base-drafts] What can change in a different version (#55)

Martin Thomson <notifications@github.com> Thu, 01 December 2016 23:15 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 10AB01299BD for <quic-issues@ietfa.amsl.com>; Thu, 1 Dec 2016 15:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level:
X-Spam-Status: No, score=-3.298 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, 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 StSmZ9fO3Sz5 for <quic-issues@ietfa.amsl.com>; Thu, 1 Dec 2016 15:15:28 -0800 (PST)
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 E740A12952B for <quic-issues@ietf.org>; Thu, 1 Dec 2016 15:15:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=k8VKVzwPYXKgppHbgesiWXq4QbM=; b=tu1xzEqnfcBvBrL0 C+NtqLUc9odDhQnM2JAh6be6oDhM90MQlct2xR4MvK6yCOVrReP18UqT/7e2/OSb DKFZwMIT33uq0LcSyMvO5WiUIjzumd5Igx2bZP+Ntnc6mvbr2WLg6QuJQr9jQhZT wiCeOCIziTzL0GNk/6q8h8hNrPI=
Received: by filter0604p1mdw1.sendgrid.net with SMTP id filter0604p1mdw1-14068-5840AF0E-29 2016-12-01 23:15:26.827439023 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id h5otbD_cSxGnj8YHaQ1V3g for <quic-issues@ietf.org>; Thu, 01 Dec 2016 23:15:26.776 +0000 (UTC)
Date: Thu, 01 Dec 2016 15:15:26 -0800
From: Martin Thomson <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/55@github.com>
Subject: [quicwg/base-drafts] What can change in a different version (#55)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5840af0ea2309_7a293fdb22d2b134771ce"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0xOsZJ68gVINoAy/eAD30q4+nTrs46RdvR1m MxMnVaVgrrxJwGjBlfv2z6g3KoNvPacBob5snPpUs1zOwu9JxUykl0b2CMt3YNq9L1U6/ZiWX5X4T3 1HCF+JCxeTx+/JW8K91GruaYJHz3aS9+KB7DXxq4alfcHO6QgNG611I/HYPolxc8uTbJ9RCBYDMmna 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/4C3-Y4E0a2A_iL7HO5wTr29yY4U>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quicwg/base-drafts <reply+0166e4ab6e843664ca08bbf439b20ca947bc920bce2eb9a392cf000000011458710e92a169ce0b80c9d5@reply.github.com>
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, 01 Dec 2016 23:15:30 -0000

We need to know what can change between versions.

The critical thing for forward compatibility is the ability to signal that a new version is being used.  In order to do so, the recipient (the server here) needs to be able to find the version field.  Given the current packet layout, that means that we need to guarantee that the connection ID and version bits behave consistently across versions and that no extra fields are added in between the start of the packet and the 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/issues/55

v2.37.1 | Report a Bug | By Email | System Status