1d Interleaved ParityfecIANA Registered
MIME: audio/1d-interleaved-parityfec
Extensions: —
{
"full": "audio/1d-interleaved-parityfec",
"type": "audio",
"subtype": "1d-interleaved-parityfec",
"extensions": [],
"iana": {
"template_url": "https://www.iana.org/assignments/media-types/audio/1d-interleaved-parityfec",
"type_name": "audio",
"subtype_name": "1d-interleaved-parityfec",
"encoding_considerations": "in the template document [RFC4288]) and contains binary data.\n\nSecurity considerations: See Section 9 of [RFC6015].\n\nInteroperability considerations: None.\n\nPublished specification: [RFC6015].\n\nApplications that use this media type: Multimedia applications that\nwant to improve resiliency against packet loss by sending redundant\ndata in addition to the source media.\n\nAdditional information: None.\n\nPerson & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG.",
"security_considerations": "Interoperability considerations: None.\n\nPublished specification: [RFC6015].\n\nApplications that use this media type: Multimedia applications that\nwant to improve resiliency against packet loss by sending redundant\ndata in addition to the source media.\n\nAdditional information: None.\n\nPerson & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG.",
"interoperability_considerations": "Published specification: [RFC6015].\n\nApplications that use this media type: Multimedia applications that\nwant to improve resiliency against packet loss by sending redundant\ndata in addition to the source media.\n\nAdditional information: None.\n\nPerson & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG.",
"applications": "want to improve resiliency against packet loss by sending redundant\ndata in addition to the source media.\n\nAdditional information: None.\n\nPerson & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG.",
"additional_information": "Person & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG.",
"intended_usage": "common",
"restrictions_on_usage": "This media type depends on RTP framing, and",
"change_controller": "IETF Audio/Video Transport Working Group delegated",
"parameters": {
"required": [
{
"name": "rate",
"description": "The RTP timestamp (clock) rate in Hz. The (integer) rate\n SHALL be larger than 1000 to provide sufficient resolution to RTCP\n operations. However, it is RECOMMENDED to select the rate that\n matches the rate of the protected source RTP stream."
},
{
"name": "L",
"description": "Number of columns of the source block. L is a positive integer\n that is less than or equal to 255."
},
{
"name": "D",
"description": "Number of rows of the source block. D is a positive integer\n that is less than or equal to 255."
},
{
"name": "repair-window",
"description": "The time that spans the FEC block (i.e., source\n packets and the corresponding repair packets). An FEC encoder\n processes a block of source packets and generates a number of\n repair packets, which are then transmitted within a certain\n duration not larger than the value of the repair window. At the\n receiver side, the FEC decoder should wait at least for the\n duration of the repair window after getting the first packet in an\n FEC block to allow all the repair packets to arrive (the waiting\n time can be adjusted if there are missing packets at the beginning\n of the FEC block). The FEC decoder can start decoding the already\n received packets sooner; however, it SHOULD NOT register an FEC\n decoding failure until it waits at least for the repair-window\n duration. The size of the repair window is specified in\n microseconds.\n\nOptional parameters: None.\n\nEncoding considerations: This media type is framed (see Section 4.8\nin the template document [RFC4288]) and contains binary data.\n\nSecurity considerations: See Section 9 of [RFC6015].\n\nInteroperability considerations: None.\n\nPublished specification: [RFC6015].\n\nApplications that use this media type: Multimedia applications that\nwant to improve resiliency against packet loss by sending redundant\ndata in addition to the source media.\n\nAdditional information: None.\n\nPerson & email address to contact for further information: Ali Begen\n<abegen&cisco.com> and the IETF Audio/Video Transport Working Group.\n\nIntended usage: COMMON.\n\nRestriction on usage: This media type depends on RTP framing, and\nhence, is only defined for transport via RTP [RFC3550].\n\nAuthor: Ali Begen <abegen&cisco.com>.\n\nChange controller: IETF Audio/Video Transport Working Group delegated\nfrom the IESG."
}
],
"optional": []
},
"template_text": "[omitted]"
}
}