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

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 14 April 2022 19:46 UTC

Return-Path: <jmh@joelhalpern.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 CDFCF3A10D9; Thu, 14 Apr 2022 12:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 (1024-bit key) header.d=joelhalpern.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 WAXlqE03D1_R; Thu, 14 Apr 2022 12:46:47 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D48A23A10D5; Thu, 14 Apr 2022 12:46:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4KfVMq4RCYz6GWNN; Thu, 14 Apr 2022 12:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1649965607; bh=jKku9yEI5buUXuxsg7z1zqnUSE4D9iG9/dJ8ReD5M4s=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=hBnFrBEIf+cL6JFpZsStuJYrcfniTO5q4sTL1ItpdNE67HVuC9mkf6h+hqOJfpQ/D Ag7QU8vlNxliRx0wesCqDFdW0UfAsxIN8JfNS3M0PzHLm3rBAIO3Tpa9WWl4yCrHTZ hgoDT6t8gUgPwp65Hph6nbxsi8qqVQPwFjoh7JGQ=
X-Quarantine-ID: <gUo0NbSYgdyL>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4KfVMp6G70z6GBNx; Thu, 14 Apr 2022 12:46:46 -0700 (PDT)
Message-ID: <a4528df2-220a-10b3-b30a-943ed8e2fdc7@joelhalpern.com>
Date: Thu, 14 Apr 2022 15:46:44 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-US
To: Andy Bierman <andy@yumaworks.com>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <CABCOCHTPZ+ieLeNRhDR7AmyYYhEgq2bjyHsW-ARM3_9sAip0vQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/XTwMWvL0DjLWVTPMWzD7sZMxAjw>
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:46:53 -0000

That does summary below does not match what others have said on this thread.

Yours,
Joel

On 4/14/2022 12:23 PM, Andy Bierman wrote:
> 
> 
> On Thu, Apr 14, 2022 at 8:01 AM Acee Lindem (acee) 
> <acee=40cisco.com@dmarc.ietf.org <mailto:40cisco.com@dmarc.ietf.org>> wrote:
> 
>     While RFC 4001 really didn't need to extend the zone index to IPv4,
>     the conversation also pertains to IPv6 address types. At least RFC
>     4001 got it right by not making the zone index part of the default
>     types and defining ipv4z and ipv6z.
> 
> 
> So is this a correct summary:
> 
>   - zone index is not used in IPv4 at all
>   - zone index is not configured by a client in IPv6 at all
>   - zone index is assigned by the system (as needed) to IPv6 link-local 
> addresses
> 
> 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.
> Nothing in RFC 6241 suggests that this is OK for <edit-config>.
> 
> 
>     Thanks,
>     Acee
> 
> 
> Andy
> 
>     On 4/14/22, 10:04 AM, "Lsr on behalf of Martin Björklund"
>     <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org> on behalf of
>     mbj+ietf@4668.se <mailto:mbj%2Bietf@4668.se>> wrote:
> 
>          I thought the discussion was only about ipv4?
> 
> 
>          /martin
> 
> 
>          Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de
>     <mailto:j.schoenwaelder@jacobs-university.de>> wrote:
>          > On Thu, Apr 14, 2022 at 03:23:31PM +0200, Martin Björklund wrote:
>          > > Hi,
>          > >
>          > > First of all, I agree that if we were to design this from
>     scratch, I
>          > > think we should have a type for just an ip address, and use
>     a second
>          > > leaf for the zone (or interface).
>          > >
>          >
>          > The notation 'fe80::4d9:ff04:4fa6:7980%en0' is widely
>     supported in
>          > application space. The IPv6 working group has a recurring
>     debate on
>          > the usage of zoned IPv6 address in URLs [1], where the debate
>     is about
>          > the question whether the % needs to be escaped or not. I do
>     not know
>          > where the latest iteration stopped, but details can be found
>     in RFC
>          > 6874 and draft-carpenter-6man-rfc6874bis-03.
>          >
>          > Philip Homburg's RIPE Labs note [2] might also be an interesting
>          > read. According to this, getaddrinfo() actually deals with zoned
>          > addresses (and hence even data model implementation that pass
>     data to
>          > getaddrinfo() to obtain socket addresses may do the right thing.)
>          >
>          > My view is that down in the network layer models, you often
>     know the
>          > interface by context and ipv6-address-no-zone is sufficient.
>     If you go
>          > to application space, you really want "ipv6-address-with-zone" by
>          > default in order to support link-local addresses.
>          >
>          > /js
>          >
>          > [1] http://[fe80::4d9:ff04:4fa6:7980%en0]/
>          >
>          > [2]
>     https://labs.ripe.net/author/philip_homburg/whats-the-deal-with-ipv6-link-local-addresses/
>     <https://labs.ripe.net/author/philip_homburg/whats-the-deal-with-ipv6-link-local-addresses/>
>          >
>          > --
>          > 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/
>     <https://www.jacobs-university.de/>>
> 
>          _______________________________________________
>          Lsr mailing list
>     Lsr@ietf.org <mailto:Lsr@ietf.org>
>     https://www.ietf.org/mailman/listinfo/lsr
>     <https://www.ietf.org/mailman/listinfo/lsr>
> 
>     _______________________________________________
>     netmod mailing list
>     netmod@ietf.org <mailto:netmod@ietf.org>
>     https://www.ietf.org/mailman/listinfo/netmod
>     <https://www.ietf.org/mailman/listinfo/netmod>
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod