‫اﻟﻌﺎﻟﻲ واﻟﺒﺤﺚ اﻟﻌﻠﻤﻲ‬ ‫‪Republic of Iraq‬‬

‫ﺟﺎﻣﻌــــﺔﺑﺎﺑــــﻞ‬ ‫‪Ministry of Higher Education and‬‬

‫ﻛﻠﯿــــــﺔﺗﻜﻨﻮﻟﻮﺟﯿﺎاﻟﻤﻌﻠﻮﻣﺎت‬ ‫‪Scientific Research‬‬
‫‪University of Babylon‬‬
‫ﻗﺴﻢ ﺷﺒﻜﺎت اﻟﻤﻌﻠﻮﻣﺎت‬
‫‪College of Information Technology‬‬
‫اﻟﺘﻘﺮﯾﺮ اﻟﻨﮭﺎﺋﻲ‬ ‫‪Department of Information Network‬‬

‫اﻟﺘﻘﺮﯾﺮ اﻟﻨﮭﺎﺋﻲ‬
‫ﻟﻠﻌﺎم اﻟﺪراﺳﻲ ‪ 2020-2019‬اﻟﻔﺼﻞ اﻟﺪراﺳﻲ )اﻟﺜﺎﻧﻲ(‬

‫ﺗﻘﺮﯾﺮ ﺑﻌﻨﻮان‬
‫)‪Session Description Protocol(sdp‬‬
‫اﻋﺪاد اﻟﻄﺎﻟﺐ‬
‫ﻋﻠﻲ ﻋﺒﺪ اﻟﺠﺒﺎر ﻣﻨﻌﻢ ﻛﺎظﻢ اﻟﺠﻨﺎﺑﻲ‬
‫ﻟﻤﺎدة)‪(Data Communication & Networking ll‬‬
‫اﻟﻤﺮﺣﻠﺔ ) اﻟﺮاﺑﻌﮫ ( اﻟﺪراﺳﺔ) اﻟﺼﺒﺎﺣﻲ (‬

‫ﺑﺎﺷﺮاف اﻻﺳﺘﺎذ‬
‫ﻣﺤﻤﺪ اﻟﺤﺴﻨﺎوي‬
2-INTRODUCTION
When initiating multimedia
teleconferences, voice-over-IP calls,
streaming video, or other sessions,
there is a requirement to convey
media details, transport addresses,
and other session description
metadata to the participants.

SDP provides a standard

representation for such information,
irrespective of how that information
is transported. SDP is purely a
format for session description -- it
does not incorporate a transport
protocol, and it is intended to use
different transport protocols as
appropriate, including the Session
Announcement Protocol [14],
Session Initiation Protocol [15],
Real Time Streaming Protocol [16],
electronic mail using the MIME
extensions, and the Hypertext
 Transport Protocol.

SDP is intended to be general purpose

so that it can be used in a
wide range of network environments
and applications. However, it is
not intended to support negotiation
of session content or media
encodings: this is viewed as outside
the scope of session
description.

This memo obsoletes RFC 2327 [6] and

RFC 3266 [10]. Section 10
outlines the changes introduced in
this memo.

3-What is Session description

Protocol(sdp)
SDP (Session Description Protocol) is a set of rules
that defines how multimedia sessions can be set up to
allow all end points to effectively participate in the
session. In this context, a session consists of a set of
communications end points along with a series of
interactions among them. The session is initiated
when the connection is first established and is
terminated when the all of the end points have
stopped participating. An example is
a videoconference conducted by a large corporation
that includes participants from multiple departments in
diverse geographic locations.

In SDP, session parameters include information such

as the session name, the date and time at which the
session is scheduled to begin, the purpose of the
session, the addresses or ports of all end points, the
data formats to be used and
the bandwidth requirements for effectively exchanging
the session data. SDP is intended primarily for use in
large WANs (wide-area networks) including
the Internet. As such, it is designed to function in a
many-to-many environment. Nevertheless, SDP can
also be employed in proprietary LANs (local area
networks) and MANs (metropolitan area networks).

4-Purpose of SDP

The purpose of SDP is to convey information about

media streams in multimedia sessions to help
participants join or gather info of a particular session.
• SDP is a short structured textual description.
 • It conveys the name and purpose of the session,
the media, protocols, codec formats, timing and
transport information.
• A tentative participant checks these information
and decides whether to join a session and how
and when to join a session if it decides to do so.
• The format has entries in the form of <type> =
<value>, where the <type> defines a unique
session parameter and the <value> provides a
specific value for that parameter.
• The general form of a SDP message is −
x = parameter1 parameter2 ... parameterN
• The line begins with a single lower-case letter, for
example, x. There are never any spaces between
the letter and the =, and there is exactly one
space between each parameter. Each field has a
defined number of parameters.

5-Session Description Parameters

Session description (* denotes optional)

• v = (protocol version)
• o = (owner/creator and session identifier)
• s = (session name)
• i =* (session information)
• u =* (URI of description)
• e =* (email address)
• p =* (phone number)
• c =* (connection information - not required if
included in all media)
• b =* (bandwidth information)
• z =* (time zone adjustments)
• k =* (encryption key)
• a =* (zero or more session attribute lines)

6- Examples of SDP Usage

6.1 Session Initiation

The Session Initiation Protocol (SIP)
[15] is an application-layer
control protocol for creating,
modifying, and terminating sessions
such as Internet multimedia
conferences, Internet telephone calls,
and multimedia distribution. The SIP
messages used to create
sessions carry session descriptions
that allow participants to agree
on a set of compatible media types.
These session descriptions are
commonly formatted using SDP. When
used with SIP, the offer/answer
model [17] provides a limited framework
for negotiation using SDP.

6.2 Streaming Media

 The Real Time Streaming Protocol (RTSP)
[16], is an application-level
protocol for control over the delivery
of data with real-time
properties. RTSP provides an
extensible framework to enable
controlled, on-demand delivery of real-
time data, such as audio and
video. An RTSP client and server
negotiate an appropriate set of
parameters for media delivery,
partially using SDP syntax to describe
those parameters.

6.3 Email and the World Wide Web

Alternative means of conveying session

descriptions include
electronic mail and the World Wide Web
(WWW). For both email and WWW
distribution, the media type
"application/sdp" is used. This enables
the automatic launching of applications
for participation in the
session from the WWW client or mail
reader in a standard manner.

Note that announcements of multicast

sessions made only via email or
the WWW do not have the property that
the receiver of a session
 announcement can necessarily receive
the session because the
multicast sessions may be restricted in
scope, and access to the WWW
server or reception of email is
possible outside this scope.

6.4 Multicast Session Announcement

In order to assist the advertisement of

multicast multimedia
conferences and other multicast
sessions, and to communicate the
relevant session setup information to
prospective participants, a
distributed session directory may be
used. An instance of such a
session directory periodically sends
packets containing a description
of the session to a well-known
multicast group. These advertisements
are received by other session
directories such that potential remote
participants can use the session
description to start the tools
required to participate in the session.
7-An SDP Example

Given below is an example session description, taken

from RFC 2327 −
v = 0
o = mhandley2890844526 2890842807 IN IP4
[Link]
s = SDP Seminar
i = A Seminar on the session description
protocol
u = [Link]
[Link]/[Link]
e = mjh@[Link](Mark Handley)
c = IN IP4 [Link]/127
t = 2873397496 2873404696
a = recvonly
m = audio 49170 RTP/AVP 0
m = video 51372 RTP/AVP 31
m = application 32416udp wb
a = orient:portrait
8. REFERENCES
1-[Link]
session_initiation_protocol_sdp.htm
2-[Link]
[Link]/definition/
SDP%3famp=1#ip=1
3-[Link]