[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Comments on draft-ietf-ipsec-ike-01.txt (long)
Okay, how about "authoritative policy control is important to administrators,"
for a
"valid reason". Otherwise, I'd argue to reduce it to a MAY.
-Rob
> -----Original Message-----
> From: owner-ipsec@lists.tislabs.com
> [mailto:owner-ipsec@lists.tislabs.com]On Behalf Of Michael C. Richardson
> Sent: Monday, June 14, 1999 3:10 PM
> To: ipsec@lists.tislabs.com
> Subject: Re: Comments on draft-ietf-ipsec-ike-01.txt (long)
>
>
>
> >>>>> "Rob" == Rob Adams <adams@cisco.com> writes:
> Rob> Changing the wording to a MUST forces people to accept key lengths
> Rob> they may not want, for whatever reason. It also forces
> Rob> implementations wishing to provide their customers with
> Rob> authoritative policy control to "break" with the standard.
>
> Rob> I firmly believe the wording must remain a SHOULD. I also would not
> Rob> like to see another globally required policy knob that makes people
> Rob> choose between "I meant what I said" and "You figure it out."
>
> We must all recall that SHOULD means:
>
> 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there
> may exist valid reasons in particular circumstances to ignore a
> particular item, but the full implications must be understood and
> carefully weighed before choosing a different course.
>
> Emphasis on "valid reasons".
>
> :!mcr!: | Network and security consulting/contract programming
> Michael Richardson | ...working from my front lawn with a long cord...
> Personal:
> http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html
> Corporate: http://www.sandelman.ottawa.on.ca/SSW/
> ON HUMILITY: To err is human, to moo bovine.
>
>
>
Follow-Ups:
References: