IETF Logo Mail Archive

Re: Yang update from IESG ?

Benoit Claise <bclaise@cisco.com> Sun, 24 November 2019 13:43 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E04F9120137; Sun, 24 Nov 2019 05:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 2VOhNReJwsY4; Sun, 24 Nov 2019 05:43:42 -0800 (PST)
Received: from bgl-iport-3.cisco.com (bgl-iport-3.cisco.com [72.163.197.27]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ACF51200C5; Sun, 24 Nov 2019 05:43:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1808; q=dns/txt; s=iport; t=1574603022; x=1575812622; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=tnE/3fidoJMgBJz7EciYR7cz8gy0mPvzc11BTht30PM=; b=GTD+fone71H9QWw4CxKpKi3GHhaLYnWI8GhIKK+zL2ATJN9g55Fgodge nSMPddoy6KPpszgEJxzAp2q9VC76OEN/yj4H5KNIl2sS9tO+/jwi2c7vn uVz/YMEixnAPe3rq78YdAI8NnQlapvISDf81IaBFVELrf3v4SUvuZAtWD 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CPAAAeJdpd/xjFo0hlGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF+gwxVIBIqhCqJA4gTiVuRUgkBAQEMAQEjDAEBgUyCdAKCTjgTAhABAQQBAQECAQUEbYULByUMhVMBBSMVQRALGAICJgICITYGAQwGAgEBgx4BgkYDLg+rHRo1dYEyhU+CUQ1jgUIGgQ4ojDCBQD+BESeCbD6CG4U+gl4EjUiJGUWWS0GCNZE8hBIGG4I/jAEnizWOSIFCiQyGFIkuAhEVgWkigVgzGggbFYMnUBEUgWSNa4VMNAMwAY8QAQE
X-IronPort-AV: E=Sophos;i="5.69,237,1571702400"; d="scan'208";a="100168180"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Nov 2019 13:43:39 +0000
Received: from [10.68.217.24] ([10.68.217.24]) (authenticated bits=0) by bgl-core-4.cisco.com (8.15.2/8.15.2) with ESMTPSA id xAODhZ6C008136 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Sun, 24 Nov 2019 13:43:38 GMT
Subject: Re: Yang update from IESG ?
To: Michael Richardson <mcr+ietf@sandelman.ca>, Ladislav Lhotka <lhotka@nic.cz>
Cc: "iesg@ietf.org" <iesg@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>, Dave Thaler <dthaler@microsoft.com>
References: <alpine.LRH.2.21.1911131435240.22669@bofh.nohats.ca> <359EC4B99E040048A7131E0F4E113AFC01E70B0061@marchand> <alpine.LRH.2.21.1911180102380.9256@bofh.nohats.ca> <10541.1574083581@dooku.sandelman.ca> <e745d480c113b09eb4f6761cf48ef1e997fc3e6c.camel@nic.cz> <CADyWQ+Eh3ULpfRp-Bg6R9V6veWS3d0Ry_zEgP7FuL2L6djhDjA@mail.gmail.com> <7631.1574141192@dooku.sandelman.ca> <3da578887bfd0db091afc71fbe75c7abc66f157f.camel@nic.cz> <7882.1574153435@dooku.sandelman.ca>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <b62bf648-197b-392c-e5ef-c26c129c3251@cisco.com>
Date: Sun, 24 Nov 2019 21:43:35 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <7882.1574153435@dooku.sandelman.ca>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Authenticated-User: bclaise
X-Outbound-SMTP-Client: 10.68.217.24, [10.68.217.24]
X-Outbound-Node: bgl-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wvJx1OlZmCQmX8e8Bnd92pYFm7c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 24 Nov 2019 13:43:45 -0000

Maybe this is already solved during the IETF week.
If not, read my answer below ..
> Ladislav Lhotka <lhotka@nic.cz> wrote:
>      > On Tue, 2019-11-19 at 13:26 +0800, Michael Richardson wrote:
>      >> Tim Wicinski <tjw.ietf@gmail.com> wrote: >> IANA has been doing it for
>      >> more than five years for a couple of YANG >> modules (six by now), and
>      >> I am not aware of any troubles so far.
>      >>
>      >> > But that's work put onto the IANA pile, and some I* organization may
>      >> > want to understand the commitment.
>      >>
>      >> And, I don't understand how the products get updated.  Are they going
>      >> to pull YANG modules from IANA?  How often: hourly? daily?  yearly?
>
>      > Products get updated ad hoc, as soon as their implementors feel the
>      > need. This usually has to be accompanied with changes in the underlying
>      > system - actually implementing support for new registry entries etc.
>
> So if software (including management software) needs explicit support for new
> IANA entries (in for instance, lists of ciphers), then why is it better for
> the (human) programmer to download a new YANG module than to just read the IANA web
> pages (or .XML equivalent)?
The point is that you download the IANA-maintained YANG modules on 
regular basis (ex: typical interface types) for the management software 
that speaks YANG. A cronjob does the job.
Since the new YANG module is backward compatible, the software works 
automatically (for the new interface type) with the new YANG module. 
Exactly like the IfType defintions for MIB modules (see 
https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml).

Regards, B.
>
> (It's not like the YANG description will have executable code for SHA4 or something)
>

v2.23.0 | Report a Bug | By Email