Re: [6lo] Zaheduzzaman Sarker's Discuss on draft-ietf-6lo-nfc-19: (with DISCUSS)

Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com> Fri, 24 February 2023 10:16 UTC

Return-Path: <zaheduzzaman.sarker@ericsson.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 17021C169536; Fri, 24 Feb 2023 02:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDRLalTFp0aO; Fri, 24 Feb 2023 02:16:52 -0800 (PST)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2088.outbound.protection.outlook.com [40.107.22.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09C3FC16B5A3; Fri, 24 Feb 2023 02:16:51 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CLWn1i7Vr4sr1Po36D1QlF9PD9LkQgGi+RtO13pRy97HmaHRGmlDZLikqaCngwomOFMZ0Y5ijGt5U9IOIcB0fZgLcUIAwIJZV9d64FPuLE0DYOnMNBFwKOjOaHGxVGgZochr+l6xiZtc6BKT5VT4loACqlQR/E7ODpon/rt9kUkQJDDoMEphejp59Dt3b6hLshPIaYD59PbsdAaoMXyL8gxsIr3m+X2JU2rJ/TvW9MuAHt5DGamMXaT0iULrlquChFSrE9xFjYkmflGb8OmyD6/uA2T42PLK468ekX3pqWuGdH+rZMttwp75BCY4RRqC5WbcNwVOresahO9D+qFieA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=plGN3h1KFes4dWKLaNbh7EQ1swvJu1C63tKqQgkV5to=; b=kjOKshITNpSCp1neGu2Cnd+7RLo7Pm9T035LZyjbv7R5hv+1I9UlpoInsIvxNppZBI8KgNrRhJY/i6ojxGGI8idnXY8UY4Zqaa/GbGKpvKkliNvVWRSNrBIa5hpXtNEbRtPfOglRH0Hry7U6E4uRoA6HKTgbOt4jmvzcctJyZjcrad/+h3wg5FH5WSpPMJ1RHaGSyJ7QPzwOOeDAHGR6AF/2iInzbnr3rDt1mljpRhYTK1SDYDwEds3aqR00bClJAgaTgTUbDXxax6aghdxkFPOrzAy4UdO/Oq56SBoaV/SLFxRemrP/beJ3JoIDNSeCzCJvltkYpb4j1nL05Q8XcQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=plGN3h1KFes4dWKLaNbh7EQ1swvJu1C63tKqQgkV5to=; b=LD28y/FhRsG3mw+JqIxNSDntT8ohZARq0+MSt4XcE7Lg6UZmwatrNYF5tgMTFhgMTnimudNws1ul20X1eU0NocRFddCdT0D1GknDbOXmX5BiLA90rfl6JGbHBPFUOfIe0GmkkUWH1EUTXj85Ta+SymBsbL4WcVqL4DRlua5+IOg=
Received: from DB7PR07MB3995.eurprd07.prod.outlook.com (2603:10a6:5:3::23) by PA4PR07MB7661.eurprd07.prod.outlook.com (2603:10a6:102:bb::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6134.24; Fri, 24 Feb 2023 10:16:46 +0000
Received: from DB7PR07MB3995.eurprd07.prod.outlook.com ([fe80::cff6:c2d5:4fc0:4afd]) by DB7PR07MB3995.eurprd07.prod.outlook.com ([fe80::cff6:c2d5:4fc0:4afd%3]) with mapi id 15.20.6134.021; Fri, 24 Feb 2023 10:16:46 +0000
From: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
To: Erik Kline <ek.ietf@gmail.com>
CC: "yhc@etri.re.kr" <yhc@etri.re.kr>, The IESG <iesg@ietf.org>, "draft-ietf-6lo-nfc@ietf.org" <draft-ietf-6lo-nfc@ietf.org>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, Samita Chakrabarti <samitac.ietf@gmail.com>, Carles Gomez <carlesgo@entel.upc.edu>, Wesley Eddy <wes@mti-systems.com>
Thread-Topic: Zaheduzzaman Sarker's Discuss on draft-ietf-6lo-nfc-19: (with DISCUSS)
Thread-Index: AQHZIKw3tusmFUpm60a9067tdOUNc66ViNqAgEhn/ICAAEABAA==
Date: Fri, 24 Feb 2023 10:16:46 +0000
Message-ID: <E0B87E9F-B1DA-4100-9AB6-1D5A3995A2CF@ericsson.com>
References: <167288516911.30036.17997314654448194343@ietfa.amsl.com> <36774852-8711-473E-B060-054007B88432@etri.re.kr> <CAMGpriWmjcF-2N-v628KWggojR+kqbCsn5fN14G6oLV6RudGDA@mail.gmail.com>
In-Reply-To: <CAMGpriWmjcF-2N-v628KWggojR+kqbCsn5fN14G6oLV6RudGDA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3731.400.51.1.1)
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DB7PR07MB3995:EE_|PA4PR07MB7661:EE_
x-ms-office365-filtering-correlation-id: 10b8e8fd-efe0-4231-718a-08db16503bfb
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: tsda0ZzMqHNYWBHgotuhR9tKkmnNXjDsvosnjEu87G1Apobc5oKYkVp5ha7AtCVgoQwNUn3XsivC/oNCHAT2t+4kLb+vemarpFVXXxJm2+qCBy2MjRYjyXx/bnpSa2UEKp1Sp7ulMmLlxzfsLlvIUxlaLq6WGU4xtgKlFXQrloe+fF54WLSNz3XQe6xJoKzmU5jAS7sYFzdiqIqgSOY9s5c322+E7VLjnPq7HYjUjcvTL8AppeTVwtIK+xCIQ5ygEuZDffszULBFTefSmtpmzbskbcTSkhEe+M/DytgaAT7/KysAIHOzXOXTpzgRnehCf6cJXRJRDDLKkYz4D4YrK1weQnjEHxh+FKwNJr0vRHFHCGQTOzmQdil6N96pficEFYB9RM71KwCyZPDTQwR00O8a/7CgZcKoo2docpa2IXeqXreAer5nqgsRussUShyBvCCZhk/K79fY+JHsA/4plD6aaZTC+m6d994E1d9Uv6IXdGqH4GIFptX+BeW68xnfgolYilA3zdXYRtxBUICevdROsz2UquiECIpmoONt4qIBLLBIuuoXfZsrz0h8zEchEptaczQXOjnnh08E+i6WJ23oXiIljVvLPedqV+Xs5l0jSKxfyQ4TbkPEVd6Er/I8UG7WuUvD8N5TVIbCZ+5RfkyJhcCVwMrl2J8EnxwgzBCwSDcvdbuZdKT+wIyF4ZVhDGyEGJ+HoOYJOMKny6GMUwuR/7LNSMWghTxDBtaEybj2ICjrD6svBYxhN3UySJ/0
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB3995.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230025)(4636009)(346002)(396003)(39860400002)(136003)(366004)(376002)(451199018)(36756003)(966005)(6486002)(71200400001)(54906003)(38070700005)(33656002)(166002)(86362001)(82960400001)(478600001)(83380400001)(2616005)(26005)(6506007)(186003)(6512007)(2906002)(8676002)(6916009)(4326008)(76116006)(66946007)(66476007)(64756008)(91956017)(66446008)(66556008)(316002)(41300700001)(44832011)(5660300002)(8936002)(53546011)(99936003)(38100700002)(122000001)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 74XEyhTEm9zQOecumC3ZIO3D1djSWJXcZnC8kXZUBibbDKTKvaoglV9Baw5f7rALaq/KYQ6AfUaegfyGTBQcTKWYIl2IDQ07njzNFyvEl4YVNNZW5zJbHp6CZWDoHDKEOYgl2rDO+DOfY5IKXEme5wLVwSHhxD8SNBXXn3kKoTL+db/JGdWeQCHc7YheCGGVdK8xO8FuwjX7kCQ6bTGkFkEcYqhQaYBfzXJG94fl9rOA+B9a97J5z9L/p82T3BKOwJkB5a4UEXLdyUXgHZkCrVN/BxENA0jRxiCWVj+krrCIh387zxDRff57bCZy3uQakT2NLWJFB+w6kFjLBTIwcSlfo4g4CW+QKZXQDdH6vXPlJtfBjPlYyO3BKRRXnjbyvHH3DG+RP3LJs4qmELoSGhFC9wzMa39aF87hKoUg6nmknHyms3epzlzCfTEDSXA5d89X3FhCaXZGCDbEInYlFnSoXVQJL6mq+WR4jnMApvIj/lnNZfni56g6/cS3x8601qGSd5SvmTLlF7Y6pUXWaMuMJJPMAonzP1dscQiBHNPBG3F6l1445CZDH934GegxqeScz7lsZn79jdMTGRZFlHSTcjk2DwCp8sqQoWFvbOoetPVHDg7Riv+AVVq0RXRvvyc6+cQYvtOY9nysR6mkYtTxUzZ3jgIvJbIDQ0xZJtIoemqtoQLsEvy8HyoIZ+UWsGemJ9Ebjc3loCZRzxWHuoRpQs7XS8l89PeMSGIw9A6xpUU49HlK2wrPHzF3yrA1/cpgOAzr+YcYENlgeGlp6TtmUTClMHASuVYer6HFYXRoi1XmVzE0/M9xZOXV2D/Vq+HRMlDf8b6M7glXYAAq987EC9uY6cT0ZfUj6YhXalUmZhu7Sf+rAmG7meQalvdF0THD61Iaz9tYMAenH+JUHF4gwUeq5OYLMQMgohlh8aaLwId6LczMr7O1/4s8BJUXAV1cSTQ4fT8DWhodee0kJ+fLRYOjMLGT8yDUYDkbS8gCaR4PBMiMuAmUOYm+HLdSRiD4k5GCLMS2P4dwvym83Vf59wnEbxiRDtSCDvrigo3PFN9oTG2BXJvBe3l4GBDDflwKj2JFigyBEli1leaCP59i7HNCEHZrXALrXi3+oyBWHx9DAt0+ARjXHSnfRtKVt42uF/irZa4ZZ5cSvIsLIpFrmyw7VVk0FRRVCK4z5TiAiMmrJ8XU1Py6CffZ+6hv6nrH9st4Xi/WwkXtNxy362Mj/NNGqEmj2KPXzpYv3qxEUegtDhiKsJtvlE5hnbE6HV/f2qXTggTQX+rvDc857WYqWcMdEYJCaQrSijD/I7fyn0v/0gE3RyVVPJMrvgJAbAvOQP22opEpJsUPky6Ke6r81olZvpNJ/TxdoEJx83F6WMH/4Lz1H0aQ29qkpGzWphh2e9kiT47bSQqpFavJkOCeNTmntcwlKgRhMTVdiKDb4I2mAUPMfeqLktcwgkaOSrxGrUGG+HY7BOlLyOK3W3x3dCyg+uore7cNBl58i3ltqn2VNbhSmUKC4LLmArzBxXuLxe4MkmLo7eq0q53S/wtvaFgwBW10OaFeo5gJEr83G36AtgiIzOsw1t8ROM0CsZu8WTGJPnFMmgPxI8brZZbRSGgQUTxyJaljdhvZncg=
Content-Type: multipart/signed; boundary="Apple-Mail=_6B809668-4E75-4388-853C-F374856F3566"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB7PR07MB3995.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 10b8e8fd-efe0-4231-718a-08db16503bfb
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2023 10:16:46.2117 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 5i6AwMnGS7f92j6OGtH4LwGMZbEC9F4XBfyeQxu0UlOg/AWGZKKkVxTILwOGNDbPjB4Y19RXiGw0HcTSalfb7HxW/KB4sOvV14gi1CvJ+iO/SO/GnD2aUmiWhUiddiHi
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PA4PR07MB7661
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/ty8KLB5-6ct3kLY9rksD8wkkdLU>
Subject: Re: [6lo] Zaheduzzaman Sarker's Discuss on draft-ietf-6lo-nfc-19: (with DISCUSS)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.39
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, 24 Feb 2023 10:16:57 -0000

It looks mostly OK to me. However, would have been better if we can get any response from Wesley Eddy (I have included him in the CC - in case he missed this conversation).

What I didn’t quite get is the reason behind certainly removing IPV6-LLCP binding from NFC logical link layer in figure 1 and how removing that helps.

//Zahed

> On 24 Feb 2023, at 07:27, Erik Kline <ek.ietf@gmail.com> wrote:
> 
> Zahed,
> 
> Do these proposed changes address your concerns?
> 
> On Sun, Jan 8, 2023 at 8:52 PM yhc@etri.re.kr <mailto:yhc@etri.re.kr> <yhc@etri.re.kr <mailto:yhc@etri.re.kr>> wrote:
>> Dear Zaheduzzaman Sarker,
>> 
>> Thanks for your DISCUSS points.
>> I am not sure what was going on Wesley Eddy's comments and why the comments were not addressed.
>> Anyway, I’m sorry about that happening.  Please find my answers inline bellow:
>> 
>> Best regards
>> Younghwan
>> 
>>> On Jan 5, 2023, at 11:19 AM, Zaheduzzaman Sarker via Datatracker <noreply@ietf.org <mailto:noreply@ietf.org>> wrote:
>>> 
>>> Zaheduzzaman Sarker has entered the following ballot position for
>>> draft-ietf-6lo-nfc-19: Discuss
>>> 
>>> 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/about/groups/iesg/statements/handling-ballot-positions/ 
>>> for more information about how to handle DISCUSS and COMMENT positions.
>>> 
>>> 
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-6lo-nfc/
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>> 
>>> Thanks for working on this specification. Thanks to Wesley Eddy for his
>>> excellent TSVART review.
>>> 
>>> As I agree with the points brought up by the TAVART reviewer, I would like to
>>> discuss why the points made by the reviewer should not be considered for this
>>> specification.
>>> 
>> 
>> There are three comments in the Wesley Eddy’s review as bellow:
>> 
>>> (1) Are there relations that need to be considered between IP header bits like
>>> the DSCP or ECN signalling relevant to NFC links, or is it expected that NFC
>>> links/hosts would not be able to utilize these meaningfully?
>> 
>> I don't think there are relations that need to be considered between IP header bits, 
>> and NFC links/hosts would not be able to utilize these meaningfully.
>> 
>> If it is required to make this clear in the draft, I will put a new texts at the end of Section 3.2.
>> 
>> NEW:
>> 
>> Section 3.2 (Protocol Stack of NFC)
>> 
>> “In addition, NFC links and host do not need to consider IP header bits for QoS signaling, 
>> or utilize these meaningfully ." 
>>  
>> 
>>> (2) How are upper layers made aware of the MTU supported on the link if it
>>> could established via either MIUX or FAR? TCP and other protocols need the
>>> correct information in order to send packets properly.
>> 
>> At the beginning of NFC LLCP (v1.0), there was a consideration for separated spec. of 
>> "binding to IP Protocol" in NFC Forum. Thus, the first draft of IPv6-over-NFC also didn’t 
>> consider MIUX because NFc can use Fragmentation and Reassembly. 
>> However,  the spec., "binding to IP Protocol" is not considered any more in NFC Forum. 
>> From IPv6-over-NFC (ver. 6), "The MIUX value MUST be 0x480 to support the IPv6 MTU 
>> requirement (of 1280 bytes)" has been put in Section 3.4.
>> 
>> If it is also required to make this clear, I will put the sentence in Section 3.4 as bellow:
>> 
>> OLD:
>> 
>> The MIUX value MUST be 0x480 to support the IPv6 MTU requirement (of 1280 bytes)
>> 
>> NEW:
>> 
>> As per the present specification, the MIUX value MUST be 0x480 to support 
>> the IPv6 MTU requirement (of 1280 bytes).
>> 
>> -------------------
>> 
>> To make these consistent, I will also revise the Figure 1 as bellow:
>> 
>> OLD:
>> 
>>        +----------------------------------------+ - - - - - - - - -
>>        |              IPv6 - LLCP               |         
>>        |                Binding                 |       NFC
>>        +----------------------------------------+   Logical Link
>>        |      Logical Link Control Protocol     |      Layer
>>        |                 (LLCP)                 |         
>>        +----------------------------------------+ - - - - - - - - -
>>        |               Activities               |        
>>        |            Digital Protocol            |   NFC Physical
>>        +----------------------------------------+       Layer
>>        |               RF Analog                |         
>>        +----------------------------------------+ - - - - - - - - -
>> 
>>                       Figure 1: Protocol Stack of NFC
>> 
>> 
>> NEW: (removing “ IPv6-LLCP Binding”)
>> 
>>        +----------------------------------------+ - - - - - - - - -
>>        |      Logical Link Control Protocol     |    NFC Logical
>>        |                 (LLCP)                 |    Link Layer
>>        +----------------------------------------+ - - - - - - - - -
>>        |               Activities               |         
>>        |            Digital Protocol            |    NFC Physical
>>        +----------------------------------------+       Layer
>>        |               RF Analog                |         
>>        +----------------------------------------+ - - - - - - - - -
>> 
>>                       Figure 1: Protocol Stack of NFC
>> 
>> 
>> 
>>> (3) The data rate ranges are mentioned, but not whether IP over NFC links would
>>> be expected to have some type of delays or variation in delays associated with
>>> them or typical frame loss rates, etc. that might be of interest in properly
>>> configuring transport protocols. One could imagine this might be the case with
>>> passive targets.
>> 
>> NFC Link layer Protocol (LLCP 1.4) provides two types of communications 
>> (i.e., connectionless transport and connection-oriented transport) by itself.
>> These are described at the end of Section 3.2, Actually, NFC links do not always
>> guarantee perfect wireless link quality, so some type of delays or variation in delay
>> would be expected in any case. 
>> 
>> I will put some texts for clarification in Section 3.2. 
>> 
>> OLD:
>> 
>>    The LLCP consists of Logical Link Control (LLC) and MAC Mapping. (…)  
>>    The Connection-oriented Transmission component is
>>    responsible for maintaining all connection-oriented data exchanges
>>    including connection set-up and termination. 
>> 
>> NEW:
>> 
>>    The LLCP consists of Logical Link Control (LLC) and MAC Mapping. (…)  
>>    The Connection-oriented Transmission component is
>>    responsible for maintaining all connection-oriented data exchanges
>>    including connection set-up and termination. However, NFC links do not 
>>    guarantee perfect wireless link quality, so some type of delays or variation 
>>    in delay would be expected in any case.
>> 
>> 
>> 
>>