Re: [lisp] LISP crypto

Dino Farinacci <farinacci@gmail.com> Fri, 06 November 2015 06:44 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 163821A9087 for <lisp@ietfa.amsl.com>; Thu, 5 Nov 2015 22:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 teN0Xm2EQpoL for <lisp@ietfa.amsl.com>; Thu, 5 Nov 2015 22:44:42 -0800 (PST)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2098F1A9068 for <lisp@ietf.org>; Thu, 5 Nov 2015 22:44:42 -0800 (PST)
Received: by ykba4 with SMTP id a4so173667169ykb.3 for <lisp@ietf.org>; Thu, 05 Nov 2015 22:44:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3BNd+4oSP0GdjN+In1mgv+zqxOiTjf3xZ3Bi7zeXsVw=; b=AgpF/Bb62aBKytt/lr0KfYmAfA9zBTCQH5+lhHYgGCbq9NItOQt58jOKhm2fYiERpx KVNuOFHjlsWD8pkESAwmfhsK+vcuSIxUHYHHKkQM5s2aAeh82PJS2oEjU3ik6Pn3rRbZ kQHTF5tY41XwPehyWwZMrUfdD/p1OXdM+7/Dm0lNT4KYcVdl18JQluv3NDacgJhdJVcq DXIfZE4tmLwOQNgWcTT8/xYIxQWxxGautbMaAZgSZ3GjaEbfUtgDDYBvJIqPfa50H4mu 0aSFcyMC7R+UQYED3XtmylsyvUmDKLRFiGCI4ZDkGifXgIlViV6FV4tccz6hyzWr23rx ingQ==
X-Received: by 10.13.242.4 with SMTP id b4mr9673113ywf.255.1446792281271; Thu, 05 Nov 2015 22:44:41 -0800 (PST)
Received: from [10.87.111.186] ([166.170.52.46]) by smtp.gmail.com with ESMTPSA id 205sm7284671ywi.55.2015.11.05.22.44.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Nov 2015 22:44:40 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (13B143)
In-Reply-To: <46848e1566054f18828428d721391388@XCH-ALN-006.cisco.com>
Date: Fri, 6 Nov 2015 15:44:35 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <326CA60F-2952-408E-B78D-2FD1540C6CEB@gmail.com>
References: <0289fb1a84a84cff89fa92a4559c829c@XCH-ALN-006.cisco.com> <FA68153A-54CE-4572-87E6-2167F6AB48F3@gmail.com> <46848e1566054f18828428d721391388@XCH-ALN-006.cisco.com>
To: "Amjad Inamdar (amjads)" <amjads@cisco.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/F_EvyioSYrIDIiWk1JmYTDbMp-k>
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] LISP crypto
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 06:44:44 -0000

In the lisp-crypto design, the ECDH shared secret is input to the KDF that produces the encryption key and integrity-check key. 

Sounds like we may already be doing what you suggest. 

And not clear to me how much more QC-safe this actually is. 

Dino

> On Nov 6, 2015, at 1:47 PM, Amjad Inamdar (amjads) <amjads@cisco.com> wrote:
> 
> Hi Dino,
> 
> The thing being proposed with IKEv2 is to include a pre-shared key in the key derivation and with sufficient entropy in the pre-shared key, this would offer fair amount of protection. You can please refer draft-fluhrer-qr-ikev2 for further details.
> 
> Thanks,
> -Amjad
> 
> -----Original Message-----
> From: Dino Farinacci [mailto:farinacci@gmail.com] 
> Sent: 06 November 2015 AM 05:34
> To: Amjad Inamdar (amjads)
> Cc: lisp@ietf.org
> Subject: Re: [lisp] LISP crypto
> 
> Amjad, we are aware of the QC-safe work going on in CFRG. We are following it but it is very researchy at this point. We can add some text indicating that we’ll follow any CFRG/SAAG recommendations (or any security area working group’s recommendation) on using QC-safe technology.
> 
> If there is anything specific you want us to look at with IKE, please send some pointers. Thanks.
> 
> Dino
> 
>> On Nov 5, 2015, at 10:37 AM, Amjad Inamdar (amjads) <amjads@cisco.com> wrote:
>> 
>> Hi Brian/Dino,
>> 
>> The key material derivation proposed in draft-ietf-lisp-crypto is based on Diffie-Hellman which is not Quantum Computer resistant. There is some work underway to make IKE that uses DH for key derivation Quantum Computer safe. Might be a good idea to consider this for lisp-crypto as well.
>> 
>> Thanks,
>> -Amjad
>> 
>> From: Amjad Inamdar (amjads)
>> Sent: 03 November 2015 PM 12:33
>> To: 'lisp@ietf.org'
>> Subject: LISP NAT Traversal
>> 
>> Hi,
>> 
>> It will be useful if LISP NAT traversal draft 
>> (draft-ermagan-lisp-nat-traversal) can elaborate on the following
>> 
>> 1) Why LISP NAT traversal cannot be accomplished without RTR (another network entity) which has implications on deployability, complexity and latency. There are other protocols (e.g IKE/IPsec) that achieve NAT-D and NAT-T without the need for additional network entity.
>> 
>> 2) Some more details on RTR deployment
>> - location of RTR in the LISP deployment like there are 
>> recommendations on PITR/PETR deployments
>> - is RTR shared across LISP sites behind NAT or each site needs a 
>> dedicated RTR
>> - what if RTR is behind another NAT (SP-NAT)
>> 
>> 3) How is multiple-NAT handled (e.g. enterprise and SP NAT)
>> 
>> Thanks,
>> -Amjad Inamdar CISSP, CCNP R&S, CCNP Security, CCDP, CCSK Senior 
>> Technical Leader CSG PI Services Security - India
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>