RFC 6406: Session PEERing for Multimedia INTerconnect (SPEERMINT) Architecture
In plain English — editorial summary, not part of the RFC
This document defines a peering architecture for the Session Initiation Protocol (SIP) and its functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6406
- Published
- November 2011
- Authors
- D. Malas; J. Livingood
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6405Voice over IP (VoIP) SIP Peering Use CasesCurrent
November 2011
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6357Design Considerations for Session Initiation Protocol (SIP) Overload ControlCurrent
August 2011
- RFC 6315IANA Registration for Enumservice 'iax'Current
July 2011
- RFC 6501Conference Information Data Model for Centralized Conferencing (XCON)Current
March 2012
- RFC 6502Conference Event Package Data Format Extension for Centralized Conferencing (XCON)Current
March 2012
- RFC 6503Centralized Conferencing Manipulation ProtocolCurrent
March 2012
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?