Re: [Netconf] Draft Charter Proposal for NETCONF WG

Kent Watsen <kwatsen@juniper.net> Wed, 22 March 2017 22:11 UTC

Return-Path: <kwatsen@juniper.net>
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 55139129B16 for <netconf@ietfa.amsl.com>; Wed, 22 Mar 2017 15:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.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 z2WTyPS8fVNU for <netconf@ietfa.amsl.com>; Wed, 22 Mar 2017 15:11:37 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0102.outbound.protection.outlook.com [104.47.36.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A5D312949F for <netconf@ietf.org>; Wed, 22 Mar 2017 15:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SEs8EJd06lASfz9B2L/gGWENabiCI4eA2BC/EX+EDqo=; b=VvZq6CSA/VoYMwWGSDZ0/K0tleALzCR8RkLJo/9PTV1HsUOXDfkmeS9Mv2WpxETviqRshdKQ2f/5qq2yV6AQO2KpnMFaGtJsRsPoQJLC9gim6bvltpJLkO0qA538XbkkZwEWRfU/2AvlWfp3JQt9OfXpNB50kQUIdW8jNI31xUo=
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com (10.160.117.151) by BN3PR0501MB1441.namprd05.prod.outlook.com (10.160.117.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.4; Wed, 22 Mar 2017 22:11:29 +0000
Received: from BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) by BN3PR0501MB1442.namprd05.prod.outlook.com ([10.160.117.151]) with mapi id 15.01.0991.013; Wed, 22 Mar 2017 22:11:28 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
CC: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Netconf <netconf@ietf.org>, "draft-ietf-rtgwg-yang-key-chain-all@ietf.org" <draft-ietf-rtgwg-yang-key-chain-all@ietf.org>
Thread-Topic: [Netconf] Draft Charter Proposal for NETCONF WG
Thread-Index: AdKROeE3Cc7ORdXbRmOFzdaoTO5UHAAgSeNTAAMyYgAABKtfAAAmUhvuAAqrwYAAXzKn3gAB6uUAAAIQ/gAAyiJeAAAC57eAAAAVAwAAAlfsAAACJWiAAAN6WAD//+pRAIAPgnqAgATDTICAASefpIAAKg0AgABUkwD//9E3gIACAQEA///Hy4A=
Date: Wed, 22 Mar 2017 22:11:28 +0000
Message-ID: <4A73C3C3-61F3-4988-B163-264B29EE1BA0@juniper.net>
References: <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> <BA52FB19-D4B9-4E1A-BFE5-7CCE6F5554B1@juniper.net> <20170321174358.GA36769@elstar.local> <65E2B5E1-A1D0-45C1-94E8-F10A35042295@juniper.net> <FF00B7D1-0418-49C5-93AF-59D837354879@gmail.com>
In-Reply-To: <FF00B7D1-0418-49C5-93AF-59D837354879@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.11]
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1441; 7:26mkIY2qYwPDbZpfR5OAePIWtQVy+AUzQXcztL0KAmtV/Ujlpxexmqbt2PvOSog1L8nqXCdIiOivTPCOOe3JWj4a6At5ivKlZk+bzHzEuZkVt3Az5hSYTr0+0NuyNSZaZ708bjUfowbKEWJd6Td+C86JKxY1SKb5xmDs3+lMDmkmWkNDBqXn4TWebJy015FQF+vzlsfaFELc6+A2tEW2wSv7f4q2bbn9HNX7QV7MNrt+He4k+EOzmUSjNDOULq9edJLI+gZDOgBTR90/wt88owb3N6/nEzU5KLzfWbi9AclVPXo7WTQ5GSLxxICg+Hgwux9QjdyVgVptbAihbu4Zmw==
x-ms-office365-filtering-correlation-id: 3bc5555f-50ad-4011-1cb4-08d4717063b7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081); SRVR:BN3PR0501MB1441;
x-microsoft-antispam-prvs: <BN3PR0501MB14417D4C115AC02645F782D5A53C0@BN3PR0501MB1441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(6041248)(20161123558025)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:BN3PR0501MB1441; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1441;
x-forefront-prvs: 02543CD7CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39410400002)(39850400002)(39860400002)(39840400002)(1411001)(6916009)(2906002)(76176999)(54356999)(33656002)(5660300001)(50986999)(4001350100001)(2950100002)(93886004)(6116002)(3846002)(122556002)(102836003)(189998001)(3660700001)(86362001)(39060400002)(66066001)(36756003)(110136004)(38730400002)(4326008)(53936002)(3280700002)(6246003)(551544002)(229853002)(54906002)(99286003)(8936002)(8676002)(81166006)(6512007)(6506006)(82746002)(6486002)(6436002)(83506001)(7736002)(83716003)(77096006)(25786009)(305945005)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1441; H:BN3PR0501MB1442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <2CFB8E87A4A91445A496994EC864BBCA@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2017 22:11:28.7802 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1441
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/3wQm-zRqA23Q608pFmtitK_qxuQ>
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: Wed, 22 Mar 2017 22:11:39 -0000

[+draft-ietf-rtgwg-yang-key-chain-all]


Hi Mahesh,


>> Again, a keystore is not limited to asymmetric keys.   At the moment 
>> it is exclusively asymmetric, but that's only because we (the authors)
>> moved the passwords (read symmetric keys) that were present in the 
>> previous version to the ietf-ssh-client module, but they may return,
>> as many real-world keystore mechanisms do manage passwords as well
>> (e.g., Mac OSX's Keychain Access utility).
>> 
>> The module names are fine, but we could update the draft title. How
>> about "A System-level Keystore Model"?
>
>
> How about "Asymmetric Key System-level Keystore Model"?
> 
> And add a reference to keychain model for symmetric keys. 


Regarding "asymmetric", as mentioned above, while the keystore module
is currently exclusively asymmetric, it's probable that passwords will
be added to it in the future.

Regarding "system-level", I'm not 100% sure.  Specifically, the PCE-PCEP
use of the ietf-tls-client module, which uses the keystore module, gives
me pause.  Is it still a system-level use then?

Maybe one of the authors of the RTGWG key-chain draft to try to express
how the two modules differ, and why they shouldn't be merged into one
draft.

Thanks,
Kent