Browse Prior Art Database

HTTP-Enabled Location Delivery (HELD) (RFC5985)

IP.com Disclosure Number: IPCOM000199535D
Original Publication Date: 2010-Sep-01
Included in the Prior Art Database: 2010-Sep-08
Document File: 78 page(s) / 87K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Barnes: AUTHOR [+2]

Abstract

The location of a Device is information that is useful for a number of applications. The L7 Location Configuration Protocol (LCP) problem statement and requirements document [RFC5687] provides some scenarios in which a Device might rely on its access network to provide location information. The Location Information Server (LIS) service applies to access networks employing both wired technology (e.g., DSL, cable) and wireless technology (e.g., WiMAX) with varying degrees of Device mobility. This document describes a protocol that can be used to acquire Location Information (LI) from a LIS within an access network.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                    M. Barnes, Ed. Request for Comments: 5985                                       Polycom Category: Standards Track                                 September 2010 ISSN: 2070-1721

                  HTTP-Enabled Location Delivery (HELD)

Abstract

   This document defines a Layer 7 Location Configuration Protocol (L7    LCP) and describes the use of HTTP and HTTP/TLS as transports for the    L7 LCP.  The L7 LCP is used for retrieving location information from    a server within an access network.  It includes options for    retrieving location information in two forms: by value and by    reference.  The protocol is an extensible application-layer protocol    that is independent of the session layer.

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/rfc5985.

Copyright Notice

   Copyright (c) 2010 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.

Barnes                       Standards Track                    [Page 1]
 RFC 5985                          HELD                    September 2010

 Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  3

   3.  Overview and Scope . . . . . . . . . . . . . . . . . . . . . .  4

   4.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  5

     4.1.  Device Identifiers, NAT and VPNs . . . . . . . . . . . . .  6

       4.1.1.  Devices and VPNs . . . . . . . . . . . . . . . . . . .  6

       4.1.2.  LIS Handling of NATs and VPNs...