[homenet] a clarification about cryptographic agility

Denis Ovsienko <denis@ovsienko.info> Wed, 06 April 2016 17:01 UTC

Return-Path: <denis@ovsienko.info>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8110812D5C0 for <homenet@ietfa.amsl.com>; Wed, 6 Apr 2016 10:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 j16zOd7wZ5Ud for <homenet@ietfa.amsl.com>; Wed, 6 Apr 2016 10:01:37 -0700 (PDT)
Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2632E12D57C for <homenet@ietf.org>; Wed, 6 Apr 2016 10:01:36 -0700 (PDT)
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1459962095779619.2619523789001; Wed, 6 Apr 2016 10:01:35 -0700 (PDT)
Date: Wed, 06 Apr 2016 18:01:35 +0100
From: Denis Ovsienko <denis@ovsienko.info>
To: <homenet@ietf.org>
Message-ID: <153ec85a8f4.c37ae3e63057.3819279020774176208@ovsienko.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-Zoho-Virus-Status: 1
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/pwgAwmTU78yf8zmKKD-qq2ewg-M>
Subject: [homenet] a clarification about cryptographic agility
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 17:01:39 -0000

Hello all.

In yesterday's talk about Babel profile for homenet one of the slides briefly discusses protocol authentication. In particular, it mentions 2 mandatory to implement cryptographic algorithms as a requirement of RFC 7298. It should be noted that this particular requirement more belongs to BCP 201. In short, as soon as any cryptographic algorithm becomes involved, cryptographic agility becomes a concern and the problem is best addressed at the design phase by carefully picking two MTI algorithms.

-- 
    Denis Ovsienko