[Sipping] http://www.ietf.org/internet-drafts/draft-sriram-sipping-poc-lip-02.txt

["Fridy Sharon-Fridman" <Fridy.Sharon-Fridman at followap.com>]

Hi,

 

As the intercept is based on SIP INVITE with SDP, why isn’t it applicable to intercept conference (xcon conference) where he media is MSRP instead of RTP etc.?

Can this I/D be generalized to handle session interception and cover PoC demands but be less tightly coupled to it, as once was the mission statement of IETF (internet Task Force…)?

 

I suggest using the needed headers and terms slightly changed:

Mode-of-Tapping

Direction

User-to-be-Tapped

 

The PoC server procedures are clearly defined in the OMA PoC specification. PoC usage scenario can be given as an illustrated example.

It will provide OMA PoC group with a sufficient solution for their demands, but not tighten the mechanism to PoC alone.

 

Cheers,

--Fridy / Followap

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