Re: [Teas] Example of model and modules designed for augmentation

Dhruv Dhody <> Mon, 25 July 2022 16:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6F7C9C13CCC3 for <>; Mon, 25 Jul 2022 09:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.107
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kBQgSD5771QX for <>; Mon, 25 Jul 2022 09:36:17 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::d33]) (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 (Postfix) with ESMTPS id A70CEC13CCC0 for <>; Mon, 25 Jul 2022 09:36:17 -0700 (PDT)
Received: by with SMTP id c185so3545119iof.7 for <>; Mon, 25 Jul 2022 09:36:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zxr+87Lja5pgycpCoSZoJ3KJydMbYGxiBWQK2lFlXZk=; b=h0dOcngJdtkNIZR0HCWp8lbqsoQGGw+mZLKvNcXkmSYL9UkLxTuleJ2zRxQOWI7ML7 qePs67bH1lrt1XAxYKiLRasee3cAgWmwODHR8k0+vZLsMM5nVQgZaOS3LaACY2y/GyG6 kGokWIbwEOHb9zL4eArT5G+VINpcro2naFlGWuk+k0LaJIUHJCnTyiKdTZiQZOVrGwPm WifjvWDGNB6tAgVWw+t1mZ94ZsrOF5WehQlWQv4qOJfTcUYcQGZM0RprYJudQjm616nS 8svl9fBVuHY6WUuW0ytd15/Hi1Z0/oMa3uC08DIoKfVvzAup0umCpKNxJg7XdaP68z8t QGiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Zxr+87Lja5pgycpCoSZoJ3KJydMbYGxiBWQK2lFlXZk=; b=c2KARCt2iVy2NEiGhnd7TDcUvkpi67Caao1biKrV0zEAaXUYCzEt71yFxt8c/jwKgp U15hsZ8FcIt+y6Uh/dmfR3FuNi7VfMkWgo+YlYODokAVUgmSrOXXwBR7a1VjHutsrHWl 0oOir9wSSeH06uJRrv4wAaCfEWf+oDRP+TJBmixp7bLgoFwpnh81ZdDCvpJyHLRg2Tkz ns7j+nZNxbBl6dIBiwwNygEAEDFG3jsWEtf4gwfwEp4sx04jLamt+YUDs3RWmNrGI8pQ OeBvEh0n+9YDm4YWao5fcG53oj4V85X8qXUVAUdRrtI5ei8LBbDkgcImQys3UbRryhdx Mr8A==
X-Gm-Message-State: AJIora/kAdXsab4qM3hHKcEa6BJ7ZSkgfdlSxUW9sCRI/dUShQabHgaI /PhCYAeaiVKLRaM+bO6M5DCoK3WXrs3YOh04ScM=
X-Google-Smtp-Source: AGRyM1vE+G8OPDsp8ccmrcX2oyqakGtHIHn11LCTHszSGoCINk37HghnwwktJkHGSXFo3SjBKjWjURko054O+LLzBqE=
X-Received: by 2002:a6b:5f03:0:b0:67b:ef4d:e3ed with SMTP id t3-20020a6b5f03000000b0067bef4de3edmr4776485iob.45.1658766976431; Mon, 25 Jul 2022 09:36:16 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Dhruv Dhody <>
Date: Mon, 25 Jul 2022 22:05:40 +0530
Message-ID: <>
To: Lou Berger <>
Cc: "Rokui, Reza (Nokia - CA/Ottawa)" <>, TEAS WG <>
Content-Type: multipart/alternative; boundary="000000000000653d9105e4a3c88c"
Archived-At: <>
Subject: Re: [Teas] Example of model and modules designed for augmentation
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 25 Jul 2022 16:36:21 -0000

Hi Lou,

There were 2 seperate questions on that slide, but with the "opaque"
example, the usecase proposed to us was for a way to add "new" attributes
via pure configuration in the current model itself without the need for any

Issue: To maintain the technology agnostic nature of the YANG model we use
> 1. A pair of (identity, value (string)) to support many attributes;
> • a common practice, for instance different metric-types use a common leaf
> metric-value of uint64 (RFC8776).
> 2. Support for “opaque” attributes that can be configured without an
> identity
> • This allow new attributes to added without updating YANG model
> Concern: Using a string instead of an explicit type in YANG there could be
> interoperability issues. The use of opaque attributes that are not defined
> in YANG adds to this issue.

We need inputs from the WG if that is a valid usecase and the correct


On Mon, Jul 25, 2022 at 9:23 PM Lou Berger <> wrote:

> Reza,
> In the session you asked for an example of a model (and modules) that
> have been designed with technology specific augmentation in mind.  For
> an example, take a look at
> --
> search for augment...
> Lou
> _______________________________________________
> Teas mailing list