From internet-drafts@ietf.org Sun Jan 13 02:17:22 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E5521F866E; Sun, 13 Jan 2013 02:17:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.538 X-Spam-Level: X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LRvRKIyMDU2z; Sun, 13 Jan 2013 02:17:22 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1751921F8650; Sun, 13 Jan 2013 02:17:22 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.37 Message-ID: <20130113101722.8310.46260.idtracker@ietfa.amsl.com> Date: Sun, 13 Jan 2013 02:17:22 -0800 Cc: simple@ietf.org Subject: [Simple] I-D Action: draft-ietf-simple-chat-18.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 10:17:22 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP for Instant Messaging and Presence Le= veraging Extensions Working Group of the IETF. Title : Multi-party Chat Using the Message Session Relay Protoco= l (MSRP) Author(s) : Aki Niemi Miguel A. Garcia-Martin Geir A. Sandbakken Filename : draft-ietf-simple-chat-18.txt Pages : 42 Date : 2013-01-13 Abstract: The Message Session Relay Protocol (MSRP) defines a mechanism for sending instant messages within a peer-to-peer session, negotiated using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). This document defines the necessary tools for establishing multi-party chat sessions, or chat rooms, using MSRP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-simple-chat There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-simple-chat-18 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-chat-18 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From miguel.a.garcia@ericsson.com Sun Jan 13 02:21:15 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D682F21F8658 for ; Sun, 13 Jan 2013 02:21:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2iNap9mAnW3 for ; Sun, 13 Jan 2013 02:21:15 -0800 (PST) Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id AB48721F848B for ; Sun, 13 Jan 2013 02:21:14 -0800 (PST) X-AuditID: c1b4fb2d-b7f316d0000028db-be-50f28a9952a5 Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id DE.E3.10459.99A82F05; Sun, 13 Jan 2013 11:21:13 +0100 (CET) Received: from [159.107.48.76] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Sun, 13 Jan 2013 11:21:13 +0100 Message-ID: <50F28A98.50803@ericsson.com> Date: Sun, 13 Jan 2013 11:21:12 +0100 From: "Miguel A. Garcia" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Simple WG References: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> In-Reply-To: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNJMWRmVeSWpSXmKPExsUyM+Jvje7Mrk8BBp9+mFosnPiP1YHRY8mS n0wBjFFcNimpOZllqUX6dglcGZc3t7IVHOKu+LrqGEsD41bOLkZODgkBE4krTyewQ9hiEhfu rWfrYuTiEBI4ySjRNgEkAeKsZpQ4ef4gWBWvgKbEtRvrWEBsFgFVidkvpoLZbALmEq0bN4LV iApESby/2sQMUS8ocXLmE7AaEQF5iRezfzGB2MICHhKtDw6xgthCAg5Ay/aAxTkFHCVWnr7F AnGRj8TqppdsIDazgIXE4jcQNzADzdn+dg4zRK+mxOSbS5knMArOQrJuFpKWWUhaFjAyr2Jk z03MzEkvN9zECAzAg1t+6+5gPHVO5BCjNAeLkjhvmOuFACGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2M4XNPLHvOGW8V2P1vt0BAbW6MFlNjzJacqJajr87yvi3Wnnxu1oZz8d3zIn10Dorr +327WlJy93mFYLpJpeHd9WciJ/Ic36Wzx/TAvon9VtWXo+UE707/pGjmkfpjxc0Hoc2JhkvS PuU67urfo6Lz+Nddfp6HXD8WTQ6ZWPey5rvEon3L3X/pKbEUZyQaajEXFScCAFCCWzwOAgAA Subject: [Simple] Fwd: New Version Notification for draft-ietf-simple-chat-18.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 10:21:16 -0000 Version -18 of the SIMPLE chat document addresses the discusses by Martin Stiemerling (congestion control) and Stephen Farrel (security). /Miguel -------- Original Message -------- Subject: New Version Notification for draft-ietf-simple-chat-18.txt Date: Sun, 13 Jan 2013 02:17:22 -0800 From: To: CC: , A new version of I-D, draft-ietf-simple-chat-18.txt has been successfully submitted by Miguel A. Garcia-Martin and posted to the IETF repository. Filename: draft-ietf-simple-chat Revision: 18 Title: Multi-party Chat Using the Message Session Relay Protocol (MSRP) Creation date: 2013-01-11 WG ID: simple Number of pages: 42 URL: http://www.ietf.org/internet-drafts/draft-ietf-simple-chat-18.txt Status: http://datatracker.ietf.org/doc/draft-ietf-simple-chat Htmlized: http://tools.ietf.org/html/draft-ietf-simple-chat-18 Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-simple-chat-18 Abstract: The Message Session Relay Protocol (MSRP) defines a mechanism for sending instant messages within a peer-to-peer session, negotiated using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). This document defines the necessary tools for establishing multi-party chat sessions, or chat rooms, using MSRP. The IETF Secretariat From wwwrun@rfc-editor.org Wed Jan 16 06:24:54 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20DC221F895B for ; Wed, 16 Jan 2013 06:24:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.34 X-Spam-Level: X-Spam-Status: No, score=-102.34 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xf4JChQAoPWQ for ; Wed, 16 Jan 2013 06:24:42 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1872B21F8959 for ; Wed, 16 Jan 2013 06:24:40 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id DD73AB1E002; Wed, 16 Jan 2013 06:13:51 -0800 (PST) To: jari.urpalainen@nokia.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, hisham.khartabil@gmail.com, ben@nostrum.com From: RFC Errata System Message-Id: <20130116141351.DD73AB1E002@rfc-editor.org> Date: Wed, 16 Jan 2013 06:13:51 -0800 (PST) Cc: dret@berkeley.edu, simple@ietf.org, rfc-editor@rfc-editor.org Subject: [Simple] [Technical Errata Reported] RFC5261 (3458) X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 14:24:54 -0000 The following errata report has been submitted for RFC5261, "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5261&eid=3458 -------------------------------------- Type: Technical Reported by: Erik Wilde Section: 8 Original Text ------------- Corrected Text -------------- Notes ----- The regex in the XSD suggests that "id()" would be a valid selector for a patch, but it would not make sense to specify such a selector since it never would select a node (there's no identifier to locate in the document). This means that while "id()" is a valid XPath expression, it should not be allowed as a selector expression within an XML patch document. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5261 (draft-ietf-simple-xml-patch-ops-04) -------------------------------------- Title : An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors Publication Date : September 2008 Author(s) : J. Urpalainen Category : PROPOSED STANDARD Source : SIP for Instant Messaging and Presence Leveraging Extensions Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From prasun.bheri@gmail.com Thu Jan 17 00:16:33 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D585B21F88D6 for ; Thu, 17 Jan 2013 00:16:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akwJ8hOLQt0j for ; Thu, 17 Jan 2013 00:16:33 -0800 (PST) Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by ietfa.amsl.com (Postfix) with ESMTP id 5011D21F88E3 for ; Thu, 17 Jan 2013 00:16:33 -0800 (PST) Received: by mail-ob0-f179.google.com with SMTP id x4so2255481obh.24 for ; Thu, 17 Jan 2013 00:16:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=KBLfW3gEQCLMO/8n54kkEVaNcoOJWNnb1C2Fca9PQaU=; b=Hhc5/7OqgMKQvjxDGgSd7vYwAgUyzbPgyBeMOC8HFgVBaWHuHEYzZPSAm3KuiBXKTp W3uzvn98KIipw4CHdNTEvBu+PWSP1e/xjcUgDc/qcxTk3kx0u7GYFDX4at9OWMdg/x0t NbRjN65c2laksyoBcgv2pAnpLDwmBSiSV1SBAznFTkPG24G8i3IQuix2U+UnaCOzTU5e ql5j8cBD2IABXLIaLl43MF0zerVcn4fe2kwzZeK69P7ldT2DePQy1GGHpj55Mp0w821s co1k7zRELhfcFad1tyoSBHZPB1AgTYn+BZvTDoSsb68axL3ihqgDbz0GBBTUW6VsJFNs 57kA== X-Received: by 10.182.188.69 with SMTP id fy5mr3204873obc.74.1358410592774; Thu, 17 Jan 2013 00:16:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.172.41 with HTTP; Thu, 17 Jan 2013 00:15:52 -0800 (PST) From: Prasun Bheri Date: Thu, 17 Jan 2013 13:45:52 +0530 Message-ID: To: Simple@ietf.org Content-Type: multipart/alternative; boundary=f46d0447f2a8d76be404d3779c3e Subject: [Simple] In context of MSRP; How to tell if incoming connection request is of type TLS or TCP? X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 08:16:34 -0000 --f46d0447f2a8d76be404d3779c3e Content-Type: text/plain; charset=ISO-8859-1 Hello Group, In regards to TLS over MSRP. Scenario: There are two sessions between UE-A and UE-B, in which B chose to be active endpoint in both the sessions (a=setup:active), of which one session is over TLS and another is over TCP. Two incoming connection requests will arrive at A. What is the best approach for A to distinguish TLS request from TCP? In case of SIP its easy as there are separate ports for TCP and TLS. so the connection request will be identified based on the port upon which the request arrived. But for MSRP rfc 4975 doesn't recommend a different port, so both requests could arrive at same 2855 port. Thanks & Regards, Prasun Bheri --f46d0447f2a8d76be404d3779c3e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Group,

In regards to TLS ov= er MSRP.=A0

Scenario:=A0
There are two sessions between =A0UE-A and UE-B, in which B chose to be = active endpoint in both the sessions (a=3Dsetup:active), of which one sessi= on is over TLS and another is over TCP.

Two incoming connection requests will arriv= e at A.=A0
What is the best approach for A to=A0distinguish= TLS request from TCP?

In case of SIP = its easy as there are separate ports for TCP and TLS. so the connection req= uest will be identified based on the port upon which the request arrived. B= ut for MSRP rfc 4975 doesn't recommend a different port, so both reques= ts could arrive at same 2855 port.=A0

Thanks & Regards,
Prasu= n Bheri





--f46d0447f2a8d76be404d3779c3e-- From rjsparks@nostrum.com Thu Jan 17 07:42:18 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C390C21F8BBB for ; Thu, 17 Jan 2013 07:42:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V1mV7YFRaRjB for ; Thu, 17 Jan 2013 07:42:17 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 281EE21F8959 for ; Thu, 17 Jan 2013 07:42:17 -0800 (PST) Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0HFg8Nn067305 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 Jan 2013 09:42:09 -0600 (CST) (envelope-from rjsparks@nostrum.com) Message-ID: <50F81BD2.3080500@nostrum.com> Date: Thu, 17 Jan 2013 09:42:10 -0600 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Miguel A. Garcia" References: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> <50F28A98.50803@ericsson.com> In-Reply-To: <50F28A98.50803@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism) Cc: Simple WG Subject: [Simple] ATTN SIMPLE WG: Re: Fwd: New Version Notification for draft-ietf-simple-chat-18.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 15:42:18 -0000 With this version, the last DISCUSSes have been cleared. This version did add a normative reference to RFC5681 and some discussion of TCP congestion. Please review that and the other changes from -17. I will wait until midweek next week to approve the draft. RjS On 1/13/13 4:21 AM, Miguel A. Garcia wrote: > Version -18 of the SIMPLE chat document addresses the discusses by > Martin Stiemerling (congestion control) and Stephen Farrel (security). > > /Miguel > > > -------- Original Message -------- > Subject: New Version Notification for draft-ietf-simple-chat-18.txt > Date: Sun, 13 Jan 2013 02:17:22 -0800 > From: > To: > CC: , > > > A new version of I-D, draft-ietf-simple-chat-18.txt > has been successfully submitted by Miguel A. Garcia-Martin and posted > to the > IETF repository. > > Filename: draft-ietf-simple-chat > Revision: 18 > Title: Multi-party Chat Using the Message Session Relay > Protocol (MSRP) > Creation date: 2013-01-11 > WG ID: simple > Number of pages: 42 > URL: http://www.ietf.org/internet-drafts/draft-ietf-simple-chat-18.txt > Status: http://datatracker.ietf.org/doc/draft-ietf-simple-chat > Htmlized: http://tools.ietf.org/html/draft-ietf-simple-chat-18 > Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-simple-chat-18 > > Abstract: > The Message Session Relay Protocol (MSRP) defines a mechanism for > sending instant messages within a peer-to-peer session, negotiated > using the Session Initiation Protocol (SIP) and the Session > Description Protocol (SDP). This document defines the necessary > tools for establishing multi-party chat sessions, or chat rooms, > using MSRP. > > > > > > The IETF Secretariat > > > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www.ietf.org/mailman/listinfo/simple From stpeter@stpeter.im Thu Jan 17 07:48:09 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F53121F8566 for ; Thu, 17 Jan 2013 07:48:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzaAXyEwlglp for ; Thu, 17 Jan 2013 07:48:08 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1FEA421F84F2 for ; Thu, 17 Jan 2013 07:48:08 -0800 (PST) Received: from [192.168.1.64] (unknown [12.207.194.2]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 090DF4005D; Thu, 17 Jan 2013 08:53:43 -0700 (MST) Message-ID: <50F81D3C.7000701@stpeter.im> Date: Thu, 17 Jan 2013 07:48:12 -0800 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Robert Sparks References: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> <50F28A98.50803@ericsson.com> <50F81BD2.3080500@nostrum.com> In-Reply-To: <50F81BD2.3080500@nostrum.com> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Simple WG Subject: Re: [Simple] ATTN SIMPLE WG: Re: Fwd: New Version Notification for draft-ietf-simple-chat-18.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 15:48:09 -0000 I took a look at this yesterday and it all seemed fine! On 1/17/13 7:42 AM, Robert Sparks wrote: > With this version, the last DISCUSSes have been cleared. > > This version did add a normative reference to RFC5681 and some > discussion of TCP congestion. > Please review that and the other changes from -17. > > I will wait until midweek next week to approve the draft. > > RjS > > On 1/13/13 4:21 AM, Miguel A. Garcia wrote: >> Version -18 of the SIMPLE chat document addresses the discusses by >> Martin Stiemerling (congestion control) and Stephen Farrel (security). >> >> /Miguel >> >> >> -------- Original Message -------- >> Subject: New Version Notification for draft-ietf-simple-chat-18.txt >> Date: Sun, 13 Jan 2013 02:17:22 -0800 >> From: >> To: >> CC: , >> >> >> A new version of I-D, draft-ietf-simple-chat-18.txt >> has been successfully submitted by Miguel A. Garcia-Martin and posted >> to the >> IETF repository. >> >> Filename: draft-ietf-simple-chat >> Revision: 18 >> Title: Multi-party Chat Using the Message Session Relay >> Protocol (MSRP) >> Creation date: 2013-01-11 >> WG ID: simple >> Number of pages: 42 >> URL: http://www.ietf.org/internet-drafts/draft-ietf-simple-chat-18.txt >> Status: http://datatracker.ietf.org/doc/draft-ietf-simple-chat >> Htmlized: http://tools.ietf.org/html/draft-ietf-simple-chat-18 >> Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-simple-chat-18 >> >> Abstract: >> The Message Session Relay Protocol (MSRP) defines a mechanism for >> sending instant messages within a peer-to-peer session, negotiated >> using the Session Initiation Protocol (SIP) and the Session >> Description Protocol (SDP). This document defines the necessary >> tools for establishing multi-party chat sessions, or chat rooms, >> using MSRP. >> >> >> >> >> >> The IETF Secretariat >> >> >> >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org >> https://www.ietf.org/mailman/listinfo/simple From ben@nostrum.com Thu Jan 17 07:58:17 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD10F21F84DE for ; Thu, 17 Jan 2013 07:58:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.562 X-Spam-Level: X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktIAtpkDl4UP for ; Thu, 17 Jan 2013 07:58:17 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B81E21F886F for ; Thu, 17 Jan 2013 07:58:16 -0800 (PST) Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0HFwDiG069089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Jan 2013 09:58:14 -0600 (CST) (envelope-from ben@nostrum.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Ben Campbell In-Reply-To: <50F81BD2.3080500@nostrum.com> Date: Thu, 17 Jan 2013 09:58:15 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130113101722.8310.14281.idtracker@ietfa.amsl.com> <50F28A98.50803@ericsson.com> <50F81BD2.3080500@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.1499) Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism) Cc: Simple WG Subject: Re: [Simple] ATTN SIMPLE WG: Re: Fwd: New Version Notification for draft-ietf-simple-chat-18.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 15:58:17 -0000 Please note there is also a new normative reference to RFC 3323, = due to some strengthened language about anonymity. This version looks good to me! On Jan 17, 2013, at 9:42 AM, Robert Sparks wrote: > With this version, the last DISCUSSes have been cleared. >=20 > This version did add a normative reference to RFC5681 and some = discussion of TCP congestion. > Please review that and the other changes from -17. >=20 > I will wait until midweek next week to approve the draft. >=20 > RjS >=20 > On 1/13/13 4:21 AM, Miguel A. Garcia wrote: >> Version -18 of the SIMPLE chat document addresses the discusses by = Martin Stiemerling (congestion control) and Stephen Farrel (security). >>=20 >> /Miguel >>=20 >>=20 >> -------- Original Message -------- >> Subject: New Version Notification for draft-ietf-simple-chat-18.txt >> Date: Sun, 13 Jan 2013 02:17:22 -0800 >> From: >> To: >> CC: , >>=20 >>=20 >> A new version of I-D, draft-ietf-simple-chat-18.txt >> has been successfully submitted by Miguel A. Garcia-Martin and posted = to the >> IETF repository. >>=20 >> Filename: draft-ietf-simple-chat >> Revision: 18 >> Title: Multi-party Chat Using the Message Session Relay = Protocol (MSRP) >> Creation date: 2013-01-11 >> WG ID: simple >> Number of pages: 42 >> URL: = http://www.ietf.org/internet-drafts/draft-ietf-simple-chat-18.txt >> Status: http://datatracker.ietf.org/doc/draft-ietf-simple-chat >> Htmlized: http://tools.ietf.org/html/draft-ietf-simple-chat-18 >> Diff: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-chat-18 >>=20 >> Abstract: >> The Message Session Relay Protocol (MSRP) defines a mechanism for >> sending instant messages within a peer-to-peer session, negotiated >> using the Session Initiation Protocol (SIP) and the Session >> Description Protocol (SDP). This document defines the necessary >> tools for establishing multi-party chat sessions, or chat rooms, >> using MSRP. >>=20 >>=20 >>=20 >>=20 >>=20 >> The IETF Secretariat >>=20 >>=20 >>=20 >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org >> https://www.ietf.org/mailman/listinfo/simple >=20 > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www.ietf.org/mailman/listinfo/simple From wwwrun@rfc-editor.org Fri Jan 18 01:38:19 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABD221F883F for ; Fri, 18 Jan 2013 01:38:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.352 X-Spam-Level: X-Spam-Status: No, score=-102.352 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2E4cDfocZqlj for ; Fri, 18 Jan 2013 01:38:18 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id C8B1521F84E7 for ; Fri, 18 Jan 2013 01:38:18 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 182ECB1E002; Fri, 18 Jan 2013 01:27:22 -0800 (PST) To: jari.urpalainen@nokia.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, hisham.khartabil@gmail.com, ben@nostrum.com From: RFC Errata System Message-Id: <20130118092722.182ECB1E002@rfc-editor.org> Date: Fri, 18 Jan 2013 01:27:22 -0800 (PST) Cc: dret@berkeley.edu, simple@ietf.org, rfc-editor@rfc-editor.org Subject: [Simple] [Technical Errata Reported] RFC5261 (3465) X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 09:38:19 -0000 The following errata report has been submitted for RFC5261, "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5261&eid=3465 -------------------------------------- Type: Technical Reported by: Erik Wilde Section: 4.2.3 Original Text ------------- Lastly, if the above two rules still don't apply, first all in-scope namespace prefixes of the evaluation context node are arranged alphabetically in an ascending order. Corrected Text -------------- n/a Notes ----- It is not entirely clear what "arranged alphabetically" refers to in this section. Sorting can be done in a variety of ways, and while many environment may have standard sort orders, not all are the same and for this standard to be implement consistently it's important to clearly state what sort order the above sentence is referring to. The suggested fix for this erratum is to add text that clearly states which sorting method should be used. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5261 (draft-ietf-simple-xml-patch-ops-04) -------------------------------------- Title : An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors Publication Date : September 2008 Author(s) : J. Urpalainen Category : PROPOSED STANDARD Source : SIP for Instant Messaging and Presence Leveraging Extensions Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From iesg-secretary@ietf.org Thu Jan 24 14:16:17 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7738111E8099; Thu, 24 Jan 2013 14:16:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.241 X-Spam-Level: X-Spam-Status: No, score=-102.241 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4mo9j3yI7vS; Thu, 24 Jan 2013 14:16:16 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E72211E80BF; Thu, 24 Jan 2013 14:16:16 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.37 Message-ID: <20130124221616.8046.25893.idtracker@ietfa.amsl.com> Date: Thu, 24 Jan 2013 14:16:16 -0800 Cc: simple chair , simple mailing list , RFC Editor Subject: [Simple] Protocol Action: 'Multi-party Chat Using the Message Session Relay Protocol (MSRP)' to Proposed Standard (draft-ietf-simple-chat-18.txt) X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 22:16:17 -0000 The IESG has approved the following document: - 'Multi-party Chat Using the Message Session Relay Protocol (MSRP)' (draft-ietf-simple-chat-18.txt) as Proposed Standard This document is the product of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group. The IESG contact persons are Robert Sparks and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-simple-chat/ Technical Summary The Message Session Relay Protocol (MSRP) defines a mechanism for sending instant messages within a peer-to-peer session, negotiated using the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). This document defines the necessary tools for establishing multi-party chat sessions, or chat rooms, using MSRP. Working Group Summary There has been controversy about doing this work in SIMPLE. The XCON working group was chartered to do create similar mechanisms in a media independent fashion. There was a compromise consensus to do this draft in SIMPLE with the idea that, with its smaller scope, it could complete more quickly than the XCON work, and that it would be a short-term solution until XCON completed the more general work. This in fact did not occur, as this draft took longer than expected due to several editor changes. Discussion at the SIMPLE meeting at IETF75 concluded that we should capture the parts of this draft were specific about mixing MSRP at a conference bridge, but abandon the rest in favor of XCON. However, this conclusion did not achieve consensus when brought it to the working group list at large. We readdressed this on the SIMPLE list in September 2010. A few participants strongly argued that the work should be abandoned, as it conflicted with (now substantially complete) work in XCON. But others (including at least one implementor) argued for completion. In particular, several people argued that this draft enabled them to build a light weight text-chat service without requiring all the features enabled by XCON. Note that the XCON working group has since completed its work and closed. In summary, the working group originally had a consensus to complete this work, and has not achieved a consensus to change that plan. We had agreement to pubreq version 07 in late 2010. The shepherd found some issues during the PROTO review. The work group discussed the substantive changes since version 07 on list, and we had a similar consensus to pubreq version 11 without a new WGLC The apps area review turned up some issues with the internationalization of nicknames. The related updates, as well as a new normative dependency on the PRECIS work, have been vetted on the SIMPLE list. Document Quality. The document has quite a bit of review over its lifespan in the SIMPLE work group. It lists Eva Leppanen, Adamu Haruna, Adam Roach, Matt Lepinski, Mary Barnes, Ben Campbell, Paul Kyzivat, Adrianv Georgescu, and Nancy Greene as reviewers in the acknowledgments. The document has undergone an MMUSIC expert review (Flemming Andreasen), since it contains an SDP extension. It has been through WGLC, multiple consensus calls, as well as an IETF last call. It has had 2 Gen-ART reviews (Christer Holmberg as Suresh Krishnan) , as well as IANA, apps-dir (Alexey Melnikov), tsv-dir (Cullen Jennings), and sec-dir (Vincent Roca) reviews. The shepherd believes that all issues raised in these reviews have been resolved. There are at least two existing implementations, "Blink" as a client and "SylkServer" as a server. A few others have indicated the intent to implement it. Additionally, the GSMA RCS 5.1 specification references this document in order to use the a=chatroom attribute. Personnel The document shepherd for this document is Ben Campbell. The responsible Area Director is Robert Sparks. From internet-drafts@ietf.org Mon Jan 28 16:44:54 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B04921F84E8; Mon, 28 Jan 2013 16:44:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.515 X-Spam-Level: X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h17qC0YtrnAQ; Mon, 28 Jan 2013 16:44:53 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0C9721F84DC; Mon, 28 Jan 2013 16:44:53 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.37 Message-ID: <20130129004453.17046.96903.idtracker@ietfa.amsl.com> Date: Mon, 28 Jan 2013 16:44:53 -0800 Cc: simple@ietf.org Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 00:44:54 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP for Instant Messaging and Presence Le= veraging Extensions Working Group of the IETF. Title : SIMPLE made Simple: An Overview of the IETF Specificatio= ns for Instant Messaging and Presence using the Session Initiation Protocol= (SIP) Author(s) : Jonathan Rosenberg Filename : draft-ietf-simple-simple-08.txt Pages : 15 Date : 2013-01-28 Abstract: The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions. This document serves as a guide to the SIMPLE suite of specifications. It breaks them up into categories and explains what each is for and how they relate to each other. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-simple-simple There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-simple-simple-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-simple-08 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From ben@nostrum.com Tue Jan 29 06:17:44 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7566321F8692 for ; Tue, 29 Jan 2013 06:17:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJxiIYvxdtnp for ; Tue, 29 Jan 2013 06:17:43 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BBA8821F8691 for ; Tue, 29 Jan 2013 06:17:42 -0800 (PST) Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0TEHfIN082177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 29 Jan 2013 08:17:42 -0600 (CST) (envelope-from ben@nostrum.com) From: Ben Campbell Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 29 Jan 2013 08:17:40 -0600 References: <20130129004453.17046.96903.idtracker@ietfa.amsl.com> To: Simple WG Message-Id: <4351AF92-3E60-4967-890B-33291473A10E@nostrum.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism) Subject: [Simple] Fwd: I-D Action: draft-ietf-simple-simple-08.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 14:17:44 -0000 (as chair) We had a WGLC on version 06 of draft-ietf-simple-simple some time (as in = years) ago. It's been on hold since then to allow the other SIMPLE work = to substantially complete. Since our penultimate milestone (simple-chat) = has recently been approved by the IESG, it's time to progress = simple-simple and complete our final chartered milestone. The only non-trivial change between 06 and 08 was the split of the entry = for the old msrp-acm draft into separate entries for RFC 6135 (COMEDIA = for MSRP) and RFC 6174 (CEMA), to account for the split of that draft. After conferring with the author and our AD, I think these changes are = pretty obvious and not likely to be controversial. Therefore we plan to = request publication of version 08. If anyone objects to that course of = action, please speak up asap. Thanks! Ben. > From: internet-drafts@ietf.org > Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt > Date: January 28, 2013 6:44:53 PM CST > To: i-d-announce@ietf.org > Cc: simple@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the SIP for Instant Messaging and = Presence Leveraging Extensions Working Group of the IETF. >=20 > Title : SIMPLE made Simple: An Overview of the IETF = Specifications for Instant Messaging and Presence using the Session = Initiation Protocol (SIP) > Author(s) : Jonathan Rosenberg > Filename : draft-ietf-simple-simple-08.txt > Pages : 15 > Date : 2013-01-28 >=20 > Abstract: > The IETF has produced many specifications related to Presence and > Instant Messaging with the Session Initiation Protocol (SIP). > Collectively, these specifications are known as SIMPLE - SIP for > Instant Messaging and Presence Leveraging Extensions. This document > serves as a guide to the SIMPLE suite of specifications. It breaks > them up into categories and explains what each is for and how they > relate to each other. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-simple-simple >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-simple-simple-08 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-simple-08 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www.ietf.org/mailman/listinfo/simple From oej@edvina.net Wed Jan 30 00:00:53 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD2B21F8B2F for ; Wed, 30 Jan 2013 00:00:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmp9QOw1Qgro for ; Wed, 30 Jan 2013 00:00:52 -0800 (PST) Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id 1186321F8B29 for ; Wed, 30 Jan 2013 00:00:49 -0800 (PST) Received: from [IPv6:2001:16d8:cc57:1000::42:1005] (unknown [IPv6:2001:16d8:cc57:1000::42:1005]) by smtp7.webway.se (Postfix) with ESMTPA id 4831F754A8AF; Wed, 30 Jan 2013 08:00:47 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Olle E Johanson In-Reply-To: <4351AF92-3E60-4967-890B-33291473A10E@nostrum.com> Date: Wed, 30 Jan 2013 08:49:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <27757F55-1837-4CC0-B65D-07B1CA6F661A@edvina.net> References: <20130129004453.17046.96903.idtracker@ietfa.amsl.com> <4351AF92-3E60-4967-890B-33291473A10E@nostrum.com> To: Ben Campbell X-Mailer: Apple Mail (2.1499) Cc: Simple WG Subject: Re: [Simple] Fwd: I-D Action: draft-ietf-simple-simple-08.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 08:00:53 -0000 29 jan 2013 kl. 15:17 skrev Ben Campbell : > (as chair) >=20 > We had a WGLC on version 06 of draft-ietf-simple-simple some time (as = in years) ago. It's been on hold since then to allow the other SIMPLE = work to substantially complete. Since our penultimate milestone = (simple-chat) has recently been approved by the IESG, it's time to = progress simple-simple and complete our final chartered milestone. >=20 > The only non-trivial change between 06 and 08 was the split of the = entry for the old msrp-acm draft into separate entries for RFC 6135 = (COMEDIA for MSRP) and RFC 6174 (CEMA), to account for the split of that = draft. >=20 > After conferring with the author and our AD, I think these changes are = pretty obvious and not likely to be controversial. Therefore we plan to = request publication of version 08. If anyone objects to that course of = action, please speak up asap. Ok, I know I had years to make a comment, but anyway :-) I would like to see references to the SIP domain certificate = specification, as it plays a role for implementors, as well as the SIP = certificate management service. These should be important for anyone = building SIMPLE implementations and adds some missing pieces in the = SIMPLE specs. - RFC 6072 Certificate Maangement Service for Session Initiation = Protocol http://tools.ietf.org/html/rfc6072 - RFC 5922 Domain Certificates in the Session Initiation Protocol http://tools.ietf.org/html/rfc5922 Maybe we could add a clarification for newbies that "The SIP = subscribe/notify mechanism is not only used in SIMPLE, but also in other = event packages outside of the scope of this document." I could possibly also add a section about the missing interoperability = in presence/XCAP implementations but that propably won't help this = particular document that I find has a lot of value. See you all at SIPit 30! Only a few days of registration open - so = please hurry to http://www.sipit.net and register! /O >=20 > Thanks! >=20 > Ben. >=20 >> From: internet-drafts@ietf.org >> Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt >> Date: January 28, 2013 6:44:53 PM CST >> To: i-d-announce@ietf.org >> Cc: simple@ietf.org >>=20 >>=20 >> A New Internet-Draft is available from the on-line Internet-Drafts = directories. >> This draft is a work item of the SIP for Instant Messaging and = Presence Leveraging Extensions Working Group of the IETF. >>=20 >> Title : SIMPLE made Simple: An Overview of the IETF = Specifications for Instant Messaging and Presence using the Session = Initiation Protocol (SIP) >> Author(s) : Jonathan Rosenberg >> Filename : draft-ietf-simple-simple-08.txt >> Pages : 15 >> Date : 2013-01-28 >>=20 >> Abstract: >> The IETF has produced many specifications related to Presence and >> Instant Messaging with the Session Initiation Protocol (SIP). >> Collectively, these specifications are known as SIMPLE - SIP for >> Instant Messaging and Presence Leveraging Extensions. This document >> serves as a guide to the SIMPLE suite of specifications. It breaks >> them up into categories and explains what each is for and how they >> relate to each other. >>=20 >>=20 >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-simple-simple >>=20 >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-simple-simple-08 >>=20 >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-simple-08 >>=20 >>=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >>=20 >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org >> https://www.ietf.org/mailman/listinfo/simple >=20 > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www.ietf.org/mailman/listinfo/simple From ben@nostrum.com Wed Jan 30 06:33:49 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13E821F8507 for ; Wed, 30 Jan 2013 06:33:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.3 X-Spam-Level: X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhIPuw4Snaxg for ; Wed, 30 Jan 2013 06:33:49 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1D08521F84BF for ; Wed, 30 Jan 2013 06:33:48 -0800 (PST) Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0UEXhJB044229 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jan 2013 08:33:43 -0600 (CST) (envelope-from ben@nostrum.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Ben Campbell In-Reply-To: <27757F55-1837-4CC0-B65D-07B1CA6F661A@edvina.net> Date: Wed, 30 Jan 2013 08:33:44 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0A03B93C-18AA-419B-84CB-E1BCDA066E39@nostrum.com> References: <20130129004453.17046.96903.idtracker@ietfa.amsl.com> <4351AF92-3E60-4967-890B-33291473A10E@nostrum.com> <27757F55-1837-4CC0-B65D-07B1CA6F661A@edvina.net> To: Olle E Johanson X-Mailer: Apple Mail (2.1499) Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism) Cc: Simple WG Subject: Re: [Simple] Fwd: I-D Action: draft-ietf-simple-simple-08.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 14:33:49 -0000 (As individual) On Jan 30, 2013, at 1:49 AM, Olle E Johanson wrote: >=20 > 29 jan 2013 kl. 15:17 skrev Ben Campbell : >=20 >> (as chair) >>=20 >> We had a WGLC on version 06 of draft-ietf-simple-simple some time (as = in years) ago. It's been on hold since then to allow the other SIMPLE = work to substantially complete. Since our penultimate milestone = (simple-chat) has recently been approved by the IESG, it's time to = progress simple-simple and complete our final chartered milestone. >>=20 >> The only non-trivial change between 06 and 08 was the split of the = entry for the old msrp-acm draft into separate entries for RFC 6135 = (COMEDIA for MSRP) and RFC 6174 (CEMA), to account for the split of that = draft. >>=20 >> After conferring with the author and our AD, I think these changes = are pretty obvious and not likely to be controversial. Therefore we plan = to request publication of version 08. If anyone objects to that course = of action, please speak up asap. >=20 > Ok, I know I had years to make a comment, but anyway :-) >=20 > I would like to see references to the SIP domain certificate = specification, as it plays a role for implementors, as well as the SIP = certificate management service. These should be important for anyone = building SIMPLE implementations and adds some missing pieces in the = SIMPLE specs. >=20 > - RFC 6072 Certificate Maangement Service for Session Initiation = Protocol > http://tools.ietf.org/html/rfc6072 > - RFC 5922 Domain Certificates in the Session Initiation Protocol > http://tools.ietf.org/html/rfc5922 >=20 > Maybe we could add a clarification for newbies that "The SIP = subscribe/notify mechanism is not only used in SIMPLE, but also in other = event packages outside of the scope of this document." >=20 My personal opinion is that general SIP mechanisms are out of scope for = this draft. Otherwise, we could pull in most of the body of work of SIP. = SIP-events is an exception, since it is core to all of the presence = work. At most,we might considert a paragraph mentioning that many SIP = related mechanisms can apply to SIMPLE just like any other SIP usage, = perhaps with a ref to the hitchhiker's guide. >=20 > I could possibly also add a section about the missing interoperability = in presence/XCAP implementations but that propably won't help this = particular document that I find has a lot of value. I agree that this wouldn't add value to this doc. Also, I think that's = important enough of a concern to warrant its own draft :-) From ben@nostrum.com Wed Jan 30 10:56:19 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF1AC21F886D for ; Wed, 30 Jan 2013 10:56:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.487 X-Spam-Level: X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFluOeeRAlNm for ; Wed, 30 Jan 2013 10:56:18 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9379121F87A4 for ; Wed, 30 Jan 2013 10:56:18 -0800 (PST) Received: from [172.20.10.2] (mobile-166-137-113-001.mycingular.net [166.137.113.1] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0UIuEsr073671 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jan 2013 12:56:15 -0600 (CST) (envelope-from ben@nostrum.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Ben Campbell In-Reply-To: <27757F55-1837-4CC0-B65D-07B1CA6F661A@edvina.net> Date: Wed, 30 Jan 2013 12:56:07 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130129004453.17046.96903.idtracker@ietfa.amsl.com> <4351AF92-3E60-4967-890B-33291473A10E@nostrum.com> <27757F55-1837-4CC0-B65D-07B1CA6F661A@edvina.net> To: Olle E Johanson X-Mailer: Apple Mail (2.1499) Received-SPF: pass (shaman.nostrum.com: 166.137.113.1 is authenticated by a trusted mechanism) Cc: Simple WG Subject: Re: [Simple] I-D Action: draft-ietf-simple-simple-08.txt X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 18:56:19 -0000 (as chair) Robert has asked us to progress this as soon as possible. I plan to go = ahead and do that for the existing version. That does _not_ mean we should ignore feedback, nor should we shut down = this discussion. We will just treat any further comments and discussion = as if they were IETF Last Call comments. Thanks! Ben. On Jan 30, 2013, at 1:49 AM, Olle E Johanson wrote: >=20 > 29 jan 2013 kl. 15:17 skrev Ben Campbell : >=20 >> (as chair) >>=20 >> We had a WGLC on version 06 of draft-ietf-simple-simple some time (as = in years) ago. It's been on hold since then to allow the other SIMPLE = work to substantially complete. Since our penultimate milestone = (simple-chat) has recently been approved by the IESG, it's time to = progress simple-simple and complete our final chartered milestone. >>=20 >> The only non-trivial change between 06 and 08 was the split of the = entry for the old msrp-acm draft into separate entries for RFC 6135 = (COMEDIA for MSRP) and RFC 6174 (CEMA), to account for the split of that = draft. >>=20 >> After conferring with the author and our AD, I think these changes = are pretty obvious and not likely to be controversial. Therefore we plan = to request publication of version 08. If anyone objects to that course = of action, please speak up asap. >=20 > Ok, I know I had years to make a comment, but anyway :-) >=20 > I would like to see references to the SIP domain certificate = specification, as it plays a role for implementors, as well as the SIP = certificate management service. These should be important for anyone = building SIMPLE implementations and adds some missing pieces in the = SIMPLE specs. >=20 > - RFC 6072 Certificate Maangement Service for Session Initiation = Protocol > http://tools.ietf.org/html/rfc6072 > - RFC 5922 Domain Certificates in the Session Initiation Protocol > http://tools.ietf.org/html/rfc5922 >=20 > Maybe we could add a clarification for newbies that "The SIP = subscribe/notify mechanism is not only used in SIMPLE, but also in other = event packages outside of the scope of this document." >=20 >=20 > I could possibly also add a section about the missing interoperability = in presence/XCAP implementations but that propably won't help this = particular document that I find has a lot of value. >=20 > See you all at SIPit 30! Only a few days of registration open - so = please hurry to http://www.sipit.net and register! > /O >=20 >>=20 >> Thanks! >>=20 >> Ben. >>=20 >>> From: internet-drafts@ietf.org >>> Subject: [Simple] I-D Action: draft-ietf-simple-simple-08.txt >>> Date: January 28, 2013 6:44:53 PM CST >>> To: i-d-announce@ietf.org >>> Cc: simple@ietf.org >>>=20 >>>=20 >>> A New Internet-Draft is available from the on-line Internet-Drafts = directories. >>> This draft is a work item of the SIP for Instant Messaging and = Presence Leveraging Extensions Working Group of the IETF. >>>=20 >>> Title : SIMPLE made Simple: An Overview of the IETF = Specifications for Instant Messaging and Presence using the Session = Initiation Protocol (SIP) >>> Author(s) : Jonathan Rosenberg >>> Filename : draft-ietf-simple-simple-08.txt >>> Pages : 15 >>> Date : 2013-01-28 >>>=20 >>> Abstract: >>> The IETF has produced many specifications related to Presence and >>> Instant Messaging with the Session Initiation Protocol (SIP). >>> Collectively, these specifications are known as SIMPLE - SIP for >>> Instant Messaging and Presence Leveraging Extensions. This document >>> serves as a guide to the SIMPLE suite of specifications. It breaks >>> them up into categories and explains what each is for and how they >>> relate to each other. >>>=20 >>>=20 >>> The IETF datatracker status page for this draft is: >>> https://datatracker.ietf.org/doc/draft-ietf-simple-simple >>>=20 >>> There's also a htmlized version available at: >>> http://tools.ietf.org/html/draft-ietf-simple-simple-08 >>>=20 >>> A diff from the previous version is available at: >>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-simple-simple-08 >>>=20 >>>=20 >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>>=20 >>> _______________________________________________ >>> Simple mailing list >>> Simple@ietf.org >>> https://www.ietf.org/mailman/listinfo/simple >>=20 >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org >> https://www.ietf.org/mailman/listinfo/simple >=20 From ben@nostrum.com Wed Jan 30 19:56:26 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C6021F8727; Wed, 30 Jan 2013 19:56:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.45 X-Spam-Level: X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iHSEtJwwopiK; Wed, 30 Jan 2013 19:56:24 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 406D821F8726; Wed, 30 Jan 2013 19:56:23 -0800 (PST) Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0V3uJfn032337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jan 2013 21:56:20 -0600 (CST) (envelope-from ben@nostrum.com) From: Ben Campbell Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Jan 2013 21:56:21 -0600 Message-Id: <4CBF82EB-0924-47B5-9022-1E9C9A7BD4CD@nostrum.com> To: IESG Secretary Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism) Cc: Simple WG Subject: [Simple] Request for Publication of draft-ietf-simple-simple-08 X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 03:56:26 -0000 Hi, The SIMPLE working group requests publication of = draft-ietf-simple-simple-08. The proto writeup follows: ------------------------------------------------------------ > Document Writeup >=20 > As required by RFC 4858, this is the current template for the Document > Shepherd Write-Up. >=20 > Changes are expected over time. This version is dated 24 February > 2012. >=20 > (1) What type of RFC is being requested (BCP, Proposed Standard, > Internet Standard, Informational, Experimental, or Historic)? Why is > this the proper type of RFC? Is this type of RFC indicated in the > title page header? >=20 The RFC is intended to be informational. The title header page indicates = informational. > (2) The IESG approval announcement includes a Document Announcement > Write-Up. Please provide such a Document Announcement Write-Up. Recent > examples can be found in the "Action" announcements for approved > documents. The approval announcement contains the following sections: Technical Summary The IETF has produced many specifications related to Presence and = Instant Messaging with the Session Initiation Protocol (SIP). = Collectively, these specifications are known as SIMPLE - SIP for Instant = Messaging and Presence Leveraging Extensions. This document serves as a = guide to the SIMPLE suite of specifications. It breaks them up into = categories and explains what each is for and how they relate to each = other. Working Group Summary This document servers as a roadmap to the SIMPLE specifications. It = introduces no technical content beyond the summaries of those = specifications. While some of the referenced specifications had some = degree of controversy, this draft was not controversial in itself. Document Quality. This document is a roadmap to other specifications, and therefore has no = directly implementable content. The document has undergone normal = working group review. There have been no specialized expert reviews, and = the shepherd does not believe such reviews are needed, other than those = normal for all documents (e.g. Gen-ART). Personnel The document shepherd for this document is Ben Campbell.=20 The responsible Area Director is Robert Sparks.=20 > (3) Briefly describe the review of this document that was performed by > the Document Shepherd. If this version of the document is not ready > for publication, please explain why the document is being forwarded to > the IESG. The document shepherd reviewed this document for content, structure, and = nits. There is a single outstanding nit (an informative reference to RFC = 3265 which has been obsoleted by RFC 6665). We plan to update that = reference along with any updates indicated by the IETF last call results = prior to final publication.=20 The shepherd believes the document to be otherwise ready for = publication.=20 > (4) Does the document Shepherd have any concerns about the depth or > breadth of the reviews that have been performed? =20 The document shepherd has no concerns about the depth or breadth=20 of the reviews.=20 > (5) Do portions of the document need review from a particular or from > broader perspective, e.g., security, operational complexity, AAA, DNS, > DHCP, XML, or internationalization? If so, describe the review that > took place. The shepherd believes all aspects of this document has been sufficiently = reviewed. There have been no specialized expert reviews, and the = shepherd does not believe such reviews are needed. > (6) Describe any specific concerns or issues that the Document = Shepherd > has with this document that the Responsible Area Director and/or the > IESG should be aware of? For example, perhaps he or she is = uncomfortable > with certain parts of the document, or has concerns whether there = really > is a need for it. In any event, if the WG has discussed those issues = and > has indicated that it still wishes to advance the document, detail = those > concerns here. The shepherd has no concerns about the document. It seems fairly = non-controversial. > (7) Has each author confirmed that any and all appropriate IPR > disclosures required for full conformance with the provisions of BCP = 78 > and BCP 79 have already been filed. If not, explain why. Author confirmation is pending at the time of submission. However, since = the document is comprised of summaries of and references to other = documents, the need for IPR disclosures seems unlikely. > (8) Has an IPR disclosure been filed that references this document? > If so, summarize any WG discussion and conclusion regarding the IPR > disclosures. There have been no IPR disclosures referencing this document. > (9) How solid is the WG consensus behind this document? Does it=20 > represent the strong concurrence of a few individuals, with others > being silent, or does the WG as a whole understand and agree with it? As an roadmap to other SIMPLE specifications, this document originally = had wide working group consensus. However, very little discussion has = occurred since then. The shepherd believes that this is to be expected = given the nature of the document as a roadmap to other work. No = significant objections have been raised to this document.=20 > (10) Has anyone threatened an appeal or otherwise indicated extreme=20 > discontent? If so, please summarize the areas of conflict in separate > email messages to the Responsible Area Director. (It should be in a > separate email because this questionnaire is publicly available.)=20 No one has threatened an appeal or otherwise indicated extreme=20 discontent.=20 > (11) Identify any ID nits the Document Shepherd has found in this > document. (See http://www.ietf.org/tools/idnits/ and the = Internet-Drafts > Checklist). Boilerplate checks are not enough; this check needs to be > thorough. The Document Shepherd believes that the document contains all needed=20 information, and that all nits are covered except for the obsolete = reference mentioned in section (3). > (12) Describe how the document meets any required formal review > criteria, such as the MIB Doctor, media type, and URI type reviews. The document has not gone through any formal review beyond routine = working group reviews. The shepherd does not believe any such reviews = are needed. > (13) Have all references within this document been identified as > either normative or informative? All references are identified as informative. > (14) Are there normative references to documents that are not ready = for > advancement or are otherwise in an unclear state? If such normative > references exist, what is the plan for their completion? There are no normative references. There is an informative reference to = draft-ietf-simple-chat, which has been approved for publication by the = IESG. > (15) Are there downward normative references references (see RFC = 3967)? > If so, list these downward references to support the Area Director in=20= > the Last Call procedure.=20 There are no normative references. > (16) Will publication of this document change the status of any > existing RFCs? Are those RFCs listed on the title page header, listed > in the abstract, and discussed in the introduction? If the RFCs are = not > listed in the Abstract and Introduction, explain why, and point to the > part of the document where the relationship of this document to the > other RFCs is discussed. If this information is not in the document, > explain why the WG considers it unnecessary. This document does not effect the status of any existing RFC. > (17) Describe the Document Shepherd's review of the IANA = considerations > section, especially with regard to its consistency with the body of = the > document. Confirm that all protocol extensions that the document makes > are associated with the appropriate reservations in IANA registries. > Confirm that any referenced IANA registries have been clearly > identified. Confirm that newly created IANA registries include a > detailed specification of the initial contents for the registry, that > allocations procedures for future registrations are defined, and a > reasonable name for the new registry has been suggested (see RFC = 5226). The shepherd has extensively reviewed the IANA considerations, and = determined that the draft makes no request of IANA, nor are any such = requests appropriate. (The shepherd further notes that the IANA considerations consist = entirely of the word "None.") > (18) List any new IANA registries that require Expert Review for = future > allocations. Provide any public guidance that the IESG would find > useful in selecting the IANA Experts for these new registries. The document does not establish any new registries. (Really, it says = "None.") > (19) Describe reviews and automated checks performed by the Document > Shepherd to validate sections of the document written in a formal > language, such as XML code, BNF rules, MIB definitions, etc. The draft contains no formal language requiring validation. From iesg-secretary@ietf.org Thu Jan 31 14:04:51 2013 Return-Path: X-Original-To: simple@ietfa.amsl.com Delivered-To: simple@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A148021F848B; Thu, 31 Jan 2013 14:04:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.518 X-Spam-Level: X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yOIRBUeYhSk4; Thu, 31 Jan 2013 14:04:50 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 375D321F8440; Thu, 31 Jan 2013 14:04:50 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.37 Message-ID: <20130131220450.537.87860.idtracker@ietfa.amsl.com> Date: Thu, 31 Jan 2013 14:04:50 -0800 Cc: simple@ietf.org Subject: [Simple] Last Call: (SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP)) to Informational RFC X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 22:04:51 -0000 The IESG has received a request from the SIP for Instant Messaging and Presence Leveraging Extensions WG (simple) to consider the following document: - 'SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence using the Session Initiation Protocol (SIP)' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-02-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIMPLE - SIP for Instant Messaging and Presence Leveraging Extensions. This document serves as a guide to the SIMPLE suite of specifications. It breaks them up into categories and explains what each is for and how they relate to each other. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-simple-simple/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-simple-simple/ballot/ No IPR declarations have been submitted directly on this I-D.