RFC 8917: The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag
In plain English — editorial summary, not part of the RFC
This document adds the 'LoST-Validation' service tag to the Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag IANA registry. This tag can appear in a Naming Authority Pointer (NAPTR) Domain Name System (DNS) record to assist clients of the Location-to-Service Translation (LoST) Protocol in identifying LoST servers designated for location validation. This tag and the information about its use update RFC 5222, which enables the explicit discovery of a server that supports location validation.
Document record
- Document ID
- RFC8917
- Published
- October 2020
- Authors
- R. Gellens; B. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 5222
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8787Location Source Parameter for the SIP Geolocation Header FieldCurrent
May 2020
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 8606ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header FieldCurrent
June 2019
- RFC 8148Next-Generation Vehicle-Initiated Emergency CallsCurrent
May 2017
- RFC 8147Next-Generation Pan-European eCallCurrent
May 2017
- RFC 7852Additional Data Related to an Emergency CallCurrent
July 2016
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?