Re: [OSPF] Fwd: YANG modules publication: what to focus on next?

"Acee Lindem (acee)" <acee@cisco.com> Wed, 17 January 2018 17:58 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A5512E04A for <ospf@ietfa.amsl.com>; Wed, 17 Jan 2018 09:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 xDqGRzIeEDHJ for <ospf@ietfa.amsl.com>; Wed, 17 Jan 2018 09:58:06 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C6D12DB71 for <ospf@ietf.org>; Wed, 17 Jan 2018 09:58:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8934; q=dns/txt; s=iport; t=1516211884; x=1517421484; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Xm4lFQN9mAqPVPtmq+tkxIRVUvjD4ljtwqIXjZ2xhEQ=; b=YqmGAlifhjEHFWeLJHcjMAwSnqw6EwUSaJctNKjOETdbdflkIpCPhgZU 3bL3lo8v8/yz+YSFTkWTmuYjXQZgFSq4SgVOHvkR7lKzm7ZcQb4660X86 vQLg39DNfGKJHuEZn1Pla9H4pqqsnTasdUY55qFhNuoTHUyVxs4ZktBf/ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DfAADijV9a/5BdJa1BGhkBAQEBAQEBAQEBAQEHAQEBAQGDQWZ0JweEDIokjl6CApcuFIICChgLhRgCGoRKPxgBAQEBAQEBAQFrKIUjAQEBBAEBIRE6FwQCAQgRAwEBAQMCJgICAiULFQgIAgQBEhqKGRA0pU+CJ4lOAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBD4VCg0CDLoMvAQEBAQEBgTUYAQEeF4MAgmUFileHVZFAAogMjUWCGYYdi12NQ4k/AhEZAYE7AR85gVBvFT2CKoRXeAGJX4ElgRcBAQE
X-IronPort-AV: E=Sophos;i="5.46,372,1511827200"; d="scan'208";a="57385913"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2018 17:58:03 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w0HHw3n0004219 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 17 Jan 2018 17:58:03 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 17 Jan 2018 12:58:02 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Wed, 17 Jan 2018 12:58:02 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "t.petch" <ietfc@btconnect.com>, "ospf@ietf.org" <ospf@ietf.org>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
Thread-Topic: [OSPF] Fwd: YANG modules publication: what to focus on next?
Thread-Index: AQHTj7taMLBc4/dpGkuCgtPUVjMADKN4WeiA
Date: Wed, 17 Jan 2018 17:58:02 +0000
Message-ID: <D684F85E.ECD35%acee@cisco.com>
References: <2a8653ac-eee8-3ced-4644-23c04cf87a51@cisco.com> <2a1609c9-e31c-eed6-c292-0ea205d547f5@cisco.com> <027201d38fbb$291b7d00$4001a8c0@gateway.2wire.net>
In-Reply-To: <027201d38fbb$291b7d00$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1788835F4E8A0B4EAF30FEE3D8CBF36A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/b2BPDk2WJYOuQzwyGzPGzbdGReo>
Subject: Re: [OSPF] Fwd: YANG modules publication: what to focus on next?
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 17:58:09 -0000

I’ve been bitten by that many times. It is isis-wg@ietf.org. However, it
doesn’t matter since the mail is being co-posted in anticipation of a
single Link-State Routing WG.

Thanks,
Acee 

On 1/17/18, 12:46 PM, "OSPF on behalf of t.petch" <ospf-bounces@ietf.org
on behalf of ietfc@btconnect.com> wrote:

>Benoit
>
>I just got a bounce telling me that the mailing list of the second of
>the WG you sent this to, the one whose name causes my e-mails to be
>blackholed, does not exist - I think that there should be a -wg at the
>end.
>
>Tom Petch
>
>
>----- Original Message -----
>From: "Benoit Claise" <bclaise@cisco.com>
>To: <ospf@ietf.org>; <isis@ietf.org>
>Sent: Tuesday, January 16, 2018 11:30 AM
>Subject: [OSPF] Fwd: YANG modules publication: what to focus on next?
>
>
>> Dear all,
>>
>> So that you know that draft-ietf-ospf-yang and
>> draft-ietf-isis-yang-****-cfg are bottlenecks to publish many YANG
>> modules. Please progress them asap.
>>
>> Regards, Benoit
>>
>>
>> -------- Forwarded Message --------
>> Subject: YANG modules publication: what to focus on next?
>> Date: Tue, 16 Jan 2018 12:27:01 +0100
>> From: Benoit Claise <bclaise@cisco.com>
>> To: NETMOD Working Group <netmod@ietf.org>
>>
>>
>> Dear all,
>>
>> At the last IETF meeting, Alia, Deborah and I looked at the
>publication
>> status of most YANG modules.
>> Since that time, I've been keeping a summary of the situation. Let me
>> share it with everybody.
>>
>> Before publishing YANG modules, we have two series of bottlenecks:
>> - the YANG module import (shown by tooling below)
>> - the normative references (MISSREF in the RFC editor queue
>> <https://www.rfc-editor.org/current_queue.php>)
>>   Note that draft-ietf-netmod-revised-datastores, a normative
>reference
>> for many YANG modules,
>>   was just approved. Good news!
>>
>> We now have many YANG modules in RFC editor queue:
>> ***draft-ietf-lime-yang-connectionless-oam-18
>>
><https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oa
>m>**
>> ****draft-ietf-lime-yang-connectionless-oam-methods-13
>>
><https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oa
>m-methods>**
>> ****draft-ietf-i2rs-yang-l3-topology-16
>> <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology>**
>> ****draft-ietf-i2rs-yang-network-topo-20
>> <https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-network-topo>**
>> ****draft-wu-l3sm-rfc8049bis-11
>> <https://datatracker.ietf.org/doc/draft-wu-l3sm-rfc8049bis>****
>> **draft-ietf-netconf-rfc6536bis-09
>> <https://datatracker.ietf.org/doc/draft-ietf-netconf-rfc6536bis>
>> *draft-ietf-netmod-rfc7223bis-03
>> <https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7223bis/>
>> draft-ietf-netmod-rfc7277bis-03
>> <https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7277bis/>
>> draft-ietf-rtgwg-yang-vrrp-09
>> <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-vrrp/>
>> draft-ietf-rtgwg-yang-rip-08
>> <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rip/>
>> draft-ietf-netmod-revised-datastores-10
>>
><https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/>
>>
>> Here are the YANG module dependencies
>>
><https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=i
>etf-ip&modules[]=ietf-connectionless-oam&modules[]=ietf-lime-time-types&
>modules[]=ietf-connectionless-oam-methods&modules[]=ietf-l3-unicast-topo
>logy&modules[]=ietf-l3-unicast-topology-state&modules[]=ietf-network-top
>ology&modules[]=ietf-network-topology-state&modules[]=ietf-network&modul
>es[]=ietf-network-state&modules[]=ietf-l3vpn-svc&modules[]=ietf-netconf-
>acm&modules[]=ietf-interfaces&modules[]=ietf-vrrp&modules[]=ietf-rip&mod
>ules[]=ietf-datastores&modules[]=ietf-origin&recurse=1&rfcs=1&show_subm=
>1&show_dir=dependencies>
>> for these RFC editor modules, as requirement before publishing.
>>
>> Some more YANG modules are on the IESG table:
>>   draft-ietf-pim-yang has a DISCUSS (Jan 11th IESG telechat)
>>   draft-ietf-netmod-rfc8022bis is on the Jan 25th IESG telechat
>>   draft-ietf-netmod-entity is on the Jan 25th IESG telechat
>>
>> Assuming those are in the RFC editor queue, this is the new set of
>YANG
>> module dependencies
>>
><https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=i
>etf-ip&modules[]=ietf-connectionless-oam&modules[]=ietf-lime-time-types&
>modules[]=ietf-connectionless-oam-methods&modules[]=ietf-l3-unicast-topo
>logy&modules[]=ietf-l3-unicast-topology-state&modules[]=ietf-network-top
>ology&modules[]=ietf-network-topology-state&modules[]=ietf-network&modul
>es[]=ietf-network-state&modules[]=ietf-l3vpn-svc&modules[]=ietf-netconf-
>acm&modules[]=ietf-interfaces&modules[]=ietf-vrrp&modules[]=ietf-rip&mod
>ules[]=ietf-pim-dm&modules[]=ietf-pim-base&modules[]=ietf-pim-sm&modules
>[]=ietf-pim-bidir&modules[]=ietf-pim-rp&modules[]=ietf-routing&modules[]
>=ietf-ipv6-router-advertisements&modules[]=ietf-ipv4-unicast-routing&mod
>ules[]=ietf-ipv6-unicast-routing&modules[]=ietf-entity&modules[]=ietf-da
>tastores&modules[]=ietf-origin&recurse=1&rfcs=1&show_subm=1&show_dir=dep
>endencies>.
>> It takes a little bit of re-arrangering the elements, but all the
>> information is there.
>>
>> The next bottlenecks for publishing those YANG modules are:
>>   draft-ietf-netmod-schema-mount
>>   draft-ietf-rtgwg-ni-model
>>   ietf-bfd-yang
>>   draft-ietf-ospf-yang
>>   draft-ietf-
>> Please progress those documents asap
>>
>> Some more updates below.
>>
>> _NI, LNE, and schema mount, RFC7895bis, schema mount:_
>>   draft-ietf-rtgwg-lne-model
>>   Status: Publication requested, Alia's AD review
>>   draft-ietf-rtgwg-ni-model
>>   Status: Publication requested, Alia's AD review
>>   draft-ietf-netmod-schema-mount:
>>   Status: WG LC closed, not sure on the next steps ...
>>   draft-ietf-netconf-rfc7895bis
>>   Status not clear...
>>
>> _LIME:_
>> draft-ietf-lime-yang-connection-oriented-oam-model-00
>>   Status: Benoit to perform the AD review.
>>
>> Regards, Benoit
>>
>
>
>------------------------------------------------------------------------
>--------
>
>
>> _______________________________________________
>> OSPF mailing list
>> OSPF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ospf
>>
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf