IETF Logo Mail Archive

Re: [netmod] AD review of draft-ietf-netmod-rfc6021-bis-00.txt

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sun, 24 March 2013 19:07 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFCF21F8576 for <netmod@ietfa.amsl.com>; Sun, 24 Mar 2013 12:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.189
X-Spam-Level:
X-Spam-Status: No, score=-103.189 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHsJsc-9F9lE for <netmod@ietfa.amsl.com>; Sun, 24 Mar 2013 12:07:22 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED2921F856D for <netmod@ietf.org>; Sun, 24 Mar 2013 12:07:22 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id A70C820BDB; Sun, 24 Mar 2013 20:07:21 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id VzDqn2s10r7X; Sun, 24 Mar 2013 20:07:21 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1855220BDA; Sun, 24 Mar 2013 20:07:21 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 3E7CB252E3E1; Sun, 24 Mar 2013 20:07:24 +0100 (CET)
Date: Sun, 24 Mar 2013 20:07:24 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ladislav Lhotka <lhotka@nic.cz>
Message-ID: <20130324190724.GA20421@elstar.local>
Mail-Followup-To: Ladislav Lhotka <lhotka@nic.cz>, Benoit Claise <bclaise@cisco.com>, NETMOD Working Group <netmod@ietf.org>
References: <514C93E9.8@cisco.com> <m2obebl34w.fsf@nic.cz> <20130322210354.GA16103@elstar.local> <514CDAE7.401@cisco.com> <CA22DC74-281B-4EAF-A7E4-8DD0E94C4176@nic.cz> <20130324092107.GA19518@elstar.local> <5162BD50-7673-4BBD-AAD7-A297ABE29906@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5162BD50-7673-4BBD-AAD7-A297ABE29906@nic.cz>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: NETMOD Working Group <netmod@ietf.org>
Subject: Re: [netmod] AD review of draft-ietf-netmod-rfc6021-bis-00.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2013 19:07:23 -0000

On Sun, Mar 24, 2013 at 05:18:29PM +0100, Ladislav Lhotka wrote:
> 
> YANG change rules require strict backward compatibility. I am afraid it is counterproductive at this stage because our initial YANG modules generally get published before they have been thouroughly tested. It would be quite daring to think that our work is flawless, despite all the effort we put in it. What if we publish the routing module and then get feedback from protocol implementors or I2RS, indicating that something should be changed, and this something breaks compatibility?
> 
> I believe errors should be corrected and significant improvements implemented, and the sooner the better. It will be much harder after a module becomes widely used.
> 

If something is seriously flawed, it can be deprecated or even made
historic and you start a second attempt. All this is possible.
Changing the semantics of an existing published definition is
generally a no go.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

v2.23.0 | Report a Bug | By Email