SIST-TS ETSI/TS 102 144 V1.1.1:2005

• Abstract:

  To endorse and constrain where relevant the RFCs 2960 and 3309 on SCTP.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI TS 102 144 V1.1.1 (2003-05) - Services and Protocols for Advanced Networks (SPAN); MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP); Stream Control Transmission Protocol (SCTP) [Endorsement of RFC 2960 and RFC 3309, modified]

SIST-TS ETSI/TS 102 144 V1.1.1:2005 is the Slovenian adoption of ETSI TS 102 144 V1.1.1, published by SIST and based on ETSI work in the SPAN series. It specifies how Stream Control Transmission Protocol (SCTP) is used with SIGTRAN adaptation layers to carry Signalling Systems No.7 (SS7) messages over Internet Protocol (IP), with modifications to RFC 2960 and RFC 3309. It is intended for people implementing, configuring, testing, or procuring SS7-over-IP transport.

What does SIST-TS ETSI/TS 102 144 V1.1.1:2005 specify?

SIST-TS ETSI/TS 102 144 V1.1.1:2005 specifies requirements for SCTP when it is used with SIGTRAN adaptation layers for transport of SS7 messages over IP. The document endorses RFC 2960 and RFC 3309, but constrains them where needed for this signalling use case.

The document is organized into scope, references, definitions and abbreviations, SCTP protocol considerations, and SCTP parameter considerations. In practice, that means it separates the protocol behavior rules from the configurable tuning values that operators and implementers need to set.

What are the key requirements of SIST-TS ETSI/TS 102 144 V1.1.1:2005?

The main requirements are concentrated in clause 4 and clause 5. They define how an SCTP endpoint should behave in a SIGTRAN environment and which parameters must be configurable for signalling transport.

Protocol behavior in clause 4

• Checksum - SCTP shall use CRC32C from RFC 3309 instead of the Adler32 checksum from RFC 2960. This matters because implementations must match the checksum expected by this profile.
• Streams and delivery - At least two incoming and two outgoing streams shall be supported, and the receiving side shall accept DATA chunks marked for unordered delivery. This gives enough stream capacity for signalling traffic and avoids rejecting valid incoming data.
• Path handling - Path MTU discovery is not required, but it shall be configurable, and an endpoint shall support two or more paths to a peer. If one destination address fails during association setup, the sender shall retry with an alternative known address. This supports resilience when network paths change.
• Packet sizing - SCTP packets carried in IP packets shall not exceed the Path MTU. INIT, INIT-ACK, DATA, and HEARTBEAT chunks shall be sized so the resulting IP packet stays within that limit. This helps avoid fragmentation problems in IP networks.
• Addressing - IPv4 address parameters shall be supported, IPv6 address parameters may be supported, and hostname address parameters shall not be supported. If a hostname appears in INIT or INIT-ACK, the receiver shall abort with the specified error cause. Singlehomed endpoints shall not include address parameters in INIT and INIT-ACK.
• Path supervision and congestion - HEARTBEAT support shall be present and enabled on idle paths by default, while Explicit Congestion Notification (ECN) is not required. In practice, endpoints need liveness checking, but not ECN support.
• User data handling - Endpoints shall support the user data size required by the upper layer; when Transport Layer Security is used, the supported size is given in the referenced guidance. If user data would produce DATA chunks too large for the Path MTU, the sender shall support fragmentation, and the receiver shall support reassembly.
• Bundling - An endpoint shall allow disabling of DATA-chunk bundling when bundling would add delay. This lets implementations reduce latency where needed.

Configurable parameters in clause 5

Clause 5 identifies SCTP parameters that shall be configurable, including retransmission timers, cookie lifetime, heartbeat interval, SACK timing/frequency, and MTU size. The table gives limits, default values from RFC 2960, and tuning granularity. For readers, this means SCTP stacks must expose operational settings rather than hard-coding one behavior.

What terms does SIST-TS ETSI/TS 102 144 V1.1.1:2005 define?

SIST-TS ETSI/TS 102 144 V1.1.1:2005 uses a short set of abbreviations that are central to the document.

• SCTP - Stream Control Transmission Protocol, the transport protocol being constrained by this document.
• IP - Internet Protocol, the network layer used to carry SCTP packets.
• IPv4 - Internet Protocol Version 4, which shall be supported as an address parameter.
• IPv6 - Internet Protocol Version 6, which may be supported as an address parameter.
• MTU - Maximum Transmission Unit, the size limit used to keep packets within the path limit.
• ECN - Explicit Congestion Notification, a congestion-signalling feature that is not required here.
• RFC - Request for Comment, the IETF document type used for the endorsed SCTP specifications.

Who uses SIST-TS ETSI/TS 102 144 V1.1.1:2005?

SIST-TS ETSI/TS 102 144 V1.1.1:2005 is used by telecom engineers and vendors implementing SIGTRAN and SS7-over-IP systems. It is also relevant to network architects, test engineers, and quality teams that need to verify SCTP behavior, address handling, multihoming, heartbeat operation, fragmentation, and timer settings in signalling equipment.

Which standards are used with SIST-TS ETSI/TS 102 144 V1.1.1:2005?

The document is based on and modifies these referenced specifications:

• IETF RFC 2960 - the original SCTP specification.
• IETF RFC 3309 - defines the CRC32C checksum change used here.
• IETF RFC 3436 - provides SCTP guidance for Transport Layer Security when that combination is used.
• ETSI TS 102 141 - M2UA for SPAN and SIGTRAN.
• ETSI TS 102 142 - M3UA for SPAN and SIGTRAN.
• ETSI TS 102 143 - SUA for SPAN and SIGTRAN.

These references show where the SCTP rules fit into the wider SIGTRAN transport stack and when related ETSI profiles matter.

What does the SIST-TS ETSI/TS 102 144 V1.1.1:2005 document contain?

SIST-TS ETSI/TS 102 144 V1.1.1:2005 contains the endorsement notice, the scope, the reference list, definitions and abbreviations, and two technical clauses. Clause 4 covers checksum selection, streams, Path MTU discovery, multihoming, chunk sizing, addressing methods, path supervision, user data size, fragmentation, unordered delivery, bundling, and ECN. Clause 5 provides a parameter table for SCTP tuning and explains SACK timing and frequency.

SLOVENSKI STANDARD
01-januar-2005
Storitve in protokoli za napredna omrežja (SPAN) – MTP/SCCP/SSCOP in SIGTRAN
(prenos SS7 preko IP) – Transportni protokol krmiljenja toka (SCTP) [privzeta RFC
2960 in RFC 3309, spremenjena]
Services and Protocols for Advanced Networks (SPAN); MTP/SCCP/SSCOP and
SIGTRAN (Transport of SS7 over IP); Stream Control Transmission Protocol (SCTP)
[Endorsement of RFC 2960 and RFC 3309, modified]
Ta slovenski standard je istoveten z: TS 102 144 Version 1.1.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Services and Protocols for Advanced Networks (SPAN);
MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP);
Stream Control Transmission Protocol (SCTP)
[Endorsement of RFC 2960 and RFC 3309, modified]

2 ETSI TS 102 144 V1.1.1 (2003-05)

Reference
DTS/SPAN-130265
Keywords
MTP, SCCP, SCTP, SIGTRAN, SS7,
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 144 V1.1.1 (2003-05)
Contents
Intellectual Property Rights.4
Foreword.4
Endorsement notice .4
Introduction .4
1 Scope.5
2 References.5
3 Definitions and abbreviations.5
3.1 Definitions.5
3.2 Abbreviations.5
4 SCTP protocol considerations.6
4.1 SCTP checksum.6
4.2 SCTP streams.6
4.3 Path MTU discovery .6
4.4 Multihoming.6
4.5 SCTP chunk size .6
4.6 Addressing methods.6
4.7 Path supervision.6
4.8 User data size .7
4.9 User data fragmentation .7
4.10 Unordered delivery of DATA chunks .7
4.11 Bundling of DATA chunks .7
4.12 Explicit Congestion Notification (ECN) .7
5 SCTP parameter considerations .7
History .8

ETSI
4 ETSI TS 102 144 V1.1.1 (2003-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This Technical Specification (TS) has been produced by ETSI Techn
...