IETF Logo Mail Archive

Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-39: (with DISCUSS and COMMENT)

Esko Dijk <esko.dijk@iotconsultancy.nl> Mon, 06 April 2020 11:19 UTC

Return-Path: <esko.dijk@iotconsultancy.nl>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01A33A0EBD for <anima@ietfa.amsl.com>; Mon, 6 Apr 2020 04:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iotconsultancynl.onmicrosoft.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 kCJBpQ6QCBD1 for <anima@ietfa.amsl.com>; Mon, 6 Apr 2020 04:19:19 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40114.outbound.protection.outlook.com [40.107.4.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 332643A0EBB for <anima@ietf.org>; Mon, 6 Apr 2020 04:19:18 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XbHgXkHMrikd2b2I35UoeqzU9zjCSpKsrEkYSh6sTAbRjqgfK5RukZ3aJODv8QJdS3IeEXfKKPPS2hi1MckTIcPV7PLcDqpuhSuMS5/+RMbOs3872SzSrnicXt3gio50HXaBLgIOACmMfrHGrHbTKMS44M2kYhDN80p2UnhXSM6/WmNE3gMTu0dWnQiS4LIGRm7W+JMN536IwSQSviqv6hTYiMctMsGYLMqDd3K8o/fA4tJHXRk8Uq2idzCiQ0ZN6SuLgAvnCx1wb6oaSIxI70k1FPKjZ8rIp1TErC47Sbd4kTJ3c13qBBA72M4mWxpsC9GJ0XiUyJJpXOJkwCLfVQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EwTt2IvXJLtGWSSg1Z6rFKu3hXB3UnOWvtjs/XqHUxg=; b=FePEmA/xu6/achhT9onk9cr7H6ondpn7PJjy17rFXDEwwt4Lef0g2oMUpHdOR5VTzdpGQeMi8gK/PuK2FtlMkvqtgO6PvEL3wmAHZl7r5LjdIR50N85eOguIFerP8ajZSOcTE17tZbc2ct+9UU65dRxwtAzhbL8XkFnQFM5TqmoG75ePd4Pm0XZSIWHq3zEzaKqU6crdMsu4u4y+nj0ciih+Q5pCIJm/6x6+NgUOK3jvuVi17x9wlAG2UDP8yE8LyCkd3tvRnjyn3o2FpbCmfW47z31ouNw+fR2lQOxdHUHWtycCU7d91Cp8EiowxhV7CLFzBLsMYAjv52RyRkZypg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=iotconsultancy.nl; dmarc=pass action=none header.from=iotconsultancy.nl; dkim=pass header.d=iotconsultancy.nl; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancynl.onmicrosoft.com; s=selector2-iotconsultancynl-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EwTt2IvXJLtGWSSg1Z6rFKu3hXB3UnOWvtjs/XqHUxg=; b=DjAIITNxlrPr+VWS/bepKs0F4G69ByU5Bsd4UApjNVQMxB5c48VnLg8EnehTuMGFfLoys74ec1wB5kzWNdg2zKQcxDIa9kX6vQHAtlmsCBAcNOuIvBrK4dvmTr/63sCMNhA+29BNqu6NQzsc0nPL5XSQGvj0Hfc/u/rdB89iJt4=
Received: from AM5P190MB0275.EURP190.PROD.OUTLOOK.COM (10.161.62.28) by AM5P190MB0500.EURP190.PROD.OUTLOOK.COM (10.161.64.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15; Mon, 6 Apr 2020 11:19:14 +0000
Received: from AM5P190MB0275.EURP190.PROD.OUTLOOK.COM ([fe80::8c96:a66b:e170:bf8f]) by AM5P190MB0275.EURP190.PROD.OUTLOOK.COM ([fe80::8c96:a66b:e170:bf8f%3]) with mapi id 15.20.2878.021; Mon, 6 Apr 2020 11:19:14 +0000
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Benjamin Kaduk <kaduk@mit.edu>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-39: (with DISCUSS and COMMENT)
Thread-Index: AQHWBu/ZmuKBXSTnP0+1TFNY1ukEm6hh9VUAgADXdgCAAF8PAIAAzCFwgAC2ZACAALWwgIAEak0AgAItZ/A=
Date: Mon, 06 Apr 2020 11:19:14 +0000
Message-ID: <AM5P190MB0275BA7298686DBADD31F0A3FDC20@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM>
References: <158561301296.11367.9776561744635554098@ietfa.amsl.com> <4603.1585620652@localhost> <20200331150202.GH50174@kduck.mit.edu> <600.1585687336@localhost> <AM5P190MB02751866462AE590EAD2EB14FDC90@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM> <5633.1585770340@localhost> <AM5P190MB027524F2D1530746DD48C4DDFDC60@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM> <13227.1586052088@localhost>
In-Reply-To: <13227.1586052088@localhost>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=esko.dijk@iotconsultancy.nl;
x-originating-ip: [85.147.167.236]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cbf27de6-b182-4a6e-a6a6-08d7da1c56c0
x-ms-traffictypediagnostic: AM5P190MB0500:
x-microsoft-antispam-prvs: <AM5P190MB0500514CFDDD4D625415DEAEFDC20@AM5P190MB0500.EURP190.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0365C0E14B
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM5P190MB0275.EURP190.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:(10019020)(136003)(366004)(376002)(346002)(39830400003)(396003)(55016002)(508600001)(5660300002)(71200400001)(81166006)(966005)(8936002)(54906003)(316002)(81156014)(76116006)(8676002)(44832011)(52536014)(66446008)(64756008)(86362001)(66556008)(66476007)(66946007)(186003)(9686003)(7696005)(6506007)(33656002)(53546011)(26005)(2906002)(4326008); DIR:OUT; SFP:1102;
received-spf: None (protection.outlook.com: iotconsultancy.nl does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: piornLLJ5ej5JQR82w2Z1BmxM4MNm+jiJex/BHkrX8lnJc3qskNxq1L4vH+vwwuI5yjQE3Kv9Anz1a/mkYYPiT2R7PznPwK6iMSEVZoMGNaUe1JEUkbg5KqD50FTwz5X2OFh/wNcGDJUu5Iez3Nupp/HlvS2BjDF1mJNSq7C9UyP66Scoj1mExt4aVD0oH3AV5TjtgKmNMQQUKIx+P/17PDzm60yRPJi47z2kslRWVi4kVsECGaiwGB57C/FB+m5qC1RY+i/5/eMK5oUwR2nvfohxwsoEG1H/BrVM5EjrxQenEEogzv5iCw6nePnhYgqH5lGeWpPeLeDizoeDmoQ+h1/1KLZr3DZN1JHN8JNj1bYN5UmOimp1iCwb1rvS02BvLVYKNtKpNqJhREnsqSOUUXzKrpskMzmRMyItgvd/Ljr0HnwjTT3tNVolXO75HyvkBh87BYpCIGRQIsiakK+t2SET4BwIlduygwwb/L7cKTpiavqqagqGV6yyTTDkt96D/VexL9/byjWqiufkTg72w==
x-ms-exchange-antispam-messagedata: T4D+CdEZSdXep02jlInaV/E/4it0ddVVEkzFlFEmXH0b0KvVxWFkBP9S+ideN4pHwxxbfckWDOexWJQTy2Usai5JTMVRxct6bAeOf0/WNDoPysSQ0BqfANE5o5pbXkO9C1Amah9WhO19kxrhPQa40g==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: iotconsultancy.nl
X-MS-Exchange-CrossTenant-Network-Message-Id: cbf27de6-b182-4a6e-a6a6-08d7da1c56c0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2020 11:19:14.3881 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 58bbf628-15d2-46bc-820b-863b6774d44b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: gDn4Frq5cQQC5UJv2og+9sBkZeoBca3iG+djAaqOvNBaeCdPluv+gTp0OY86whnJ4fkPJWdx1g3zkl4GaXjeHNxGGmKRzmzDC2Aa8KVmdjk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5P190MB0500
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/D9KHOSuDtH1gNkBPASRM5w5F-4U>
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-39: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 11:19:22 -0000

Hello Michael,

Currently BRSKI Section 5.5.4 has this text:

   The MASA MUST verify that the registrar voucher-request is signed by a registrar

If the Registrar would use a non-RA certificate e.g. ACME (LE) standard EE certificate, then it seems that it cannot get anything from MASA...?
And BRSKI would not work?

Esko

-----Original Message-----
From: Anima <anima-bounces@ietf.org> On Behalf Of Michael Richardson
Sent: Sunday, April 5, 2020 04:01
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: Benjamin Kaduk <kaduk@mit.edu>; anima@ietf.org
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-39: (with DISCUSS and COMMENT)


Esko Dijk <esko.dijk@iotconsultancy.nl> wrote:
    > The current BRSKI text to me suggests that CA:TRUE is a requirement for
    > the pinned-domain-cert. But I'm okay with not having CA:TRUE for this
    > certificate, as you propose, in which case I think the BRSKI text needs
    > some minor updates on the wording.

    > For example, if it's just a Registrar cert with CA:FALSE and RA:TRUE
    > then it shouldn't be called a "domain CA" cert or "domain cert".

    > If the Registrar is not a CA, it does need to be a Registration
    > Authority (RA). (See Section 2.5.3 / 2.5.5 / 5.5.4 /
    > https://tools.ietf.org/html/rfc6402#section-2.10 )

    > So the requirement for the pinned cert is that it is either RA or CA.
    > (Both seems also possible to encode in the cert, although that seems
    > equivalent to a CA.)

I think you that you are likely correct: every entry in a chain which is not
the EE, has CA:TRUE, and the last one, is the Registrar which ought to have
cmcRA set.

If I were to locate a PKIX-lawyer hat, I would say that the Pledge SHOULD
check this.   Given that there is a strong desire to operate registrar's
using only certificates obtained via ACME (LE), and it will be difficult to
get cmcRA set... I don't know what to do here.
  <Please insert long EMU Thread here>

We have written in the ACP document that a device SHOULD verify the cmcRA bit
is set on any EST server that the device speaks to to renew it's certificate.

Please note that I am saying "device" and not pledge!
We did not insist on cmcRA be set in section 5.1, specifically because we
didn't know if RA:TRUE was something we could insist upon here.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email