[Sip] More general question on S-S-L mode in RPH

[Janet P Gunn <[e-mail]>]

What do the S-S-L modes apply to?

In this case, I am just looking just at the dimension of which messages are
accepted, and which are rejected- ignoring the other features which have
been associated with the mode.

4.3.2 says that "mode" is a characteristic of the SIP element:

"When handling requests with unknown namespaces or priority values,
   elements can operate in one of three modes, "strict", "semi-strict"
   and "loose"."

This makes some sense to me (comments below).

There are other places that imply that the mode is a characteristic of the
domain.  4.3.3 says:

"Strict Mode is for administrative domains (or realms) that ..."

But table 1 in section 7 says:

"                                            New   New Error
Namespace  Levels   Mode    Operation   Rej. code  code    Reference
---------  ------   ----    ---------   ---------  ----    ---------
   dsn       5     strict   preemption      no      417    [This RFC]

   drsn      6     strict   preemption      no      417    [This RFC]

   q735      5     strict   preemption      no      417    [This RFC]

   ets       5  semi-strict preferential    no      417    [This RFC]

   wps       5  semi-strict preferential    no      417    [This RFC]

                   Table 1. Namespace Parameters"

Which makes "mode" a characteristic of the namespace.

This makes less sense to me.  If any of these namespaces appear in an RPH
in a SIP message which is being processed by a SIP element operating in
loose mode, they will NOT get the strict or semi-strict behavior specified
in Table 1.

It seems to me that the mode is/should be a function of the (SIP element,
namespace) pair.

For instance a SIP element could be "strict" for namespace A and
"semi-strict" for namespace B.

So a message with just A would succeed
A message with just B would be rejected
A message with A and B would succeed
A message with just C would  be rejected
A message with A and C would be rejected

Or the SIP element could be "strict" for namespace A, and "loose" for
everything else.

So a message with just A would succeed
A message with just B would be rejected
A message with A and B would succeed
A message with just C would  be rejected
A message with A and C would be succeed.

I don't think you could combine "semi-strict" and "loose" in the same SIP
element.

Am I missing something?

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 [e-mail] for questions on current sip
Use [e-mail] for new developments on the application of sip