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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 02 April 2019 12:17 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 77BE21201E7 for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:17:17 -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_HIGH=-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 V4dcdOb_-WCo for <netmod@ietfa.amsl.com>; Tue, 2 Apr 2019 05:17:15 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30AD512015D for <netmod@ietf.org>; Tue, 2 Apr 2019 05:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5382; q=dns/txt; s=iport; t=1554207435; x=1555417035; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WbDzGG13SHvu3QmYshMf8wfiJ+F4K8lhwyQJ5xYbDAs=; b=HywoXB/HJXuH3HDVtzo+M4qucWW8m5CI7aWucyRxfpVH/D7vC9xGTJe1 JwAidkTpQgWDclmqy1PpP2Q0EEDnNxv4KRP3VP7wav6iKSt5bE5+6Tfw3 TBJhQHIjIM4bRwTsvDnBnCs7WxrVDkoI8FsAWn3jrF0wR5nK9+qANICDo Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BCAADCUaNc/5xdJa1iAxkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgWWCEWiBAycKhASVVZo6DgEBGAuEA0YCF4UlIjgSAQE?= =?us-ascii?q?DAQEJAQMCbRwMhUoBAQEBAwEBIRE6CwwCAgIBCA4CAQQBAQECAiYCAgIZDAs?= =?us-ascii?q?VCAgCBAENBQgTgwiBdQ+tQYEvij0FgQYkhF6GVReBQD+BEYMSPoJhAQGBeAo?= =?us-ascii?q?mgkOCVwONAoRDlA8JAodyi2wigmCRWItGk1wCERWBLjYhgVZwFTuCbAmGIoR?= =?us-ascii?q?hhT9BMY86gR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.60,300,1549929600"; d="scan'208";a="538944997"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Apr 2019 12:17:13 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x32CHDN6016847 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Apr 2019 12:17:13 GMT
Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Apr 2019 07:17:12 -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 07:17:12 -0500
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "Acee Lindem (acee)" <acee@cisco.com>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] 6991bis: address-with-prefix-length
Thread-Index: AQHU6JiheSPJmEQr00OIJbt8HN1cWaYnzkaAgAAE/QCAAA6lgIAAAb6AgAC1e6A=
Date: Tue, 2 Apr 2019 12:17:12 +0000
Message-ID: <e00461e683244644b3401e0d433446c4@XCH-RCD-007.cisco.com>
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>
In-Reply-To: <20190401.192951.1060904547331848297.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/snNEeJPXVaDLSAm2acqP8po8BFQ>
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 12:17:18 -0000

> -----Original Message-----
> From: netmod <netmod-bounces@ietf.org> On Behalf Of Martin Bjorklund
> Sent: 01 April 2019 18:30
> To: Acee Lindem (acee) <acee@cisco.com>
> Cc: netmod@ietf.org
> Subject: Re: [netmod] 6991bis: address-with-prefix-length
> 
> 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" :)
> 
> 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.

Thanks,
Rob


> 
> 
> /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
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod