Draft: draft-ietf-acme-acme

Commentary: badState should be orderNotReady Use " wildcard domain name " consistently instead of " wildcard prefix " 
 Thanks : ballotboxwith_check :
Paragraph (version A):
This field MUST be present and true for authorizations created as
a result of a newOrder request containing a DNS identifier with a
value that contained a wildcard prefix.  For other authorizations,
it MUST be absent.
Paragraph (version B):
This field MUST be present and true for authorizations created as
a result of a newOrder request containing a DNS identifier with a
value that was a wildcard domain name.  For other authorizations,
it MUST be absent.  Wildcard domain names are described in order-
objects.
Paragraph (version A):
The only type of identifier defined by this specification is a fully
qualified domain name (type: "dns").  The domain name MUST be encoded
in the form in which it would appear in a certificate.  That is, it
MUST be encoded according to the rules in Section 7 of RFC5280.
Servers MUST verify any identifier values that begin with the ASCII-
Compatible Encoding prefix "xn--" as defined in RFC5890 are properly
encoded.  Wildcard domain names (with "*" as the first label) MUST
NOT be included in authorization objects.  If an authorization object
conveys authorization for the base domain of a newOrder DNS type
identifier with a wildcard prefix, then the optional authorizations
"wildcard" field MUST be present with a value of true.
Paragraph (version B):
The only type of identifier defined by this specification is a fully
qualified domain name (type: "dns").  The domain name MUST be encoded
in the form in which it would appear in a certificate.  That is, it
MUST be encoded according to the rules in Section 7 of RFC5280.
Servers MUST verify any identifier values that begin with the ASCII-
Compatible Encoding prefix "xn--" as defined in RFC5890 are properly
encoded.  Wildcard domain names (with "*" as the first label) MUST
NOT be included in authorization objects.  If an authorization object
conveys authorization for the base domain of a newOrder DNS
identifier containing a wildcard domain name, then the optional
authorizations "wildcard" field MUST be present with a value of true.
Paragraph (version A):
A request to finalize an order will result in error if the order is
not in the "ready" state.  In such cases, the server MUST return a
403 (Forbidden) error with a problem document of type "badState".
The client should then send a POST-as-GET request to the order
resource to obtain its current state.  The status of the order will
indicate what action the client should take (see below).
Paragraph (version B):
A request to finalize an order will result in error if the order is
not in the "ready" state.  In such cases, the server MUST return a
403 (Forbidden) error with a problem document of type
"orderNotReady".  The client should then send a POST-as-GET request
to the order resource to obtain its current state.  The status of the
order will indicate what action the client should take (see below).
Paragraph (version A):
Note that because the identifier in a pre-authorization request is
the exact identifier to be included in the authorization object, pre-
authorization cannot be used to authorize issuance with wildcard DNS
identifiers.
Paragraph (version B):
Note that because the identifier in a pre-authorization request is
the exact identifier to be included in the authorization object, pre-
authorization cannot be used to authorize issuance of certificates
containing wildcard domain names.