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

"Acee Lindem (acee)" <acee@cisco.com> Mon, 01 April 2019 20:29 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 56DBA1200CE for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 13:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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=VEwzPmGG; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=k5U/O6XG
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 SLGlBi6iUcJJ for <netmod@ietfa.amsl.com>; Mon, 1 Apr 2019 13:29:19 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A36712001B for <netmod@ietf.org>; Mon, 1 Apr 2019 13:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7888; q=dns/txt; s=iport; t=1554150559; x=1555360159; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rfdOZI20F/vQrhHSWjaX/+R+oOXIOmwrt2cf1CBwTv4=; b=VEwzPmGGy0uodGWQDj+d/HweinImF8B4RQ8tpmhBRSbbPjFcGhNQKT1M v0tv/Elh4mqItcNfNkX8oRh5VJZ4U823T4FIf/PeK21X2WXqKYeN3DaZf Mk6aJPTnJZxt+A4hphNS/91rj0CGZhZuwY1rf/Nz6xYVPkl0i480Z0Two w=;
IronPort-PHdr: =?us-ascii?q?9a23=3A9Lk5rxLP60L5uKMcvNmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeCuKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuMAkD2BPXrdCc9Ws9FUQwt8g=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAAAzdKJc/5BdJa1hAxkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgVIDAQEBAQELAYE9UANodAQLJwqEBINHA48zgleXD4E?= =?us-ascii?q?ugSQDVA4BARgLCYN6RgIXhS0iNQgNAQEDAQEJAQMCbRwMhUoBAQEBAgEBASE?= =?us-ascii?q?RDAEBLAsBDQICAQgQCAICJgICAhkMCxUQAgQBDQWDIgGBXQMNCAEOoyECihR?= =?us-ascii?q?xgS+CeQEBBYUCGIIMAwUFgQYkAYRdhlUXgX+BEScfgkw+gmEBAYFhFwomgkM?= =?us-ascii?q?xgiaNA4RBkylgCQKMMocsGpQsiz+TTgIEAgQFAg4BAQWBTwMzgVZwFTsqAYJ?= =?us-ascii?q?BggqDbjOEYYU/coEojhQBgR4BAQ?=
X-IronPort-AV: E=Sophos;i="5.60,297,1549929600"; d="scan'208";a="252881974"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Apr 2019 20:29:17 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x31KTHXh002676 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Apr 2019 20:29:17 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 15:29:16 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 15:29:16 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 1 Apr 2019 16:29:16 -0400
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=rfdOZI20F/vQrhHSWjaX/+R+oOXIOmwrt2cf1CBwTv4=; b=k5U/O6XGtD4RoLxoq4Cvvu2R4s/ZFu3IgrlvV/y2y9Cn5FYRDrB2m9qxdKhxwfy+4tDJrEPW0Pjsgo5QZ6+ciMIK3jOcLybTSPo4Lm9/EYWGczzHkW+0UDQty7XPWBdP/U5bDDcUHjHpGf/q1lFGIAf5kV4pHQTuVOUuJG+jpmk=
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com (10.174.112.11) by BN6PR1101MB2355.namprd11.prod.outlook.com (10.173.200.19) 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 20:29:15 +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 20:29:15 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Kristian Larsson <kristian@spritelink.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] 6991bis: address-with-prefix-length
Thread-Index: AQHU6JixdGMCt4a400OFM02B5CwunKYnenSA///B7wCAAA6kAIAARM2A//+/doCAAGTygP//yqgA
Date: Mon, 1 Apr 2019 20:29:14 +0000
Message-ID: <CB853BE0-CA25-4DB0-BE8E-BC4A12D2AED7@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> <4780543F-F233-4874-A5CA-266DCD9C4D70@cisco.com> <7b169ac3-bcf9-1cc2-930f-5c684acb99b7@spritelink.net>
In-Reply-To: <7b169ac3-bcf9-1cc2-930f-5c684acb99b7@spritelink.net>
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: a85fedca-8a1c-43e4-2362-08d6b6e0b558
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN6PR1101MB2355;
x-ms-traffictypediagnostic: BN6PR1101MB2355:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BN6PR1101MB23559BD8D8D8DB09597CF411C2550@BN6PR1101MB2355.namprd11.prod.outlook.com>
x-forefront-prvs: 0994F5E0C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(136003)(396003)(376002)(39860400002)(54094003)(199004)(189003)(26005)(4326008)(66574012)(106356001)(186003)(966005)(8676002)(305945005)(110136005)(76176011)(54906003)(93886005)(6486002)(478600001)(81156014)(82746002)(6506007)(229853002)(81166006)(83716004)(14454004)(316002)(36756003)(53546011)(7736002)(8936002)(105586002)(99286004)(102836004)(25786009)(33656002)(66066001)(6246003)(71190400001)(71200400001)(6436002)(486006)(2616005)(68736007)(97736004)(6306002)(5660300002)(14444005)(2906002)(6512007)(53936002)(256004)(3846002)(6116002)(86362001)(446003)(11346002)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1101MB2355; 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: sSX9ho/qBrIWM3Hk570kSLr9jc41vvR9T6lM+eghrY1sDCiov05o6T3/S5nzGMbTYKpAQYwL2UhNjj2LtYF8/px3EtOOSrfYvpS+Vh277D1O8PsOhNUnGGuPnaL2tjGgQPsb5PLMz5j1tVgMSAODJ8WJ3wL4tlNa2BMd14aTvUbpiz7PljVebwnCm+JK1LuT69LnqxJ2HV7BYDzCa+R9rC+muUg20kG6XyUKet1dWxxfwAWENfcrfa12eovwF8jXhYRNoi5zYRMIvB/HBpmhUJCT/k36F2+1FPxGI2k3V7jQoe99Xf4DWwqYEIR9yxMvHcNXf1feVm35VB9vUd3p4k8WTKQTx67V7RLNfoMRA0flanc166vodCHSG6O9hKLTzE2n9s8slHMeSaCdvxfICAcB8MdRm71Ek6DG/nMBLwA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F801AC89D6BD349877DA45C7066EBED@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a85fedca-8a1c-43e4-2362-08d6b6e0b558
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2019 20:29:14.9644 (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: BN6PR1101MB2355
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OJGDsa6fxjX5QciXM2s9XctN10Y>
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 20:29:22 -0000

Hi Kristian,
Ok - I see that even though the existing ipv4-prefi type requires all 4 octets of the address, the description indicates that the host portion must be zero in the canonical format. Now that I understand your requirement, I'm in favor of adding a type that removes this restriction (i.e., the last statement in the description). 
Thanks,
Acee

´╗┐On 4/1/19, 3:40 PM, "Kristian Larsson" <kristian@spritelink.net>; wrote:

    
    
    On 2019-04-01 19:38, Acee Lindem (acee) wrote:
    > 
    > 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.
    
    No, it does not. You must be referring to some other use case. I want to 
    configure the IP address and prefix-length on an interface. The 
    prefix-length naturally needs to align with the prefix-length / subnet 
    mask used on the network to which the interface is connected. If it is a 
    /24 network then the prefix-length needs to be 24. I can't just say it's 
    a /32 so I can enter this information - the router wouldn't understand 
    what is then connected to that network / interface and wouldn't be able 
    to route packets correctly.
    
    At the same time, I need to specify the exact IP address to be used by 
    this device on the interface, so I need to have bits set to the right of 
    the mask, thus I can't use current ip-prefix type.
    
    
    > The convenience is primarily for mapping to CLI.
    
    Heh, I don't understand what it has to do with CLI but since you're the 
    second person mentioning there must be some connection I don't see.
    
    Kind regards,
        Kristian.
    
    
    
    
    >      "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
    >      
    >