AUTH48 status of draft-ietf-dhc-dhcpv4-over-dhcpv6-ra-06 (RFC-to-be 9928)
This document is in AUTH48 state as of 2026-02-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 |
|---|---|---|
| C. Porfiri (content) | Y | 2026-02-26 |
| S. Krishnan (content) | Y | 2026-03-05 |
| J. Arkko (content) | N | |
| M. Kühlewind (content) | Y | 2026-02-23 |
| C. Porfiri (format) | N | |
| S. Krishnan (format) | N | |
| J. Arkko (format) | N | |
| M. Kühlewind (format) | N |
Notes:
2026-02-18: Sent questions to authors. 2026-02-23: Received updated markdown file. All questions addressed. One author approval received. 2026-02-25: Sent updated files. 2026-02-26: Received another author approval. Awaiting two more content approvals before conversion to RFCXML. 2026-03-05: Received another author content approval. Awaiting one final author content approval before converting to RFCXML. NOTE: This document was submitted and edited in markdown as part of the RPC pilot test, and thus requires two rounds of approvals from each author. For more information, please see: https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_instructions_completing_auth48_using_kramdown
Instructions to author(s):
Please see the AUTH48 notification email from the RFC Editor that contains a link to the edited document and other information. To send your approval or changes, please Reply All to that message.
When all approvals have been received, publication is imminent. Upon publication as an RFC, this AUTH48 status page will no longer be available.