[6lo] Comments on draft-ietf-6lo-schc-15dot4
Kiran Makhijani <kiranmak@gmail.com> Thu, 18 May 2023 15:10 UTC
Return-Path: <kiranmak@gmail.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 899E5C151538 for <6lo@ietfa.amsl.com>; Thu, 18 May 2023 08:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4zcfcY9nAX_M for <6lo@ietfa.amsl.com>; Thu, 18 May 2023 08:10:08 -0700 (PDT)
Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88EE0C151982 for <6lo@ietf.org>; Thu, 18 May 2023 08:09:41 -0700 (PDT)
Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-561e5014336so14714007b3.1 for <6lo@ietf.org>; Thu, 18 May 2023 08:09:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684422580; x=1687014580; h=to:subject:message-id:date:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=dwCmtCj/7trLm12Acxu11GqkjC4pzDvrmCvfmY+70lg=; b=LOu8PpbQ48STBP8MrorUqRoQkfo3TzP9xCbUiMIOs5YohG60N4PJRLCqWrrucR54Bu CgPk9ZzMRX68y9lEbwIIGMkf6bRvquTO7G/J++I/YFhyTdYGpW3IgdoKU/jb/p+3k8Lt U+ILRVUBoNpUxLtobu8brh0ZAryMmBl+xaqDBDkLpjA8NZ1nUsvYhuz/Q315G2aYKk6n 4PMxo0/b/Ghnhq8pPyvSLevQHlUJrZalOkQRMp/Fdi7RiRAvxiSFLoRm7exOsc500ni0 KtYt2N3pboSbJMAN0b7N98A5BKngrd7OhIrC4MFA5p8Ilj5h6YJodCUtOaAmzQwwXrxD 7DmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684422580; x=1687014580; h=to:subject:message-id:date:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=dwCmtCj/7trLm12Acxu11GqkjC4pzDvrmCvfmY+70lg=; b=Tejiwpgzmv72dNC2ZX/O5+gwvNk0YyTIpJBlJoPhaxwpTxetXiBU/QnbNY47YjxWmZ PRuirIRGcnnfFMA9EvzjRdUeY3UaU6Uu40WOv7TBudHjGA7kY7CQY6UeXWsU0lvf/USz GROXcB8ZoPvg76HaJhetz5ltHYNTXTxpvInc7jjCdObz0wXo7rmNrZ7tt8fu69Da4Yhc MrcHbAuDMsRZHpLG4Uhue7+1Pq2cMejvghiKUgrEVE0x8F3pt4VOFoU3+pL8rOwidgSX 9CCEXqiEKMBbGuEEK1BNgxauXbD+X4o8AHgt9P2Lk2XOP0FM+ultQJtLWL2JxBKUX6fo /gFA==
X-Gm-Message-State: AC+VfDwfkdVpNz5DqbbCmi/mKXB5kNMrz8vI5yEsFwnnrO3BszC2gK4w 8V0ocbRetkUO46nW9DYsm/ZBpUon/sWIYqclUPwLNK6xrSI=
X-Google-Smtp-Source: ACHHUZ6v8C6o/YVFSoFqw680gddh4rE/CwmkzZi73cWfjW2CIkVbDPQLKFvQjNnrQetYPj5TPKBbWD5R0VtBN2vWtqI=
X-Received: by 2002:a0d:d750:0:b0:55d:c333:26c4 with SMTP id z77-20020a0dd750000000b0055dc33326c4mr1856140ywd.0.1684422580333; Thu, 18 May 2023 08:09:40 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 18 May 2023 08:09:39 -0700
From: Kiran Makhijani <kiranmak@gmail.com>
MIME-Version: 1.0
Date: Thu, 18 May 2023 08:09:39 -0700
Message-ID: <CAEZ-O0krGN=q-rmHHhTS-7exgtk9m8mXoO6oK4P6WUmGukLEow@mail.gmail.com>
To: 6lo@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008d6fd305fbf93110"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/qgY8ylAG5AABepP0_cJTIohFU8k>
Subject: [6lo] Comments on draft-ietf-6lo-schc-15dot4
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: Thu, 18 May 2023 15:10:09 -0000
Hello authors, Apologies for late comments. May be we can talk about the detailed review later, instead I wanted to discuss high-level points first. Please take them as comments from a newbie... 1. I found it bit challenging to catch up with all the past 4-digit RFC-soup that this document need to reference (3 from SCHC, 3 from base 6lowPAN, a few on RPL). It becomes arduous to follow everything (I had to read 4 to 5 documents before getting reasonable understanding on how I could help with review). I am not sure how can this be addressed but something to consider as a broader assumption when writing the document. 2. One suggestion is to re-write architecture section. 2.1. Since 6lowPAN is using SCHC, I find it odd that it does not talk about adapting SCHC architecture in LLN. i.e. say what node will need to support what SCHC functionality. Then the document will become easier to read. For instance, you could draw a LLN with 6LRs, BRs etc. and say what SCHC gateway functionality will fit where instead of saying in straight-forward RPL rules should be installed in all LRs... 2.2 So I suggest first present both the architecture then map functions will be better and then develop cases. 2.3 Ques: how are SCHC rules distributed in LPWAN? Can same techniques be used or RPL is the only approach? (sorry, I am not finished reading SCHC and don’t know this yet). 3. I would have really liked to see 'SCHC dispatch' discussed earlier as part of the architecture instead of dealing with it later. This is a key LLN dataplane enhancement and everything builds on top of it. The key is you are not adding new rules, you are using LLN data plane to carry SCHC and nodes with knowledge of this feature will process accordingly. To summarize, when you put this together, reading of document will be very simple: - adapt SCHC architecture - describe new dataplane enhancement - describe routing mechanisms - formats... What do you think? It's possible I must have misunderstood, in that case please bear with my ignorance :-). Thanks Kiran
- [6lo] Comments on draft-ietf-6lo-schc-15dot4 Kiran Makhijani
- Re: [6lo] Comments on draft-ietf-6lo-schc-15dot4 Carles Gomez Montenegro