IETF Logo Mail Archive

Re: [payload] Updates on FLEX FEC (ver -19)

"Ali C. Begen" <ali.begen@networked.media> Mon, 01 April 2019 22:57 UTC

Return-Path: <ali.begen@networked.media>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EBB4120193 for <payload@ietfa.amsl.com>; Mon, 1 Apr 2019 15:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 RHkagzsY4sGT for <payload@ietfa.amsl.com>; Mon, 1 Apr 2019 15:57:44 -0700 (PDT)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 AE1061201B1 for <payload@ietf.org>; Mon, 1 Apr 2019 15:57:44 -0700 (PDT)
Received: by mail-yb1-xb2f.google.com with SMTP id b18so4092137yba.12 for <payload@ietf.org>; Mon, 01 Apr 2019 15:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PP1LjK+ZEKDtLhMT1KS0SZZKnnjpAtTzsj5LFr62iOs=; b=zAKYMMRKq8/JdsQphoaT7M6K8uTNPFPuHF8O7vC9fEmsRGYUQHyP7+XKwGLcH9Vydb h2xglRtR7I9oltHnZPJ2icX2j7h0GyyOW3fFJZObnpJMNREqclaNJpAZXvTL5e7BalDS hU+lrOCXyS/bhmwyEvEtiiTf1xcuiynU5SJ6KF8ejg4LlfH/XfD0I0tRCLmG8LQuwS5o qIN9gIAclUU3Qv5A/P2+imoMrrPFwsaYgC0GYVEdMMzaW08TOOAkPHRdQvxT7C3kJhK1 /C43Y4it+m2PyiQLkrp9VhK1wfq2BsG3hbJmGGQeNK/Kj0JYcOwcnzDb7pBRHMhVbhs0 5SOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PP1LjK+ZEKDtLhMT1KS0SZZKnnjpAtTzsj5LFr62iOs=; b=t1d7kuhpv+AzidIXOFpPZjB69eNJvLro4wFGe9VIUX/Z4+MxMHFNk35i+uwti8iG1V PsG/2RxAfTbF48wsvpQdvh2+bFlFYtUXsPvqzuIfQRdmdZm6kADVRNUpyLIBJ5mN7o6z 9+zLk4hs0tpV9lE3/n4CVjlUb1VxDX/sFoeG8xCQzJT7JJ1sMzzwqRdBdRYKns12PyYF Y09WrUSNzqkwfjaVvLxooH2xqKzCvn76QWj8IaSYQmusnbmtc9LRxX2oFg/IzkzqNvVo m4+IrN+fpAG8YxuCZCaB0cqmo3ZmxijLx07vvgQr7bcqb93Y4VQ8f6pS9bZpFTNsOuvU 9PQQ==
X-Gm-Message-State: APjAAAXeYIypxl0KXwW/VVbviQ2Hu9hrxSZlTBOnZqmKg2mU09Bmjt8L 690nYYapn6DCUgJI99jPeRhqls3JpGeDkzdoOH7ftw==
X-Google-Smtp-Source: APXvYqweVGATRgNc8/9kpDr+HSbhlG5z1/RVxNplz/bNPK1mRvn9FndymR53AZOcQQol+9lAon3VpUrPzfszx581dVw=
X-Received: by 2002:a5b:28c:: with SMTP id x12mr54318617ybl.196.1554159463734; Mon, 01 Apr 2019 15:57:43 -0700 (PDT)
MIME-Version: 1.0
References: <5e948e46153445c892dc661085d21073@NASANEXM01C.na.qualcomm.com>
In-Reply-To: <5e948e46153445c892dc661085d21073@NASANEXM01C.na.qualcomm.com>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Tue, 02 Apr 2019 01:57:32 +0300
Message-ID: <CAA4McztCnsm+coMH6B=9_UHFfX+sdWmuXR6veXuKUxjPaGjytw@mail.gmail.com>
To: Giridhar Mandyam <mandyam@qti.qualcomm.com>
Cc: "payload@ietf.org" <payload@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c2b9d905857ff202"
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/LsOfGDh1a0cWdjf3HJLEkz8LTm0>
Subject: Re: [payload] Updates on FLEX FEC (ver -19)
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 22:57:48 -0000

Folks, please provide feedback. There are important changes in the flex fec
and in a few days, the draft will be shipped to the RFC editor.

Thanks.

On Thu, Mar 28, 2019 at 9:19 PM Giridhar Mandyam <mandyam@qti.qualcomm.com>
wrote:

> Dear Payload WG,
>
> After offline discussion with the editors and reviewers (special thanks to
> Bernard Aboba), we have decided that the spec needed to be slightly
> modified.  Version -19 contains the following changes:
>
> a) Recommendation against negotiation of RTP RTX when FLEX FEC is used.  A
> new section 1.1.7 on the use of FLEX FEC retransmissions has been added to
> indicate as such.
>
> b) Elimination of all optional SDP parameters (e.g. ToP, L and D fields).
> This means that the sender can send any FEC configuration (as indicated by
> the FEC header) as long as it stays consistent with the mandatory SDP
> parameters (rate and repair window).  Sec. 1.1.6, 1.1.7, 4.2.2, and 5 are
> the primary impacted sections.  We believe this will greatly simplify SDP
> O/A and while retaining the "flexibility" of FLEX FEC to adapt FEC repair
> data on a packet-by-packet basis.
>         - Note that L and D cannot be larger than 255, respectively.  As
> we gain implementation experience, if we decide that 255 is not sufficient
> then it could be possible to extend the corresponding header fields in the
> future. Currently there are header values that are reserved (R=F=1 and
> L=D=0) that could be used to indicate the use of an extended L and D field,
> as an example of one way to implement extended fields for L and D.
>
> c) Slight adjustment of Sec. 6.3.1.2 to correct for sequence numbering
> errors in the abstract procedure for grouping of source packets using their
> RTP sequence numbers.
>
> d) Accounting for the remaining nit's in Benjamin Kaduk's last review.
>
> e) Explicitly defining "FLEX FEC" in the abstract.
>
> Please provide any feedback within 7 days of the sending of this
> notification.
>
> Thank you,
>
> -The Editors of FLEX FEC
>
>
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload
>

v2.39.1 | Report a Bug | By Email | System Status