Re: Blog: YANG Really Takes Off in the Industry

Benoit Claise <bclaise@cisco.com> Mon, 08 December 2014 09:32 UTC

Return-Path: <bclaise@cisco.com>
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 DFF6D1A87AE for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 01:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.51
X-Spam-Level:
X-Spam-Status: No, score=-9.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, 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 eaVboBPufo80 for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 01:32:38 -0800 (PST)
Received: from bgl-iport-4.cisco.com (bgl-iport-4.cisco.com [72.163.197.28]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67F281A8738 for <ietf@ietf.org>; Mon, 8 Dec 2014 01:32:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8851; q=dns/txt; s=iport; t=1418031157; x=1419240757; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=JIo04VQTmwbT5G5+xoXCLUseZEiRyv4+00qFst50bKA=; b=LDACIucI0FMtZ9shGCCfSkIfPYRCS9IfXMxLOw1mf/ZNhYAO6ig/04Kt XUeS7qNnBwdTZ4r6GIEjx1aTJrixrodfyJAag6e2ntksmNP+j3mssYOpX VlMp3XhlWE1eRJJjeJXK4TXtBrp4fOXZldl5EycsJ+6WBTaClFoPfm0UU s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At0EACpvhVRIo8UY/2dsb2JhbABag1hYxhQBCYYTAoE7AQEBAQF9hAMBAQQBAQF1ARALGAkWCAcJAwIBAgEVHxEGDQEFAgEBEIgnDdRNAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSKU4V8B4Q2BYQikxiCJYZvjFCDcD4wgkMBAQE
X-IronPort-AV: E=Sophos; i="5.07,537,1413244800"; d="scan'208,217"; a="17813051"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-4.cisco.com with ESMTP; 08 Dec 2014 09:32:31 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by bgl-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sB89WNRY011002; Mon, 8 Dec 2014 09:32:26 GMT
Message-ID: <54857027.6080107@cisco.com>
Date: Mon, 08 Dec 2014 10:32:23 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: Re: Blog: YANG Really Takes Off in the Industry
References: <54770BA5.5060603@cisco.com> <809EFD2B-A845-46B7-A394-A9C9E5393CD5@piuha.net> <547874D6.1090001@cisco.com> <7890AE32-F7A9-4C32-9C3D-8251E70B1F29@lucidvision.com>
In-Reply-To: <7890AE32-F7A9-4C32-9C3D-8251E70B1F29@lucidvision.com>
Content-Type: multipart/alternative; boundary="------------050105080207060805020408"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xI6ZhT_1gBQedssjJDGneNeXv5U
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, 08 Dec 2014 09:32:41 -0000

Hi Tom,

In light of the numerous YANG models these days, there is the YANG 
doctors scaling issue. You're right, even if the number of YANG doctors 
recently increased, we need other venues to provide advice to YANG model 
designers. This should solve the issue of designing properly the YANG 
models.
On the other hand, there is a bigger issue, IMO: the proper coordination 
of those YANG models. This is not the YANG doctors responsibility. This 
can't be: see the YANG doctors scalability issue.  So who's 
responsibility is this? Simply asserting "it's the community 
responsibility" is the easy answer, but I'm afraid it will not work.

Regards, Benoit
>
> One of the things that came up in a number of discussions I had in 
> Hawaii and afterwards was around the coordination and encouragement 
> topics. A number of people commented both during these discussions 
> (and I think someone did during one of the Netmod sessions) that the 
> “MIB Doctor” model we are using is not going to scale out to the 
> numbers of Yang models that are in need of advice or review, nor will 
> be scale in terms of progressing models through the IETF’s RFC 
> process. The fact is that we simply do not have enough Yang Doctors to 
> cover all of the models in question, despite our best efforts.   It is 
> for this reason that I strongly encourage other venues of review and 
> advice such as a continued “advice” or “Yangathon” session at each 
> IETF meeting going forward, as well as encouraging a loosening of the 
> interim WG meeting rules to encourage more meetings, as well as 
> perhaps less formalized ones.  I also encourage the IETF to start 
> pairing up with other organizations such as OpenDaylight, Openstack 
> and OP-NFV and join their Yangathons there.
>
> —Tom
>
>
>
>> On Nov 28, 2014:8:12 AM, at 8:12 AM, Benoit Claise <bclaise@cisco.com 
>> <mailto:bclaise@cisco.com>> wrote:
>>
>> Hi Jari,
>>
>> Let me open the discussion.
>> What is important at this point in time is the coordination of those 
>> YANG models.
>> All of them come at the same time, and this required some urgent 
>> attention.
>> Focusing on the routing YANG models with "Rtg-yang-coord@ietf.org" 
>> <Rtg-yang-coord@ietf.org> 
>> <https://www.ietf.org/mailman/listinfo/rtg-yang-coord> is a step in 
>> the right direction. Indeed the community needs to agree on how to 
>> model IGPs, BGP, the topology, etc...
>> However, the coordination should also occur with the data models 
>> developed in other IETF WGs. And the IETF might need to reach out to 
>> different SDOs/consortia.
>> As the operators told me: we can't afford to develop those data 
>> models independently from each others.
>>
>> Regards, Benoit
>>> Thanks for writing this article, Benoit!
>>>
>>> The wave of new data models is obviously interesting and exciting. But I wanted to open a discussion with you all on what we should do with regards to serving this need better. Is there something that we could do better at the IETF to be able deal with this new work?
>>>
>>> Jari
>>>
>>
>