[Lsr] ietf-ospf@2019-10-17.yang: questions
Renato Westphal <renatowestphal@gmail.com> Thu, 01 September 2022 18:30 UTC
Return-Path: <renatowestphal@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 9153BC152577; Thu, 1 Sep 2022 11:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 CS_oFFXDT4sB; Thu, 1 Sep 2022 11:30:31 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 11067C15258D; Thu, 1 Sep 2022 11:30:26 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id 199so18191272pfz.2; Thu, 01 Sep 2022 11:30:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date; bh=5J2uudzygLiAZHtdQH5o/F9wYZYCJmVQAcM9FIjoH6w=; b=XRaLNsKXau1ffWAPWrZurKy9JDsa52xPI4j6xZ/5q8XNvE6q8WHnxiEtNGBANoPjr2 Azi0YeEs4k/NeG/gKCUJ12nsE3cwtfY+TwjIKyb/4G9HA2wuPheFCOWylaN/PnfNy1HS RNB8SYnnyH3hEgUSVA//+Tj8xyA+oIOxKp+bJshqTU5vD9SxACbi2Rr0CRy7emyXOFQd gAZ5YQtD4lVDkhP7+3tt3LiDTGvyNpJUT/eEqPsJIMA8N+CRgY4VBJpu37v/QRqJMZR4 WFnU9JzILWFNv22A1MDVK3g+epRwh7iTa6RpuBvI4nA/dxYZotTnyZpwQh3zLjnhD0uw 7mmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=5J2uudzygLiAZHtdQH5o/F9wYZYCJmVQAcM9FIjoH6w=; b=anptxs+PitQ3HYy0RfQW9PeJmmBWlkWXlmdk+CQavxX3LYVF5Odxv75go52AYfPmNc nSQIMR1HM5W6SeS37Q21/kuGAv7GMkEVsLHwEp4rkIekDRSW0yzmGuIwaCax67qnBvXK OXzR8di/fLpWwmGbehPwdbMZ5cjKA30dlRN3m0RldDUuPDNHH/sr1XfEuJIut7NP8oAg LkzYDVYaLBu9nH2WCJ8FHKp7/ziNWq7d0teYREn/J9oqKTaN9Yy7p9vXIi+GRbM667bb ufq8fIGezXlOJUH0qQWETrTl5LeGHJNliBgnaRVAuYbi/upYKxqqLe6sFZV8QwnJXAgK IOWg==
X-Gm-Message-State: ACgBeo0w/NldjeJzfd+sRIDLFcf8gtDq7lBM5+kY7UndfHP7+i6RGv5w i8kzKY3YHDkD6TXOVLy0WPuuboRigyyfJVVtafqSy3vtHz8=
X-Google-Smtp-Source: AA6agR7TKRbD1XOCOm575ZUrvKF7+9+atU4ke50fSty/ONsJ24coSWh7k7TM5b+9j2F4nR0z7sjuDXCjNkMbvuZnbX0=
X-Received: by 2002:a65:6cca:0:b0:427:17e6:b32b with SMTP id g10-20020a656cca000000b0042717e6b32bmr26507914pgw.349.1662057024784; Thu, 01 Sep 2022 11:30:24 -0700 (PDT)
MIME-Version: 1.0
From: Renato Westphal <renatowestphal@gmail.com>
Date: Thu, 01 Sep 2022 15:30:13 -0300
Message-ID: <CAChaegntR+bM_oxdcNnNcAXmeqfX28e_d2Z3H9VxMFMDzfDwmA@mail.gmail.com>
To: draft-ietf-ospf-yang@ietf.org, lsr@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008f0a9d05e7a1ce22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-VkINsJHQv9Vpn4ASCdq7tPH_x8>
Subject: [Lsr] ietf-ospf@2019-10-17.yang: questions
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: Thu, 01 Sep 2022 18:30:35 -0000
Hi all, I have a few questions about the OSPF YANG module. I apologize if some of these questions were already asked before, but I couldn't find anything in the mailing list archives. I also listed a few improvement suggestions, but I'm not sure if the draft can be updated at this point (it's status is listed as "RFC Ed Queue"). 1. /ietf-routing:routing/control-plane-protocols/control-plane-protocol/ietf-ospf:ospf/areas/area/interfaces OSPFv3 is known to run a per-link basis whereas OSPFv2 runs on a per-IP-subnet basis. So what does it mean to configure an interface for OSPFv2 operation? Should OSPFv2 run only on the interface primary address, or run separate OSPFv2 instances for each one of the interface addresses? The latter option doesn't seem viable since interfaces live under OSPF instances in the YANG hierarchy, but I'd like to hear what others think about this. 2. /ietf-routing:routing/control-plane-protocols/control-plane-protocol/ietf-ospf:ospf/address-family Given how OSPFv2 doesn't support multiple address families, wouldn't it be a good idea to constrain this leaf to OSPFv3 instances only (e.g. using a `when` statement)? 3. /ietf-routing:routing/control-plane-protocols/control-plane-protocol/ietf-ospf:ospf/areas/area/interfaces/interface/instance-id Based on the range of accepted values (`0 .. 31`), one must assume that this is a relative Instance-ID (based on RFC5838's address-family Instance-ID ranges). I think it would be useful to have that clear in the node description. 4. /ietf-routing:routing/control-plane-protocols/control-plane-protocol/ietf-ospf:ospf/local-rib/route I see this routing table lists destination networks only. Shouldn't there be a separate list for routes to border routers? 5. /ietf-routing:routing/control-plane-protocols/control-plane-protocol/ietf-ospf:ospf/local-rib/route/next-hops/next-hop This list is keyed by the `next-hop` leaf, which is an IP address. Given that directly connected routes don't have an IP address, shouldn't this be a keyless list instead? 6. /ietf-ospf:clear-database I think the description of this RPC could benefit from a more detailed explanation. In addition to clearing the OSPF database, I assume all adjacencies need to be reset as well (in order to resync the LSDB). Could someone clarify what would be the expected behavior here? 7. How should route redistribution be configured? I see ietf-rip.yang has a separate container for that purpose, but ietf-ospf.yang (and other IGP modules) don't do the same. I also noticed the BGP model is using definition from ietf-routing-policy.yang. 8. Two standard configuration parameters (or "Configurable Constants") seem to be missing in the YANG module: RFC1583Compatibility (RFC 2328) and LinkLSASuppression (RFC 5340). Was that intentional? 9. RFC 8405 specifies the following: If this SPF Back-Off algorithm is enabled by default, then in order to have consistent SPF delays between implementations with default configuration, the following default values SHOULD be implemented: INITIAL_SPF_DELAY 50 ms SHORT_SPF_DELAY 200 ms LONG_SPF_DELAY 5000 ms TIME_TO_LEARN_INTERVAL 500 ms HOLDDOWN_INTERVAL 10000 ms The OSPF YANG module, however, doesn't have those default values. Shouldn't they be added? 10. RFC 7949 defines a mechanism to use IPv4 to transport OSPFv3 packets. Shouldn't there be a configuration leaf to enable that mechanism? Best Regards, -- Renato Westphal
- [Lsr] ietf-ospf@2019-10-17.yang: questions Renato Westphal
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Acee Lindem (acee)
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Christian Hopps
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Acee Lindem (acee)
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Renato Westphal
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions tom petch
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Acee Lindem (acee)
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Renato Westphal
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Acee Lindem (acee)
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Renato Westphal
- Re: [Lsr] ietf-ospf@2019-10-17.yang: questions Acee Lindem (acee)