Re: [lisp] LISP crypto

Dino Farinacci <farinacci@gmail.com> Fri, 06 November 2015 00:36 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 E6AC61A6FFE for <lisp@ietfa.amsl.com>; Thu, 5 Nov 2015 16:36:27 -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 fQAQt4imfvIq for <lisp@ietfa.amsl.com>; Thu, 5 Nov 2015 16:36:26 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (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 4023B1A6FF1 for <lisp@ietf.org>; Thu, 5 Nov 2015 16:36:26 -0800 (PST)
Received: by pasz6 with SMTP id z6so107049389pas.2 for <lisp@ietf.org>; Thu, 05 Nov 2015 16:36:26 -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=uU3RK9MhcjarH0Pw2XhSFSFU+LVwoQRB9rKz6+ZWZjk=; b=z8VRv5EU6Hftc/P3/jRts9DfwIaKb6v5UJUQoKsSXsC3jco48vk+0cfBYe5SSSOKIa AUtI0AGJBynHRp/zA5v1uIzA/tZNBTACiC0rAxJBedaQN3jdqCxXnPQfsBkcypUro7Vh jx/c11lXYliUw9oAVtA3xQWlbkn/uV1WaZiyyE7Gk5ncZR6ezGnqhyjwdc3HstgVCzYX TVxikQBvkRDa3vJVpY1pRTmuPiDU6nJYoxSCykcHTq9i8hI4DA38NqakRxYRVXstZp0a FrViK5e+WEuoNZffS6zdKc3hr0iFgzCRa0HKwjjfwNx8WMK0YjQR/CKDqc/aA0dXB581 T+3Q==
X-Received: by 10.68.227.69 with SMTP id ry5mr13575344pbc.148.1446770185941; Thu, 05 Nov 2015 16:36:25 -0800 (PST)
Received: from t20010c400000308028a91aeec12dfbcc.v6.meeting.ietf94.jp (t20010c400000308028a91aeec12dfbcc.v6.meeting.ietf94.jp. [2001:c40:0:3080:28a9:1aee:c12d:fbcc]) by smtp.gmail.com with ESMTPSA id ho3sm10080452pbb.18.2015.11.05.16.36.24 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 Nov 2015 16:36:25 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <563BF308.3010407@cs.tcd.ie>
Date: Thu, 05 Nov 2015 16:36:22 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4651FF16-9710-47D5-B1CA-0CC72C0B69E9@gmail.com>
References: <0289fb1a84a84cff89fa92a4559c829c@XCH-ALN-006.cisco.com> <FA68153A-54CE-4572-87E6-2167F6AB48F3@gmail.com> <563BF308.3010407@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/2nGtVmxeicsqPrgg7sce9vBblSU>
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 00:36:28 -0000

Okay, thanks for input Stephen, appreciated.

Dino

> On Nov 5, 2015, at 4:23 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> 
> On 06/11/15 00:03, Dino Farinacci wrote:
>> 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. 
> 
> Correct. It would be premature IMO to try to incorporate any
> functionality that aims to mitigate QC attacks against
> asymmetric crypto since we're not at a point where we know how
> to do that effectively and efficiently.
> 
>> 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.
> 
> I don't think that's needed myself.
> 
> S.
> 
>> 
>> 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
>> 
>> _______________________________________________ lisp mailing list 
>> lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
>>