1. Jonathan Rosenberg dynamicsoft
App Interaction
Jonathan Rosenberg
dynamicsoft

2. Changes
Substantial restructuring to reflect its role as a normative document
No longer using grid parameter to correlate SUBSCRIBE with dialog
Doesn’t work with forking
Requires a different grid in every dialog always
Applications provide an app name to the application using From display name
Making sure we have coverage from call-info features

3. Open Issue
How to match REFER to dialog the component is associated with?
Send REFER on same dialog
Yuck – many known problems
Some kind of explicit correlator
Header, parameter, etc.
No correlator
Web app won’t automatically close when call ends (unless using some kind of client side scripting)
Proposal:

4. Reg Event Have found a bug in XML extensibility during time in RFC-ed
Need to provide fix to rfc-ed
Basic fix allows extensions to contact

5. Example
<?xml version="1.0"?>    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"                 version="0" state="full">      <registration id="as9"                    state="active">        <contact id="76" state="active" event="registered"                 duration-registered="7322"                 q="0.8" params="newparam=foo;audio">                  </contact>      </registration>    </reginfo>

6. Further Question: Unknown Params
Existing reg-event has a params XML attribute
Contains any other contact params for which another XML representation is not defined params=“audio="true&quot”
Question: Now that we can extend contact, do we want this?

7. Example Extension
<?xml version="1.0"?>    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"             xmlns:callerprefs="urn:ietf:params:xml:ns:callerprefs"                 version="0" state="full">      <registration id="as9"                    state="active">        <contact id="76" state="active" event="registered"                 duration-registered="7322"                 q="0.8" params="newparam=foo;audio">                     <callerprefs:audio/>           <unknown-param name="newparam>foo</unknown-param>        </contact>      </registration>    </reginfo>

8. Options
Keep params element, its ugly but works – we don’t want to change at this stage
Define an <unknown-boolean>, <unknown-int>, etc. elements and allow as Contact children
If a real extension is defined, data could be in two places
Use XML extensions for unknown data
Reg event notifications won’t contain data not understood by the server
Similar to discussions in SIMPLE on prescaps

9. Proposal: Option 3 Cleanest solution
Servers shouldn’t send data they don’t understand