Hi Spencer,
On Mon, 18 May 2009, Spencer Dawkins wrote:
Otherwise, the requester will recv the same error code.
I'm sorry, I'm not asking the question clearly - I'm asking why these SHOULD
NOTs aren't MUST NOTs. Is there a reason why the requestor would resend the
messages for the same service, without changing anything?
If there's a reason, SHOULD NOT would be appropriate. If there's not a
reason, perhaps MUST NOTs would be more appropriate.
Thanks for the clarification.
MUST NOT, might be too strong for this. For what ever reasons,
a given implementation might prefer to resend after some time.
We really need not even specify this, but for completeness we
just put this with "SHOULD NOT".
Sri
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
