IETF Logo Mail Archive

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

"Murray S. Kucherawy" <superuser@gmail.com> Sun, 23 July 2023 16:54 UTC

Return-Path: <superuser@gmail.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 9A79CC14F73E for <ecrit@ietfa.amsl.com>; Sun, 23 Jul 2023 09:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zuSBBfVCbdgu for <ecrit@ietfa.amsl.com>; Sun, 23 Jul 2023 09:54:38 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 B989DC14F738 for <ecrit@ietf.org>; Sun, 23 Jul 2023 09:54:38 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-522205646fdso168297a12.0 for <ecrit@ietf.org>; Sun, 23 Jul 2023 09:54:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690131277; x=1690736077; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=g9rgE/bOu3H6ElPTNFlkluKpF1GGa9PRmYhxDhuambw=; b=emyO91WJfmN2ss+zeOPyq6e5wkWlvOcY9s+i01B0ds2Pezp8KIR86upgGx3xTeNpiB MIDYvgx4uaVQG9t2ZfYmXCNWTgAAezpB58DmRaILJ9ZCGoXTETk865ZAA0pUmJzERycc XWx8cYiRMMJWFLoj2fm5wmLqwnE/soAbCixw7EgUMhLb5fIzoizQAWSjJPZArAgjSnQr PEt9FXlILMBJVl0JiPBqoy2A8+YurouMdU/Y4HbFafGAgRp3+mDQJNfdhmu0HxI6rQgZ l58zqnz7EUipieqGu5aNd296Bhaqjw8BYywyS6AwELRCbuRtySZX4rJX/UEk9emRdygg xxKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690131277; x=1690736077; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=g9rgE/bOu3H6ElPTNFlkluKpF1GGa9PRmYhxDhuambw=; b=bCX9Hd9jVXwF5SkeJMU3AP0GHdHPp/UGINs+Ixe2Zg1YQHX+OCr3QJ0SunmrNrnIsU IZaQo96VJnQ3hFpQtcOL+IgQpC3AJpdrWc8QsgtQLC9n94aO4ksTNmVEFd3trlzqetAQ qdVddhTlBRXKuZd8jShWaJDWsh4szcFJNPRpx+d4URUITGDL/NN1vyYSM8DHOOUvGusd cR+rLSjpxNU5HKTGBglHH0zU8s2pI/kvl2eNpn7gkCg/FUFrikrfxq0h4TwFmLHyeRVx PXdmPrQ6b98S+Fbp2LZTa8zFX/8ZK+Xlcpgd+Rs7NzL7O3A2oTowHUhyXD7GXG20SrjI RyEQ==
X-Gm-Message-State: ABy/qLYFZYaik+IEJjgYrjlxznNxEQw6jU+gDXYR3+ESbvNz+TAIcRZ1 XSAHxxp2Bv4rFHettK/Kzu11jeFDjS0GwN/sKiw=
X-Google-Smtp-Source: APBJJlF2foebPhwx6SSJoqS/UZBnAtafV1Q7bXocLXdAHG3FMTzbCUnslKrkKkIp3e/2r+A5pRde7AFp9hn426C6yh0=
X-Received: by 2002:a17:906:74d4:b0:992:387:44d1 with SMTP id z20-20020a17090674d400b00992038744d1mr6361755ejl.7.1690131277059; Sun, 23 Jul 2023 09:54:37 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwaoNEFRo7VM_P0T5ENa6Dpr+zSo5MKpYPgOukk5FRb4gA@mail.gmail.com> <B171CB86-FD28-4084-ADC8-FFF530212FA5@brianrosen.net>
In-Reply-To: <B171CB86-FD28-4084-ADC8-FFF530212FA5@brianrosen.net>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 23 Jul 2023 09:54:24 -0700
Message-ID: <CAL0qLwYGxfW03vFu0ma+zw038Yw_XpR0O1M=6ULV9kGGmS-e6g@mail.gmail.com>
To: Brian Rosen <br@brianrosen.net>
Cc: Guy Caron <guycaron911@gmail.com>, ecrit@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006499fc06012a5a6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/tG-QJZuBV3wpFv8QNWQPZB-6bZU>
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: Sun, 23 Jul 2023 16:54:42 -0000

ping?

(If this got published, I can't find a record of it in email)

On Mon, May 15, 2023 at 3:25 PM Brian Rosen <br@brianrosen.net> wrote:

> 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 <dwightpurtle@gmail.com>
>> *Envoyé le :*12 janvier 2023 00:33
>> *À : *Guy Caron <guycaron911@gmail.com>
>> *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
>>
>>
>> _______________________________________________
>> 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
>>
>

v2.23.0 | Report a Bug | By Email