Re: [6lo] I-D Action: draft-li-6lo-native-short-address-01.txt

Luigi Iannone <ggx@gigix.net> Wed, 09 March 2022 13:07 UTC

Return-Path: <ggx@gigix.net>
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 E4E273A103E for <6lo@ietfa.amsl.com>; Wed, 9 Mar 2022 05:07:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20210112.gappssmtp.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 dkBb9i6W-aTg for <6lo@ietfa.amsl.com>; Wed, 9 Mar 2022 05:07:10 -0800 (PST)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 A9E883A102E for <6lo@ietf.org>; Wed, 9 Mar 2022 05:07:09 -0800 (PST)
Received: by mail-wm1-x332.google.com with SMTP id r187-20020a1c2bc4000000b003810e6b192aso1435016wmr.1 for <6lo@ietf.org>; Wed, 09 Mar 2022 05:07:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:message-id:date :cc:to; bh=Vx+TknMEyuXjKMh8fb8HWVUxuPVS+rOGnKPeulDnZ2I=; b=XqIAl2CGMyvdOvCqVJ6H3Mqz0KZL3/VMraiUo2mQ59HWwOQ40rBw0P3iAmdRfif2VG SmMCiCi689+idaT3z7dESFqAOxLFfNke5XoEJDzRnwQ19GgLfNrfRlPSdxerQV8+mKeL 1BZXkMRih0bV5pMZu6A6fADL9YdPQPf1Q/CtXzPch/G1odjpi8VZmv76bx+g/OrBvE0K K/ddrcc3WfoRS95SdF5fbmQWfJdbwNigap2d89h29HKLDC+xls6PzKWN26xKMcOcUFR7 stSAk+5kGHjouFK3p7/B7kbNISRFQMYw9ePvXAFjIgyR9vOT96BvK4YTxYqZsJ8mf7+T XxOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:message-id:date:cc:to; bh=Vx+TknMEyuXjKMh8fb8HWVUxuPVS+rOGnKPeulDnZ2I=; b=eZwt6L7A87uHhMa7A6gHOM/Ss6k11j+EhyhvR+hUOL3uhiIWuu1iSGP+N9zRPu0WlG 9lLqvsu6qC33UpkLOaIm6kgv10UNCgH9Ey5anrDION/ZmE/yHjRS9Z5Grg0/sMrwofCs xo7fVHUlurUBUMxm6ezdRGXKD1laIMiTpLDw9OMtmuUx9CKDzlj9JMGBxe1xV5rM1lgd Hl64Pz43z/xn3lGzIcLFuf5SyMD3eC5PbFb84QrAYOsrXwgeZpdmbaOwaMBKdetaRwuV 4JzFGpV8OpOkmnBGY1A1/IRBdny/llJCs5gNgfVxqMOSVMirNUMer3XUFkCcAv8P37nA dWQQ==
X-Gm-Message-State: AOAM532ohoJDibEQTSdWt8mUVF+2qEQydG+BhMAv5dA2FMW8OzZiwp50 cyoCCkZfI5TgBHx4v5tOfUV1unmh0CJ+oA==
X-Google-Smtp-Source: ABdhPJw4ZnaeioKGX1Lo/nJ6loEiDbMBN9YPdGUAKMA9S2G3kv6qvKmtAk5wt2HMDdyBSyh6ihQ1MQ==
X-Received: by 2002:a7b:c30e:0:b0:37f:a63d:3d1f with SMTP id k14-20020a7bc30e000000b0037fa63d3d1fmr3328825wmj.178.1646831227102; Wed, 09 Mar 2022 05:07:07 -0800 (PST)
Received: from smtpclient.apple (2a02-8440-3341-b5fb-8159-6372-f3b7-d698.rev.sfr.net. [2a02:8440:3341:b5fb:8159:6372:f3b7:d698]) by smtp.gmail.com with ESMTPSA id m3-20020a5d6243000000b001e33760776fsm1632812wrv.10.2022.03.09.05.07.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Mar 2022 05:07:06 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Luigi Iannone <ggx@gigix.net>
Mime-Version: 1.0 (1.0)
Message-Id: <EFFEB2F9-7213-4A9D-9967-065D0A0F71F5@gigix.net>
Date: Wed, 09 Mar 2022 14:07:05 +0100
Cc: 6lo@ietf.org, draft-li-6lo-native-short-address@ietf.org
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (19D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/mMqVctND3yA8C0WQAX73Pi77jtk>
Subject: Re: [6lo] I-D Action: draft-li-6lo-native-short-address-01.txt
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: Wed, 09 Mar 2022 13:07:15 -0000

Hi Carsten, All,

This is a follow up of previous feedback.

We submitted an update with several improvements, namely:
- Even stronger applicability scope right at the beginning of the document;
- Clarification in the architectural overview;
- Detailed the address assignment procedure (including the definition of two ND options)
- Revised and detailed the different roles of the node (root/forwarder/leaf).

We welcome any further feedback on this latest version.

Thanks

Ciao

L.


Sent from my iPad

> On 17 Feb 2022, at 13:08, Luigi Iannone <ggx@gigix.net> wrote:
> 
> Hi Carsten,
> 
> Thanks for your mail.
> Please see inline.
> 
> Ciao
> 
> L.
> 
> 
>> On 17 Feb 2022, at 11:11, Carsten Bormann <cabo@tzi.org> wrote:
>>> On 2021-12-14, at 10:09, Luigi Iannone <ggx@gigix.net> wrote:
>>> While we believe that the document is becoming mature, we still welcome any feedback people can send us.
>> I haven’t read the new version,
> You should. We did a lot of improvements ;-)
> 
>> but I stick with the observation that the problem/opportunity addressed is already solved with 6lo header compression (and will be more so once we have SCHC header compression in 6lo),
> Yes, the 6lo header compression is suitable in general for all IoT scenarios. However, this draft is targeting at scenarios and applications with static network topology and stable network connections. 
> In those cases, the NSA could bring in even shorter packet header (addressing) and _more_ importantly much simpler (stateless) forwarding mechanism, which will further saves the power consumption of the IoT system.
> 
>> and NSA does not have the same desirable properties with respect to preserving IPv6 semantics that the header compression solutions have.
> Can you articulate a bit more? Exactly which “desirable property” is present in HC but not in NSA.
> I can provide an example of the other way around, NSA provides stateless forwarding, HC does not do that.
> The new version of the document (read it :-) ) provides all the details on the operations to be performed on the gateway to translate from NSA to IPv6 and vice versa. 
> 
>> Right now, I would like us to focus on making the SCHC solution really good.
> I am also willing to help, but one does not exclude the other...
> 
>> In the end, that may not look very different on the wire from NSA (as far as addresses are concerned — SCHC of course can do more).
> We are coding the simulator exactly to quantify the differences. In certain scenarios NSA provide some advantage.
> But do not forget the second important property: stateless forwarding, we believe it is not negligible.
> 
> Ciao
> 
> L.  
> 
> 
> 
>> Grüße, Carsten