Draft: draft-ietf-anima-brski-ae

Commentary: This is mostly typos and rewording , plus converting some diagrams so that aasvg can do a better job . 
 Thank you for improvements . I will merge them now and then place some fixups .
CA Certs Request: The pledge optionally requests the latest
relevant CA certificates.  This ensures that the pledge has the
complete set of current CA certificates beyond the pinned-domain-
cert (which is contained in the voucher and may be just the domain
registrar certificate).
CA Certs Response: It MUST contain the current root CA
certificate, which typically is the LDevID trust anchor, and any
additional certificates that the pledge may need to validate
certificates.
Attribute Request: Typically, the automated bootstrapping occurs
without local administrative configuration of the pledge.
Nevertheless, there are cases in which the pledge may also include
additional attributes specific to the target domain into the
certification request.  To get these attributes in advance, the
attribute request can be used.
Attribute Response: It MUST contain the attributes to be included
in the subsequent certification request.
Certificate Request: This certification request MUST contain the
authenticated self-contained object ensuring both proof-of-
possession of the corresponding private key and proof-of-identity
of the requester.
Certificate Response: The certification response message MUST
contain on success the requested certificate and MAY include
further information, like certificates of intermediate CAs.
Certificate Confirm: An optional confirmation sent after the
requested certificate has been received and validated.  It
contains a positive or negative confirmation by the pledge whether
the certificate was successfully enrolled and fits its needs.
PKI/Registrar Confirm: An acknowledgment by the PKI or registrar
that MUST be sent on reception of the Cert Confirm.
CA Certs Request [1]: The pledge optionally requests the latest
relevant CA certificates.  This ensures that the pledge has the
complete set of current CA certificates beyond the pinned-domain-
cert (which is contained in the voucher and may be just the domain
registrar certificate).
CA Certs Response [2]: It MUST contain the current root CA
certificate, which typically is the LDevID trust anchor, and any
additional certificates that the pledge may need to validate
certificates.
Attribute Request [3]: Typically, the automated bootstrapping
occurs without local administrative configuration of the pledge.
Nevertheless, there are cases in which the pledge may also include
additional attributes specific to the target domain into the
certification request.  To get these attributes in advance, the
attribute request can be used.
Attribute Response [4]: It MUST contain the attributes to be
included in the subsequent certification request.
Certificate Request [5]: This certification request MUST contain
the authenticated self-contained object ensuring both proof-of-
possession of the corresponding private key and proof-of-identity
of the requester.
Certificate Response [6]: The certification response message MUST
contain on success the requested certificate and MAY include
further information, like certificates of intermediate CAs.
Certificate Confirm [7]: An optional confirmation sent after the
requested certificate has been received and validated.  It
contains a positive or negative confirmation by the pledge whether
the certificate was successfully enrolled and fits its needs.
PKI/Registrar Confirm [8]: An acknowledgment by the PKI or
registrar that MUST be sent on reception of the Cert Confirm.