-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design questions left for FIP #177
Comments
i. undergoing discussion, to be added in a different Draft PR later on. This Draft PR should contain ii. too (at least the part of ii. relating #176 ). iii. and iv. added to the following Draft PR v. to be tracked by @Stebalien vi. to be discussed, but updates made to the same Draft PR as iii. and iv. |
For ii. what is the state of the @Stebalien @Kubuxu ? |
Talked to @Kubuxu; let's wait until early next week and see if @Stebalien is back; if not, @Kubuxu will pick up specifying 2 (FDEP) and 5 (ECTipset format) for the FIP. |
i. is optimistically submitted to a dedicated Draft PR but discussion is still open. |
I am not sure about task No. 6 Should the FIP go as far as documenting when to start an instance or pull certificates? They seem to be more on the implementation side than algorithmic part. Perhaps a paragraph on suggestions would suffice if the concensus is that the FIP should include them. Apart from that I think the FIP could move to last call, unless there is something that I have missed. @anorth thoughts? |
Yeah I think we're almost done with these design questions. I think it would be appropriate for the FIP to mention something about when to pull certificates, although I agree the policy is largely up to the client. I would still be a bit hesitant to say the FIP is ready for last call right now, though. Things are still changing and we have yet to do a pass pushing implementation things back into the FIP - we need to be about done with implementation for that. We also have audits to review and I suspect we might find something there too. |
Left design questions, only to be marked as done once they are in a PR for the FIP at least.
Tasks
The text was updated successfully, but these errors were encountered: