Re: I-D Action: draft-ietf-rtgwg-yang-key-chain-18.txt

"Acee Lindem (acee)" <acee@cisco.com> Tue, 11 April 2017 18:17 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 3B4B612EBC7 for <rtgwg@ietfa.amsl.com>; Tue, 11 Apr 2017 11:17:52 -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 JdCZQNRpGarX for <rtgwg@ietfa.amsl.com>; Tue, 11 Apr 2017 11:17:50 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25AD012EBA4 for <rtgwg@ietf.org>; Tue, 11 Apr 2017 11:17:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2604; q=dns/txt; s=iport; t=1491934641; x=1493144241; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tU+auq0IAD+yRGapO7TDPspSH0joav4dOCqM4sOah/A=; b=Jp77Kp2AfM8qozSatfjw64Y1Oas9nmyYtpn7BCK+42bzUX2T8GKrGOne nrz4r6zVX1r2NOgTpH9BnZaHW6Vw2+vY6KdwXfR3BGg8NHITH+qnELly9 VoNGoBsPttHQbgtJw+hqfRgoxTCV218HJGoFNthesVWj2xqUfZpAV6Scu E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAQBZHO1Y/5BdJa1cGQEBAQEBAQEBAQEBBwEBAQEBg1NhgQsHjXKnJoIPIQ2FdgKDYj8YAQIBAQEBAQEBayiFFgIBAwEBODQLEAIBCDYQJwslAgQBDQWKEA6rSIp6AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYtAgxeHJAWcfwGGf4tegX9VhFmKF5QAAR84gQVbFRgphlp1iEiBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.37,186,1488844800"; d="scan'208";a="231693316"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Apr 2017 18:17:20 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v3BIHJDl005872 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Apr 2017 18:17:20 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 11 Apr 2017 14:17:19 -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, 11 Apr 2017 14:17:19 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Vincent Roca <vincent.roca@inria.fr>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: I-D Action: draft-ietf-rtgwg-yang-key-chain-18.txt
Thread-Topic: I-D Action: draft-ietf-rtgwg-yang-key-chain-18.txt
Thread-Index: AQHSsu9T8GT1BpGI00OsgXRR+kG7yKHAedKA
Date: Tue, 11 Apr 2017 18:17:19 +0000
Message-ID: <D5129518.A837B%acee@cisco.com>
References: <149193437885.15788.9995920650504218251@ietfa.amsl.com>
In-Reply-To: <149193437885.15788.9995920650504218251@ietfa.amsl.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.197]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9C979B9D24CE9D4C93963A102E1E5D88@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/GQLuoK8rqMbMiK4VUIDyKKGwLvk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Apr 2017 18:17:52 -0000

This version includes comments from Vincent Roca (Security Directorate
Review) and Matthew Miller (GenART Review). We are still considering
whether to remove the aes-key-wrap feature completely.

On 4/11/17, 2:12 PM, "rtgwg on behalf of internet-drafts@ietf.org"
<rtgwg-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the Routing Area Working Group of the IETF.
>
>        Title           : Routing Key Chain YANG Data Model
>        Authors         : Acee Lindem
>                          Yingzhen Qu
>                          Derek Yeung
>                          Ing-Wher Chen
>                          Jeffrey Zhang
>	Filename        : draft-ietf-rtgwg-yang-key-chain-18.txt
>	Pages           : 25
>	Date            : 2017-04-11
>
>Abstract:
>   This document describes the key chain YANG data model.  Key chains
>   are commonly used for routing protocol authentication and other
>   applications requiring symmetric keys.  A key chain is a list of
>   elements each containing a key string, send lifetime, accept
>   lifetime, and algorithm (authentication or encryption).  By properly
>   overlapping the send and accept lifetimes of multiple key chain
>   elements, key strings and algorithms may be gracefully updated.  By
>   representing them in a YANG data model, key distribution can be
>   automated.
>
>   In some applications, the protocols do not use the key chain element
>   key directly, but rather a key derivation function is used to derive
>   a short-lived key from the key chain element key (e.g., the Master
>   Keys used in the TCP Authentication Option(TCP-AO)).
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/
>
>There are also htmlized versions available at:
>https://tools.ietf.org/html/draft-ietf-rtgwg-yang-key-chain-18
>https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-yang-key-chain-18
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-yang-key-chain-18
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>rtgwg mailing list
>rtgwg@ietf.org
>https://www.ietf.org/mailman/listinfo/rtgwg