Requirements for Session Policy for the Session Initiation Protocol (SIP)
draft-ietf-sipping-session-policy-req-02

Document Type Expired Internet-Draft (sipping WG)
Author Jonathan Rosenberg 
Last updated 2004-07-20
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-sipping-session-policy-req-02.txt

Abstract

The proxy server plays a central role as an intermediary in the establishment of sessions in the Session Initiation Protocol (SIP). In that role, they can define and impact policies on call routing, rendezvous, and other call features. However, there is no standard means by which proxies can have any influence on session policies, such as the codecs that are to be used. As such, ad-hoc and non-conformant techniques have been deployed to allow for such policy mechanisms. There is a need for a standards-based and complete mechanism for session policies. This document defines a set of requirements for such a mechanism.

Authors

Jonathan Rosenberg (jdrosen@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)