RE: [Sip] Strict, Semi-Strict and Loose mode in RPH

James said,

>[JG]I am not as concerned about this case (valid namespace.valid value -
>just not authorized).

I would think this is of concern - as anyone (literally) can be in this
group.

I was thinking that it was of less concern because it is someone who
already knows the valid namespace and value.

But you are right, if it is someone who is randomly or systematically
trying namespace/value combinations, we just told them "you got a hit".
So I take it back about being less concerned.

Janet

----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

RE: [Sip] Strict, Semi-Strict and Loose mode in RPH - not a good fit for ets and wps