Re: [netmod] type equivalence
Martin Björklund <mbj+ietf@4668.se> Sat, 27 February 2021 14:46 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 9A1423A08AA for <netmod@ietfa.amsl.com>; Sat, 27 Feb 2021 06:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.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, PDS_NAKED_TO_NUMERO=1.999, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=fpqPfpfF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZkFD+93H
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 AOwBAK0Ni9qc for <netmod@ietfa.amsl.com>; Sat, 27 Feb 2021 06:46:57 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8B373A08A5 for <netmod@ietf.org>; Sat, 27 Feb 2021 06:46:57 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 096575C0045; Sat, 27 Feb 2021 09:46:57 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 27 Feb 2021 09:46:57 -0500
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= oiP3uj0jlnabb8wCpwldbA+z1AF5k1xN1mSmbnHFyLk=; b=fpqPfpfFQ2vKo3zC 79J7imJWYThimhfvl7SC2K/zSllEtVdjtgRlvJOQGApeCzjWrpVelizIQ9IJ5StG C4ajJd4BWG0FBDdiHFZKMavXhbx1ebCSABRP7SHDpfNN31Bhl0xebs/BRnxtI3Xt WXncVBzL6ElQ6B6HZuGnZxmnZOMrOsi6I/KWubwpAGGSoyRVZUxYs2/RSNUWO0Dg wDvUo7c0R6YZKAuwnhGbeRGNBwupMYUsIRAUB60JRZGdj5FGfuLkHIGbI0/4BdM5 4MLkjHpQr2qlHFzX9YI6fHLTMtOV4+Pf76t1Hg9YTGP6JL8iWyQzR8byTAhl+U4v cMr9dQ==
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=oiP3uj0jlnabb8wCpwldbA+z1AF5k1xN1mSmbnHFy Lk=; b=ZkFD+93H5gvCamj78K139dJkfu/ipR8T6GXesjV4/JyFOyfw3R3QqPtG0 TIpY4lcZV0Lspk137w4iHMQ/tzoqf2K5p/uGI8NAXVJqhuHf3NuICoZyiGW+KPHy RuOyhPaVePzkOIjNVvuU9E4rOTrCuYPdpK7Aahs7Eyuk9Ri+MSOPZCWx4617bWfH bsvf747fqInO8QKtCVXq7vcRIIf+3xlH3yZweAxpMLyiPf6xL/KFghaGUDQdPXOW BGF0vKIZ+27UaM7wIU45VFsibK1FDjJQQj3XbsuJcziYmwtrBAQEEEuoK3KAJr+X j7wXKv2LC5QqLl4BnoTwe+MqtGSpQ==
X-ME-Sender: <xms:X1s6YDm1-NsDeUKQYjq22ETy_C3ilOiPMye2exV9cdqknlIotdr0mA> <xme:X1s6YG17OOLrf_qziaws9yLBoMuh44U5v2L3O_qEOL4W7rX_EvspEDG9VdpCciqVb lcTWgBl3yc7DWSFaqI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrleefgdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffkvffuhfgjfhfogggtgfesthejre dtredtvdenucfhrhhomhepofgrrhhtihhnuceujhpnrhhklhhunhguuceomhgsjhdoihgv thhfseegieeikedrshgvqeenucggtffrrghtthgvrhhnpeejteegvdeuleefudduueelge efgfevvefgveeujeehhfelgefhleeiheeffffhkeenucffohhmrghinhepihgvthhfrdho rhhgnecukfhppeduheekrddujeegrdegrddvudehnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhgsjhdoihgvthhfseegieeikedrshgv
X-ME-Proxy: <xmx:X1s6YJrTzFb-2sdS6mcBJBnBvvX3Oxv-fd64FXcXiDkbGiwvPJ3yBQ> <xmx:X1s6YLngLd4U4OcJTgd9wMBJLkTg-R4uLAUGGT_ELktevECShVM4Mw> <xmx:X1s6YB2pPqYr40lrJpydP4Ou90mOp9EHapg8tH9E8tOfxt_4P-gEaQ> <xmx:YVs6YO8JY8tU2pjjlW8Eli9_sn1LtoVJ1s8shxoDCvNff5mY83z83g>
Received: from localhost (unknown [158.174.4.215]) by mail.messagingengine.com (Postfix) with ESMTPA id C012E24005A; Sat, 27 Feb 2021 09:46:54 -0500 (EST)
Date: Sat, 27 Feb 2021 15:46:53 +0100
Message-Id: <20210227.154653.1811714010920179474.id@4668.se>
To: rwilton=40cisco.com@dmarc.ietf.org
Cc: j.schoenwaelder@jacobs-university.de, netmod@ietf.org
From: Martin Björklund <mbj+ietf@4668.se>
In-Reply-To: <MN2PR11MB4366C5CEE2EA32EEAC36B65CB59C9@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <20210226175521.rwnzxeyvub2odn6p@anna.jacobs.jacobs-university.de> <MN2PR11MB4366D67CC946AE94A4C1AF6CB59D9@MN2PR11MB4366.namprd11.prod.outlook.com> <MN2PR11MB4366C5CEE2EA32EEAC36B65CB59C9@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/NQHCVdtvZaL429hYio-QXG5T8rY>
Subject: Re: [netmod] type equivalence
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: Sat, 27 Feb 2021 14:47:00 -0000
"Rob Wilton \(rwilton\)" <rwilton=40cisco.com@dmarc.ietf.org> wrote: > Sorry, but I wish to raise another question regarding changing types. > > Are you allowed to change from one type to another type that > 'contains' the first type. > > typedef smallInt { > type int8 { range "0..100"; }; > } > > typedef biggerInt { > type int8 { range "0..200"; }; > } > > Can I change leaf foo from: > > leaf foo { > type smallInt; > } > > to: > > leaf foo { > type biggerInt; > } Yes, this was clearly the intention. We have these two rules: o A "range", "length", or "pattern" statement may expand the allowed value space. o A "type" statement may be replaced with another "type" statement that does not change the syntax or semantics of the type. For example, an inline type definition may be replaced with a typedef, but an int8 type cannot be replaced by an int16, since the syntax would change. But I assume you mean that the second bullet doesn't allow an expanded value space? /martin > > I'm not sure that the chapter 11 rules in RFC 7950 formally allow this (either with or without the proposed errata), but intuitively I would expected this to be allowed by commutativity, since this change is clearly legal if you go via a third intermediate type. > > E.g., you could change leaf foo from using smallInt to a new tempInt: > > typedef tempInt { > type int8 { range "0..100"; }; > } > > Then, as a second update, change the range in tempInt: > > typedef tempInt { > type int8 { range "0..200"; }; > } > > And in the final step change leaf foo from using tempInt to use biggerInt. > > Rob > > > > -----Original Message----- > > From: Rob Wilton (rwilton) > > Sent: 26 February 2021 19:06 > > To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> > > Cc: NetMod WG <netmod@ietf.org> > > Subject: RE: [netmod] type equivalence > > > > > > > > > -----Original Message----- > > > From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> > > > Sent: 26 February 2021 17:55 > > > To: Rob Wilton (rwilton) <rwilton@cisco.com> > > > Cc: netmod@ietf.org > > > Subject: Re: [netmod] type equivalence > > > > > > On Fri, Feb 26, 2021 at 03:27:39PM +0000, Rob Wilton (rwilton) wrote: > > > > > > > > Sure, but if we are going to submit an errata for this definition, we > > > want to ensure that updated definition is clear in all axes, not only > > the > > > specific issue that was originally raised. > > > > > > > > > > This is where the IETF shines, there is an attempt to fix a minor > > > problem and the result is N additional possible problems are put on > > > the table to be considered as well before the minor problem can be > > > fixed. My interest was the original question since I did run into it, > > > my interest is low in fixing all other possible problems that people > > > can think of. > > [RW] > > > > I'm not convinced that accurately describes the situation. > > > > If it helps to clarify, I have three specific goals here: > > > > (1) Check that the proposed corrected text doesn't contain further bugs > > that also need to be fixed. After all you cannot file an errata on an > > errata, and it doesn't look great for me if I have to request that a > > verified errata is changed to rejected because it contains further issues > > in a two sentence paragraph. > > > > (2) Workout whether the errata can be marked as verified, hold for update, > > or needs to be rejected. > > > > (3) Check that the same bug doesn't exist in other places. I agree that > > this is a tangential goal, and I have already forked this into a separate > > thread, as you had requested. > > > > I am not asking you to generically fix or define "semantics", but I really > > would like our proposed replacement text to be entirely unambiguous, and > > contain no further issues. > > > > E.g., I'm wondering, would your proposed new definition allow us to change > > from the IETF to IEEE MAC address definition? The underlying type is the > > same (String), and arguably the semantics of both types is the same (i.e., > > they both represent an IEEE 802 MAC address), but the syntax of the two > > types clearly differs. > > > > Regards, > > Rob > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod
- [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Ladislav Lhotka
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Ladislav Lhotka
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Carsten Bormann
- Re: [netmod] type equivalence tom petch
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Andy Bierman
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Andy Bierman
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Andy Bierman
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Andy Bierman
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] [SUSPECTED SPAM] Re: type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Martin Björklund
- Re: [netmod] type equivalence Rob Wilton (rwilton)
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Juergen Schoenwaelder
- Re: [netmod] type equivalence Carsten Bormann