Re: Last Call for draft-ietf-rtgwg-yang-key-chain

"Acee Lindem (acee)" <acee@cisco.com> Tue, 07 February 2017 12:11 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD581293F2; Tue, 7 Feb 2017 04:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 hdVRuB_y9_BX; Tue, 7 Feb 2017 04:11:42 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1014129A20; Tue, 7 Feb 2017 04:11:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=245694; q=dns/txt; s=iport; t=1486469502; x=1487679102; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=O84bnEjZp9h+IBUFN8jaHo1/bRT39t4PmwwSCKdPT4I=; b=BVfrtyrlnbcjCuxzM4F9hQj4VpK/5m/ga31iRzw2mSf73zGF04vFNLE7 CQ/T0m6KtJT7HFdf2rS6EC0ccRVfcKFdmEdJ5k9RnTRvOeB0n8BE2R2bO Qm4GC83J9mZq7TAKYMfg1QPODOOK8NuhmG3JoQKa2kjMyfQaa2Geyj+AP Q=;
X-Files: lbfofigjgheccaop.png : 164628
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAQB8uJlY/5ldJa1DGhkBAQEBAQEBAQEBAQcBAQEBAYJvOCphgQkHjVmSD4JYhTSNKoIJAx8BCoV4AoJPPxgBAgEBAQEBAQFiKIRpAQEBBAEBAxhRBgUQAgEIEQMBAgYBAQEfBwIVAQkFAQsUCQgCBAENBAEGAwWJTQMVDi2xOiuHEQ2ECgEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4PizuCQw6BVREBBi0JFoUvBZpWXTgBg2+CBQGHf4QZgXuFF4lxijCERYQZAR84dghPFTyERB2BYXUBhnCBIYEMAQEB
X-IronPort-AV: E=Sophos;i="5.33,346,1477958400"; d="png'150?scan'150,208,217,150";a="382465558"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Feb 2017 12:11:40 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v17CBeGG028212 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Feb 2017 12:11:40 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Feb 2017 07:11:39 -0500
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, 7 Feb 2017 07:11:39 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>
Subject: Re: Last Call for draft-ietf-rtgwg-yang-key-chain
Thread-Topic: Last Call for draft-ietf-rtgwg-yang-key-chain
Thread-Index: AQHSgTEHwsuadg03xEOr4erja84zjaFddECA
Date: Tue, 07 Feb 2017 12:11:39 +0000
Message-ID: <D4BF2210.9BC28%acee@cisco.com>
References: <B3277A36-1A7A-4C45-A931-699FE2B2C85A@gmail.com> <0FC4166F-3CB3-4344-95C1-145CCEA1F467@gmail.com> <D4BE763D.9BB34%acee@cisco.com> <de6d8a29-8a68-5dd9-e447-fbc34204ca89@cisco.com>
In-Reply-To: <de6d8a29-8a68-5dd9-e447-fbc34204ca89@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: multipart/mixed; boundary="_004_D4BF22109BC28aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/yGhEvrLgQUoFLUvvojA8LN9MeMI>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "draft-ietf-rtgwg-yang-key-chain@ietf.org" <draft-ietf-rtgwg-yang-key-chain@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 12:11:44 -0000

Hi Benoit,

This is the IETF key-chain model which is comprised of a lists of symmetric keys that are used for applications such as routing protocol authentication and encryption. The IETF keystore model is comprised of lists of asymmetric keys and certificates that are used for applications such as NETCONF authentication and encryption. The two models are in no way dependent on one another.

Thanks,
Acee

From: "Benoit Claise (bclaise)" <bclaise@cisco.com<mailto:bclaise@cisco.com>>
Date: Tuesday, February 7, 2017 at 5:57 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>, Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>, "draft-ietf-rtgwg-yang-key-chain@ietf.org<mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org>" <draft-ietf-rtgwg-yang-key-chain@ietf.org<mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org>>, "netconf-chairs@ietf.org<mailto:netconf-chairs@ietf.org>" <netconf-chairs@ietf.org<mailto:netconf-chairs@ietf.org>>, Kent Watsen <kwatsen@juniper.net<mailto:kwatsen@juniper.net>>
Subject: Re: Last Call for draft-ietf-rtgwg-yang-key-chain

On 2/7/2017 12:53 AM, Acee Lindem (acee) wrote:
I support as a co-author. This IETF YANG model is currently referenced by a number or the other protocol models for specification of authentication keys including OSPF, IS-IS, RIP, and VRRP.
And note that there are dependencies on some NETCONF WG documents.
http://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-keychain&orgs[]=ietf&recurse=1&rfcs=1

Basically, this "Client/Server Configuration Model" package, i.e. those drafts:
    draft-ietf-netconf-keystore-00 Keystore Model
    draft-ietf-netconf-ssh-client-server-00 SSH Client and Server Models
    draft-ietf-netconf-tls-client-server-00 TLS Client and Server Models
    draft-ietf-netconf-netconf-client-server-00 NETCONF Client and Server Models
    draft-ietf-netconf-restconf-client-server-00 RESTCONF Client and Server Models

For this package, see http://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-tls-client&modules[]=ietf-tls-server&modules[]=ietf-ssh-client&modules[]=ietf-ssh-server&modules[]=ietf-restconf-client&modules[]=ietf-restconf-server&modules[]=ietf-key-store&modules[]=ietf-netconf-client&modules[]=ietf-netconf-server&orgs[]=ietf&recurse=&rfcs=1

[cid:part2.13E69E3B.C5C6A792@cisco.com]

Copying the NETCONF chairs, to get the latest status, and to make sure this NETCONF package progresses at the same pace.

Regards, Benoit

Thanks,
Acee
P.S. Not aware of any IPR in case you want to ask again ;^)

From: Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>
Date: Monday, February 6, 2017 at 1:35 PM
To: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>, "draft-ietf-rtgwg-yang-key-chain@ietf.org<mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org>" <draft-ietf-rtgwg-yang-key-chain@ietf.org<mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org>>
Subject: Re: Last Call for draft-ietf-rtgwg-yang-key-chain
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>
Resent-To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Jeffrey Zhang <zzhang@juniper.net<mailto:zzhang@juniper.net>>, <derek@arrcus.com<mailto:derek@arrcus.com>>, Helen Chen <ichen@kuatrotech.com<mailto:ichen@kuatrotech.com>>, Yingzhen Qu <yingzhen.qu@huawei.com<mailto:yingzhen.qu@huawei.com>>, <yi.yang@sockrate.com<mailto:yi.yang@sockrate.com>>
Resent-Date: Monday, February 6, 2017 at 1:35 PM

Dear RTGWG,

There have been significant changes to the draft-ietf-rtgwg-yang-key-chain draft.
We would like the wg to review the updated draft and hence start another, 1 week long WGLC.

Please indicate support/ no-support by February 13, 2017.

Thanks,
Jeff & Chris

From: Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>>
Date: Friday, September 9, 2016 at 16:11
To: RTGWG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Cc: rtgwg-chairs <rtgwg-chairs@ietf.org<mailto:rtgwg-chairs@ietf.org>>, <draft-ietf-rtgwg-yang-key-chain@ietf.org<mailto:draft-ietf-rtgwg-yang-key-chain@ietf.org>>
Subject: Last Call for draft-ietf-rtgwg-yang-key-chain

Dear RTGWG,

The authors have requested the RTGWG to last call draft-ietf-rtgwg-yang-key-chain


There was consensus that document is ready for the last call during the last IETF meeting and the authors have addressed all the comments from Directorate QA review.
Please indicate support or no-support by September 23rd, 2016.


IPR:
If you are listed as a document author or contributor, please respond to this email.
of whether or not you are aware of any relevant IPR. The response needs to be sent to the RTGWG mailing list.
The document will not advance to the next stage until a response has been received from each author and each
individual that has contributed to the document.


Thanks,
Jeff & Chris



_______________________________________________
rtgwg mailing list
rtgwg@ietf.org<mailto:rtgwg@ietf.org>https://www.ietf.org/mailman/listinfo/rtgwg