AUTH48 status page for C350

Cluster Details


AUTH48 status of draft-ietf-tsvwg-ecn-encap-guidelines-22 (RFC-to-be 9599)

This document is in AUTH48 state as of 2024-06-10. 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
B. Briscoe Y 2024-07-12
J. Kaippallimalil Y 2024-06-18
AD - Zaheduzzaman Sarker N  

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

Notes:

2024-06-10: Questions sent to authors. 2024-06-18: Reminder email sent. 2024-07-05: Posted updated files. Two followup items sent. 2024-07-10: Posted updated files. One followup item sent. 2024-07-12: AD email sent. 2024-07-22: Reminder AD email sent.


AUTH48 status of draft-ietf-trill-ecn-support-07 (RFC-to-be 9600)

This document is in AUTH48 state as of 2024-06-10. 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. Eastlake 3rd Y 2024-06-20
B. Briscoe Y 2024-06-28
AD (Alia Atlas for the Routing ADs) N  

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

Notes:

2024-06-10: Questions sent to authors. 2024-06-17: Reminder/Questions resent to correct mailing lists. 2024-06-18: Response received. 2024-06-19: 1 followup question sent. 2024-06-19: Response received. 2024-06-20: All questions addressed. Posted updated files. 2024-06-25: Posted updated files. Sent 1 followup comment. 2024-07-01: Sent AD followup item. 2024-07-08: Sent AD reminder. 2024-07-15: Sent AD reminder. 2024-07-15: Routing ADs agreed to have Alia Atlas review and approve changes for the ADs because of the history of this document. Alia was the AD when this document was approved in 2018. 2024-07-22: Sent AD reminder.


AUTH48-DONE status of draft-ietf-tsvwg-rfc6040update-shim-23 (RFC-to-be 9601)

This document is in AUTH48 state as of 2024-06-10. 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
B. Briscoe Y 2024-07-12
AD - Zaheduzzaman Sarker Y 2024-07-22

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

Notes:

2024-06-10: Questions sent to the author. 2024-06-18: Reminder email sent. 2024-06-25: Response received. 2024-07-02: All questions addressed. Posted updated files. Sent 2 followup comments. 2024-07-09: Author sent updated files with edits. 2024-07-09: Posted updated files. 2024-07-12: Sent AD items. 2024-07-22: Sent AD reminder.


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.



Advanced Search