[lp-wan] Architecture

Laurent Toutain <laurent.toutain@imt-atlantique.fr> Tue, 28 June 2022 07:52 UTC

Return-Path: <laurent.toutain@imt-atlantique.fr>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D550DC15CF59 for <lp-wan@ietfa.amsl.com>; Tue, 28 Jun 2022 00:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=imt-atlantique.fr
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 7fcCckIMzVAY for <lp-wan@ietfa.amsl.com>; Tue, 28 Jun 2022 00:52:53 -0700 (PDT)
Received: from zproxy130.enst.fr (zproxy130.enst.fr [IPv6:2001:660:330f:2::c2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 727DFC15CF5E for <lp-wan@ietf.org>; Tue, 28 Jun 2022 00:52:52 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id D839D120320 for <lp-wan@ietf.org>; Tue, 28 Jun 2022 09:52:47 +0200 (CEST)
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 9srgrb-jEnaD for <lp-wan@ietf.org>; Tue, 28 Jun 2022 09:52:47 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 445D1120471 for <lp-wan@ietf.org>; Tue, 28 Jun 2022 09:52:47 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy130.enst.fr 445D1120471
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1656402767; bh=4KGsKmtlGHh61nS2CnrATo8mgInmQ5mazTygrXtfMPk=; h=MIME-Version:From:Date:Message-ID:To; b=BZeIq7CjOoARWDCRHhRk6OU8X7KtG5NC5U32CQMjmK7BrcTGVJ7yIpiUYEh37QCgG ATRnA0ocfIbPXn4ljSRMWj6mRoRmUGRWKiePBRG1gDH0eg9zbxwOMQ7PohybhVq3XL xlQ7Q6mRRxMHFxaOGgUWf8mcGjeiTKeyZFcfWbGw=
X-Virus-Scanned: amavisd-new at zproxy130.enst.fr
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id S6_Sw4cSD9j6 for <lp-wan@ietf.org>; Tue, 28 Jun 2022 09:52:47 +0200 (CEST)
Received: from mail-qv1-f50.google.com (mail-qv1-f50.google.com [209.85.219.50]) by zproxy130.enst.fr (Postfix) with ESMTPSA id 1DD92120320 for <lp-wan@ietf.org>; Tue, 28 Jun 2022 09:52:47 +0200 (CEST)
Received: by mail-qv1-f50.google.com with SMTP id 2so3955757qvc.0 for <lp-wan@ietf.org>; Tue, 28 Jun 2022 00:52:47 -0700 (PDT)
X-Gm-Message-State: AJIora8w4+lIuGYCNxM0Y8j14PquHwD56CJfT1e5TD7RHbyxorI0/KJX LRmgOQj0y7Qoj5e29BefYQdNav/Vc8vEtqM89bM=
X-Google-Smtp-Source: AGRyM1u6bVvUTjBWo+Rg5x0U9d/Eh3iTURYjwAd8ysGLSOMMGKb/+noNOMz91R2tvmyI4JkM9AYXb+tcTviiBWPMPSg=
X-Received: by 2002:a05:622a:1d0:b0:306:87aa:a15d with SMTP id t16-20020a05622a01d000b0030687aaa15dmr12152250qtw.161.1656402765847; Tue, 28 Jun 2022 00:52:45 -0700 (PDT)
MIME-Version: 1.0
From: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Date: Tue, 28 Jun 2022 09:52:10 +0200
X-Gmail-Original-Message-ID: <CABONVQb+OwCTsLzMtnkakHsCaGpfg03rVihgegRD3Jf0zG=LMg@mail.gmail.com>
Message-ID: <CABONVQb+OwCTsLzMtnkakHsCaGpfg03rVihgegRD3Jf0zG=LMg@mail.gmail.com>
To: lp-wan <lp-wan@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076a19b05e27d5229"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/b_IN3xHNPU3t44PSjlEGu27JM0M>
Subject: [lp-wan] Architecture
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2022 07:52:57 -0000

Dear lpwaner,

I thought we had an interim this afternoon, but the next meeting is in
Philly. I would like to discuss on the architecture and the YANG data model.

Current data model is limited to RFC 8724 and RFC8824 and can be easily
augmented for compound Ack and OAM. What is missing is how to manage the
rules. In openSCHC set of rules are assigned to a device and there is a
single core SCHC.

Carles raised the need to study a more generic approach for mesh network
where the notion of device and SCHC core do not exists anymore and rules
are more an association between a device and a core. This may be solved by
identifying the set of rules by a device ID and a core ID.

RFC 9039 (thanks to Alex for the ref) defines a way to build URN that can
be used has identifier. We can use 2 URN to identify a set of rules. But
that ASCII characters and it is not a compact representation.

So we have the current YANG data model that defines a set of rules that
will be augmented with a set of rule ID pointing both ends IDs (one of them
can be none for a star topology and both of them for PPP).

In my opinion, we should specify on the architecture document, a more
generic model covering PPP, star and mesh and also more precisely the
interaction between them. From that, we will be able to define an
augmentation of the basic data model.

The way we include a mesh model with SCHC can be an interesting thing to
investigate during the hackathon.

See you,

Laurent