IETF Logo Mail Archive

Re: Yang update from IESG ?

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 19 November 2019 05:26 UTC

Return-Path: <mcr@sandelman.ca>
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 51972120048; Mon, 18 Nov 2019 21:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.436
X-Spam-Level: *
X-Spam-Status: No, score=1.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 OFMbO-wQgoQ5; Mon, 18 Nov 2019 21:26:35 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC48120013; Mon, 18 Nov 2019 21:26:34 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:e86e:6eff:fe36:f4b7]) by relay.sandelman.ca (Postfix) with ESMTPS id 233341F450; Tue, 19 Nov 2019 05:26:33 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 0E71D137A; Tue, 19 Nov 2019 13:26:32 +0800 (+08)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "iesg@ietf.org" <iesg@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Yang update from IESG ?
In-reply-to: <CADyWQ+Eh3ULpfRp-Bg6R9V6veWS3d0Ry_zEgP7FuL2L6djhDjA@mail.gmail.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>
Comments: In-reply-to Tim Wicinski <tjw.ietf@gmail.com> message dated "Mon, 18 Nov 2019 22:49:15 +0800."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 19 Nov 2019 13:26:32 +0800
Message-ID: <7631.1574141192@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NAh0qPZmnGCfftF6nWR0KfhDS2A>
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: Tue, 19 Nov 2019 05:26:39 -0000

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?

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email