Paul Wouters via Datatracker <[email protected]> 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 <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
