Lance Stout | 23 Apr 00:28 2014
Picon

Fwd: New Version Notification for draft-ietf-xmpp-websocket-06.txt

FYI

This version addresses feedback from Ben Campbell:

- Changed the use of <invalid-namespace/> error to a MUST instead of SHOULD
- Specify that TLS MUST be enabled at the WebSocket layer, if used
- Clarify that a server can close the connection with see-other-uri at any time
- Clarify that the closing process mirrors RFC 6120
- Reword the considerations when using XEP-0198 to be clearer
- Explicitly state that whitespace keepalives MUST NOT be used (based on the framing restrictions; use
Ping or Stream Management instead)
- Note that ping control frames MAY be used, but might not be accessible in all cases

Begin forwarded message:

> From: internet-drafts <at> ietf.org
> Subject: New Version Notification for draft-ietf-xmpp-websocket-06.txt
> Date: April 22, 2014 at 3:22:20 PM PDT
> To: "Lance Stout" <lance <at> andyet.net>, Eric Cestari <eric <at> cstar.io>, "Eric Cestari"
<eric <at> cstar.io>, "Jack Moffitt" <jack <at> metajack.im>, Lance Stout <lance <at> andyet.net>, Jack Moffitt <jack <at> metajack.im>
> 
> 
> A new version of I-D, draft-ietf-xmpp-websocket-06.txt
> has been successfully submitted by Lance Stout and posted to the
> IETF repository.
> 
> Name:		draft-ietf-xmpp-websocket
> Revision:	06
> Title:		An XMPP Sub-protocol for WebSocket
> Document date:	2014-04-22
(Continue reading)

internet-drafts | 23 Apr 00:22 2014
Picon

I-D Action: draft-ietf-xmpp-websocket-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF.

        Title           : An XMPP Sub-protocol for WebSocket
        Authors         : Lance Stout
                          Jack Moffitt
                          Eric Cestari
	Filename        : draft-ietf-xmpp-websocket-06.txt
	Pages           : 14
	Date            : 2014-04-22

Abstract:
   This document defines a binding for the XMPP protocol over a
   WebSocket transport layer.  A WebSocket binding for XMPP provides
   higher performance than the current HTTP binding for XMPP.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-xmpp-websocket-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-websocket-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
(Continue reading)

Ben Campbell | 21 Apr 23:15 2014

Comments on draft-ietf-xmpp-websocket-05

Here's some just under the wire comments on draft-ietf-xmpp-websocket-05. It mostly looks fine, but I
have a few comments, mainly about some 2119 language, and about connection managers:

-- 3.1: "During the WebSocket handshake, the client MUST include the Sec-WebSocket-Protocol header in
its handshake, and the value |xmpp| MUST be included in the list of protocols. "

Isn't the "MUST include Sec-WebSocket-Protocol" part really a requirement of WebSocket in general? That
is, is it in any way specific to XMPP?, if it's simply a repetition of a general WebSocket requirement, we
should not state it normatively here. ( In any case, it seems to be implied by the "value MUST include xmpp"  part.)

-- 3.2.2: "...  MUST close the stream with an error, which SHOULD be <invalid-namespace> ..."

Why SHOULD and not MUST? Are there reasonable circumstances to choose something else? Can you offer
guidance on why one might choose something else, and what impact that would have?

-- 3.6:

Do we have to worry about half-closes situations where the peer does not respond in a timely manner? How
about glare?

How does the XEP-0198 guidance after the figure interact with the guidance saying the closing party SHOULD
close the stream? That would seem to imply one SHOULD NOT keep the stream alive, since that would involve
not closing the stream.

-- 3.6.1: Can a server (or connection manager) redirect the client at any time?

-- 3.8:

First paragraph says clients can use extra whitespace, but goes onto say you SHOULD use WebSocket ping
control frames. Does that mean we are recommending _against_ using the extra whitespace? If so, I'd avoid
(Continue reading)

internet-drafts | 21 Apr 02:31 2014
Picon

I-D Action: draft-ietf-xmpp-websocket-05.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF.

        Title           : An XMPP Sub-protocol for WebSocket
        Authors         : Lance Stout
                          Jack Moffitt
                          Eric Cestari
	Filename        : draft-ietf-xmpp-websocket-05.txt
	Pages           : 14
	Date            : 2014-04-20

Abstract:
   This document defines a binding for the XMPP protocol over a
   WebSocket transport layer.  A WebSocket binding for XMPP provides
   higher performance than the current HTTP binding for XMPP.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-xmpp-websocket-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-websocket-05

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
(Continue reading)

Lance Stout | 20 Apr 01:04 2014
Picon

Fwd: New Version Notification for draft-ietf-xmpp-websocket-03.txt

FYI

There are no protocol-affecting changes in this update. It re-organizes the text to give an up-front
description of the framing process, and other editorial cleanup.

Begin forwarded message:

> From: internet-drafts <at> ietf.org
> Subject: New Version Notification for draft-ietf-xmpp-websocket-03.txt
> Date: April 19, 2014 at 4:00:43 PM PDT
> To: "Lance Stout" <lance <at> andyet.net>, Eric Cestari <eric <at> cstar.io>, "Eric Cestari"
<eric <at> cstar.io>, "Jack Moffitt" <jack <at> metajack.im>, Lance Stout <lance <at> andyet.net>, Jack Moffitt <jack <at> metajack.im>
> 
> 
> A new version of I-D, draft-ietf-xmpp-websocket-03.txt
> has been successfully submitted by Lance Stout and posted to the
> IETF repository.
> 
> Name:		draft-ietf-xmpp-websocket
> Revision:	03
> Title:		An XMPP Sub-protocol for WebSocket
> Document date:	2014-04-19
> Group:		xmpp
> Pages:		13
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-xmpp-websocket-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-xmpp-websocket-03
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-websocket-03
> 
> Abstract:
(Continue reading)

Ben Campbell | 7 Apr 23:29 2014

WGLC of draft-ietf-xmpp-websocket-02

This is a Working Group Last Call of draft-ietf-xmpp-websocket-02. The draft is available at the
following URL:

http://tools.ietf.org/html/draft-ietf-xmpp-websocket-02

The WGLC will conclude on 21 April, 2014. Please send your comments to the authors and the XMPP mailing list.

Thanks!

Ben.
Peter Saint-Andre | 7 Apr 00:08 2014

Fwd: [Stox] WGLC for draft-ietf-stox-groupchat-04

FYI.

-------- Original Message --------
Subject: [Stox] WGLC for draft-ietf-stox-groupchat-04
Date: Sun, 6 Apr 2014 20:20:39 +0200
From: Yana Stamcheva <yana <at> jitsi.org>
To: stox <at> ietf.org

The editors and the chairs believe that the following draft is now ready 
and hereby start a 2-week Working Group Last Call for:

draft-ietf-stox-groupchat-04 : 
http://tools.ietf.org/html/draft-ietf-stox-groupchat-04 (Last updated on 
2014-03-25)

The WGLC ends on April 21, 2014.

Please review the document and bring any remaining issues, or issues 
whose resolution is not satisfactory, to the attention of the Working 
Group on this list before April 21.

If after reviewing the document you find it complete and do not have any 
comments, please send a note to that effect as well!

Regards,
Yana Stamcheva & Markus Isomaki
_______________________________________________
stox mailing list
stox <at> ietf.org
https://www.ietf.org/mailman/listinfo/stox
(Continue reading)

Ben Campbell | 27 Mar 05:29 2014

Draft Minutes from London

Hi,

The _draft_ minutes from the XMPP meeting in London are available at
http://www.ietf.org/proceedings/89/minutes/minutes-89-xmpp . Please send any corrections to the
chairs as soon as possible.

Thanks!

Ben.
Ben Campbell | 17 Mar 20:50 2014

WGLC of draft-ietf-xmpp-6122bis-11

This is a Working Group Last Call of draft-ietf-xmpp-6122bis-11. The draft is available at the following URL:

http://tools.ietf.org/html/draft-ietf-xmpp-6122bis-11

The WGLC will conclude on 31 March, 2014. Please send your comments to the authors and the XMPP mailing list.

Thanks!

Ben.
Peter Saint-Andre | 10 Mar 21:04 2014

XMPP over WebSocket schemas

As noted during the working group session last week, there's a small 
copy-and-paste error in the schema for the <open/> element: the 
see-other-uri attribute is allowed only on the <close/> element. Thus...

OLD

      <xs:element name='open'>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base='empty'>
              <xs:attribute name='from' type='xs:string'
                            use='optional'/>
              <xs:attribute name='id' type='xs:string'
                            use='optional'/>
              <xs:attribute name='see-other-uri' type='xs:anyURI'
                            use='optional'/>
              <xs:attribute name='to' type='xs:string'
                            use='optional'/>
              <xs:attribute name='version' type='xs:decimal'
                            use='optional'/>
              <xs:attribute ref='xml:lang'
                            use='optional'/>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>

NEW

      <xs:element name='open'>
(Continue reading)

Joe Hildebrand (jhildebr | 8 Mar 12:11 2014
Picon

Comments on draft-alkemade-xmpp-iq-validation-00

(no hats)

Section 1: suggest s/it was found//

Before Section 4: suggest adding some examples in a new section.  Good
iq/response, spoofed response with different from (perhaps followed by
real response to make it clear), unexpected 'from' from the server

Section 4: suggest switching the order of 4.1 and 4.2.  current section
4.1 is an edge case, leading with the core mechanism is more understandible

Section 4.1: quote 6120 and 3920 directly if possible.

Section 4.2: we had lots of discussion over "unique".  We'll likely want
some flavor of that discussion in the final text.  For the MUST ignore
text, can the client log an error or notify the user?

Section 6: we'll likely want some security analysis here.

May a server perform this tracking too, and reject things that look like
attacks?

This doc is a good start.  I think we should adopt it into the working
group immediately.

--

-- 
Joe Hildebrand

Gmane