Re: [Lsr] Extended LSA: was I-D Action: draft-ietf-lsr-ospf-admin-tags-08.txt

Acee Lindem <acee.ietf@gmail.com> Fri, 09 June 2023 15:06 UTC

Return-Path: <acee.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3704BC14CE4D for <lsr@ietfa.amsl.com>; Fri, 9 Jun 2023 08:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcdkEqnagWtk for <lsr@ietfa.amsl.com>; Fri, 9 Jun 2023 08:06:05 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 7E26AC151B21 for <lsr@ietf.org>; Fri, 9 Jun 2023 08:06:05 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id af79cd13be357-75d4f12d4a3so185489285a.0 for <lsr@ietf.org>; Fri, 09 Jun 2023 08:06:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686323164; x=1688915164; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=hnb6W5vOFThUG/NPtqk/CdvK3RHG/J7ppAgSCZXuhS0=; b=res6r2D5mL7ODaw303WiZ1Ucmxx9jhOmZl1JpjYlgQh6dkWe4ImNlOqcFAOmQa+Weq s2S5t0NZy480U7WQCvTOv0msUaMhx/7ifCDivP407vgu+oswyZna1mtqZ0Qzvh0dSf/2 yZWT8X8bcIC6PUQM9vaaP6g/obzslAkATjIJMt4Bgh5NlO4tKF9wq6OC/b3LW8pJE+6Z nSre3FzzOj6Wvwsa2PO8ropTR9eD2JTkZPA920zoXPc+HkRpL75D6SDWQwNKO9x7ciDO 4JndcUYe/uQwSCg+UyK2s/ga26DyBqOgisxOmr7MGZoOyafbU9Z5CU14Yi5xn05rZ+h0 xt4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686323164; x=1688915164; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hnb6W5vOFThUG/NPtqk/CdvK3RHG/J7ppAgSCZXuhS0=; b=Cbc+DiTZUc4RuVGPEWrUaFwRcpI+7smiK+zb73ZmxLzDiAhgQ2EKai2s5hcy4QPHny R2VtHTn5MqDRecKkkL1R+11fpiedk3cadYIfiouPw9EfWZwFQBj2cRawuVf702urDm3L qBixgm/pUEFXoBZvboyRq2LhoBhfTu+3jP/ziSxc3VgjpAqaB19nyDpxIf+bJFhggFwZ 2dfwdqzKy/Lkd62Dq/r5kEBuO6JT1W8HUWQBiUeIr0I43+Z3qy3DeWf6YhoafEx1TLUd D3dZq4kIXfHJzZao37wXK1TLJQ0Cks6x2VmhXnqGZmjvPw0s+eGopyBCKXp+IffF2s6l 2rzw==
X-Gm-Message-State: AC+VfDyrdK8+GpoCfCWue/J/AA2g/u6SMm5Frq7PHllCTyIO7NysZAwt lyslqtxtzaBYARwg6JQi3A2caKuSHyY=
X-Google-Smtp-Source: ACHHUZ7YUh7jobc3Z9hzF4mzo9za5TOJgYU7ebdhqfN1NSQqRovr+UdaOt167EnDPe9j1hNtZRJN4w==
X-Received: by 2002:a05:620a:271f:b0:75e:d8b4:3011 with SMTP id b31-20020a05620a271f00b0075ed8b43011mr1674593qkp.0.1686323164164; Fri, 09 Jun 2023 08:06:04 -0700 (PDT)
Received: from smtpclient.apple ([136.56.20.4]) by smtp.gmail.com with ESMTPSA id f17-20020a05620a069100b007593af0c85fsm1085343qkh.88.2023.06.09.08.06.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jun 2023 08:06:03 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Acee Lindem <acee.ietf@gmail.com>
In-Reply-To: <AM7PR07MB62486AB860CCC9C013472C93A049A@AM7PR07MB6248.eurprd07.prod.outlook.com>
Date: Fri, 09 Jun 2023 11:05:51 -0400
Cc: lsr <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <160FFB14-1D45-403D-BD65-3E3354582E53@gmail.com>
References: <168530219283.37199.13683516265047111726@ietfa.amsl.com> <819DE55E-B762-49A2-872A-18A7DE4C2F39@gmail.com> <AM7PR07MB624844DD067FB10CA60C9FA8A0489@AM7PR07MB6248.eurprd07.prod.outlook.com> <6E26D56F-0BDA-4D80-B798-EB5DF80B90A9@gmail.com> <AM7PR07MB62486AB860CCC9C013472C93A049A@AM7PR07MB6248.eurprd07.prod.outlook.com>
To: tom petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/N9T08I7gzWSx0gr23VUbWg5AP_Q>
Subject: Re: [Lsr] Extended LSA: was I-D Action: draft-ietf-lsr-ospf-admin-tags-08.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jun 2023 15:06:09 -0000

Hi Tom, 

I believe Yingzhen and I have fixed all of these nits in the -14 version. 

https://datatracker.ietf.org/doc/draft-ietf-lsr-ospfv3-extended-lsa-yang/


> On Jun 1, 2023, at 6:16 AM, tom petch <ietfc@btconnect.com> wrote:
> 
> Acee
> 
> My comments all relate to the 'latter I-D', that is to the extended LSAs YANG model, the one you really want to publish and not to the admin tags (which you will doubtless want to publish in due course).
> 
> Tom Petch.
> _____________________________________
> From: Acee Lindem <acee.ietf@gmail.com>
> Sent: 31 May 2023 19:44
> Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-ospf-admin-tags-08.txt
> 
> Hi Tom,
> 
> On May 31, 2023, at 06:45, tom petch <ietfc@btconnect.com> wrote:
> 
> From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of Acee Lindem <acee.ietf@gmail.com<mailto:acee.ietf@gmail.com>>
> Sent: 28 May 2023 20:35
> 
> Simply refreshed before expiration and updated a reference. We really need to publish the extended LSAs YANG model as it is a prerequisite for a lot of drafts.
> 
> <tp>
> Regarding the latter, I noted back in 2020 that it was a tough read and that has not changed, so I will likely only have the energy to review it once and so will wait for at least WGLC before undertaking such a review.  Meanwhile  I see some editorial glitches but would not appreciate a revised I-D unless and until that WGLC is imminent.
> 
> s.1.1 text is out of date
> 
> I don’t see a problem in -09.

I updated with with the full list of normative words. 


> 
> 
> /opf:ospfv3/ospf:body:
> here and elsewhere, what is the final colon doing?
> 
> I don’t see this anywhere in the draft.

For better or worse, this is the format that “pyang -f tree” provides. 


> 
> 
> 
> contact URL is out of date
> 
> I’ll update my Email.

This is updated. 


> 
> 
> references to OSPF YANG need updating to the RFC
> 
> This is fixed in -09.

Fixed. 


> 
> 
> 
> 'Figure .. ' now appears in four places, doubtless a 'good idea' from the tool makers.
> 
> There is only “Figure 1”.

I agree this is confusing. I’ve removed all the figure designations.  

Thanks,
Acee



> 
> Thanks,
> Acee
> 
> 
> 
> Like I say, not justifying a new I-D just yet IMHO.
> 
> Tom Petch
> 
> Thanks,
> Acee
> 
> On May 28, 2023, at 3:29 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the Link State Routing
> (LSR) WG of the IETF.
> 
> Title           : Extensions to OSPF for Advertising Prefix Administrative Tags
> Authors         : Acee Lindem
>                   Peter Psenak
>                   Yingzhen Qu
> Filename        : draft-ietf-lsr-ospf-admin-tags-08.txt
> Pages           : 19
> Date            : 2023-05-28
> 
> Abstract:
> It is useful for routers in OSPFv2 and OSPFv3 routing domains to be
> able to associate tags with prefixes.  Previously, OSPFv2 and OSPFv3
> were relegated to a single tag and only for AS External and Not-So-
> Stubby-Area (NSSA) prefixes.  With the flexible encodings provided by
> OSPFv2 Prefix/Link Attribute Advertisement and OSPFv3 Extended LSAs,
> multiple administrative tags may be advertised for all types of
> prefixes.  These administrative tags can be used for many
> applications including route redistribution policy, selective prefix
> prioritization, selective IP Fast-ReRoute (IPFRR) prefix protection,
> and many others.
> 
> The ISIS protocol supports a similar mechanism that is described in
> RFC 5130.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-admin-tags/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lsr-ospf-admin-tags-08.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-ospf-admin-tags-08
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org<mailto:Lsr@ietf.org>
> https://www.ietf.org/mailman/listinfo/lsr
>