Validation of Locations Around a Planned Change
draft-ietf-ecrit-lost-planned-changes-01

Document Type Expired Internet-Draft (ecrit WG)
Last updated 2018-09-06 (latest revision 2018-03-05)
Replaces draft-ecrit-lost-planned-changes
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WG, Awaiting Expert Review/Resolution of Issues Raised
Document shepherd Allison Mankin
IESG IESG state Expired
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Allison Mankin <allison.mankin@gmail.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-ecrit-lost-planned-changes-01.txt

Abstract

This document defines an extension to LoST (RFC5222) that allows a planned change to the data in the LoST server to occur. Records that previously were valid will become invalid at a date in the future, and new locations will become valid after the date. The extension adds two elements to the <findservice> request: A URI to be used to inform the LIS that previously valid locations will be invalid after the planned change date, and add a date which requests the server to perform validation as of the date specified. It also adds an optional Time-To-Live element to the response, which informs clients about the current expected lifetime of the validation. This document also provides a conventional XML schema for LoST, as backwards compatible alternative to the RelaxNG schema in RFC5222

Authors

Brian Rosen (br@brianrosen.net)

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