{
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Erasure correction is not authentication; protect payloads and decoding metadata against undetected modification.",
      "citationIds": [
        "rfc5053"
      ]
    }
  ],
  "related": [
    "raptorq",
    "fountain-code",
    "lt-code",
    "erasure-coding",
    "systematic-code"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "slug": "raptor-code",
  "term": "Raptor code",
  "aliases": [
    "Raptor codes"
  ],
  "definition": "A Raptor code combines a precode with LT encoding to generate repair symbols for recovering a source block from received encoding symbols.",
  "note": "RFC 5053 specifies a systematic Raptor scheme. Unchanged source symbols are available alongside repair symbols. Encoding first derives intermediate symbols subject to precode constraints, then applies LT encoding. Intermediate symbols are not simply the transmitted source symbols. [rfc5053]\n\nIts four-byte FEC Payload ID assigns 16 bits each to the source-block number and encoding-symbol identifier. Bytes 01 02 03 04 therefore identify block 258 and symbol 772. Object transmission information supplies the decoding context. The example checks field interpretation, not a complete encoded packet. [rfc5053]\n\nSuccessful decoding requires a full-rank system for the intermediate symbols. Systematic layout does not provide an MDS any-subset guarantee. RaptorQ is a different scheme, not an interchangeable name or wire format. [rfc5053] [rfc6330]\n\nThe precode lets the LT stage leave some intermediate symbols unrecovered; its erasure correction then fills those gaps. This relaxes the LT stage's requirement to cover every input symbol. The precode and LT degree distribution must be designed together. [shokrollahi2006]",
  "citations": [
    {
      "id": "rfc5053",
      "title": "Luby et al. RFC 5053 (2007), sections 1, 3, 4.1, 5.4, 5.5.2 and 6: systematic Raptor and recovery.",
      "url": "https://www.rfc-editor.org/rfc/rfc5053.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "rfc6330",
      "title": "Luby et al. RFC 6330 (2011), sections 1 and 3.2: distinct RaptorQ scheme and payload identifiers.",
      "url": "https://www.rfc-editor.org/rfc/rfc6330.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "shokrollahi2006",
      "title": "Shokrollahi. Raptor Codes. IEEE Transactions on Information Theory 52(6), 2551-2567 (2006), section IV. DOI: 10.1109/TIT.2006.874390.",
      "url": "https://people.ece.ubc.ca/janm/Papers_RG/Shokrollahi_IT_June06.pdf",
      "accessed": "2026-11-21"
    }
  ],
  "provenance": [
    "The generic construction and RFC 5053 scheme are distinguished. The byte example is constructed arithmetic, not execution of an FEC codec."
  ]
}
