RFC 9260
1. Introduction
▶SCTP provides reliable, message-oriented transport with support for multi-homing (multiple IP addresses per endpoint) and multi-streaming (multiple independent message streams within an association). It was originally designed for signaling transport (SIGTRAN) and is widely used in telecom.
In 3GPP, SCTP carries Diameter messages (AAA signaling), NGAP (5G NR control plane between gNB and AMF), S1AP (LTE control plane), and X2AP/XnAP (inter-base-station handover signaling).
2. Key Features for 3GPP
▶| Feature | Description | 3GPP Benefit |
|---|---|---|
| Multi-homing | Multiple IP addresses per endpoint | Network resilience — automatic failover between paths |
| Multi-streaming | Independent ordered streams within association | No head-of-line blocking across streams |
| Message boundaries | Preserves application message boundaries | Diameter message framing without length headers |
| 4-way handshake | INIT → INIT-ACK → COOKIE-ECHO → COOKIE-ACK | DoS protection via stateless cookies |
| Heartbeat | PATH MTU discovery and path monitoring | Detect path failures for multi-homed endpoints |
| Ordered/unordered delivery | Per-stream ordering control | Flexibility for different message priorities |
3. Association Setup
▶The 4-way handshake protects against SYN flood attacks — the server does not allocate state until the COOKIE-ECHO is received with a valid cookie.
Client (gNB) Server (AMF) | | | INIT | | [Initiate Tag, A-RWND, | | Number of Outbound Streams, | | Number of Inbound Streams, | | Initial TSN] | |--------------------------------->| | | | INIT-ACK | | [Initiate Tag, A-RWND, | | State Cookie, | | Supported Extensions] | |<---------------------------------| | | | COOKIE-ECHO | | [State Cookie] | |--------------------------------->| | | | COOKIE-ACK | |<---------------------------------| | | | [SCTP Association Established] |
4. 3GPP Interface Mapping
▶| Interface | Application Protocol | Transport | Network Segment |
|---|---|---|---|
| NG-C (N2) | NGAP | SCTP | gNB ↔ AMF |
| Xn-C | XnAP | SCTP | gNB ↔ gNB |
| S6a/S6d | Diameter | SCTP | MME ↔ HSS |
| Gx | Diameter | SCTP | PCEF ↔ PCRF |
| S1-MME | S1AP | SCTP | eNB ↔ MME |
| X2-C | X2AP | SCTP | eNB ↔ eNB |
5. Security Considerations
▶- SCTP itself provides no encryption — relies on IPsec (RFC 4301) or DTLS (RFC 6083) for security
- The cookie mechanism in INIT protects against blind connection flooding
- SCTP multi-homing improves availability but increases attack surface — all addresses must be secured
- Implementations must handle ABORT chunks carefully to prevent association hijacking