[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [security-services] Erratum: MAY NOT->MUST NOT
Eve - I definitely agree to the changes as recommended. I will however, add this to the errata document so that we have a record of it and can formally dispose of it during our next call. Thanks, Jahan ---------------- Jahan Moreh Chief Security Architect 310.286.3070 > -----Original Message----- > From: Eve L. Maler [mailto:eve.maler@sun.com] > Sent: Friday, April 04, 2003 9:52 AM > To: 'security-services@lists.oasis-open.org' > Subject: Re: [security-services] Erratum: MAY NOT->MUST NOT > > > Oops, forgot to mention that the line numbers referenced below are from > the 1.0 Standard version, not the latest 1.1 draft. > > Eve L. Maler wrote: > > There are two instances of the phrase "MAY NOT" in the core spec (lines > > 1050 and 1258). This phrase is not actually defined by RFC 2199; I > > believe what was meant was "MUST NOT". For this reason, and because > > "may not" is a classic ambiguous phrase in technical documentation > > ("don't do this", as opposed to "you may or may not do this"), I > > recommend that we change it to "MUST NOT" in both locations. > > > > I did not find any other occurrences of this uppercase phrase in the > > other documents. > > > > Eve > > -- > Eve Maler +1 781 442 3190 > Sun Microsystems cell +1 781 354 9441 > Web Technologies and Standards eve.maler @ sun.com >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]