[6lo] Re: Running 6lo on DECT-2020 NR+
Carles Gomez Montenegro <carles.gomez@upc.edu> Tue, 04 November 2025 15:16 UTC
Return-Path: <carles.gomez@upc.edu>
X-Original-To: 6lo@mail2.ietf.org
Delivered-To: 6lo@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3D04D82949E0 for <6lo@mail2.ietf.org>; Tue, 4 Nov 2025 07:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
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, 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=upc.edu
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XmS1B7_F0TNU for <6lo@mail2.ietf.org>; Tue, 4 Nov 2025 07:16:43 -0800 (PST)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8831782947B4 for <6lo@ietf.org>; Tue, 4 Nov 2025 07:15:40 -0800 (PST)
Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-b6d3effe106so890384466b.2 for <6lo@ietf.org>; Tue, 04 Nov 2025 07:15:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=upc.edu; s=google; t=1762269333; x=1762874133; darn=ietf.org; 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=NqbfVsHAA69CnMnECo7OvL2NG3okcv4mhbOkQW1+xK0=; b=A/hMt/JTMcSAIdZK1NuZmJUFXgRoXD0SYe4Re23yuVw5yyN6YzIY5HQKcEoa2jjakm aV01t1hG6HMdGqQ4ICN8V8n54G3yHtk1HXuqOYN2+RB5u3rYRs5Rv2OIKh7LVBRk4m/Q 5/xi4YSYN8sVz8qORpot0gzcnw4dfBfIWtkCunMEisLoJsBdpwR2MOMFAJY8XARlEejA SkU6LC2MCbJvXIaISELxRYon9jGKuFoD20bHhftUlNDHINGipQ6xy5O03euF+7kGaWnL Xr12gZSET5mLUX5JO31AEL1/4ae67Xb8DmsLox1+9hH/eIHyJ0EuAqr/ifAyjrECEYY/ f+NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762269333; x=1762874133; 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=NqbfVsHAA69CnMnECo7OvL2NG3okcv4mhbOkQW1+xK0=; b=VozDhlleuTNO2B25qE4JWlDTKvIXG0BHvLOaTZGOEWo2g+K0w06EIiTO+eIDAbxnBP DtDQ8Se2mPWPPjipSisRSXEjyby2tEXME2qtL00rQC1zH+dzIo7yD+4jhgZYMZBpi/G5 41IGxMGflEvQn1TxOI0jeIkJbzZMh9Jm43J0PBUyDdE8SNG0e7OJL8uOySv+7j8bbzsI v14QmhNcpiDfNptT0LU9bEJNG5+6gd2wnUO7nkWIj9jMo4ScL0B3iu+wKErPn8SSyYo3 eTjmoW2Y22ls5Jc8UZLPvdrTdVKmI3MQvn53vpWu1XyNlIE5Fe9GassQYwxcN8iejSa1 kVSg==
X-Gm-Message-State: AOJu0Yz7s/kzkX9KjR/n3EFgECiKxsB36NEwtJyoxmMnQdioMcw8L0e2 MoTz0nzuusu00EY/aKRW9LzNipB/+LrjiunBbu/bbz8dhVLDDJveZ14nzz8z2zkrCnwdi3LPBfS JTBIVGh19YOhwFGmln20hWi6OKlyygVE3VwRtgwlgp5qn9HhK54dOO6rjYg==
X-Gm-Gg: ASbGnctleD6se5ZzLny+1mnrH6WX25DYQLoo6XJ+IVg7eZIjomKN+jLErPvdR4jgPw1 rmCSx2DvxkivVLB7mhI8zUXoRuAmunto2wyvj9vnTZC44d1OXn0znmRSnwgwDC8ReS6NQ2eIomT RYR2lc366dOKF9MdQJbt/gCIs+4CH+sTpBMr6H92YbGG/JTpchDwCCHLGKQqt13HohetEQqOqxY eDN6fQrG2q+oyspxffRAi0uUOTjM1wwZ1B0NFCJbFnFESq+IWjCIECQBz7ltg==
X-Google-Smtp-Source: AGHT+IF4MwdFpn6FQUDmMxPXrHavRmgOMRuFOK1rqy8sxgbD4kaBFqlvzG5fwhBpRWIHXa5UO7Fpyyp89CX8h1kDoE4=
X-Received: by 2002:a17:906:b859:b0:b70:b077:b948 with SMTP id a640c23a62f3a-b70b077bc3emr606468766b.35.1762269333466; Tue, 04 Nov 2025 07:15:33 -0800 (PST)
MIME-Version: 1.0
References: <aQn2cAc7Cn9_DgGi@hephaistos.amsuess.com>
In-Reply-To: <aQn2cAc7Cn9_DgGi@hephaistos.amsuess.com>
From: Carles Gomez Montenegro <carles.gomez@upc.edu>
Date: Tue, 04 Nov 2025 16:15:20 +0100
X-Gm-Features: AWmQ_bnbe8A-r_BNtxfuCq67wR0kiY3BAW99oKixpqsChYUgwlNk3HfNCRw_oCQ
Message-ID: <CAAUO2xx+uk3aGNbTBGfMHz-sU56_5=NTVTg1esWcLghrZbxTWg@mail.gmail.com>
To: Christian Amsüss <christian@amsuess.com>
Content-Type: multipart/alternative; boundary="0000000000009ec8a40642c64da6"
Message-ID-Hash: NE3Y75Q3NABSKU24ZDG5KG7AVIZ5WVYQ
X-Message-ID-Hash: NE3Y75Q3NABSKU24ZDG5KG7AVIZ5WVYQ
X-MailFrom: carles.gomez@upc.edu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-6lo.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 6lo@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: carles.gomez@upc.edu
Subject: [6lo] Re: Running 6lo on DECT-2020 NR+
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/4uers7WFMNfVX3EFkoJrY6mwxY8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Owner: <mailto:6lo-owner@ietf.org>
List-Post: <mailto:6lo@ietf.org>
List-Subscribe: <mailto:6lo-join@ietf.org>
List-Unsubscribe: <mailto:6lo-leave@ietf.org>
Hello Christian, Many thanks for bringing the topic to the 6lo mailing list! I am personally not aware of documents or efforts to fill the gaps that you mentioned. It would be great if anyone aware of such efforts (if any) could provide any details. Cheers, Carles <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre de virus.www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, 4 Nov 2025 at 13:50, Christian Amsüss <christian@amsuess.com> wrote: > Hello 6lo group, > > since RFC8105 has been published, ETSI has completed a new iteration of > the DECT standard, markeded as DECT-2020 NR+, technically ETSI TS > 103-636-1 and -v5 (those are the IP-relevant ones), which unlike the ULE > used in 8105 merely coexists with (and is not part of the same stack as) > the classical DECT service. > > Their codepoint allocations reserve an "endpoint value" (multiplex point > for different protocols) fo 0x8003 for compressed IPv6 datagrams > following RFC6282, but no document for details -- for example, RFC8105 > talked about how their 40- and 20-bit addresses could or could not be > used, and what level of assembly is expected from the DECT layers. For > comparison, DECT-2020 uses long 32-bit and short 16-bit addresses (now > random), and hop-by-hop retransmission and fragmentation/reassembly. > > While I think that some choices in how to actually do 6lo over DECT-2020 > have obvious deductions from RFC8105, some (such as address > reconstruction or considerations for the DECT mesh) could need explicit > spelling-out. > > Do you known of any public or WIP documents or efforts to fill those > gaps? > > Best regards > Christian > > [1]: > https://portal.etsi.org/PNNS/Protocol-Specification-Allocation/DECT-2020-NR-Endpoint-Multiplexing-Addresses > > -- > To use raw power is to make yourself infinitely vulnerable to greater > powers. > -- Bene Gesserit axiom > _______________________________________________ > 6lo mailing list -- 6lo@ietf.org > To unsubscribe send an email to 6lo-leave@ietf.org >
- [6lo] Running 6lo on DECT-2020 NR+ Christian Amsüss
- [6lo] Re: Running 6lo on DECT-2020 NR+ Carles Gomez Montenegro