Allowing SIP Resource-Priority Header in SIP Responses
draft-polk-sip-rph-in-responses-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2008-02-23 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-polk-sip-rph-in-responses-01.txt
Abstract
The Session Initiation Protocol (SIP) Resource-Priority Header is ignored in SIP responses, according to RFC 4412. This was a design choice during RFC 4412's development. This is now considered a bad design choice in certain scenarios. This document corrects RFC 4412's communications model by optionally allowing a SIP server or user agent (UA) to process the Resource-Priority Header in a response. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)