ticates itself to MASA as "I'm in
domain X / customer X" and then the same Registrar in its EST server role
assigns the Pledge to "domain / customer Y". And the MASA doesn't know about
this; it logs the Pledge to "domain X".
Esko
-Original Message-
From: Michael
Esko Dijk wrote:
> The new text looks good now. I was still wondering about the pg 12
> requirement in RFC 8366 ; which amounts to:
> The [domain certificate supplied to the pledge separately by the
> bootstrapping protocol] MUST have [pinned-domain-cert] somewhere in its
>
Thanks Michael for this update,
The new text looks good now. I was still wondering about the pg 12 requirement
in RFC 8366 ; which amounts to:
The [domain certificate supplied to the pledge separately by the
bootstrapping protocol] MUST have [pinned-domain-cert] somewhere in its chain
of
