RE: [sarif] SHOULD => SHALL in "Security implications"

From
Michael Fanning <>
Date
2018-01-11T15:32:54+00:00
ID
Thread
RE: [sarif] SHOULD => SHALL in "Security implications"
Thanks, Larry. I agree this is the right thing to do.

 

Nice catch, Jim. Security is important. 
😊

 

Michael

 

From:  [mailto:]
On Behalf Of Larry Golding (Comcast)

Sent: Wednesday, January 10, 2018 1:31 PM

To: 

Subject: [sarif] SHOULD => SHALL in "Security implications"

 

In this morning’s meeting, Jim moved, and it was agreed, to replace “SHOULD NOT” with “SHALL NOT” in one of the bullet points in the “Security implications” section. Upon re-reading that section, I think it best to replace
all SHOULDs with SHALLs, and all SHOULD NOTs with SHALL NOTs, in that section.

 

I’m going to make those changes in the Provisional Draft I’m now working on. If anyone please disagrees, please respond to this message, and I will file a bug in the GitHub repo so we can discuss it further.

 

Thanks,

Larry