Re: [Netconf] Draft Charter Proposal for NETCONF WG
"Acee Lindem (acee)" <acee@cisco.com> Tue, 21 March 2017 14:22 UTC
Return-Path: <acee@cisco.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 06D4E1294AC; Tue, 21 Mar 2017 07:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 jc5jIkX5Q9WS; Tue, 21 Mar 2017 07:22:42 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B092C12949D; Tue, 21 Mar 2017 07:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11946; q=dns/txt; s=iport; t=1490106162; x=1491315762; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Ph0rGFaaKoq/HRlY9mrOLKcfp4mBMGd+FyO9yJFdgms=; b=EQGZB0rWNviGPnI3j0PrieFLYNFNxPZx7b6kKW+zSBt2fGohhoQ8NsJJ JcG7cxaMJGFxRyDRRXLg4C4bASetDD3vWl0zzrQeutD9ixOhjN/WTv0Xb MVqPD54uWRs8wAlAZv6vXzQ+OcyAFXzfg/xZajt+ok3WtEe99Fhd5QRDG I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ATAQCdNtFY/4MNJK1eGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQoHjWuRXogSjTKCDh8LhS5KAoMSPxgBAgEBAQEBAQFrKIUVAQEBAQMBAWwEAgUMBAIBCBUBAgwBGgchBgsUEQIEAQkEBYlsAxUOrRyHPw2DBAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFiz2CUYFLIhaFZQWJHYcBi3g6AYZ5hxqEMoF7hSiDV4YzimuET4QkAR84gQRYFUGGV3WHE4EhgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.36,198,1486425600"; d="scan'208";a="223026951"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Mar 2017 14:22:41 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v2LEMfbv008286 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 21 Mar 2017 14:22:41 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 21 Mar 2017 10:22:40 -0400
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.1210.000; Tue, 21 Mar 2017 10:22:40 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "t.petch" <ietfc@btconnect.com>, Mehmet Ersue <mersue@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
CC: 'Netconf' <netconf@ietf.org>, RTGWG <rtgwg@ietf.org>
Thread-Topic: [Netconf] Draft Charter Proposal for NETCONF WG
Thread-Index: AQHSojVbsjloti5TfEiMBOab9w67O6GfWMEA
Date: Tue, 21 Mar 2017 14:22:40 +0000
Message-ID: <D4F6AE83.A3890%acee@cisco.com>
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> <02ee01d2a22b$295b2be0$4001a8c0@gateway.2wire.net> <30B0C127-1FA5-4177-9718-F687029F24C9@gmail.com>
In-Reply-To: <30B0C127-1FA5-4177-9718-F687029F24C9@gmail.com>
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="iso-8859-1"
Content-ID: <ADBB300E7CE81A4BAD31B0989FE12894@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/q2VgJkKNvoxRQx7Qi_tFTF6a0qw>
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 14:22:46 -0000
Tom, If you read the two drafts and look at the data nodes in the two models, you¹ll quickly realize that they have entirely different purposes. Thanks, Acee On 3/21/17, 7:21 AM, "rtgwg on behalf of Jeff Tantsura" <rtgwg-bounces@ietf.org on behalf of jefftant.ietf@gmail.com> wrote: >Tom, > >Including RTGWG, the draft-ietf-rtgwg-yang-key-chain home. >In general, there¹s no interactions, rtgwg-yang-key-chain work has been >focused on data model for routing protocols key-chain¹s configuration and >management. > >Thanks! > >Cheers, >Jeff > >On 3/21/17, 03:08, "Netconf on behalf of t.petch" ><netconf-bounces@ietf.org on behalf of ietfc@btconnect.com> wrote: > > 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 mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > > > >_______________________________________________ >rtgwg mailing list >rtgwg@ietf.org >https://www.ietf.org/mailman/listinfo/rtgwg
- [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)