Original text:
IANA [SHALL update/has added] the following notes: <del> Experts are to verify that there is in fact a publicly available specification.  An Internet Draft that is posted and never published or a specification in another standards body, industry consortium, university site, etc. suffices. </del>  As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the IANA [SHALL add/has added] the following notes for additional information: <del> The designated expert RFC8126 only ensures that the specification is publicly available.  An Internet Draft that is posted and never </del>  published or a standard in another standards body, industry <del> consortium, university site, etc. suffices. </del>  As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the has not been through the IETF consensus process, has limited applicability, or is intended only for specific use cases. <del> The designated expert RFC8126 only ensures that the specification is publicly available.  An Internet Draft that is posted and never </del>  published or a standard in another standards body, industry <del> consortium, university site, etc. suffices. </del>  Despite the following behavior being misguided, experience has shown that some customers use the IANA registry as checklist against which IANA [SHALL add/has added] the following notes: <del> The designated expert RFC8126 only ensures that the specification is publicly available.  An Internet Draft that is posted and never </del>  published or a standard in another standards body, industry <del> consortium, university site, etc. suffices. </del>  As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the To provide additional information for the designated experts, IANA [SHALL add/has added] the following note:  The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never published or a standard in another standards body, industry <del> consortium, university site, etc. suffices.  The expert also verifies that the label is a string consisting of printable ASCII </del>  characters beginning with "EXPORTER".  IANA MUST also verify that one label is not a prefix of any other label.  For example, labels "key" or "master secretary" are forbidden. IANA [SHALL add/has added] the following note:  Certificate Types marked as "Yes" are those allocated via Standards Track RFCs.  Certificate Types marked as "No" are not.

Reviewer comments:
This change aligns the DE text and adds more info about what the DE does and doesn't do. It also capitalizes "Recommended" so that it's more clear that we're referring to the column. NAME PTAL
LGTM, thanks for unifying the DE language.

Revised text:
IANA [SHALL update/has added] the following notes:  <ins> The role of the designature expert is described in [this-RFC]. The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never published or a standard in another standards body, industry consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the extension. </ins> As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the IANA [SHALL add/has added] the following notes for additional information:  <ins> The role of the designature expert is described in [this-RFC]. The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never </ins> published or a standard in another standards body, industry  <ins> consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the cipher suite. </ins> As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the has not been through the IETF consensus process, has limited applicability, or is intended only for specific use cases.  <ins> The role of the designature expert is described in [this-RFC]. The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never </ins> published or a standard in another standards body, industry  <ins> consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the supported group. </ins> Despite the following behavior being misguided, experience has shown that some customers use the IANA registry as checklist against which IANA [SHALL add/has added] the following notes:  <ins> The role of the designature expert is described in [this-RFC]. The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never </ins> published or a standard in another standards body, industry  <ins> consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the identifier. </ins> As specified in RFC8126, assignments made in the Private Use space are not generally useful for broad interoperability.  It is the To provide additional information for the designated experts, IANA [SHALL add/has added] the following note: <ins> The role of the designature expert is described in [this-RFC]. </ins> The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never published or a standard in another standards body, industry  <ins> consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the exporter.  The expert also verifies that the label is a string consisting of printable ASCII </ins> characters beginning with "EXPORTER".  IANA MUST also verify that one label is not a prefix of any other label.  For example, labels "key" or "master secretary" are forbidden. IANA [SHALL add/has added] the following note: <ins> The role of the designature expert is described in [this-RFC]. The designated expert RFC8126 ensures that the specification is publicly available.  An Internet Draft that is posted and never published or a standard in another standards body, industry consortium, university site, etc. suffices.  The expert may provide more in depth reviews, but their approval should not be taken as an endorsement of the certificate type. The designated expert RFC8126 only ensures that the specification is publicly available.  An Internet Draft that is posted and never published or a standard in another standards body, industry consortium, university site, etc. suffices. </ins> Certificate Types marked as "Yes" are those allocated via Standards Track RFCs.  Certificate Types marked as "No" are not.