Subject: RE: [mediactrl] Review Comments: sip-control-framework-00 and ivr-control-package-00

From: "Chris Boulton" <[email-masked]>
Date: Mon, 6 Feb 2006 11:24:51 GMT

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<font size=3
face="Times New Roman"> 

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial'>Please see our review comments on
these two IDs (control-framework-00 and ivr-control-package-00).

<font size=3 color=navy
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] HI Adnan – many thanks or the review. 
More in-line.

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Chris.

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'> 

<font size=3
face="Times New Roman"> 

<font size=3
face="Times New Roman"> 

<font size=3
face=Arial>draft-boulton-sip-control-framework-00

<font size=3
face="Times New Roman"> 

<font size=2
face=Arial>General Comments:

<span
style='font-size:10.0pt;font-family:Arial'>    In general we
agree with the approach taken in this ID to allow

<span
style='font-size:10.0pt;font-family:Arial'>    media control
interface to be transport independent. This ID does

<span
style='font-size:10.0pt;font-family:Arial'>    seem to support
this framework effectively for TCP, however, there

<span
style='font-size:10.0pt;font-family:Arial'>    are a few issues
we'd like to point out or request clarification with

<span
style='font-size:10.0pt;font-family:Arial'>    respect to SIP.
These items are identified below.

<span
style='font-size:10.0pt;font-family:Arial'>1. The control framework focuses on
establishing a control channel

<span
style='font-size:10.0pt;font-family:Arial'>    over TCP,
however, it does not seem to describe if its the intention

<span
style='font-size:10.0pt;font-family:Arial'>    of this
specification to allow SIP to be negotiated as the transport as well.

<span
style='font-size:10.0pt;font-family:Arial'>    Ie. using the
existing SIP methods for exchange of control and events

<span
style='font-size:10.0pt;font-family:Arial'>    to and from the
media server. 

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] that is primarily because it is not our
intention for this framework.  The framework proposes a generic (not media
server specific) solution that is designed to leverage SIP for it’s
intended purpose (media Session Initiation) for the creation of a reliable
command set exchange.

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<span
style='font-size:10.0pt;font-family:Arial'>2. This ID defines how to create the
intial control channel (tcp), and

<span
style='font-size:10.0pt;font-family:Arial'>    subsequent
transaction exchanges are also defined above tcp,

<span
style='font-size:10.0pt;font-family:Arial'>    eg: control cmds,
responses, reports, etc. However, support for an

<span
style='font-size:10.0pt;font-family:Arial'>    interface between
client and server based on SIP, where re-use of

<span
style='font-size:10.0pt;font-family:Arial'>    of many of the
existing SIP methods (such as options, subscribe, and

<span
style='font-size:10.0pt;font-family:Arial'>    notify,
etc) is also required. It seems that over time, this ID may have

<span
style='font-size:10.0pt;font-family:Arial'>    to re-invent the
mechanisms already available in SIP. For this reason

<span
style='font-size:10.0pt;font-family:Arial'>    alone, allowing
SIP as negotiated transport (in addition to tcp) should

<span
style='font-size:10.0pt;font-family:Arial'>    also be
supported.

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] OK – I am afraid that I don’t quite
see the necessity for using SIP?  Take a look at how the SIMPLE guys
designed MSRP for instant messaging.  Many problems were identified with
using the SIP MESSAGE method for transporting content.  To name but a few
we have 1) SIP fragmentation problem, the fact that default is UDP for SIP,
potential traversal of SIP proxies for every message.  We have already discussed
the use of OPTIONS for discovery + had a detailed debate about using
SUBSCRIBE/NOTIFY for events.  As this is an 00 version we are happy to
continue such debates but for earlier versions we made the call that they would
be carried over the new channel.  I definitely don’t get the need
for control commands as well – what is the point of having a ‘control’
channel.  Why have 2 mechanisms?

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<span
style='font-size:10.0pt;font-family:Arial'>3. Server capabilities discovery
(packages and revisions) requires 

<span
style='font-size:10.0pt;font-family:Arial'>    further discussion
and updates. Hopefully future revisions of this

<span
style='font-size:10.0pt;font-family:Arial'>    ID can elaborate
on this aspect.

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] Definitely.

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<span
style='font-size:10.0pt;font-family:Arial'>4. The ID requires use of SIP
extensions (requires header and additional

<span
style='font-size:10.0pt;font-family:Arial'>    SDP parameters),
however a SIP service context could also be used

<span
style='font-size:10.0pt;font-family:Arial'>    to establish a
control channel. This approach may be simpler

<span
style='font-size:10.0pt;font-family:Arial'>    not requiring
sip/sdp extensions. Was this approach taken into

<span
style='font-size:10.0pt;font-family:Arial'>    consideration ?

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial'>5. Client/Server interfaces may be
required in both directions or in just a

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    single
direction, depending on the nature and requirements of the packages 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    which
use this control framework. The control framework appears not to

<span
style='font-size:10.0pt;font-family:Arial'>    support such a
model of transport negotiation. Perhaps I've mis-read

<span
style='font-size:10.0pt;font-family:Arial'>    this, please
clarify.

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] take a look at section 9.2. 

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<span
style='font-size:10.0pt;font-family:Arial'>(detailed section by section comments
on the control framework ID 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> are included at the
end of this email)

<font size=3
face="Times New Roman"> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[Chris Boulton] I’m going to hand over to Scott to
respond to the IVR package section.  I will cover the detailed review at
the end of this mail as I revise the doc soon and post additional comments for
discussion in separate mails.  Thanks again for the detailed review.

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'> 

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Chris.

<span
style='font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'> 

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<font size=3
face="Times New Roman"> 

<font size=3
face=Arial>draft-boulton-ivr-control-package-00

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<font size=2
face=Arial>General Comments:

<span
style='font-size:10.0pt;font-family:Arial'>    The IVR package
ID, in its reliance on VoiceXML and parts of CCXML, is

<span
style='font-size:10.0pt;font-family:Arial'>    not suitable for
media server ivr controls, for several reasons, many of

<span
style='font-size:10.0pt;font-family:Arial'>    which have
already been discussed in earlier threads on this list.

<span
style='font-size:10.0pt;font-family:Arial'>    We'd like to
reiterate some of these issues in our review comments

<span
style='font-size:10.0pt;font-family:Arial'>    as well.

<span
style='font-size:10.0pt;font-family:Arial'>1. The ivr-control-packge (VXML) is
very well suited for application logic and

<span
style='font-size:10.0pt;font-family:Arial'>    is not well
suited towards providing general purpose and granular enough 

<span
style='font-size:10.0pt;font-family:Arial'>    media processing
controls.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>2. VXML is also quite burdensome,
from a processing perspective. Most of

<span
style='font-size:10.0pt;font-family:Arial'>    the application
processing logic would still reside within the application server.

<span
style='font-size:10.0pt;font-family:Arial'>    So having to
carry the burden of VXML but only using some small parts of

<span
style='font-size:10.0pt;font-family:Arial'>    of the language
for real media processing does not seem to fit the model

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    requiring
clear separation between application servers and media servers.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>3. The media processing interfaces
for IVR and Conferencing have already been 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    well
specified by the M* <span
style='font-size:10.0pt;font-family:Arial'>specifications, so
replacing these with VXML, or even

<span
style='font-size:10.0pt;font-family:Arial'>    sub-sections of
VXML and CCXML, does not bring any new value.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>4. The flexibility in invoking vxml
dialogs is also supported by the M* specifications,

<span
style='font-size:10.0pt;font-family:Arial'>    (ie: using
application/vxml+xml) where VXML may be required for some reason.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    However,
this does not imply that the standard interface to media server

<span
style='font-size:10.0pt;font-family:Arial'>    is VXML; ie it's
an exception (for sake of flexibility) rather than the rule.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>5. The event exchange mechanism (via
namelists etc) in VXML is between the

<span
style='font-size:10.0pt;font-family:Arial'>    VXML application
and the HTTP servers. However, using the ivr control package

<span
style='font-size:10.0pt;font-family:Arial'>    as media server
control language, the event exchange and control flow mechanism

<span
style='font-size:10.0pt;font-family:Arial'>    is now also
between the media server and application server, in addition to with

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'>    the HTTP
server. This complicates and blurs the architecture unnecessarily.

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>Thanks

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:Arial'>Adnan Saleem

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<font size=2
color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'>P.S. Specific review comments/questions on<font
size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:blue'> <font size=2
color=black face="Trebuchet MS"><span style='font-size:10.0pt;font-family:"Trebuchet MS";
color:black'>draft-boulton-sip-control-framework-00

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Specific comments<font size=2
color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:blue'> <span
style='font-size:10.0pt;font-family:Arial;color:black'>(mostly questions and
suggestions), by section:

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 3.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
Client informs server of package(s) it supports,<font size=2
color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:blue'> <span
style='font-size:10.0pt;font-family:Arial;color:black'>(<example-package>),

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
however, in some cases the server may need to supply supported packages

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
to client, and then client selects one. Perhaps both mechanisms

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>         should
be supported, similar to sdp offer/answer model ?

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            2.
What happens if server does not support supplied example-package,

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
ie; is the connection still established and the pacakge can be

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
further re-negotiated ? Can packages be added anytime during

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
lifetime of connection ?

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            3.
Can multiple packages be requested by client? I assume so,

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
and this mechanism should be described.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            5.
A consistent package naming scheme along with revisioning should

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
be described.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            4.
Is the control channel limited to the 'negotiated' package, ie

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
if over the established control channel, a request is issued

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
for an unstated package which the server supports, then should

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
the server reject such requests<font size=2 color=blue
face=Arial> <font
size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'>? 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            5.
Q: would it not be possible to avoid mandating use of SDP.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
Ie. connection established could be done with or without SDP,

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
by using additional header fields of INV. Avoiding a forced SDP

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
use would make the connection establishment transaction

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
flow simpler.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            6.
This section describes behaviour of client when it receives the

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
200 OK from server, but it does not describe the expected

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
behaviour when the server receives INV or other SIP methods

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
over this SIP dialog.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 4.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
Although this section is left for future update, using P2P

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
type mechanism might be useful to consider for locating

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
external servers

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            2.
Also, location of external servers should be based on capabilities

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
of external servers; ie: locate based on what packages are

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
required by client and supported by servers (including package

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
version ids).

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>      3. Load related
server location would be useful also. Ie. servers

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>         could
report load index, and then client could select one with

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
lowest current load index.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 5.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
<port> field indicates which port the client is willing to

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
accept a connection, but it's not clear why a "valid port range"

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>         is
required when client does not wish to accept incomming

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
connection and why this is a "range" rather then a specific

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
port number.<span
style='font-size:10.0pt;font-family:Arial;color:blue'> <font
size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'>(I guess the range could be <font size=2
color=black face="Trebuchet MS"><span style='font-size:10.0pt;font-family:"Trebuchet MS";
color:black'>limited to single item)

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            2.
Some control packages would require the client to accept incoming

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
requests or events, while other control packages may not.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
So if the client does not provide appropriate <port> when a

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
control package requires it, then there should be mechanism

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
to resolve this condition or reject the connection setup.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 5.1

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
not clear what is being stated in this section. should be

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
reworded.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 6.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
A mechanism for defining and registering unique package tokens

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
should be described

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            2.
Revisions or versions of control packages should be taken into

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
consideration when client and server are discovering package

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
support by the server

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 7.1

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
Not clear on what are "all required manditory and optional

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
control framework headers" are. Clarification required here.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            2.
Content-type should be requried specifying a registered

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
MIME type

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            3.
5 sec timeout seems too low. Would recommend 15s.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            4.
A transaction timeout and retry mechanism is required on the

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
client side, with a sequence number to ensure transactions

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
are not incorrectly executed multiple times on the server

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            5.
Should consider making a statement about transaction id

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
uniqueness within the client, size and wraparound.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 7.1.2

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
Not sure but is it the purpose of continuous REPORT messages

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
(based on server specified timeout values) to ensure that

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
server has not encountered an error or to keep the session

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
alive in absence of traffic for a long period of time ?

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
(ie. is this mechanism for keep-alive control)

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 7.2

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
As the editor note indicates, I agree that ability to include

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
message body in Responses is very usefull and should be

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>        
included.
<span style='font-size:10.0pt;
font-family:Arial;color:blue'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Section 9.

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
several issues with control packages already stated earlier

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'> 

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>Remaining sections:

<p class=MsoPlainText style='margin-right:0cm;margin-bottom:3.0pt;margin-left:
36.0pt'><span style='font-size:10.0pt;
font-family:Arial;color:black'>            1.
no comments, as most of them are largely empty or incomplete

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<span
style='font-size:10.0pt;font-family:"Trebuchet MS"'> 

<font size=3
face="Times New Roman"> 

Information contained in this e-mail and any attachments are intended for the use of the addressee only, and may contain confidential information of Ubiquity Software Corporation. All unauthorized use, disclosure or distribution is strictly prohibited.  If you are not the addressee, please notify the sender immediately and destroy all copies of this email.  Unless otherwise expressly agreed in writing signed by an officer of Ubiquity Software Corporation, nothing in this communication shall be deemed to be legally binding. Thank-you