Notes for WIDEX at IETF 66
as reported by Vlad Stirbu, Vlad.Stirbu@nokia.com

HTTP binding

Ted Hardie: one REX document from the server but is this true for the renderer also?
Dave Raggett: yes a continous POST from the Renderer
TH: no need to to the same in both direction. one xml from the server and many small requests from the renderer.

Lisa: ADs don't feel that the proposed extensions are not in line with the way HTTP was intended to be extended
TH: extend HTTP with mime types. spend time to bulett proof of this HTTP binding. solve the issues with HTTP nature before pushing forward. http might not be the way forward to pass beyond ajax. problems with deep inspection proxies that inspect http post.

DW: parallel with SIP on symmetric HTTP
TH: HTTP is stateless and you need to layer state over http.

REX Status

TH: 

I Petterson: some interoperability problems might appear with event packaging if one widex element makes assumptions about the other end.


Situation on W3C REX and influence on us

Ted has filed a 3rd party IPR declaration.

WG to review the IPR disclosures from FT and think about how they affect us.



SIP Binding

not to pursue at this time.