< draft-ietf-ecrit-lost-planned-changes-02.txt   draft-ietf-ecrit-lost-planned-changes-03.txt >
ecrit B. Rosen ecrit B. Rosen
Internet-Draft October 23, 2018 Internet-Draft April 26, 2019
Updates: RFC5222 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: April 26, 2019 Expires: October 28, 2019
Validation of Locations Around a Planned Change Validation of Locations Around a Planned Change
draft-ietf-ecrit-lost-planned-changes-02 draft-ietf-ecrit-lost-planned-changes-03
Abstract Abstract
This document defines an extension to LoST (RFC5222) that allows a This document defines an extension to LoST (RFC5222) that allows a
planned change to the data in the LoST server to occur. Records that 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, previously were valid will become invalid at a date in the future,
and new locations will become valid after the date. The extension and new locations will become valid after the date. The extension
adds two elements to the <findservice> request: A URI to be used to adds two elements to the <findservice> request: A URI to be used to
inform the LIS that previously valid locations will be invalid after inform the LIS that previously valid locations will be invalid after
the planned change date, and add a date which requests the server to the planned change date, and add a date which requests the server to
skipping to change at page 1, line 41 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 26, 2019. This Internet-Draft will expire on October 28, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 21 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 4
3. <plannedChange> element . . . . . . . . . . . . . . . . . . . 4 3. <plannedChange> element . . . . . . . . . . . . . . . . . . . 4
4. <locationInvalidated> object . . . . . . . . . . . . . . . . 4 4. <locationInvalidated> object . . . . . . . . . . . . . . . . 4
5. URI Not Stored Warning . . . . . . . . . . . . . . . . . . . 5 5. URI Not Stored Warning . . . . . . . . . . . . . . . . . . . 5
6. Time-To-Live (TTL) in Response . . . . . . . . . . . . . . . 5 6. Time-To-Live (TTL) in Response . . . . . . . . . . . . . . . 5
7. Replacement XML schema . . . . . . . . . . . . . . . . . . . 6 7. Replacement XML schema . . . . . . . . . . . . . . . . . . . 6
8. Extension XML schema . . . . . . . . . . . . . . . . . . . . 14 8. Extension XML Schema . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
10.1. Replacement Schema Registration . . . . . . . . . . . . 16 10.1. Replacement XML Schema Registration . . . . . . . . . . 16
10.2. Replacement Schema Registration . . . . . . . . . . . . 16 10.2. Extension XML Schema Registration . . . . . . . . . . . 16
10.3. LoST Namespace Registration . . . . . . . . . . . . . . 16 10.3. LoST Namespace Registration . . . . . . . . . . . . . . 16
11. Normative References . . . . . . . . . . . . . . . . . . . . 17 11. Normative References . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
This document describes an update to the LoST protocol + which allows 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 a <findservice> request to optionally add a URI and a date to be used
with planned changes to the underlying location information in the with planned changes to the underlying location information in the
server. The URI is retained by the LoST server, associated with the server. The URI is retained by the LoST server, associated with the
skipping to change at page 14, line 43 skipping to change at page 14, line 47
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:sequence> <xs:sequence>
<xs:group ref="notLost" <xs:group ref="notLost"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:group> </xs:group>
</xs:schema> </xs:schema>
8. Extension XML schema 8. Extension XML Schema
This schema provides the extension to the prior section schema for This schema provides the extension to the prior section schema for
planned changes: planned changes:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:lostPlannedChange1" xmlns="urn:ietf:params:xml:ns:lostPlannedChange1"
targetNamespace="urn:ietf:params:xml:ns:lostPlannedChange1" targetNamespace="urn:ietf:params:xml:ns:lostPlannedChange1"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- Import base Lost --> <!-- Import base Lost -->
skipping to change at page 16, line 23 skipping to change at page 16, line 23
operating the LoST server may have a credential traceable to a well operating the LoST server may have a credential traceable to a well
known Certificate Authority known to provide credentials for public known Certificate Authority known to provide credentials for public
safety agencies. Many of the clients will be operated by local ISPs safety agencies. Many of the clients will be operated by local ISPs
or other service providers where the server operator can reasonably or other service providers where the server operator can reasonably
obtain a good credential to use for the URI. Where the server does obtain a good credential to use for the URI. Where the server does
not recognize the client, its policy MAY limit the use of this not recognize the client, its policy MAY limit the use of this
feature beyond what it would limit a client it recognized. feature beyond what it would limit a client it recognized.
10. IANA Considerations 10. IANA Considerations
10.1. Replacement Schema Registration 10.1. Replacement XML Schema Registration
URI: urn:ietf:params:xml:schema:lost3 URI: urn:ietf:params:xml:schema:lost3
Registrant Contact: IETF ECRIT Working Group, Brian Rosen Registrant Contact: IETF ECRIT Working Group, Brian Rosen
(br@brianrosen.net). (br@brianrosen.net).
The XML Schema is found in <xref target="schema"/>. The XML Schema is found in Section 7.
10.2. Replacement Schema Registration 10.2. Extension XML Schema Registration
URI: urn:ietf:params:xml:schema:lostPlannedChange1 URI: urn:ietf:params:xml:schema:lostPlannedChange1
Registrant Contact: IETF ECRIT Working Group, Brian Rosen Registrant Contact: IETF ECRIT Working Group, Brian Rosen
(br@brianrosen.net). (br@brianrosen.net).
The XML Schema is found in <xref target="extSchema"100/>. The XML Schema is found in Section 8.
10.3. LoST Namespace Registration 10.3. LoST Namespace Registration
URI: urn:ietf:params:xml:ns:lost-plannedChange1 URI: urn:ietf:params:xml:ns:lost-plannedChange1
Registrant Contact: IETF ECRIT Working Group, Brian Rosen Registrant Contact: IETF ECRIT Working Group, Brian Rosen
(br@brianrosen.net). (br@brianrosen.net).
XML: XML:
BEGIN BEGIN
 End of changes. 12 change blocks. 
13 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/