![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
James and Ken,
Quite interesting remarks you have made. I agree to Ken's syllogistics and I love James' consideration on corporeal world practice.
Let's begin at the beginning. What is the requirement level for exceptions of "MUST NOTs" ?
First, in RFC terms, MAY has the equal value to MAY NOT. In fact, there is no definition on "MAY NOT" in RFC 2119.
Exceptions to MUST NOTs means there are cases which are not prohibited. The semantics gives me the implication that the appripriate requirement level is placed between "SHOULD NOT" and "MAY".
Most specs have bugs.
Harald
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.