Re: [6lo] Review Request for ipv6-over-nfc-07

최영환 <yhc@etri.re.kr> Mon, 03 July 2017 08:08 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 D97F212EC3A; Mon, 3 Jul 2017 01:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, 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 7C_kjdLr6NJq; Mon, 3 Jul 2017 01:08:34 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr [129.254.27.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 681D11300BB; Mon, 3 Jul 2017 01:08:29 -0700 (PDT)
Received: from SMTP4.etri.info (129.254.28.74) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 3 Jul 2017 17:08:24 +0900
Received: from SMTP2.etri.info ([169.254.2.246]) by SMTP4.etri.info ([10.2.6.33]) with mapi id 14.03.0319.002; Mon, 3 Jul 2017 17:08:23 +0900
From: =?utf-8?B?7LWc7JiB7ZmY?= <yhc@etri.re.kr>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Samita Chakrabarti <samitac.ietf@gmail.com>, Dave Thaler <dthaler@microsoft.com>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, lo <6lo@ietf.org>
CC: James Woodyatt <jhw@google.com>, =?utf-8?B?67CV7KCV7IiY?= <pjs@etri.re.kr>
Thread-Topic: Review Request for ipv6-over-nfc-07
Thread-Index: AQHS3loOtHS3JPGfYE6gpuhow2yOt6IlNN4AgByxXqA=
Date: Mon, 3 Jul 2017 08:08:23 +0000
Message-ID: <B2C0C4C29044814AB285BBB7C754D92458C05E70@SMTP2.etri.info>
References: <CAKmdBpeUiiaixp1Dept0spes769jOJrYHVg4TCN1r1qPkDmA2g@mail.gmail.com> <62cc094156074e1ba96abc761e89e7a0@XCH-RCD-001.cisco.com>
In-Reply-To: <62cc094156074e1ba96abc761e89e7a0@XCH-RCD-001.cisco.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: multipart/alternative; boundary="_000_B2C0C4C29044814AB285BBB7C754D92458C05E70SMTP2etriinfo_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Wh-gZKzVIXnlqKQMEyTRH6ujSBs>
Subject: Re: [6lo] Review Request for ipv6-over-nfc-07
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 03 Jul 2017 08:08:41 -0000

Dear Pascal,

First of all, thanks for your comments.
Please, see in-line bellows:

BRs,
Younghwan Choi

From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
Sent: Thursday, June 15, 2017 7:43 PM
To: Samita Chakrabarti <samitac.ietf@gmail.com>om>; Dave Thaler <dthaler@microsoft.com>om>; 최영환 <yhc@etri.re.kr>kr>; 6lo-chairs@ietf.org; lo <6lo@ietf.org>
Cc: James Woodyatt <jhw@google.com>
Subject: RE: Review Request for ipv6-over-nfc-07

Dear authors ;

Thanks for incorporating a nonce in the computation of the privacy address. This addresses my concern. It would have been good to insist that you are doing it in the security section as well, but the text there confirms that the address is not repeated on the next connection so we should be all set. Also in the security section, I’m not sure what to do with this text:

“

   However, malicious tries for one connection of a long-lived link with
   NFC technology are not secure, so the method of deriving interface
   identifiers from 6-bit NFC Link layer addresses is intended to
   preserve global uniqueness when it is possible.  Therefore, it
   requires a way to protect from duplication through accident or
  forgery and to define a way to include sufficient bit of entropy in
   the IPv6 interface identifier, such as random EUI-64.

“
I fail to understand the first sentence and the paragraph reads as a problem statement, but for what?  Seems that section 4.3 does now provide the required entropy, correct?

>>  Yes, it’s correct. I support your comments. The paragraph have been done before I added the new texts in section 4.3. I’ll revise the paragraph in security section for the next version.

About section 4.5, I think some more text could be useful to assign the role of 6LBR.
If 2 similar devices meet (say 2 handeheld), whether one is 6LR/LBR. How would that be decided?
When they are different, if there is a fixed device (a payment terminal, say) or provides connectivity as a router, then it makes sense that it is 6LBR.
This could be described so we would not end up with 2 devices that cannot talk because they only do 6LN.

>>  You’re right. The current version does not mention the role of 6LBR when two NFC-devices meet. I’m working to add more texts for the role in the next version. Maybe, the new version (-08) including reflection about all feedback from you and James will be produced soon! Thanks a lot.

Cheers,

Pascal


From: Samita Chakrabarti [mailto:samitac.ietf@gmail.com]
Sent: mardi 6 juin 2017 02:16
To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>; Dave Thaler <dthaler@microsoft.com<mailto:dthaler@microsoft.com>>; 최영환 <yhc@etri.re.kr<mailto:yhc@etri.re.kr>>; 6lo-chairs@ietf.org<mailto:6lo-chairs@ietf.org>; lo <6lo@ietf.org<mailto:6lo@ietf.org>>
Cc: James Woodyatt <jhw@google.com<mailto:jhw@google.com>>
Subject: Review Request for ipv6-over-nfc-07



Hello Dave, Pascal, James and WG members:

ipv6-over-nfc-07 has just been published and the author mentions that he had addressed the comments from Pascal and Dave.

 Pascal and Dave,  would you please have sometime to review version 07 to check if your comments are addressed?

I have appended the excerpt from IETF98 meeting minutes for your reference.
This document is due for WG LC if  it looks okay.

James, you are shepherd for NFC draft -- please let us know if you are okay with the document's next step.

Thanks,
-Samita

As per IETF98 meeting minutes:
================================================

2 IPv6 over NFC                                    Younghwan Choi
  https://tools.ietf.org/wg/6lo/draft-ietf-6lo-nfc-06 was presented by Younghawn Choi on updates and
  discussed comments from WG and NFC forum. The draft was reviewed by NFC forum, no more comments
  from NFC forum. The author likes to move to WGLC.

  Dave Thaler:IID generation changed as a result of previous meeting

  Pascal: Replacing 6 bit address with hashing function with fixed parameters. Scanning is still
  easy. How is it different?
  YC: offset. Dave: offset should be random to add entropy, not predictable.
  Gabriel: offset may not be a right name. Nonce would be better.
  Samita: need reviewers before WGLC. Pascal, Dave, would you volunteer?
  Pascal will do the review and Dave agreed to review the final update.
=======================================================
---------- Forwarded message ----------
From: 최영환 <yhc@etri.re.kr<mailto:yhc@etri.re.kr>>
Date: Sun, Jun 4, 2017 at 5:02 PM
Subject: RE: [6lo] Request for IETF99@Prague 6lo Agenda items
To: Samita Chakrabarti <samitac.ietf@gmail.com<mailto:samitac.ietf@gmail.com>>
Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com<mailto:Gabriel.Montenegro@microsoft.com>>
Hello Samita,

I’ve submitted the new version of ipv6-over-nfc (-07). The document is ready for review.
Thanks.

Best regards,
Younghwan Choi