




















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
This lecture was delivered by Dr. Ram Sai at Jaypee University of Engineering and Technology for Computers and Network Programming course. It includes: Stream, Protocol, Sctp, Control, Transmission, Congestion, Tcp, Udp, Multihoming, Feature, Robustness
Typology: Slides
1 / 28
This page cannot be seen from the preview
Don't miss anything!





















Provide
multiple
streams
between
connection
endpoints,
each
with
its
own
reliable
sequenced
delivery
of
messages
A
lost
message
in
one
of
these
streams
does
not
block
delivery
of
messages
in
any
of
the
other
streams
In
contrast
to
TCP,
where
a
loss
at
any
point
in
the
single
stream
of
bytes
blocks
delivery
of
all
future
data
on
the
connection
until
the
loss
is
repaired
docsity.com
Host
initiates
an
association
by
sending
an
packet
to
Host
Host
responds
with
an
packet
that
contains
the
following
fields:
A
Verification
tag
A
Cookie
The
packet
does
not
contain
these
fields.
The
cookie
contains
the
necessary
state
information,
which
the
server
uses
to
allocate
resources
for
the
association.
The
cookie
field
includes
a
signature
for
authenticity
and
a
timestamp
to
prevent
replay
attacks
using
old
cookies.
Unlike
Host
in
does
not
allocate
resources
at
this
point
in
the
connection.
The
verification
tag
provides
a
key
that
enables
Host
to
verify
that
the
packet
belongs
to
the
current
association.
Host
sends
the
packet
to
Host
If
Host
has
a
forged
address,
it
never
receives
the
chunk
This
prevents
Host
from
sending
the
packet.
As
a
result,
the
conversation
ends
without
the
server
allocating
any
resources
for
the
connection.
Host
responds
with
a
chunk
and
allocates
resources
for
the
connection.
The
connection
is
now
established
between
Host
and
Host
Host
can
now
start
sending
data
to
Host
10
11
13
At
any
given
time,
multiple
processes
can
be
using
any
given
transport:
or
All
three
transport
layers
use
16
‐bit
integer
port
numbers
to
differentiate
between
these
processes
When
a
client
wants
to
contact
a
server,
the
client
must
identify
the
server
with
which
it
wants
to
communicate
and
define
a
group
of
well
‐known
ports
to
identify
well
known
services
FTP
servers
are
assigned
the
well
‐known
port
of
21
TFTP
servers
are
assigned
the
UDP
port
of
69
Clients
normally
use
ephemeral
ports,
that
is,
short
‐lived
ports,
normally
assigned
automatically
by
the
transport
protocol
to
the
client
Clients
normally
do
not
care
about
the
value
of
the
ephemeral
port;
the
client
just
needs
to
be
certain
that
the
ephemeral
port
is
unique
on
the
client
host
The
transport
protocol
code
guarantees
this
uniqueness
14
The
well
‐known
ports:
These
port
numbers
are
controlled
and
assigned
by
the
The
registered
ports:
not
controlled
by
registers
and
lists
the
uses
of
these
ports
as
a
convenience
to
the
community.
When
possible,
the
same
port
is
assigned
to
a
given
service
for
both
and
For
example,
ports
through
are
assigned
for
an
Window
server
Upper
limit
was
introduced
to
range
ephemeral
ports.
Unix
systems
uses
reserved
port,
which
is
any
port
less
than
These
ports
can
only
be
assigned
to
a
socket
by
an
appropriately
privileged
process.
All
the
well
known
ports
are
reserved
ports;
hence,
the
server
allocating
this
port
(such
as
the
server)
must
have
superuser
privileges
when
it
starts.
allocated
ephemeral
ports
.fine
in
the
early
1980s,
but
it
is
easy
today
to
find
a
host
that
can
support
more
than
connections
at
any
given
time.
Therefore,
many
newer
systems
allocate
ephemeral
ports
differently
to
provide
more
ephemeral
ports,
either
using
the
‐defined
ephemeral
range
or
a
larger
range.
TCP
Port
Numbers
&
Concurrent
Servers
19
With a concurrent server, where the main server loop spawns achild to handle each new connection, what happens if the childcontinues to use the well-known port number while servicing a
long request?
TCP
Port
Numbers
&
Concurrent
Servers
server
client
listening socket
connection request to206.62.226.35, port 21
20