Re: [bmwg] Murray Kucherawy's Discuss on draft-ietf-bmwg-ngfw-performance-13: (with DISCUSS and COMMENT)
Michael Richardson <[email protected]> Fri, 11 Feb 2022 09:06:06 -0500
| Newsgroups | gmane.ietf.general,gmane.ietf.bmwg |
|---|---|
| Message-ID | <656115.1644588366@dooku> |
Scott Bradner <[email protected]> wrote: > speaking as the editor of RFC 2119 > nice chart of how to misuse SHOULD but - imo - SHOULD is a MUST with an escape clause > I do not think it is useful to use SHOULD without specifically saying > what the escape clause is - > i.e. specifically say when its OK to not act as if it was a MUST I've gotten caught by this regularly. I don't want to write MUST because if feels rude to be so demanding, and I can envision *some* escape clause, I'm just not yet sure what it is yet. That's wrong on my part. > (if I had to do it all over again I would not have included SHOULD/SHOULD NOT) It's hard to imagine some other word that would allow for the escape clause. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
(application/pgp-signature, 658 B)
-----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEow/1qDVgAbWL2zxYcAKuwszYgEMFAmIGbU4ACgkQcAKuwszY gEPtNAwAxlVUIas2AiSRqT04jMbuMEHrcdgVACKoFOsTdHjvpE9gklePkkarBf8F jxIsAfQfLy/gkfHlLan6YM9k9Pwv5d9meLNdNs5Hf7eM6erzxXJHPTMaXumxweNh 4IR9aG/VZPA8+iBlzugC/QkjUmF4px3c8XiFEkVHKi7Z2p+FqBS7z/8TvxHt7xhI D6MlHMBXIrmWfaUxSRusNR25KSy2GccZIzrN+2gxbGr7Lhnte4CzKNYlJIJv0XQE S7xQfvHE69qgnJHLiLvKFt6ylJc04TzS25UWzrSMLKk6irvC/U+11VpCTpp8sCSu dGwEj5Daeg55wOWo/6tWI1PiXjL+fLSU6RDGn+sLHnIypnCoeN43jpO7lOmyx94Y hLV0p2jPAKcRcJ8Iob43er5b61ML1q6d5GPqh3iSpSZtQNqqiR3+VOkNUblsu0Zr ukrhge7p7bU+7QVovLxAriQK7OzAlmH9VRsif/lznG78rD9bX1N/E0gi5nJe7S5k kajyrv2m =YVNY -----END PGP SIGNATURE-----