Re: [lisp] About lisp crypto

Dino Farinacci <farinacci@gmail.com> Wed, 29 July 2015 00:13 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 6A0F41A0120 for <lisp@ietfa.amsl.com>; Tue, 28 Jul 2015 17:13:12 -0700 (PDT)
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 A3d4jbCzLIlw for <lisp@ietfa.amsl.com>; Tue, 28 Jul 2015 17:13:06 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::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 6CEF91A011B for <lisp@ietf.org>; Tue, 28 Jul 2015 17:13:06 -0700 (PDT)
Received: by pdbbh15 with SMTP id bh15so78817318pdb.1 for <lisp@ietf.org>; Tue, 28 Jul 2015 17:13:06 -0700 (PDT)
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=yGaf6XJI5k+EDW7ceYCpCVJz2pldeDpzMfV9yzBttag=; b=cekV9zHQayJLsJwarEpnAc9Tb96hDmq8PUA0J4EbnQYqdL9k8C9OSImIxrt/6BKE/w 5c8PAePrfuPQpe89MLOTAwq2oLcclcroLH1PYL/rzSzsGQPs36wWI6f+JRUf0phLLmoA 98n0E8HDl5JSdS/PgyzEPV8IxiZP/U9VowSJ3oXzmpQGhDgvlvhZntOPB2Qwc/FBAnr8 9fSrGXBtdgbVc0TlyfMyviP90GcHq3FO9BZgCbrVL2POzsqbaCUkHzRBOopQib4Jjj/q lv6Ru5LH+4RhLQPI6B8w+rOVb5W7au6cFu9Wcx3Y7GIgOzKgS1Y55YTBsoHY23DyXpSc O4vQ==
X-Received: by 10.70.48.34 with SMTP id i2mr85816698pdn.125.1438128785923; Tue, 28 Jul 2015 17:13:05 -0700 (PDT)
Received: from ?IPv6:2601:646:8d00:25f0:152b:255:a053:be5d? ([2601:646:8d00:25f0:152b:255:a053:be5d]) by smtp.gmail.com with ESMTPSA id cz1sm37198350pdb.44.2015.07.28.17.13.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jul 2015 17:13:04 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <29264E37AFF9384FAEBBC9C6CD32643415F12DD6@DEMUMBX011.nsn-intra.net>
Date: Tue, 28 Jul 2015 17:13:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFE0D2F8-9D8D-4E79-9281-B6E67135FE95@gmail.com>
References: <29264E37AFF9384FAEBBC9C6CD32643415F12DD6@DEMUMBX011.nsn-intra.net>
To: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/4uyDicVTDf8_6kJuj-7PSkwxeb8>
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] About 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: Wed, 29 Jul 2015 00:13:12 -0000

> On Jul 27, 2015, at 11:43 PM, Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia.com> wrote:
> 
> Hello Dino and others 
>  
> In  the last LISP WG meeting you presented changes to lisp-cypto. On slide 4 it is said that IV was added to the start of payload and ICV at the end.
> I cannot find them in the lisp-crypto-01.

The draft is a working group document so the draft name is draft-ietf-lisp-crypto-01.txt.

> See
> https://tools.ietf.org/rfcdiff?url2=draft-farinacci-lisp-crypto-01.txt
>  
> I am curious about the use of IV particularly and it relationship to the key exchange via Mappings system. Hopefully this would be described in the draft where IV and ICV are to be discussed.

The IV is locally generated by the ITR. We say how to use it in the draft.

> Best regards
> Hannu

Thanks,
Dino

>  
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp