Re: [quicwg/base-drafts] A fixed transport parameter profile is legitimate (#3429)

Nick Harper <notifications@github.com> Thu, 06 February 2020 15:04 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 8DC371200CC for <quic-issues@ietfa.amsl.com>; Thu, 6 Feb 2020 07:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, 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 rH5zPq-8jRDF for <quic-issues@ietfa.amsl.com>; Thu, 6 Feb 2020 07:04:36 -0800 (PST)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BBE012080C for <quic-issues@ietf.org>; Thu, 6 Feb 2020 07:04:36 -0800 (PST)
Received: from github-lowworker-275fa97.va3-iad.github.net (github-lowworker-275fa97.va3-iad.github.net [10.48.17.64]) by smtp.github.com (Postfix) with ESMTP id 006EC280A72 for <quic-issues@ietf.org>; Thu, 6 Feb 2020 07:04:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1581001473; bh=MqmDKLWqqcfZthff5Inq8f+UVFtwen3HRXpe+89UOjs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gEOH1CluA85l8tLvcoj98QHuTskoMiNLmRxCjBqY/HDZ1I6Za4N4GSv6BSEZtxyO5 gMRX9WoPfQ0Cp+7QXdZsIxlBaM/E8mJUP4EUJHjUQEYx42I+MFDilNEMdnz2lTUjFk bB1ztBQmJuBy1VUfkMKepfq7sVKxrs2jk8Qn76ZY=
Date: Thu, 06 Feb 2020 07:04:32 -0800
From: Nick Harper <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK77DA333DFPP44CHHN4JFOYBEVBNHHCC3RHVQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3429/582947242@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3429@github.com>
References: <quicwg/base-drafts/issues/3429@github.com>
Subject: Re: [quicwg/base-drafts] A fixed transport parameter profile is legitimate (#3429)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3c2b00e5297_3b893f80fb0cd968409720"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nharper
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/2nwpsXkELNjO1F5eey4frwiVVWw>
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: Thu, 06 Feb 2020 15:04:39 -0000

I looked through the existing transport parameters for what currently conflicts with a fixed profile of transport parameters. I've only found one (apart from the already discussed active_connection_id_limit): original_connection_id. This field is necessarily dependent on what the client sends. The only way to avoid this is to not send Retry packets so you don't need to send this TP. The rest of the transport parameters appear to be independent of what the peer sent.

-- 
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/3429#issuecomment-582947242