Re: [netmod] Blog: YANG Really Takes Off in the Industry

Dean Bogdanovic <deanb@juniper.net> Mon, 01 December 2014 21:26 UTC

Return-Path: <deanb@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0411A90BC for <ietf@ietfa.amsl.com>; Mon, 1 Dec 2014 13:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 6K7DTINbefhe for <ietf@ietfa.amsl.com>; Mon, 1 Dec 2014 13:26:20 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0723.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::723]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A35901ABC10 for <ietf@ietf.org>; Mon, 1 Dec 2014 13:25:46 -0800 (PST)
Received: from BN1PR05MB423.namprd05.prod.outlook.com (10.141.58.146) by BN1PR05MB438.namprd05.prod.outlook.com (10.141.58.12) with Microsoft SMTP Server (TLS) id 15.1.26.15; Mon, 1 Dec 2014 21:25:24 +0000
Received: from BN1PR05MB424.namprd05.prod.outlook.com (10.141.58.148) by BN1PR05MB423.namprd05.prod.outlook.com (10.141.58.146) with Microsoft SMTP Server (TLS) id 15.1.26.15; Mon, 1 Dec 2014 21:25:22 +0000
Received: from BN1PR05MB424.namprd05.prod.outlook.com ([169.254.8.145]) by BN1PR05MB424.namprd05.prod.outlook.com ([169.254.8.84]) with mapi id 15.01.0026.003; Mon, 1 Dec 2014 21:25:22 +0000
From: Dean Bogdanovic <deanb@juniper.net>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: Re: [netmod] Blog: YANG Really Takes Off in the Industry
Thread-Topic: [netmod] Blog: YANG Really Takes Off in the Industry
Thread-Index: AQHQCjpTcdFHWvvEy0mHnKnSCcZk/5x6K1QAgABBWQCAAGqzgIAAbskA
Date: Mon, 01 Dec 2014 21:25:22 +0000
Message-ID: <996DA5DA-BD25-454B-A871-198782798391@juniper.net>
References: <54770BA5.5060603@cisco.com> <5B0D568E-9F17-49A9-8E0C-7F202E02464D@juniper.net> <547C2650.8090806@cisco.com> <B3A36D25-EFCD-4002-9996-957751EAF8A4@lucidvision.com>
In-Reply-To: <B3A36D25-EFCD-4002-9996-957751EAF8A4@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.1510)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.14]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB423;UriScan:;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB423;
x-forefront-prvs: 0412A98A59
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(199003)(377454003)(24454002)(189002)(101416001)(106116001)(92726001)(92566001)(50986999)(76176999)(15202345003)(66066001)(93886004)(87286001)(95666004)(88136002)(99286002)(104166001)(89996001)(87936001)(20776003)(2656002)(106356001)(40100003)(105586002)(83716003)(46102003)(16236675004)(33656002)(36756003)(19580395003)(19580405001)(99396003)(77096004)(107046002)(120916001)(50226001)(122556002)(4396001)(31966008)(57306001)(19617315012)(110136001)(93916002)(77156002)(21056001)(64706001)(62966003)(97736003)(15975445006)(86362001)(68736005)(82746002)(104396001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB423; H:BN1PR05MB424.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_996DA5DABD25454BA871198782798391junipernet_"
MIME-Version: 1.0
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB438;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CWy22GTbafYCCjiNiVRbK6kp3Mw
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 21:26:22 -0000

Tom,

See in-line
On Dec 1, 2014, at 9:48 AM, Thomas D. Nadeau <tnadeau@lucidvision.com<mailto:tnadeau@lucidvision.com>> wrote:


On Dec 1, 2014:3:26 AM, at 3:26 AM, Benoit Claise <bclaise@cisco.com<mailto:bclaise@cisco.com>> wrote:

Dean,

See in-line.
Benoit,

You describe the situation really well, but as next step we have to get more organized and more coordination in modeling work. We have to make sure that there is not too much overlap between efforts, not too waste resources
... and inconsistencies between data models, which is my primary concern.

Let's take one example: policies. I see policies in many YANG models. How do we make sure the policie definitions are consistent and extensible? How can we coordinate this (huge) effort? Who is in charge? The collective responsibility might not be enough…

Coordination is only one issue: its operational efficacy that is also of paramount importance here. We should do what we’ve done in NETMOD's “design teams”: pair up people that are truly implementing functionality in real or virtual devices with operators to ensure that the models created are grounded in the realities of implementation and deployment.

I agree with you on operational efficacy, but as there are more and more models, I see some duplication work, so I really see a need to get a meta architecture asap, so that the teams can be more efficient.

Dean


—Tom



and as well create an architecture description document, where the relationship between models will be described. With that we can see which models can be reused as base model in other models.
Good example of coordination is the rtg-coord-yang mailing list, but we need one for all IETF, to be able to find what are other the teams working on.
Right.

Regards, Benoit

We should not let this momentum go away and with few simple steps (like improving coordination and system meta architecture), continue to feed positive energy into this situation.

Dean
On Nov 27, 2014, at 6:31 AM, Benoit Claise <bclaise@cisco.com<mailto:bclaise@cisco.com>> wrote:

Dear all,

[netmod WG list is bcc'ed]

Enjoy http://www.ietf.org/blog/2014/11/yang-really-takes-off-in-the-industry/

Regards, Benoit


_______________________________________________
netmod mailing list
netmod@ietf.org<mailto:netmod@ietf.org>
https://www.ietf.org/mailman/listinfo/netmod