SCTP packet structure and common chunk types explained

Stream Control Transmission Protocol (SCTP) carries signalling and other message-oriented traffic across IP networks. Unlike TCP, it supports multistreaming, multihoming and message boundaries, which makes it valuable in SIGTRAN deployments connecting SS7 networks to modern packet infrastructure.

Understanding the packet layout helps engineers troubleshoot associations, inspect call-control traffic and interpret captures from systems used by carriers, utilities and enterprise platforms. The same knowledge applies whether traffic is crossing a Sydney data centre, a Melbourne exchange or a long-haul link serving regional Western Australia.

The common header

Every SCTP packet begins with a 12-byte common header. It contains a source port, destination port, verification tag and checksum. The port fields are each 16 bits, while the verification tag and CRC-32c checksum are each 32 bits.

The verification tag identifies the association and helps reject packets that do not belong to the current session. During the initial exchange, the tag has special handling: an INIT uses a zero value, while the INIT ACK supplies a tag that subsequent packets must use. The checksum provides integrity protection against accidental corruption.

After the common header, one or more chunks follow. A packet may therefore carry control information and user data together, subject to the path MTU. Chunk boundaries are important because SCTP remains message-oriented rather than presenting a continuous byte stream like TCP.

How chunks are arranged

Each chunk starts with a four-byte header: an eight-bit type, eight-bit flags field and 16-bit length. The length covers the chunk header and its content, but not any padding added to align the next chunk on a four-byte boundary.

A receiver uses the type value to decide how to parse the chunk. Flags are interpreted according to the chunk definition; unknown flags are generally handled according to the relevant RFC rules. A malformed length can make the remainder of the packet impossible to parse, so packet analysers should validate both the declared size and available capture bytes.

The association setup follows a cookie-based exchange. INIT advertises capabilities, addresses, inbound and outbound stream counts, and an initiation tag. INIT ACK returns similar information plus a state cookie. COOKIE ECHO proves that the endpoint received the cookie, and COOKIE ACK confirms the association. This approach limits exposure to certain resource-exhaustion attacks.

For engineers mapping SS7 over IP, SIGTRAN solutions provide useful context around how SCTP supports protocols such as M3UA and its relationship with MTP3-style signalling functions.

Core control and data chunks

The DATA chunk transports an upper-layer message. Its flags indicate whether the chunk begins or ends a complete message, and a stream identifier plus stream sequence number supports ordered delivery within a stream. The transmission sequence number is used for acknowledgement and loss recovery.

SACK, or Selective Acknowledgement, reports cumulative receipt, gaps and duplicate transmission sequence numbers. It lets the sender retransmit missing chunks without resending everything that arrived successfully. HEARTBEAT and HEARTBEAT ACK test path reachability, which is particularly useful when an association has multiple network addresses.

ABORT terminates an association immediately, while SHUTDOWN, SHUTDOWN ACK and SHUTDOWN COMPLETE support an orderly close. ERROR reports protocol problems. The FORWARD TSN chunk supports partial reliability by allowing abandoned data to be skipped; I-DATA extends data transfer for interleaving in implementations that support RFC 8260.

Reading flags requires the same care as interpreting any protocol signal: context matters more than one isolated bit. A useful analogy is reading play cues, where a single movement can be misleading without the surrounding behaviour.

Recognising chunks in a packet capture

A packet capture normally displays the common header first, followed by chunks in sequence. Start by checking the association, verification tag and checksum status. Then inspect the chunk type, length, flags and any stream or transmission sequence numbers.

In Australia, troubleshooting may involve a carrier link between Sydney and Brisbane, a cloud-hosted signalling platform in Melbourne, or a multihomed service supporting remote facilities near Perth or Darwin. Differences in path delay and failover behaviour can expose timer issues that are not visible in a small office test.

Australian operators must also consider operational governance. Packet captures can contain subscriber or routing information, so retention and access controls should align with the Privacy Act 1988. Telecommunications environments may also involve obligations under the Telecommunications (Interception and Access) Act 1979, along with network and emergency-service requirements overseen by the Australian Communications and Media Authority.

Field reference and practical checks

The following summary is useful when reading a hexadecimal dump or Wireshark dissection:

Chunk Type value Main purpose
DATA 0 Carries an upper-layer message
INIT 1 Starts association negotiation
INIT ACK 2 Responds and supplies a cookie
SACK 3 Acknowledges received data
HEARTBEAT 4 Tests a path
HEARTBEAT ACK 5 Confirms path testing
ABORT 6 Stops an association immediately
SHUTDOWN 7 Begins graceful closure
COOKIE ECHO 10 Returns the setup cookie
COOKIE ACK 11 Confirms cookie processing
SHUTDOWN COMPLETE 14 Completes graceful closure
I-DATA 64 Supports interleaved message delivery
FORWARD TSN 192 Advances delivery past abandoned data

Practical inspection priorities

  • Confirm that the packet checksum and declared lengths are valid.
  • Match verification tags to the correct SCTP association.
  • Check SACK gaps, duplicate TSNs and retransmission timing.
  • Review INIT parameters for stream counts, addresses and supported extensions.
  • Compare HEARTBEAT results with interface failover and route changes.

A healthy trace generally shows a coherent INIT exchange, cookie completion, DATA traffic and timely SACK responses. Repeated INIT attempts, missing COOKIE ACK messages or growing SACK gaps may indicate filtering, MTU problems, asymmetric routing or an overloaded endpoint.

A concrete first step is to capture one controlled SCTP association and label every common-header field and chunk before investigating higher-layer SS7 messages.