AUTH48 status of draft-ietf-calext-jscontact-16 (RFC-to-be 9553)

This document is in AUTH48 state as of 2024-03-06. It has not yet been published as an RFC. The RFC Editor is awaiting approvals from the author(s) as shown below (and anyone else listed) before continuing the publication process.

Name Approved? Date of Approval
R. Stepanek Y 2024-04-05
M. Loffredo Y 2024-04-05
AD - O. Steele Y 2024-04-19
IANA Y 2024-04-09

** This document is part of Cluster C481, so may have additional holds before publication.

Notes:

2024-03-06: questions sent to authors and AD. 2024-03-14: reminder to respond sent to authors and AD. Response received that replies may be delayed due to the IETF meeting. 2024-03-20: response received. 2024-04-02: response received. Requested AD approval of the changes made after the document was approved as well as several changes made during AUTH48. 2024-04-04: added Orie to the thread and asked him to approve the changes described above. Approval received. 2024-04-05: responses received. Asked IANA to update their registries to match the edited document [IANA #1362591]. 2024-04-09: IANA updates are complete. 2024-04-19: changes made to Section 2.1.9; requested AD approval. Approval received. Note: the authors confirmed on 3/14/24 that this document should be published with the companion documents (RFCs-to-be 9554 and 9555). They would also like to wait for I-D.ietf-uuidrev-rfc4122bis to be published so they can include the RFC number (RFC 9562) prior to publication.

Instructions to author(s):

Please see the AUTH48 notification email from the RFC Editor that contains a link to the edited document and other information. To send your approval or changes, please Reply All to that message.

When all approvals have been received, publication is imminent. Upon publication as an RFC, this AUTH48 status page will no longer be available.



Advanced Search