Extension to the ua-profile Event Package to Support the Application Profile Type
draft-channabasappa-sipping-app-profile-type-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Dolly , Sumanth Channabasappa , Joshua B. Littlefield , Salvatore Loreto | ||
| Last updated | 2008-11-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Framework for Session Initiation Protocol User Agent Profile Delivery specifies an event package (ua-profile) that can be used by user agents to retrieve profile data. The framework also allows for optional notification of changes to the retrieved profiles. Three profile types are specified: local-network, device, and user. This document extends that event package to support an additional profile type, application. This would enable User Agents to retrieve profile data specific to one or more applications.
Authors
Martin Dolly
Sumanth Channabasappa
Joshua B. Littlefield
Salvatore Loreto
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)