From stpeter@stpeter.im Mon Dec 2 12:53:39 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 923881ADF61 for ; Mon, 2 Dec 2013 12:53:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZwSLy4j-sBN for ; Mon, 2 Dec 2013 12:53:37 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C5BA01ADF55 for ; Mon, 2 Dec 2013 12:53:37 -0800 (PST) Received: from ergon.local (unknown [64.101.72.104]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id CF4C34032B; Mon, 2 Dec 2013 13:53:34 -0700 (MST) Message-ID: <529CF34D.3070705@stpeter.im> Date: Mon, 02 Dec 2013 13:53:33 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: XMPP References: <20131127200633.B0EA379E00A@rfc-editor.org> In-Reply-To: <20131127200633.B0EA379E00A@rfc-editor.org> X-Enigmail-Version: 1.6 X-Forwarded-Message-Id: <20131127200633.B0EA379E00A@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [xmpp] Fwd: RFC 7081 on CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 20:53:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI. - -------- Original Message -------- Subject: RFC 7081 on CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) Date: Wed, 27 Nov 2013 12:06:33 -0800 (PST) From: rfc-editor@rfc-editor.org Reply-To: ietf@ietf.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 7081 Title: CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) Author: E. Ivov, P. Saint-Andre, E. Marocco Status: Informational Stream: IETF Date: November 2013 Mailbox: emcho@jitsi.org, psaintan@cisco.com, enrico.marocco@telecomitalia.it Pages: 19 Characters: 46772 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ivov-xmpp-cusax-09.txt URL: http://www.rfc-editor.org/rfc/rfc7081.txt This document suggests some strategies for the combined use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) both in user-oriented clients and in deployed servers. Such strategies, which mainly consist of configuration changes and minimal software modifications to existing clients and servers, aim to provide a single, full-featured, real-time communication service by using complementary subsets of features from SIP and from XMPP. Typically, such subsets consist of telephony capabilities from SIP and instant messaging and presence capabilities from XMPP. This document does not define any new protocols or syntax for either SIP or XMPP and, by intent, does not attempt to standardize "best current practices". Instead, it merely aims to provide practical guidance to those who are interested in the combined use of SIP and XMPP for real-time communication. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSnPNNAAoJEOoGpJErxa2pahsP/0x4LFXqiGG/RNSTUzDguh/6 faMii3+LK0yB7MdgTuh6N+zVqajkkFQnvpT0Z76Zopru3H+O/U6MPK00NbC5PGI4 j+dhdtZsje4/jwTDoj5IPQAczo6J2PakSsJDrlGRylGNPgGhEPRLPGqTxzNL8GZC XQXL6UC4dPEDWM+jy1ypz4NpvwBQQbxvLD+AgV9xP5/Pqe+jmdcIJiYLDpQ7ssBj 9dNYUYg5KSLhfDpsZ0RIfMF+gMk/QPS9SjjBxt+jqjk/orzIntLSA1xPH3eji37X ABCc3zt2clDLJDRaX14PRM9zWfFiF/QYY9CcKvN5o2KBdNzdoUAZMRNrnYIrjm0A VkJC8De7zJiFgGdGvmteJER8MlWtANKhyqm8N8rLESl3RO0nKSK8xTdaNDAHfKcu r/3L2HbxoUK4EkGhLS62vWGAZ8rIY62R4ZBrC6o0ylAfIem7QPVkoimyNcvf6oxp A1lGJuBuq60lE8fUIBITIABCWGIijlMkoZHgo+DDuYuiD1eXrLfVsJdzzyuOZLLK Nyec4h/8BfbOJyEwRVkCwKmlumNIo5BRAgNnRW5D0+eHmzHWCSMgZrvBOopLShBr slyQDbpTLBWDOKQW7LpHW67BGbR8yTscmbVsKSbe36J3DVLB6OvszV/THt578YMx XaUY12e2/hU7Q1WAXEG0 =F8cK -----END PGP SIGNATURE----- From stpeter@stpeter.im Mon Dec 2 14:42:05 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758351AD845 for ; Mon, 2 Dec 2013 14:42:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zfjbafRY3hkl for ; Mon, 2 Dec 2013 14:42:03 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B00551ADDAF for ; Mon, 2 Dec 2013 14:42:03 -0800 (PST) Received: from ergon.local (unknown [64.101.72.104]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C3F3F4032A; Mon, 2 Dec 2013 15:42:00 -0700 (MST) Message-ID: <529D0CB7.2090203@stpeter.im> Date: Mon, 02 Dec 2013 15:41:59 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: XMPP X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [xmpp] WebSocket open/close X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 22:42:05 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as I can see, we didn't have agreement in the room at IETF 88 about the framing for stream open and close. Based on informal, offlist discussion since then, it seems that most current implementations send the RFC 6120 and tags, and don't use something like specialized and elements. Unless folks on this list have concerns about the first approach, personally I'd be comfortable going with the running code. What do others think? Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSnQy3AAoJEOoGpJErxa2pl8AP/1ojqiMTD1i1/OEbMVZuGzEi NbQjhqAujLKjPRxEBko5iQ2n2hpfbSIqrX1ZUm31kdQnc5GggQJFQuvvw4B1Afj5 yrfEmHgeCfIRkvsPV39B/tihXCW5ozqQNy0bE/HpOqBSeSyPHOljQydYRu7o21Ad st5hf/3BYpZb6VHUsBgtWV1gooKLpeWKDMOjHclnVaYHd6jOWPqKzHa4R2EmnRSB JLqUjjjkm9Zxp5e2XRJQKxk/LPgr34cj8VXZf7yiKPd1eXSwdwEhwy3ESVG51cjL 5L1j2wxCy8ZcrB9CUmiNXAWzwQQrDkUWCQsf4+VqwCedZV3xBvzncKtMxrXuBvz8 pzYbBXHnH6ZKBvhkTrlFsMidlk2DDwsVTjQpZkjwWuo4euc9W77s9QhoNWEH6fwB QV0FJ6V+I5x+H7OscjJwdoe5+zAmhSkZUtCzqfddMUu+o33AGaJtjvUaZeojFzB4 x1nBVZCpXrs0vlXParekBzOZICQ810c6nlLTXRjbHNjQl23YASdj/f4vnHCKsKPN D5ilMlR4Zc5aqY9B3pvFrXuNDnBRnol/hpn5uHkp++Bp4uwRDikBT6EAFjBDN1xO C7MBlvdtGEFGqv7ykWrGjQ1OYwqtk1jrjEXYxfEov7h1e0F1YL6pfLHAd6uA5NhP Sjuwgtedh8Pk5LQbn1aJ =ncWw -----END PGP SIGNATURE----- From metajack@gmail.com Mon Dec 2 14:52:30 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3EC1ADF46 for ; Mon, 2 Dec 2013 14:52:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.278 X-Spam-Level: X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBhdwXsmXEoe for ; Mon, 2 Dec 2013 14:52:29 -0800 (PST) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 64BEE1ADDCA for ; Mon, 2 Dec 2013 14:52:29 -0800 (PST) Received: by mail-ob0-f179.google.com with SMTP id wm4so13403084obc.24 for ; Mon, 02 Dec 2013 14:52:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DBHwwgkKzyQV0CxTcRZK0taiI+VbZykdmrM79U3K34k=; b=NWcIpM+EjCcWtN4Mh3pHHop8TwuR0WKDu04OdgSr0lsEgQX3dSw6maWqlec1/3rl9i Tpzs2WNmyicprRuKOrTj0hEdKY48lDmAu2k70LH9B7USA9waisZ9DhI0/8fxL1Pcpg6o hv0QE67HwqFvvrGDurwEevEBamDik2pGEl3jjepwzs/6QWn7aaYeW3PAHnC1NPwTvw/g hcEIoNLQDVRnD9F3ft4Zq9FOw89T3pd32UC14m1UF+d53dmB8HMNvKuXnxpBuDwu+AQY K5Jr4fcipxjMwdBFOuSin9gXpcP9WLygafE7I3+3DHvVB5Q9o1sZlvCNkr5HsXZBQG7O xFQQ== MIME-Version: 1.0 X-Received: by 10.60.99.71 with SMTP id eo7mr2727148oeb.61.1386024746816; Mon, 02 Dec 2013 14:52:26 -0800 (PST) Sender: metajack@gmail.com Received: by 10.60.17.70 with HTTP; Mon, 2 Dec 2013 14:52:26 -0800 (PST) In-Reply-To: <529D0CB7.2090203@stpeter.im> References: <529D0CB7.2090203@stpeter.im> Date: Mon, 2 Dec 2013 15:52:26 -0700 X-Google-Sender-Auth: fgagPg0ZeTpRDr9SCFf_OlHIvTk Message-ID: From: Jack Moffitt To: Peter Saint-Andre Content-Type: text/plain; charset=ISO-8859-1 Cc: XMPP Subject: Re: [xmpp] WebSocket open/close X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 22:52:30 -0000 and can be treated as tokens and don't require a streaming parser. The attributes are easily picked out in a regex. That's probably why we originally defined them that way even though it's unparseable as XML by JavaScript using the native parsers. jack. On Mon, Dec 2, 2013 at 3:41 PM, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > As far as I can see, we didn't have agreement in the room at IETF 88 > about the framing for stream open and close. Based on informal, > offlist discussion since then, it seems that most current > implementations send the RFC 6120 and > tags, and don't use something like specialized and > elements. Unless folks on this list have concerns about the first > approach, personally I'd be comfortable going with the running code. > What do others think? > > Peter > > - -- > Peter Saint-Andre > https://stpeter.im/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.19 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJSnQy3AAoJEOoGpJErxa2pl8AP/1ojqiMTD1i1/OEbMVZuGzEi > NbQjhqAujLKjPRxEBko5iQ2n2hpfbSIqrX1ZUm31kdQnc5GggQJFQuvvw4B1Afj5 > yrfEmHgeCfIRkvsPV39B/tihXCW5ozqQNy0bE/HpOqBSeSyPHOljQydYRu7o21Ad > st5hf/3BYpZb6VHUsBgtWV1gooKLpeWKDMOjHclnVaYHd6jOWPqKzHa4R2EmnRSB > JLqUjjjkm9Zxp5e2XRJQKxk/LPgr34cj8VXZf7yiKPd1eXSwdwEhwy3ESVG51cjL > 5L1j2wxCy8ZcrB9CUmiNXAWzwQQrDkUWCQsf4+VqwCedZV3xBvzncKtMxrXuBvz8 > pzYbBXHnH6ZKBvhkTrlFsMidlk2DDwsVTjQpZkjwWuo4euc9W77s9QhoNWEH6fwB > QV0FJ6V+I5x+H7OscjJwdoe5+zAmhSkZUtCzqfddMUu+o33AGaJtjvUaZeojFzB4 > x1nBVZCpXrs0vlXParekBzOZICQ810c6nlLTXRjbHNjQl23YASdj/f4vnHCKsKPN > D5ilMlR4Zc5aqY9B3pvFrXuNDnBRnol/hpn5uHkp++Bp4uwRDikBT6EAFjBDN1xO > C7MBlvdtGEFGqv7ykWrGjQ1OYwqtk1jrjEXYxfEov7h1e0F1YL6pfLHAd6uA5NhP > Sjuwgtedh8Pk5LQbn1aJ > =ncWw > -----END PGP SIGNATURE----- > _______________________________________________ > xmpp mailing list > xmpp@ietf.org > https://www.ietf.org/mailman/listinfo/xmpp From stpeter@stpeter.im Mon Dec 2 15:02:34 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC8A1ADF4E for ; Mon, 2 Dec 2013 15:02:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qp3sYljVGx50 for ; Mon, 2 Dec 2013 15:02:33 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EDC671ADBCD for ; Mon, 2 Dec 2013 15:02:32 -0800 (PST) Received: from ergon.local (unknown [64.101.72.104]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3AE254032A; Mon, 2 Dec 2013 16:02:30 -0700 (MST) Message-ID: <529D1184.9080301@stpeter.im> Date: Mon, 02 Dec 2013 16:02:28 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Jack Moffitt References: <529D0CB7.2090203@stpeter.im> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: XMPP Subject: Re: [xmpp] WebSocket open/close X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 23:02:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Right. We'll probably want to mandate the 'stream' prefix for ease of regex matching, but we come close to doing that in RFC 6120 anyway. On 12/2/13 3:52 PM, Jack Moffitt wrote: > and can be treated as tokens and > don't require a streaming parser. The attributes are easily picked > out in a regex. That's probably why we originally defined them that > way even though it's unparseable as XML by JavaScript using the > native parsers. > > jack. > > On Mon, Dec 2, 2013 at 3:41 PM, Peter Saint-Andre > wrote: As far as I can see, we didn't have > agreement in the room at IETF 88 about the framing for stream open > and close. Based on informal, offlist discussion since then, it > seems that most current implementations send the RFC 6120 > and tags, and don't use something > like specialized and elements. Unless folks on this > list have concerns about the first approach, personally I'd be > comfortable going with the running code. What do others think? > > Peter > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSnRGEAAoJEOoGpJErxa2pOGgP/iJRzo/dWwooV5YjAZl1iHjJ FPDtdmlxi6VZ+22AuSpwqZlCJ5WQF77JkkMsATrCmX5xhD8oxZIJcjZS6MiR8Ivq cc4GqnYcmh/Zlyg3c/gODbgue7zC4wPq2UjMYrIw7bKctqLrZ/3noX8nc+H58Lhj TEMsGFd3NASqkEQuTLawdKJjDtTPgbz4LqNML6oMBGb7cLmNYE+dELWtryP0AsNi lgK91Q+APlEFeFfIReIK6tgHpXMLlJQNQPv8Fwu92bz+dP/fLdb78rxs1i3SYiY3 z8FSYhqOdD256EQC7PJry1dqRGEQJZUMIOLDynPhJKlkalJQ8hGLGI3BsYyWqkGD 8mLrVHkH5McglvfA9WG3B5R6N37TxPE8lsQOkjf813HkQvGxyEtGpBtBJcj42+o6 TTVe6uMiVO2uVC8acaOeNBZOKcRTN1DRXDi1KiuCkvrN+p9KsufgtuX1zueW90/Y UARugm/a/TzQxXnE3lcPDvwgq+OFA+J+04tocgyaZVsx2VAtV7aszNu+J6usCUit A4eJCm3h0PioArZzWse1sY2RgI2yJkYjJtUe7tRT8UQJE0nWdZrSxGdoXYEWn8/A iIUk3Ft01xspqqFCSzY5EsLH8zYfO2mWbALMyHY7mUKS4y74tdiLeJVQsrB7c3m1 kXu9qYwujyuDUrfzcMUU =5HC2 -----END PGP SIGNATURE----- From stpeter@stpeter.im Tue Dec 17 12:25:12 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9E71AD8F7 for ; Tue, 17 Dec 2013 12:25:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.44 X-Spam-Level: X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WmlLDubKBB3w for ; Tue, 17 Dec 2013 12:25:10 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C6F1C1ACCF0 for ; Tue, 17 Dec 2013 12:25:10 -0800 (PST) Received: from sjc-vpn6-418.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D7C134010C; Tue, 17 Dec 2013 13:25:08 -0700 (MST) Message-ID: <52B0B323.5050805@stpeter.im> Date: Tue, 17 Dec 2013 13:25:07 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: XMPP References: <20131217202338.32484.54532.idtracker@ietfa.amsl.com> In-Reply-To: <20131217202338.32484.54532.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.6 X-Forwarded-Message-Id: <20131217202338.32484.54532.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [xmpp] Fwd: I-D Action: draft-saintandre-xmpp-tls-03.txt X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 20:25:12 -0000 FYI. -------- Original Message -------- Subject: I-D Action: draft-saintandre-xmpp-tls-03.txt Date: Tue, 17 Dec 2013 12:23:38 -0800 From: internet-drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP) Author(s) : Peter Saint-Andre Filename : draft-saintandre-xmpp-tls-03.txt Pages : 10 Date : 2013-12-17 Abstract: This document provides recommendations for the use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP). This document updates RFC 6120. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-saintandre-xmpp-tls There's also a htmlized version available at: http://tools.ietf.org/html/draft-saintandre-xmpp-tls-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-saintandre-xmpp-tls-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt From dave@cridland.net Wed Dec 18 10:09:05 2013 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B71C1AE037 for ; Wed, 18 Dec 2013 10:09:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.378 X-Spam-Level: X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDMG0vLwkPh4 for ; Wed, 18 Dec 2013 10:09:03 -0800 (PST) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 43DAB1AE006 for ; Wed, 18 Dec 2013 10:09:03 -0800 (PST) Received: by mail-oa0-f49.google.com with SMTP id i4so8601904oah.36 for ; Wed, 18 Dec 2013 10:09:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jayJLS9Y3MzD46EvbaOxayO1KYUzI8Ko65ovl4ZeqEs=; b=HBNgf7v/eNtoKnJnqRnkqppZV6V5z9NAolzS0FIE+t808xF4wkjbkHQL8J9iJxN7Qx qRVTAO9W0COL0ttSEu43b9mmPmc3R76+DfbungqiWn0UQGRGiwd6hJZcRe0wZBaWIG3U rUAq7b3dNqAbIMDVlnZVTtKVXfwV1msYbgWoA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jayJLS9Y3MzD46EvbaOxayO1KYUzI8Ko65ovl4ZeqEs=; b=HpjD7GdIA6gHy5N8IeMs3+W8YEpJvKv8+IiEibO0nhj0ARw1PSbnaIWdQtPsWS8OKX 074JZjYXycglkyBNJ+lVl2HFamvPhxW7AKcXH/zaN5ypEe7cLDzDejJW20JhKvrz+d4w PR4xu1WTu7ghcwj908RErAxJZMHEY/oH1GBtVgOaBTmUk572Clu60hitT5z8A5GAJQzF sr1v27eHz1W7ox0fr6LlYrq7ju+3Q13aWH5w9Myw2ER4GPvWQ5Tn0gYnlm3zcd7UMmMG y9ANy+UNbEeiW9tJqV+i2vJ4BWHulVd2jOFcNrSLmttvyiGiSu6vweHhSUBeDzAl+MJ2 lB/g== X-Gm-Message-State: ALoCoQl/ibL0JVPKNen5pJGmGc+v1lLtMZALiyQ6yZ2PxlJJg8uB3DXt4583Cz4vVCS19wqnKMLM MIME-Version: 1.0 X-Received: by 10.60.51.161 with SMTP id l1mr2837123oeo.69.1387390141701; Wed, 18 Dec 2013 10:09:01 -0800 (PST) Received: by 10.60.144.38 with HTTP; Wed, 18 Dec 2013 10:09:01 -0800 (PST) In-Reply-To: <52B0B323.5050805@stpeter.im> References: <20131217202338.32484.54532.idtracker@ietfa.amsl.com> <52B0B323.5050805@stpeter.im> Date: Wed, 18 Dec 2013 18:09:01 +0000 Message-ID: From: Dave Cridland To: Peter Saint-Andre Content-Type: multipart/alternative; boundary=001a11c2f3ec8fb7b804edd2f0ef Cc: XMPP Subject: Re: [xmpp] Fwd: I-D Action: draft-saintandre-xmpp-tls-03.txt X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 18:09:05 -0000 --001a11c2f3ec8fb7b804edd2f0ef Content-Type: text/plain; charset=ISO-8859-1 Some scattergun comments. 1) I think you're saying SHOULD support, MAY negotiate TLS 1.1. Are you? Are we also saying SHOULD support later TLS versions, and SHOULD negotiate them? 2) There was some interesting discussions on the use of long-lived DH parameters and the resultant levels of perfection in the forward secrecy over on (erm) one of the XSF lists. It'd be nice to get some recommendations of longevity of the DH parameters - many implementations either hard-code these or generate them once only. On Tue, Dec 17, 2013 at 8:25 PM, Peter Saint-Andre wrote: > FYI. > > > -------- Original Message -------- > Subject: I-D Action: draft-saintandre-xmpp-tls-03.txt > Date: Tue, 17 Dec 2013 12:23:38 -0800 > From: internet-drafts@ietf.org > Reply-To: internet-drafts@ietf.org > To: i-d-announce@ietf.org > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Use of Transport Layer Security (TLS) in the > Extensible Messaging and Presence Protocol (XMPP) > Author(s) : Peter Saint-Andre > Filename : draft-saintandre-xmpp-tls-03.txt > Pages : 10 > Date : 2013-12-17 > > Abstract: > This document provides recommendations for the use of Transport Layer > Security (TLS) in the Extensible Messaging and Presence Protocol > (XMPP). This document updates RFC 6120. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-saintandre-xmpp-tls > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-saintandre-xmpp-tls-03 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-saintandre-xmpp-tls-03 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > _______________________________________________ > xmpp mailing list > xmpp@ietf.org > https://www.ietf.org/mailman/listinfo/xmpp > --001a11c2f3ec8fb7b804edd2f0ef Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Some scattergun comments.

1) I think yo= u're saying SHOULD support, MAY negotiate TLS 1.1. Are you? Are we also= saying SHOULD support later TLS versions, and SHOULD negotiate them?

2) There was some interesting discussions on the use of= long-lived DH parameters and the resultant levels of perfection in the for= ward secrecy over on (erm) one of the XSF lists. It'd be nice to get so= me recommendations of longevity of the DH parameters - many implementations= either hard-code these or generate them once only.


On Tue,= Dec 17, 2013 at 8:25 PM, Peter Saint-Andre <stpeter@stpeter.im>= wrote:
FYI.


-------- Original Message --------
Subject: I-D Action: draft-saintandre-xmpp-tls-03.txt
Date: Tue, 17 Dec 2013 12:23:38 -0800
From: internet-drafts@ietf.org<= /a>
Reply-To: internet-drafts@ietf.= org
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Use of Transport Layer Security= (TLS) in the
Extensible Messaging and Presence Protocol (XMPP)
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Peter Saint-Andre
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-saintandre-xmpp-tls-03.txt<= br> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 10
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-12-17

Abstract:
=A0 =A0This document provides recommendations for the use of Transport Laye= r
=A0 =A0Security (TLS) in the Extensible Messaging and Presence Protocol
=A0 =A0(XMPP). =A0This document updates RFC 6120.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-saintandre-xmpp= -tls-03


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

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d= -announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt


_______________________________________________
xmpp mailing list
xmpp@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/xmpp

--001a11c2f3ec8fb7b804edd2f0ef--