[media-types] registeration of audio/video/text/application flexfec media subtypes
"Roni Even (A)" <roni.even@huawei.com> Mon, 26 November 2018 07:58 UTC
Return-Path: <roni.even@huawei.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD2E1294D0 for <media-types@ietfa.amsl.com>; Sun, 25 Nov 2018 23:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MoO7IxEaFhdM for <media-types@ietfa.amsl.com>; Sun, 25 Nov 2018 23:58:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 625D3130DC7 for <media-types@ietf.org>; Sun, 25 Nov 2018 23:58:53 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id ADA67A3BA6C34 for <media-types@ietf.org>; Mon, 26 Nov 2018 07:58:48 +0000 (GMT)
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 26 Nov 2018 07:58:50 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.140]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0415.000; Mon, 26 Nov 2018 15:58:40 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: "media-types@ietf.org" <media-types@ietf.org>
Thread-Topic: registeration of audio/video/text/application flexfec media subtypes
Thread-Index: AdSCadb67+0YbePGTJW14ARj+KchGQ==
Date: Mon, 26 Nov 2018 07:58:40 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18C809D7@dggemm526-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.166]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD18C809D7dggemm526mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/l51sS-ebyvtyJ0iMMlBCrFqekHQ>
Subject: [media-types] registeration of audio/video/text/application flexfec media subtypes
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2018 07:59:00 -0000
Hi, RTP payload formats for the Forward Error Correction (FEC) in https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11 is ready for publication as a Payload WG document The document registers flexfec subtype The new registration is in Section 5.1 of the document and is also given below. Comments on the registration are welcome. Thanks. Roni Even Payload WG co-chair 5.1.1<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-5.1.1>. Registration of audio/flexfec Type name: audio Subtype name: flexfec Required parameters: o rate: The RTP timestamp (clock) rate. The rate SHALL be larger than 1000 Hz to provide sufficient resolution to RTCP operations. However, it is RECOMMENDED to select the rate that matches the rate of the protected source RTP stream. o repair-window: The time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds. Optional parameters: o L: indicates the number of columns of the source block that are protected by this FEC block and it applies to all the source SSRCs. L is a positive integer. o D: indicates the number of rows of the source block that are protected by this FEC block and it applies to all the source SSRCs. D is a positive integer. o ToP: indicates the type of protection applied by the sender: 0 for 1-D interleaved FEC protection, 1 for 1-D non-interleaved FEC protection, 2 for 2-D parity FEC protection, and 3 for retransmission. There can only be one value listed for ToP. Note that both L and D in the optional parameters should follow the value pairings stated in Section 4.2.2.2<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.2.2.2> if included. Encoding considerations: This media type is framed (See Section 4.8<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.8> in the template document [RFC6838<https://tools.ietf.org/html/rfc6838>]) and contains binary data. Security considerations: See Section 9<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-9> of [RFCXXXX]. Interoperability considerations: None. Published specification: [RFCXXXX]. Applications that use this media type: Multimedia applications that want to improve resiliency against packet loss by sending redundant data in addition to the source media. Fragment identifier considerations: None. Additional information: None. Person & email address to contact for further information: Varun Singh <varun@callstats.io> and IETF Audio/Video Transport Payloads Working Group. Intended usage: COMMON. Restriction on usage: This media type depends on RTP framing, and hence, is only defined for transport via RTP [RFC3550<https://tools.ietf.org/html/rfc3550>]. Author: Varun Singh <varun@callstats.io>. Change controller: IETF Audio/Video Transport Working Group delegated from the IESG. Provisional registration? (standards tree only): Yes. 5.1.2<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-5.1.2>. Registration of video/flexfec Type name: video Subtype name: flexfec Required parameters: o rate: The RTP timestamp (clock) rate. The rate SHALL be larger than 1000 Hz to provide sufficient resolution to RTCP operations. However, it is RECOMMENDED to select the rate that matches the rate of the protected source RTP stream. o repair-window: The time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds. Optional parameters: o L: indicates the number of columns of the source block that are protected by this FEC block and it applies to all the source SSRCs. L is a positive integer. o D: indicates the number of rows of the source block that are protected by this FEC block and it applies to all the source SSRCs. D is a positive integer. o ToP: indicates the type of protection applied by the sender: 0 for 1-D interleaved FEC protection, 1 for 1-D non-interleaved FEC protection, 2 for 2-D parity FEC protection, and 3 for retransmission. There can only be one value listed for ToP. Note that both L and D in the optional parameters should follow the value pairings stated in Section 4.2.2.2<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.2.2.2> if included. Encoding considerations: This media type is framed (See Section 4.8<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.8> in the template document [RFC6838<https://tools.ietf.org/html/rfc6838>]) and contains binary data. Security considerations: See Section 9<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-9> of [RFCXXXX]. Interoperability considerations: None. Published specification: [RFCXXXX]. Applications that use this media type: Multimedia applications that want to improve resiliency against packet loss by sending redundant data in addition to the source media. Fragment identifier considerations: None. Additional information: None. Person & email address to contact for further information: Varun Singh <varun@callstats.io> and IETF Audio/Video Transport Payloads Working Group. Intended usage: COMMON. Restriction on usage: This media type depends on RTP framing, and hence, is only defined for transport via RTP [RFC3550<https://tools.ietf.org/html/rfc3550>]. Author: Varun Singh <varun@callstats.io>. Change controller: IETF Audio/Video Transport Working Group delegated from the IESG. Provisional registration? (standards tree only): Yes. 5.1.3<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-5.1.3>. Registration of text/flexfec Type name: text Subtype name: flexfec Required parameters: o rate: The RTP timestamp (clock) rate. The rate SHALL be larger than 1000 Hz to provide sufficient resolution to RTCP operations. However, it is RECOMMENDED to select the rate that matches the rate of the protected source RTP stream. o repair-window: The time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds. Optional parameters: o L: indicates the number of columns of the source block that are protected by this FEC block and it applies to all the source SSRCs. L is a positive integer. o D: indicates the number of rows of the source block that are protected by this FEC block and it applies to all the source SSRCs. D is a positive integer. o ToP: indicates the type of protection applied by the sender: 0 for 1-D interleaved FEC protection, 1 for 1-D non-interleaved FEC protection, 2 for 2-D parity FEC protection, and 3 for retransmission. There can only be one value listed for ToP. Note that both L and D in the optional parameters should follow the value pairings stated in Section 4.2.2.2<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.2.2.2> if included. Encoding considerations: This media type is framed (See Section 4.8<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.8> in the template document [RFC6838<https://tools.ietf.org/html/rfc6838>]) and contains binary data. Security considerations: See Section 9<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-9> of [RFCXXXX]. Interoperability considerations: None. Published specification: [RFCXXXX]. Applications that use this media type: Multimedia applications that want to improve resiliency against packet loss by sending redundant data in addition to the source media. Fragment identifier considerations: None. Additional information: None. Person & email address to contact for further information: Varun Singh <vvarun@callstats.io> and IETF Audio/Video Transport Payloads Working Group. Intended usage: COMMON. Restriction on usage: This media type depends on RTP framing, and hence, is only defined for transport via RTP [RFC3550<https://tools.ietf.org/html/rfc3550>]. Author: Varun Singh <varun@callstats.io>. Change controller: IETF Audio/Video Transport Working Group delegated from the IESG. Provisional registration? (standards tree only): Yes. 5.1.4<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-5.1.4>. Registration of application/flexfec Type name: application Subtype name: flexfec Required parameters: o rate: The RTP timestamp (clock) rate. The rate SHALL be larger than 1000 Hz to provide sufficient resolution to RTCP operations. However, it is RECOMMENDED to select the rate that matches the rate of the protected source RTP stream. o repair-window: The time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds. Optional parameters: o L: indicates the number of columns of the source block that are protected by this FEC block and it applies to all the source SSRCs. L is a positive integer. o D: indicates the number of rows of the source block that are protected by this FEC block and it applies to all the source SSRCs. D is a positive integer. o ToP: indicates the type of protection applied by the sender: 0 for 1-D interleaved FEC protection, 1 for 1-D non-interleaved FEC protection, 2 for 2-D parity FEC protection, and 3 for retransmission. There can only be one value listed for ToP. Note that both L and D in the optional parameters should follow the value pairings stated in Section 4.2.2.2<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.2.2.2> if included. Encoding considerations: This media type is framed (See Section 4.8<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-4.8> in the template document [RFC6838<https://tools.ietf.org/html/rfc6838>]) and contains binary data. Security considerations: See Section 9<https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-11#section-9> of [RFCXXXX]. Interoperability considerations: None. Published specification: [RFCXXXX]. Applications that use this media type: Multimedia applications that want to improve resiliency against packet loss by sending redundant data in addition to the source media. Fragment identifier considerations: None. Additional information: None. Person & email address to contact for further information: Varun Singh <varun@callstats.io> and IETF Audio/Video Transport Payloads Working Group. Intended usage: COMMON. Restriction on usage: This media type depends on RTP framing, and hence, is only defined for transport via RTP [RFC3550<https://tools.ietf.org/html/rfc3550>]. Author: Varun Singh <varun@callstats.io>. Change controller: IETF Audio/Video Transport Working Group delegated from the IESG. Provisional registration? (standards tree only): Yes.
- [media-types] registeration of audio/video/text/a… Roni Even (A)