[rfc-dist] RFC 5373 on Requesting Answering Modes for the Session Initiation Protocol (SIP)
rfc-editor at rfc-editor.org
Tue Nov 25 15:31:47 PST 2008
A new Request for Comments is now available in online RFC libraries.
Title: Requesting Answering Modes for the
Session Initiation Protocol (SIP)
Author: D. Willis, Ed.,
Status: Standards Track
Date: November 2008
Mailbox: dean.willis at softarmor.com,
aallen at rim.com
I-D Tag: draft-ietf-sip-answermode-07.txt
This document extends SIP with two header fields and associated
option tags that can be used in INVITE requests to convey the
requester's preference for user-interface handling related to
answering of that request. The first header, "Answer-Mode",
expresses a preference as to whether the target node's user interface
waits for user input before accepting the request or, instead,
accepts the request without waiting on user input. The second
header, "Priv-Answer-Mode", is similar to the first, except that it
requests administrative-level access and has consequent additional
authentication and authorization requirements. These behaviors have
applicability to applications such as push-to-talk and to diagnostics
like loop-back. Usage of each header field in a response to indicate
how the request was handled is also defined. [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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist