Git Product home page Git Product logo

Comments (11)

buidav avatar buidav commented on September 23, 2024 2

@adhilto Can you please provide a reference to a publicly available document that defines the SHALL vs. SHOULD? Also do we have other terms that need definition such as MAY? If yes, can you provide the language for that too. Thank u!

Had a blast from the past to that 2 hour 6 a.m meeting last year.
RFC2119 was what was brought up as our source for the SHALL/SHOULD
https://datatracker.ietf.org/doc/html/rfc2119

from scubagear.

buidav avatar buidav commented on September 23, 2024 2

@adhilto Can you please provide a reference to a publicly available document that defines the SHALL vs. SHOULD? Also do we have other terms that need definition such as MAY? If yes, can you provide the language for that too. Thank u!

Had a blast from the past to that 2 hour 6 a.m meeting last year. RFC2119 was what was brought up as our source for the SHALL/SHOULD https://datatracker.ietf.org/doc/html/rfc2119

The quote below from the link is very relevant to this issue ^^ " Authors who follow these guidelines should incorporate this phrase near the beginning of their document:

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
  NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
  "OPTIONAL" in this document are to be interpreted as described in
  [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).

"

Alden posted this elsewhere. Reposting

For April Fools, we should replace the link to RFC 2119 with RFC 6919 :)
RFC6919

from scubagear.

buidav avatar buidav commented on September 23, 2024 1

@adhilto Can you please provide a reference to a publicly available document that defines the SHALL vs. SHOULD? Also do we have other terms that need definition such as MAY? If yes, can you provide the language for that too. Thank u!

Had a blast from the past to that 2 hour 6 a.m meeting last year. RFC2119 was what was brought up as our source for the SHALL/SHOULD https://datatracker.ietf.org/doc/html/rfc2119

The quote below from the link is very relevant to this issue ^^
"
Authors who follow these guidelines
should incorporate this phrase near the beginning of their document:

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
  NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
  "OPTIONAL" in this document are to be interpreted as described in
  [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).

"

from scubagear.

tkol2022 avatar tkol2022 commented on September 23, 2024

@gdasher Can you kindly provide definitions for SHALL versus SHOULD that you would like to include in the baseline? Also, where would you like the reference to the hybrid solutions document, what should that say and what URL should that reference?
Thanks!

from scubagear.

tkol2022 avatar tkol2022 commented on September 23, 2024

@adhilto Can you please provide a reference to a publicly available document that defines the SHALL vs. SHOULD? Also do we have other terms that need definition such as MAY? If yes, can you provide the language for that too. Thank u!

from scubagear.

adhilto avatar adhilto commented on September 23, 2024

Or did they mean SHOULD incorporate? 😄

from scubagear.

tkol2022 avatar tkol2022 commented on September 23, 2024

@gdasher Can you please provide a sentence or two on what you want included regarding the Hybrid Identity document?

Do you want that at the top of the AAD baseline? In other baselines as well or just AAD?

from scubagear.

tkol2022 avatar tkol2022 commented on September 23, 2024

@gdasher pinging again. See previous comment.

from scubagear.

ahuynhMITRE avatar ahuynhMITRE commented on September 23, 2024

updated the front-matter and acknowledgements, also included the link to RFC 2119.

from scubagear.

ahuynhMITRE avatar ahuynhMITRE commented on September 23, 2024

current status is that the front-matter and acknowledgements have been submitted to CISA for review!

from scubagear.

ahuynhMITRE avatar ahuynhMITRE commented on September 23, 2024

front matter and acknowledgements have been approved by CISA and updated in the example markdown

from scubagear.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.