Re: [Teas] [yang-doctors] Feedback on options for issue #1 in TE tunnel YANG

Ladislav Lhotka <lhotka@nic.cz> Mon, 25 July 2016 13:38 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8D312D0E0; Mon, 25 Jul 2016 06:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 3CpXrbatsAop; Mon, 25 Jul 2016 06:38:29 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 75AD512D833; Mon, 25 Jul 2016 06:38:29 -0700 (PDT)
Received: from localhost (unknown [195.113.220.110]) by trail.lhotka.name (Postfix) with ESMTPSA id F1FD31CC0281; Mon, 25 Jul 2016 15:38:33 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Tarek Saad (tsaad)" <tsaad@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
In-Reply-To: <5717BEB6-46B6-47EB-BE9B-F8A5AE2E8EFB@cisco.com>
References: <5717BEB6-46B6-47EB-BE9B-F8A5AE2E8EFB@cisco.com>
User-Agent: Notmuch/0.22.1 (http://notmuchmail.org) Emacs/24.4.51.2 (x86_64-apple-darwin14.0.0)
Date: Mon, 25 Jul 2016 15:38:39 +0200
Message-ID: <m2shuxq1ls.fsf@birdie.labs.nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/1qsEdmhg9AKr6rJd8fdlBt8-9do>
Cc: "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] [yang-doctors] Feedback on options for issue #1 in TE tunnel YANG
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2016 13:38:31 -0000

Hi Tarek,

your analysis of available solutions seems correct and exhaustive. Maybe
I don't fully understand option #3 but I think you could achieve a
reasonable level of "object-orientedness" and separation of
technology-specific data by defining appropriate hierarchy of identities
(possibly with multiple inheritance, which is now possible in YANG 1.1),
and then using conditional augments.

As for option #2, the design of schema mount could perhaps include some
means for refering to data nodes and/or definitions in the parent
schema. This would however make the subschema usable only in a specific
context.

Lada

"Tarek Saad (tsaad)" <tsaad@cisco.com> writes:

> Hi YANG doctors,
>
> We have a requirement to reuse generic data across multiple technology model instantiations for model we’re driving in draft-ietf-teas-yang-te. For this, we've identified a number of proposals and tried to summarize them in slides 7-10 in the deck @ http://www.ietf.org/proceedings/96/slides/slides-96-teas-3.pptx
>
> We are seeking your expert advice on the best way of the options to proceed with and whether there’s a precedence in other IETF models that have solved similar issues.
>
> Regards,
> Tarek (and co-authors)
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C