
From nobody Sun Dec  2 07:36:39 2018
Return-Path: <mcr@sandelman.ca>
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 2A785130EDF for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 07:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WX_6h54N2wjD for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 07:36:37 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AB8F130EDE for <anima@ietf.org>; Sun,  2 Dec 2018 07:36:37 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [90.207.60.186]) by relay.sandelman.ca (Postfix) with ESMTPS id 8AE071F8BE; Sun,  2 Dec 2018 15:36:34 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 49CC51964; Sun,  2 Dec 2018 10:36:00 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
cc: Kent Watsen <kwatsen@juniper.net>
to: "anima\@ietf.org" <anima@ietf.org>
In-reply-to: <E79F03FA-E4D7-4ED1-9552-F00300C6DD9D@juniper.net>
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <480.1543543174@dooku.sandelman.ca> <E79F03FA-E4D7-4ED1-9552-F00300C6DD9D@juniper.net>
Comments: In-reply-to Kent Watsen <kwatsen@juniper.net> message dated "Fri, 30 Nov 2018 17:37:09 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 02 Dec 2018 15:36:00 -0000
Message-ID: <3750.1543764960@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/T5-MhL4XYkWHg_Oelg_4m8-TX3k>
Subject: [Anima] a multiplicity of pinned certificates
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: Sun, 02 Dec 2018 15:36:39 -0000

--=-=-=
Content-Type: text/plain


Kent Watsen <kwatsen@juniper.net> wrote:
    > Separately, as long as we're raising issues with RFC 8366, I strongly
    > believe that the pinned-domain-certificate should've be a list of
    > certificates.  Or, in crypto-types [1] terms, a trust-anchor-cert-cms,
    > not a trust-anchor-cert-x509.  To enable the pinned-domain-certificate
    > for an intermediate CA to be a chain that includes the root self-signed
    > certificate, thus supporting tooling unable to validate partial-chains.

I believe that a future version could make this change relatively easily,
particularly if we do it quickly. Destinguishing between arrays of 1-element
and single-items isn't that difficult in the serializations we have.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwD+98ACgkQlUzhVv38
QpCO8QgAi7co9fQI1DbKzcMr7rFE03xJo0zE+bS+sOPy91ZISOTWjA88ApeQCDdf
0r5Sewwy3Td7hGchZoXSU6RJQsdE74dxnXdSw7fwIxb6TPN+1+DCkeUWcXvJD4dC
BqpAwA4YmdANJxUJf9JWKZcXwcfcT2r5FgK1105CC73qfa6GpcaQCsXF+xBMOiNB
qpP4nq80OeHg4STVix4SFlbzUMrlC1quQoqJgS7npqkC5a2A18/iLxQI+xX/2uO2
7o9zxi5toQkAtRzG3NK+eH4xQX/5OCXIVuFsetiAFDzQR+7hp0oq5rnhpJTKEinw
e9hEicYaIn9PGHV/to9Bx/5gNfHnOg==
=Y46p
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Dec  2 10:20:06 2018
Return-Path: <mcr@sandelman.ca>
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 29F9D127AC2 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 10:20:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 gQjUMBuawS49 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 10:20:02 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BFBE126CC7 for <anima@ietf.org>; Sun,  2 Dec 2018 10:20:02 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [80.233.42.178]) by relay.sandelman.ca (Postfix) with ESMTPS id 15DD51F8E8; Sun,  2 Dec 2018 18:20:00 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B51B91964; Sun,  2 Dec 2018 12:41:51 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>
In-reply-to: <6073b8f9-82e0-538b-38ba-cab272e927a1@gmail.com>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net> <69BC6F4A-1E43-4B0C-92D3-9B8D18AE4621@cisco.com> <61B8DE18-6C35-46D6-842F-B8D45520D13B@siemens.com> <7A978C68-14EF-4DEF-ADF7-9FA72E28BD4C@cisco.com> <e1a40fd5-abc1-277e-ed05-75f3d9438be0@gmail.com> <E6C9F0E527F94F4692731382340B3378148B97C9@DENBGAT9EH2MSX.ww902.siemens.net> <6073b8f9-82e0-538b-38ba-cab272e927a1@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Tue, 27 Nov 2018 08:37:17 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 02 Dec 2018 17:41:51 -0000
Message-ID: <26459.1543772511@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/E9CZQl4j023sAQktPunjrW6Ymdw>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Sun, 02 Dec 2018 18:20:05 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > OK, thanks. I'm interested in another scenario too: one where the
    > operator will not accept using a connection to the open Internet and
    > therefore will not accept any real-time access to any MASA. As I've
    > said for several years, this is a highly likely scenario in some types
    > of network which insist on air-gap security or for some other reason do
    > not trust a MASA (see Randy Bush's comments a few weeks ago,
    > e.g. https://mailarchive.ietf.org/arch/msg/anima/rK_rlT3JH0AFGlS47XSRqQB2DJI
    > ).

    > For such networks the only solution I can see is that all MASAs are
    > replaced by a single OASA (Operator Authorized Signing Authority) that
    > is configured and controlled by the operator. It handles the

    > Registrar-MASA protocol and returns vouchers exactly like a MASA,
    > except that it emphatically isn't on the global Internet. The OASA
    > would procure a long-life voucher (normally from the relevant MASA, via
    > a nonceless registrar voucher-request) when a device is purchased and
    > added to inventory, and then deliver that voucher or a short-term
    > voucher when a registrar needs it. Instead of using the MASA URL for
    > each manufacturer, registrar-to-OASA connections all use a locally
    > defined URL for the OASA. Otherwise the protocol is standard BRSKI.

So you are looking for a kind of transitivity in vouchers.
The long-lived voucher points to an intermediary, and that intermediary can
further delegate.  I originally described such a situation back in 2014.

This is from my bookmarks, I hope it's the right bookmark, as I'm writing
this offline (above Torchwood):
  https://mailarchive.ietf.org/arch/msg/6tisch-security/2kObJLkLlhuI-HU9s5yqfRm0n00

Such a system also supports resale, with the caveat that the secondary
vendors can potentially reassert their ownership!

A different system, which I'm writing up now in response to the reviews, is
that the the original vendor supports replacing the IDevID.  This permits the
first owner to change their root trust anchor to them.  They then become the
MASA for the next owner.   This requires no new protocol mechanisms.

This permits a number of scenarios including:
   1) resale without OEM permission
   2) "off-line" MASA/OASA as you describe above.
   3) ship-to-aggregator-and-forget
   4) death of OEM.

However, it requires the device to go through an enrollment cycle prior to
death of OEM, and it requires the OEM to permit the IDevID anchor to be
replaced (and the replacement to persist through factory resets).
It is not clear to me that many vendors will be willing to do this, however,
it is really the ultimate "root"ing of the device, and the OEM very
clearly no longer has any warantee or liability if this is done.

There are some half-transfer mechanisms were one could consider if the LDevID
is permitted to be used, leaving the IDevID also available.  This seems
mechanically easy, but seems to open many issues.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwEGV8ACgkQlUzhVv38
QpBBiQgAiwZ3WBnso4om2c4YOGHTtjrQDfffT94k9LP+taES/aDf5H9Qdx4L36A7
05V3xA3tXljVfdb+E8kiyr7WaHlKu75P4qVgFE51FwD8q8tlS4ZpGZddMHDgl47o
9CWOqhuOkKonbfk3sMjhQ1Oox6bqfEaLgB/iQw61Z7XiI89RxGG3aad6NM8k3yRK
OuEBRqjpBJiBlXDA5NssAdOCQTKigu6huU8GxQMQYF7ckSjD6pmvYcCttod6nbw0
cdwX7kbh0BMOYboMkiGAhIKX4lNmWMdrge6QalWOB4sUCTUYiP2a27bI1pE31zKK
nLOvijInlJ4KTcCy3rVLySDKGueESg==
=aqje
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Dec  2 10:25:03 2018
Return-Path: <mcr@sandelman.ca>
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 818B6128B14 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 10:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 I6Cn4G3Pazo6 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 10:25:00 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4090127AC2 for <anima@ietf.org>; Sun,  2 Dec 2018 10:24:59 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [80.233.42.178]) by relay.sandelman.ca (Postfix) with ESMTPS id 6C9691F8D6; Sun,  2 Dec 2018 18:24:58 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 46DF41B2C; Sun,  2 Dec 2018 12:44:46 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>
In-reply-to: <477f8964-52ca-84e6-1b4c-7f0d27cfec7b@gmail.com>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net> <69BC6F4A-1E43-4B0C-92D3-9B8D18AE4621@cisco.com> <61B8DE18-6C35-46D6-842F-B8D45520D13B@siemens.com> <7A978C68-14EF-4DEF-ADF7-9FA72E28BD4C@cisco.com> <e1a40fd5-abc1-277e-ed05-75f3d9438be0@gmail.com> <E6C9F0E527F94F4692731382340B3378148B97C9@DENBGAT9EH2MSX.ww902.siemens.net> <6073b8f9-82e0-538b-38ba-cab272e927a1@gmail.com> <2C1BC3EE-2F21-47FB-887A-681CCCAD28BD@cisco.com> <477f8964-52ca-84e6-1b4c-7f0d27cfec7b@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Wed, 28 Nov 2018 08:37:52 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 02 Dec 2018 17:44:46 -0000
Message-ID: <27027.1543772686@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/3E_b671y2Ze6_BZwqM3sz6MeGy4>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Sun, 02 Dec 2018 18:25:01 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > Indeed not. My suggestion creates no new protocol and doesn't change anything
    > for the registrar, proxy, and pledge. It recycles the registrar-MASA protocol
    > as the registrar-OASA protocol. And presumably it also recycles the registrar-MASA
    > protocol as the OASA-MASA protocol, when the OASA needs to get a new nonceless
    > voucher for a newly purchased pledge. I think there's a very modest amount
    > of "new".

I think that "My suggestion" refers to the OASA concept?

I believe that it creates new protocol in the form of extensions to 8366
processing.  I think it also requires the Registrar to contact the OASA
(overriding the MASA URL in the IDevID), but maybe you have another idea.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwEGg0ACgkQlUzhVv38
QpDx4ggAik/d2pYBV7c2+XoCz2dlhe30cyfm07SeCfhKX3Nso0V8jYPJCQsfuC7L
Geo/ONgg0A9iaRHVzcviBdv5XeNnOIJfrlX+u3XMC9EP/XnVb7bndlwIU2KBtN38
voeIblqH1MtXRlnW/sZjBA/gCrHFqtSq2dXHBJ8vzezv2joUxgDa0VAhgC2Irw8E
neBdPmczzuRRKhjJdXdur5F2rnucDUgI2W7dEzd+A3sFQD7GnZ3O2x0rCDrJkkbq
m3OGhFFPY2zFAvcHwOwmC6oxazaeek6OZnju5Fid0cxu9TjCOE397NzG1CoVrTQk
fptbIbsvlNhSP7zlIdtt1BfC1Flx7g==
=eXP0
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Dec  2 11:21:13 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 37A87128C65 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:21:12 -0800 (PST)
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 IOPZewoVAA5T for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:21:11 -0800 (PST)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 E0C7B126CC7 for <anima@ietf.org>; Sun,  2 Dec 2018 11:21:10 -0800 (PST)
Received: by mail-pf1-x42b.google.com with SMTP id b7so5223955pfi.8 for <anima@ietf.org>; Sun, 02 Dec 2018 11:21:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=pTyNoxPkD5W++TbkAJ0rDQl5Hb9YidJ+zz+xJtXeGMo=; b=TXMgH52+4YZRfMCLSzTZPi/G+wIBAif4UNNBwF81Y3WbrBpRkXD1U1Z3yMkxWSLYGG +2aTjQ3YrSBJ8yeT4Q/pGLiYemLVkkJvshx+LVaANr4xfkDqtDj9ohv/80WXo5wgN4em Dh1qrrGuPqiyeDG13nAvjnc1QASZ++zzdK4CIbnQBcVzoDSAcsobSZbAc9sJ6lb9cOmx kQzRBNvHR+ZRpoSG/J80wptrYtdqqd9I9XzKDPammEUc06/eXI/tlI0cQQdf7hAb3YzJ BqGNUTF060zFcG5vT8GM2MiNpjncxP6ZqHkLjDoLxJAVhshu2WC5mluDPhcno6YPGGTh OidA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pTyNoxPkD5W++TbkAJ0rDQl5Hb9YidJ+zz+xJtXeGMo=; b=kIXsqSj6YpD/4aveHF21qxZEQK4ExaQA2yEFDb63cZTS1l/dUnn1fr+7gujgS1yNtE fyreYXrf1r1A+Vo7e3By95AD7pqxi1dPmSSnPf2j2mHCrHmjNUjiN/yB3fx0zMEw4SEm Zlwv/AaDxjPRWEfZVfNUEEdrBAFky8wJ6jKFOJOeaoqtWHpH2EGXXn2+RtiqJoN7DG5O J6KSlXWTJxzrQA4MtJ4UeaUxo1WffA73ZL1qDOIsf63yIz7EnAs8m/wOXP48ehB04qnI He2G61FrZD/Y5Lpz3j5VPevpmTxupu1QWihdjSyPv/CBHEIEGqmvkF1La6a2Aftf1Mkj qYXw==
X-Gm-Message-State: AA+aEWaemLynavGPNa5ANbuzvmCt5E6ATjFQYUCKjGKzdjrw5ftgJIaJ rwPAeyZVsbfAeED3kAJw88Ffc+bj
X-Google-Smtp-Source: AFSGD/VJ6XxU6CwjUx8OpRTqmq/qcHC+DMl+L5UjyTaKyQ6g9gZUUsQfLBN5vqWhjsKXb0NLvSVTnA==
X-Received: by 2002:a62:6799:: with SMTP id t25mr13134824pfj.139.1543778470226;  Sun, 02 Dec 2018 11:21:10 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id 12sm10760106pgd.35.2018.12.02.11.21.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Dec 2018 11:21:09 -0800 (PST)
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net> <69BC6F4A-1E43-4B0C-92D3-9B8D18AE4621@cisco.com> <61B8DE18-6C35-46D6-842F-B8D45520D13B@siemens.com> <7A978C68-14EF-4DEF-ADF7-9FA72E28BD4C@cisco.com> <e1a40fd5-abc1-277e-ed05-75f3d9438be0@gmail.com> <E6C9F0E527F94F4692731382340B3378148B97C9@DENBGAT9EH2MSX.ww902.siemens.net> <6073b8f9-82e0-538b-38ba-cab272e927a1@gmail.com> <2C1BC3EE-2F21-47FB-887A-681CCCAD28BD@cisco.com> <477f8964-52ca-84e6-1b4c-7f0d27cfec7b@gmail.com> <27027.1543772686@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2fb7d133-4ee9-477f-fea8-1cc3e6acbd38@gmail.com>
Date: Mon, 3 Dec 2018 08:21:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <27027.1543772686@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/rl3ZRWGIA7Rxtb8qC7NgYf-88WU>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Sun, 02 Dec 2018 19:21:12 -0000

On 2018-12-03 06:44, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > Indeed not. My suggestion creates no new protocol and doesn't change anything
>     > for the registrar, proxy, and pledge. It recycles the registrar-MASA protocol
>     > as the registrar-OASA protocol. And presumably it also recycles the registrar-MASA
>     > protocol as the OASA-MASA protocol, when the OASA needs to get a new nonceless
>     > voucher for a newly purchased pledge. I think there's a very modest amount
>     > of "new".
> 
> I think that "My suggestion" refers to the OASA concept?
> 
> I believe that it creates new protocol in the form of extensions to 8366
> processing.  

Possibly. I haven't gone into the details.

> I think it also requires the Registrar to contact the OASA
> (overriding the MASA URL in the IDevID), but maybe you have another idea.

No, exactly that. 

    Brian


From nobody Sun Dec  2 11:29:08 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 11E111292F1 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 VfrmVbQ8JQ7e for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:29:05 -0800 (PST)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 CEF7A1292AD for <anima@ietf.org>; Sun,  2 Dec 2018 11:29:04 -0800 (PST)
Received: by mail-pg1-x534.google.com with SMTP id n2so4711214pgm.3 for <anima@ietf.org>; Sun, 02 Dec 2018 11:29:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=GnkDKL0EK5bLoPjmE5QjdvqdEMDmdMwh+f+f+IW7P4w=; b=if1KVYwsiCyJtPDCzxGX3t35c6O2HJxpSjgGPjIfQKdJgmM7GIqXLN4O6UcuF6DHiG sV6+Kb6D0rR7G6I5woLT758I3yQCrUpp0hUHyMstYSusSQPhzbvmgeVf8jOKhCuBkswX 7jiTTOiiJjgQ8ApC/vA6RxMkuDCt3ztwrPdidn2HNWONjW5cHDYLk7XW2zb1wSOiDpWU rehrS7uzMw2lKQQYr5X8/VJNrO9/wGoaAPp2GrijNh1z5H02zY75jLR5HHuX3OAA8mQy 6tyHDjt28GuQy2rpvs5tCoNsMX3cVpA2L2Lda6LlDj6YAjZuQUoO/ZReSLA2n5QNnHBm m+pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GnkDKL0EK5bLoPjmE5QjdvqdEMDmdMwh+f+f+IW7P4w=; b=cSecKJ78BYyGU5qqv4RniGsp/1tFgId5MnpFopvPol1jrITTrf7FbnS14/N7pbu42V VPeWRvHBjYkdSnMFvH2MIATbNqCDSdC9wek7bLkHJIqBJBBrmxguUqxb2q7nfB7r5ZXW QHa/mamrz/y7eAeRIMFG2SLhmLDhW+2NG630jFiQPdyS2Lnf1qJiElMo73FVYmB5P2+r GZ/qfG1VoVdzBXMAWFfAmpLd6D9hKPfeM4asYC8YPxCySiOrMCORqzxrzvi5oF2gYeWr kFZ82a9BFL/ntx5JX/MSaKnNEFVZXroTbSR6No6MygDxSEXu5k2dhZT4ARDOrgcbqenk RGVA==
X-Gm-Message-State: AA+aEWZvtrF4jNwJe+LrmNzH3e9Loaj1qdodPBRr3ySeEFtV853OT8eD EmcgU+fDT9KSSDxgxhlrzDTfHnKS
X-Google-Smtp-Source: AFSGD/X3byqM0JESuuCZpCNN7HyvH1FOF3qW4qaCNCWREROFKPJNN7dN9MxkdkZAzckTxT2aTVV7Qw==
X-Received: by 2002:a63:3546:: with SMTP id c67mr11247420pga.284.1543778943843;  Sun, 02 Dec 2018 11:29:03 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id b2sm20522365pgg.87.2018.12.02.11.29.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Dec 2018 11:29:03 -0800 (PST)
To: Michael Richardson <mcr@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net> <69BC6F4A-1E43-4B0C-92D3-9B8D18AE4621@cisco.com> <61B8DE18-6C35-46D6-842F-B8D45520D13B@siemens.com> <7A978C68-14EF-4DEF-ADF7-9FA72E28BD4C@cisco.com> <e1a40fd5-abc1-277e-ed05-75f3d9438be0@gmail.com> <E6C9F0E527F94F4692731382340B3378148B97C9@DENBGAT9EH2MSX.ww902.siemens.net> <6073b8f9-82e0-538b-38ba-cab272e927a1@gmail.com> <26459.1543772511@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bfb9a7ca-029b-cdb4-3fa6-705e61319747@gmail.com>
Date: Mon, 3 Dec 2018 08:28:57 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <26459.1543772511@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/RH2JEK1co_pOOPrrbLowo_Pr9k0>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Sun, 02 Dec 2018 19:29:07 -0000

On 2018-12-03 06:41, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > OK, thanks. I'm interested in another scenario too: one where the
>     > operator will not accept using a connection to the open Internet and
>     > therefore will not accept any real-time access to any MASA. As I've
>     > said for several years, this is a highly likely scenario in some types
>     > of network which insist on air-gap security or for some other reason do
>     > not trust a MASA (see Randy Bush's comments a few weeks ago,
>     > e.g. https://mailarchive.ietf.org/arch/msg/anima/rK_rlT3JH0AFGlS47XSRqQB2DJI
>     > ).
> 
>     > For such networks the only solution I can see is that all MASAs are
>     > replaced by a single OASA (Operator Authorized Signing Authority) that
>     > is configured and controlled by the operator. It handles the
> 
>     > Registrar-MASA protocol and returns vouchers exactly like a MASA,
>     > except that it emphatically isn't on the global Internet. The OASA
>     > would procure a long-life voucher (normally from the relevant MASA, via
>     > a nonceless registrar voucher-request) when a device is purchased and
>     > added to inventory, and then deliver that voucher or a short-term
>     > voucher when a registrar needs it. Instead of using the MASA URL for
>     > each manufacturer, registrar-to-OASA connections all use a locally
>     > defined URL for the OASA. Otherwise the protocol is standard BRSKI.
> 
> So you are looking for a kind of transitivity in vouchers.
> The long-lived voucher points to an intermediary, and that intermediary can
> further delegate.  I originally described such a situation back in 2014.
> 
> This is from my bookmarks, I hope it's the right bookmark, as I'm writing
> this offline (above Torchwood):
>   https://mailarchive.ietf.org/arch/msg/6tisch-security/2kObJLkLlhuI-HU9s5yqfRm0n00
> 
> Such a system also supports resale, with the caveat that the secondary
> vendors can potentially reassert their ownership!

Yes. If I'm not mistaken this would still work if the manufacturer
no longer exists and its private key has been destroyed. As I think
Randy Bush said, it's not OK if a device becomes unusable when that
happens. Basically we need transfer of ownership to mean transfer
of the ability to create a voucher. 
 
> A different system, which I'm writing up now in response to the reviews, is
> that the the original vendor supports replacing the IDevID.  This permits the
> first owner to change their root trust anchor to them.  They then become the
> MASA for the next owner.   This requires no new protocol mechanisms.
> 
> This permits a number of scenarios including:
>    1) resale without OEM permission
>    2) "off-line" MASA/OASA as you describe above.
>    3) ship-to-aggregator-and-forget
>    4) death of OEM.
> 
> However, it requires the device to go through an enrollment cycle prior to
> death of OEM, and it requires the OEM to permit the IDevID anchor to be
> replaced (and the replacement to persist through factory resets).
> It is not clear to me that many vendors will be willing to do this, however,

But then maybe people will refuse to buy their products.

> it is really the ultimate "root"ing of the device, and the OEM very
> clearly no longer has any warantee or liability if this is done.
> 
> There are some half-transfer mechanisms were one could consider if the LDevID
> is permitted to be used, leaving the IDevID also available.  This seems
> mechanically easy, but seems to open many issues.

I think all this needs to be explored in detail. Whether that is ANIMA
business is another question.

Thanks
    Brian


From nobody Sun Dec  2 11:42:43 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 D89581294D0 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:42:41 -0800 (PST)
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 XVatsPZvpZwo for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 11:42:39 -0800 (PST)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 BD748126CC7 for <anima@ietf.org>; Sun,  2 Dec 2018 11:42:39 -0800 (PST)
Received: by mail-pl1-x62d.google.com with SMTP id k8so5296057pls.11 for <anima@ietf.org>; Sun, 02 Dec 2018 11:42:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=wlpgyJdfgFnbe8Q63YkdS7OUhhYlaXJa5eKsun3T1uM=; b=a31Ov+MMi3Usz9Y6aovihqHfsa/I2bBSBgRgDuoY5Ig4unER8+O4W+mSt3UPjjTLyx vKNZ2jgeKZ3js8Ts+bSO/xkgysXL+5Ao1g93vrgYGpPiHnXszclmQ18dcmzGszmMf9P/ 9dvbD2OtVDrSmGje0ip7xmIQ5b6eJ0kJz5w0A56FYD/Tu/bDAw5ybi7tTZyai1UBghw2 QiWYkrRQT5MumBOtp7y+kNELcnUIdckHjgSXMhbYDIuqZOWHKZZC9GkGZH9DRFm+/TCt xJYJ5NiOH3J6RYwNe6nL3bOLvXwE98BM/x0x8/BZhEiVn0DAN/jpFJFBks3QqiS+Wki1 SGmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=wlpgyJdfgFnbe8Q63YkdS7OUhhYlaXJa5eKsun3T1uM=; b=l4JZ8w013QfWErF6/Oz650iToa3/6G7G0PmvDGEZJZG08BTezVB5vYchIddC69UR9s razL63TaYf1LFf5h/tIm5X+sNqeNT7ekR4Fx1uzXy98IIt/4dr4+ip7UlLBw+Mdbhbd+ arzwR5qssMshs3mW9umVUJHCXFdzvvCOlBe2HbGIOP/H8UZYGKqui36KB4mO8SZRo6XU kk+LB7vvSoqzuB2n5DpytkZpOLtfcVrRVJpOgwq31j+cwX+Qb5Z8gSgEtkNtwpkfyxYY UqYILRIFTSV3BE5NmNgkOvR3CJFOKZ16QiX8h/i3slzmgHT4fH88UZCniG05hBoa6Zk7 y8aw==
X-Gm-Message-State: AA+aEWZZ+pa9cvFQ6Ilu8IrNkowvTmRjO6nonUEDL8eKLsy7J2jNrfyT dpXOjG5bJJCGLW2pEl6TZrKYBkfj
X-Google-Smtp-Source: AFSGD/VTCVtCuSua0UvzPj0qjp+3xQvEPJizViQZ8Ur8aQBO0i6G9A+v6MZJ86Xpjl2CU1nhpDICfw==
X-Received: by 2002:a17:902:7882:: with SMTP id q2mr13651382pll.305.1543779759139;  Sun, 02 Dec 2018 11:42:39 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id z14sm18155756pgv.47.2018.12.02.11.42.37 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Dec 2018 11:42:38 -0800 (PST)
To: anima@ietf.org
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <7970.1543544813@dooku.sandelman.ca> <2e4d2c8f-67be-a78e-5930-b078e60f694b@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0f875bcf-9b99-977f-ce3b-11ed63ae4273@gmail.com>
Date: Mon, 3 Dec 2018 08:42:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <2e4d2c8f-67be-a78e-5930-b078e60f694b@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/vjBKB-Uyi0tcfZLEp8VjslL9hVA>
Subject: Re: [Anima] security review issue 11: what if MASA refuses to provide a voucher #88
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: Sun, 02 Dec 2018 19:42:42 -0000

A small clarification below...

On 2018-11-30 16:45, Brian E Carpenter wrote:
> On 2018-11-30 15:26, Michael Richardson wrote:
>>
>> https://github.com/anima-wg/anima-bootstrap/issues/88
>>
>>> What happens if the MASA refuses to provide a voucher, or provides a wrong
>>> voucher? Can the MASA be used to restrain commerce with specific countries?
>>> Is that a feature or a bug?
>>
>> BRSKI does not eliminate other mechanisms of enrolling devices.
>> If the vendor eliminates all other ways of enrolling devices, then yes, it
>> could be used as a restraint.  But, many vendors already restrict which
>> firmware can be used in which countries, and by which customers.
>>
>> It's a feature that the MASA can be used to defer theft.
>> It's a bug that the MASA can be used to prevent resale.
>> I'd love to resolve the situation, but I don't know how.
> 
> The feature is good. The bug is a regulatory issue; IANAL
> but in any case (as with DRM) it's completely outside the IETF's
> control.
> 
> Imagine a military device in such a context. You pull the trigger
> and the gun pops up a window saying "Not authorised for use
> in Elbonia." From most viewpoints, that's a Good Thing.

To be clear, the gun won't shoot because it failed to enrol
when the Elbonian army deployed it. BRSKI happens, or doesn't
happen, at enrolment time, not later.

   Brian


From nobody Sun Dec  2 12:05:31 2018
Return-Path: <mcr@sandelman.ca>
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 169C31294D0 for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 12:05:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 U-KMGbe1fwgE for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 12:05:28 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E26F128D0C for <anima@ietf.org>; Sun,  2 Dec 2018 12:05:28 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:c7d:b752:2f00:c3eb:b5be:80ee:7c56]) by relay.sandelman.ca (Postfix) with ESMTPS id 78D3C1F8BE; Sun,  2 Dec 2018 20:05:25 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 8E16014F2; Sun,  2 Dec 2018 12:30:03 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>
cc: "Fries\, Steffen" <steffen.fries@siemens.com>
In-reply-to: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net>
Comments: In-reply-to "Fries, Steffen" <steffen.fries@siemens.com> message dated "Fri, 23 Nov 2018 16:53:45 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 02 Dec 2018 17:30:03 -0000
Message-ID: <24056.1543771803@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/s0TfTjac77gqBaHrn57yyHw5Vvg>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Sun, 02 Dec 2018 20:05:30 -0000

--=-=-=
Content-Type: text/plain


Fries, Steffen <steffen.fries@siemens.com> wrote:
    > Besides this, we see further use cases, in which the connection to the PKI is
    > not always available. This may be the case if the connection to the CA is only
    > temporary available or not directly available. Here, the approach would require
    > a rather asynchronous handling. In such a setup the domain registrar could for
    > instance store the object (certification request) and forward it upon
    > connectivity to the PKI for further processing. The forward may be based on a
    > communication connection or even manually. This asynchronous approach requires
    > that the object itself is self-protecting ensuring its integrity (like a PKCS#7
    > wrapping of the PKCS#10 request or similar). Based on the specified BRSKI
    > features, we did not see the support for this type of requirements directly.

BRSKI is simply the mechanism to create a secure channel.
What happens afterwards is up to EST-RFC7030 (or something else, but the ANIMA
ACP specifies EST-RFC7030).

7030 section 4.2.3 says, near the end:

   If the server responds with an HTTP [RFC2616] 202, this indicates
   that the request has been accepted for processing but that a response
   is not yet available.  The server MUST include a Retry-After header
   as defined for HTTP 503 responses.  The server also MAY include
   informative human-readable content.  The client MUST wait at least
   the specified "retry-after" time before repeating the same request.
   The client repeats the initial enrollment request after the
   appropriate "retry-after" interval has expired.  The client SHOULD
   log or inform the end-user of this event.  The server is responsible
   for maintaining all states necessary to recognize and handle retry
   operations as the client is stateless in this regard; it simply sends
   the same request repeatedly until it receives a different response
   code.  All other return codes are handled as specified in HTTP
   [RFC2616].

so a delayed reply is permissible.
BRSKI could perhaps be more clear about whether the pledge is expected to:
 1) keep the TLS connection open.
 1B) do this virtually via TLS session resumption ticket
 2) if it closes it, should it keep track of the Registrar certificate?
 3) alternatively, should it try again and expect a voucher to be presented?
   (which gets into: whether it records the nonce, and is happy with a
   replay of the nonced voucher it got before)



{I found the non-standard quoting styles and HTML parts made the thread
incredibly difficult to follow.  We have access to WG lists via IMAP,
so you can use quite a number of programs other than what your IT department
expects you to use for email.}

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwEFpsACgkQlUzhVv38
QpA5JwgAj54LoTnq9YLI5zEBA3PhkBm9WbZ2DLa2ISGhiIlBAs7PKkW3StxInntp
O7VkNleBHXK6M56qa2C6LS2HXINGMjrFrew2oV7msDfEEBaOKFAjev/grMmAyzJd
lw9LRwilWtDaSsIu2r1rKfESsAtPLD68ZEcvNuP5Qkj3aGtVgHp6EzNl4Gzm30AF
2z3MZJClvOVm9RPOru5/R5VjFo25okU6KVpXxHI4YrVImbglcXBY/GJPmdkngLYM
b+fGd8p+o0VhMW9SWGrKDqUF4FP81LI1cZLbcBHeni4KkmLPk5nWFMV12quegMDd
m/ulWg0F6YTFwDgrx7wheVTcJoDXLA==
=rQ71
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Dec  2 15:54:26 2018
Return-Path: <mcr@sandelman.ca>
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 C7361130DCF for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 15:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 DR-wDE1y_ymE for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 15:54:21 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90C1D130DD8 for <anima@ietf.org>; Sun,  2 Dec 2018 15:54:20 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:c7d:b752:2f00:c3eb:b5be:80ee:7c56]) by relay.sandelman.ca (Postfix) with ESMTPS id 825411F8BE for <anima@ietf.org>; Sun,  2 Dec 2018 23:54:19 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id E260614F2; Sun,  2 Dec 2018 23:53:47 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-reply-to: <0b517731-ef11-4484-7bf8-46e313a2ac49@gmail.com>
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <0b517731-ef11-4484-7bf8-46e313a2ac49@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Fri, 30 Nov 2018 13:57:26 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 02 Dec 2018 23:53:47 -0000
Message-ID: <24016.1543794827@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WSBO4JB_CwjO7BKGevxyAmopbzw>
Subject: Re: [Anima] [Gen-art] dealing with many the secdir and genart comments [on draft-ietf-anima-bootstrapping-keyinfra]
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: Sun, 02 Dec 2018 23:54:24 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> The authors seriously believe that this will result in an attempt to
    >> boil the ocean.  Yes, BRSKI is exciting for many and opens many door=
s,
    >> but in the context of the *ANIMA* Charter, we strongly think that th=
is
    >> document should leave the oceans alone, and deal only with the ANIMA
    >> ACP usage.

    > Yes, violent agreement. From all the interest outside ANIMA, the basic
    > idea of BRSKI is a big hit and will be re-used in other contexts. I
    > think a strong statement about the specific scope of *this* document
    > belongs in the Abstract and Introduction, with a comment that variant
    > usages of BRSKI in other scenarios will be documented separately.

Brian, these are my proposed changes to the abstract, intro,
and adding a section on ACP Applicability.  I think that there is probably
more to say there.

This has become issue #116.

diff --git a/dtbootstrap-anima-keyinfra.xml b/dtbootstrap-anima-keyinfra.xml
index 78ce2a3..e705904 100644
=2D-- a/dtbootstrap-anima-keyinfra.xml
+++ b/dtbootstrap-anima-keyinfra.xml
@@ -82,19 +82,21 @@
=20
     <abstract>
       <t>
=2D        This document specifies automated bootstrapping of a remote secu=
re
=2D        key infrastructure (BRSKI) using manufacturer installed X.509 ce=
rtificate, in
=2D        combination with a manufacturer's authorizing service, both onli=
ne and offline.
+        This document specifies automated bootstrapping of an Autonomic
+        Control Plane.  To do this a remote secure
+        key infrastructure (BRSKI) is created using manufacturer installed
+        X.509 certificate, in combination with a manufacturer's authorizing
+        service, both online and offline.=20
         Bootstrapping a new device can occur using a routable address and a
         cloud service, or using only link-local connectivity, or on
         limited/disconnected networks. Support for lower security models,
         including devices with minimal identity, is described for legacy r=
easons
=20
@@ -103,7 +105,22 @@
       <t>
         BRSKI provides a solution for secure zero-touch (automated) bootst=
rap of
         virgin (untouched) devices that are called pledges in this
=2D        document. These pledges need to discover (or be discovered by) an
+        document.
+      </t>
+=20=20=20=20=20=20
+      <t>
+        This document primarily provides for the needs of
+        the ISP and Enterprise focused ANIMA=20
+        <xref target=3D"I-D.ietf-anima-autonomic-control-plane">Autonomic=
=20
+        Control Plane (ACP)</xref>.  Other users of the BRSKI protocol
+        will need to provide separate applicability statements that
+        include privacy and security considerations appropriate to that
+        deployment.  Section <xref target=3D"acpapplicability" /> explains=
 the details
+        applicability for this the ACP usage.
+      </t>
+=20=20=20=20=20=20
+      <t>
+        This document describes how pledges discover (or be discovered by)=
 an
         element of the network domain to which the pledge belongs to perfo=
rm
         the bootstrap.  This element (device) is called the
         registrar.  Before any other operation, pledge and registrar need =
to

@@ -2755,6 +2772,64 @@ Reference: [This document]
 	  </t>
 	</section>
     </section>
+    <section anchor=3D"acpapplicability" title=3D"Applicability to the Aut=
onomic
+                                              Control Plane">
+      <t>
+        This document provides a solution to the requirements for secure
+        bootstrap set out in <xref target=3D"RFC8368">Using an Autonomic C=
ontrol Plane for
+        Stable Connectivity of Network Operations, Administration, and
+        Maintenance </xref>,=20
+        <xref target=3D"I-D.ietf-anima-reference-model" >A Reference Model=
 for
+        Autonomic Networking</xref> and specifically the=20
+        <xref target=3D"I-D.ietf-anima-autonomic-control-plane">An Autonom=
ic
+        Control Plane (ACP)</xref>, section 3.2 (Secure Bootstrap), and
+        section 6.1 (ACP Domain, Certificate and Network).
+      </t>
+      <t>
+        The protocol described in this document has appeal in a number of
+        other non-ANIMA use cases.  Such uses of the protocol will be
+        deploying into other environments with different tradeoffs of
+        privacy, security, reliability and autonomy from manufacturers.
+        As such those use cases will need to provide their own applicabili=
ty
+        statements, and will need to address unique privacy and security
+        considerations for the environments in which they are used.
+      </t>
+      <t>
+        The autonomic control plane that this document provides bootstrap
+        for is typically a medium to large Internet Service Provider
+        organization, or an equivalent Enterprise that has signficant laye=
r-3
+        router connectivity.  (A network consistenting of primarily layer-2
+        is not excluded, but the adjacencies that the ACP will create and
+        maintain will not reflect the topology until all devices participa=
te
+        in the ACP).
+      </t>
+      <t>
+        As specified in the ANIMA charter, this work "..focuses on
+        professionally-managed networks."  Such a network has an operator
+        and can do things like like install, configure and operate the
+        Registrar function.  The operator makes purchasing decisions
+        and is aware of what manufacturers it expects to see on it's
+        network.
+      </t>
+      <t>
+        Such an operator also is capable of performing the traditional
+        (craft serial-console) based bootstrap of devices. The zero-touch
+        mechanism presented in this and the ACP document represents a
+        signficiant efficiency: in particular it reduces the need to
+        put senior experts on airplanes to configure devices in person.
+        There is a recognition as the technology evolves that not every
+        situation may work out, and occasionally a human still still have =
to
+        visit.
+      </t>
+      <t>
+        The BRSKI protocol is going into environments where there have
+        already been quite a number of vendor proprietary management
+        systems.  Those are not expected to go away quickly, but rather to
+        leverage the secure credentials that are provisioned by BRSKI.  The
+        connectivity requirements of said management systems are provided
+        by the ACP.
+      </t>
+    </section>
     <section anchor=3D"privacyconsiderations" title=3D"Privacy Considerati=
ons">
       <section title=3D"MASA audit log">
       <t>
@@ -3292,6 +3367,7 @@ Reference: [This document]
=20
       <?rfc include=3D"reference.I-D.ietf-anima-autonomic-control-plane" ?>
       <?rfc include=3D"reference.RFC.8366" ?>
+      <?rfc include=3D"reference.RFC.8368" ?>
       <?rfc include=3D"reference.I-D.ietf-anima-grasp" ?>
=20
       <reference anchor=3D"IDevID"

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwEcIsACgkQlUzhVv38
QpC4Tgf/ZX7zBE0DPN85itKTqVESHY5oMC1DRKXK2uFg0+y8ppiJLqDWFkYaL7UR
R5ZhH+0/fbKSa1vs9coDqR48Ov4DjNx/h4u9+4fQIAprszL1zoTtyn1R5XREHz/H
ywZ9bGbNHYAs3EVhnlwFZTl8X8ih4aSO16/QHLoNWT3KwEQ4iNrOTiEl+/IodY4C
Vu6HHfynxwjT/JS4J9ucm08sxkE2bFTmaT9u6MhsDLE5PlzMxBfL0uu/qImLwLnR
G174S/rkT+3H6I+6ns2q0o27KYGVK6CDcJ626kM1WefpVJsSn0tJwKiJ0bGWHxdZ
N8YGLIqtEvXNWchqxJqDQVU6gwq66Q==
=hlYk
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Dec  2 16:06:45 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 13C34130DDB for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 16:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 GFwcDFM41cdO for <anima@ietfa.amsl.com>; Sun,  2 Dec 2018 16:06:41 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 23CC8129533 for <anima@ietf.org>; Sun,  2 Dec 2018 16:06:41 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id b7so5411836pfi.8 for <anima@ietf.org>; Sun, 02 Dec 2018 16:06:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=0xaVhjSCxSjsAGwroCkCaWs09vZPnkjDrcJxlTVE0lM=; b=H+oDylSHvyDgUY73/XkfDDpqMX+Lq5cQgFQ6AcYWOIigS+Il5Jo8YjJ3gFNqFD5JGz 8gnHWoTu0wsygs5kzoMk1IrGwjXb4z+oxa8Go5GK/f1GxWcvsmZ8v3oAfbSwPqeOi1Pn Qa/8PvcPBb4siIEPZ/jTQsevSYXpNw4BrheZHVRFoU59uD00WLkEE/YGDpEqW40XOU6c 6a93jQr53iDYvIs9u5DLmy/lQPTNwq5y6QfHz4DrjH38izJ+UavSJTXdiWXYhA0pZdxK Qbj9DiZlfFEoOPHAp1BQedCxQs0YXLD66MP5Y4PgoICCBTOCeVZpb0iuorNKGCWnUCy7 hAoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0xaVhjSCxSjsAGwroCkCaWs09vZPnkjDrcJxlTVE0lM=; b=S/HaujWB4qu6cToXUEZmtVF4mHRocfIu6E1V02TQ/01khljzE2bgK8ZeDo1t5k/RQ1 s9YLCKus2rEwP/IK7q79ZHXUJLmhC8KGljoz9aev1nfh79PuZ2ZRAAMa9+jyIFNI9OAD KkgPUefKx7FGbn8IJNbhrm9+ngWFA9kj9Atzh/N/ieZKIv9YRJSTJxFQgflavXeQuMny j7uUNc6/9UAnsXvMJcHwUIRMyMw/QfMfh5vhOAs9XcArD4VLTXb9L2zjDilpclSJoF13 Pqh8i7QvSnaB7gkygCUEXytQksdBa/e6jOk29DBjg82MaSC8tm59oDxGrBsC4E2klW6d Bgcw==
X-Gm-Message-State: AA+aEWYTS8u1SHs/bLCnlMwmbx9sB6qHE5ZfpXpg91qt7AqzwvFS/1y1 /UHoYz2zGUNDemqlcC5b+4GE8xKD
X-Google-Smtp-Source: AFSGD/W0M8+fi3UGhTvGnR+Y9WIC4Lbh02Zosa7VQ1yvbP0lE0vPYpxDObfv5lPX9IhJ9s++ySkS2Q==
X-Received: by 2002:a62:546:: with SMTP id 67mr13479767pff.99.1543795600175; Sun, 02 Dec 2018 16:06:40 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id w88sm4087510pfk.11.2018.12.02.16.06.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Dec 2018 16:06:39 -0800 (PST)
To: Michael Richardson <mcr+ietf@sandelman.ca>, anima@ietf.org
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <0b517731-ef11-4484-7bf8-46e313a2ac49@gmail.com> <24016.1543794827@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f6002a83-b292-b323-04ee-d0d26acdd782@gmail.com>
Date: Mon, 3 Dec 2018 13:06:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <24016.1543794827@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/eCqd6V80ORCO1_9tJ9M8ufvqP3g>
Subject: Re: [Anima] [Gen-art] dealing with many the secdir and genart comments [on draft-ietf-anima-bootstrapping-keyinfra]
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, 03 Dec 2018 00:06:44 -0000

On 2018-12-03 12:53, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> The authors seriously believe that this will result in an attempt to
>     >> boil the ocean.  Yes, BRSKI is exciting for many and opens many doors,
>     >> but in the context of the *ANIMA* Charter, we strongly think that this
>     >> document should leave the oceans alone, and deal only with the ANIMA
>     >> ACP usage.
> 
>     > Yes, violent agreement. From all the interest outside ANIMA, the basic
>     > idea of BRSKI is a big hit and will be re-used in other contexts. I
>     > think a strong statement about the specific scope of *this* document
>     > belongs in the Abstract and Introduction, with a comment that variant
>     > usages of BRSKI in other scenarios will be documented separately.
> 
> Brian, these are my proposed changes to the abstract, intro,
> and adding a section on ACP Applicability.  I think that there is probably
> more to say there.

Perhaps, but I think these changes clarify the scope correctly.

Thanks
     Brian

> 
> This has become issue #116.
> 
> diff --git a/dtbootstrap-anima-keyinfra.xml b/dtbootstrap-anima-keyinfra.xml
> index 78ce2a3..e705904 100644
> --- a/dtbootstrap-anima-keyinfra.xml
> +++ b/dtbootstrap-anima-keyinfra.xml
> @@ -82,19 +82,21 @@
>  
>      <abstract>
>        <t>
> -        This document specifies automated bootstrapping of a remote secure
> -        key infrastructure (BRSKI) using manufacturer installed X.509 certificate, in
> -        combination with a manufacturer's authorizing service, both online and offline.
> +        This document specifies automated bootstrapping of an Autonomic
> +        Control Plane.  To do this a remote secure
> +        key infrastructure (BRSKI) is created using manufacturer installed
> +        X.509 certificate, in combination with a manufacturer's authorizing
> +        service, both online and offline. 
>          Bootstrapping a new device can occur using a routable address and a
>          cloud service, or using only link-local connectivity, or on
>          limited/disconnected networks. Support for lower security models,
>          including devices with minimal identity, is described for legacy reasons
>  
> @@ -103,7 +105,22 @@
>        <t>
>          BRSKI provides a solution for secure zero-touch (automated) bootstrap of
>          virgin (untouched) devices that are called pledges in this
> -        document. These pledges need to discover (or be discovered by) an
> +        document.
> +      </t>
> +      
> +      <t>
> +        This document primarily provides for the needs of
> +        the ISP and Enterprise focused ANIMA 
> +        <xref target="I-D.ietf-anima-autonomic-control-plane">Autonomic 
> +        Control Plane (ACP)</xref>.  Other users of the BRSKI protocol
> +        will need to provide separate applicability statements that
> +        include privacy and security considerations appropriate to that
> +        deployment.  Section <xref target="acpapplicability" /> explains the details
> +        applicability for this the ACP usage.
> +      </t>
> +      
> +      <t>
> +        This document describes how pledges discover (or be discovered by) an
>          element of the network domain to which the pledge belongs to perform
>          the bootstrap.  This element (device) is called the
>          registrar.  Before any other operation, pledge and registrar need to
> 
> @@ -2755,6 +2772,64 @@ Reference: [This document]
>  	  </t>
>  	</section>
>      </section>
> +    <section anchor="acpapplicability" title="Applicability to the Autonomic
> +                                              Control Plane">
> +      <t>
> +        This document provides a solution to the requirements for secure
> +        bootstrap set out in <xref target="RFC8368">Using an Autonomic Control Plane for
> +        Stable Connectivity of Network Operations, Administration, and
> +        Maintenance </xref>, 
> +        <xref target="I-D.ietf-anima-reference-model" >A Reference Model for
> +        Autonomic Networking</xref> and specifically the 
> +        <xref target="I-D.ietf-anima-autonomic-control-plane">An Autonomic
> +        Control Plane (ACP)</xref>, section 3.2 (Secure Bootstrap), and
> +        section 6.1 (ACP Domain, Certificate and Network).
> +      </t>
> +      <t>
> +        The protocol described in this document has appeal in a number of
> +        other non-ANIMA use cases.  Such uses of the protocol will be
> +        deploying into other environments with different tradeoffs of
> +        privacy, security, reliability and autonomy from manufacturers.
> +        As such those use cases will need to provide their own applicability
> +        statements, and will need to address unique privacy and security
> +        considerations for the environments in which they are used.
> +      </t>
> +      <t>
> +        The autonomic control plane that this document provides bootstrap
> +        for is typically a medium to large Internet Service Provider
> +        organization, or an equivalent Enterprise that has signficant layer-3
> +        router connectivity.  (A network consistenting of primarily layer-2
> +        is not excluded, but the adjacencies that the ACP will create and
> +        maintain will not reflect the topology until all devices participate
> +        in the ACP).
> +      </t>
> +      <t>
> +        As specified in the ANIMA charter, this work "..focuses on
> +        professionally-managed networks."  Such a network has an operator
> +        and can do things like like install, configure and operate the
> +        Registrar function.  The operator makes purchasing decisions
> +        and is aware of what manufacturers it expects to see on it's
> +        network.
> +      </t>
> +      <t>
> +        Such an operator also is capable of performing the traditional
> +        (craft serial-console) based bootstrap of devices. The zero-touch
> +        mechanism presented in this and the ACP document represents a
> +        signficiant efficiency: in particular it reduces the need to
> +        put senior experts on airplanes to configure devices in person.
> +        There is a recognition as the technology evolves that not every
> +        situation may work out, and occasionally a human still still have to
> +        visit.
> +      </t>
> +      <t>
> +        The BRSKI protocol is going into environments where there have
> +        already been quite a number of vendor proprietary management
> +        systems.  Those are not expected to go away quickly, but rather to
> +        leverage the secure credentials that are provisioned by BRSKI.  The
> +        connectivity requirements of said management systems are provided
> +        by the ACP.
> +      </t>
> +    </section>
>      <section anchor="privacyconsiderations" title="Privacy Considerations">
>        <section title="MASA audit log">
>        <t>
> @@ -3292,6 +3367,7 @@ Reference: [This document]
>  
>        <?rfc include="reference.I-D.ietf-anima-autonomic-control-plane" ?>
>        <?rfc include="reference.RFC.8366" ?>
> +      <?rfc include="reference.RFC.8368" ?>
>        <?rfc include="reference.I-D.ietf-anima-grasp" ?>
>  
>        <reference anchor="IDevID"
> 
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> 


From nobody Mon Dec  3 01:23:40 2018
Return-Path: <mcr@sandelman.ca>
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 A85AD130E2A for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 01:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 56g_8OuM3bTP for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 01:23:34 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAB74126C01 for <anima@ietf.org>; Mon,  3 Dec 2018 01:23:33 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:c7d:b752:2f00:c3eb:b5be:80ee:7c56]) by relay.sandelman.ca (Postfix) with ESMTPS id A2C311F8BD; Mon,  3 Dec 2018 09:23:31 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B82251704; Mon,  3 Dec 2018 09:22:59 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org
In-reply-to: <f6002a83-b292-b323-04ee-d0d26acdd782@gmail.com>
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <0b517731-ef11-4484-7bf8-46e313a2ac49@gmail.com> <24016.1543794827@dooku.sandelman.ca> <f6002a83-b292-b323-04ee-d0d26acdd782@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Mon, 03 Dec 2018 13:06:33 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 03 Dec 2018 09:22:59 -0000
Message-ID: <10330.1543828979@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/3u4BiwdrGz_CJVOBMUuW00Hbkao>
Subject: Re: [Anima] [Gen-art] dealing with many the secdir and genart comments [on draft-ietf-anima-bootstrapping-keyinfra]
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, 03 Dec 2018 09:23:36 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> >> The authors seriously believe that this will result in an attempt=
 to
    >> >> boil the ocean.  Yes, BRSKI is exciting for many and opens many d=
oors,
    >> >> but in the context of the *ANIMA* Charter, we strongly think that=
 this
    >> >> document should leave the oceans alone, and deal only with the AN=
IMA
    >> >> ACP usage.
    >>=20
    >> > Yes, violent agreement. From all the interest outside ANIMA, the b=
asic
    >> > idea of BRSKI is a big hit and will be re-used in other contexts. I
    >> > think a strong statement about the specific scope of *this* docume=
nt
    >> > belongs in the Abstract and Introduction, with a comment that vari=
ant
    >> > usages of BRSKI in other scenarios will be documented separately.
    >>=20
    >> Brian, these are my proposed changes to the abstract, intro,
    >> and adding a section on ACP Applicability.  I think that there is pr=
obably
    >> more to say there.

    > Perhaps, but I think these changes clarify the scope correctly.

My sense in writing the words was that there were more words needed.
But I didn't know what else I could nail down scope-wise, so I stopped.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwE9fMACgkQlUzhVv38
QpCn5Af/eEs8pqnBda8e+EeRwMuBjscc0QX4E7qk+a3f1wuzPE6o0oWRfAEQgst9
eXvgAdxk6G+7m+mCPjIgAJ3pNyBVTHlZlrDZ30E9xVHhu1Ho3EtOKOBSB5QMLtsM
Vhf6iFIeGZea3/tkguTU2pxLvRkw9X3N0OIhjzQ9fwhNThFlIkj/3reRW51sNNxe
tPE47ORN28NkEUTA3BvFyKGa7J3NRAfwxZJHsmu/G/uf9O7etWkXdn/0vMbFw1Tq
2noomcVmAqQEWPhWlCWaSHZjHbSgnc5C/sU82aARC8rzzZnoGjoE1S32DSU6O3RJ
VFRhz3uYtxo/rTxfWLm1qGkRnAdXrw==
=LMBI
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Dec  3 04:10:46 2018
Return-Path: <mcr@sandelman.ca>
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 9ED32130E77 for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 04:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 G0RckmV__cjz for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 04:10:41 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96A53130E98 for <anima@ietf.org>; Mon,  3 Dec 2018 04:10:41 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [185.201.60.232]) by relay.sandelman.ca (Postfix) with ESMTPS id CCBC51F8BD; Mon,  3 Dec 2018 12:10:37 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id A7AFA3AF2; Mon,  3 Dec 2018 12:09:50 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: max pritikin <pritikin@cisco.com>, anima@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 03 Dec 2018 12:09:50 -0000
Message-ID: <19433.1543838990@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/5Zo94tjmq6FQdrnPDYhflUI7C3w>
Subject: [Anima] underspecification in handling of unsigned voucher requests
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, 03 Dec 2018 12:10:45 -0000

--=-=-=
Content-Type: text/plain


Max, one of the hurdles that the Fairhair Alliance interop experienced was
due to under-specification of the unsigned pledge request.  Most implemented
unsigned pledge requests because it was simpler.

In the past two weeks I was trying to implement unsigned pledge requests, and
I had a number of assumptions challenged in the process.
I am seriously of the opinion that unsigned voucher requests (whether
constrained or not) may have no value at all and should be removed.
(At least, I would like to write that they are unwelcome in the ACP
applicability section)

Assumptions I had which were not verified by our text:

1) that the unsigned voucher request should be placed into
   prior-signed-voucher-request in (parboiled: Registrar->MASA)
   voucher-request.
   The MASA can distinguish between a signed object (which may be a voucher
   request, or a prior signed voucher for renewals[%1]).

2) that the unsigned voucher request should even be copied to the MASA *AT ALL*
   We don't say anything about that.  We hardly even talk about the
   processing.
   I enclose text/diff at the bottom to change that.

3) I assumed that the proximity-registrar-cert has meaning in the unsigned
   voucher-request.  One might claim that it's presence provides no value at
   all since the request is not signed.
   The only piece that has any value would seem to be the nonce.
   So if the pledge has a clock and does not need freshness in it's voucher,
   it could use a time-limited voucher (expiry-on set), then it would
   essentially send an empty voucher-request.  This surprised me to realize.

4) If the unsigned voucher-request has no value/content, why send it on to
   the MASA at all.  I pondered this for awhile, and then remembered that
   this is a channel from the Pledge to the MASA, and that we wanted to
   permit this channel to be extensible and available for proprietary uses if
   desired.  We have this for signed voucher-requests as is.
   If we want to maintain this for unsigned voucher-requests, then we need
   to mandate that it be passed upwards.

Putting unsigned (JSON) into prior-signed-voucher-request seems wrong from a
YANG point of view: see next message on that.

[%1] - can vouchers with nonces be renewed by the MASA?  I think we will need
     clarifying text once someone has implemented this.

diff --git a/dtbootstrap-anima-keyinfra.txt b/dtbootstrap-anima-keyinfra.txt
index a5c4163..8ac806b 100644
--- a/dtbootstrap-anima-keyinfra.txt
+++ b/dtbootstrap-anima-keyinfra.txt
@@ -2062,17 +2118,30 @@ Internet-Draft                    BRSKI                    November 2018
    Example 1.

    The registrar validates the client identity as described in EST
-   [RFC7030] section 3.3.2.  If the request is signed the registrar
-   confirms that the 'proximity' asserion and associated 'proximity-
-   registrar-cert' are correct.

+   [RFC7030] section 3.3.2.  This involves validating the signatory of
+   the TLS Client Certificate.  As described in the next section, there
+   are different models for authorizing accepted devices.

+
+
+   If the request is signed the registrar confirms that the voucher-
+   request is signed by the same key as terminates the TLS connection.

+   The Registrar extracts the serial-number of the pledge from the TLS
+   Client Certificate.  It uses this serial-number to form it's voucher-
+   request.
+
+   The Registrar examines the pledge's voucher-request (verifying the
+   signature, if the request is signed) and extracts any nonce present
+   to include in it's voucher-request.  In addition, any 'proximity'
+   assertion and associated 'proximity-registrar-cert' need to be
+   verified to be correct.




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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwFHQ4ACgkQlUzhVv38
QpCEIAf9HwvXXGEu+cxPJX4tNXrLM59FEUSKzcpqFfhl5F4IgU7BlonQ2yWKPpSI
37JHOOrF7yYmdUreRGoIekNBALpYnhLK0JYO8ZFpUDDYseUiJBnh+VsyzHVolvc/
wWixOx95DnERaG3QW4tdrSuYOqqmwIbcRA0xQGn1FTcPgtpl7zYbNpP2ZgqjiCfs
M3yhHyZwMg0IqQiWu7DQgiSdLKRSBMD5lBC+3bpbOp7lU4C5PVZ5aOCoj5wA4gci
huUjAUHHWvC5CqdPl+0fVTLptyelIOVOzwAoiVHVyCYA+XpNGc84rInZvCdpxtym
1OJFOTY+q70U4D8/IVZL682PikwALQ==
=bIf6
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Dec  3 04:43:45 2018
Return-Path: <mcr@sandelman.ca>
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 24D98130F9A for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 04:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 oAw-UecmLJ8m for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 04:43:41 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CE92130EC2 for <anima@ietf.org>; Mon,  3 Dec 2018 04:43:41 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [185.201.60.232]) by relay.sandelman.ca (Postfix) with ESMTPS id A9C1A1F8BD; Mon,  3 Dec 2018 12:43:38 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id E23993AF2; Mon,  3 Dec 2018 12:42:53 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: Kent Watsen <kwatsen@juniper.net>, max pritikin <pritikin@cisco.com>
CC: anima@ietf.org
In-reply-to: <19433.1543838990@dooku.sandelman.ca>
References: <19433.1543838990@dooku.sandelman.ca>
Comments: In-reply-to Michael Richardson <mcr+ietf@sandelman.ca> message dated "Mon, 03 Dec 2018 12:09:50 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 03 Dec 2018 12:42:53 -0000
Message-ID: <21401.1543840973@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/nYtP6EGYLKNZcuVbYkuf2x6ubX8>
Subject: [Anima] adding pledge-voucher-request for unsigned requests
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, 03 Dec 2018 12:43:43 -0000

--=-=-=
Content-Type: text/plain


I've tried to add a new field to the (parboiled) voucher-request that
would go from the Registrar to the MASA.  This is to contain a copy of the
unsigned raw (Pledge->Registrar) voucher-request.  This is for the situation
where that request is unsigned.

Kent, I'll need some help here.  I think this may call for a YANG mount?
As I'm trying to say that at the pledge-voucher-request that there will be
an instance of voucher-request.
(I've written "binary" for the moment so that the YANG will compile)

I've also specified that the entire JSON (including the outer:
"ietf-voucher-request:voucher" should go here. I don't know if that's typical
JSON serialization.  Whether or not it goes there, the document needs to be
explicit about it.
(ps: I'd rather remove unsigned requests though)


        leaf pledge-voucher-request {
          type SOMETHING;
          description
            "When the pledge provides an unsigned voucher request, the
             Registrar includes the contents of that voucher-request verbatim
             in this field.  The serialization of the Registrar to MASA
             voucher-request is assumed to be the same as the serialization of the
             Pledge to Registrar voucher-request.

             The entire contents of the voucher-request including any outer
             ietf-voucher-request:voucher should be included in this field.

             The Registrar should not be surprised if there are additional
             attributes, private between the pledge and MASA that are included
             in this field.";
        }


+
+        <t hangText="pledge-voucher-request:">If an unsigned
+        voucher-request was received, then it is included in this field
+        rather than in the prior-signed-voucher-request field.  Within the
+        context of the ACP scope, unsigned voucher-requests are received in
+        JSON format, therefore this field is in JSON format as a dictionary.
+        It includes the outer "ietf-voucher-request:voucher" layer.
+        This is in contrast to the signed version, where the signed artifact
+        is include in a base64 format.  It is not illegal for attributes
+        unknown to a registrar to be included by the pledge.
+        </t>
+

...
+       +-- pledge-voucher-request?          binary


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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwFJM0ACgkQlUzhVv38
QpAtEgf7B16Jn59OfRXeY78iCNVhr/X1K9NzrQXbCWpKENkcHP57Ri+FqOFK3gog
DW8HXj07pxMVkruKmmnGGbf1dpOVGPnS3jD5rWhs8lqKhg5V6EvLtEaQoVOKw/QF
Mt4BDt/QUKS7wAObbJmgYzYPBdRlMXDy+zUjAqdJ8QYhW5dEx4AinX3rlmTQ547d
sychhlWotlTwCS7nNkPjgH0isKWMqyt7bUOfV+I/otg2ps3ARM1r0L8gecW3c7O+
9UC8f6ypX4XuOiZGAPiHRliiyyi3Iv1orKEO3jM6Ai0cVpljazk536H9oybj4fwj
Br4Snx48lnzSZ2GueIjruCO4J1Jlkg==
=VzkF
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Dec  3 09:00:30 2018
Return-Path: <kwatsen@juniper.net>
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 6BCF0130E0E for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 09:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.161
X-Spam-Level: 
X-Spam-Status: No, score=-4.161 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 eNA7eTZG81mA for <anima@ietfa.amsl.com>; Mon,  3 Dec 2018 09:00:21 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 7D383130F52 for <anima@ietf.org>; Mon,  3 Dec 2018 09:00:19 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wB3GswuB019217; Mon, 3 Dec 2018 09:00:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=xBNfY6E8EHk7VBLudLk4AW54eZ516Xb/fEgvRfQ15iw=; b=qo84W/MUc3jGUVJdVHf6vhTFdhazyrv53GFKKMKl9zuHfncfHsUxFGD9WWsOz8aKKEeJ 2wrRwWl2iqpiiUxFb8CrAvOUUDlivnVt0swTIus8B43aV/g7EdsHhMBRVQMit/9iIiaD /2SwkqUfWs851htAzJjCXQZ8T1b844YXcegzSxq7Q+2kR3GVRT71E0gtFVlg96Ad/htJ StjKih2qrgLIHFvFX9L0ie9w4bJrcz9ZH8cs0sRg0Xi6upNvwiBn39a0OQNVwKQT/UT5 3cXNoRBwklTXi4htuntLYsgxcQXmDEe8Ppvjhd1X4va0x3ql26CaShxIcxok12x/MCQ/ /w== 
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2053.outbound.protection.outlook.com [104.47.44.53]) by mx0a-00273201.pphosted.com with ESMTP id 2p51p7gpnj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 03 Dec 2018 09:00:16 -0800
Received: from DM6PR05MB4665.namprd05.prod.outlook.com (20.176.109.202) by DM6PR05MB4652.namprd05.prod.outlook.com (20.176.109.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1404.13; Mon, 3 Dec 2018 17:00:14 +0000
Received: from DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::f0f3:20f0:2104:638c]) by DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::f0f3:20f0:2104:638c%2]) with mapi id 15.20.1404.016; Mon, 3 Dec 2018 17:00:14 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Michael Richardson <mcr@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: a multiplicity of pinned certificates
Thread-Index: AQHUilTUUtb7vITjiUW38W2QpXJC3qVs6tmA
Date: Mon, 3 Dec 2018 17:00:14 +0000
Message-ID: <E967EC8A-E665-4F60-994E-96D40A074B92@juniper.net>
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <480.1543543174@dooku.sandelman.ca> <E79F03FA-E4D7-4ED1-9552-F00300C6DD9D@juniper.net> <3750.1543764960@dooku.sandelman.ca>
In-Reply-To: <3750.1543764960@dooku.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.10.4.181110
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR05MB4652; 6:5AZ7otJn4SQG7lI/Dt67ms/TgWx7AHdMSESdH4pBiNiGb8Ejy17be47fzRNiaxJ/TnGOlzW6DmJDIuJZdZqijWDIeokM9a+Znqi3raF1cWBIU4mFh+w4BiEN+dNnNgaSK7DkjtY1v0L9mQlve03FvLX9tHcrRk3LbLRLJg1ow3uPd1I6ZCBVIN/g2tiJx8ErpLGLix6F00loQpvjODft13Oxlo70F0Ev/xgpUGfZq+rHnXg8Xrq5PrBzCa/rppw7wQc86QPZk0zGzT+utdhuurZNmLwJKoG1bQUBL/V7awXAKExcjD6Fsqjjg8NWdFpJxMk9TljposGWbJnAQijM0gIBmQjAVKSUkd+gvNvvsAyATQK6T14NgAZNlup6Fq2hI8uBpsizEXwCybJuHiez3qh7dHkB5hm2OmhkI4iODnA7G25StR9aYKDEIg7rYknt3hjMRREgIjrUK0bCBBkWPA==; 5:upzDcaq2eDh94QRlSVceh40nILZL4NJa5n/3SiFwHvaC88vEgimsq2PimjweTRbWVct5yDgSI0MEnX30/av1leCyjQrFfTYK3ICThT0vMKSDfYYatLDLmyf+EHeTXM19w1VH9oaGW2YyIyfwidxpcUb0QrXESP0kwNseEEZYBys=; 7:YFilP4VOEZI/8QY6lkKtBkwKjXL0jhEgmFb8XvOkwHKhZQujR+UV34VnytJTbJZlwwo7Dbb3tfEUXqYyZWVhN0wJHS0C/yCJ+4mOCDAYYb2hrj5XlJtKvQX9sanyX2f5ntNQVtoNYx4tEBZHZ1CGQA==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 37916703-172b-408d-a424-08d65940cb8e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM6PR05MB4652; 
x-ms-traffictypediagnostic: DM6PR05MB4652:
x-microsoft-antispam-prvs: <DM6PR05MB46523442B005B56CB1CFEDD6A5AE0@DM6PR05MB4652.namprd05.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(3231455)(999002)(944501493)(52105112)(93006095)(93001095)(6055026)(148016)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:DM6PR05MB4652; BCL:0; PCL:0; RULEID:; SRVR:DM6PR05MB4652; 
x-forefront-prvs: 08756AC3C8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(39860400002)(346002)(376002)(136003)(189003)(199004)(105586002)(82746002)(316002)(68736007)(83716004)(93886005)(97736004)(476003)(25786009)(71200400001)(71190400001)(106356001)(478600001)(102836004)(33656002)(256004)(486006)(76176011)(58126008)(2616005)(6506007)(110136005)(186003)(99286004)(2906002)(14444005)(6246003)(66066001)(6436002)(14454004)(5660300001)(305945005)(446003)(7736002)(36756003)(53936002)(6512007)(3846002)(6116002)(6486002)(86362001)(11346002)(81166006)(229853002)(26005)(81156014)(8936002)(2501003)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4652; H:DM6PR05MB4665.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 4sMAS8iQtr+TcSK9DbCKhI19171G/SF+nJppRFHUlX2Fg4dnZC+76ICR/+LO+3tRyMa/3bTjhEqvzVkN9na0cmRyWUNdFifW+uXR439bFoBxzifjlgBl4rqG/pNjF+IuE5dT7dgEbTGT/de5K3Z7fg9oxlHL/Mc1FuJPhMHa0xLqwyvYmQWYSeJrmjCCZTylm/d0qrc/T6/knbPJJGUDkOkvM1YMEekhxCay0vscrAMNEJJ1anJH4YEzXrDYZ1lGofF0Ao+fAzAPxpSClQ+blIw3QV44RowjzY5UDhA5ni4zlxEMr5d9A2aIw0UNUyYfgauuB/jsdksMsQY2Kldfu9/TvEd+qp0WIGPhwKtzJQ8=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <A77B26001CE05E428376A6756F1A94E6@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 37916703-172b-408d-a424-08d65940cb8e
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Dec 2018 17:00:14.5864 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4652
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-12-03_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1812030158
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_jw3zOREm9Nw50UGAlLETq1v0I4>
Subject: Re: [Anima] a multiplicity of pinned certificates
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, 03 Dec 2018 17:00:28 -0000

DQoNCj4gICAgPiBTZXBhcmF0ZWx5LCBhcyBsb25nIGFzIHdlJ3JlIHJhaXNpbmcgaXNzdWVzIHdp
dGggUkZDIDgzNjYsIEkgc3Ryb25nbHkNCj4gICAgPiBiZWxpZXZlIHRoYXQgdGhlIHBpbm5lZC1k
b21haW4tY2VydGlmaWNhdGUgc2hvdWxkJ3ZlIGJlIGEgbGlzdCBvZg0KPiAgICA+IGNlcnRpZmlj
YXRlcy4gIE9yLCBpbiBjcnlwdG8tdHlwZXMgWzFdIHRlcm1zLCBhIHRydXN0LWFuY2hvci1jZXJ0
LWNtcywNCj4gICAgPiBub3QgYSB0cnVzdC1hbmNob3ItY2VydC14NTA5LiAgVG8gZW5hYmxlIHRo
ZSBwaW5uZWQtZG9tYWluLWNlcnRpZmljYXRlDQo+ICAgID4gZm9yIGFuIGludGVybWVkaWF0ZSBD
QSB0byBiZSBhIGNoYWluIHRoYXQgaW5jbHVkZXMgdGhlIHJvb3Qgc2VsZi1zaWduZWQNCj4gICAg
PiBjZXJ0aWZpY2F0ZSwgdGh1cyBzdXBwb3J0aW5nIHRvb2xpbmcgdW5hYmxlIHRvIHZhbGlkYXRl
IHBhcnRpYWwtY2hhaW5zLg0KPg0KPiBJIGJlbGlldmUgdGhhdCBhIGZ1dHVyZSB2ZXJzaW9uIGNv
dWxkIG1ha2UgdGhpcyBjaGFuZ2UgcmVsYXRpdmVseSBlYXNpbHksDQo+IHBhcnRpY3VsYXJseSBp
ZiB3ZSBkbyBpdCBxdWlja2x5LiBEZXN0aW5ndWlzaGluZyBiZXR3ZWVuIGFycmF5cyBvZiAxLWVs
ZW1lbnQNCj4gYW5kIHNpbmdsZS1pdGVtcyBpc24ndCB0aGF0IGRpZmZpY3VsdCBpbiB0aGUgc2Vy
aWFsaXphdGlvbnMgd2UgaGF2ZS4NCg0KQnkgImZ1dHVyZSB2ZXJzaW9uIiwgZG8geW91IG1lYW4g
YW4gcmZjODM2NmJpcz8NCg0KSWYgb3BlbiB0byB0aGF0LCBJIGNvdWxkIGRyYWZ0IGFuIEktRC4u
Lg0KDQpLLg0KDQoNCg==


From nobody Mon Dec  3 15:49:10 2018
Return-Path: <housley@vigilsec.com>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4091B130E57; Mon,  3 Dec 2018 15:49:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <Iot-dir@ietf.org>
Cc: draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org, ietf@ietf.org, anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154388094719.4951.644465000786184923@ietfa.amsl.com>
Date: Mon, 03 Dec 2018 15:49:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/1N7AR8hqu2oIWuTFFd9OQOab8SI>
Subject: [Anima] Iotdir telechat review of draft-ietf-anima-bootstrapping-keyinfra-17
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Dec 2018 23:49:07 -0000

Reviewer: Russ Housley
Review result: Not Ready

I reviewed this document as part of the IoT Directorate's effort to
IoT-related IETF documents being processed by the IESG.  These comments
were written primarily for the benefit of the Internet Area Directors.
Document authors, document editors, and WG chairs should treat these
comments just like any other IETF Last Call comments.

Document: draft-ietf-anima-bootstrapping-keyinfra-17
Reviewer: Russ Housley
Review Date: 2018-11-28
IETF LC End Date: unknown
IESG Telechat date: unknown

Summary: Has Issues

(Note: I did not review the Appendices.)


Major Concerns:

Section 2.2 says:

   ...  The registrar
   maintains control over the transport and policy decisions allowing
   the local security policy of the domain network to be enforced.

I have no idea what this means.  Please clarify.

In Section 2.3, it says:

   5.  (Optional) Signing of voucher-request by the pledges IDevID to
       enable MASA to generate voucher only to a registrar that has a
       connection to the pledge.

This is an important section to understand BRSKI, but I cannot parse
this sentence.  Please reword.

Section 2.3.1 talks about pledges being uniquely identified by a
"serial-number" in voucher and voucher-requests.  Pledges are also
uniquely identified by their serial number in certificates.

Section 2.3.1 refers to HardwareModuleName, which is defined in
RFC 4108.  It says that the HardwareModuleName hwSerialNum is base64
encoded.  RFC 4108 does not require base64 encoding.  Where does that
requirement come from?

Section 3.1 shows the YANG tree model of the Voucher-Request.  I am far
from a YANG expert, but I expected a subsequent section to describe the
semantics of each field.  The examples in Section 3.2 are useful, but
they are not a replacement.  Some fields (like voucher/expires-on) are
not described in Section 3.3.  I assume that this is building on another
module because this one contains "import ietf-voucher", but this does
not say what RFC contains the imported module to learn the rest of the
semantics.

I think that the CDDL in Sections 4.1.1 and 4.3 are supposed to be
structures.  If that is correct, the structure should look something
like the following, which includes type information:

   basic-header = [
     field1: int,
     field2: text,
   ]

   advanced-header = [
     ~basic-header,
     field3: bytes,
     field4: ~time,
   ]

I have no idea what the boxes in Figure 10 represent.

Section 7.2 does not contain enough information to make the needed
object identifier assignments.

In Section 7.4, the IESG (not the IETF Chair) should be the contact
for standards-track registrations.

I think the security considerations ought to describe the consequences
of compromise of the various private keys in the ecosystem.  Some only
impact one device, but others have much greater impact.

I think the security considerations ought to say something about the
nonce.  First, it should point to RFC 4086.  Second, it should say
something about the consequences of a poor random source.  It does not
need to be a comprehensive as the section dealing with setting time.


Minor Concerns:

The Introduction says:

   BRSKI provides a solution for secure zero-touch (automated) bootstrap
   of virgin (untouched) devices that are called pledges in this
   document.  These pledges need to discover (or be discovered by) an
   element of the network domain to which the pledge belongs to perform
   the bootstrap.  This element (device) is called the registrar. ...

I find the two uses of device to be a bit confusing.  I suggest:

   Bootstrapping Remote Secure Key Infrastructures (BRSKI) provides a
   solution for secure zero-touch (automated) bootstrap of virgin
   (untouched) devices, called pledges.  Pledges need to discover (or be
   discovered by) an element of the network domain to which the pledge
   belongs to perform the bootstrap, called the registrar. ...

In the Introduction, in the paragraph that follows the description of
the four points of trust, I think there is a significant typo.  An
IEEE 802.1AR LDevID certificate addresses points 1 and 2, and then a
"voucher" addresses points 3 and 2.  I suspect that the second "2"
should be "4".  If not, some additional text is needed to cover point 4.

Section 1.2: Please update the first paragraph to reference RFC 8174
in addition to RFC 2119, as follows: 

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

I think that "/ next steps" should be dropped from the title of
Section 1.4.

I think that Section 1.5 would be well served with bullets that are full
sentences.  For example, the document says:

   o  BRSKI: Request Voucher

This terse phrase, I think, covers the requesting of a voucher by the
pledge from the MASA, and then receiving the voucher.  Alternatively,
you could provide forward pointers that describe each of these terse
phrases.

Section 2 uses "Manufacturer Service" and "Vendor Service".  I think
they are the same thing.  Neither of these is defined in Section 1.2,
so I am not totally sure.  Please clarify.

Section 2 says:

   ...  It
   is unlikely that an integrator could provide Ownership Tracking
   services for multiple manufacturers due to the required sales channel
   integrations necessary to track ownership. ...

However, it seems possible for the integrator to provide a referral to
the appropriate Ownership Tracking service or provide a proxy.

Section 2 talks about a "PKI Registration Authority".  No context is
given.  At a minimum, a reference to RFC 5280 seems appropriate.  If
there is a more specific role that an RA might play in BRSKI, then
that should be explained or referenced.

Section 2.5.3 talks briefly about the "Implicit Trust Anchor database".
Please add a reference to RFC 7030 here; it is needed to understand the
concept.

In the security considerations, it would be good to cover how the owner
of a device might cope the a manufactured going out of business or
stopping support for a device.  This is really not a problem if the
device is already on a network and it does not ever need to move to
another network.

Section 11.1: Please add a normative reference to RFC 8174.


Nits:

The abstract says:

   ... Bootstrapping a new device can
   occur using a routable address and a cloud service, or using only
   link-local connectivity, or on limited/disconnected networks. ...

This is a complex sentence.  Can it be up-leveled for the Abstract?
If not, can it be reworded to be more straightforward? 

Please spell out "BRSKI" in the first sentence of the Introduction.
I did this in my suggested text in the previous portion of this review.

The quotes do not balance in the second to last paragraph of the
Introduction.

Please put the terms that are defined in Section 1.2 in alphabetical
order.

In section 1.2, the definition of "drop ship" talks about "drop-ship".
Please pick one spelling.

In Section 1.2, you define "Join Registrar (and Coordinator)", but the
Introduction seems to talk about this role simply as the "Registrar".
I think it would be helpful to include a "Registrar" entry here to
help the reader.  Similarly for "Join Proxy" and "Proxy".

The Introduction talks about IEEE 802.1AR LDevID; please add LDevID to
the definitions in Section 1.2.

In Figure 1: s/PKI Certificate Authority/PKI Certification Authority/

In Section 2.3: s/fake pledged/fake pledges/

In Section 2.3: s/pledges MASA/pledge's MASA/

In Section 2.3: s/(see Appendix C./(see Appendix C)./

In Section 2.3: s/pledges IDevID/pledge's IDevID/

In Section 2.6.1, the list of five time sources should be turned
into a real sentence.

In Section 2.6.1, please turn "See / (Section 5.2)" into a sentence.

In many places: s/global internet/global Internet/

In many places: s/internet at large/Internet at large/

Lists of bullets come in many flavors.  Some bullets end with a comma,
some end with a period, and others end with no punctuation at all.
Please pick one style and use it everywhere.


FYI:

I compiled the MASAURLExtnModule-2016 ASN.1 module.  It compiles fine,
but I find the indent and white space style used awkward.



From nobody Tue Dec  4 03:49:41 2018
Return-Path: <mcr@sandelman.ca>
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 8AC12128766; Tue,  4 Dec 2018 03:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Bq4PVYKqJYyh; Tue,  4 Dec 2018 03:49:37 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F4D1128CF3; Tue,  4 Dec 2018 03:49:37 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [80.233.42.246]) by relay.sandelman.ca (Postfix) with ESMTPS id 5A9E01F8BE; Tue,  4 Dec 2018 11:49:35 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 95C302825; Tue,  4 Dec 2018 11:49:00 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>
cc: Iot-dir@ietf.org, draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org, ietf@ietf.org, anima@ietf.org
In-reply-to: <154388094719.4951.644465000786184923@ietfa.amsl.com>
References: <154388094719.4951.644465000786184923@ietfa.amsl.com>
Comments: In-reply-to Russ Housley <housley@vigilsec.com> message dated "Mon, 03 Dec 2018 15:49:07 -0800."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 04 Dec 2018 11:49:00 -0000
Message-ID: <4671.1543924140@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/VddzKoNLvgTNmc8Kx3vTrYw3zRg>
Subject: Re: [Anima] Iotdir telechat review of draft-ietf-anima-bootstrapping-keyinfra-17
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: Tue, 04 Dec 2018 11:49:40 -0000

--=-=-=
Content-Type: text/plain


Thank you Russ!
I will turn your comments into issues, attempting to de-duplicate against
what we already have.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAlwGaawACgkQlUzhVv38
QpAPdwgAlPY4BSNxrGkwEuWVPM3OmUZ1sctecJxpxhT8sqF38GAU0YCNrqZ8AlJR
amY+NsjrFLgPj1GdHY21qpdVEXIovepeyfh2kRjN84uhgeBuNeIcb2s8g7bZJ8Cu
7pdR3SxMT2XfT8UTlioLyyfKbzLkIZKTxKWV2bs8moR8IOflgi4QoejGzur8CsgO
WA+ExReA9flJsfaIxgdOepmcNevQVWnuPmoJuKZIxqGXq0VrCIpyXNJfXdbOGCUr
Kh6fG68rEofMW4piC+nLitcv81MslT8lG4vScKl8LGu9rSu5MhHb3ueQXhE5dciB
1xrvqgGBR4d8omc+uvaKaC0PHhlRYA==
=RKk2
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Dec  5 02:05:48 2018
Return-Path: <steffen.fries@siemens.com>
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 55003130DCC for <anima@ietfa.amsl.com>; Wed,  5 Dec 2018 02:05:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Wj4KX0Mm41Pz for <anima@ietfa.amsl.com>; Wed,  5 Dec 2018 02:05:45 -0800 (PST)
Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) (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 C927B124BF6 for <anima@ietf.org>; Wed,  5 Dec 2018 02:05:44 -0800 (PST)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id wB5A5gPV010334 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 5 Dec 2018 11:05:42 +0100
Received: from DEFTHW99ERJMSX.ww902.siemens.net (defthw99erjmsx.ww902.siemens.net [139.22.70.135]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id wB5A5g5R031369 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 5 Dec 2018 11:05:42 +0100
Received: from DENBGAT9ERMMSX.ww902.siemens.net (139.22.70.140) by DEFTHW99ERJMSX.ww902.siemens.net (139.22.70.135) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 11:05:41 +0100
Received: from DENBGAT9EH2MSX.ww902.siemens.net ([169.254.6.167]) by DENBGAT9ERMMSX.ww902.siemens.net ([139.22.70.140]) with mapi id 14.03.0415.000; Wed, 5 Dec 2018 11:05:41 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] BRSKI support for asynchronous processing
Thread-Index: AQHUimSoLXgxFpsJfkqDjblsgITcc6Vvx/aA
Date: Wed, 5 Dec 2018 10:05:41 +0000
Message-ID: <E6C9F0E527F94F4692731382340B3378148C4264@DENBGAT9EH2MSX.ww902.siemens.net>
References: <E6C9F0E527F94F4692731382340B3378148B7C30@DENBGAT9EH2MSX.ww902.siemens.net> <24056.1543771803@dooku.sandelman.ca>
In-Reply-To: <24056.1543771803@dooku.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.22.70.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/9lB1THA70JHWavcyCyLuP1lF2Vs>
Subject: Re: [Anima] BRSKI support for asynchronous processing
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: Wed, 05 Dec 2018 10:05:47 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:=20
>     > Besides this, we see further use cases, in which the connection to =
the PKI is
>     > not always available. This may be the case if the connection to the=
 CA is only
>     > temporary available or not directly available. Here, the approach w=
ould require
>     > a rather asynchronous handling. In such a setup the domain registra=
r could for
>     > instance store the object (certification request) and forward it up=
on
>     > connectivity to the PKI for further processing. The forward may be =
based on a
>     > communication connection or even manually. This asynchronous approa=
ch requires
>     > that the object itself is self-protecting ensuring its integrity (l=
ike a PKCS#7
>     > wrapping of the PKCS#10 request or similar). Based on the specified=
 BRSKI
>     > features, we did not see the support for this type of requirements =
directly.
>=20
> BRSKI is simply the mechanism to create a secure channel.
> What happens afterwards is up to EST-RFC7030 (or something else, but the =
ANIMA ACP specifies EST-RFC7030).
I realized the exclusive close binding to EST and was questioning this base=
d on some use cases mentioned in an=20
earlier email like enrolling device in a plant / building / train wagon. I =
completely understand the mandatory=20
support on the domain registrar side but not the pledge side.  My understan=
ding from ANIMA ACP is that=20
one has to support EST on an ACP node in any case, even if a different enro=
llment protocol is used.=20
It may not be a problem for new products, but existing products leveraging =
the voucher approach=20
may need to be adopted more than functionally necessary. Also, if self-cont=
ainment of the certification=20
request would help to address asynchronous use cases, EST as is may have  s=
ome restrictions.=20

=20
> 7030 section 4.2.3 says, near the end:
>=20
>    If the server responds with an HTTP [RFC2616] 202, this indicates
>    that the request has been accepted for processing but that a response
>    is not yet available.  The server MUST include a Retry-After header
>    as defined for HTTP 503 responses.  The server also MAY include
>    informative human-readable content.  The client MUST wait at least
>    the specified "retry-after" time before repeating the same request.
>    The client repeats the initial enrollment request after the
>    appropriate "retry-after" interval has expired.  The client SHOULD
>    log or inform the end-user of this event.  The server is responsible
>    for maintaining all states necessary to recognize and handle retry
>    operations as the client is stateless in this regard; it simply sends
>    the same request repeatedly until it receives a different response
>    code.  All other return codes are handled as specified in HTTP
>    [RFC2616].
>=20
> so a delayed reply is permissible.
Yes, the pledge may retry, but there are certain restrictions:
- You either have to keep the TLS connection open (as you mentioned below) =
or perform resumption.=20
  Depending on the use case, you may not have a direct connection to the CA=
 so it may take some=20
  time before the certificate will be provided. If you chose resumption the=
 pledge needs to generate=20
  a new PKCS#10 request to take the changed tls_unique into account. This w=
ill also require the EST=20
  server to keep track of repeated certification requests from the same ple=
dge. I also made some=20
  further notes below in your list.
- If the RA/CA is not directly reachable, the authorization decision for th=
e certification request needs=20
  to be done on the EST server (well, this is actually also the case for th=
e online case). Not a problem=20
  if the RA is co-located with the Domain Registrar. If the RA/CA are locat=
ed in the operators backend,=20
  the Domain Registrar would basically perform a store and forward of the c=
ertification request/response
  and may not be involved directly in the authorization. The binding to the=
 requesting identity=20
  would be removed after the first EST server and not be visible to the (ba=
ckend) RA. Besides=20
  authorization also the tracking of components is often done in the centra=
l location in conjunction=20
  with the RA.=20
  An example may be a train wagon in which the components shall be equipped=
 with the certificates=20
  of the new owner.  The domain is basically the wagon and issuing certific=
ates would be done in the=20
  railway companies backend once the wagon is connected. To prepare this, t=
he components in the=20
  wagon can already prepare this be registering locally at the domain regis=
trar.=20

> BRSKI could perhaps be more clear about whether the pledge is expected to=
:
>  1) keep the TLS connection open.
Probably the best to have less recreation of PKCS#10 requests

>  1B) do this virtually via TLS session resumption ticket
Possible but requires to recreate the PKCS#10 request with the new tls_uniq=
ue value

>  2) if it closes it, should it keep track of the Registrar certificate?
Definitely to ensure it is taking to the same registrar afterwards. Other a=
ctions like=20
the time synchronization have been done before based on the Registrar certi=
ficate.=20
If that changes, what would be the consequences?

>  3) alternatively, should it try again and expect a voucher to be present=
ed?
>    (which gets into: whether it records the nonce, and is happy with a
>    replay of the nonced voucher it got before)
If it records the nonce, would that conflict with the statement in BRSKI se=
ction 5.2,=20
that the nonce MUST NOT be reused for multiple bootstrapping attempts? Mayb=
e not,=20
as it may not be counted as attempt as the pledge was not generating a new=
=20
voucher request.
=20
Best regards
Steffen

>=20
>=20
>=20
> {I found the non-standard quoting styles and HTML parts made the thread i=
ncredibly difficult to follow.  We have access to WG lists via
> IMAP, so you can use quite a number of programs other than what your IT d=
epartment expects you to use for email.}
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
=3D IPv6 IoT consulting =3D-
>=20
>=20


From nobody Thu Dec  6 13:49:28 2018
Return-Path: <pkampana@cisco.com>
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 C0AC0130ECE for <anima@ietfa.amsl.com>; Thu,  6 Dec 2018 13:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.959
X-Spam-Level: 
X-Spam-Status: No, score=-15.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Pe58MwdukRIz for <anima@ietfa.amsl.com>; Thu,  6 Dec 2018 13:49:24 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5391E130E57 for <anima@ietf.org>; Thu,  6 Dec 2018 13:49:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3680; q=dns/txt; s=iport; t=1544132964; x=1545342564; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wCsCHGvzeHEdKujg6lFiME4vWBDmCYFkAhY0bd1ooA8=; b=gEAJwjnzLA/pGI+LH41dgNDt89KWki1RERyV6l/TZqnSKPvwrq9ssuSv RJAsa2ftw5kAVmlHKL2vb81hI1QSB9KGvkGBB/yM/R69D1n9b+UQcA40j BcB+TJggrP4fD9vWmx9Z2hyl5uMPOoPYJAh78+xDV9KtbnoFekIA4CiZC A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAAAQmAlc/5NdJa1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQInCowJjA+CDZdOgXoLAQEfgVi?= =?us-ascii?q?CdQKDFSI0CQ0BAwEBAgEBAm0cDIU8AQEBBDo/DAQCAQgRBAEBHxAyHQgCBAE?= =?us-ascii?q?NBQiDGoIBpUeCL4oqjB8XgUA/gRGDEoFBAYkaAqBfCQKRPCCRNokOj1cCERS?= =?us-ascii?q?BJx84gVVwFYMnCYUriydBMYoigR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,323,1539648000"; d="scan'208";a="495734501"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Dec 2018 21:49:23 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id wB6LnM5w008619 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 6 Dec 2018 21:49:23 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 6 Dec 2018 15:49:22 -0600
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Thu, 6 Dec 2018 15:49:22 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Max Pritikin (pritikin)" <pritikin@cisco.com>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: unsigned voucher requests in BRSKI
Thread-Index: AQHUhT2IV4Y6y6t420S9CBoc9iP2jKVySzTA
Date: Thu, 6 Dec 2018 21:49:22 +0000
Message-ID: <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com>
References: <31331.1543205187@dooku.sandelman.ca>
In-Reply-To: <31331.1543205187@dooku.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.180.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.23, xch-aln-013.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ScPb3RKX0JNf3pChQ-IDcmVURcY>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Thu, 06 Dec 2018 21:49:27 -0000

Hi Michael,

I think=20
1) CMS signed JSON, containing (prior=3DCMS signed JSON) or=20
4) CMS signed JSON, containing unsigned JSON.
should be the MTI. Adding CBOR instead of could be an optional thing for th=
e future (pretty much what you say in RFC8366).=20

About=20
> Also, I still am unclear if the constrained-BRSKI belongs in the constrai=
ned-voucher document.  I would sure like some clear opinions.

I am of the opining to put Constrained-BRSKI in draft-ietf-anima-constraine=
d-voucher. The reason is that they go hand in hand. The disadvantage is tha=
t then draft-ietf-anima-constrained-voucher becomes more complicated and I =
think that is why you folks broke down BRSKI in two documents. Now that BRS=
KI and Voucher are standardized though, doing both in the constrained vouch=
er document will not be that bad. I mean, it will not defining something br=
and new and complicated, it will just be adjusting the two ANIMA documents =
in one for constrained environments.=20

Rgs,
Panos

-----Original Message-----
From: Michael Richardson <mcr+ietf@sandelman.ca>=20
Sent: Sunday, November 25, 2018 11:06 PM
To: Max Pritikin (pritikin) <pritikin@cisco.com>; Panos Kampanakis (pkampan=
a) <pkampana@cisco.com>; consultancy <consultancy@vanderstok.org>; Kent Wat=
sen <kwatsen@juniper.net>
Cc: anima@ietf.org
Subject: unsigned voucher requests in BRSKI

* PGP Signed by an unknown key


With a single signed voucher format, it's clear that if the pledge sends an=
 unsigned voucher request that the Registrar should send a CMS signed vouch=
er request, and ask for a CMS signed voucher.

I have used the term "parboiled" for the artifact from Registrar to MASA, a=
nd "raw" for the artifact from Pledge to Registar.  Not everyone liked thos=
e terms, but I used in my code.

With the addition of CBOR, and COSE, we have a bunch of possibilities for t=
he (parboiled) artifact from the Registrar to the MASA:

1) CMS signed JSON, containing (prior=3DCMS signed JSON)
2) CMS signed CBOR, containing (prior=3DCMS signed CBOR)
3) COSE signed CBOR, containing (prior=3DCOSE signed CBOR)
4) CMS signed JSON, containing unsigned JSON.
5) CMS signed JSON, containing unsigned CBOR.
6) CMS signed CBOR, containing unsigned CBOR.

I don't think we ever should be embedding JSON based artifacts inside CBOR,=
 so there are some possibilities that I've ruled out already.  Argue the po=
int.

I have up to this point assumed that
  1) COSE signed CBOR pledge requests result in COSE voucher artifacts.
  2) CMS signed JSON pledge requests result in CMS voucher artifacts.
  3) CMS signed CBOR pledge requests result in CMS signed CBOR voucher
     artifacts.

When the Pledge request is unsigned JSON... all we know is that it's JSON.
I think that this means that the parboiled artifact should be CMS signed JS=
ON, and it should return a CMS signed voucher to the pledge. Of course, the=
 *MASA* knows.  The Registrar can set the Accept: header to */*, and
see what if understands what is returned.   This seems like a poor way to g=
et
interoperable systems.

Also, I still am unclear if the constrained-BRSKI belongs in the constraine=
d-voucher document.  I would sure like some clear opinions.

--
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        | network architect=
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [



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




* Unknown Key
* 0xFDFC4290


From nobody Sat Dec  8 16:11:36 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 7AB1C130FAB for <anima@ietfa.amsl.com>; Sat,  8 Dec 2018 16:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 b2t8583lpfgD for <anima@ietfa.amsl.com>; Sat,  8 Dec 2018 16:11:33 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E477130FA8 for <anima@ietf.org>; Sat,  8 Dec 2018 16:11:33 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2E0DE20008; Sat,  8 Dec 2018 19:11:26 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id CA13ADAF; Sat,  8 Dec 2018 19:11:31 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C5BED54; Sat,  8 Dec 2018 19:11:31 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>, "anima\@ietf.org" <anima@ietf.org>
cc: "Max Pritikin \(pritikin\)" <pritikin@cisco.com>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
In-Reply-To: <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com>
References: <31331.1543205187@dooku.sandelman.ca> <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sat, 08 Dec 2018 19:11:31 -0500
Message-ID: <6717.1544314291@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/zA_gKXpSIYHY8X-3LeQ8q4TBc-k>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Sun, 09 Dec 2018 00:11:36 -0000

--=-=-=
Content-Type: text/plain


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> I think
> 1) CMS signed JSON, containing (prior=CMS signed JSON) or
> 4) CMS signed JSON, containing unsigned JSON.

So, in the unsigned pledge request, you feel that the pledge request needs to
go up to the MASA?

It is not clear from the document that anything of the pledge requests goes
upwards.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwMXbMACgkQgItw+93Q
3WWUOAgAjzK98PmEDBm1ABPagd3BZRO13TzOGCrMQZCvVYX1zgSTFZxJViZRZiik
xJIrLgnw15HUJ9RNGPxN1j0npCgQPvhn4Hpkdi2b7Rzw/i9DTiTNzrSonwco3T+S
uE2dyiPtV6DFOgBEXIcRARvcAv1cSHuj18vDubEm6QrOFh6qwEXPkzwMpVpJFVh+
54asp458Pgcf2RS8Ze6gLG9F540ZsV9zS0z4eqdqt6vYZ6pQ2All9Hb1v5aBq03C
Myupj9cmzUDUC7x8fltOuQlM3WallGmTraRjC2bRUYac4T1ShmRD4RFRnzi5ZSFm
aNSIEHIiLIYiq24TbcKbCTgmabtViA==
=AeB1
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Dec 10 19:38:29 2018
Return-Path: <pkampana@cisco.com>
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 EE379126CC7 for <anima@ietfa.amsl.com>; Mon, 10 Dec 2018 19:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.961
X-Spam-Level: 
X-Spam-Status: No, score=-15.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 db-pyJJWJBX8 for <anima@ietfa.amsl.com>; Mon, 10 Dec 2018 19:38:23 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DA95126C01 for <anima@ietf.org>; Mon, 10 Dec 2018 19:38:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1201; q=dns/txt; s=iport; t=1544499503; x=1545709103; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+Rv01ZLeZ4L2omA7RlvwhSHtBb0rBhTjP/Gikc5XfUg=; b=Ja3RTlgf4Ik8LJv9kt9511TyjgWqxCdHd5qpbNYbX6JuPkA8UPB38354 atJ770HQ9nCNbGEOmMMQOBmEgiPAi3+9lPxKise2KETvstP4QrEP8WY/r GUW6aW8C4eosCUvP4swAS3peq4PMELIOOVhldDskRuByCakNFqzKOISUQ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAADxLw9c/5xdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggOBaCcKjAqMEIINl1GBegsBAYF3gnU?= =?us-ascii?q?CgysiNAkNAQMBAQIBAQJtKIU8AQEBAQM6PwwEAgEIEQQBAQEeEDIdCAIEAQ0?= =?us-ascii?q?FCIUbpzGKLYwhF4FAP4ERgxKBQQGJGgKgdQkCkUUgkT2JIo9nAhEUgScfOIF?= =?us-ascii?q?WcBWDJ5BbQTGKR4EfAQE?=
X-IronPort-AV: E=Sophos;i="5.56,340,1539648000"; d="scan'208";a="211261392"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2018 03:38:22 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id wBB3cMfI029399 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Dec 2018 03:38:22 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 10 Dec 2018 21:38:21 -0600
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Mon, 10 Dec 2018 21:38:21 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
CC: "Max Pritikin (pritikin)" <pritikin@cisco.com>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
Thread-Topic: unsigned voucher requests in BRSKI
Thread-Index: AQHUhT2IV4Y6y6t420S9CBoc9iP2jKVySzTAgAO2X4CAAvXrgA==
Date: Tue, 11 Dec 2018 03:38:21 +0000
Message-ID: <96570e67749741ce9ef24f4711a8171e@XCH-ALN-010.cisco.com>
References: <31331.1543205187@dooku.sandelman.ca> <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com> <6717.1544314291@localhost>
In-Reply-To: <6717.1544314291@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.174.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.23, xch-rcd-013.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/TwEco0uVFwV-VjbMmIZLJ0eSge0>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Tue, 11 Dec 2018 03:38:27 -0000

Hey Michael,=20
I was assuming it was mandatory in the current draft, but I was wrong. As y=
ou suggest it is not clear in the -17 version. I do think that an unsigned =
voucher should make it to the MASA, like a signed one would, for consistenc=
y.=20
Panos


-----Original Message-----
From: Michael Richardson <mcr+ietf@sandelman.ca>=20
Sent: Saturday, December 08, 2018 7:12 PM
To: Panos Kampanakis (pkampana) <pkampana@cisco.com>; anima@ietf.org
Cc: Max Pritikin (pritikin) <pritikin@cisco.com>; consultancy <consultancy@=
vanderstok.org>; Kent Watsen <kwatsen@juniper.net>
Subject: Re: unsigned voucher requests in BRSKI

* PGP Signed by an unknown key


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> I think
> 1) CMS signed JSON, containing (prior=3DCMS signed JSON) or
> 4) CMS signed JSON, containing unsigned JSON.

So, in the unsigned pledge request, you feel that the pledge request needs =
to go up to the MASA?

It is not clear from the document that anything of the pledge requests goes=
 upwards.

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




* Unknown Key
* 0xDDD0DD65


From nobody Tue Dec 11 08:29:35 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 7A39C130E3C; Tue, 11 Dec 2018 08:29:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Uo8Z0n6hyK8t; Tue, 11 Dec 2018 08:29:32 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5FC4130E44; Tue, 11 Dec 2018 08:29:25 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 27D0020089; Tue, 11 Dec 2018 11:29:18 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id EB30DE1B; Tue, 11 Dec 2018 11:29:23 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E93A1E15; Tue, 11 Dec 2018 11:29:23 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ace@ietf.org, anima@ietf.org
cc: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>, Peter van der Stok <stokcons@bbhmail.nl>, max pritikin <pritikin@cisco.com>
In-Reply-To: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 11 Dec 2018 11:29:23 -0500
Message-ID: <3831.1544545763@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_wCWeZhm4RwjjJY8ebX09VvgNns>
Subject: [Anima] est-coaps clarification on /att and /crts
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: Tue, 11 Dec 2018 16:29:34 -0000

--=-=-=
Content-Type: text/plain


A clarification question from an implementor (me) in the context of
constrained BRSKI state machine.

The /att and /crts requests do not do anything to change the state
of client or server.  It would seem that it might be safe to permit
clients which have not yet authenticated to do this operation.
(/att gets CSR attributes, and /crts gets the list of trust anchors)

When EST-COAPS is used on its own, there usually needs to be a manufacturer
trust anchor installed on the Registrar before any connection will be
permitted.

When EST-COAPS is used as step 2 of constrained-BRSKI, whether or not
the Registrar will accept any (and all) connections depends upon
configuration of the operator.  Some devices might not be doing BRSKI
(not need to, they already trust the operator, but they might still have
IDevID only.  This might happen during a transition)

If the Registrar is "open" to new manufacturers, should the Registrar
permit /att and /crts actions to be done by clients that it does not
recognize?   The /att call on an ANIMA ACP network would reveal to the
client the ULA that would be used for that client (and perhaps other
interesting things), and the /crts would show the name of the operator.
Note that the later info probably is revealed just by doing the TLS
handshake.

I think that they should be restricted in general, but I'm concerned that
there might be some situation I've missed.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwP5eMACgkQgItw+93Q
3WUc+ggAj/7eT48Il7b89cAe71nakfMGu53IZoFoSmyIZ8dlRaxJch5rpaDei6QY
L3ovnBYYCdNs1C92eXjciLcuQLq2prgDUqj36NoE1EywLVKyL3+mXkmTUpzjJVqY
HOPrZZlEHNW35PbH0eua3HVPVku74WPL6M5VPjZdiq/QUXe0f+V8ZVFCn6j7E7ik
p9ggESmc6vk9Sop5tfADhFtVA7diFXJ6xFoEElF6S/A0Kve+ijcW6m3OUwplqG82
C4uSVvALJNg1pSRwmYpMy6P1ru4+eoiusgNR+ORQiN0XLtOwv14hT6YJ3I5RpZUB
QV3clD9Oq9EOXhOA+p6hAIPh4GgPtw==
=XhQ8
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Dec 11 09:50:17 2018
Return-Path: <ietf@augustcellars.com>
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 AD00A130ED8; Tue, 11 Dec 2018 09:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 e4VNpQPV75GW; Tue, 11 Dec 2018 09:50:09 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4BFC130EC7; Tue, 11 Dec 2018 09:50:08 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 09:45:03 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, <ace@ietf.org>, <anima@ietf.org>
CC: 'Peter van der Stok' <stokcons@bbhmail.nl>, 'max pritikin' <pritikin@cisco.com>, "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost>
In-Reply-To: <3831.1544545763@localhost>
Date: Tue, 11 Dec 2018 09:50:00 -0800
Message-ID: <036301d49179$f2558bf0$d700a3d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGPjv7lcqlAiUUAise1VV4kpyPAbQIUVGQwpfMyi5A=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yVzSSec0i7hYSHKH9cL1WMECybE>
Subject: Re: [Anima] [Ace] est-coaps clarification on /att and /crts
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: Tue, 11 Dec 2018 17:50:11 -0000

Clarification requested - exactly what element is the Registrar?

The one item that I can generally think of that might be a problem is that
the answers to /att and /crts may differ based on the entity that is asking
the question.  In this case not having the entity being validated means that
the "wrong" answer may be returned or different answers would be returned
before and after validation.

Jim


> -----Original Message-----
> From: Ace <ace-bounces@ietf.org> On Behalf Of Michael Richardson
> Sent: Tuesday, December 11, 2018 8:29 AM
> To: ace@ietf.org; anima@ietf.org
> Cc: Peter van der Stok <stokcons@bbhmail.nl>; max pritikin
> <pritikin@cisco.com>; Panos Kampanakis (pkampana) <pkampana@cisco.com>
> Subject: [Ace] est-coaps clarification on /att and /crts
> 
> 
> A clarification question from an implementor (me) in the context of
> constrained BRSKI state machine.
> 
> The /att and /crts requests do not do anything to change the state of
client or
> server.  It would seem that it might be safe to permit clients which have
not yet
> authenticated to do this operation.
> (/att gets CSR attributes, and /crts gets the list of trust anchors)
> 
> When EST-COAPS is used on its own, there usually needs to be a
manufacturer
> trust anchor installed on the Registrar before any connection will be
permitted.
> 
> When EST-COAPS is used as step 2 of constrained-BRSKI, whether or not the
> Registrar will accept any (and all) connections depends upon configuration
of
> the operator.  Some devices might not be doing BRSKI (not need to, they
> already trust the operator, but they might still have IDevID only.  This
might
> happen during a transition)
> 
> If the Registrar is "open" to new manufacturers, should the Registrar
permit
> /att and /crts actions to be done by clients that it does not
> recognize?   The /att call on an ANIMA ACP network would reveal to the
> client the ULA that would be used for that client (and perhaps other
interesting
> things), and the /crts would show the name of the operator.
> Note that the later info probably is revealed just by doing the TLS
handshake.
> 
> I think that they should be restricted in general, but I'm concerned that
there
> might be some situation I've missed.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -
> = IPv6 IoT consulting =-
> 
> 



From nobody Tue Dec 11 09:57:43 2018
Return-Path: <pkampana@cisco.com>
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 913F2130ED6; Tue, 11 Dec 2018 09:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.961
X-Spam-Level: 
X-Spam-Status: No, score=-15.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uVhrIw20vEV9; Tue, 11 Dec 2018 09:57:33 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19899130EC7; Tue, 11 Dec 2018 09:57:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3305; q=dns/txt; s=iport; t=1544551053; x=1545760653; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=SLDjphjuKfzoOT0xIfTPUYK0xiFyZzNKoLj7TFSd2C4=; b=TRSTR8Zq/sX2R4jieZGJz8QOqRsKjTCvr2a4zHPjdoQ+f7b+9fcUnRjJ bbu8mJ4qIE5STg+JoXcIt5/B14kEbaCWVWpU/ovx4Zwt6J1e8NdsyooAM U6K58KOlG/D2U/zTeYAsZ+HvPm7jHPQV1PsAppIWAEWQUS5VItWzoUFDX Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAADW+Q9c/4UNJK1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGCA2aBAicKjAqMEYINl1KBegsBAYF3gnUCgmw?= =?us-ascii?q?iNAkNAQMBAQIBAQJtKIU8AQEBAQM6PwwEAgEIEQQBAR8QMh0IAgQBDQUIgxq?= =?us-ascii?q?CAacoii+Jc4JIF4FAP4ERgxKEa4VxAolRhW6QZ1UJApFHIJFAiSOPaQIRFIE?= =?us-ascii?q?nHziBVnAVO4JskFtBMYpLgR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,343,1539648000"; d="scan'208";a="497489908"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2018 17:57:31 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id wBBHvVKO022224 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Dec 2018 17:57:31 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 11:57:31 -0600
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Tue, 11 Dec 2018 11:57:31 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "ace@ietf.org" <ace@ietf.org>,  "anima@ietf.org" <anima@ietf.org>
CC: Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin (pritikin)" <pritikin@cisco.com>
Thread-Topic: est-coaps clarification on /att and /crts
Thread-Index: AQHUkW6xEQf9wDn5PkCg7PZRmoPArKV5u4Kg
Date: Tue, 11 Dec 2018 17:57:30 +0000
Message-ID: <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost>
In-Reply-To: <3831.1544545763@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.174.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/byIqfCWPwAduBf9PgWly607R8HM>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Tue, 11 Dec 2018 17:57:36 -0000

Hi Michael,

I thought about this for the EST-coaps draft. EST allowed for unauthenticat=
ed /cacerts and /csrattrs (/crt and /att in EST-coaps) as you are suggestin=
g. It is not as simple in EST-coaps. Two reasons:=20
1) There are constrained networks where an easy amplification attack could =
take place. For example the /crt request is very small and the response can=
 be big (a few KBs in the context of a constrained network is big). If unau=
thenticated, then /crts could be an easy amplification attack to saturate a=
 constrained network. We don't want that to happen. We want all our clients=
 to be authenticated by DTLS before they start loading up our RF network.
2) Additionally, there is a practical challenge of COAPS. When the DTLS han=
dshake is taking place the server does not know what the request will be. I=
n EST the server would send an HTTP WWW-Authenticate header to ask the clie=
nt to authenticate. Such a mechanism does not exist in COAP, so it would no=
t be straightforward unless we introduced a bunch of new things into COAP.

I think it is still right to authenticate clients even for /crt and /att in=
 the EST-coaps context. Maybe that is something to be revisited in Constrai=
ned-BRSKI/voucher, but not taken lightly.=20

Rgs,
Panos



-----Original Message-----
From: Michael Richardson <mcr+ietf@sandelman.ca>=20
Sent: Tuesday, December 11, 2018 11:29 AM
To: ace@ietf.org; anima@ietf.org
Cc: Panos Kampanakis (pkampana) <pkampana@cisco.com>; Peter van der Stok <s=
tokcons@bbhmail.nl>; Max Pritikin (pritikin) <pritikin@cisco.com>
Subject: est-coaps clarification on /att and /crts

* PGP Signed by an unknown key


A clarification question from an implementor (me) in the context of constra=
ined BRSKI state machine.

The /att and /crts requests do not do anything to change the state of clien=
t or server.  It would seem that it might be safe to permit clients which h=
ave not yet authenticated to do this operation.
(/att gets CSR attributes, and /crts gets the list of trust anchors)

When EST-COAPS is used on its own, there usually needs to be a manufacturer=
 trust anchor installed on the Registrar before any connection will be perm=
itted.

When EST-COAPS is used as step 2 of constrained-BRSKI, whether or not the R=
egistrar will accept any (and all) connections depends upon configuration o=
f the operator.  Some devices might not be doing BRSKI (not need to, they a=
lready trust the operator, but they might still have IDevID only.  This mig=
ht happen during a transition)

If the Registrar is "open" to new manufacturers, should the Registrar permi=
t /att and /crts actions to be done by clients that it does not
recognize?   The /att call on an ANIMA ACP network would reveal to the
client the ULA that would be used for that client (and perhaps other intere=
sting things), and the /crts would show the name of the operator.
Note that the later info probably is revealed just by doing the TLS handsha=
ke.

I think that they should be restricted in general, but I'm concerned that t=
here might be some situation I've missed.

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




* Unknown Key
* 0xDDD0DD65


From nobody Tue Dec 11 14:17:04 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 60766130F29; Tue, 11 Dec 2018 14:16:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NNFHUNgA2osZ; Tue, 11 Dec 2018 14:16:53 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19ADA12E036; Tue, 11 Dec 2018 14:16:53 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D8DB520089; Tue, 11 Dec 2018 17:16:44 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id ADFAAE1B; Tue, 11 Dec 2018 17:16:50 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id AB8D0E15; Tue, 11 Dec 2018 17:16:50 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Jim Schaad <ietf@augustcellars.com>
cc: ace@ietf.org, anima@ietf.org, "'Peter van der Stok'" <stokcons@bbhmail.nl>, "'max pritikin'" <pritikin@cisco.com>, "'Panos Kampanakis \(pkampana\)'" <pkampana@cisco.com>
In-Reply-To: <036301d49179$f2558bf0$d700a3d0$@augustcellars.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <036301d49179$f2558bf0$d700a3d0$@augustcellars.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 11 Dec 2018 17:16:50 -0500
Message-ID: <26234.1544566610@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/gxNlBPIl0YmxB5QOG-XAXkRIM0g>
Subject: Re: [Anima] [Ace] est-coaps clarification on /att and /crts
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: Tue, 11 Dec 2018 22:16:56 -0000

--=-=-=
Content-Type: text/plain


Jim Schaad <ietf@augustcellars.com> wrote:
> Clarification requested - exactly what element is the Registrar?

It's an EST RFC7030 term, but essentially it's the server that connects to
(or is) the CA.

> The one item that I can generally think of that might be a problem is that
> the answers to /att and /crts may differ based on the entity that is asking
> the question.  In this case not having the entity being validated means that
> the "wrong" answer may be returned or different answers would be returned
> before and after validation.

Yes, I agree: it should be restricted.

I think that it should be restricted. Partly, I'm just not sure where the
text should go, or if it needs to be said at all.

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

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwQN1IACgkQgItw+93Q
3WWqxQf+NFoMxAB/+Uya2GyIlaSiCdVgucwBC0HyhOqtNYpD/I62GNB75pdBAy+X
sxloBYNm0xujOH8JneNIecMAYGQpEFugIsF2DlJSZXM6/OkDyksCqwe9qfD0bUF5
eqPQn+CtjpKirEYf6yIPJaoN2QxALhMd2PTv4ijvtsQGjL1iP39xjWRv2X1cOfWy
zGwzwhlv8kLerUPYwxP/f0sW3uiTco73ZDPfZmuVTEWcF4fi27BLl8hY3npXXQo4
1PX4GpWWjsso1T1/3EdLXD7yvlo+/OZmOO/DB1CfjM/72ryiqPUUFQhsUxT5+YpO
TlVHJ5nClXwMzl0aSZ9jn1oWxoi5Hg==
=Zog5
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Dec 11 14:21:57 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 17E5212E036; Tue, 11 Dec 2018 14:21:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 GAXmGf4HNrLC; Tue, 11 Dec 2018 14:21:48 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 743B91286E7; Tue, 11 Dec 2018 14:21:48 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B01A720089; Tue, 11 Dec 2018 17:21:41 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 85E69E1B; Tue, 11 Dec 2018 17:21:47 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 83DCCE15; Tue, 11 Dec 2018 17:21:47 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>, "ace\@ietf.org" <ace@ietf.org>, "anima\@ietf.org" <anima@ietf.org>
CC: Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>
In-Reply-To: <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 11 Dec 2018 17:21:47 -0500
Message-ID: <27594.1544566907@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/T-us3BIgVT-qImbF2bFE--N01lk>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Tue, 11 Dec 2018 22:21:51 -0000

--=-=-=
Content-Type: text/plain


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> I thought about this for the EST-coaps draft. EST allowed for
> unauthenticated /cacerts and /csrattrs (/crt and /att in EST-coaps) as you
> are suggesting.

Exactly.

> It is not as simple in EST-coaps. Two reasons:

> 1) There are constrained networks where an easy amplification attack could
> take place. For example the /crt request is very small and the response can
> be big (a few KBs in the context of a constrained network is big). If
> unauthenticated, then /crts could be an easy amplification attack to
> saturate a constrained network. We don't want that to happen. We want all
> our clients to be authenticated by DTLS before they start loading up our RF
> network.

I'm not suggesting that the DTLS be skipped, I'm suggesting that the client
certificate presented might be meaningless to the EST server.
As for amplication attacks, they usually depend upon forged source addresses,
and in that case the DTLS wouldn't have completed.

> 2) Additionally, there is a practical challenge of COAPS. When the DTLS
> handshake is taking place the server does not know what the request will
> be. In EST the server would send an HTTP WWW-Authenticate header to ask the
> client to authenticate. Such a mechanism does not exist in COAP, so it
> would not be straightforward unless we introduced a bunch of new things
> into COAP.

AFAIK, we don't support HTTP-level authentication in COAPS, only DTLS level
authentication is specified in EST-COAPS.

> I think it is still right to authenticate clients even for /crt and /att in
> the EST-coaps context. Maybe that is something to be revisited in
> Constrained-BRSKI/voucher, but not taken lightly.

So I think that we need to say something in EST-COAPS to explain that we do
not see a use case for replying to /crts and /att for clients which are not
recognized.  Is 401 (4.01) or 403 (4.03) more appropriate do you think?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwQOHsACgkQgItw+93Q
3WUPkQf/T66QDd+QWBpsJsKMBHcvrMeZkH5FzhwNc7qNaHlvpEm3kp7nUThZFcg3
BqR9T/dP1iue/I8fdbOT28b1OEDNRgBild8ntf4eCPoS3lqy5dBo/GnCOL0ycnoS
swDOQrIVnEF3vPWZMW3+uxEpsuZrI3JAS0vWa79qI+s5wpCvu0Gv1mh5b8Srnyk6
pbcxfHyj7kQl1f4cz+cxYcT2xBpccGN1Dqa2xqbnuPogocWFX3+LilnrLNm1DaQC
xRPvxket4rhBH2PPsjmnj+YHtvOsICWdnqMNavKgARpyRKqv2S+LKlccrRf+fspX
e97AbcZoLH+suJBq4ztaYftHSat8Ug==
=jcX7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Dec 11 14:23:10 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 2023F130F61 for <anima@ietfa.amsl.com>; Tue, 11 Dec 2018 14:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Jk0ytwSqaFPP for <anima@ietfa.amsl.com>; Tue, 11 Dec 2018 14:23:03 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2D1C12E036 for <anima@ietf.org>; Tue, 11 Dec 2018 14:23:03 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1B66920089; Tue, 11 Dec 2018 17:22:57 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id EA13CE1B; Tue, 11 Dec 2018 17:23:02 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E977EE15; Tue, 11 Dec 2018 17:23:02 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>
cc: "anima\@ietf.org" <anima@ietf.org>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
In-Reply-To: <96570e67749741ce9ef24f4711a8171e@XCH-ALN-010.cisco.com>
References: <31331.1543205187@dooku.sandelman.ca> <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com> <6717.1544314291@localhost> <96570e67749741ce9ef24f4711a8171e@XCH-ALN-010.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 11 Dec 2018 17:23:02 -0500
Message-ID: <27943.1544566982@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/frddCw_rbQSE1_4lXOk9elI4b8A>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Tue, 11 Dec 2018 22:23:07 -0000

--=-=-=
Content-Type: text/plain


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> I was assuming it was mandatory in the current draft, but I was wrong. As
> you suggest it is not clear in the -17 version. I do think that an unsigned
> voucher should make it to the MASA, like a signed one would, for
> consistency.

okay, I'm glad that we agree that it should be consistent.

I'm not convinced it's worth having unsigned pledge requests at all.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwQOMYACgkQgItw+93Q
3WXVLAf/Wagg9M6qz1sUolfvKnQVqUgMv27tqbELMQda6R30dGwKfEQO4elS3NQk
9ZmA6wlHvGwrrUDrdXussxQE5wxC6rortPXdANC4HM8tBR+zjNVJiKkn7DoffZpN
aIzT4NSaqt3RkEJn2oQklZfYUSKw9jc75m99+0qycrqgsTaAJaxSxeau5tyapLGK
w97FLgST9DNaylDN7HaC4LJhmN0v13P1T7DCW0ENw7YxCVJZQpsIVM6CHV/XCfiB
epQMMtJq1y++RjTpno9Tf+OOHuYYwyXWW2yZEZxlx/kG31aCuxAhMGcjNP81X0BD
Keo/3N8242vJdUTFq8ycQN+zTTxTaQ==
=N+Fy
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Dec 11 15:27:01 2018
Return-Path: <pritikin@cisco.com>
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 1D0CE130F63 for <anima@ietfa.amsl.com>; Tue, 11 Dec 2018 15:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level: 
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 mCkqdnDOFCtP for <anima@ietfa.amsl.com>; Tue, 11 Dec 2018 15:26:57 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57A53124D68 for <anima@ietf.org>; Tue, 11 Dec 2018 15:26:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1934; q=dns/txt; s=iport; t=1544570817; x=1545780417; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Byz71ae6S+8h60mwkSbm/4BbIhyhycoGKPavHWR+MYE=; b=jP0GeowNjzRorUXmRE5a7HuM0jerCZyGbbR/BOA49pD5OPer8tQ7HXWU jPPHcT0uWYTNJbtkqd4hmd3gm6J6M60YVcwGjQ5f86mo9ZR12BvWGpLbo 1eTIWAb7zPB4xRZRoed7xqu4EbI6fOEB/6ALX5QKBGD4Ou+okmx+jzzvY o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAADpRhBc/4QNJK1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgVopgWgnCoNxiBmMEoFoJXyWVoF6CwE?= =?us-ascii?q?BgXeCdQIXglUiNAkNAQMBAQIBAQJtKIU8AQEBAQIBIxFFBQsCAQgYAgImAgI?= =?us-ascii?q?CMBUQAgQOBYMhgXoIpgqBL4otgQuJboFCF4F/gREnDBOCFzWBQQGGQzGCJgK?= =?us-ascii?q?gJlUJAo1jg2wYgX+PQZkMAhEUgScfOIFWcBVlAYJBgjOBCgEMjRFBMYpMgR8?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,343,1539648000"; d="scan'208";a="484032241"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2018 23:26:56 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id wBBNQuI9014424 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Dec 2018 23:26:56 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 17:26:55 -0600
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1395.000; Tue, 11 Dec 2018 17:26:55 -0600
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, "anima@ietf.org" <anima@ietf.org>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
Thread-Topic: unsigned voucher requests in BRSKI
Thread-Index: AQHUhT2I5TAzcNtwDEK/OjpiRydQR6VytTIAgANMYYCAA15zgIABOjwAgAAR14A=
Date: Tue, 11 Dec 2018 23:26:55 +0000
Message-ID: <54D14F99-1027-4EEE-8805-8CC4616BC74E@cisco.com>
References: <31331.1543205187@dooku.sandelman.ca> <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com> <6717.1544314291@localhost> <96570e67749741ce9ef24f4711a8171e@XCH-ALN-010.cisco.com> <27943.1544566982@localhost>
In-Reply-To: <27943.1544566982@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.99.106.3]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6E23E3A67215314AA202D1E770682E3B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.19, xch-aln-009.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Rd-P-kj0prsZ9qvpsLuL0yYr5GM>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Tue, 11 Dec 2018 23:26:59 -0000

DQoNCj4gT24gRGVjIDExLCAyMDE4LCBhdCAzOjIzIFBNLCBNaWNoYWVsIFJpY2hhcmRzb24gPG1j
citpZXRmQHNhbmRlbG1hbi5jYT4gd3JvdGU6DQo+IA0KPiANCj4gUGFub3MgS2FtcGFuYWtpcyAo
cGthbXBhbmEpIDxwa2FtcGFuYUBjaXNjby5jb20+IHdyb3RlOg0KPj4gSSB3YXMgYXNzdW1pbmcg
aXQgd2FzIG1hbmRhdG9yeSBpbiB0aGUgY3VycmVudCBkcmFmdCwgYnV0IEkgd2FzIHdyb25nLiBB
cw0KPj4geW91IHN1Z2dlc3QgaXQgaXMgbm90IGNsZWFyIGluIHRoZSAtMTcgdmVyc2lvbi4gSSBk
byB0aGluayB0aGF0IGFuIHVuc2lnbmVkDQo+PiB2b3VjaGVyIHNob3VsZCBtYWtlIGl0IHRvIHRo
ZSBNQVNBLCBsaWtlIGEgc2lnbmVkIG9uZSB3b3VsZCwgZm9yDQo+PiBjb25zaXN0ZW5jeS4NCj4g
DQo+IG9rYXksIEknbSBnbGFkIHRoYXQgd2UgYWdyZWUgdGhhdCBpdCBzaG91bGQgYmUgY29uc2lz
dGVudC4NCj4gDQo+IEknbSBub3QgY29udmluY2VkIGl0J3Mgd29ydGggaGF2aW5nIHVuc2lnbmVk
IHBsZWRnZSByZXF1ZXN0cyBhdCBhbGwuDQoNClNhZGx5IEkgdGhpbmsgd2Ugc3RpbGwgaGF2ZSB0
byByZXNwZWN0IGZvbGtzIHRoYXQgYXJlIHdvcnJpZWQgYWJvdXQgdGhlIGV4dHJhIGNyeXB0byBv
cGVyYXRpb25zIG9uIHRoZSBwbGVkZ2UuIFBhcnRpY3VsYXJseSBnaXZlbiB0aGUgc2l6ZS9jb21w
bGV4aXR5IG9mIGEgQ01TIHNpZ25hdHVyZS4gSUYgd2XigJlkIGdvbmUgd2l0aCBhIGp3dC9jd3Qg
c2lnbmF0dXJlIEnigJlkIGJlIG1vcmUgb3BlbiB0byDigJxqdXN0IHNpZ24gZXZlcnl0aGluZ+KA
nS4gDQoNCkkgcmVzcGVjdCB0aGUgZGVzaXJlIHRvIGZvcndhcmQgdGhlIHVuc2lnbmVkIHJlcXVl
c3Qg4oCcZm9yIGNvbnNpc3RlbmN54oCdIGJ1dCBkaXNhZ3JlZS4gTXkgcmVhc29uaW5nIGlzIHRo
YXQgdGhlIHVuc2lnbmVkIHJlcXVlc3QgaXMgKm5vdCBzaWduZWQqIGFuZCB0aGVyZWZvcmUgY2Fu
IE5PVCBwcm92aWRlIGFueSB2YWx1ZSB0byB0aGUgTUFTQS4gQXMgc3VjaCBpbmNsdWRpbmcgaXQg
aW4gdGhlIG1lc3NhZ2VzIGlzIHNpbXBseSBhZGRpdGlvbmFsIG92ZXJoZWFkIGFuZCBvcHBvcnR1
bml0eSBmb3IgYSBNQVNBIHRvIG1lc3MgdXAgYW5kLCBmb3IgZXhhbXBsZSwgdXNlIHRoZSBub25j
ZSBmcm9tIGl0IGV2ZW4gaWYgdGhlIFJlZ2lzdHJhciBkb2VzbuKAmXQgd2FudCBhIG5vbmNlIChv
ciBvdGhlciB3ZWlyZCBidWdzIHRoYXQgd291bGQgYmUgZGlmZmljdWx0IHRvIG5vdGljZSB1bnRp
bCB0aGV5IHdlcmUgYSBwYWluKS4gDQoNCi0gbWF4DQoNCj4gDQo+IC0tDQo+IE1pY2hhZWwgUmlj
aGFyZHNvbiA8bWNyK0lFVEZAc2FuZGVsbWFuLmNhPiwgU2FuZGVsbWFuIFNvZnR3YXJlIFdvcmtz
DQo+IC09IElQdjYgSW9UIGNvbnN1bHRpbmcgPS0NCj4gDQo+IA0KPiANCg0K


From nobody Tue Dec 11 16:52:12 2018
Return-Path: <pritikin@cisco.com>
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 67233129C6A; Tue, 11 Dec 2018 16:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.959
X-Spam-Level: 
X-Spam-Status: No, score=-15.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ih50og4ZTzbg; Tue, 11 Dec 2018 16:52:03 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 381D5127598; Tue, 11 Dec 2018 16:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9850; q=dns/txt; s=iport; t=1544575923; x=1545785523; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TNb0supGxN3wSnMe2Rn4hSzkyIAh+6di0SdaU8MfIFE=; b=QPAn+1NvpZRZl3o76eiNQSlJuZABeYlm2YU3NHqduI6ec2FjviwDJijz Rvqy7wFFcytnAGCOwq1TqDpu+Ji2+XVpnfFyeRzeH7KhFfbBQl2qfkFl8 2WfC+kf1TKFAr82atfjnJKUUC43K1L8MlXrILUNhese0Uw8/sV4Cz7v1c I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAAAlWxBc/5RdJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ12ZoECJwqDcYgZjBKUBoVZgXoLAQE?= =?us-ascii?q?ngVCCdQIXglUiNAkNAQMBAQIBAQJtHAyFPQYjVhACAQg/AwICAjAUEQIEDgW?= =?us-ascii?q?DIQGBHWQPpgSBL4oqBYw7F4F/gTgfgkyDHgEBAgGBSIMaMYImAolRgVqDfJF?= =?us-ascii?q?UCQKHB4pIGJFAjhaKdgIRFIEnHziBVnAVZQGCQYIiBReIXoU/QTEBiR8rgQG?= =?us-ascii?q?BHwEB?=
X-IronPort-AV: E=Sophos;i="5.56,343,1539648000";  d="scan'208,217";a="211767364"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Dec 2018 00:52:02 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id wBC0q2nA011229 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Dec 2018 00:52:02 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 18:52:01 -0600
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1395.000; Tue, 11 Dec 2018 18:52:01 -0600
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Jim Schaad <ietf@augustcellars.com>, "ace@ietf.org" <ace@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Peter van der Stok <stokcons@bbhmail.nl>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Thread-Topic: [Ace] est-coaps clarification on /att and /crts
Thread-Index: AQHUkW6wpKPGP7xkTEa+IFO1X4G7f6V6NZcAgABKjQCAACtXgA==
Date: Wed, 12 Dec 2018 00:52:01 +0000
Message-ID: <B4901FFA-18C1-4B85-8B7A-60DD98A8D521@cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <036301d49179$f2558bf0$d700a3d0$@augustcellars.com> <26234.1544566610@localhost>
In-Reply-To: <26234.1544566610@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.99.106.3]
Content-Type: multipart/alternative; boundary="_000_B4901FFA18C14B858B7A60DD98A8D521ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/JhIPXK_Cv8NBSCExwjhhp8giBiQ>
Subject: Re: [Anima] [Ace] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 00:52:06 -0000

--_000_B4901FFA18C14B858B7A60DD98A8D521ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCk9uIERlYyAxMSwgMjAxOCwgYXQgMzoxNiBQTSwgTWljaGFlbCBSaWNoYXJkc29uIDxtY3Ir
aWV0ZkBzYW5kZWxtYW4uY2E8bWFpbHRvOm1jcitpZXRmQHNhbmRlbG1hbi5jYT4+IHdyb3RlOg0K
DQoNCkppbSBTY2hhYWQgPGlldGZAYXVndXN0Y2VsbGFycy5jb208bWFpbHRvOmlldGZAYXVndXN0
Y2VsbGFycy5jb20+PiB3cm90ZToNCkNsYXJpZmljYXRpb24gcmVxdWVzdGVkIC0gZXhhY3RseSB3
aGF0IGVsZW1lbnQgaXMgdGhlIFJlZ2lzdHJhcj8NCg0KSXQncyBhbiBFU1QgUkZDNzAzMCB0ZXJt
LCBidXQgZXNzZW50aWFsbHkgaXQncyB0aGUgc2VydmVyIHRoYXQgY29ubmVjdHMgdG8NCihvciBp
cykgdGhlIENBLg0KDQpUaGUgUmVnaXN0cmFyIHRlcm1pbm9sb2d5IGlzIGZyb20gdGhlIEFuaW1h
IHdvcmtpbmcgZ3JvdXAgYW5kIGlzIGNsb3NlbHkgYW5hbG9nb3VzIHRvIHRoZSDigJxSZWdpc3Ry
YXRpb24gQXV0aG9yaXR54oCdIHdlIGtub3cgYW5kIGxvdmUgZnJvbSB0aGUgUEtJIHNwYWNlLg0K
DQoNCiAgIEpvaW4gUmVnaXN0cmFyIChhbmQgQ29vcmRpbmF0b3IpOiAgQSByZXByZXNlbnRhdGl2
ZSBvZiB0aGUgZG9tYWluDQogICAgICB0aGF0IGlzIGNvbmZpZ3VyZWQsIHBlcmhhcHMgYXV0b25v
bWljYWxseSwgdG8gZGVjaWRlIHdoZXRoZXIgYSBuZXcNCg0KICAgICAgZGV2aWNlIGlzIGFsbG93
ZWQgdG8gam9pbiB0aGUgZG9tYWluLiAgVGhlIGFkbWluaXN0cmF0b3Igb2YgdGhlDQoNCg0KICAg
ICAgZG9tYWluIGludGVyZmFjZXMgd2l0aCBhICJqb2luIHJlZ2lzdHJhciAoYW5kIGNvb3JkaW5h
dG9yKSIgdG8NCiAgICAgIGNvbnRyb2wgdGhpcyBwcm9jZXNzLiAgVHlwaWNhbGx5IGEgam9pbiBy
ZWdpc3RyYXIgaXMgImluc2lkZSIgaXRzDQogICAgICBkb21haW4uICBGb3Igc2ltcGxpY2l0eSB0
aGlzIGRvY3VtZW50IG9mdGVuIHJlZmVycyB0byB0aGlzIGFzIGp1c3QNCiAgICAgICJyZWdpc3Ry
YXIiLiAgV2l0aGluIFtJLUQuaWV0Zi1hbmltYS1yZWZlcmVuY2UtbW9kZWw8aHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYW5pbWEtYm9vdHN0cmFwcGluZy1rZXlpbmZyYS0x
NyNyZWYtSS1ELmlldGYtYW5pbWEtcmVmZXJlbmNlLW1vZGVsPl0gdGhpcyBpcw0KICAgICAgcmVm
ZXJlZCB0byBhcyB0aGUgImpvaW4gcmVnaXN0cmFyIGF1dG9ub21pYyBzZXJ2aWNlIGFnZW50Ii4N
Cg0KSXQgdGVybWluYXRlcyB0aGUgQlJTS0kgcHJvdG9jb2wgZnJvbSB0aGUgbmV3IGRldmljZSBh
bmQsIGFmdGVyIHByb2Nlc3NpbmcgYW5kIGRlY2lzaW9ucywgZm9yd2FyZHMgbWVzc2FnZXMgdG8g
YSBtYW51ZmFjdHVyZXIgYXV0aG9yaXplZCBzaWduaW5nIGF1dGhvcml0eSB0byBvYnRhaW4gdm91
Y2hlcnMgYW5kIGVuc3VyZSByZWNvcmRzL2F1ZGl0LWxvZ3MgYXJlIGtlcHQuIEl0IGFsc28gcHVs
bHMgdGhvc2UgYXVkaXQgbG9ncyB0byBtYWtlIGFkZGl0aW9uYWwgZGVjaXNpb25zLiBJdCBpcyBy
ZXNwb25zaWJsZSBmb3IgbWFraW5nIHRoZSBhdXRob3JpemF0aW9uIGRlY2lzaW9uIGNvbmNlcm5p
bmcgaWYgdGhlIG5ldyBkZXZpY2Ugc2hvdWxkIGJlIGFsbG93ZWQgdG8gam9pbiB0aGUgbmV0d29y
ay4NCg0KSXQgYWxzbyBvcHRpb25hbGx5IGRvdWJsZXMgYXMgYSBlbnJvbGxtZW50IG92ZXIgc2Vj
dXJlIHRyYW5zcG9ydCAoUkZDNzAzMCkgcmVnaXN0cmF0aW9uIGF1dGhvcml0eSBpbiB0aGUgbm9y
bWFsIFBLSSBzZW5zZS4gVGhpcyBpcyByZWNvbW1lbmRlZCBpbiB0aGF0IEJSU0tJIHJlY29tbWVu
ZHMgdGhhdCBkZXZpY2VzIGdvIG9uIHRvIGVucm9sbCBhbmQgb2J0YWluIGEgY2VydGlmaWNhdGUu
DQoNCi0gbWF4DQoNCg0KVGhlIG9uZSBpdGVtIHRoYXQgSSBjYW4gZ2VuZXJhbGx5IHRoaW5rIG9m
IHRoYXQgbWlnaHQgYmUgYSBwcm9ibGVtIGlzIHRoYXQNCnRoZSBhbnN3ZXJzIHRvIC9hdHQgYW5k
IC9jcnRzIG1heSBkaWZmZXIgYmFzZWQgb24gdGhlIGVudGl0eSB0aGF0IGlzIGFza2luZw0KdGhl
IHF1ZXN0aW9uLiAgSW4gdGhpcyBjYXNlIG5vdCBoYXZpbmcgdGhlIGVudGl0eSBiZWluZyB2YWxp
ZGF0ZWQgbWVhbnMgdGhhdA0KdGhlICJ3cm9uZyIgYW5zd2VyIG1heSBiZSByZXR1cm5lZCBvciBk
aWZmZXJlbnQgYW5zd2VycyB3b3VsZCBiZSByZXR1cm5lZA0KYmVmb3JlIGFuZCBhZnRlciB2YWxp
ZGF0aW9uLg0KDQpZZXMsIEkgYWdyZWU6IGl0IHNob3VsZCBiZSByZXN0cmljdGVkLg0KDQpJIHRo
aW5rIHRoYXQgaXQgc2hvdWxkIGJlIHJlc3RyaWN0ZWQuIFBhcnRseSwgSSdtIGp1c3Qgbm90IHN1
cmUgd2hlcmUgdGhlDQp0ZXh0IHNob3VsZCBnbywgb3IgaWYgaXQgbmVlZHMgdG8gYmUgc2FpZCBh
dCBhbGwuDQoNCi0tDQpNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1hbi5jYTxt
YWlsdG86bWNyK0lFVEZAc2FuZGVsbWFuLmNhPj4sIFNhbmRlbG1hbiBTb2Z0d2FyZSBXb3Jrcw0K
LT0gSVB2NiBJb1QgY29uc3VsdGluZyA9LQ0KDQo=

--_000_B4901FFA18C14B858B7A60DD98A8D521ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FAF9EE9D4519C94C92AFB85C138F6E25@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxkaXY+PGJyIGNsYXNz
PSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPk9u
IERlYyAxMSwgMjAxOCwgYXQgMzoxNiBQTSwgTWljaGFlbCBSaWNoYXJkc29uICZsdDs8YSBocmVm
PSJtYWlsdG86bWNyJiM0MztpZXRmQHNhbmRlbG1hbi5jYSIgY2xhc3M9IiI+bWNyJiM0MztpZXRm
QHNhbmRlbG1hbi5jYTwvYT4mZ3Q7IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1pbnRl
cmNoYW5nZS1uZXdsaW5lIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCkppbSBTY2hhYWQgJmx0OzxhIGhyZWY9Im1haWx0bzppZXRmQGF1Z3VzdGNlbGxhcnMu
Y29tIiBjbGFzcz0iIj5pZXRmQGF1Z3VzdGNlbGxhcnMuY29tPC9hPiZndDsgd3JvdGU6PGJyIGNs
YXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+Q2xhcmlmaWNhdGlvbiBy
ZXF1ZXN0ZWQgLSBleGFjdGx5IHdoYXQgZWxlbWVudCBpcyB0aGUgUmVnaXN0cmFyPzxiciBjbGFz
cz0iIj4NCjwvYmxvY2txdW90ZT4NCjxiciBjbGFzcz0iIj4NCkl0J3MgYW4gRVNUIFJGQzcwMzAg
dGVybSwgYnV0IGVzc2VudGlhbGx5IGl0J3MgdGhlIHNlcnZlciB0aGF0IGNvbm5lY3RzIHRvPGJy
IGNsYXNzPSIiPg0KKG9yIGlzKSB0aGUgQ0EuPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2PlRoZSBSZWdp
c3RyYXIgdGVybWlub2xvZ3kgaXMgZnJvbSB0aGUgQW5pbWEgd29ya2luZyBncm91cCBhbmQgaXMg
Y2xvc2VseSBhbmFsb2dvdXMgdG8gdGhlIOKAnFJlZ2lzdHJhdGlvbiBBdXRob3JpdHnigJ0gd2Ug
a25vdyBhbmQgbG92ZSBmcm9tIHRoZSBQS0kgc3BhY2UuJm5ic3A7PC9kaXY+DQo8ZGl2PjxiciBj
bGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250
LXNpemU6IDEzLjMzMzNweDsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IGJy
ZWFrLWJlZm9yZTogcGFnZTsgZm9udC12YXJpYW50LWxpZ2F0dXJlczogbm9ybWFsOyBvcnBoYW5z
OiAyOyB3aWRvd3M6IDI7Ij4gICBKb2luIFJlZ2lzdHJhciAoYW5kIENvb3JkaW5hdG9yKTogIEEg
cmVwcmVzZW50YXRpdmUgb2YgdGhlIGRvbWFpbg0KICAgICAgdGhhdCBpcyBjb25maWd1cmVkLCBw
ZXJoYXBzIGF1dG9ub21pY2FsbHksIHRvIGRlY2lkZSB3aGV0aGVyIGEgbmV3PC9wcmU+DQo8cHJl
IGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxMy4zMzMzcHg7IG1hcmdpbi10b3A6
IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBicmVhay1iZWZvcmU6IHBhZ2U7IGZvbnQtdmFyaWFu
dC1saWdhdHVyZXM6IG5vcm1hbDsgb3JwaGFuczogMjsgd2lkb3dzOiAyOyI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTogMTMuMzMzM3B4OyIgY2xhc3M9IiI+ICAgICAgZGV2aWNlIGlzIGFsbG93ZWQg
dG8gam9pbiB0aGUgZG9tYWluLiAgVGhlIGFkbWluaXN0cmF0b3Igb2YgdGhlPC9zcGFuPg0KPC9w
cmU+DQo8cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxMy4zMzMzcHg7IG1h
cmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBicmVhay1iZWZvcmU6IHBhZ2U7IGZv
bnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDsgb3JwaGFuczogMjsgd2lkb3dzOiAyOyI+ICAg
ICAgZG9tYWluIGludGVyZmFjZXMgd2l0aCBhICZxdW90O2pvaW4gcmVnaXN0cmFyIChhbmQgY29v
cmRpbmF0b3IpJnF1b3Q7IHRvDQogICAgICBjb250cm9sIHRoaXMgcHJvY2Vzcy4gIFR5cGljYWxs
eSBhIGpvaW4gcmVnaXN0cmFyIGlzICZxdW90O2luc2lkZSZxdW90OyBpdHMNCiAgICAgIGRvbWFp
bi4gIEZvciBzaW1wbGljaXR5IHRoaXMgZG9jdW1lbnQgb2Z0ZW4gcmVmZXJzIHRvIHRoaXMgYXMg
anVzdA0KICAgICAgJnF1b3Q7cmVnaXN0cmFyJnF1b3Q7LiAgV2l0aGluIFs8YSBocmVmPSJodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1hbmltYS1ib290c3RyYXBwaW5nLWtl
eWluZnJhLTE3I3JlZi1JLUQuaWV0Zi1hbmltYS1yZWZlcmVuY2UtbW9kZWwiIHRpdGxlPSImcXVv
dDtBIFJlZmVyZW5jZSBNb2RlbCBmb3IgQXV0b25vbWljIE5ldHdvcmtpbmcmcXVvdDsiIGNsYXNz
PSIiPkktRC5pZXRmLWFuaW1hLXJlZmVyZW5jZS1tb2RlbDwvYT5dIHRoaXMgaXMNCiAgICAgIHJl
ZmVyZWQgdG8gYXMgdGhlICZxdW90O2pvaW4gcmVnaXN0cmFyIGF1dG9ub21pYyBzZXJ2aWNlIGFn
ZW50JnF1b3Q7LiA8L3ByZT4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8
ZGl2IGNsYXNzPSIiPkl0IHRlcm1pbmF0ZXMgdGhlIEJSU0tJIHByb3RvY29sIGZyb20gdGhlIG5l
dyBkZXZpY2UgYW5kLCBhZnRlciBwcm9jZXNzaW5nIGFuZCBkZWNpc2lvbnMsIGZvcndhcmRzIG1l
c3NhZ2VzIHRvIGEgbWFudWZhY3R1cmVyIGF1dGhvcml6ZWQgc2lnbmluZyBhdXRob3JpdHkgdG8g
b2J0YWluIHZvdWNoZXJzIGFuZCBlbnN1cmUgcmVjb3Jkcy9hdWRpdC1sb2dzIGFyZSBrZXB0LiBJ
dCBhbHNvIHB1bGxzIHRob3NlIGF1ZGl0IGxvZ3MNCiB0byBtYWtlIGFkZGl0aW9uYWwgZGVjaXNp
b25zLiBJdCBpcyByZXNwb25zaWJsZSBmb3IgbWFraW5nIHRoZSBhdXRob3JpemF0aW9uIGRlY2lz
aW9uIGNvbmNlcm5pbmcgaWYgdGhlIG5ldyBkZXZpY2Ugc2hvdWxkIGJlIGFsbG93ZWQgdG8gam9p
biB0aGUgbmV0d29yay4mbmJzcDs8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0K
PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkl0IGFsc28gb3B0aW9uYWxseSBkb3VibGVzIGFzIGEgZW5y
b2xsbWVudCBvdmVyIHNlY3VyZSB0cmFuc3BvcnQgKFJGQzcwMzApIHJlZ2lzdHJhdGlvbiBhdXRo
b3JpdHkgaW4gdGhlIG5vcm1hbCBQS0kgc2Vuc2UuIFRoaXMgaXMgcmVjb21tZW5kZWQgaW4gdGhh
dCBCUlNLSSByZWNvbW1lbmRzIHRoYXQgZGV2aWNlcyBnbyBvbiB0byBlbnJvbGwgYW5kIG9idGFp
biBhIGNlcnRpZmljYXRlLiZuYnNwOzwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+LSBtYXg8L2Rpdj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIi
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRp
diBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0i
Ij5UaGUgb25lIGl0ZW0gdGhhdCBJIGNhbiBnZW5lcmFsbHkgdGhpbmsgb2YgdGhhdCBtaWdodCBi
ZSBhIHByb2JsZW0gaXMgdGhhdDxiciBjbGFzcz0iIj4NCnRoZSBhbnN3ZXJzIHRvIC9hdHQgYW5k
IC9jcnRzIG1heSBkaWZmZXIgYmFzZWQgb24gdGhlIGVudGl0eSB0aGF0IGlzIGFza2luZzxiciBj
bGFzcz0iIj4NCnRoZSBxdWVzdGlvbi4gJm5ic3A7SW4gdGhpcyBjYXNlIG5vdCBoYXZpbmcgdGhl
IGVudGl0eSBiZWluZyB2YWxpZGF0ZWQgbWVhbnMgdGhhdDxiciBjbGFzcz0iIj4NCnRoZSAmcXVv
dDt3cm9uZyZxdW90OyBhbnN3ZXIgbWF5IGJlIHJldHVybmVkIG9yIGRpZmZlcmVudCBhbnN3ZXJz
IHdvdWxkIGJlIHJldHVybmVkPGJyIGNsYXNzPSIiPg0KYmVmb3JlIGFuZCBhZnRlciB2YWxpZGF0
aW9uLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCjxiciBjbGFzcz0iIj4NClllcywgSSBh
Z3JlZTogaXQgc2hvdWxkIGJlIHJlc3RyaWN0ZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KSSB0aGluayB0aGF0IGl0IHNob3VsZCBiZSByZXN0cmljdGVkLiBQYXJ0bHksIEknbSBqdXN0
IG5vdCBzdXJlIHdoZXJlIHRoZTxiciBjbGFzcz0iIj4NCnRleHQgc2hvdWxkIGdvLCBvciBpZiBp
dCBuZWVkcyB0byBiZSBzYWlkIGF0IGFsbC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQot
LTxiciBjbGFzcz0iIj4NCk1pY2hhZWwgUmljaGFyZHNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1j
ciYjNDM7SUVURkBzYW5kZWxtYW4uY2EiIGNsYXNzPSIiPm1jciYjNDM7SUVURkBzYW5kZWxtYW4u
Y2E8L2E+Jmd0OywgU2FuZGVsbWFuIFNvZnR3YXJlIFdvcmtzPGJyIGNsYXNzPSIiPg0KLT0gSVB2
NiBJb1QgY29uc3VsdGluZyA9LTxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_B4901FFA18C14B858B7A60DD98A8D521ciscocom_--


From nobody Tue Dec 11 18:59:18 2018
Return-Path: <pkampana@cisco.com>
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 B07B4131007; Tue, 11 Dec 2018 18:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level: 
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 StiwEyB2_lz0; Tue, 11 Dec 2018 18:59:14 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8741C1277D2; Tue, 11 Dec 2018 18:59:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4599; q=dns/txt; s=iport; t=1544583554; x=1545793154; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=LFwOWljz6mrzN4BjrEIickIClcAr5V5xVKDbPkK7o8U=; b=MolTP/HYlUqhAaJ7f+GIYgUYqWArU4LLPbHLByEkt+ybbQzuTn834Eq3 rq0lfH59azmB6xrNxuQwzo46vABI6oEXe6EaJiotdN6oq/DpJLLTl1TdS +cCA2QReLdkZNJub+VpBGYztgisU9bgNwhQWwWyfhtec7H7IjX7RD3I14 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAACkeBBc/5JdJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQInCowKjh+XUoF6CwEBH4FYgnU?= =?us-ascii?q?CgmwiNAkNAQMBAQIBAQJtHAyFPAEBAQECATo/BQcEAgEIEQQBAQEeEDIdCAI?= =?us-ascii?q?EAQ0FCIMagXkIpx+KMIlzgkgXgUA/gRGDEoRrhXEClXaKMFUJApFJIJFCiSO?= =?us-ascii?q?PagIRFIEnHziBVnAVgycJhSuLJ0ExiziBHwEB?=
X-IronPort-AV: E=Sophos;i="5.56,343,1539648000"; d="scan'208";a="211803218"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Dec 2018 02:59:13 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id wBC2xDov001154 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Dec 2018 02:59:13 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Dec 2018 20:59:12 -0600
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Tue, 11 Dec 2018 20:59:12 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "ace@ietf.org" <ace@ietf.org>,  "anima@ietf.org" <anima@ietf.org>
CC: Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin (pritikin)" <pritikin@cisco.com>
Thread-Topic: est-coaps clarification on /att and /crts
Thread-Index: AQHUkW6xEQf9wDn5PkCg7PZRmoPArKV5u4KggADGBID//+UPkA==
Date: Wed, 12 Dec 2018 02:59:12 +0000
Message-ID: <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost>
In-Reply-To: <27594.1544566907@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.174.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/UB6zQsOqMvwRsoPKHIm3z_Yeis8>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 02:59:17 -0000

Gotcha, so you are describing a provisional DTLS connection at the server.=
=20

Just to give a bit more color, in a usecase we are working on right now the=
 mesh network link rate <100Kbps. That network gets oversubscribed with leg=
it cacert responses. I can only imagine how worse it would be if bad guys w=
ere allowed to send small /crt requests and trigger big cert responses.=20

Just a 4.01 would not tell the client that he needs to send client certs fo=
r auth. In plain EST it would take an HTTP 401 with an=20
WWW-Authenticate  =3D "WWW-Authenticate" ":" 1#challenge
header in the response. Unless we replicate that a generic 4.01 would not b=
e enough for the client to know what to do.=20

Another issue is EST-coaps request pipelining. A cacerts could precede an e=
nrollment in the same DTLS connection (for really constrained devices that =
don't want to establish two connections). This could be opening room for un=
authenticated enrollments when pipelining is used.=20

I think it is a good idea to not repeat the EST behavior in regards to /crt=
 and /att. Provisional TLS at the server could have value in Constrianed-BR=
SKI/voucher though, for some situations though.=20

> So I think that we need to say something in EST-COAPS to explain that we =
do not see a use case for replying to /crts and /att for clients which are =
not recognized.  Is 401 (4.01) or 403 (4.03) more appropriate do you think?=
=20

Currently we say that clients need to be authenticated in a DTLS connection=
 before an EST-coaps request. Do you want to make it more explicit to say t=
hat even though EST allowed for it, EST-coaps does not allow unauthenticate=
d /crt and /att? We can certainly add that.=20

Rgs,
Panos


-----Original Message-----
From: Michael Richardson <mcr+ietf@sandelman.ca>=20
Sent: Tuesday, December 11, 2018 5:22 PM
To: Panos Kampanakis (pkampana) <pkampana@cisco.com>; ace@ietf.org; anima@i=
etf.org
Cc: Peter van der Stok <stokcons@bbhmail.nl>; Max Pritikin (pritikin) <prit=
ikin@cisco.com>
Subject: Re: est-coaps clarification on /att and /crts

* PGP Signed by an unknown key


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> I thought about this for the EST-coaps draft. EST allowed for=20
> unauthenticated /cacerts and /csrattrs (/crt and /att in EST-coaps) as=20
> you are suggesting.

Exactly.

> It is not as simple in EST-coaps. Two reasons:

> 1) There are constrained networks where an easy amplification attack=20
> could take place. For example the /crt request is very small and the=20
> response can be big (a few KBs in the context of a constrained network=20
> is big). If unauthenticated, then /crts could be an easy amplification=20
> attack to saturate a constrained network. We don't want that to=20
> happen. We want all our clients to be authenticated by DTLS before=20
> they start loading up our RF network.

I'm not suggesting that the DTLS be skipped, I'm suggesting that the client=
 certificate presented might be meaningless to the EST server.
As for amplication attacks, they usually depend upon forged source addresse=
s, and in that case the DTLS wouldn't have completed.

> 2) Additionally, there is a practical challenge of COAPS. When the=20
> DTLS handshake is taking place the server does not know what the=20
> request will be. In EST the server would send an HTTP WWW-Authenticate=20
> header to ask the client to authenticate. Such a mechanism does not=20
> exist in COAP, so it would not be straightforward unless we introduced=20
> a bunch of new things into COAP.

AFAIK, we don't support HTTP-level authentication in COAPS, only DTLS level=
 authentication is specified in EST-COAPS.

> I think it is still right to authenticate clients even for /crt and=20
> /att in the EST-coaps context. Maybe that is something to be revisited=20
> in Constrained-BRSKI/voucher, but not taken lightly.

So I think that we need to say something in EST-COAPS to explain that we do=
 not see a use case for replying to /crts and /att for clients which are no=
t recognized.  Is 401 (4.01) or 403 (4.03) more appropriate do you think?

--
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        |    IoT architect =
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [



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




* Unknown Key
* 0xDDD0DD65


From nobody Wed Dec 12 08:01:37 2018
Return-Path: <Hannes.Tschofenig@arm.com>
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 3B0AF130E5F; Wed, 12 Dec 2018 08:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.36
X-Spam-Level: 
X-Spam-Status: No, score=-3.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.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 f7MRG92Uwz9v; Wed, 12 Dec 2018 08:01:16 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40040.outbound.protection.outlook.com [40.107.4.40]) (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 BC097130E78; Wed, 12 Dec 2018 08:01:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=K775lBOs9TkLpemjUhiW2XBLPku/RVrgu30J/iIaXRo=; b=OLjnHrBH4Kkcbie3L8KUESnO5Ru6FhKytg+EXsX/xmgyddMh8jpDcgGGUSK1vKQAmqGK4e+nodpQ146E2bGQA1CPieOX4I8FfceOXWbdHNUB6p3zJC9rs3VnQbioOBTSrFzHge1cIrWBD3mDVcckYZS4rYBo5tfTyZsonKLX9zU=
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB1503.eurprd08.prod.outlook.com (10.167.210.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1404.19; Wed, 12 Dec 2018 16:01:12 +0000
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::2056:1db1:e01:4670]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::2056:1db1:e01:4670%3]) with mapi id 15.20.1404.026; Wed, 12 Dec 2018 16:01:12 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "ace@ietf.org" <ace@ietf.org>, "anima@ietf.org" <anima@ietf.org>
CC: Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin (pritikin)" <pritikin@cisco.com>
Thread-Topic: est-coaps clarification on /att and /crts
Thread-Index: AQHUkca4BtLnIlFbhEGGxTZ2pBjVOKV7Q0YQ
Date: Wed, 12 Dec 2018 16:01:12 +0000
Message-ID: <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost> <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com>
In-Reply-To: <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com; 
x-originating-ip: [217.140.106.27]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0801MB1503; 6:qpXhigW1CzCFsOXfdhV01yZk9/ezPSdVXrhy2gg+RpOVds6DnvmTp3xJSI4Cz06yi1TY0qdtDiASmEr0vmFc5p0lsDw1r1g2obRKy23Q2DwKP3/Ec6vB+LquOQO7nDIkOMAV0MDHMmRJdllneOr7A+SZ0wqODe//+CM1/RPnK+1a4P4vCH/RzGxk2FwEaF/7e4KOstOi8aF3kmYEgLTSBbLN39vdegiEdj7M0oiFUXHoRS6Axjw9FK6sex0NsXrbz5iJLQiYUCYNXZLJ1NOt3tCTwQOIu7xoCfS/VvR1EDbtzrhjdoLbJhN8xUL98scHFUv8iKmY6I0vCUjqfR21/djWgIjr7M1ipX2gUf/rlHETB54Plchd0BoC51+OEIwzK2F/Q/l7QLMVUUALakEugH3hMc1G86coSjqsrKILQeitigxxvEBWkBa4//axF49NVxjnVvCDlsnThYeupS/dTQ==; 5:786I35Nixfnwk3HjzyFE/kttq/LYEMIZE6RzArYhtnywt6gsSibufEuuWGlSJ1QqOD9FwpRmp7yq4uBB1qCGu/+UVWdPMo5jBbFBxJBqCvBMwz5P05LIISlOHhJOfnaNtqU3gVdpbkqjWYgwOr1xUNv8wpyWGOpTMUJVI4gmWPs=; 7:9uCnX9KrCAxaWoEFWQ4jte6N5OqUGwbZA3VV8Dw3ybFXEJw6BC7v5bQpQbp4HdD/eJYK8osn1bwnO+Yu3alZCwiztXtKsBzwjOmzBemTlKq5vp/RBcMHT8PTlXE4YdqDsdIjn0qe/xFLZJ8jiADBlg==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 10aa4913-7ec9-4d9c-e63d-08d6604b0a02
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB1503; 
x-ms-traffictypediagnostic: VI1PR0801MB1503:
x-microsoft-antispam-prvs: <VI1PR0801MB1503206A8835D4B69900C1C8FAA70@VI1PR0801MB1503.eurprd08.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(3230017)(999002)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3231472)(944501520)(52105112)(3002001)(93006095)(93001095)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123558120)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:VI1PR0801MB1503; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0801MB1503; 
x-forefront-prvs: 0884AAA693
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(396003)(366004)(39860400002)(136003)(376002)(40434004)(199004)(189003)(8936002)(305945005)(256004)(8676002)(5660300001)(4326008)(11346002)(6436002)(476003)(81166006)(76176011)(229853002)(486006)(25786009)(446003)(71200400001)(86362001)(74316002)(99286004)(93886005)(2906002)(71190400001)(3846002)(7696005)(316002)(68736007)(54906003)(6116002)(14454004)(81156014)(110136005)(106356001)(66066001)(33656002)(105586002)(97736004)(2501003)(5024004)(55016002)(7736002)(9686003)(53936002)(6246003)(72206003)(478600001)(186003)(26005)(6506007)(102836004)(14444005); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB1503; H:VI1PR0801MB2112.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 3BgQM3S5Cmhwl53aB+Gpe1Y/ZgPUPxNk91sk4BEIBxNzZQGqU2+DvVydAjeI4yb0RoPtP1p4koHqAG5KlQYRtdjo1V2BCwo7ZNM9AdGAQvo8aP5YvNXRM4Y1zl3eJHmb9c4XM2F1ff63gofSjvvwfgpiMLyyt0Gj/vJw/BBTcZQGXgDZz0MC3UwLU2rMNfxc+JSais2LG2NOrGbnX0LVVcAsgy3T0wD0POYrTcoL1dQagOztIPC3BIAtCvBMSfTG9Qhp6gbxwFXQrk3An8Oy7qte5vvhHxuheKfNu5BQHvuL68qmw7Y8zMHsrcvOcUm/
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 10aa4913-7ec9-4d9c-e63d-08d6604b0a02
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Dec 2018 16:01:12.4688 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB1503
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yrAbXYcPrKdnb2Kq9V04nzUg3j4>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 16:01:36 -0000

Hi Panos, Hi Michael,

> We want all our clients to be authenticated by DTLS before they start loa=
ding up our RF network.
> I'm not suggesting that the DTLS be skipped, I'm suggesting that the clie=
nt certificate presented might be meaningless to the EST server.

I am curious what security model you have in mind? If you don't do client a=
uthentication then you are essentially issuing certificates to an anonymous=
 entity. This feels like a very bad idea, particularly since the CA is supp=
osed to assert the identifier of the client via the certificate.

What am I missing here?

Ciao
Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.


From nobody Wed Dec 12 11:13:21 2018
Return-Path: <pkampana@cisco.com>
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 9912D131261; Wed, 12 Dec 2018 11:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.96
X-Spam-Level: 
X-Spam-Status: No, score=-15.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 WLkkqA68c7Xl; Wed, 12 Dec 2018 11:13:15 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7EBE130F08; Wed, 12 Dec 2018 11:13:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1701; q=dns/txt; s=iport; t=1544641995; x=1545851595; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=2bDVMT/5S4OowiKsOl/doUUuWhaqaBa6tMGPCaLmadU=; b=E/xvRBfNQi70TCl5DOKgDWh23y4uvBmKN33KhwLX36Jc+dz9C2XrmvOZ lEBHShI4AE54iN1sSjcRsxFjVY98u6ak+bk9j+vXk3/nARnbREuyKj6UF XRuVkXXy8m/7ITUFTb15t8+9akjNY6LSZQWq1H35MMvtXOqBjkn2Xyg/0 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAADRXBFc/5RdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgVopgWgnCowLjBGCDZdTFIFmCwEBhGw?= =?us-ascii?q?CgnwiNAkNAQMBAQIBAQJtKIU8AQEBAQIBOjYJBQcEAgEIEQQBAR8QMh0IAgQ?= =?us-ascii?q?BDQUIhRMIqBeKKYsfgR0XgUA/JmuDEoROARIBCR0xhSMCiSGXawkCjWiDZSC?= =?us-ascii?q?BXCOEd4pQiSmPbwIRFIEnHzhlcXAVO4Jsgz0BAo0bQTGLSYEfgR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,345,1539648000"; d="scan'208";a="211545458"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Dec 2018 19:13:14 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id wBCJDEEN010235 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 12 Dec 2018 19:13:14 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 12 Dec 2018 13:13:13 -0600
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1395.000; Wed, 12 Dec 2018 13:13:13 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "ace@ietf.org" <ace@ietf.org>, "anima@ietf.org" <anima@ietf.org>
CC: Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin (pritikin)" <pritikin@cisco.com>
Thread-Topic: est-coaps clarification on /att and /crts
Thread-Index: AQHUkW6xEQf9wDn5PkCg7PZRmoPArKV5u4KggADGBID//+UPkIABQvEA///E8MA=
Date: Wed, 12 Dec 2018 19:13:13 +0000
Message-ID: <de390a455e90491eb096822874b13491@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost> <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com> <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
In-Reply-To: <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.34.173]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6fyM77qLybU_3FjKXKeJH-fKK5Q>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 19:13:19 -0000

Hi Hannes,
Michael was only asking if allowing any anonymous entity to get the cacerts=
 (trusted root cert list) is worth it. RFC7030 allows for this. Of course a=
n enrollment would still require authentication/authorization.=20
I was making the case that it is not worth to even allow anonymous get cace=
rts.=20
Panos


-----Original Message-----
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>=20
Sent: Wednesday, December 12, 2018 11:01 AM
To: Panos Kampanakis (pkampana) <pkampana@cisco.com>; Michael Richardson <m=
cr+ietf@sandelman.ca>; ace@ietf.org; anima@ietf.org
Cc: Peter van der Stok <stokcons@bbhmail.nl>; Max Pritikin (pritikin) <prit=
ikin@cisco.com>
Subject: RE: est-coaps clarification on /att and /crts

Hi Panos, Hi Michael,

> We want all our clients to be authenticated by DTLS before they start loa=
ding up our RF network.
> I'm not suggesting that the DTLS be skipped, I'm suggesting that the clie=
nt certificate presented might be meaningless to the EST server.

I am curious what security model you have in mind? If you don't do client a=
uthentication then you are essentially issuing certificates to an anonymous=
 entity. This feels like a very bad idea, particularly since the CA is supp=
osed to assert the identifier of the client via the certificate.

What am I missing here?

Ciao
Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.


From nobody Wed Dec 12 11:18:11 2018
Return-Path: <ietf@augustcellars.com>
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 85EBE130F16; Wed, 12 Dec 2018 11:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vvMF7n6opDbK; Wed, 12 Dec 2018 11:18:01 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA713130F09; Wed, 12 Dec 2018 11:18:00 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 12 Dec 2018 11:12:51 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Hannes Tschofenig' <Hannes.Tschofenig@arm.com>, "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>, <ace@ietf.org>, <anima@ietf.org>
CC: 'Peter van der Stok' <stokcons@bbhmail.nl>, "'Max Pritikin (pritikin)'" <pritikin@cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost> <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com> <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
In-Reply-To: <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
Date: Wed, 12 Dec 2018 11:17:49 -0800
Message-ID: <04a101d4924f$610eab50$232c01f0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGPjv7lcqlAiUUAise1VV4kpyPAbQIUVGQwAvmGCYUCY0fpRgJQ0QBzAff7TbOlp7ECMA==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jqW6UsaBMmcalEwnJV1sdwJZLLU>
Subject: Re: [Anima] [Ace] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 19:18:05 -0000

> -----Original Message-----
> From: Ace <ace-bounces@ietf.org> On Behalf Of Hannes Tschofenig
> Sent: Wednesday, December 12, 2018 8:01 AM
> To: Panos Kampanakis (pkampana) <pkampana@cisco.com>; Michael
> Richardson <mcr+ietf@sandelman.ca>; ace@ietf.org; anima@ietf.org
> Cc: Peter van der Stok <stokcons@bbhmail.nl>; Max Pritikin (pritikin)
> <pritikin@cisco.com>
> Subject: Re: [Ace] est-coaps clarification on /att and /crts
> 
> Hi Panos, Hi Michael,
> 
> > We want all our clients to be authenticated by DTLS before they start
loading
> up our RF network.
> > I'm not suggesting that the DTLS be skipped, I'm suggesting that the
client
> certificate presented might be meaningless to the EST server.
> 
> I am curious what security model you have in mind? If you don't do client
> authentication then you are essentially issuing certificates to an
anonymous
> entity. This feels like a very bad idea, particularly since the CA is
supposed to
> assert the identifier of the client via the certificate.
> 
> What am I missing here?

Hannes, 

What you are missing is that the question is not about issuing the
certificate.  That is going to require client authentication.  What is being
looked at is getting the list of trust anchors or the template for a
certificate request based on an anonymous client.

Jim

> 
> Ciao
> Hannes
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
recipient,
> please notify the sender immediately and do not disclose the contents to
any
> other person, use it for any purpose, or store or copy the information in
any
> medium. Thank you.
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace


From nobody Wed Dec 12 11:34:00 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 77D7E131239 for <anima@ietfa.amsl.com>; Wed, 12 Dec 2018 11:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 l3S4tKdjRDJa for <anima@ietfa.amsl.com>; Wed, 12 Dec 2018 11:33:55 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 B4982130F20 for <anima@ietf.org>; Wed, 12 Dec 2018 11:33:55 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id t13so9042593ply.13 for <anima@ietf.org>; Wed, 12 Dec 2018 11:33:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fR7aEna8XLXh/YKUVXlbdtUmHqzRHQBy0ftTu2EEaT8=; b=XfyP3j+702WyMNG16UXGOk3smA4LHqI8b0TwypUE44qf2jbtzVaQ3EEe8ugY9jzjAR SLEHnIJx7zeIwTl5B62Dp5cLVaIuymCrVE39M5yk4kVKzH2bPEzSacvGQHuf8S4DDOni epa5LV/uYUoWkqQv1y0hJVqiVU7UmOM3vMR+A6Abb9BSTrz3G2h1qxNpvZItB3HA8Z0a HVS5ZXSqXzl8gTfk+g1I+tOLcMGflhdXNXEy6p3RzTTsVNMvgWqZFhCV/bTbCicDnEBE Ss8yRH+uwB7hm7mcVQ9zAuNVHEbn+4n8Wubl3mb5baFS0sVp07+WfKDfIpdZ3QyycGWB Q5YQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fR7aEna8XLXh/YKUVXlbdtUmHqzRHQBy0ftTu2EEaT8=; b=k+1Hpqel2QJkdupokuM0OA35EGkdAg07ig4jWn+gpHjkZhOW4J/6lrnQ4oFuayvYVu T3XPYXemMCKeGUySm+ywaBgyBLAh8TUme0Oh0iorD/DrYyrm1BaFqTF5VVWLmmcVlPty 2k3JM9nYjsPJRw3dN2cmcjif/Oh7ZMAtOmI4utkbHeNuoAjpZnkjVCRNtC5YupHZMhl3 nYFiV3uHagdn+pn44eG5qGq8NCveqB8CoTM3PIH1WkRKWOHVW5owza/v/G0dtRGqQk2V cOlLkwdESiDPbjpxMWIhgHSjGzES+3jhlheRctcQPtmGN0pAYH+IgEKWLT1Inw23UCi8 A+GQ==
X-Gm-Message-State: AA+aEWZcD7GougzV3UIyehlKvkzZN5ZzN6lV8IgDjEYwFbxnW6bSidB2 C08ic5mtBieZ4IJeGd5lWMZGOrAoP6s=
X-Google-Smtp-Source: AFSGD/VBtAsVeRvByaFfTtnvByZiJY0ZNy+zAKBG/IH0ug+wmXGF6Lr1HRbUPEjsgxgCVliBhop3EQ==
X-Received: by 2002:a17:902:bd0b:: with SMTP id p11mr21154269pls.259.1544643234920;  Wed, 12 Dec 2018 11:33:54 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id b5sm37304105pfc.150.2018.12.12.11.33.53 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Dec 2018 11:33:54 -0800 (PST)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: Anima WG <anima@ietf.org>
References: <154464277622.21337.17843192863207122168@ietfa.amsl.com>
Message-ID: <313c9673-4cd4-2583-613e-8db871c005e9@gmail.com>
Date: Thu, 13 Dec 2018 08:33:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <154464277622.21337.17843192863207122168@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/j7-eLesRJm1VlqNkkBEHVKCAPKo>
Subject: [Anima] Fwd: I-D Action: draft-carpenter-limited-domains-05.txt
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: Wed, 12 Dec 2018 19:33:59 -0000

An update following recent comments.

Discussion on int-area@ietf.org please.

-------- Forwarded Message --------
Subject: I-D Action: draft-carpenter-limited-domains-05.txt
Date: Wed, 12 Dec 2018 11:26:16 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Limited Domains and Internet Protocols
        Authors         : Brian Carpenter
                          Bing Liu
	Filename        : draft-carpenter-limited-domains-05.txt
	Pages           : 23
	Date            : 2018-12-12

Abstract:
   There is a noticeable trend towards network requirements, behaviours
   and semantics that are specific to a limited region of the Internet
   and a particular set of requirements.  Policies, default parameters,
   the options supported, the style of network management and security
   requirements may vary.  This document reviews examples of such
   limited domains, also known as controlled environments, and emerging
   solutions, and develops a related taxonomy.  It then briefly
   discusses the standardization of protocols for limited domains.
   Finally, it shows the needs for a precise definition of limited
   domain membership and for mechanisms to allow nodes to join a domain
   securely and to find other members, including boundary nodes.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-carpenter-limited-domains/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-carpenter-limited-domains-05
https://datatracker.ietf.org/doc/html/draft-carpenter-limited-domains-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-carpenter-limited-domains-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Wed Dec 12 13:45:19 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 DDCEE1312DB; Wed, 12 Dec 2018 13:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 TLh7wGZXfmam; Wed, 12 Dec 2018 13:45:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8872F1312D9; Wed, 12 Dec 2018 13:45:09 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CA4CB20089; Wed, 12 Dec 2018 16:45:02 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id AF606DF7; Wed, 12 Dec 2018 16:45:08 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id AD55965; Wed, 12 Dec 2018 16:45:08 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>
cc: "ace\@ietf.org" <ace@ietf.org>, "anima\@ietf.org" <anima@ietf.org>, Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>
In-Reply-To: <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost> <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 12 Dec 2018 16:45:08 -0500
Message-ID: <24917.1544651108@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/63jbrk5bfLqCc06RbBGzSMjCFOQ>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 21:45:12 -0000

--=-=-=
Content-Type: text/plain


Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> Gotcha, so you are describing a provisional DTLS connection at the server.

I'm thinking about a Registrar that might be serving both provisional
connections and ones that are just renewing LDevIDs, and maybe ones that
also serve selected factory installed IDevIDs (a use case which est-coaps
caters directly to).

> Currently we say that clients need to be authenticated in a DTLS connection
> before an EST-coaps request. Do you want to make it more explicit to say
> that even though EST allowed for it, EST-coaps does not allow
> unauthenticated /crt and /att? We can certainly add that.

I'd like to add this.

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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwRgWQACgkQgItw+93Q
3WWT7ggAsPpX8JEJmKxY8e1BrZRoXWhx88H55/K7iXZJ2IajUL2PfHwag01SCIV5
Gejh8Uwhmfh+35Ayk9dk1gqEpBjyDBetU3mpeAf0D6sQq11bGmfldZ5YUxfP0Cku
Be+M1zRroujr300o48LvmdzcXcoP2xarvNXxAGTw6rTpWhJDGI9Vn27YB6hUM2bI
xk5MpRXZ4hPWNRixX6Oc6t12/5tgw+eF0vBbKXKTCqmAoHp++7JzSFe9jD1Emn9+
s/vYJmFGMzNx5T5uRti8xm32ZVEk+LgzpEyXjWRqQh8qRCh3KQhDgsDNcMymqeM8
Z02/Rh3S65niqbL4BFhzlKVFEg2D/Q==
=uKnf
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Dec 12 13:50:03 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 54DAC130F9D; Wed, 12 Dec 2018 13:50:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vCZ_ceINHpYU; Wed, 12 Dec 2018 13:50:00 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32A7E130F14; Wed, 12 Dec 2018 13:50:00 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3FF1920089; Wed, 12 Dec 2018 16:49:53 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 25115DF7; Wed, 12 Dec 2018 16:49:59 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 22D0B65; Wed, 12 Dec 2018 16:49:59 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
cc: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>, "ace\@ietf.org" <ace@ietf.org>, "anima\@ietf.org" <anima@ietf.org>, Peter van der Stok <stokcons@bbhmail.nl>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>
In-Reply-To: <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <47b9e5cbf7e64fad91a9fc79e83e392c@XCH-ALN-010.cisco.com> <27594.1544566907@localhost> <e5c042393be24304b0275ed07ea6ba2b@XCH-ALN-010.cisco.com> <VI1PR0801MB2112BE91B53B96FEB3C35E80FAA70@VI1PR0801MB2112.eurprd08.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 12 Dec 2018 16:49:59 -0500
Message-ID: <26097.1544651399@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-0HJRsT53f_SDGhaBpeqZCnE2Gw>
Subject: Re: [Anima] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 21:50:02 -0000

--=-=-=
Content-Type: text/plain


Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
> > We want all our clients to be authenticated by DTLS before they start
> > loading up our RF network.
> > I'm not suggesting that the DTLS be skipped, I'm suggesting that the
> > client certificate presented might be meaningless to the EST server.

> I am curious what security model you have in mind? If you don't do client
> authentication then you are essentially issuing certificates to an
> anonymous entity. This feels like a very bad idea, particularly since the
> CA is supposed to assert the identifier of the client via the certificate.

Clients which are not **yet** authenticatable.
The client shows up, does a DTLS connection.

We let the DTLS connection succeed, because we want to record the particulars
of the client, so we can ask a human.  Much like happens when you ssh to
a new host: it stops to ask if you you agree with the key.
You don't know, so you hit ^C.
So, that's all.  We don't intend to issue certificates... yet.

I'm also asking if there is some use case where the client might legitimate
need the list of trust anchors (/cacerts request) in order so that it can...?
(I couldn't think of a use case)

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

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwRgoYACgkQgItw+93Q
3WUAywf8DNBaU+Vq663N1NptMYEAeXksSV2LPDVUSzO7j0Z4CY4N3OihMxcexDvM
xlPCWojmOZSeO5OSKvQCQYtRVkgAwHNm99QE20iiN4Jyh3kCF6HT9XWnq8DvDgzC
nsIUC+iiWZSQU5W33mT4pL0E9dgnrD5r+lofE2/1rXR9nKULpAj3ufk3nfbUSbwQ
DBECaSUljTrKj8/spXfW0AYMw/eAsijrz/fNAH01/+w5QjYy/NlEWZ4xLFfEyJdX
8bm5PjLoowa+drLh2HRIt3YLoCXEUfm/5qY1Rl7phTu2BaSDTl/VYL9829MB8hb9
U5lofG3jfEbV8SYAd2Hu3U/rYzo+bw==
=KuMr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Dec 12 13:52:15 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 6CF0B1312DB; Wed, 12 Dec 2018 13:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2R2oN6tzjoO2; Wed, 12 Dec 2018 13:52:04 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64160130F9D; Wed, 12 Dec 2018 13:52:04 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AA56820089; Wed, 12 Dec 2018 16:51:57 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 8F774DF7; Wed, 12 Dec 2018 16:52:03 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8D82665; Wed, 12 Dec 2018 16:52:03 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Max Pritikin \(pritikin\)" <pritikin@cisco.com>
cc: Jim Schaad <ietf@augustcellars.com>, "ace\@ietf.org" <ace@ietf.org>, "anima\@ietf.org" <anima@ietf.org>, Peter van der Stok <stokcons@bbhmail.nl>, "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>
In-Reply-To: <B4901FFA-18C1-4B85-8B7A-60DD98A8D521@cisco.com>
References: <c07a0c0ecb5d48c4aed2595ab8cbef5c@XCH-ALN-010.cisco.com> <3831.1544545763@localhost> <036301d49179$f2558bf0$d700a3d0$@augustcellars.com> <26234.1544566610@localhost> <B4901FFA-18C1-4B85-8B7A-60DD98A8D521@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 12 Dec 2018 16:52:03 -0500
Message-ID: <26644.1544651523@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jmV_AdkG7gyac0ilrAsZ_y4Hr14>
Subject: Re: [Anima] [Ace] est-coaps clarification on /att and /crts
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: Wed, 12 Dec 2018 21:52:07 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Max Pritikin (pritikin) <pritikin@cisco.com> wrote:
>     Jim Schaad <ietf@augustcellars.com> wrote:
>
jim>     Clarification requested - exactly what element is the Registrar?

mcr>     It's an EST RFC7030 term, but essentially it's the server that
mcr>     connects to  (or is) the CA.

max> The Registrar terminology is from the Anima working group and is close=
ly
max> analogous to the =E2=80=9CRegistration Authority=E2=80=9D we know and =
love from the PKI
max> space.

Oh, right. I forgot that Registration Authority (RA) is not the same word as
"Registrar".  I wonder if we should have aligned that more, or aligned it l=
ess.


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




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwRgwMACgkQgItw+93Q
3WViLAgArKWctVotCxbo/VK+skZUT7x7BtMEXOwZ1Xyn+NfCXYFz2300m402nf19
wZCN5ACTSuD71wEVWSIArKIQOsTBVYOXgKOPV+JTTh3EWSe1Ns2Dy0aUgkikTwNR
8MVSclo1SQMeKobKff/2kbefNWkzqM1L97/nhPWxbdpfpY+fmJo2wBLze7mINR5q
zd0ZOGdMrBIuI8234Wumie1lxemPDLu6bYMW1rCksIcbaFhhteMbqWTpOrh4Bo32
Gua06NfN6vSdr/9/o+BvrX7kRKnpa67Gk/g3Fu6JUxfuRsiD5Ug/pJ+0W80Zivf9
X8GWc+kGbGcEdoW5/JgRnK4Sg1BIFA==
=eFo2
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Dec 13 07:05:07 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 4554E12785F for <anima@ietfa.amsl.com>; Thu, 13 Dec 2018 07:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NlCt0Hr18YwO for <anima@ietfa.amsl.com>; Thu, 13 Dec 2018 07:05:01 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E643112777C for <anima@ietf.org>; Thu, 13 Dec 2018 07:05:00 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CA4952008F; Thu, 13 Dec 2018 10:04:53 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 725E1D55; Thu, 13 Dec 2018 10:04:59 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6FBF9201; Thu, 13 Dec 2018 10:04:59 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Max Pritikin \(pritikin\)" <pritikin@cisco.com>
cc: "Panos Kampanakis \(pkampana\)" <pkampana@cisco.com>, "anima\@ietf.org" <anima@ietf.org>, consultancy <consultancy@vanderstok.org>, Kent Watsen <kwatsen@juniper.net>
In-Reply-To: <54D14F99-1027-4EEE-8805-8CC4616BC74E@cisco.com>
References: <31331.1543205187@dooku.sandelman.ca> <74eefbf79ef1462db2c75020fe9703fb@XCH-ALN-010.cisco.com> <6717.1544314291@localhost> <96570e67749741ce9ef24f4711a8171e@XCH-ALN-010.cisco.com> <27943.1544566982@localhost> <54D14F99-1027-4EEE-8805-8CC4616BC74E@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 13 Dec 2018 10:04:59 -0500
Message-ID: <31699.1544713499@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jf4o4EvQcLgBE8ZHRHlGQa_zpL0>
Subject: Re: [Anima] unsigned voucher requests in BRSKI
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: Thu, 13 Dec 2018 15:05:04 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Max Pritikin (pritikin) <pritikin@cisco.com> wrote:
> > On Dec 11, 2018, at 3:23 PM, Michael Richardson <mcr+ietf@sandelman.ca>=
 wrote:
> >
> >
> > Panos Kampanakis (pkampana) <pkampana@cisco.com> wrote:
> >> I was assuming it was mandatory in the current draft, but I was wrong.=
 As
> >> you suggest it is not clear in the -17 version. I do think that an uns=
igned
> >> voucher should make it to the MASA, like a signed one would, for
> >> consistency.
> >
> > okay, I'm glad that we agree that it should be consistent.
> >
> > I'm not convinced it's worth having unsigned pledge requests at all.
>
> Sadly I think we still have to respect folks that are worried about the
> extra crypto operations on the pledge. Particularly given the
> size/complexity of a CMS signature. IF we=E2=80=99d gone with a jwt/cwt s=
ignature
> I=E2=80=99d be more open to =E2=80=9Cjust sign everything=E2=80=9D.

Okay, but constrained vouchers signed with COSE?
We weren't sure we'd have that when we did the unsigned pledge request.

> I respect the desire to forward the unsigned request =E2=80=9Cfor consist=
ency=E2=80=9D but
> disagree. My reasoning is that the unsigned request is *not signed* and
> therefore can NOT provide any value to the MASA. As such including it in
> the messages is simply additional overhead and opportunity for a MASA to
> mess up and, for example, use the nonce from it even if the Registrar
> doesn=E2=80=99t want a nonce (or other weird bugs that would be difficult=
 to notice
> until they were a pain).

I definitely see your point.

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

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwSdRsACgkQgItw+93Q
3WUAmwgAlcVKWxhCS8FiV6qb0+b71i3s9YKebbHrjb5odIQNkRAJicl+HisBYTZG
q3gYBEflq9qeefTKTc/GOblEQi9HzqY7L0MzNxFynlIrVc2dkiMiUr1pRP/yFgby
370yHyvC3dsHJI4gEvXHGxeRfWmr6TZMaIwC+k6gxuef+vVsc6mTIynSBpL+CnEH
pP17euPIiFpzAUg2CVoL83QWYYHoPS6blDHCB3Q/xq21TqrTqMXeDqDGsh52ddVx
vCptYvL482c5uXphrON5BnNAs9k7xMQFwJ4G99uQtiXQrkH/1RyXJsp28X0lAHoO
Q0DXXAZjSlTWgiASHoHlM/5CiL15/Q==
=naa/
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Dec 13 08:27:13 2018
Return-Path: <mcr+ietf@sandelman.ca>
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 BAFF2126BED; Thu, 13 Dec 2018 08:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VI2A1r0-Syvk; Thu, 13 Dec 2018 08:27:08 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705CC127B4C; Thu, 13 Dec 2018 08:27:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 31D4A2008F; Thu, 13 Dec 2018 11:27:01 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 1DEC4D55; Thu, 13 Dec 2018 11:27:07 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1BAD4201; Thu, 13 Dec 2018 11:27:07 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>
cc: Iot-dir@ietf.org, draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org, ietf@ietf.org, anima@ietf.org
In-Reply-To: <154388094719.4951.644465000786184923@ietfa.amsl.com>
References: <154388094719.4951.644465000786184923@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 13 Dec 2018 11:27:07 -0500
Message-ID: <20444.1544718427@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/VgcxckYiVEZPwP3sEUrYoJWX_gY>
Subject: Re: [Anima] Iotdir telechat review of draft-ietf-anima-bootstrapping-keyinfra-17
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: Thu, 13 Dec 2018 16:27:12 -0000

--=-=-=
Content-Type: text/plain


Russ Housley <housley@vigilsec.com> wrote:
> Major Concerns:
>
> Section 2.2 says:
>
>    ...  The registrar
>    maintains control over the transport and policy decisions allowing
>    the local security policy of the domain network to be enforced.
>
> I have no idea what this means.  Please clarify.

duplicates issue raised by Jari:
https://github.com/anima-wg/anima-bootstrap/issues/92

> In Section 2.3, it says:
>
>    5.  (Optional) Signing of voucher-request by the pledges IDevID to
>        enable MASA to generate voucher only to a registrar that has a
>        connection to the pledge.
>
> This is an important section to understand BRSKI, but I cannot parse
> this sentence.  Please reword.

https://github.com/anima-wg/anima-bootstrap/issues/93

> Section 2.3.1 talks about pledges being uniquely identified by a
> "serial-number" in voucher and voucher-requests.  Pledges are also
> uniquely identified by their serial number in certificates.
>
> Section 2.3.1 refers to HardwareModuleName, which is defined in
> RFC 4108.  It says that the HardwareModuleName hwSerialNum is base64
> encoded.  RFC 4108 does not require base64 encoding.  Where does that
> requirement come from?

duplicates:
https://github.com/anima-wg/anima-bootstrap/issues/95

> Section 3.1 shows the YANG tree model of the Voucher-Request.  I am far
> from a YANG expert, but I expected a subsequent section to describe the
> semantics of each field.  The examples in Section 3.2 are useful, but
> they are not a replacement.  Some fields (like voucher/expires-on) are
> not described in Section 3.3.  I assume that this is building on another
> module because this one contains "import ietf-voucher", but this does
> not say what RFC contains the imported module to learn the rest of the
> semantics.

I think that the sentence:
  The notation used in this diagram is described in [RFC8366].

should be changed to say:
   The voucher-request builds upon
   the voucher artifact described in <xref target="RFC8366" />.
   The tree diagram is described in <xref target="RFC8340" />.

(we described tree-diagrams in 8366 at one point, because we didn't know if
8340 would get published in time)

> I think that the CDDL in Sections 4.1.1 and 4.3 are supposed to be
> structures.  If that is correct, the structure should look something
> like the following, which includes type information:
>
>    basic-header = [
>      field1: int,
>      field2: text,
>    ]
>
>    advanced-header = [
>      ~basic-header,
>      field3: bytes,
>      field4: ~time,
>    ]

We are filling in the gaps for the definition in GRASP M_FLOOD
mechanism.  We aren't defining a new structure.
I'm not sure if we can do this any other way.

> I have no idea what the boxes in Figure 10 represent.

Hmm. I guess we chopped the boxes off of the flow from section 2.4.
Would a reference back to section 2.4 help?
Maybe we should not repeat the boxes.

> Section 7.2 does not contain enough information to make the needed
> object identifier assignments.

Right we had a note to fix that. It's: SMI Security for PKIX Certificate Extension
  https://www.iana.org/assignments/smi-numbers/smi-numbers.xml#smi-numbers-1.3.6.1.5.5.7.1

> In Section 7.4, the IESG (not the IETF Chair) should be the contact
> for standards-track registrations.

Done.

>
> I think the security considerations ought to describe the consequences
> of compromise of the various private keys in the ecosystem.  Some only
> impact one device, but others have much greater impact.

okay.
I'm expanding issue #80 to include describing this.
    https://github.com/anima-wg/anima-bootstrap/issues/80

> I think the security considerations ought to say something about the
> nonce.  First, it should point to RFC 4086.  Second, it should say
> something about the consequences of a poor random source.  It does not
> need to be a comprehensive as the section dealing with setting time.

I've expanded issue #91:
     https://github.com/anima-wg/anima-bootstrap/issues/91

>
> Minor Concerns:

next email.

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

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlwSiFoACgkQgItw+93Q
3WVMGwgAqwESkSy97zOAn5NwfOt6TLIrkUnd8BjKeMsbF41693q5SxKl/HqBERC7
I5eBOyxLf2Hi3okhnAWSsssdcnTybAofC/+mplqdOXq7hVPlXMizPSiHzNmTmwi2
VlPRtBaIurfJuR/C2vCJwvLcUUMY/cRn6kl8d5WvBF2xklpMyHEMkjLPvRvR5h1V
mvJSf0+6PV3N2FipUabFsvYqO/J2Bic6jhejwsiOCrsNUydS3uviI/svkbl8X0Oy
XOnZW44WCupWXudimEEWLsTqCWCdHclU2HchfcPnmWMJ9bco7EwZJRsGvybrMjjo
T4W/5G4f7IAQstbskf/VhLu+KAMKxQ==
=nwB5
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Dec 13 09:16:36 2018
Return-Path: <housley@vigilsec.com>
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 2E3E4130E35 for <anima@ietfa.amsl.com>; Thu, 13 Dec 2018 09:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 vmsia-nnq-r8 for <anima@ietfa.amsl.com>; Thu, 13 Dec 2018 09:16:23 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 725CF130E3A for <anima@ietf.org>; Thu, 13 Dec 2018 09:16:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 194A0300A4B for <anima@ietf.org>; Thu, 13 Dec 2018 12:16:21 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VN9lBySyW96P for <anima@ietf.org>; Thu, 13 Dec 2018 12:16:19 -0500 (EST)
Received: from [192.168.1.161] (pool-108-45-137-105.washdc.fios.verizon.net [108.45.137.105]) by mail.smeinc.net (Postfix) with ESMTPSA id 0C46F300A20; Thu, 13 Dec 2018 12:16:19 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <0AB99A18-C0D0-4F99-9416-FBD8350E4502@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F0965590-7B89-4467-BA9C-CE57D50B6124"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 13 Dec 2018 12:16:20 -0500
In-Reply-To: <20444.1544718427@localhost>
Cc: "iot-dir@ietf.org" <Iot-dir@ietf.org>, draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org, IETF <ietf@ietf.org>, anima@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <154388094719.4951.644465000786184923@ietfa.amsl.com> <20444.1544718427@localhost>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/81EWtUgwSel19zL79cM2D4JkGIQ>
Subject: Re: [Anima] Iotdir telechat review of draft-ietf-anima-bootstrapping-keyinfra-17
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: Thu, 13 Dec 2018 17:16:34 -0000

--Apple-Mail=_F0965590-7B89-4467-BA9C-CE57D50B6124
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


>> Section 3.1 shows the YANG tree model of the Voucher-Request.  I am =
far
>> from a YANG expert, but I expected a subsequent section to describe =
the
>> semantics of each field.  The examples in Section 3.2 are useful, but
>> they are not a replacement.  Some fields (like voucher/expires-on) =
are
>> not described in Section 3.3.  I assume that this is building on =
another
>> module because this one contains "import ietf-voucher", but this does
>> not say what RFC contains the imported module to learn the rest of =
the
>> semantics.
>=20
> I think that the sentence:
>  The notation used in this diagram is described in [RFC8366].
>=20
> should be changed to say:
>   The voucher-request builds upon
>   the voucher artifact described in <xref target=3D"RFC8366" />.
>   The tree diagram is described in <xref target=3D"RFC8340" />.
>=20
> (we described tree-diagrams in 8366 at one point, because we didn't =
know if
> 8340 would get published in time)

Okay.  That works for me.

>=20
>> I think that the CDDL in Sections 4.1.1 and 4.3 are supposed to be
>> structures.  If that is correct, the structure should look something
>> like the following, which includes type information:
>>=20
>>   basic-header =3D [
>>     field1: int,
>>     field2: text,
>>   ]
>>=20
>>   advanced-header =3D [
>>     ~basic-header,
>>     field3: bytes,
>>     field4: ~time,
>>   ]
>=20
> We are filling in the gaps for the definition in GRASP M_FLOOD
> mechanism.  We aren't defining a new structure.
> I'm not sure if we can do this any other way.

Something needs to be done to set the context.  Clearly, I misunderstood =
the intent.

>> I have no idea what the boxes in Figure 10 represent.
>=20
> Hmm. I guess we chopped the boxes off of the flow from section 2.4.
> Would a reference back to section 2.4 help?
> Maybe we should not repeat the boxes.

I reference to Section 2.4 with no boxes would be more helpful than the =
current figure.

>> Section 7.2 does not contain enough information to make the needed
>> object identifier assignments.
>=20
> Right we had a note to fix that. It's: SMI Security for PKIX =
Certificate Extension
>  =
https://www.iana.org/assignments/smi-numbers/smi-numbers.xml#smi-numbers-1=
.3.6.1.5.5.7.1

I guessed that, but no guessing should be needed for IANA registry =
assignment.

Russ

--Apple-Mail=_F0965590-7B89-4467-BA9C-CE57D50B6124
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iF0EARECAB0WIQRJuTEKFXbtfFQz5huK5O7Q9ZwRywUCXBKT5AAKCRCK5O7Q9ZwR
ywX2AKD0+BuQODvYN6a4BOLGgohJKQFS9gCgjn0Q9e5LwGwsI2vObEV2/LKPSGY=
=Gw/e
-----END PGP SIGNATURE-----

--Apple-Mail=_F0965590-7B89-4467-BA9C-CE57D50B6124--


From nobody Thu Dec 13 12:40:32 2018
Return-Path: <brian.e.carpenter@gmail.com>
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 8241F130E90; Thu, 13 Dec 2018 12:40:31 -0800 (PST)
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 mY9WsYcrtoEP; Thu, 13 Dec 2018 12:40:29 -0800 (PST)
Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) (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 A076A130E86; Thu, 13 Dec 2018 12:40:29 -0800 (PST)
Received: by mail-pl1-x644.google.com with SMTP id p8so1608311plo.2; Thu, 13 Dec 2018 12:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ssd4juQyABmZDmu00fO+wXbM0HdQqrvNwDK9OQGY34M=; b=ma3nHYSY2sbullxo3NbIBlmn4WVrj/Re7cNmh8WI/WVFewKWbB8WrOoETxBt9EHaTj siuWAk1yVZ6QcWLA2db/mdAGhMx+Fiso+5kjWApTXEqYQLmkv0bFK91Yf98+11nNWY2i ipD+mTiBY9Br/6iDvKaGQHuDBJfH2q0hhLOgFOm5KR8lwdfPn8yvWeymvv78lPRAmhHQ kVIn1XJXMj6PUGqjN44IYZPHKdQCPltNs+cwdBixvULjtlrdVZG7wUGxF/z/bGD0oQjR 7B1wQbRdrC3a0YVzlPi2Q131dDLEbnAeXU4VySqIrHfB2d2DJJbzdabsT6SUZsxiixZd D98w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ssd4juQyABmZDmu00fO+wXbM0HdQqrvNwDK9OQGY34M=; b=QMLM0pbvz/cJyMiEYdp1acnHGDDLacfdwNkOjfN+40lXq9XDAG2ZR1znSVGqQd/+Rm cogPxxTI9J9rDKCba17SzNHm4WYErKsSL5OQXV3hRIfjkoJbCGvCIAGBjtZI6YYAF9AK cAndeZHJu+/rIu+QhfZBgiZzKHVaYBPAMEw54q9kTHFJLFMZge8fDZAmhbHOxXoBrZZN 6Wx+iGjbIH8wexLPzBUOaWGqWTn429nZDcqE8JBy7fHXS9VSDlvJcD0D879jl7cGp5go hiRMwDdigZjngrXmVVqTf8fgG4OyKl3ExqYjxhFQkAvHghVzO7GuwUZw6h9e8LMNp0wO eoWw==
X-Gm-Message-State: AA+aEWZAxjSg5ZCrI/jY87Jwvb7BqXMekm4jNeds32WsmPVj3WeN1wjg pGfo0wozTLJjZ7Ug9atYbWCbSDP7hY4=
X-Google-Smtp-Source: AFSGD/XHVMOa7YNLaAtCEGX6cswHzHMyG+X3Z+3AFz3CUHf6vcLFMGogBNUHW6KCJg41VGCrRKypDA==
X-Received: by 2002:a17:902:4464:: with SMTP id k91mr285282pld.13.1544733628936;  Thu, 13 Dec 2018 12:40:28 -0800 (PST)
Received: from [10.100.9.248] ([58.84.227.247]) by smtp.gmail.com with ESMTPSA id a18sm3632854pgj.30.2018.12.13.12.40.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Dec 2018 12:40:28 -0800 (PST)
To: Russ Housley <housley@vigilsec.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org, anima@ietf.org, IETF <ietf@ietf.org>, "iot-dir@ietf.org" <Iot-dir@ietf.org>
References: <154388094719.4951.644465000786184923@ietfa.amsl.com> <20444.1544718427@localhost> <0AB99A18-C0D0-4F99-9416-FBD8350E4502@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3a30b5b0-7487-deb1-539e-d95a0471db74@gmail.com>
Date: Fri, 14 Dec 2018 09:40:19 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <0AB99A18-C0D0-4F99-9416-FBD8350E4502@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/p3LwD125fG7egVBVkcp5t6T3VAY>
Subject: Re: [Anima] Iotdir telechat review of draft-ietf-anima-bootstrapping-keyinfra-17
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: Thu, 13 Dec 2018 20:40:32 -0000

On one point:

On 2018-12-14 06:16, Russ Housley wrote:
...
>>> I think that the CDDL in Sections 4.1.1 and 4.3 are supposed to be
>>> structures.  If that is correct, the structure should look something
>>> like the following, which includes type information:
>>>
>>>   basic-header = [
>>>     field1: int,
>>>     field2: text,
>>>   ]
>>>
>>>   advanced-header = [
>>>     ~basic-header,
>>>     field3: bytes,
>>>     field4: ~time,
>>>   ]
>>
>> We are filling in the gaps for the definition in GRASP M_FLOOD
>> mechanism.  We aren't defining a new structure.
>> I'm not sure if we can do this any other way.
> 
> Something needs to be done to set the context.  Clearly, I misunderstood the intent.

The CDDL which is being extended is defined in https://tools.ietf.org/html/draft-ietf-anima-grasp-15#section-5,
and that draft is fully approved but waiting in MISSREF limbo.

I don't have any concerns about the BRSKI CDDL because I did a toy implementation (Pledji.py, Procksy.py and Reggie.py at https://github.com/becarpenter/graspy). The CDDL in the draft has changed very slightly since then; when I have some free time I can update my Python code, but the differences are negligible.

[Side note: I don't think anybody would claim that they can automatically generate running code from CDDL yet. If that becomes realistic, it would be the acid test for CDDL used in protocol specs. But it's quite a way in the future, IMHO.]

Regards
    Brian

