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

Benoit Claise <bclaise@cisco.com> Thu, 30 July 2015 13:28 UTC

Return-Path: <bclaise@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 488651A886B; Thu, 30 Jul 2015 06:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, 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 WxwCgDL_oDOZ; Thu, 30 Jul 2015 06:28:51 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 907EC1A8931; Thu, 30 Jul 2015 06:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1841; q=dns/txt; s=iport; t=1438262930; x=1439472530; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=A+yXipNvRMKf/XMuv2jcED26PpiXtdeJjqZLcpDSTIs=; b=SxhvzlrHtv92ciuj10O2+gpwLgrah6Or8eMcKu4rzQe7PwTaNxW5m7yY XYzxq2+Eb7PGVuYVFGkWHpkFya2Sv+fE3YWwMbao2QYth2fTqrP9VW8yH gEvOYYD4Ij+qqmvdL58rLrV66myDQo14fAQFHUwW9zh7J5wY5IJ4v8+Cw E=;
X-IronPort-AV: E=Sophos;i="5.15,577,1432598400"; d="scan'208";a="589855319"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 30 Jul 2015 13:28:49 +0000
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t6UDSmuR025858; Thu, 30 Jul 2015 13:28:48 GMT
To: Nadeau Thomas <tnadeau@lucidvision.com>, Rob Shakir <rjs@rob.sh>, "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>, YANG Doctors <yang-doctors@ietf.org>, Berger Lou <lberger@labn.net>, "Acee Lindem (acee)" <acee@cisco.com>, Loa Andersson <loa@pi.nu>
References: <D1DAB06D.298C6%acee@cisco.com> <etPan.55b60a41.3b25a484.755b@piccolo.local> <FD8CBA1C-AF7D-47EE-A469-A6361EF00D8F@lucidvision.com> <20150730093112.GD16332@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <55BA2690.1000808@cisco.com>
Date: Thu, 30 Jul 2015 15:28:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <20150730093112.GD16332@elstar.local>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/ng5fGnIyh68_QqSckl6KjJI98fQ>
Subject: Re: [Rtg-yang-coord] [yang-doctors] 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: Thu, 30 Jul 2015 13:28:52 -0000

On 30/07/2015 11:31, Juergen Schoenwaelder wrote:
> On Mon, Jul 27, 2015 at 06:06:49AM -0700, Nadeau Thomas wrote:
>> 	Speaking as NETMOD co-chair:
>>
>> 	This is precisely why we are doing this effort and the others in the way that we are - across areas, with a wide enough group of people involved to hopefully cover the real requirements not just say server implementations, or client implementations - we want to cover those and operators who would using them.  So if one of the outputs of a DT is to conclude that the existing standard models are insufficient, then we will work to revise them.  The DTs should strive to recycle what is there as much as possible, but if in the end it is insufficient there is no other option.  So in summary: The DT should not believe that it is constrained to using only existing models as-is,
>>
> Tom,
>
> the value of standards is their stability and that we do not change
> them every other day. In other words, someone proposing to redo a
> standard must have very strong arguments that the current one is
> fundamentally flawed and unusable. And these arguments should in my
> view be brought to the place where the affected standards were
> created.
>
> If the routing area starts to work on the premise that published IETF
> standards will be redone based on some ideas originating from a DT but
> without agreement of the people who were involved in creating and
> implementing the standard, then I think we have a problem.
This is the reason why we organized a NETMOD interim meeting on the YANG 
model structure in June (and another one on the oper status btw).
Unfortunately, some key openconfig people were not in Prague to discuss 
further. Another NETMOD interim is the way to go. Currently in 
discussion with the NETMOD chairs.

Regards, Benoit
>
> /js
>