| < draft-ietf-payload-flexible-fec-scheme-15.txt | draft-ietf-payload-flexible-fec-scheme-16.txt > | |||
|---|---|---|---|---|
| PAYLOAD M. Zanaty | PAYLOAD M. Zanaty | |||
| Internet-Draft Cisco | Internet-Draft Cisco | |||
| Intended status: Standards Track V. Singh | Intended status: Standards Track V. Singh | |||
| Expires: July 17, 2019 callstats.io | Expires: July 21, 2019 callstats.io | |||
| A. Begen | A. Begen | |||
| Networked Media | Networked Media | |||
| G. Mandyam | G. Mandyam | |||
| Qualcomm Inc. | Qualcomm Inc. | |||
| January 13, 2019 | January 17, 2019 | |||
| RTP Payload Format for Flexible Forward Error Correction (FEC) | RTP Payload Format for Flexible Forward Error Correction (FEC) | |||
| draft-ietf-payload-flexible-fec-scheme-15 | draft-ietf-payload-flexible-fec-scheme-16 | |||
| Abstract | Abstract | |||
| This document defines new RTP payload formats for the Forward Error | This document defines new RTP payload formats for the Forward Error | |||
| Correction (FEC) packets that are generated by the non-interleaved | Correction (FEC) packets that are generated by the non-interleaved | |||
| and interleaved parity codes from source media encapsulated in RTP. | and interleaved parity codes from source media encapsulated in RTP. | |||
| These parity codes are systematic codes, where a number of FEC repair | These parity codes are systematic codes, where a number of FEC repair | |||
| packets are generated from a set of source packets from one or more | packets are generated from a set of source packets from one or more | |||
| source RTP streams. These FEC repair packets are sent in a | source RTP streams. These FEC repair packets are sent in a | |||
| redundancy RTP stream separate from the source RTP stream(s) that | redundancy RTP stream separate from the source RTP stream(s) that | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on July 17, 2019. | This Internet-Draft will expire on July 21, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 26, line 28 ¶ | skipping to change at page 26, line 28 ¶ | |||
| Published specification: [RFCXXXX]. | Published specification: [RFCXXXX]. | |||
| Applications that use this media type: Multimedia applications that | Applications that use this media type: Multimedia applications that | |||
| want to improve resiliency against packet loss by sending redundant | want to improve resiliency against packet loss by sending redundant | |||
| data in addition to the source media. | data in addition to the source media. | |||
| Fragment identifier considerations: None. | Fragment identifier considerations: None. | |||
| Additional information: None. | Additional information: None. | |||
| Person & email address to contact for further information: Varun | Person & email address to contact for further information: IESG | |||
| Singh <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working | <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working Group | |||
| Group (or it's successor as delegated by the IESG). | (or it's successor as delegated by the IESG). | |||
| Intended usage: COMMON. | Intended usage: COMMON. | |||
| Restriction on usage: This media type depends on RTP framing, and | Restriction on usage: This media type depends on RTP framing, and | |||
| hence, is only defined for transport via RTP [RFC3550]. | hence, is only defined for transport via RTP [RFC3550]. | |||
| Author: Varun Singh <iesg@ietf.org>. | Author: Varun Singh <varun@callstats.io>. | |||
| Change controller: IETF Audio/Video Transport Payloads Working Group | Change controller: IETF Audio/Video Transport Payloads Working Group | |||
| delegated from the IESG (or it's successor as delegated by the IESG). | delegated from the IESG (or it's successor as delegated by the IESG). | |||
| 5.1.2. Registration of video/flexfec | 5.1.2. Registration of video/flexfec | |||
| Type name: video | Type name: video | |||
| Subtype name: flexfec | Subtype name: flexfec | |||
| skipping to change at page 27, line 49 ¶ | skipping to change at page 27, line 49 ¶ | |||
| Published specification: [RFCXXXX]. | Published specification: [RFCXXXX]. | |||
| Applications that use this media type: Multimedia applications that | Applications that use this media type: Multimedia applications that | |||
| want to improve resiliency against packet loss by sending redundant | want to improve resiliency against packet loss by sending redundant | |||
| data in addition to the source media. | data in addition to the source media. | |||
| Fragment identifier considerations: None. | Fragment identifier considerations: None. | |||
| Additional information: None. | Additional information: None. | |||
| Person & email address to contact for further information: Varun | Person & email address to contact for further information: IESG | |||
| Singh <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working | <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working Group | |||
| Group (or it's successor as delegated by the IESG). | (or it's successor as delegated by the IESG). | |||
| Intended usage: COMMON. | Intended usage: COMMON. | |||
| Restriction on usage: This media type depends on RTP framing, and | Restriction on usage: This media type depends on RTP framing, and | |||
| hence, is only defined for transport via RTP [RFC3550]. | hence, is only defined for transport via RTP [RFC3550]. | |||
| Author: Varun Singh <iesg@ietf.org>. | Author: Varun Singh <varun@callstats.io>. | |||
| Change controller: IETF Audio/Video Transport Payloads Working Group | Change controller: IETF Audio/Video Transport Payloads Working Group | |||
| delegated from the IESG (or it's successor as delegated by the IESG). | delegated from the IESG (or it's successor as delegated by the IESG). | |||
| 5.1.3. Registration of text/flexfec | 5.1.3. Registration of text/flexfec | |||
| Type name: text | Type name: text | |||
| Subtype name: flexfec | Subtype name: flexfec | |||
| skipping to change at page 29, line 22 ¶ | skipping to change at page 29, line 22 ¶ | |||
| Published specification: [RFCXXXX]. | Published specification: [RFCXXXX]. | |||
| Applications that use this media type: Multimedia applications that | Applications that use this media type: Multimedia applications that | |||
| want to improve resiliency against packet loss by sending redundant | want to improve resiliency against packet loss by sending redundant | |||
| data in addition to the source media. | data in addition to the source media. | |||
| Fragment identifier considerations: None. | Fragment identifier considerations: None. | |||
| Additional information: None. | Additional information: None. | |||
| Person & email address to contact for further information: Varun | Person & email address to contact for further information: IESG | |||
| Singh <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working | <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working Group | |||
| Group (or it's successor as delegated by the IESG). | (or it's successor as delegated by the IESG). | |||
| Intended usage: COMMON. | Intended usage: COMMON. | |||
| Restriction on usage: This media type depends on RTP framing, and | Restriction on usage: This media type depends on RTP framing, and | |||
| hence, is only defined for transport via RTP [RFC3550]. | hence, is only defined for transport via RTP [RFC3550]. | |||
| Author: Varun Singh <iesg@ietf.org>. | Author: Varun Singh <varun@callstats.io>. | |||
| Change controller: IETF Audio/Video Transport Payloads Working Group | Change controller: IETF Audio/Video Transport Payloads Working Group | |||
| delegated from the IESG (or it's successor as delegated by the IESG). | delegated from the IESG (or it's successor as delegated by the IESG). | |||
| 5.1.4. Registration of application/flexfec | 5.1.4. Registration of application/flexfec | |||
| Type name: application | Type name: application | |||
| Subtype name: flexfec | Subtype name: flexfec | |||
| skipping to change at page 30, line 42 ¶ | skipping to change at page 30, line 42 ¶ | |||
| Published specification: [RFCXXXX]. | Published specification: [RFCXXXX]. | |||
| Applications that use this media type: Multimedia applications that | Applications that use this media type: Multimedia applications that | |||
| want to improve resiliency against packet loss by sending redundant | want to improve resiliency against packet loss by sending redundant | |||
| data in addition to the source media. | data in addition to the source media. | |||
| Fragment identifier considerations: None. | Fragment identifier considerations: None. | |||
| Additional information: None. | Additional information: None. | |||
| Person & email address to contact for further information: Varun | Person & email address to contact for further information: IESG | |||
| Singh <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working | <iesg@ietf.org> and IETF Audio/Video Transport Payloads Working Group | |||
| Group (or it's successor as delegated by the IESG). | (or it's successor as delegated by the IESG). | |||
| Intended usage: COMMON. | Intended usage: COMMON. | |||
| Restriction on usage: This media type depends on RTP framing, and | Restriction on usage: This media type depends on RTP framing, and | |||
| hence, is only defined for transport via RTP [RFC3550]. | hence, is only defined for transport via RTP [RFC3550]. | |||
| Author: Varun Singh <iesg@ietf.org>. | Author: Varun Singh <varun@callstats.io>. | |||
| Change controller: IETF Audio/Video Transport Payloads Working Group | Change controller: IETF Audio/Video Transport Payloads Working Group | |||
| delegated from the IESG (or it's successor as delegated by the IESG). | delegated from the IESG (or it's successor as delegated by the IESG). | |||
| 5.2. Mapping to SDP Parameters | 5.2. Mapping to SDP Parameters | |||
| Applications that use the RTP transport commonly use Session | Applications that use the RTP transport commonly use Session | |||
| Description Protocol (SDP) [RFC4566] to describe their RTP sessions. | Description Protocol (SDP) [RFC4566] to describe their RTP sessions. | |||
| The information that is used to specify the media types in an RTP | The information that is used to specify the media types in an RTP | |||
| session has specific mappings to the fields in an SDP description. | session has specific mappings to the fields in an SDP description. | |||
| End of changes. 12 change blocks. | ||||
| 20 lines changed or deleted | 20 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||