AUTH48 status page for C506
Cluster Details
- draft-ietf-lamps-e2e-mail-guidance-17.txt (RFC-to-be 9787) AUTH48*R
- draft-ietf-lamps-header-protection-25.txt (RFC-to-be 9788) AUTH48*R
AUTH48 status of draft-ietf-lamps-e2e-mail-guidance-17 (RFC-to-be 9787)
This document is in AUTH48 state as of 2025-05-20. 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 |
|---|---|---|
| D. Gillmor | Y | 2025-06-17 |
| B. Hoeneisen | N | |
| A. Melnikov | Y | 2025-06-10 |
| AD - R. Danyliw | Y | 2025-07-16 |
** This document is part of Cluster C506, so may have additional holds before publication.
Notes:
2025-05-20: Questions sent to authors. 2025-05-21: Response received addressing some of the questions. 25 questions not yet addressed. 2025-05-22: Updated files sent w/ 1 follow-up question. 2025-05-29: Reminder sent. 2025-05-30: Response received. 2025-06-02: Updated files sent. 2025-06-09: Sent files w/ inclusive language updates per discussion w/ AD. 2025-06-17: Received XML file w/ additional updates. Updated files sent. 2025-06-27: Reminder sent. 2025-07-10: Reminder sent. 2025-07-11: Received XML file w/ additional updates. 2025-07-14: Updated files sent. Requested AD approval. 2025-07-23: Reminder sent. *NOTE: There is an open issue on GitHub regarding the misalignment of non-ASCII characters in artwork in the PDF output: https://github.com/ietf-tools/xml2rfc/issues/1245
AUTH48 status of draft-ietf-lamps-header-protection-25 (RFC-to-be 9788)
This document is in AUTH48 state as of 2025-05-20. 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 |
|---|---|---|
| D. Gillmor | Y | 2025-06-17 |
| B. Hoeneisen | N | |
| A. Melnikov | Y | 2025-06-27 |
| AD - R. Danyliw | Y | 2025-07-30 |
** This document is part of Cluster C506, so may have additional holds before publication.
Notes:
2025-05-20: Questions sent to authors. 2025-05-21: Response received addressing some of the questions. 19 questions not yet addressed. 2025-05-22: Updated files sent w/ some follow-up questions. 2025-05-23: Received a few responses w/ additional updates. 2025-05-29: Updated files sent w/ a number of follow-up questions/comments. 2025-06-09: Sent files w/ inclusive language updates per discussion w/ AD. Resent follow-up questions/comments. 2025-06-11: Response received answering most questions. Updated files sent w/ remaining follow-up questions. 2025-06-12: XML files w/ additional updates received. 2025-06-16: XML files w/ additional updates received. Updated files sent. 2025-06-27: Reminder sent. 2025-07-10: Reminder sent. 2025-07-15: Additional updates received. 2025-07-16: Updated files sent. AD approval requested. Awaiting XML file w/ updated BOX DRAWINGS. 2025-07-17: XML file received. Updated files sent. *resolved*NOTE: There is an open issue on GitHub regarding the misalignment of non-ASCII characters in artwork in the PDF output: https://github.com/ietf-tools/xml2rfc/issues/1245
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.