Re: [netmod] usage of ip-address in openconfig

Andy Bierman <andy@yumaworks.com> Thu, 21 April 2022 01:19 UTC

Return-Path: <andy@yumaworks.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 B3F0A3A17F5 for <netmod@ietfa.amsl.com>; Wed, 20 Apr 2022 18:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level:
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NUMERIC_HTTP_ADDR=1.242, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks.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 ByzpCa59gPsa for <netmod@ietfa.amsl.com>; Wed, 20 Apr 2022 18:19:22 -0700 (PDT)
Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ACE33A15BF for <netmod@ietf.org>; Wed, 20 Apr 2022 18:19:22 -0700 (PDT)
Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-2edbd522c21so36582377b3.13 for <netmod@ietf.org>; Wed, 20 Apr 2022 18:19:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PYAjUNE4TPXhp9SMyouTenIoebQO5zEM6aIN3dBughA=; b=VfAD1h8JU/ohZxkN+t6lnkPmknQlDE86UYxSLTntydEcy+yGBoirSuVz/a8q8ZlG4M a3yFKTRcmaCmUkOK3CieFsRW1YfLX6/fM2ikWRiYauRH4B0QXC1LrD04Y/PgpjiG2Sqv 95xjsHfmrbe10FBCYK2t5PiiMPaFMrNtq7M/VsHjSedWpG4GwZEXX2ci7b4MNdnxswer LqE4hKCTXXhUPyWiNjQmG7R9zrCabGFaLVCD0FSCJwpmotvhhhZES07zHdQUWxgNmbup II34pnAs4t6AzD7l6LIxkKVF+FaSYghjqBPZXY7bzCIbRFyBQdQzKOczNPafskYBV9CE eHjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PYAjUNE4TPXhp9SMyouTenIoebQO5zEM6aIN3dBughA=; b=UisD6Wjij+RRQZ6V6UflojlXR7B8cL3lZsCLwqhmWplaTFTsKAlA3F6YmJz4DT0QPV izhzRYHIgIdotiRlBD1qa0Eaj+5z9bkBXHGlLOuk9OEonEmeFuPgb6bWSCPzb9befaV5 KBwKnh48xu4d0RjiUvx5evaIWFWMe1eBKHtM81BQ3AqcKG+Z1xB3ptJ/XutR/qefrfMO DmmHB6AS7JpEiadUs9lm922lvvD7G7N6OuneGPiFI5ZA3yApnlRsjOj+z+/SS8AGjIHB H2jzVWrGgPJ3fj32WVXU8uFrZu5SxXCAAEt59c3W3NnlB1ciXO2n9IL0gCObMEV5SriK RPpw==
X-Gm-Message-State: AOAM530pl05l+15+TpFkHbHwPZnL8hDCs5AQRL7B5S5IkuFYqppJS8GU CaRKIEGQ5CXsvjjgSKX7WbqNnWKTW+5Je5KvzUNM1AR0FrY=
X-Google-Smtp-Source: ABdhPJwr409x4R54DkdghYfmCI1AcESr1R7UC+TpaSH3++9v+zgDsAlXNBG+hK37/AOTvkJlCxQmlkZU+d3cTfYLfi8=
X-Received: by 2002:a81:9ca:0:b0:2eb:f567:217f with SMTP id 193-20020a8109ca000000b002ebf567217fmr23319474ywj.322.1650503960565; Wed, 20 Apr 2022 18:19:20 -0700 (PDT)
MIME-Version: 1.0
References: <CABCOCHRMOfVL4=p9UfNJVgLE7fGEDmKKmOAariDHXFdm1b4iew@mail.gmail.com> <20220420213448.w4aex5cpthejkvvh@anna> <CABCOCHS-r3F-hT+wW1M724nAnq2LHZFPJzMruus_Y4TB8GtEqQ@mail.gmail.com> <20220420223440.7vouloqkv5illw2p@anna> <8E016824-BDC7-4096-B92B-ECC4B6B7C4B9@cisco.com>
In-Reply-To: <8E016824-BDC7-4096-B92B-ECC4B6B7C4B9@cisco.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 20 Apr 2022 18:19:09 -0700
Message-ID: <CABCOCHRY2nwM9W4C_KK+h94_jK8=xEPf3qtE7QUmybMjVcfT-Q@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>, NetMod WG <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000452ee805dd1fe6f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ISsnZZ2mMt6m-88N2I6mPuCL78k>
Subject: Re: [netmod] usage of ip-address in openconfig
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, 21 Apr 2022 01:19:27 -0000

On Wed, Apr 20, 2022 at 4:02 PM Acee Lindem (acee) <acee@cisco.com> wrote:

>
>
> On 4/20/22, 6:35 PM, "netmod on behalf of Jürgen Schönwälder" <
> netmod-bounces@ietf.org on behalf of j.schoenwaelder@jacobs-university.de>
> wrote:
>
>     On Wed, Apr 20, 2022 at 02:51:35PM -0700, Andy Bierman wrote:
>     > On Wed, Apr 20, 2022 at 2:34 PM Jürgen Schönwälder <
>     > j.schoenwaelder@jacobs-university.de> wrote:
>     >
>     > > I am not sure it helps to look at individual data models but since
>     > > openconfig is often presented as getting things right, here is
> what I
>     > > find in openconfig-system-logging.yang
>     > >
>     > Not sure why this missing feature is relevant.
>
>     I suggest that people questioning the need to support scoped IPv6
>     addresses in IETF YANG data models write an I-D explaining why IETF
>     YANG data models do not need to support scoped IPv6 addresses and pass
>     the I-D through the IPv6 working group.
>
> The question is not whether there is a single use case for IPv6 link local
> addresses with a zone. The question is whether the base pattern for IPv6
> addresses should include a zone and whether one was expected for all the
> existing YANG model usages of inet:ipv6-address. I think that given the
> very narrow scope, the answer is clearly no.  Additionally, the zone is
> only applicable to IPv6 link-local addresses yet the pattern in RFC 6991
> allows the zone for ALL IPv6 addresses. This is also clearly wrong.
>
>

I think Martin's original comment about 0.0.0.0 applies here as well.
The pattern cannot be trusted to validate a client-provided IP address.
It accepts all possible variants, including some invalid variants.

It is always the server responsibility to validate the client input for the
specific data node.
Just reject all zone index variants from the client and ip-address ==
ip-address-no-zone.

If the argument is that a zone index is always allowed (even if the usage
is limited)
then why does the ip-address-no-zone typedef exist at all?  There are no
YANG guidelines
for picking between them.


Andy







> Do you at least admit that IPv4 link-scoped addresses with zone have no
> useful purpose? Or are you going to try and argue that the ever-popular
> 169.254.0.0/16 addresses are an absolute requirement for YANG models and
> expected for every usage of inet:ipv4-address?
>
> Acee
> P.S. I would add that it is a good thing that syslog server can't be
> mapped to a link-local address with a zone in the Open-Config model. In
> general, IPv6 services such as syslog servers should be mapped to global
> IPv6 addresses.
>
>
>     /js
>
>     --
>     Jürgen Schönwälder              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
>
>