Location Source Parameter for the SIP Geolocation Header Field
draft-ietf-sipcore-locparam-00

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

• Versions
• 00
• 01

SIPCORE                                                  J. Winterbottom
Internet-Draft                               Winterb Consulting Services
Updates: RFC6442 (if approved)                                 R. Jesske
Intended status: Standards Track                        Deutsche Telekom
Expires: February 3, 2019                                     B. Chatras
                                                             Orange Labs
                                                               A. Hutton
                                                                   Unify
                                                          August 2, 2018

     Location Source Parameter for the SIP Geolocation Header Field
                   draft-ietf-sipcore-locparam-00.txt

Abstract

   There are some circumstances where a geolocation header field may
   contain more than one location value.  Knowing the identity of the
   node adding the location value allows the recipient more freedom in
   selecting the value to look at first rather than relying solely on
   the order of the location values.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 3, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Winterbottom, et al.    Expires February 3, 2019                [Page 1]
Internet-Draft             Location Parameter                August 2018

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Registration of loc-src Parameter for geolocation header
           field . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

Winterbottom, et al.    Expires February 3, 2019                [Page 2]
Internet-Draft             Location Parameter                August 2018

1.  Introduction

   The SIP geolocation specification [RFC6442] describes the
   "Geolocation" SIP header field which is used to indicate that the SIP
   message is conveying location information.  The specification
   suggests that only one location value should be conveyed.  However,
   some communications architectures, such as 3GPP [TS23-167] and ETSI
   [M493], prefer to use information provided by edge-proxies or
   acquired through the use of core-network nodes, before using
   information provided solely by user equipment (UE).  These solutions
   don't preclude the use of UE provided location but require a means of
   being able to distinguish the identity of the node adding the
   location value to the SIP message from that provided by the UE.

   [RFC6442] stipulates that the order of location values in the
   geolocation header field is the same as the order in which they were
   added to the header field.  Whilst this order provides guidance to
   the recipient as to which values were added to the message earlier in