RFC 8433: A Simpler Method for Resolving Alert-Info URNs
In plain English — editorial summary, not part of the RFC
The "alert" namespace of Uniform Resource Names (URNs) can be used in the Alert-Info header field of Session Initiation Protocol (SIP) requests and responses to inform a voice over IP (VoIP) telephone (user agent) of the characteristics of the call that the user agent has originated or terminated. The user agent must resolve the URNs into a signal; that is, it must select the best available signal to present to its user to indicate the characteristics of the call. RFC 7462 describes a non-normative algorithm for signal selection. This document describes a more efficient alternative algorithm: a user agent's designer can, based on the user agent's signals and their meanings, construct a finite state machine (FSM) to process the URNs to select a signal in a way that obeys the restrictions given in the definition of the "alert" URN namespace.
Document record
- Document ID
- RFC8433
- Published
- August 2018
- Authors
- D. Worley
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 45
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 2862RTP Payload Format for Real-Time PointersCurrent
June 2000
- RFC 6193Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)Current
April 2011
- RFC 5379Guidelines for Using the Privacy Mechanism for SIPCurrent
February 2010
- RFC 5022Media Server Control Markup Language (MSCML) and ProtocolCurrent
September 2007
- RFC 4722Media Server Control Markup Language (MSCML) and ProtocolObsoleted
November 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?