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

Kristian Larsson <kristian@spritelink.net> Mon, 01 April 2019 19:38 UTC

Return-Path: <kristian@spritelink.net>
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 9373C120511 for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 12:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6lxtQXro0Ty2 for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 12:38:00 -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 C99E2120506 for <netmod@ietf.org>; Mon, 1 Apr 2019 12:37:59 -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 64BDE3F439; Mon, 1 Apr 2019 21:37:55 +0200 (CEST)
To: Martin Bjorklund <mbj@tail-f.com>, acee@cisco.com
Cc: j.schoenwaelder@jacobs-university.de, netmod@ietf.org
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>
From: Kristian Larsson <kristian@spritelink.net>
Message-ID: <af1cadb6-a4da-1504-698a-fa8aec463eb8@spritelink.net>
Date: Mon, 1 Apr 2019 21:37:55 +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: <20190401.192951.1060904547331848297.mbj@tail-f.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/2nsj-L5ZIRhySl_O5PFmO3VBqI4>
Subject: Re: [netmod] 6991bis: address-with-prefix-length
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: Mon, 01 Apr 2019 19:38:10 -0000


On 2019-04-01 19:29, Martin Bjorklund wrote:
> Hi,
> 
> 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" :)

Right you are, though I'm open to other names but let's first agree on 
use case / need :)


> 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.

Dunno how "manual" has any bearing. This is IMHO just about natural data 
modeling.

You say it's two values but when one can't be used without the other, 
are they so separated? You can't configure an interface with just an 
address or just a subnet mask. You need both - they belong together.

Similarly, in a routing table you have prefixes, which consist of an 
address and a length - it got its own data type yet you could apply your 
argument to it and say they should be separated. It's just that *that* 
data type forbids bits to be set in the mask portion of the address, 
which is correct for the routing table use case, but means it can't be 
used to describe an interface address and mask.

    kll




> 
> 
> /martin
> 
> 
> "Acee Lindem (acee)" <acee@cisco.com> wrote:
>> Ok, now I'm confused. I see that the ietf-inet-type model already has the types ipv4-prefix and ipv6-prefix. How are these any different???
>> Thanks,
>> Acee
>>
>> ´╗┐On 4/1/19, 12:31 PM, "Acee Lindem (acee)" <acee@cisco.com> wrote:
>>
>>      I believe the "address-" could be omitted from the type identifiers. At least within the routing area, "ipv4-prefix" is unambiguous.
>>      Thanks,
>>      Acee
>>      
>>      On 4/1/19, 12:14 PM, "netmod on behalf of Juergen Schoenwaelder" <netmod-bounces@ietf.org on behalf of j.schoenwaelder@jacobs-university.de> wrote:
>>      
>>          This is the right time for this and I would call these
>>          ip-address-prefix, ipv4-address-prefix and ipv6-address
>>          prefix.
>>          
>>          /js
>>          
>>          On Mon, Apr 01, 2019 at 04:38:34PM +0200, Kristian Larsson wrote:
>>          > Hello,
>>          >
>>          > seeing that 6991 is up for a refresh I wonder if this would be the time to
>>          > suggest the addition of a type for address-and-prefix-length, for example
>>          > like 192.0.2.1/24?
>>          >
>>          > I find that it's the most natural way express the address and prefix-length
>>          > to configure on an interface or for some other use. We currently have an
>>          > ip-prefix type which allows CIDR style prefixes but since all bits to the
>>          > right of the mask is to be 0 it is only possible to use for describing the
>>          > IP prefix / network address itself - not the address of a host in that
>>          > network.
>>          >
>>          > I actually wish the interface-ip modules would have used a combined leaf for
>>          > these settings rather than the dual-leaf approach it currently has, but I
>>          > suppose that ship has sailed :/
>>          >
>>          > Regardless, can we add such a type? Is this the document and time to do it?
>>          > :)
>>          >
>>          > Kind regard,
>>          >    Kristian.
>>          >
>>          > _______________________________________________
>>          > netmod mailing list
>>          > netmod@ietf.org
>>          > https://www.ietf.org/mailman/listinfo/netmod
>>          
>>          --
>>          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