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

Martin Bjorklund <mbj@tail-f.com> Thu, 18 April 2019 12:43 UTC

Return-Path: <mbj@tail-f.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 04C5112030E for <netmod@ietfa.amsl.com>; Thu, 18 Apr 2019 05:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 FhdsafhWpTsU for <netmod@ietfa.amsl.com>; Thu, 18 Apr 2019 05:43:35 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 411C212030D for <netmod@ietf.org>; Thu, 18 Apr 2019 05:43:35 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 73DCE1AE0451; Thu, 18 Apr 2019 14:43:33 +0200 (CEST)
Date: Thu, 18 Apr 2019 14:43:36 +0200 (CEST)
Message-Id: <20190418.144336.66180625062045470.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: lhotka@nic.cz, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20190418123651.pcadbphcdpgjedt2@anna.jacobs.jacobs-university.de>
References: <20190418120353.gslhfbdic3tuyqu6@anna.jacobs.jacobs-university.de> <20190418.141843.1973570958718557899.mbj@tail-f.com> <20190418123651.pcadbphcdpgjedt2@anna.jacobs.jacobs-university.de>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ZUAss6Z7hU95xBLSSIQNMAxgs_g>
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: Thu, 18 Apr 2019 12:43:37 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Thu, Apr 18, 2019 at 02:18:43PM +0200, Martin Bjorklund wrote:
> > 
> > > It
> > > is sometimes convenient to treat something that is in fact constructed
> > > as an atomic value.
> > 
> > Convenient for users that enter these values, perhaps.  But not as
> > convenient for a program (or a filter) that needs one of the combined
> > values.  For example, suppose I want to find all entries with a given
> > prefix; that is non-trivial with a combined ip-address-and-prefix
> > type.
> >
> 
> Syntactically, ip-prefix and ip-address-and-prefix look the same, it
> is all about whether the non-prefix bits carry a meaning or not. Once
> these bits carry a meaning, you argue that this combination is a bad
> idea? Or do you argue that ip-prefix also is a bad idea

No, filtering works b/c ip-prefix has a canonical format.

I argue that in general it is a bad idea to combine two values into
one.


/martin


> (and if so do
> you propose ip-prefix to be deprecated)? And what do we do with url?
> 
> /js
> 
> -- 
> 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/>
>