Re: [netmod] "uint24" in rfc6991-bis?

Martin Björklund <mbj+ietf@4668.se> Thu, 23 April 2020 09:57 UTC

Return-Path: <mbj+ietf@4668.se>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A02953A180E for <netmod@ietfa.amsl.com>; Thu, 23 Apr 2020 02:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.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, PDS_NAKED_TO_NUMERO=1.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=v/jn9oeU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TEENGNNl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXu5gcRUVntK for <netmod@ietfa.amsl.com>; Thu, 23 Apr 2020 02:57:20 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48F2B3A180D for <netmod@ietf.org>; Thu, 23 Apr 2020 02:57:20 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 5A921736; Thu, 23 Apr 2020 05:57:19 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 23 Apr 2020 05:57:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=date :message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= eX2H2dorWHY8S/6mJ95o+KhlVLFD7Jv9vHVxgaJlvO0=; b=v/jn9oeUDZUc4bkH bejfqY2Zz1Ohri+i4BphgAtbmiPs9FOIDAZI2MXbjIqqO7e1tKyG+pObTTSjp6o9 GQBu7l00mOiEX27nL1RxRs3Z3fMe5c8eI2tqibJDFouOITKKakaj9so552EC/Njk +wbKvlg49T3HzMel4Htvzkv9ABxYQCEJkMVlGHmAC0jBoVJuRX7qVOp9ilWvkqvX +tAuuNacLtku6bKW0FhhzNURur2ux1yoNX9INtdvU+4T4VMkwSWGquMz0i/Gmhn9 Hr/8JYSFDi7AxPV0PIcpyM3JN+v22lQPZC2MzAaX7Wfj0mlrkzJlJeIEkwZLWnEk 8MK0ww==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=eX2H2dorWHY8S/6mJ95o+KhlVLFD7Jv9vHVxgaJlv O0=; b=TEENGNNloM5uKR+tscxT80f/d0jX2+uE8AimxYxg1SCOO7KYuKrhXmeDT F3f2JN0C+Br0rquKW+w5NW6LZamp5JOBz0j8hHRoAbUZfe3wXltyKgTlEDqihqnk /6I+BgdplkY948Y6Dq2hvfo5oCx1IaU+/Lv8Pg/wVsTonWilNKrTrKptVkEVlojS ShmPPyJVEcYpaYa8EMI8thhy4+7efFXdrQ0irDZ/4orjZFlu9tVCSYedHxS+I8/6 s5DwUYQVKVi5xB1qvP1otH2Gs5n/l79PmKtlPLdbq8T+Ima8AxzziqlFe03I2XxT Pryogle2+BGBRUV6BI9lFSJcAXaPw==
X-ME-Sender: <xms:fmahXsIyR8IBsdNxeqz_ZFJsg-USuw2RbfgZ4duiOI6FxrmY3QMFgw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeelgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffkvffuhfgjfhfogggtgfesthejre dtredtvdenucfhrhhomhepofgrrhhtihhnuceujhpnrhhklhhunhguuceomhgsjhdoihgv thhfseegieeikedrshgvqeenucffohhmrghinhepihgvthhfrdhorhhgpdhjrggtohgssh dquhhnihhvvghrshhithihrdguvgenucfkphepudehkedrudejgedrgedrgeegnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgsjhdoihgvth hfseegieeikedrshgv
X-ME-Proxy: <xmx:fmahXnEH80XqbxRWLo7jHoCi1-TrP9DiroZdaAlkBmA2jOk08JTDwA> <xmx:fmahXrsnXgmyBcR3M3IAucMY_uld_bKker17no_qkEaMDMa_-UdbdQ> <xmx:fmahXuvw-l1qIUMorUcHk0Lg1VqE1K-0ppiyDKmrEWRz0JtBxSYMxg> <xmx:fmahXpc97N3HQmF-f7vZGAazh10263yiGbg6MT9tYiREhDMoHvb5CQ>
Received: from localhost (unknown [158.174.4.44]) by mail.messagingengine.com (Postfix) with ESMTPA id 8C7A33065D23; Thu, 23 Apr 2020 05:57:17 -0400 (EDT)
Date: Thu, 23 Apr 2020 11:57:15 +0200
Message-Id: <20200423.115715.467694125357149481.id@4668.se>
To: rwilton=40cisco.com@dmarc.ietf.org
Cc: j.schoenwaelder@jacobs-university.de, nite@hq.sk, netmod@ietf.org
From: Martin Björklund <mbj+ietf@4668.se>
In-Reply-To: <MN2PR11MB4366B7889896668A4A92CEBBB5D30@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <a185a706-235e-a780-1cdd-147ac33a4e40@hq.sk> <20200422220855.jlpgobh2ixloaheq@anna.jacobs.jacobs-university.de> <MN2PR11MB4366B7889896668A4A92CEBBB5D30@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/HO_9Fp6iDhNVoSU_4r9y6HT3Qs4>
Subject: Re: [netmod] "uint24" in rfc6991-bis?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 09:57:22 -0000

"Rob Wilton \(rwilton\)" <rwilton=40cisco.com@dmarc.ietf.org> wrote:
> [As an individual contributor]
> 
> > -----Original Message-----
> > From: netmod <netmod-bounces@ietf.org> On Behalf Of Juergen
> > Schoenwaelder
> > Sent: 22 April 2020 23:09
> > To: Robert Varga <nite@hq.sk>
> > Cc: netmod@ietf.org
> > Subject: Re: [netmod] "uint24" in rfc6991-bis?
> > 
> > On Wed, Apr 22, 2020 at 11:17:26PM +0200, Robert Varga wrote:
> > > Hello,
> > >
> > > a number of IETF protocols-and-whatnots are operating on unsigned
> > > 24bit (or 3-octet) entities. For example:
> > >
> > > https://tools.ietf.org/html/rfc7471#section-4.1.5
> > > https://tools.ietf.org/html/rfc7471#section-4.4.5
> > > SRGB range start/length in https://tools.ietf.org/html/rfc8669
> > 
> > For these use cases, it might be also a good idea to define types that
> > capture the additional semantics. SRGB seems to consist of two 24-bit
> > values - I can't tell whether it makes sense to model this 6-octet
> > value
> > as two 3-octet values in YANG.
> > 
> > > I wonder whether it would make sense to provide something like:
> > >
> > > type uint24 {
> > >    type uint32;
> > >    range 0..16777215;
> > > }
> > >
> > > in ietf-inet-types as a common base type for such definitions.
> > 
> > If we add such a definition, it likely should go into ietf-yang-types.
> [RW] 
> 
> I would find this type somewhat confusing in the sense that it mixing
> the underlying YANG datatype with the range of the value space,

I agree.

> e.g., I don't think of uint8 as
> type uint8 {
>    type uint32;
>    range 0..255;
> }
> 
> because the encoding is allowed to be different.  Perhaps having a
> slightly different name would help avoid possible confusion with the
> built in types?

Then the question is if it really is so common so that we need a type
in ietf-yang-types for this.


/martin


> 
> Regards,
> Rob
> 
> 
> > 
> > /js
> > 
> > --
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> > Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
> > 
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod