AUTH48 status page for C508
Cluster Details
- draft-ietf-taps-arch-19.txt (RFC-to-be 9621) AUTH48
- draft-ietf-taps-interface-26.txt (RFC-to-be 9622) AUTH48*R
- draft-ietf-taps-impl-18.txt (RFC-to-be 9623) AUTH48*R
AUTH48 status of draft-ietf-taps-arch-19 (RFC-to-be 9621)
This document is in AUTH48 state as of 2024-11-18. 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 |
|---|---|---|
| T. Pauly, Ed. | N | |
| B. Trammell, Ed. | Y | 2024-12-06 |
| A. Brunstrom | N | |
| G. Fairhurst | N | |
| C. S. Perkins | Y | 2024-12-06 |
** This document is part of Cluster C508, so may have additional holds before publication.
Notes:
2024-11-18: document-specific questions sent to authors (cluster-wide questions will follow once all documents reach AUTH48). 2024-12-6: awaiting cluster-wide guidance only (all document-specific queries resolved). 2024-12-9: Only question 4 from cluster-wide queries remains outstanding (capitalization).
AUTH48 status of draft-ietf-taps-interface-26 (RFC-to-be 9622)
This document is in AUTH48 state as of 2024-11-18. 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. Trammell, Ed. | Y | 2024-12-06 |
| M. Welzl, Ed. | Y | 2024-12-05 |
| R. Enghardt | Y | 2024-12-04 |
| G. Fairhurst | Y | 2024-12-03 |
| M. Kuehlewind | Y | 2024-12-03 |
| C. S. Perkins | Y | 2024-12-06 |
| P. Tiesel | Y | 2024-12-03 |
| T. Pauly | N |
** This document is part of Cluster C508, so may have additional holds before publication.
Notes:
2024-11-18: document-specific questions sent to authors (cluster-wide questions will follow once all documents reach AUTH48). 2024-11-22: document-specific questions resolved except: #39, 41, and 42. 2024-12-03: document shepherd suggests a review of the document title and cluster-wide questions about capping and tt element use are sent to authors. 2024-12-04: title updated. 2024-12-09: cluster-wide question responses have yet to be incorporated. These overlap document-specific queries 39 and 41. Question 42 has been resolved. 2024-12-12: cluster-wide responses to capitalization have been resolved per M. Welzl's email.
AUTH48 status of draft-ietf-taps-impl-18 (RFC-to-be 9623)
This document is in AUTH48 state as of 2024-11-25. 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 |
|---|---|---|
| A. Brunstrom, Ed. | N | |
| T. Pauly, Ed. | N | |
| R. Enghardt | Y | 2024-12-09 |
| P. Tiesel | N | |
| M. Welzl | N |
** This document is part of Cluster C508, so may have additional holds before publication.
Notes:
2024-11-25: document-specific questions sent to authors (cluster-wide queries and further capitalization questions yet to come). 2024-12-03: cluster-wide questions sent. 2024-12-04: all document-specific queries resolved. 2024-12-09: cluster-wide queries regarding the use of the tt element and capitalization consistency are the only outstanding questions remaining. 2024-12-12: cluster-wide responses to capitalization have been resolved per M. Welzl's email.
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.