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

"Acee Lindem (acee)" <acee@cisco.com> Mon, 01 April 2019 17:38 UTC

Return-Path: <acee@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 4680C120199 for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 10:38:59 -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 header.b=SD8rtH3k; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=dTreX7v0
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 b2eQPfhNVYI9 for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 10:38:56 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 961A2120187 for <netmod@ietf.org>; Mon, 1 Apr 2019 10:38:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5166; q=dns/txt; s=iport; t=1554140336; x=1555349936; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=o2b8JdIqGqbaRQcfny6W09W3hAp5M51N94SAzFtpO9Y=; b=SD8rtH3kYlLs9GTovyxJPfPQYTMU8vpOW/Gl4/kF7ocMN4+aNV1eS3vV wZfdPhUH+uIWyPtp9tcFbYnaMKdmZiGxcyK/KK4i1gGIaQWNgZC/jQxJt 0yeDlZimH/fxL5s/s2wsXd3WoJTHaONai8jbFnspY8KzK56IAgLcEkEio 4=;
IronPort-PHdr: 9a23:pQEImRwIu0M5G8LXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YRGN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A+GsHbIQKUhYEjcsMmAl1CcWIBGXwLeXhaGoxG8ERHFI=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALAADaS6Jc/5xdJa1gAxoBAQEBAQIBAQEBBwIBAQEBgVMDAQEBAQsBgT1QA2h0BAsnCoQEg0cDjzOCMiWXD4EugSQDVA4BARgLCYN6RgIXhS0iNgcNAQEDAQEJAQMCbRwMhUsBAQEDAQEhEQwBASwLAQ0CAgEIDgIIAgImAgICGQwLFRACBA4FgyIBgV0DFQEOoT8CihRxgS+CeQEBBYR/GIIMAwUFgQYkAYRdhlUXgX+BEScME4JMPoJhAQGBYRcKJoJDMYImjQOEQZMpYAkCk14alCyfDQIEAgQFAg4BAQWBVAYrgVZwFTsqAYJBggqDbjOEYYU/coEojhQBgR4BAQ
X-IronPort-AV: E=Sophos;i="5.60,297,1549929600"; d="scan'208";a="542351312"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Apr 2019 17:38:55 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x31HctPd006911 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Apr 2019 17:38:55 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 12:38:54 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 12:38:53 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 1 Apr 2019 12:38:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=o2b8JdIqGqbaRQcfny6W09W3hAp5M51N94SAzFtpO9Y=; b=dTreX7v06/MxJEH9A9TA4zeznMz0sOYXf9FTDmC7zS8/1616svdhzc/nDsjvoJ+jHoY9cW7qfG1zEbvm6OtMhyE7mFngnUncv6yS42pZaiMOzsu8m9c8Pn9VHazqtzC3HWLeCGoicoovYMIK7XoBT0en3gQXCbHfvzEiQc18xiA=
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com (10.174.112.11) by BN6PR1101MB2177.namprd11.prod.outlook.com (10.174.112.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.20; Mon, 1 Apr 2019 17:38:52 +0000
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9c05:e282:840b:51a1]) by BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9c05:e282:840b:51a1%8]) with mapi id 15.20.1750.017; Mon, 1 Apr 2019 17:38:52 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>, "kristian@spritelink.net" <kristian@spritelink.net>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] 6991bis: address-with-prefix-length
Thread-Index: AQHU6JixdGMCt4a400OFM02B5CwunKYnenSA///B7wCAAA6kAIAARM2A//+/doA=
Date: Mon, 01 Apr 2019 17:38:52 +0000
Message-ID: <4780543F-F233-4874-A5CA-266DCD9C4D70@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-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b045fc72-1a58-442e-5c99-08d6b6c8e866
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN6PR1101MB2177;
x-ms-traffictypediagnostic: BN6PR1101MB2177:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BN6PR1101MB21779E7BD6901D396DE9B2F6C2550@BN6PR1101MB2177.namprd11.prod.outlook.com>
x-forefront-prvs: 0994F5E0C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(136003)(346002)(376002)(39860400002)(199004)(189003)(54094003)(86362001)(6246003)(68736007)(36756003)(106356001)(93886005)(6436002)(316002)(6486002)(81166006)(76176011)(99286004)(486006)(8676002)(81156014)(53546011)(6506007)(102836004)(476003)(186003)(26005)(446003)(2616005)(11346002)(97736004)(66066001)(256004)(14444005)(966005)(6306002)(8936002)(33656002)(53936002)(5660300002)(25786009)(6512007)(54906003)(105586002)(305945005)(3846002)(6116002)(6916009)(229853002)(7736002)(478600001)(4326008)(2906002)(82746002)(71200400001)(14454004)(71190400001)(83716004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1101MB2177; H:BN6PR1101MB2226.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: D87JRItvUyXaoCsWMKCNLbshuxDL1Cn36Ut9ZGQ0AHPu/6h9Xgyr+gLtYb2wD3gFE4uWjCm2cISoqxNNAg5UU/KRrVDZ/Fay10JbBYLjr8feJNCthzPvByJOv/wZrz56gBY+9HK183NKay95jdOgHvHR9lz8dX0Rp0GMqwZFkrZJJYN3R/Z2xzVheZKqJxwwJUqq0HszcK+YMm6pdPHgBRepVAGsAXG25qUTOu/03wdsokKfhp29WSa26QgRwvK3jlsja3AurIqElxVk9NviHkLq44wjsVCnnhD73a2QUUsuUplg/udiOfD2dm25T3J4rawur4BS+1F+zI50b034c99VKKMGiV/6MIu5sC7zuTzH/XIiuOAhyF9xV1mLRmxR7VkNplZHibFRfwxqDpwbrCGu8caaEoGynpH57MIK5+o=
Content-Type: text/plain; charset="utf-8"
Content-ID: <114A47E215991D4289D4AC8C5E8D6AA6@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b045fc72-1a58-442e-5c99-08d6b6c8e866
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2019 17:38:52.6319 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1101MB2177
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/T5A2uugaWounAO96lQkFMMNE5Js>
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 17:38:59 -0000

On 4/1/19, 1:30 PM, "Martin Bjorklund" <mbj@tail-f.com> 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" :)

Ok - I understand now. 
    
    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.

Agreed. It seems a prefix with a prefix length of 32 for IPv4 or 128 for IPv6 would allow specification. The convenience is primarily for mapping to CLI.

Thanks,
Acee
    
    
    /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