Access rules for dialog state?

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Access rules for dialog state?

Adrian Georgescu
I have a question about the policy for subscriptions to dialog state.  
How should this be done? Would a new pres-rules document make sense  
for this. Like dialog-rules, same schema.

I could not find any normative specification, did someone find  
something related to this?

Regards,
Adrian



_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Iñaki Baz Castillo
2009/7/7 Adrian Georgescu <[hidden email]>:
> I have a question about the policy for subscriptions to dialog state.
> How should this be done? Would a new pres-rules document make sense
> for this. Like dialog-rules, same schema.
>
> I could not find any normative specification, did someone find
> something related to this?

Hi Adrian, recently I've read all the XCAP related RFC's and documents
and found no info at all about RFC 4235. It seems that XCAP is just
defined for SIMPLE presence (events "presence", "presence.watcher" and
so).

In section 6 of RFC 5025 (pres-rules) there is an example of XML
document in which there is no keyword "presence" at all, so I assume
it is intended just for "presence" event :(
  http://tools.ietf.org/html/rfc5025#section-6

However, would opensips presence module ask for such authorization
rules to the XCAP server if the SUBSCRIBE event is different than
"presence"?


--
Iñaki Baz Castillo
<[hidden email]>

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Iñaki Baz Castillo
2009/7/7 Iñaki Baz Castillo <[hidden email]>:

> 2009/7/7 Adrian Georgescu <[hidden email]>:
>> I have a question about the policy for subscriptions to dialog state.
>> How should this be done? Would a new pres-rules document make sense
>> for this. Like dialog-rules, same schema.
>>
>> I could not find any normative specification, did someone find
>> something related to this?
>
> Hi Adrian, recently I've read all the XCAP related RFC's and documents
> and found no info at all about RFC 4235. It seems that XCAP is just
> defined for SIMPLE presence (events "presence", "presence.watcher" and
> so).
>
> In section 6 of RFC 5025 (pres-rules) there is an example of XML
> document in which there is no keyword "presence" at all, so I assume
> it is intended just for "presence" event :(
>  http://tools.ietf.org/html/rfc5025#section-6
>
> However, would opensips presence module ask for such authorization
> rules to the XCAP server if the SUBSCRIBE event is different than
> "presence"?

Adrian, since I'm also interested in this exotic topic, I've started a
thread in sip-implementors:
  https://lists.cs.columbia.edu/pipermail/sip-implementors/2009-July/023106.html

Feel free to join it :)



--
Iñaki Baz Castillo
<[hidden email]>

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Adrian Georgescu
For the lack of other pragmatic methods I would implement the following:

A. Suport in OpenXCAP server a new auid, document name dialog-rules  
with the clear purpose of providing an authorization policy for dialog  
Event
B. Setup the OpenSIPS PA module that handles the dialog event to read  
it in order to apply a policy, the same as presence_xml does with pres-
rules

Does anyone see a problem with this approach?

Adrian


On Jul 7, 2009, at 3:37 PM, Iñaki Baz Castillo wrote:

> 2009/7/7 Iñaki Baz Castillo <[hidden email]>:
>> 2009/7/7 Adrian Georgescu <[hidden email]>:
>>> I have a question about the policy for subscriptions to dialog  
>>> state.
>>> How should this be done? Would a new pres-rules document make sense
>>> for this. Like dialog-rules, same schema.
>>>
>>> I could not find any normative specification, did someone find
>>> something related to this?
>>
>> Hi Adrian, recently I've read all the XCAP related RFC's and  
>> documents
>> and found no info at all about RFC 4235. It seems that XCAP is just
>> defined for SIMPLE presence (events "presence", "presence.watcher"  
>> and
>> so).
>>
>> In section 6 of RFC 5025 (pres-rules) there is an example of XML
>> document in which there is no keyword "presence" at all, so I assume
>> it is intended just for "presence" event :(
>>  http://tools.ietf.org/html/rfc5025#section-6
>>
>> However, would opensips presence module ask for such authorization
>> rules to the XCAP server if the SUBSCRIBE event is different than
>> "presence"?
>
> Adrian, since I'm also interested in this exotic topic, I've started a
> thread in sip-implementors:
>  https://lists.cs.columbia.edu/pipermail/sip-implementors/2009-July/023106.html
>
> Feel free to join it :)
>
>
>
> --
> Iñaki Baz Castillo
> <[hidden email]>


_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Iñaki Baz Castillo
2009/7/7 Adrian Georgescu <[hidden email]>:
> For the lack of other pragmatic methods I would implement the following:
>
> A. Suport in OpenXCAP server a new auid, document name dialog-rules with the
> clear purpose of providing an authorization policy for dialog Event
> B. Setup the OpenSIPS PA module that handles the dialog event to read it in
> order to apply a policy, the same as presence_xml does with pres-rules
>
> Does anyone see a problem with this approach?

I think that is the expected approach :)
However, I would like to receive replies in sip-implementors.

--
Iñaki Baz Castillo
<[hidden email]>

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Adrian Georgescu

On Jul 7, 2009, at 4:54 PM, Iñaki Baz Castillo wrote:

> 2009/7/7 Adrian Georgescu <[hidden email]>:
>> For the lack of other pragmatic methods I would implement the  
>> following:
>>
>> A. Suport in OpenXCAP server a new auid, document name dialog-rules  
>> with the
>> clear purpose of providing an authorization policy for dialog Event
>> B. Setup the OpenSIPS PA module that handles the dialog event to  
>> read it in
>> order to apply a policy, the same as presence_xml does with pres-
>> rules
>>
>> Does anyone see a problem with this approach?
>
> I think that is the expected approach :)
> However, I would like to receive replies in sip-implementors.

I thought we are the SIP implementors ;-)

Adrian


_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Iñaki Baz Castillo
2009/7/7 Adrian Georgescu <[hidden email]>:
>> I think that is the expected approach :)
>> However, I would like to receive replies in sip-implementors.
>
> I thought we are the SIP implementors ;-)

100% agree :)


--
Iñaki Baz Castillo
<[hidden email]>

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Access rules for dialog state?

Victor Pascual Avila
In reply to this post by Adrian Georgescu
On Tue, Jul 7, 2009 at 4:17 PM, Adrian Georgescu<[hidden email]> wrote:

> For the lack of other pragmatic methods I would implement the following:
>
> A. Suport in OpenXCAP server a new auid, document name dialog-rules
> with the clear purpose of providing an authorization policy for dialog
> Event
> B. Setup the OpenSIPS PA module that handles the dialog event to read
> it in order to apply a policy, the same as presence_xml does with pres-
> rules
>
> Does anyone see a problem with this approach?

It makes sense.
--
Victor Pascual Ávila

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel