1d Interleaved ParityfecIANA Registered

MIME: video/1d-interleaved-parityfec
Extensions: —
{
  "full": "video/1d-interleaved-parityfec",
  "type": "video",
  "subtype": "1d-interleaved-parityfec",
  "extensions": [],
  "iana": {
    "template_url": "https://www.iana.org/assignments/media-types/video/1d-interleaved-parityfec",
    "type_name": "video",
    "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\nSHALL be larger than 1000 to provide sufficient resolution to RTCP\noperations. However, it is RECOMMENDED to select the rate that\nmatches the rate of the protected source RTP stream."
        },
        {
          "name": "L",
          "description": "Number of columns of the source block. L is a positive integer\nthat is less than or equal to 255."
        },
        {
          "name": "D",
          "description": "Number of rows of the source block. D is a positive integer\nthat is less than or equal to 255."
        },
        {
          "name": "repair-window",
          "description": "The time that spans the FEC block (i.e., source\npackets and the corresponding repair packets). An FEC encoder\nprocesses a block of source packets and generates a number of\nrepair packets, which are then transmitted within a certain\nduration not larger than the value of the repair window. At the\nreceiver side, the FEC decoder should wait at least for the\nduration of the repair window after getting the first packet in an\nFEC block to allow all the repair packets to arrive (the waiting\ntime can be adjusted if there are missing packets at the beginning\nof the FEC block). The FEC decoder can start decoding the already\nreceived packets sooner; however, it SHOULD NOT register an FEC\ndecoding failure until it waits at least for the repair-window\nduration. The size of the repair window is specified in\nmicroseconds.\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]"
  }
}