<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>AW: Emergency Services and Service classes</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Gary,</FONT>
</P>
<P><FONT SIZE=2>after skimming over your contribution, two immediate comments:</FONT>
</P>
<P><FONT SIZE=2>1) QoS signalling within your serviceClass may overlap (or even conflict) with what will eventually appear in H.323 annex N. We should try to have QOS information in one place only. ServiceClass is one possible place, but then we should make sure that it covers also the requirements of annex N. </FONT></P>
<P><FONT SIZE=2>2) For the terminating side, the primary goal should be protection. In other words, the called party would be protected against calls below a certain class of service ("do not disturb unless it's urgent"), and existing calls would not be affected unless resources are needed for a call with higher priority. </FONT></P>
<P><FONT SIZE=2>It may even be worthwhile to specify separate protection levels separate from priority levels. </FONT>
<BR><FONT SIZE=2>For example, the call intrusion supplementary service recently approved by SG16 (Rec. H.450.11) follows such a concept: the caller is only allowed to intrude on an established call if his capability level is higher than the combined protection levels of the called party and the remote party of the established call. </FONT></P>
<P><FONT SIZE=2>Ernst Horvath</FONT>
<BR><FONT SIZE=2>Siemens AG</FONT>
</P>
<P><FONT SIZE=2>> -----Ursprüngliche Nachricht-----</FONT>
<BR><FONT SIZE=2>> Von: Gary Thom [<A HREF="mailto:gthom@delta-info.com">mailto:gthom@delta-info.com</A>]</FONT>
<BR><FONT SIZE=2>> Gesendet am: Donnerstag, 03. Mai 2001 17:07</FONT>
<BR><FONT SIZE=2>> An: ITU-SG16@mailbag.cps.INTEL.COM</FONT>
<BR><FONT SIZE=2>> Betreff: Emergency Services and Service classes</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> All,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Attached is a preliimary copy of a contribution to the </FONT>
<BR><FONT SIZE=2>> upcomming Brazil</FONT>
<BR><FONT SIZE=2>> meeting. It still needs US approval.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> It defines service classes using the generic extensible framework, and</FONT>
<BR><FONT SIZE=2>> should be more applicable than just emergency services. </FONT>
<BR><FONT SIZE=2>> Extension markers</FONT>
<BR><FONT SIZE=2>> were put in to allow addition of new priority and quality values.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Let me know if you have any comments, suggestions, or questions.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Thanks</FONT>
<BR><FONT SIZE=2>> Gary</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> --------------------------------------------</FONT>
<BR><FONT SIZE=2>> Name : Gary A. Thom</FONT>
<BR><FONT SIZE=2>> Company: Delta Information Systems, Inc.</FONT>
<BR><FONT SIZE=2>> Address: 300 Welsh Rd., Bldg 3</FONT>
<BR><FONT SIZE=2>> Horsham, PA 19044 USA</FONT>
<BR><FONT SIZE=2>> Phone : +1-215-657-5270 x123</FONT>
<BR><FONT SIZE=2>> Fax : +1-215-657-5273</FONT>
<BR><FONT SIZE=2>> E-mail : gthom@delta-info.com</FONT>
<BR><FONT SIZE=2>> Website: www.delta-info.com</FONT>
<BR><FONT SIZE=2>> --------------------------------------------</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>