[WG-IMS] Technical Requirements - RFC

[Răzvan Crainea]

Hi, all!

Let me jump in with some ideas about the high-level design of the IMS 
AKA authentication: the plan is to create an entity for managing the AV 
(authentication vectors) required by the AKA algorithm. This entity will 
interact via two generic interfaces.
The first interface will face the authentication module and it should 
provide to the (new IMS) challenging and authentication functions an 
internal API that can be used to get a new AV, mark it as used, 
invalidate it, etc.
The second interface will be required by the AV storage entity in order 
to fetch the needed AVs - this interface may be implemented by various 
modules. An example of such implementation would be a module that uses 
the internal diameter interface to do the Cx MAR/MAA requests to get the 
AVs from an HSS. Another implementation may require to run some routes 
to fetch the AVs through other script mechanisms, like hand-crafted 
Diameter requests, etc.
Any feedback is welcome, so if you have any suggestions, do let us know.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com

On 12/18/23 12:26, Bogdan-Andrei Iancu wrote:
> Hi all,
> 
> A quick reminder on this, as we should try to wrap up this stage by the 
> end of this week (before the holiday). This will help us to stay on 
> tracks with the 3.5 release.
> 
> So, if you have any input on the tech requirements topic, please 
> contribute :)
> 
> Thanks and regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> 
> On 12.12.2023 12:56, Bogdan-Andrei Iancu wrote:
>> Hi all,
>>
>> As the scoping process was successfully completed last week (see the 
>> conclusions here 
>> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Scope>), 
>> the next milestone is to explore the technical details and 
>> implications of each IMS component to be addressed.
>> Here we are heavily relying on the input (as expertise) from people 
>> already involved in the IMS world, so please contribute as much as 
>> possible :).
>>
>> A first list of technical requirements is already compiled here 
>> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Requirements> - I tried to group the requirements around the components we have scoped as to be addressed.
>>
>> Now, what we need to do here:
>>
>> * verify and complete the list of requirements, to be sure nothing is 
>> missing in order to properly implement the IMS support.
>>
>> * comments or details about the items on the list are welcome - as 
>> many details/info as better
>>
>> * a "weak" item on the list is the Presence server - even if the SIP 
>> flows are clear, what is not yet 100% clear (at least for me) is what 
>> "event"'s are needed here - for sure the "presence" and as far as I 
>> heard the "reg" (RFC3680). But anyone can throw more light here ?
>>
>>
>> Thanks and regards,
>> -- 
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> _______________________________________________
>> Wg-ims mailing list
>> Wg-ims at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
> 
> Hi all,
> 
> A quick reminder on this, as we should try to wrap up this stage by the 
> end of this week (before the holiday). This will help us to stay on 
> tracks with the 3.5 release.
> 
> So, if you have any input on the tech requirements topic, please 
> contribute :)
> 
> Thanks and regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> 
> On 12.12.2023 12:56, Bogdan-Andrei Iancu wrote:
>> Hi all,
>>
>> As the scoping process was successfully completed last week (see the 
>> conclusions here 
>> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Scope>), 
>> the next milestone is to explore the technical details and 
>> implications of each IMS component to be addressed.
>> Here we are heavily relying on the input (as expertise) from people 
>> already involved in the IMS world, so please contribute as much as 
>> possible :).
>>
>> A first list of technical requirements is already compiled here 
>> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Requirements> - I tried to group the requirements around the components we have scoped as to be addressed.
>>
>> Now, what we need to do here:
>>
>> * verify and complete the list of requirements, to be sure nothing is 
>> missing in order to properly implement the IMS support.
>>
>> * comments or details about the items on the list are welcome - as 
>> many details/info as better
>>
>> * a "weak" item on the list is the Presence server - even if the SIP 
>> flows are clear, what is not yet 100% clear (at least for me) is what 
>> "event"'s are needed here - for sure the "presence" and as far as I 
>> heard the "reg" (RFC3680). But anyone can throw more light here ?
>>
>>
>> Thanks and regards,
>> -- 
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> _______________________________________________
>> Wg-ims mailing list
>> Wg-ims at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
> 
> 
> _______________________________________________
> Wg-ims mailing list
> Wg-ims at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims