IETF Logo Mail Archive

Re: [Ecrit] Does anyone support Planned-Changed?

Randall Gellens <rg+ietf@randy.pensive.org> Tue, 19 September 2023 03:06 UTC

Return-Path: <rg+ietf@randy.pensive.org>
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 7CE4EC151071 for <ecrit@ietfa.amsl.com>; Mon, 18 Sep 2023 20:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 i7K6NU4Q-stQ for <ecrit@ietfa.amsl.com>; Mon, 18 Sep 2023 20:06:57 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id E922CC14CE22 for <ecrit@ietf.org>; Mon, 18 Sep 2023 20:06:56 -0700 (PDT)
Received: from [99.111.97.173] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 18 Sep 2023 20:06:56 -0700
From: Randall Gellens <rg+ietf@randy.pensive.org>
To: Brian Rosen <br=40brianrosen.net@dmarc.ietf.org>
Cc: Dan Banks <dbanks=40ddti.net@dmarc.ietf.org>, ECRIT <ecrit@ietf.org>
Date: Mon, 18 Sep 2023 20:06:55 -0700
X-Mailer: MailMate (1.14r5937)
Message-ID: <67F70878-2C84-4DE7-BF3C-226F30B46FAD@randy.pensive.org>
In-Reply-To: <FF1134ED-648D-4749-9183-0DAA4CEB32A1@brianrosen.net>
References: <169219476007.7384.18270557568145715058@ietfa.amsl.com> <8ED387FA-8A0B-4BA4-A96B-787697400C5D@randy.pensive.org> <03e001d9e260$39e27320$ada75960$@gmx.net> <DC7D1C4A-1867-49B8-A18A-DB04A84EAD01@brianrosen.net> <BL3PR17MB616143444F59E8B15F4AF702A7F0A@BL3PR17MB6161.namprd17.prod.outlook.com> <FF1134ED-648D-4749-9183-0DAA4CEB32A1@brianrosen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/LXRk8F15TkixZtdgy_kmU7L3Q1g>
Subject: Re: [Ecrit] Does anyone support Planned-Changed?
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, 19 Sep 2023 03:06:57 -0000

On 18 Sep 2023, at 12:09, Brian Rosen wrote:

> Haha, I meant bring things into a alignment with each other, not 
> geospatial lat/lon.  I will change to “synchronize changes"

Just on this wording point, I think "synchronize changes" implies more 
precise timing than we intend to suggest. Perhaps something such as:

OLD:
to coordinate changes

NEW:
so LoST clients and servers can make changes that are coordinated in 
time

OR:
so LoST clients and servers can coordinate changes


--Randall

v2.23.0 | Report a Bug | By Email