<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: H.323 URL</TITLE>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META content="MSHTML 5.00.3018.900" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial>Francois,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>If I want to provide a means of allowing somebody to call
me by placing a URL on a web page, I need to provide something that can be
resolved universally by H.323 endpoints. Bob mentioned querying a
database-- that's certainly a possibility, assuming that that database contains
all of the information it needs to resolve an address.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>What I am afraid of here is that we are introducing syntax
to reach a resource without defining any procedure.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>If I see this url:</FONT></DIV>
<DIV><FONT face=Arial><A
href="mailto:h323:paulej@packetizer.com">h323:paulej@packetizer.com</A></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>What does that tell the H.323 entity? Is there a GK
that is expecting a LRQ, AccessRequest, or is it something else entirely?
Perhaps the right solution is to define (in normative text) the procedure for
using SRV DNS records to query the packetizer.com domain.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>As Pete rightfully pointed out, an H.323 URL would be the
perfect place to place conference identifiers for multipoint
conferences:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial><A
href="mailto:h323:conf-server1@packetizer.com;cid:XXXX-XXXX-XXXX-XXXX">h323:conf-server1@packetizer.com;cid:XXXX-XXXX-XXXX-XXXX</A></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>I think we need to work on the procedural part of this
now. Who is working on that?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial>Paul</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A href="mailto:audet@NORTELNETWORKS.COM"
title=audet@NORTELNETWORKS.COM>Francois Audet</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
href="mailto:ITU-SG16@mailbag.cps.intel.com"
title=ITU-SG16@mailbag.cps.intel.com>ITU-SG16@mailbag.cps.intel.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, June 16, 2000 11:48
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: H.323 URL</DIV>
<DIV><BR></DIV>
<P><FONT size=2>I would agree with Bob here. </FONT></P>
<P><FONT size=2>Using an H.323 URL for a telephone number would imply that you
can only be </FONT><BR><FONT size=2>reached using H.323. Is this you
intention?</FONT> </P>
<P><FONT size=2>> -----Original Message-----</FONT> <BR><FONT size=2>>
From: Callaghan, Robert [<A
href="mailto:Robert.Callaghan@ICN.SIEMENS.COM">mailto:Robert.Callaghan@ICN.SIEMENS.COM</A>]</FONT>
<BR><FONT size=2>> Sent: Friday, June 16, 2000 5:39 AM</FONT> <BR><FONT
size=2>> To: <A
href="mailto:ITU-SG16@MAILBAG.INTEL.COM">ITU-SG16@MAILBAG.INTEL.COM</A></FONT>
<BR><FONT size=2>> Subject: Re: H.323 URL</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> </FONT><BR><FONT size=2>> Paul,</FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>> I think that this is
getting complicated.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
I did not envision the use of the H.323-URL to encompase a </FONT><BR><FONT
size=2>> telephone number.</FONT> <BR><FONT size=2>> I only conceede for
the purpose of progress.</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> I saw the H.323-URL to be an identifier that would be used to
access a</FONT> <BR><FONT size=2>> database. The DNS portion would
identify the database, the </FONT><BR><FONT size=2>> userID would be</FONT>
<BR><FONT size=2>> the entry in the database. The database would then
return </FONT><BR><FONT size=2>> the necessary</FONT> <BR><FONT size=2>>
information to complete the call. It is highly propable that this</FONT>
<BR><FONT size=2>> information would include an E.164 or PNP address.
This is </FONT><BR><FONT size=2>> especially true</FONT> <BR><FONT
size=2>> when the call must be ompleted over the SCN.</FONT> <BR><FONT
size=2>> </FONT><BR><FONT size=2>> I saw telephone numbers being defined
in the "Tel:" URL </FONT><BR><FONT size=2>> defined in RFC2806.</FONT>
<BR><FONT size=2>> This URL covers many of optional fields needed to make
an SCN </FONT><BR><FONT size=2>> call which are</FONT> <BR><FONT
size=2>> not presently covered in H.323.</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> If we are to have multiple forms of an H.323 URL,
I would </FONT><BR><FONT size=2>> prefer to have</FONT> <BR><FONT
size=2>> multi-URL IDs.</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> Bob</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> P.S.
(By the way, the complex, cover everything, is where the </FONT><BR><FONT
size=2>> last try at an</FONT> <BR><FONT size=2>> H.323 URL
diaappeared.)</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
------------------------------------------------------------------</FONT>
<BR><FONT size=2>> Robert Callaghan</FONT> <BR><FONT size=2>> Siemens
Enterprise Networks</FONT> <BR><FONT size=2>> Tel:
+1.561.923.1756 Fax: +1.561.923.1403</FONT> <BR><FONT
size=2>> Email: Robert.Callaghan@ICN.Siemens.com</FONT> <BR><FONT
size=2>>
------------------------------------------------------------------</FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>> </FONT><BR><FONT
size=2>> -----Original Message-----</FONT> <BR><FONT size=2>> From: Paul
E. Jones [<A
href="mailto:paulej@packetizer.com">mailto:paulej@packetizer.com</A>]</FONT>
<BR><FONT size=2>> Sent: Friday, June 16, 2000 3:11 AM</FONT> <BR><FONT
size=2>> To: Callaghan, Robert; 'Orit Levin'</FONT> <BR><FONT size=2>>
Cc: Mailing list for parties associated with ITU-T Study Group 16</FONT>
<BR><FONT size=2>> (E-mail)</FONT> <BR><FONT size=2>> Subject: Re: H.323
URL</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> </FONT><BR><FONT
size=2>> Bob,</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> I'm
still surprised that you don't want to see the URL expanded...</FONT>
<BR><FONT size=2>> especially to address party number types. Here is
is currently:</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
H323-URL = "H323:" user
["@" hostport]</FONT> <BR><FONT size=2>>
user =
username | phone-number</FONT> <BR><FONT size=2>>
username = *( unreserved |
escaped | "&" | "=" | "+" </FONT><BR><FONT size=2>> | "$" | ","
)</FONT> <BR><FONT size=2>>
hostport = host [ ":" port ]</FONT>
<BR><FONT size=2>>
host =
hostname | IPv4address</FONT> <BR><FONT size=2>>
hostname = *( domainlabel "." )
toplabel [ "." ]</FONT> <BR><FONT size=2>>
domainlabel = alphanum | alphanum *( alphanum | "-" )
alphanum</FONT> <BR><FONT size=2>>
toplabel = alpha | alpha *( alphanum
| "-" ) alphanum</FONT> <BR><FONT size=2>>
IPv4address = 1*digit "." 1*digit "." 1*digit "."
1*digit</FONT> <BR><FONT size=2>>
port =
*digit</FONT> <BR><FONT size=2>>
reserved = ";" | "/" | "?" | ":" |
"@" | "&" | "=" | </FONT><BR><FONT size=2>> "+" |"$" | ","</FONT>
<BR><FONT size=2>>
digits = 1*DIGIT</FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>> However, to be useful,
information that follows the "h323:" should be</FONT> <BR><FONT size=2>>
something in a form that an H.323 Gatekeeper can resolve.
</FONT><BR><FONT size=2>> Those things</FONT> <BR><FONT size=2>>
include:</FONT> <BR><FONT size=2>> dialedDigits</FONT>
<BR><FONT size=2>> h323-ID</FONT> <BR><FONT
size=2>> email-ID</FONT> <BR><FONT size=2>>
partyNumber</FONT> <BR><FONT size=2>> or one of the transportAddress
types.</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>> This seems to
be a reasonable syntax:</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> H323-URL = "H323:"
Address</FONT> <BR><FONT size=2>>
Address = AliasAddress /
TransportAddress</FONT> <BR><FONT size=2>> AliasAddress =
dialedDigits / h323-ID / email-ID / partyNumber</FONT> <BR><FONT size=2>>
dialedDigits = "dialedDigits=" 1*digit</FONT> <BR><FONT
size=2>> h323-ID =
"h323-ID=" 1*OCTET ; UTF-8 string represting the</FONT> <BR><FONT
size=2>> BMPString</FONT> <BR><FONT size=2>>
email-ID = "email-ID="
email-ID-spec</FONT> <BR><FONT size=2>> partyNumber
= e164Number / dataPartyNumber / telexPartyNumber /</FONT> <BR><FONT
size=2>> privateNumber</FONT> <BR><FONT
size=2>>
/ nationalStandardPartyNumber</FONT> <BR><FONT size=2>>
email-ID-spec = mailbox / group</FONT> <BR><FONT size=2>>
group = phrase ":"
[ mailbox ] ";"</FONT> <BR><FONT size=2>>
phrase = 1*word</FONT>
<BR><FONT size=2>>
word = atom
/ quoted-string</FONT> <BR><FONT size=2>>
atom =
1*CHAR ; any CHAR except specials, SPACE and CTLs</FONT> <BR><FONT
size=2>> specials = "(" / ")" /
"<" / ">" / "@" ; Must be in quoted-</FONT> <BR><FONT
size=2>>
/ "," / ";" / ":" / "\" / <"> ; string, to use</FONT>
<BR><FONT
size=2>>
/ "." / "[" /
"]"
; within a word.</FONT> <BR><FONT size=2>> quoted-string
=</FONT> <BR><FONT size=2>>
mailbox = addr-spec / phrase
route-addr</FONT> <BR><FONT size=2>>
addr-spec = local-part "@" domain</FONT>
<BR><FONT size=2>> local-part = word *("."
word)</FONT> <BR><FONT size=2>>
domain = sub-domain
*("." sub-domain)</FONT> <BR><FONT size=2>>
sub-domain = domain-ref / domain-literal</FONT>
<BR><FONT size=2>> domain-ref = atom</FONT>
<BR><FONT size=2>> domain-literal = "[" *(dtext / quoted-pair)
"]"</FONT> <BR><FONT size=2>>
dtext =
1*CHAR ; Any CHAR excluding "[", "]", "\" & CR,</FONT> <BR><FONT
size=2>>
; & including linear-white-space></FONT> <BR><FONT size=2>>
linear-white-space = 1*([CRLF] LWSP-char)</FONT> <BR><FONT size=2>>
LWSP-char = SP / HTAB</FONT> <BR><FONT
size=2>> quoted-pair = "\" CHAR</FONT> <BR><FONT
size=2>> phrase =
1*word</FONT> <BR><FONT size=2>> route-addr =
"<" [route] addr-spec ">"</FONT> <BR><FONT size=2>>
route = "@" domain
":"</FONT> <BR><FONT size=2>> e164Number =
"e164Number=" publicTypeOfNumber "," digits</FONT> <BR><FONT size=2>>
digits = 1*(DIGIT / "#"
/ "*" / ",")</FONT> <BR><FONT size=2>> publicTypeOfNumber = "unknown" /
"internationalStandard" / </FONT><BR><FONT size=2>> "nationalNumber"</FONT>
<BR><FONT
size=2>>
/ "networkSpecificNumber" / "subscriberNumber" /</FONT> <BR><FONT
size=2>>
/ "abbreviatedNumber"</FONT> <BR><FONT size=2>> dataPartyNumber =
"dataPartyNumber=" digits</FONT> <BR><FONT size=2>> telexPartyNumber=
"telexPartyNumber=" digits</FONT> <BR><FONT size=2>> privatePartyNumber =
"privatePartyNumber=" </FONT><BR><FONT size=2>> privateTypeOfNumber ","
digits</FONT> <BR><FONT size=2>> privateTypeOfNumber = "unknown" /
"level2RegionalNumber" /</FONT> <BR><FONT size=2>>
"level1RegionalNumber"</FONT> <BR><FONT
size=2>>
/ "pISNSpecificNumber" / "localNumber" /</FONT> <BR><FONT size=2>>
"abbreviatedNumber"</FONT> <BR><FONT size=2>> TransportAddress = ipAddress
/ ipSourceRoute / ipxAddress / ip6Address</FONT> <BR><FONT
size=2>>
/ netBios / nsap / nonStandardAddress</FONT> <BR><FONT size=2>>
ipAddress = ip ":" port</FONT> <BR><FONT
size=2>>
ip
= 1*DIGIT "." 1*DIGIT "." 1*DIGIT "." 1*DIGIT</FONT> <BR><FONT size=2>>
port =
1*DIGIT</FONT> <BR><FONT size=2>> ipSourceRoute = ip ":" port
"," ip *1("," ip) ";" ("strict" </FONT><BR><FONT size=2>> / "loose")</FONT>
<BR><FONT size=2>> ipxAddress = 1*DIGIT ":"
1*DIGIT ":" 1*DIGIT</FONT> <BR><FONT size=2>>
ip6Address = 1*HEXDIGIT 14*(":" [1*HEXDIGIT])
1*HEXDIGIT</FONT> <BR><FONT size=2>>
HEXDIGIT = DIGIT / "A" / "B" / "C" /
"D" / "E" / "F"</FONT> <BR><FONT size=2>>
netBios = ;;
and so forth</FONT> <BR><FONT size=2>>
nsap
=</FONT> <BR><FONT size=2>> nonStandardAddress =</FONT> <BR><FONT
size=2>> </FONT><BR><FONT size=2>> Now, there may be an error or two in
there, but at least it </FONT><BR><FONT size=2>> is more complete</FONT>
<BR><FONT size=2>> and an H.323 system knows how to work with these.
(Note I </FONT><BR><FONT size=2>> did not address</FONT> <BR><FONT
size=2>> the new V4 alias "mobileIUM")</FONT> <BR><FONT size=2>>
</FONT><BR><FONT size=2>> If we used this grammar, I don't think we would
need a lot of </FONT><BR><FONT size=2>> strange rules</FONT> <BR><FONT
size=2>> about what you do with the URL. Basically, you take it apart
</FONT><BR><FONT size=2>> according to</FONT> <BR><FONT size=2>> its
internal parts to form an alias address that a Gatekeeper </FONT><BR><FONT
size=2>> can resolve.</FONT> <BR><FONT size=2>> </FONT><BR><FONT
size=2>> Paul</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
----- Original Message -----</FONT> <BR><FONT size=2>> From: "Callaghan,
Robert" <Robert.Callaghan@icn.siemens.com></FONT> <BR><FONT size=2>>
To: "'Orit Levin'" <orit@radvision.com>; "'Paul E. Jones'"</FONT>
<BR><FONT size=2>> <paulej@PACKETIZER.COM></FONT> <BR><FONT
size=2>> Cc: "Mailing list for parties associated with ITU-T Study
</FONT><BR><FONT size=2>> Group 16 (E-mail)"</FONT> <BR><FONT size=2>>
<ITU-SG16@mailbag.cps.intel.com></FONT> <BR><FONT size=2>> Sent:
Wednesday, June 14, 2000 3:50 PM</FONT> <BR><FONT size=2>> Subject: RE:
H.323 URL</FONT> <BR><FONT size=2>> </FONT><BR><FONT size=2>>
</FONT><BR><FONT size=2>> > Orit,</FONT> <BR><FONT size=2>>
></FONT> <BR><FONT size=2>> > In my opinion, an email-ID alias
conforms to RFC-822 and is </FONT><BR><FONT size=2>> interpreted</FONT>
<BR><FONT size=2>> > according the rules stated in H.225.0. An
H.323-URL-ID conforms to</FONT> <BR><FONT size=2>> > TD-40a/Osaka and is
interpreted according to the rules </FONT><BR><FONT size=2>> stated in
TD-40a.</FONT> <BR><FONT size=2>> An</FONT> <BR><FONT size=2>> >
H.323-ID is a character string without any rules of </FONT><BR><FONT
size=2>> interpretation. I see</FONT> <BR><FONT size=2>> > no
need to blend these contexts. All three addressing </FONT><BR><FONT
size=2>> modes can be use;</FONT> <BR><FONT size=2>> > each in its
own context.</FONT> <BR><FONT size=2>> ></FONT> <BR><FONT size=2>>
> However, these are my opinion. Maybe more work is needed
</FONT><BR><FONT size=2>> in Portland.</FONT> <BR><FONT size=2>>
></FONT> <BR><FONT size=2>> > Bob</FONT> <BR><FONT size=2>>
></FONT> <BR><FONT size=2>> >
------------------------------------------------------------------</FONT>
<BR><FONT size=2>> > Robert Callaghan</FONT> <BR><FONT size=2>> >
Siemens Enterprise Networks</FONT> <BR><FONT size=2>> > Tel:
+1.561.923.1756 Fax: +1.561.923.1403</FONT> <BR><FONT size=2>> > Email:
Robert.Callaghan@ICN.Siemens.com</FONT> <BR><FONT size=2>> >
------------------------------------------------------------------</FONT>
<BR><FONT size=2>> ></FONT> <BR><FONT size=2>> ></FONT> <BR><FONT
size=2>> > -----Original Message-----</FONT> <BR><FONT size=2>> >
From: Orit Levin [<A
href="mailto:orit@radvision.com">mailto:orit@radvision.com</A>]</FONT>
<BR><FONT size=2>> > Sent: Wednesday, June 14, 2000 11:45 AM</FONT>
<BR><FONT size=2>> > To: Callaghan, Robert; 'Paul E. Jones'</FONT>
<BR><FONT size=2>> > Cc: Mailing list for parties associated with ITU-T
Study Group 16</FONT> <BR><FONT size=2>> > (E-mail)</FONT> <BR><FONT
size=2>> > Subject: Re: H.323 URL</FONT> <BR><FONT size=2>>
></FONT> <BR><FONT size=2>> ></FONT> <BR><FONT size=2>> > Hello
Bob and Paul!</FONT> <BR><FONT size=2>> > I don't see backwards
compatibility problem, when the URL </FONT><BR><FONT size=2>> says
explicitly</FONT> <BR><FONT size=2>> > H323-URL. An appropriate change
may be to state, that the </FONT><BR><FONT size=2>> default meaning</FONT>
<BR><FONT size=2>> of</FONT> <BR><FONT size=2>> > url, encoded into
email-ID alias, is according to RFC-822.</FONT> <BR><FONT size=2>> >
Now, I feel a need to put a chapter explaining what is the </FONT><BR><FONT
size=2>> meaning of</FONT> <BR><FONT size=2>> email</FONT> <BR><FONT
size=2>> > URL (apart from its syntax) when used in H.323 Network.
</FONT><BR><FONT size=2>> There is some</FONT> <BR><FONT size=2>> >
explanation in H.225.0 Appendix IV. Do you find it clear </FONT><BR><FONT
size=2>> and sufficient?</FONT> <BR><FONT size=2>> > Orit
Levin</FONT> <BR><FONT size=2>> > RADVision Inc.</FONT> <BR><FONT
size=2>> > 575 Corporate Drive Suite 420</FONT> <BR><FONT size=2>>
> Mahwah, NJ 07430</FONT> <BR><FONT size=2>> > Tel: 1 201 529
4300 (230)</FONT> <BR><FONT size=2>> > Fax: 1 201 529 3516</FONT>
<BR><FONT size=2>> > www.radvision.com</FONT> <BR><FONT size=2>> >
orit@radvision.com</FONT> <BR><FONT size=2>> > -----Original
Message-----</FONT> <BR><FONT size=2>> > From: Callaghan, Robert
<Robert.Callaghan@icn.siemens.com></FONT> <BR><FONT size=2>> > To:
'Paul E. Jones' <paulej@PACKETIZER.COM>; 'Orit Levin'</FONT> <BR><FONT
size=2>> > <orit@radvision.com></FONT> <BR><FONT size=2>> >
Cc: Mailing list for parties associated with ITU-T Study </FONT><BR><FONT
size=2>> Group 16 (E-mail)</FONT> <BR><FONT size=2>> >
<ITU-SG16@mailbag.cps.intel.com></FONT> <BR><FONT size=2>> > Date:
Wednesday, June 14, 2000 9:56 AM</FONT> <BR><FONT size=2>> > Subject:
H.323 URL</FONT> <BR><FONT size=2>> ></FONT> <BR><FONT size=2>>
></FONT> <BR><FONT size=2>> > >Paul,</FONT> <BR><FONT size=2>>
> ></FONT> <BR><FONT size=2>> > >I have a backward
compatibility item for you to think about.</FONT> <BR><FONT size=2>> >
></FONT> <BR><FONT size=2>> > >TD-40/Osaka states that the
H323-URL may be coded into the </FONT><BR><FONT size=2>> email-ID
for</FONT> <BR><FONT size=2>> > >alias address. However,
H.225.0 states that the email-ID </FONT><BR><FONT size=2>> shall
conform</FONT> <BR><FONT size=2>> to</FONT> <BR><FONT size=2>> >
>RFC822. This is an exclusionary requirement in that other
</FONT><BR><FONT size=2>> standards may</FONT> <BR><FONT size=2>> >
not</FONT> <BR><FONT size=2>> > >be used. Also, Note 4 of the
BNF definition of the </FONT><BR><FONT size=2>> H323-URL clearly</FONT>
<BR><FONT size=2>> states</FONT> <BR><FONT size=2>> > >that that
the H323-URL is *not* compatible with RFC822.</FONT> <BR><FONT size=2>>
> ></FONT> <BR><FONT size=2>> > >Therefor, I propose that the
H323-URL cannot be coded into </FONT><BR><FONT size=2>> the email-ID</FONT>
<BR><FONT size=2>> for</FONT> <BR><FONT size=2>> > >alias address
because of compatibility problems.</FONT> <BR><FONT size=2>> >
></FONT> <BR><FONT size=2>> > >Bob</FONT> <BR><FONT size=2>>
> ></FONT> <BR><FONT size=2>> >
>------------------------------------------------------------------</FONT>
<BR><FONT size=2>> > >Robert Callaghan</FONT> <BR><FONT size=2>>
> >Siemens Enterprise Networks</FONT> <BR><FONT size=2>> >
>Tel: +1.561.923.1756 Fax: +1.561.923.1403</FONT> <BR><FONT size=2>>
> >Email: Robert.Callaghan@ICN.Siemens.com</FONT> <BR><FONT size=2>>
>
>------------------------------------------------------------------</FONT>
<BR><FONT size=2>> > ></FONT> <BR><FONT size=2>> ></FONT>
<BR><FONT size=2>> </FONT><BR><FONT size=2>>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</FONT>
<BR><FONT size=2>> For help on this mail list, send "HELP ITU-SG16" in a
message to</FONT> <BR><FONT size=2>> listserv@mailbag.intel.com</FONT>
<BR><FONT size=2>> </FONT></P></BLOCKQUOTE></BODY></HTML>