Re: [quicwg/base-drafts] CC state after a change of path? (#2685)

Jana Iyengar <notifications@github.com> Fri, 17 May 2019 02:01 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 4D15C12033E for <quic-issues@ietfa.amsl.com>; Thu, 16 May 2019 19:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 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, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 jhB49M5Mp5Is for <quic-issues@ietfa.amsl.com>; Thu, 16 May 2019 19:01:51 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5B7A120154 for <quic-issues@ietf.org>; Thu, 16 May 2019 19:01:50 -0700 (PDT)
Date: Thu, 16 May 2019 19:01:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558058509; bh=ut42KOeNuLYNxzc89CSDLr+nvo8DoZytvuOQoe/2+hQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V7S51CRrHX/38u16JYw0/EGRGY/Q0gP3JOOKB3acoTrdNOalYdEIJPQeEpmrEulC3 XX0tWn1smSqbabWdaN0yLpHoSB5YDBDo/8uA9TfW5mI6ep4Exwp0RZ7zyhEN+t8vQa WXLfzDZ7UCIjfwm+7VzhQ8b/pWh54kqJTqr/h2do=
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY3KUFP46MFXH5VIEN25NEI3EVBNHHBUYMJPU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2685/493291186@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2685@github.com>
References: <quicwg/base-drafts/issues/2685@github.com>
Subject: Re: [quicwg/base-drafts] CC state after a change of path? (#2685)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cde160d59685_14ec3f8462ecd968104973"; 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/HJ2RcwU8d-UgKewQKqfiMIUXvwg>
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: Fri, 17 May 2019 02:01:52 -0000

> • Does the "reset" require setting the CC to the initial window value for a connection? I think so.
Yes. We should articulate this better though.

> • Why not MUST?
To allow for pre-existing knowledge, such as stored values. I think this can be changed to say "unless an endpoint has other knowledge, it MUST reset" (or some such).

> This could therefore be seen as a “significant” departure from conventional approaches considered safe
Fair point. The intent here again was to allow pre-existing knowledge to be used, but I think the wording can be changed to reflect that more explicitly.

-- 
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/2685#issuecomment-493291186