It's a communication problem. If you want your audience to understand exactly what you're saying, and implement along very specific lines, you need to tell them in a way they understand. Personally I prefer a quieter approach, but I've been told that these days one MUST use MUST or implementors just won't get it. "Huh, that's a requirement? But you didn't say MUST." I suggest turning this thread into a survey, and finding out how people who actually write code look for in order to know what's required.
- Re: I'm struggling with 2219 language again Thomas Narten
- Re: I'm struggling with 2219 language again ned+ietf
- Re: I'm struggling with 2219 language aga... Pete Resnick
- Re: I'm struggling with 2219 language... ned+ietf
- Re: I'm struggling with 2219 lan... C. M. Heard
- Compliance to a protocol descrip... Robin Uyeshiro
- Re: I'm struggling with 2219 language again Lou Berger
- Re: I'm struggling with 2219 language again Hector Santos
- RE: I'm struggling with 2219 language again Adrian Farrel
- Re: I'm struggling with 2219 language again Scott Brim
- Re: I'm struggling with 2219 language again Peter Saint-Andre
- Re: I'm struggling with 2219 language again Richard Barnes
- Re: I'm struggling with 2219 language aga... Ben Campbell
- Re: I'm struggling with 2219 language again Mark Nottingham
- Re: I'm struggling with 2219 language again Hector Santos
- A proposal for a scientific approach to this question ... Marc Petit-Huguenin
- Re: A proposal for a scientific approach to this ... Dick Franks
- Re: A proposal for a scientific approach to t... John Day
- Re: A proposal for a scientific approach to t... Donald Eastlake
