RFC 5947: Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document states requirements for a standardized SIP registration mechanism for multiple addresses of record (AORs), the mechanism being suitable for deployment by SIP service providers on a large scale in support of small to medium sized Private Branch Exchanges (PBXs). The requirements are for a solution that can, as a minimum, support AORs based on E.164 numbers. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5947
- Published
- September 2010
- Authors
- J. Elwell; H. Kaplan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6140Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent
September 2005
- RFC 8587NFS Version 4.0 Trunking UpdateCurrent
May 2019
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 5968Guidelines for Extending the RTP Control Protocol (RTCP)Current
September 2010
- RFC 5924Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 CertificatesCurrent
June 2010
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
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?