AUTH48 status page for C350
Cluster Details
- draft-ietf-tsvwg-l4s-arch-20.txt RFC9330 PUB
- draft-ietf-tsvwg-ecn-l4s-id-29.txt RFC9331 PUB
- draft-ietf-tsvwg-aqm-dualq-coupled-25.txt RFC9332 PUB
- draft-ietf-tsvwg-ecn-encap-guidelines-22.txt RFC9599 PUB
- draft-ietf-trill-ecn-support-07.txt RFC9600 PUB
- draft-ietf-tsvwg-rfc6040update-shim-23.txt RFC9601 PUB
- draft-ietf-tsvwg-nqb-33.txt (RFC-to-be 9956) AUTH48
- draft-briscoe-docsis-q-protection-07.txt (RFC-to-be 9957) AUTH48*R
AUTH48 status of draft-ietf-tsvwg-nqb-33 (RFC-to-be 9956)
This document is in AUTH48 state as of 2026-04-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 |
|---|---|---|
| G. White | N | |
| T. Fossati | N | |
| R. Geib | N |
** This document is part of Cluster C350, so may have additional holds before publication.
Notes:
2026-04-06: questions sent to authors.
AUTH48 status of draft-briscoe-docsis-q-protection-07 (RFC-to-be 9957)
This document is in AUTH48 state as of 2026-04-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 |
|---|---|---|
| B. Briscoe, Ed. | N | |
| G. White | N |
** This document is part of Cluster C350, so may have additional holds before publication.
Notes:
2026-04-06: questions sent to authors. 2026-04-08: responses received. 2026-04-10: follow-up questions / outstanding issues list sent. 2026-04-16: 3 issues remain (copyright issue, URLs to CableLabs specs, trademark symbol in the title) that G. White will report back on.
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.