[rmcat] review of draft-ietf-avtcore-cc-feedback-message-04

Steffen Schulze <steschu77@gmail.com> Tue, 23 July 2019 16:01 UTC

Return-Path: <steschu77@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B3612012C for <rmcat@ietfa.amsl.com>; Tue, 23 Jul 2019 09:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 v5hPit_FnEWE for <rmcat@ietfa.amsl.com>; Tue, 23 Jul 2019 09:01:05 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 545F21200BA for <rmcat@ietf.org>; Tue, 23 Jul 2019 09:01:05 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id s22so31539199qkj.12 for <rmcat@ietf.org>; Tue, 23 Jul 2019 09:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=CRcz0ps9Zm2YrAD2kRw8tNtd8wogwWwT3dJbWx58lqQ=; b=WuYpZHqFwEvKQryNMM3bEaOaKPBrvkwepr11YqHRjqWtoJ0GY39jb+aDi2aP7cv4at c7kdBtXQvxGuueBV/lTeKJ6BLjifpFU/pbIwn4TXb2Emu/VLIisUNdLjsYc3eBNQSQR6 MMwH1Crq3B9V8tvWnmdtW2LeuhF8R5VUyDaQIOZg+oarVfWpVMuCkIEzFGcq2oMfw965 xC5TUcDvDFzY7/cL/O1V5ozuUnW2FLpXfgydGVmgFC3+3uAE6o6nVk5HVDQ418z93/k5 +fpIdVjQGQzLAK1+7Fnh+387KSS16ASxgV50MEjgtYuTNEMHaYBesvUSmkscLwiLF9bv uRLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CRcz0ps9Zm2YrAD2kRw8tNtd8wogwWwT3dJbWx58lqQ=; b=WW4982XqZ5mTTaMFxvOS8iPyZg+2aubso8Mn4IoIs0o02ht9Uk3p8Us9iv9RyEPXIA PVVw9Hf3QSys8r5jFmyqgAohhHYsqNiwOXQ8rfdaMWv6kvdOO3yRpn54y/BOx4E7vhWZ 6sQSfDv0dZBIdAh+/x1DHYvuoLvFlbBaA3/KyMTmVI8OyvtaqeRsRjtIZ95ByIiXJdd3 ErJ2i9yBGq/WZVXeAqMZu14hCi8HA/VsAx936jcgCk5celar1Cde82r79I5xM3lO8mDr YLmtrdj4qTDKE82aShwUJ+fgJt/jAlIQX6cv/aGjnnUIy6TJMpUW2p28YVWc3hk2NjXq S2+A==
X-Gm-Message-State: APjAAAX3mxNBTkLB/aTKQxkhn4E1LWJua5mPkHUz2iib1H1hRU2wH520 7x5IZ6ShsVOlD2OxTECSvnmXrS8KOujV7yp1EKC2G4iDFc8=
X-Google-Smtp-Source: APXvYqz0OSKIUMxM0W1obx76owtEYfg1KQp+ujOSZlKqdH5bi4yoSiuUjaOGmnGJaOyjl8yOi1HooUD4WNHvr0m9lYY=
X-Received: by 2002:a37:d247:: with SMTP id f68mr53072185qkj.177.1563897664139; Tue, 23 Jul 2019 09:01:04 -0700 (PDT)
MIME-Version: 1.0
From: Steffen Schulze <steschu77@gmail.com>
Date: Tue, 23 Jul 2019 12:00:47 -0400
Message-ID: <CAOLMUdBCtnsDgJbrx91tFN++B3=ibvRepn4tyMShNhoHNx4MDQ@mail.gmail.com>
To: rmcat@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/C7ClG0yHPJpysT7UBD7ff6YPqXc>
Subject: [rmcat] review of draft-ietf-avtcore-cc-feedback-message-04
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 16:01:07 -0000

Hi,

while reviewing draft-ietf-avtcore-cc-feedback-message-04 I found a
minor typo you might want to fix on page 7:

then an ECN-CE mark MUST be reported that for packet;

to

then an ECN-CE mark MUST be reported for that packet;

In addition I have some questions:

If a duplicate packet arrives which would update the ECN-CE field for
the previously reported packet, as stated on page 7, how far back the
receiver must report that?

Can a CCFB packet include multiple reports for the same SSRC? (Which
would be interesting for updating a duplicate.)

The current proposal includes information about packet reception back
to the sender for all kinds of QoS parameters, including jitter,
packet-loss, round-trip time, etc. Therefore would it be worth
considering to report duplicate packets to the sender as well?

Thanks and regards,
Steffen