CNCF Zero Trust Whitepaper

[mrsabath]

This is an attempt to convert the CNCF Zero Trust Whitepaper to Markdown format as requested by the community.
The original document: https://docs.google.com/document/d/10g2390JdCBXmSmzQ_EGHFWrg2JosPsXLaqXaGQ-B9NA/edit?usp=sharing

CNCF issue: #950

This is still a draft. I just started the conversion and it requires more work and cleanup

[netlify]

✅ Deploy Preview for tag-security ready!

Name	Link
🔨 Latest commit	9167688
🔍 Latest deploy log	https://app.netlify.com/sites/tag-security/deploys/66684029bda4d5000805f348
😎 Deploy Preview	https://deploy-preview-1229--tag-security.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[PushkarJ]

Thank you for opening the PR. @mrsabath as you make progress to make this "merge ready" please also address the linter, spellchecks and link checker output in the above CI checks

[y-tabata]

Is the recommendation for cipher suites as described in RFC9325 unnecessary?
It might be a good idea to just link to BCP195.

[mrsabath]

Thank you @y-tabata for your suggestions. The automation I used for converting from Doc to Markdown is not perfect and even though I did a lot of manual updates, there are still bugs that you were able to discover

[anvega]

Is this still a draft? This PR seems to contain work in progress. As per our established practices, we refrain from merging draft or incomplete work into the repository to avoid introducing outdated or inconsistent content. The existing markdown files you'll find represent the most recent, stable versions of their respective publications. So the work, whether in Markdown or PDF format, should be merged only after thorough review and completion.

During our chairs and tech leads discussion this morning, we acknowledged the need for comprehensive publishing guidelines to clarify the process and minimize confusion going forward. These guidelines will be documented and disseminated accordingly.

I appreciate the progress made so far on this effort. Given its current state, I recommend dedicating focused attention over the next two weeks to bring it to completion. Once finalized, we can proceed with merging the updates. To facilitate this, I will provide more detailed feedback on the tracking issue.

[mrsabath]

Is this still a draft? This PR seems to contain work in progress.

This work has been completed. We went through several stages and reviews. Several version of PDF were create. The latest one seems to be the most completed.

During our chairs and tech leads discussion this morning, we acknowledged the need for comprehensive publishing guidelines to clarify the process and minimize confusion going forward. These guidelines will be documented and disseminated accordingly.

I am in full agreement, and I would love to contribute to these guidelines, and provide my own suggestions and observations, as the process was long and challenging

I appreciate the progress made so far on this effort. Given its current state, I recommend dedicating focused attention over the next two weeks to bring it to completion. Once finalized, we can proceed with merging the updates. To facilitate this, I will provide more detailed feedback on the tracking issue.

Thank you for your feedback @anvega , let's close on the loose ends if any.

[eddie-knight]

I'm stepping in to help push this across the finish line, with the goal of completing all edits by Friday, June 21.

Community and TAG feedback is now being applied in a concerted push from myself and the lead authors.

No additional feedback will be accepted via this pull request.

[jkjell]

Closing due to #1395 replacing this.