<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi all,<br>
<br>
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.<br>
<br>
So, if you have any input on the tech requirements topic, please
contribute :)<br>
<br>
Thanks and regards,<br>
</font>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
<div class="moz-cite-prefix">On 12.12.2023 12:56, Bogdan-Andrei
Iancu wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b6d8d1a3-792e-423e-9dd1-1cbb4d8271eb@opensips.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<font face="monospace">Hi all,<br>
<br>
As the scoping process was successfully completed last week (see
the <a
href="https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Scope"
moz-do-not-send="true">conclusions here</a>), the next
milestone is to explore the technical details and implications
of each IMS component to be addressed.<br>
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 :).<br>
<br>
A first list of technical requirements is <a
href="https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Requirements"
moz-do-not-send="true">already compiled here</a> - I tried to
group the requirements around the components we have scoped as
to be addressed.<br>
<br>
Now, what we need to do here:<br>
<br>
* verify and complete the list of requirements, to be sure
nothing is missing in order to properly implement the IMS
support.<br>
<br>
* comments or details about the items on the list are welcome -
as many details/info as better<br>
<br>
* 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 ?<br>
<br>
<br>
Thanks and regards,<br>
</font>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext"
href="https://www.opensips-solutions.com" moz-do-not-send="true">https://www.opensips-solutions.com</a>
<a class="moz-txt-link-freetext" href="https://www.siphub.com"
moz-do-not-send="true">https://www.siphub.com</a></pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Wg-ims mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wg-ims@lists.opensips.org">Wg-ims@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims">http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims</a>
</pre>
</blockquote>
<br>
</body>
</html>