Validation of Locations Around a Planned Change
draft-ecrit-lost-planned-changes-00
| Document | Type |
Replaced Internet-Draft
(ecrit WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian Rosen | ||
| Last updated | 2017-01-19 (Latest revision 2016-07-18) | ||
| Replaces | draft-rosen-ecrit-lost-planned-changes | ||
| Replaced by | draft-ietf-ecrit-lost-planned-changes | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Allison Mankin | ||
| IESG | IESG state | Replaced by draft-ietf-ecrit-lost-planned-changes | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| 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 is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)