Re: [Netconf] Draft Charter Proposal for NETCONF WG
t.petch <ietfc@btconnect.com> Tue, 21 March 2017 10:10 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F99E1296BD for <netconf@ietfa.amsl.com>; Tue, 21 Mar 2017 03:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 g4kawABJ5nHh for <netconf@ietfa.amsl.com>; Tue, 21 Mar 2017 03:10:37 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0138.outbound.protection.outlook.com [104.47.1.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA531296C1 for <netconf@ietf.org>; Tue, 21 Mar 2017 03:10:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=UZDRTtE3pWQ+WmpzDuv5JsyDXd3t9u2HHFj9BIeVaq4=; b=iPiu7KB/KNQhxfDbRmy/xL6SZMCE0c8qEvxgHDYmTG4thjqolNq7jRzRHfslpPe8gWMifE2vX44R33piblqp9/jJ8M2iwapmx2oE/QPR7PJtRiMfO3Ozvl/21B+PDH2QDv2AOsEWELj1rBFUldaezcaipj1f6WmqTGDNNnX80N0=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.185.203.75) by DB6PR0701MB2999.eurprd07.prod.outlook.com (10.168.84.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.4; Tue, 21 Mar 2017 10:10:33 +0000
Message-ID: <02ee01d2a22b$295b2be0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Mehmet Ersue <mersue@gmail.com>, 'Benoit Claise' <bclaise@cisco.com>
CC: 'Netconf' <netconf@ietf.org>
References: <014101d2913a$3db72870$b9257950$@gmail.com> <070e01d291ba$9bb8f4a0$4001a8c0@gateway.2wire.net> <m2fuiye8rj.fsf@birdie.labs.nic.cz> <072D22E1-66DA-414E-BD16-C43D36BE9B6E@juniper.net> <026e01d29273$5cc0cfc0$4001a8c0@gateway.2wire.net> <5A12F60C-3BA9-41A2-B77C-9E73B9DA115D@juniper.net> <05c201d2941a$d4bd4500$4001a8c0@gateway.2wire.net> <20170303133448.GA3133@elstar.local> <00b201d2942b$32395b50$96ac11f0$@gmail.com> <014701d29753$bb651790$322f46b0$@ndzh.com> <CABCOCHSacn15vfo8MR0K-UJJo6E0AZ14Gwj3M43KYkgbtwK8Kg@mail.gmail.com> <005101d2975f$ae87ac20$0b970460$@ndzh.com> <017d01d29769$0df70b20$29e52160$@gmail.com> <010701d29771$a45f66e0$ed1e34a0$@ndzh.com> <026601d2977f$8d059600$a710c200$@gmail.com> <685B9088-7557-4C6E-9A8F-54C3208DB312@juniper.net> <7217bc23-0e1e-c250-929d-e18c3f0a800f@cisco.com> <07b601d2a197$9865d5b0$c9318110$@gmail.com>
Date: Tue, 21 Mar 2017 10:08:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.185.203.75]
X-ClientProxiedBy: VI1PR09CA0062.eurprd09.prod.outlook.com (10.174.49.30) To DB6PR0701MB2999.eurprd07.prod.outlook.com (10.168.84.137)
X-MS-Office365-Filtering-Correlation-Id: 969772fc-edca-4f95-8519-08d47042833d
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:DB6PR0701MB2999;
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 3:c0GpoZM4ZjKk0i5sfmao65ubB9dKfBAgcBIIbvv8n8gOLhiak1KmVrNCfnZ+WZR6Gi7l77RiNIcNLz0Jy0Nct5t8cyQjbvjwpWua1hnI6fEXdbjK7HGBDL8EVKRjdNk/Kwf1L1Pwr2JJ6i0fz2vzzcGoOxam0FaAi+ykqM9v45E4/Nu9B06de45wKxr0CDGpAjnHI87AwDvNwHWpxKnW0Dd3A1sKkmW6S5oT0uWvPzyHLcDwgjqf6N5E8bLafLrmwx4xvLTQGBe4NKYPTRdynA==; 25:A1j0OZ8uiHOdPoVtoW4kCaY9n0sN2C4HHIvDz4v6ySd256l4gi2LxbjMElNd1++PA9ot6e9wBI+vaOiyeEZ7wDC91O92bFgIVEjJZoo5WTj7tHV20arYH4ipaPzrixaRzkisqhb5kFNb5xAPuJPuvJl/qwH1rt8R9uMoiQuM34kSIp0JCbEI4U2jFhfDCPVeAJuqmtoQB/gFZ/ffGN+KOpEKDRBMtAIfj0EM3RGEaHonfXGNrtBRNvTlzN7dihJopdweTE8YxYIIihlzAAK7+ks6opoK6cVB/uhjxaecYDYCtM54syw4m24nfWL+dqmAeUbl9Q7kctEHUjVck1xkDx6d4puqQpRqH10hreoCfLnzEtYS5uHl1+VXebnZShtjFgHrfITIKiaDoJvnlQatLpOfiXtKzKZ/3AzG8UE31dkwG2rK7G3DdIQwEu5aBRCHLklxqB99C/zGurY40Ra7+g==
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 31:LqsbFQGNTw9Vtfx5GNVQX5k46Y5+FKFSwmQE1TvibsozDoMnWGzGmkA53w2Kdu6yYHYmxUZCQH0g9mjzsYLz3Epx64J7/OH0+WzXxO2KNSbEYERN/BdYTq1/eSQeA572dlUBMa8Vq8qcIaPW0+TOB8Al3y+nux0ORRN2E/BWDT5h4LXy1IK8TV7KhpiV/mHI2V4QDg3EYSlwsTIaGee99P/Lhk5ABGf4Mo7cX4F3s88QkNBK08yeoNp0ngdx21tT
X-Microsoft-Antispam-PRVS: <DB6PR0701MB299925D0B0746C6E2679749AA03D0@DB6PR0701MB2999.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(278428928389397)(138986009662008)(95692535739014);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123555025)(20161123558025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:DB6PR0701MB2999; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2999;
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 4:30Wsg5i76pO+RPJIv07PM3ELgDnDIdKKKLdhksXZBvgjCyQBUBEBDaG+Ho7+frSZlpQ7d2uaqk7yiXMLOBHe9/nz/EVKJOWp7JXu4+IYh+d1jfsWZXEaceAc5q3lWaGvYr9NyCFV11/3u1cQV50CyiD+jdSjFEhS612LuQOsBTLR18VElTKs90O3Fgt3FqOslcsspBbAQ074/dvMYCSzM9NcWv8bCHjLklxb8e9h/moSx6ubZ+3Cn5NgFuKky9CCdF7Y289pSfqmBRa28a007eSFH9NUi7IaC1y42LbsUFgdX+nlFDdxFMmCvKbe0VYw9sOeUfr1f4WKcc+5WGIgcT855fV6GPISpLu0tOD56AhGOKmiXlnBaJNJY1jFHfT6x++NyIhFyzraiAL21dh+PoZMTqVcNiIPwMmWf6xO7XNSgj7qUFJ2dFjmUyt/ygroJvKHjnIeYrIibFZ+UJ/ORRU0FBp7/UQTExLclA/9/Ywcq87i4FcbICWWDS3chNQn8TTdCNoJHuAtV5d72AiV4+gn8RuqMVq5vEezfCszVHQpmcZvtosot6752zp33u9drr0UA1R778ADvSu+2+SORT6zKfvvxkPUn0gXO6idk8rRTUv693fSpoYPZfWYmNGWRbke7gRqCHPv5c/oLELncUpeikMRM2WyVjWJt0D5FU0ovTn27CDmbVd4p5w6CeAKBqzlpLbuv87+6zV6pF6KqJx4ia+leIZtwfw/Y15AzFymypMKVMG9++poO0D4eIDI
X-Forefront-PRVS: 02530BD3AA
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(45074003)(377454003)(24454002)(13464003)(84392002)(86362001)(230700001)(93886004)(116806002)(2906002)(561944003)(53936002)(4326008)(14496001)(53546009)(189998001)(81686999)(76176999)(50986999)(81816999)(7736002)(47776003)(62236002)(44716002)(5660300001)(6666003)(66066001)(50466002)(4720700003)(229853002)(3846002)(305945005)(23756003)(1556002)(6116002)(8676002)(81166006)(42186005)(50226002)(1456003)(6496005)(25786008)(44736005)(6306002)(6486002)(9686003)(38730400002)(6246003)(33646002)(61296003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2999; H:pc6; FPR:; SPF:None; MLV:nov; PTR:InfoNoRecords; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 23:R5vXUUhn+n4up3mVQPKbFF3JI/x5oI7AmL5m0ekM8wyO7qUoZARaVWDL6V/sBQkwmJCYF4qGSQhjMztth7Bh84oIQeC2UOd6BMVshIuuGkAaG9dqCKqk2gnryWetVggdb9SZ/T5VdVNUZjedEFi4ddiPTUGfeyo/WM4//JZDMy1ndjIveiJEbvwJoySyJQbqM7keIAEaUqUyV77kMXtC5inDIacdSeywbBhrsy05ZU1kMTaPm6aacu9L5OzgB/vuL9FkB+kqVQtCjFm9sUe6zBo2sxBW2/AJkz/g80Rz+Uo4X84CYpgSE77J7d39bKBX4QfAcSVVXsSwJH00FUcAYHFK7/daaW+EtNPIjfQbUDAeHW7FOPY4NFsvRxIoHrHYLtWmaSORf+SRTNHD9voU9LCl8R8ZfIuDKOfzmJqSjImpkdZuLeVH3keh9Q7VJgi7Emul/N1tyuGvRPJKzt9pMRvnSmyUfweK9YMgPSH76P6pruQUeqgECU1wZLsHrg9AA2Kp2650cDseVBpqW3aKBqTLsPayS36jTKEqa+fYGrXNDJsSu9dlxPulr6z5k+HUFPx7Z0LESI0T4vaLby5+xqN009JSx9/dPgkrYXQzO55yx/Y+Yk0wGY+4fiyudzwVh/5Yq8mo6Iut8Z0I6Nje+GL6RmXs4zyzFbimkm5eEUhNK+RZm7k33HNBhsnAbz6oqzsf7/3wyP0XDVXFTl+s+spMNjhexiIVJCYkaVW2EFbtuENzAKZm3ZasuQXATPJaDAm6Ak4WnUZG6gqvp5/ZZCq5h0pmVoEEtyeiALfgm25i8Cl0J6jFkStr4cr6j5ymD6Fpw4B4tOCKPV+O/adn6eWmbzKkkZD9NJr0ELVGr7b12ommQbtauAo8gMbEDD3wk88Mf1QvjltmlnD+D6hMJGGHiCrV94GPELVVHU7KJKo3J/Ywcx9IKF5gsvlWfYf5tOsJqCN9un3tFS+WmgKle5dMGpU3wpndjavXv4Ew20nBeCgYEeTs4LjTaZNi5Eooko5nG27SfcZMVV0i7tJWdZvMJel1GGGmfgA5nK3YYXySQ4Fj0DVU5LmbCSAY4hxFh9BDV8hYGyp9/vfX5aLB7lFMIQ8FUq2QtuJ+KKOkgwKQviRPuHbxZVDzPstqwe4RJdLn9lpgDoVVUBSBRKmddTAnRRfuebF8M/L8KUrHVZxX/zCDEe3tUSqWnK/Zy9FcP7IYcDEv9ot24ZWL8tsVtSIInAT6TbiKGzEneE+gF5c4uGRAXQyBVZykxevumTYKHMZ7v8xWPLANUvV5CgOld6AvD0dS14a+FBTAxqGXCzg=
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 6:bTYFPQSp7zc+b3os3Z+ApdHHAoqxmkGa/a/Vr1dQYgJw7uZa+aJM2j29FDIY7pOxv4ZtVlpcH/U4hyvNohG7rYhqvsYKOF4QvtAvz+QX5t2I2nqx/SRbhV5fm7Fa5LnauXhRaUZzVuzw/1Q5M7fsO7t61Rp4Tn4MoI22qLdeYOW14oMur7dA3pA0chhYBxvh5Ay5rkGDGaQB2xlHTwb8d+mG8W2/3fg1rAbiuq/DBgM7Xd4KWvjcyLOduTpKsGgCLjMPVNvcXgaKUdIVeoX3NB53zm0LG4xUraxeWx75wWD2++9nL7a/lcvZFqpAi5oFK5kOBGDHawJ8K5rphYpm6BD9Gl9DZbisA3CS021Hxh39puDAYivOCm91WYUcxHslxLQyOFfThmxWe+NpWmxtNg==; 5:nMrH5ujK+chf+kfwu7V3Ejiqjj5FgutVTOUF2jXgBbbsT5XqKM8NfLBbbEz3HJgKwWBw+wKRiQwfIWJBUJ7hJBIIIgQFqcgOcHvNK+64xFv3sDi8fMArqnr64O9Sve0A9YTyrUkAiDimwUxOqdlmzw==; 24:PSGrjGzjgqdt1rVJXL674omS/fGpcu7wZChAWCBL8y1IBq6Iy2CVmLRXqBjVDLW7o/fsfvxcYaizZB9shwpiBc0IfmoOzPR22O/VbgS/qGg=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2999; 7:6b+UTMTfJf4qlq6JLMOIbr7htJY9n27/PGdDbALVeD0DBSBFNJaqoy/f5Hskp/zRGHWY2qOfj2/2Vanrm67B0jYgk3KhngTzo1Lk1Uoki9a9VTsLkDijgTgTKPQE1Lz4vL9R2N3OaJioYAEjTEbRPvLfp59Xxy3M8swEgBK/W06xDXKhnR4YDUGzfoQAyQ62cQX0EhDK71uV0nzAGQ9hJRsP6eBqmZ8ZAy2AWlDkUAewEgXpw/ldAzrG+U8xQoImA+mNEnVPK+Ckq1iSMMK4Gxq/ACWhw2g1fmlxZAsLuzZssKpTs9GBMdzLLglZk5BLvrYPS8nWS3FDBq+J/zOmvA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2017 10:10:33.2457 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2999
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/K2GUx-_FkpmMItvQgy-WiPPk_-s>
Subject: Re: [Netconf] Draft Charter Proposal for NETCONF WG
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2017 10:10:41 -0000
What interaction, if any, is there between draft-ietf-rtgwg-yang-key-chain-15.txt This document describes the key chain YANG data model. file "ietf-key-chain@2017-02-16.yang" currently in IETF Last Call, and draft-ietf-netconf-system-keychain-00 This document defines a YANG data module for a system-level keychain mechanism file "ietf-system-keychain@2016-07-08.yang" ? Tom Petch ----- Original Message ----- From: "Mehmet Ersue" <mersue@gmail.com> To: "'Benoit Claise'" <bclaise@cisco.com>; "'Susan Hares'" <shares@ndzh.com> Sent: Monday, March 20, 2017 4:32 PM > Dear All, > > > > based on the recent discussion and proposals please find below the updated > charter proposal for NETCONF WG. > > Please comment before March 24, 2017. > > > Following Benoit's support the I2RS-related additions have been added as a > separated item. > > Being dependent on netmod-revised-datastores point 6 and 7 have been defined > as a goal without a deadline. > > > Mehmet > > > Network Configuration (netconf) > > ------------------------------- > > > > Charter > > > > Current Status: Active > > > > Chairs: > > Mahesh Jethanandani <mjethanandani@gmail.com> > > Mehmet Ersue <mersue@gmail.com> > > > > Operations and Management Area Directors: > > Benoit Claise <bclaise@cisco.com> > > Joel Jaeggli <joelja@bogus.com> > > > > Operations and Management Area Advisor: > > Benoit Claise <bclaise@cisco.com> > > > > Mailing Lists: > > General Discussion: netconf@ietf.org > > To Subscribe: https://www.ietf.org/mailman/listinfo/netconf > > Archive: <https://mailarchive.ietf.org/arch/browse/netconf/> > https://mailarchive.ietf.org/arch/browse/netconf/ > > > > Description of Working Group: > > > > Configuration of networks of devices has become a critical requirement > > for operators in today's highly interconnected networks. Large and > > small operators alike have developed their own mechanisms or have used > > vendor specific mechanisms to transfer configuration data to and from > > a device and to examine device state information which may impact the > > configuration. Each of these mechanisms may be different in various > > aspects, such as session establishment, user authentication, > > configuration data exchange, and error responses. > > > > The NETCONF protocol (RFC 6241) provides mechanisms to install, > > manipulate, and delete the configuration of network devices. NETCONF > > is based on the secure transport (SSH is mandatory to implement while > > TLS is an optional transport). The NETCONF protocol is data modeling > > language independent, but YANG (RFC 7950) is the recommended NETCONF > > modeling language, which introduces advanced language features for > > configuration management. > > > > NETCONF WG recently finalized the development of RESTCONF protocol > > (RFC 8040) which provides an interface over HTTPs for accessing data > > defined in YANG. RESTCONF is based on the capabilities and uses the > > datastore concept defined in the NETCONF protocol specification. In > > support of RESTCONF the YANG-Patch (RFC 8072) mechanism has been > > provided for applying patches to configuration datastores. The YANG > > Module Library (RFC 7895) provides information about all YANG modules > > used by a network management server. > > > > Last but not least NETCONF and RESTCONF Call Home (RFC 8071) have been > > developed, which enable a server to initiate a secure connection to a > > NETCONF or RESTCONF client respectively. > > > > In the current phase of NETCONF's incremental development the > > workgroup will focus on following items: > > > > 1. Finalize the YANG data module for a system-level keystore mechanism, > > that can be used to hold onto asymmetric private keys and certificates > > that are trusted by the system advertising support for this module. > > Based on the known dependencies this draft has the highest priority > > for the WG. > > > > 2. Finalize Server and Client Configuration YANG modules for both > > NETCONF and RESTCONF as well as the Client and Server Models for SSH > > and TLS. > > > > 3. Finalize the Zero-touch provisioning for NETCONF or RESTCONF-based > > Management as a technique to establish a secure network management > > relationship between a newly delivered network device configured with > > just its factory default settings, and the Network Management System) > > > > 4. Provide a revised version of RFC 6536 (NETCONF Access Control > > Model) by adding support for RESTCONF and the YANG 1.1. constructs > > like "action" and the "notification" statements. > > > > 5. Provide a set of documents enabling advanced notification/ > > subscription capabilities, which gracefully co-exist in a deployment > > of RFC 5277. The new capabilities include e.g. transport independence, > > multiple dynamic and configured subscriptions in a transport > > session. RFC 5277 will be obsoleted in parallel to the publication of > > the new document set. Following specifications will be addressed: > > - Protocol-neutral notification framework, i.e., explaining the > > concepts of subscriptions, filters, subscription state > > notifications, replay, etc. and defining the associated YANG data > > model, RPCs, etc. > > - Definition of notifications sent over NETCONF and how YANG > > notifications are encoded in XML and JSON. Include considerations > > for parallel support / implementation compatibility with RFC-5277. > > - Definition of notifications sent over RESTCONF and HTTP2 and how > > YANG notifications are encoded in XML and JSON. Include specifics > > of call-home and heartbeat for subscriptions. > > - The subscription and push mechanism for YANG datastores allowing > > subscriber applications to request updates from a YANG datastore. > > > > 6. Provide a revision for the NETCONF and RESTCONF protocols and the > > used datastore framework building on the datastore concept in NETMOD > > revised datastores work. Bug fixing will be done and potential > > extensions will be added. Provide guidance on how to adapt and use > > YANG with NETCONF and RESCONF protocols. NETCONF XML Encoding Rules > > from RFC 7950 will be moved to RFC6241bis. > > > > 7. Define capabilities for NETCONF and RESTCONF to support I2RS protocol > > and ephemeral state datastore requirements. > > > > Based on the implementation, deployment experience and inter- > > operability testing, the WG aims to produce a NETCONF status report > > in a later stage. The result may be clarifications for RFC6241 and > > RFC6242 and addressing any reported errata. > > > > > > Goals and Milestones: > > Done Submit NETCONF/RESTCONF Call Home to AD/IESG for consideration as > Proposed Standard > > Done Submit YANG Library to AD/IESG for consideration as Proposed > Standard > > Done Submit RESTCONF to AD/IESG for consideration as Proposed Standard > > Done Submit YANG Patch to AD/IESG for consideration as Proposed > Standard > > > > May 2017 WGLC for Zero-touch configuration mechanism > > Jun 2017 Submit Zero-touch configuration to AD/IESG for consideration as > Proposed Standard > > May 2017 WGLC for system-level keystore mechanism > > Jun 2017 Submit keystore mechanism to AD/IESG for consideration as > Proposed Standard > > May 2017 WGLC for Server and Client models for NETCONF and RESTCONF > > Jun 2017 Submit Server and Client Configuration models to AD/IESG for > consideration as Proposed Standard > > May 2017 WGLC for Client and Server Models for SSH and TLS > > Jun 2017 Submit Client and Server Models for SSH and TLS to AD/IESG for > consideration as Proposed Standard > > Jun 2017 WGLC for RFC 6536bis (NETCONF Access Control Model) > > Jul 2017 Submit RFC 6536bis to AD/IESG for consideration as Proposed > Standard > > Jun 2017 WGLC for advanced Notification/Subscription specifications > > Jul 2017 Submit Notification/Subscription specifications to AD/IESG for > consideration as Proposed Standard > > > > > > From: Benoit Claise [mailto:bclaise@cisco.com] > Sent: Friday, March 17, 2017 4:49 PM > To: Kent Watsen <kwatsen@juniper.net>; Mehmet Ersue <mersue@gmail.com>; > 'Susan Hares' <shares@ndzh.com>; 'Andy Bierman' <andy@yumaworks.com> > Cc: 'Netconf' <netconf@ietf.org> > > > > On 3/8/2017 12:57 AM, Kent Watsen wrote: > > I agree with Mehmet, any changes to the NC/RC protocols should be done in > the NETCONF WG. > > +1. > > Regards, Benoit > > <snip>
- [Netconf] Draft Charter Proposal for NETCONF WG Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Lou Berger
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Lou Berger
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] health of NETCONF t.petch
- Re: [Netconf] health of NETCONF Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] health of NETCONF t.petch
- Re: [Netconf] health of NETCONF Ladislav Lhotka
- Re: [Netconf] health of NETCONF Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Alexander Clemm
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Alexander Clemm
- Re: [Netconf] Draft Charter Proposal for NETCONF … Alexander Clemm
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Alexander Clemm
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Andy Bierman
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Benoit Claise
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mehmet Ersue
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Jeff Tantsura
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Susan Hares
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Robert Wilton
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mahesh Jethanandani
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mahesh Jethanandani
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mahesh Jethanandani
- Re: [Netconf] Draft Charter Proposal for NETCONF … Mahesh Jethanandani
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Juergen Schoenwaelder
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … Ladislav Lhotka
- Re: [Netconf] Draft Charter Proposal for NETCONF … t.petch
- Re: [Netconf] Draft Charter Proposal for NETCONF … Eric Voit (evoit)
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Kent Watsen
- Re: [Netconf] Draft Charter Proposal for NETCONF … Acee Lindem (acee)