Re: [netmod] 6991bis: address-with-prefix-length

Kristian Larsson <> Mon, 01 April 2019 20:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A99E8120161 for <>; Mon, 1 Apr 2019 13:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OW5QG_2Ys4Bc for <>; Mon, 1 Apr 2019 13:08:51 -0700 (PDT)
Received: from Mail1.SpriteLink.NET ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 631291200CC for <>; Mon, 1 Apr 2019 13:08:51 -0700 (PDT)
Received: from mbp.local ( []) by Mail1.SpriteLink.NET (Postfix) with ESMTPSA id A357F3FA32 for <>; Mon, 1 Apr 2019 22:08:47 +0200 (CEST)
References: <> <> <> <> <>
From: Kristian Larsson <>
Message-ID: <>
Date: Mon, 1 Apr 2019 22:08:47 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [netmod] 6991bis: address-with-prefix-length
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 01 Apr 2019 20:08:53 -0000

Hello Mahesh,

On 2019-04-01 21:40, Mahesh Jethanandani wrote:
>> On Apr 1, 2019, at 10:29 AM, Martin Bjorklund <> wrote:
>> 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.
> Agree. The combination makes sense for CLI, but for modeling the address and prefix should be separate.

Okay, then why do we have an ip-prefix data type at all? With the same 
line of argument you apply, it should be split up.

So you're the third person bringing up CLI. I don't get this at all. I 
don't see how CLI are different from everything else. This is about data 
modeling and data modeling is about expressing the world in a data 
modeling language. It's like painting a picture but instead of a brush 
you have a schema language like YANG. What do you see? Express it. It 
doesn't matter if the purpose is a CLI, a web page or just exposing it 
via NETCONF for another system to consume.

I think address-and-prefix-length is natural. JUNOS uses this format. XR 
uses this format (for IPv6 at least). Nokia SROS uses this format.

We have written a bunch of models where the lack of this IMHO makes them 
less elegant. I'd like for there to be an IETF standard data type to 
make those models more elegant.

Kind regards,