Validation of Locations Around a Planned Change
draft-ietf-ecrit-lost-planned-changes-01
| The information below is for an old version of the document | |||||
|---|---|---|---|---|---|
| Document | Type | Expired Internet-Draft (ecrit WG) | |||
| Author | Brian Rosen | ||||
| Last updated | 2018-09-06 (latest revision 2018-03-05) | ||||
| Replaces | draft-ecrit-lost-planned-changes | ||||
| Stream | Internet Engineering Task Force (IETF) | ||||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||||
| Additional Resources |
|
||||
| Stream | WG state | Waiting for WG Chair Go-Ahead (wg milestone: Aug 2017 - Submit 'Validation o... ) | |||
| 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> | ||||
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.)