Re: [6lo] 6lo-NFC status update?

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Fri, 04 March 2022 18:01 UTC

Return-Path: <carlesgo@entel.upc.edu>
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 26D933A0B0D; Fri, 4 Mar 2022 10:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 lQ0iQHMbqd9z; Fri, 4 Mar 2022 10:01:06 -0800 (PST)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (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 AE9023A08F2; Fri, 4 Mar 2022 10:01:05 -0800 (PST)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.40.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id 224I0lab006554; Fri, 4 Mar 2022 19:00:47 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.40.6]) by entelserver.upc.edu (Postfix) with ESMTP id 297001D53C1; Fri, 4 Mar 2022 19:00:46 +0100 (CET)
Received: from 79.158.120.70 by webmail.entel.upc.edu with HTTP; Fri, 4 Mar 2022 19:00:50 +0100
Message-ID: <0b5cc3096095eceb05345f4bf6cfd737.squirrel@webmail.entel.upc.edu>
In-Reply-To: <021e01d82fd2$3eee4570$bccad050$@yahoo.com>
References: <YiIR5qzuofR+bXlJ@hephaistos.amsuess.com> <oh9lxjj0nf3h.oh9lxjj2w4dj.g1@dooray.com> <021e01d82fd2$3eee4570$bccad050$@yahoo.com>
Date: Fri, 04 Mar 2022 19:00:50 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: g_e_montenegro=40yahoo.com@dmarc.ietf.org
Cc: yhc@etri.re.kr, draft-ietf-6lo-nfc@ietf.org, 6lo@ietf.org, "\"'Christian Amsüss'\"" <christian@amsuess.com>, 'Erik Kline' <ek.ietf@gmail.com>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at violet
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Fri, 04 Mar 2022 19:00:48 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/7hKgx75MeIwO5ocOgdRAKQIPQY4>
Subject: Re: [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 18:01:17 -0000

Hi,

Just to provide a few more details:

As captured in the IETF 112 minutes, the IESG was concerned that the NFC
specification was not publicly available (e.g. to allow checking any
details that might relevant to the IPv6 over NFC draft).

The authors provided a recent version of the NFC spec to Erik, and the way
to proceed is being discussed.

Cheers,

Carles



> +Erik
>
> Per the datatracker status info
> (https://datatracker.ietf.org/doc/draft-ietf-6lo-nfc/):
>
> IESG State: IESG Evaluation::AD Followup
>
> Perhaps Erik can comment?
>
> Gabriel
>
>> -----Original Message-----
>> From: 6lo <6lo-bounces@ietf.org> On Behalf Of ???
>> Sent: Friday, March 4, 2022 09:01
>> To: draft-ietf-6lo-nfc@ietf.org; 6lo@ietf.org; Christian Amsüss
>> <christian@amsuess.com>
>> Subject: Re: [6lo] 6lo-NFC status update?
>>
>> Dear Christian,
>>
>> I'm the author of the 6lo-NFC.
>> I believe the the draft (-17) has been resolved about all the COMMENTs
>> and
>> DISSCUSS from the IESG reviews with supporting of the 6lo Chairs.
>> But I don't know why this draft is stuck on the same status for a long
>> time.
>> I also have been waiting for something like action items for the next
>> step of
>> this draft.
>>
>> The 6lo chairs do not need to find new authors because I am an author of
>> the draft.
>> I would like finish this draft as soon as possible.
>>
>> BR,
>> Younghwan Choi
>>
>> -----------------------------------------------
>> YOUNGHWAN CHOI, Ph.D.
>> Principal Researcher, PEC, ETRI
>> Tel +82-42-860-1429   Fax +82-42-860-5404
>> Email  yhc@etri.re.kr
>>
>>
>>
>> -----Original Message-----
>> From:  "Christian Amsüss" <christian@amsuess.com>
>> To:      <draft-ietf-6lo-nfc@ietf.org>;   <6lo@ietf.org>;
>> Cc:
>> Sent:  2022-03-04 (금) 22:20:13 (UTC+09:00)
>> Subject: 6lo-NFC status update?
>>
>> 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