AUTH48 status page for C430

Cluster Details


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. N  
M. Nottingham, Ed. N  
J. Reschke, Ed. N  
AD - M. Kucherawy, F. Palombini Y 2021-12-30
IANA N  

** 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. ***** Note 1: We will request the following updates to the following IANA registries prior to publication. ) 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


AUTH48 status of draft-ietf-httpbis-cache-19 (RFC-to-be 9111)

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. N  
M. Nottingham, Ed. N  
J. Reschke, Ed. N  

** 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. 2021-12-23: Response received from M. Nottingham. All document-specific questions answered. 2022-01-05: Response and XML file received from J. Reschke. Feedback incorporated. 2022-01-06: Response received from M. Nottingham. 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. Document-specific and clusterwide feedback incorporated. 2022-01-11: M. Nottingham requested quote marks around directives to be removed. RFC-Editor asked if quote marks should be retained or removed for "public" and "private" directives. 2022-01-18: Reminded M. Nottingham to clarify if quote marks should be retained or removed for for "public" and "private" directives.


AUTH48 status of draft-ietf-httpbis-messaging-19 (RFC-to-be 9112)

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. N  
M. Nottingham, Ed. N  
J. Reschke, Ed. N  
IANA N  

** 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. 2022-01-05: Response and XML file received from J. Reschke. Feedback incorporated. 2022-01-06: J. Reschke requested edits to xref targets to be rolled back clusterwide. Edits rolled back. 2022-01-06: Feedback received from R. Fielding. M. Nottingham requested clusterwide changes. 2022-01-10: J. Reschke requested further cluster-wide changes. Document-specific and cluster-wide feedback incorporated. 2022-01-12: J. Reschke made updates to the Acknowledgements. 2022-01-13: J. Reschke added quote marks to media types. 2022-01-18: J. Reschke provided document-specific feedback for unanswered questions - changes were incorporated. 2022-01-20: J. Reschke requested further updates (mostly reverted text to the original form). Edits were made and an additional question was asked. 2022-01-21: Question was answered (removed hyphen from instances of "line break" and "line length"). **** Note 1: We will ask IANA to update the following entry in the "HTTP Transfer Coding Registry" (https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#transfer-coding) to match the other entries: OLD: "deflate" compressed data ([RFC1951]) inside the "zlib" data format ([RFC1950]) NEW: "deflate" compressed data [RFC1951] inside the "zlib" data format [RFC1950]


AUTH48 status of draft-ietf-quic-http-34 (RFC-to-be 9113)

This document is in AUTH48 state as of 2022-01-17. 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
M. Bishop, Ed. N  

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

Notes:

2022-01-18: Questions sent to the author.


AUTH48 status of draft-ietf-quic-qpack-21 (RFC-to-be 9114)

This document is in AUTH48 state as of 2022-01-17. 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. Krasic Y 2022-01-18
M. Bishop N  
A. Frindell, Ed. N  

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

Notes:

2022-01-18: Questions sent to the authors.


AUTH48-DONE status of draft-ietf-httpbis-expect-ct-08 (RFC-to-be 9163)

This document is in AUTH48 state as of 2021-10-11. 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
E. Stark Y 2021-11-08
AD: Francesca Palombini Y 2021-12-07

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

Notes:

2021-10-11: questions sent to author 2021-11-5: Reply received from author. 3 outstanding questions. 2021-11-7: Reply received no outstanding questions. Waiting on RFC 9162. 2021-11-24: AD approval required 2021-12-7: AD approval received. All approvals received. 2021-12-10: This document has moved from cluster C377 to C430. 2021-12-10: This document is waiting on companion documents RFC-to-be 9110 (draft-ietf-httpbis-semantics) and RFC-to-be 9111 (draft-ietf-httpbis-cache) to be published.


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.