{
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Correct equation solving cannot establish that accepted data are authentic; verification remains a separate requirement.",
      "citationIds": [
        "rfc6330"
      ]
    }
  ],
  "related": [
    "raptor-code",
    "fountain-code",
    "lt-code",
    "erasure-coding",
    "systematic-code"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "slug": "raptorq",
  "term": "RaptorQ",
  "aliases": [
    "RaptorQ code"
  ],
  "definition": "RaptorQ is the systematic fountain code specified in RFC 6330 for source-block recovery using original source symbols and generated repair symbols.",
  "note": "RaptorQ encodes source blocks independently. Extra symbols for one block cannot repair another block's missing information. Object-wide packet counts therefore cannot establish complete recovery. Decoding needs the object transmission information and the matching block and symbol identifiers. [rfc6330]\n\nIts four-byte FEC Payload ID uses an 8-bit source-block number and a 24-bit encoding-symbol identifier. Bytes 01 02 03 04 identify block 1 and symbol 131844, unlike the Raptor layout. This is a field-layout example, not an encoded-packet validation. [rfc6330] [rfc5053]\n\nRFC 6330's failure bounds use supported extended block sizes K' and independently, uniformly selected identifiers. They are conditional requirements, not a guarantee for every K-symbol set or a measured storage-loss rate. Source blocks may be padded from K to K'; with multiple sub-blocks, a symbol need not be a contiguous slice of the object. [rfc6330]\n\nVerified erratum 5548 corrects the transfer-length limit to 942574504275 octets: 56403 x 65535 x 255. The 8-bit block-count field Z cannot represent 256. The width of a block identifier does not establish the number of blocks an object can contain. [erratum5548]",
  "citations": [
    {
      "id": "rfc6330",
      "title": "Luby et al. RFC 6330 (2011), sections 3, 4.4, 5.3.1, 5.8 and 6: RaptorQ blocks, identifiers and conditional recovery.",
      "url": "https://www.rfc-editor.org/rfc/rfc6330.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "rfc5053",
      "title": "Luby et al. RFC 5053 (2007), section 3.1: Raptor uses a different FEC Payload ID layout.",
      "url": "https://www.rfc-editor.org/rfc/rfc5053.html#section-3.1",
      "accessed": "2026-11-21"
    },
    {
      "id": "erratum5548",
      "title": "RFC 6330 technical erratum 5548, section 3.3.2: block-count and transfer-length correction, verified 2 June 2020.",
      "url": "https://www.rfc-editor.org/errata/eid5548",
      "accessed": "2026-11-21"
    }
  ],
  "provenance": [
    "RFC requirements and exact field-layout arithmetic are distinguished from codec execution and storage-fleet evidence."
  ]
}
