Validation of Locations Around a Planned Change
draft-rosen-ecrit-lost-planned-changes-03
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-04-21 (latest revision 2015-10-19) | ||
| Replaced by | draft-ecrit-lost-planned-changes | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ecrit-lost-planned-changes | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-rosen-ecrit-lost-planned-changes-03.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 TTL element to the response, which informs all queriers the current expected lifetime of the validation.
Authors
Brian Rosen (br@brianrosen.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)