Two comments regarding references in draft-ietf-regext-rdap-jscontact: 1. The document includes an informative reference to draft-ietf-jmap-jscontact. That should be a normative reference because I don't think it's possible to implement draft-ietf-regext-rdap-jscontact without normative inclusion of JSContact itself.
2. draft-ietf-httpapi-deprecation-header (an informative reference) has expired. That'll be a problem when it comes time for last calls and IESG review/approval. Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
