Browse Prior Art Database

Private Session Initiation Protocol (SIP) Extensions for Media Authorization (RFC3313)

IP.com Disclosure Number: IPCOM000010815D
Original Publication Date: 2003-Jan-01
Included in the Prior Art Database: 2003-Jan-23
Document File: 17 page(s) / 37K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Marshall: AUTHOR [+2]

Abstract

This document describes the need for Quality of Service (QoS) and media authorization and defines a Session Initiation Protocol (SIP) extension that can be used to integrate QoS admission control with call signaling and help guard against denial of service attacks. The use of this extension is only applicable in administrative domains, or among federations of administrative domains with previously agreed-upon policies, where both the SIP proxy authorizing the QoS, and the policy control of the underlying network providing the QoS, belong to that administrative domain or federation of domains.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � W. Marshall, Ed.

Request for Comments: 3313� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � AT&T

Category: Informational� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � January 2003

� � � � � � � � � Private Session Initiation Protocol (SIP) Extensions

� � � � � � � � � � � � � � � � � � � � � � � for Media Authorization

Status of this Memo

� � This memo provides information for the Internet community.� It does

� � not specify an Internet standard of any kind.� Distribution of this

� � memo is unlimited.

Copyright Notice

� � Copyright (C) The Internet Society (2003).� All Rights Reserved.

Abstract

� � This document describes the need for Quality of Service (QoS) and

� � media authorization and defines a Session Initiation Protocol (SIP)

� � extension that can be used to integrate QoS admission control with

� � call signaling and help guard against denial of service attacks.� The

� � use of this extension is only applicable in administrative domains,

� � or among federations of administrative domains with previously

� � agreed-upon policies, where both the SIP proxy authorizing the QoS,

� � and the policy control of the underlying network providing the QoS,

� � belong to that administrative domain or federation of domains.

Marshall, Ed.� � � � � � � � � � � � � � � Informational� � � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3313� � � � � � � � SIP Extensions for Media Authorization� � � � January 2003

Table of Contents

� � 1. Scope of Applicability.........................................� 2

� � 2. Conventions Used in this Document..............................� 3

� � 3. Background and Motivation......................................� 3

� � 4. Overview.......................................................� 4

� � 5. Changes to SIP to Support Media Authorization..................� 4

� � � � � 5.1 SIP Header Extension.......................................� 5

� � � � � 5.2 SIP Procedures.............................................� 5

� � � � � � � 5.2.1 User Agent Client (UAC)................................� 6

� � � � � � � 5.2.2 User Agent Server (UAS)................................� 6

� � � � � � � 5.2.3 Originating Proxy (OP).................................� 7

� � � � � � � 5.2.4 Destination Proxy (DP).................................� 7

� � 6. Examples.......................................................� 8

� � � � � 6.1 Requesting Bandwidth via RSVP Messaging....................� 8

� � � � � � � 6.1.1 User Agent Client Side.................................� 8

� � � � � � � 6.1.2 User Agent Server Side................................. 10

� � 7. Advantages of the Proposed Approach............................ 12

� � 8. Security Considerations........................................ 13

� � 9. IANA Considerations............................................ 13

� � 10. Notice Regarding Intel...