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

Document Type Active Internet-Draft (ecrit WG)
Last updated 2018-10-23
Replaces draft-ecrit-lost-planned-changes
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml 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 I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Allison Mankin <allison.mankin@gmail.com>
ecrit                                                           B. Rosen
Internet-Draft                                          October 23, 2018
Intended status: Standards Track
Expires: April 26, 2019

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

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

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 26, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Rosen                    Expires April 26, 2019                 [Page 1]
Internet-Draft            LoST Planned Changes              October 2018

   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   4
   3.  <plannedChange> element . . . . . . . . . . . . . . . . . . .   4
   4.  <locationInvalidated> object  . . . . . . . . . . . . . . . .   4
   5.  URI Not Stored Warning  . . . . . . . . . . . . . . . . . . .   5
   6.  Time-To-Live (TTL) in Response  . . . . . . . . . . . . . . .   5
   7.  Replacement XML schema  . . . . . . . . . . . . . . . . . . .   6
   8.  Extension XML schema  . . . . . . . . . . . . . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     10.1.  Replacement Schema Registration  . . . . . . . . . . . .  16
     10.2.  Replacement Schema Registration  . . . . . . . . . . . .  16
     10.3.  LoST Namespace Registration  . . . . . . . . . . . . . .  16
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   This document describes an update to the LoST protocol + which allows
   a <findservice> request to optionally add a URI and a date to be used
   with planned changes to the underlying location information in the
   server.  The URI is retained by the LoST server, associated with the
   data record that was validated, and used to notify the LIS (the LoST
   client) when a location which was previously valid will become
   invalid.  The date is used by the client to ask the server to perform
   validation as of a future date.  In addition to this mechanism, the
   <findserviceResponse> is also extended to provide a Time-To-Live
   (TTL) for validation, after which the client should revalidate the
   location.

   Validation of civic locations involves dealing with data that changes
   over time.  A typical example is a portion of a county or province
   that was not part of a municipality is "annexed" to a municipality.
   Prior to the change, the content of the PIDF-LO A3 element would be
   blank, or represent some other value and after the change would be
   the municipality that annexed that part of the county/province.  This
Show full document text