Re: [6lo] SCHC HC over IEEE 802.15.4: 1. Generic vs IEEE 802.15.4-specific document

Carles Gomez Montenegro <carles.gomez@upc.edu> Fri, 14 July 2023 12:36 UTC

Return-Path: <carles.gomez@upc.edu>
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 813C7C151AFE for <6lo@ietfa.amsl.com>; Fri, 14 Jul 2023 05:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.895
X-Spam-Level:
X-Spam-Status: No, score=-6.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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, URIBL_BLOCKED=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 (2048-bit key) header.d=upc-edu.20221208.gappssmtp.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 oesgPGxW8a4r for <6lo@ietfa.amsl.com>; Fri, 14 Jul 2023 05:36:01 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 A0AE8C15108F for <6lo@ietf.org>; Fri, 14 Jul 2023 05:36:01 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-3fbc54cab6fso17287265e9.0 for <6lo@ietf.org>; Fri, 14 Jul 2023 05:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=upc-edu.20221208.gappssmtp.com; s=20221208; t=1689338159; x=1691930159; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dvl0m/39fWAxofdyoqTeU5ue4ulIe1fTRhF7ADid+Dc=; b=ItpUMkouBwkxpSGd7s5g+sFGRGuAADSOZJdHlee3Kc3DUhW56IjwV/mf7whvjVmVIg 9cuzYt7GTQ8iQv/ma+dbYRfqCrShn4QJbpHQPgqaYSEe+4lFDEQFxdVmsFm8IAb8RHIn zgjYgcWZ+FYD6qY0SHU9iSVCLIsIEod2FcIevbpO/F5MlUNc/UUzJaXJ5SqAV7cd3Pdq quwwDgjX1kkptREqZbUDSZHh7LwaEtHl4J1BIaKKj6Nf7WdewupSmf908yYy6UstXjCg IsLuj+n/LepCha2Hw5CZ3vAvQE7p3gO22RFpagHu3sHMH4a50YFMRXcv5+szB22PZjPC ZAYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689338159; x=1691930159; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dvl0m/39fWAxofdyoqTeU5ue4ulIe1fTRhF7ADid+Dc=; b=DuCjajlXcvZg/HpJMOk70yO1RUJoV4DeaZRQ2dIRkR2bZNl8oj/Ai3xCMDoCIv0zjV 8kx3Pq6MFTWQEwGxyKBZAGDacjPHRpxNaf7vPN+kNnlDOurDrfdqnKUkxu+a7AqL3cZ5 Fa80FEaPWnBgUGQZ1F3q251mWvzuw7S8XkS1o+PgKfPgzgmrbGwwj2iagBILKubk4a1C BLVNlSUNHcwUYvZo2VrKAlDEaTK+RME+ohw6LUwaxwg9yeYS1rckZtjMqaIop2ZZglZO NDAxJi89LAieaGphg0N/E7Tr4+GIfpcyifv+eY6bgxf9PdODLq1Ik+e4GhwWVxwBSgtV 2uGw==
X-Gm-Message-State: ABy/qLaJp6uM4ci02luNz8s5CzvQWC0sEIuMkW9GhZAwwqdNmJK0MB1q YR2/0Yge8nBQp9xBLK0pkbkIRXLrjGFvU1YxBgFIWA==
X-Google-Smtp-Source: APBJJlFtCQoREJ6S++7kUt2KrxIiVVGWrJSNK8+1XhPyRBDM89/VqZFpBv4VjUq6981kjY/QkawrA+afp0yb30J+F8Q=
X-Received: by 2002:adf:e6c4:0:b0:314:11ea:480d with SMTP id y4-20020adfe6c4000000b0031411ea480dmr3785900wrm.9.1689338159232; Fri, 14 Jul 2023 05:35:59 -0700 (PDT)
MIME-Version: 1.0
References: <CAAUO2xzozvZJEb4wV56Y5F1aK=Yfve5Kudet_Gk0+_c-LnC8gw@mail.gmail.com> <3C3B4FC7-D41B-4AAD-A5A9-91F21510BAC1@cisco.com>
In-Reply-To: <3C3B4FC7-D41B-4AAD-A5A9-91F21510BAC1@cisco.com>
Reply-To: carles.gomez@upc.edu
From: Carles Gomez Montenegro <carles.gomez@upc.edu>
Date: Fri, 14 Jul 2023 14:35:47 +0200
Message-ID: <CAAUO2xzGQWoC_9zZFAsYG6308hF5xSk88gVF9XDQjf0Hg5kD8A@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: "6lo@ietf.org" <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e31541060071b04f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Y8NwiJsuYW4UmRAHSWcxOAnVA4E>
Subject: Re: [6lo] SCHC HC over IEEE 802.15.4: 1. Generic vs IEEE 802.15.4-specific document
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, 14 Jul 2023 12:36:05 -0000

Hello Pascal,

Thanks for your message.

Sure, let's talk about it at IETF 117!

Cheers,

Carles (as WG participant)

On Thu, 13 Jul 2023 at 13:21, Pascal Thubert (pthubert) <pthubert@cisco.com>
wrote:

> Hello Carles:
>
> I have an item (against the architecture) about the information that SCHC
> needs in the packets (some of which being implicit could be elided)
>
> My bottom line is that once we have that we should be able to define the
> use cases for which a separate spec is desirable vs on that covers multiple
> L2s.
>
> Same as for IPv6 over foo I guess…
>
> Let’s talk in SF!
>
>
> Regards,
>
> Pascal
>
> Le 13 juil. 2023 à 11:35, Carles Gomez Montenegro <carles.gomez@upc.edu>
> a écrit :
>
> 
> Dear 6lo WG,
>
> We would like to receive feedback about two potential discussion items
> regarding the document on transmission of SCHC-compressed packets over IEEE
> 802.15.4 networks [1]. We will send one separate message for each item.
>
> 1. Generic vs IEEE 802.15.4-specific document
>
> One question that has been raised on occasion is whether the document
> should be written specifically to enable the use of SCHC header compression
> over IEEE 802.15.4 networks (i.e., the current approach) or in a generic
> way, independent of a specific underlying technology.
>
> We (authors) followed the current IEEE 802.15.4-specific approach as it
> seemed more straightforward, and focusing on IEEE 802.15.4 entailed
> interesting opportunities. Coincidentally, this approach is similar to the
> original 6LoWPAN approach, which was designed to enable IPv6 over, mostly,
> IEEE 802.15.4. 6LoWPAN has been reused/adapted in 6lo to enable IPv6 over
> several other technologies, by means of a technology-specific document for
> each technology. Perhaps a similar approach could be followed if there is
> interest to enable the use of SCHC header compression over other
> technologies.
>
> Notes:
>
> - If we write a generic document, there will still need to be a
> technology-specific document for each intended underlying technology.
>
> - The document uses only the SCHC header compression component (i.e.,
> 6LoWPAN/6lo functionality is used for fragmentation).
>
> Thoughts? Would you have any particular preference on this matter?
>
> Thanks,
>
> Carles and Ana (document authors)
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-6lo-schc-15dot4/
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>
>