OCM-IP: First draft of the I-D document.#370
Conversation
|
I'm going through the doc, at least as a first pass. I can also help with the CI, I have something already, will commit in this branch. |
|
I'm reading this as well I have some points that I will write in coming days in review |
If possible, I think it would be good to invert this flow. I.e. merge this PR, and them work on the content of the documents by making pr:s against it. Remeber that merging this PR makes no difference of the status of the document at the IETF, the call for adoption is what makes it an "official" document in the WG, and I think addressing all concerns as reviews against this PR will be much harder than the opposite, changing the document incrementally after it has been merged. |
The text in the document more or less assumed #365 were going to be merged. Instead we decided to close it in favor of this document, so the format of the JWT needed to be more thouroughly incorporated in the spec here.
Early on Matthias Kraus noticed that client_id and providerId could/should be the same.
glpatcern
left a comment
glpatcern
left a comment
There was a problem hiding this comment.
I think this is overall OK, let's indeed merge the PR and then we go through the details as part of the adoption process.
I would only explicitly add a paragraph in the introduction:
Co-authored-by: Giuseppe Lo Presti <giuseppe.lopresti@cern.ch>
3 participants
This PR adds the first draft of the Open Cloud Mesh Integration Protocol, and acknowledges Enrique's contribution in the main OCM spec.
I don't think it will be valuable to work too much on the text of this spec in this pr, rather focusing on IETF ID nits and such (if there are any), the IETF call for adoption procedure will safeguard that we do not introduce a bad document, and obviously we will have to evolve this document incrementally in pr's going forward.
I would appreciate assistance with the CI for building the xml document on pr.