Hi Lance,
> On 19 Jul 2015, at 00:26, Lance Stout <[email protected]> wrote: > > Looking at the diff, I noticed a change that violates core RFC 6120. > > Namely: > > <iq from='[email protected]/orchard' > id='zid615d9' > to='[email protected]/balcony' > type='set'> > <jingle xmlns='urn:xmpp:jingle:1' sid='a73sjjvkla37jfea'/> > <conference-info xmlns="urn:ietf:params:xml:ns:conference-info" > entity="xmpp:[email protected]/orchard" > state="full" > version="1"> > ... > </conference-info> > </iq> > > Including two elements like that in an IQ is not allowed. > > > > I would think that the more appropriate format would be to use a Jingle > session-info update: > > <iq from='[email protected]/orchard' > id='zid615d9' > to='[email protected]/balcony' > type='set'> > <jingle xmlns='urn:xmpp:jingle:1' sid='a73sjjvkla37jfea' > action='session-info'> > <conference-info xmlns="urn:ietf:params:xml:ns:conference-info" > entity="xmpp:[email protected]/orchard" > state="full" > version="1"> > ... > </conference-info> > </jingle> > </iq> > Good catch! IIRC I talked about this with Emil back in the day, but it might have been lost in transit while I revived the changes. I’ll dig a bit and see if we ended up having something different and get back to you. Cheers, -- Saúl Ibarra Corretgé AG Projects
signature.asc
Description: Message signed with OpenPGP using GPGMail
