AUTH48 status page for C365

Cluster Details


AUTH48 status of draft-ietf-ippm-metric-registry-24 (RFC-to-be 8911)

This document is in AUTH48 state as of 2020-09-22. 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. Bagnulo Y 2021-03-22
B. Claise Y 2021-03-19
P. Eardley Y 2021-03-22
A. Morton Y 2021-04-05
A. Akhter Y 2021-03-22
AD - Martin Duke Y 2021-03-30
IANA N  

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

Notes:

2020-09-22: questions sent to the authors. AD approval requested for a couple of items. 2020-10-30: worked though many questions; sent followup questions and added IANA to the discussion. Updated files posted. Ongoing discussion with Al and IANA. 2020-12-04: updated document posted for review; followup questions sent. Reminder sent to AD 2020-12-14: updated document posted for review 2021-01-07: updated document posted 2021-01-22: reminder sent 2021-02-17: reminder sent 2021-02-20: reply received 2021-03-05: updated files posted for review; AD asked to review the few items previously requested for approval plus all of the updates made since Feb 21 2021-03-30: AD approval received 2021-04-05: marked Al's approval after making updates based on his mail 4/2/2021. Verify that IANA has updated their registry per the following: [rfced] IANA update: b) Regarding this item, IANA indicates they will update this note when the Registry Entries are available. The Note for the Performance Metrics (registry) should read: "Summary category shown. Complete registry entries available in the URIs of each row."


AUTH48 status of draft-ietf-ippm-initial-registry-16 (RFC-to-be 8912)

This document is in AUTH48 state as of 2020-09-22. 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
A. Morton N  
M. Bagnulo N  
P. Eardley N  
K. D'Souza N  
AD - Martin Duke Y 2020-12-08

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

Notes:

2020-09-22: questions sent to the authors. AD approval requested for a couple of items. 2020-10-16: updates posted for review 2020-11-25: reminder sent 2020-12-4: reminders sent to author and Martin 2021-01-22: reminder sent 2021-02-17: reminder sent 2021-03-06: reminder sent 2021-04-05: updated files posted


AUTH48-DONE status of draft-ietf-ippm-twamp-yang-13 (RFC-to-be 8913)

This document is in AUTH48 state as of 2020-09-28. 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. Civil Y 2020-12-07
A. Morton Y 2020-12-09
R. Rahman Y 2020-12-07
M. Jethanandani Y 2020-12-07
K. Pentikousis, Ed. Y 2020-12-08
AD - Martin Duke Y 2020-12-01

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

Notes:

2020-09-28: questions sent to the authors. 2020-10-29: Asked for AD approval of updates to the Security Considerations section. 2020-12-01: AD approval received.


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.