Re: [Ecrit] WGLC: draft-ietf-ecrit-lost-planned-changes-08

I have reviewed the draft and support advancing it.

Best Regards,
*James Kinney*

*Chief Innovation Officer | INdigital *

On Thu, Aug 31, 2023 at 9:42 AM Randall Gellens <
rg+ietf@coretechnologyconsulting.com> wrote:

> Speaking as a WG participant, I have read this draft and support
> advancing it.
>
> --Randall
>
> On 16 Aug 2023, at 7:19, Randall Gellens wrote:
>
> > This begins WGLC for draft-ietf-ecrit-lost-planned-changes-08.
> >
> > It will be a standard 2 week last call ending August 30.
> >
> > Please send statements of support and any final comments to the list.
> >
> >
> > --Randall
> >
> > Forwarded message:
> >
> >> From: internet-drafts@ietf.org
> >> To: i-d-announce@ietf.org
> >> Cc: ecrit@ietf.org
> >> Subject: [Ecrit] I-D Action:
> >> draft-ietf-ecrit-lost-planned-changes-08.txt
> >> Date: Wed, 16 Aug 2023 07:06:00 -0700
> >>
> >> 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-08.txt
> >>    Pages           : 21
> >>    Date            : 2023-08-16
> >>
> >> 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-08.html
> >>
> >> A diff from the previous version is available at:
> >>
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ecrit-lost-planned-changes-08
> >>
> >> Internet-Drafts are also available by rsync at
> >> rsync.ietf.org::internet-drafts
> >>
> >>
> >> _______________________________________________
> >> Ecrit mailing list
> >> Ecrit@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ecrit
> >
> > _______________________________________________
> > Ecrit mailing list
> > Ecrit@ietf.org
> > https://www.ietf.org/mailman/listinfo/ecrit
>
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>