Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Framework for Session Set-up with Media Authorization (RFC3521)

IP.com Disclosure Number: IPCOM000012166D
Original Publication Date: 2003-Apr-01
Included in the Prior Art Database: 2003-Apr-15
Document File: 26 page(s) / 60K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L-N. Hamer: AUTHOR [+3]

Abstract

Establishing multimedia streams must take into account requirements for end-to-end QoS, authorization of network resource usage and accurate accounting for resources used. During session set up, policies may be enforced to ensure that the media streams being requested lie within the bounds of the service profile established for the requesting host. Similarly, when a host requests resources to provide a certain QoS for a packet flow, policies may be enforced to ensure that the required resources lie within the bounds of the resource profile established for the requesting host.

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

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � L-N. Hamer

Request for Comments: 3521� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � B. Gage

Category: Informational� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Nortel Networks

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � H. Shieh

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � AT&T Wireless

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � April 2003

� � � � � � � � Framework for Session Set-up with 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

� � Establishing multimedia streams must take into account requirements

� � for end-to-end QoS, authorization of network resource usage and

� � accurate accounting for resources used.� During session set up,

� � policies may be enforced to ensure that the media streams being

� � requested lie within the bounds of the service profile established

� � for the requesting host.� Similarly, when a host requests resources

� � to provide a certain QoS for a packet flow, policies may be enforced

� � to ensure that the required resources lie within the bounds of the

� � resource profile established for the requesting host.

� � To prevent fraud and to ensure accurate billing, this document

� � describes various scenarios and mechanisms that provide the linkage

� � required to verify that the resources being used to provide a

� � requested QoS are in-line with the media streams requested (and

� � authorized) for the session.

Hamer, et al. � � � � � � � � � � � � � � � Informational� � � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3521� � � � � � � Session Set-up with Media Authorization� � � � � � April 2003

Table of Contents

� � 1.� Introduction....................................................2

� � 2.� Conventions used in this document...............................3

� � 3.� Definition of terms.............................................4

� � 4.� The Coupled Model...............................................5

� � � � � � 4.1� � Coupled Model Message Flows...............................6

� � � � � � 4.2� � Coupled Model Authorization Token.........................8

� � � � � � 4.3� � Coupled Model Protocol Impacts............................8

� � 5.� The Associated Model <<using One Policy Server>>................8

� � � � � � 5.1� � Associated Model Message Flows

� � � � � � � � � � � � <<using One Policy Server>>...............................9

� � � � � � 5.2� � Associated Model Autho...