Re: [Acme] Paul Wouters' No Objection on draft-ietf-acme-integrations-13: (with COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 13 March 2023 09:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0A2C14EB17; Mon, 13 Mar 2023 02:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.091
X-Spam-Level:
X-Spam-Status: No, score=-1.091 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5pGGhD1os5Uq; Mon, 13 Mar 2023 02:21:09 -0700 (PDT)
Received: from relay.sandelman.ca (unknown [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A03EC072E74; Mon, 13 Mar 2023 02:19:11 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [91.183.8.37]) by relay.sandelman.ca (Postfix) with ESMTPS id 9785A201D3; Mon, 13 Mar 2023 08:55:09 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 19218A1072; Thu, 9 Mar 2023 09:54:22 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 157ECA1071; Thu, 9 Mar 2023 15:54:22 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Wouters <paul.wouters@aiven.io>
cc: The IESG <iesg@ietf.org>, draft-ietf-acme-integrations@ietf.org, acme-chairs@ietf.org, acme@ietf.org, decoole@radium.ncsc.mil
In-reply-to: <167772596322.21739.9689242730499702095@ietfa.amsl.com>
References: <167772596322.21739.9689242730499702095@ietfa.amsl.com>
Comments: In-reply-to Paul Wouters via Datatracker <noreply@ietf.org> message dated "Wed, 01 Mar 2023 18:59:23 -0800."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 09 Mar 2023 15:54:22 +0100
Message-ID: <2179204.1678373662@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/4Me2eGh8VarmHmXI9sxoRmqMlOY>
Subject: Re: [Acme] Paul Wouters' No Objection on draft-ietf-acme-integrations-13: (with COMMENT)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2023 09:21:12 -0000

Paul Wouters via Datatracker <noreply@ietf.org> wrote:
    > Where does "pledge" come from? Is this a normative reference to
    > something?

Yes, it's a reference to RFC8366 (and RFC8995).

I'll add:

- Pledge:  from {{?RFC8366}}, the prospective device attempting to find and
      securely join a domain.  When shipped, it only trusts authorized
      representatives of the manufacturer.

It is, btw, representing visually as a duck, because of:

  [Stajano99theresurrecting]
                Stajano, F. and R. Anderson, "The Resurrecting Duckling:
                Security Issues for Ad-Hoc Wireless Networks", 1999,
                <https://www.cl.cam.ac.uk/research/dtg/www/files/
                publications/public/files/tr.1999.2.pdf>.

https://github.com/upros/acme-integrations/pull/58


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