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 1F3151200D8
 for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 08:56:14 -0700 (PDT)
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 RePmpPsq8rNN for <quic-issues@ietfa.amsl.com>;
 Tue, 17 Sep 2019 08:56:12 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 7CE3012009E
 for <quic-issues@ietf.org>; Tue, 17 Sep 2019 08:56:12 -0700 (PDT)
Date: Tue, 17 Sep 2019 08:56:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1568735771;
 bh=BJUyw/MTneTpZe5PXXzSlPakh4nG5r4q0yBxriTPLCQ=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=DArPEIgkWJaiyJUXx+tZ3VVd4R/BX7UXS7yOrdutk9/JxkZ+LkJmoCrKtAfqAZNiW
 ZZgL6+xet4MxWW5DyyK7zrdSpL9axHGfWNhGbefi0h9sN1uvSOwn3Q99cI68VXUF4U
 SYXFIUBPNkoQtOZ3tDUcY9bD7DmVLGzr+eeLDxLU=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2FH7HKFLCKZLLXEQV3RY2JXEVBNHHB25D7KM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3037/532284657@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3037@github.com>
References: <quicwg/base-drafts/issues/3037@github.com>
Subject: Re: [quicwg/base-drafts] Require peers to check if
 RETIRE_CONNECTION_ID sequence number is valid (#3037)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5d81021b6bfc5_16f13fdc1c6cd9682030f3";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/eJvGHl5whgIfQq_UR7JVGzMAbz4>
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, 17 Sep 2019 15:56:14 -0000


----==_mimepart_5d81021b6bfc5_16f13fdc1c6cd9682030f3
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@nibanks 
> The `SHOULD` is for `in a timely manner`. If you don't do it, the connection will eventually break, likely via a stateless reset.

The question is the intent of using "SHOULD in a timely manner" rather than "MUST in a timely manner". Yes, the connection would break, if the receiver does not migrate to a new connection ID. However, because we use a SHOULD, that is one of the expected outcomes when an endpoint sends a NEW_CONNECTION_ID frame carrying non-zero Retire Prior To field.

-- 
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/3037#issuecomment-532284657
----==_mimepart_5d81021b6bfc5_16f13fdc1c6cd9682030f3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=20663557" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/nibanks">@nibanks</a></p>
<blockquote>
<p>The <code>SHOULD</code> is for <code>in a timely manner</code>. If you don't do it, the connection will eventually break, likely via a stateless reset.</p>
</blockquote>
<p>The question is the intent of using "SHOULD in a timely manner" rather than "MUST in a timely manner". Yes, the connection would break, if the receiver does not migrate to a new connection ID. However, because we use a SHOULD, that is one of the expected outcomes when an endpoint sends a NEW_CONNECTION_ID frame carrying non-zero Retire Prior To field.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3037?email_source=notifications&amp;email_token=AFTOJK36VMT3SX5LD4BP7N3QKD4ZXA5CNFSM4IXFBLR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65AJ4I#issuecomment-532284657">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK56C4SFQTEFSH3YC33QKD4ZXANCNFSM4IXFBLRQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK3U42JTDQM7Z5UAHPDQKD4ZXA5CNFSM4IXFBLR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65AJ4I.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3037?email_source=notifications\u0026email_token=AFTOJK36VMT3SX5LD4BP7N3QKD4ZXA5CNFSM4IXFBLR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65AJ4I#issuecomment-532284657",
"url": "https://github.com/quicwg/base-drafts/issues/3037?email_source=notifications\u0026email_token=AFTOJK36VMT3SX5LD4BP7N3QKD4ZXA5CNFSM4IXFBLR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65AJ4I#issuecomment-532284657",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5d81021b6bfc5_16f13fdc1c6cd9682030f3--

