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

"Tarek Saad (tsaad)" <tsaad@cisco.com> Tue, 13 September 2016 01:59 UTC

Return-Path: <tsaad@cisco.com>
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 56BC912B192; Mon, 12 Sep 2016 18:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level:
X-Spam-Status: No, score=-16.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Y3xaWAvh14JZ; Mon, 12 Sep 2016 18:59:31 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72BEF12B18E; Mon, 12 Sep 2016 18:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3330; q=dns/txt; s=iport; t=1473731971; x=1474941571; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=POjDmRZ/wJZITaSQmgjyXPpzgHFpaEKct1OGFYsnjxY=; b=MyEmTTPj0w/F9V+Pu6YJuno2Sz7glb5DiRHDVez0QpERmIr6BqLwV1vi uPhGGHDSzLD0kbopfgUtPT2FJYeIccJ/tnbhLdnWEdlwhhE0YWIiKTaU/ aIotcbw0kMt3gFQMwJD8k818Rk5Qf3Dt3pDtPpR2KWU+WXqyCFzhE+9OI k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CqAQD+XNdX/40NJK1dGgEBAQECAQEBAQgBAQEBgzoBAQEBAR5XfAeNLKYMhRKCAxkLhXkCHIEqOBQBAgEBAQEBAQFeJ4RiAQEDAQEBASARNwMLEAIBCBoCJgICAiULFRACBAENBQkSiCcIDrFrjDwBAQEBAQEBAQEBAQEBAQEBAQEBAQEcgQaFKoF5CIJPhEEXgmsrghIdBZljAYdah3GBbo10hneFXoN6AR42hFtwAYYvfwEBAQ
X-IronPort-AV: E=Sophos;i="5.30,326,1470700800"; d="scan'208";a="150495882"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Sep 2016 01:59:18 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u8D1xIKM031470 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Sep 2016 01:59:18 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 12 Sep 2016 21:59:17 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1210.000; Mon, 12 Sep 2016 21:59:17 -0400
From: "Tarek Saad (tsaad)" <tsaad@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Ladislav Lhotka <lhotka@nic.cz>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] Feedback on options for issue #1 in TE tunnel YANG
Thread-Index: AQHR40+/+ckpgGliikuVQKDwySwMQqApcCKAgETylgCACJuFAA==
Date: Tue, 13 Sep 2016 01:59:17 +0000
Message-ID: <9B92CD59-7846-4280-8FC8-C5F724056E7B@cisco.com>
References: <5717BEB6-46B6-47EB-BE9B-F8A5AE2E8EFB@cisco.com> <m2shuxq1ls.fsf@birdie.labs.nic.cz> <fff07100-d73b-6270-ace5-26889ca48d51@cisco.com>
In-Reply-To: <fff07100-d73b-6270-ace5-26889ca48d51@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.19.0.160817
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.243.103]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F55E63746B1823448513D49A35B397E4@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/44tqKpdzRNu-mHGmH3nlYNl6ahI>
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: Tue, 13 Sep 2016 01:59:33 -0000

Hi Benoit/Yang Drs,

Thanks, and sorry for delayed response. We discussed this amongst the authors. From Lada’s response, we are interested in functionality extension he mentioned below. I am not sure if the authors of “draft-ietf-netmod-schema-mount” have this planned in their next version update or not. However, if not, we will consider the way to proceed from our side with the remaining other options.

    > 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.

Regards,
Tarek

On 2016-09-07, 6:32 AM, "Benoit Claise (bclaise)" <bclaise@cisco.com> wrote:

    Tarek,
    
    Do you have the answers you need?
    
    Regards, B.
    > 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