<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content=Word.Document name=ProgId>
<META content="MSHTML 5.50.4207.2601" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK
href="cid:filelist.xml@01C01BF7.62369430" rel=File-List><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>0</w:Zoom>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:DrawingGridHorizontalSpacing>5 pt</w:DrawingGridHorizontalSpacing>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Cló Gaelach \(Twomey\);
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
SPAN.EmailStyle18 {
COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
SPAN.EmailStyle19 {
COLOR: #993366; mso-style-type: personal; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
SPAN.EmailStyle20 {
COLOR: #003300; mso-style-type: personal-reply; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1027"/>
</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 style="tab-interval: .5in" vLink=blue link=blue bgColor=white>
<DIV><FONT face=Arial>Orit,</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I'm not sure I am clear on what you are saying by
"Zone1...GK2"</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I expect the URL to be used these ways:</FONT></DIV>
<OL>
<LI><FONT face=Arial>The endpoint just hands the URL to the GK for
resolution</FONT></LI>
<LI><FONT face=Arial>The GK may perform some DNS operation to resolve the
address (ffs - Annex O)</FONT></LI>
<LI><FONT face=Arial>If the "mode" of the URL is "direct", the endpoint may
resolve the address of the endpoint and send a Setup (ffs - Annex
O)</FONT></LI></OL>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I can agree with having a basic URL, but we either have
little or no text in the URL section (which it is quite short enough) or we
decide, at the very least, what the difference is between a URL that represents
a callable entity, versus one that is not a callable entity.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I am proposing:</FONT></DIV>
<DIV><FONT face=Arial>h323:paulej@packetizer.com;mode=indirect</FONT></DIV>
<DIV><FONT face=Arial>h323:paulej@paris.packetizer.com;mode=direct</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Where "mode=indirect" would be the default. Your
proposal below is that without parameters, a Setup is the default-- and I do not
agree with that. In my opinion, it is far more likely that the query is
going to require the services of some entity (such as a Gatekeeper) to resolve
my address. This is especially true when I use a dynamic IP address, have
my network hierarchy "undisclosed" to the external community, etc. Also,
URLs are likely to follow e-mail addresses. Of course, that begs the
question of why we don't just put more emphasis on that. Of course, I
agree that URLs provide more flexibility, as they can be expanded to allow us to
select an MCU and conference on the MCU, for example.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I would be willing to drop the "port" portion of the URL
if we agree that it's only applicable for the "direct" mode. In that case, the
syntax might be:</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT
face=Arial>h323:paulej@paris.packetizer.com;mode=direct,port=1720</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Note that there are two values: one to indicate the mode
and one to indicate the port. We could allow the port to be semicolon
(";") separated, rather than coma separated. It makes no big difference to
me, but the port should only be available for "direct" calls. When the
calls are "indirect" (i.e., resolution by some Annex O means), the GK may
receive the request or the port will be learned from SRV queries-- that we can
determine later.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Is this acceptable?</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Paul</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=orit@radvision.com href="mailto:orit@radvision.com">Orit Levin</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=ITU-SG16@mailbag.cps.intel.com
href="mailto:ITU-SG16@mailbag.cps.intel.com">ITU-SG16@mailbag.cps.intel.com</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, September 11, 2000 3:01
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: Revised H.323 URL
document</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2>
<DIV>Bob!</DIV>
<DIV>Below is my take on the current situation. </DIV>
<DIV><FONT size=2>The three of us have the following different views
on the possible use of the H.323 URL.</FONT></DIV>
<DIV><FONT size=2>If I try to map them into the H.323 "classic" picture of
EP1---GK1-------GK2---EP2 . The GKs are optional. If exist, they may contain
BE as well.</FONT></DIV>
<DIV><FONT size=2>I understand the following:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>Bob:: indirect: EP1---GK1; direct: EP1
--------Zone2</FONT></DIV>
<DIV><FONT size=2>Paul:: indirect: Zone1-------GK2; direct:
Zone1------EP2</FONT></DIV>
<DIV><FONT size=2>Orit:: Zone1-------Zone2 (with H.225.0 Q.931, LRQ or Annex
G) possible between them for a specific call.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>We "agree" that all of the scenarios should be allowed.
</FONT></DIV>
<DIV><FONT size=2>"It seems like" we disagree about
the priority/emergency of each of the applications above.</FONT></DIV>
<DIV><FONT size=2>Saying that, I don't like very much
to define a solution based on the "perceived priority" of the
applications.</FONT></DIV>
<DIV><FONT size=2>My proposed approach</FONT><FONT size=2> is, <U>above
all</U>, guided by the fact, that <U>the DESTINATION is the one to design its
URL scheme, implement and, eventually, publish its
URL(s).</U></FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The URL </FONT><FONT size=2></FONT></DIV>
<DIV><FONT size=2>- has a key (I.e. the DNS domain) for
IP resolution only</FONT></DIV>
<DIV><FONT size=2>- says what is the first H.323 protocol to
contact this IP address, all the scenarios above are addressed.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>If the DNS portion (I.e. "host") is not present, it
automatically means, that the local (pre-configured or RAS discovered)
gatekeeper will resolve the "user" name (using RAS, Annex G, another DNS
lookup, other means). It is an exception, but it is still consistent with the
approach above (The local zone is responsible for the URL scheme, it
published.)</FONT></DIV>
<DIV><FONT face=Arial size=3></FONT> </DIV>
<DIV>The bottom line: I agree with the last proposal for H.323v4:</DIV>
<DIV>No parameters at all. The default: H.225.0/Q.931/Setup with its default
TCP port. </DIV>
<DIV>Paul?</DIV>
<DIV><FONT face=Arial size=3></FONT> </DIV>
<DIV><FONT size=2>Best Regards,</FONT></DIV></FONT></DIV>
<DIV>Orit Levin<BR>RADVision Inc.<BR>575 Corporate Drive Suite 420<BR>Mahwah,
NJ 07430<BR>Tel: 1 201 529 4300 (230)<BR>Fax: 1 201 529 3516<BR><A
href="http://www.radvision.com">www.radvision.com</A><BR><A
href="mailto:orit@radvision.com">orit@radvision.com</A></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial size=2><B>-----Original Message-----</B><BR><B>From:
</B>Callaghan, Robert <<A
href="mailto:Robert.Callaghan@icn.siemens.com">Robert.Callaghan@icn.siemens.com</A>><BR><B>To:
</B>'Orit Levin' <<A
href="mailto:orit@radvision.com">orit@radvision.com</A>><BR><B>Cc: </B><A
href="mailto:ITU-SG16@mailbag.cps.intel.com">ITU-SG16@mailbag.cps.intel.com</A>
<<A
href="mailto:ITU-SG16@mailbag.cps.intel.com">ITU-SG16@mailbag.cps.intel.com</A>><BR><B>Date:
</B>Monday, September 11, 2000 1:53 PM<BR><B>Subject: </B>RE: Revised H.323
URL document<BR><BR></DIV></FONT>
<DIV class=Section1>
<P class=MsoNormal><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">Orit,<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">Let
us try to focus on a few points first:<SPAN style="mso-spacerun: yes">
</SPAN>(These are snippets from the
thread.)<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">OL: Are you
interested in efficiently running H.323 over the
Internet?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RC: Yes!<SPAN
style="mso-spacerun: yes"> </SPAN>For clarification, this is the H.323
as defined in H.323v4 and H.225.0v4.<SPAN style="mso-spacerun: yes">
</SPAN>For the November decision, there should not be any extensions,
implicit or explicit.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">OL:
The picture, in my mind, is different from yours and fits the "traditional"
H.323. For every H.323 call, logically there are (at least) two GKs: source
and destination. (Physically, both of them are optional, based on the "mode"
policy inside the corresponding H.323
zones.)<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">RC:<SPAN
style="mso-spacerun: yes"> </SPAN>I agree with your model of two
endpoint each with an optional GKs based on zone policies. <SPAN
style="mso-spacerun: yes"> </SPAN>The source and destination policies
are independent from each other.<SPAN style="mso-spacerun: yes">
</SPAN>I don’t know how this is different, as you
state.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">OL:
</SPAN></FONT></SPAN><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">By
specifying in H323-URL the "mode" of operation between the source EP and a
GK, you propose to use the URL for "publishing" the relations between the EP
and "ITS" GK PER DESTINATION! It is, indeed, very different from the H.323
today. Moreover, you implicitly introduce a concept of a "source" GK, being
re-defined each time BY THE DESTINATION. (This case may be considered as an
additional application for the H.323
URL)<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RC: I
make so such assumption.<SPAN style="mso-spacerun: yes"> </SPAN>In the
“Direct” model, I assume that the given address is directly callable.<SPAN
style="mso-spacerun: yes"> </SPAN>The routing model is not specified
nor assumed.<SPAN style="mso-spacerun: yes"> </SPAN>If the term
“Direct” is a problem in that the term overlaps with the routing model then
the use of “Callable” would be fine.<SPAN style="mso-spacerun: yes">
</SPAN>The use of the DNS service to convert the DNS domain to an IP address
is assumed.<SPAN style="mso-spacerun: yes"> </SPAN>This is also the
only use of the DNS server. <SPAN style="mso-spacerun: yes"> </SPAN>No
DNS records beyond the “A” record will be used.<SPAN
style="mso-spacerun: yes"> </SPAN>If the initial use of the H.323 URL
could be limited to this service.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RC:<SPAN
style="mso-spacerun: yes"> </SPAN>The use of the “Indirect” or “non
callable” form has bothered me in that its use is not clearly defined.<SPAN
style="mso-spacerun: yes"> </SPAN>My view is that this was a means to
access an H.323 repository to obtain the true address. <SPAN
style="mso-spacerun: yes"> </SPAN>Apparently there are other
views.<SPAN style="mso-spacerun: yes"> </SPAN>Therefore I suggest that
a solution would be to drop this form for
now.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">OL:
The natural use of URLs is between the zones/domain. For H.323, it is an
OPTION, what kind of address resolution to propose and use. <U>The beauty of
the URL approach is that the DESTINATION provides an option to be reached
using the DNS lookup</U>, if it chooses so and populates properly the
DNS.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">RC:
The may be beautify for some; but it is definitely new.<SPAN
style="mso-spacerun: yes"> </SPAN>I know of nothing in H.323v4 that
describes the procedures and rules for this type of address resolution.
<SPAN style="mso-spacerun: yes"> </SPAN>This can be discussed as part
of Annex O, after the decision on
H.323v4.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle19><FONT face=Arial color=blue
size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">OL: We don't have
to agree on the mailing list. We can spend more then one meeting in order to
reach "the consensus". In that case, I would support the inclusion
of the minimal H323-URL only (without any parameters and without the
PORT number) towards the H.323v4.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RC: I agree that it
is not possible to agree to a complex solution on the mailing list.<SPAN
style="mso-spacerun: yes"> </SPAN>However, I hope that we can agree to
a simple URL without any parameters or port (ouch! </SPAN></FONT><FONT
face=Wingdings color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Wingdings; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-symbol-font-family: Wingdings"><SPAN
style="mso-char-type: symbol; mso-symbol-font-family: Wingdings">J</SPAN></SPAN></FONT><FONT
face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">) where this URL is
the actual address to be used in a SETUP message.<SPAN
style="mso-spacerun: yes"> </SPAN>This should not change anything in
H.323 including the use of the GK.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I hope that this
helps.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Bob</SPAN></FONT><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoAutoSig><!--[if supportFields]><span class=EmailStyle20><font
size=2 color="#003300" face=Arial><span style='font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'><span style='mso-element:field-begin'></span><span
style="mso-spacerun: yes"> </span>AUTOTEXTLIST \s "E-mail
Signature" <span style='mso-element:field-separator'></span></span></font></span><![endif]--><FONT
color=#003300><SPAN
style="COLOR: #003300">------------------------------------------------------------------</SPAN></FONT><FONT
color=#003300><SPAN
style="COLOR: #003300; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Cló Gaelach (Twomey)" color=#339966
size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: #339966; FONT-FAMILY: 'Cló Gaelach \(Twomey\)'">Robert
Callaghan<o:p></o:p></SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt">Siemens
Enterprise Networks</SPAN></FONT><FONT color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt">Tel:
+1.561.923.1756<SPAN
style="mso-tab-count: 1">
</SPAN>Fax: +1.561.923.1403</SPAN></FONT><FONT color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt">Email:<SPAN
style="mso-tab-count: 1">
</SPAN>Robert.Callaghan@ICN.Siemens.com</SPAN></FONT><FONT color=#003300
size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" color=#003300 size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: #003300">------------------------------------------------------------------</SPAN></FONT><FONT
color=#003300><SPAN
style="COLOR: #003300; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><!--[if supportFields]><span class=EmailStyle20><font
size=2 color="#003300" face=Arial><span style='font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:Arial'><span style='mso-element:field-end'></span></span></font></span><![endif]--><FONT
color=black><SPAN
style="COLOR: black"><![if !supportEmptyParas]><![endif]> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>