Hi, Sri,
(Thanks to everyone for the quick responses - I can still remember the
review without having to re-read it ;-)
If the request is rejected with a specific reason, there is not point
for the requester to continue to send the messages for the exact same
service. Its ok to resend the message when some thing changes. Ex: An
administrative action allowing the user for that service.
So, the "SHOULD NOT" is with the goal to avoid unnecessary messaging.
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,
Spencer
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
