IETF Logo Mail Archive

Re: Yang update from IESG ?

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Mon, 18 November 2019 16:55 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
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 5859F120121 for <ietf@ietfa.amsl.com>; Mon, 18 Nov 2019 08:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 iML2mZup8prl for <ietf@ietfa.amsl.com>; Mon, 18 Nov 2019 08:55:47 -0800 (PST)
Received: from mail-pj1-f46.google.com (mail-pj1-f46.google.com [209.85.216.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CD7F120045 for <ietf@ietf.org>; Mon, 18 Nov 2019 08:55:47 -0800 (PST)
Received: by mail-pj1-f46.google.com with SMTP id y21so1659727pjn.9 for <ietf@ietf.org>; Mon, 18 Nov 2019 08:55:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ChZE6syj17k6k8y9dPU6F/GQmLXqeqbw54T426dpNMU=; b=S9LjyVOu3yAFsul5Z59iJkMe3X07kwER82hrjUeU9H+o/93h9Z9frDgvZ+d9qy6DN0 4F2arrEjI7/iyBjdwLcnAU2fIiaOG5XcxGaeJLX9tn9tsVFXGBsDsHWkT6u5byI2/bmX SrKkssvE81VLB+L7lLcSZfl0cYnKTUbyOCcq6fQW6hQBBaxsnkOXuN1/+0kDHCMRknsw uReIQCgdMWHg71AP2pY+XbyZWG2+vMC6iB8JXcTUrxLhcK+kj5isNahGp8UtZpu9sp2x ua9yCZgSZ/AzsOo3ZxErtlGpobbSyUjvkTe2Z3mgnaISyL1my85wlKQVOE0S32wXe3sS xWqw==
X-Gm-Message-State: APjAAAWAPQXYvoZd1PMGhNYgCbaaSLLiuIeuGi2mHTAYw+IkShcbJFfY mBxxgVPvT6TzHA7uTdsFcuyrbBzjtUM=
X-Google-Smtp-Source: APXvYqzvhSCP6TtRSb877ADpCGt8Z3m9u7pScutbTzDwSEeCDI1qqDREV3qtMeRYi+dznLTqFQM8kg==
X-Received: by 2002:a17:902:b612:: with SMTP id b18mr30580514pls.210.1574096146514; Mon, 18 Nov 2019 08:55:46 -0800 (PST)
Received: from [192.168.1.105] (c-73-231-235-186.hsd1.ca.comcast.net. [73.231.235.186]) by smtp.gmail.com with ESMTPSA id c12sm22244877pfp.178.2019.11.18.08.55.45 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Nov 2019 08:55:46 -0800 (PST)
Subject: Re: Yang update from IESG ?
To: ietf@ietf.org
References: <alpine.LRH.2.21.1911131435240.22669@bofh.nohats.ca> <359EC4B99E040048A7131E0F4E113AFC01E70B0061@marchand> <alpine.LRH.2.21.1911180102380.9256@bofh.nohats.ca> <a130f7c9d82299f8975ba9a9e8a2e4a6445878b4.camel@nic.cz>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <6d9fae63-e2f1-0806-ccf8-8d0118e4ff35@alumni.stanford.edu>
Date: Mon, 18 Nov 2019 08:55:44 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <a130f7c9d82299f8975ba9a9e8a2e4a6445878b4.camel@nic.cz>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Antivirus: Avast (VPS 191117-0, 11/17/2019), Outbound message
X-Antivirus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bJibqRpSzCDpz69yZb4O5WEtXNM>
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: Mon, 18 Nov 2019 16:55:48 -0000

Hi -

On 11/17/2019 11:05 PM, Ladislav Lhotka wrote:
...
 > The snapshot should represent the consensus of a corresponding 
working group
 > regarding the best way of modelling a given IANA registry in YANG. 
After the
 > publication of that RFC, IANA is expected to update the YANG module 
along with
 > the registry so as to keep both in sync.
...

Have you considered doing what the ltru WG did in the course of 
producing BCP 47?
The I-D handed off to the RFC editor had a working copy of the registry 
content,
with instructions to remove that portion of the content upon 
publication.  It required
a little coordination with IANA, but avoided the problem of anyone ever 
mistaking
the RFC for the registry.  The same might be a possible course of action 
with modules
like these.

Randy

v2.23.0 | Report a Bug | By Email