Re: Unrecoverable loss pattern

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Mon, 26 February 2018 07:37 UTC

Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146DD12D0C3 for <quic@ietfa.amsl.com>; Sun, 25 Feb 2018 23:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 J251SNgzTxn7 for <quic@ietfa.amsl.com>; Sun, 25 Feb 2018 23:36:58 -0800 (PST)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B481120721 for <quic@ietf.org>; Sun, 25 Feb 2018 23:36:58 -0800 (PST)
Received: by mail-io0-x22a.google.com with SMTP id h23so5593090iob.11 for <quic@ietf.org>; Sun, 25 Feb 2018 23:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=lSNJCvLAvkmMsxX1L6lCT8EWG2SPn3ldHi4fLGD+TLE=; b=YTNwFUiuPPjLYZiOTTqfF0+b5KvToB0iAATtQPEpqU2suRCkm6RDj8s/2oN56sRzN3 FpwdBqz6/fl4wBwBtvc8MXJem0B73sP6G4ln9pXx+8IylChVHpY9lLqBKcSOW9367KXk Ee9mVDbR9U+ue2wqphD6qmmURX/7QYA9ML57RaIFHvGMsOl0hBZwh37wgHS0G6h4DLV1 +j5KrJ4dFlLkX6OJJdYvVUoa0emJXgiZgcmnIIabxc1fPTIm1qKInhQMeekT6PRphcCc TAM1nuwn1kAQfEbSAVgMnYUZo5IDC8Wjd1Ws6mtkRWz5UMjDC74MDxwRm+0v1GZ16YXn Y5Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=lSNJCvLAvkmMsxX1L6lCT8EWG2SPn3ldHi4fLGD+TLE=; b=Cv5E3uhy+no/JMKxcVoZYCq0i1f53pj5fICkzw28CJ93o48Y8e0hGZoyovTUh0XWSl ffPMiM7q/vtlJjvvFF9KNspQJWyaVu9xexVSL0ws9btmB4rLnXnxAxECXae8FThZcfsD WviRlZGpc4XvjLGS/92CTk8FH5QtzH4qtueqYKk5evCTg4ofWBVeQkAtcFAU4wvx7SuX +Xw4Nu5ALmey0EWgidzD2d7EdeiTpakWG56xvaW2PWGZ/Ap+bcKIUln/A+XUP+8y5YUZ rQh7uNUNtrg6x9mmgHLWh53TtcxwDUdSVttyuPBglt4sWPhBX9aFgb0725nL5dUL/ehW Ws9w==
X-Gm-Message-State: APf1xPC4KMfsIxcKYe169vrLI6i1xoLoQsbs+pDv0/J9L53j6zn4BOiM H8EaqhqEzWAMu+n79q7tJtOhR0rGdwzYH/+rdcU=
X-Google-Smtp-Source: AG47ELuNFwr4I6HiI6nE4GdB1NSMgONeuGjtg6YcdqGw1FkjaQJDVCZuDBmlQhYBa8AiG/Aw8up12Rp55YB2jc/kY0Q=
X-Received: by 10.107.17.20 with SMTP id z20mr10995909ioi.274.1519630617801; Sun, 25 Feb 2018 23:36:57 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 26 Feb 2018 02:36:57 -0500
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdeaFV7-q34Ha2MAO6s7U-=3a_juUOwcw3AD0s7uP7MDcA@mail.gmail.com>
References: <CAOYVs2q1QSpvZjPRfbJmKhhQ6eApwLSSFSbbOBt2J-PAeqVELQ@mail.gmail.com> <CABkgnnWuXJb2_BcfU4N=ODwy5JDZKBBd6TyhFmXLbPgVrvCoEA@mail.gmail.com> <CAOYVs2q0q6YrFfipd7UEENoz2ht2Mr0fPqnvy5pJRz-bPxCJpw@mail.gmail.com> <059bc7c6-a8cb-c46b-c971-333b9051c222@huitema.net> <CAOYVs2ogy77tjE+e9_mj6YNYcsDP0iduUKsE-_JnMrOeo4jVbQ@mail.gmail.com> <CABkgnnVLdKiaEDdGKjLXB9wNZ8vxvV_ZyJQnLAR4VxsjUDvjyg@mail.gmail.com> <f62726b4-564a-4e45-726b-63705753ddf2@huitema.net> <CAN1APdeaFV7-q34Ha2MAO6s7U-=3a_juUOwcw3AD0s7uP7MDcA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 26 Feb 2018 02:36:57 -0500
Message-ID: <CAN1APddOkP7GcTdsy3Z6mMOfhX6WyD8zw4scV=--i8Y13jjy-A@mail.gmail.com>
Subject: Re: Unrecoverable loss pattern
To: Martin Thomson <martin.thomson@gmail.com>, Christian Huitema <huitema@huitema.net>, Marten Seemann <martenseemann@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="001a113eda8a29fc4f0566189312"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Tq2gM4c475GTTUqhdQKSbaazcZc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2018 07:37:00 -0000

Another thing:

The concept might be more general handover in path-migration, multi-path,
visible path specific sequence numbers, and rekeying.
Rather than having 7 or so different constructs, there might be an
underlying principle called handoff?

Kind Regards,
Mikkel Fahnøe Jørgensen


On 26 February 2018 at 08.33.48, Mikkel Fahnøe Jørgensen (mikkelfj@gmail.com)
wrote:

> The solution might be to send a "Finished received" frame in the
protected data flow, and require an ACK for that frame. That way, the
problem would really be solved.

That is sort of a handshake of the handshake, but I like the idea.
Could that somehow extend to 0-RTT as a more general concept?