RFC 6915: Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)
In plain English — editorial summary, not part of the RFC
RFC 6155 specifies an extension for the HTTP-Enabled Location Delivery (HELD) protocol, allowing the use of an IP address and port number to request a Device location based on an individual packet flow. However, certain kinds of NAT require that identifiers for both ends of the packet flow must be specified in order to unambiguously satisfy the location request. This document specifies an XML Schema and a URN Sub-Namespace for a Flow Identity Extension for HELD to support this requirement. This document updates RFC 6155 by deprecating the port number elements specified therein.
Document record
- Document ID
- RFC6915
- Published
- April 2013
- Authors
- R. Bellis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 6155
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 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 7216Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNSCurrent
April 2014
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 8957Synonymous Flow Label FrameworkCurrent
January 2021
- RFC 6914SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)Current
April 2013
- RFC 6917Media Resource BrokeringCurrent
April 2013
- RFC 6910Completion of Calls for the Session Initiation Protocol (SIP)Current
April 2013
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?