Re: [Idr] YANG requirements for IDR drafts (was Re: draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20))

Robert Raszuk <robert@raszuk.net> Tue, 05 July 2022 20:36 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10AB5C13C36B for <idr@ietfa.amsl.com>; Tue, 5 Jul 2022 13:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=raszuk.net
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 Bk6xLMoVuPVy for <idr@ietfa.amsl.com>; Tue, 5 Jul 2022 13:36:25 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 4A485C139AD2 for <idr@ietf.org>; Tue, 5 Jul 2022 13:36:24 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id r9so15980372ljp.9 for <idr@ietf.org>; Tue, 05 Jul 2022 13:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KuVRIk5muD+y6NPGsnlp/pJaQj+siIIcjpAfKjtnHUM=; b=fARB/5dLnvvZo1yuLRRNAlEe4hdJNuwzqOmEUgdxefBY0QE4RfdSZAHlJ6xc0/72Hb HPaAVullX+nlXBMy/fYfOH/B2s+w/qHNynJ+7830WiuDWacnmj/xSBXZAZAPQa7mGSpi VyZfVpbTK1SAneZrLd7wJhyiX4E/FpGTFhaH21o1fyc6DXrEAtVC332wU23jBxjEwo0g FQTm05trKxxaMWAP9+pOcB4odR1agdCCc5sjQxqhLcZYsMzumn41o9VMwLuRWHqIVvll nBDvCQ+2F2AP6MGp8IrK7qIpgxC5l4s7EiQ2IQ+tdOJVYk5Wh2Rb79FxDYKhIdv47rMs UTFA==
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=KuVRIk5muD+y6NPGsnlp/pJaQj+siIIcjpAfKjtnHUM=; b=FcqZloPqvgRdhDYSczPPvcsIkLFM0qBygnG1EQch464xs+Lmji+UWLMkw1LZSAVrSm 2YGfh9fmvde6sqCCGTLlQPsCngbn8+FOjgJ04ZkENsFGtDTPNakVqivOfYVdSr05Pe5c dHBJtmw9sTcVafj4XrgS2TurQd8X6R3x9Ln4gsj1Z+pw92jNutkKdRwlgmjKHO617TVl tlJP220+15NFWNdCsIKF+9nwqOOnv7fUB9N1Wu59UQ1+zhYBj5vrcCyfapXQkr8xmmDR /KtagwMEzJXzL9hfRRKwT0jQHjdEK/HLcN09wKbbx6pOgDR4g/ALXNa/qZZlEYTWBRCd kf/g==
X-Gm-Message-State: AJIora8ESrIGMQ4LM0825lwQf3/aI+/MvnalYw9JzELzFTwDZWYyhyE6 SFfGOPPQH6mqNlm1or407qYqYa887FgFp6PTcmA3uA==
X-Google-Smtp-Source: AGRyM1tLKs/oSlkcw0jFycoKOHJADxZPyz8SWCfjDsXO7jDQLU0tFUUNE5kAuIWw1XQx6Xq51KZPNizt/vfEuz16hM4=
X-Received: by 2002:a05:651c:244:b0:255:32c8:dd42 with SMTP id x4-20020a05651c024400b0025532c8dd42mr19687935ljn.101.1657053382388; Tue, 05 Jul 2022 13:36:22 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB487213F9F5CD1A5E104B4645B3A29@BYAPR08MB4872.namprd08.prod.outlook.com> <CAH6gdPx+YbTXronoYzSuk7xNXGfsH5iD5i3Q5oDWMoKucCRexQ@mail.gmail.com> <DM6PR08MB48730CA153D5FFDF5C235C12B3AC9@DM6PR08MB4873.namprd08.prod.outlook.com> <821D2B29-C637-44A0-9D46-25AB33D7E11D@juniper.net> <CAH6gdPz2JRrxih52HekJxuDTC0ng52Q296L+zs7U4=rOHjFiOg@mail.gmail.com> <CA+wi2hMnhWEcHXw1q7TJASeExQzp7OwWrJ+2s1qP2aPNKgUX8A@mail.gmail.com> <CAH6gdPxTTXer+-OAWvBVP+WjEpKS5x8OP+dW-9nmtUbKmA2d=g@mail.gmail.com> <CA+wi2hPGJr325-mKSKi=JT7q6EMtWWmM=JAvOLKyve3oh+RysQ@mail.gmail.com> <BYAPR08MB48721013BC2D3F0FEA0B170BB3B49@BYAPR08MB4872.namprd08.prod.outlook.com> <BYAPR08MB487284932F3C9E2328ECA1A0B3BB9@BYAPR08MB4872.namprd08.prod.outlook.com> <CAOj+MMGPekwBtLBDooJb5+bOX+BqotsRt+Vd1RrE+XfmOLaJzA@mail.gmail.com> <A06F5DA4-3873-4AAE-852C-58138ADB9246@pfrc.org>
In-Reply-To: <A06F5DA4-3873-4AAE-852C-58138ADB9246@pfrc.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 05 Jul 2022 22:36:22 +0200
Message-ID: <CAOj+MMHTQKZi4xzMF1Fne7eiP2d=i-n=HHCo2YquX-JTrafFVA@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Sue Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, lsr <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003b41f905e314ce8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jKhKWVR23Cy08DL-eIP1i4tEPK0>
Subject: Re: [Idr] YANG requirements for IDR drafts (was Re: draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20))
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2022 20:36:29 -0000

Hi Jeff,

Many thx for your note. As I clarified to Sue my question was really about
LSR WG not IDR :)

And the trigger was Gunter's claim that his employer's OS is already
sending content of LSDB over YANG.

So I was a bit puzzled what happens with new extensions if they like ISIS
reflection if they do not contain the YANG model from day one ? How is that
data being encoded if at all ?

That answer is also important to alternative to BGP-LS discussion but let's
have a separate discussion on this in the coming weeks.

Best,
R.


On Tue, Jul 5, 2022 at 10:28 PM Jeffrey Haas <jhaas@pfrc.org> wrote:

> Robert,
>
>
> On Jun 30, 2022, at 6:56 PM, Robert Raszuk <robert@raszuk.net> wrote:
>
> Isn't the YANG section a requirement for all protocol extension
> documents before they are sent for publications these days ?
>
>
> We're not yet to the point where extensions to YANG modules are part of
> base IETF work, but we're probably going to need to have that discussions
> soon across IETF.
>
> This year will see base YANG modules for a number of protocols done.  I
> had hoped I could contribute toward the BGP YANG module getting done closer
> to start of year than not, the BGP module is more likely to be complete
> this fall.[1]
>
> Once we have the base modules out, augmentations for them covering various
> extensions will make sense.  Prior to the publication of the base modules,
> we wouldn't have had the documents advance due to MISREF dependencies.
>
> Once our base module is out, we'll have need of a number of small
> augmentation modules to fill in the missing features.  If you're looking to
> help with that work, there's probably room to start writing some drafts
> now.  I think the BGP YANG module is structurally solid for most
> configuration and operational state.  Policy is the remaining large piece
> of work.
>
> That said, I think we'll find trying to write YANG for BGP-LS challenging.
>
> The reason I am asking this is in fact in light of the other discussions
> we have on IDR list where at least one mode of link state state
> advertisement can be done using YANG encoding. Is YANG section optional in
> LSR WG documents which define new protocol extensions and new functionality
> ? If an implementation uses YANG to push LSDB how the new TLVs defined in
> the draft are going to be shared across ?
>
>
> I think your broader question about what a streaming protocol for IGP
> state looks like is probably best addressed in those threads.  But, as
> above, it's going to be an interesting modeling exercise.
>
> -- Jeff
>
>