FW: New Version Notification for draft-chen-rtg-key-table-yang-00.txt

Ing-Wher Chen <ing-wher.chen@ericsson.com> Fri, 13 March 2015 01:19 UTC

Return-Path: <ing-wher.chen@ericsson.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 EAC861AC408 for <rtgwg@ietfa.amsl.com>; Thu, 12 Mar 2015 18:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 PQFdIAJKs2bU for <rtgwg@ietfa.amsl.com>; Thu, 12 Mar 2015 18:19:10 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C8FA1A891C for <rtgwg@ietf.org>; Thu, 12 Mar 2015 18:19:10 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-48-5501d9c0e705
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 10.F7.17241.0C9D1055; Thu, 12 Mar 2015 19:24:01 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0210.002; Thu, 12 Mar 2015 21:19:09 -0400
From: Ing-Wher Chen <ing-wher.chen@ericsson.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-chen-rtg-key-table-yang-00.txt
Thread-Topic: New Version Notification for draft-chen-rtg-key-table-yang-00.txt
Thread-Index: AQHQWq4HBbA/aa5H8km053txYbu9Mp0ZoQTA
Date: Fri, 13 Mar 2015 01:19:07 +0000
Message-ID: <BF6E0BD839774345977891C597F8B50C9C9E02@eusaamb109.ericsson.se>
References: <20150309211409.17985.74578.idtracker@ietfa.amsl.com>
In-Reply-To: <20150309211409.17985.74578.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyuXSPt+7Bm4yhBi+nslhcePOb2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGb+WNTIWvJCp+L3JsoGxQ6aLkZNDQsBEYmbbdjYIW0ziwr31 QDYXh5DAEUaJld9Ps0M4yxklXrx+zQxSxSZgILHh4xYmEFtEQFWid1YrWLewQIDE/bPf2CDi gRI/v7+FqjGS+NP6FizOAlS/flYnmM0r4C3xbPEFMFtIwFGifVUvWD2ngJPEk7XrWEBsRqCL vp9aAxZnFhCXuPVkPhPEpQISS/acZ4awRSVePv7HCmErSuzrnw50NAdQvabE+l36EK2KElO6 H7JDrBWUODnzCcsERtFZSKbOQuiYhaRjFpKOBYwsqxg5SotTy3LTjQw3MQKD/pgEm+MOxgWf LA8xCnAwKvHwfjjBECrEmlhWXJl7iFGag0VJnLfsysEQIYH0xJLU7NTUgtSi+KLSnNTiQ4xM HJxSDYwxU+xbVd5/18p2sm3VMjq9/VOXgYPtb3V2uTl/JTrytm55sVHhx5X3svsck6c8sUv/ Y+7TaOn0TJ45aN3hkhVWt94cZX2r+vZbQrd3dd+cu2I2h9SiHa42TOHS+bF2xeE83qkhy7Qs Lk1J3LWM+X+UseQ3Vs19blJnrnXpvP8+6YyI6um9aVxKLMUZiYZazEXFiQBCH0z7WwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/Id68a_G0HmeEGlKPt9ZO56-GMZY>
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: <http://www.ietf.org/mail-archive/web/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, 13 Mar 2015 01:19:12 -0000

1) Key Management

The base key-chain draft <https://datatracker.ietf.org/doc/draft-acee-rtg-yang-key-chain/>
 manages authentication keys using key-chains, where a key-chain consists of a set of keys.

However, the base key-chain draft also provides the flexibility to allow for different vendor
implementations and different protocol implementations to manage authentication keys using
the key-chain concept (or even using non-keychain concepts).

2) Properties of Keys

Regardless of how keys are managed, some, if not all, of the authentication-key attributes
defined in RFC 7210 are inherent attributes of an authentication-key, and are independent
of how keys are managed.  Examples of this include the "direction" of the key and the "KDF"
to use with a key.  (RFC 7210 is the standards-track definition of data needed for routing
protocol authentication.)

This draft <https://datatracker.ietf.org/doc/draft-chen-rtg-key-table-yang/> defines
OPTIONAL additions the key-chain draft so implementations MAY include all the
authentication-key attributes described in RFC 7210.  Because these additional
authentication-key attributes are OPTIONAL, any implementation MAY choose to omit them.
For example, a router that does not support the latest TCP-AO RFC to protect BGP would
not care about the authentication-key "direction".

Thanks,
Helen

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, March 09, 2015 5:14 PM
To: Ing-Wher Chen; Ing-Wher Chen
Subject: New Version Notification for draft-chen-rtg-key-table-yang-00.txt


A new version of I-D, draft-chen-rtg-key-table-yang-00.txt
has been successfully submitted by I. Chen and posted to the IETF repository.

Name:		draft-chen-rtg-key-table-yang
Revision:	00
Title:		YANG Data Model for RFC 7210 Key Table
Document date:	2015-03-09
Group:		Individual Submission
Pages:		9
URL:            http://www.ietf.org/internet-drafts/draft-chen-rtg-key-table-yang-00.txt
Status:         https://datatracker.ietf.org/doc/draft-chen-rtg-key-table-yang/
Htmlized:       http://tools.ietf.org/html/draft-chen-rtg-key-table-yang-00


Abstract:
   This document defines a YANG data model to describe the key table
   defined in RFC 7210.  The data model defined in this document
   augments the existing key-chain model with additional key attributes
   specified in RFC 7210.

                                                                                  


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