Re: [quicwg/base-drafts] Request to Retire Locally Issued CIDs (#2769)

Mike Bishop <notifications@github.com> Thu, 06 June 2019 21:11 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 F30C5120132 for <quic-issues@ietfa.amsl.com>; Thu, 6 Jun 2019 14:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.605
X-Spam-Level:
X-Spam-Status: No, score=-6.605 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 AhGHE_S8qQZw for <quic-issues@ietfa.amsl.com>; Thu, 6 Jun 2019 14:11:27 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8418C12011B for <quic-issues@ietf.org>; Thu, 6 Jun 2019 14:11:27 -0700 (PDT)
Date: Thu, 06 Jun 2019 14:11:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1559855486; bh=sYw34kFoAFD83ODcDGZJc5/oSgor/ZwGHpsH9CRnw0M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zqGbagEeFZ8hmS1s0unXRYILpJKGtAWJwOOABmB9AnDCgaxwCv46qdT22Wy+pqIMq qIJrz7sB6Y0+0pygR/vf6F/nygGNVmFgJ4DG2EU1koXDA+opAUz7PUvvedIGiWgp+C XmFKltC93gjFSilz8cdqu2+Hsd5QJngAsCWor4iw=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY2LMMN5CHL66JI5IF3A2Z75EVBNHHBV45H2U@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2769/c499669154@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2769@github.com>
References: <quicwg/base-drafts/pull/2769@github.com>
Subject: Re: [quicwg/base-drafts] Request to Retire Locally Issued CIDs (#2769)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cf9817e46067_e233fa723ecd95c72396"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/QFUdT0cJaqkryvzScuEzXeKvvjs>
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 Jun 2019 21:11:29 -0000

IIRC, the conclusion we reached on the CID design team was that:
- When the client sends RETIRE, that's a statement that it has purged that CID and SRT; the CID will never be used again, and the SRT won't be recognized.  The server can immediately declare that CID void upon receipt.
- If an earlier packet got delayed, it will trigger a SR, because the server doesn't recognize the CID any more.  This is also true if the client messed up and sends a later packet with the retired CID; the server will discard it.
- The client will receive the server's reset, but not recognize it as such because the SRT isn't one that it knows any more.

The important thing is that the client has already deleted the SRT before sending the RETIRE and the server can safely purge state immediately upon receipt.

In this PR, I think we have the right model by letting the client have a little time to make sure those requirements are true before sending the RETIRE.  You MUST retire the CIDs, but you're not obligated to do so instantly.

-- 
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/pull/2769#issuecomment-499669154