AUTH48 status of draft-ietf-httpbis-semantics-19 (RFC-to-be 9110)
This document is in AUTH48 state as of 2021-12-23. 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 |
|---|---|---|
| R. Fielding, Ed. | Y | 2022-04-21 |
| M. Nottingham, Ed. | Y | 2022-04-22 |
| J. Reschke, Ed. | Y | 2022-04-22 |
| AD - M. Kucherawy, F. Palombini | Y | 2022-04-01 |
| IANA | Y | 2022-04-25 |
** This document is part of Cluster C430, so may have additional holds before publication.
Notes:
2021-12-23: Document-specific and cluster-wide questions sent to authors and ADs. 2021-12-23: Response to cluster-wide questions received from M. Nottingham. 2021-12-24: Response to cluster-wide questions received from J. Reschke. 2021-12-29: Document-specific response received from J. Reschke. 2021-12-30: AD approval received from F. Palombini. 2022-01-02: Document-specific response received from J. Reschke. 2022-01-03: Followup questions sent. 2022-01-04: Response received from J. Reschke. 2022-01-05: XML file received from J. Reschke. Followup question sent. Feedback incorporated. 2022-01-06: J. Reschke requested edits to xref targets to be rolled back clusterwide. Edits rolled back. M. Nottingham requested clusterwide changes. 2022-01-10: J. Reschke requested further clusterwide changes. Feedback incorporated. 2022-01-21: Feedback received from R. Fielding. 2022-01-24: Feedback received from J. Reschke. 2022-01-25: Feedback incorporated. 2022-01-31: Feedback on formatting received from M. Nottingham and incorporated. Followup question sent. 2022-02-10: Feedback and XML file received from J. Reschke and incorporated. 2022-02-14: Updated XML file received from J. Reschke. 2022-02-15: XML file incorporated. 2022-02-16: Updated XML file received from J. Reschke and incorporated. 2022-02-17: Updated XML file received from J. Reschke and incorporated. AD approval requested. Second updated XML file received from J. Reschke. 2022-02-22: Updated XML file incorporated. Approval received from F. Palombini. 2022-03-04: Updated XML file answering some document-specific questions received from J. Reschke, more updates forthcoming. 2022-03-07: Updates incorporated. 2022-03-08: Updated XML file answering some document-specific questions received from J. Reschke, more updates forthcoming. Updates incorporated. 2022-03-09: Updated XML file answering some document-specific questions received from J. Reschke, more updates forthcoming. Updates incorporated. 2022-03-11: Updated XML file answering some document-specific questions received from J. Reschke, more updates forthcoming. Updates incorporated. 2022-03-13: Updated XML file with technical changes received from J. Reschke. 2022-03-14: Updates incorporated. AD approval requested regarding changes made to clarify range validity/satisfiability. 2022-03-16: Updated XML file with editorial changes received from J. Reschke. 2022-03-29: Updated XML file with reference updates received from J. Reschke. 2022-03-30: Approval received from F. Palombini regarding changes made to clarify range validity/satisfiability. 2022-03-31: XML file updates from 3-16 and 3-29 incorporated. AD approval requested regarding moving [HTTP/2] reference from RFC 7540 to RFC 9113. 2022-04-01: AD approval of [HTTP/2] reference change received. 2022-04-04: Update to xrefs requested by M. Nottingham. 2022-04-05: Update incorporated. 2022-04-14: XML file received from J. Reschke and updates incorporated. 2022-04-18: Feedback received from R. Fielding and incorporated. 2022-04-21: Approval received from R. Fielding. 2022-04-22: Approval received from J. Reschke and M. Nottingham. Requested IANA to make updates. 2022-04-25: IANA updates completed [IANA #1229793]: ) On the "Hypertext Transfer Protocol (HTTP) Upgrade Token Registry" (https://www.iana.org/assignments/http-upgrade-tokens/): OLD: Note Please see [RFC7230], Section 8.6.1 for details regarding token registrations. ... any DIGIT.DIGIT (e.g, "2.0") ANY DIGIT.DIGIT (e.g.. "1.2") New: Note Please see Section 16.7 of [RFC9110] for details regarding token registrations. ... any DIGIT.DIGIT (e.g., "2.0") ANY DIGIT.DIGIT (e.g., "1.2") ) On the Media Type template (https://www.iana.org/assignments/media-types/multipart/byteranges) OLD: HTTP components supporting multiple ranges in a single request. New: HTTP components supporting multiple ranges in a single request ) On the "Media Types" registry (https://www.iana.org/assignments/media-types/media-types.xhtml), remove the period from the following (not included in this document): OLD: Expert Review for Vendor and Personal Trees. New: Expert Review for Vendor and Personal Trees 2022-04-27: Authors requested waiting for RFC 9114 (draft-ietf-quic-http), an informative reference, to be published. Document was updated. 2022-04-28: R. Fielding requested updates to table headings. 2022-04-29: Feedback incorporated.
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.
