Chap 13 Modified PP2003

Chapter 13
Stream Control
Transmission Protocol
Objectives
Upon completion you will be able to:
Be able to name and understand the services offered by SCTP
Understand SCTPs flow and error control and congestion control
Be familiar with the fields in a SCTP segment
Understand the phases in an SCTP association
Understand the SCTP state transition diagram
TCP/IP Protocol Suite
Figure 13.1
TCP/IP protocol suite
SCTP combines the better features of UDP and TCP

SCTP is reliable, message-oriented (preserves the message
boundaries and at the same time detects lost data, duplicate
data and out of order data)
It also has congestion control and flow control mechanisms.
SCTP uses all well-known ports in the TCP space.
Table 13.1 lists some extra port numbers used by SCTP.
Table 13.1 Some SCTP applications
Figure 13.2
Multiple-stream concept
In TCP, each connection between a client and a server involve

a single stream and is called an association in SCTP.
SCTP allows multiple streams. If one stream is blocked, the
other streams can still deliver data. Very useful for real-time
applications.
Note:
SCTP association allows multiple IP
addresses for each end.
Figure 13.3
Multihoming concept
Multiple sources and multiple receivers allows

for a fault-tolerant approach
Note:
In SCTP, a data chunk is numbered
using a TSN.
Note:
To distinguish between different
streams, SCTP uses a SI.
Note:
To distinguish between different data
chunks belonging to the same stream,
SCTP uses SSNs.
Figure 13.4
Comparison between a TCP segment and an SCTP packet
10
Figure 13.4
Comparison between a TCP segment and an SCTP packet
An association may send many packets, a packet may contain

several chunks, and chunks may belong to different streams.
SCTP control info is in the Control chunk.
Data chunks can carry data from multiple streams.
No options section. Options in SCTP are handled by defining n
Chunk types.
SCTP header is smaller only 12 bytes
SCTP uses a 32-bit checksum
11
Note:
TCP has segments;
SCTP has packets.
12
Note:
In SCTP, control information and data
information are carried in separate
chunks.
13
Figure 13.5
Packet, data chunks, and streams
14
Note:
Transmission Sequence Number (TSN)

Stream Identifier (SI)
Stream Sequence Number (SSN)
Data chunks are identified by three

identifiers: TSN, SI, and SSN.
TSN is a cumulative number
identifying the association; SI defines
the stream; SSN defines the chunk in
a stream.
15
Note:
In SCTP, acknowledgment numbers
are used to acknowledge only data
chunks; control chunks are
acknowledged by other control chunks
if necessary.
16
13.3 PACKET FORMAT

We show the format of a packet and different types of chunks. An SCTP
packet has a mandatory general header and a set of blocks called
chunks. There are two types of chunks: control chunks and data chunks.
The topics discussed in this section include:

General Header
Chunks
17
Figure 13.6
SCTP packet format
18
Note:
In an SCTP packet, control chunks
come before data chunks.
19
Figure 13.7 General header

General header always comes first.
Verification tag: a number that matches a packet to an
association.
There is a verification used for each direction in the
association.
CRC-32 checksum.
20
Figure 13.8
Common layout of a chunk
Control chunks come before data chunks.

Type: can define up to 256 types of chunks (only a few
have been defined so far; the rest are reserved for
future use.
Flag: define special flags that a particular chunk may
need. Each bit has a different meaning depending on
the type of the chunk.
Length: is needed because the size of the information

section is dependent on the type of the chunk.
Defines the total size of the chunk, in bytes, including the
type, flag, and length fields.
21
Note:
Chunks need to terminate on a 32-bit
(4 byte) boundary.
22
Table 13.2 Different type of Chunks
23
Note:
The number of padding bytes are not
included in the value of
the length field.
24
Figure 13.9
DATA chunk
To indicate which
protocol the SCTP is
carrying
U bit: a 1 signals unordered data(SSN is ignored); 0 is ordered data (d

The message carrying the chunk is delivered to the application
without waiting for the other messages (even if it is out of order)
B=1 and E=1? No fragmentation, whole message in one chunk
B=1 and E=0? First fragment, B=0 and E=1? Last fragment
B=0 and E=0? Middle fragment
25
Note:
A DATA chunk cannot carry data belonging
to more than one message, but a message
can be split into several chunks.
The data field of the DATA chunk must carry
at least one byte of data, which means the
value of length field cannot be
less than 17.
26
Figure 13.10
INIT chunk (initiation chunk)
INIT chunk is the first chunk sent by an end point to

establish an association.
27
Initiation tag
Defines the value of the verification tag for

packets travelling in the opposite direction.
This tag is the same for all packets travelling in
one direction in an association.
Is determined during association
establishment.
random number -> (1 and 2 32 1).
0 -> no association -> permitted only by the
general header of the INIT chunk.
Advertised receiver window credit
Used in flow control and defines the initial

amount of data in bytes the sender of INIT
chunk can allow.
In SCTP, sequence numbers are in terms of
chunks.
28
Outbound stream
Maximum inbound stream
Defines the maximum number of streams that the

initiator of the association can support in the inbound
direction.
Cant be increased by the other end.
Initial TSN
Defines the number of streams that the initiator of the

association suggests for streams in the outbound
direction.
Initializes the TSN in the outbound direction.

< 232.
Variable length parameters
Optional parameters that may be added to define the IP

address of sending end point, the number of IP
addresses the end point can support (multihome) and
other parameters.
For example, Parameter type = 5. This parameter lists
all the IPV4 addresses used at the sending endpoint.
29
Note:
No other chunk can be carried in a
packet that carries an INIT chunk.
30
Figure 13.11 INIT ACK chunk
The INIT ACK

chunk is the
second packet
sent during
association
establishment.
Parameter type: defines the state cookie

sent by the sender of this chunk.
31
Note:
No other chunk can be carried in a
packet that carries an
INIT ACK chunk.
32
Figure 13.12
COOKIE ECHO chunk
The COOKIE ECHO chunk is the third chunk sent

during association establishment.
It is sent by the end point that receives an INIT ACK
chunk.
Can also carry user data.
33
Figure 13.13
COOKIE ACK
The COOKIE ACK chunk is the fourth and last chunk

sent during association establishment.
It is sent by the end point that receives a COOKIE
ECHO chunk.
Can also carry user data.
34
Figure 13.14
SACK chunk
35
Cumulative TSN acknowledgement
Advertised receiver window credit
Is the updated value for the receiver window

size.
Number of gap ACK blocks
Defines the TSN of the last data chunk

received in sequence.
Defines the number of gaps in the data

chunk received after the cumulative TSN.
The gap defines the sequence of received
chunks, not the missing chunks.
Number of duplicates
Defines the number of duplicate chunks

following the cumulative TSN.
36
Gap ACK block start offset
Gap ACK block end offset
For each gap block, it gives the starting

TSN relative to the cumulative TSN.
For each gap block, it gives the ending
TSN relative to the cumulative TSN.
Duplicate TSN
For each duplicate chunk, it gives the

TSN of the chunk.
37
Figure 13.15
HEARTBEAT and HEARTBEAT ACK chunks
Heartbeat: probes the peer for liveliness.

Heartbeat ACK: Acknowledges heartbeat chunk.
Sender-specific information: includes the local

time and the IP address of the sender.
It is copied without change into the heartbeat
ACK chunk.
38
Figure 13.16
SHUTDOWN, SHUTDOWN ACK, and SHUTDOWN

COMPLETE chunks
The T flag shows that the sender does not have

Transmission control block (TCB) table which holds info
about each connection.
39
Figure 13.17
ERROR chunk
The error chunk is sent when an end point finds some

error in a received packet.
The sending of an error chunk does not imply the
aborting of the association.
40
Table 13.3 Errors
41
Figure 13.18
ABORT chunk
The abort chunk is sent when an end point finds a fatal

error and needs to abort the association.
One or more error cause: 1-Invalid Stream Identifier, 2Missing Mandatory Parameter, 9- No User Data
42
13.4 AN SCTP ASSOCIATION

SCTP, like TCP, is a connection-oriented protocol. However, a
connection in SCTP is called an association to emphasize multihoming

Association Establishment
Data Transfer
Association Termination
Association Abortion
43
Figure 13.19
Four-way handshaking
44
Note:
No other chunk is allowed in a packet
carrying an INIT or INIT ACK chunk.
A COOKIE ECHO or a COOKIE ACK
chunk can carry DATA chunks.
45
Note:
In SCTP, only DATA chunks consume
TSNs;
DATA chunks are the only chunks that
are acknowledged.
46
Figure 13.20
Simple data transfer
Note: cumTSN
does not point
to next TSN
expected!
47
Note:
The acknowledgment in SCTP defines
the cumulative TSN, the TSN of the
last DATA chunk received in order.
48
Figure 13.21
Association termination
SCTP does not allow a half-closed

association.
49
Figure 13.22
Association abortion
50
13.5 STATE TRANSITION DIAGRAM

To keep track of all the different events happening during association
establishment, association termination, and data transfer, the SCTP
software, like TCP, is implemented as a finite state machine.

Scenarios
Simultaneous Close
51
Figure 13.23
State transition diagram
52
Table 13.4 States for SCTP
53
Figure 13.24
A common scenario of states
54
Figure 13.25
Simultaneous open
55
Figure 13.26
Simultaneous close
56
13.6 FLOW CONTROL

Flow control in SCTP is similar to that in TCP. In SCTP, we need to
handle two units of data, the byte and the chunk.

Receiver Site
Sender Site
A Scenario
57
Figure 13.27
Flow control, receiver site
58
Figure 13.28
Flow control, sender site
59
Figure 13.29
Flow control scenario
rwnd and winSize agreed upon during init phase to be 20
60
13.7 ERROR CONTROL

SCTP uses a SACK chunk to report the state of the receiver buffer to the
sender. Each implementation uses a different set of entities and timers
for the receiver and sender sites.

Receiver Site
Sender Site
Sending Data Chunks
Generating SACK Chunks
61
Figure 13.30
Error control, receiver site
62
Figure 13.31
Error control, sender site
63
Figure 13.32
New state at the sender site after receiving a SACK chunk
64
13.8 CONGESTION CONTROL

SCTP uses the same strategies for congestion control as TCP. SCTP uses
slow start, congestion avoidance, and congestion detection phases.
65

Chap 13 Modified PP2003

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Chap 13 Modified PP2003

Загружено:

Авторское право:

Доступные форматы

Chapter 13

TCP/IP Protocol Suite

TCP/IP protocol suite

SCTP combines the better features of UDP and TCP

Table 13.1 Some SCTP applications

TCP/IP Protocol Suite

In TCP, each connection between a client and a server involve

TCP/IP Protocol Suite

TCP/IP Protocol Suite

Multiple sources and multiple receivers allows

TCP/IP Protocol Suite

TCP/IP Protocol Suite

TCP/IP Protocol Suite

TCP/IP Protocol Suite

TCP/IP Protocol Suite

Comparison between a TCP segment and an SCTP packet

Comparison between a TCP segment and an SCTP packet

An association may send many packets, a packet may contain

TCP/IP Protocol Suite

TCP/IP Protocol Suite

TCP/IP Protocol Suite

TCP/IP Protocol Suite

Packet, data chunks, and streams

Transmission Sequence Number (TSN)

Data chunks are identified by three

TCP/IP Protocol Suite

13.3 PACKET FORMAT

The topics discussed in this section include:

TCP/IP Protocol Suite

TCP/IP Protocol Suite

SCTP packet format

TCP/IP Protocol Suite

Figure 13.7 General header

TCP/IP Protocol Suite

Common layout of a chunk

Control chunks come before data chunks.

Length: is needed because the size of the information

TCP/IP Protocol Suite

Table 13.2 Different type of Chunks

TCP/IP Protocol Suite

TCP/IP Protocol Suite

U bit: a 1 signals unordered data(SSN is ignored); 0 is ordered data (d

INIT chunk (initiation chunk)

INIT chunk is the first chunk sent by an end point to

Defines the value of the verification tag for

Advertised receiver window credit

Used in flow control and defines the initial

TCP/IP Protocol Suite

Maximum inbound stream

Defines the maximum number of streams that the

Defines the number of streams that the initiator of the

Initializes the TSN in the outbound direction.

Variable length parameters

Optional parameters that may be added to define the IP

TCP/IP Protocol Suite

TCP/IP Protocol Suite

Figure 13.11 INIT ACK chunk

The INIT ACK

TCP/IP Protocol Suite

Parameter type: defines the state cookie

TCP/IP Protocol Suite

COOKIE ECHO chunk

The COOKIE ECHO chunk is the third chunk sent

TCP/IP Protocol Suite