RFC 6442: Location Conveyance for the Session Initiation Protocol
In plain English — editorial summary, not part of the RFC
This document defines an extension to the Session Initiation Protocol (SIP) to convey geographic location information from one SIP entity to another SIP entity. The SIP extension covers end-to-end conveyance as well as location-based routing, where SIP intermediaries make routing decisions based upon the location of the Location Target. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6442
- Published
- December 2011
- Authors
- J. Polk; B. Rosen; J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 35
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6446Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate ControlCurrent
January 2012
- RFC 6223Indication of Support for Keep-AliveCurrent
April 2011
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 5898Connectivity Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
July 2010
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 7092A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User AgentsCurrent
December 2013
- RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current
January 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?