[Standards-JIG] Re: proto-JEP: Proposed Stream Feature Improvements

[Alexander Gnauck]

looks ok to me,.
in the first example the <starttls/> from the client is missing

C: <stream:stream
      xmlns='jabber:client'
      xmlns:stream='http://etherx.jabber.org/streams'
      to='example.com'
      version='1.0'>

S: <stream:stream
      xmlns='jabber:client'
      xmlns:stream='http://etherx.jabber.org/streams'
      id='c2s_123'
      from='example.com'
      version='1.0'>

S: <stream:features>
      <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
        <required/>
      </starttls>
    </stream:features>

C: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

S: <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>


JEP Editor schrieb:
> The JEP Editor has received a proposal for a new JEP.
> 
> Title: Proposed Stream Feature Improvements
> 
> Abstract: This document proposes improvements to the XML stream features definition for inclusion in the specification that supersedes RFC 3920.
> 
> URL: http://www.jabber.org/jeps/inbox/streamfeatures.html
> 
> The Jabber Council will decide within 7 days (or at its next meeting) whether to accept this proposal as an official JEP.
> 
>