Location Conveyance for the Session Initiation Protocol
RFC 6442

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 09

Internet Engineering Task Force (IETF)                           J. Polk
Request for Comments: 6442                                 Cisco Systems
Category: Standards Track                                       B. Rosen
ISSN: 2070-1721                                              J. Peterson
                                                                 NeuStar
                                                           December 2011

        Location Conveyance for the Session Initiation Protocol

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6442.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Polk, et al.                 Standards Track                    [Page 1]
RFC 6442               Location Conveyance in SIP          December 2011

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction ....................................................3
   2. Conventions and Terminology Used in This Document ...............4
   3. Overview of SIP Location Conveyance .............................4
      3.1. Location Conveyed by Value .................................4
      3.2. Location Conveyed as a Location URI ........................5
      3.3. Location Conveyed though a SIP Intermediary ................6
      3.4. SIP Intermediary Replacing Bad Location ....................7
   4. SIP Extensions for Geolocation Conveyance .......................8
      4.1. The Geolocation Header Field ...............................8
      4.2. The Geolocation-Routing Header Field ......................11
           4.2.1. Explaining Geolocation-Routing Header-Value
                  States .............................................12
      4.3. 424 (Bad Location Information) Response Code ..............14
      4.4. The Geolocation-Error Header Field ........................15
      4.5. Location URIs in Message Bodies ...........................19
      4.6. Location Profile Negotiation ..............................19
   5. Geolocation Examples ...........................................20
      5.1. Location-by-Value (in Coordinate Format) ..................20
      5.2. Two Locations Composed in Same Location Object Example ....21
   6. Geopriv Privacy Considerations .................................23
   7. Security Considerations ........................................24
   8. IANA Considerations ............................................26
      8.1. IANA Registration for the SIP Geolocation Header Field ....26
      8.2. IANA Registration for the SIP Geolocation-Routing
           Header Field ..............................................26
      8.3. IANA Registration for Location Profiles ...................27
      8.4. IANA Registration for 424 Response Code ...................27
      8.5. IANA Registration of New Geolocation-Error Header Field ...28