How about:
2. Updated Requirements
This document removes and replaces the normative requirements from sections 3.1.1
and section 3.1.2 of RFC3405 with:
and section 3.1.2 of RFC3405 with:
The registration of a NAPTR record for a URI scheme MUST NOT precede registration of that scheme. IANA will review the request against for
1. correctness and technical soundness (eg. valid databases, service parameters etc.) and
2. consistency with the published URI resolution application specification, and
3. to ensure that the NAPTR record for a DNS-based URI does not delegate resolution of the URI to a party other than the holder of the DNS name. This last rule is to insure that a given URI's resolution hint doesn't hijack (inadvertently or otherwise) network traffic for a given domain.
3. IANA Considerations
This update does not change the IANA submission procedure in Section 5 of RFC 3405.
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
