Skip to main content

Validation of Locations Around a Planned Change

Document Type Expired Internet-Draft (ecrit WG)
Author Brian Rosen
Last updated 2022-04-14 (Latest revision 2021-10-11)
Replaces draft-ecrit-lost-planned-changes
Stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Expired & archived
plain text html xml htmlized pdfized bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Associated WG milestone
Aug 2017
Submit 'Validation of Locations Around a Planned Change' to the IESG for consideration as a Standards Track RFC
Document shepherd Roger Marshall
IESG IESG state Expired (IESG: Dead)
Action Holders
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Murray Kucherawy
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:


This document defines an extension to the Location to Service Translation (LoST) protocol (RFC5222) that allows planned changes to the data to be handled smoothly. This extension is only useful with the validation function of LoST. It is beneficial for LoST validation clients to be aware of planned changes, as records that previously were valid may become invalid at a known future date, and new locations may become valid after the date. This extension adds an element to the <findService> request: a date that allows the LoST client to request that the server perform validation as of the date specified. It adds an optional Time-To-Live element to the response, which informs clients of the current expected lifetime of a validation. It also adds a separate interface to the LoST server that allows a client to poll for planned changes. Additionally, this document provides a conventional XML schema for LoST, as a backwards compatible alternative to the RelaxNG schema in RFC5222.


Brian Rosen

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)