AUTH48 status page for C373

Cluster Details


AUTH48 status of draft-ietf-dnsop-terminology-bis-14 (RFC-to-be 8499)

This document is in AUTH48 state as of 2018-11-08. 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
P. Hoffman N  
A. Sullivan N  
K. Fujiwara N  

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

Notes:

2018-11-08: questions sent to authors.


AUTH48-DONE status of draft-ietf-dnsop-refuse-any-07 (RFC-to-be 8482)

This document is in AUTH48 state as of 2018-10-15. 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
AD - W. Kumari Y 2018-10-18
J. Abley Y 2018-10-31
O. Gudmundsson Y 2018-10-31
M. Majkowski Y 2018-10-31
E. Hunt Y 2018-10-31

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

Notes:

*Note: This document should be published at the same time as draft-ietf-dnsop-terminology-bis (RFC-to-be 8499). RFC-to-be 8499 is currently in AUTH48 state. See https://www.rfc-editor.org/auth48/rfc8499. 2018-10-15: questions sent to authors 2018-10-17: all questions addressed 2018-10-18: sent three followup questions 2018-10-18: requested AD approval (Note: AD already approved inclusion of normative 'SHOULD' in Section 4.2) 2018-10-18: AD approval received 2018-10-25: sent additional followup question 2018-10-25: followup questions addressed 2018-10-30: 3 additional questions sent 2018-10-30: all questions addressed


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.