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

Document Type Active Internet-Draft (sipcore WG)
Last updated 2019-10-20 (latest revision 2019-10-08)
Replaces draft-winterbottom-sipcore-locparam
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Jean Mahoney
Shepherd write-up Show (last changed 2019-10-20)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to Jean Mahoney <mahoney@nostrum.com>
SIPCORE                                                  J. Winterbottom
Internet-Draft                               Winterb Consulting Services
Updates: 6442 (if approved)                                    R. Jesske
Intended status: Standards Track                        Deutsche Telekom
Expires: April 10, 2020                                       B. Chatras
                                                             Orange Labs
                                                               A. Hutton
                                                                    Atos
                                                         October 8, 2019

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

Abstract

   There are some circumstances where a Geolocation header field may
   contain more than one locationValue.  Knowing the identity of the
   node adding the locationValue allows the recipient more freedom in
   selecting the value to look at first rather than relying solely on
   the order of the locationValues.  This document defines the "loc-src"
   parameter so that the entity adding the locationValue to Geolocation
   header field can identify itself using its hostname.  This document
   updates RFC 6442.

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 April 10, 2020.

Copyright Notice

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

Winterbottom, et al.     Expires April 10, 2020                 [Page 1]
Internet-Draft             Location Parameter               October 2019

   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
   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 . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Registration of loc-src parameter for Geolocation header
           field . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

Winterbottom, et al.     Expires April 10, 2020                 [Page 2]
Internet-Draft             Location Parameter               October 2019

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.  [RFC6442] specifies that
   SIP intermediaries should not add locationValues to a SIP request
   that already contains locationValue.  [RFC6442] also states that if a
   SIP intermediary adds location it is fully responsible for addressing
   the concerns of any 424 (Bad Location Information) SIP response it
   receives.  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
Show full document text