AUTH48 status page for C306

Cluster Details


AUTH48-DONE status of draft-ietf-sidr-bgpsec-ops-16 (RFC-to-be 8207)

This document is in AUTH48 state as of 2017-06-14. 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. Bush Y 2017-07-25
AD - A. Retana Y 2017-06-19

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

Notes:

2017-06-14: questions sent to authors and ADs and cluster-wide questions sent as well. 2017-06-15 reply received (document-specific questions addressed; cluster-wide questions still open) 2017-06-15 received AD approval of change in question #4 2017-06-15 requested AD approval for Section 3 change 2017-06-19 received AD approval for Section 3 change


AUTH48-DONE status of draft-ietf-sidr-bgpsec-pki-profiles-21 (RFC-to-be 8209)

This document is in AUTH48 state as of 2017-06-14. 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. Reynolds Y 2017-07-06
S. Turner Y 2017-07-05
S. Kent Y 2017-06-21
AD: Alvaro Retana Y 2017-06-20

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

Notes:

2017-06-14: questions sent to authors and cluster-wide questions sent. 2017-06-20: Requested AD approval for (1) update to Section 3.1.3.2 and (2) addition of RFC 6481 to the list of Normative References.


AUTH48-DONE status of draft-ietf-sidr-bgpsec-protocol-23 (RFC-to-be 8205)

This document is in AUTH48 state as of 2017-06-14. 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. Lepinski, Ed. Y 2017-09-21
K. Sriram, Ed. Y 2017-09-21
AD - A. Retana Y 2017-09-21

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

Notes:

2017-06-14: Questions sent to authors. Clusterwide questions exist. 2017-06-22: request AD approval for changes in the acks/contribs sections. 2017-06-29: Initial approval from Kotikalapudi Sriram. 2017-06-30: Initial approval from Matt Lepinski. 2017-07-12: AD approval for updates to Figures 8 and 9 received. Approval of updates to the Acknowledgements and Contributors sections is still pending. 2017-07-14: AD approval received re. updates to the Acknowledgements and Contributors sections. Asked for approval of newly updated text following Figures 8 and 9. 2017-07-17: AD approval received re. newly updated text following Figures 8 and 9. 2017-07-26: Moved from AUTH48-DONE back to AUTH48; AD approval is pending until final text is decided upon (re. question raised by Sam Weiler about Authors and Contributors lists). 2017-09-18: AD approval received. 2017-09-21: Approval from Matt Lepinski re. updated Contributors section. 2017-09-21: Approval from Kotikalapudi Sriram re. updated Contributors section. 2017-09-21: AD approval for additional update to Acknowledgements section received.


AUTH48-DONE status of draft-ietf-sidr-adverse-actions-04 (RFC-to-be 8211)

This document is in AUTH48 state as of 2017-06-14. 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. Kent Y 2017-07-03
D. Ma Y 2017-06-14

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

Notes:

2017-06-14: Question sent to the authors. Cluster questions apply as well. 2017:06-14: Reply received (document-specific questions addressed; cluster-wide questions still open)


AUTH48 status of draft-ietf-sidr-as-migration-06 (RFC-to-be 8206)

This document is in AUTH48 state as of 2017-06-16. 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
W. George Y 2017-06-28
S. Murphy N  
AD - A. Retana Y 2017-09-11

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

Notes:

2017-06-16: questions sent to authors 2017-06-26: reply received 2017-06-27: followup question sent regarding question #3 2017-06-28: response for question #3 received 2017-07-12: authors and AD discussing discrepancy with examples 2017-09-11: reply received with reworked examples


AUTH48-DONE status of draft-ietf-sidr-rpki-rtr-rfc6810-bis-09 (RFC-to-be 8210)

This document is in AUTH48 state as of 2017-06-14. 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. Bush Y 2017-06-30
R. Austein Y 2017-06-30

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

Notes:

2017-06-14: Question sent to the authors. Cluster questions apply as well.


AUTH48-DONE status of draft-ietf-sidr-bgpsec-algs-18 (RFC-to-be 8208)

This document is in AUTH48 state as of 2017-06-14. 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. Turner Y 2017-06-16
O. Borchert Y 2017-06-16

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

Notes:

2017-06-14: Question sent to the authors. Cluster questions apply as well.


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.



Search RFCs
Advanced Search
×