<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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=windows-1252">
<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@01C01725.75EA1DC0" 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:Compatibility>
<w:ForgetLastTabAlignment/>
<w:DoNotUseHTMLParagraphAutoSpacing/>
</w:Compatibility>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
font-family: Cló Gaelach \(Twomey\);
}
@font-face {
font-family: Tahoma;
}
@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
}
</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>Bob,</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I think we're agreement on all points below, but I still
have concerns about the case issue.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I whole heartedly agree that using case insensitive names
is ideal-- it reduces a lot of confusion for the user. However, I know
that 'A' and 'a' are the same and it's very easy to write software to do the
same. One easy way to do that is to use a function like "tolower()" in C
when before storing/comparing values. However, is there a Unicode
equivalent? Such a function would have to be aware of the complete set
Unicode characters and know which ones are the upper/lower case versions of the
others. Is that something we can assume that people will implement or do
you think imposing such a requirement will be met with resistance?</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>My biggest fear is that some GKs will properly handle all
characters and most will not.</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=Robert.Callaghan@icn.siemens.com
href="mailto:Robert.Callaghan@icn.siemens.com">Callaghan, Robert</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=paulej@packetizer.com
href="mailto:paulej@packetizer.com">'Paul E. Jones'</A> ; <A
title=ITU-SG16@mailbag.cps.intel.com
href="mailto:ITU-SG16@mailbag.cps.intel.com">Mailing list for parties
associated with ITU-T Study Group 16</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=orit@radvision.com
href="mailto:orit@radvision.com">Orit Levin</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, September 05, 2000 10:37
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: Re: H.323 URL
Specification</DIV>
<DIV><BR></DIV>
<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">Paul,<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">I
agree that HTML can be a problem, that I know of.<SPAN
style="mso-spacerun: yes"> </SPAN>I only replied to 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><SPAN class=EmailStyle20><FONT face=Arial color=#003300
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">See
below.<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">Bob<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><!--[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 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt">------------------------------------------------------------------</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=MsoNormal><FONT face="Cló Gaelach (Twomey)" color=green size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: green; FONT-FAMILY: 'Cló Gaelach \(Twomey\)'">Robert
Callaghan<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><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=MsoNormal><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=MsoNormal><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><A
href="mailto:Robert.Callaghan@ICN.Siemens.com">Robert.Callaghan@ICN.Siemens.com</A></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=MsoNormal><FONT face="Times New Roman" color=#003300 size=1><SPAN
style="FONT-SIZE: 8pt; COLOR: #003300; mso-bidi-font-size: 12.0pt">------------------------------------------------------------------</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=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]--><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 style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face=Tahoma color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma">-----Original
Message-----<BR style="mso-special-character: line-break"><![if !supportLineBreakNewLine]><BR
style="mso-special-character: line-break"><![endif]></SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face="Times New Roman" color=navy size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy"> <o:p></o:p></SPAN></FONT></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 115.5pt; BORDER-LEFT: medium none; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·</SPAN></FONT></SPAN><SPAN
class=EmailStyle18><FONT color=navy size=1><SPAN
style="FONT-SIZE: 7pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">
</SPAN></FONT></SPAN><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">For
protocol, use “h225rs” or “h323rs” instead of “ras”.<SPAN
style="mso-spacerun: yes"> </SPAN>This controls the confusion with the
dial-in protocol know as RAS.</SPAN></FONT></SPAN><FONT color=navy><SPAN
style="COLOR: navy"> </SPAN></FONT><SPAN class=EmailStyle18><FONT face=Arial
color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 115.5pt; BORDER-LEFT: medium none; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·</SPAN></FONT></SPAN><SPAN
class=EmailStyle18><FONT color=navy size=1><SPAN
style="FONT-SIZE: 7pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">
</SPAN></FONT></SPAN><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">For
protocol, use “h225cs” or “h323cs” instead of “q931”.<SPAN
style="mso-spacerun: yes"> </SPAN>This controls the confusion with real
Q.931</SPAN></FONT></SPAN><FONT color=navy><SPAN style="COLOR: navy">
</SPAN></FONT><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">For
protocol, use “h225ar” or “h323ar” instead of
“annex-g”.</SPAN></FONT></SPAN><FONT color=navy><SPAN style="COLOR: navy">
</SPAN></FONT><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P></DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 75.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I really like the use
of "ras", even though there are conflicts in other contexts. However, I
agree that q931 is not really ideal. How about these: lrq, setup,
ar (for AccessRequest)? So rather than specifying a protocol, we specify
the message to use?<o:p></o:p></SPAN></FONT></P></DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">[RWC]
I definitely don’t like q931 and annex-g.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"> <o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">As a
secondary question, how is an endpoint to handle ras and annex-g?<SPAN
style="mso-spacerun: yes"> </SPAN>Obtain the information directly or go
through the GK?<SPAN style="mso-spacerun: yes"> </SPAN>This should be
stated.<o:p></o:p></SPAN></FONT></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face=Arial color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial">My view on this is
that the endpoint should have one of two options:</SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face=Arial color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial">1) It contacts the
endpoint directly, or</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face=Arial color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial">2) It sends
to URL to the GK for resolution</SPAN></FONT><FONT face=Arial
color=black><SPAN
style="COLOR: black; FONT-FAMILY: Arial; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><SPAN class=EmailStyle20><FONT
face=Arial color=#003300 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">[RWC]
<SPAN style="mso-spacerun: yes"> </SPAN>I agree with this as long as GK
resolution is performed via normal RAS.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 115.5pt; BORDER-LEFT: medium none; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·</SPAN></FONT></SPAN><SPAN
class=EmailStyle18><FONT color=navy size=1><SPAN
style="FONT-SIZE: 7pt; mso-ascii-font-family: 'Times New Roman'; mso-hansi-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'">
</SPAN></FONT></SPAN><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">Is
“escaped” limited to two hexdigits?<SPAN style="mso-spacerun: yes">
</SPAN>How does one escape to Unicode characters?<SPAN
style="mso-spacerun: yes"> </SPAN>This should be
possible.</SPAN></FONT></SPAN><FONT color=navy><SPAN style="COLOR: navy">
</SPAN></FONT><SPAN class=EmailStyle18><FONT face=Arial color=navy
size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P></DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 75.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">It has never been
proposed to use unicode, so, yes, the "escaped" set is limited to two bytes
(the data type is actually IA5String). However, we could add a statement
that says that the entire H323-URL is UTF-8 encoded. In that way,
characters from other languages could converted to UTF-8 and then escaped
where necessary.</SPAN></FONT><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P></DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">[RWC]
We cannot have UTF-8 in the domain part of the URL.<SPAN
style="mso-spacerun: yes"> </SPAN>I would like to see UTF-8 in the
user part of the name through the use of escaped
characters.<o:p></o:p></SPAN></FONT></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face=Arial color=black size=4><SPAN
style="FONT-SIZE: 13.5pt; COLOR: black; FONT-FAMILY: Arial"><SPAN
style="mso-spacerun: yes"> </SPAN>So perhaps the user part of the name
should be defined as a UTF-8 encoded string of characters, with the only
restrictions being that "%" and "@" must be escaped if they exist in the user
part.<SPAN style="mso-spacerun: yes"> </SPAN>Sound
good?</SPAN></FONT><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 75.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">However, this does
bring to my attention the fact that the character set is now very
limited. Any character can be represented, but it would be nice to allow
François to enter his name like that, rather than Fran%83ois. What
character set limitations does IA5 impose on us? Can we use any binary
value between 0-255 for each character? If so, I would also like to
propose that we change the "unreserved" production to allow any character
between 0-255, excluding % and @ (since those have special meanings).
What do you think?<o:p></o:p></SPAN></FONT></P></DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; MARGIN-LEFT: 39.75pt; BORDER-LEFT: medium none; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; tab-stops: list .5in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">[RWC]
0-255 is not sufficient.<o:p></o:p></SPAN></FONT></SPAN></P></DIV>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: Arial; mso-ansi-font-size: 12.0pt">I
believe that the above mentioned change (re: UTF-8) will give us the means of
allowing the full range of unicode characters for the user name
part.</SPAN></FONT></SPAN><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">However,
this raises another question: how do we enforce the rule that names are not
case sensitive. That would suggest that for any given character set
within unicode, the manufacturer will have to know which characters are the
upper and lower case ranges. Is this desirable to recommend? I
like names that are not case sensitive, but this might be overly complex to
try to do. It would make internationalization of a Gatekeeper, for
example, much more difficult than it is today-- I suspect some vendors will
not go through the effort.</SPAN></FONT></SPAN><FONT color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">Should
we re-think the "case insensitive" issue?</SPAN></FONT></SPAN><SPAN
class=EmailStyle19><FONT face=Arial color=black size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal style="tab-stops: list .5in"><SPAN class=EmailStyle20><FONT
face=Arial color=#003300 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">[RWC]
<SPAN style="mso-spacerun: yes"> </SPAN>I don’t see case insensitive as
being in conflict with UTF-8.<SPAN style="mso-spacerun: yes">
</SPAN>Part of the characters as defined as case oriented and some are
not.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=black><SPAN
style="COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in; tab-stops: list .5in"><FONT
face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT><FONT
color=navy><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>