I think you have hit the root cause on the head.
I would also offer that by removing the crutch, or raising the bar to using the
crutch, will help alleviate the root cause.
On Aug 30, 2011, at 11:44 AM, Keith Moore wrote:
e.g. For the specific case of optional features that must be negotiated, I
don't think that SHOULD is the problem. Rather I think that optional
features are too common. That's not to say that optional features and
feature negotiation are never useful, particularly when extending a protocol
that is already well-established in the field. But if making features
optional is seen by WGs as a way to avoid making hard decisions about what is
required to interoperate, that really is a problem. It just doesn't have
anything to do with SHOULD.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf