IETF Logo Mail Archive

[OPSAWG]Re: draft-ietf-opsawg-mud-acceptable-urls-13.txt => move from OPSAWG to IOTOPS

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 31 March 2025 11:53 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@mail2.ietf.org
Delivered-To: opsawg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A8BE8150F661; Mon, 31 Mar 2025 04:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QgrObGM7OA-j; Mon, 31 Mar 2025 04:53:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1485E150F64F; Mon, 31 Mar 2025 04:53:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 982241800E; Mon, 31 Mar 2025 07:53:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id lRBmwvCQ1pWv; Mon, 31 Mar 2025 07:53:25 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1743422005; bh=YbuiMYNyp+imDnzWPdVww3YsoB4JkyFBzeBsdu4dcDw=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=Qu+hluKArx2j0crYMrkC85Ig8dseOv2ZzbIVAG7DdWmpFBlZ+TPH9HDRtf8HHaMtK KmzMjruXG0En1qSIy1tgBa7TkFjlbE2VtJ/35YRinfmhQe8vKbnjqVvMA408MTHVqs 9CGkqhFPQOY6usUCdyh3UFyM1lxO+Oi89Qzug1QNEjqfC+2ZKQ2xa6oW2nk92WxeC2 lHE2bZ1omD7RqnTTyB3rDxR5Cl1OAkcgMrjU2b5PL9aI+ORmM32XQEC1cNcsHD0r0v 9aoECEvb+TKbjDU9vmapVZroKsI9OHGFcfCzNRP1JBE557e2LTIJlLuNsXqBG5eI7q iCnUVpXCeq2xg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5FC1C1800C; Mon, 31 Mar 2025 07:53:25 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5C3CA119; Mon, 31 Mar 2025 07:53:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tom petch <ietfc@btconnect.com>
In-Reply-To: <AM6PR07MB41037B673AFE5AC2C037A7DDA0A22@AM6PR07MB4103.eurprd07.prod.outlook.com>
References: <174213451807.130475.11476688578417644928@dt-datatracker-5b9b68c5b6-zxk6z> <1f9ea1a4-9293-4b20-9e49-a05f250335a3@huawei.com> <AM6PR07MB41037B673AFE5AC2C037A7DDA0A22@AM6PR07MB4103.eurprd07.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 31 Mar 2025 07:53:25 -0400
Message-ID: <23965.1743422005@obiwan.sandelman.ca>
Message-ID-Hash: 5VWSKWHTS73NTKKLEMTNJ3LWTI534LI4
X-Message-ID-Hash: 5VWSKWHTS73NTKKLEMTNJ3LWTI534LI4
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsawg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>, opsawg <opsawg@ietf.org>, "iotops@ietf.org" <iotops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OPSAWG]Re: draft-ietf-opsawg-mud-acceptable-urls-13.txt => move from OPSAWG to IOTOPS
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/NkuqIKddrUB7Oq44Vnu6S8qwdog>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Owner: <mailto:opsawg-owner@ietf.org>
List-Post: <mailto:opsawg@ietf.org>
List-Subscribe: <mailto:opsawg-join@ietf.org>
List-Unsubscribe: <mailto:opsawg-leave@ietf.org>

tom petch <ietfc@btconnect.com> wrote:
    tp> I hope that you keep the name the same.  I do trip up over LSR
    tp> documents that are 'draft-ietf-ospf' but I see much worse when it
    tp> becomes beyond the wit of some AD to track a document back to its
    tp> first submission:-(

Hi, the DT has a facility to mark one draft as being replaced by another.
When the rechartering is done, and IOTOPS adopts, then that will get done.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.38.3 | Report a Bug | By Email | System Status