[rfc-dist] RFC 4412 on Communications Resource Priority for the Session Initiation Protocol (SIP)
rfc-editor at rfc-editor.org
Mon Feb 27 12:50:46 PST 2006
A new Request for Comments is now available in online RFC libraries.
Title: Communications Resource Priority for the
Session Initiation Protocol (SIP)
Author: H. Schulzrinne, J. Polk
Status: Standards Track
Date: February 2006
Mailbox: hgs at cs.columbia.edu,
jmpolk at cisco.com
I-D Tag: draft-ietf-sip-resource-priority-10.txt
This document defines two new Session Initiation Protocol (SIP) header
fields for communicating resource priority, namely,
\"Resource-Priority\" and \"Accept-Resource-Priority\". The
\"Resource-Priority\" header field can influence the behavior of SIP
user agents (such as telephone gateways and IP telephones) and SIP
proxies. It does not directly influence the forwarding behavior of IP
routers. [STANDARDS TRACK]
This document is a product of the Session Initiation Protocol
Working Group of the IETF
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of
the Internet Official Protocol Standards (STD 1) for the
standardization state and status of this protocol. Distribution of
this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist