IETF Logo Mail Archive

Re: [Ecrit] Objet : Status on draft-ietf-ecrit-similar-location-19

Brian Rosen <br@brianrosen.net> Mon, 15 May 2023 22:25 UTC

Return-Path: <br@brianrosen.net>
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 96D1DC291239 for <ecrit@ietfa.amsl.com>; Mon, 15 May 2023 15:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.193
X-Spam-Level:
X-Spam-Status: No, score=-1.193 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=brianrosen.net
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 MIgpfHnRJ5rt for <ecrit@ietfa.amsl.com>; Mon, 15 May 2023 15:25:33 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA3C2C013FE6 for <ecrit@ietf.org>; Mon, 15 May 2023 15:25:33 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-1aaf792c210so15605455ad.0 for <ecrit@ietf.org>; Mon, 15 May 2023 15:25:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1684189531; x=1686781531; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=8CY8+fosg01QaOUXOOe/YizNlnW+XBth6v1xsikbx7U=; b=MqeIGiuVnm/FqFp6NVNaKGNDUf9S0YTTqP8l8Iph4bjuOZN15D+WWPibi2/dnA7YGe d2k2sA/vA1cL5yXyu4C/Y+JELWHCVK7YEgW1bcR3+yR28PYODuomGH5j1ne2iPgH+NsM A8AcySvoob3//5XO1dJpxf1RLyKbhCcfKONh4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684189531; x=1686781531; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=8CY8+fosg01QaOUXOOe/YizNlnW+XBth6v1xsikbx7U=; b=IinRZHSgQp28wFWB/SA4S/8fyvfzVboeVN/wukk4cwYPBFJdB+QJTU/xFKw0b4DTAi oiDGc5t1IFTIVsnApV+ks0+0QaMJ6/+3jBH2WlSFTIYzRLLLZM4OOrTCTY6XuNAXXr5y Bid/M+odeW0G+EpVmMuK2H21VPjTapvZ7dAOWaDYTLy09EOct4YaoovcrlrS+Lx9WJZU o5JkMMwvt4kXaoHqwJk/doL6+jpfgribCJwjUAoO0rxY/GMGByzRAK32rg6mNZEzh00f mNG0lvyPDiFJBdLx/56hI2UFZJaAC0Gbqt6O4DxOGlWnczjjw1o3V/7KvpPoUBN+5RlK UrVg==
X-Gm-Message-State: AC+VfDw1oCxV+ruS+/FoA4bAy27MJmmGWkuhUNN5WVDzBKC06jO03joi LKdvmTAJXLr96yx5bnJ7bNzvQa37QrfH4QqHZpt7rw==
X-Google-Smtp-Source: ACHHUZ5FGugkdLaUoLhZIVTqG/HoY2+r6y17Amylbt8SQvWYNSeXNSVyXR5GjAHsAA5iE5DjQ7nPjA==
X-Received: by 2002:a17:902:e850:b0:1ac:85e9:3c9c with SMTP id t16-20020a170902e85000b001ac85e93c9cmr9730513plg.1.1684189531227; Mon, 15 May 2023 15:25:31 -0700 (PDT)
Received: from smtpclient.apple (135-180-32-155.fiber.dynamic.sonic.net. [135.180.32.155]) by smtp.gmail.com with ESMTPSA id y18-20020a17090322d200b001a1a82fc6d3sm13984574plg.268.2023.05.15.15.25.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 May 2023 15:25:30 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-218FE8FA-7950-46DB-91C3-ACAC70130422"
Content-Transfer-Encoding: 7bit
From: Brian Rosen <br@brianrosen.net>
Mime-Version: 1.0 (1.0)
Date: Mon, 15 May 2023 15:25:19 -0700
Message-Id: <B171CB86-FD28-4084-ADC8-FFF530212FA5@brianrosen.net>
References: <CAL0qLwaoNEFRo7VM_P0T5ENa6Dpr+zSo5MKpYPgOukk5FRb4gA@mail.gmail.com>
Cc: Guy Caron <guycaron911@gmail.com>, ecrit@ietf.org
In-Reply-To: <CAL0qLwaoNEFRo7VM_P0T5ENa6Dpr+zSo5MKpYPgOukk5FRb4gA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: iPhone Mail (20E252)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/MTqgNOgMlLaKHbdlA8Pu0O40Ik4>
Subject: Re: [Ecrit] Objet : Status on draft-ietf-ecrit-similar-location-19
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: Mon, 15 May 2023 22:25:37 -0000

Yes, hope to have “final” draft in the ne t 2-3 days

On May 15, 2023, at 9:54 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:


So can we finish planned-changes?

-MSK

On Tue, Jan 31, 2023 at 3:07 PM Brian Rosen <br@brianrosen.net> wrote:
Making any changes would require pulling the document back to the work group, editing, and restarting work group last call, IETF last call, and the IESG review/telecast process.  Then it would go to the back of the RFC Editor queue. 

You would be better off beating me up to finish planned-changes 

Brian 

On Jan 31, 2023, at 1:33 PM, Guy Caron <guycaron911@gmail.com> wrote:



Correct me if I’m wrong but it seems to me that similar-location leverages the extension point, which was defined by RFC 5222. None of the new elements defined in planned-changes are needed to support similar-location.

 

The only linkage I can see is in section 6 of planned-changes that presents an alternative in XML schema to the RFC 5222 Relax NG one. However, there is nothing in that section that states normatively that it replaces the RFC 5222 Relax NG schema.

 

So, to unlock similar-location, would it be possible to remove the reference to planned-changes altogether?

 

Alternatively, the XML schema could be moved from planned-changes to similar-location and let planned-changes refer to the similar-location RFC, similar-location being much more advanced that planned-changes.

 

Thoughts?

 

Guy

 

De : Dwight Purtle
Envoyé le :12 janvier 2023 00:33
À : Guy Caron
Cc : ecrit@ietf.org
Objet :Re: [Ecrit] Status on draft-ietf-ecrit-similar-location-19

 

ECRIT-Similar-Location contains a reference to LoST-Planned-Changes, which is not yet complete.  Thus the MISSREF.

 

Dwight Purtle

 

On Wed, Jan 11, 2023 at 11:00 AM Guy Caron <guycaron911@gmail.com> wrote:

What’s the status on this draft?

 

There was an announcement on 7 March 2022 that the IESG approved the draft as a Proposed Standard, yet the draft seems stuck in the REF Editor queue with a MISSREF and that, for 309 days.

 

Thanks,

 

Guy

 

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/ecrit

 

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/ecrit
_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/ecrit

v2.23.0 | Report a Bug | By Email