IETF Logo Mail Archive

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

최영환 <yhc@etri.re.kr> Fri, 04 March 2022 14:01 UTC

Return-Path: <yhc@etri.re.kr>
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 16EA73A0C0B for <6lo@ietfa.amsl.com>; Fri, 4 Mar 2022 06:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NO_DNS_FOR_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dooray.com
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 00qx0ebRHYx7 for <6lo@ietfa.amsl.com>; Fri, 4 Mar 2022 06:01:21 -0800 (PST)
Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4233A0A0A for <6lo@ietf.org>; Fri, 4 Mar 2022 06:01:16 -0800 (PST)
Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 4 Mar 2022 23:01:12 +0900
X-Original-SENDERIP: 211.180.235.152
X-Original-MAILFROM: yhc@etri.re.kr
X-Original-RCPTTO: 6lo@ietf.org
Received: from [10.162.225.109] (HELO send002.gov-dooray.com) ([10.162.225.109]) by send001-relay.gov-dooray.com with SMTP id 5902c9aa62221ba8; Fri, 04 Mar 2022 23:01:12 +0900
DKIM-Signature: a=rsa-sha256; b=UpKUzmAkvvMJ1APnOL2y5Oui9OA7U9unGbZtPRiBhkyqlN8ghW6d/+opWghD0e8ITSqaUIXMfU 3f81jv8Y/ORl4umXgny3umxlsPW5fSeKu/Zg1RlOeJ40QfGWbY22Iu63xjYAdFd9UFtzL/OcRRJC CJhFTs+TKma80h6Ke7xWpBC8FEg06CppU9ZwlZFka1M8Lbw+DtsO93RDrgHriWZrrDyzaFxTo+nN 2xvd6wBTy///9QhdIVIKnvx2KSNUYNbiNaV3LPc9t+j3jd71dHYwmf36KiGtHX1EXojvswrLlI/V yqZq9TFQZUrRCcXlTm8O3Rx1ra4lOsevLy0lwOJA==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=sewOZTjqSeB1jArXj4PIrTyOTGVPTJDC0aiXipdtaaE=; h=From:To:Subject:Message-ID;
Dooray-Meta-Signature: hNaqwgD9Bg5O8BBFL9VKY7jfCV+4N0TJ/E2O3Xd7eukaBWDUw4F9p R5x0pdJxqjN6s915o7W1VucUCd+W2Cmmzb1Yz6hTpO6WkJGj6mVBaiigzlMafiLUfPLuVCEGghQN bYMWdVICHxwK7Z/OtIqhDB4j9vVkFLB0RYFjCo/WxFTM+VSpiZm3hQSbZ9m0dCN/6q5dni7Nk3mK W2HXzAzw8vfBnBwsMK4+Qktt2v13TWg+kjelb3zJouvP7C4v1j5Wx73500OmDQrF4WLnesyvmaNn vLixjlddvUWAXhXRbMu/ov4jzMv9aVYH5lUuqsMa9CXj8h8yWmPejR8DtbPj2YgkUdpDm1MPRFwL MqG03s=
Received: from [129.254.29.11] (HELO 129.254.29.11) ([129.254.29.11]) by send002.gov-dooray.com with SMTP id e608301362221ba7; Fri, 04 Mar 2022 23:01:11 +0900
From: 최영환 <yhc@etri.re.kr>
To: draft-ietf-6lo-nfc@ietf.org, 6lo@ietf.org, Christian Amsüss <christian@amsuess.com>
Message-ID: <oh9lxjj0nf3h.oh9lxjj2w4dj.g1@dooray.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Dsn-Request: true
X-Dooray-Agent: mail-api
X-Dooray-Mail-Id: 3222051497139783725
Importance: Normal
X-Priority: Normal
X-MSMail-Priority: Normal
X-Dooray-Attached: c3+LUOpPU/IB7Wl+oemm0lw5HiI/bJHHYClX72L8E3o=
Sender: yhc@etri.re.kr
Date: Fri, 04 Mar 2022 23:01:11 +0900
References: <YiIR5qzuofR+bXlJ@hephaistos.amsuess.com>
In-Reply-To: <YiIR5qzuofR+bXlJ@hephaistos.amsuess.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/jN7cmpdnTGwEDLIctScj_mcs5G8>
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 14:01:26 -0000

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

v2.23.0 | Report a Bug | By Email