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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 02 April 2019 15:37 UTC

Return-Path: <rwilton@cisco.com>
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 63FC0120155 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 08:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 hpJNw49Hdhya for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 08:37:11 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA58E120110 for <netmod@ietf.org>; Tue, 2 Apr 2019 08:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4832; q=dns/txt; s=iport; t=1554219430; x=1555429030; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=PQS4pL4WvuQXFaLKJQc4OtLer01ku/e+YQo7aLsQyMw=; b=hAcLpXQVpPQXBJAHNPHSJDlzskx9Hx/rx4YS4YsrtfuARSb+W56f+Sq7 G/2X71lFmKMAPe7FGEyVWZZDxXfUEotjSIn3y6tD+X2Z4ynH2bOES3FEQ DbwY04Y2nNqLbtSQllP7MPe3iBFCyN7Q+KF8HgCEkL0iBD1OQdaoM+fzP s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAAD6gKNc/4gNJK1iAxkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgVIDAQEBAQELAYIQaIEDJwqZXYk4jweBew4BARgLhAN?= =?us-ascii?q?GAoU8IjUIDQEBAwEBCQEDAm0cDIVKAQEBAQIBAQE4NAsMAgICAQgOAgEEAQE?= =?us-ascii?q?BHhAbBgYLHQgCBAENBQiDG4FdAw0ID69QiAgNghoFBYEqAYRdhlUXgUA/gRG?= =?us-ascii?q?DEj6CGkcBAYICJoUaA4pNhniTWTYJAow4g22DOSKUOItGh1WMBwIRFYEuIQM?= =?us-ascii?q?zgVZwFTuCbIYrhGGFP0ExjzqBHwEB?=
X-IronPort-AV: E=Sophos;i="5.60,301,1549929600"; d="scan'208";a="256570759"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Apr 2019 15:37:09 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x32Fb9JL022567 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Apr 2019 15:37:09 GMT
Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Apr 2019 10:37:08 -0500
Received: from xch-rcd-007.cisco.com ([173.37.102.17]) by XCH-RCD-007.cisco.com ([173.37.102.17]) with mapi id 15.00.1473.003; Tue, 2 Apr 2019 10:37:08 -0500
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] 6991bis: address-with-prefix-length
Thread-Index: AQHU6JiheSPJmEQr00OIJbt8HN1cWaYpHj4AgAAIngD//9pa0A==
Date: Tue, 2 Apr 2019 15:37:08 +0000
Message-ID: <ebdf44cb1f47475fb44a51e01c9a809e@XCH-RCD-007.cisco.com>
References: <7d368608-7c73-4287-bfa3-69a8db8576a2@Spark> <082d01d4e944$aae0e3a0$4001a8c0@gateway.2wire.net> <20190402121550.7da6lxd6n5qiphsd@anna.jacobs.jacobs-university.de> <20190402.144640.408659609107514722.mbj@tail-f.com>
In-Reply-To: <20190402.144640.408659609107514722.mbj@tail-f.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.63.23.177]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Tf27WLh16EauG2891TaGKdk1wC8>
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: Tue, 02 Apr 2019 15:37:14 -0000


> -----Original Message-----
> From: netmod <netmod-bounces@ietf.org>; On Behalf Of Martin Bjorklund
> Sent: 02 April 2019 13:47
> To: j.schoenwaelder@jacobs-university.de
> Cc: netmod@ietf.org
> Subject: Re: [netmod] 6991bis: address-with-prefix-length
> 
> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>; wrote:
> > If you go back ~20 messages, my proposal was ip-address-prefix,
> > ipv4-address-prefix, and ipv6-address-prefix.
> 
> Do we agree that this type really specifies two values in one?  If so I think the
> "and" is useful.

Isn't an "IP prefix" made up of an "IP address" and a "prefix length"?

So, I think that the names above are probably right, or otherwise if you want the "and" then perhaps it should be "ip-address-and-prefix-length" - which seems clunky?

Thanks,
Rob


> 
> Also note that the current text in RFC 6991 says:
> 
>      The ipv4-prefix type represents an IPv4 address prefix.
> 
> so having a type ipv4-address-prefix for something that is not (only) an
> "ipv4 address prefix" is imo confusing.
> 
> 
> /martin
> 
> 
> 
> 
> >
> > /js
> >
> > On Tue, Apr 02, 2019 at 11:13:09AM +0000, tom petch wrote:
> > > ----- Original Message -----
> > > From: "Jeff Tantsura" <jefftant.ietf@gmail.com>;
> > > To: <netmod@ietf.org>;; "Kristian Larsson" <kristian@spritelink.net>;
> > > Sent: Monday, April 01, 2019 11:09 PM
> > >
> > > What Kristian has proposed makes sense, in favor.
> > >
> > > <tp>
> > >
> > > Yes, I support this idea and we should be able to come up with a
> > > more user-friendly name;  address-prefix or address-length ?
> > >
> > > Tom Petch
> > >
> > > p.s.
> > >
> > >    identifier          = (ALPHA / "_")
> > >                          *(ALPHA / DIGIT / "_" / "-" / ".")
> > >
> > > Cheers,
> > > Jeff
> > > On Apr 1, 2019, 1:09 PM -0700, Kristian Larsson
> > > <kristian@spritelink.net>;, wrote:
> > > > Hello Mahesh,
> > > >
> > > > On 2019-04-01 21:40, Mahesh Jethanandani wrote:
> > > > >
> > > > > > On Apr 1, 2019, at 10:29 AM, Martin Bjorklund <mbj@tail-f.com>;
> > > 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,
> > > > Kristian.
> > > >
> > > > _______________________________________________
> > > > 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
> > > >
> > >
> > > _______________________________________________
> > > 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