A guideline on message headers and URI in SIP/SIMPLE framework
draft-ashir-simple-message-guideline-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ashir Ahmed | ||
| Last updated | 2004-02-11 | ||
| 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
SUBSCRIBE, NOTIFY and PUBLISH methods in SIP are responsible for carrying presence information to a target destination. Message headers (Request-line, To, From, Contact etc.) indicate SIP entities that are identified by a URI. This document clarifies the indication of the message headers and provides a guideline on URI usage in the header fields. The authors hope that this document will be useful for SIP/SIMPLE implementers, interoperability testers, designers, and protocol researchers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)