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

Benoit Claise <bclaise@cisco.com> Tue, 07 February 2017 10:57 UTC

Return-Path: <bclaise@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 05910129AD0; Tue, 7 Feb 2017 02:57:57 -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_H4=-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 xUJA9chwV-T8; Tue, 7 Feb 2017 02:57:54 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3450129ACB; Tue, 7 Feb 2017 02:57:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=243941; q=dns/txt; s=iport; t=1486465073; x=1487674673; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=onJYHSEZJ5BOq0SwPKHRrNDdTejgYo6DqLYBXmK47WM=; b=ip5dqBxM9z31ZNSi227DxSTI6gXQX/wA5E4i6G4lkF63XB7O0Jq5yaJI 2lFx2ZsJfXJwdA4EcHNzBn7M3XC8Mo3gNUaII2PkQAICZMaq8+2pgx4qT t7O5O9SY/1FN3tMU0QdqfS3PAZccmipvk/aPlO63YGA6UjRfIhO4uPS4m g=;
X-Files: lbfofigjgheccaop.png : 164628
X-IronPort-AV: E=Sophos;i="5.33,346,1477958400"; d="png'150?scan'150,208,217,150";a="652296203"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Feb 2017 10:57:51 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v17Avnk8007987; Tue, 7 Feb 2017 10:57:49 GMT
Subject: Re: Last Call for draft-ietf-rtgwg-yang-key-chain
To: "Acee Lindem (acee)" <acee@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>
References: <B3277A36-1A7A-4C45-A931-699FE2B2C85A@gmail.com> <0FC4166F-3CB3-4344-95C1-145CCEA1F467@gmail.com> <D4BE763D.9BB34%acee@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <de6d8a29-8a68-5dd9-e447-fbc34204ca89@cisco.com>
Date: Tue, 07 Feb 2017 11:57:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D4BE763D.9BB34%acee@cisco.com>
Content-Type: multipart/alternative; boundary="------------DD1547BFBCF2468655666C90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/opq4gA7cRWUp0ry0Di3eIeI4gvE>
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 10:57:57 -0000

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



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
> https://www.ietf.org/mailman/listinfo/rtgwg