Re: [6lo] Warren Kumari's No Objection on draft-ietf-6lo-nfc-13: (with COMMENT)

최영환 <yhc@etri.re.kr> Fri, 07 June 2019 08:06 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 F2A85120121 for <6lo@ietfa.amsl.com>; Fri, 7 Jun 2019 01:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 rqgES3i_PWsK for <6lo@ietfa.amsl.com>; Fri, 7 Jun 2019 01:06:30 -0700 (PDT)
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 A56901200B6 for <6lo@ietf.org>; Fri, 7 Jun 2019 01:06:28 -0700 (PDT)
Received: from unknown (HELO smtpeg.etri.re.kr) (129.254.27.141) by 129.254.9.16 with ESMTP; 7 Jun 2019 16:59:41 +0900
X-Original-SENDERIP: 129.254.27.141
X-Original-MAILFROM: yhc@etri.re.kr
X-Original-RCPTTO: 6lo-chairs@ietf.org, samitac.ietf@gmail.com, bill.wu@huawei.com, 6lo@ietf.org, iesg@ietf.org, warren@kumari.net, carlesgo@entel.upc.edu, draft-ietf-6lo-nfc@ietf.org
Received: from SMTP5.etri.info (129.254.28.75) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 7 Jun 2019 16:59:45 +0900
Received: from SMTP2.etri.info ([169.254.2.250]) by SMTP5.etri.info ([169.254.5.142]) with mapi id 14.03.0319.002; Fri, 7 Jun 2019 16:59:40 +0900
From: 최영환 <yhc@etri.re.kr>
To: Warren Kumari <warren@kumari.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-6lo-nfc@ietf.org" <draft-ietf-6lo-nfc@ietf.org>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, "bill.wu@huawei.com" <bill.wu@huawei.com>
Thread-Topic: Warren Kumari's No Objection on draft-ietf-6lo-nfc-13: (with COMMENT)
Thread-Index: AQHU2j9SnelRJAWMoEG/HC11hP/GUaaP5IPAgAB0vUA=
Date: Fri, 07 Jun 2019 07:59:39 +0000
Message-ID: <B2C0C4C29044814AB285BBB7C754D9249AC9F1E9@SMTP2.etri.info>
References: <155255185094.2671.15731799736877181880.idtracker@ietfa.amsl.com>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.170.124]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/-IZ6vWi5fL5C3JsTMTZrQQNCx3Y>
Subject: Re: [6lo] Warren Kumari's No Objection on draft-ietf-6lo-nfc-13: (with COMMENT)
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, 07 Jun 2019 08:06:32 -0000

Hello Warren and all,

Thanks for your valuable reviews.
Please find my answers inline.

BRs,
Younghwan Choi

> -----Original Message-----
> From: Warren Kumari via Datatracker <noreply@ietf.org>
> Sent: Thursday, March 14, 2019 5:24 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-6lo-nfc@ietf.org; Carles Gomez 
> <carlesgo@entel.upc.edu>; Samita Chakrabarti <samitac.ietf@gmail.com>; 
> 6lo-chairs@ietf.org; carlesgo@entel.upc.edu; 6lo@ietf.org; 
> bill.wu@huawei.com
> Subject: Warren Kumari's No Objection on draft-ietf-6lo-nfc-13: (with
> COMMENT)
> 
> Warren Kumari has entered the following ballot position for
> draft-ietf-6lo-nfc-13: No Objection
> 
> When responding, please keep the subject line intact and reply to all 
> email addresses included in the To and CC lines. (Feel free to cut 
> this introductory paragraph, however.)
> 
> 
> Please refer to 
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-6lo-nfc/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I apologize - I've read the document, but it doesn't seem like it 
> contains enough information to allow a full implementation.
> 
> The document keeps talking about the fact that the range is limited to 
> 10cm, and makes some security assertions from this - from the little 
> that I understand about this technology (and I wasn't able to follow 
> all the references), ISO 15693 tags using NDEF are now part of the NFC 
> specification - these  work up to 1M. I have no idea if this protocol 
> is supposed to work over that, but if so, 1M is greater than 10cm.

You are right. Normally, NFC applications says communications with less than 10cm or single touch between two NFC devices, but I also know 1M range is available technically. But, 1M, I think, is also very short distance. Either 10cm distance or 1M distance of NFC is ok for IPv6 over NFC. Even though 1M is used for IPv6 over NFC, nothing of this document needs to change. Only some more explanations about the maximum 1M distance of NFC can be put if it is ok.

> 
> Also, I see you did respond to the OpsDir review ( 
> https://datatracker.ietf.org/doc/review-ietf-6lo-nfc-12-opsdir-lc-wu-
> 2018-12-19/
> -- thank you very much, Qin) , but there are things in these which 
> don't seem fully addressed. As an example, Qin asked: ----  Section 3.4 said ”
> the MTU size in NFC LLCP MUST be calculated from the MIU
>    value as follows:
>                              MIU = 128 + MIUX.”
> Can you provide formula to calculate MTU from MIU? Not clear how MTU 
> is related to MIU? ---

It would be "MTU = MIU = 128 + MIUX."

> 
> You responded: "YH >> Actually, MIU is the same as MTU. Specifications 
> in NFC forum use 'MIU', and we use 'MTU'. But these two has the same 
> meaning."
> 
> I read version 13 of this document and had the exact same question -- 
> how do I calculate the MTU from the MIU? If they really are the same 
> thing (which I'm not sure they are), the document should state that, 
> so readers can more easily implement.
> 

This document uses the two terms, "MIU" and "MTU". Actually, technical meaning of the two terms is the same. NFC spec says it as MIU. IETF says it as MTU. So, I mentioned this one in section 3.4. If more explanations about MIU for clarification, I will put the explanations about relationships between the two terms.