Re: [quicwg/base-drafts] CID ratcheting language is imprecise (#1452)

Mike Bishop <notifications@github.com> Wed, 20 June 2018 19:20 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 C8DC5131106 for <quic-issues@ietfa.amsl.com>; Wed, 20 Jun 2018 12:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 nOlJmGoKiSh1 for <quic-issues@ietfa.amsl.com>; Wed, 20 Jun 2018 12:20:29 -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 A13A113117B for <quic-issues@ietf.org>; Wed, 20 Jun 2018 12:20:29 -0700 (PDT)
Date: Wed, 20 Jun 2018 12:20:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529522427; bh=DuMrq8LIHzzuq7sskWS/gp5V2vul9yMPfWU2aGaQeUA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T8ojGoN3sMmCNqeS2PBT3D1y8060e9l541jtaiZVxp3RKdVNc8QorSCXI4PwCCmYH tGJ++2RzrTQdVaFnIKcQKKi4BHWDYFDgyMD+UkTkBkXujzcfylv2QcC8KsM9KvkbNL QvV3FALF3/L3O7QNbQ6nP2KX4socqwojQ4Qw44Ac=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd40128bb5c76c5057ac44c96e844df55b664d85e92cf0000000117426afb92a169ce13d7106f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1452/398866138@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1452@github.com>
References: <quicwg/base-drafts/issues/1452@github.com>
Subject: Re: [quicwg/base-drafts] CID ratcheting language is imprecise (#1452)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b2aa8fba8e7a_286c2af4a6688f60435359"; 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/XNuiHHvX0zoTpTRDuQdZHYYvoW0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 20 Jun 2018 19:20:37 -0000

Packet loss makes this even harder, similar to the case in #1464.  Using the counter approach, if you don't un-count a CID where all packets using it were lost, you'll fail to change CIDs the next time the peer changes.  However, if you *do* un-count it, but any of the packets were declared lost in error, then you wind up in the same loop where your delayed packet causes the peer to change, which causes you to change, which causes the peer to change....

I'm starting to think we need the sequence numbers back to make this work, but with some additional text about probing packets on a different path being handled a bit differently.

-- 
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/1452#issuecomment-398866138