Kristian Larsson <kristian@spritelink.net> Tue, 02 April 2019 12:28 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3E9F120187 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:28:26 -0700 (PDT)
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 YgQW3bd0ipY6 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:28:23 -0700 (PDT)
Received: from Mail1.SpriteLink.NET (Mail1.spritelink.net [195.182.5.127]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17281204D2 for <netmod@ietf.org>; Tue, 2 Apr 2019 05:28:23 -0700 (PDT)
Received: from mbp.local (c-bb9de253.014-82-73746f13.bbcust.telenor.se [83.226.157.187]) by Mail1.SpriteLink.NET (Postfix) with ESMTPSA id 16C0D3F482 for <netmod@ietf.org>; Tue, 2 Apr 2019 14:28:16 +0200 (CEST)
References: <20190401161321.seiodlfsmjjvjcp5@anna.jacobs.jacobs-university.de> <F1537180-6BF3-40C7-BCFA-3AAE0290AE9D@cisco.com> <A0F7987F-AA67-4A63-8FEE-3B74B5B47CF1@cisco.com> <20190401.192951.1060904547331848297.mbj@tail-f.com> <e00461e683244644b3401e0d433446c4@XCH-RCD-007.cisco.com>
Message-ID: <c20432c2-852b-6b5e-2a74-fd5504ac97ca@spritelink.net>
Date: Tue, 2 Apr 2019 14:28:15 +0200
In-Reply-To: <e00461e683244644b3401e0d433446c4@XCH-RCD-007.cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/gshnDp2U2JE1t_HG1hMtmMf62YI>
X-List-Received-Date: Tue, 02 Apr 2019 12:28:27 -0000
On 2019-04-02 14:17, Rob Wilton (rwilton) wrote:
>> From: netmod <netmod-bounces@ietf.org>; On Behalf Of Martin Bjorklund
>> Sent: 01 April 2019 18:30
>> To: Acee Lindem (acee) <acee@cisco.com>;
>> Subject: Re: [netmod] 6991bis: address-with-prefix-length
>> The request was for a combined type that contains both an ip address
>> *and* a prefix length in one value.  Hence the name "ip-address-and-prefix-
>> length" :)
>> I know that this type is convenient, esp. if you use it for manual input, but I
>> wonder if it really is good practice to squeeze two values into one.
> Perhaps allowing YANG to support a tuple type would be an elegant solution.  I.e. the value exists on a single path, and has to be atomically updated, but the value can still be composed from different types.
I think that would be a great addition to YANG. I've had numerous
discussions over the awkardness of using a grouping to group multiple
leaves together when you really want to define some form of compound /
However, that is a longer term project and IMHO not something that
should stop adding a ip-address-and-prefix-length type to 6991bis today :)
Kristian Larsson <kristian@spritelink.net> Tue, 02 April 2019 12:28 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3E9F120187 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:28:26 -0700 (PDT)
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 YgQW3bd0ipY6 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:28:23 -0700 (PDT)
Received: from Mail1.SpriteLink.NET (Mail1.spritelink.net [195.182.5.127]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17281204D2 for <netmod@ietf.org>; Tue, 2 Apr 2019 05:28:23 -0700 (PDT)
Received: from mbp.local (c-bb9de253.014-82-73746f13.bbcust.telenor.se [83.226.157.187]) by Mail1.SpriteLink.NET (Postfix) with ESMTPSA id 16C0D3F482 for <netmod@ietf.org>; Tue, 2 Apr 2019 14:28:16 +0200 (CEST)
References: <20190401161321.seiodlfsmjjvjcp5@anna.jacobs.jacobs-university.de> <F1537180-6BF3-40C7-BCFA-3AAE0290AE9D@cisco.com> <A0F7987F-AA67-4A63-8FEE-3B74B5B47CF1@cisco.com> <20190401.192951.1060904547331848297.mbj@tail-f.com> <e00461e683244644b3401e0d433446c4@XCH-RCD-007.cisco.com>
Message-ID: <c20432c2-852b-6b5e-2a74-fd5504ac97ca@spritelink.net>
Date: Tue, 2 Apr 2019 14:28:15 +0200
In-Re
ply-To: <e00461e683244644b3401e0d433446c4@XCH-RCD-007.cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/gshnDp2U2JE1t_HG1hMtmMf62YI>
X-List-Received-Date: Tue, 02 Apr 2019 12:28:27 -0000
On 2019-04-02 14:17, Rob Wilton (rwilton) wrote:
>> From: netmod <netmod-bounces@ietf.org>; On Behalf Of Martin Bjorklund
>> Sent: 01 April 2019 18:30
>> To: Acee Lindem (acee) <acee@cisco.com>;
>> Subject: Re: [netmod] 6991bis: address-with-prefix-length
>> The request was for a combined type that contains both an ip address
>> *and* a prefix length in one value.  Hence the name "ip-address-and-prefix-
>> length" :)
>> I know that this type is convenient, esp. if you use it for manual input, but I
>> wonder if it really is good practice to squeeze two values into one.
> Perhaps allowing YANG to support a tuple type would be an elegant solution.  I.e. the value exists on a single path, and has to be atomically updated, but the value can still be composed from different types.
I think that would be a great addition to YANG. I've had numerous
discussions over the awkardness of using a grouping to group multiple
leaves together when you really want to define some form of compound /
However, that is a longer term project and IMHO not something that
should stop adding a ip-address-and-prefix-length type to 6991bis today :)