SovereignCloudStack
#675 - Node to Node encryption
generally LGTM, but I want to reread it a second time, as it's quite a long document, at the very least there are some spelling mistakes lurking in there imho, but I didn't want to comment on minor errors before actually having read the whole thing first.
Will provide more feedback, hopefully tomorrow. Thanks for working on this!
@artificial-intelligence would you like to provide more feedback on this?
@mbuechse @artificial-intelligence can we merge this one or do you have some further comments/discussion points?
What is the reason for putting it into the Drafts folder? Why was it merged in "Proposal" state? If it's a decision record that has been accepted by the corresponding team (I guess Team IaaS in this case), then the status field should be Draft, the file should be renamed to, say, scs-0122-v1-node-to-node-encryption.md and be put under Standards.
What is the reason for putting it into the Drafts folder? Why was it merged in "Proposal" state? If it's a decision record that has been accepted by the corresponding team (I guess Team IaaS in this case), then the
statusfield should beDraft, the file should be renamed to, say,scs-0122-v1-node-to-node-encryption.mdand be put underStandards.
@mbuechse It makes sense. We will rename it and put it under the Standards. Before that, we will ask team IaaS for final validation. Thanks for bringing this up!
