Brian Weis (bew) <[email protected]> wrote: > So I’ve been trolling through the code, and discovered that the http > application/* headers do not match the latest release. I also hadn’t realized > that the Pledge can send either "application/json” (unsigned) or > "application/voucher-cms+json” (signed) vouchers. I’ve changed the > unsigned string to match the draft. But this raises a question:
> If the Pledge sends an unsigned Voucher, I would expect the Registrar to
> forward it in the MASA server as the "prior-signed-voucher”. But in fact
> it’s not signed, and I see elsewhere that the Registrar is supposed to
> send it signed. From Section 3 of -12:
> The "prior-signed-voucher-request" leaf is be used in Registrar
> voucher-requests to the Pledge voucher-request. It contains the
> encoded (signed form) of the Pledge voucher-request.
> What is the correct behavior?
I've opened this as issue:
https://github.com/anima-wg/anima-bootstrap/issues/48
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
