IETF Logo Mail Archive

Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption

Fabio Maino <fmaino@cisco.com> Fri, 05 December 2014 22:52 UTC

Return-Path: <fmaino@cisco.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 645BC1A6FE3 for <lisp@ietfa.amsl.com>; Fri, 5 Dec 2014 14:52:35 -0800 (PST)
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 smEo20_7r1z0 for <lisp@ietfa.amsl.com>; Fri, 5 Dec 2014 14:52:34 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EB471A6FE1 for <lisp@ietf.org>; Fri, 5 Dec 2014 14:52:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=783; q=dns/txt; s=iport; t=1417819954; x=1419029554; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=XuTEb6yKSP3G+fpjESUtpqUbv+OeZR+bD4BwL8QFFiA=; b=h06KVYwPQ5qD2jg0pinKZq7mS2pzM+kpT9+LjC9juvcREF+NjWAcL4hR PD+DUyj+WiJ2VCskAYevDNXjrruI/S7sN7Uh2WvayChpAIIPhI2nmYntO msW8n86Ri7lwVAKaej2d5DjrL/JsNUbiuyCuZcgoRyQHRqHxUE/JTrJZo I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAMk2glStJA2F/2dsb2JhbABZgwaEL8Z7gmICgRcWAQEBAQF9hAMBAQQdBhVAARALGAICBRYLAgIJAwIBAgFFBgEMAQcBAYg3v0uWYgEBAQEBAQEBAQEBAQEBAQEBAQEBAReBKI8nB4JvgUcBBIowjy+Gb4xQhBAegnMBAQE
X-IronPort-AV: E=Sophos;i="5.07,525,1413244800"; d="scan'208";a="103147759"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP; 05 Dec 2014 22:52:31 +0000
Received: from [10.24.40.117] ([10.24.40.117]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id sB5MqVdB020390; Fri, 5 Dec 2014 22:52:31 GMT
Message-ID: <5482373A.9060302@cisco.com>
Date: Fri, 05 Dec 2014 14:52:42 -0800
From: Fabio Maino <fmaino@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Dino Farinacci <farinacci@gmail.com>
References: <D35D7CD0-20E5-4210-8025-7C92441DD339@gigix.net> <5480B13C.4090203@cisco.com> <97DA0D20-84D3-4478-8F90-C033E67172CD@gmail.com> <5481DCB6.6070300@cisco.com> <B8414A88-F630-4FC3-A2FC-05235D78D483@gmail.com> <54822778.6050505@cisco.com> <54822CE0.7050109@cs.tcd.ie>
In-Reply-To: <54822CE0.7050109@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/QHZ_JE1SHaV7WKit2T-zUqpZuRI
Cc: lisp@ietf.org
Subject: Re: [lisp] draft-farinacci-lisp-crypto-01 - Call for WG Adoption
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: <http://www.ietf.org/mail-archive/web/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, 05 Dec 2014 22:52:35 -0000

On 12/5/14, 2:08 PM, Stephen Farrell wrote:
>
> On 05/12/14 21:45, Fabio Maino wrote:
>> On 12/5/14, 9:36 AM, Dino Farinacci wrote:
>>>> Hi Dino,
>>>> I have no problems with the control plane part. An encap with
>>>> multiprotocol support would allow to do IPsec encap before LISP
>>>> encap, and could be used with the unauthenticated DH mechanism that
>>>> you propose.
>>> Well draft-farinacci-lisp-crypto-01 with LISP-SEC can give you an
>>> authenticated DH mechanism as well.
>> yes, but the DH mechanism itself is unauthenticated.
> There is no problem in figuring out a way to bind a DH and
> an authentication exchange. That's been done many times in
> different protocols.
>
> S.
>

Absolutely, and LISP-SEC is indeed one of the way to do it.

Fabio

v2.23.0 | Report a Bug | By Email