On 08/30/2011 06:07 PM, Bill McQuillan wrote:
How about recommending SHOULD ... BECAUSE to encourage the author
to justify the SHOULD.
+1
Although saying something like this should do: "If there's a SHOULD
clause in the document, the document MUST provide background and
rationale for making the behaviour optional.
For an implementor it's often pretty hard to decide whether to implement
functionality marked as SHOULD given that he has zero context and no
idea whether the reason he has for not implementing the feature is at
all in line with RFC authors' intentions.
Martin
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf