Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations

"Rob Wilton (rwilton)" <rwilton@cisco.com> Sat, 16 November 2019 09:20 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod-ver-dt@ietfa.amsl.com
Delivered-To: netmod-ver-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90987120103; Sat, 16 Nov 2019 01:20:23 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 header.b=BKDKWB7q; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ATRNOeDP
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 Qgwov3WMwvQR; Sat, 16 Nov 2019 01:20:21 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C19B512008B; Sat, 16 Nov 2019 01:20:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9928; q=dns/txt; s=iport; t=1573896020; x=1575105620; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WAbYwZwP/bGbj6Cezi7HDS0094u4ArY2XKfPVzVt3eI=; b=BKDKWB7qvnnIONWqg4dz1T7YYDqE1fVgXUbe2btSuvSzA0V1oQJ82JCt N3ZMMhx3iJpYOGccEfvNU0XQrNa7Fpir7MAYX6Vo639eJf8ihbvrrPaWp keJfSgEVycgSxeYUfT28OcLp+FkAUaPPL6ijUy9ODvITh1+20HjeWJHvW Q=;
IronPort-PHdr: 9a23:lYahiBfkAlvrmekLH6q5n8relGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dTM7GNhFUndu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAAAIv89d/4ENJK1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYFsAwEBAQELAYFKUAVsWCAECyqEKYNGA4pzgl6YAIEugSQDVAkBAQEMAQEYCwoCAQGDe0UCF4IMJDYHDgIDCwEBBAEBAQIBBQRthTcMhVEBAQEEAQEQCwYRDAEBLAsBCwQCAQgOAwQBAQECAiYCAgIlCxUICAIEAQ0FCBADB4MBgkYDLgECDKR8AoE4iBEaNXWBMoJ+AQEFhSQYghcDBoEOKAGMFBiBQD+BEUaCHi4+gQSBXgEBgWMVgnkygiyNV4I8nhoKgiqVaoI+h2iPa45IgUGYRwIEAgQFAg4BAQWBWQoogVhwFTuCbFARFJEag3OFFIU/dIEokA4BAQ
X-IronPort-AV: E=Sophos;i="5.68,311,1569283200"; d="scan'208";a="652190625"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Nov 2019 09:20:00 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id xAG9K09P011091 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 16 Nov 2019 09:20:00 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 16 Nov 2019 03:19:59 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 16 Nov 2019 03:19:59 -0600
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 16 Nov 2019 04:19:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kWHLlHleMq6d/lgNH+MSYQEVbY1yk49OZTJ4OcxVMTn6dEnAcBz7EnHL1/ACFQBtp3b2cz3WB5t3yoqtIa04dm6aar/7Pwx7tG+9tZvSCOrxq56mKXWKHPmaRQVnKyNNytrtyBG9KGOGXvE/hYafm1eCjJLjEa/DK4O6udCtaMDbFhzMZJDDAD5t5YJOz4PrP9VI+1r7tRGwWu+fNdLBzjmlwBWYPALG0Z9IADgC9Ve18RCkcnReRdrzWTeTvfKqdyiqCwxfAYD7qcu2bfaPOjloOhxzkagC0zzqsbsPcTlm0kWrHeZ7rKkdCn5bO7doQw6xv9A+r15pSCJRAWQUDQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WAbYwZwP/bGbj6Cezi7HDS0094u4ArY2XKfPVzVt3eI=; b=U3owXAJyIvk64CsiD2NCBiQ2ANMeQpgym65CVU2HJJHtxsKqgVvuQWpf1tN0kB3q8Hep1NFFytQLcOvvZ7phZpGDa+cB5kWueFpnALDKle0Y8ngSvxWGUJ8YeaMzN4YVFkybgy3Fgtc5cfNAvcKdbVoOUNL9QGW4mDDQHB8IFd/x+SxQWiJ/LUbvZX0HpNd7jkGZnxcMHNknj2xd1dI6u6kIsnP4i8zThyNshcwIVU99v+cLoX76MnY3XrheVig/QVnRDr4JNhYPEMr03dhKO5lTwVa3vh0H63yAgbj3aiTaHJR94tNIQ2Osp5uVL5JF20tZ7FF2gTrqLGdaHsYhIQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WAbYwZwP/bGbj6Cezi7HDS0094u4ArY2XKfPVzVt3eI=; b=ATRNOeDPhOizKKcznAQckcruykLh28mdjI539mCNRFi9APumXqUsEoVv/cCmdOuYUjAGDe8H3hl4l2Glla3sNeW8npumcdH10czUJmVo/Sucyn0ShyIyqFUNp9OZxWxVqM+jKH/bibnQnSd6uIKEP4Jecv1AP5dc33bsXEmaxW0=
Received: from BY5PR11MB4355.namprd11.prod.outlook.com (52.132.254.141) by BY5PR11MB4212.namprd11.prod.outlook.com (52.132.255.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.28; Sat, 16 Nov 2019 09:19:57 +0000
Received: from BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::44:93bb:6c88:251c]) by BY5PR11MB4355.namprd11.prod.outlook.com ([fe80::44:93bb:6c88:251c%5]) with mapi id 15.20.2451.029; Sat, 16 Nov 2019 09:19:57 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Lou Berger <lberger@labn.net>, NetMod WG Chairs <netmod-chairs@ietf.org>
CC: "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Thread-Topic: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations
Thread-Index: AQHViOqR3+fBe/XhR0ybwAmc5igpjadm8TSAgBEOhQCAAtGsMIAB8zUAgAACRHCAABU4gIAAAgAQgAlrfICAABx70IAABRGAgAc8eVA=
Date: Sat, 16 Nov 2019 09:19:57 +0000
Message-ID: <BY5PR11MB43554A111CE24EE4D433C2F5B5730@BY5PR11MB4355.namprd11.prod.outlook.com>
References: <0100016df4023541-879644c6-353f-4b32-9ccd-96dcd3d5e113-000000@email.amazonses.com> <0100016df49997cc-581feda8-01ed-4980-b8bb-2ffd5d648df9-000000@email.amazonses.com> <619859ba-f5b7-b08d-d928-0d70ad3cffaf@labn.net> <MN2PR11MB4366A6DF5DF4C29F1D97BECAB57F0@MN2PR11MB4366.namprd11.prod.outlook.com> <0a2825d0-a871-f0c3-aca9-4b9c61ee2f07@labn.net> <MN2PR11MB43662722E0F1B65442BAD5E3B57E0@MN2PR11MB4366.namprd11.prod.outlook.com> <bc3b6674-ebaf-e056-1dbe-08a52fb8cc58@labn.net> <MN2PR11MB436655746DE65AF6B9DFDF23B57E0@MN2PR11MB4366.namprd11.prod.outlook.com> <9d0a54b7-a6fb-2bbe-9cb6-4915e2d497ef@labn.net> <MN2PR11MB4366C020FBDA87295862368DB5740@MN2PR11MB4366.namprd11.prod.outlook.com> <4f5d3a85-4d24-8364-66e8-442dd6aff897@labn.net>
In-Reply-To: <4f5d3a85-4d24-8364-66e8-442dd6aff897@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [2001:420:c0d4:1002::ba]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5bd4ed59-75ee-40f4-5c97-08d76a762621
x-ms-traffictypediagnostic: BY5PR11MB4212:
x-microsoft-antispam-prvs: <BY5PR11MB4212B59C529868550BFA748DB5730@BY5PR11MB4212.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02234DBFF6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(39860400002)(346002)(376002)(366004)(396003)(189003)(199004)(13464003)(51444003)(305945005)(7736002)(476003)(316002)(446003)(11346002)(4326008)(486006)(6116002)(33656002)(74316002)(966005)(7696005)(81156014)(14454004)(81166006)(5660300002)(76176011)(478600001)(8676002)(229853002)(86362001)(256004)(8936002)(14444005)(186003)(46003)(25786009)(99286004)(6246003)(110136005)(6436002)(55016002)(66476007)(64756008)(66946007)(102836004)(52536014)(66556008)(66446008)(53546011)(6506007)(6306002)(71200400001)(76116006)(2906002)(71190400001)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4212; H:BY5PR11MB4355.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +Ka5Ux4Fg89h9enpQuDj9m6uKxrbKQF6wVzj5dUiBURTQ94K0k+3SMdCzLQB+ekgOevupozY3v4FPgOqehGJfbjyv+ejQdYHpB8GxPc+lUHYXxB3pAl6s+7kLpHqIO1ErRjIG8cLWQMd12GHxZq5vYkVqbJHJx0OVSDT3a0SKFlB8bnZoo0Mv1T63uEW6Cq0rdN+2Fg7KSb+tVjpia497vJ+L30gz/WrTAvbao5iLvK0PsfcV8AxcJPmAo5uyPnOxl0ta9V2F4V8i8OgHX1f6xSF/SDnCt+7zMHnxKkte69PktMOkngusMIvvj4zeIqa48bMLGwzNvrwgiY8AWs+25eYWZ7LUY7fa5F3Ca10/IYqb7RBnwHa/d5Z+aZUOfDR+ytLa8e1K7OJcnsB/EJo+KzVv+/73lubXcCUNjl4ufwSANApSMeFMdAbmKO1GivT
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5bd4ed59-75ee-40f4-5c97-08d76a762621
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2019 09:19:57.1771 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: LQJOgm4pqb0akeiSAu+UpMTQiaKVSauOuwqQmXKjJyTpQgeY+HOB6LAB06Tuch+aZdgJcLKnArdhitzDGR5nzQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4212
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/UULxelJYpKek0EJivW7PUl9Qc6g>
Subject: Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations
X-BeenThere: netmod-ver-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NetMod WG YANG Model Versioning Design Team <netmod-ver-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod-ver-dt/>
List-Post: <mailto:netmod-ver-dt@ietf.org>
List-Help: <mailto:netmod-ver-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2019 09:20:24 -0000

Hi Lou,

I will post a draft on YANG schema comparison this evening/tomorrow morning.

If time is available, please may I adjust our agenda to:

DT Update overview & status update – Rob Wilton (10 mins)
draft-ietf-netmod-yang-versioning-reqs-01
draft-verdt-netmod-yang-solutions-02

Updated YANG Module Revision Handling –Bo Wu (10 mins)
draft-verdt-netmod-yang-module-versioning-01

YANG Semantic Versioning – Joe Clarke (10 mins)
draft-verdt-netmod-yang-semver-01

YANG Packages – Rob Wilton (25 mins)
draft-rwilton-netmod-yang-packages-02

YANG Schema Version Selection – Joe Clarke (Reshad Rahman) (25 mins)
draft-wilton-netmod-yang-ver-selection-01

YANG Schema Comparison – Rob Wilton (15 mins)
draft-verdt-netmod-yang-schema-comparison-00

Next steps? – Rob Wilton

Thanks,
Rob
 

-----Original Message-----
From: Netmod-ver-dt <netmod-ver-dt-bounces@ietf.org> On Behalf Of Lou Berger
Sent: 12 November 2019 02:33
To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs <netmod-chairs@ietf.org>
Cc: netmod-ver-dt@ietf.org
Subject: Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations

we have plenty of time, so this won't be a problem!

On 11/11/2019 1:16 PM, Rob Wilton (rwilton) wrote:
> Okay ... I'll see if I can put together a rough draft before next week.  If I manage to do this, then I might request a last minute schedule change to add 15 mins to verbally outline the solution.
>
> Thanks,
> Rob
>
>
>> -----Original Message-----
>> From: Netmod-ver-dt <netmod-ver-dt-bounces@ietf.org> On Behalf Of Lou 
>> Berger
>> Sent: 11 November 2019 16:33
>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs 
>> <netmod- chairs@ietf.org>
>> Cc: netmod-ver-dt@ietf.org
>> Subject: Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call 
>> for Presentations
>>
>> Hi,
>>
>> We discussed this today.  Our preference would be for a thin/minimal 
>> draft covering the tooling and the output showing the intended 
>> direction for the work and for this to be included in the set 
>> adoption call.  It really doesn't have to be complete /much -- just 
>> enough to show intended direction.  Hopefully this is minimal enough 
>> effort for it to be submitted quite rapidly.
>>
>> Does that work for you?
>>
>> Thanks,
>>
>> Lou (Joel and Kent)
>>
>> On 11/5/2019 11:43 AM, Rob Wilton (rwilton) wrote:
>>> Ack.  Thanks.
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Lou Berger <lberger@labn.net>
>>>> Sent: 05 November 2019 16:35
>>>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs
>>>> <netmod- chairs@ietf.org>
>>>> Cc: netmod-ver-dt@ietf.org
>>>> Subject: Re: [netmod] NETMOD 106 Schedule and Call for 
>>>> Presentations
>>>>
>>>> I'll discuss with my co-chairs. I think this is also fair to raise 
>>>> at the meeting...
>>>>
>>>> On 11/5/2019 10:49 AM, Rob Wilton (rwilton) wrote:
>>>>> We might like to ask you (the chairs) to reconsider the discussion 
>>>>> as to
>>>> whether we can do a call for adoption on some of these drafts?
>>>>> I know that the chairs have previously wanted to adopt the drafts 
>>>>> as an
>>>> entire set to cover the whole solution.  And we are obviously still 
>>>> missing the draft of schema comparison tooling.  Arguably this 
>>>> draft isn't required for the solution, only strongly desirable to 
>>>> have because it is only intending to address requirement 2.2 (which 
>>>> has always been a SHOULD rather than a MUST):
>>>>>           2.2  A mechanism SHOULD be defined to determine whether data
>>>>>                nodes between two arbitrary YANG module revisions 
>>>>> have
>> (i)
>>>>>                not changed, (ii) changed in a backwards-compatible way,
>>>>>                (iii) changed in a non-backwards-compatible way.
>>>>>
>>>>> Note, there is no intention of dropping this last draft, and we 
>>>>> already
>>>> have some pyang tooling/scripts that perform this task, but I think 
>>>> that it could also realistically follow on a bit after the other
>> drafts.
>>>>> All the "MUST" requirements are intended to be addressed by the 
>>>>> set of
>>>> drafts below.
>>>>> Personally, I think that these 4 drafts are all in good enough 
>>>>> shape
>>>> that they could be considered for an WG adoption call:
>>>>>      draft-verdt-netmod-yang-solutions-02
>>>>>      draft-verdt-netmod-yang-module-versioning-01
>>>>>      draft-verdt-netmod-yang-semver-01
>>>>>      draft-rwilton-netmod-yang-packages-02
>>>>>
>>>>> I think that this draft is also well on its way to be ready for WG
>>>> adoption:
>>>>>      draft-wilton-netmod-yang-ver-selection-01
>>>>>
>>>>>      - IMO, the key bit that we still need to figure out for this 
>>>>> draft is
>>>> exactly how packages are sensibly put together (e.g. for optional 
>>>> feature sets and bugfixes) in a way that doesn't defeat one of the 
>>>> main benefits of packages for clients (i.e. being able to know the 
>>>> exact device schema offline without having to download/check the 
>>>> entirely of YANG library on connection).  But equally I see no 
>>>> reason why that couldn't be figured out after the document as been 
>>>> adopted as
>> a WG item.
>>>>> Finally, doing an adoption call on these drafts may act as a 
>>>>> forcing
>>>> function to get the WG to discuss/agree whether this solution is on 
>>>> the right path.
>>>>> Of course, it is your decision.
>>>>>
>>>>> Thanks,
>>>>> Rob
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Lou Berger <lberger@labn.net>
>>>>>> Sent: 05 November 2019 15:11
>>>>>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs
>>>>>> <netmod- chairs@ietf.org>
>>>>>> Cc: netmod-ver-dt@ietf.org
>>>>>> Subject: Re: [netmod] NETMOD 106 Schedule and Call for 
>>>>>> Presentations
>>>>>>
>>>>>> You're the headliner -- so should have the time ;-)
>>>>>>
>>>>>> On 11/4/2019 4:49 AM, Rob Wilton (rwilton) wrote:
>>>>>>> 1) DT Update overview & status update (10 mins, Rob?):
>>>>>>> YANG Module Versioning Requirements
>>>>>>> draft-ietf-netmod-yang-versioning-reqs-01
>>>>>>>
>>>>>>> YANG Versioning Solution Overview
>>>>>>> draft-verdt-netmod-yang-solutions-02
>>>>>>>
>>>>>>> 2) Updated YANG Module Revision Handling (10 mins, tbd?):
>>>>>>> draft-verdt-netmod-yang-module-versioning-01
>>>>>>>
>>>>>>> 3) YANG Semantic Versioning (10 mins, Joe?)
>>>>>>> draft-verdt-netmod-yang-semver-01
>>>>>>>
>>>>>>> 4) YANG Packages (25 mins, Rob)
>>>>>>> draft-rwilton-netmod-yang-packages-02
>>>>>>>
>>>>>>> 5) YANG Schema Version Selection (25 mins, tbd?)
>>>>>>> draft-wilton-netmod-yang-ver-selection-01
>>> _______________________________________________
>>> Netmod-ver-dt mailing list
>>> Netmod-ver-dt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netmod-ver-dt
>>>
>> _______________________________________________
>> Netmod-ver-dt mailing list
>> Netmod-ver-dt@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod-ver-dt

_______________________________________________
Netmod-ver-dt mailing list
Netmod-ver-dt@ietf.org
https://www.ietf.org/mailman/listinfo/netmod-ver-dt