Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)

Martin Thomson <notifications@github.com> Tue, 19 March 2019 00:33 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 30BA9130E6A for <quic-issues@ietfa.amsl.com>; Mon, 18 Mar 2019 17:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.384
X-Spam-Level:
X-Spam-Status: No, score=-6.384 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_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 5iQbYeuYmP90 for <quic-issues@ietfa.amsl.com>; Mon, 18 Mar 2019 17:33: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 C31D31277E7 for <quic-issues@ietf.org>; Mon, 18 Mar 2019 17:33:17 -0700 (PDT)
Date: Mon, 18 Mar 2019 17:33:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1552955596; bh=pgKbbgKYF9Q7tLVyhvDRm3C/wKNU6i0qEZ+nrkeI8RQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M8pauZe4hqxPtbC7NpJ51B6gVLFagOCiG4Nz4yXjMqV1c6OUy0mrJXyDgUa54+E1K r7kb1ZUG2eBfqTK5A+Al2K/cZUxwwPamfLOf1kpa8CfyZjGW5Nt4tnXSb/EJQg09xG mRC2G1iuHwqZNzPhgXjWNT8TZcEBO495e7a04atA=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba5406582c5f5c9543b05a14595c2b4c3536d102992cf0000000118a7facc92a169ce192ea180@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2528/474152870@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2528@github.com>
References: <quicwg/base-drafts/issues/2528@github.com>
Subject: Re: [quicwg/base-drafts] Are transport parameters mandatory? (#2528)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c9038ccacb29_781e3f8c780d45b4164598"; 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/fWEZRS9VwTw2-hOso9YggmOiFeQ>
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, 19 Mar 2019 00:33:19 -0000

The issue could have been more precisely worded.  The question was about the entire QUIC transport parameters extension.  Individual parameters are still clearly optional.

We should be very crisp about that.  Up until -18, this was mandatory, but we don't need the version parameters any 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/2528#issuecomment-474152870