AUTH48 status page for C481
Cluster Details
- draft-ietf-calext-jscontact-16.txt (RFC-to-be 9553) AUTH48-DONE
- draft-ietf-calext-vcard-jscontact-extensions-10.txt (RFC-to-be 9554) AUTH48-DONE*R
- draft-ietf-calext-jscontact-vcard-13.txt (RFC-to-be 9555) AUTH48-DONE*R
AUTH48-DONE 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.
AUTH48-DONE status of draft-ietf-calext-vcard-jscontact-extensions-10 (RFC-to-be 9554)
This document is in AUTH48 state as of 2024-03-15. 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-10 |
| M. Loffredo | Y | 2024-04-10 |
| AD - M. Kucherawy | Y | 2024-04-02 |
| AD - O. Steele | Y | 2024-04-09 |
** This document is part of Cluster C481, so may have additional holds before publication.
Notes:
2024-03-15: questions sent to authors. 2024-03-25: reminder sent. 2024-04-02: responses received. AD (Murray) approved the changes between versions 15 and 17 (and Orie also provided approval). 2024-04-03: requested AD approval of Sections 3.2 and 3.4. 2024-04-08: posed questions to the authors and sent reminder to the AD (Orie) to approve changes in Sections 3.2 and 3.4. 2024-04-09: AD (Orie) approved Sections 3.2 and 3.4. 2024-04-10: responses received.
AUTH48-DONE status of draft-ietf-calext-jscontact-vcard-13 (RFC-to-be 9555)
This document is in AUTH48 state as of 2024-03-15. 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 |
|---|---|---|
| M. Loffredo | Y | 2024-04-17 |
| R. Stepanek | Y | 2024-04-17 |
| AD - R. Danyliw (for changes submitted after approval) | Y | 2024-03-19 |
| AD - O. Steele (for changes during AUTH48) | Y | 2024-04-15 |
** This document is part of Cluster C481, so may have additional holds before publication.
Notes:
2024-03-15: questions sent to authors and AD. 2024-03-19: AD approval received for changes between versions -13 to -15. 2024-03-27: reminder sent. 2024-04-02: response received. 2024-04-04: responses received. 2024-04-15: response received. Asked for AD approval of changes made during AUTH48 (multiple sections). AD approval received. In addition, the AD confirmed that the use of "whitespace" is okay per the context. 2024-04-18: authors confirmed that they want to wait to publish this cluster until RFC-to-be 9562 has completed AUTH48 (so they can include the number in this doc).
Instructions to author(s):
Please see the AUTH48 notification email from the RFC Editor that contains links to the edited files and other information. To send your approval of or changes for a specific document, please Reply All to the message for the given RFC-to-be in question.
If cluster-wide questions were received, please Reply All to that email so each of the relevant parties may partake in the decision process.
See information below for the status of documents within the cluster that are in AUTH48.
When all approvals for a given document have been received, publication will continue once its normative references have completed the AUTH48 process as well. Upon publication of the cluster, this AUTH48 status page will no longer be available.