RFC 6447: Filtering Location Notifications in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document describes filters that limit asynchronous location notifications to compelling events. These filters are designed as an extension to RFC 4661, an XML-based format for event notification filtering, and based on RFC 3856, the SIP presence event package. The resulting location information is conveyed in existing location formats wrapped in the Presence Information Data Format Location Object (PIDF-LO). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6447
- Published
- January 2012
- Authors
- R. Mahy; B. Rosen; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)Current
January 2013
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 2011
- RFC 7035Relative Location RepresentationCurrent
October 2013
- RFC 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 7199Location Configuration Extensions for Policy ManagementCurrent
April 2014
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
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?