Hi Scott, Thanks for your quick feedback. Addison already replied that he was willing to work through and replace or uppercase the pseudo-imperatives. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald at sharplabs.com > -----Original Message----- > From: Scott Hollenbeck [mailto:sah at 428cobrajet.net] > Sent: Wednesday, June 08, 2005 6:32 PM > To: 'McDonald, Ira'; ltru at ietf.org > Subject: RE: [Ltru] Confusing conformance language > > > > -----Original Message----- > > From: McDonald, Ira [mailto:imcdonald at sharplabs.com] > > Sent: Wednesday, June 08, 2005 11:42 AM > > To: ltru at ietf.org > > Subject: [Ltru] Confusing conformance language > > > > Hi, > > > > It's pretty much best practice in RFCs to avoid entirely the > > use of lowercase 'must' or 'should' as some dubious > > distinction from conformance imperatives 'MUST' or 'SHOULD' > > (RFC 2119 terms). > > > > The lowercase term 'must' appeared 28 times and the lowercase > > term 'should' appeared 31 times in the latest Registry > > version <draft-ietf-ltru-registry-03.txt>. The uppercase > term 'MUST' > > appeared 88 times and the uppercase term 'SHOULD' appeared > > 21 times. > > > > While I realize it would be a pain to disentangle, replace, > > and disambiguate these lowercase uses, this is low-hanging > > fruit for an IETF last call objection. And it would cause > > too much rewriting to be handled as directives to the RFC > > Editor, in all likelihood. > > > > Randy - do you have an opinion here? > > I do, and I'd prefer that the lower case forms NOT be used to > avoid just the > sort of potential confusion described above. The IESG > doesn't seem to deal > with it consistently, either, so it's best to avoid the issue > completely if > at all possible. > > -Scott- > _______________________________________________ Ltru mailing list Ltru at lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.