Return-Path: X-Original-To: core@mail2.ietf.org Delivered-To: core@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 632C910378C1D for ; Thu, 18 Jun 2026 08:45:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781797532; bh=/9ZNIT/NoFa+C/Z+jfJCz11XcyKHTtv7xw5q+F42eHE=; h=Date:Subject:To:References:Cc:From:In-Reply-To; b=vxJNmyoHM2f/Mgd1Dy+GaJ1tY2U2v4wEhWhRfouzD1GsqIfE/piIMqMEEEGrbk9QC PYgloN/QMiX6eUqt3oEns2D9GxeSILmLxnER5BdZADpEGSXQjl9/KV6KaDbDgAY/eT clF4oJYGb4eckDo5tQbX8f+SRcD0GOMNMXiK9JTU= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -7.101 X-Spam-Level: X-Spam-Status: No, score=-7.101 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz 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 CJ--aOYOb5CI for ; Thu, 18 Jun 2026 08:45:30 -0700 (PDT) Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0AF4A1037883F for ; Thu, 18 Jun 2026 08:43:31 -0700 (PDT) Received: from [IPV6:2001:1488:fffe:6:5d7c:2a8:ce48:e9d8] (unknown [IPv6:2001:1488:fffe:6:5d7c:2a8:ce48:e9d8]) by mail.nic.cz (Postfix) with ESMTPSA id 246471C13B2; Thu, 18 Jun 2026 17:43:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1781797411; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hGjnXfVuE6v8VhZ3sjKsL/8qmZy7fMjnMyDGxkEcH/U=; b=vbXekmcgA/S5Vuw4X2Lm08vYI4LTxIb1WtBNR1k+ynCgjVtercRD2kK+8HlTifPPCVS84R b4A30Ms39ShSr0Bq1CCuBewKiIiJycB7YCm9H0Rj61smVbEb68F8Ozth9SSIZOCCm5su8j GgX+/+z+DtRRkkAxATDVrRbjcpt8sCg= Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vojtech.vilimek@nic.cz smtp.mailfrom=vojtech.vilimek@nic.cz Message-ID: <0c1d576d-7954-4eb4-980c-784d17551599@nic.cz> Date: Thu, 18 Jun 2026 17:43:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Laurent Toutain References: <6c2d619c-8299-4de1-8abc-9f5eaab86a1b@nic.cz> Content-Language: en-US From: Vojtech Vilimek In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Server: mail X-Rspamd-Queue-Id: 246471C13B2 X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP X-Rspamd-Action: no action X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[text/plain]; FUZZY_RATELIMITED(0.00)[rspamd.com]; ARC_NA(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]; WHITELISTED_IP(0.00)[2001:1488:fffe:6:5d7c:2a8:ce48:e9d8]; FROM_HAS_DN(0.00)[]; LOCAL_OUTBOUND(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+] Message-ID-Hash: KNQPYHTPSHGY23GAPVMIPTAIZREZ34BX X-Message-ID-Hash: KNQPYHTPSHGY23GAPVMIPTAIZREZ34BX X-MailFrom: vojtech.vilimek@nic.cz X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: core X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bcore=5D_Re=3A_CoRE_WG_Interim=3A_Private_SIDs?= List-Id: "Constrained RESTful Environments (CoRE) Working Group list" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hi Laurent, On 6/18/26 4:44 PM, Laurent Toutain wrote: > Ok, it may be to strict, in my opinion we can at least RECOMMAND not to > process private SIDs, they  SHOULD only be used for transmission. > I like this formulation much more. > > Section 3. Processing and Interoperability: >  >  If a YANG Data Model has not been configured for private SID >  >  translation, its SIDs are transmitted as-is, using their official >  >  values.  Translation is therefore purely opt-in per model: ... > > How should the YANG Data Model configuration look like? > > > it is not the YANG data model, I wanted to say that a SID not covered by > translation are not modified. > The term Data Model as defined in RFC 7950, Terminology: | o data model: A data model describes how data is represented and | accessed. So the term covers all YANG Modules implemented by a server. > > Other SDOs will have a mega-range with a CBOR representation on 5 bytes. > Term mega-range is used by RFC 9595, the SDOs holding PEN numbers will only receive smaller "normal" range only. For receiving a Mega-range, a special process is established. RFC 9595: | 6.3. New IANA Registry: YANG-SID Mega-Ranges | | The name of this registry is "YANG-SID Mega-Ranges". This registry | is used to record the delegation of the management of a block of SIDs | to a third party (such as Standards Development Organizations (SDOs) | or registrars). | ... I asked because the IANA YANG SID registry, Mega-Ranges subregistry does not list any of the mentioned parties. > That's a very interesting way to compress the identityref value, but it > works well only if the SIDs come from the same range. Exactly, great observation. Have a nice day! Best regards, Vojtech Vilimek CZ.NIC z. s. p. o.