AUTH48 status page for C321

Cluster Details


AUTH48-DONE status of draft-ietf-tls-rfc4492bis-17 (RFC-to-be 8422)

This document is in AUTH48 state as of 2018-07-02. 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
Y. Nir Y 2018-07-16
S. Josefsson Y 2018-07-17
M. Pegourie-Gonnard Y 2018-07-16

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

Notes:

2018-07-02: questions sent to authors. 2018-07-09: Reply received.


AUTH48-DONE status of draft-ietf-curdle-cms-ecdh-new-curves-10 (RFC-to-be 8418)

This document is in AUTH48 state as of 2018-06-29. 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. Housley Y 2018-07-16

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

Notes:

2018-06-29: document-specific questions and cluster-wide questions sent. 2018-06-30: responses received.


AUTH48-DONE status of draft-ietf-curdle-cms-eddsa-signatures-08 (RFC-to-be 8419)

This document is in AUTH48 state as of 2018-06-29. 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. Housley Y 2018-07-16

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

Notes:

2018-06-29: document-specific questions and cluster-wide questions sent. 2018-06-30: responses received.


AUTH48-DONE status of draft-schaad-curdle-oid-registry-03 (RFC-to-be 8411)

This document is in AUTH48 state as of 2018-06-04. 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
J. Schaad Y 2018-06-28
R. Andrews Y 2018-07-17

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

Notes:

2018-05-04: previously released to AUTH48 as RFC-to-be 8371. Authors requested this document be put on hold pending informative reference to draft-ietf-curdle-pkix. 2018-06-04: New number (8411) assigned. Waiting for draft-ietf-curdle-pkix to move to AUTH48. Please review reference to that draft prior to publication for title updates. 2018-06-29: cluster-wide questions sent (C321).


AUTH48 status of draft-ietf-ipsecme-eddsa-04 (RFC-to-be 8420)

This document is in AUTH48 state as of 2018-07-02. 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
Y. Nir Y 2018-07-18
ADs - B. Kaduk and E. Rescorla N  

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

Notes:

2018-07-02: questions sent to author. 2018-07-03: reply received. 2018-07-10: followup question for author; one item for AD to review/approve 2018-07-10: followup question for author addressed


AUTH48 status of draft-ietf-curdle-pkix-10 (RFC-to-be 8410)

This document is in AUTH48 state as of 2018-06-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
S. Josefsson N  
J. Schaad Y 2018-07-12
AD - B. Kaduk, E. Rescorla N  

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

Notes:

2018-06-25: questions sent to authors. 2018-06-28: responses received. 2018-06-29: cluster-wide questions sent (C321). 2018-07-03: AD approval requested. All applicable cluster-wide questions responded to and applied.


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.