Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-planned-changes-07.txt
Randall Gellens <rg+ietf@coretechnologyconsulting.com> Tue, 15 August 2023 17:40 UTC
Return-Path: <rg+ietf@coretechnologyconsulting.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66AF6C151707 for <ecrit@ietfa.amsl.com>; Tue, 15 Aug 2023 10:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQUt2y-8ev-Y for <ecrit@ietfa.amsl.com>; Tue, 15 Aug 2023 10:40:33 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id DBE12C151086 for <ecrit@ietf.org>; Tue, 15 Aug 2023 10:40:32 -0700 (PDT)
Received: from [99.111.97.131] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 15 Aug 2023 10:40:31 -0700
From: Randall Gellens <rg+ietf@coretechnologyconsulting.com>
To: Brian Rosen <br@brianrosen.net>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, ECRIT <ecrit@ietf.org>, Roger Marshall <RMarshall@telecomsys.com>
Date: Tue, 15 Aug 2023 10:40:31 -0700
X-Mailer: MailMate (1.14r5937)
Message-ID: <7ED65775-0DE0-4BD7-AB99-2987E1A89218@coretechnologyconsulting.com>
In-Reply-To: <DCB336E7-C5FA-44F1-AA17-675AF1453C86@brianrosen.net>
References: <5B047008-7D4E-4BFE-BE78-CC33BCEF7A73@brianrosen.net> <5B47FE0D-E3AE-4099-AD42-5968754EACF2@coretechnologyconsulting.com> <DCB336E7-C5FA-44F1-AA17-675AF1453C86@brianrosen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/2bcCw8apurQR2tezsl7oeS_nh24>
Subject: Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-planned-changes-07.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Emergency Context Resolution with Internet Technologies <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2023 17:40:37 -0000
That's OK, or you could do a super quick rev to fix that, as otherwise someone else will comment about it. --Randall On 15 Aug 2023, at 10:13, Brian Rosen wrote: > I don’t have the LoST-Sync changes in. I think we’re going to > have to do a larger fix to LoST Sync (signatures don’t work as > specified), and we’ll do them there. > > In the first paragraph of Section 3, the text talks about 3 entry > points. It expressly says “one” and “three” but refers to the > second as “Another”. The change suggested by Victor makes the > numbering for “two” explicit. We can just go with what is there, > or if there is another version to deal with comments we get in the > approval process, I’ll fix it then. > > Brian > > >> On Aug 15, 2023, at 12:48 PM, Randall Gellens >> <rg+ietf@coretechnologyconsulting.com> wrote: >> >> 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
- [Ecrit] I-D Action: draft-ietf-ecrit-lost-planned… internet-drafts
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Brian Rosen
- [Ecrit] Fwd: I-D Action: draft-ietf-ecrit-lost-pl… Randall Gellens
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Brian Rosen
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Roger Marshall
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Randall Gellens
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Randall Gellens
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Roger Marshall
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Brian Rosen
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Randall Gellens
- Re: [Ecrit] I-D Action: draft-ietf-ecrit-lost-pla… Brian Rosen