Add required IANA Consciderations section

https://authors.ietf.org/iana-considerations

Author: mickenordin

IETF-RFC.md

@@ -524,6 +524,9 @@ Receiving Server to persuade the Sending Server to share the same Resource with
 The details of the payload and side effects such a notification may have are out of scope of this version of this specification.
 Note that the Receiving Party sending such a notification has no way of knowing if the Sending Party understood and processed the reshare request or not.
 
+# IANA Considerations
+This document has no IANA actions.
+
 # Appendix A: Multi Factor Authentication
 If a Receiving Server exposes the capability `enforce-mfa`, it indicates that it will try and comply with a MFA requirement set on a Share. If the Sending Server trusts the Receiving Server, the Sending Server MAY set the requirement `mfa-enforced` on a Share, which the Receiving Server MUST honor. A compliant Receiving Server that signals that it is MFA-capable MUST not allow access to a resource protected with the `mfa-enforced` requirement, if the Receiving Party has not provided a second factor to establish their identity with greater confidence.