Considerations for Session-specific SIP Session Policies
draft-hilt-sipping-consider-policy-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Volker Hilt | ||
Last updated | 2004-05-14 | ||
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
This draft intends to trigger discussions within the SIP community on how to implement session-specific policies in SIP. In particular, we discuss why the piggyback model, which was proposed previously, does not meet important requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)