[OPSAWG] [Fwd: Your thoughts on draft-richardson-mud-qrcode]

"RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org> Mon, 15 March 2021 10:19 UTC

Return-Path: <rfc-ise@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A1A3A0A06; Mon, 15 Mar 2021 03:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-5TqRIUa5nO; Mon, 15 Mar 2021 03:19:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E31533A0A02; Mon, 15 Mar 2021 03:19:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9148AF40726; Mon, 15 Mar 2021 03:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OArN_0Px7Qk7; Mon, 15 Mar 2021 03:19:36 -0700 (PDT)
Received: from www.rfc-editor.org (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 3CBA5F40775; Mon, 15 Mar 2021 03:19:36 -0700 (PDT)
Received: from 84.93.109.31 (SquirrelMail authenticated user rfcpise) by www.rfc-editor.org with HTTP; Mon, 15 Mar 2021 03:19:36 -0700
Message-ID: <2a12c6bcb4bbbde5e4f046a9763272be.squirrel@www.rfc-editor.org>
In-Reply-To: <240866a424caca4cf10e5df833533ffe.squirrel@www.rfc-editor.org>
References: <240866a424caca4cf10e5df833533ffe.squirrel@www.rfc-editor.org>
Date: Mon, 15 Mar 2021 03:19:36 -0700
From: "RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org>
To: opsawg-chairs@ietf.org
Cc: opsawg@ietf.org, rfc-ise@rfc-editor.org
Reply-To: rfc-ise@rfc-editor.org
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/aLtOAXXw_5tBwVKOX2W-k2ijTkk>
Subject: [OPSAWG] [Fwd: Your thoughts on draft-richardson-mud-qrcode]
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2021 10:19:45 -0000

Hi OPSAWG chairs,

I wrote to you at the start of Janusary about draft-richardson-mud-qrcode/
 which is derived from draft-richardson-opsawg-securehomegateway-mud

My question was whether, in your opinion, this should be in the OPSAWG or
it is OK for it to be published in the Independent Stream.

I also wondered if you are aware of any history related to the document
that you could share with me.

I see from the mailing list that Michael has raised the draft on the list
a couple of times, but without any follow-up.

What I'd like to know (and the WG can contribute to this discussion) is
whether this is something that the WG would like to complete and publish
in the IETF stream.

Any thoughts?

Thanks,
Adrian
-- 
Adrian Farrel (Independent Stream Editor),
rfc-ise@rfc-editor.org