IETF Logo Mail Archive

[6lo] 6lo-NFC status update?

Christian Amsüss <christian@amsuess.com> Fri, 04 March 2022 13:19 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27FB43A1403; Fri, 4 Mar 2022 05:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 5zmFOlhAXaKn; Fri, 4 Mar 2022 05:19:42 -0800 (PST)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA31B3A1405; Fri, 4 Mar 2022 05:19:40 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com ([IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by smtp.akis.at (8.17.1/8.17.1) with ESMTPS id 224DJaap091725 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 4 Mar 2022 14:19:36 +0100 (CET) (envelope-from christian@amsuess.com)
X-Authentication-Warning: smtp.akis.at: Host [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd] claimed to be poseidon-mailhub.amsuess.com
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 72A38D0; Fri, 4 Mar 2022 14:19:35 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:12a:4729:24dd:e3f1]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 174E5FD; Fri, 4 Mar 2022 14:19:35 +0100 (CET)
Received: (nullmailer pid 3803363 invoked by uid 1000); Fri, 04 Mar 2022 13:19:34 -0000
Date: Fri, 04 Mar 2022 14:19:34 +0100
From: Christian Amsüss <christian@amsuess.com>
To: draft-ietf-6lo-nfc@ietf.org, 6lo@ietf.org
Message-ID: <YiIR5qzuofR+bXlJ@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="YdxpDse1zSK/vixJ"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/gcNJWXlyOA-L4a4vdnciOpTDh4o>
Subject: [6lo] 6lo-NFC status update?
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2022 13:19:46 -0000

Hello 6lo-nfc authors & group,

I'm trying to determine the state of draft-ietf-6lo-nfc.

What I can see is that it got to IESG review, got comments criticizing
its choice of words (both around "security" and on marketing-material)
and lack of clarity in interaction with lower layer specs (especially
their public availability) -- and updates into late 2020 -- and then
nothing more.

I am a quiet bystander in this group (merely consuming its output), and
do not have concrete implementation plans for 6lo-nfc yet, but it's on
my list of "would like to play with".

Is there a roadmap for 6lo-nfc to go on? Will the authors resume work,
if not, will the chairs find new authors to finish it, or will the draft
be abandoned even after having reached WG consensus?

BR
Christian

-- 
Yesterday is history, tomorrow is a mystery, and today is a gift. That
is why it is called the present.
  -- ancient saying

v2.23.0 | Report a Bug | By Email