IETF Logo Mail Archive

Re: [lisp] Deriving Map-Register/Notify authentication key from PSK [Was: Re: Benjamin Kaduk's Discuss on draft-ietf-lisp-rfc6833bis-24: (with DISCUSS and COMMENT)]

Dino Farinacci <farinacci@gmail.com> Sat, 23 March 2019 18:06 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 E4935129532; Sat, 23 Mar 2019 11:06:41 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 4jtjr7K7pmSX; Sat, 23 Mar 2019 11:06:40 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 AAA21127963; Sat, 23 Mar 2019 11:06:40 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id j26so1640614pgl.5; Sat, 23 Mar 2019 11:06:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YCTNGXxYmMebpaphEEvuGz0FFF+fv5BW1zOfFBCDsN0=; b=h2h6XGg/XRHyQ69O9HquvvQ/Blr5G4EsOHIV/CZOs1y1zWxlSE1Zpxn0smeqLQbs6d GEPJ8bK0JyuIn3K3jImEqF1OTd1dEu73Fr7m7FFoL7A30YB6kvH8PwJDdVwdl+kS2VxR yZs0cIatO8mXgYybLgynpIJNPrx6FqwF7f8aQruPfgoUDmFHeSKorv07sAj0yWYUi3WR 8nlczpAkct8hQMqftv6seSR9TYVYRsx1L8ARlgtaB13ZOim+ef3wPmeEJ2Hgd6pHSNF4 6quBSgVnNSXqdRdYSpUSVr1Jo+Lb/0NzDKTm5QdAMlAkosu6ywO5moq1PrC994IYDQrL cAZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YCTNGXxYmMebpaphEEvuGz0FFF+fv5BW1zOfFBCDsN0=; b=LR8A7zdvRT/BKFWO9jC2X6xh1PUHyJaHvROa3l2XoHxAoPgBI+2yFvCkKVJ8Mym4sh xRmyZ2bAwYdj98QjAu+hqm6EtiChR9liunUw+zxx22Pqa5hNSVe3pG+cESHWrzxsR0Xd OSWVWgKpKOWsjGNGoJmPsVtnvyhw7UuUxNkdjJeojdQY+K1OS9qldjDHq31wjic3Sr9K 3jv3bW6J1gWAkkoWf79h1C56tlP3tRmRBCfqQR1A6CyQOLsAyZEjUqXpdKlbvG852eHt s3syK7KgIyAH4/CjVMTzPs3Ry/shuLxA76ajtU0oDt5dPowlmwSKD3lCtf3/f6fqLs8U d5zg==
X-Gm-Message-State: APjAAAUjkH1SiFIKaiHd0tjVVv7G0vCKOkMU78o2aLUNl5KW7F+65pC+ l1f+HW3bl3S6Zi+4hXp8q4CBhkIP
X-Google-Smtp-Source: APXvYqxo6AlE8sTlTve9wKUTFtR6t9tVx0PqWW2dbunGBPzIW5KzkcWjDm+pfkOS/0kgLxdWIVgnWA==
X-Received: by 2002:a62:ab14:: with SMTP id p20mr16021868pff.23.1553364400077; Sat, 23 Mar 2019 11:06:40 -0700 (PDT)
Received: from ?IPv6:2600:380:c01c:d29:7148:f06a:37dd:abae? ([2600:380:c01c:d29:7148:f06a:37dd:abae]) by smtp.gmail.com with ESMTPSA id g64sm6133872pfg.13.2019.03.23.11.06.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Mar 2019 11:06:34 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <20190323130834.GX88959@kduck.mit.edu>
Date: Sat, 23 Mar 2019 11:06:33 -0700
Cc: Fabio Maino <fmaino@cisco.com>, lisp-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-lisp-rfc6833bis@ietf.org, lisp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2350CED-72A0-40E7-A467-6F3C0975C794@gmail.com>
References: <154954743968.23471.9935733647283605722.idtracker@ietfa.amsl.com> <0d5057bf-46a4-afa2-0794-09c444cfde99@cisco.com> <20190320150544.GE80498@kduck.mit.edu> <BB32AA11-8316-4FB5-900B-234D87E140AF@gmail.com> <20190323130834.GX88959@kduck.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/vsG5j3j7wMuWnDec21YMzr6DJMM>
Subject: Re: [lisp] Deriving Map-Register/Notify authentication key from PSK [Was: Re: Benjamin Kaduk's Discuss on draft-ietf-lisp-rfc6833bis-24: (with DISCUSS and COMMENT)]
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: Sat, 23 Mar 2019 18:06:42 -0000

> I'm not sure I understand the need for "use a different key for consecutive
> messages", but probably we should just talk about that on Tuesday.

Well in your last reply you felt it was okay if we used the nonce in each Map-Register for a new key per message. 

What this addition brings is use of a different PSK with nonce for a new authentication key, per message. 

If you think it’s not necessary, we can leave it out. 

But it is not clear to me if you support app-key per Fabio’s suggestion. Can you clarify that a nonce and PSK by themselves is sufficient?

Dino

v2.23.0 | Report a Bug | By Email