RFC 6271: Requirements for SIP-Based Session Peering
In plain English — editorial summary, not part of the RFC
This memo captures protocol requirements to enable session peering of voice, presence, instant messaging, and other types of multimedia traffic. This informational document is intended to link the various use cases described for session peering to protocol solutions. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6271
- Published
- June 2011
- Authors
- J-F. Mule
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 8085UDP Usage GuidelinesUpdated
March 2017
- RFC 3383Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)Obsoleted
September 2002
- RFC 2350Expectations for Computer Security Incident ResponseCurrent
June 1998
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 2011
- RFC 6285Unicast-Based Rapid Acquisition of Multicast RTP SessionsCurrent
June 2011
- RFC 6231An Interactive Voice Response (IVR) Control Package for the Media Control Channel FrameworkUpdated
May 2011
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?