<!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 content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3013.2600" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK
href="cid:filelist.xml@01C0136A.7C41C4C0" 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: Tahoma;
}
@font-face {
font-family: Cló Gaelach \(Twomey\);
}
P.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; 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-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoAutoSig {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoAutoSig {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
SPAN.EmailStyle17 {
COLOR: navy; 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]--><!doctype HTML></HEAD>
<BODY bgColor=white lang=EN-US link=blue style="tab-interval: .5in" vLink=blue>
<DIV><FONT color=#000080 face=Arial>Bob and others,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#000080 face=Arial>Please see my comments inline:</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px"><![if !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]>
<DIV class=Section1>
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The
default protocol should be mandatory.<SPAN style="mso-spacerun: yes">
</SPAN>In this case, flexibility kills
interworking.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></DIV></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>Agreed.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">The
port should be specified as belonging the specified
protocol.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>What do you mean? Are you in favor of this:</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2><A
href="mailto:h323:paulej@packetizer.com:1719">h323:paulej@packetizer.com:1719</A></FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>or do you want this:</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2><A
href="mailto:h323:paulej@packetizer.com;proto=ras,port=1719">h323:paulej@packetizer.com;proto=ras,port=1719</A></FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; 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.<o:p></o:p></SPAN></FONT></SPAN>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; 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<o:p></o:p></SPAN></FONT></SPAN> <SPAN class=EmailStyle17><FONT
color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">For
protocol, use “h225ar” or “h323ar” instead of
“annex-g”.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>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:</FONT><FONT face=Arial size=2> lrq, setup,
ar (for AccessRequest)? So rather than specifying a protocol, we specify
the message to use?</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>Or how about this-- make it easier for those not familiar with
the protocols. Specify the type of device:</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2> <A
href="mailto:h323:paulej@packetizer.com;device=gk">h323:paulej@packetizer.com;dev=gk</A></FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>Or dev=ep or dev=be</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>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.</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; 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”.<o:p></o:p></SPAN></FONT></SPAN>
</LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>If we just specify the type of device the URL is associated
with it will resolve this issue.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">Do
we need annex-f to be specified as a protocol? <SPAN
style="mso-spacerun: yes"> </SPAN>It appears to me that we have this
need.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>We could add "dev=a-set" as an option (audio SET), but I'm not
fond of that idea. I suppose it might be useful in the enterprise
environment where one may, indeed, have all SET devices and calls are placed
directly between each other.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; 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.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>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. </FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>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?</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">If
nesting is supported, how is this defined or used? <SPAN
style="mso-spacerun: yes"> </SPAN>If not, then there is no
nesting.<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>I don't envision nesting one address type inside the URL, if
that's what you are asking. You convinced me before that, if the user
alias is not sufficient, then other URL schemes should suffice, such as "tel"
for reaching phone numbers.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt">When
this URL is used in the url-id field, is the URL name inclusion
mandatory?<SPAN style="mso-spacerun: yes"> </SPAN>If not, what is the
default?<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>I would say "yes" and double "yes". If the scheme name is not
present, one could not determine that it was the H323-URL. We definitely
want to allow the usage of "http" or "tel" or even "sip". I can image an
H.323 endpoint that gets launched and the only address on hand is <A
href="mailto:sip:paulej@packetizer.com">sip:paulej@packetizer.com</A> and the
Gatekeeper must route the call to an IP gateway than can provide interworking
functions.</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<UL style="mso-margin-top-alt: 0in" type=disc>
<LI class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN
class=EmailStyle17><FONT color=navy face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt; 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).<o:p></o:p></SPAN></FONT></SPAN> </LI></UL></BLOCKQUOTE>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>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.</FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"><FONT
face=Arial size=2>Paul<![if !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><!--[if supportFields]><span class=EmailStyle17><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=EmailStyle17><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]--><![if !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]></FONT></DIV>
<DIV class=MsoNormal
style="COLOR: navy; mso-list: l0 level1 lfo1; tab-stops: list .5in"> </DIV></BODY></HTML>