[Ecrit] Fwd: I-D Action: draft-ietf-ecrit-lost-planned-changes-07.txt

Brian,

Are the changes you propose here reflected in -07?

Can you remind me what "entry point numbering" means?

Roger: You are listed as the shepherd. Are you able and willing to do so 
or should I ask Dwight?

--Randall

Forwarded message:

> From: Brian Rosen <br@brianrosen.net>
> To: ECRIT <ecrit@ietf.org>
> Subject: Re: [Ecrit] I-D Action: 
> draft-ietf-ecrit-lost-planned-changes-07.txt
> Date: Mon, 22 May 2023 15:14:17 -0400
>
> I updated planned-changes to fix the typos reported by Victor.  I 
> managed to undo one of his requested edits (entry point numbering), 
> which I will fix soon.  If I missed anything else, please remind me.
>
> I propose to add another part to this document, which would be to add 
> “AsOf” and “Expires” metadata to a LoST sync transaction, so a 
> Forest Guide can do the same thing with planned changes as a LoST 
> server could.
>
> Brian
>
>
>> On May 22, 2023, at 2:56 PM, internet-drafts@ietf.org wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This Internet-Draft is a work item of the Emergency 
>> Context
>> Resolution with Internet Technologies (ECRIT) WG of the IETF.
>>
>>   Title           : Validation of Locations Around a Planned Change
>>   Author          : Brian Rosen
>>   Filename        : draft-ietf-ecrit-lost-planned-changes-07.txt
>>   Pages           : 21
>>   Date            : 2023-05-22
>>
>> Abstract:
>>   This document defines an extension to the Location to Service
>>   Translation (LoST) protocol (RFC5222) that allows a LoSR server ti
>>   notify a client of planned changes to the data.  This extension is
>>   only useful with the validation function of LoST.  It is beneficial
>>   for LoST validation clients to be aware of planned changes, as
>>   records that previously were valid may become invalid at a known
>>   future date, and new locations may become valid after the date.  
>> This
>>   extension adds an element to the <findService> request: a date that
>>   allows the LoST client to request that the server perform 
>> validation
>>   as of the date specified.  It adds an optional Time-To-Live element
>>   to the response, which informs clients of the current expected
>>   lifetime of a validation.  It also adds a separate interface to the
>>   LoST server that allows a client to poll for planned changes.
>>   Additionally, this document provides a conventional XML schema for
>>   LoST, as a backwards compatible alternative to the RelaxNG schema 
>> in
>>   RFC5222.
>>
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-ecrit-lost-planned-changes/
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-ietf-ecrit-lost-planned-changes-07.html
>>
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ecrit-lost-planned-changes-07
>>
>> Internet-Drafts are also available by rsync at 
>> rsync.ietf.org::internet-drafts
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit