Re: [netmod] [Lsr] I-D Action: draft-ietf-lsr-ospfv3-extended-lsa-yang-10.txt

Andy Bierman <andy@yumaworks.com> Thu, 14 April 2022 19:48 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 8EFA63A10F8 for <netmod@ietfa.amsl.com>; Thu, 14 Apr 2022 12:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Rbedze4oH3oB for <netmod@ietfa.amsl.com>; Thu, 14 Apr 2022 12:48:31 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 F29483A1102 for <netmod@ietf.org>; Thu, 14 Apr 2022 12:48:30 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id p65so11267631ybp.9 for <netmod@ietf.org>; Thu, 14 Apr 2022 12:48:30 -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; bh=ILCmUEPt8xQDxftLsaSjN/+paZ9o9S6DxVTQa1yhsHQ=; b=c+Awl6YNFDpl0Pd5czAoifQUaQ4aZa6LaJJmCT8ejTjPwGaAaBS7LW8BjmrN9jzuTQ g6qk73KNvZHvGH6K/o2M+F/pkwkUjGy4utHBau8JsnH6gPDipT4ZnPOezYdo0MtCKd+6 9HDFhmFCSH0VLAxBLKd+qSEjfrxF5VkyksrxdI31NyuwNgJYJxsDt1NZVRgzOg1S+nGO Ldc6alFKjKKBIxm+nXftkBAR5PFTZY9+z86FJLoLMZgF70z2QF5/3oQa/6KjLU7dwEvA dzzsuiuoETAxa/71x4ElspvsHhbE9W1Ivm9Fc8w5drhRtzeDFC+khoKpVoGgiDvUfWWy 1gsQ==
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; bh=ILCmUEPt8xQDxftLsaSjN/+paZ9o9S6DxVTQa1yhsHQ=; b=xIewmxOuzpwWLryh7TDXSTnOwfD7sIRPNIuCaMjAyxVlrGI9FyA8AjsVxb/baei6+b JbApK4kK6IjCYdt74/i2hi6Uyou/IYrtc9B3nSCIEgagWpTJllgH8JgnMhFFdJdcZbyj qIu78PR7SL0ZOL+YgDiPqeevCsZsI/XGa1LGzRx3KXyXKp20fDIGLUTQ0qTwgYOWTdaY Mn64Uq/fyUHMCq5JB0DAxbBn0V7cQjsXZd1prLYUh4hRTbxtFGCP5e+AGpMah1ScGXD7 N1s95AG9/5bti4O0T25mlUkRgOvuu31hZwRHmESz0howM6mAsljbst+YhOHTQKo1e1SH WK/A==
X-Gm-Message-State: AOAM530DRf78arFpoz4mOLF7VvtdoUwbZ/dQOVf50+NlpBydPqJUMROs XTLvAVHHYoF3CJGTn1w0CtqndK/Azm40QrlLbR4NiA==
X-Google-Smtp-Source: ABdhPJw9NacExKtTTES20nValB6PtVEjdHCX/RSx1jUTvCvX1Cxuu6B3b9TbYypQhFyZX9WLm/j9yN7WCPN0AhFOSag=
X-Received: by 2002:a5b:247:0:b0:624:4d24:94ee with SMTP id g7-20020a5b0247000000b006244d2494eemr3038020ybp.197.1649965709787; Thu, 14 Apr 2022 12:48:29 -0700 (PDT)
MIME-Version: 1.0
References: <BY5PR11MB41966C83474B52949C2B660FB5EF9@BY5PR11MB4196.namprd11.prod.outlook.com> <20220414.152331.1522036488630734842.id@4668.se> <20220414134730.62e3fyhl7e4pvuz4@anna> <20220414.160345.1807693114840953491.id@4668.se> <1347E93F-F193-4677-8070-5E28EDB2F14F@cisco.com> <CABCOCHTPZ+ieLeNRhDR7AmyYYhEgq2bjyHsW-ARM3_9sAip0vQ@mail.gmail.com> <20220414193836.ufqzfhnitb5l5w3h@anna>
In-Reply-To: <20220414193836.ufqzfhnitb5l5w3h@anna>
From: Andy Bierman <andy@yumaworks.com>
Date: Thu, 14 Apr 2022 12:48:18 -0700
Message-ID: <CABCOCHQApdv7U15kYZFGopeFE8dR9Xr9SN9vSrwWobwoX-9jyg@mail.gmail.com>
To: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, Martin Björklund <mbj+ietf@4668.se>, "lsr@ietf.org" <lsr@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000616a005dca2946c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/CfCt6_6rPMVilCK9Pbv0ZzTnK-4>
Subject: Re: [netmod] [Lsr] I-D Action: draft-ietf-lsr-ospfv3-extended-lsa-yang-10.txt
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, 14 Apr 2022 19:48:37 -0000

On Thu, Apr 14, 2022 at 12:38 PM Jürgen Schönwälder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Thu, Apr 14, 2022 at 09:23:38AM -0700, Andy Bierman wrote:
> > >
> > So is this a correct summary:
> >
> >  - zone index is not used in IPv4 at all
>
> There are link-local IPv4 addresses, they are less wide-spread since
> IPv4 stacks generally do not auto-configure IPv4 link-local addresses.
> Nobody will be able to confirm "not used at all", this questions is
> somewhat rhetoric since nobody can answer it.
>
> >  - zone index is not configured by a client in IPv6 at all
>
> Configuring zone indexes is required in many cases to reach services
> that are only reachable via link-local addresses. I mentioned the DNS
> resolver example and this applies to pretty much any transport layer
> endpoint. This is why by design (and not by accident) the with zone
> version of ip-address is used in the inet:host typedef.
>
> >  - zone index is assigned by the system (as needed) to IPv6 link-local
> > addresses
>
> A link-local address exists on a link and as such does not need a zone
> index as long it is used on the link. However, when you want to refer
> to a link-local address on a system with more than one link, then the
> link-local address is ambiguous and to disambiguate things you either
> specify in adding the interface to be used or you embed the zone index
> in the address. Since application code usually assumes that a
> transport address is an (ip-address, port) tuple, people converged on
> adding the zone to the ip address (instead of rewriting all APIs to
> use (ip-address, port, interface) tuples. The zoned IP address
> notation is meanwhile widely supported. This is why we have, for
> example, RFC 6874 (but the IPv6 folks have a reoccuring debate about
> the question whether the % needs to be percent encoded or not,
> draft-carpenter-6man-rfc6874bis-03).
>
> > I want to add a server option in our code to always reject (or alter)
> > an edit that contains a zone index.  I need to know the consensus on
> > whether it is OK to ignore a zone index from a client.
>
> It is your choice to design a product that will not work with
> link-local addresses. For IETF data models, I expect that the bar is
> higher and that people can expect that IETF data models are written to
> also work with link-local addresses. If implementers than decide that
> their users do not need to work with link-local addresses, so be it,
> you can make your server reject the optional zone index. But others
> can decide that they customers can also work with link-local
> addresses. If we blindly remove the zone index from ip-address, then
> the IETF would break data models for those who consider link-local
> addresses a first class citizen.
>
>
A server option is useful for an implementation that does not
support zone index configuration. It is an implementation detail so out of
scope.

The proposal is for a 2 year phase to change modules
that really do want a zone index.  It is not blindly removing the zone
index.


> Nothing in RFC 6241 suggests that this is OK for <edit-config>.
>
> I have no clue what you mean. If your server recceives a value that
> your server does not support, you reject the value.
>
> /js
>

Andy



>
> PS: I recall the side meetings with IPv6 people to sort out how we add
>     proper IPv6 support to MIB modules, which led to RFC 4001, which
>     later influenced the YANG typedefs. Almost 20 years later (and
>     IPv6 deployed at a much larger scale) I find myself in a
>     discussion where people question that we need to support
>     link-local addresses. This is very irritating.
>
>     Apparently, getaddrinfo() implementations tend to handle zoned
>     link-local addresses just fine and any code that passes a zoned ip
>     address string to getaddrinfo() will likely return you a socket
>     address with the sin6_scope_id filled in properly. You actually
>     have to do extra work to prevent the right thing to happen if your
>     code passes strings on to getaddinfo(). I am puzzled why people
>     want to do this.
>
> --
> 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/>
>