[Rtg-yang-coord] Key Chain Cryptographic Algorithms

"Acee Lindem (acee)" <acee@cisco.com> Wed, 01 April 2015 18:20 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA5AF1A1BD7 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 11:20:15 -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 5GM-vDM7Wp5o for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 11:20:14 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB2F21A8A27 for <rtg-yang-coord@ietf.org>; Wed, 1 Apr 2015 11:20:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=760; q=dns/txt; s=iport; t=1427912412; x=1429122012; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=DwplQNfpwlNVr2AAEiL+yIyMdGMbVuzx3ev5n5vGSGE=; b=hGrWcmtgP4vS1+7CK/ASrBtGi9V998jYR0LOZ7Gb7IPVU2vZvapSOh2P 95tTzn/b8pHEl19YajntK+th6Xdc0q95f0aNEgkqKUeUzWYxeY+WsxPYr 2wdRuxF4EiEj79fauCdl4GUyWsdbAp6xdCCnbcenc933wBgAK9Ur6jEPJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A4BQD6NRxV/5ldJa1cgwaBM4MQyD8egStMAQEBAQEBfYQbIxFFEgEWDAImAgQwFRIEDog0tWaZCAEBAQEBAQEDAQEBAQEBARuBIY8Bgm+BRQWQY4l2lEAig26CM38BAQE
X-IronPort-AV: E=Sophos;i="5.11,505,1422921600"; d="scan'208";a="408418687"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 01 Apr 2015 18:20:12 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t31IKC33030878 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 18:20:12 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.236]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 13:20:12 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Jeff Haas <jhaas@pfrc.org>
Thread-Topic: Key Chain Cryptographic Algorithms
Thread-Index: AQHQbKh9Z+tYulJ3VUqZ71InoFgd5A==
Date: Wed, 1 Apr 2015 18:20:11 +0000
Message-ID: <D1417DC7.14340%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <130C30A01D325D428415B18EA8ED70D2@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/th5x6VNaEH-pt-LJguy5EJ4l49w>
Cc: Routing YANG <rtg-yang-coord@ietf.org>
Subject: [Rtg-yang-coord] Key Chain Cryptographic Algorithms
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 18:20:16 -0000

Hi Jeff, 

With respect to using identities for the list of key-chain algorithms, I
don’t believe this is necessary. We are currently using the YANG choice
statement for the cryptographic algorithm list. The gives us the
following extendibility:

   1. A given authentication algorithm can be made optional with a
feature. I tested this with pyang compilation and it works fine.

   2. The choice statement also may be augmented to add additional
      cryptographic protocols. I also tested this with pyang compilation.

Thanks,
Acee