[quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)
Martin Thomson <notifications@github.com> Tue, 25 September 2018 00:50 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 A34E7131197 for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 17:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, URIBL_BLOCKED=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 XCHqkFBGsfhr for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 17:50:42 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23C613115B for <quic-issues@ietf.org>; Mon, 24 Sep 2018 17:50:42 -0700 (PDT)
Date: Mon, 24 Sep 2018 17:50:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537836641; bh=hIXmLGJbhzdPwnSVBw73IX6rGbFbFhscEA6Lo+JIW5U=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=haFV3ZoXUiiUHTadPXDiMDI3NFz9lzQ/WSMKxxG+gII4RvRcRXvgBEhGrpd9fsp3A D8xgOlsGG4QzqKgaapj9KRNsMFqSuaVO7S5IQ0hiwdxT1VboAy7Y9Vf8oTFXywJRXV 44tqOYdZc7J0GdTZAqpXwd9D9NKtQlkh/0jGxNos=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd11b9c19e724c109ac38e54c8bde490463783f7592cf0000000117c1486192a169ce15a89a06@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1795@github.com>
Subject: [quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba98661b84c9_428a3f9a858d45b4171092"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/esAon4qI4IUXPI2msamRrf38bVA>
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, 25 Sep 2018 00:50:45 -0000
Ideally, we want an endpoint to change connection ID if its peer changes connection ID. However, this leads to infinite changing of connection IDs if you implement the naive version of this. We need an algorithm that is simple enough to implement, but immune to the looping problem. This isn't critical (we can live without it), but it would be a nice to have. Currently Section 6.11.5 is where this would live. -- 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/1795
- [quicwg/base-drafts] Define a safe algorithm for … Martin Thomson
- Re: [quicwg/base-drafts] Define a safe algorithm … Kazuho Oku
- Re: [quicwg/base-drafts] Define a safe algorithm … MikkelFJ
- Re: [quicwg/base-drafts] Define a safe algorithm … Martin Thomson
- Re: [quicwg/base-drafts] Define a safe algorithm … MikkelFJ
- Re: [quicwg/base-drafts] Define a safe algorithm … Mark Nottingham
- Re: [quicwg/base-drafts] Define a safe algorithm … Martin Thomson