<!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@01C0141A.B243D8F0" 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: 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-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>Bob,</FONT></DIV><![if !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><!--[if supportFields]><span class=EmailStyle19><font
size=2 color="#993366" 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]--><!--[if supportFields]><span class=EmailStyle19><font
size=2 color="#993366" 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]--><![if !supportEmptyParas]><![endif]><![if !supportLists]>
<DIV><FONT face="Times New Roman" color=#993366 size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: #993366"></SPAN></FONT><FONT color=#993366><SPAN
style="COLOR: #993366; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT> </DIV>
<DIV><FONT color=#993366><SPAN
style="COLOR: #993366; mso-color-alt: windowtext"><o:p>HTML mail makes replying
hard.... or at least Outlook Express doesn't work real
well.</o:p></SPAN></FONT></DIV>
<DIV><FONT color=#993366><SPAN
style="COLOR: #993366; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=Section1>
<P class=MsoNormal><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>
<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; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l4 level1 lfo2; 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">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><SPAN class=EmailStyle18><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">The
port should be specified as belonging the specified
protocol.</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>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">What do you
mean? Are you in favor of this:</SPAN></FONT><FONT color=navy><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><A
href="mailto:paulej@packetizer.com:1719">h323:paulej@packetizer.com:1719</A></SPAN></FONT><FONT
color=navy><SPAN style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">or do you want
this:</SPAN></FONT><FONT color=navy><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><A
href="mailto:paulej@packetizer.com;proto=ras,port=1719">h323:paulej@packetizer.com;proto=ras,port=1719</A><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><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 prefer choice one in the base
specification.<o:p></o:p></SPAN></FONT></SPAN></P></DIV></BLOCKQUOTE>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000></FONT></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000>I also prefer the first choice.</FONT></SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; 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>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<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: black; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l5 level1 lfo3; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><![if !supportLists]><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><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: 75.75pt; BORDER-LEFT: black; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l5 level1 lfo3; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><![if !supportLists]><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><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>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><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>
<P class=MsoNormal style="tab-stops: list .5in"><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="tab-stops: list .5in"><SPAN class=EmailStyle19><FONT
face=Arial color=#993366 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="tab-stops: list .5in"><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></BLOCKQUOTE>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000>My view on this is that the endpoint should have one of two
options:</FONT></SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000>1) It contacts the endpoint directly, or</FONT></SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000>2) It sends to URL to the GK for
resolution</FONT></SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">This suggests to me that we're
taking the wrong approach with this "proto" extension and we should just remove
it.</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">Perhaps we should replace
"proto" with "mode". We could have this format:</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy">h323:paulej@packetizer.com;mode=direct</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">or</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy">h323:paulej@packetizer.com;mode=indirect
(default if "mode" is not specified)</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">The "direct" mode would
suggest that the endpoint is reachable directly with the specified URL. In
other words, a Setup message may be sent directly to the endpoint at
"packetizer.com" (the endpoint would have to resolve the address to get an 'A'
record from DNS).</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">The "indirect" mode would
suggest that the endpoint should send the query to it's GK. The Gatekeeper
would then perform a DNS query looking for the Gatekeeper associated with
"packetizer.com" or would send the query to its Border Element for
resolution.</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">If it finds a Gatekeeper for
the given domain, it would then send an LRQ to the Gatekeeper.</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">If it finds a Border Element
for the given domain, the Border Element would send an AccessRequest to the
Border Element.</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"></SPAN></FONT> </P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face=Arial color=#000000
size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy">I believe Annex O should
define the procedure for how we define and specify Gatekeepers and Border
Elements stored in DNS.</SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; 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>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Or how about this--
make it easier for those not familiar with the protocols. Specify the
type of device:</SPAN></FONT><FONT color=navy><SPAN
style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> <A
href="mailto:h323:paulej@packetizer.com;device=gk">h323:paulej@packetizer.com;dev=gk</A></SPAN></FONT><FONT
color=navy><SPAN style="COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Or dev=ep or
dev=be<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><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]
This was a mistake on my part.<SPAN style="mso-spacerun: yes"> </SPAN>I
meant annex-k for the API link.<SPAN style="mso-spacerun: yes">
</SPAN>We don’t need a device field.<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=navy size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy"> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The software/hardware
can then determine the protocol. This might be the best solution, since
"h323" is supposed to represent the protocol in the first
place.</SPAN></FONT><FONT color=navy><SPAN
style="COLOR: navy"><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=navy size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy"> <o:p></o:p></SPAN></FONT></P>
<DIV class=Section1
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; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l3 level1 lfo4; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><![if !supportLists]><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><SPAN class=EmailStyle18><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">The
specification of “ras” belonging to LRQ is limiting.<SPAN
style="mso-spacerun: yes"> </SPAN>For me, the first contact is over ARQ
to my GK.<SPAN style="mso-spacerun: yes"> </SPAN>Then the GK may use LRQ
or any other means to resolve the address.<SPAN
style="mso-spacerun: yes"> </SPAN>From this view point, there is no
difference between “ras” and “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>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">If we just specify
the type of device the URL is associated with it will resolve this
issue.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><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]
The type of device for what: the endpoint for the contact point. <SPAN
style="mso-spacerun: yes"> </SPAN>I don’t think the URL should change the
normal procedure of an endpoint using the GK, if one is present. <SPAN
style="mso-spacerun: yes"> </SPAN>Annex-g should never be used by and
endpoint (see annex g). <SPAN style="mso-spacerun: yes"> </SPAN>The only
applies to GKs or boarder elements.<o:p></o:p></SPAN></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><SPAN
class=EmailStyle18><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><![if !supportEmptyParas]><![endif]> </SPAN></FONT></SPAN><SPAN
class=EmailStyle18><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: #993366; 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=EmailStyle19><FONT
face=Arial color=#993366 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>
<DIV class=Section1
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; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l7 level1 lfo6; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><![if !supportLists]><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><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>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><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=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial; mso-color-alt: windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><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><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></BLOCKQUOTE>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN
style="mso-spacerun: yes"><FONT color=#000000 size=4> 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. Sound good?</FONT></SPAN></SPAN></P>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><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>
<P class=MsoNormal style="tab-stops: list .5in"><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></BLOCKQUOTE><![if !supportEmptyParas]><![endif]>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#993366 size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"><FONT
color=#000000 size=3>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.</FONT></SPAN></FONT></SPAN></P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN> </P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; 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></P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN> </P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">Should
we re-think the "case insensitive" issue?</SPAN></FONT></SPAN></P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN> </P>
<P class=MsoNormal dir=ltr style="tab-stops: list .5in"><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN><SPAN
class=EmailStyle19><FONT face=Arial color=#000000 size=3><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN> </P>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<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: black; TEXT-INDENT: -0.25in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none; mso-list: l6 level1 lfo9; tab-stops: list 1.0in; mso-border-left-alt: solid black 1.5pt; mso-padding-alt: 0in 0in 0in 4.0pt"><![if !supportLists]><SPAN
class=EmailStyle18><FONT face=Symbol color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol; mso-bidi-font-size: 12.0pt">·<FONT
face="Times New Roman" size=1><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></FONT></SPAN></FONT></SPAN><![endif]><SPAN class=EmailStyle18><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt">I see
no need for the URL ARQ be resolved to a URL.<SPAN
style="mso-spacerun: yes"> </SPAN>It could be resolved to any alias
using the alias replacement rules.<SPAN style="mso-spacerun: yes">
</SPAN>The means that an URL in and ARQ could be replaced with a partyNumber
(last paragraph).</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="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT
face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">You lost me
here. If you are saying that there's no need to put a partyNumber inside
a URL or that the GK should be allowed to map the URL alias to a partyNumber
when returning an ACF, I agree. Otherwise, I need some
clarification.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="tab-stops: list .5in"><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]
It is possible to pass a URL to a GK and have it respond with a partyNumber
under the rules of alias substitution by the GK.<SPAN
style="mso-spacerun: yes"> </SPAN>Then the SETUP is sent using the
partyNumber alias not the url
alias.<o:p></o:p></SPAN></FONT></SPAN></P></BLOCKQUOTE>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; tab-stops: list .5in"><FONT face="Times New Roman"
color=navy size=3><SPAN style="FONT-SIZE: 12pt; COLOR: navy"><FONT face=Arial
color=#000000>Agreed. This should be done when the endpoint indicates that
it can map aliases.</FONT></SPAN></FONT></P><!--[if supportFields]><span
class=EmailStyle18><font size=2 color=navy 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]--><!--[if supportFields]><span
class=EmailStyle18><font size=2 color=navy 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]-->
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; 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>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0px; tab-stops: list .5in"><FONT
face="Times New Roman" color=navy size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: navy"><o:p>Paul</o:p></SPAN></FONT></P>
<P class=MsoNormal dir=ltr
style="MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0px; 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></BODY></HTML>