FW: New Version Notification for draft-acee-rtg-yang-key-chain-08.txt

"Acee Lindem (acee)" <acee@cisco.com> Fri, 25 September 2015 16:34 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4F871ACDDB for <rtgwg@ietfa.amsl.com>; Fri, 25 Sep 2015 09:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Ynd8AIXSGPkR for <rtgwg@ietfa.amsl.com>; Fri, 25 Sep 2015 09:34:40 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 558741ACDD9 for <rtgwg@ietf.org>; Fri, 25 Sep 2015 09:34:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2588; q=dns/txt; s=iport; t=1443198880; x=1444408480; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=RlVojNyq9gJ1HWzHycLBReErlHjGAgVHkPM8m5KG40c=; b=Ay2AsJlTjySv5vzLTyc5DVMLiG/KS3anAZrD3HbLyMPpT0EvQCW7lXYT V+2WqFAo3fqmkdCJz+pqFD5cSkBdE4CbCdS134agg4YQer7OjxsKL7g+7 ueUsrNHCaP9NiUaoc11yGUAopw0cldZO0m/bUJeUbQEbESmKpp/d5ntsA 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOAgCjdgVW/4oNJK1dgyRUaQaDJLoGAQ2BfIV3AhyBEDgUAQEBAQEBAYEKhCUBAQQjEUMSAgEIGgImAgICMBUGAQYDAgQTiC4Nt22UIQEBAQEBAQEDAQEBAQEBAQEagSKKToUUgmmBQwWMfYhqAYURh3mBT0aDcJUlHwEBQoQBcQGIZoEFAQEB
X-IronPort-AV: E=Sophos;i="5.17,587,1437436800"; d="scan'208";a="191555949"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-5.cisco.com with ESMTP; 25 Sep 2015 16:34:39 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t8PGYdt9019939 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <rtgwg@ietf.org>; Fri, 25 Sep 2015 16:34:39 GMT
Received: from xch-rcd-020.cisco.com (173.37.102.30) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 25 Sep 2015 11:34:38 -0500
Received: from xhc-rcd-x11.cisco.com (173.37.183.85) by xch-rcd-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Fri, 25 Sep 2015 11:34:38 -0500
Received: from xmb-aln-x06.cisco.com ([169.254.1.127]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0248.002; Fri, 25 Sep 2015 11:34:38 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Routing WG <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-acee-rtg-yang-key-chain-08.txt
Thread-Topic: New Version Notification for draft-acee-rtg-yang-key-chain-08.txt
Thread-Index: AQHQ96/AFH/xCFqBdEax31YDc0KftJ5NgYUA
Date: Fri, 25 Sep 2015 16:34:38 +0000
Message-ID: <D22AEF67.32D19%acee@cisco.com>
References: <20150925163216.9468.61776.idtracker@ietfa.amsl.com>
In-Reply-To: <20150925163216.9468.61776.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.36.7.23]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E73AADCECD6D0B4594A9D36D59620C60@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/q20_mO_mEaqZVbcohdg-0-p_CBo>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Sep 2015 16:34:42 -0000

Jeff, Chris, 

I’d like to request an adoption poll for the IETF Key Chain YANG model.
This version includes several additions based on conversations with Brian
Weis. 

Thanks,
Acee 

On 9/25/15, 12:32 PM, "internet-drafts@ietf.org"
<internet-drafts@ietf.org> wrote:

>
>A new version of I-D, draft-acee-rtg-yang-key-chain-08.txt
>has been successfully submitted by Acee Lindem and posted to the
>IETF repository.
>
>Name:		draft-acee-rtg-yang-key-chain
>Revision:	08
>Title:		Key Chain YANG Data Model
>Document date:	2015-09-25
>Group:		Individual Submission
>Pages:		19
>URL:            
>https://www.ietf.org/internet-drafts/draft-acee-rtg-yang-key-chain-08.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-acee-rtg-yang-key-chain/
>Htmlized:       
>https://tools.ietf.org/html/draft-acee-rtg-yang-key-chain-08
>Diff:           
>https://www.ietf.org/rfcdiff?url2=draft-acee-rtg-yang-key-chain-08
>
>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.  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.
>
>                  
>        
>
>
>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.
>
>The IETF Secretariat
>