Re: [netmod] yang-next meeting at IETF 104?

Kent Watsen <kwatsen@juniper.net> Mon, 14 January 2019 22:27 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4141313F0 for <netmod@ietfa.amsl.com>; Mon, 14 Jan 2019 14:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.254
X-Spam-Level:
X-Spam-Status: No, score=-5.254 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 LQCkCxb0G63h for <netmod@ietfa.amsl.com>; Mon, 14 Jan 2019 14:27:17 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171C71313EC for <netmod@ietf.org>; Mon, 14 Jan 2019 14:27:16 -0800 (PST)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0EMRFkm021956; Mon, 14 Jan 2019 14:27:15 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=1IvYOHI3/sNBjHnR8G3ZtGfihrE/HsBK/uXUav2vd80=; b=UhgyWaKCBzsPJr9BvTIMDSrkUwTh79vemuJ5Lv55M/rJgB8eNXJAGv+NQGK4mo8IlJSP BbVdzsLUV1ZWTaSagzn5U0lEC4anTM3Hc6SJy/NE4Y9fgqy60e5kgcicjHSLPNmMFDtA ozPH2Wo3PXn1YstkAqeCywyL9eEjA7Qux3cKnWgnKElTOE7aRUebJXvmnJyhMLiNqbnr sIy6Rw6X+XcYZxP1lPlKEpvtk8TmkEEPf9y+jvaB6ue90uAsP0QhOr4k5zVWMeBywtih Xn5jx+7pjDGecnVUM3FnEknxVxIdcRQrR1MsJC69JCOgzZWZMPXe7p/N3LnO40r9eB9n yA==
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp2052.outbound.protection.outlook.com [104.47.49.52]) by mx0b-00273201.pphosted.com with ESMTP id 2q0yfv8ap7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 14 Jan 2019 14:27:15 -0800
Received: from BYAPR05MB5416.namprd05.prod.outlook.com (20.177.184.221) by BYAPR05MB4741.namprd05.prod.outlook.com (52.135.233.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.19; Mon, 14 Jan 2019 22:27:12 +0000
Received: from BYAPR05MB5416.namprd05.prod.outlook.com ([fe80::ccee:5d54:3370:e50b]) by BYAPR05MB5416.namprd05.prod.outlook.com ([fe80::ccee:5d54:3370:e50b%5]) with mapi id 15.20.1537.018; Mon, 14 Jan 2019 22:27:12 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "rwilton@cisco.com" <rwilton@cisco.com>, "andy@yumaworks.com" <andy@yumaworks.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] yang-next meeting at IETF 104?
Thread-Index: AQHUrCuq8LA2K3fznUKN5CVaZ7vS9qWu/8MAgAACgoD//9TgAIAAWGqA///U3YA=
Date: Mon, 14 Jan 2019 22:27:12 +0000
Message-ID: <B0A12CCE-C6D6-4757-B6F2-339075B4747A@juniper.net>
References: <20190114.181030.1714833278513265488.mbj@tail-f.com> <9292f38a-1f09-d738-6d4c-0645d78f86d5@cisco.com> <F3997729-2E38-4EC7-BFE2-21E7CD55F990@juniper.net> <20190114.210135.1957093582321067772.mbj@tail-f.com>
In-Reply-To: <20190114.210135.1957093582321067772.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.5.181209
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4741; 6:Pw2ohuvGseFUhBCbJUlb/7GlGf38yLavPgo4YIeFYZQNK8/ajT/aYDZsSpxuLuWj8uPaBmO9Nw9MByV0ncrxhD+SypdzlB0tSpT7yMz9nuwuoDRUqj6XIEJAeLG77TQJCMHy+H4xHtGRoniADTyAQ3+1q6T9ZkKPf6gb+YMszwpe5cQua2Ex8rGehB8prKterVdm44amb1V+9Bvmsw2tViwMtgsKqNNdXTO8uO9IRjQIcUMsaIfa/iuGFDWtBQ3zxW+wzv81jXVJveN7sZF3PNERqj/F38aDEKaFE2uX25FROkWkC1WsvdXXq6hyVwNXjzQv0tdK4SY/1Xjl3dbnXGkjO2R5KgodV82MOGbfC1wQPlPQz9vAvVqYjMFDDjCwM7EkOp5iaBITYsbI66r1/q8C6+ih3l4OhtZKao9V8OhHxURBsKfe8Emg0EPcrOKLBRoZowQ5wovbok0IF8ZUgA==; 5:AyxZcZn9gcMxmecMg55tkE7Bx2Ix1jVblh6jeyy1F2TQNb2H6TiaEWT9KHtfX7erczH+Q6G4RlMHMIuCKt+OfwcxZNMoOZ9vjBPFuuecxwW85p8E46+ZOWHbUFvAOmX7J+Ar/JM9h3ZMHbj8swmnboeOJx/BLGgMWFtzT466S2+BKDFYjE2eqX1YD8FZgW6yduJONlHKsNmEyPU1q2aw7w==; 7:BGdtsWvclkp/+Zv+Hov5jDp/N9lKg7dd5YRLVZfT2MVn7L5RZAckcm5bmdhu0ip2h/+N83DgbExUbWkhCRoV2s3ItUw0uQbYJyaDcaGgkE2nzSxjRIRutaQqACvUDc3SrVxd6SiK5+2iO4lNiyViIQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: dfe4be0d-5560-4620-db27-08d67a6f6e39
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4741;
x-ms-traffictypediagnostic: BYAPR05MB4741:
x-microsoft-antispam-prvs: <BYAPR05MB4741654B1C25850A70504754A5800@BYAPR05MB4741.namprd05.prod.outlook.com>
x-forefront-prvs: 0917DFAC67
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39850400004)(376002)(346002)(366004)(396003)(199004)(189003)(52024003)(51444003)(6512007)(25786009)(186003)(76176011)(82746002)(229853002)(4326008)(99286004)(105586002)(6306002)(53936002)(316002)(256004)(476003)(486006)(54906003)(68736007)(5660300001)(97736004)(14454004)(26005)(58126008)(6246003)(106356001)(6486002)(2616005)(305945005)(8936002)(11346002)(6436002)(6506007)(8676002)(6916009)(86362001)(36756003)(33656002)(446003)(3846002)(6116002)(2906002)(7736002)(83716004)(81166006)(66066001)(81156014)(71190400001)(71200400001)(478600001)(102836004)(93886005)(966005); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4741; H:BYAPR05MB5416.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: VddZZzA4BlMJVFYI/aIAG3qyii/vPZhgDUw7gQ2IDoUow/r3pkw+con75YD+D2trb/Gnit2isMHKT/uGGog3aOuW2ba4zwm+Sm2JB4f4664vQmgw0I8SQmtFwPEHpJncNsCFMwO5yIKV3RxDwbPswiQDye3Ygpx2tUhgMXjn+I7z+9uoa9x2RxjDv89dDsN7DS8HSRAMvxw0O3yj9sQERyEd5u/XVvATyMytxMzHjvSHywtvWnpHKY1xEjI/0r00D8IHaWyxJ/q4bnQ0gGbDZJYmN9z+QB3chbVMn4FohtjIqcgAolN3ZvMMFTpml///61Zb5XJhF3kZVFj69LKi12cGMJzPluRNRmFaGwvQLfsk+eoqdfEM34RIlfSQjBXELN7iXf+QVG33ccuolCUv36lgfMOQ6sZu+69jlp3l38k=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <CD88F04BD7D7E140915B2F167D4E134A@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: dfe4be0d-5560-4620-db27-08d67a6f6e39
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jan 2019 22:27:12.7687 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4741
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-01-14_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901140173
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/SZBRsHF87wKhgmuaR2HLAllpG8I>
Subject: Re: [netmod] yang-next meeting at IETF 104?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 22:27:19 -0000

>> PS: I've been too busy to setup a virtual meeting for us to finish the
>> review of the YANG-next items in the GitHub tracker.  But things are
>> just beginning to free up a little for me now.  Would folks like to
>> have a meeting before 104 to finish that review?
>
> I think that's what the side meeting would do - review the current
> items to see what makes sense.

Sure, but perhaps the in-person time would be better spent analyzing the results of the reviews?  Recall that we're trying to score each item on three axis: importance, complexity, backward-compatibility.

Current results here:  https://github.com/netmod-wg/yang-next/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc.

At the rate we were going (about 40% done), I imagine it taking 2-4 hours to score the remaining issues.  This may not be an issue if we can meet multiple times during the week but, if time is tight, I'd rather have this part done before we meet.

Kent // contributor