IETF Logo Mail Archive

Re: [lisp] Virtual meeting

Dino Farinacci <farinacci@gmail.com> Wed, 01 April 2020 00:38 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7234D3A0E57 for <lisp@ietfa.amsl.com>; Tue, 31 Mar 2020 17:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.53
X-Spam-Level:
X-Spam-Status: No, score=0.53 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_28=0.726, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CZ9t_V7wbPyd for <lisp@ietfa.amsl.com>; Tue, 31 Mar 2020 17:38:04 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 E87353A0E5B for <lisp@ietf.org>; Tue, 31 Mar 2020 17:38:03 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id b1so11201191pgm.8 for <lisp@ietf.org>; Tue, 31 Mar 2020 17:38:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=iA4wn3rx+wGRAGnT2UsteBtc9XjImlzz/TXSaXxF2Kc=; b=pj4eJOGBGHSwT/cIK2BCui/8hLHGi0m/nBURzuqSn64nlP5hY+5+x/5CiMEKVEaXQ8 YYOLRW4RJkk2+xAkNJ+vJ/Ftmxvi0e57qZpZ7A+auyE+pySCutUwyzSsHCF2YyzyIH6I HeF3bYISRtegCPVcOGECN+WNrhYNGmzLiWVdjskj1cpRQsYI4DwbUUz8k2+VQtoyfIhD dBpSte/Y2h72r0ltgimtUZ6l5s/isrplGKoAmm/mNNSSFamq/92MiE9k97omAOCuZb+U vjl0oX6+lvuUqg+Q0Ub00eodcFopcWuOJ9IacLT7duEQJz5nbIF81ZDymnO381AUE1gw G+DQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=iA4wn3rx+wGRAGnT2UsteBtc9XjImlzz/TXSaXxF2Kc=; b=KmHzx1WL6LywfFeJaBn6j+MvNeUw4J+Mfnsxpvs3MPBn1gFWLkgl3JelZOKGT+1K4i VQ1FawA17IYb3XoAge+9ND+Q9XYXZZFbzdfBhRgIB55PvJ5kgir5gXgtUbrbQ+O8FdlH 15MoDMLUxjYWSbe1GSBdExQr+646gvfbUkVfAWxejiV8gaCqwOBIWqVLi69W2KtG5ggQ +YJID1gYLjxTcuLyh94swvahkIVHfBAX64JAVoQ6Y/i7WPNGZTFqHYDVrWBzXn1UC/5i HygVBHOiJ5f+hT3aMCsk29XtFuhlx1x4OY3RJt6gjmxmNXhR3FY3OYkIm/kpjxvkvH4o susQ==
X-Gm-Message-State: ANhLgQ2l9BkYHwmRjrjmWv+7O8/qmxVEcA5aU4rkOA3IGtygoz9OmtDr JlD6w2OQvJPY9k7yj6W9Xxu/ED39tfA=
X-Google-Smtp-Source: ADFU+vs9vPTMkU7+f6rkNlT8YFypeJpm5fLL4iHxvdL7kee2cj19A7+JjcTT5b28uq1HYpv/0uQGFw==
X-Received: by 2002:aa7:9471:: with SMTP id t17mr20493090pfq.272.1585701483100; Tue, 31 Mar 2020 17:38:03 -0700 (PDT)
Received: from ?IPv6:2601:646:9600:af10:1896:ffbf:722e:92d5? ([2601:646:9600:af10:1896:ffbf:722e:92d5]) by smtp.gmail.com with ESMTPSA id l7sm252760pfl.171.2020.03.31.17.38.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Mar 2020 17:38:01 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <222E7375-84DD-4DEF-B349-29459F5548DE@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_65435A4E-71CE-4BAA-BA9A-F8C17D0E3318"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Date: Tue, 31 Mar 2020 17:38:00 -0700
In-Reply-To: <131b7796-c819-90c7-c7d5-3d4e86e5ec98@joelhalpern.com>
Cc: "lisp@ietf.org" <lisp@ietf.org>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
References: <bf751274-3d10-4675-40ff-0876b968ec58@joelhalpern.com> <EB8728FF-8299-4915-81C0-7A414E1A1735@gmail.com> <b2bf2e7c-9535-e6b2-51ff-dc922c875fb7@joelhalpern.com> <F0929D9F-2726-48AF-90E0-9242A5898F4C@gmail.com> <e995cd58-3504-c7b4-a970-f55550e3829b@joelhalpern.com> <0310FDA2-6AE2-472B-82A7-D38039F64DDB@cisco.com> <293fbb16-75c4-bb79-e183-eaf781b696e3@joelhalpern.com> <613F569E-6FCF-4363-A60A-CB14C6459FE2@cisco.com> <8e654897-26f6-e4c2-db74-e5a15155e04b@joelhalpern.com> <D4231D6A-A0EC-484D-BE3A-C3E31476178B@gmail.com> <e87119cf-443e-753a-1c87-0c2ae197a61a@joelhalpern.com> <9C98131B-A82E-43DE-B1F4-417018EF2C10@gmail.com> <245a8fc4-c937-887d-bf30-6070fb6a7dc6@joelhalpern.com> <1A349ADD-92F6-4945-B688-A1F1552F2136@gmail.com> <b43577df-0c51-beba-372e-5cdbb9d68f18@joelhalpern.com> <17C04FAE-6CD7-43F7-8B6F-525BD4D5AA11@gmail.com> <131b7796-c819-90c7-c7d5-3d4e86e5ec98@joelhalpern.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/LHysqmliCjBvNityyRq8yGkc2tQ>
Subject: Re: [lisp] Virtual meeting
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Apr 2020 00:38:06 -0000

Yes, you did. Great. Let’s get some opinions from the list and from the LISP-SEC experts. Fabio would have to comment on how flexible the Map-Reply Authentication Data field is to add the pubsub key-material.

Map-Request:



Map-Reply:



Dino

> On Mar 31, 2020, at 5:31 PM, Joel Halpern Direct <jmh.direct@joelhalpern.com> wrote:
> 
> Yep, that fills in the details nicely.  I started from "we should be able to bootstrap the security through lisp-sec".
> 
> Yours,
> Joel
> 
> On 3/31/2020 8:27 PM, Dino Farinacci wrote:
>>> Sorry, yes, it is the MS, not the MR, who provides the information to construct the key, since it is the MS who is generating the notifies. Sorry I still cross them up.
>> Oh good. That is more clear now. So if you are saying this:
>> (1) Use LISP-sec as defined today.
>> (2) Have the MS wrap some new key material with the MS-OTK and pass it to the ETR.
>> (3) The ETR replies as it does today but we have new protected key material in the Map-Reply.
>> (4) The MS stores the new key-material.
>> (5) The ITR generates the new key-material because it can unwrap the MS-OTK that is derived from the ITR-OTK.
>> (6) Any subsequent unsolicited Map-Notify messages from the MS (for an RLOC-change) are signed with the new key-material. Which the ITR can verify since it has the new key-material from step (5).
>> That is a shared-key created with the pair of OTKs. I think that can work. Fabio needs to verify.
>> I know you didn’t say all these details but I’m progressing your point, for discussion.
>> Dino

v2.23.0 | Report a Bug | By Email