AUTH48 status page for C396

Cluster Details


AUTH48 status of draft-ietf-tram-stunbis-21 (RFC-to-be 8489)

This document is in AUTH48 state as of 2019-07-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
M. Petit-Huguenin N  
G. Salgueiro N  
J. Rosenberg N  
D. Wing N  
R. Mahy N  
P. Matthews N  
IANA N  
ADs - M. Westerlund Y 2019-09-26

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

Notes:

2019-07-29: questions sent to authors. 2019-08-14: reply received. 2019-08-22: four followup questions sent to authors; requested AD approval for 4 items. 2019-08-22: followup questions #1 and #2 addressed; #3 and #4 still open 2019-08-28: AD approved 4 items 2019-08-29: updated document per author email of 2019-08-26. Sent 3 followup questions (numbered a, b, c); followup questions #3 and #4 previously sent are also still open. 2019-08-29: Requested AD approval for 5 additional items 2019-08-30: followup questions numbered a, b, and c are closed. followup questions #3 and #4 are still open. 2019-08-30: AD approved 5 additional items, but would like to run these changes and another potential change proposed by Marc by the working group. We will wait to mark AD approval until the working group review is complete. 2019-09-23: requested AD approval for 3 additional items; all questions now closed (#3 and #4 were open but addressed by Marc). 2019-09-26: AD approval received but still missing the sentences about motivation for why OpaqueString profile is being used. Authors discussing concerns raised by Rohan. 2019-10-29: AD put document on hold due to lack of moving the registration rules forward from RFC 5389. Also, doc is missing explanation for choice of OpaqueString. Note: Prior to publication, the RPC will request that IANA update the registry to match the document.


AUTH48 status of draft-ietf-tram-turnbis-29 (RFC-to-be 8656)

This document is in AUTH48 state as of 2019-12-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
T. Reddy, Ed. Y 2019-12-07
A. Johnston, Ed. Y 2019-12-08
P. Matthews N  
J. Rosenberg N  

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

Notes:

2019-12-02: questions sent to the authors. 2019-12-03: Reply received. One outstanding question. 2019-12-06: No outstanding questions.


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.