<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Folks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the benefit of those who have not attended SG16 meetings recently, I want to share some of the more exciting work the group is doing in the area of IP-based multimedia communications (IPMC). Specifically, this message is focused on H.323 and H.325 (AMS) work.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The work on H.325 has been moving forward slowly, partly due to changes in peoples’ priorities due to the global economic crisis, but also do to challenges with finding the right path forward. The vision for what H.325 will enable has not substantially changed, but we had to find a way to realize that vision in a way that can actually be easily implemented.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In recent meetings, I think that’s starting to become clearer with new concepts being introduced in H.323 called “Assets”. An Asset is a an application that implements a subset of the H.225.0 and H.245 protocols to provide a very specific function (or set of functions), such as an electronic whiteboard, file transfer, or application sharing. Each application type will be defined in its own Asset application specification.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>At a high level, the user’s terminal and an Asset associate with each other using call-independent supplementary service messages, which are a type of message already defined and supported in H.323. In this way, we do not introduce new message types and messages will work over the existing H.323 infrastructure. Once devices are associated, they can be queried, invoked, and terminated using similar message constructs.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Assets themselves register with the Gatekeeper as a “Simple Endpoint Type” (SET). Presently, H.323 defines two SET device types, so Assets will be a third type of SET.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>During the IMTC meeting that will be held in Portugal next month (<a href="http://imtc.org/forum2013/agenda.html">http://imtc.org/forum2013/agenda.html</a>), Spranto (<a href="http://www.spranto.com">http://www.spranto.com</a>) will be there providing a live demonstration of the H.323 Asset concept. Not only that, but it will be a demonstration working through NAT/FW devices. This should be really interesting since, in my opinion, this represents the next-step in multimedia communications by bringing together a plurality of devices and applications to provide for a richer user experience.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In parallel, we are now modeling the same approach in H.325. We’re defining the H.325 signaling messages, working to ensure that we keep the number of message primitives to a minimum and to reduce the complexity of every entity. We also decided to switch to using JSON for signaling in H.325, which should be very interesting to developers. It should make it easier to build a web-based H.325 application, but it is also much easier to explain the protocol, extend it, etc. JSON has proven to be a very flexible and simple syntax.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If you are interested in getting involved either the H.323 Asset work or the H.325 work, feel free to reach out to me. I’ve have been neglectful of the H.325 design mailing list for a while now, I know, due to my other priorities preempting a lot of my direct involvement. However, I would very much like to re-start the interim electronic meetings on H.325 if there is interest. We can do that following the upcoming SG16 meeting (28 October – 8 November). Just let me know and I’ll make plans accordingly.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the meantime, I would definitely encourage you to try to make it to the IMTC meeting to see some of this new stuff in action.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers!<o:p></o:p></p><p class=MsoNormal>Paul E. Jones<o:p></o:p></p><p class=MsoNormal>Rapportuer, ITU-T Q2/SG16<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>