Re: New Version Notification for draft-michel-quic-fec-00.txt

Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com> Wed, 26 October 2022 08:04 UTC

Return-Path: <nicolas.kuhn.ietf@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 ED4E7C14F73E for <quic@ietfa.amsl.com>; Wed, 26 Oct 2022 01:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GysTLyu9Wn8I for <quic@ietfa.amsl.com>; Wed, 26 Oct 2022 01:04:41 -0700 (PDT)
Received: from mail-oa1-x2e.google.com (mail-oa1-x2e.google.com [IPv6:2001:4860:4864:20::2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32C37C14F730 for <quic@ietf.org>; Wed, 26 Oct 2022 01:04:41 -0700 (PDT)
Received: by mail-oa1-x2e.google.com with SMTP id 586e51a60fabf-13b6c1c89bdso13168122fac.13 for <quic@ietf.org>; Wed, 26 Oct 2022 01:04:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DNR0ErF7DFvmxuI+brlLrhPZYJH4gRTEmheLSSxXeQA=; b=fem9WMzgPajV3J4YrviOJrcNAwysPrnvto01Q1KhRPU9SQvEucLR6RJP31akXqOA6+ K9/pI6WARhJET3KsbGta29EVcKD+UWP976mOcoHbKDGVa0QMMhGxATguYmmiZWn083ed 3ADh1kKaR/pfn++6S+vg/tftYaQmHazhwwY/rEQZ494mskAg3mauQiI9okuzhTyBhKXS HSwdqAzZNF2Cgs2rrZof9tIeKi91DkbOFpChy+i6XzFZRIv6BembLpbktcvPf+zvMJcY rck1TXuyAJoheyj4fOf0URPor88SSD45/tX8M1FGRT4Sg3z+HYn/pLWGbp+eNzr4PiqY LYXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DNR0ErF7DFvmxuI+brlLrhPZYJH4gRTEmheLSSxXeQA=; b=WkvxrbEwdsWGK5gWg7iJxpZdyQ+5WLi/Zdx23ElmWMViUG3P6Ky1FIAWehy8ZqUSuB QlYMMx1WZd0jMeM58ua63us0gUzPOq2uvTlSf849asRJN/AqwFC/wi8tXO31hFfCKy2x NfB4UAgpZ8wOSgVV+PWr3QlcZx4M5UHw33awOjRHhU640pVWGpDK0RgmG0itp2T072Rf 4QWppLXNyLbPBZgulE7FBXdzoEb2/f7nGH1JK45MhwiPyhWrnluYwvesb7MSB9LIo548 C4NMU3fnAtkFGbnaULsLkgnChYz1ebF6yyhqjm4xy0wGR6JocGokzHZrGQ+Z/pqQerP5 fsrA==
X-Gm-Message-State: ACrzQf1qheZ6SLsd25fP+gC/iPM7eiaGeBYK3t0zkWDAO1k7UefjV8Ir /6JlAGU7AP5mXl+hgrJBqWLkBK+dP5aw+0djY/8=
X-Google-Smtp-Source: AMsMyM4BIYQSMIM9Q9cdGGUs4V1cQJ761FicHpl2H7rD6kfY9ktrkNnO6irisAGKA+6Fy38qtLeqCtDLH9va/sORBbE=
X-Received: by 2002:a05:6870:e30e:b0:132:e934:5c0a with SMTP id z14-20020a056870e30e00b00132e9345c0amr1329198oad.202.1666771479606; Wed, 26 Oct 2022 01:04:39 -0700 (PDT)
MIME-Version: 1.0
References: <166635428256.33398.3422317514834517586@ietfa.amsl.com> <6339ddf0-aad1-2579-4a75-2c1d0fa5f94b@uclouvain.be>
In-Reply-To: <6339ddf0-aad1-2579-4a75-2c1d0fa5f94b@uclouvain.be>
From: Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>
Date: Wed, 26 Oct 2022 10:04:26 +0200
Message-ID: <CAL0D2oRKcZJzSoY9QnPL-ADv0=6tmmky7uGnEfyA+E1p03EJVg@mail.gmail.com>
Subject: Re: New Version Notification for draft-michel-quic-fec-00.txt
To: François Michel <francois.michel@uclouvain.be>
Cc: quic@ietf.org, Olivier Bonaventure <olivier.bonaventure@uclouvain.be>, Marie-Jose Montpetit <marie@mjmontpetit.com>, louis.navarre@uclouvain.be
Content-Type: multipart/alternative; boundary="000000000000f6b99405ebeb79f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Miu49ZHCnZ2t_HbyGT9RqFMtv54>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 26 Oct 2022 08:04:45 -0000

Dear François, all,

Thank you for this document. This is very important for the
lossy-GEO-satellite scenario, so thank you!

I have some questions/comments on the document :
- Taxonomy : you may want to refer to RFC8406 on the taxonomy related to
coding
- On the coding channel :
  "A coding channel can be seen as a
   communication channel between a QUIC receiver and a FEC decoder."
  => This is in contradiction with the notion proposed in RFC 9265.
  I think that the coding channel should be seen between the FEC-coder and
the FEC-decoder.
- The notion of APP_DATA in Figure 1 is not clear to me. IMHO the
presentation on this should be improved.
- On DATAGRAMS : I agree that if a solution can also protect DATAGRAMS,
this could help in lossy scenarios
- "In this document,
   we propose to consider whole frames as part of the source symbols."
  => This is important and should be highlighted in the document. It may be
worth expliciting what is meant by "whole frames" and maybe provide
examples.
- Alternative 1 vs Alternative 2 : alternative 2 has an impact on the QUIC
packet scheduler. For this reason, I am not sure whether it is relevant.

I hope this helps,
Kind regards,

Nicolas

On Fri, Oct 21, 2022 at 2:50 PM François Michel <
francois.michel@uclouvain.be> wrote:

> Dear all,
>
> Here is a draft discussing the addition of Forward Erasure Correction to
> QUIC.
>
> We wrote this draft to discuss FEC in QUIC and experiment with people.
> It is inspired by our previous work at the nwcrg. We also have
> interesting real-network results that we would be happy to show to
> motivate the interest for this extension.
>
> The design is at an early stage and is intended to evolve. Do not
> hesitate to provide us with comments on the document or the extension in
> general.
>
> Regards,
>
> François
>
>
> -------- Message transféré --------
> Sujet : New Version Notification for draft-michel-quic-fec-00.txt
> Date : Fri, 21 Oct 2022 05:11:22 -0700
> De : internet-drafts@ietf.org
> Pour : François Michel <francois.michel@uclouvain.be>, Francois Michel
> <francois.michel@uclouvain.be>, Olivier Bonaventure
> <Olivier.Bonaventure@uclouvain.be>, Olivier Bonaventure
> <olivier.bonaventure@uclouvain.be>
>
>
> A new version of I-D, draft-michel-quic-fec-00.txt
> has been successfully submitted by François Michel and posted to the
> IETF repository.
>
> Name:           draft-michel-quic-fec
> Revision:       00
> Title:          Forward Erasure Correction for QUIC loss recovery
> Document date:  2022-10-21
> Group:          Individual Submission
> Pages:          14
> URL:
> https://www.ietf.org/archive/id/draft-michel-quic-fec-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-michel-quic-fec
> Html:
> https://www.ietf.org/archive/id/draft-michel-quic-fec-00.html
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-michel-quic-fec>
>
> Abstract:
>     This documents lays down the QUIC protocol design considerations
>     needed for QUIC to apply Forward Erasure Correction on the data sent
>     through the network.
>
>
>
>
> The IETF Secretariat
>
>
>