RFC 6223: Indication of Support for Keep-Alive
In plain English — editorial summary, not part of the RFC
This specification defines a new Session Initiation Protocol (SIP) Via header field parameter, "keep", which allows adjacent SIP entities to explicitly negotiate usage of the Network Address Translation (NAT) keep-alive mechanisms defined in SIP Outbound, in cases where SIP Outbound is not supported, cannot be applied, or where usage of keep-alives is not implicitly negotiated as part of the SIP Outbound negotiation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6223
- Published
- April 2011
- Authors
- C. Holmberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 6442Location Conveyance for the Session Initiation ProtocolUpdated
December 2011
- RFC 6446Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate ControlCurrent
January 2012
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
- RFC 5898Connectivity Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
July 2010
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
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?