Re: [netmod] I-D Action: draft-ietf-rtgwg-yang-key-chain-13.txt

"Acee Lindem (acee)" <acee@cisco.com> Thu, 19 January 2017 10:56 UTC

Return-Path: <acee@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38859129441; Thu, 19 Jan 2017 02:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.7
X-Spam-Level:
X-Spam-Status: No, score=-16.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Xf1Le9OBGyu8; Thu, 19 Jan 2017 02:56:38 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AACC012943A; Thu, 19 Jan 2017 02:56:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2577; q=dns/txt; s=iport; t=1484823398; x=1486032998; h=from:cc:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=FxertJDErNDgBb70H9WXhu4ULAtTl8+ielQkvYJxrHs=; b=ib7Qc52oJFA/SVVK7sBYS5XsFoiorzyWBTJOpyQoIkAm9e9Hx/Ek7tSg ttsB4K8p4HyOEn7P+szMR6bR89hVsMAR3haRBii4Obj2kciLLpmVT5JVH 0wUoKniXTP/7v6OFlpE0XDxgYt6zTZhJwLcHpN+qyZtcnr8z5GOaC8ZYa 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQA6moBY/4wNJK1eGQEBAQEBAQEBAQEBBwEBAQEBgz8BAQEBAR9gfA0HjVKRV5VYggwfC4V4AiaBUj8YAQIBAQEBAQEBYyiEYQkCBAEBODQLEAIBCDYQJwslAhIFhXKDEQ6xd4o8AQEBAQEBBAEBAQEBAQEhizmDDIRUgk0Fm0QBhmCLBIF3UoQ9iWiSbwEfOIFGFRgiXwuFTXOIV4ENAQEF
X-IronPort-AV: E=Sophos;i="5.33,253,1477958400"; d="scan'208";a="199997903"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jan 2017 10:56:37 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v0JAub3H007228 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jan 2017 10:56:37 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; Thu, 19 Jan 2017 05:56:36 -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; Thu, 19 Jan 2017 05:56:36 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
Thread-Topic: I-D Action: draft-ietf-rtgwg-yang-key-chain-13.txt
Thread-Index: AQHSckK0ovkAVP+npESQ+e4y1kcrKg==
Date: Thu, 19 Jan 2017 10:56:36 +0000
Message-ID: <D4A604C8.94B0D%acee@cisco.com>
References: <148482273303.10461.13311488338617348540.idtracker@ietfa.amsl.com>
In-Reply-To: <148482273303.10461.13311488338617348540.idtracker@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.201]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <763B584D362B1C42BAD07CA1B5C91E8C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/u11gKLewRiJBfwyRADvY5QJvrt0>
Cc: NETMOD WG <netmod@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: [netmod] I-D Action: draft-ietf-rtgwg-yang-key-chain-13.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2017 10:56:40 -0000

This version uses NETCONF Access Control Model (NACM) rules, as defined in
RFC 6536, to make key-strings inaccessible by default. The key-strings are
now retrievable in the operational state as long as the proper NACM rules
are defined. 

Thanks,
Acee 

On 1/19/17, 5:45 AM, "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
>                          Yi Yang
>	Filename        : draft-ietf-rtgwg-yang-key-chain-13.txt
>	Pages           : 24
>	Date            : 2017-01-19
>
>Abstract:
>   This document describes the key chain YANG data model.  A key chain
>   is a list of elements each containing a key, send lifetime, accept
>   lifetime, and algorithm (authentication or encryption).  By properly
>   overlapping the send and accept lifetimes of multiple key chain
>   elements, keys and algorithms may be gracefully updated.  By
>   representing them in a YANG data model, key distribution can be
>   automated.  Key chains are commonly used for routing protocol
>   authentication and other applications.  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.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/
>
>There's also a htmlized version available at:
>https://tools.ietf.org/html/draft-ietf-rtgwg-yang-key-chain-13
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-yang-key-chain-13
>
>
>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