IETF Logo Mail Archive

Re: [Rtg-yang-coord] Routing YANG Design Team Scope

"Acee Lindem (acee)" <acee@cisco.com> Tue, 28 July 2015 18:29 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8B31B2D5F; Tue, 28 Jul 2015 11:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 HUa8yQezFoOg; Tue, 28 Jul 2015 11:29:16 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5A01B2D23; Tue, 28 Jul 2015 11:29:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7528; q=dns/txt; s=iport; t=1438108155; x=1439317755; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ok1ZhRfvk9uSssm66wqlYotMwUGHF5aAiOSADhdlCKs=; b=YTDYUt//loFL+b1jFKutfVbpngABb8szPDN2RG4Iilji/B0Hfa2OJqyU 2cdtAkE+0vvsblAi7Y0NYL3Skcok6YNAmfwudz2R0Qe0ohkLzkLVa4bNf ls+8BJ90wU0L1xQmkLu1Sy02LCzMB+cHdZR+lkFxFHSeDXc6+/myt8jW+ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AABABVybdV/49dJa1bgkhNgT0Ggx25EQmHegIcgT04FAEBAQEBAQGBCoQkAQEEI1YQAgEIDjEDAgICHxEUEQIEDgWIGQMSui6QYA2FLwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLToJOgjkHgmkvgRQFlGgBileBapF+hy0mZIMZb4FIgQQBAQE
X-IronPort-AV: E=Sophos;i="5.15,564,1432598400"; d="scan'208,217";a="173340575"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Jul 2015 18:29:15 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t6SITETt004928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Jul 2015 18:29:14 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.37]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Tue, 28 Jul 2015 13:29:14 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Thread-Topic: [Rtg-yang-coord] Routing YANG Design Team Scope
Thread-Index: AQHQyBKPtAZjqBZX7EimmnBlKBFrDZ3vbc2AgABdoICAAXXFgIAAIx+AgAAl9oA=
Date: Tue, 28 Jul 2015 18:29:13 +0000
Message-ID: <02A437FC-64AA-489C-8310-39F677CAF418@cisco.com>
References: <D1DAB06D.298C6%acee@cisco.com> <20150726204927.GA17784@elstar.local> <B2F97D6D-C316-4176-83E3-E08E6F553E9D@gmail.com> <D1DBB3C4.2991F%acee@cisco.com> <022BA705-5EA2-4C4D-B012-EF2946F5F523@gmail.com> <6D8CFA7E-4E24-4FC2-BB69-31F4F436ACFC@cisco.com> <D6BC554B-5349-4DA5-A4A3-228F3D8855DA@gmail.com>
In-Reply-To: <D6BC554B-5349-4DA5-A4A3-228F3D8855DA@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.152.204]
Content-Type: multipart/alternative; boundary="_000_02A437FC64AA489C831039F677CAF418ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/U_qzNR3LDop8rdWcxofGkVw2tGc>
Cc: "rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, YANG Doctors <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Loa Andersson <loa@pi.nu>
Subject: Re: [Rtg-yang-coord] Routing YANG Design Team Scope
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2015 18:29:17 -0000

Mahesh,
The meta model is a “model of models” the proposes a hierarchy. The individual models are separate.
With respect to augmentation, if “grouping” cannot be augmented directly we then must provide containers that can be augmented.
I think you are getting down into the YANG mechanics when the focus should be on the overall model structure. However, the design team is certainly open to suggestions if you have a better representation.
Thanks,
Acee
On Jul 28, 2015, at 12:13 PM, Mahesh Jethanandani <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>> wrote:

Acee,

On Jul 28, 2015, at 7:07 AM, Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:

The networking-instance is used to instantiate separate layer-3 or layer-2 domains as opposed to protocol domains. For example, in many implementations, a networking-instance would correspond to a VRF or a Virtual Switch Instance (VSI). Hence, it would not make sense to define a separate networking-instance for MPLS since it is only one piece of a layer-3 domain.

Ok.

Similarly, could oam-protocols, control-plane-protocols, system-management, networking-services be identityrefs also? mpls could be part of tunneling-protocols that would include protocols such as gre.

My concern with the model as it is structured, is its size. Not in terms of code size (because you are using groupings judiciously) but the ultimate size of the tree. I expect the device model to lay the framework for other models to augment the model. In addition, groupings cannot be augmented and if there is a new system-management definition tomorrow, the current structure does not allow for that to be added.

Mahesh Jethanandani
mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>

v2.23.0 | Report a Bug | By Email