
From stpeter@stpeter.im  Tue Sep  1 12:52:24 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A6C03A6BED for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 12:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gmDfc8UiW622 for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 12:52:23 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id F370F3A68C1 for <xmpp@ietf.org>; Tue,  1 Sep 2009 12:52:22 -0700 (PDT)
Received: from dhcp-64-101-72-216.cisco.com (dhcp-64-101-72-216.cisco.com [64.101.72.216]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 435A24007B for <xmpp@ietf.org>; Tue,  1 Sep 2009 13:46:08 -0600 (MDT)
Message-ID: <4A9D79FE.4090208@stpeter.im>
Date: Tue, 01 Sep 2009 13:46:06 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [xmpp] 3920bis: architecture
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2009 19:52:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've rewritten the Architecture section of 3920bis, which has always
struck me as fairly weak. Here is the result from my working copy
(further tweaks are possible). The most significant references are to:

EMAIL-ARCH = D. Crocker, RFC 5598: Internet Mail Architecture

REST = R. Fielding, "Architectural Styles and the Design of
Network-based Software Architectures",
http://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf

***

2.  Architecture

   XMPP provides a technology for the asynchronous, end-to-end exchange
   of structured data by means of direct, persistent XML streams among a
   distributed network of globally-addressable, presence-aware clients
   and servers.  Because this architectural style involves ubiquitous
   knowledge of network availability and a conceptually unlimited number
   of concurrent information transactions in the context of a given
   client-to-server or server-to-server session, we could label it
   "Availability for Concurrent Transactions" (ACT) to distinguish it
   from the "Representational State Transfer" [REST] architectural style
   familiar from the World Wide Web. Although the architecture of XMPP
   is similar in important ways to that of the email network (see
   [EMAIL-ARCH]), it introduces several modifications to facilitate
   near-real-time communication.  The salient features of this ACTive
   architectural style are as follows.

2.1.  Global Addresses

   As with email, XMPP uses globally-unique addresses (based on the
   Domain Name System) in order to route and deliver messages over the
   network.  All XMPP entities are addressable on the network, most
   particularly clients and servers but also various additional services
   that can be accessed by clients and servers.  In general, server
   addresses are of the form "domain.tld" (e.g., "im.example.com"),
   accounts hosted at a server are of the form "localpart@domain.tld"
   (e.g., "juliet@im.example.com"), and a particular connected device or
   resource that is currently authorized for interaction on behalf of an
   account is of the form "localpart@domain.tld/resource" (e.g.,
   "juliet@im.example.com/balcony").  XMPP addresses are defined under
   Section 3.

2.2.  Presence

   XMPP includes the ability for an entity to advertise its network
   availability or "presence" to other entities.  Such availability for
   communication is signalled end-to-end via dedicated communication
   primitives in XMPP (the <presence/> stanza).  Although knowledge of
   network availability is not strictly necessary for the exchange of
   XMPP messages, it facilitates real-time interaction because the
   originator of a message can know before initiating communication that
   the intended recipient is online and available.  XMPP presence is
   defined in [xmpp-im].

2.3.  Persistent Streams

   Availability for communication is also built into point-to-point
   connections (e.g., a discrete client-to-server or server-to-server
   connection) through the use of direct, persistent XML streams between
   the entity that initiated the connection (either a client or a
   server) and the entity that received the connection (a server).  Thus
   either party to a stream knows that it can immediately push data to
   the other party for immediate routing or delivery.  XML streams are
   defined under Section 5.

2.4.  Structured Data

   The basic unit of meaning in XMPP is not an XML stream (which simply
   provides the transport for point-to-point communication) but an XML
   "stanza", which is essentially a fragment of XML that is sent over a
   stream.  The root element of a stanza includes routing attributes
   (such as "from" and "to" addresses) and the child elements of the
   stanza contain a payload for delivery to the intended recipient.  XML
   stanzas are defined under Section 9.

2.5.  Distributed Network

   In practice, XMPP consists of a network of clients and servers that
   inter-communicate (however, communication between any two given
   deployed servers is strictly OPTIONAL).  Thus, for example, the user
   <juliet@im.example.com> associated with the server <im.example.com>
   might be able to exchange messages, presence, and other structured
   data with the user <romeo@example.net> associated with the server
   <example.net>.  This pattern is familiar from messaging protocols
   that make use of global addresses, such as the email network (see
   [SMTP] and [EMAIL-ARCH]).  As a result, end-to-end communication in
   XMPP is logically peer-to-peer but physically client-to-server-to-
   server-to-client, as illustrated in the following diagram.

     example.net ---------------- im.example.com
        |                                |
        |                                |
   romeo@example.net           juliet@im.example.com


      Note: Architectures that employ XML streams (Section 5) and XML
      stanzas (Section 9) but that establish peer-to-peer connections
      directly between clients using technologies based on [LINKLOCAL]
      have been deployed, but such architectures are not described in
      this specification and are best described as "XMPP-like"; for
      details, see [XEP-0174].  In addition, XML streams can be
      established end-to-end over any reliable transport, including
      extensions to XMPP itself; however, such methods are out of scope
      for this specification.

2.6.  Server

   A SERVER is an entity whose primary responsibilities are to:

   o  Manage XML streams (Section 5) with local clients and deliver XML
      stanzas (Section 9) to those clients over the negotiated streams.
   o  Subject to local service policies on server-to-server
      communication, manage XML streams (Section 5) with foreign servers
      and route XML stanzas (Section 9) to those servers over the
      negotiated streams.

   Depending on the application, the secondary responsibilities of an
   XMPP server can include:


   o  Storing XML data that is used by clients (e.g., contact lists for
      users of XMPP-based instant messaging and presence applications as
      defined in [xmpp-im]); in this case, the relevant XML stanza is
      handled directly by the server itself on behalf of the client and
      is not routed to a foreign server or delivered to a local entity.
   o  Hosting local services that also use XMPP as the basis for
      communication but that provide additional functionality beyond
      that defined in this document or in [xmpp-im]; examples include
      multi-user conferencing services as specified in [XEP-0045] and
      publish-subscribe services as specified in [XEP-0060].

2.7.  Client

   A CLIENT is an entity that establishes an XML stream with a server by
   authenticating using the credentials of a local account and that then
   completes resource binding (Section 8) in order to enable delivery of
   XML stanzas via the server to the client.  A client then uses XMPP to
   communicate with its server, other clients, and any other accessible
   entities on a network.  Multiple clients can connect simultaneously
   to a server on behalf of a local account, where each client is
   differentiated by the resource identifier portion of an XMPP address
   (e.g., <localpart@domain/home> vs. <localpart@domain/work>), as
   defined under Section 3 and Section 8.

***

/psa

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqdef4ACgkQNL8k5A2w/vyDdACfcmH5Nwu0xgxWSnZ6vRc2aFve
t3AAn1cav13ygChU0CdvJBofgJ22OAp5
=leFa
-----END PGP SIGNATURE-----

From dave@cridland.net  Tue Sep  1 13:04:09 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 214243A6CBD for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 13:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0J0zH8P-DHWu for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 13:04:08 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 40E223A68A6 for <xmpp@ietf.org>; Tue,  1 Sep 2009 13:04:08 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <Sp1-QgBOpx34@peirce.dave.cridland.net>; Tue, 1 Sep 2009 21:04:18 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <4A9D79FE.4090208@stpeter.im>
In-Reply-To: <4A9D79FE.4090208@stpeter.im>
MIME-Version: 1.0
Message-Id: <23259.1251835461.954649@puncture>
Date: Tue, 01 Sep 2009 21:04:21 +0100
From: Dave Cridland <dave@cridland.net>
To: Peter Saint-Andre <stpeter@stpeter.im>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: Re: [xmpp] 3920bis: architecture
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2009 20:04:09 -0000

On Tue Sep  1 20:46:06 2009, Peter Saint-Andre wrote:
>    "Availability for Concurrent Transactions" (ACT) to distinguish  
> it
>    from the "Representational State Transfer" [REST] architectural  
> style
>    familiar from the World Wide Web. Although the architecture of  
> XMPP

I do like that. I feel guilty for promoting yet more cheesy contrived  
acronyms, but I do like that.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From k.i.smith@gmail.com  Tue Sep  1 23:28:07 2009
Return-Path: <k.i.smith@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F7E23A680A for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 23:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRoKPi0WkI6k for <xmpp@core3.amsl.com>; Tue,  1 Sep 2009 23:28:06 -0700 (PDT)
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.211.174]) by core3.amsl.com (Postfix) with ESMTP id A1F5E3A67CC for <xmpp@ietf.org>; Tue,  1 Sep 2009 23:28:06 -0700 (PDT)
Received: by ywh4 with SMTP id 4so920824ywh.17 for <xmpp@ietf.org>; Tue, 01 Sep 2009 23:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=nX4VKQu1DqsDZmzx4ZoxMMEw7lfCojhjnRg23u4R7TA=; b=VGRSxuBUTjnvb49iD84KKSpDBnwgIonXFQyGdzFrgKL2y5L29g9lOsHB0223ogzPAw 3vkBzuH7eUT9F2ye2eNzCjnJ1yL9dF138KtkH3OogT3TlqTHh6qGLeJd1ODx8RwYVWnv wzJhDTjNAri9R+TUS3CHRj0xEY0MNHOb2ycKM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=gXOYSexEV2aqByzNN1x9NPoB6aEXp9sm+fK7T87fDfQ9443/Kz5Xm8mX94MDIYLy6L 2OHyUNmOESh3Yefz1pbOswEVC3yrrXtahDm+XrxGgNoTTYBKOdRejepJ1SHEWc47O1Kb 4Nf+kQH/U018g41pGL+3WGdqIQmtQVHlGAa/4=
MIME-Version: 1.0
Sender: k.i.smith@gmail.com
Received: by 10.100.17.14 with SMTP id 14mr8566277anq.163.1251872827979; Tue,  01 Sep 2009 23:27:07 -0700 (PDT)
In-Reply-To: <23259.1251835461.954649@puncture>
References: <4A9D79FE.4090208@stpeter.im> <23259.1251835461.954649@puncture>
Date: Wed, 2 Sep 2009 07:27:07 +0100
X-Google-Sender-Auth: 50cd6ecbe5b283f2
Message-ID: <f5aae3ec0909012327x1c180dd2yc8ddbb6631548d0a@mail.gmail.com>
From: Kevin Smith <kevin@kismith.co.uk>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] 3920bis: architecture
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: kevin@kismith.co.uk
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2009 06:28:07 -0000

On Tue, Sep 1, 2009 at 9:04 PM, Dave Cridland<dave@cridland.net> wrote:
>> =A0 "Availability for Concurrent Transactions" (ACT) to distinguish it
>> =A0 from the "Representational State Transfer" [REST] architectural styl=
e
>> =A0 familiar from the World Wide Web. Although the architecture of XMPP
> I do like that. I feel guilty for promoting yet more cheesy contrived
> acronyms, but I do like that.


I feel no such guilt; it looks good. Thanks Peter.

/K

From stpeter@stpeter.im  Wed Sep  9 14:50:14 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93EC53A68B4 for <xmpp@core3.amsl.com>; Wed,  9 Sep 2009 14:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9Hh4iKUWpTX for <xmpp@core3.amsl.com>; Wed,  9 Sep 2009 14:50:12 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 56BB53A680F for <xmpp@ietf.org>; Wed,  9 Sep 2009 14:50:12 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 648604007B for <xmpp@ietf.org>; Wed,  9 Sep 2009 15:50:45 -0600 (MDT)
Message-ID: <4AA82334.8070207@stpeter.im>
Date: Wed, 09 Sep 2009 15:50:44 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: [xmpp] pipelining during stream setup
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2009 21:50:14 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a forward from an older discussion on the standards@xmpp.org
list. I will probably look into this for the -02 version of 3920bis and
might post about it again soon.

/psa

- -------- Original Message --------
Subject: Re: [Standards] mobile optimizations (was: Re:  Google Androïd
SDK not XMPP compliant ?)
Date: Mon, 18 Feb 2008 13:33:13 +0000
From: Tony Finch <dot@dotat.at>
Reply-To: XMPP Extension Discussion List <standards@xmpp.org>
To: XMPP Extension Discussion List <standards@xmpp.org>
References:
<6ca210320802140055m73133123t8dcb67e84644207@mail.gmail.com>
<14867.1202999962.276834@peirce.dave.cridland.net>
<47B49FD5.6050609@stpeter.im>

How important is session startup latency for mobile XMPP? The motivation
for SMTP quickstart was to make sending email faster. Sending email is
quite an interactive action (though good client software can hide the
latency). The equivalent in XMPP is sending a message on a connection
that's already open. Session startup, on the other hand, is tied in with
things like associating with an access point or starting a GPRS
connection, doing DNS lookups, and all sorts of slow things before XMPP
can get going.

With that in mind, if it is worth optimising XMPP startup, then it's
probably worth taking the simplest possible approach which does not
require any stunt buffer handling. From the specification writer's point
of view, it amounts to adding some text to 3920bis which explains where
XMPP is asynchronous / pipelinable and where it is not. If you allow
pipelining of startup utterances other than transitions between XML and
TLS, and SASL exchanges, you can get something like the following. By
startup utterances, I mean that client and server can say <stream> in
either order, and the client can cache the server's <features/> and
proceed with <starttls/> and <auth/> on the assumption that the
<features/> have not changed.


C: TCP SYN
S: TCP SYN/ACK
C: TCP ACK

client does not need to wait for server's <stream> header, since its
stream header is the same regardless. in principle it should wait for the
server's <features/> before issuing <starttls/> but (a) it can cache the
<features/>, (b) unexpected lack of TLS support is something worth warning
the user about, (c) the protocol allows it to recover gracefully from the
error.

C: XMPP1 <stream>
          <starttls/>

server has to wait for client syn

S: XMPP1 <stream>
          <features/>
          <proceed/>

layering switch here, so there must be a round trip delay. there are two
kinds of TLS negotiation, without and with a session cache hit.

without

C: TLS hello
S: TLS stuff
C: TLS again
S: TLS finish

with

C: TLS hello
S: TLS stuff
C: TLS finish

to properly benefit from session cache optimisation, you need to let
either the server or the client start the stream first. that is, the
following two utterances can be in either order. the server and the client
send these as soon as the TLS layer returns from the handshake, and with a
good TLS implementation one of these will piggy-back on the last TLS
finish packet.

with a TLS session cache hit the packets come in this order:

C: XMPP2 <stream>
          <auth/>

S: XMPP2 <stream>
          <features/>

the client now has to wait for the server's reply, which in this case
should come immediately. (without a TLS session cache there's another
round trip delay.) the server can re-start its stream immediately, since
it is always the last to speak in SASL. when the client gets the SASL
response it can re-start its stream (and XML parser).

S: XMPP2  <success/>
   XMPP3 <stream>
          <features/>

C: XMPP3 <stream>
          <iq><bind/></iq>

client must wait for <iq> reply before it can do anything useful

S: XMPP3 <iq><bind><jid/></bind></iq>

Without a TLS session cache hit, we get 6RTT before useful data can be
transferred:

C: TCP SYN
S: TCP SYN/ACK
C: TCP ACK
   TCP XMPP1 <stream><starttls/>
S: TCP XMPP1 <stream><features/><proceed/>
C: TCP XMPP1 TLS hello
S: TCP XMPP1 TLS stuff
C: TCP XMPP1 TLS again
S: TCP XMPP1 TLS finish
   TCP XMPP1 TLS XMPP2 <stream><features/>
C: TCP XMPP1 TLS XMPP2 <stream><auth/>
S: TCP XMPP1 TLS XMPP2 <success/>
   TCP XMPP1 TLS XMPP2 XMPP3 <stream><features/>
C: TCP XMPP1 TLS XMPP2 XMPP3 <stream><iq><bind/></iq>
S: TCP XMPP1 TLS XMPP2 XMPP3 <iq><bind><jid/></bind></iq>

With a TLS session cache hit, we get 5RTT:

C: TCP SYN
S: TCP SYN/ACK
C: TCP ACK
   TCP XMPP1 <stream><starttls/>
S: TCP XMPP1 <stream><features/><proceed/>
C: TCP XMPP1 TLS hello
S: TCP XMPP1 TLS stuff
C: TCP XMPP1 TLS finish
   TCP XMPP1 TLS XMPP2 <stream><auth/>
S: TCP XMPP1 TLS XMPP2 <stream><features/><success/>
   TCP XMPP1 TLS XMPP2 XMPP3 <stream><features/>
C: TCP XMPP1 TLS XMPP2 XMPP3 <stream><iq><bind/></iq>
S: TCP XMPP1 TLS XMPP2 XMPP3 <iq><bind><jid/></bind></iq>

Note that all the layers come in contiguous lumps. Stunt buffering is
required if they get interleaved in the packet trace, e.g.

C: TCP ACK
   TCP XMPP1 <stream><starttls/>
   TCP XMPP1 TLS hello
S: TCP XMPP1 <stream><features/><proceed/>
   TCP XMPP1 TLS stuff
C: TCP XMPP1 TLS finish
   TCP XMPP1 TLS XMPP2 <stream><auth/>
   TCP XMPP1 TLS XMPP2 XMPP3 <stream><iq><bind/></iq>
S: TCP XMPP1 TLS XMPP2 <stream><features/><success/>
   TCP XMPP1 TLS XMPP2 XMPP3 <stream><features/><iq><bind><jid/></bind></iq>

I have not treated SASL in detail above. In particular I haven't examined
challenge/response mechanisms. In the last trace above, the XMPP2 layer
startup and the SASL negotiation get interleaved. I think this is be OK
since SASL is framed by XMPP2, not layered on top like TLS.

Tony.
- --
f.a.n.finch  <dot@dotat.at>  http://dotat.at/
VIKING NORTH UTSIRE: NORTHWEST 5 OR 6, DECREASING 4. MODERATE OR ROUGH.
OCCASIONAL RAIN. MODERATE OR GOOD, OCCASIONALLY POOR.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqoIzQACgkQNL8k5A2w/vw1owCdEfu5Nwl1dPfkKGdBUHwwiB1w
ZwYAn3pMcAezRgpUlIPKU1jpDGimyIPS
=Z5ru
-----END PGP SIGNATURE-----

From dmeyer@sachmittel.de  Thu Sep 10 02:05:17 2009
Return-Path: <dmeyer@sachmittel.de>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A15A3A698F for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 02:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.32
X-Spam-Level: 
X-Spam-Status: No, score=-1.32 tagged_above=-999 required=5 tests=[AWL=-0.929,  BAYES_20=-0.74, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DWACORmqS91 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 02:05:16 -0700 (PDT)
Received: from mail.bitschubser.de (mail.bitschubser.de [78.47.214.53]) by core3.amsl.com (Postfix) with ESMTP id 4FA133A62C1 for <xmpp@ietf.org>; Thu, 10 Sep 2009 02:05:16 -0700 (PDT)
Received: from phex.sachmittel.de (dmeyer.openvpn.informatik.uni-bremen.de [134.102.217.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bitschubser.de (Postfix) with ESMTP id 4EC8010211A; Thu, 10 Sep 2009 11:05:47 +0200 (CEST)
Received: by phex.sachmittel.de (Postfix, from userid 1000) id 1B86DE050; Thu, 10 Sep 2009 11:05:46 +0200 (CEST)
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4AA82334.8070207@stpeter.im>
From: Dirk Meyer <dmeyer@tzi.de>
In-Reply-To: <4AA82334.8070207@stpeter.im> (Peter Saint-Andre's message of "Wed\, 09 Sep 2009 15\:50\:44 -0600")
Organization: Universitaet Bremen, Germany
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
Date: Thu, 10 Sep 2009 11:05:46 +0200
Message-ID: <87ocpjw4np.fsf@phex.sachmittel.de>
Lines: 42
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] pipelining during stream setup
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 09:05:17 -0000

Tony Finch wrote:
> With that in mind, if it is worth optimising XMPP startup, then it's
> probably worth taking the simplest possible approach which does not
> require any stunt buffer handling. 

Well, maybe we want to merge TLS and client authentication into one step
without a stream restart. We had some discussion about it some time ago,
but maybe we want to consider it for a fast restart.

C: <stream>

S:  <stream>
      <features>
        <starttls/>
        <tlssrp/>
      </features>
     </stream>

C: <tlsstrp/>

S: <proceed/>

Now we use TLS-SRP with server certificates and the client using user
name and password for authentication:

C: TLS hello, request SRP, JID
S: Accept SRP, send certificate
C: Proof identity, TLS finish
S: TLS finish

After that the server continues with sending a new set of features:

S: <features/>

This get's rid of the two stream restarts for TLS and SASL and SASL
itself.


Dischi

-- 
Never put off until tomorrow what you can do the day after.

From stpeter@stpeter.im  Thu Sep 10 11:41:15 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EAAE3A6869 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 11:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.639
X-Spam-Level: 
X-Spam-Status: No, score=-2.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kwoOtYHtbAFn for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 11:41:13 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id D2D0B3A69FF for <xmpp@ietf.org>; Thu, 10 Sep 2009 11:41:12 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 57B8C40D09 for <xmpp@ietf.org>; Thu, 10 Sep 2009 12:41:33 -0600 (MDT)
Message-ID: <4AA9485C.7020803@stpeter.im>
Date: Thu, 10 Sep 2009 12:41:32 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 18:41:15 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I propose adding the following informational (and self-explanatory)
paragraph to the section on TCP Binding in 3920bis...

4.6.  Reliability

   The use of long-lived TCP connections in XMPP implies that the
   sending of XML stanzas over XML streams can be unreliable, since the
   parties to a long-lived TCP connection might not discover a
   connectivity disruption in a timely manner.  At the XMPP application
   layer, long connectivity disruptions can result in undelivered
   stanzas.  Although the core XMPP technology defined in this
   specification does not contain features to overcome this lack of
   reliability, an XMPP extension for doing so is defined in [XEP-0198].


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqpSFwACgkQNL8k5A2w/vyymgCg+HKmS9xK9T2dbdGy93aKZhAo
Vv4AnRcVtNBmXv0ncitf/UOSskyFdq0W
=fsnz
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Thu Sep 10 12:10:49 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 382103A6A6F for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 12:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level: 
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjOT6aMD9Mzl for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 12:10:47 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id B3A323A6A45 for <xmpp@ietf.org>; Thu, 10 Sep 2009 12:10:47 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 283D740D09 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:11:16 -0600 (MDT)
Message-ID: <4AA94F52.2050802@stpeter.im>
Date: Thu, 10 Sep 2009 13:11:14 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [xmpp] 3920bis: wildcards in certs
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 19:10:49 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In a recent message on the vcarddav list, Alexey Melnikov noted what
seems to be a change of IETF policy regarding the inclusion of wildcards
in certificates:

"Based on the discussion during an IESG telechat several ADs agreed that
f* wildcards shouldn't be allowed anymore. So, the document should say
that it complies with RFC 2818, except for f* type wildcards are not
allowed. (wildcards in the leftmost label are still allowed). This is
consistent with the advice from RFC 5280."

http://www.ietf.org/mail-archive/web/vcarddav/current/msg01138.html

Although this preference has not yet been codified anywhere as far as I
know, I tend to agree with it. Therefore I would propose that we change
the following paragraph in Section 15.2.1.1.2 (!) of 3920bis...

From:

   The dNSName MAY contain the wildcard character '*'.  The wildcard
   character applies only to the left-most domain name component or
   component fragment and matches any single component or component
   fragment.  For instance, a dNSName of *.example.com matches
   foo.example.com but not bar.foo.example.com or example.com itself;
   similarly, a dNSName of im*.example.net matches im1.example.net and
   im2.example.net but not chat.example.net or example.net itself.

To:

   The dNSName MAY contain the wildcard character '*'.  The wildcard
   character applies only to the left-most domain name component and
   matches any single component (thus a dNSName of *.example.com matches
   foo.example.com but not bar.foo.example.com or example.com itself).
   The wildcard character is not allowed in component fragments (thus a
   dNSName of im*.example.net is not allowed and shall not be taken to
   match im1.example.net and im2.example.net).

Objections?

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqpT1IACgkQNL8k5A2w/vzcjwCbB0qE/mFrYF4Ro/bgEIfz/Yq7
BTEAnRj5zAozx9tD8X2iNsJCaHJuYsQt
=jUx5
-----END PGP SIGNATURE-----

From florian.zeitz@gmx.de  Thu Sep 10 12:24:13 2009
Return-Path: <florian.zeitz@gmx.de>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B29A03A67E2 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 12:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id adEXXevJpwdq for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 12:24:12 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 74E093A697E for <xmpp@ietf.org>; Thu, 10 Sep 2009 12:23:22 -0700 (PDT)
Received: (qmail invoked by alias); 10 Sep 2009 19:23:56 -0000
Received: from xdsl-87-78-44-76.netcologne.de (EHLO [192.168.0.38]) [87.78.44.76] by mail.gmx.net (mp052) with SMTP; 10 Sep 2009 21:23:56 +0200
X-Authenticated: #30932406
X-Provags-ID: V01U2FsdGVkX19HoDs/mydH+DEfFfO0XYCfYGufxMD+6VN+ztelXY 7ldcjg/EjYMjEh
Message-ID: <4AA9524B.9000206@gmx.de>
Date: Thu, 10 Sep 2009 21:23:55 +0200
From: Florian Zeitz <florian.zeitz@gmx.de>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
References: <4AA9485C.7020803@stpeter.im>
In-Reply-To: <4AA9485C.7020803@stpeter.im>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.5
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 19:24:14 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Saint-Andre wrote:
> I propose adding the following informational (and self-explanatory)
> paragraph to the section on TCP Binding in 3920bis...
> 
> 4.6.  Reliability
> 
>    The use of long-lived TCP connections in XMPP implies that the
>    sending of XML stanzas over XML streams can be unreliable, since the
>    parties to a long-lived TCP connection might not discover a
>    connectivity disruption in a timely manner.  At the XMPP application
>    layer, long connectivity disruptions can result in undelivered
>    stanzas.  Although the core XMPP technology defined in this
>    specification does not contain features to overcome this lack of
>    reliability, an XMPP extension for doing so is defined in [XEP-0198].
> 
> 

This sounds like a good idea to me.
I was wondering whether it might be a good idea to mention XEP-0184 too
though.
Possibly in a different context, maybe even in 3921bis.
It seems much more useful for the normal Instant Messaging case as long
as XEP-0198 is not widely deployed IMHO. OTOH not mentioning 184 might
be a way to increase 198 deployment...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqpUkEACgkQ0JXcdjR+9YQFEACgr1qPmYz+7rF5MysQ8RxAGOQX
RAoAnArNzDycnhxodKG1VX5TqXNiQOP4
=uZ7G
-----END PGP SIGNATURE-----

From justin@affinix.com  Thu Sep 10 13:10:44 2009
Return-Path: <justin@affinix.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBDD83A6A97 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sD0LGIrXPnNE for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:10:43 -0700 (PDT)
Received: from homiemail-a2.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by core3.amsl.com (Postfix) with ESMTP id B849D3A6AD3 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:10:43 -0700 (PDT)
Received: from localhost (andross.dreamhost.com [75.119.221.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTP id 2484ED26E7 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:11:11 -0700 (PDT)
From: Justin Karneges <justin@affinix.com>
To: xmpp@ietf.org
Date: Thu, 10 Sep 2009 13:11:10 -0700
User-Agent: KMail/1.9.10
References: <4AA9485C.7020803@stpeter.im> <4AA9524B.9000206@gmx.de>
In-Reply-To: <4AA9524B.9000206@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909101311.10962.justin@affinix.com>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 20:10:44 -0000

On Thursday 10 September 2009 12:23:55 Florian Zeitz wrote:
> I was wondering whether it might be a good idea to mention XEP-0184 too
> though.
> Possibly in a different context, maybe even in 3921bis.
> It seems much more useful for the normal Instant Messaging case as long
> as XEP-0198 is not widely deployed IMHO. OTOH not mentioning 184 might
> be a way to increase 198 deployment...

My (biased) opinion is that XEP-0184 should certainly not be suggested as a 
solution to basic delivery problems.  Let's encourage fixing that problem in 
the right place (XEP-0198, at the xmpp-core level).

XEP-0184 could be mentioned as a solution to certain special needs, such as 
the need to know 'when' (as opposed to 'if') a message was received by the 
final endpoint, or the need to send a message of high importance when the 
delivery capacity of the hops is not known or cannot be trusted.  But please, 
I don't think people should be implementing 184 to get around wi-fi drops, 
and we should be careful not to encourage or promote this.

-Justin

From zarevucky.jiri@gmail.com  Thu Sep 10 13:30:56 2009
Return-Path: <zarevucky.jiri@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00B393A6B92 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level: 
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vgqd64Ve7lE for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:30:55 -0700 (PDT)
Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com [209.85.220.217]) by core3.amsl.com (Postfix) with ESMTP id 0A1253A6AC5 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:30:54 -0700 (PDT)
Received: by fxm17 with SMTP id 17so390407fxm.37 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=NPV/tNYUecO4JgwuvDuWu2azcXKA13p6wuEwuoIuEIk=; b=itNSmySnD2/nh8g0w2tIYL0OH5dUKFglyqi3pqYK5SIoDZYvaTDp5ApA3UXiev2u1R +4cZbvoyza+irkf09sJdDWHoXujtiyHzBo+Au99p4it1FK347G5kCEdYS0JASjb8gSl9 wUQ4Hegfz0Gb3DtjEltq3CPrE7Z6N9XtPsiYo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=PCciQPcKxbthlJ1Zikt1U1WBoApN1NHWDs2Au09d2/klxz/7oTLd517CzhqLg+duPm 7lxsP6D7jPButOtTq4CXe3a1h8TuMcNkkxFfPaI0RTRJnyKoM2uTlIhsdAFPaHpaJCVa 2FBsNahy7zt8nWQVRbD5AK7H1UdtqAhOrbeRM=
Received: by 10.86.187.7 with SMTP id k7mr1593418fgf.30.1252614687451; Thu, 10 Sep 2009 13:31:27 -0700 (PDT)
Received: from ?10.10.10.20? ([94.229.94.1]) by mx.google.com with ESMTPS id 3sm112056fge.28.2009.09.10.13.31.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Sep 2009 13:31:26 -0700 (PDT)
Message-ID: <4AA9621C.6040009@gmail.com>
Date: Thu, 10 Sep 2009 22:31:24 +0200
From: =?UTF-8?B?SmnFmcOtIFrDoXJldsO6Y2t5?= <zarevucky.jiri@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: xmpp@ietf.org
References: <4AA9485C.7020803@stpeter.im>
In-Reply-To: <4AA9485C.7020803@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 20:30:56 -0000

On 09/10/2009 08:41 PM, Peter Saint-Andre wrote:
> I propose adding the following informational (and self-explanatory)
> paragraph to the section on TCP Binding in 3920bis...
>
> 4.6.  Reliability
>
>     The use of long-lived TCP connections in XMPP implies that the
>     sending of XML stanzas over XML streams can be unreliable, since the
>     parties to a long-lived TCP connection might not discover a
>     connectivity disruption in a timely manner.  At the XMPP application
>     layer, long connectivity disruptions can result in undelivered
>     stanzas.  Although the core XMPP technology defined in this
>     specification does not contain features to overcome this lack of
>     reliability, an XMPP extension for doing so is defined in [XEP-0198].
>
>    

Such note is a good idea, but I wouldn't address a specific XEP in an 
RFC document. Although unlikely, these can be obsoleted and replaced 
with new ones, while RFC is kind of long-lived and difficult to update. 
Also, there are more extensions that address reliability. I'd suggest 
changing the last sentence to something like this:

Although the core XMPP technology defined in this specification does not 
contain features to overcome this lack of reliability, XMPP extensions 
exist to rectify this problem (for example [XEP-0198]).


From fabio.forno@gmail.com  Thu Sep 10 13:33:25 2009
Return-Path: <fabio.forno@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643B73A6812 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMg8GaXo+mZE for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:33:24 -0700 (PDT)
Received: from mail-yx0-f200.google.com (mail-yx0-f200.google.com [209.85.210.200]) by core3.amsl.com (Postfix) with ESMTP id 714A43A6946 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:33:23 -0700 (PDT)
Received: by yxe38 with SMTP id 38so613686yxe.6 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:33:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IHeCXVGEIO/UjDvcw1vb515R12ja3E/NE/Azc53Uo1g=; b=HkI4LZ+t5Sv91W/DMYC7MUxJ077SbroWTIiUPtx7RJZHCzwYAYTjOl48gzMfPA7efS WmdX90mgamV9qtoFRJUZvAGykzK5LQck1ugBb0qVgZjE3G+s+TB6bEsKPl1TmyKCkAU7 tkfDRTkLee46mlJF1hBb8teeNM71atIJAsENo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dUJgG96RdHT0lwIMi35siq5E1fGjSSQ5t29Xs9DcBuvtTXh9Z+t1uTQJ9bE1vz+Xid lewHjVHGMRjsr/WKNsiHfLkhDn7UgguLYYuByJAoQl7L1wZnwbsfYXEQSyhlXnEHX025 XL5dvPv37Ylma6fp1Zf8d0rQxtqpqXbyswiEI=
MIME-Version: 1.0
Received: by 10.90.182.20 with SMTP id e20mr1120308agf.106.1252614833868; Thu,  10 Sep 2009 13:33:53 -0700 (PDT)
In-Reply-To: <200909101311.10962.justin@affinix.com>
References: <4AA9485C.7020803@stpeter.im> <4AA9524B.9000206@gmx.de> <200909101311.10962.justin@affinix.com>
Date: Thu, 10 Sep 2009 22:33:53 +0200
Message-ID: <2fd53c3a0909101333p748f12a1td985c4d4f371cae7@mail.gmail.com>
From: Fabio Forno <fabio.forno@gmail.com>
To: Justin Karneges <justin@affinix.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: xmpp@ietf.org
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 20:33:25 -0000

On Thu, Sep 10, 2009 at 10:11 PM, Justin Karneges <justin@affinix.com> wrot=
e:

> My (biased) opinion is that XEP-0184 should certainly not be suggested as=
 a
> solution to basic delivery problems. =A0Let's encourage fixing that probl=
em in
> the right place (XEP-0198, at the xmpp-core level).
>
> XEP-0184 could be mentioned as a solution to certain special needs, such =
as
> the need to know 'when' (as opposed to 'if') a message was received by th=
e
> final endpoint, or the need to send a message of high importance when the
> delivery capacity of the hops is not known or cannot be trusted. =A0But p=
lease,
> I don't think people should be implementing 184 to get around wi-fi drops=
,
> and we should be careful not to encourage or promote this.

I'm just adding my less biased POW: at the beginning I wasn't
convinced of a XEP-0184 like approach, since it requires cooperation
at the stream and session level, with some obvious drawbacks like a
messier server implementation (session management must be reworked in
order to keep alive dropped connections for a while, we must count and
aknowledge packets), resume still requires a long handshake in the
stream initialization (see the other thread about fast stream resume).
In few words: the approach sounded reasonable, but unlikely to be
implemented soon for these complications. I therefore was more keen to
follow a transport based approach (BOSH like solutions have all we
need for recovering from lost connections). There is only a problem:
it is easy to implement, but if we separate session recovery from
session management (as it happens in BOSH) it is likely to end in
situations in which your peers don't know you are offline, you won't
recover soon, and they send packets to a sink eating out packets  (the
BOSH like client connector, or the transport). Same considerations
apply to a more sophisticated SCTP binding: when the connection is
temporary dropped packets run the risk to be lost in the transport, if
the client isn't able to resume the session. Perhaps a trasnport based
solution, like a SCTP binding, has still benefits, since it minimizes
the need to restart the stream, but XEP-0198 at the top of it remains
essential for complete reliability.

bye

--=20
Fabio Forno, Ph.D.
Bluendo srl http://www.bluendo.com
jabber id: ff@jabber.bluendo.com

From melo@simplicidade.org  Thu Sep 10 13:40:51 2009
Return-Path: <melo@simplicidade.org>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3700C3A6A74 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBpL7V+TpVO4 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 13:40:49 -0700 (PDT)
Received: from speed.simplicidade.org (d001.h.gncd.net [193.227.238.37]) by core3.amsl.com (Postfix) with SMTP id 84D143A6A40 for <xmpp@ietf.org>; Thu, 10 Sep 2009 13:40:48 -0700 (PDT)
Received: (qmail 495 invoked from network); 10 Sep 2009 20:41:21 -0000
Received: from bl8-202-251.dsl.telepac.pt (HELO MrTray.lan) (85.241.202.251) (smtp-auth username melo@simplicidade.org, mechanism plain) by speed.simplicidade.org (qpsmtpd/0.43rc1) with (AES256-SHA encrypted) ESMTPSA; Thu, 10 Sep 2009 21:41:21 +0100
Message-Id: <F344DF37-A23B-48F5-B5D1-64415974260F@simplicidade.org>
From: Pedro Melo <melo@simplicidade.org>
To: XMPP <xmpp@ietf.org>
In-Reply-To: <4AA9485C.7020803@stpeter.im>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 10 Sep 2009 21:41:11 +0100
References: <4AA9485C.7020803@stpeter.im>
X-Mailer: Apple Mail (2.936)
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 20:40:51 -0000

On 2009/09/10, at 19:41, Peter Saint-Andre wrote:

> 4.6.  Reliability
>
>   The use of long-lived TCP connections in XMPP implies that the
>   sending of XML stanzas over XML streams can be unreliable, since the
>   parties to a long-lived TCP connection might not discover a
>   connectivity disruption in a timely manner.  At the XMPP application
>   layer, long connectivity disruptions can result in undelivered
>   stanzas.  Although the core XMPP technology defined in this
>   specification does not contain features to overcome this lack of
>   reliability, an XMPP extension for doing so is defined in  
> [XEP-0198].

I agree with general idea, but I do wonder if we should include XEP  
numbers in a RFC.

My concern is that we might want to use a new number for a new  
protocol and the RFC would be out-of-date.

Maybe we should a registry for best current practices, that we could  
update without having to change the RFC.

Just a though.

Best regards,


From florian.zeitz@gmx.de  Thu Sep 10 15:32:48 2009
Return-Path: <florian.zeitz@gmx.de>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFE953A6AD5 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 15:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-zyOJco3LZL for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 15:32:47 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id B6C1C28C1CB for <xmpp@ietf.org>; Thu, 10 Sep 2009 15:32:46 -0700 (PDT)
Received: (qmail invoked by alias); 10 Sep 2009 22:33:21 -0000
Received: from xdsl-87-78-44-76.netcologne.de (EHLO [192.168.0.38]) [87.78.44.76] by mail.gmx.net (mp060) with SMTP; 11 Sep 2009 00:33:21 +0200
X-Authenticated: #30932406
X-Provags-ID: V01U2FsdGVkX19RZr5KBLdRRhLEbR0jDxQIbZMB4LaF2c3wHNXV7j ExsTwX4xCOJ2vm
Message-ID: <4AA97EAF.5080809@gmx.de>
Date: Fri, 11 Sep 2009 00:33:19 +0200
From: Florian Zeitz <florian.zeitz@gmx.de>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: xmpp@ietf.org
References: <4AA9485C.7020803@stpeter.im> <4AA9524B.9000206@gmx.de> <200909101311.10962.justin@affinix.com>
In-Reply-To: <200909101311.10962.justin@affinix.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.47
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 22:32:48 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Justin Karneges wrote:
> XEP-0184 could be mentioned as a solution to certain special needs, such as 
> the need to know 'when' (as opposed to 'if') a message was received by the 
> final endpoint, or the need to send a message of high importance when the 
> delivery capacity of the hops is not known or cannot be trusted.  But please, 
> I don't think people should be implementing 184 to get around wi-fi drops, 
> and we should be careful not to encourage or promote this.
> 
> -Justin
I definitely agree (also replying to what Peter Saint-Andre send to the
standards list (by accident I assume)) that this has a different scope
and would (if at all) be included in 3921bis with a different use case
attached to it, but currently XEP-0184 is much more useful for knowing
'if' a message has been delivered.
It is implemented in Miranda, Gajim and Pidgin right now (AFAIK) and it
really tells you if the message got to the other end. XEP-0198 can only
tell you if a stanza made the hop (if I understand it correctly) which
means I can get an ACK from my server, but the message gets lost after
that (e.g. my friend's wi-fi drops) and I'll never know (the assumption
here is that only my server and client support XEP-0198 in that chain).

- - Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqpfq4ACgkQ0JXcdjR+9YSNOQCeM87ewh0iJOz8rdZSRg/qQuAv
S3EAn2448o9lztpMkUjehZns1T5/d+03
=/RCz
-----END PGP SIGNATURE-----

From justin@affinix.com  Thu Sep 10 17:40:14 2009
Return-Path: <justin@affinix.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B55773A6821 for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 17:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1g0UgT4rlnSS for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 17:40:14 -0700 (PDT)
Received: from homiemail-a14.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by core3.amsl.com (Postfix) with ESMTP id EB6CC3A68A5 for <xmpp@ietf.org>; Thu, 10 Sep 2009 17:40:13 -0700 (PDT)
Received: from localhost (andross.dreamhost.com [75.119.221.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPSA id 133708C06A for <xmpp@ietf.org>; Thu, 10 Sep 2009 17:40:50 -0700 (PDT)
From: Justin Karneges <justin@affinix.com>
To: xmpp@ietf.org
Date: Thu, 10 Sep 2009 17:40:49 -0700
User-Agent: KMail/1.9.10
References: <4AA9485C.7020803@stpeter.im> <200909101311.10962.justin@affinix.com> <4AA97EAF.5080809@gmx.de>
In-Reply-To: <4AA97EAF.5080809@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909101740.49098.justin@affinix.com>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 00:40:14 -0000

On Thursday 10 September 2009 15:33:19 Florian Zeitz wrote:
> Justin Karneges wrote:
> > XEP-0184 could be mentioned as a solution to certain special needs, such
> > as the need to know 'when' (as opposed to 'if') a message was received by
> > the final endpoint, or the need to send a message of high importance when
> > the delivery capacity of the hops is not known or cannot be trusted.  But
> > please, I don't think people should be implementing 184 to get around
> > wi-fi drops, and we should be careful not to encourage or promote this.
> >
> > -Justin
>
> I definitely agree (also replying to what Peter Saint-Andre send to the
> standards list (by accident I assume)) that this has a different scope
> and would (if at all) be included in 3921bis with a different use case
> attached to it, but currently XEP-0184 is much more useful for knowing
> 'if' a message has been delivered.
> It is implemented in Miranda, Gajim and Pidgin right now (AFAIK) and it
> really tells you if the message got to the other end. XEP-0198 can only
> tell you if a stanza made the hop (if I understand it correctly) which
> means I can get an ACK from my server, but the message gets lost after
> that (e.g. my friend's wi-fi drops) and I'll never know (the assumption
> here is that only my server and client support XEP-0198 in that chain).

Yes, XEP-0184 is a more practical solution today, especially if clients are 
already using it.  Unfortunately it's just such a bad one.  Imagine if SMTP 
were unreliable and we all had to use end-to-end email message receipts in 
order to not lose mail.  I don't mind 184 as an interim solution, but I hope 
all this client support of it doesn't cause people to be lazy about 198.  
That would just be really sad.

-Justin

From stpeter@stpeter.im  Thu Sep 10 18:19:53 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 305F83A63EB for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 18:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.388
X-Spam-Level: 
X-Spam-Status: No, score=-2.388 tagged_above=-999 required=5 tests=[AWL=0.211,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2LvMfb10wQr for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 18:19:52 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 46F023A6A9C for <xmpp@ietf.org>; Thu, 10 Sep 2009 18:19:52 -0700 (PDT)
Received: from squire.local (dsl-175-240.dynamic-dsl.frii.net [216.17.175.240]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5517040D09; Thu, 10 Sep 2009 19:20:06 -0600 (MDT)
Message-ID: <4AA9A5BB.300@stpeter.im>
Date: Thu, 10 Sep 2009 19:19:55 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Justin Karneges <justin@affinix.com>
References: <4AA9485C.7020803@stpeter.im> <4AA9524B.9000206@gmx.de> <200909101311.10962.justin@affinix.com>
In-Reply-To: <200909101311.10962.justin@affinix.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 01:19:53 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/10/09 2:11 PM, Justin Karneges wrote:
> On Thursday 10 September 2009 12:23:55 Florian Zeitz wrote:
>> I was wondering whether it might be a good idea to mention XEP-0184 too
>> though.
>> Possibly in a different context, maybe even in 3921bis.
>> It seems much more useful for the normal Instant Messaging case as long
>> as XEP-0198 is not widely deployed IMHO. OTOH not mentioning 184 might
>> be a way to increase 198 deployment...
> 
> My (biased) opinion is that XEP-0184 should certainly not be suggested as a 
> solution to basic delivery problems.  Let's encourage fixing that problem in 
> the right place (XEP-0198, at the xmpp-core level).
> 
> XEP-0184 could be mentioned as a solution to certain special needs, such as 
> the need to know 'when' (as opposed to 'if') a message was received by the 
> final endpoint, or the need to send a message of high importance when the 
> delivery capacity of the hops is not known or cannot be trusted.  But please, 
> I don't think people should be implementing 184 to get around wi-fi drops, 
> and we should be careful not to encourage or promote this.

Agreed!

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqppbsACgkQNL8k5A2w/vzzGgCeJn0iiwSLKoofTnrJyKwD0BM5
6TIAn0ap3bh4jKS+Xf1YcoVAAIXdPdXa
=+JaB
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Thu Sep 10 18:22:41 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8009E28C15C for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 18:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.396
X-Spam-Level: 
X-Spam-Status: No, score=-2.396 tagged_above=-999 required=5 tests=[AWL=0.203,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wWNBqW-EuDmz for <xmpp@core3.amsl.com>; Thu, 10 Sep 2009 18:22:40 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 69D563A69A6 for <xmpp@ietf.org>; Thu, 10 Sep 2009 18:22:40 -0700 (PDT)
Received: from squire.local (dsl-175-240.dynamic-dsl.frii.net [216.17.175.240]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4949A40D09; Thu, 10 Sep 2009 19:23:13 -0600 (MDT)
Message-ID: <4AA9A680.8030407@stpeter.im>
Date: Thu, 10 Sep 2009 19:23:12 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Pedro Melo <melo@simplicidade.org>, XMPP <xmpp@ietf.org>
References: <4AA9485C.7020803@stpeter.im> <F344DF37-A23B-48F5-B5D1-64415974260F@simplicidade.org>
In-Reply-To: <F344DF37-A23B-48F5-B5D1-64415974260F@simplicidade.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 01:22:41 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/10/09 2:41 PM, Pedro Melo wrote:
> 
> On 2009/09/10, at 19:41, Peter Saint-Andre wrote:
> 
>> 4.6.  Reliability
>> 
>> The use of long-lived TCP connections in XMPP implies that the 
>> sending of XML stanzas over XML streams can be unreliable, since
>> the parties to a long-lived TCP connection might not discover a 
>> connectivity disruption in a timely manner.  At the XMPP
>> application layer, long connectivity disruptions can result in
>> undelivered stanzas.  Although the core XMPP technology defined in
>> this specification does not contain features to overcome this lack
>> of reliability, an XMPP extension for doing so is defined in
>> [XEP-0198].
> 
> I agree with general idea, but I do wonder if we should include XEP 
> numbers in a RFC.

If we don't provide specific references, how will developers learn about
things like the stream management protocol? As long as the URLs are
stable, we can always publish pointers from something like XEP-0198 to
whatever the replacement protocol is (the IETF doesn't have that kind of
flexibility because they cannot change an RFC once it has been
published, whereas the XSF can modify published XEPs in place).

> My concern is that we might want to use a new number for a new
> protocol and the RFC would be out-of-date.

So we reference the new from the old, which gets superseded or
obsoleted. No big deal.

> Maybe we should a registry for best current practices, that we could 
> update without having to change the RFC.

Overkill, IMHO.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqppoAACgkQNL8k5A2w/vzqogCgry/wxJI/kkHqJAmJBLJ7HbRS
74oAnRR+bZ5gOw6yDoP3KaKLjo7u0FmW
=3wDQ
-----END PGP SIGNATURE-----

From dave@cridland.net  Fri Sep 11 05:33:52 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD0D13A69EC for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=-0.093, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vbqv1MQ3TBO0 for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:33:51 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 5E0E03A685E for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:33:22 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SqoywQAZcZKp@peirce.dave.cridland.net>; Fri, 11 Sep 2009 12:21:37 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <4AA9485C.7020803@stpeter.im> <4AA9621C.6040009@gmail.com>
In-Reply-To: <4AA9621C.6040009@gmail.com>
MIME-Version: 1.0
Message-Id: <4848.1252668096.620806@puncture>
Date: Fri, 11 Sep 2009 12:21:36 +0100
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?B?SmnFmcOtIFrDoXJldsO6Y2t5?= <zarevucky.jiri@gmail.com>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Encoded: Changed encoding from 8Bit for 7bit transmission
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 12:33:52 -0000

On Thu Sep 10 21:31:24 2009, Ji=C5=99=C3=AD Z=C3=A1rev=C3=BAcky wrote:
> On 09/10/2009 08:41 PM, Peter Saint-Andre wrote:
>> I propose adding the following informational (and self-explanatory)
>> paragraph to the section on TCP Binding in 3920bis...
>> =

>> 4.6.  Reliability
>> =

>>     The use of long-lived TCP connections in XMPP implies that the
>>     sending of XML stanzas over XML streams can be unreliable,  =

>> since the
>>     parties to a long-lived TCP connection might not discover a
>>     connectivity disruption in a timely manner.  At the XMPP  =

>> application
>>     layer, long connectivity disruptions can result in undelivered
>>     stanzas.  Although the core XMPP technology defined in this
>>     specification does not contain features to overcome this lack  =

>> of
>>     reliability, an XMPP extension for doing so is defined in  =

>> [XEP-0198].
>> =

>>    =

> =

> Such note is a good idea, but I wouldn't address a specific XEP in  =

> an RFC document

I would - even though a XEP can change, it's entirely reasonable to  =

reference them, as the reference is equivalent to the equally valid  =

STD reference. It's referencing a technology, not the specific  =

version of it.

> Although the core XMPP technology defined in this specification  =

> does not contain features to overcome this lack of reliability,  =

> XMPP extensions exist to rectify this problem (for example  =

> [XEP-0198]).

This is reasonable too, and reads more informatively - I don't think  =

we need a normative reference here. (Indeed, we shouldn't have any  =

normative references from the core XMPP RFC to any XMPP Extension  =

Proposals...)

Dave.
-- =

Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From dave@cridland.net  Fri Sep 11 05:33:53 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AA973A685E for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rncyjViQAEHG for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:33:52 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 832FF3A6A2C for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:33:27 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SqoyyQAZcSyq@peirce.dave.cridland.net>; Fri, 11 Sep 2009 12:21:45 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
References: <4AA9485C.7020803@stpeter.im> <F344DF37-A23B-48F5-B5D1-64415974260F@simplicidade.org>
In-Reply-To: <F344DF37-A23B-48F5-B5D1-64415974260F@simplicidade.org>
MIME-Version: 1.0
Message-Id: <4848.1252668102.620442@puncture>
Date: Fri, 11 Sep 2009 12:21:42 +0100
From: Dave Cridland <dave@cridland.net>
To: Pedro Melo <melo@simplicidade.org>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 12:33:53 -0000

On Thu Sep 10 21:41:11 2009, Pedro Melo wrote:
> 
> On 2009/09/10, at 19:41, Peter Saint-Andre wrote:
> 
>> 4.6.  Reliability
>> 
>>   The use of long-lived TCP connections in XMPP implies that the
>>   sending of XML stanzas over XML streams can be unreliable, since  
>> the
>>   parties to a long-lived TCP connection might not discover a
>>   connectivity disruption in a timely manner.  At the XMPP  
>> application
>>   layer, long connectivity disruptions can result in undelivered
>>   stanzas.  Although the core XMPP technology defined in this
>>   specification does not contain features to overcome this lack of
>>   reliability, an XMPP extension for doing so is defined in   
>> [XEP-0198].
> 
> I agree with general idea, but I do wonder if we should include XEP  
>  numbers in a RFC.
> 
> My concern is that we might want to use a new number for a new   
> protocol and the RFC would be out-of-date.

A completely new extension for achieving the same goals might have a  
new XEP, but we can place a pointer from XEP-0198 to it, if we feel  
that's appropriate. It's far more flexible than referencing an RFC,  
where even an update will cause the reference to be outdated.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From remko.troncon@gmail.com  Fri Sep 11 05:42:16 2009
Return-Path: <remko.troncon@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F411F3A6A2B for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUNh-InBG0da for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:42:15 -0700 (PDT)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 117183A6858 for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:42:14 -0700 (PDT)
Received: by bwz19 with SMTP id 19so745346bwz.37 for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:42:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=YCPJ7X2ZELf1rKN2w8vF+pLTDfSdpFMqkVM3ajfRSHc=; b=sKxrLHqs0ZKGXxhPj/ZhGfZ1ixny/YvfdM5xe9KnmNLqkuHF/IEyY1v97NoXZpTaVX gvSBCC6WmYY1QUk29DRWK0ID9CH0uP7Vilv3vWSXmMafO3Lej+9l7GcIVRRR4az0VzY0 /RkGWFXYM+LV7kV0mamQHzbBMaXgkrnqQDT5k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=tMrzm5nfEUZZYX31kRH2cejKbec1RIuqQcR3TITSazJ0FAw00jEIxUeqwUrCbpnhAr JKFl8xShrV/4aug01TI+ARDWPIId8pojILTZjMcB95GWMPOmXaddvVaE/ZsOLt5c7LKn m910wF3gFuYdB5LfHGoJ3rH1M73KB5thGLQpI=
MIME-Version: 1.0
Sender: remko.troncon@gmail.com
Received: by 10.103.86.34 with SMTP id o34mr1391849mul.118.1252672967903; Fri,  11 Sep 2009 05:42:47 -0700 (PDT)
In-Reply-To: <4848.1252668096.620806@puncture>
References: <4AA9485C.7020803@stpeter.im> <4AA9621C.6040009@gmail.com> <4848.1252668096.620806@puncture>
Date: Fri, 11 Sep 2009 14:42:47 +0200
X-Google-Sender-Auth: 2584ea773ffb8161
Message-ID: <133fd4c60909110542k240d0b66s708d0ad08114e0c9@mail.gmail.com>
From: =?UTF-8?Q?Remko_Tron=C3=A7on?= <remko@el-tramo.be>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 12:42:16 -0000

>> Although the core XMPP technology defined in this specification does not
>> contain features to overcome this lack of reliability, XMPP extensions exist
>> to rectify this problem (for example [XEP-0198]).
>
> This is reasonable too, and reads more informatively - I don't think we need
> a normative reference here. (Indeed, we shouldn't have any normative
> references from the core XMPP RFC to any XMPP Extension Proposals...)

 I think that's what Pedro meant by 'not referencing XEPs'. The
software engineer in me also feels uncomfortable with a direct
dependency on XEPs from the RFC, so I prefer this version (with or
without the explicit XEP-198 reference)

cheers,
Remko

From fabio.forno@gmail.com  Fri Sep 11 05:50:16 2009
Return-Path: <fabio.forno@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C69D28C0EC for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2S2MdEqWIXNi for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 05:50:14 -0700 (PDT)
Received: from mail-yx0-f200.google.com (mail-yx0-f200.google.com [209.85.210.200]) by core3.amsl.com (Postfix) with ESMTP id 347593A685C for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:50:14 -0700 (PDT)
Received: by yxe38 with SMTP id 38so1324310yxe.6 for <xmpp@ietf.org>; Fri, 11 Sep 2009 05:50:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=AT0Mq5aS9C05cZ2vT3lq/EwDbeDWuazLDR/L1OTS6XI=; b=U5c2a1PNnpi1OC+vRZsPT6VPvLwzpwPnHDf82YRT9ADwZMGho4cfezihGgJI4kQs64 Rf+S8YDAL+NR2z5wpaZ9PX3JPONqmUM6PNm3bMIXzKdVSNoQxQf+msola3UoXseEohbC 2b5qo1Mf8oh3Cuzv90cEtkH9vSFj+Rka3w7aw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uA68/XOmR/MXg5aaK4PnFGD0xdS/JbMvp/sbXsUMC+O5+M7Pa0lAs+oUi5FJY+MT40 oDs4IplwTVqpP6SKhsEKVQQzsBWkUG6JCuImlcHpO/oJ9CTZnyyoRj0sn5msXZhrA3Nt yCptxVSAr+p78tF84y1bySO+i3giIL9jIE8ig=
MIME-Version: 1.0
Received: by 10.91.22.6 with SMTP id z6mr1668497agi.65.1252673448250; Fri, 11  Sep 2009 05:50:48 -0700 (PDT)
In-Reply-To: <4848.1252668096.620806@puncture>
References: <4AA9485C.7020803@stpeter.im> <4AA9621C.6040009@gmail.com> <4848.1252668096.620806@puncture>
Date: Fri, 11 Sep 2009 14:50:48 +0200
Message-ID: <2fd53c3a0909110550p52d55f58w8af380601abb2911@mail.gmail.com>
From: Fabio Forno <fabio.forno@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 12:50:16 -0000

On Fri, Sep 11, 2009 at 1:21 PM, Dave Cridland <dave@cridland.net> wrote:
>> Although the core XMPP technology defined in this specification does not
>> contain features to overcome this lack of reliability, XMPP extensions exist
>> to rectify this problem (for example [XEP-0198]).
>
> This is reasonable too, and reads more informatively - I don't think we need
> a normative reference here. (Indeed, we shouldn't have any normative
> references from the core XMPP RFC to any XMPP Extension Proposals...)

As I've said I prefer this formulation since it just says:
- we are aware of the problem
- we intentionally left out the solution
- solutions exist and a possible one is xep-198

-- 
Fabio Forno, Ph.D.
Bluendo srl http://www.bluendo.com
jabber id: ff@jabber.bluendo.com

From stpeter@stpeter.im  Fri Sep 11 10:45:33 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 870A228C131 for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 10:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.834
X-Spam-Level: 
X-Spam-Status: No, score=-2.834 tagged_above=-999 required=5 tests=[AWL=-0.535, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qEHYP51-t05S for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 10:45:32 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id AD83B3A6988 for <xmpp@ietf.org>; Fri, 11 Sep 2009 10:45:32 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 077F340D09; Fri, 11 Sep 2009 11:46:09 -0600 (MDT)
Message-ID: <4AAA8CE0.8090903@stpeter.im>
Date: Fri, 11 Sep 2009 11:46:08 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: =?UTF-8?B?UmVta28gVHJvbsOnb24=?= <remko@el-tramo.be>
References: <4AA9485C.7020803@stpeter.im> <4AA9621C.6040009@gmail.com>	<4848.1252668096.620806@puncture> <133fd4c60909110542k240d0b66s708d0ad08114e0c9@mail.gmail.com>
In-Reply-To: <133fd4c60909110542k240d0b66s708d0ad08114e0c9@mail.gmail.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 17:45:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/09 6:42 AM, Remko Tronçon wrote:
>>> Although the core XMPP technology defined in this specification does not
>>> contain features to overcome this lack of reliability, XMPP extensions exist
>>> to rectify this problem (for example [XEP-0198]).
>> This is reasonable too, and reads more informatively - I don't think we need
>> a normative reference here. (Indeed, we shouldn't have any normative
>> references from the core XMPP RFC to any XMPP Extension Proposals...)
> 
>  I think that's what Pedro meant by 'not referencing XEPs'. The
> software engineer in me also feels uncomfortable with a direct
> dependency on XEPs from the RFC, so I prefer this version (with or
> without the explicit XEP-198 reference)

This is not a dependency, it is an informational pointer. How are people
supposed to find out that XEP-0198 is the place to look (for now)? I
like this text:

   Although the core XMPP technology defined in this
   specification does not contain features to overcome this lack of
   reliability, there exist XMPP extensions for doing so (e.g.,
   [XEP-0198]).

3920bis also contains informational references to XEPs 1, 16, 30, 45,
60, 71, 77, 124, 156, 165, 174, 175, 178, 191, 199, 205, 206, 220, and
271. All of those *might* change at some point in the future. IMHO that
doesn't mean it's a bad idea to reference them informationally. In fact
I think it's a bad idea to shy away from referencing specifications that
might prove helpful to developers when they read 3920bis for the next X
years (until we publish 3920ter, that is ;).

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqjOAACgkQNL8k5A2w/vxzNgCeMmWMe1swi786LvI+zrQs+rGD
9yUAoIlbDP6ZrNvoArsk1fkhc0CLabeh
=UGfb
-----END PGP SIGNATURE-----

From k.i.smith@gmail.com  Fri Sep 11 14:19:46 2009
Return-Path: <k.i.smith@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 570043A6853 for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 14:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4Qxf9JkDySi for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 14:19:45 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by core3.amsl.com (Postfix) with ESMTP id 997DC3A67DD for <xmpp@ietf.org>; Fri, 11 Sep 2009 14:19:45 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c5so505283anc.4 for <xmpp@ietf.org>; Fri, 11 Sep 2009 14:20:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=hGk0LVa0LJaVWATXAIFt4n2v3LHPvwHFVZTn7J0wNsc=; b=BBsG3VvrqTu84MNClVODDgPmHjFwwYKZug1xv804/VYQ9IReq6JeUQe/mnC/6FB/Fm wkSuH0c4mXmdabqhfEQ5LqJ9v+hG0BV0vmGV5Q/T0u/QoQBGauJUld18kKX6uXclzEHf DCbjjANZSyTQRF648ujYQtR2XOOiwP9IODKCY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=UYl5TxdpPKpzxyoDa7uPApWoxhZDEcgYWMzQD+TezWsiUhpyPynLGkVktG7XgXeLEb PMbpRIco+iJyZOS07PAmD7UKZiaYqqtrkmf/DkT8UlMaHjHWOV/a/Uiydck6UTHOE2gL QkUEwthJLlKxRlRQC7ieA4NT0tIW2ztjoCLIU=
MIME-Version: 1.0
Sender: k.i.smith@gmail.com
Received: by 10.101.194.8 with SMTP id w8mr3777783anp.190.1252704020905; Fri,  11 Sep 2009 14:20:20 -0700 (PDT)
In-Reply-To: <4AAA8CE0.8090903@stpeter.im>
References: <4AA9485C.7020803@stpeter.im> <4AA9621C.6040009@gmail.com> <4848.1252668096.620806@puncture> <133fd4c60909110542k240d0b66s708d0ad08114e0c9@mail.gmail.com> <4AAA8CE0.8090903@stpeter.im>
Date: Fri, 11 Sep 2009 22:20:20 +0100
X-Google-Sender-Auth: 2c0b570b0f44a50c
Message-ID: <f5aae3ec0909111420j7a0304cg9bfcfc006ce519b1@mail.gmail.com>
From: Kevin Smith <kevin@kismith.co.uk>
To: XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] 3920bis: reliability
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: kevin@kismith.co.uk
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 21:19:46 -0000

Sorry, I jumped into this thread far too late to influence it. I'd
prefer the informational reference to '198' rather than to 'e.g. 198',
but I'm happy with the text I just saw get checked in.

/K

From stpeter@stpeter.im  Fri Sep 11 14:25:23 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF45C3A69FC for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 14:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.972
X-Spam-Level: 
X-Spam-Status: No, score=-2.972 tagged_above=-999 required=5 tests=[AWL=-0.374, BAYES_00=-2.599, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d4kpXpMuJ8YJ for <xmpp@core3.amsl.com>; Fri, 11 Sep 2009 14:25:23 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 05F323A6359 for <xmpp@ietf.org>; Fri, 11 Sep 2009 14:25:23 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0C0EB40D09 for <xmpp@ietf.org>; Fri, 11 Sep 2009 15:25:59 -0600 (MDT)
Message-ID: <4AAAC066.9000206@stpeter.im>
Date: Fri, 11 Sep 2009 15:25:58 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [xmpp] 3920bis-02
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 21:25:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've just submitted version -02 of draft-ietf-xmpp-3920bis. The
changelog is:

1. Reworked the architecture section
2. Added section on reliability
3. Updated certs section to forbid f* wildcards
4. Corrected the discussion venue
5. Changed the term "foreign domain" to "remote domain"
6. Updated a reference or two

The SVN diff is here:

http://svn.xmpp.org:18080/browse/XMPP/trunk/internet-drafts/draft-ietf-xmpp-3920bis-02.xml?r1=3378&r2=3415

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqwGYACgkQNL8k5A2w/vwSxgCeILv7DSV18e4IHLPWHaG2mYZW
wWgAn3+MkrcnsOAug7XaZC11ArRuOm0t
=uUJ9
-----END PGP SIGNATURE-----

From root@core3.amsl.com  Fri Sep 11 14:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: xmpp@ietf.org
Delivered-To: xmpp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A1DE228C199; Fri, 11 Sep 2009 14:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090911213001.A1DE228C199@core3.amsl.com>
Date: Fri, 11 Sep 2009 14:30:01 -0700 (PDT)
Cc: xmpp@ietf.org
Subject: [xmpp] I-D Action:draft-ietf-xmpp-3920bis-02.txt
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 21:30:01 -0000

--NextPart

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           : Extensible Messaging and Presence Protocol (XMPP): Core
	Author(s)       : P. Saint-Andre
	Filename        : draft-ietf-xmpp-3920bis-02.txt
	Pages           : 166
	Date            : 2009-09-11

This document defines the core features of the Extensible Messaging
and Presence Protocol (XMPP), a technology for streaming Extensible
Markup Language (XML) elements for the purpose of exchanging
structured information in close to real time between any two or more
network-aware entities.  XMPP provides a generalized, extensible
framework for incrementally exchanging XML data, upon which a variety
of applications can be built.  The framework includes methods for
stream setup and teardown, channel encryption, authentication of a
client to a server and of one server to another server, and
primitives for push-style messages, publication of network
availability information ("presence"), and request-response
interactions.  This document also specifies the format for XMPP
addresses, which are fully internationalizable.

This document obsoletes RFC 3920.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xmpp-3920bis-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xmpp-3920bis-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-09-11141638.I-D@ietf.org>


--NextPart--

From stpeter@stpeter.im  Mon Sep 14 09:03:51 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 631943A6A73 for <xmpp@core3.amsl.com>; Mon, 14 Sep 2009 09:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.964
X-Spam-Level: 
X-Spam-Status: No, score=-2.964 tagged_above=-999 required=5 tests=[AWL=-0.365, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1sUdnSAbIjYx for <xmpp@core3.amsl.com>; Mon, 14 Sep 2009 09:03:50 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 6DE713A6A71 for <xmpp@ietf.org>; Mon, 14 Sep 2009 09:03:50 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2529A40D13 for <xmpp@ietf.org>; Mon, 14 Sep 2009 10:04:21 -0600 (MDT)
Message-ID: <4AAE6984.8040201@stpeter.im>
Date: Mon, 14 Sep 2009 10:04:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2009 16:03:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The SASL SCRAM mechanism is currently in IETF Last Call:

http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt

This mechanism is intended to replace DIGEST-MD5. Does it make sense for
the XMPP WG to specify SCRAM as mandatory-to-implement?

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkquaYQACgkQNL8k5A2w/vzFRQCdERQEzeKwmLIZ5WqrenVkzBqC
tREAn0cUoD/jMpA+ACIhB95rY18sXvkl
=oITq
-----END PGP SIGNATURE-----

From simon@josefsson.org  Tue Sep 15 04:21:13 2009
Return-Path: <simon@josefsson.org>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62E623A69E8 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 04:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dN8KNhrGgANV for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 04:21:12 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 4015B28C0EF for <xmpp@ietf.org>; Tue, 15 Sep 2009 04:21:11 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8FBLsEi030332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 15 Sep 2009 13:21:56 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4AAE6984.8040201@stpeter.im>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090915:xmpp@ietf.org::6DFp4H26IlaGuN64:1GpJ
X-Hashcash: 1:22:090915:stpeter@stpeter.im::BTe6qE9E8dg00Eu9:5sXt
Date: Tue, 15 Sep 2009 13:21:54 +0200
In-Reply-To: <4AAE6984.8040201@stpeter.im> (Peter Saint-Andre's message of "Mon, 14 Sep 2009 10:04:20 -0600")
Message-ID: <87eiq8pi5p.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 11:21:13 -0000

Peter Saint-Andre <stpeter@stpeter.im> writes:

> The SASL SCRAM mechanism is currently in IETF Last Call:
>
> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>
> This mechanism is intended to replace DIGEST-MD5. Does it make sense for
> the XMPP WG to specify SCRAM as mandatory-to-implement?

Yes. (although I'm not a XMPP implementer)

Did XMPP make use of DIGEST-MD5 security layers, in theory
(specification) and in practice (implementations)?

/Simon

From fabio.forno@gmail.com  Tue Sep 15 05:14:55 2009
Return-Path: <fabio.forno@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D99A23A6AF3 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvLRpM4+nr+a for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:14:55 -0700 (PDT)
Received: from mail-yw0-f199.google.com (mail-yw0-f199.google.com [209.85.211.199]) by core3.amsl.com (Postfix) with ESMTP id D6F0F3A6AE9 for <xmpp@ietf.org>; Tue, 15 Sep 2009 05:14:54 -0700 (PDT)
Received: by ywh37 with SMTP id 37so5677778ywh.17 for <xmpp@ietf.org>; Tue, 15 Sep 2009 05:15:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=zPIM0k+KLXUzAOo02gG4eQNlJfWbFgYywK03mubb5AU=; b=LTW6cPZIYA8KdPdLcHW65fjxKIg/xWukPIzqW55njMKYJVqXe8FYJz8Uj/HYu6+xwP 8Sl/6Sni7zeVevzvRZ6eu5dvqOMieNYIoROIJiBKsJq1p+y4asIYvcyCamhUB9JkwDIG cbzxJ35uxpEN78EOtemrcqbgq+u0OgfGoiV/Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=APk9JZZmRRMgUfMBqZy2knbvZK/nXy1+NMfJIh0EPcWrQWw+N1TOljB4EUxI3PfEk5 reNOISO+517Z06gon9jZ6iTL/z7cEn4HfaazG3tlXIKezxNY40TShNp0wzbAyExOBLLM x5aT0Y0q6dF1rj11Y4BwdQJXRaXeaMZ6m0LTs=
MIME-Version: 1.0
Received: by 10.100.17.27 with SMTP id 27mr7409109anq.199.1253016939069; Tue,  15 Sep 2009 05:15:39 -0700 (PDT)
In-Reply-To: <4AAE6984.8040201@stpeter.im>
References: <4AAE6984.8040201@stpeter.im>
Date: Tue, 15 Sep 2009 14:15:39 +0200
Message-ID: <2fd53c3a0909150515x27498ac2y9bbb362a879579bb@mail.gmail.com>
From: Fabio Forno <fabio.forno@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 12:14:55 -0000

2009/9/14 Peter Saint-Andre <stpeter@stpeter.im>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The SASL SCRAM mechanism is currently in IETF Last Call:
>
> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>
> This mechanism is intended to replace DIGEST-MD5. Does it make sense for
> the XMPP WG to specify SCRAM as mandatory-to-implement?

Does SCRAM support a digest based auth like DIGEST-MD5 or, better,
does it allow secure authentication over an unsecure channel? In that
case definitively yes, since there many case in which I don't need
TLS, but at least i want to protect my credentials.

-- 
Fabio Forno, Ph.D.
Bluendo srl http://www.bluendo.com
jabber id: ff@jabber.bluendo.com

From simon@josefsson.org  Tue Sep 15 05:19:38 2009
Return-Path: <simon@josefsson.org>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 732903A69CD for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level: 
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEdp7Wy7XNWv for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:19:37 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 42E7E3A6819 for <xmpp@ietf.org>; Tue, 15 Sep 2009 05:19:36 -0700 (PDT)
Received: from mocca.josefsson.org (c80-216-24-211.bredband.comhem.se [80.216.24.211]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n8FCKHjD031720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 15 Sep 2009 14:20:19 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Fabio Forno <fabio.forno@gmail.com>
References: <4AAE6984.8040201@stpeter.im> <2fd53c3a0909150515x27498ac2y9bbb362a879579bb@mail.gmail.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090915:xmpp@ietf.org::q7YJv0wFspHh2h5D:2H8n
X-Hashcash: 1:22:090915:fabio.forno@gmail.com::wWGNSag1Y7apDOZn:5FIJ
X-Hashcash: 1:22:090915:stpeter@stpeter.im::jTnst6EAlL+gRfYQ:CAOG
Date: Tue, 15 Sep 2009 14:20:17 +0200
In-Reply-To: <2fd53c3a0909150515x27498ac2y9bbb362a879579bb@mail.gmail.com> (Fabio Forno's message of "Tue, 15 Sep 2009 14:15:39 +0200")
Message-ID: <87r5u8o0vy.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 12:19:38 -0000

Fabio Forno <fabio.forno@gmail.com> writes:

> 2009/9/14 Peter Saint-Andre <stpeter@stpeter.im>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> The SASL SCRAM mechanism is currently in IETF Last Call:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>>
>> This mechanism is intended to replace DIGEST-MD5. Does it make sense for
>> the XMPP WG to specify SCRAM as mandatory-to-implement?
>
> Does SCRAM support a digest based auth like DIGEST-MD5 or, better,
> does it allow secure authentication over an unsecure channel?

Yes.  (Of course it depend on your definition of "secure"..)

> In that case definitively yes, since there many case in which I don't
> need TLS, but at least i want to protect my credentials.

You are still vulnerable to active attackers that hijack the connection
after you have authenticated yourself.  But I agree in some situations
that is an acceptable risk.

To use SCRAM (or CRAM-MD5 or DIGEST-MD5) you need a secure channel.  If
you used DIGEST-MD5 with security layers you will need SCRAM+TLS
instead.  SCRAM does not provide any SASL security layers.  I hope you
weren't using DIGEST-MD5 security layers, because they weren't that
good...

/Simon

From fabio.forno@gmail.com  Tue Sep 15 05:32:31 2009
Return-Path: <fabio.forno@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 370553A67F5 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDnElSIy-8dh for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 05:32:30 -0700 (PDT)
Received: from mail-yx0-f194.google.com (mail-yx0-f194.google.com [209.85.210.194]) by core3.amsl.com (Postfix) with ESMTP id 5B8D13A6B09 for <xmpp@ietf.org>; Tue, 15 Sep 2009 05:32:30 -0700 (PDT)
Received: by yxe32 with SMTP id 32so54035yxe.5 for <xmpp@ietf.org>; Tue, 15 Sep 2009 05:33:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vui6/g7D/G1ch7GTh0nstYCLU07aSgKTM9Fx8jFdrcc=; b=OEtH9vJW2YykBgm3VSk2Nj8olQ5F+kZuSJFC+eP+l21LnSODcsyWlOpTKh6JoSUtjk 0OxJhhIxLIHnJ0BClix6fCpLIEnBooBTu/hB7ZUZZ3hYC2UgTqJ+S2P5neXt56mL9jny OPrhsbggIqLIo3eSFoeQ5FYXLZ0hlsjQUx/W0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KZXk1R3fZieemm+ieoA4uLTgNqPyzSeQKyWZLX/uWPeee1r6Sk8FTDmzMgLX3Izg/5 YkpZdQRf+J564cBKPOE8MVwZ0ByrN1vnc/L8XSh3enEOJ7eRHz3BnQeStHG9Lb0jTD/e Bdi6RghCbfwH9Iv0xS5iWaMC6CMw7Fk7ZRev8=
MIME-Version: 1.0
Received: by 10.90.16.34 with SMTP id 34mr4585685agp.47.1253017993752; Tue, 15  Sep 2009 05:33:13 -0700 (PDT)
In-Reply-To: <87r5u8o0vy.fsf@mocca.josefsson.org>
References: <4AAE6984.8040201@stpeter.im> <2fd53c3a0909150515x27498ac2y9bbb362a879579bb@mail.gmail.com> <87r5u8o0vy.fsf@mocca.josefsson.org>
Date: Tue, 15 Sep 2009 14:33:13 +0200
Message-ID: <2fd53c3a0909150533q18119274pbc5977d4a615c522@mail.gmail.com>
From: Fabio Forno <fabio.forno@gmail.com>
To: Simon Josefsson <simon@josefsson.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 12:32:31 -0000

2009/9/15 Simon Josefsson <simon@josefsson.org>:

>> In that case definitively yes, since there many case in which I don't
>> need TLS, but at least i want to protect my credentials.
>
> You are still vulnerable to active attackers that hijack the connection
> after you have authenticated yourself. =A0But I agree in some situations
> that is an acceptable risk.

Sure, the rationale is minimizing damage: most the times I can survive
an hijacked session, while a stolen password could make me cry.

> To use SCRAM (or CRAM-MD5 or DIGEST-MD5) you need a secure channel. =A0If
> you used DIGEST-MD5 with security layers you will need SCRAM+TLS
> instead. =A0SCRAM does not provide any SASL security layers. =A0I hope yo=
u
> weren't using DIGEST-MD5 security layers, because they weren't that
> good...

Well indeed that's the only option offered by most servers if you
can't run TLS on the client (for some mobiles it's too heavy), and
since users can choose any server..

--=20
Fabio Forno, Ph.D.
Bluendo srl http://www.bluendo.com
jabber id: ff@jabber.bluendo.com

From stpeter@stpeter.im  Tue Sep 15 06:54:01 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E0043A683B for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 06:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12VFLdKFA6ut for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 06:54:00 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 80CCB3A6811 for <xmpp@ietf.org>; Tue, 15 Sep 2009 06:53:55 -0700 (PDT)
Received: from squire.local (dsl-228-30.dynamic-dsl.frii.net [216.17.228.30]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 18BEC40D13; Tue, 15 Sep 2009 07:54:38 -0600 (MDT)
Message-ID: <4AAF9C9C.6030004@stpeter.im>
Date: Tue, 15 Sep 2009 07:54:36 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <4AAE6984.8040201@stpeter.im> <87eiq8pi5p.fsf@mocca.josefsson.org>
In-Reply-To: <87eiq8pi5p.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 13:54:01 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/15/09 5:21 AM, Simon Josefsson wrote:
> Peter Saint-Andre <stpeter@stpeter.im> writes:
> 
>> The SASL SCRAM mechanism is currently in IETF Last Call:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>>
>> This mechanism is intended to replace DIGEST-MD5. Does it make sense for
>> the XMPP WG to specify SCRAM as mandatory-to-implement?
> 
> Yes. (although I'm not a XMPP implementer)
> 
> Did XMPP make use of DIGEST-MD5 security layers, in theory
> (specification) 

In theory, yes (by inheritance from RFC 2831).

> and in practice (implementations)?

Not in practice as far as I know.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqvnJwACgkQNL8k5A2w/vxlqQCg2J52oTA8NqmpDZ+v5yH6T+tt
T4MAoN7c4+8od+XKRvxfHEnQjeSu5qbW
=GkXC
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Tue Sep 15 13:32:23 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 487113A6A3D for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 13:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level: 
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=-0.637, BAYES_00=-2.599, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dST440Q+VMM for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 13:32:22 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 5D42E3A690A for <xmpp@ietf.org>; Tue, 15 Sep 2009 13:32:22 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8726640D13; Tue, 15 Sep 2009 14:33:09 -0600 (MDT)
Message-ID: <4AAFFA04.2080202@stpeter.im>
Date: Tue, 15 Sep 2009 14:33:08 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <4AAE6984.8040201@stpeter.im>	<2fd53c3a0909150515x27498ac2y9bbb362a879579bb@mail.gmail.com> <87r5u8o0vy.fsf@mocca.josefsson.org>
In-Reply-To: <87r5u8o0vy.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 20:32:23 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/15/09 6:20 AM, Simon Josefsson wrote:
> Fabio Forno <fabio.forno@gmail.com> writes:
> 
>> 2009/9/14 Peter Saint-Andre <stpeter@stpeter.im>:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> The SASL SCRAM mechanism is currently in IETF Last Call:
>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>>>
>>> This mechanism is intended to replace DIGEST-MD5. Does it make sense for
>>> the XMPP WG to specify SCRAM as mandatory-to-implement?
>> Does SCRAM support a digest based auth like DIGEST-MD5 or, better,
>> does it allow secure authentication over an unsecure channel?
> 
> Yes.  (Of course it depend on your definition of "secure"..)
> 
>> In that case definitively yes, since there many case in which I don't
>> need TLS, but at least i want to protect my credentials.
> 
> You are still vulnerable to active attackers that hijack the connection
> after you have authenticated yourself.  But I agree in some situations
> that is an acceptable risk.
> 
> To use SCRAM (or CRAM-MD5 or DIGEST-MD5) you need a secure channel.  If
> you used DIGEST-MD5 with security layers you will need SCRAM+TLS
> instead.  SCRAM does not provide any SASL security layers.  I hope you
> weren't using DIGEST-MD5 security layers, because they weren't that
> good...

As mentioned, I don't think that anyone was using DIGEST-MD5 security
layers in XMPP. If I'm wrong about that I'd love to be corrected.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqv+gQACgkQNL8k5A2w/vxsMACgk30mLadr5nWuLi4O92A7iAYg
PPgAoMHpB0SPIqnBFSa7fQxRUVGFnJ5i
=O+if
-----END PGP SIGNATURE-----

From justin@affinix.com  Tue Sep 15 14:36:36 2009
Return-Path: <justin@affinix.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 096BC3A6A62 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 14:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MYdT6aZgVjhy for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 14:36:35 -0700 (PDT)
Received: from homiemail-a4.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by core3.amsl.com (Postfix) with ESMTP id 59CFB3A693A for <xmpp@ietf.org>; Tue, 15 Sep 2009 14:36:35 -0700 (PDT)
Received: from localhost (andross.dreamhost.com [75.119.221.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a4.g.dreamhost.com (Postfix) with ESMTP id 5BD26403A8 for <xmpp@ietf.org>; Tue, 15 Sep 2009 14:37:22 -0700 (PDT)
From: Justin Karneges <justin@affinix.com>
To: xmpp@ietf.org
Date: Tue, 15 Sep 2009 14:37:28 -0700
User-Agent: KMail/1.9.10
References: <4AAE6984.8040201@stpeter.im> <87r5u8o0vy.fsf@mocca.josefsson.org> <4AAFFA04.2080202@stpeter.im>
In-Reply-To: <4AAFFA04.2080202@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909151437.28773.justin@affinix.com>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 21:36:36 -0000

On Tuesday 15 September 2009 13:33:08 Peter Saint-Andre wrote:
> On 9/15/09 6:20 AM, Simon Josefsson wrote:
> > To use SCRAM (or CRAM-MD5 or DIGEST-MD5) you need a secure channel.  If
> > you used DIGEST-MD5 with security layers you will need SCRAM+TLS
> > instead.  SCRAM does not provide any SASL security layers.  I hope you
> > weren't using DIGEST-MD5 security layers, because they weren't that
> > good...
>
> As mentioned, I don't think that anyone was using DIGEST-MD5 security
> layers in XMPP. If I'm wrong about that I'd love to be corrected.

Psi supports this feature but nobody knows it.  You have to pair the client 
with cyrus-sasl, which is not how we ship by default.

I'm not aware of anyone using DIGEST-MD5 security layers in practice.  That's 
a shame, because I do think it's a useful feature.  Even if the security 
isn't that good, it's certainly better than unchecked TLS (something people 
still do today).

-Justin

From Kurt.Zeilenga@Isode.com  Tue Sep 15 15:58:48 2009
Return-Path: <Kurt.Zeilenga@Isode.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29ED128C179 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 15:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hd07d0eHlsDE for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 15:58:47 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 60E003A67B0 for <xmpp@ietf.org>; Tue, 15 Sep 2009 15:58:47 -0700 (PDT)
Received: from [192.168.0.13] ((unknown) [92.29.4.84])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <SrAcUgB9YQNS@rufus.isode.com>; Tue, 15 Sep 2009 23:59:34 +0100
X-SMTP-Protocol-Errors: NORDNS
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
In-Reply-To: <4AAE6984.8040201@stpeter.im>
Date: Tue, 15 Sep 2009 23:58:57 +0100
Message-Id: <1CC26974-8BDA-4ED7-83C9-732719F68295@Isode.com>
References: <4AAE6984.8040201@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1076)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Cc: XMPP <xmpp@ietf.org>
Subject: Re: [xmpp] SCRAM as MTI?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 22:58:48 -0000

On Sep 14, 2009, at 5:04 PM, Peter Saint-Andre wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The SASL SCRAM mechanism is currently in IETF Last Call:
>
> http://www.ietf.org/internet-drafts/draft-ietf-sasl-scram-07.txt
>
> This mechanism is intended to replace DIGEST-MD5. Does it make sense  
> for
> the XMPP WG to specify SCRAM as mandatory-to-implement?

Yes.

-- Kurt

From stpeter@stpeter.im  Tue Sep 15 16:49:57 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B16013A6A9A for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 16:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level: 
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.189,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSmzjVyRtYV0 for <xmpp@core3.amsl.com>; Tue, 15 Sep 2009 16:49:56 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id A34513A68CC for <xmpp@ietf.org>; Tue, 15 Sep 2009 16:49:56 -0700 (PDT)
Received: from squire.local (dsl-228-30.dynamic-dsl.frii.net [216.17.228.30]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3029840D13 for <xmpp@ietf.org>; Tue, 15 Sep 2009 17:50:42 -0600 (MDT)
Message-ID: <4AB020DE.3040601@stpeter.im>
Date: Tue, 15 Sep 2009 17:18:54 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: XMPP <xmpp@ietf.org>
References: <2BD0827F-6713-42FD-81E1-FEAE01B331DF@Isode.com>
In-Reply-To: <2BD0827F-6713-42FD-81E1-FEAE01B331DF@Isode.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [xmpp] [Standards] definition of common attribute 'id'
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 23:49:57 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Comment at bottom.

On 8/4/09 7:37 PM, Kurt Zeilenga wrote:
> The definition of 'id' (9.1.3 of 3920bis) says:
>> The 'id' attribute MAY be used by a sending entity for internal
>> tracking of stanzas that it sends and receives (especially for
>> tracking the request-response interaction inherent in the semantics of
>> IQ stanzas). The value of the 'id' attribute MAY be unique globally,
>> within a domain, or within a stream. The semantics of IQ stanzas
>> impose additional restrictions; see Section 9.2.3.
> I think the first MAY is trying to do two things at once.  It's trying
> to 1) state that providing the 'id' attribute is at the sending entity's
> option and 2) what the purpose of the attribute is.  I think it would be
> better to separate these.  For instance:
>       The purpose of the id attribute is to allow a response stanza to
> be associated with a particular request stanza.
>       Except where specified differently, the entity originating a
> request stanza MAY include an 'id' attribute.
> I note that 'sending entity' is a term that not well defined.  Elsewhere
> in the document, 'sending entity' simply refers to the entity which sent
> a particular stanza (and 'receiving entity' simply refers to an entity
> which received a particular stanza).
> If we use this meaning here, this sentence could be read that the entity
> sending a response stanza has the option not to include the id attribute
> provided in the request stanza as it is 'sending' the response stanza.  
> Even if we took the 'sending entity' to refer to a party sending a
> request, that would imply that a server sending a request on behalf of a
> client MAY not include the id attribute the client provided when it
> originated the request.
> I would think for this feature to "work" in general, an entity
> responding to a request containing an id attribute MUST provide an id
> attribute with the same value as the request contained in the request. 
> This requirement does not appear to be well specified.
> As far as unique, no uniqueness property should be assumed by the
> receiving entity.  The receiving property should treat id values as
> opaque value.
> While the originating entity of a request could ensure values they
> generate have some uniqueness property, the only actual requirement is
> that originating entities SHOULD produce values in a manner which
> ensures that outstanding requests (requests they've sent but have yet to
> receive a response for) do not share the same value.  For instance, an
> implementation which serializes it requests (never has more than one
> outstanding) could use the same id value for all requests it generates.
> -- Kurt

In draft-ietf-xmpp-3920bis-02 can be found the following text:

***

9.1.3.  id

   The 'id' attribute is used by the entity that generates a stanza
   ("the originating entity") to track any response or error stanza that
   it might receive in relation to the generated stanza from another
   entity (such as an intermediate server or the intended recipient).

   It is up to the originating entity whether the value of the 'id'
   attribute will be unique only within its current stream (session) or
   unique globally.

   For <message/> and <presence/> stanzas, it is RECOMMENDED for the
   originating entity to include an 'id' attribute; for <iq/> stanzas,
   it is REQUIRED.

   If the generated stanza includes an 'id' attribute then it is
   REQUIRED for the response or error stanza to also include an 'id'
   attribute, where the value of the 'id' attribute MUST match that of
   the generated stanza.

   Note: The semantics of IQ stanzas impose additional restrictions; see
   Section 9.2.3.

***

If that is still unclear, please post to this list.

/psa


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqwIN4ACgkQNL8k5A2w/vz7SwCgsmvV4PGotQiLjJHy219Lfs/J
0XMAoJsLYqWcLZvfxPiKH188EVf3q8xk
=djqI
-----END PGP SIGNATURE-----


From jehan.marmottard@gmail.com  Wed Sep 23 09:00:39 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8881B28C121 for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nEIzmk4qgEU for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:00:38 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id A718D3A69BA for <xmpp@ietf.org>; Wed, 23 Sep 2009 09:00:37 -0700 (PDT)
Received: by ewy28 with SMTP id 28so1255287ewy.42 for <xmpp@ietf.org>; Wed, 23 Sep 2009 09:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=ShRorGDs3NDM/iJA/5KEPHd2HEDU6LzAybfc0F8y3dM=; b=rVJao1zXCAqZBVHm/SmBEKNO7h40CV7rE/cFYkYeEo99xeJJWY5ReRHQcoyzk8+fUQ TtBvrc/MCB8xYaczu7r5MoNm3llxZ4LeJ78HIILefwF2/lfNUxZaVngmh32Ie2EjrAHZ eL1gxk/ALHlWacGaF3I44SOrMXBG/5a02w3Yw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cFv3zI2VscU+yDt8Fy+FcZa78v65dtlWzIZrUZnkT5bksLwuLSNu8g6/g6r8OWKH1/ mQOvz09Po3Sf4DRGuAoSx2kwk+o8A7QKKTOm+5lp8f+ZL9TotGEjC59jFxoKBafUR05N 2+yH8iM62I5EpuKQXqiGCAIR8N5r/64sBbY+k=
MIME-Version: 1.0
Received: by 10.210.9.13 with SMTP id 13mr2840970ebi.7.1253721700189; Wed, 23  Sep 2009 09:01:40 -0700 (PDT)
Date: Thu, 24 Sep 2009 01:01:40 +0900
Message-ID: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 16:06:26 -0000

Hi,

yesterday I was discussing with Peter about how namespace requirements
were presented in RFC 3920bis, and we both agreed that it is wrong.
The RFC is clearly trying to make an excuse for badly programmed XML
parsers, not able to expand prefixes into namespaces (or keep track of
declared prefix in parent elements). So you MUST absolutely have a
default namespace in the root <stream>, and this one MUST be the one
for the stanza ("jabber:client" or "jabber:server", most typically) +
you MUST have a prefix declared, for the stream related first level
elements, and this prefix MUST be "stream".
So for instance, the current RFC asks me to reject and consider this
stream start as an error, though it is perfectly valid XML and
conforming to XMPP:

<toto:stream
          from='juliet@im.example.com'
          to='im.example.com'
          version='1.0'
          xml:lang='en'
          xmlns='jabber:client'
          xmlns:toto='http://etherx.jabber.org/streams'>

And many other examples: for instance, if I prefer to use a declared
namespace for "jabber:client" instead of a default namespace, why
couldn't I? This is good XML, and what only matters is the final
expanded name (however we got to it). This is all for historical
reasons, for backward compatibility with jabberd 1.0 in "old" times,
as Peter explained me, but we agreed that nowayday, such a stuff
should not be in an RFC, presented as "the good way to do". Probably
it should just become a note of "For historical reasons, some
implementations may require...", so that we still aknowledge this old
issue, but without asking softwares to refuse the other good ways.

There are several parts to change about this. In particular in 12.2

-------------------
12.2.1. Streams Namespace

   A streams namespace declaration is REQUIRED in all XML stream headers
   and the name of the streams namespace MUST be
   'http://etherx.jabber.org/streams'.  If this rule is violated, the
   entity that receives the offending stream header MUST return a stream
   error to the sending entity, which SHOULD be <invalid-namespace/> but
   MAY be <bad-format/>.

   The element names of the <stream/> element and its <features/> and
   <error/> children MUST be qualified by the streams namespace prefix
   in all instances.  If this rule is violated, the entity that receives
   the offending element MUST return a stream error to the sending
   entity, which SHOULD be <bad-format/>.

   An implementation SHOULD generate only the 'stream:' prefix for these
   elements, and for historical reasons MAY accept only the 'stream:'
   prefix.  If an entity receives a stream header with a streams
   namespace prefix it does not accept, it MUST return a stream error to
   the sending entity, which SHOULD be <bad-namespace-prefix/> but MAY
   be <bad-format/>.

-------------------

should probably become something like:

-----------------
12.2.1. Streams Namespace

   The element names of the <stream/> element and its <features/> and
   <error/> children MUST be qualified in all instances by the streams
namespace,
   whose value is "http://etherx.jabber.org/streams".  If this rule is
violated, the entity that receives
   the offending element MUST return a stream error to the sending
   entity, which SHOULD be <bad-format/>.

For historical reasons, some older implementations may accept only a
stream element qualification through a prefix named "stream" (and not
for instance through a default namespace, nor a prefix named other
than "stream"), declared in the initial <stream/> element. For
backwards compatibility, it may therefore be a good idea, though not
mandatory, to declare a prefix named "stream" and with value
"http://etherx.jabber.org/streams" in the <stream/> header. However an
implementation MUST NOT send any error, hence reject a stream doing
differently, as long as the qualified names for the <stream/>,
<features/> and <error/> element are correct with this alternative
method.
-----------------------------

Then I would change the next section:

-----------------------------
12.2.2. Default Namespace


   A default namespace declaration is REQUIRED and defines the allowable
   first-level children of the root stream element.  This namespace
   declaration MUST be the same for the initial stream and the response
   stream so that both streams are qualified consistently.  The default
   namespace declaration applies to the stream and all first-level child
   element sent within a stream unless explicitly qualified by the
   streams namespace or another namespace.

   A server implementation MUST support the following two default
   namespaces:

   o  jabber:client -- this default namespace is declared when the
      stream is used for communication between a client and a server
   o  jabber:server -- this default namespace is declared when the
      stream is used for communication between two servers

   A client implementation MUST support the 'jabber:client' default
   namespace.

   If an implementation accepts a stream that is qualified by the
   'jabber:client' or 'jabber:server' namespace, it MUST support the
   common attributes (Section 9.1) and basic semantics (Section 9.2) of
   all three core stanza types (message, presence, and IQ).

   For historical reasons, an implementation MAY refuse to support any
   other default namespaces.  If an entity receives a stream header with
   a default namespace it does not support, it MUST return an <invalid-
   namespace/> stream error.

   An implementation MUST NOT generate namespace prefixes for elements
   qualified by the default namespace if the default namespace is
   'jabber:client' or 'jabber:server'.

      Note: The 'jabber:client' and 'jabber:server' namespaces are
      nearly identical but are used in different contexts (client-to-
      server communication for 'jabber:client' and server-to-server
      communication for 'jabber:server').  The only difference between
      the two is that the 'to' and 'from' attributes are OPTIONAL on
      stanzas sent over XML streams qualified by the 'jabber:client'
      namespace, whereas they are REQUIRED on stanzas sent over XML
      streams qualified by the 'jabber:server' namespace.

   An implementation MAY support a default namespace other than "jabber:
   client" or "jabber:server".  However, because such namespaces would
   define applications other than XMPP, they are to be defined in
   separate specifications.
-------------------

As follow:

------------
12.2.2. First Level Namespaces

On first level, an implementation MUST understand the children element
<features/> and <error/>, qualified by the stream namespace
"http://etherx.jabber.org/streams" (see previous section) as well as
other first-level children defined by implementation choice.
These allowable first level children, other than the ones qualified by
the stream namespace, must be qualified by specific namespaces
grouping them into a common semantic applications. Such first level
children are called the stanzas.

   A server implementation MUST support the following two default
   namespaces:

   o  jabber:client -- this namespace qualifies core stanzas when the
      stream is used for communication between a client and a server
   o  jabber:server -- this namespace qualifies core stanzas when the
      stream is used for communication between two servers

   A client implementation MUST support the 'jabber:client' default
   namespace.

   If an implementation accepts a stream that is qualified by the
   'jabber:client' or 'jabber:server' namespace, it MUST support the
   common attributes (Section 9.1) and basic semantics (Section 9.2) of
   all three core stanza types (message, presence, and IQ).

   For historical reasons, an implementation MAY refuse to support any
   other stanza namespace.  If an entity receives a first level
element qualified
by a namespace it does not support, it MUST return an <invalid-
   namespace/> stream error. In an entity receives a first level
element qualified by
a namespace it supports, but whose local name is not defined in this namespace,
it MUST return an <unsupported-stanza-type/> stream error.

      Note: The 'jabber:client' and 'jabber:server' namespaces are
      nearly identical but are used in different contexts (client-to-
      server communication for 'jabber:client' and server-to-server
      communication for 'jabber:server').  The only difference between
      the two is that the 'to' and 'from' attributes are OPTIONAL on
      stanzas sent over XML streams qualified by the 'jabber:client'
      namespace, whereas they are REQUIRED on stanzas sent over XML
      streams qualified by the 'jabber:server' namespace.

   An implementation MAY support stanzas qualified by namespaces other
than "jabber:
   client" or "jabber:server".  However, because such namespaces would
   define applications other than XMPP, they are to be defined in
   separate specifications.

--------------

There are other stuffs to change in the RFC related to this
problematic. But for now let's launch the discussion from this point.
:-)
Bye.

Jehan

From metajack@gmail.com  Wed Sep 23 09:21:33 2009
Return-Path: <metajack@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B4273A6877 for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYRIeckN143v for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:21:32 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id A1C473A6765 for <xmpp@ietf.org>; Wed, 23 Sep 2009 09:21:32 -0700 (PDT)
Received: by ewy28 with SMTP id 28so1278448ewy.42 for <xmpp@ietf.org>; Wed, 23 Sep 2009 09:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=dpVWx6rAqxEU8IQqc6c0nQ/mzwMaKmuJUUGPHz1uQZY=; b=YLd8fIctqnHGThhY2Cv6NUxRr3jvCGTFhTETY83xfdXlrIyXrmoVdLDZD6YdnP1dw7 EUPj1HaCg1Dhk/1oR+9rDM+jM5QGVkPVeRZ5K5PfuUBlvc0Empvvd8+MNl+yUQUaF4s4 /LxnY/U8Ua8iTca55Pb7BVFYsPWHT0ijAmsA8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=j1pRPr6biagqKcFhAfLsQphieyyr4neR0R0X01rztWV2p2VYSQAClUD7GxuuTwyPy2 3u3H7YT1bhLS66SGMKVg83XTuHi+vYJNMf5qgv2dGRUxQ0LCEVSA7hUdgdi/JNYSMwQz 8LLCKleV8AIq2oczXb8IbEjbKJh5m+kZMm4wk=
MIME-Version: 1.0
Sender: metajack@gmail.com
Received: by 10.216.48.211 with SMTP id v61mr557062web.67.1253722956139; Wed,  23 Sep 2009 09:22:36 -0700 (PDT)
In-Reply-To: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
Date: Wed, 23 Sep 2009 10:22:36 -0600
X-Google-Sender-Auth: 5f67764a62909f39
Message-ID: <9b58f4550909230922v63afcfb1tfe54e62257ad3440@mail.gmail.com>
From: Jack Moffitt <jack@collecta.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 16:21:33 -0000

> yesterday I was discussing with Peter about how namespace requirements
> were presented in RFC 3920bis, and we both agreed that it is wrong.
> The RFC is clearly trying to make an excuse for badly programmed XML
> parsers, not able to expand prefixes into namespaces (or keep track of
> declared prefix in parent elements). So you MUST absolutely have a
> default namespace in the root <stream>, and this one MUST be the one
> for the stanza ("jabber:client" or "jabber:server", most typically) +
> you MUST have a prefix declared, for the stream related first level
> elements, and this prefix MUST be "stream".
> So for instance, the current RFC asks me to reject and consider this
> stream start as an error, though it is perfectly valid XML and
> conforming to XMPP:

I am +1 on fixing this stuff.

This might also be a good time to bring up the XML-NAMES
well-formedness issues and address those as well.  I'd have to go back
and look at what the consensus (if any) was for that.  But I seem to
recall a proposal that suggested we disallow other prefixes in the
top-level stream element and not throw XML parse errors on namespace
well-formedness issues.

jack.

From stpeter@stpeter.im  Wed Sep 23 09:57:56 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A05533A686C for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.818
X-Spam-Level: 
X-Spam-Status: No, score=-2.818 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mykWeY7XJcD for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 09:57:55 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id BCC2F3A67B7 for <xmpp@ietf.org>; Wed, 23 Sep 2009 09:57:55 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1E00B40D21; Wed, 23 Sep 2009 10:59:01 -0600 (MDT)
Message-ID: <4ABA53D4.4060406@stpeter.im>
Date: Wed, 23 Sep 2009 10:59:00 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Jack Moffitt <jack@collecta.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <9b58f4550909230922v63afcfb1tfe54e62257ad3440@mail.gmail.com>
In-Reply-To: <9b58f4550909230922v63afcfb1tfe54e62257ad3440@mail.gmail.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: xmpp@ietf.org
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 16:57:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/23/09 10:22 AM, Jack Moffitt wrote:

> This might also be a good time to bring up the XML-NAMES
> well-formedness issues and address those as well.  I'd have to go back
> and look at what the consensus (if any) was for that.  But I seem to
> recall a proposal that suggested we disallow other prefixes in the
> top-level stream element and not throw XML parse errors on namespace
> well-formedness issues.

I posted about that on August 14:

http://www.ietf.org/mail-archive/web/xmpp/current/msg00155.html

I think that the text I posted incorporates the list consensus, so I'd
be curious to see if others agree.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq6U9QACgkQNL8k5A2w/vylhQCgs6xLRMnopJD5K10hvv1YjE7t
b8UAoLAQmRVFsyDMRlxw/ap2cKjrVsoF
=xzRj
-----END PGP SIGNATURE-----

From dave@cridland.net  Wed Sep 23 10:10:14 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FB553A6A5A for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGD1ESHGmnsv for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:10:13 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id C8AA93A6911 for <xmpp@ietf.org>; Wed, 23 Sep 2009 10:10:12 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SrpWsABdm29X@peirce.dave.cridland.net>; Wed, 23 Sep 2009 18:11:13 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
In-Reply-To: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <14412.1253725891.012680@puncture>
Date: Wed, 23 Sep 2009 18:11:31 +0100
From: Dave Cridland <dave@cridland.net>
To: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Encoded: Changed encoding from 8Bit for 7bit transmission
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 17:10:14 -0000

On Wed Sep 23 17:01:40 2009, Jehan Pag=E8s wrote:
> The RFC is clearly trying to make an excuse for badly programmed XML
> parsers, not able to expand prefixes into namespaces (or keep track  =

> of
> declared prefix in parent elements).

It's also opening the door for heavily optimized pathways which elide  =

reserialization and all sorts.

>  So you MUST absolutely have a
> default namespace in the root <stream>, and this one MUST be the one
> for the stanza ("jabber:client" or "jabber:server", most typically)

Right, this allows us to detirmine whether it's a client, server, or  =

component. We actually do this - so if you want to, you can point  =

clients, components, and servers alike at a single port and it'll all  =

just work.

If we didn't do this, we'd need some additional signalling to  =

distinguish, or else we'd have to use distinct TCP ports for all  =

three, which seems suboptimal, especially when we're already using  =

this quite happily.

>  +
> you MUST have a prefix declared, for the stream related first level
> elements,

Well if you've already got a default namespace, it stands to reason  =

you can't have the stream top-level elements in it.

>  and this prefix MUST be "stream".

I don't care about this, and FWIW, we do not rely on it. Also, it's a  =

SHOULD not a MUST, and a MAY rely on. The latter, I think, needs  =

changing - this should be SHOULD (because of legacy systems) and MUST  =

NOT rely on.


> So for instance, the current RFC asks me to reject and consider this
> stream start as an error, though it is perfectly valid XML and
> conforming to XMPP:
> =

> <toto:stream
>           from=3D'juliet@im.example.com'
>           to=3D'im.example.com'
>           version=3D'1.0'
>           xml:lang=3D'en'
>           xmlns=3D'jabber:client'
>           xmlns:toto=3D'http://etherx.jabber.org/streams'>
> =

> =

No, the RFC says you MAY reject it. Section 11.2.1 says so.


> And many other examples: for instance, if I prefer to use a declared
> namespace for "jabber:client" instead of a default namespace, why
> couldn't I?

See above. Various other things, like XEP-0220, get triggered by the  =

default namespace choice of the initiator of the stream.

> For historical reasons, some older implementations may accept only a
> stream element qualification through a prefix named "stream" (and  =

> not
> for instance through a default namespace, nor a prefix named other
> than "stream"), declared in the initial <stream/> element. For
> backwards compatibility, it may therefore be a good idea, though not
> mandatory, to declare a prefix named "stream" and with value
> "http://etherx.jabber.org/streams" in the <stream/> header. However  =

> an
> implementation MUST NOT send any error, hence reject a stream doing
> differently, as long as the qualified names for the <stream/>,
> <features/> and <error/> element are correct with this alternative
> method.

"it may therefore be a good idea, though not mandatory" =3D SHOULD.

Dave.
-- =

Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From remko.troncon@gmail.com  Wed Sep 23 10:27:05 2009
Return-Path: <remko.troncon@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C7F328C159 for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ii88jOq22DxK for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:27:04 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 95CBE28C121 for <xmpp@ietf.org>; Wed, 23 Sep 2009 10:27:04 -0700 (PDT)
Received: by ewy28 with SMTP id 28so1350254ewy.42 for <xmpp@ietf.org>; Wed, 23 Sep 2009 10:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=S0WIpvuPLSB1j+GqaI5AL1Ug4SLHhNogcbiutecq3o8=; b=jMiZaLRcNYVNRxdm5w5stPWtHSR9jOaFWyLoLYQ3bXd0AY+ro2uNauS1IdpdeR52yw f+dXjo1iRtqk8cLybUPyNo/0bA5q0mTbbiElfSSYraDAUcRzsyXeQ7iaQB1QBZrlwxcm chucTbY184HMa0pLUFvnsRnis1xIo4hj3wrWg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=uHwmJ7UUrx+qsZadxWcHqVXtmsubu9Pz8X04AGKu59sZc3sv8WaM1VeT71l/B+JAHc vB2P4k6JnRXlvXFr5uGeu/oL76/H/mcPQkPp2aXYBSErdi9qCxb9IQRlUwWsm1aeA/6Y +ZHn+Njqg2dNKIw03gwqCaIUypApWTPRs4yr8=
MIME-Version: 1.0
Sender: remko.troncon@gmail.com
Received: by 10.216.72.149 with SMTP id t21mr510672wed.136.1253726885484; Wed,  23 Sep 2009 10:28:05 -0700 (PDT)
In-Reply-To: <14412.1253725891.012680@puncture>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <14412.1253725891.012680@puncture>
Date: Wed, 23 Sep 2009 19:28:05 +0200
X-Google-Sender-Auth: 915d1c81afd6a472
Message-ID: <133fd4c60909231028v69a01c7v4c71b027778d02ea@mail.gmail.com>
From: =?UTF-8?Q?Remko_Tron=C3=A7on?= <remko@el-tramo.be>
To: XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 17:27:05 -0000

> If we didn't do this, we'd need some additional signalling to distinguish,
> or else we'd have to use distinct TCP ports for all three, which seems
> suboptimal, especially when we're already using this quite happily.

The 'correct' way is probably to use doctypes on the XML stream, but
let's not go there. I'm in favor of keeping default namespaces on the
toplevel element of the stream, as a way to distinguish the type of
stream.

I also agree that the namespace prefix shouldn't be mandatory.

cheers,
Remko

From jehan.marmottard@gmail.com  Wed Sep 23 10:45:58 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAD763A659A for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiObgy5CaTk3 for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 10:45:57 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 8752A3A67AF for <xmpp@ietf.org>; Wed, 23 Sep 2009 10:45:56 -0700 (PDT)
Received: by ewy28 with SMTP id 28so1369985ewy.42 for <xmpp@ietf.org>; Wed, 23 Sep 2009 10:47:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=WsxBweJUK9SagluPCP/Tvz/nr/ob1iNFe1Yjb19T4wM=; b=rhNf3JJCmbM1IXfpomUnUvGbQIO+s0hqAWIPRPJ9WGznxT9qIFBq0+EjhV/LpLuvjM vWaL+eJ2IkBUi1rdTcLL/uqo1yBMlwALHK6hKYh9ziXVVm+SRzWS2h/KZolERWBpsv4p vzeewzaIdXhrmJxvt61FHemnBXIajEmlTSbyQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hug77osN+/6DqwtpiJC9osqnKFXECD0Fp777xmjO+Q7RO+8TAiAvNsCStb4VnVs55f axUo8QeM7adKrrQ67dV6OPtSRXmr4kIAUTa/4yLpoYNrN37ho21DZ65pwqXCQb+tTYZA 5YQSfo/8s9vpQHOFV9rwRisJD3Q44MSvY/qJU=
MIME-Version: 1.0
Received: by 10.211.173.16 with SMTP id a16mr2947854ebp.66.1253728020825; Wed,  23 Sep 2009 10:47:00 -0700 (PDT)
In-Reply-To: <75a410780909231045n623f3508i7aed8cee6264551c@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <14412.1253725891.012680@puncture> <75a410780909231045n623f3508i7aed8cee6264551c@mail.gmail.com>
Date: Thu, 24 Sep 2009 02:47:00 +0900
Message-ID: <75a410780909231047j461846farcdd9b2539f0ac1a2@mail.gmail.com>
From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: multipart/alternative; boundary=00504502c87a53873f0474424dd2
Subject: [xmpp] Fwd:  Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 17:45:58 -0000

--00504502c87a53873f0474424dd2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Oups sorry, this message went only to Dave, not the whole list. :-)

Jehan

---------- Forwarded message ----------
From: Jehan Pag=E8s <jehan.marmottard@gmail.com>
Date: 2009/9/24
Subject: Re: [xmpp] Use of namespace in RFC 3920
To: Dave Cridland <dave@cridland.net>


Hi,

On Thu, Sep 24, 2009 at 2:11 AM, Dave Cridland <dave@cridland.net> wrote:

>
>   So you MUST absolutely have a
>> default namespace in the root <stream>, and this one MUST be the one
>> for the stanza ("jabber:client" or "jabber:server", most typically)
>>
>
> Right, this allows us to detirmine whether it's a client, server, or
> component. We actually do this - so if you want to, you can point clients=
,
> components, and servers alike at a single port and it'll all just work.
>
> If we didn't do this, we'd need some additional signalling to distinguish=
,
> or else we'd have to use distinct TCP ports for all three, which seems
> suboptimal, especially when we're already using this quite happily.
>

I don't really see the problem. This can be seen also on the received
stanza, which is the same thing. I don't tell we stop using namespace, but
that telling they MUST (or SHOULD) be done on such specific way does not
seem right to me. What matters, in my logic, is just the finale qualified
name of stanza, which means the tuple (namespace, local name). So you can
still redirect clients, components and servers to the same port. And you
will still distinguish them with the finale qualified name (however it has
been qualified: default ns, prefix, etc.).


>   +
>> you MUST have a prefix declared, for the stream related first level
>> elements,
>>
>
> Well if you've already got a default namespace, it stands to reason you
> can't have the stream top-level elements in it.
>

No, I don't say that it is not a logical way to do. I just say that there
are others and that the RFC should not force to do a specific way. For
instance, you could imagine that you set the stream ns as the default ns an=
d
declare a prefix for "jabber:client" (or "jabber:server", or whatever) and
use this prefix in the stanzas, instead of doing the opposite. I just say i=
t
should not matter, as at the end, what matters is the qualified name.


>
>   and this prefix MUST be "stream".
>>
>
> I don't care about this, and FWIW, we do not rely on it. Also, it's a
> SHOULD not a MUST, and a MAY rely on. The latter, I think, needs changing=
 -
> this should be SHOULD (because of legacy systems) and MUST NOT rely on.
>

Ok right this is a "SHOULD", not a "MUST". But "SHOULD" is still a strong
"recommandation". This is for me different than saying that legacy systems
were doing a check on this, so it is a good idea tocontinue to use the name
"stream"



>
>
>  So for instance, the current RFC asks me to reject and consider this
>> stream start as an error, though it is perfectly valid XML and
>> conforming to XMPP:
>>
>> <toto:stream
>>          from=3D'juliet@im.example.com'
>>          to=3D'im.example.com'
>>          version=3D'1.0'
>>          xml:lang=3D'en'
>>          xmlns=3D'jabber:client'
>>          xmlns:toto=3D'http://etherx.jabber.org/streams'>
>>
>>
>>  No, the RFC says you MAY reject it. Section 11.2.1 says so.
>

Yes. We MAY, you are right. I am not forced. Still, the RFC tells me it is
perfectly good (yet not mandatory, I agree) to refuse a perfectly well
formed (and valid) XML, which conforms to the XMPP DTD, namespace choices,
and so on. I personally don't think this is really nice.

>
>
>  And many other examples: for instance, if I prefer to use a declared
>> namespace for "jabber:client" instead of a default namespace, why
>> couldn't I?
>>
>
> See above. Various other things, like XEP-0220, get triggered by the
> default namespace choice of the initiator of the stream.
>

Yes. And I agree, but my answer is the same: I don't see the difference of
getting namespace on the stanzas themselves.


>
>  For historical reasons, some older implementations may accept only a
>> stream element qualification through a prefix named "stream" (and not
>> for instance through a default namespace, nor a prefix named other
>> than "stream"), declared in the initial <stream/> element. For
>> backwards compatibility, it may therefore be a good idea, though not
>> mandatory, to declare a prefix named "stream" and with value
>> "http://etherx.jabber.org/streams" in the <stream/> header. However an
>> implementation MUST NOT send any error, hence reject a stream doing
>> differently, as long as the qualified names for the <stream/>,
>> <features/> and <error/> element are correct with this alternative
>> method.
>>
>
> "it may therefore be a good idea, though not mandatory" =3D SHOULD.
>
>
Yes. I agree globally. But I still think this "SHOULD" is too strong, so no=
t
exactly the same. Note also that what I added is that I removed the
possibility of the error. That's for me the main point. So yes we can keep
it a "SHOULD", but it must not prevent from doing another way, perfectly
XML-compliant.

Bye.

Jehan

--00504502c87a53873f0474424dd2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Oups sorry, this message went only to Dave, not the whole list. :-)<br><br>=
Jehan<br><br><div class=3D"gmail_quote">---------- Forwarded message ------=
----<br>From: <b class=3D"gmail_sendername">Jehan Pag=E8s</b> <span dir=3D"=
ltr">&lt;<a href=3D"mailto:jehan.marmottard@gmail.com">jehan.marmottard@gma=
il.com</a>&gt;</span><br>
Date: 2009/9/24<br>Subject: Re: [xmpp] Use of namespace in RFC 3920<br>To: =
Dave Cridland &lt;<a href=3D"mailto:dave@cridland.net">dave@cridland.net</a=
>&gt;<br><br><br>Hi,<br><br><div class=3D"gmail_quote"><div class=3D"im">On=
 Thu, Sep 24, 2009 at 2:11 AM, Dave Cridland <span dir=3D"ltr">&lt;<a href=
=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(=
204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
=A0So you MUST absolutely have a<br>
default namespace in the root &lt;stream&gt;, and this one MUST be the one<=
br>
for the stanza (&quot;jabber:client&quot; or &quot;jabber:server&quot;, mos=
t typically)<br>
</blockquote>
<br></div>
Right, this allows us to detirmine whether it&#39;s a client, server, or co=
mponent. We actually do this - so if you want to, you can point clients, co=
mponents, and servers alike at a single port and it&#39;ll all just work.<b=
r>


<br>
If we didn&#39;t do this, we&#39;d need some additional signalling to disti=
nguish, or else we&#39;d have to use distinct TCP ports for all three, whic=
h seems suboptimal, especially when we&#39;re already using this quite happ=
ily.<div>

<br></div></blockquote></div><div><br>I don&#39;t really see the problem. T=
his can be seen also on the received stanza, which is the same thing. I don=
&#39;t tell we stop using namespace, but that telling they MUST (or SHOULD)=
 be done on such specific way does not seem right to me. What matters, in m=
y logic, is just the finale qualified name of stanza, which means the tuple=
 (namespace, local name). So you can still redirect clients, components and=
 servers to the same port. And you will still distinguish them with the fin=
ale qualified name (however it has been qualified: default ns, prefix, etc.=
).<br>

<br></div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"bord=
er-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-l=
eft: 1ex;"><div>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
=A0+<br>
you MUST have a prefix declared, for the stream related first level<br>
elements,<br>
</blockquote>
<br></div>
Well if you&#39;ve already got a default namespace, it stands to reason you=
 can&#39;t have the stream top-level elements in it.<div><br></div></blockq=
uote></div><div><br>No, I don&#39;t say that it is not a logical way to do.=
 I just say that there are others and that the RFC should not force to do a=
 specific way. For instance, you could imagine that you set the stream ns a=
s the default ns and declare a prefix for &quot;jabber:client&quot; (or &qu=
ot;jabber:server&quot;, or whatever) and use this prefix in the stanzas, in=
stead of doing the opposite. I just say it should not matter, as at the end=
, what matters is the qualified name.<br>

=A0<br></div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"b=
order-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddin=
g-left: 1ex;"><div>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
=A0and this prefix MUST be &quot;stream&quot;.<br>
</blockquote>
<br></div>
I don&#39;t care about this, and FWIW, we do not rely on it. Also, it&#39;s=
 a SHOULD not a MUST, and a MAY rely on. The latter, I think, needs changin=
g - this should be SHOULD (because of legacy systems) and MUST NOT rely on.=
<div>

<br></div></blockquote></div><div><br>Ok right this is a &quot;SHOULD&quot;=
, not a &quot;MUST&quot;. But &quot;SHOULD&quot; is still a strong &quot;re=
commandation&quot;. This is for me different than saying that legacy system=
s were doing a check on this, so it is a good idea tocontinue to use the na=
me &quot;stream&quot;<br>

<br>=A0<br></div><div class=3D"im"><blockquote class=3D"gmail_quote" style=
=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p=
adding-left: 1ex;"><div>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So for instance, the current RFC asks me to reject and consider this<br>
stream start as an error, though it is perfectly valid XML and<br>
conforming to XMPP:<br>
<br>
&lt;toto:stream<br>
 =A0 =A0 =A0 =A0 =A0from=3D&#39;<a href=3D"mailto:juliet@im.example.com" ta=
rget=3D"_blank">juliet@im.example.com</a>&#39;<br>
 =A0 =A0 =A0 =A0 =A0to=3D&#39;<a href=3D"http://im.example.com" target=3D"_=
blank">im.example.com</a>&#39;<br>
 =A0 =A0 =A0 =A0 =A0version=3D&#39;1.0&#39;<br>
 =A0 =A0 =A0 =A0 =A0xml:lang=3D&#39;en&#39;<br>
 =A0 =A0 =A0 =A0 =A0xmlns=3D&#39;jabber:client&#39;<br>
 =A0 =A0 =A0 =A0 =A0xmlns:toto=3D&#39;<a href=3D"http://etherx.jabber.org/s=
treams" target=3D"_blank">http://etherx.jabber.org/streams</a>&#39;&gt;<br>
<br>
<br>
</blockquote></div>
No, the RFC says you MAY reject it. Section 11.2.1 says so.<div><br></div><=
/blockquote></div><div><br>Yes. We MAY, you are right. I am not forced. Sti=
ll, the RFC tells me it is perfectly good (yet not mandatory, I agree) to r=
efuse a perfectly well formed (and valid) XML, which conforms to the XMPP D=
TD, namespace choices, and so on. I personally don&#39;t think this is real=
ly nice.<br>

</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"border-l=
eft: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:=
 1ex;"><div>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And many other examples: for instance, if I prefer to use a declared<br>
namespace for &quot;jabber:client&quot; instead of a default namespace, why=
<br>
couldn&#39;t I?<br>
</blockquote>
<br></div>
See above. Various other things, like XEP-0220, get triggered by the defaul=
t namespace choice of the initiator of the stream.<div><br></div></blockquo=
te></div><div><br>Yes. And I agree, but my answer is the same: I don&#39;t =
see the difference of getting namespace on the stanzas themselves.<br>

=A0<br></div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"b=
order-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddin=
g-left: 1ex;"><div>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For historical reasons, some older implementations may accept only a<br>
stream element qualification through a prefix named &quot;stream&quot; (and=
 not<br>
for instance through a default namespace, nor a prefix named other<br>
than &quot;stream&quot;), declared in the initial &lt;stream/&gt; element. =
For<br>
backwards compatibility, it may therefore be a good idea, though not<br>
mandatory, to declare a prefix named &quot;stream&quot; and with value<br>
&quot;<a href=3D"http://etherx.jabber.org/streams" target=3D"_blank">http:/=
/etherx.jabber.org/streams</a>&quot; in the &lt;stream/&gt; header. However=
 an<br>
implementation MUST NOT send any error, hence reject a stream doing<br>
differently, as long as the qualified names for the &lt;stream/&gt;,<br>
&lt;features/&gt; and &lt;error/&gt; element are correct with this alternat=
ive<br>
method.<br>
</blockquote>
<br></div>
&quot;it may therefore be a good idea, though not mandatory&quot; =3D SHOUL=
D.<br>
<br></blockquote></div><div><br>Yes. I agree globally. But I still think th=
is &quot;SHOULD&quot; is too strong, so not exactly the same. Note also tha=
t what I added is that I removed the possibility of the error. That&#39;s f=
or me the main point. So yes we can keep it a &quot;SHOULD&quot;, but it mu=
st not prevent from doing another way, perfectly XML-compliant.<br>

=A0<br>Bye.<br><br>Jehan<br></div></div><br>
</div><br>

--00504502c87a53873f0474424dd2--

From mwild1@gmail.com  Wed Sep 23 13:37:56 2009
Return-Path: <mwild1@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A6B13A6822 for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 13:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WuhI2nvf1ZQX for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 13:37:55 -0700 (PDT)
Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 5C7233A6882 for <xmpp@ietf.org>; Wed, 23 Sep 2009 13:37:55 -0700 (PDT)
Received: by fxm27 with SMTP id 27so882486fxm.42 for <xmpp@ietf.org>; Wed, 23 Sep 2009 13:38:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EJ27X/6GPlCQVuuYYjRBlShfRJXQ3w/stcjryifK2aY=; b=t2kd/nURj3V9zHqI/0iNFBxhVtjFm3D5r5ssVAToUyyC5/pnWu/Na5Ub15jyjkvJF1 k72ASJjN5h7xuvOW0OBKl2h56Yw7H/Q5il87nKdMozdejDpyYqdermNPomxUYOeXnnqf CTgrq7OVZFY+VzKDRexErH7ac1ASRRMrgazXQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=HbBLw+tGgTELojbLaGj6minfSZFHe3uTJ+O0Z3mvIrlvt/k0q47J49IXOQ9ag22VbX 4oWW1QSDUIl99eBgeqfRNUgi41+yOrE+NTZOwCON6pNGoNqUg9aQbl6XZWUzyifCKPGl fgEAc6REOLZiM2yMvg0TY6UQ5dZ2k4enjj2Wg=
MIME-Version: 1.0
Received: by 10.204.162.143 with SMTP id v15mr2294225bkx.50.1253738337163;  Wed, 23 Sep 2009 13:38:57 -0700 (PDT)
In-Reply-To: <133fd4c60909231028v69a01c7v4c71b027778d02ea@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <14412.1253725891.012680@puncture> <133fd4c60909231028v69a01c7v4c71b027778d02ea@mail.gmail.com>
Date: Wed, 23 Sep 2009 21:38:57 +0100
Message-ID: <4db9cacb0909231338p49658c65h7c3d6ff0849ac61d@mail.gmail.com>
From: Matthew Wild <mwild1@gmail.com>
To: =?ISO-8859-1?Q?Remko_Tron=E7on?= <remko@el-tramo.be>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2009 20:37:56 -0000

2009/9/23 Remko Tron=E7on <remko@el-tramo.be>:
>> If we didn't do this, we'd need some additional signalling to distinguis=
h,
>> or else we'd have to use distinct TCP ports for all three, which seems
>> suboptimal, especially when we're already using this quite happily.
>
> The 'correct' way is probably to use doctypes on the XML stream, but
> let's not go there. I'm in favor of keeping default namespaces on the
> toplevel element of the stream, as a way to distinguish the type of
> stream.
>
> I also agree that the namespace prefix shouldn't be mandatory.
>

Simple +1 from me, since every implementation seems to be handling
these issues differently right now (either disallowing, or trying to
work around) it would be good to have official clarification.

Matthew

From cking@mumbo.ca  Wed Sep 23 21:41:42 2009
Return-Path: <cking@mumbo.ca>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14A2A3A67AC for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 21:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.717
X-Spam-Level: 
X-Spam-Status: No, score=-0.717 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6MA4iz7R5tN for <xmpp@core3.amsl.com>; Wed, 23 Sep 2009 21:41:41 -0700 (PDT)
Received: from renoir.mumbo.ca (renoir.mumbo.ca [67.223.232.134]) by core3.amsl.com (Postfix) with ESMTP id D181A3A67FF for <xmpp@ietf.org>; Wed, 23 Sep 2009 21:41:40 -0700 (PDT)
Received: from [192.168.1.15] (S0106001b63f2007e.gv.shawcable.net [24.69.175.15]) by renoir.mumbo.ca (Postfix) with ESMTPA id E56F250016 for <xmpp@ietf.org>; Wed, 23 Sep 2009 21:42:47 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
From: Curtis King <cking@mumbo.ca>
In-Reply-To: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
Date: Wed, 23 Sep 2009 21:42:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
To: xmpp@ietf.org
X-Mailer: Apple Mail (2.1076)
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 04:41:42 -0000

On 2009-09-23, at 9:01 AM, Jehan Pag=E8s wrote:

> There are other stuffs to change in the RFC related to this
> problematic. But for now let's launch the discussion from this point.
> :

What does this all gain us? I think there needs to-be a real benefit =20
to making such a change and I don't see one. Only a lot of potential =20
pain. IMHO, we should be tightening the scope of XML which can be sent =20=

not loosening it.

ck


From jehan.marmottard@gmail.com  Thu Sep 24 01:05:33 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63CED3A68E3 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcWEv9EP0B4R for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:05:32 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 4DF8D3A677D for <xmpp@ietf.org>; Thu, 24 Sep 2009 01:05:32 -0700 (PDT)
Received: by ewy28 with SMTP id 28so1995925ewy.42 for <xmpp@ietf.org>; Thu, 24 Sep 2009 01:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ac2NqhcN6rE9zbhQ1o0FSpjLUSF9VLCi37Z68n0HI7Y=; b=GQ40ehqJSCGbbHdxt3VA8if1E8SQHrpd5XYZJ98PVWhhd61igYuryrovf/G//lmsGK 3PRSu/ceGM0P3KqIFys00i16iOtGntJM2I9NJqUHXqH6GrMxNBC3brnbzuBDiQGycuFl KNiggGahG2Fv3YsyKPkLZMuhI8IBGHPenrcts=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=h/RHXDuo5fesbFMXVxrwcebNq1W6t5dd6jv3yVOFMZFhDQp2Vynm6OqO9oMz9F/H+3 j3rFz2u0BjUtVGuY6pz7148jlcMwlG/IUC5G1+K8pu9mr2b1LQQyEb6AQWY5SQN+1Rug DXraLeYP3ton53DPd4FNjuhk/2QDIDFfNV3YE=
MIME-Version: 1.0
Received: by 10.211.146.5 with SMTP id y5mr3787642ebn.41.1253779597320; Thu,  24 Sep 2009 01:06:37 -0700 (PDT)
In-Reply-To: <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com>
Date: Thu, 24 Sep 2009 17:06:36 +0900
Message-ID: <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com>
From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [xmpp] Fwd:  Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 08:05:33 -0000

Aaargh, sorry! Once again not to the list. I am really not used to
mailing list, sorry for this.


---------- Forwarded message ----------
From: Jehan Pag=E8s <jehan.marmottard@gmail.com>
Date: 2009/9/24
Subject: Re: [xmpp] Use of namespace in RFC 3920
To: Curtis King <cking@mumbo.ca>


Hi,

On Thu, Sep 24, 2009 at 1:42 PM, Curtis King <cking@mumbo.ca> wrote:
>
> What does this all gain us? I think there needs to-be a real benefit to
> making such a change and I don't see one. Only a lot of potential pain.
> IMHO, we should be tightening the scope of XML which can be sent not
> loosening it.
>

That's indeed what I am doing. Right now XMPP is not really following
XML rules. It made new ones, and make it more difficult.
Let's make the example from my experience. I am writing currently an
XMPP library, and I wrote also an XML library. My XML library, like
most of the others I have tried (the one which deals well with XML and
XML namespace RFC, at least), does expand the name of XML elements
into qualified names. So honestly it doesn't care how it has been
expanded, not does XML by definition. The problem is that the XMPP RFC
does. And this is problematic and a lot of pain for me.

If I want to really do like the XMPP RFC proposes, I should modify my
XML parser with surcharge about where a namespace has been declared or
set as default. This is what is lot of pain, according to me.
This is the current XMPP RFC which tightens XML and make its use
painful, not the opposite.
Bye.

Jehan

From remko.troncon@gmail.com  Thu Sep 24 01:37:21 2009
Return-Path: <remko.troncon@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF1EB3A689C for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7vSItlttnO0 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:37:21 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 042C53A6919 for <xmpp@ietf.org>; Thu, 24 Sep 2009 01:37:20 -0700 (PDT)
Received: by ewy28 with SMTP id 28so2019476ewy.42 for <xmpp@ietf.org>; Thu, 24 Sep 2009 01:38:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=7zGTVKDpOg46vHRG8CRx+qSsruxYEn8brKhqBTOlAww=; b=TLhdozcyvvI/H0qJq55KYnKVPuP5xXIwQW5EO+UzJH6NzXVJhpeOKRxQA0qE4DQsA0 0bJC/N+VOYbcwQryf+jQcg/EsXC0uj49j6W1naruT6CFEDbqXfCJ+5Dzcv23i0TnkXx0 a5C2mxNg0R+FdYPTfWP61r/F+sxoy3TUisI8c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=dkf8cgHRRDmCBZOTXD67dn8uhW2e4XvaN8T77xIqHlX+Mi7QpXZ46IOQdk0Iu7SMMb +JV+oBVS4lPfCpPO3ZJyyEXAZxcvuHz2alyT1/p9VRm6qp9rpaMRxf9ykqP4l5+9nqPf rx8/mRX1xc6KrLcvESz7YvUAP75cOzQT2rR6k=
MIME-Version: 1.0
Sender: remko.troncon@gmail.com
Received: by 10.216.87.143 with SMTP id y15mr734892wee.39.1253781505738; Thu,  24 Sep 2009 01:38:25 -0700 (PDT)
In-Reply-To: <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com>
Date: Thu, 24 Sep 2009 10:38:25 +0200
X-Google-Sender-Auth: 7c08d2eb17d685e3
Message-ID: <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com>
From: =?UTF-8?Q?Remko_Tron=C3=A7on?= <remko@el-tramo.be>
To: XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 08:37:22 -0000

> That's indeed what I am doing. Right now XMPP is not really following
> XML rules. It made new ones, and make it more difficult.

As far as i remember, XMPP is following XML rules, but only made them
stricter, such that the parsers were simpler (i.e. didn't have to deal
with full XML spec). This implies that the serializers have to play by
some rules (which isn't so bad, since serializing doesn't necessarily
need an XML library).

I don't really see why you would need to modify your XML parser to
handle XMPP if it can handle XML, but maybe I'm missing something.

cheers,
Remko

From dave@cridland.net  Thu Sep 24 01:44:22 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 573563A67D9 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjZEqmNNasQ0 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 01:44:21 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 2454F3A6898 for <xmpp@ietf.org>; Thu, 24 Sep 2009 01:44:21 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SrsxoQBdmxPq@peirce.dave.cridland.net>; Thu, 24 Sep 2009 09:45:21 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com>
In-Reply-To: <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <17720.1253781940.785601@puncture>
Date: Thu, 24 Sep 2009 09:45:40 +0100
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?Q?Remko_Tron=C3=A7on?= <remko@el-tramo.be>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Encoded: Changed encoding from 8Bit for 7bit transmission
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 08:44:22 -0000

On Thu Sep 24 09:38:25 2009, Remko Tron=E7on wrote:
> > That's indeed what I am doing. Right now XMPP is not really  =

> following
> > XML rules. It made new ones, and make it more difficult.
> =

> As far as i remember, XMPP is following XML rules, but only made  =

> them
> stricter, such that the parsers were simpler (i.e. didn't have to  =

> deal
> with full XML spec). This implies that the serializers have to play  =

> by
> some rules (which isn't so bad, since serializing doesn't  =

> necessarily
> need an XML library).
> =

> I don't really see why you would need to modify your XML parser to
> handle XMPP if it can handle XML, but maybe I'm missing something.

You need to find out what the default namespace is bound to.

You can do this by concatenating a dummy element early on, if needs  =

be - so you insert a "<tracer/>", then look to see what namespace it  =

ended up with.

The serializer need to be able to explicitly set the default  =

namespace, instead of shoving everything under ugly machine generated  =

namespace prefices.

But this assumes that your XML library doesn't simply allow you to  =

lookup, and set, the default namespace prefix anyway - I can't really  =

believe that this would be unusual, given that it's useful for  =

producing compact serialized output in many cases.

Dave.
-- =

Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From jehan.marmottard@gmail.com  Thu Sep 24 04:09:34 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0B023A697A for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 04:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyQEGHzdgT6Z for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 04:09:34 -0700 (PDT)
Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by core3.amsl.com (Postfix) with ESMTP id 9EF603A69B7 for <xmpp@ietf.org>; Thu, 24 Sep 2009 04:09:33 -0700 (PDT)
Received: by ewy28 with SMTP id 28so2139803ewy.42 for <xmpp@ietf.org>; Thu, 24 Sep 2009 04:10:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=U5TwwGgtPmHbqKzsLof55yjSAKI+bNjhft0fYdxFZD8=; b=F40ReFOz0kO+2SIBSMsLsLOEP3BG6UPMr935mtmsXJoyT94m8y3ESM3jbH18pahhC0 9zvh1ilBTqP86I9DmiB7qXCDwkK2py9Pr9i367xz6Phph93NiU1vJa3QE0Ta6WU9IeDW NtSh+XXNC/Vi6hSCiqbqrD49m78Mp1povZXhM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Dcadzke7YutEckyIB1F5PKVuzDm92i233te4kgvtXX1NBoRGxCQRPhhOMfi6oshuXI iuPCTs43guoleANoGy53qmL5g+rp3ffJazYu4jOg2HVoemMuoDiokwiM/bTZug0nMdsn RfDE/Tbh828juKMIVuQzE+oqlcEjNA2qIcf1k=
MIME-Version: 1.0
Received: by 10.211.146.5 with SMTP id y5mr4007892ebn.41.1253790637961; Thu,  24 Sep 2009 04:10:37 -0700 (PDT)
In-Reply-To: <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com>
Date: Thu, 24 Sep 2009 20:10:37 +0900
Message-ID: <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com>
From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [xmpp] Fwd:  Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 11:09:35 -0000

Third message, third same reply mistake. I know: I am stupid.


---------- Forwarded message ----------
From: Jehan Pag=E8s <jehan.marmottard@gmail.com>
Date: Thu, Sep 24, 2009 at 8:01 PM
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
To: Remko Tron=E7on <remko@el-tramo.be>


Hi,

2009/9/24 Remko Tron=E7on <remko@el-tramo.be>:
>> That's indeed what I am doing. Right now XMPP is not really following
>> XML rules. It made new ones, and make it more difficult.
>
> As far as i remember, XMPP is following XML rules, but only made them
> stricter, such that the parsers were simpler (i.e. didn't have to deal
> with full XML spec). This implies that the serializers have to play by
> some rules (which isn't so bad, since serializing doesn't necessarily
> need an XML library).
>

you are right. But I think this may have been considered simpler some
time ago, maybe depending on the state of the art of XML parsers and
serializers at that time. But nowaydays, it does not look to me that
these XMPP particularities make parsing/serialization really simpler
or better than the basic XML way. Or maybe I don't see the point. I am
not an expert of all what has been done on XML and on all the kind of
optimizations that can be done. Just as of for now, I don't see how
easier/faster/better these particularities make XML parsing, nor
serialization, compared to the more general way of XML.

f you have any link about how some of your implementations may use
such namespace particularities of XMPP to optimize parsing or
serialization, I would be happy to read on. Maybe there can be
something that I don't get, and then I may understand better your
reticence to change.

For my own, the XML I send still follow these rules anyway. But what
bothers me the most is that we are asked (some MUSTs), or encouraged
(some SHOULDs), to reject some well-formed (in the meaning of XML
namespace) and valid XML, even though it corresponds to XMPP DTD. This
is why it does seem more like a patch on the RFC (instead of on codes)
to make developper's life easier (or not: for me, not even). That's
does not look like the best way.

> I don't really see why you would need to modify your XML parser to
> handle XMPP if it can handle XML, but maybe I'm missing something.
>

In fact when I parse the XML stream, I just keep the namespace
context, but I remove the namespace prefix declarations and default
namespaces after having used the information for expansion. At the
time I was writing the XML parser, it was looking the cleaner way
because the (default and prefix) ns declarations are not meaningful
attributes outside of name qualification. So they become just useless
(if not attribute pollution) once the namespace expansion has been
done.

Then I wrote the XMPP parser based upon my XML parser, hence the XMPP
parser gets the qualified name directly. I could change it of course
and let the ns declarations into the attributes. It is not as though
it was particularly difficult. But then I add an additional, though
useless, complexity (check not only the qualified names, but also how
they have been qualified) to my XMPP parser + the fact that I still
don't see any reason for this + the fact that I will be refusing
well-formed and valid XML (so by principle, it is also annoying: XMPP
namespace usage are not following the W3C recommandations).
Bye.

Jehan

From dave@cridland.net  Thu Sep 24 08:02:34 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABACA3A692C for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wls4s09JDSGa for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:02:34 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 93EC33A6359 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:02:33 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SruKRwBdmw9R@peirce.dave.cridland.net>; Thu, 24 Sep 2009 16:03:35 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com>
In-Reply-To: <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <17720.1253804637.072163@puncture>
Date: Thu, 24 Sep 2009 16:03:57 +0100
From: Dave Cridland <dave@cridland.net>
To: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Encoded: Changed encoding from 8Bit for 7bit transmission
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 15:02:34 -0000

On Thu Sep 24 12:10:37 2009, Jehan Pag=E8s wrote:
> Then I wrote the XMPP parser based upon my XML parser, hence the  =

> XMPP
> parser gets the qualified name directly. I could change it of course
> and let the ns declarations into the attributes. It is not as though
> it was particularly difficult. But then I add an additional, though
> useless, complexity (check not only the qualified names, but also  =

> how
> they have been qualified) to my XMPP parser + the fact that I still
> don't see any reason for this + the fact that I will be refusing
> well-formed and valid XML (so by principle, it is also annoying:  =

> XMPP
> namespace usage are not following the W3C recommandations).

<foo/> is also well-formed XML. You - hopefully - reject that too,  =

because it's not valid XMPP.

The spec says very little - intentionally - about the validity of the  =

XML involved.

Dave.
-- =

Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From jehan.marmottard@gmail.com  Thu Sep 24 08:34:44 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E4F828C128 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42JQayL5tUNw for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:34:43 -0700 (PDT)
Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by core3.amsl.com (Postfix) with ESMTP id 76E5D28C110 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:34:42 -0700 (PDT)
Received: by ewy2 with SMTP id 2so559140ewy.10 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:35:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=rG17UhtB8so6BOsaVM7h7YkWybv5nGAciEDIrQlDreM=; b=moJmSBkQjgxZ6o80QyakrErw5bltTAGtLrK4Gm66WK9aqlJeKiBFQUDFlHTZKuqk4w D2ZaByJqPDYaDSsjg6N4h9N75s/oatwFcRQtZlB2pwPiijwxRaf12nlNH3CR1Xf1Ji21 DLqegNuBTogvAhvIMNVuGByKIJE/nBl49D8AA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Cr5V73uA3vut9Gx85t7PqiuTOHv5NASIjfXEIHFUDQ3tM4CtWlvIMUIWnUX8Q9+nIT hiTxnB1IwyjU9ilq+t7ZRP3raFYxScFVhbjeKT51gfYPO3EjaOxW9HWq2wW0w+SYjx7J /JQpdasRH1EgfjldLefYfkxVrEcRr1shMLCQA=
MIME-Version: 1.0
Received: by 10.210.94.7 with SMTP id r7mr7672410ebb.36.1253806548833; Thu, 24  Sep 2009 08:35:48 -0700 (PDT)
In-Reply-To: <17720.1253804637.072163@puncture>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture>
Date: Fri, 25 Sep 2009 00:35:48 +0900
Message-ID: <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com>
From: "jehan.marmottard" <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 15:34:44 -0000

Hi,

On Fri, Sep 25, 2009 at 12:03 AM, Dave Cridland <dave@cridland.net> wrote:
>
> <foo/> is also well-formed XML. You - hopefully - reject that too, because
> it's not valid XMPP.
>

I do. But what bothers me is more that I am asked to refuse such
opening stream for instance:

 <stream:stream
          from='juliet@im.example.com'
          to='im.example.com'
          version='1.0'
          xml:lang='en'
          xmlns:client='jabber:client'
          xmlns:stream='http://etherx.jabber.org/streams'>

If the sender expects to send prefixed stanzas is an example:
"<client:message ..." Why a program would do that? I don't know and I
don't care because I expand the namespace, as required by the XML
namespace recommandation. So this is transparent for my
implementation. But for some strange reason XMPP wants me to make some
kind of exception:

---
12.2.2. Default Namespace

   A default namespace declaration is REQUIRED [...]
---

Another example is this:

 <stream
          from='juliet@im.example.com'
          to='im.example.com'
          version='1.0'
          xml:lang='en'
          xmlns:client='jabber:client'
          xmlns='http://etherx.jabber.org/streams'>

----
12.2.1. Streams Namespace

   A streams namespace declaration is REQUIRED in all XML stream headers
   and the name of the streams namespace MUST be
   'http://etherx.jabber.org/streams'.  If this rule is violated, the
   entity that receives the offending stream header MUST return a stream
   error to the sending entity, which SHOULD be <invalid-namespace/> but
   MAY be <bad-format/>.
----

This is perfectly valid as for namespace qualification, but the RFC
"REQUIRES" a stream namespace declaration (why is a default ns for
stream not good? Once again this should be transparent).
Etc.

> The spec says very little - intentionally - about the validity of the XML
> involved.

Yes but it says these stuffs about how the namespaces MUST or SHOULD
be declared or set default, which I don't understand.

By the way, to come back to the example of the use of the default ns
as a "signal" for knowing if it is a client/server/component, I
already answered that you get this information anyway immediately
after (through a stanza).
But in fact I thought afterwards: you also get it in the stream
header, even without the default ns to "jabber:client/server". You get
this information from the "from" attributes:
- if there is no "from" attribute, then it is definitely a client, as
a server must set a "from".
- if there is a "from", then you know anyway your users, so you can
see if it is a client or a server.

But even without this, we still get all the necessary information on
the stanza qualified name anyway.
Bye.

Jehan

From metajack@gmail.com  Thu Sep 24 08:40:52 2009
Return-Path: <metajack@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2C303A67DA for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level: 
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEIi2QB+Uxi8 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:40:49 -0700 (PDT)
Received: from mail-bw0-f210.google.com (mail-bw0-f210.google.com [209.85.218.210]) by core3.amsl.com (Postfix) with ESMTP id ABCF73A6900 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:40:46 -0700 (PDT)
Received: by bwz6 with SMTP id 6so1394240bwz.37 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=XB5Fcpee4KFPdbEhiemIYcppUy9HcBhIQjQW3Zj1Dk4=; b=b7UQpEtUghv5FGAPbMAwXmoEf+kNK3rMbmRC30pWPKF76MOJ2U/u49yw9zmFsZaP8J COA7EACQRkebhyytInLYPHJBBDwYiM4jKvRGNHS+kVn/4Iv8/gS6d5Qt23/tm6fgfFWs +pNCtj9iofQ3zLbedH6B/05ATi10sFYF6aHSI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=wJTckPXHCiurjBjcllzpokMpGwKRYwphyYoi8iy8lHOUNP8gi27oydIr7NX6ZueErv Ae1HSZmqZKxM3BumI+7yoLbNfEcYuXq2e3PoHO2HHP9/82eEBYjlvLpg6DjKn2G6zvCj iWlZaOoUbWmWt58eR4SyKvur71LalkDNamFZo=
MIME-Version: 1.0
Sender: metajack@gmail.com
Received: by 10.204.155.71 with SMTP id r7mr3144769bkw.164.1253806910177; Thu,  24 Sep 2009 08:41:50 -0700 (PDT)
In-Reply-To: <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture> <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com>
Date: Thu, 24 Sep 2009 09:41:50 -0600
X-Google-Sender-Auth: 6b81497886a42040
Message-ID: <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com>
From: Jack Moffitt <jack@collecta.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 15:40:52 -0000

> But for some strange reason XMPP wants me to make some
> kind of exception:

The reason is not strange at all.

If you have a namespace prefix in one stream header, it must be in
another where it is used.  So if you allow arbitrary XML like you have
proposed there, then every server will have to translate from one
representation to another.  This means a complete parse and
reserialization cycle at each point.

If we all agree on a default namespace, this is not required, and is a
huge gain in efficiency.  Now XMPP servers don't even have to parse
stanzas.  They can simply regex out the to/from attributes and pass
the stanza on as a bag of bytes.

The <stream:stream> prefixes aren't really that big of a deal because
they are only between two endpoints and don't leak out to other
places, which is why I think it's ok to relax those.

jack.

From dave@cridland.net  Thu Sep 24 08:48:08 2009
Return-Path: <dave@cridland.net>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32CC428C121 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level: 
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWuMELTQt99r for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:48:07 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 0879D28C11A for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:48:07 -0700 (PDT)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <SruU9gBdmydi@peirce.dave.cridland.net>; Thu, 24 Sep 2009 16:49:10 +0100
X-SMTP-Protocol-Errors: NORDNS
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture> <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com> <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com>
In-Reply-To: <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <17720.1253807371.877093@puncture>
Date: Thu, 24 Sep 2009 16:49:31 +0100
From: Dave Cridland <dave@cridland.net>
To: Jack Moffitt <jack@collecta.com>, XMPP Working Group <xmpp@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 15:48:08 -0000

On Thu Sep 24 16:41:50 2009, Jack Moffitt wrote:
> If we all agree on a default namespace, this is not required, and  
> is a
> huge gain in efficiency.  Now XMPP servers don't even have to parse
> stanzas.  They can simply regex out the to/from attributes and pass
> the stanza on as a bag of bytes.

Not that you can actually do quite that, but it's certainly true you  
can get a lot closer to lexing than parsing, and remove potentially  
all the reserialization.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From melo@simplicidade.org  Thu Sep 24 08:59:38 2009
Return-Path: <melo@simplicidade.org>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C847D28C107 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lM+9-3BKMvC4 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 08:59:38 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id 5B47C3A6A15 for <xmpp@ietf.org>; Thu, 24 Sep 2009 08:59:36 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so390154eye.51 for <xmpp@ietf.org>; Thu, 24 Sep 2009 09:00:41 -0700 (PDT)
Received: by 10.210.156.7 with SMTP id d7mr7847738ebe.16.1253808041430; Thu, 24 Sep 2009 09:00:41 -0700 (PDT)
Received: from ?192.168.0.101? (bl4-150-254.dsl.telepac.pt [81.193.150.254]) by mx.google.com with ESMTPS id 28sm715744eyg.16.2009.09.24.09.00.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Sep 2009 09:00:40 -0700 (PDT)
Message-Id: <472A4811-807F-423D-9492-84D4020DF3D2@simplicidade.org>
From: Pedro Melo <melo@simplicidade.org>
To: XMPP <xmpp@ietf.org>
In-Reply-To: <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 24 Sep 2009 17:00:32 +0100
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <20E40716-139E-4277-AD5B-E4218AB3CB82@mumbo.ca> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture> <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com> <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 15:59:38 -0000

On 2009/09/24, at 16:41, Jack Moffitt wrote:

> If you have a namespace prefix in one stream header, it must be in
> another where it is used.  So if you allow arbitrary XML like you have
> proposed there, then every server will have to translate from one
> representation to another.  This means a complete parse and
> reserialization cycle at each point.

+1.

> If we all agree on a default namespace, this is not required, and is a
> huge gain in efficiency.  Now XMPP servers don't even have to parse
> stanzas.  They can simply regex out the to/from attributes and pass
> the stanza on as a bag of bytes.

-1 :)

You still need to at least lex it to make sure that it is well-formed  
XML.

But yes, after that you should be able to pass along the entire string  
buffer.

> The <stream:stream> prefixes aren't really that big of a deal because
> they are only between two endpoints and don't leak out to other
> places, which is why I think it's ok to relax those.

Also, by placing the stanzas that do cross XML streams (presence,  
message, and iq) in the default namespace, you can transport the  
string buffer without further processing.

That another reason not to declare extra namespaces in the <stream>  
opening node that would be used inside stanzas.

Best 

From k.i.smith@gmail.com  Thu Sep 24 09:48:20 2009
Return-Path: <k.i.smith@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF1CB28C144 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 09:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yL3xtccAvd1w for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 09:48:20 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id 44A6B28C135 for <xmpp@ietf.org>; Thu, 24 Sep 2009 09:48:20 -0700 (PDT)
Received: by pxi3 with SMTP id 3so2296862pxi.31 for <xmpp@ietf.org>; Thu, 24 Sep 2009 09:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=V5CLhSN2RJBDf7qG7P6qmydfi0mMYOlNFXtnn0yL9J4=; b=jAwTvc2LgeAMjQJkAcqXWCRH3Ym1bHK3pNpRUAynmQQhyVL3ObF5dLGJIWqmAjFp3K JS+H5BYS2u4/S59kKiA8QADj16TdYNxm9PQd068mfT3FwfuxR/aIbB+/CWobGJ+dJCKx OhsXhzHVglAqa7AamaxdOTEllaYzu9jCqsjUw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=caelilmpaVVqhzxA70dZ4KlgoF3EeIkKk76jOvJ+IaRbMs716PY9iUWR7azTYPDk9l HRWES3DtxTax9y4ro+tqHUL/a6cixL4GtalRw9s//dTbtlpW3zrBq0zTO0qwQreiIVZi X6vy2tHr+eT4lpeRTRU+srpgrgnNCzK4RVMe4=
MIME-Version: 1.0
Sender: k.i.smith@gmail.com
Received: by 10.140.144.2 with SMTP id r2mr325845rvd.0.1253810966834; Thu, 24  Sep 2009 09:49:26 -0700 (PDT)
In-Reply-To: <472A4811-807F-423D-9492-84D4020DF3D2@simplicidade.org>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <75a410780909240105t6aa48a8fued8044c155a6dab4@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture> <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com> <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com> <472A4811-807F-423D-9492-84D4020DF3D2@simplicidade.org>
Date: Thu, 24 Sep 2009 17:49:26 +0100
X-Google-Sender-Auth: 2d93088ab4a59ed9
Message-ID: <f5aae3ec0909240949y4f03196h3fd842e2742d5e1e@mail.gmail.com>
From: Kevin Smith <kevin@kismith.co.uk>
To: XMPP <xmpp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: kevin@kismith.co.uk
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 16:48:21 -0000

I don't have anything to add to this discussion, I'd just like to
plant my flag in the "Show me some benefit to this before we consider
breaking a large proportion of running server code" camp.

/K

From Joe.Hildebrand@webex.com  Thu Sep 24 10:17:43 2009
Return-Path: <Joe.Hildebrand@webex.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 84B543A6A85 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 10:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.269
X-Spam-Level: 
X-Spam-Status: No, score=-104.269 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ki2GYDFsz8jt for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 10:17:42 -0700 (PDT)
Received: from gw1.webex.com (gw1.webex.com [64.68.122.208]) by core3.amsl.com (Postfix) with SMTP id C6A7E3A6A7F for <xmpp@ietf.org>; Thu, 24 Sep 2009 10:17:42 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw1.webex.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 24 Sep 2009 10:18:51 -0700
Received: from 64.101.74.200 ([64.101.74.200]) by SRV-EXSC03.webex.local ([192.168.252.200]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 24 Sep 2009 17:18:11 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 24 Sep 2009 11:18:10 -0600
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Jehan =?ISO-8859-1?B?UGFn6HM=?= <jehan.marmottard@gmail.com>, <xmpp@ietf.org>
Message-ID: <C6E105F2.146D3%joe.hildebrand@webex.com>
Thread-Topic: [xmpp] Fwd:  Use of namespace in RFC 3920
Thread-Index: Aco9Ov1EL34efPvUlEyFjDlKtN6uyw==
In-Reply-To: <75a410780909231047j461846farcdd9b2539f0ac1a2@mail.gmail.com>
IM-ID: xmpp:jhildebrand@corp.jabber.com
Presence-ID: xmpp:jhildebrand@corp.jabber.com
Jabber-ID: jhildebrand@corp.jabber.com
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 24 Sep 2009 17:18:51.0407 (UTC) FILETIME=[15F2A9F0:01CA3D3B]
Subject: Re: [xmpp] Fwd:  Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 17:17:43 -0000

(in my role as individual, not as chair)


On 9/23/09 11:47 AM, "Jehan Pag=E8s" <jehan.marmottard@gmail.com> wrote:

> No, I don't say that it is not a logical way to do. I just say that there
> are others and that the RFC should not force to do a specific way.

The RFC should promote interoperability, and backwards-compatibility is a
goal from the charter.

> For
> instance, you could imagine that you set the stream ns as the default ns =
and
> declare a prefix for "jabber:client" (or "jabber:server", or whatever) an=
d
> use this prefix in the stanzas, instead of doing the opposite. I just say=
 it
> should not matter, as at the end, what matters is the qualified name.

As long as your server has not been coded to check the first byte of the
element name for fast routing decisions.  I know of at least two servers
that do this.

--=20
Joe Hildebrand


From metajack@gmail.com  Thu Sep 24 10:28:22 2009
Return-Path: <metajack@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FCAE3A699D for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 10:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGAh8OmvXYp8 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 10:28:21 -0700 (PDT)
Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 7F70B3A6877 for <xmpp@ietf.org>; Thu, 24 Sep 2009 10:28:21 -0700 (PDT)
Received: by fxm27 with SMTP id 27so1523856fxm.42 for <xmpp@ietf.org>; Thu, 24 Sep 2009 10:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=R+xLB7IYNk9W6wYK/+/XWUwgmsGvZiQ71+4czEhHR50=; b=nuesBfPxMaypuwo+HflHAp4CaeznZQiUmQ0DaZglWPCofIWwTxF4ayqZivG8XItV2n rl7nTVr71e0vOMbRMfuAIEuVCL8VL0cERR4DWZklMSR4y/i11yGEzeSedFDoVD0MgohJ QDr958zNhpZ67HC7EHa2UxJIy2KB8P28K2RVs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=TXIoHD5/t2wOYeYTmWrpHLF5citYb8lv+YpLqE4UdxEfUi9nCbaaC+AJBzJj6Xq5OL y0xXwczmGjH7y9e6XHo2/HgZFYz1RwukifHZndF12/SvJ6OqKze+Xvg6atR6Abhh9MpD Xru6Ko2nW8KVL8HOmakXHwhtly7UpeUGEyQ74=
MIME-Version: 1.0
Sender: metajack@gmail.com
Received: by 10.204.141.3 with SMTP id k3mr3247831bku.177.1253813366112; Thu,  24 Sep 2009 10:29:26 -0700 (PDT)
In-Reply-To: <C6E105F2.146D3%joe.hildebrand@webex.com>
References: <75a410780909231047j461846farcdd9b2539f0ac1a2@mail.gmail.com> <C6E105F2.146D3%joe.hildebrand@webex.com>
Date: Thu, 24 Sep 2009 11:29:26 -0600
X-Google-Sender-Auth: 05ef208337f51aea
Message-ID: <9b58f4550909241029i2b08d730nccc80fc37bcf40d3@mail.gmail.com>
From: Jack Moffitt <jack@collecta.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 17:28:22 -0000

> As long as your server has not been coded to check the first byte of the
> element name for fast routing decisions. =A0I know of at least two server=
s
> that do this.

Surely it's not that much less efficient to check the first byte
following the ':' instead?  This does at least provide a good reason
why it was set in stone to begin with.

jack.

From Joe.Hildebrand@webex.com  Thu Sep 24 11:39:07 2009
Return-Path: <Joe.Hildebrand@webex.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C26F13A6407 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 11:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.714
X-Spam-Level: 
X-Spam-Status: No, score=-103.714 tagged_above=-999 required=5 tests=[AWL=-0.578, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Egr-tE8M2tml for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 11:39:07 -0700 (PDT)
Received: from gw2.webex.com (gw2.webex.com [64.68.122.209]) by core3.amsl.com (Postfix) with SMTP id 18FDB3A68E8 for <xmpp@ietf.org>; Thu, 24 Sep 2009 11:39:05 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw2.webex.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 24 Sep 2009 11:40:15 -0700
Received: from 64.101.74.200 ([64.101.74.200]) by SRV-EXSC03.webex.local ([192.168.252.200]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 24 Sep 2009 18:39:47 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 24 Sep 2009 12:39:46 -0600
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Jack Moffitt <jack@collecta.com>, <xmpp@ietf.org>
Message-ID: <C6E11912.14703%joe.hildebrand@webex.com>
Thread-Topic: [xmpp] Fwd: Use of namespace in RFC 3920
Thread-Index: Aco9RmOCcDsPKmLHuEWkAJw3h8UY/Q==
In-Reply-To: <9b58f4550909241029i2b08d730nccc80fc37bcf40d3@mail.gmail.com>
IM-ID: xmpp:jhildebrand@corp.jabber.com
Presence-ID: xmpp:jhildebrand@corp.jabber.com
Jabber-ID: jhildebrand@corp.jabber.com
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 24 Sep 2009 18:40:15.0124 (UTC) FILETIME=[74DEBD40:01CA3D46]
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 18:39:07 -0000

On 9/24/09 11:29 AM, "Jack Moffitt" <jack@collecta.com> wrote:

>> As long as your server has not been coded to check the first byte of the
>> element name for fast routing decisions. =A0I know of at least two servers
>> that do this.
>=20
> Surely it's not that much less efficient to check the first byte
> following the ':' instead?  This does at least provide a good reason
> why it was set in stone to begin with.

A) it's a backward-compatibility issue
B) the ':' is not at a fixed offset, so you have to scan up to it.

--=20
Joe Hildebrand


From stpeter@stpeter.im  Thu Sep 24 11:41:40 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A7F23A68E8 for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 11:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.804
X-Spam-Level: 
X-Spam-Status: No, score=-2.804 tagged_above=-999 required=5 tests=[AWL=-0.205, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKS7paFSNUsE for <xmpp@core3.amsl.com>; Thu, 24 Sep 2009 11:41:39 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id DC54B3A68D3 for <xmpp@ietf.org>; Thu, 24 Sep 2009 11:41:38 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 929E24007B; Thu, 24 Sep 2009 12:42:47 -0600 (MDT)
Message-ID: <4ABBBDA6.8080102@stpeter.im>
Date: Thu, 24 Sep 2009 12:42:46 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Joe Hildebrand <joe.hildebrand@webex.com>
References: <C6E11912.14703%joe.hildebrand@webex.com>
In-Reply-To: <C6E11912.14703%joe.hildebrand@webex.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: xmpp@ietf.org
Subject: Re: [xmpp] Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 18:41:41 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/24/09 12:39 PM, Joe Hildebrand wrote:
> On 9/24/09 11:29 AM, "Jack Moffitt" <jack@collecta.com> wrote:
> 
>>> As long as your server has not been coded to check the first byte of the
>>> element name for fast routing decisions.  I know of at least two servers
>>> that do this.
>> Surely it's not that much less efficient to check the first byte
>> following the ':' instead?  This does at least provide a good reason
>> why it was set in stone to begin with.
> 
> A) it's a backward-compatibility issue
> B) the ':' is not at a fixed offset, so you have to scan up to it.

The original jabberd server code looks to see if the element begins with
"<m" for message, "<p" for presence, and "<i" for IQ...

Not that that's the right thing to do, mind you.

/psa

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq7vaYACgkQNL8k5A2w/vwhqwCgscCCAMFbhvVZ8/YP1xhcO4Xg
MWAAnj26RFYL8bbQmF7MIUpjuBzIi9ke
=qelB
-----END PGP SIGNATURE-----

From jehan.marmottard@gmail.com  Fri Sep 25 11:06:33 2009
Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB72D3A6939 for <xmpp@core3.amsl.com>; Fri, 25 Sep 2009 11:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.81
X-Spam-Level: 
X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+lM0dMWzMoG for <xmpp@core3.amsl.com>; Fri, 25 Sep 2009 11:06:32 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 701153A677C for <xmpp@ietf.org>; Fri, 25 Sep 2009 11:06:32 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 22so619748eye.51 for <xmpp@ietf.org>; Fri, 25 Sep 2009 11:07:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=t4huUoSWpVTcJmWL+Lq6HrRdmi9doJb/anLvqzSGU7E=; b=sBUdMTOREGc2akIp6PWLMqzQwhEyWhA28wIOn32tgc59Ne10twkNRfcxHle1M7BSBL K8S94xLG7GEa4HWOx8PXJfg9k9Id1/Sk+4JAROMGZB1sOOgsWsTnDaLLoGRw4jSx0qPN 45rYEcvGd2tVEO66cdJddLviNl5dvPJSHiK8o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=t+qKBylQnvsiGLA9nf6KvwbWrHdZ9NRe24RZE9Ke2mL0kRousjY4UvEpxodAAWABIN tXFWmTDB/7ElnOAYBNDr4Jc9Zxz/LU79Vh6gKJyanU3ZTxp5SOXOMEJhPgiFE/uA1E/v rGI2E2HdORfMbPWQ4eYnZYRCM5eK1SeThtG7E=
MIME-Version: 1.0
Received: by 10.211.160.1 with SMTP id m1mr9573077ebo.50.1253902060889; Fri,  25 Sep 2009 11:07:40 -0700 (PDT)
In-Reply-To: <f5aae3ec0909240949y4f03196h3fd842e2742d5e1e@mail.gmail.com>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <75a410780909240106m23fbf5dbudb91cf86398f5150@mail.gmail.com> <133fd4c60909240138r455a15b5rf9c9eada60061ebf@mail.gmail.com> <75a410780909240401q72c84594qc6b2c2070c212fa4@mail.gmail.com> <75a410780909240410v6479c0adh80a215c5d5b64a56@mail.gmail.com> <17720.1253804637.072163@puncture> <75a410780909240835w69a61af2s47be85b16dd70a07@mail.gmail.com> <9b58f4550909240841y47cabbeay4804f1f386b55bcf@mail.gmail.com> <472A4811-807F-423D-9492-84D4020DF3D2@simplicidade.org> <f5aae3ec0909240949y4f03196h3fd842e2742d5e1e@mail.gmail.com>
Date: Sat, 26 Sep 2009 03:07:40 +0900
Message-ID: <75a410780909251107x4e625c35r8e4008c3bf54aa7c@mail.gmail.com>
From: =?ISO-8859-1?Q?Jehan_Pag=E8s?= <jehan.marmottard@gmail.com>
To: xmpp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 18:06:33 -0000

Hi all,

On Fri, Sep 25, 2009 at 1:49 AM, Kevin Smith <kevin@kismith.co.uk> wrote:
> I don't have anything to add to this discussion, I'd just like to
> plant my flag in the "Show me some benefit to this before we consider
> breaking a large proportion of running server code" camp.
>

Ok I don't really know what to answer now. The fact is that I
understand your answers and your reasons. There appears to be some
kind of "heavy" optimizations on some current usage which requires
apparently to be very liberal with XML (the example of just checking
first letter for instance). After this I still wonder, first, of much
these optimizations are that efficient compared to a more common
parsing method. But this is not that easy to say, so let's not make a
point of it...

Furthermore I wonder how much they can be considered "good" (but
"good" is often a pretty subjective word, even on technical topics).
On a strict "good design" point of view, the first-letter-check for
instance seems to me far too liberal on the strictness of XML. As
Peter said on his last email "Not that that's the right thing to do,
mind you.".

But still it exists. And apparently on at least 2 implementations, as
Joe said. So we don't want to break this. It is clear. Then I would
say 2 things:

1/ Still I know there are still a lot of softwares doing normal
parsing/reserialization. For them the modification would not be that
hard (remove the additional tests). Moreover it looks to me that these
restrictions are helpful to implementations wishing to make such kind
of very big shortcuts/optimizations (like checking a single byte
instead of a whole name) but are at the opposite a burden for the ones
which don't (making additional tests. That's not like very big burden,
but still it is useless).

2/ It is not as though it would suddenly break all implementations.
The RFC should still recommend (with SHOULD) to have a prefix named
"stream", to define it in the opening stream tag, and to have a
default namespace in this same tag. And people will most probably
follow these recommendations anyway, at least because they don't want
to be broken against some big servers using old implementations.
But at least the RFC is clean (I like clean designs) and this kind of
checks can be slowly removed from code bases in time (and never made
on new codes). No need to hurry. No need any "code camp". That's not
going to change our lives or make all implementation suddenly
obsolete. It will be just a "minor bug" which probably will never be
noticed by users.

But if that's not enough, I don't know what to say more.
Bye.

Jehan

From justin@affinix.com  Fri Sep 25 11:26:24 2009
Return-Path: <justin@affinix.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B842928C0E0 for <xmpp@core3.amsl.com>; Fri, 25 Sep 2009 11:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NYllgJL4PNQ for <xmpp@core3.amsl.com>; Fri, 25 Sep 2009 11:26:24 -0700 (PDT)
Received: from homiemail-a1.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by core3.amsl.com (Postfix) with ESMTP id 1479628B797 for <xmpp@ietf.org>; Fri, 25 Sep 2009 11:26:24 -0700 (PDT)
Received: from localhost (andross.dreamhost.com [75.119.221.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTP id C048C119DD3 for <xmpp@ietf.org>; Fri, 25 Sep 2009 11:27:34 -0700 (PDT)
From: Justin Karneges <justin@affinix.com>
To: xmpp@ietf.org
Date: Fri, 25 Sep 2009 11:27:37 -0700
User-Agent: KMail/1.9.10
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com> <f5aae3ec0909240949y4f03196h3fd842e2742d5e1e@mail.gmail.com> <75a410780909251107x4e625c35r8e4008c3bf54aa7c@mail.gmail.com>
In-Reply-To: <75a410780909251107x4e625c35r8e4008c3bf54aa7c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200909251127.38111.justin@affinix.com>
Subject: Re: [xmpp] Fwd: Fwd: Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 18:26:24 -0000

On Friday 25 September 2009 11:07:40 Jehan Pag=E8s wrote:
> 2/ It is not as though it would suddenly break all implementations.
> The RFC should still recommend (with SHOULD) to have a prefix named
> "stream", to define it in the opening stream tag, and to have a
> default namespace in this same tag. And people will most probably
> follow these recommendations anyway, at least because they don't want
> to be broken against some big servers using old implementations.
> But at least the RFC is clean (I like clean designs) and this kind of
> checks can be slowly removed from code bases in time (and never made
> on new codes). No need to hurry. No need any "code camp". That's not
> going to change our lives or make all implementation suddenly
> obsolete. It will be just a "minor bug" which probably will never be
> noticed by users.

Agree.

At this point, I figure a good number of us are using off-the-shelf, compli=
ant=20
XML parsers, and so I would like to see the XML generation rules relaxed.  =
We=20
can keep all of the backwards compatibility stuff marked with SHOULDs.

=2DJustin

From stpeter@stpeter.im  Wed Sep 30 15:55:13 2009
Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 667B53A6784 for <xmpp@core3.amsl.com>; Wed, 30 Sep 2009 15:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.311,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhtTZQo4T-uu for <xmpp@core3.amsl.com>; Wed, 30 Sep 2009 15:55:12 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 8B6003A6781 for <xmpp@ietf.org>; Wed, 30 Sep 2009 15:55:12 -0700 (PDT)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 194FA4007B; Wed, 30 Sep 2009 16:56:36 -0600 (MDT)
Message-ID: <4AC3E223.2090805@stpeter.im>
Date: Wed, 30 Sep 2009 16:56:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: =?UTF-8?B?SmVoYW4gUGFnw6hz?= <jehan.marmottard@gmail.com>,  XMPP <xmpp@ietf.org>
References: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
In-Reply-To: <75a410780909230901o1f705f94uee27599ffc3a31e1@mail.gmail.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [xmpp] Use of namespace in RFC 3920
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2009 22:55:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/23/09 10:01 AM, Jehan Pagès wrote:
> Hi,
> 
> yesterday I was discussing with Peter about how namespace requirements
> were presented in RFC 3920bis, and we both agreed that it is wrong.

I think that some points need to be clarified, but I do not agree with
all of your conclusions.

> The RFC is clearly trying to make an excuse for badly programmed XML
> parsers, not able to expand prefixes into namespaces (or keep track of
> declared prefix in parent elements). So you MUST absolutely have a
> default namespace in the root <stream>, and this one MUST be the one
> for the stanza ("jabber:client" or "jabber:server", most typically) +

I see no reason to relax this restriction. Among other things, it would
break most XMPP implementations, which seems like a bad idea.

> you MUST have a prefix declared, for the stream related first level
> elements, 

As Dave pointed out, that falls out from having a default namespace.

> and this prefix MUST be "stream".

This is SHOULD in the spec. However, I think we can relax it to say only
that an implementation MAY accept only "stream:" as the prefix. You can
draw your own conclusions about whether you ought to set the prefix to
"stream:" in your implementation (e.g., to avoid interoperability problems).

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrD4iIACgkQNL8k5A2w/vzXugCfR+4sh2cCyWaRN6CP8oRZM1w+
pkkAn3imadOoJ+uL7FkLtAAzsf1lGwcS
=0w1N
-----END PGP SIGNATURE-----
