[Iot-onboarding] BRSKI-EST and TLS Unique ID check
"M. Ranganathan" <mranga@gmail.com> Fri, 03 April 2020 16:46 UTC
Return-Path: <mranga@gmail.com>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1303C3A080A for <iot-onboarding@ietfa.amsl.com>; Fri, 3 Apr 2020 09:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 F4FEWIxEVaZK for <iot-onboarding@ietfa.amsl.com>; Fri, 3 Apr 2020 09:45:59 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 C5B8E3A0811 for <iot-onboarding@ietf.org>; Fri, 3 Apr 2020 09:45:53 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id q9so8211792iod.4 for <iot-onboarding@ietf.org>; Fri, 03 Apr 2020 09:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=qdCsr2BZ9JvkZcXRa9A2+BBfHlQWQ9HADjC064nig+M=; b=KcNQr9ha1I/OW3deH8H0MKLxToDRUUixWO2PLLXIuY5zDTIVQa8UtgQCIF5Sv1yhY+ YZAG4ROKDL9t2oAJJkpsY5M/3H2aUlBrAzRVGKIusZo7/w2ey5AHqILJNeUnB1e3Lu5P TYJBYuVag2QAYH3/CqeUT9FFutZOzwBP+Afl8lzt5sHZEOpuH4tWSKk9Zwx/poyhtoEI VdrlLFO5qD1fBvsQDowwRx6SvjhpkVazsSXzizWof0zVM8Hq6shgQFQPenCnri5fQDFY ndsLzACftp82/nyTPFGr+BEhv5u/r1Vv9kEOGohXbK6Kf3yk6dEEtlHJlIcYLXmO176Z yurg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qdCsr2BZ9JvkZcXRa9A2+BBfHlQWQ9HADjC064nig+M=; b=o4ei+C7T0nIh05P5gf9bPkolwF6oX5sQK2YQ14D/iJhfqbDvH7ltcejTSXIT1QFh77 7rLo1hkA4BS+NnDwhYjD8Dm+EbBHe5lZtZek2lBXcJbpM7RQ+z3OUFvbuNyvPMJ6cA3O NCeDicQ0e67sUIqzQfvwLW2DmYhzQZwD76zH/CVBFu3nn9DhnNcg9N7EKGlSXoU+qpqF 4o0T/u61ohj+ItjBFeCPHQs5vC4IGuaehE5Ge1mf1Cz1kfNwIyhvWFOIsOleqrG8nfl0 UkBcp48dZsX7CfKGJGXWzfk0C3cISkCd8pSR2OLFr3uXacNxKTJLF9xL33rAhnQq2sKW nNHw==
X-Gm-Message-State: AGi0PuZbI+IVPhIDAU+17UcswS8xbdPTYvEtkebvLkMZ/m8U+t9FrTH4 Z2j05Nw9u0A+V7mQTNesC1XsF4VkFdU1abFBx8iJASC1pH8=
X-Google-Smtp-Source: APiQypL/GIbvql0NK+lmgVKtt9nsNx1BH6RPgieUGhLe/keI3xccbKrq1KmPB2mh8O7f/EjHyzxN0sq5xfZpU9c5Tww=
X-Received: by 2002:a5d:970e:: with SMTP id h14mr8381529iol.133.1585932352254; Fri, 03 Apr 2020 09:45:52 -0700 (PDT)
MIME-Version: 1.0
From: "M. Ranganathan" <mranga@gmail.com>
Date: Fri, 03 Apr 2020 12:45:15 -0400
Message-ID: <CAHiu4JMF22GQBV+yNtN5ySUvJtcc8_+xj9biJLE9Dcc1YvUp9w@mail.gmail.com>
To: iot-onboarding@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/nDJDlP6GgM4P9QWcTLIIchd62V4>
Subject: [Iot-onboarding] BRSKI-EST and TLS Unique ID check
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 16:46:06 -0000
Hello, The EST spec says that if the password on a simpleenroll CSR exists then that password should match the tls unique identifier of the HTTPS connection (section 3.5). Given that BRSKI establishes a persistent HTTPS connection, is this check even required? I looked at draft-richardson-anima-registrar-considerations but I could not find anything about this so I would appreciate some clarification. Thanks, Ranga -- M. Ranganathan
- [Iot-onboarding] BRSKI-EST and TLS Unique ID check M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Dan Harkins
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Dan Harkins
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Michael Richardson
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Michael Richardson